HELP Nexus 7 JB 4.2 update - Nexus 7 General

So I just received the Jellybean 4.2 update today. I was a little excited. However, after the update the device is now sluggish, unresponsive, it refuses to connect to any wifi or bluetooth device, and all other manner of trouble.
I want to revert back to 4.1.2 and I am using the Nexus Root Toolkit. The app cannot unlock, root, or reflash the stock 4.1.2 rom though. I always get the error Fastboot device was not found. What does this mean and how do I fix it? I've booted into the Fastboot thing where it says Start at the top.
Someone please help, I have 3 Nexus 7's here all suffering from the same issues.
EDIT:
USB debugging is on.
The drivers are installed and configured via the guide in Nexus Root Toolkit.

You are getting that error because you need to enable USB debugging. In 4.2 it is hidden. Go to settings/about and spam hit the build number until it says Congrats you are now a developer. Go into develpper options, enable USB debugging. Voila, should now be able to reflash.
Sent from my Galaxy Nexus using Tapatalk 2

It only seems to work on the main account. Not that it matters much. It says your a developer but you cannot access the options
Sent from my Nexus 7 using XDA Premium HD app

bolagnaise said:
You are getting that error because you need to enable USB debugging. In 4.2 it is hidden. Go to settings/about and spam hit the build number until it says Congrats you are now a developer. Go into develpper options, enable USB debugging. Voila, should now be able to reflash.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I've had usb debugging on the entire time and still get that same error.

Related

[Q] Droid 4 Motofail Root Method Not Working

