Database Users

having trouble with usb drivers

so i am new to android and i decided " hey why don't i try to root my nexus" so i tried and i cant get any father that checking if the computer can see my device which it cant for some reason. so i went online i figured out that i don't have the usb driver for android. so after that i tried to down load then and i even installed them and restarted my computer and it still wont work. so if any one can help me with my problem it would be greatly appreciated.

On Home Screen, press menu>settings>applications>development and make sure USB debugging is checked.

What OS you running?
Specs would help, where did you get your drivers? What other software have you tried?

i turned on the debugging and it still hasnt worked
i am running xp. i downloaded the android sdk from here
developer.android.com

i just want to put the modaco desire rom on my phone that my onl reason for wanting to root. i really like the sense ui

I am having a similar problem, so i might as well use this thread instead of creating a new one.
I have a dual boot computer, win7 and fedora, both have SDK. I unlocked my nexus one with windows, as i noticed the commands were considerably easier, or at least they don't work when i plug the linux ones into fedora.
Last night i was going to push the undervolt kernel so i plugged my n1 while in win7, It instantly came up complaining about drivers, which i had already installed and had previously worked, i went to re-install them, and windows says they are up to date, but still no luck recognising the device (Debugging mode is definately on)
So i switched to fedora, no driver pop ups obviously, but when i try to push the kernel through, it does not recognise the device.
In the bootloader it says "fastboot usb" while plugged in.
I can't pinpoint when it stopped working, but the last time i used fastboot was to put the RA recovery, since then i flashed CM 5.0.2, CM 5.0.3.1, the desire rom, and used a nandroid restore to get back to 5.0.3.1
Anyone got any ideas? Without fastboot i am pretty much restricted to flashing .zip files from the recovery.

yeah i cant even unlock mine its so frustrating

Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...

temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse

drbrendin said:
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
I tried all day too like a gazillion times.... and wonder does everyone have driver issues? I tried with my XP computer and windows 7, no go, then I read posts people having the same issue, then they just post " nevermind got it" and didn't even write what they did to get it.......
Click to expand...
Click to collapse

not everyone is a dev

Ok, I have my Nexus One set up so I can use with via Windows 7 (desktop) or Ubuntu (Laptop).
The Linux part is a bit more involved, but since everyone is running Windows (unless I missed something), I will work there.
First of all, your phone needs to be in Dev mode (which was covered earlier).
With the phone UNPLUGGED from the PC, uninstall any previous SDK installs you have and be sure to remove the directory.
Then, install the SDK found here: SDK
Install this SDK and let it complete the install, which will include downloading for a bit. You need to do this since the SDK package above does NOT include the right drivers!!!
Once this has been completed, plug your phone into the computer via USB. Your computer will find a new device, however, it cannot locate the drivers for it. Browse and point the installer to:
DRIVE:\PATH_TO_android-sdk-windows\usb_driver
Don't go any further than this!!
Now, let it do it's thing and you should have a new device in the device manager called:
Android Phone
...|_Android Composite ADB Interface
Now, go to the command prompt and change to the following directory:
DRIVE:\PATH_TO_android-sdk-windows\tools
There, you will find adb.exe
Type:
adb devices
and you should see:
List of devices attached
HT019P801614 device
If not, something got screwed up and would need to dig further to help ya.

Ok ill give this a try once get home from school

nexus one root.
Ok assuming that you have the android sdk installed correctly, try rooting your phone via the superboot method. The first link below has a full detailed guide for rooting the nexus one and I believe has all of the device drivers for those who have not been able to get them running well. If you still have trouble getting the drivers working checkout the second link. Anyone who is relatively new to working with the sdk and is not familiar with working the commands check out the third link. Read the entire thread! it is very helpful.
1) http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
2) http://forum.xda-developers.com/showthread.php?t=613217
3) http://forum.xda-developers.com/showthread.php?t=619153
If you have any questions PM me on xda. I'll try and help in anyway, it took my like two days to actually root my nexus, I wasnt familiar with using ADB and Fastboot to root.

One thing I know I was having problems with since I came from the G1 was that the new SDK has to actually be installed via an .exe now. I was used to it all being in a zip so I kept trying to load up what I thought were the right USB drivers, but they were actually the 1.6 drivers I already had. So make sure to run the .exe that comes with the SDK.

