Database Users

Unrevoked problems

Sorry to be a hassle, but I just can't figure this out!!
I've rooted my phone with the "new clarified method" thread, gotten to the clockwork mod and everything, but once I've done that I just cannot get the Unrevoked 2 to work. I've tried it on Windows 7, xp, and osx, and nothing seems to work! The main issue I'm getting is that it'll do the whole process, and then I think it says "reboot to recovery" and then I just get that old phone with a red triangle error. What could I possibly be doing wrong??? It can't be driver issues, because doesn't OSX do that automatically?

I had a similar issue on windows 7 and a simple pc reboot seemed to work for me.

Nope, still no luck. Am I supposed to put these Reflash files on the phone somewhere? I just feel like I'm missing some big step or something. Why is there no good tutorial on this process yet?

Oh my god I think I'm going to go insane! Please someone, point me in the right direction! I have done this hundreds of times now, I'm gonna die. All I can get is "Done!" and then my phone is showing me a big dumb red exclamation point triangle thingy. What am I doing wrong??????

Was I supposed to do something once I first reached the clockwork on my initial root? Cuz all I did was reboot to OS. I don't know if anybody can tell, but I'm kinda desperate. hah

Did you make sure that the phone is recongized in the device manager once plugged in? Need to help us out tell me what you have done so far? Did you install the SDK USB Drivers?
when at the command prompt, did you type adb devices? Does your device show up as connected?

larry996 said:
Did you make sure that the phone is recongized in the device manager once plugged in? Need to help us out tell me what you have done so far? Did you install the SDK USB Drivers?
when at the command prompt, did you type adb devices? Does your device show up as connected?
Click to expand...
Click to collapse
I was having the same problem also until I ran reflash.exe and the command prompt both as admin. I also reran Android SDK installing all of the updates. After plugging in the phone, the SDK picked up two more updates, one of which was USB drivers. Once I did that, things seemed to have worked.

