Thread Closed

[TOOL] Nexus 7 (2013) All-In-One Toolkit v1.0 [7-30-2013] [PERM ROOT][Noob-Proof]

31st July 2013, 12:12 AM   |  #21  
Senior Member
Flag Chicago
Thanks Meter: 440
 
1,073 posts
Join Date:Joined: Aug 2012
More
Quote:
Originally Posted by jeffc83

Getting my N7 tomorrow. Will this work on Win8 64? Thanks in advance.

Sent from my SCH-I605 using xda app-developers app

Should, I've used his toolkit for my HTC One on Win8 x64.
The Following User Says Thank You to dark2099 For This Useful Post: [ View ]
31st July 2013, 03:08 AM   |  #22  
Member
Thanks Meter: 4
 
31 posts
Join Date:Joined: Nov 2010
Minor Snags (and the solutions to them)
First off, let me say thank you to the Dev. I appreciate the work you put into this, truly.

For those who are having problems or have additional questions, I will offer my advice.

Q: Do I used this Before or After the System Update?

A: I cannot speak for others, but I used this All-in-One tool Before installing the System Update that the Nexus automatically downloaded. (If someone else can chime in on this, it’d probably help some confused user.)

Q: The command prompt window/ADB window/Something says that the device is "Offline." What do I do?

A: Yeah, I ran into this and I was a bit baffled. It would seem that the “adb.exe” file, located within the “Tools” folder is outdated. Why others did not run into this I cannot say, but I doubt very much that I had a newer adb.exe sitting around on my system than is included here. Supposedly any version after 16 will suffice, but I used the adb.exe found in this package: http://dl.google.com/android/reposit....1-windows.zip

Once you unzip the folder, find adb.exe, and copy/paste the file into the Tools folder of this All-in-One. Now try running the All-in-One utility again.

If the device still registers as offline, try typing in the command prompt window

adb kill-server

After you hit enter, type:

adb devices

It will take a second for the daemon to boot up, but once it does you /should/ have be prompted on the Nexus 7 to approve debugging from the PC it is hooked up to. (I checked the little tic box that offers, “Always allow from this computer?”)

Once you hit Yes (Always allow), you should be good to follow on with the procedure.

Q: I did all this, I got into fastboot, and..nothing happened?!

A: I don’t remember exactly what this was about, but I rebooted into Android (use the volume buttons to scroll; do not freak out that the touch screen isn’t working; use the power button to select “Start”), closed down everything on my PC that related to the All-In-One utility, and started it again at the “Reboot into bootloader” step. From there on, all has been well.

Again, I hope this helps anyone else who runs into these issues. Thanks again to Hasoon2000 for making this newbie friendly from the start.

Kindly,
Newbie
The Following User Says Thank You to JustAnotherNewbie For This Useful Post: [ View ]
31st July 2013, 04:28 AM   |  #23  
akarol's Avatar
Senior Member
Flag Orlando
Thanks Meter: 251
 
2,008 posts
Join Date:Joined: Jun 2010
More
Quote:
Originally Posted by JustAnotherNewbie

First off, let me say thank you to the Dev. I appreciate the work you put into this, truly.

For those who are having problems or have additional questions, I will offer my advice.

Q: Do I used this Before or After the System Update?

A: I cannot speak for others, but I used this All-in-One tool Before installing the System Update that the Nexus automatically downloaded. (If someone else can chime in on this, it’d probably help some confused user.)

Q: The command prompt window/ADB window/Something says that the device is "Offline." What do I do?

A: Yeah, I ran into this and I was a bit baffled. It would seem that the “adb.exe” file, located within the “Tools” folder is outdated. Why others did not run into this I cannot say, but I doubt very much that I had a newer adb.exe sitting around on my system than is included here. Supposedly any version after 16 will suffice, but I used the adb.exe found in this package: http://dl.google.com/android/reposit....1-windows.zip

Once you unzip the folder, find adb.exe, and copy/paste the file into the Tools folder of this All-in-One. Now try running the All-in-One utility again.

If the device still registers as offline, try typing in the command prompt window

adb kill-server

After you hit enter, type:

adb devices

It will take a second for the daemon to boot up, but once it does you /should/ have be prompted on the Nexus 7 to approve debugging from the PC it is hooked up to. (I checked the little tic box that offers, “Always allow from this computer?”)

Once you hit Yes (Always allow), you should be good to follow on with the procedure.

Q: I did all this, I got into fastboot, and..nothing happened?!

A: I don’t remember exactly what this was about, but I rebooted into Android (use the volume buttons to scroll; do not freak out that the touch screen isn’t working; use the power button to select “Start”), closed down everything on my PC that related to the All-In-One utility, and started it again at the “Reboot into bootloader” step. From there on, all has been well.

Again, I hope this helps anyone else who runs into these issues. Thanks again to Hasoon2000 for making this newbie friendly from the start.