ok so while i was downloading the sdk a notification came up that said that it could not rename the directory. is this bad?

i am having an issue with installing the right driver as well. my computer keeps installing the nexus one as a "mass storage device". i have uninstalled and reinstalled a few times but no luck. i have the phone set to debug mode, using XP btw. any help would be appreciated.

And The Annoyance Continues!

Jeez I love the vibrant but I'm so unbelievably annoyed. First I rooted my phone and flashed clockwork mod recovery in order to delete some bloatware, not that I needed the clockwork mod recovery right now but did it anyway. So after that my Vibrant lagged, my sync was broken and my market no longer worked, so I used Odin to get back to stock thanks to a good suggestion and now I am attempting to root again and I would prefer to root through ADB but hence here we go again more annoyances, for some reason Windows 7 does not recognize my device in debugging mode. I have installed the drivers and it says "drivers installed successfully and ready to use" yet when I go to device manager it says "no driver files installed" and does not recognize my device. My nexus one, Mytouch and G1 were SOOOO much easier to work with, never had a problem.
So can someone help me out? Why is windows 7 sucking the big one right now? I can obviously root by just putting the file in my root directory, booting in stock recovery and doing update.zip so that's really not the big deal, the big deal is, I WANT ADB, this is pissing me off. I can't do anything in ADB because my device is not listed / recognized

justanothergirl said:
Jeez I love the vibrant but I'm so unbelievably annoyed. First I rooted my phone and flashed clockwork mod recovery in order to delete some bloatware, not that I needed the clockwork mod recovery right now but did it anyway. So after that my Vibrant lagged, my sync was broken and my market no longer worked, so I used Odin to get back to stock thanks to a good suggestion and now I am attempting to root again and I would prefer to root through ADB but hence here we go again more annoyances, for some reason Windows 7 does not recognize my device in debugging mode. I have installed the drivers and it says "drivers installed successfully and ready to use" yet when I go to device manager it says "no driver files installed" and does not recognize my device. My nexus one, Mytouch and G1 were SOOOO much easier to work with, never had a problem.
So can someone help me out? Why is windows 7 sucking the big one right now? I can obviously root by just putting the file in my root directory, booting in stock recovery and doing update.zip so that's really not the big deal, the big deal is, I WANT ADB, this is pissing me off. I can't do anything in ADB because my device is not listed / recognized
Click to expand...
Click to collapse
That's why I am doing all my development work on a linux box Try removing the driver and cleaning the registry (I am not sure if Win 7 has such a thing) and re-install the drivers. Put the the phone in USB debug mode and connect to the PC.

Certain you installed the right ones? Seems like it took a few times before I found the ones that worked and gave the adb connection in device manager. Been a while, but pretty sure i had to download Kies and unzip the .exe to find the drivers. The final .exe is called "SAMSUNG_USB_Driver_for_Mobile_Phones.exe" (nice name..) and its version 1.3.750 and is about 18MB.
After that, worked like a charm

fearmonkey said:
Certain you installed the right ones? Seems like it took a few times before I found the ones that worked and gave the adb connection in device manager. Been a while, but pretty sure i had to download Kies and unzip the .exe to find the drivers. The final .exe is called "SAMSUNG_USB_Driver_for_Mobile_Phones.exe" (nice name..) and its version 1.3.750 and is about 18MB.
After that, worked like a charm
Click to expand...
Click to collapse
Yeah that's the one I installed. I have no idea why Windows 7 is being a super douche.

justanothergirl said:
Yeah that's the one I installed. I have no idea why Windows 7 is being a super douche.
Click to expand...
Click to collapse
Meh, i blame samsung on this one. Once i finally got it installed, seemed to do ok..
but it is slowly coming back to me now..yes.
So, rename/unzip that SAMSUNG*.exe file to a directory. Probably will ask to overwrite some files (why they are in there twice..no clue). Run the setup.exe. Boom!
I'd uninstall them and re-install to verify..but, I kinda like having adb around and I already wasted a couple hours trying to get it to work that first time..

That worked! Thanks a million! You rock <333

[Q] Stock 4.2.2. refusing to ADB to then root