Use attn1's method. The clarified method didnt work for me properly.
I assume you never flashed a rooted rom after reaching clockwork mod. If not the phone is not yet rooted. You have to get back to clockwork recovery and flash a rooted rom (either attn1's liberated one or his stock rooted rom). Both found in his liberated thread. Then set up all the drivers for unrevoked and run it. It should work then.

When my phone is just sitting in bootloader, it is not recognized by adb devices.

You have to go through the whole loop process again booting your phone into recovery and connecting the usb cable.

gdeadfan said:
When my phone is just sitting in bootloader, it is not recognized by adb devices.
Click to expand...
Click to collapse
Thats not good, try reformatting your sd card on your pc with an external reader not with your phone and try again. I'm almost certain it needs to be recognized by adb devices when in bootloader.

Just managed to install the Liberated beta ROM, but now unrevoked can't even get past superuser privelages. it's not popping up anymore

Nevermind, it gets past superuser now, but now it just says "waiting for reboot" and completely reboots the phone to the point at which i can use it regularly

Have you installed the hboot drivers?
Re-ran unrevoked?
Edit: Does it reach "done!"?

Yes, yes, and yes. And my phone just keeps getting to the red triangle. doesn't make any sense to me! And at this point, I'm positive I have no drivers getting in the way like Sync etc., and I'm sure HBoot is installed correctly.

Go to the android market and download titanium backup. It requires root so if it installs we know that you are at least rooted.

Try this, because I had the same problem. Go into device manager with Revoked2 says waiting for reboot. Look under devices above my computer or below cant remember and right click uninstall and remove the android device. reboot your computer then see if it installs are does it automatically, if not don't do anything just plug the phone in and get to hboot/ red triangle screen, then try revoked2 again. This finally got loop to read my device then when I got to clockwork I loaded "liberated rom"
Screw revoked2, just get to clockwork recovery and have liberated rom on your SD card ready to go. Then after install I ran revoked2 for clockwork mod.
Good Luck

Please avoid creating new threads for existing topics. Before creating a new post or thread, you should read all available information in the many Aria rooting threads.
Thank you for your understanding and cooperation as we work to organize the Aria forums.

im such a frustrated noobie

someone please tell me what does ADB stand for????????
i hate myself for being such a noob but what can i do?!?!?! whats adb pleaseeee...
and why is it that everytime i go into command prompt to try and do stuff with the phone it never finds "androidsdk"
ahh!!!!!

Frenzifun said:
someone please tell me what does ADB stand for????????
i hate myself for being such a noob but what can i do?!?!?! whats adb pleaseeee...
and why is it that everytime i go into command prompt to try and do stuff with the phone it never finds "androidsdk"
ahh!!!!!
Click to expand...
Click to collapse
How about you tell everyone what you are trying to do, and what you are typing in command prompt.

Android Debug Bridge....
Do you have Samsung drivers installed/setup?
Take a nice deep breath and do one learning step at a time. Android has a lot to teach. I would also encourage learning the phone use basics, reading up on things before attempting any mods. Welcome to android family.

Here is a good thread to start in.... http://forum.xda-developers.com/showthread.php?t=790004

tats_06 said:
Android Debug Bridge....
Do you have Samsung drivers installed/setup?
Take a nice deep breath and do one learning step at a time. Android has a lot to teach. I would also encourage learning the phone use basics, reading up on things before attempting any mods. Welcome to android family.
Click to expand...
Click to collapse
lol ... well i already opened another thread about how to put hebrew fonts on the phone to support hebrew instead of seing empty boxes on facebooks and websites and what not... my phone Was rooted, Was voodooed but there was force closing on things and market stopped working so i completely stocked the phone, only thing that doesnt work now is my phone memory which is on 0.00 which i read and you apparently have to root the phone all over again
so right now... the phone memory is my only issue, i guess i can live without hebrew if its too much of a hassle to install while rooted::
http://forum.xda-developers.com/showthread.php?t=480964
i have no idea how to work this^^^
i have the drivers installed like i said, i was able to odin, root, and voodoo, clockwork as well ofcourse. now phone is completely stock except for that memory issue.
http://forum.xda-developers.com/showthread.php?t=804457&highlight=phone+memory
completely got lost in this thread... so yeah, those are my problems with the phone at the moment. i wont mention the obvious of gps etc.

another awesome issue, everytime my phone is turned off and back on, it starts that set up process all over again... language; facebook; google... etc... why?

Once you install adb on your computer you have to go to change the path on your computer to point to that folder. Or you can change your directory to the one that holds the adb file from within the command prompt. This should allow you to run the commands.
The issue you are having with the memory on your phone is because voodoo did not completely uninstall. You can fix this by running the steps in this forum to uninstall voodoo. Don't try the one step zip, you are going to have to do the three step manual method to make this work. Don't forget the final step to wipe data.
Once this is done voodoo will be gone, memory should be back, and phone should stop resetting on every boot.
Obviously you aren't the only one to ever have these issues. But you can recover.
Good luck.
Sent from my SCH-I500 using XDA App

No intro
Here is what I did:
Wanted to flash new ROM, [ROM] Super Clean DI01 + AOSP apps, (Thanks to everyone who worked on it AND everyone on this forum cause Ive spent the past week reading the threads and felt confident enough in the info and the support to try).
BUT
when trying to download with ODIN (not certain if this was the right method, too late now) found that it did not work, couldnt see file when looking in the PDA browse.
STUPIDLY disconnected phone from computer while in DOWNLOAD MODE. You know, when the screen says "DONT DISCONNECT FROM TARGET". Apparently, the rebus string for "you dun f*cked up" is a phone symbol... a yellow triangle w/!...computer symbol.
What do I do to get back to fun?
Tried reboot, tried CWR reboot, tried Nandroid restore w/reboot still the YDFU symbol
*EDIT* I continued searching while awaiting a response and found this thread: Stuck on connection warning screen. This got me out of the YDFU screen into a nice force loop. Since I am not a -complete noob- I pulled a nandroid backup outta my hat and ...tada back to good, now to the fun!

Team Win Recovery Loop

Hello, I am new to XDA as being a member. This is my first post, and I promise I have spent at least an hour looking for similar threads to no avail.
Now to explain my problem,
Last night I rooted my kindle again after the 6.3 update that destroyed my last root. I used the Kindle Fire utility 9.5 by Vashypoo, and selected install permanent root with superuser.
As I discovered after this, I needed to get team win recovery before getting 6.3, so the KFU installed it for me, and it backed up my data before continuing with the rest of the root. After it said complete, I booted up my kindle, to find a yellow triangle and in a couple seconds, i got sent to this page automatically that I know now is the team win main menu. Every time I boot up my kindle, I get sent to the team win main page. I saw on a video by Nat3mil that the reason this was happening was because my kindle was automatically booting in recovery, so I tried to use kindle's bootmode menu to change the bootmode back to normal (4000) whenever I try, I get a message saying "The system cannot find the drive specified", and it would stop doing anything. I tried to manually set the bootmode back to normal by using command lines from a forum here on xda, similar to my problem, HOWEVER, whenever I try to connect my kindle to the pc, 9 out of ten times, my computer doesnt even recognize my kindle is connected, and when it does, it installs software, KFU says adb is online, and STILL whenever I try using KFU, command lines, or the Kindle Unbrick utility, it says "waiting for device". I literally cannot do a thing without help.... So to sum up, my problem is that I cannot connect my kindle to the computer, and second, I don't know what else to try... I really need help, and I have been doing tons of research (over six hours) to no avail, or progress.
Thank you for your time, and I hope that someone can help me.

Read this guide. It will give you an idea of what your problem is and what you are doing wrong. Its lengthy but worth it if you want do much with your Kindle, like installing recovery.
http://forum.xda-developers.com/showthread.php?p=23747567
Sent from my Amazon Kindle Fire using xda premium

your on the right path When you get it to say waiting for device hold the power button to shut the kindle off and then turn it back on and it will connect during boot up

soupmagnet said:
Read this guide. It will give you an idea of what your problem is and what you are doing wrong. Its lengthy but worth it if you want do much with your Kindle, like installing recovery.
http://forum.xda-developers.com/showthread.php?p=23747567
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
You see, I already read this in my expansive research. It doesnt exactly help, My computer does not recognize my device. I have manually installed the driver multiple times, my problem is not ignorance... But the thread was a bit helpful with less knowledgeable people such as myself. I do however have MUCH more experience with a lot of this than I let on by my passage above. Thank you for answering, but do you know what to do in my case? This is not a repeated thread, because I have seen nothing like this on a previous thread

MLS_Dumpster said:
You see, I already read this in my expansive research. It doesnt exactly help, My computer does not recognize my device. I have manually installed the driver multiple times, my problem is not ignorance... But the thread was a bit helpful with less knowledgeable people such as myself. I do however have MUCH more experience with a lot of this than I let on by my passage above. Thank you for answering, but do you know what to do in my case? This is not a repeated thread, because I have seen nothing like this on a previous thread
Click to expand...
Click to collapse
You have to get it to how you had it to say waiting for device... reinstall the drivers, reboot comp what ever you have to do than do what i posted... you can even open a command promp from the KFU tools folder by going to tools hold shift and right click... open command than type..
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot

It happens randomly, You see, another problem I have been having is that, My kindle has no problem connecting to the computer, in device manager, I have adb interface up and running, my kindle connected, but it isnt useable, it says my adb is offline, and whenever that happens, I cannot do a thing... There is no tred whatsoever as to how to get adb working, as it happens at random tries of me installing the drivers, and restarting my comp/kindle, do you have any idea how to get it working? Thanks by the way, You literally are a lifesaver.

MLS_Dumpster said:
It happens randomly, You see, another problem I have been having is that, My kindle has no problem connecting to the computer, in device manager, I have adb interface up and running, my kindle connected, but it isnt useable, it says my adb is offline, and whenever that happens, I cannot do a thing... There is no tred whatsoever as to how to get adb working, as it happens at random tries of me installing the drivers, and restarting my comp/kindle, do you have any idea how to get it working? Thanks by the way, You literally are a lifesaver.
Click to expand...
Click to collapse
Im on linux so idk how to set it up on windows.... i have read of people having issues with the drivers and having to reinstall them after using kfu.. id just make sure you delete the kindle driver and the android adb composite driver and start fresh.. or even try and mount it threw twrp mabe that will help

Thanks for helping me, seriously. Windows is annoying with drivers. I'll try what you suggested. Thanks again

DJLamontagneIII said:
Im on linux so idk how to set it up on windows.... i have read of people having issues with the drivers and having to reinstall them after using kfu.. id just make sure you delete the kindle driver and the android adb composite driver and start fresh.. or even try and mount it threw twrp mabe that will help
Click to expand...
Click to collapse
THANK YOU THANK YOU THANK YOU THANK YOU
IT WORKED. YOU, sir, are a life saver.
Thanks again.

MLS_Dumpster said:
THANK YOU THANK YOU THANK YOU THANK YOU
IT WORKED. YOU, sir, are a life saver.
Thanks again.
Click to expand...
Click to collapse
Awsome

MLS_Dumpster said:
You see, I already read this in my expansive research. It doesnt exactly help, My computer does not recognize my device. I have manually installed the driver multiple times, my problem is not ignorance... But the thread was a bit helpful with less knowledgeable people such as myself. I do however have MUCH more experience with a lot of this than I let on by my passage above. Thank you for answering, but do you know what to do in my case? This is not a repeated thread, because I have seen nothing like this on a previous thread
Click to expand...
Click to collapse
I wasn't trying to be rude but the exact problem you were having was covered in the thread that I posted along with the same solution suggested by DJLamontagnelll.
Sent from my Amazon Kindle Fire using xda premium

soupmagnet said:
I wasn't trying to be rude but the exact problem you were having was covered in the thread that I posted along with the same solution suggested by DJLamontagnelll.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I think I sounded more harsh than I meant to be. The solutions on the thread only cover one of my problems, and thats the drive thing. Thanks, you did help.
Sent from my Kindle Fire using XDA

Hello.
I write to you because I have a big problem with mi LG G2 D802.
Yesterday I tried to install a CRM apk to use in a signature of the University. I was using CM11, but the apk had failed. So, I restored my ROM STOCK backup and when the phone start, a new update was downloaded and installed. Then, the phone only enter in recovery mode. I tried the different wipes, restore again ROM Stock, install again CM11 ROM but the problem was not solved.
I tried to enter in bootleader (pushing vol+ and insert the usb cable), but the phone reboot in recovery.
Now, I don´t know why, the phone is empty. I tried to restore ROM Stock backup from USB OTG but the recovery don´t recognizes the folders.
Please, can anybody help me? I need the pone!
Thanks.
Regards,
Nicolas.

nicolas_h18 said:
Hello.
I write to you because I have a big problem with mi LG G2 D802.
Yesterday I tried to install a CRM apk to use in a signature of the University. I was using CM11, but the apk had failed. So, I restored my ROM STOCK backup and when the phone start, a new update was downloaded and installed. Then, the phone only enter in recovery mode. I tried the different wipes, restore again ROM Stock, install again CM11 ROM but the problem was not solved.
I tried to enter in bootleader (pushing vol+ and insert the usb cable), but the phone reboot in recovery.
Now, I don´t know why, the phone is empty. I tried to restore ROM Stock backup from USB OTG but the recovery don´t recognizes the folders.
Please, can anybody help me? I need the pone!
Thanks.
Regards,
Nicolas.
Click to expand...
Click to collapse
Please post in correct forum. G2 Q&A, Help & Troubleshooting

[Q] adb offline nexus 7 4.2.2

Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:

Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?

how to do that?
compty said:
Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?
Click to expand...
Click to collapse
how to unlock bootloader 4.2.2?
yes usb debugging is enabled

I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.

google toolkit error trying to unlock
compty said:
I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.
Click to expand...
Click to collapse
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally

Same problem
leo9252 said:
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally
Click to expand...
Click to collapse
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.

Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981

further problems
sicameron32 said:
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.
Click to expand...
Click to collapse
So I was going to do it the old fasion way by following this guide
http://forum.xda-developers.com/showthread.php?t=2150661
I didn't quite get step four because the nexus 7 doesn't have an SDcard, but I copied the zip to the root of the device.
When I did step 7 the device did not go to Fastboot, it didn't go anywhere other than a black screen. I think I have a faulty unit, or the holding of the volume buttons with the power is really not the way to get to fastboot, either way I am looking at a brick right now. Any thoughts will be welcome. I messed around with it for 10 min now and got the device to re-boot. Not sure if I should try the fast boot option again.

Are you on Windows 8 by any chance?
Because I couldn't get it to work on Windows 8 and had to use Windows 7.

You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.

everyone i got it working! adb offline fixed
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.

leo9252 said:
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.
Click to expand...
Click to collapse
It won't let me download and install anything from the 4.2 list...did you do anything else?

myleb said:
You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.
Click to expand...
Click to collapse
FWIW, here is my experience:
PC: Win7 Pro x64 SP1 - SDK platform-tools 16.0.1 - SDK Tools 21.1 - ADB v 1.0.31
N7: JDQ39 Stock *
( *OK, i diddled default.prop in my boot image to set "ro.secure =0". I don't know if that could make a difference or not )
The Nexus 7 asks for confirmation of inbound adb sessions for every new adb server invocation on the client PC.
When it does ask for credentials, you have to get to the on-screen display pretty quickly - a couple of seconds at most. If you don't the device will be reported as "offline" by the first invocation of
adb devices
If you accept the connection, the next time you run "adb devices", the status is back to normal (reports "device" instead of "offline").
You can test this out yourself - just iterate in a loop these three commands:
adb devices
adb devices
adb kill-server
Nothing that can't be understood by someone who knows what is going on; but I suppose that all the toolkits are running adb underneath the hood, so it is certainly possible to get tripped up when using a toolkit if you aren't Jhonny-on-the-Spot when that dialog pops up on the tablet.
Also, for the adventuresome:
I note that the new stock JDQ39 (4.2.2) ramdisk has a new line in the default.prop that was not in JOP40D (4.2.1) :
Code:
ro.adb.secure=1
I suppose that could be toggled off if you have a favorite kernel/ramdisk setup and you don't want to be bothered by this stuff. But it does mean unpacking/repacking your boot images.
cheers

I'm having the same problem. Never recognizes an ADB device. When it does it shows my serial number followed by "offline."
Any ideas? I'm ready to return this thing.
---------- Post added at 08:28 PM ---------- Previous post was at 08:16 PM ----------
Out of curiousity what driver are you using and how are you installing it?
Also where is your device coming up in the device manager?
I've tried so many things that I think I'm getting off track. Sadly my motorola phones were much easier to root.

how come you cant?
LucentBirch said:
It won't let me download and install anything from the 4.2 list...did you do anything else?
Click to expand...
Click to collapse
How come you can't download and install from the SDK manager?
That's how my problem got fixed.

Worked
jibdev said:
Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981
Click to expand...
Click to collapse
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.

you're welcome
sicameron32 said:
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.
Click to expand...
Click to collapse
I knew someone would find this useful.
:laugh::good:

leo9252 said:
I knew someone would find this useful.
:laugh::good:
Click to expand...
Click to collapse
The sad thing is I have no idea what finally got it to work. Maybe just an extra reboot I had forgotten at some point. I do know however that I had to add a few extra lines (hardware ID) to the .inf file in the usb driver. Not sure which did the trick. I also used a combo of the toolkit to unlock and the manual method to root. Also I am unable to boot my device into the bootloader/fastboot via windows and rather have to manually (physically) shut down the device and enter the bootloader via the physical buttons. Probably an issue with the windows drivers again, but at least I have full functionality once in fastboot.
Only thing is now I can't get access to the storage via windows. And there's no way in hell I want to change the ADB drivers without knowing which finally worked for me. I'm thinking though that this is an entirely different device in device manager (I'm obviously not that knowledgeable).
Also I'm kinda annoyed by the unlocked padlock symbol on startup. I suppose that should be a welcome sign of achievement after spending all day trying to unlock/root, especially for such an unlearned person as myself.

did you clear this issue?
leo9252 said:
Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:
Click to expand...
Click to collapse
if not, pls gimme a mesg.
cause I'm a noob, I cannot use link here. :crying:
This issue is included in 4.2.2, and ADB is disabled by default for security.
I tested on my Nexus 4, 4.2.2 running. :fingers-crossed:

Okey. So to summarise: there is this new security feature in android 4.2. that makes the device show a popup if you want to allow the connected computer to use the adb = debugging bridge. But for this to work, you need to have the newest adb binary, which needs to print 1.0.31 when you run "adb version"
(found that info here --> http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/ )
Under linux when you try to do it the old-school google-recommended way and download the huge "adt-bundle-linux-x86_64-20130219" and use the "android" tool to find new updates to the platform tools, it will tell you you already got the latest version which is rev 16.0.2 which contains an adb binary which will print version 1.0.26 which will not work with this new android 4.2.2 security feature.
So after searching for a linux adb 1.0.31 binary, I found it here:
https://github.com/mozilla/r2d2b2g/commit/2eefcc05366173ca51635da8f542fd8473ba0fea -->
https://ftp.mozilla.org/pub/mozilla.org/labs/r2d2b2g/adb-1.0.31-linux.zip
with that binary I finally can use adb on my nexus 7 again.

[Q] Ach! Doh! I did it. I bricked my N7 while going 4.4 to 4.3

I know. You guys have heard it all before...but
I was using WugFresh to re-flash back to 4.3 from 4.4 and the recovery was taking so long. After an hour of running, I was moving the device to a coffee table when the cable fell out.
Hay, why isn't a message include in WugFresh like the backup process as to approximately how long this process takes? That brings up another issue in general with these old N7s is that these micro-USB female connectors get loose after so many years of use, makes connecting and charging difficult.
But I digress.
I have read often in the XDA forums about a factory reset ‘from bricked feature’ in WugFresh, but I can not find that feature anywhere where ‘bricked’. anything is. If it is there, where is it?
Anyway, how can I recover the bootloader and everything without having to learn doing everything via a cmd line or .bat process?
These are the facts:
Nexus 7 2012, 8g, re-flashing back to 4.3 from 4.4, using Nexus Root Kit
v1.8.2, Flash Stock + Unroot (I had read in XDA Forum somewhere where it was suggested to go back to a factory vs to use this option).
The N7 is currently has one of 4 states available: Bootloader screen (with below stated status), Google initial screen (with "Start" Showing and "Booting failed" in the upper right corner), or it can Power off. Recovery Mode is an option, but does nothing but cycles to the Google initial screen.
In Fastboot mode the status says this:
FASTBOOT MODE
Product name - grouper (it got that far)
Variant - grouper
HU version - E3
LOCK STATE - UNLOCKED
Bootloader Version - N/A
Serial Number - 015d2109ab281807
SIGNING - not defined yet
Of course I can't get an MTP connection to Microsoft XP, but an "Unknown
device" error shows up under USB when I connect the cable. No drivers from WMSDK kit or any from WugFresh worked.
Oh, and by the way, the WugFresh backup didn't work for me. It saved next to nothing, but I have another type of backup that works, so no worry.
GOT ANY SUGGESTIONS?

Looks like it will be fine follow the sticky for reflashing a factory image.
http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Don't use toolkits for flashing devices just learn the adb commands its much safer. The reason there is no time for completing a flash if it varies with devices.
FYI the wugfresh option you are looking for is return to stock/unroot with soft bricked checked
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.

Captain Sweatpants said:
Looks like it will be fine follow the sticky for reflashing a factory image.
http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Don't use toolkits for flashing devices just learn the adb commands its much safer. The reason there is no time for completing a flash if it varies with devices.
FYI the wugfresh option you are looking for is return to stock/unroot with soft bricked checked
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Click to expand...
Click to collapse
{Q} Thanks Captain, I have been following the Guide instruction, but I have some other questions before I proceed.
In your Quote above you said “follow the sticky for reflashing”, I don’t know what you mean by a “sticky” and I have looked though a lot of the pages after the "[GUIDE] Flashing a Factory Image with fastboot / return to stock" and I can not find “reflashing” mentioned yet. Did you mean to go directly to the "Flashing the Factory Image" section in the Guide and follow that?
Since I didn't know that answer, I went a head and read the whole Guide and other questions popped up: If I have to download Java SE JDK will the Version 6 I already have work? The Oracle website you directed me to won’t let me download Version 8; however, Android SDK did accept Version 6 to install.
I did re-download all the drivers as instructed and put the JWR66V bootloader into the place of the JWR66Y one and then inserted bootloader-grouper-4.23.img, image-nakasi-jwr66y.zip, flash-all.sh, and flash-base.sh all into <my sdk directory>\platform-tools as the Guide says.
Now that I think I have it all ready to go, will I still have to run the Adb cmds to install Drivers?

I don’t know what you mean by a “sticky"
Click to expand...
Click to collapse
A sticky is a thread that a mod has "stickied" meaning that it won't move down the forum but stays at the top.
I can not find “reflashing” mentioned yet. Did you mean to go directly to the "Flashing the Factory Image" section in the Guide and follow that?
Click to expand...
Click to collapse
Yes that's what I meant.
Just follow the whole guide and take it slow if you have been relying on toolkits like wugfresh this will be a not of a learning curve
Now that I think I have it all ready to go, will I still have to run the Adb cmds to install Drivers?
Click to expand...
Click to collapse
Yes you still have to install drivers you shouldn't need adb to do that just make sure windows has the correct adb and fastboot drivers installed. If you have been using wugfresh NRT the drivers should be OK.
As your device is soft bricked where the guide says use the command adb reboot bootloader you will need to manually enter the bootloader by pressing power & vol +
Sent from my C5303 using xda app-developers app

Now its Driver installation issues
Captain Sweatpants said:
A sticky is a thread that a mod has "stickied" meaning that it won't move down the forum but stays at the top. Yes that's what I meant.
Just follow the whole guide and take it slow if you have been relying on toolkits like wugfresh this will be a not of a learning curve
Yes you still have to install drivers you shouldn't need adb to do that just make sure windows has the correct adb and fastboot drivers installed. If you have been using wugfresh NRT the drivers should be OK.
As your device is soft bricked where the guide says use the command adb reboot bootloader you will need to manually enter the bootloader by pressing power & vol +
Sent from my C5303 using xda app-developers app
Click to expand...
Click to collapse
{Q} Installing the driver now seems to be the issue. I tried a couple of things:
1. I know this was not exactly appropriate, but I went into Device Manager, located the USB “Unknown Device”, tried to update
the Driver after selecting it, directed the screens to both the ‘supposed’ drivers in WugFresh and Adb subdir’s. None took.
2. Then I forced a new device though the Control Panel’s, Add New Hardware, navigated to “Add a new hardware device” and
selected “Google Nexus 7 ADB interface”, and it created the new device. The Device Manager showed and error on the
device, so I refreshed it with the Adb driver, with no different results.
3. I then added the device driver “Google Nexus Bootloader Interface” via Add New Hardware
4. I rebooted the computer. After it came back up…
5. I looked at the Device Manager with no change in the status of any of the Android or the Unknown USB Device.
6. I insured the N7 was in bootloader mode by rebooting with volume keys/on key.
7. I went ahead and ran “adb drivers” cmd after entering the “cd’ cmd. I got the following:
Bear with me as I have no screen printing capability at this time.
>Command Prompt screen:
>C:\<adb dir>\platform-tools> adb devices
>List of devices attached
>C:\<adb dir>>\platform-tools>
And as you can see, NO listing showed.
So what’s next? I have another XP computer I can try this on, but I will have to get all the Abd stuff over to it 1st. While you answer I will try that.

Your Nexus in fastboot mode is not an adb device so it won't show up. Change your command to fastboot devices and it should work.
If you are still having driver issues download USB deveiw and remove anything that looks like a Nexus bootloader interface or adb device
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.

Captain Sweatpants said:
Your Nexus in fastboot mode is not an adb device so it won't show up. Change your command to fastboot devices and it should work.
If you are still having driver issues download USB deveiw and remove anything that looks like a Nexus bootloader interface or adb device.
Click to expand...
Click to collapse
OK, I have tried what you said with no results. If you would be willing to work with my computer directly, I have a method of allowing you to see what I see. The 2nd computer I have the N7 on right now have very little personal stuff on it, and I would be willing to let you access it. I have set up a temporary e-mail address [email protected] you can send an e-mail to with your e-mail address, and we can correspond directly, thus I can give you the access you need. I know you are else where in the world, so I would be willing to leave my computer up for you to see it all when you like. What do you think?
Tell me the final score of Zebre and your teem, what date it occurred, and what the sport is so I know it is you. Send the answer to the e-mail above, so I know it is you. I’ll only give you a short time to respond.

nickynooner said:
OK, I have tried what you said with no results. If you would be willing to work with my computer directly, I have a method of allowing you to see what I see. The 2nd computer I have the N7 on right now have very little personal stuff on it, and I would be willing to let you access it. I have set up a temporary e-mail address [email protected] you can send an e-mail to with your e-mail address, and we can correspond directly, thus I can give you the access you need. I know you are else where in the world, so I would be willing to leave my computer up for you to see it all when you like. What do you think?
Tell me the final score of Zebre and your teem, what date it occurred, and what the sport is so I know it is you. Send the answer to the e-mail above, so I know it is you. I’ll only give you a short time to respond.
Click to expand...
Click to collapse
It wouldn't work as I would need to be able to press buttons on the nexus.
If none of this is working then try wugfresh NRT again make sure you have the most up-to-date version from www.wugfresh.com its 1.8.2
The option you are looking for is unroot/back to stock there is an option for soft bricked make sure that is ticked
Sent from my Nexus 7
Hit thanks if I've helped

The Fat Lady Just Sang an Unhappy Song!
Hi Captain,
Thank you for all of your help and patience with me. I have read a lot more about the status of my device through looking at the XDA forum about other devices that have the kind of issue I do, and I have concluded mine is HARDbricked. I went ahead and ordered another motherboard off of eBay. My device was an 8G and I got a 32G replacement, making sure it was for my age of my N7. XDA forum and other websites say the boards are interchangeable. I was thinking about buying a new device anyway and this way I can upgrade and still have the same familiar device with no learning curve of a new one.