I'm trying to root my stock Droid 4 using Motofail, and I can get to the beginning of the method but then all I get is this:
Motorola universal root script ($version version)
by Dan Rosenberg (@djrbliss)
Tested on Droid 3, Droid Bionic, and Droid RAZR
Before continuing, ensure USB debugging is enabled, that your
device is in charge only mode, and your phone is connected via USB.
Press any key to continue . . .
Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
My phone is all of those things listed, and as far as I know I haven't done anything incorrectly. Anybody know how to fix this?
You do have the latest USB drivers from Motorola, right?
Aside from that and having USB mode in Charge Only, I personally can't think of any issues getting the root tool from starting up (but, hey, I'm no expert in this field).
Sent from my DROID4 using XDA
BPMOmega said:
You do have the latest USB drivers from Motorola, right?
Aside from that and having USB mode in Charge Only, I personally can't think of any issues getting the root tool from starting up (but, hey, I'm no expert in this field).
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
I was unable to find a Droid 4 ADB driver. Would a Droid RAZR one work?
wynn55 said:
I was unable to find a Droid 4 ADB driver. Would a Droid RAZR one work?
Click to expand...
Click to collapse
You can just get the drivers straight from the motorola site. They aren't phone specific. And just to share by experience the root method didn't work for me the first time either so I just ran it again and it worked. Just make sure you have usb debugging enabled and your phone is in charge only mode.
Thanks!
Grizzy3 said:
You can just get the drivers straight from the motorola site. They aren't phone specific. And just to share by experience the root method didn't work for me the first time either so I just ran it again and it worked. Just make sure you have usb debugging enabled and your phone is in charge only mode.
Click to expand...
Click to collapse
This seemed to do the trick! Thanks for the help.
wynn55 said:
This seemed to do the trick! Thanks for the help.
Click to expand...
Click to collapse
I'm glad it worked for you
BPMOmega said:
You do have the latest USB drivers from Motorola, right?
Aside from that and having USB mode in Charge Only, I personally can't think of any issues getting the root tool from starting up (but, hey, I'm no expert in this field).
Click to expand...
Click to collapse
Is "Charge Only" the same thing as "USB Debugging" (the wording used in the Rosenberg instructions)? I'm thinking about getting a D4 and would want to root but I'm doing some research first.
Thanks.
OhioGuy67 said:
Is "Charge Only" the same thing as "USB Debugging" (the wording used in the Rosenberg instructions)? I'm thinking about getting a D4 and would want to root but I'm doing some research first.
Thanks.
Click to expand...
Click to collapse
No. "Charge Only" is the option you will select when you connect USB (you'll see a status notification that you can tap to bring up the USB mode dialog).
Enable debugging is selected in settings under "Developer Options".

[SOLVED] Stock 4.2.1 upgrade failed.

I've bought my son and daughter a nexus 7 each for Christmas.
His upgraded over the air fine, hers downloaded the firmware, rebooted and the installation started.
After a couple of minutes the Android fell over with a red exclamation mark.
I've tried forcing the upgrade and the same happened.
Any ideas how to upgrade her nexus 7?
Thanks
Fastboot mode is working ?
Sent from my GT-I9100 using xda premium
I've not tried it.
How do I try it?
Assuming it's ok, does that help with upgrading?
Any issue truing fast boot mode?
Any ideas? Or will it need replacing?
Factory reset and try again
Sent from my Nexus 7
I have the same problem.
Hey guys,
I made an account just to post this, however it was all done my G2 so I apologize for poor formatting and/or not completely clear instructions. This issue has kept me up for hours upon hours, and I finally figured out how to fix it. The issue apparently has something to do with the way the Nexus was formatted, prohibiting the update from working. Google/Asus support have been useless regarding the issue which is a very simple fix just requiring the user to reflash the N7 with a stock image. It has been confirmed working by not just me but other people on the reddit nexus 7 board. Here is what I did (copy/pasted from my reddit thread):
---------------------------------------------------------------------------------------------------------------------
There are two methods to fix this, an in depth method, and an easy and quick method. My first time I used the in depth, but I tested this with the easy method too so I'll just post that. I'm on a cell phone so I'm not going into the in depth method - I'm posting this so hopefully the other people like me who got this on Christmas won't have to return it.
----------------
For the quick and easy method, download Wug's toolkit here:
(google this, forums wont let me post links until I reach 10 posts)
Run the driver install guide, making sure to follow the parts about uninstalling previous drivers. Follow this to a T. Next, unlock your bootloader. Its painless and takes seconds. Next, go here and download your Nexus specific update.
(Find this on google developer site, you can google it too - forums wont let me post links - also make sure its 4.2.1)
Click on the "back to stock + unroot" -- we never rooted, but just do this. Select other/browse and browse to the image you downloaded. Flash this. You WILL fail on three files - it says something like recovery.sig failed - it will do it for two other .sig files. This is fine. Let it do its thing. A few minutes later your android will boot up. Log in, and go to settings. Click about tablet. Click on build number like 10 times, until it tells you developer options unlocked. Go into developer options and enable USB debugging. Now, go back to Wugs toolkit and lock the bootloader. There you have it, an updated nexus running stock everything, and locked so your warranty is not void.
----------------------------------------------------------------------------------------------------------------------------
This was a very sloppy guide put together on my cell phone. Any questions just post and I'll do my best to get back to you. Goodluck!
Hi.
Thanks for the reply.
Just wondering if there is an easier way to do this.
I'm not comfortable flashing a new device.
What was the suggestion about fast boot?
Thanks
albert_htc said:
Hi.
Thanks for the reply.
Just wondering if there is an easier way to do this.
I'm not comfortable flashing a new device.
What was the suggestion about fast boot?
Thanks
Click to expand...
Click to collapse
This is definitely the easiest way for you to fix your problems. The risk of your device becoming unusable is practically none. This is the beauty of nexus devices, Google provides official factory reset ROMs for you to flash in these sorts of situations. You can either use Wugs or mskip's tookit as advised to automate the process (fastboot commands used to flash the recovery image, fastboot commands are simply used to flash it to your device) or you can use fastboot to flash it yourself manually (still very easy)
I would 100% do this to fix your device. Don't be scared! This is the official way of fixing a nexus device when it doesn't function.
Thanks.
I'm trying this now.
I've uninstalled all previous drivers, and it's updated to an 'Android Phone -> Android Composite ADB Interface'
I've clicked the Reboot BootLoader Button.. and nothing happens on the tablet.
This was trying with the #3 driver option.
I'm now trying driver #2 !!
Another quick question...
Once all this is done, will I have issues with it in the future, or should this resolve future updates.?
albert_htc said:
Another quick question...
Once all this is done, will I have issues with it in the future, or should this resolve future updates.?
Click to expand...
Click to collapse
I'm not certain about the driver issues because I don't use Wug's toolkit, sorry!
However, when you get this completed, it should solve this problem in the future.
I've had to go with option 1 for the drivers..
but it's done and working
One thing I did have to do after unlocking the boot loader was reset up on the wifi and re enable USB debugging before I could continue.
all sorted thanks
albert_htc said:
Thanks.
I'm trying this now.
I've uninstalled all previous drivers, and it's updated to an 'Android Phone -> Android Composite ADB Interface'
I've clicked the Reboot BootLoader Button.. and nothing happens on the tablet.
This was trying with the #3 driver option.
I'm now trying driver #2 !!
Click to expand...
Click to collapse
Let us know how it comes out and if there's problems, exactly where you're hitting the problem. I will try to help you out and later today I could probably get on team viewer and help you figure the drivers out.
Sent from my Nexus 7 using Tapatalk HD
Hi CharliesTheMan..
It's working. Had to use option 1 for the drivers.. but its updated and working
Thanks
Glad it worked out!
Sent from my Nexus 7 using Tapatalk HD

New Security Features for ADB in 4.2.2

After upgrading to 4.2.2, some N7 will not be seen by any computer via USB and the only way to remedy it is to shut off USB debugging. On other devices, the computer will see the N7 even if USB debugging is enabled, but running "adb devices" will show the device as offline. This is a problem with the Nexus 10 as well.
UPDATE: This turns out to be security. See below.
Sent from my Nexus 7 using Tapatalk HD
oldblue910 said:
After upgrading to 4.2.2, some N7 will not be seen by any computer via USB and the only way to remedy it is to shut off USB debugging. On other devices, the computer will see the N7 even if USB debugging is enabled, but running "adb devices" will show the device as offline. This is a problem with the Nexus 10 as well.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Just waiting for more ppl to confirm this problem. I still stay at 4.2.1
Re: Warning: 4.2.2 Breaks ADB and USB Debugging
No problems here. USB debugging turned on, transferring my data back to my storage now. Tho I did update my SDK tools to the latest the other day. You will see a new pop up message to allow debugging pop up.
Sent from my Nexus 4 using xda premium
rayford85 said:
No problems here. USB debugging turned on, transferring my data back to my storage now. Tho I did update my SDK tools to the latest the other day. You will see a new pop up message to allow debugging pop up.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Ah this may be my issue...I may need to update my SDK tools. I haven't done that in months.
Confirmed breakage usb debugging and adb on my nexus 7
I just installed the 4.2.2 update on rooted stock and after installation root no longer worked. When I went to re-root I could not connect. It showed my tablet but it said it was showing as turned off or unavailable even though it was connected so then I restored back to 4.2.1 unrooted and tryed to connect and same problem. You can connect and send media files but anything else is not working at least for me.
So for my device I can confirm adb and usb debugging seems broken for now. I have the first production run 16 wifi model. I can also say wifi performance seems improved. The signal seems slightly boosted and also seems to stream content smoother farther away from the router. I do not have any bluetooth devices to confirm those fixes. Seems fast and stable for me so far.
I will probably revert back to a custom rom since I like the rooted apps but this release initially seems pretty solid.
Re: Warning: 4.2.2 Breaks ADB and USB Debugging
robbbzilla said:
I just installed the 4.2.2 update on rooted stock and after installation root no longer worked. When I went to re-root I could not connect. It showed my tablet but it said it was showing as turned off or unavailable even though it was connected so then I restored back to 4.2.1 unrooted and tryed to connect and same problem. You can connect and send media files but anything else is not working at least for me.
So for my device I can confirm adb and usb debugging seems broken for now. I have the first production run 16 wifi model. I can also say wifi performance seems improved. The signal seems slightly boosted and also seems to stream content smoother farther away from the router. I do not have any bluetooth devices to confirm those fixes. Seems fast and stable for me so far.
I will probably revert back to a custom rom since I like the rooted apps but this release initially seems pretty solid.
Click to expand...
Click to collapse
There's a new security feature in 4.2.2 to keep "adb thiefs" off your device. http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/
After you enable USB debugging and plug the device in, you should get a prompt to allow the computer access to your device.
Sent from my Nexus 4 using xda premium
Wouldn't exactly say "it's broken" considering:
http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/
It's a new addition to the ADB security and I'm sure as time passes we'll learn more about the inner workings.
Disclaimer: I installed 4.2.2 this morning just after it was released and I had no issues with ADB or USB debugging in the 2-3 hours I was testing it - I was pure stock across the board from 4.2.1 to 4.2.2 and had no problems.
Bleh, post above me covered it just as I did, only a few seconds faster.
Definitely not a bug
... it's a security feature, as mentioned above. I was pulling my hair out over it at first, until I rebooted my computer and restarted adb, and got the familiar dialog. You have to activate it for each machine you plug it into, it seems.
rayford85 said:
There's a new security feature in 4.2.2 to keep "adb thiefs" off your device. http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/
After you enable USB debugging and plug the device in, you should get a prompt to allow the computer access to your device.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I know about the security feature. It did not prompt me. I even turned usb debugging on and off, turned pc and device on and off. I cleared cache and no difference. I did not get any prompt.
Maybe it is just me.
I will reflash and reboot and update it again and see if it works but for me it doesn't work. Not sure about broken just not working for installing root. I can transfer media files fine.
Just run the Android SDK Manager and update everything. Fixed.
Always remember, new version? Use ADB? Update SDK.
Also Wugs Toolkit will work again if you replace the adb files that comes with his kit.
r00t4rd3d said:
Just run the Android SDK Manager and update everything. Fixed.
Always remember, new version? Use ADB? Update SDK.
Also Wugs Toolkit will work again if you replace the adb files that comes with his kit.
Click to expand...
Click to collapse
I will give it a shot. Sometimes I forget to do basic things thinking I know about something I don't. So many more knowledgeable people here. Thanks for the help.
R
oldblue910 said:
After upgrading to 4.2.2, some N7 will not be seen by any computer via USB and the only way to remedy it is to shut off USB debugging. On other devices, the computer will see the N7 even if USB debugging is enabled, but running "adb devices" will show the device as offline. This is a problem with the Nexus 10 as well.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
It was working for me,I used adb to pull the system of the nexus 7.
Re: Warning: 4.2.2 Breaks ADB and USB Debugging
Updating adb fixed my N10 but not the N7. On the N7, with USB debugging enabled, adb devices shows no devices and will not show up as a media device. If I disable USB debugging, it will show up as a media device, though. Also, adb sideload works fine in stock recovery. Any thoughts?
Sent from my Galaxy Nexus using Tapatalk 2
Re: Warning: 4.2.2 Breaks ADB and USB Debugging
Yes, be sure to update your SDK to API17. There is a glitch on the SDK manager though that I had where I had to refresh the list twice to even have API17 appear. Otherwise it ended at API16/4.1
Sent from my Nexus 7 using Tapatalk HD
Re: Warning: 4.2.2 Breaks ADB and USB Debugging
r00t4rd3d said:
Just run the Android SDK Manager and update everything. Fixed.
Always remember, new version? Use ADB? Update SDK.
Also Wugs Toolkit will work again if you replace the adb files that comes with his
Where can I find the adb file I need to 'replace in wugs kit?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
tdizzle404 said:
Where can I find the adb file I need to 'replace in wugs kit?
Click to expand...
Click to collapse
The data folder of where ever you installed Wugs tool kit too. I replaced 4 files, adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll. You get these 4 files from the Android SDK platform-tools folder after you update the SDK.
-
Perhaps the title of this thread should be changed from
"Warning: 4.2.2 Breaks ADB and USB Debugging"
to
"New Enhanced Security Feature with 4.2.2"
Just a thought..
r00t4rd3d said:
The data folder of where ever you installed Wugs tool kit too. I replaced 4 files, adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll. You get these 4 files from the Android SDK platform-tools folder after you update the SDK.
-
Click to expand...
Click to collapse
Cheers, that was just the info I needed to reapply root after upgrading to 4.2.2. I couldn't work out why ADB could connect but not Wugs toolkit.
ingenious247 said:
Perhaps the title of this thread should be changed from
"Warning: 4.2.2 Breaks ADB and USB Debugging"
to
"New Enhanced Security Feature with 4.2.2"
Just a thought..
Click to expand...
Click to collapse
Exactly ADB Debug has always been a huge glaring security hole for Android devices, some third party apps have been developed or added functionality to disable ADB Debug when the screen is off, etc, to close this hole.
Thanks
r00t4rd3d said:
The data folder of where ever you installed Wugs tool kit too. I replaced 4 files, adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll. You get these 4 files from the Android SDK platform-tools folder after you update the SDK.
-
Click to expand...
Click to collapse
you made it possible for me to be rooted again ... wish i could thank you more than once ... that was getting frustrating ... now after that whole ordeal im considering going back to aokp jb mr1 B3 over staying stock ... but maybe ill just wait ... depends on how long i can stand using the GNEX with a cracked f'n screen lol ... man can the SG4 hurry up??? idk what to do right now .. i need something to flashhhhhhh!!!

[Q] How to unlock bootloader on 6.0 Stock

Hi,
So today I bought a Nexus 6. I straight away updated to 6.0, forgetting that I should have unlocked the bootloader! So now I wan to know if I can unlock the bootloader on stock! I really want root so thanks in advance to those who are able to help!!!
Regards
Yep, install the Android SDK (or just the tools adb and fastboot). If on windows install the driver, connect your phone, and type
fastboot flashing unlock
But this will erase everything on your device.
istperson said:
Yep, install the Android SDK (or just the tools adb and fastboot). If on windows install the driver, connect your phone, and type
fastboot flashing unlock
But this will erase everything on your device.
Click to expand...
Click to collapse
Before typing that command be sure to go into Developer options and enable both USB debugging and OEM unlocking.
Sent from my P01MA using Tapatalk
wtherrell said:
Before typing that command be sure to go into Developer options and enable both USB debugging and OEM unlocking.
Sent from my P01MA using Tapatalk
Click to expand...
Click to collapse
Yes, sorry, I left that part out.
Also read a lot about rooting marshmallow, it's not that simple as it was with Lollipop. You need a modified boot.img with either a custom kernel, or with modified sepolicies file, before you root it, otherwise it will just stop booting.
You could always use Nexus Root Toolkit. It worked for me no problem.
I wouldn't recommend. It still does not substitite for reading about it before rooting, and if you read enough that you know what it's doing, then you know enough to do it yourself.
Remember, rootkits only work until the next update for marshmallow, then you have to wait until it's developer updates it, otherwise it'll softbrick the phone, and you'll have to undo it.
People come here constanly asking what's wrong with MRA58R? Because the rootkit worked perfectly with MRA58K, and now it displays a red triangle and won't boot.
So if you search xda for red triangle, you'll find also solutions that will actually make rootkits obsolete.
Sent from my Nexus 6 running cyosp using Tapatalk
istperson said:
I wouldn't recommend. It still does not substitite for reading about it before rooting, and if you read enough that you know what it's doing, then you know enough to do it yourself.
Remember, rootkits only work until the next update for marshmallow, then you have to wait until it's developer updates it, otherwise it'll softbrick the phone, and you'll have to undo it.
People come here constanly asking what's wrong with MRA58R? Because the rootkit worked perfectly with MRA58K, and now it displays a red triangle and won't boot.
So if you search xda for red triangle, you'll find also solutions that will actually make rootkits obsolete.
Sent from my Nexus 6 running cyosp using Tapatalk
Click to expand...
Click to collapse
Toolkits are not recommended especialy for newbies, just learn a few simple adb/fastboot commands and stay in control all the way

Trying to root using NRT and getting errors

I am getting an error message of 'ADB recovery device not found'. Gone through all of the suggested steps and still getting the same error. Any help please?
'ADB recovery device not found'or just 'device not found'?
It sounds like a driver problem. What are "all the suggested steps"? Do you mean the walkthrough of setting up PC drivers?
But why use NRT for something as simple as root? Once you have your drivers properly installed, you can use ADB to reboot into TWRP recovery (either permanently or temporarily) and in TWRP install SuperSU v2.68. Simple.
dahawthorne said:
'ADB recovery device not found'or just 'device not found'?
It sounds like a driver problem. What are "all the suggested steps"? Do you mean the walkthrough of setting up PC drivers?
But why use NRT for something as simple as root? Once you have your drivers properly installed, you can use ADB to reboot into TWRP recovery (either permanently or temporarily) and in TWRP install SuperSU v2.68. Simple.
Click to expand...
Click to collapse
Been through the process of installing the drivers, followed it word for word twice. ADB recovery device not found is the message that comes up.
How do I use ADB? Do I have to install/download twrp and SuperSU?
Sent from my Nexus 6 using XDA Free mobile app
You can do nothing in NRT or manually until you resolve your driver problems. Have you enabled OEM unlock in Settings? Enable Developer options & USB debugging? Is your device unlocked? If it is, when you reboot the first screen will show a small unlocked padlock.
There's too little information to give any proper answers. Tell us what you've done since you took the device out of the box.
dahawthorne said:
You can do nothing in NRT or manually until you resolve your driver problems. Have you enabled OEM unlock in Settings? Enable Developer options & USB debugging? Is your device unlocked? If it is, when you reboot the first screen will show a small unlocked padlock.
There's too little information to give any proper answers. Tell us what you've done since you took the device out of the box.
Click to expand...
Click to collapse
I was previously rooted until last week. Unrooted to try and make my bank app work. OEM unlocked and USB debugging checked. Last time I rooted I used this process and worked fine.
Sent from my Nexus 6 using XDA Free mobile app
Same laptop/computer? No OS changes that might have disabled drivers?
Please just reply inline without repeating this answer - I've just written it, so I know what it says and I don't need to read it again. Same advice for all users unless there's a long and convoluted thread where the backward reference isn't clear - in simple straightforward threads like this one there's no value in copying the entire message that you're replying to...
It's a company laptop that had a policy installed recently that prevents exe files. That's all, only other difference is the phone is now on the February security update.
Sent from my Nexus 6 using XDA Free mobile app
If I installed NRT on my company laptop I'd be fired immediately and walked off the premises. I don't know how we can help you - if your laptop is locked down with company security policies then that's likely to be the reason.
So my only suggestion is - use another laptop.
They are cool with it.
I will ask for the recent policy to be removed and see if that fixes it. Appreciate your time, thanks.
Sent from my Nexus 6 using XDA Free mobile app

Categories

Resources