I had a windows 7 PC perfectly working in booting a Nexus 7 to flash and root etc, it did a Nexus 4 last week.
There is some problem with drivers and 4.2.2. specifically. My story was it was 4.1.2. rooted and it was refusing to OTA update but I wasn't bothered due to the bugs/performance in 4.1.1 so I waited til 4.2.2. came along. The N7 refused to take OTA 4.2.2. I got the Android icon with the Red icon out its belly and it would boot back as 4.1.2 every time.
So using Nexus Rootkit I did a "stock flash+unroot" to 4.2.1 and then let it did a OTA to 4.2.2 and that worked so I have a stock 4.2.2 but not it won't root, it would do that ADB bootloader type stuff. I've tried updating driving umpteen times but it like it simply won't obey ADB type commands? I'm not a rooting expert I just used the toolkit and howtos.
So stuck.
In hindsight as it WAS doing ADB at 4.2.1 I should have rooted and then otarootkeeper then OTA to 4.2.2. but I didn't know 4.2.2 rooting fails.
Any ideas?

same for me!!!
Help...

Well, the OTA for 4.2.2 would fail every time because of version diffs in the files. You had to be on 4.2.1 to accept the OTA.
1. Out of curiosity, did you remember to re-enable USB debugging?
2. Did you update you SDK for 4.2.2?
If you still have issues after enabling debugging, then try the Universal Naked driver. It was the only one to work on my Win7 box. Also, make sure only 1 instance of ADB is running.
At least you don't have a super weird issue like me where flashing stock recovery refuses to stick, but TWRP flashes with no problem.
Sent from my Nexus 7 using Tapatalk 2

can root a stock 4.2.2 - it works!
I fixed it!
I'd been trying toolkit all of its options and none worked. So I followed this guide which contains an error which is irrelevant.
http://m.ibtimes.co.uk/root-nexus7-official-android422-jdq39-jellybean-ota-434720.html
Do its step 1. It downloads the Google USB drivers - THEY WORK. This is the problem with other guides they point to drivers which don't work.
Ignore its step 2 because you find step 1 includes fastboot so you don't need to get it separate. I lost a lot of time on that one problem because the link to that shared file fastboot.zip won't download so I hunted and found another and when I was going to copy to the required destination in step 2 I found the fastboot file alreadt there! So ignore step 2
Step 3. Now I downloaded it on the Nexus 7 itself and mine was in /sdcard/Downloads or you can copy on the PC and then copy it over to the N7 via USB cable.
Step 4. Press and hold power off you get option select power off.
Step 5. At the step 1 you'll see WHERE it is installing the SDK to, you need to go to that folder in this step 5 as described.
Step 6. As describe, press vol down and power button together and keep them hold. Then a menu screen shows mine had been unlocked from before. Now dont't touch the N7. Go to Windows machine.
Step 7. My Windows Pc doesn't have command prompt option inside a folder so I opened command prompt and CD down to where step 1 was.
Step 8. Type that command. Mine simply worked fperfectly first time. It had a copying type command which looked happy.
Step 9. Back on the N7 hit the vol up button til you see a "recovery" type word on screen.
Step 10 and 11 as described.
Step 12. Now is the next area where howto guide is wrong / misleading, I had on my screen some gibberish folders and an "update.zip" not the supersu zip from step 3. Initially I tried the update.zip and it went crazy but fortunately a hard power-off got me fixed so then next time I looked around for the supersu zip. So of the stuff on-scren where was like 0/ type folder so I selected that THEN I could see the sdcard/download folder I could go down to and then select the zip file. The /sdcard folder isn't showing firstly you have to go /0 and then you see it.
Step 13 do it.
Then get it booted and then go into Supersu app and run it and then make sure you install voodoo root keeper app and select it to preserve root.
So I've got a vanilla 4.2.2. with root and so far it all works. Features which kept me on 4.1.2 like PPP-widget simply work.
Phew.
I've spent about 15 hours on this trying to eliminate my own dumbness as the cause.
I think basically the ADB drivers in the Toolkits are bumb, ignore them they don't work I think the Android SDK with its Google USB drivers are the ones which work with 4.2.2 I guess the Toolkits need to be updated.

