So my nexus won't charge unless its off.. and it won't connect to my computer either. I can't send it in to Sam's club (or can i?) if its rooted. I needdddddd some major help figuring out some way i can replace it... a way to unroot + lock the bootloader. Please? anyoneeeee? By the way... i have no idea how to use adb and stuff because i used a one-click script :/
Things like this is where I really hate how there are one click scripts.
If you aren't knowledgeable about what the tool is doing, don't do it.
Since its probably easier for you to just use another one click tool, use Wug Fresh's one click and use "Return to Stock"
Please, for the love of god, don't do this to your device if you don't know what you are doing.
rohan32 said:
Things like this is where I really hate how there are one click scripts.
If you aren't knowledgeable about what the tool is doing, don't do it.
Since its probably easier for you to just use another one click tool, use Wug Fresh's one click and use "Return to Stock"
Please, for the love of god, don't do this to your device if you don't know what you are doing.
Click to expand...
Click to collapse
He said he can't connect to his PC (broken USB port, I guess).
You may be able to unroot it, but you probably cannot lock the bootloader without USB. Sorry, I don't know of a way to.
OP, you could at least do a Factory data reset under Backup & reset in Settings. I doubt that that would lock and unroot the device, but I don't think Sam's Club would really care.
Is it because you need someone to set up the drivers and get ADB working on your computer?
Is your device recognized at all when you connect it to a computer?
You can probably try to factory reset, if you haven't flashed other ROMs.
Also, if you flashed ClockWork Mod bootloaders, Google how to root HTC One X.
CharliesTheMan said:
Is it because you need someone to set up the drivers and get ADB working on your computer?
Is your device recognized at all when you connect it to a computer?
Click to expand...
Click to collapse
I have adb set up... just no idea how to use it. No, it isnt.
I did factory reset... to no avail...
1. Did you install a custom Kernel or ROM?
2. Your computer doesn't even make any sort of "ding" sound when you plug the tablet in? How about if you slowly wiggle the cable around in the tablet?
Well if you managed to root your tablet using a toolkit then you're computer must have a functioning port. the toolkit probably has a return to stock option so run it. Factory/data resets will only wrote the data partition but will not touch system/bootloader. You will need access to a computer in order to fully return to stock with the bootloader locked.
Ryands991 said:
1. Did you install a custom Kernel or ROM?
2. Your computer doesn't even make any sort of "ding" sound when you plug the tablet in? How about if you slowly wiggle the cable around in the tablet?
Click to expand...
Click to collapse
Nope, it was running stock. Nope! It works if the device is OFF though.
evonc said:
Well if you managed to root your tablet using a toolkit then you're computer must have a functioning port. the toolkit probably has a return to stock option so run it. Factory/data resets will only wrote the data partition but will not touch system/bootloader. You will need access to a computer in order to fully return to stock with the bootloader locked.
Click to expand...
Click to collapse
Thing is... my computer will NOT recognize the device. It will charge it if its off but thats it.
speednub said:
Thing is... my computer will NOT recognize the device. It will charge it if its off but thats it.
Click to expand...
Click to collapse
How did you root it if your PC doesn't recognize it. Make sure adb is enabled in dev options. Also try typing "adb devices" in your computer after you have adb setup. If it doesn't work get the universal drivers from the dev section and reinstall the drivers.
Boot into the bootloader (Power+Volume down), does your computer detect anything at all?
Any unknown devices or familiar device names in "Device manager"?
Edit: It might be Volume up and down with power... Don't remember.... I always use ADB to go into the bootloader.
You had it right, volume down+power=bootloader.
Like a couple people said..you used a computer to get in you can use it to get out. I've pretty much screwed and unscrewed just about everything on this tablet..probably been in the same situation here too. Its a nexus device, I'd actually be impressed if you did something not easily fixable. Maybe a little more thorough explanation of exactly what you have done so far, how you've done it, and what you've done it with. Paint us a picture. Should be a very simple fix. Small details can make a huge difference.
Sent from my Nexus 7 using xda premium
I believe he is having the same problem that I am. It worked fine at one point(mine worked fine for two weeks), then something happened and now the usb port does not work while powered on. I cannot charge it or connect to a computer via usb while powered up. If i turn off the tablet, I can charge it. I have tried multiple cables/chargers with the same results. Originally I was able to connect via ADB to my computer with this tablet, but cannot anymore. Also, I swapped the usb port hardware out of my nexus 7 with my wife's nexus 7 to see if it was the plug. Same result. The port from my tablet works just fine in hers, but hers does not work in mine. I'm not sure what happened, but I cannot unroot/lock the device without the USB so I cannot return it. Very depressing.
Rooted/Stock Nexus 7
x52x58 said:
I believe he is having the same problem that I am. It worked fine at one point(mine worked fine for two weeks), then something happened and now the usb port does not work while powered on. I cannot charge it or connect to a computer via usb while powered up. If i turn off the tablet, I can charge it. I have tried multiple cables/chargers with the same results. Originally I was able to connect via ADB to my computer with this tablet, but cannot anymore. Also, I swapped the usb port hardware out of my nexus 7 with my wife's nexus 7 to see if it was the plug. Same result. The port from my tablet works just fine in hers, but hers does not work in mine. I'm not sure what happened, but I cannot unroot/lock the device without the USB so I cannot return it. Very depressing.
Rooted/Stock Nexus 7
Click to expand...
Click to collapse
Have you tried WugFresh's toolkit? There's a flash stock + unroot with a “can't boot up" option. Then you can relock the bootloader.
Sent from my Nexus 7 using xda premium
Does it require USB access?
Sent from my Nexus 7 using Tapatalk 2
Yea but not adb. Might even be able to start with tablet off. Not sure if either will work but its an easy start. You've used fastboot before right? It's easy. The toolkit thread will walk you through a couple simple steps. Again, don't get your hopes up it's just an easy start.
Sent from my Galaxy Nexus using xda premium
Related
windows wont recongnize my fascinate. yes it is a verizon. cant use odin as windows doesnt like my phone. and yes i did mess it up. Ive odin it a few times before with success. I have installed the samsung driver also. My question is, is it totally bricked or is there anything i can do?
Thanks.
Well what did you do prior to "bricking" it? What did you flash, etc.
Sent from my SCH-I500 using XDA App
Try a different USB port, different cable, and finally a Different computer.
Okay so what your saying is it will flash into: download mode If not and you see a black screen you could possibly try this so you will have to get an extra Mini USB to do so and a few other things: http://www.youtube.com/watch?v=Rdn5GoRjhn0&feature=youtu.be
If you are able to go into download mode ect there is no need for the above to be done. Or you might want to try looking at this: http://forum.xda-developers.com/showthread.php?t=1153310
I am not responsible for what you do with this information though read through carefully to see if you want to take these steps on your device. From what I read and see some have had problems switching back to Odin when this program took over.
What Sendan has said here would probably help us more as I just jumped right into it for you. There may or may not be a need to do these steps listed here if we have more info on what is happening with your device.
Give me a detailed description of what you did, what you used, and what happens to it now.
Sent from my GT-P7510 using xda premium
cleanerdude said:
windows wont recongnize my fascinate. yes it is a verizon. cant use odin as windows doesnt like my phone. and yes i did mess it up. Ive odin it a few times before with success. I have installed the samsung driver also. My question is, is it totally bricked or is there anything i can do?
Thanks.
Click to expand...
Click to collapse
Not sure if this will help, but I had a similar problem (PC wouldn't recognize phone in usb mode or download mode, Odin wouldn't connect, multiple cables had same result, remove/reinstall of Samsung drivers didn't help).
I ended up installing the Samsung drivers on a laptop that had never had them installed. Connection success! Was able to use Odin from that machine to flash back to stock Froyo/ED05.
After that, usb and download mode worked on the original PC. Same drivers that wouldn't work previously. Can't explain it, YMMV. It got me out of a jam.
Good luck.
maybe i freaked out. i put battery in just now and was able to boot into red recovery. yesterday i used it as an excuse to go buy a galaxy 2 on att. im trying an older backup. tried one a couple nights ago and it kept getting stuck. i have had the hardest time. started on a mac with heimdall and couldnt get it to work. went to a windows machine. couldnt get odin to work right with it. not sure now what i did to brick it. my win laptop i usually use is at my girlfriends. was just hoping to make this phone last til nexus prime.
Ok messing with it more. everytime i try something in recovery it will end up on the black screen with the phone to computer and the yellow sign between. heimdall (back on the mac) wont recognize it. not sure if i can do something in recovery
So Odin won't recognize your phone in download mode? You using the stock USB cord? Try different ports? Best thing would be to flash Stock ED05 and restart from there.
OK got it figured. Usb cord must be the problem. Now have cyanogenmod 7.1. But can't get gapps to install. Have tried rom manager and downloading it
Sent from my SAMSUNG-SGH-I777 using Tapatalk
And fixed gapps. Had to use power menu to recovery. So all fixed.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
So, got a replacement Nexus 4 today, and it's been updated to 4.2.2 and for some reason, it comes up as offline on ADB no matter what I do.
However, the funny thing is, my other Nexus 4, the one I was getting the replacement for, connects to ADB wonderfully. Shows up as a device, no problem. It's on 4.2.1.
Question 1: How can I manage to get the gosh darn thing to be recognized as online. I've tried two different cables, both of which connect with the 4.2.1 nexus but not the 4.2.2.
Question 2: Can I install a custom recovery without ADB?
EDIT: Consider this solved... it seems I had a bit much to drink... little did I know I don't need ADB... just fastboot.
Oh well All is well.
x3phyr said:
So, got a replacement Nexus 4 today, and it's been updated to 4.2.2 and for some reason, it comes up as offline on ADB no matter what I do.
However, the funny thing is, my other Nexus 4, the one I was getting the replacement for, connects to ADB wonderfully. Shows up as a device, no problem. It's on 4.2.1.
Question 1: How can I manage to get the gosh darn thing to be recognized as online. I've tried two different cables, both of which connect with the 4.2.1 nexus but not the 4.2.2.
Question 2: Can I install a custom recovery without ADB?
Click to expand...
Click to collapse
Is the device recognized by Windows? Checking under Computer>Properties>Device Manager does the phone show up correctly?
Use the search in the future please. Just update ADB. With 4.2.2 the phone will pop up to ask you if you want to authorize your computer to access the phone, this "feature" requires the updated ADB, no change to fastboot, so you'll be fine getting the recovery on there, but ffr with ADB.
Unlock and Root 4.2.2
h.nocturna said:
Is the device recognized by Windows? Checking under Computer>Properties>Device Manager does the phone show up correctly?
Click to expand...
Click to collapse
If you're trying to unlock and root your nexus, you can follow the steps on this forum http://forum.xda-developers.com/show....php?t=2147413 There's another way to unlock and root your device (via adb) since Wugfresh's NRT doesn't support 4.2.2. Just make sure you use the correct .img file for your specific device.
You can also update any old SDK files by opening the SDK Manager on your pc.
USSENTERNCC1701E said:
Use the search in the future please. Just update ADB. With 4.2.2 the phone will pop up to ask you if you want to authorize your computer to access the phone, this "feature" requires the updated ADB, no change to fastboot, so you'll be fine getting the recovery on there, but ffr with ADB.
Click to expand...
Click to collapse
I did use the search feature and I will have you know that the FIRST THING I DID was download and update the absolute most recent ADB so thank you, but the degrading "learn to search" comment was not applicable.
Anyhow, this whole conversation is fairly irrelevant since I got what I needed to do, done.
Thanks for the help everyone.
Mind telling me what you did, im stuck in the same situation
gsusx said:
Mind telling me what you did, im stuck in the same situation
Click to expand...
Click to collapse
same situation. whatd you end up doing?
gsusx said:
Mind telling me what you did, im stuck in the same situation
Click to expand...
Click to collapse
whocanhebe said:
same situation. whatd you end up doing?
Click to expand...
Click to collapse
Download this and replace your old adb & fastboot
http://forum.xda-developers.com/showpost.php?p=37935821&postcount=26
Have you tried entering:
adb kill server
adb start-server
Read this:
http://stackoverflow.com/questions/8162581/why-does-adb-return-offline-after-the-device-string
It worked for me. I did it last night when I had the same issue.
hiya
might be havving a blonde day but even using this my device still shows in cmd as offline when i type "adb devices"
what am i doing so horribly wrong
gsusx said:
hiya
might be havving a blonde day but even using this my device still shows in cmd as offline when i type "adb devices"
what am i doing so horribly wrong
Click to expand...
Click to collapse
if you have updated adb try killing the server with adb kill-server
EZ
Hey
Guys had the same problem and it was really simple to solve.
When you start adb and type adb devices and your device comes offline.
Go to settings>developer options - unchecked USB debugging and check it again, right after your computer will recognize your phone and in the phone will appear a box with your computer's Mac address asking you to allow connection.
gsusx said:
hiya
might be havving a blonde day but even using this my device still shows in cmd as offline when i type "adb devices"
what am i doing so horribly wrong
Click to expand...
Click to collapse
Have you downloaded the updated version of adb from post #8? And make sure you use that rather than whichever you were using? That was all I needed to do to get my offline Nexus 4 online again...
It have something to do with usb debugging not being enabled on the new phone?
Sent from my Nexus 4 using Tapatalk 2
VoiD_Dweller said:
It have something to do with usb debugging not being enabled on the new phone?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
In that case, I don't think you get the "offline" status from adb - I think it wouldn't appear at all?
It appears that the Linux SDK isn't fully updated (as of today, newest build is 0219). My adb version is 1.0.29, and from a bit of research it seems that that version cannot ask your device for the OK it needs in 4.2.2. I hope I'm wrong though...
EDIT: When I had basically given up, I re-checked one last time, and there it was on my screen; the OK. Unfortunately, I have no idea what permitted this. Let the building start. Good luck to all of you!
jotss said:
Hey
Guys had the same problem and it was really simple to solve.
When you start adb and type adb devices and your device comes offline.
Go to settings>developer options - unchecked USB debugging and check it again, right after your computer will recognize your phone and in the phone will appear a box with your computer's Mac address asking you to allow connection.
Click to expand...
Click to collapse
^ This worked for me. Thanks a lot! :good:
I'm insanely frustrated. My N7 was rooted. Suddenly now it's not.
Absolutely nothing is working properly. I tried installing the adt-bundle for Windows. It doesn't install. All I get is a quick DOS prompt flash, and nothing actually installs.
I tried installing the Sixaxis pair tool. That won't work, because I get this message: http://i.imgur.com/VU9Ou14.png
I tried running CF Root, it doesn't detect my N7.
I'm using Windows 8. I don't know if it's my PC, my N7, or me. Maybe all of the above? But for some reason nothing seems to want to work. The sheer volume of information on rooting my device is overwhelming. If anyone can give me a hand, it would be greatly appreciated.
End result for me, is I just want to use my PS3 controller with my N7. It's not even working with a hard wired connection for some reason.
Do you still have a custom recovery installed?
I don't see anything in your post that says which rom you're using, also if you double clicked on something like adb or fastboot.exe you're doing it wrong, course it'll just immediately close, you have to run it from cmd.
Please go read some of the stickied posts because it seems like you haven't grasped the concept of using adb/fastboot and the problem is likely easily fixed if you just read the instructions instead of relying solely on tool kits.
I'm not using a rom, nor did I ever install a recovery. All I needed to do in order to use my PS3 controller wirelessly, was to root the device. That's all I need to do.
Is it not completely ****ed up that I get these two messages? My PC clearly shows that the ADB drivers are properly installed. However any kind of rooting tool I use does not detect my N7. USB debugging is selected on my tablet. I just don't get it.
http://i.imgur.com/xwTb1vS.png
wrong forum
Q&a
Sent from my Nexus 7 using Tapatalk 4
I use wugfresh's tool kit and it's very simple! Try it
Hi,
I broke my Nexus 4 screen so I can't do anything, the touchscreen is completely down. But the display is working.
I have bought a new Nexus 4 and I want to get my photos from the broken device. The problem is that I can't unlock the phone (pattern), so I can't access to these. USB debugging is off and the device isn't rooted.
I hope someone have a solution for me. Does any virtual touchscreen exist ?
Ghuillaume said:
Hi,
I broke my Nexus 4 screen so I can't do anything, the touchscreen is completely down. But the display is working.
I have bought a new Nexus 4 and I want to get my photos from the broken device. The problem is that I can't unlock the phone (pattern), so I can't access to these. USB debugging is off and the device isn't rooted.
I hope someone have a solution for me. Does any virtual touchscreen exist ?
Click to expand...
Click to collapse
Don't know if there is a simpler option, but this might help you:
http://forum.xda-developers.com/showthread.php?t=2433307
Not sure if adb works with usb debugging disabled though...
That has to be the Worst case scenario. Another reason I use Google drive and keep pics synced via cloud
Sent from my Nexus 4 using xda app-developers app
It's really annoying, I just need to unlock my phone but I can't !
I'm not comfortable with the idea having my pics on Google's servers, but I will find something to backup data now..
Maybe the only way is to wait the nexus to be obsolete and find a screen for a low price
Oh wait !
USB debugging is ON ! I didn't see the bean icon because there are a lot of notifications.
But I can't use adb :
$ adb shell
error: device unauthorized. Please check the confirmation dialog on your device.
Click to expand...
Click to collapse
Ghuillaume said:
Oh wait !
USB debugging is ON ! I didn't see the bean icon because there are a lot of notifications.
But I can't use adb :
Click to expand...
Click to collapse
I'm assuming that because your phone isn't rooted you don't have a custom recovery or an unlocked bootloader. Is this correct?
i know with my HTC desire i run adb, when the device is turned off and connected to PC .
i think you can try it with your N4 , there are tools to do it google it .
good luck
You can try some combination of Airdroid (older version) and adb/shell command. So you'll need your device connected and older version of Airdroid - not two, because it asks for user action to accept the connection, and the older one just gives random generated password for the user to input in their browsers.
Now, you'll need to push the apk on your phone, and then just start it from your adb shell with the following command:
am start -a android.intent.action.MAIN -n com.sand.airdroid/.Splash - this should work on the old version
am start -a android.intent.action.MAIN -n com.sand.airdroid/.SplashActivity_ this works on last airdroid
At least you can try with other app that doesn't need user interaction on their display to get into the phone memory from their browsers. You can just install them from play store.
The first time that I'm writing here in Nexus forum though I am here with my 2 old DHD for about 2 years and I hope my answer could be helpful. And now I am here because of my soon to come Nexus 4
You could try to unlock, flash CWM then "adb pull" the files from there. No need for the digitizer to get it done. Fully charge the battery before starting.
You don't need root access, just adb debugging.
For everything off your phone: adb pull /sdcard/
Done.
EDIT: If you just want your pics from your camera the command would be adb pull /sdcard/DCIM/Camera/
lopezk38 said:
I'm assuming that because your phone isn't rooted you don't have a custom recovery or an unlocked bootloader. Is this correct?
Click to expand...
Click to collapse
You don't need root to use adb.
You only need to for adb to access anything beyond the sdcard.
When you first use adb there is a pop up on the device that asks if you want to allow the pc access.
He can't use the touchscreen to confirm its ok. This is the reason after I flash a Rom hook up to my pc ASAP and have it remember my computer to allow me access if this were to happen to me.
illru said:
You could try to unlock, flash CWM then "adb pull" the files from there. No need for the digitizer to get it done. Fully charge the battery before starting.
Click to expand...
Click to collapse
HUGE reason why this won't work:
unlocking the bootloader wipes the entire device.
Which... is pointless if you're trying to recover data.
studacris said:
HUGE reason why this won't work:
unlocking the bootloader wipes the entire device.
Which... is pointless if you're trying to recover data.
Click to expand...
Click to collapse
If you flash the custom recovery immediately after unlocking (without rebooting into android in between) your data should not get wiped.
Well then... I sit here humbly corrected.
studacris said:
Well then... I sit here humbly corrected.
Click to expand...
Click to collapse
Dont worry, its not really an officially documented thing...more of just a bug with the bootloader.
Also if flashing your phone makes you nervous you could try to pull from in stock recovery but I don't know if it will work. Never played with stock recovery, it dose not last on my phone for very long.
illru said:
Also if flashing your phone makes you nervous you could try to pull from in stock recovery but I don't know if it will work. Never played with stock recovery, it dose not last on my phone for very long.
Click to expand...
Click to collapse
I dont think adb works in stock recovery. Only custom ones afaik.
Okay, I bought a Nexus 10 off someone, and they had already rooted the device. Bootloader is unlocked and whatnot. That's where my problems start. I can not for the life of me get fastboot or adb to see this thing.
Here's my info:
Google Nexus 10 (Samsung)
ClockworkMod Recovery 6.0.4.3
Bootloader Version: MANTALJ12a
Windows 8.1 Pro x64
Full Android SDK
Samsung drivers installed (I rooted my Galaxy Nexus without issue).
USB has a direct connection
Before I decided to format and try to install a stock .zip, I could access the tablet as a media (That's how I got the .zip on the device).
Steps to how I got here:
Flashed Cyanogenmod 10.2 or whatever. Didn't want JB, wanted Lollipop.
Pushed the (what I thought was correct) .zip to /sdcard
Booted into recovery
Formatted /system, /cache, /data, /factory
Reflashed the .zip
Failed. Miserably.
I named the .zip as something simple and just overwrote it. I wouldn't have this issue if it wasn't for that. I know I did a bad there.
But still, nothing I can do will get fastboot/adb to see the device. It makes the sounds that it's connected when I plug it in. I'm using an elevated prompt as well, but it will not pull the device. How do I get myself out of this hole? If I could push a new .zip to somewhere on /sdcard I could at least use the recovery to reflash.
Wrong device ? [emoji14]
Khaon said:
Wrong device ? [emoji14]
Click to expand...
Click to collapse
No, I was going to put it in the general help thread, may be better here since this may not be a simple question (Please prove me wrong).
Some additional things I've tried:
The NExus Root Toolkit. Removing all drivers etc. Still getting to fastboot by PWR+ VOL+ + VOL-.
Still nothing. Should I go to my wife's computer and try it there? I might do that anyways.
gothmog1065 said:
Some additional things I've tried:
The NExus Root Toolkit. Removing all drivers etc. Still getting to fastboot by PWR+ VOL+ + VOL-.
Still nothing. Should I go to my wife's computer and try it there? I might do that anyways.
Click to expand...
Click to collapse
You don't have access to have os then? How did you push your zip if you don't have access to adb?
I have seen people who couldn't get adb and fastboot working on their windows and switching to another computer solved the issues.
Ok, make sure to make a full clean of your drivers. Wug toolkit explain how to. Then install proper samsung driver and this
If it is not a hardware's problem, you should have access to fastboot & adb. You might try on another computer if possible. A clean one would be the best (i.e. never used any droid devices, etc.).
Another workaround would be to use and otg cable and an usb drive with any zip of your liking.
Another one, I had an issue long time ago, similar, I had to flash through odin in downloading mode to fix my problems.
BUT did you really deleted /factory partition? It contains various proprietary files needed for the device to work. Well concerns more devices with imei and stuff to allow 3g connection and co. Might have no incidence tho on your device's behavior.
Khaon said:
You don't have access to have os then? How did you push your zip if you don't have access to adb?
Click to expand...
Click to collapse
Sorry if I wasn't clear on this, I have 100% access to my computer. I have the Android SDK installed, and adb/fastboot commands working in command prompt. They're just not seeing the tablet.
Ok, make sure to make a full clean of your drivers. Wug toolkit explain how to. Then install proper samsung driver and this
Click to expand...
Click to collapse
Yeah, that's one of the steps I did. Followed the Wug toolkit and removed everything. Still not seeing the tablet.
If it is not a hardware's problem, you should have access to fastboot & adb. You might try on another computer if possible. A clean one would be the best (i.e. never used any droid devices, etc.).
Click to expand...
Click to collapse
Yeah, seems to be doing the same on my wife's computer (Win 7 HP, never had my phone/tablet hooked to it). I get adb/fastboot loaded and working in the command prompt, and it registers when I plug in, but neither command will "see" the tablet.
Another workaround would be to use and otg cable and an usb drive with any zip of your liking.
Another one, I had an issue long time ago, similar, I had to flash through odin in downloading mode to fix my problems.
BUT did you really deleted /factory partition? It contains various proprietary files needed for the device to work. Well concerns more devices with imei and stuff to allow 3g connection and co. Might have no incidence tho on your device's behavior.
Click to expand...
Click to collapse
It's a Wifi tablet, no cellular data and IMEI etc.
edit: As a side note, I've been thinking about reformatting my computer, though it'll be a huge pain to get it back to here as I've got to go from 7 - 8.0 - 8.1 on the upgrade paths to get it back here again.
gothmog1065 said:
Sorry if I wasn't clear on this, I have 100% access to my computer. I have the Android SDK installed, and adb/fastboot commands working in command prompt. They're just not seeing the tablet.
Click to expand...
Click to collapse
From my own experience, having similar issue with the windows drivers for adb, but eventually I fixed it. I really doubt you are screwed.
adb version output ? 1.0.32 is latest.
Yeah, that's one of the steps I did. Followed the Wug toolkit and removed everything. Still not seeing the tablet.
Click to expand...
Click to collapse
Installed universal adb drivers? Nothing shows up in the device manager?
Yeah, seems to be doing the same on my wife's computer (Win 7 HP, never had my phone/tablet hooked to it). I get adb/fastboot loaded and working in the command prompt, and it registers when I plug in, but neither command will "see" the tablet.
Click to expand...
Click to collapse
You might try odin.
Usb mtp doesn’t work from recovery?
Khaon said:
From my own experience, having similar issue with the windows drivers for adb, but eventually I fixed it. I really doubt you are screwed.
adb version output ? 1.0.32 is latest.
Installed universal adb drivers? Nothing shows up in the device manager?
?
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.32, yep latest.
I just feel like I'm missing something, maybe something stupid. HOWEVER, I'm now getting my nexus 10 to show up in device manager with a ? on it. Already tried the direct Samsung drivers, the universal drivers in the Wug toolkit.
gothmog1065 said:
Android Debug Bridge version 1.0.32, yep latest.
I just feel like I'm missing something, maybe something stupid. HOWEVER, I'm now getting my nexus 10 to show up in device manager with a ? on it. Already tried the direct Samsung drivers, the universal drivers in the Wug toolkit.
Click to expand...
Click to collapse
Did you deleted all samsung vendor, etc from the usb program, you know what i am talking about?
You can force to install drivers from device maanger, don't remember how, when installing manually, you must do some step , install from floppy or file, get inf files or so, you will get a prompt telling you it might be harmfull and it will force installation. Might be the solution?
The culprit is definitely software-sided.
Does the mount internal storage (mtp) work?
Would this be easier in Linux? I could pop open my Ubuntu VM and do this if it'd be easier?
Beyond that, are you telling me to try and install the drivers from the driver files created by the Samsung vendor .exe?
I have tried to 'mount USB storage' from recovery, but it doesn't seem to do anything. /system /cache /data /factory are all mounted ATM and nothing is showing.
You've already got more advanced advice than I can offer but when I tried to update to 5.0.1 from 4.4.4, I couldn't get my windows computer to see my device. I was trying the adb fastboot but it I couldn't get it to work.
Wug's toolkit got it all straightened out (http://forum.xda-developers.com/showthread.php?t=2015467)[*]. There was an option on his interface that asked whether the device was working properly or not (a!most missed it as a choice). Checked that box and it went through much of the process I had done (installing adb, updating drivers etc). Long story short, it worked.
Where did you see this option? The only thing I see is the Soft Brick/Bootloop option where it will install the factory again. Was it that or somewhere else?
I swear to the Android droid that I tried that before. That seems to be doing what needs to be done, holy crap thanks!
e: I would like to know, however, why fastboot/adp wouldn't work but this would without doing any of the other stuff?
gothmog1065 said:
Where did you see this option? The only thing I see is the Soft Brick/Bootloop option where it will install the factory again. Was it that or somewhere else?
I swear to the Android droid that I tried that before. That seems to be doing what needs to be done, holy crap thanks!
e: I would like to know, however, why fastboot/adp wouldn't work but this would without doing any of the other stuff?
Click to expand...
Click to collapse
You're right. I confused the heading but choosing that option got my computer and my Nexus "talking." After installing the factory image I think you can then push a cusom ROM to you Nexus (http://forums.androidcentral.com/go...acks/264619-wugs-nexus-toolkit-questions.html).
gothmog1065 said:
Where did you see this option? The only thing I see is the Soft Brick/Bootloop option where it will install the factory again. Was it that or somewhere else?
I swear to the Android droid that I tried that before. That seems to be doing what needs to be done, holy crap thanks!
e: I would like to know, however, why fastboot/adp wouldn't work but this would without doing any of the other stuff?
Click to expand...
Click to collapse
Problem solved ? I always had less issues with fastboot and adb on Linux you can install a ppa that install for you adb and fastboot
Hovewer if you are using 2.8.2.0 you will need 1.0.32 and the ppa includes 1.0.31 so only adb sideload fails.
Sent from my nexus 10