Related
USB/MicroSD mount is working, but I cannot get ADB to work. This is really pissing me off. I had it working fine on Vista but I'm a dumbass and decided to upgrade to Win7 Ultimate.
Device Manager does not show "Android Composite ADB Interface" or "Nexus One" or anything that looks remotely like that.
The instructions here: http://forum.xda-developers.com/showthread.php?t=613054 -- do not work for me, as you can see in the screenshot I've provided below, nothing shows up.
SCREENSHOT (same also attached in case something happens to the link): http://imgur.com/uoaWH.jpg
1. The Android SDK is installed.
2. Java JDK 64 & 32 bit versions are both installed.
3. Plugged in my phone, turned on USB Debugging, nothing happened. Device manager list didn't change at all. No alerts near the systray from Win7.
4. I used "USB Deview" and uninstalled everything that looked like "Google" or "HTC" (saw nothing that said HTC or Android, just Google).
5. After #4, gave this POS a reboot, no change when plugging the phone in.
I have the driver downloaded, separately, as well as the one that comes with the Android SDK.
I'm at a complete loss.
Help is deeply, truly, appreciated, and I'll be clicking on some "DONATE" links if you can help me fix this.
EDIT: RESOLVED
Windows7 didn't like this ROM: http://forum.xda-developers.com/showthread.php?t=702191
But it loves this one: http://forum.xda-developers.com/showthread.php?t=714184
Needless to say... I'm pretty happy!
usb driver installed?
rori~ said:
usb driver installed?
Click to expand...
Click to collapse
Yes.
And USB debugging is enabled.
I can mount the SD, but it looks like Windows thinks my phone is nothing more than a storage device. The ADB crap is not showing up in the Device Manager like it did on Vista, nor is there *anything* that says "Nexus One" except in... see new screenshot.
http://imgur.com/J7OzA.jpg
Is your Nexus running 2.2?
I had this exact problem as soon as I updated to 2.2; Windows 7 simply refuses to accept the device.
Put your device in recovery mode and see if fastboot can detect it. For me it can, but ADB and DDMS both think nothing is connected when the phone is on and in debug mode.
I have a HTC Magic as well which works absolutely fine (even when running CM6, which is 2.2 based) but the Nexus on 2.2 is just a no go. If you've unlocked your bootloader you could downgrade to 2.1 again. I never had problems on Win7 with 2.1.
Your only other option is to add your comments to the bug, here: code.google.com/p/android/issues/detail?id=9437 (sorry, I'm still not allowed to post proper links yet)
It seems very few people are experiencing this (or reporting it when they do) so my hopes for them fixing it are pretty low.
Are you on version R3 of the USB driver?
What happens when you plug in the phone with usb debugging turned on (on the status bar) ?
Does it ask for a driver? if so manually point it to C:\android-sdk-windows\usb_driver (may differ)
below is a SS of the driver files being uses on my win-7 64 bit desktop.
Try something for me. I am having the same as you but try this. Boot your phone in recovery mode and see if adb works then. My pc sees the phone as adb in recovery but it doesn't see it as adb on the home screen. Not sure why this is but it worked at one time.
Prod1702 said:
Try something for me. I am having the same as you but try this. Boot your phone in recovery mode and see if adb works then. My pc sees the phone as adb in recovery but it doesn't see it as adb on the home screen. Not sure why this is but it worked at one time.
Click to expand...
Click to collapse
Holy ****.
I love you.
I've been pulling my hair out. Seriously.
I booted into recovery, plugged the phone in, Windows tried installing drivers, but failed, then I saw "Nexus One" listed in Device Manager, and after installing the drivers that came with the SDK, the "Android Phone" and "Android Composite ADB Interface" stuff shows up in the device manager, and adb commands work... when my phone is booted into Recovery.
Recovery was the key.
Thank you!!!!!!
Could the ROM I'm using have anything to do with this?
ADB recognizes the device when I'm recovery, and the "adb push" commands do their thing, but I don't see the files being pushed where I'm pushing them to.
Do I just have to enable the "USB toggle" thing?
I just installed Win 7 and used these directions from the android developers website and everything worked flawlessly from the getgo:
http:// developer.android.com/sdk/index.html/
Hmmm, correct url, not working, 404, maybe it'll work if you copy/paste and take the spaces out from between // and developer.
What recovery image are you using? I've had good luck with ClockworkMod and it's 'mount system' option as far as push/pull while in recovery.
IT WAS THE ROM.
I went back to the ROM I was using previously, and ADB WORKS FINE NOW IN WINDOWS 7.
I was using this ROM: http://forum.xda-developers.com/showthread.php?t=702191
adb remount
adb devices
Nothing worked!
Completely wiped and, went back to this: http://forum.xda-developers.com/showthread.php?t=714184
It works now!!!
Something had to be wrong....that's stable rom. There's more than one custom rom that has it for a base.
pendo said:
Something had to be wrong....that's stable rom. There's more than one custom rom that has it for a base.
Click to expand...
Click to collapse
I'm not knocking the ROM or the developer of the ROM, but I made a backup, wiped everything, flashed the MCR ROM again, went back to the same problem.
Putting the other ROM back... no more problem. ADB commands work fine, and Windows7 sees my phone.
Ryjabo said:
I'm not knocking the ROM or the developer of the ROM, but I made a backup, wiped everything, flashed the MCR ROM again, went back to the same problem.
Putting the other ROM back... no more problem. ADB commands work fine, and Windows7 sees my phone.
Click to expand...
Click to collapse
And I don't doubt what you're saying...I was just thinking it was strange.....but hey strange things do happen so who knows, lol.
I just recently got into modding my N1 a few weeks ago and finally hit my first snag:
Original root was through superoneclick, so bootloader is still locked. I flashed over to stock GRI40 OTA without realizing (stupidly) that flashing
it would also flash over my RA recovery and unroot my phone. Now, superoneclick is incompatible with GRI40, so I can't re-root through that, and I'm having trouble
with unlocking the bootloader through fastboot.
I get no response from ADB or fastboot in windows cmd prompt when I boot phone to FASTBOOT.
the command "fastboot devices" gives me a repeat of the same prompt with no error. (I can't get fastboot to work in normal debugging mode either, and I don't know if it usually will, because this is the first time I've used it.)
the command "adb devices" gives me response-- "list of devices attached" with nothing below (ADB works fine in debugging mode though).
I thought it might be a driver problem, but "Android bootloader Interface" driver is on the device manager list while phone is in fastboot, and seems to be properly
installed; I can't seem to find another suitable driver to update it to anyways.
Beyond that, there don't seem to be any other drivers running in the device manager either.
It's to the point where I'm considering taking the long way around and re-rooting through passimg, but that may not work anyways from what I've been reading, and that still won't fix my fastboot issue.
Any ideas on why I can't get fastboot to work?
my devise manager lists it as 'Android 1.0' when connected with fast boot..
if the drivers were installed on their own, then uninstal them.. and manually update the drivers (download them yourself)
that might help.. idk..
Sent from my nexus one
I think that may be part of the problem because I'm not seeing Android 1.0 on the device manager list. I do have an unknown device on there, but I can't update the driver with any of the Google USB drivers. Also, I'm pretty sure it's not my N1 because I'll unplug the N1, delete the unknown device, and scan for hardware changes and it will pop up again, so I don't think it has anything to do with my phone.
Put your phone in to fast boot, plug the phone in to a different port on your computer. If you have been plugging it in to the front, plug it in to the back. If you have been plugging it in to the back, plug it in to the front.
This should force windows to re-detect your device and it will hopefully install the missing drivers you're needing...
That was a good idea, but I had no luck with that one either. Thanks though.
Alright, shreyas said device is "Android 1.0" from windows device manager when the phone is in fastboot. Why does mine say "Android Bootloader Interface" and is this the case for everyone else?
Even more interestingly, I'll uninstall it, manually install whatever driver I chose for it, and that installation will fail. Then, I'll uninstall it again and have 'puter automatically scan for hardware, "android 1.0" pops up as one of the unknown devices but then gets reassigned as "android Bootloader Interface" after automatically installing drivers.
Oh yeah, I'm running Windows 7 64.
The drivers mentioned here didn't help either
http://forum.xda-developers.com/showthread.php?t=702927
stratmn5105571 said:
Oh yeah, I'm running Windows 7 64.
Click to expand...
Click to collapse
i am on win7 32!
btw umm try this link
http://android.modaco.com/content/z...com/319156/winxp-7-zte-blade-drivers-and-adb/
another umm stupid thing mayb, did you try out adb wireless..?
Have you tried using the PDANet drivers? Those are the ones that I've had the best luck with on my Win7 x64 laptop.
EDIT: Seems you have...
I'd recommed using an application called USBDeView (I think?) to manually uninstall all USB drivers for Android/HTC/ADB/NexusOne/etc, and THEN installing the PDANet drivers.
Thanks for your help. I ended up downloading "superboot," which has fastboot on it, and it works just fine. I don't know what the deal is with the fastboot that came with the SDK but my computer just doesn't seem to like it. I checked and rechecked all commands and file directories, and I just don't get it...oh well, I hope this helps others.
Thanks again.
CAPTIVATE - Frozen on AT&T Boot, Unrecognized via USB, NO access to CWM - PLEASE HELP
HI - I've been fighting this captivate for over 48 hours. Being very familiar with all this, and not doing this for the first time either, the fact that I can't get this resolved drives me insane as I have never been so mentally exhausted in being incapable of resolving a problem, thus seeking professional guidance from the Gods on mobile technology!
HERE IS THE SPIEL:
Device: Samsung Captivate i897 (Device is rooted)
Software: AOKP build.38
Kernel: IcyGlitch v14
CWM: Installed v.5-----
The Problem
Device stuck at AT&T Logo - Not Looping (just stuck)
Windows XP Professional SP3 (x86) with all recommended USB drivers will not detect device. Device Manager displays the phone as unknown, regardless of drivers & upon inputting it into a USB (2.0) windows displays a message "USB Device is not recognized".
Windows 7 Ultimate SP1 (x64) brings up identical message as that of Windows XP with all proper & recommended drivers with the phone recognized as "unknown"
Device boots into download mode via holding Vol.+/- and plugin in USB cable. Both Heimdall & Odin can't recognized the device when it's in UNKNOWN state by windows. Although all drivers are installed.
Purchased new Micro USB cable - NOTHING - that's testing all USB ports on all my systems.
The Story:
The device was working flawlessly being able to mount as mass storage on both my Windows 7 Ultimate SP1 (x64) & Windows XP Professional SP3 (x86) until i've upgraded to AOKP build #38. The upgrade was successful (2 months ago). 2 days ago, i decided to upgrade to AOKP build #40. The device was not recognized as mass storage but rather "Unknown Device" or "USB Device not Recognized" - although the phone was in full working condition (USB Debugging was enabled). After some reading, I realized that the AOKP build #38 has a bug where there was a problem with mounting & the camera was not functioning since it had no access to external_sd (a problem that was very irritating since the update, but i had no time to look into it until recently). I followed a similar tutorial (http://forum.xda-developers.com/showthread.php?t=1545801) which required the editing of the vold.fstab file with Root Explorer, resolving the issue of external_sd becoming accessible on the phone with camera working, however unable to mount and copy the new AOKP Build 40 ROM through Windows to flash via CWM.
At this point I booted into CWM via holding volume +/- & power button. Wiped everything, and loaded a backup I've done a # of months ago where everything was working perfectly. There was an error when it was "...loading data image" which is normal, so I did it again and the error persisted. On the second attempt, it again re-sent me primary CWM menu where i was intending to now load another backup. I accidentally clicked the restart button, having already cleaned the devlick cache, etc, including user data which brought me this NIGHTMARE of problems.
I will be forever grateful the the kind soul which will help me resolve this, as I am at a phase of taking this samsung captivate and throwing it against a wall.
I assume you can still access recovery? Try putting CM9 on the external SD with a card reader, and flashing that...
EDIT: Just saw you can't access CWM... Try recovery again... all three until ATT comes up, immediately let off power... Try multiple times... Leave the battery out, hold all three, have someone else insert it, and let off power at ATT... When going into download mode, leave the battery out, hook it up, hold boths vols, and insert the battery...
The Unknown device issue....
Uninstall your drivers... Here are drivers to manually install, they are 64bit... so try right clicking the Unknown device in device manager and doing a manual driver update...
OP,
See this thread... Captivate Connection Issues...
Sent from my SAMSUNG-SGH-I777 using xda premium
B-Naughty: Thank you. I have tried this & that no luck. Even loaded Linux Mint 13, however heimdall is being a !*&#@ in loading the firmware...Perhaps if you would know any (proper) packages for a Samsung Captivate i897 via heimdall id be grateful. I used heimdall-suite-1.3.2 command line & frontend. Will try again tomorrow. Although still haven't figured out whether or not it read the phone in Linux (it's a different world for me)
4-2ndtwin: My friend, thank you for the detailed link. I have been doing this for over 48 hours ... nothing. I'll give it another shot via Linux, if not i'll try Ubuntu. Truly am just confused out of my mind, never had this before.
PS: The phone's data is wiped & it's stuck at AT&T when loaded via power button. Booting into DOWNLOAD MODE isn't a problem. All combination to load into recovery, did not work. I mean...there must be a way! There always is...Any further ideas or should i simply through it out and buy a Galaxy SIII?
I897UCKK4 Stock, Wipe, with option to install Bootloaders, Param,and Repartition-Heimdall One-Click
And try all of your USB cords, I don't know what you bought, but a bad one, or a lot of times an aftermarket one won't work...
Edit:
I saw you can get into download mode. So my original post doesn't help much.
Have you tried installing the Andoid SDK and downloading the nexus drivers from there? Perhaps your device now thinks it is a nexus. It might be worth a shot.
^
+ 1
Yes... I second this ^
Sent from my SAMSUNG-SGH-I777 using xda premium
This happened to me and I just reflash the boot loader and reinstalled the same from to keep my data
Decrapitated Samsung
Thank you all for the support.
At this point I've installed SDK Manager w/Google USB revision 6, latest Java, all proper drivers...nothing. Tried all usbs on all systems.
Q: If the phone goes into download mode, is it not in a default state and must be detected? I have a samsung galaxy tab 10.1, detects immediately. Samsung YPS3 mp3 player detects immediately - Samsung Captivate however, nothing...
I set up a clean Windows 7 Ultimate x64bit (all june 2012 updates + .Net 4.0). Installed all usb drivers...same thing, UNKNOWN DEVICE - so the usb cable works...but now when you go and manually upgrade driver via device manager, it says that the best driver for the unknown device is already installed.
Anyone want's a free captivate lol...
At this point...I dont even know what to ask...since i've tried everything. I'll try to revisit Ubuntu & Linux later this evenings and report status!
Thanks for the I897UCKK4 Stock, Wipe, with option to install Bootloaders, Param,and Repartition-Heimdall One-Click link, i can't use it since the phone isn't detected by the application
I would say you need to uninstall any/all drivers for your captivate. This includes heimdall installed drivers. Make sure to uninstall the drivers for the "unknown" device also.
kScorpion said:
Thank you all for the support.
At this point I've installed SDK Manager w/Google USB revision 6, latest Java, all proper drivers...nothing. Tried all usbs on all systems.
Q: If the phone goes into download mode, is it not in a default state and must be detected? I have a samsung galaxy tab 10.1, detects immediately. Samsung YPS3 mp3 player detects immediately - Samsung Captivate however, nothing...
I set up a clean Windows 7 Ultimate x64bit (all june 2012 updates + .Net 4.0). Installed all usb drivers...same thing, UNKNOWN DEVICE - so the usb cable works...but now when you go and manually upgrade driver via device manager, it says that the best driver for the unknown device is already installed.
Anyone want's a free captivate lol...
At this point...I dont even know what to ask...since i've tried everything. I'll try to revisit Ubuntu & Linux later this evenings and report status!
Thanks for the I897UCKK4 Stock, Wipe, with option to install Bootloaders, Param,and Repartition-Heimdall One-Click link, i can't use it since the phone isn't detected by the application
Click to expand...
Click to collapse
Seems as though you have a hardware problem with the phone, or a s/w problem so messed up you're down to Unbrickable Mod
---------- Post added at 08:35 PM ---------- Previous post was at 08:34 PM ----------
Red_81 said:
I would say you need to uninstall any/all drivers for your captivate. This includes heimdall installed drivers. Make sure to uninstall the drivers for the "unknown" device also.
Click to expand...
Click to collapse
He had a fresh Windows install and install drivers...
Unbrickable MOD - wont be able to do this my self, would need an electric to look into it. I mean the phone isn't bricked, it accesses download mode i just have to get it to connect via usb to be read as a "samsung composite device" to flash the bootloader. As now, it would be stuck at the AT&T screen without giving access to CWM.
I have installed Ubuntu 12.04 - set up java 7 - loaded Heimdall One-Click stock rom provided above via java...tried all USB's phone not detected via DOWNLOAD MODE. Phone not detected at all!
This is just insane...If it's in DOWNLOAD MODE, it should be accessible, not the contrary. Ubuntu doesn't need usb drivers, should be plug&play...Both XP & Win7Ultimate at least recognized the phone as an unknown device. On Ubuntu it does nothing at all, as if it never was plugged in.
The microusb slot on the phone is not damaged / cable is stock, also have another one from Staples. The system w/XP is reading all devices on a plug&play basis and read the captivate before flawlessly. Same applies to the Asus P43 laptop, which read the device without hesitation on Win7 Ultimate x64. The Ubuntu is now on the laptop...tried connecting the Galaxy Tab 10.1 (Samsung) it recognized it immediately...with full access to files etc.
Last plea for Ideas...before i'll send this captivate to hell, to where the journey isn't captivating at all!
It sounds like you have a bad flash. You need jtag to fix this issue. Contact mobiletechvideos and Josh should be able to repair it for you. I think at this point you've tried every other option.
Sent from my SAMSUNG-SGH-I897 using xda premium
kScorpion said:
Thank you all for the support.
At this point I've installed SDK Manager w/Google USB revision 6, latest Java, all proper drivers...nothing. Tried all usbs on all systems.
Q: If the phone goes into download mode, is it not in a default state and must be detected? I have a samsung galaxy tab 10.1, detects immediately. Samsung YPS3 mp3 player detects immediately - Samsung Captivate however, nothing...
I set up a clean Windows 7 Ultimate x64bit (all june 2012 updates + .Net 4.0). Installed all usb drivers...same thing, UNKNOWN DEVICE - so the usb cable works...but now when you go and manually upgrade driver via device manager, it says that the best driver for the unknown device is already installed.
Anyone want's a free captivate lol...
At this point...I dont even know what to ask...since i've tried everything. I'll try to revisit Ubuntu & Linux later this evenings and report status!
Thanks for the I897UCKK4 Stock, Wipe, with option to install Bootloaders, Param,and Repartition-Heimdall One-Click link, i can't use it since the phone isn't detected by the application
Click to expand...
Click to collapse
did u try reverting back to stock using ODIN 1 Click Stock Firmware Installer? there's a tutorial on youtube by mobiletechvideos original post by connexion2005.
Samsung Captivate (ODIN 1 Click Stock Firmware Installer)
youtube.com/watch?v=UDtxnH4lFuk
I would like to have that free captivate thou :good:
Same Problem
i have the same prob and if i try to recovery mode (i.e. by pressing volume buttons and power button simultaneously)
i get following type of errors
"E:failed to mount /cache (Invalid argument)
E:Can't mount/cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log"
kindly sugeest some way out
I have done everything possible to get it connected and recognized by the PC & all is failing. I have tried to "manually" install the Samsung composite Device driver via "have disk method in Device Manager.
In XP:
I load device manager and than do the following:
Click Universal Serial Bus Controllers
Right click "unknown device" which is the captivate
Select Update Driver
Select Install from a list or specific location (Advanced)
Select Don't Search. I will choose the driver to install. (Click Next)
Select "Have Disk" with the (show compatible devices) checked
Browse to the directory of extracted 32bit Windows XP Drivers: SGH-i897_Captivate_USB_Drivers_5_02_0_2
Select "ssadadb2.inf" & click open
And than i get the msg saying:The specified location does not contain information about your hardware
...WTF... I mean really...
Windows 7 Ultimate:
Same procedure as above until you select have disk, pick a proper x64 driver provided by XDA - also tried the Universal_Naked_Driver_Beta_0.6 ...there was progress that got me very excited - the Phone was detected as: Samsung Android Composite Device. Was I happy...until i clicked next and got this msg:Samsung Android USB Composite Device - This device cannot start. (Code10)...
There must be a solution: I had the phone bricked when i first tried to change from stock rom, managed to load it in download mode, and it was detected fine on all systems via USB with the same accessories, worked like a charm...so when this happened i wasn't concerned, as i thought id follow standard procedure, accept it did not work.
Anyone?
Let's try this since you seem to be stuck in a boot loop.
Code:
adb wait-for-device reboot recovery
Make sure your phone is plugged in and reboot it. If your machine recognizes the phone at any point in the boot process it will kick it into recovery.
Once there you can try to restore the backup again.
If this doesn't work, you will most likely need JTAG service. Because of the bad image flash your device might not "think" it is a Captivate any longer and that's why the drivers aren't working.
Red_81 :Thank You. Would you please be more specific & put into a 1,2,3...process?
1. Power off device
2. Plug in to computer
3. Open a command prompt
4. Navigate to adb.exe (android sdk or inside my kk4 root utility)
5. Enter command above
6. Boot up phone.
7. Hopefully go into recovery
Sent from my SGH-I777 using xda premium
Thank you. I've been endlessly fighting the achievement of the PC systems to detect the captivate & no results. Thank you all for you help...when i have time i'll JTAG this device, or probably not even going to bother and pick up a SGIII. By the way Red_81:http://forum.xda-developers.com/showthread.php?t=1680048 is an amazing app, if only my phone was detected as it's recognized as unknown device, so there isn't much it can do. Although i highly recommend it to anyone else whose phone is detected.
Okay so i did something i shouldn't of.
After buying a T-mobile dell streak 7 online, i found out it had been rooted with clockwork recovery mod by dj steve v4.0.1.4. When i tried working with it i found out i couldn't use the phone functions of the tablet so i decided to do a factory reset in the settings. To my dismay the problem only got worse and now when the tablet boots up normally it asks me for a password that wasn't on there before. I read on a thread somewhere that this is because the device is trying to decrypt something but that it's because there's no OS on it. I can still boot up in recovery mode and perform all the options in there.
So i bought a usb cable for it hoping that i would be able to flash it back to factory settings, but now i am unable to get it to work with usb.
I have a win 7 64 bit and i have tried downloading divers from all kinds of places which seem to be the right ones but windows will not allow me to install them and insists that the best ones are installed.
I've downloaded android sdk tools and installed all the components that are pertinent to this version and make (at least i think)
I've tried downloading PDAnet, the pc sync tool that is available on the dell site and that didn't work either. Under fastboot mode on the tablet the driver is installed correctly but still appears as a unknow device and i don't see the fastboot window show up when i plug it in so...
I've literally read hundreds of threads to see if maybe i could do it by placing update.zip files on the sd card and then installing them under CWM, some have worked, some haven't but when i reboot it's still the same.
Please help!!!
timaloud said:
Okay so i did something i shouldn't of.
After buying a T-mobile dell streak 7 online, i found out it had been rooted with clockwork recovery mod by dj steve v4.0.1.4. When i tried working with it i found out i couldn't use the phone functions of the tablet so i decided to do a factory reset in the settings. To my dismay the problem only got worse and now when the tablet boots up normally it asks me for a password that wasn't on there before. I read on a thread somewhere that this is because the device is trying to decrypt something but that it's because there's no OS on it. I can still boot up in recovery mode and perform all the options in there.
So i bought a usb cable for it hoping that i would be able to flash it back to factory settings, but now i am unable to get it to work with usb.
I have a win 7 64 bit and i have tried downloading divers from all kinds of places which seem to be the right ones but windows will not allow me to install them and insists that the best ones are installed.
I've downloaded android sdk tools and installed all the components that are pertinent to this version and make (at least i think)
I've tried downloading PDAnet, the pc sync tool that is available on the dell site and that didn't work either. Under fastboot mode on the tablet the driver is installed correctly but still appears as a unknow device and i don't see the fastboot window show up when i plug it in so...
I've literally read hundreds of threads to see if maybe i could do it by placing update.zip files on the sd card and then installing them under CWM, some have worked, some haven't but when i reboot it's still the same.
Please help!!!
Click to expand...
Click to collapse
You need to grab a NVFLash pack, put device in APX mode, install the APX drivers, and install a complete full restore.
reply
giveen said:
You need to grab a NVFLash pack, put device in APX mode, install the APX drivers, and install a complete full restore.
Click to expand...
Click to collapse
Thank you so much for taking your time to help.
Ok so i downloaded NVFlash, that i have found to be able to put my device in APX mode i need to hold down the power button and the volume - button at the same time when booting up but that sends me to fastboot. Is this the same as APX ? Sorry i don't know much about this.
Also when you say install the APX drivers, i have not been able to find these, could you send me a link ?
I don't mean to be rude or mean, but this is a question that has been answered a hundred times here, please look around and read a bit, we are getting tired of holding baby hands.
Thanks for your imput
giveen said:
I don't mean to be rude or mean, but this is a question that has been answered a hundred times here, please look around and read a bit, we are getting tired of holding baby hands.
Click to expand...
Click to collapse
Hey! Thank you for answering. Please don't be too quick to pass judgement, I have read hundreds of threads and i have downloaded all kinds of different drivers, roms, and recovery images. I've followed all the instructions of the related posts but the Tablet's OS wont boot up. I cannot install any .pkg updates because any option i select when i boot it up holding down power and volume + buttons sends me to CWM recovery mod and all the update.zip roms that i have installed this way have made no difference.
I have come to the conclusion that i need to flash a recovery image from the computer but i cannot because all the drivers i have found for it have not worked. My device does not appear as a drive therefore i can't see it in nvflash or even windows for that matter. yesterday i called dell support to see if they had any drivers available that weren't already posted on their site but with no luck.
The reason i'm writing this is because i was hoping someone had a similar problem and could help me, i know you deal with people that don't even take the trouble to look into the other threads every day, but believe me i have.
If you can help i would greatly appreciate it, or point me to what i'm doing wrong Tks.
In NVflash or APX mode the S7 doesn't appear as a drive. With your S7 on plugged into your PC, you don't see it as a drive? This should work right out of the box. Although some have reported the manual mentioned Driver. Zip folder is missing.
If hold the Volume + and - button in a plug into your PC, do your hear a beep? If so, you would then go into the device manager, select the APX device and install the drivars from the NVflash download package.
These videos posted by "giveen" may help as well: http://www.youtube.com/playlist?list=PLB99FAE280F618B12
awesome
wptski said:
In NVflash or APX mode the S7 doesn't appear as a drive. With your S7 on plugged into your PC, you don't see it as a drive? This should work right out of the box. Although some have reported the manual mentioned Driver. Zip folder is missing.
If hold the Volume + and - button in a plug into your PC, do your hear a beep? If so, you would then go into the device manager, select the APX device and install the drivars from the NVflash download package.
These videos posted by "giveen" may help as well:
Thank you so much, i was finally able to install the drivers in APX mode. Flashing it from here shouldn't be too much of a hassle. Very grateful for your help. Cheers
Click to expand...
Click to collapse
some assistance please.
I've been at it for about 40 minutes now, trying to sideload 5.1 onto the N6. Go me! Unfortunately I have come to a halt due to my computer not being able to recognize my device in recovery mode. I have the nexus root tool kit installed on my Win7 PC and i have done all the steps as far as driver installation and the toolkit says it is a success. I even open up command prompt when the device is turned on and type "adb devices" and it gives me the device info, I can even use my explorer to see the files I have in storage on the device too. Now if I type the same command while the device in in recovery mode, my computer tells me the device is not found. I have since downloaded the google drivers and tried updating the driver manually through Device Manager and that tells me that the drivers are up to date/best driver is already installed etc. So after goofing with that for a few tries, I uninstalled ALL nexus/google drivers and reinstalled them, twice now, with the same result.
Am I doing something wrong? Why does my computer not want me to update? why does it hate me?
melficeapollo said:
some assistance please.
I've been at it for about 40 minutes now, trying to sideload 5.1 onto the N6. Go me! Unfortunately I have come to a halt due to my computer not being able to recognize my device in recovery mode. I have the nexus root tool kit installed on my Win7 PC and i have done all the steps as far as driver installation and the toolkit says it is a success. I even open up command prompt when the device is turned on and type "adb devices" and it gives me the device info, I can even use my explorer to see the files I have in storage on the device too. Now if I type the same command while the device in in recovery mode, my computer tells me the device is not found. I have since downloaded the google drivers and tried updating the driver manually through Device Manager and that tells me that the drivers are up to date/best driver is already installed etc. So after goofing with that for a few tries, I uninstalled ALL nexus/google drivers and reinstalled them, twice now, with the same result.
Am I doing something wrong? Why does my computer not want me to update? why does it hate me?
Click to expand...
Click to collapse
Here is a channel i subscribe and the guy goes in detail about wugfresh root tool kid, some of the videos are from december. hope it helps.
https://www.youtube.com/channel/UCWhQwvCaC2ZMkCnrC15NfAw
i went the the link and viewed a video about sideloading through the toolkit, never knew i could do that, but i still came across the same problem. my computer wont recognize it.. smh..
melficeapollo said:
i went the the link and viewed a video about sideloading through the toolkit, never knew i could do that, but i still came across the same problem. my computer wont recognize it.. smh..
Click to expand...
Click to collapse
When you get the device not found error, unplug USB and reconnect. May have to repeat once or twice.
Evolution_Freak said:
When you get the device not found error, unplug USB and reconnect. May have to repeat once or twice.
Click to expand...
Click to collapse
Tried that like it was going out of style lol. No luck.
i finally got it figured out!!
i used the toolkit and install;ed Universal Google Drivers (option #3) and my pc was finally able to detect my device in recovery mode.
so if anyone comes across the same problem of not having the "right" drivers or not having your device detected,
1.) Install Universal Google Drivers and reboot your computer
2.) proceed to sideload your update.