nikon120 said:
Well, the OTA for 4.2.2 would fail every time because of version diffs in the files. You had to be on 4.2.1 to accept the OTA.
1. Out of curiosity, did you remember to re-enable USB debugging?
2. Did you update you SDK for 4.2.2?
If you still have issues after enabling debugging, then try the Universal Naked driver. It was the only one to work on my Win7 box. Also, make sure only 1 instance of ADB is running.
At least you don't have a super weird issue like me where flashing stock recovery refuses to stick, but TWRP flashes with no problem.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
The problem seems to be drivers. The N7 stock 4.2.2 simply refuses to respond to Root Toolkit its drivers are simply not working, the N7 is ignoring to get into fastboot. I figured it out see my later post.
I think 4.2.2. is too new for toolkits and people's 4.2.2. rooting guides are buggy and relate to old old instructioned since outdated and in error. By trial+error I figured it.

nikon120 said:
Well, the OTA for 4.2.2 would fail every time because of version diffs in the files. You had to be on 4.2.1 to accept the OTA.
1. Out of curiosity, did you remember to re-enable USB debugging?
2. Did you update you SDK for 4.2.2?
If you still have issues after enabling debugging, then try the Universal Naked driver. It was the only one to work on my Win7 box. Also, make sure only 1 instance of ADB is running.
At least you don't have a super weird issue like me where flashing stock recovery refuses to stick, but TWRP flashes with no problem.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Addtional my N7 did OTA receive the 4.1.2 to 4.2.2 update I even went into the /cache and the file name had version names to match so OTA was thinking itself capable. I think in some unlock / root past event I'd something screwed something up and OTA simply weren't working full stop. I did though manage to use Toolkit to get to stock 4.2.1 and then the drivers in the toolkit then don't work with 4.2.2, that's the broken bit. If you use Android SDK Google USB drivers, they work and you have to use command prompt fastboot as in the HOWTO I just posted to get it all working.
Toolkit drives broken with 4.2.2.

dont use a root toolkit. do it the right way, there arent any issue.
fastboot oem unlock, fastboot flash a recovery, flash the su binaries or a custom rom, reboot. thats it.

FYI - I've found that to use the toolkit (the 4.0.0 toolkit is what I used), you need to replace the adb-toolkit.exe (or whatever adb.exe is called in your toolkit) with the adb.exe that comes in the SDK (after you've updated your SDK, of course).
Otherwise, ADB shows as "offline" in the toolkit menu.
Hope that helps someone...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

The issue is what you typed is gibberish to most including me.
Sent from my Nexus 7 using xda app-developers app

[SOLVED] Restore a Nexus 7 with no OS (and trouble with adb) driver

Hi!
I've messed up with my tablet and I've ended up with a Nexus 7 with TWRP 2.6 but no OS installed.
I did some research but didn't find a solution to get 4.3 working in this case.
Any help?

Three things you'll need to restore your Nexus 7.
-Fastboot and ADB (Android SDK, platform-tools)
-Nexus 7 4.3 factory image (here)
-USB cable
First, you need to download the factory image. After that, you need to extract the zip into /platform-tools in your SDK.
Now you see a file named flash-all.bat, before you run that you need to connect your Nexus 7 to the computer. If you have your Nexus 7 plugged in, and the PC recognizes it, you can run flash-all.bat. Now you should see a CMD window popping up, with some commands. After the process is finished you've got a brand new Nexus 7. :good:

See the sticky that says flashing a factory image with fastboot/returning to stock. It is a couple from the top and walks you through fixing it.
Sent from my Nexus 4 using Tapatalk 4

Thanks, but stuck in the stage 7 :
Click Browse and locate the USB driver folder. (The Google USB Driver is located in <sdk>\extras\google\usb_driver\.)
Click to expand...
Click to collapse
However my PC recognize an android device but can't install the driver.

The Android Composite ADB Interface Driver 8.0.0.0 driver from SDK is for when in bootloader and booted into ROM. Naked Driver 0.72 is needed for when in recovery or else the computer would show "Nexus 7" under Unknown Devices in the Device Manager. With Naked Driver 0.72 installed, ADB can be used in recovery to copy a custom ROM zip to the internal storage then flash it.

Solution
Issue solved by the Nexus 7 Toolkit.
For people in the same situation:
1) Install the adb drive with the toolkit.
2) Flash a stock image with the toolkit.
You'll end up with a restored Nexus 7
Thanks for the help!

Lost OS in my Nexus 7
Hi there,
I accidentally wiped out my Nexus 7 (2012) and lost the OS in there of course. Cannot boot up from Nexus. Followed the steps you listed but I don't see the "flash-all.bat" in the platform-tool folder.
Also, I have tried other ways to push the img to Nexus 7 thru my laptop or a OTG cable with USB drive but seemed the Nexus 7 cannot be found or linked to any of the external devices.
As for the img, what kind of format should be extracted into the platform-tool folder? The original download is .tar and should I rename the extracted file to .img?
Need help...please. Thanks!!!