Kindly,
Newbie

Turns out the problem is not the device but with ADB itself. You must update to the latest ADB files in order for the RSA key prompt to come up. I finally got it to work after searching "Minimal ADB and Fastboot" on Google and downloading the latest files from the xda-developers thread that comes up. I believe the ADB files that are contained with this AIO Toolkit are not the latest one.

Hasoon2000, could you please update the ADB files to avoid people from having this issue in the future? If anyone needs the link to the latest ADB files, just click on the link below:

http://forum.xda-developers.com/show...php?p=42407269

---------- Post added at 11:28 PM ---------- Previous post was at 10:49 PM ----------

I would definitely add to the OP that a Factory Reset is necessary if not flashing a new ROM while rooting or you'll be stuck on boot.

Sent from my HTC One using Tapatalk 4 Beta
The Following User Says Thank You to akarol For This Useful Post: [ View ]
31st July 2013, 07:17 AM   |  #24  
hasoon2000's Avatar
OP Senior Member
Flag Orland Park, Illinois
Thanks Meter: 9,193
 
3,512 posts
Join Date:Joined: Feb 2008
Donate to Me
More
v1.0.1 Released! 7-31-2013
- Updated ADB/Fastboot so the toolkit should now work with the device.
- Added more info to the message box. If you don't flash a ROM, you MUST do a factory reset within the custom recovery, or else the device will be soft bricked!

Download is in Post 2.
31st July 2013, 09:08 AM   |  #25  
corythug's Avatar
Senior Member
Flag PA
Thanks Meter: 208
 
1,587 posts
Join Date:Joined: Aug 2011
More
Quote:
Originally Posted by hasoon2000

v1.0.1 Released! 7-31-2013
- Updated ADB/Fastboot so the toolkit should now work with the device.
- Added more info to the message box. If you don't flash a ROM, you MUST do a factory reset within the custom recovery, or else the device will be soft bricked!

Download is in Post 2.

That's why mine bricked! Lol. Sorry it was really messing with me trying to figure out what went borked.

Sent from my SGH-I747 using Tapatalk 2
31st July 2013, 03:41 PM   |  #26  
turdbogls's Avatar
Senior Member
Orlando
Thanks Meter: 240
 
654 posts
Join Date:Joined: Oct 2010
Donate to Me
OK, so I had the old download, replaced ADB with the latest one and everything went as planned. I really appreciate the hard work man. I could not, for the life of me, get my phone to communicate with ADB. never had problems before with other Nexii(nexus'?)
but this worked really good. unlocked, rooted, custom recovery. I am again comfortable with my android tablet (felt so lost on Stock/locked) lol
31st July 2013, 06:36 PM   |  #27  
Senior Member
Thanks Meter: 20
 
200 posts
Join Date:Joined: Jan 2011
Not that it matters a whole lot, but I get this error when trying to open any of the links..... Its something to do with my home computer because it works fine on my work computer.
Attached Thumbnails
Click image for larger version

Name:	Toolkit Error.jpg
Views:	356
Size:	224.6 KB
ID:	2155740  
31st July 2013, 07:21 PM   |  #28  
hasoon2000's Avatar
OP Senior Member
Flag Orland Park, Illinois
Thanks Meter: 9,193
 
3,512 posts
Join Date:Joined: Feb 2008
Donate to Me
More
Quote:
Originally Posted by corythug

That's why mine bricked! Lol. Sorry it was really messing with me trying to figure out what went borked.

Sent from my SGH-I747 using Tapatalk 2

Luckily, someone said to do a factory reset!

Quote:
Originally Posted by turdbogls

OK, so I had the old download, replaced ADB with the latest one and everything went as planned. I really appreciate the hard work man. I could not, for the life of me, get my phone to communicate with ADB. never had problems before with other Nexii(nexus'?)
but this worked really good. unlocked, rooted, custom recovery. I am again comfortable with my android tablet (felt so lost on Stock/locked) lol

Everything went good with the toolkit after you updated the ADB Files?

Quote:
Originally Posted by fstbusa

Not that it matters a whole lot, but I get this error when trying to open any of the links..... Its something to do with my home computer because it works fine on my work computer.

That's strange. Your default web browser should automatically open it.
31st July 2013, 07:25 PM   |  #29  
Senior Member
Thanks Meter: 20
 
200 posts
Join Date:Joined: Jan 2011
I fixed it by going into the program defaults and setting firefox as my default browser. Must have been some error/issue with my default browser.
31st July 2013, 09:37 PM   |  #30  
ruvy01's Avatar
Senior Member
Flag Wastefield, New England
Thanks Meter: 19
 
114 posts
Join Date:Joined: Oct 2010
More
ok so i flashed the recovery using this toolkit but when i boot to TWRP it asks me for a password? never had that happen before...

Thread Closed Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in Nexus 7 (2013) Android Development by ThreadRank