I received a nexus 7 from a family member that has a X on it. I downloaded Nexus 7 Toolkit 4.0.0 and tried the stock reflash and all (option 9?) and it finally seemed to complete correctly after randomly closing a few times but now it's still stuck on the X.
How do I know my build to make sure I am selecting the right image? I just googled my baseband and the version 4.1.2 popped upbeside it in searches so I went with that.
It seems like I can't get the most recent update to the toolkit unless I pay for it, but I only planned on using it once and don't even know if that would solve my problem. If i knew for sure it would, sure I would purchase it. Any idea what I might be doing wrong?
Thanks
kmad86 said:
I received a nexus 7 from a family member that has a X on it. I downloaded Nexus 7 Toolkit 4.0.0 and tried the stock reflash and all (option 9?) and it finally seemed to complete correctly after randomly closing a few times but now it's still stuck on the X.
How do I know my build to make sure I am selecting the right image? I just googled my baseband and the version 4.1.2 popped upbeside it in searches so I went with that.
It seems like I can't get the most recent update to the toolkit unless I pay for it, but I only planned on using it once and don't even know if that would solve my problem. If i knew for sure it would, sure I would purchase it. Any idea what I might be doing wrong?
Thanks
Click to expand...
Click to collapse
I know this may seem kinda silly, but I had a really similar problem and I solved it by going into Recovery and wiping everything, then I was able to flash another ROM from too manager.
MarioES said:
I know this may seem kinda silly, but I had a really similar problem and I solved it by going into Recovery and wiping everything, then I was able to flash another ROM from too manager.
Click to expand...
Click to collapse
Yeah, that was the first thing I tried.
kmad86 said:
Yeah, that was the first thing I tried.
Click to expand...
Click to collapse
If that didn't work I'm afraid a manual flash is your only option, don't think any toolkits will work.
http://forum.xda-developers.com/showthread.php?t=1781250
Check that out, pretty straightforward and should do the trick.
MarioES said:
If that didn't work I'm afraid a manual flash is your only option, don't think any toolkits will work.
http://forum.xda-developers.com/showthread.php?t=1781250
Check that out, pretty straightforward and should do the trick.
Click to expand...
Click to collapse
I'm a rook when it comes to the command stuff. Some quick questions and I think I can be on my way.
1. How do I open a command prompt to my ADB and Fastboot directory? I have no idea what that means. Do I make a folder on my desktop titled Nexus 7, and inside that put something?
2. I can't boot into Android so what do I do when it says "if you're booted into Android" do I just put it in fastboot and say good?
(The last command prompt stuff I did was in 2002 for my computer using Windows XP it's been a while. Kinda rusty)
I appreciate the help guys, I'm learning! I guess I could send it in, but I like the learning experience and challenge.
kmad86 said:
I'm a rook when it comes to the command stuff. Some quick questions and I think I can be on my way.
1. How do I open a command prompt to my ADB and Fastboot directory? I have no idea what that means. Do I make a folder on my desktop titled Nexus 7, and inside that put something?
2. I can't boot into Android so what do I do when it says "if you're booted into Android" do I just put it in fastboot and say good?
(The last command prompt stuff I did was in 2002 for my computer using Windows XP it's been a while. Kinda rusty)
I appreciate the help guys, I'm learning! I guess I could send it in, but I like the learning experience and challenge.
Click to expand...
Click to collapse
You need to download the Android SDK for that so you can have the fastboot program. Download and install that first then you can proceed to flashing a rom using the fastboot command.
kmad86 said:
I'm a rook when it comes to the command stuff. Some quick questions and I think I can be on my way.
1. How do I open a command prompt to my ADB and Fastboot directory? I have no idea what that means. Do I make a folder on my desktop titled Nexus 7, and inside that put something?
2. I can't boot into Android so what do I do when it says "if you're booted into Android" do I just put it in fastboot and say good?
(The last command prompt stuff I did was in 2002 for my computer using Windows XP it's been a while. Kinda rusty)
I appreciate the help guys, I'm learning! I guess I could send it in, but I like the learning experience and challenge.
Click to expand...
Click to collapse
I'm not very good at this stuff either, and a manual flash was the first thing I tried. You'll get it!
If you can't boot into Android skip step 3 and go to 4, which is the same (just that you're loaded into the bootloader, which you should be able to access).
About the other issue, google it and look for a londatiga.net link (can't post links as a new user). All you need is the Android SDK
MarioES said:
I'm not very good at this stuff either, and a manual flash was the first thing I tried. You'll get it!
If you can't boot into Android skip step 3 and go to 4, which is the same (just that you're loaded into the bootloader, which you should be able to access).
About the other issue, google it and look for a londatiga.net link (can't post links as a new user). All you need is the Android SDK
Click to expand...
Click to collapse
I found FastBoot in the Platform-Tools folder, but I double click it and a command prompt looking screen pops up, but disappears.
EDIT: Got it.
Thanks for the help
Ok, so I figured out the command prompt.
For those of you searching for this, and in the same situation as I, I clicked on Start>and searched Command where my command prompt popped up as C:\users\admin> and i was really confused. From there my Toolkit was in Desktop>Nexus 7 Stuff>Toolkit>ADT Bundle>SDK>Platform-Tools.
I typed in command prompt "cd desktop" and enter. Then I was at C:\users\admin\desktop> From there I entered "cd nexus 7 stuff" and enter. and on to toolkit, then the next until I was at platform tools. Then I followed the instructions and whala!
(Now I am stuck on writing "boot") i've searched and found nothing.
Related
I need help, I got the Nexus (sprint) and have tried and tried to unlock. I had fits, read many forums, and was directoed to an unlocker forum. I used Superboot GR140. I had downloaded su 2.3.6.1 to my phone.
Using this method, it unlocked but now I am stuck. I cannot get anything else to load.
I'm not sure if I used an incorrect Superboot method (meaning for a different phone since the forums aren't split).
I have access to Fastboot Mode Screen, phone is recognized, but when using cmd, it shows C:\Superboot. I do not know what else to do to direct it to files I have on my computer or how to download these, 2.3.4 back to my phone. I'm stuck and really need help.
I will gladly push the Thanks button for any help I can get to get me up and
running again.
Thanks
Go look in the developer section, one of the stickies, the one that talks about the nexus s 4g cdma. You might have flashed something that was meant for the gsm nexus s. It has links to correct files and guides for the sprint version of the nexus.
Pm me and I will help u over the I'm client of your choice.
Basically, I have no service, and no card, so since I can access Fastboot Mode, and unlocked, is there a way to push a rom direct onto Sprint phone.
I looked in Developers Forums, I am not ready to jump in with custom rom yet (I have used extensively on other phones) but would like to start with stock, go with root and programs as needed.
So how would I push to phone via computer? and what programs, again, no idea of commands to use.
Have you flashed CWM yet? You can use that to reflash the stock ROM. Worst case you can use this thread:
http://forum.xda-developers.com/showthread.php?t=1072698
That will bring you to 100% out of the box factory settings
If you can get into fastboot, then you didn't brick it. You'll be fine, you just need to get in touch with someone that can walk you through the process of fixing it. Or search around, read, and take your time to figure out what to do.
It's not hard. The worse thing you can do is panic or rush to fix it.
Basically what you did when using superboot was you actually installed a boot.img file not meant for your device on your phone. What you should do is, go through the guide for your specific phone...you will have to install a recovery image and then install a custom rom or stock rom.
I do not know if you know your way around with fastboot....basically you could also ask a dev to send you the original boot.img and flash it using fastboot but the first stepi described is easier.
Sent from my Nexus S using Tapatalk
nmoreman said:
I need help, I got the Nexus (sprint) and have tried and tried to unlock. I had fits, read many forums, and was directoed to an unlocker forum. I used Superboot GR140. I had downloaded su 2.3.6.1 to my phone.
Using this method, it unlocked but now I am stuck. I cannot get anything else to load.
I'm not sure if I used an incorrect Superboot method (meaning for a different phone since the forums aren't split).
I have access to Fastboot Mode Screen, phone is recognized, but when using cmd, it shows C:\Superboot. I do not know what else to do to direct it to files I have on my computer or how to download these, 2.3.4 back to my phone. I'm stuck and really need help.
I will gladly push the Thanks button for any help I can get to get me up and
running again.
Thanks
Click to expand...
Click to collapse
If you are going to waste your brand new phone by being stupid how about giving it to me instead! Ill take good care of it.
Sent from my PC36100 using XDA App
Here Try this and let me know if it work:
1.Download this platform-tools.zip and extract it to your desktop
2.Connect your phone to the PC and enter bootloader mode
3.Press and hold Shift while right-clicking the folder you extracted 'platform-tools'
4.Click 'Open command window here' from the pop-up menu. cmd.exe window will open.
5.If the Bootloader is Unlocked continue to the next step. Type in the cmd.exe window 'Fastboot oem unlock' and follow the steps on the phone screen.
6.Type in the cmd.exe window 'fastboot flash boot boot.img'.
7.Type in the cmd.exe window 'fastboot reboot'.
nmoreman said:
I need help, I got the Nexus (sprint) and have tried and tried to unlock. I had fits, read many forums, and was directoed to an unlocker forum. I used Superboot GR140. I had downloaded su 2.3.6.1 to my phone.
Using this method, it unlocked but now I am stuck. I cannot get anything else to load.
I'm not sure if I used an incorrect Superboot method (meaning for a different phone since the forums aren't split).
I have access to Fastboot Mode Screen, phone is recognized, but when using cmd, it shows C:\Superboot. I do not know what else to do to direct it to files I have on my computer or how to download these, 2.3.4 back to my phone. I'm stuck and really need help.
I will gladly push the Thanks button for any help I can get to get me up and
running again.
Thanks
Click to expand...
Click to collapse
THANK YOU, for answer, but it didn't work.
I downloaded, opened, opened cmd from there.
My phone is unlocked, setting there with unlock screen, put it in bootloader mode, but when I type in instructions, it comes back "not recognized as internal, external command, program, batch file"
This is the problem I had when trying to unlock, so reading, used Superboot, probably wrong phone, so now it is wiped and empty.
I also read another thread suggesting Odin in this situation. Have downloaded that, SamsungSimpleDL, followed those directions, that doesn't work either. I have hacked and rommed Epic, very familiar with that, if it works, but cannot point to proper files (pda, pit, or bootloader).
So any other ideas, I am very good at directions, that is how I learned
My Phone is Fixed - YEAH
This did not work, but this link did
http://forum.xda-developers.com/showthread.php?t=1072698&page=4
Basically used Odin (my old backup from Samsung Epic) and it worked when all these suggestions wouldn't.
I couldn't unlock easily, like all of these, therefore used Superboot. Would recommend no one touches that!!
I couldn't run any of the commands before this, and still couldn't use these.
So the instructions to dig thru the Developers section is correct, but so hard with so many customs, phones, carriers, to choose from. Makes it difficult
So use this link if stuck like me, I am just glad I con't have a brick, and I'm still pushing the Thanks button for all who helped, that's what will make this fun.
so long story short, i wiped all my data to flash a rom and forgot i hadnt re downloaded the zip and accidentlly hit reboot now and now i am stuck on the GOOGLE screen....ive tried reflashing the stock rom through the tool kit but all it keeps saying is waiting for adb...what do i do??? please help asap, thank you!
Try using wugs root tool to revert to stock. There is an option you need to check in that program which says that your tablet cannot boot up.
EDIT:
WugFresh said:
IF THE PROGRAM IS STALLING ON YOU (FOR ADB CHECK):
Restart the toolkit
On the main interface hit the "Launch" button to open Advanced utilities
In the advanced utilities interface; hit the "Launch CMD Prompt" button
Type the following cmd
Code:
adb start-server
Now you should be able to use any of the utilities in the toolkit without it stalling.
This extra step is just a temporary solution, until I release v1.5.3; then this won't be necessary.
Click to expand...
Click to collapse
Why does this not STOP, Your using the wrong section..
Also to fix the adb thing it says it in the original OP
Reboot into bootloader mods, hold power until it turns off, then hold power+volume down
Now go into toolkit and go to advance and click launch cmd, then type "adb start-server"
exit out of cmd and restore stock, make sure it says device is not on.
Some people just dont know how to read. SMH
im using the nexus 7 tool kit v 1.1.0 ....i opened..open manual command or whatever and typed what you said and it told me adb is not recognized as an internal or external command, operable program or batch file....omg, im screwed arent i ???? ....can u please guide me through this step by step...i havent had this thing 3 days already and its completely froze
it will not shut off!!! i hit all the buttons you have said and it just reboots to the google screen everytime....im lost!
blueizee said:
im using the nexus 7 tool kit v 1.1.0 ....i opened..open manual command or whatever and typed what you said and it told me adb is not recognized as an internal or external command, operable program or batch file....omg, im screwed arent i ???? ....can u please guide me through this step by step...i havent had this thing 3 days already and its completely froze
Click to expand...
Click to collapse
Did you open it up within the wugs toolkit? You need to open it up through the program, not through windows..
It honestly isn't hard. To be perfectly honest, if you can't figure out how to use a toolkit, or adb for that matter, you shouldn't be flashing roms.
P.S. You are far from bricked..
In the first place this does not belong here.
What the dude said, if you don't know what android sdk or java jde is dont flash roms
Install those two programs i mentioned reboot computer, now type that in.
Wow again??? This has to stop lol seriously
Everyday Thiers 2-3 post in the wrong section
Please pay attention ppl
Sent from my Nexus 7 using xda premium
listen big mouths...i made a simple mistake if you read my OP, i accidentlly hit reboot my tablet when i shouldnt have (first time mistake)...not on purpose, ok...and i apologize for posting here, i meant to go in Q&A but i panicked and didnt realize i was still in development...i know how to flash roms...im no genius but i know the basics and never bricked any of my android devices before, so i would appreciate you guys stop jumping to conclusions and give me a helping hand...thats what this site is for isnt it ? not smartass's. THANK YOU!
blueizee said:
listen big mouths...i made a simple mistake if you read my OP, i accidentlly hit reboot my tablet when i shouldnt have (first time mistake)...not on purpose, ok...and i apologize for posting here, i meant to go in Q&A but i panicked and didnt realize i was still in development...i know how to flash roms...im no genius but i know the basics and never bricked any of my android devices before, so i would appreciate you guys stop jumping to conclusions and give me a helping hand...thats what this site is for isnt it ? not smartass's. THANK YOU!
Click to expand...
Click to collapse
This isn't tech support
Sent from my SGH-I727 using xda premium
If what was posted above doesn't work
Hold power till it turns off
Hold power and vol down to boot into bootloader
Pulled straight from Google, a little searching goes a long way
On your PC, copy CWM-grouper-recovery.img into the same the folder where fastboot.exe is located. You can find fastboot.exe in the platform-tools directory inside the Android SDK folder.
Open a command terminal and navigate it to where fastboot.exe is located. Type this command and press Enter:
fastboot flash recovery CWM-grouper-recovery.img
After a successful flash, type this command:
fastboot reboot-bootloader
Select Recovery from the bootloader menu on your tablet to boot it into Recovery Mode.
Click to expand...
Click to collapse
You will probably have to do everything manually and push the new or stock rom if you don't know how to do that, you got a lot to read.
This is why tool kits are bad. If you had adb and knew a few basics this thread wouldn't exist.
Sent from my SCH-I535 using Tapatalk 2
BaconStep said:
This isn't tech support
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
Sure seems like I saw people trying to help you out with some storage issues you were having in the Glazed thread. I don't have anything to help the OP, but I felt like calling out a hypocrite.
Semantics said:
Sure seems like I saw people trying to help you out with some storage issues you were having in the Glazed thread. I don't have anything to help the OP, but I felt like calling out a hypocrite.
Click to expand...
Click to collapse
Lol
Sent from my SGH-I727 using xda premium
Learn to use fastboot and flash factory images. Read the guide. Read it again. Fix your device.
/ end thread
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.
My Rom version is 4.2.2. And I have upgraded the toolkit to v4.3.9, the latest one.
I was able to unlock the bootloader. However, I couldn't root my Nexus 7.
Nexus 7 gets stuck at "booting the downloaded image", while the toolkit was showing "Waiting for adb Mode".
Luckily, the Nexus 7 wasn't bricked though. I was able to boot into the official image, by holding the power button for a long time.
I tried many times with different options in the Toolkit. Still got no luck. Many suggestions are welcome. Thanks.
Dont waste any more time with toolkits. take 5 minutes to learn how to do it manually
Pirateghost said:
Dont waste any more time with toolkits. take 5 minutes to learn how to do it manually
Click to expand...
Click to collapse
@Pirateghost, is there any good guide for this? Most of google search results point to this toolkit.
It is working now. I had to run Windows on the bare metal of my macbook. It won't work when Windows is running within a virtual machine.
ejj3 said:
@Pirateghost, is there any good guide for this? Most of google search results point to this toolkit.
It is working now. I had to run Windows on the bare metal of my macbook. It won't work when Windows is running within a virtual machine.
Click to expand...
Click to collapse
Now that your N7 is already unlocked, all you need is a recovery... Download this: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.1-grouper.img
Also make sure that you have the android sdk installed. It's easy enough to find.
Open the platform-tools folder, hold shift and right click; then choose "open command window here"
Make sure that your N7 is rebooted into the bootloader and run the command "fastboot flash recovery recoveryname.img" replacing recoveryname with the name of the recovery.
After that, follow the instructions to flash any custom rom or supersu from recovery... I'm sure that there are more detailed instructions elsewhere, but that's all you really need at the moment...
ejj3 said:
@Pirateghost, is there any good guide for this? Most of google search results point to this toolkit.
It is working now. I had to run Windows on the bare metal of my macbook. It won't work when Windows is running within a virtual machine.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?t=2150661
And you DONT need windows to use fast boot or adb
Sent from my Galaxy Nexus
So i decided a few days ago to try and flash a factory image for kitkat on my N7. But i downloaded the image for the wrong device. the script has wiped recovery and system etc. The N7 now just boots to bootloader.
i got the proper factory image to flash, but i cannot get the device recognized on the pc running Windows 7 now. its showing as Other Devices / Android. I did install the drivers from the SDK and it now appears as Android ADB Interface. However ADB is still not recognizing it. I have done adb devices but nothing is found.
Any help, it is fixable isnt it??
You can't use adb commands in fastboot. You should use fastboot commands and flash the factory image
Sent from my Nexus 5
Tones1971 said:
So i decided a few days ago to try and flash a factory image for kitkat on my N7. But i downloaded the image for the wrong device. the script has wiped recovery and system etc. The N7 now just boots to bootloader.
i got the proper factory image to flash, but i cannot get the device recognized on the pc running Windows 7 now. its showing as Other Devices / Android. I did install the drivers from the SDK and it now appears as Android ADB Interface. However ADB is still not recognizing it. I have done adb devices but nothing is found.
Any help, it is fixable isnt it??
Click to expand...
Click to collapse
Well, I had a serious issue with something similar, after trying to update (not flash the factory image) to KitKat it produced an error and now it's bootlooping and, worse, my computer won't recognize the device, so I can't flash the factory image whatsoever. Your problem is much more light, as your computer is actually recognizing the device. What I'd suggest is using the Nexus Root Toolkit by WugFresh. Yes, I know, a lot of people here don't like using it but it's extremely useful when you have drivers issues.
It's actually a pretty straight forward procedure, you install the toolkit and it will ask you for your device model, android version, etc., then take you through the process of updates and stuff. Then, on the main window, you have this wizard "Full Driver Installation Guide" that will give you 4 ways to get your device working. You can find the Toolkit here: http://www.wugfresh.com/nrt/. Good luck!
I vote we ban all talk of toolkits. 99.9% of the help threads around here start with, "I was using/used x toolkit and now my device won't boot."
What happened to people learning about their devices?
How about learning how to fix your problems, rather than compound them by not understanding what you are doing? How about if you don't have the capacity to learn it, you leave it the F alone?
Sent from my Nexus 5
Pirateghost said:
I vote we ban all talk of toolkits. 99.9% of the help threads around here start with, "I was using/used x toolkit and now my device won't boot."
What happened to people learning about their devices?
How about learning how to fix your problems, rather than compound them by not understanding what you are doing? How about if you don't have the capacity to learn it, you leave it the F alone?
Sent from my Nexus 5
Click to expand...
Click to collapse
It's also difficult when trying to assist somebody... they're using the vocabulary of toolkits (which I'm not familiar with)... and I'm going on about fastboot... which they don't understand. It's like there are now two different languages... TOOLKIT and FASTBOOT.
Makes it very difficult to assist people.
Maybe I should have a tinker with Wugfresh... if for no other reason than to at least get an insight into how these things work.
Rgrds,
Ged.
The concept of the toolkit is great. It's the implementation and use of it that is horrible.
I think a toolkit should walk you through the actual steps and force you to type in the commands. You select an option of what you want it to do, it tells you what to type step by step to achieve said goal, and checks that you don't type in the wrong thing for the option you selected.
Unfortunately I don't think there is a market for that when you can get everything 'one clicked' for you.
Sent from my Nexus 5
Pirateghost said:
The concept of the toolkit is great. It's the implementation and use of it that is horrible.
I think a toolkit should walk you through the actual steps and force you to type in the commands. You select an option of what you want it to do, it tells you what to type step by step to achieve said goal, and checks that you don't type in the wrong thing for the option you selected.
Unfortunately I don't think there is a market for that when you can get everything 'one clicked' for you.
Sent from my Nexus 5
Click to expand...
Click to collapse
So an edit box where you could be prompted to type in things like fastboot flash recovery recovery.img... interesting idea... sort of walks you through the process, but doesn't obsessively hold your hand, where you don't learn anything.
I suspect most people just have problems with drivers, because, let's face it, fastboot and ADB aren't exactly difficult to use... unless people have difficulty understanding command lines in these GUI driven days, where everything is a simple menu or button click away... kind of sad really.
Rgrds,
Ged.
GedBlake said:
So an edit box where you could be prompted to type in things like fastboot flash recovery recovery.img... interesting idea... sort of walks you through the process, but doesn't obsessively hold your hand, where you don't learn anything.
I suspect most people just have problems with drivers, because, let's face it, fastboot and ADB aren't exactly difficult to use... unless people have difficulty understanding command lines in these GUI driven days, where everything is a simple menu or button click away... kind of sad really.
Rgrds,
Ged.
Click to expand...
Click to collapse
Basically yeah.
I have a feeling a good portion of the hesitation comes from the command line being scary to most people.
Sent from my Nexus 5
In the tgz file you download there is a 'flash-all.bat' file that does everything for you. If you open it in notepad, you see exactly what it does and in what order.
Yes, drivers are probably the issue, they were for me at least. I ended up using NRT (wugs toolkit) to install drivers (and root later, but that's a new topic)
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jwr66y.zip
echo Press any key to exit...
pause >nul
exit
This is a Google way to flash the factory image.
---------- Post added at 10:02 PM ---------- Previous post was at 09:59 PM ----------
Pirateghost said:
The concept of the toolkit is great. It's the implementation and use of it that is horrible.
I think a toolkit should walk you through the actual steps and force you to type in the commands. You select an option of what you want it to do, it tells you what to type step by step to achieve said goal, and checks that you don't type in the wrong thing for the option you selected.
Unfortunately I don't think there is a market for that when you can get everything 'one clicked' for you.
Sent from my Nexus 5
Click to expand...
Click to collapse
The idea is great, try writing it
I'm sure it'll be greeted with appreciation.
Tones1971 said:
So i decided a few days ago to try and flash a factory image for kitkat on my N7. But i downloaded the image for the wrong device. the script has wiped recovery and system etc. The N7 now just boots to bootloader.
i got the proper factory image to flash, but i cannot get the device recognized on the pc running Windows 7 now. its showing as Other Devices / Android. I did install the drivers from the SDK and it now appears as Android ADB Interface. However ADB is still not recognizing it. I have done adb devices but nothing is found.
Any help, it is fixable isnt it??
Click to expand...
Click to collapse
As long as you can still boot into bootloader mode, it is still fixable. Try reinstalling fastboot drivers.
Pirateghost said:
I vote we ban all talk of toolkits. 99.9% of the help threads around here start with, "I was using/used x toolkit and now my device won't boot."
What happened to people learning about their devices?
How about learning how to fix your problems, rather than compound them by not understanding what you are doing? How about if you don't have the capacity to learn it, you leave it the F alone?
Sent from my Nexus 5
Click to expand...
Click to collapse
Yeah, because that was really helpful to him. I didn't tell him to use the toolkit to flash, root, unlock, or anything of the sort. For drivers issues, I do recommend (and will continue to do so) using the toolkit when official drivers don't work, because it has helped me a lot in the past, but I haven't used it to flash anything.
Download the image for your device and extract it into a folder
Download the zip below and move the files into the folder you created above
http://forum.xda-developers.com/showthread.php?t=1484407
Switch device off. Hold volume down and turn it back on, so it's in fastboot mode
Plug device into computer
Run "flash-all.bat" in the system image folder you extracted first
Want to thank everybody for their replies. Have had a family emergency so havent had a chance to try any suggestions, but didnt want to just ignore the thread i started.