I assume you downloaded the proper factory image (nakasi from wi-fi, nakasig for 3g) from here: https://developers.google.com/android/nexus/images
It's a tgz file, but you can open and extract it with winrar (maybe others work too).
Boot your device to bootloader mode and connect it to your computer.

no luck...
Hi Erovia,
Thanks for replying. I am sure that I downloaded from that google site and I had the rev from 4.1.x ~ 4.4.2 and all of them are in .tar format. I used 7z to unzip and they got no extension after unzipping and all came out 1 file only. Does Flash-all locate in the image from google after unzipping?
I think I am having 2 problems now before I can move forward.
1.. Don't have the right image with .tgz as you described.
2.. Can never get the flash-all file.
Thanks.

1) All images are in tgz on that official site.
2) I can't help you with 7zip, try WinRar, it's very staightforward with it.

<No OS Issue Resolved>
Issue resolved and wanted to share lesson leant here:
For some reason, all the image I downloaded from Google developer site were in TAR format. I had a co-work with MacBook Pro and another Dell with Unix installed, when he downloaded the images, all of them came with TGZ and were able to unzip to a folder with files in it.
I came back and manually changed the extension file name from .tar to .tgz then it worked. I don't know why all windows laptops I tried had this same problem BUT fortunately I got it figured out.
I also ran into issues using SDK tool. after I click on Flash-all.bat, the cmd window popped up but it got stuck after few seconds.
I tried alternate method by locating the files unzipped from the image to the folder where I saved the adb, fastboot tools. Then I went to windows search type in CMD for DOS and went to the folder by using the DOS commend "cd" change directory. to the folder. Then typed in Flash-all.bat and it worked!!! Unbelievable I successfully installed the 4.4.2 to the device and rooting it with the "Nexus Root Toolkit" now.....
I think it just does not work too well with Windows for both image downloading as well as pushing the image to device.
Again, thanks for the help.

Help!
hcy97 said:
Issue resolved and wanted to share lesson leant here:
For some reason, all the image I downloaded from Google developer site were in TAR format. I had a co-work with MacBook Pro and another Dell with Unix installed, when he downloaded the images, all of them came with TGZ and were able to unzip to a folder with files in it.
I came back and manually changed the extension file name from .tar to .tgz then it worked. I don't know why all windows laptops I tried had this same problem BUT fortunately I got it figured out.
I also ran into issues using SDK tool. after I click on Flash-all.bat, the cmd window popped up but it got stuck after few seconds.
I tried alternate method by locating the files unzipped from the image to the folder where I saved the adb, fastboot tools. Then I went to windows search type in CMD for DOS and went to the folder by using the DOS commend "cd" change directory. to the folder. Then typed in Flash-all.bat and it worked!!! Unbelievable I successfully installed the 4.4.2 to the device and rooting it with the "Nexus Root Toolkit" now.....
I think it just does not work too well with Windows for both image downloading as well as pushing the image to device.
Again, thanks for the help.
Click to expand...
Click to collapse
Hi!
I just had a question. I have deleted my OS on Nexus 7 (2012) except that the tablet was also encrypted. Do the steps to flash the stock image still remain the same or do i need to do something differently? Sorry if this is a trivial question, I am a noob and totally regretting all the **** I have done to my tab. Would appreciate it if you could help out.
Thanks
Worked perfectly...thanks buddy! Just need to root now!

AFAIK you can proceed as usual.

hi guys please i lost my OS of my new nexus 7 wifi
when i was downgrading my new nexus 7 2013 wifi model i didnt know what i did but it is stuck in google and down of that some lock symbol but it not starting at all i dont know what happen please help me guys i think my OS has crashed help please guyzzzzzz ............:crying:

maheshchinna313 said:
when i was downgrading my new nexus 7 2013 wifi model i didnt know what i did but it is stuck in google and down of that some lock symbol but it not starting at all i dont know what happen please help me guys i think my OS has crashed help please guyzzzzzz ............:crying:
Click to expand...
Click to collapse
poor friend... I have the same issue, After the starting graphics, I see the lock screen for a second and it reboots. Again. And again, and again...
Let's try to fix it together. Stay in touch.

