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
Related
hi all,
I have Nexus S i9023 from Vodafone Australia.
my Nexus S stuck at boot animation after i updated my phone with ICS 4.0.4.
I will explain why this happened before i write the solution.
- Originally i rooted my phone and unlocked the bootloader a while back, then Vodafone released the ICS OTA update, which i installed, worked perfect, recently they release another update of Jelly Bean 4.1, which again i accepted, but, this time phone started, i touched the first key and phone responded in a reboot. after a reboot, i unlocked the screen, another reboot and a continuous loop of reboots.
-i thought this is happening bcoz of unlocked bootloader and superuser app sitting in the system. i followed up many forums to UNROOT, which i could not understand, finally i used "1 Click unroot for Nexus S 4G", obviously i knew that this is not for my nexus. but still i used it. it worked.
- later i updated with ICS OTA update, then Nexus S stuck at boot animation for one full day.
Now below are all actions i took to fix the problem.
- Installed PDANET drivers for this device
- Installed Java SE 32bit
- Installed SDK for Android which detects 32bit Java, and within SDK i installed android platform and google drivers.
- Copied and Replaced all files from "platform-tools" (folder within Android SDK installation) to "tools" folder.
- Downloaded "recovery-clockwork-5.0.2.0-crespo" and copied this file into "tools" folder (a folder within Android SDK installation)
- Downloaded this zip file - android.clients.google.com/packages/ota/google_crespo/1ada25375426.signed-soju-ota-189904.1ada2537.zip
- Connected my Nexus S in fastboot mode and ran the following commands in cmd
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo
- then i went into clockwork recovery mod in my phone.
- i mounted my phone's USB SD card and copied the binary i downloaded as above.
- then i chose "install zip from SD card". Once installation finished. i ran the following command in cmd
fastboot oem lock
Now my phone is back to stock.
P.S. when my phone stuck at boot animation, i thought i bricked my phone. and spent a whole day searching for unbricking/resurrecting etc. But this symptom means NOT bricked yet.
below is the site for official binaries
sites.google.com/site/baroqueworksdevandroid/offcail-binary
I am a noob, so i thought this guide will help other noobs.
Thanks
I've seen something like that before, but different how it happen. I had stock NS4G with Gingerbread and had the ota update for ics come across so i did it. It did get stuck on the boot screen also and never would complete the boot. So i took it to an tech at sprint and they unlocked the phone and the did the update. Only to last a couple hours for another issues to come up with ICS. Whenever would click the home key on my phone it would keep opening up google earth, even after factory resets.
Why don't you guys just run custom roms? They run smoother than stock and the boot loop things are easy solvable.
Sent from my Nexus S using xda app-developers app
kwibis said:
Why don't you guys just run custom roms? They run smoother than stock and the boot loop things are easy solvable.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
They might not want to run custom Roms. I don't but some people might prefer the"Stock" experience.
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.
I have two Nexus 4s. Both were running 4.2.2, rooted, with custom recovery and the Franco Kernel. On a Mac, using the command line, I flashed stock recovery and the stock kernel in preparation for taking the 4.3 OTA.
First, on the newer N4, which has far less thing loaded on it and doesn't have a SIM card...
I tried to install the OTA letting the device/OS do it via the prompt after it was downloaded. But though it tried to start the process, it failed.
So I tried to install the full OS using the command line on a Mac following efrant's instructions in http://forum.xda-developers.com/showthread.php?t=2010312. Fastboot commands have always worked there, but I've never been able to execute adb.
Code:
./fastboot-mac flash system system.img
This is something I've done successfully before. But not this time. I flashed recovery and the radio, but when I tried to flash the system, I got an error message (usb_write failed with status e00002be or something about a partition not existing). So I took the phone to a Windows machine and used Wugfresh's tool. I couldn't successfully set up the drivers, but fastboot worked. So I did the return to stock and root thing. And it worked, getting me back to 4.2.2 in an out of the box state. I ran the OTA right away and easily got to 4.3.
Then, since I was already on the Windows machine, I used Wug's tool to try and root. No success. I can't seem to install custom recovery, either temporarily or permanently. I don't get an error message, but I can't boot into it, either. I just get the dreaded lying down Android icon with the red exclamation point.
Any ideas why I couldn't install system.img on the Mac command line? And why can't I get custom recovery? And what I can do to get it right?
Now, the older N4, which is my main phone. I have a current Titanium Backup, but not a Nandroid, at least not a current one. I haven't tried, yet, to update it to 4.3. But as mentioned, I did try to go back to the stock kernel and recovery in preparation. The problem there is that I also get the lying down Android instead of stock recovery and even worse, occasionally slow and laggy performance, which I hadn't had to begin with. Otherwise, it's 4.2.2 with that radio and kernel.
Any thoughts or help on this would be much appreciated.
I'm still hoping someone can offer me some sort of insight on this.
Dev Options and USB Debugging have been enabled on these N4s. I also want to say that I'm not trying to do anything I haven't done a bunch of times before both with NRT and from the command line with N4s and N7s. But I'm stuck in ways I haven't been before and I don't understand why or what to do about it.
I dont know exactly what you mean but the android laying down is the stock recovery.
Sent from my Nexus 4 using xda app-developers app
Hmm. I thought there was another, simple, volume key driven recovery interface from prior experience with this. I'm probably confusing a non-touch version of CM Recovery. Thanks for clarifying.
I finally got drivers working on the Windows 8 machine (the Universal Naked Driver that I found here at XDA). I was able to use the command line through NRT to get custom recovery onto the first of the N4s I described. I couldn't do that on the Mac via the command line or through the NRT interface before that. It just didn't work. Once that was in place, rerooting was easy. But it was a long road to get there with obstacles I hadn't encountered on earlier rooting and updating adventures.
I haven't tried to update my daily driver, yet. I may wait until things stabilize more with 4.3 and the various ROMs. Since I may have little choice other than to start over, I might do something other than the stock ROM.
One thing I've discovered is that running a more recent version of fastboot and adb helps. I can do some things on the Mac from the command line that I couldn't do with versions a few month older. (April, 2012 vs. November, 2012).
I still can't successfully run the OTA on one of my N4s, though. Maybe I need to unroot first, though I never have before.
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
Preamble
As a crotchety old man, my eye twitches and my back hurts every time I read a guide with superfluous steps, a root toolkit or an autoroot script for a nexus device. So, at the request of @thejmannnc, here's my simple root guide for Nexus 7 2013 LTE (deb).
NOTE: this will work just as well for the WiFi only version (flo), so long as you download the specific custom recovery for your device.
If your bootloader is locked (e.g. if this is your first time rooting this device)YOU WILL LOSE ALL YOUR DATA. There is no way around this.
Prerequisites
NOTE: I'm not writing a guide for these prerequisites
Prerequisite 1: "Fastboot" on a machine running a desktop operating system
Fastboot is one of the platform tools you can get from the android software development kit (SDK). You will need to install it. You can install the complete SDK, the platform tools, the two most basic platform tools (fastboot and adb), or, in theory, just fastboot.
*If you want to use adb as well, you will need to enable developer options and USB debugging on your N7. See the end of this post.
The SDK from Google:
http://developer.android.com/sdk/index.html
An XDA created tool for adb and fastboot. I haven't used it, but I'm told it works:
http://forum.xda-developers.com/showthread.php?p=42407269
A guide for installing the SDK for Windows 7:
http://forum.xda-developers.com/showthread.php?t=1830108
A guide for installing the SDK for Mac OS X:
http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/
Prerequisite 2: IF you use a Windows machine, USB DRIVER
Driver from Google. Note, the Google driver may not work for Windows 8:
http://developer.android.com/sdk/win-usb.html
If that doesn't work for you, try this driver:
https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Prerequisite 3: A custom recovery .img file
Download a custom recovery .img file to your computer (or any machine with a USB port that runs a desktop operating system). Place the file in the same directory (folder) that houses fastboot. I recommend TWRP custom recovery.
TWRP for deb (LTE):
http://techerrata.com/browse/twrp2/deb
TWRP for flo (WiFi only):
http://techerrata.com/browse/twrp2/flo
THE ACTUAL GUIDE
Step 1: Unlock your bootloader
Power down your Nexus 7. Once you've totally powered down, hold down the power and volume down key on your nexus 7.
Plug your Nexus 7 into your computer.
Open a command prompt (Windows) or Terminal window (Mac OS X, Linux) in the directory that houses fastboot (or navigate to that directory using the command cd, or, if you've properly set up your platform tools in Mac OS X, don't pay any attention to the directory).
Type the following command (this is the step that wipes your device.):
Code:
fastbot oem unlock
Follow the prompts. Then reboot your Nexus 7 by pressing the power button when the menus says "START". During the reboot your N7 will go through a factory reset.
Step 2: Download the superuser binaries:
On your Nexus 7, download from this link:
http://download.chainfire.eu/
Step 3: Install TWRP and superuser binaries
Reboot into bootloader as you did for step 1:
Power down your Nexus 7. Once you've totally powered down, hold down the power and volume down key on your nexus 7.
Plug your Nexus 7 into your computer.
Open a command prompt (Windows) or Terminal window (Mac OS X, Linux) in the directory that houses fastboot (or navigate to that directory using the command cd, or, if you've properly set up your platform tools in Mac OS X, don't pay any attention to the directory).
Type the following command:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-deb.img
If you downloaded a different version (or the recovery for flo), replace "openrecovery-twrp-2.6.3.1-deb.img" with the file name for the image you downloaded.
Once you've flashed recovery, you should still be in the bootloader. Use the volume keys to navigate to "Recovery mode". (Hint, it's two taps of the volume down button. Press the power button to reboot into recovery mode.
Once recovery reboots, you'll see a menu with 8 buttons in a 4x2 grid. Tap "Install".
Navigate to your Download directory, where you'll find the file "UPDATE-SuperSU-v1.75.zip" (or whatever version was current when you downloaded it). Tap that file.
Swipe to confirm flash.
Once the superuser binaries have installed, tap the "Reboot System" button.
Congratulations! You're now rooted.
Epilogue:
If you want to use the android debug bridge (adb) you'll need to enable developer options and usb debugging.
Under settings, about tablet, tap build number 7 times to enable developer options, back out to settings, developer options, check USB debugging
You are the Man!! Thank you for taking the time to help me make this process so easy on me. You have definitely simplified the process. There's not alot of people in this world that would take their time and knowledge to help out a stranger. Not many people out there left like you! Im sure this will also help out countless others out there like me as well.
Cant say thanks enough,
Jimmy aka thejmannnc
thejmannnc said:
You are the Man!! Thank you for taking the time to help me make this process so easy on me. You have definitely simplified the process. There's not alot of people in this world that would take their time and knowledge to help out a stranger. Not many people out there left like you! Im sure this will also help out countless others out there like me as well.
Cant say thanks enough,
Jimmy aka thejmannnc
Click to expand...
Click to collapse
Your welcome. Please let me know if you have any trouble.
Sent from my Nexus 6 using Tapatalk 4
I had done the step above, however I am in boot loop now. I can not seem to get out of it.
I had tried to Factory Reset within TeamWin Recovery, however it is giving me a failed message.
Please help
---------- Post added at 12:06 AM ---------- Previous post was at 12:06 AM ----------
I had done the step above, however I am in boot loop now. I can not seem to get out of it.
I had tried to Factory Reset within TeamWin Recovery, however it is giving me a failed message.
Please help
xdhall said:
Your welcome. Please let me know if you have any trouble.
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
Hello,, I just got the nexus 7 and it immediately wamts to update to 4.4. Should I let it? Didnt know if this would affect using the guide you created. I wont touch anythimg until I hear from you to be on the safe side.
Thanks,
thejmannnc
cs378 said:
I had done the step above, however I am in boot loop now. I can not seem to get out of it.
I had tried to Factory Reset within TeamWin Recovery, however it is giving me a failed message.
Please help
---------- Post added at 12:06 AM ---------- Previous post was at 12:06 AM ----------
I had done the step above, however I am in boot loop now. I can not seem to get out of it.
I had tried to Factory Reset within TeamWin Recovery, however it is giving me a failed message.
Please help
Click to expand...
Click to collapse
To recover from bootloop, turn off your device, let it sit for a couple of minutes, reboot into recovery and wipe cache/dalvik cache.
If this doesn't work, verify that you downloaded the correct TWRP image for your device. (Deb = LTE, flo = Wi-Fi only).
Sent from my Nexus 6 using Tapatalk 4
thejmannnc said:
Hello,, I just got the nexus 7 and it immediately wamts to update to 4.4. Should I let it? Didnt know if this would affect using the guide you created. I wont touch anythimg until I hear from you to be on the safe side.
Thanks,
thejmannnc
Click to expand...
Click to collapse
Yes. Update to 4.4. It won't impact the guide.
Sent from my Nexus 6 using Tapatalk 4
xdhall said:
Yes. Update to 4.4. It won't impact the guide.
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
Ok. Thanks for getting back to me so quickly, would have been just my luck!!
xdhall said:
Yes. Update to 4.4. It won't impact the guide.
Sent from my Nexus 6 using Tapatalk 4[/QUOT
For some reason I am having trouble installing the driver. Downloaded, extracted, now stuck. Maybe im just tired and stressed but never had trouble with drivers before. Well at least the tablet was delivered today! Am I missing something simp
e?
Click to expand...
Click to collapse
thejmannnc said:
xdhall said:
Yes. Update to 4.4. It won't impact the guide.
Sent from my Nexus 6 using Tapatalk 4[/QUOT
For some reason I am having trouble installing the driver. Downloaded, extracted, now stuck. Maybe im just tired and stressed but never had trouble with drivers before. Well at least the tablet was delivered today! Am I missing something simp
e?
Click to expand...
Click to collapse
You don't need to enable USB debugging to root with fastboot, but it's possible that you need to in order to install the drivers. I don't use a Windows machine, so I don't have specific knowledge of the driver installation procedure. Enabling USB debugging is described in the guide epilogue. If that doesn't work, you'll have to ask someone with more experience on a Windows machine (or find a machine running a Linux based OS like Mac OS X or Ubuntu--they don't need drivers). Wish I could be more help.
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
xdhall said:
thejmannnc said:
You don't need to enable USB debugging to root with fastboot, but it's possible that you need to in order to install the drivers. I don't use a Windows machine, so I don't have specific knowledge of the driver installation procedure. Enabling USB debugging is described in the guide epilogue. If that doesn't work, you'll have to ask someone with more experience on a Windows machine (or find a machine running a Linux based OS like Mac OS X or Ubuntu--they don't need drivers). Wish I could be more help.
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
Got it all taken care of! Time to relax!!! Thanks for all your help!! If your ever in NC look me up and ill buy you a beer!!
Have a good one!
Thejmannnc
Click to expand...
Click to collapse
Thank you for such a easy to do guide. Android amateur is now rooted and ready to install custom ROM onto his 2013 LTE
I did the Mac part of guide. No problems.