Before anyone complains id like to say that i have done research into this and searched through the forums for a thread on the same matter but i have not found one.
I have recently purchased a Nexus 4 (the most well designed and premium feeling phone ive ever owned) running completely stock unrooted android 5.0.2, however upon connecting it to two different laptops i have been unable to access my files on the device or connect to the nexus root toolkit to root it.
device manager tells me that it recognises the device but the drivers are not installed. all the phone does is charge when its plugged in unless i turn on usb debugging and this only makes the noise that it makes when any device is inserted.
any help with this will be much appreciated, cheers
smiley118118 said:
Before anyone complains id like to say that i have done research into this and searched through the forums for a thread on the same matter but i have not found one.
I have recently purchased a Nexus 4 (the most well designed and premium feeling phone ive ever owned) running completely stock unrooted android 5.0.2, however upon connecting it to two different laptops i have been unable to access my files on the device or connect to the nexus root toolkit to root it.
device manager tells me that it recognises the device but the drivers are not installed. all the phone does is charge when its plugged in unless i turn on usb debugging and this only makes the noise that it makes when any device is inserted.
any help with this will be much appreciated, cheers
Click to expand...
Click to collapse
Google 15 second adb install xda. That will install drivers as well as adb and fastboot. You don't need nrt to root it. Flash the twrp image in fastboot, then flash supersu in twrp. http://techerrata.com/browse/twrp2/mako. http://download.chainfire.eu/693/SuperSU/BETA-SuperSU-v2.44.zip
Sent from my Nexus 9 using XDA Free mobile app
Related
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
Hey guys, my first post here. I signed up for this forum a little while ago and I've just been a lurker since today. Lots of great stuff on this forum!
I finally got my Nexus 4 phone when they went back on sale in late January, I came from an iPhone 3GS and I've been loving the switch every day since!
But now I have a problem that I hope you guys can help me with.
When I first got my phone the first thing I did was unlock the bootloader and root the device, I had 4.2.1 on my phone and forced the 4.2.2 update by clearing the cache/data of a few apps when it was mentioned on this forum (Bad mistake I think). I went to download titanium with root the other day to start to backup my apps/phone before I started messing with kernels and audio upgrades in case I messed something up and needed to reinstall. Unfortunately since this is my first Android phone I didn't know that upgrading would also remove my root access. Not a problem I though, I'll just go ahead and re-root the device, well that's where I started to see various problems.
I installed the SUser 1.0.4 zip on my phone (After I tried .98), booted up into the clockwork recovery option, extracted the zip from within clockwork to root my device again and nothing. I tried a couple of times, even tried the Nexus 4 toolkit but that didn't seem to work either. Rootchecker won't recognize that my phone is rooted.
In fastboot mode it shows my phone is
Secure boot - enabled (Green)
Lock State - unlocked (red)
When I was in the Nexus 4 toolkit I also noticed that it wouldn't recognize my phone's serial USB debugging mode even when I turned it on (Pressing the build number 7 times and checking the usb debugging box in developer options). When in fastboot mode my computer recognized my phone without a problem. I am still able to move stuff on and off of the phone through windows explorer, but only when it's NOT in debugging mode, my computer beeps like something is connected when in USB debugging mode but nothing shows up anywhere except in device manager. I tried installing the drivers that were posted for 4.2.2 and also tried installing the drivers through the toolkit but neither would fix that problem. Another thing I noticed was that I never got a prompt on my phone to allow my computer access to debugging mode like people mentioned that I should get.
Now either I messed something up somewhere along the lines, (good chance)
or I'm an idiot and i'm missing something really obvious (better chance)
Anyone have any suggestions as to what I can do or how I can get my root access back?
Thanks a bunch in advance for any help you guys can give me, and if I left some info out of here that you need let me know.
kelmino said:
Now either I messed something up somewhere along the lines, (good chance)
or I'm an idiot and i'm missing something really obvious (better chance)
Click to expand...
Click to collapse
Oh wow... yup I'm an idiot and missed something really obvious....
I just installed the SuperSU app from the playstore and I do have root access again and apps request access.
ugh I'm a moron, I spent hours on this yesterday and as soon as I post this I fix the issue
Sorry guys
Now my only problem is I can't see my phone from the playstore on my computer but I'm not worried about that, I think I can fix that as I see another post up here for that same issue.
perhabs this helps
http://forum.xda-developers.com/showthread.php?t=2159744
u dont need to extraxt su zip file....download drivers..use tool kit to unlock bootloader..then flash temporary clockwork recovery...flash su in recovery....download goo manager from playstore to flash permanent recovery
Sent from my Nexus 4 using xda app-developers app
dont use toolkit. do it the long way so you know what you're doing otherwise you're walking in a room blindedly hoping you'd get through the maze.
in the long run, it'll be worth it. very simple & easy to do.
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
I have checked at least hundred threads now, but my problem seems unique! (First time this happened to me )
When I connect my N7 (WiFi, 32 GB) to my laptop (Win 8.1), it says "USB device not recognized - The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." In Device Manager, it is like the image attached, no other recognition for the device. Upon selecting Properties, It says "Code 43" in status, also says "A request for the device descriptor failed". That happened with 2 computers; I used 2 cables (both worked previously). So it means N7's USB port is somehow malfunctioning. But it gets charged as well as ever!!
This started after I tried an OTA update of 4.4 earlier (the download had not completed, but a prior small update (1-3 MB) was installed).
Now, I have Android SDK (latest version) and installed those google USB driver and platform-tools. I have NRT 1.7.9 (which worked for me previously). But I cant get my N7 to answer to ADB requests. [highlight]Upon connecting USB, it says "Charging (USB)" but no option regarding PTP or MTP appears.[/highlight] I have developer tools installed. I followed the instructions given in NRT about ADB installation to the letter but still no progress. I have tried a factory reset too.
BTW, I dont have a custom recovery flashed. It vanished along with the precious root privilage.
Now the N7 is in Android 4.3 (JWR66Y), bootloader is unlocked, SuperSU is Installed (but do not work due to having no root access and I cant even Uninstall it for the same reasons!!!). Now the OTA update also do not work mysteriously (it downloaded the 4.4.2 update and went on to install it, but as the bar started filling, it only said "error" and stopped!!! no explanations whatsoever!!!!). I will be very happy any of the followings:
[highlight]1. root without computer (wireless ADB is also welcome),
2. working OTA, or anyhow the 4.4.2 update
3. working ADB connection with my laptop.[/highlight]
Any help will be very helpful... Thank you in advance...
If you can not communicate via USB hardware, then using fastboot is not an option (obviously). And so therefore the lock state of your bootloader is quite irrelevant, too.
Even if you were to get adb over tcp (WiFi) working, that doesn't get you much, as an adb login shell on a stock ROM is just an unprivileged user; it's not much different from using a terminal emulator app (from a privilege escalation point of view).
The only other thing left is an exploit (privilege escalation) method that runs under the stock ROM. Something similar to that Motochopper exploit from some time ago. I suppose that particular hole was plugged; whether or not a new exploit exists, I can't tell you.
You could always just send the tablet back for repair. Seems like not having a working USB port is pretty crippling to someone who wants to root, flash ROMs, copy backups off the tablet, etc.
Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...
Aaron061992 said:
Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...
Click to expand...
Click to collapse
Well that is very different than having a broken USB port.
You probably noticed in your search that this forum is littered with thousands of reports from users complaining about their Windows drivers. It gets pretty old, frankly. (No drivers are needed at all for Linux or Mac OS/X).
Here is a suggestion that I made in another thread just a few days ago about using fastboot under Linux - in your case, you will be on your way after installing a recovery, e.g.
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-grouper.img
I even attached the most recent version of the (Android SDK Linux) fastboot to that post.
Note that you don't even need a dual-boot PC or PC with a semi-permanent Linux install; you can do the whole thing with one of those "Live CD" boots and a USB stick.
good luck
Hi,
I'm currently ran into a very frustrating driver problem with my nexus and i was looking for some help.
I an having trouble with my nexus when i was in the middle of rooting it i had just unlocked it using Wugfresh's root toolkit when the drivers i used were no longer recognized it as as an ADB device and i couldn't carry on my rooting, i have tried reinstalling the drivers multiple times and it doesn't work and it has gotten to a point where it names it as unrecognized so i cannot even transfer files to it anymore, could anyone help me.
P.S. if you want more details about what i did ask me.
Benthrax said:
Hi,
I'm currently ran into a very frustrating driver problem with my nexus and i was looking for some help.
I an having trouble with my nexus when i was in the middle of rooting it i had just unlocked it using Wugfresh's root toolkit when the drivers i used were no longer recognized it as as an ADB device and i couldn't carry on my rooting, i have tried reinstalling the drivers multiple times and it doesn't work and it has gotten to a point where it names it as unrecognized so i cannot even transfer files to it anymore, could anyone help me.
P.S. if you want more details about what i did ask me.
Click to expand...
Click to collapse
Ran into same problem with this ****Wug's thing. Trash it and use Skipsoft Unified Android Toolkit instead. Took me a long time to erase all traces of Wurst. You need to uninstall and delete the Wurst' driver in device manager for Skipsoft to work.