I'm really happy to say that I managed it with the Android Toolkit by Skipsoft. Although I did the same process many times (1. unlock the bootloader & 2. flash a stock image), it worked the 6th or 7th time.. Don't know why. Maybe because I reinstalled (and repaired) the drivers. Also, I was unable to flash the 4.4.2, so I did it with thw 4.1.2
Good luck dude!

How to Restore your Device
Anmar21 said:
Hi!
I've messed up with my tablet and I've ended up with a Nexus 7 with TWRP 2.6 but no OS installed. I'd like to put 4.3 Back on it Again!
Please help me!
Click to expand...
Click to collapse
To do this steps you don't need to be a Professional.
Simply read it all through and try to Understand it.
You need 3 Things for this WugFix Guide to Work.
1.Download WugFresh'S Nexus 7 Root Toolkit from wwW.WugFresh.Com
2.MicroUSB-Cable that fits in to your Computer and your Tablet.
3.The Android 4.3 Factory Image File for your Nexus 7 (2012?) with Build Number „JWR66N"; „JWR66V" or „JVR66Y" or maybe JWR66L.
1.Install the Nexus Root Toolkit (I've got 1.8.4 but right now, the Newest program Version is 1.8.6.)
2.In the Window "Your model type:" you choose „Auto Detect Device + Buidl"
2.1.If that does not work, then choose your Options Manually.
NASAKI-GROUPER Android 4.3.0 has a Build of 6 Letters and/or Numbers that starts with JWR66 and ends with a „V";„N"„L" or „Y"."
Now it depends on WHAT DO YOU ACTUALLY WANT...
BEFORE DOING ANYTHING, if you want to Backup first, read THIS [http://forum.xda-developers.com/showthread.php?t=1766475&page=102]
If you wanna get the Nexus 7 back as it was like after Purechas(eI)ing, then Choose
„Soft-Bricked or Bootloop" in the „Back to Stock"-Menu on the Main Window with the title „Nexus Root Tooklit v.[Version Number.]"
Then click on the „Flash to-Stock + Unroot" --Button and then Open (Launch) the Image File
You can DOWNlOAD THE IMAGE FILE HERE: „htt ps : / / developers.google.com/android/nexus/images?hl=de&Hnh=1"
The File is Probably Saved here: „%USERPROFILE%\Downloads\FIREFOX DOWNLOADS\" or without „FireFox Downloads" the Path is „%userprofile%\DownLoAdS\".
There is no difference betwéén a or A, DoWnlOaDs or Downloads, but there is Actually a Diff. between "é" and the Nomral „e".
After the Process Progress is done, try to boot up your Nexus.
Hmmmmm..... let's see!
If you are still not OK, then try the Option Relock>OEM LOCK in the Main Window Panel of the Program.
Click to expand...
Click to collapse
I hope i could help you.
(I) Wish you a Nice day
and have a Nice day with your Nexus 7!
Hopefully i've been able to Hélp.
♥HA❤NN❤AH♥
My Recommendation for any case: IsoBuster, made ONLY BY Peter van Hoove!
Click to expand...
Click to collapse

howdy y'all,
so im trying to help out my buddy. he currently has no os installed as well, but can boot to bootloader and twrp recovery 2.5. no idea how he has that but I figure I could just mount some zip files and be on my way. Currently whenever we try to do anything in twrp(ie wipe/mount) it is just hung up on unable to mount /radio even when all I have checked is system. I can't use adb or fastboot as far as I'm aware of; I've tried to use the unified android toolkit from skipsoft but its no dice since I was never able to turn on debug mode to begin with? So yeah any help would be much appreciated
oh and I know its not my cable or usb ports since the tablet can still charge.

Nexus 7 os wiped by mistake
Hello guys
I have a similar problem here. I wiped out Nexus 7 2012 (mobile) OS by mistake and now all it does is switch on and display "Google" and an open padlock below. i tried my Nexus Root Toolkit to stock recovery, actually i tried even recovery but ADB connectivity cannot be established (tried all usb ports).
Currently the tablet cannot even switch off, switches back on on its own...in simple terms, my tablet is dead, its like a computer without OS. My computer recognize it though but with the exclamation mark in the device manager.
please help

Nexus 7 (2013) 32gb ADB Driver and other driver problems *HELP*

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.