Database Develop

[Guide] Rooting the Nexus 7 - 4.2 (JOP40C)

Preparation:
Open your device manager(PC)
Control Panel -> Device Manager
Remove literally everything to do with Android/Electronics a.k.a
Nexus, Android, Nexus 7, Androids, HTC, HTCDrivers (you get the picture)
Next Step
Plug your Nexus in, CHANGE THE SETTINGS TO CAMERA(P2P) not MTP
Also ensure USB Debugging is checked.
Getting the required program:
Now, download the latest WugFresh toolkit.
Direct Download (Goo.IM)
Wugs Site
Once Downloaded:
Open ToolKit and Click "Full Installation Drivers with guide"
Choose the PDA.Net method.
Follow the Guide and let the drivers install, it should also install PDA.Net at the same time (on PC) which should appear in bottom right of screen (PC Screen)
When Drivers are Installed:
Once the drivers are installed, go to the ToolKit again, under "Build Type" choose "Nakasi All Build TYPES **"
Rooting:
Now, when your build type is set to all build types, proceed with "Root", follow instructions again and it should reboot into a "Temporary TWRP", this is great.
Flashing Necessary Root Files:
Navigate to SDCard, ReadyToFlash! and find BusyBox and SuperSU, flash them using TWRP.
Clear Cache
Reboot, VOILA!
IF IVE MISSED ANYTHING OR YOU'D LIKE TO SEE ANYTHING ADDED, LET ME KNOW AND I'LL GET IT DONE !!

This will work for all Android versions. The 4.2 specifics is getting the drivers installed to recognise the N7. (Also the CamperP2P not MTP)

I wanted to test but the download is too slow (2 hours).

Is the same procedure valid for Nexus 7 3g?
Thanks
Sent from my GT-I9100 using xda premium

I have a nexus 7 in 4.2 and I have been very successful in the root. However, it must accurately.
Disabled security options on the Control of Android applications and behavioral allow installation of application from memory, if the root does not work.
The interface of the application should be reviewed at ergonomic figures to describe the sequence of steps (1. 2. 3.) ...
Otherwise it is a good job, thank you again for sharing your knowledge.
Sorry for my bad english
An admirer

mekanix said:
Is the same procedure valid for Nexus 7 3g?
Thanks
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Should be exactly the same, as all build types are selected, just ensure you choose the right software version.

Can you guys help me..i can't run su command again after update to 4.2..how to give some application like es explorer root access in 4.2. Thank,s.
Sent from my Nexus 7 using xda app-developers app

You don't need BusyBox to root. I'd recommend avoiding it because it has been known to cause problems with system updates in the past.

GldRush98 said:
You don't need BusyBox to root. I'd recommend avoiding it because it has been known to cause problems with system updates in the past.
Click to expand...
Click to collapse
BusyBox is not a MUST but its recommended.
It just provides more commands for Linux/Unix based functions. (Probably more useful for advanced users)

Would this work for JOP40D version firmware?
Can't see anywhere on here detailing how to root that version of the Nexus 7.
Cheers

23james said:
Would this work for JOP40D version firmware?
Can't see anywhere on here detailing how to root that version of the Nexus 7.
Cheers
Click to expand...
Click to collapse
I just rooted my N7 (JB 4.2.1/JOP40D) using Nexus 7 Toolkit v 4.0.0
It's quite easy to do. I basically needed to root so I can use OTG usb to mount USB Flash Drive so I can watch Videos/Movies.

Wilks3y said:
IF IVE MISSED ANYTHING OR YOU'D LIKE TO SEE ANYTHING ADDED, LET ME KNOW AND I'LL GET IT DONE !!
Click to expand...
Click to collapse
Put windows only in the title

DC-IT said:
I basically needed to root so I can use OTG usb to mount USB Flash Drive so I can watch Videos/Movies.
Click to expand...
Click to collapse
Root not needed to do this. I can do it just fine on 4.2.1 unrooted.

DC-IT said:
I just rooted my N7 (JB 4.2.1/JOP40D) using Nexus 7 Toolkit v 4.0.0
It's quite easy to do. I basically needed to root so I can use OTG usb to mount USB Flash Drive so I can watch Videos/Movies.
Click to expand...
Click to collapse
Thanks for the reply. I'm guessing I need to separately unlock the bootloader before rooting? I literally have no idea how to do this. I rooted my Droid 2 a while ago and it was dead simple, this seems a lot more complicated! Also, is this is the same procedure for the 3g nexus?

link broken
Wilks3y said:
Now, download the latest WugFresh toolkit.
Direct Download
Click to expand...
Click to collapse
The direct download link is broken

Hemidroids said:
Put windows only in the title
Click to expand...
Click to collapse
Will create a Linux method if people want?
ukjaybrat said:
The direct download link is broken
Click to expand...
Click to collapse
Will be fixed gimme a min

Link Fixed.
Any1 else want a linux guide?

Hi All,
I wanted to check if i can root my Nexus 7 (16gb wifi) and continue to use the stock rom that is currently running ?
i.e. i want to use OrBot for proxy which needs superuser access hence need to root, but i want to continue using the stock rom that has come with Nexus 7. I couldn't find much detail on continuing with the stock rom.
Also can i use the "Settings"->"About Tablet"->"check for updates", when the next update comes even after i root my device or should manually update ??
Thanks,
Anup.

too long??
kitten13 said:
I wanted to test but the download is too slow (2 hours).
Click to expand...
Click to collapse
How does it take 2 hours to download a 24 mg file??

not working says it dont regaize my usb 2.0 i dont know why cain fastboot it shows adb user in device manager!!

How to root kindle fire any version (including 8.4.6)

To Start off... This is for windows and Linux! I had a lot of trouble at first trying to root. But as soon as i stumbled upon this 1 click root and the correct adb drivers i rooted fast and easy. My kindle was running 8.4.3 for this. But several people have came to me saying it works with 8.4.6 os. So what u want is the normal usb cable and windows/linux. And download the two files at the bottom.
Before you begin, if you have Windows Vista or Windows 7 or 8, open a Command Prompt & type ‘ping 4.2.2.2‘ then press enter. If you get replies, carry on with the rest of the guide. If not, you’ll have to carry out this small fix first! Skip to the bottom where it says "Still not work? Then move onto the "How to?..."
How to?...
1. ENABLE ADB IN SETTINGS UNDER SECURITY
Step 1. Download all files provided in the post and keep kindle unplugged at all times
Step 2. To be safe uninstall any other drivers for the kindle installed on the operating system (Win.) And Reboot.
Step 3. Install the adb drivers provided in the .zip
Step 4. Unzip the bin4ry tool on ur desktop and run the .bat file for windows as admin/.sh for Linux.
Step 5. Keep kindle unplugged still... The menu u will be promoted with will ask you what is ur device type. Select normal.
Step 6. Once you selected normal and the command prompt will say plug in your device. Do it.
Step 7. It will say a bunch of stuff, once it stops spitting out lines, if your kindle isnt already. Unlock it.
Step 8. Hopefully u get a window on ur kindle asking to restore and enter ur credentials. JUST PRESS RESTORE AT THE BOTTOM.
Click to expand...
Click to collapse
IF U GET LOST... ON THE CMD JUST FOLLOW THE DIRECTIONS ON THE COMPUTER. If I helped press the like button:good:
Still not work?
Right click on My Computer/Computer (whichever you have) and choose Properties.
Go into System and this will open System properties. Once here, select ‘Advanced System Settings’.
Next choose ‘Environment Variables’ and under the ‘System Variables’ find ‘Path’.
Select ‘Path’ with your mouse and choose ‘edit’.
Scroll to the very end of the list in here. It’ll have various paths for different things, all separated by a semi-colon like this ‘;‘. Be careful not to change anything else here, simply paste in ‘;C:\Windows\System32‘. Note that there’s no space between ; and the C:\Windows\System32 and this statement isn’t case sensitive, it can be both upper and lowercase or a mix.
Click OK & repeat until you’ve closed System Properties.
Test by opening Command Prompt (Start > Run > cmd OK, Win-key + R > cmd OK, or however you prefer to get there) & ping 4.2.2.2 again. If you see replies, congratz, you’re all set!
Click to expand...
Click to collapse
Kindle Fire HD 8.9 ADB drivers.zip
Bin4ry Root v30

Reserved :highfive:

2nd bootloader and TWRP for 8.4.3
Brandonrz said:
To Start off... This is for windows and Linux! I had a lot of trouble at first trying to root. But as soon as i stumbled upon this 1 click root and the correct adb drivers i rooted fast and easy. My kindle was running 8.4.3 for this. So what u want is the normal usb cable and windows/linux. And download the two files at the bottom.
Before you begin, if you have Windows Vista or Windows 7, open a Command Prompt & type ‘ping 4.2.2.2‘ then press enter. If you get replies, carry on with the rest of the guide. If not, you’ll have to carry out this small fix first! Skip to the bottom where it says "Still not work? Then move onto the "How to?..."
How to?...
IF U GET LOST... ON THE CMD JUST FOLLOW THE DIRECTIONS ON THE COMPUTER. If I helped press the like button:good:
Still not work?
Kindle Fire HD 8.9 ADB drivers.zip
Bin4ry Root v30
Click to expand...
Click to collapse
Now that I'm rooted could you do a tutorial on how to add a 2nd bootloader plus TWRP using 8.4.3? It would be greatly appreciated by many of us beginners!

rebelduke said:
Now that I'm rooted could you do a tutorial on how to add a 2nd bootloader plus TWRP using 8.4.3? It would be greatly appreciated by many of us beginners!
Click to expand...
Click to collapse
I'll get on it asap, but remember that I'm playing it by ear since I just got my kindle about a week ago. Right now I'm creating a tut on how to install the play store.
Sent from my Kindle Fire 8.9 HD via T-T Hd

Unfortunately it's not working for me. My Kindle is on 8.4.3 and has ADB enabled.I've installed the ADB drivers and rebooted my Windows 7 64-bit PC. I've pinged the tablet and get a response. I run the batch file as admin and press (1). I get some messages including "connect your device". A demon gets succesfully started at 5037. But after that I see nothing... My kindle's screen is unlocked, btw.
Any ideas?

pattiman said:
Unfortunately it's not working for me. My Kindle is on 8.4.3 and has ADB enabled.I've installed the ADB drivers and rebooted my Windows 7 64-bit PC. I've pinged the tablet and get a response. I run the batch file as admin and press (1). I get some messages including "connect your device". A demon gets succesfully started at 5037. But after that I see nothing... My kindle's screen is unlocked, btw.
Any ideas?
Click to expand...
Click to collapse
Delete the bin4ry folder. And unzip it again, run option 1 while unplugged. Then plug in your kindle.
Sent from my Kindle Fire 8.9 HD via T-T Hd

I tried the older root option and that worked fine. Thanks for your effort!

pattiman said:
I tried the older root option and that worked fine. Thanks for your effort!
Click to expand...
Click to collapse
Np. Glad I could help.
Sent from my Kindle Fire 8.9 HD via T-T Hd

pattiman said:
I tried the older root option and that worked fine. Thanks for your effort!
Click to expand...
Click to collapse
What does this mean? The older root option?
I am in the exact same boat. I can ping the device, but when running runme.bat it just sticks at waiting for device.
I deleted and re-extracted the zip file. That did not help. I am going to go try other root options to see if I can figure out which one you did that worked.

spearoid said:
What does this mean? The older root option?
I am in the exact same boat. I can ping the device, but when running runme.bat it just sticks at waiting for device.
I deleted and re-extracted the zip file. That did not help. I am going to go try other root options to see if I can figure out which one you did that worked.
Click to expand...
Click to collapse
I was able to use the instructions in the OP to root my KFHD 8.9 on 8.4.3. The adb drivers linked to in the OP were the problem for me. I had previously installed drivers that were a different size exe (9.183 MB) that I reverted to that allowed me to connect to the Fire through adb and run the tool from the OP to root.

spearoid said:
What does this mean? The older root option?
Click to expand...
Click to collapse
I used the method from this thread: http://forum.xda-developers.com/showthread.php?t=2069117

spearoid said:
I was able to use the instructions in the OP to root my KFHD 8.9 on 8.4.3. The adb drivers linked to in the OP were the problem for me. I had previously installed drivers that were a different size exe (9.183 MB) that I reverted to that allowed me to connect to the Fire through adb and run the tool from the OP to root.
Click to expand...
Click to collapse
I'm glad I could help another root
Sent from my Kindle Fire 8.9 HD via T-T Hd

1 downgrade, 2 failed attempts, one brick and a redscreen later... I installed 2nd boot loader + twrp + cm10.1 All starting from 8.4.3 ganna post a tut soon for you guys.
Sent from my Amazon Kindle Fire HD using Tapatalk HD

Edit: Delete post, mod please.
Sent from my Amazon Kindle Fire HD using Tapatalk HD

so i did everything step by step ,
it appeared to communicate fine and said done, however my device remains unrooted - no super user function
any ideas?
///
Update - manually installed super user app and prompt app, got it working!!

wnyzfinest said:
so i did everything step by step ,
it appeared to communicate fine and said done, however my device remains unrooted - no super user function
any ideas?
///
Update - manually installed super user app and prompt app, got it working!!
Click to expand...
Click to collapse
Glad you got it
Sent from my Amazon Kindle Fire HD using Tapatalk HD

8.4.6 Update..
Does anyone know if this root method will work for the 8.4.6 update that my Kindle just automatically upgraded to? I had it rooted before on 8.4.3 using this method.
Trying to decide if I risk it or wait till someone with a factory cable tests it first. Please let me know if it works successfully for you and I will update with my results if I get brave and try it myself...

Board373 said:
Does anyone know if this root method will work for the 8.4.6 update that my Kindle just automatically upgraded to? I had it rooted before on 8.4.3 using this method.
Trying to decide if I risk it or wait till someone with a factory cable tests it first. Please let me know if it works successfully for you and I will update with my results if I get brave and try it myself...
Click to expand...
Click to collapse
Did you have OTA updates blocked on 8.4.3? If so, by what method? I'm just asking because I'm still nervous about leaving my wifi on after rooting 8.4.3 and using the method of OTA blocking which renames the otacerts file.

sonicanomaly said:
Did you have OTA updates blocked on 8.4.3? If so, by what method? I'm just asking because I'm still nervous about leaving my wifi on after rooting 8.4.3 and using the method of OTA blocking which renames the otacerts file.
Click to expand...
Click to collapse
No I did not have OTA updates blocked and I always leave WiFi on, otherwise its a paperweight in my opinion. I hope this method will work for root with 8.4.6 but I think I will wait for someone with a factory cable to attempt first.

Board373 said:
No I did not have OTA updates blocked and I always leave WiFi on, otherwise its a paperweight in my opinion. I hope this method will work for root with 8.4.6 but I think I will wait for someone with a factory cable to attempt first.
Click to expand...
Click to collapse
Ah, I agree about that and it's why I hate being uncertain if my OTA blocking works because I'd hate to be stuck with an update that finally breaks the rooting exploit or something of that sort. That said, however, from what I've read the 8.9" Fire HD doesn't need a factory cable to enter fastboot. No confirmation on my end of that, as I've yet to need to use fastboot and thus haven't tried it.
I do know, however, that KFFirstAide's method of rooting with the latest version of the software (downloaded from here: http://forum.xda-developers.com/showthread.php?t=2096888 ) worked flawlessly on 8.4.3 for me. And those who tried the older version on 8.4.3 didn't report any bricking or anything of that sort, simply that the process completed but did not successfully root. I would assume, but certainly not guarantee or suggest to know with any certainty, that it puts the risk of bricking in the event it can't root the firmware version down to a low percentage. It may be worth attempting. But I definitely see why you're worried about it; I'd be hesitant, as well.
Good luck, and I hope someone who's had experience with 8.4.6 can come along and offer you some solid answers. I'd definitely suggest blocking OTA updates when you regain root, though. With OTA blocked, you can still manually download any updates you want (preferably after seeing whether it's capable of being re-rooted) and install them via usb, whenever you wish.

[Q] SuperSU Binary issue, root help!

Hi,
I have a T-Mobile LG G Flex that used to be rooted and after android system update now it doesn't have root access. Here's the thing: I ran TowelRoot and it displayed the following message: "This device isn't supported". Afterwards I downloaded and installed StumpRoot and when I run the app it displays a message saying: "Device is rooted" but when I run the Root Checker app it tells me device has no root access.
Heres the Software Information from the device:
Android Version
4.4.2
Baseband Version
M8974A-AAAANAZM-2.0.20064
Kernel Version
3.4.0
Build Number
KOT49I.D95920s
Software Version
D95920s
Can anyone point me towards a solution for this? I made a new thread regarding this matter because even though I've seen many people post similar situations they're for other type of devices. Any help will be deeply appreciated.
Thanks,

I'd say you might have to grab the tot for the d959, flash back to stock and run the updates again, then use stump.
ROGERS • LG G Flex D950G • Stock ROOT 4.4.2 • V4A • 180DPI • FLEXIN'

Eun-Hjzjined said:
I'd say you might have to grab the tot for the d959, flash back to stock and run the updates again, then use stump.
ROGERS • LG G Flex D950G • Stock ROOT 4.4.2 • V4A • 180DPI • FLEXIN'
Click to expand...
Click to collapse
What do you mean by 'tot'?

IamMAC said:
What do you mean by 'tot'?
Click to expand...
Click to collapse
Can someone answer this for me?
This always happens to me, I post a new thread and I get my questions answered once but after that no more help. Is this a forum rule?, do I need to help another user before receiving help again. I'd appreciate if someone could point me in the right track.
Thanks!,

IamMAC said:
Can someone answer this for me?
This always happens to me, I post a new thread and I get my questions answered once but after that no more help. Is this a forum rule?, do I need to help another user before receiving help again. I'd appreciate if someone could point me in the right track.
Thanks!,
Click to expand...
Click to collapse
Get back to stock using tot file following this guide:
http://forum.xda-developers.com/showthread.php?t=2644083

A lot of peep have been posting that they're not able to root the latest update with the previous methods. And also T-Mobile doesn't use a tot file. Its .kdz. But not gonna work due to the latest update doesn't have download mode. So if you're on the latest, I suggest find a root method ( try stumproot, safe root, I/o root, vroot, towel root, hell id try anything. But that's me. I don't suggest shoot blind if you don't know what you're doing) then install freedom flex get a custom recovery then make a backup and flash d'fuse's rooted KitKat and disable ota's.

mattwheat said:
A lot of peep have been posting that they're not able to root the latest update with the previous methods. And also T-Mobile doesn't use a tot file. Its .kdz. But not gonna work due to the latest update doesn't have download mode. So if you're on the latest, I suggest find a root method ( try stumproot, safe root, I/o root, vroot, towel root, hell id try anything. But that's me. I don't suggest shoot blind if you don't know what you're doing) then install freedom flex get a custom recovery then make a backup and flash d'fuse's rooted KitKat and disable ota's.
Click to expand...
Click to collapse
I'm having the same problem as OP, got any other methods that you think might work? tried all the ones I could find/ you listed and none have worked yet!

any update OP?

dmifsud44 said:
any update OP?
Click to expand...
Click to collapse
In my case I haven't been able to try anything because my tether app stopped working and I can't get any VPN service to work. Any suggestions on this other issue?

IamMAC said:
Hi,
I have a T-Mobile LG G Flex that used to be rooted and after android system update now it doesn't have root access. Here's the thing: I ran TowelRoot and it displayed the following message: "This device isn't supported". Afterwards I downloaded and installed StumpRoot and when I run the app it displays a message saying: "Device is rooted" but when I run the Root Checker app it tells me device has no root access.
Heres the Software Information from the device:
Android Version
4.4.2
Baseband Version
M8974A-AAAANAZM-2.0.20064
Kernel Version
3.4.0
Build Number
KOT49I.D95920s
Software Version
D95920s
Can anyone point me towards a solution for this? I made a new thread regarding this matter because even though I've seen many people post similar situations they're for other type of devices. Any help will be deeply appreciated.
Thanks,
Click to expand...
Click to collapse
No no no
Just install SU from playstore update binaries
P o o f there u'll have Root had same issue, you havta download SU AND INSTALL IT MANUALLY

fix
The fix for this problem is to download lg mobile support tool
on your pc
Click on options-upgrade recovery
Let it download
You will need to plug your phone
In via USB for the last 10 percent
You will now be unrooted and able to
Reroot with stumproots brute force
Oh and you will get download mode back
Power off-vol up+ plug in USB

damnrose said:
The fix for this problem is to download lg mobile support tool
on your pc
Click on options-upgrade recovery
Let it download
You will need to plug your phone
In via USB for the last 10 percent
You will now be unrooted and able to
Reroot with stumproots brute force
Oh and you will get download mode back
Power off-vol up+ plug in USB
Click to expand...
Click to collapse
I followed your steps and I was able to get the device up and running once again with ROOT access.
Thanks a million,

damnrose said:
The fix for this problem is to download lg mobile support tool
on your pc
Click on options-upgrade recovery
Let it download
You will need to plug your phone
In via USB for the last 10 percent
You will now be unrooted and able to
Reroot with stumproots brute force
Oh and you will get download mode back
Power off-vol up+ plug in USB
Click to expand...
Click to collapse
:good: This worked for me as well! Thanks

supersu problem
Hey! Rooted my phone yeasterday.
I have installed lateste version of SuperSU on play store, but still not working. says there is no binary fil to SU installed when I try to open the app.
My version is 4.4.2
device model
Samsung Galaxy GT 19505

Senzi said:
Hey! Rooted my phone yeasterday.
I have installed lateste version of SuperSU on play store, but still not working. says there is no binary fil to SU installed when I try to open the app.
My version is 4.4.2
device model
Samsung Galaxy GT 19505
Click to expand...
Click to collapse
This is a gflex thread not s4
But for your phone
if you have a recovery installed(If you don't you can flash it with Odin google it)
Boot into recovery
Flash the su zip from chainfires website
Should fix your issue

damnrose said:
This is a gflex thread not s4
But for your phone
if you have a recovery installed(If you don't you can flash it with Odin google it)
Boot into recovery
Flash the su zip from chainfires website
Should fix your issue
Click to expand...
Click to collapse
Dont think I got recovery installed, but I will try to flash it. But what does it mean "flash it"?

Senzi said:
Dont think I got recovery installed, but I will try to flash it. But what does it mean "flash it"?
Click to expand...
Click to collapse
"Flash It" or "Flashing" means to copy files to your device using an application such as ODIN.

Need help..
IamMAC said:
I followed your steps and I was able to get the device up and running once again with ROOT access.
Thanks a million,
Click to expand...
Click to collapse
Hi, so I am stuck without recovery or download mode. I know that the LG Mobile Support Tool should work but I tried it on two PCs and just as it finishes extracting the software after it downloads, the program runs into an error and closes. I am running D95920s like everyone else here. Just no luck. Any suggestions? I plugged in at 90% Not sure if im doing anything wrong.
Update: So the LG Mobile Tool has many security checks and it doesn't always allow for flashing. If anybody comes across this problem in the future. Refer to mattwheats instructions.
Here: http://forum.xda-developers.com/lg-g-flex/general/fyi-taking-ota-rooted-twrp-t2999344
It will force your phone to flash without download mode.

http://forum.xda-developers.com/showthread.php?p=60119946

"Error: device not found" when in Recovery - can't figure it out

Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!

@Lucky Armpit
When you are in recovery, at the adb sideload screen, unplug your N6 and plug it in again.

Lucky Armpit said:
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
Click to expand...
Click to collapse
Use Wugs toolkit to install drivers. It has a great step by step set-up to make sure it works and it tests everything so you know it works..

cam30era said:
@Lucky Armpit
When you are in recovery, at the adb sideload screen, unplug your N6 and plug it in again.
Click to expand...
Click to collapse
Hi cam30era, I tried that but it didn't help. I didn't try it after using Wug's toolkit so it's worth another shot.
Xplicit84 said:
Use Wugs toolkit to install drivers. It has a great step by step set-up to make sure it works and it tests everything so you know it works..
Click to expand...
Click to collapse
Hi Xplicit84, I used the Wugs toolkit provided in the NRT to install the proper drivers (it worked fantastic, by the way... mad props to Wug). That didn't help unfortunately.

try a different usb port
goto the device manager in windows and see if everything is good (no ! by a device)

apristel said:
try a different usb port
goto the device manager in windows and see if everything is good (no ! by a device)
Click to expand...
Click to collapse
Hi apristel, yup, tried that too, as I had read that perhaps there may be an issue with USB 3.0 ports. I don't think I have USB 3.0 ports (my laptop is a 2012-era Alienware M17x R3) but I tried a different port for the sake of doing it and it didn't make a difference.

Where did you get the 5.1 .zip file? Give us the exact name of the file because the 5.1 VZW .zip file that has been posted here that ends with .xml.zip is not designed for an adb sideload command. I.e., not designed to be flashed in recovery at all.

teddyearp said:
Where did you get the 5.1 .zip file? Give us the exact name of the file because the 5.1 VZW .zip file that has been posted here that ends with .xml.zip is not designed for an adb sideload command. I.e., not designed to be flashed in recovery at all.
Click to expand...
Click to collapse
Hi teddyearp, I downloaded it from a link on Droid-Life. I don't remember the exact name of the file because I renamed it to something much shorter, but here's where I got it from -
http://www.droid-life.com/2015/03/1...s-for-nexus-devices-4-5-6-7-9-10/#more-163271
Edit - Here's the direct link (the one I used) - http://android.clients.google.com/p...ed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip

Lucky Armpit said:
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
Click to expand...
Click to collapse
Any luck, having the same problem and it's driving me nuts.

Mongo23ny said:
Any luck, having the same problem and it's driving me nuts.
Click to expand...
Click to collapse
Are you selecting "apply update from ADB" in recovery and then hitting power?
Then: adb sideload <filename of update.zip>
?

apristel said:
Are you selecting "apply update from ADB" in recovery and then hitting power?
Then: adb sideload <filename of update.zip>
?
Click to expand...
Click to collapse
Yes, as soon as boots into recovery it completely disappears from device manager. If I run the command after apply update from adb it says device not found.

Mongo23ny said:
Yes, as soon as boots into recovery it completely disappears from device manager. If I run the command after apply update from adb it says device not found.
Click to expand...
Click to collapse
Most likely a driver issue. I can remote in and check it out if you want using teamviewer

Go through the driver setup in wug again, pay close attention when you are deleting any old drivers..... delete anything that says google nexus or android... I had to do it twice.... put the phone into adb side load mode... check device manager again.. make sure you dont have a ? by android device... I did... update the driver from wug ( also I hid the sdk driver folder by renaming it so windows didn't try to pick up the driver from there again... once installed bingo!

apristel said:
Most likely a driver issue. I can remote in and check it out if you want using teamviewer
Click to expand...
Click to collapse
When I run the command reboot bootloader, no problem. But when it is in recovery I watched it disappear from device manager.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Gage_Hero said:
Go through the driver setup in wug again, pay close attention when you are deleting any old drivers..... delete anything that says google nexus or android... I had to do it twice.... put the phone into adb side load mode... check device manager again.. make sure you dont have a ? by android device... I did... update the driver from wug ( also I hid the sdk driver folder by renaming it so windows didn't try to pick up the driver from there again... once installed bingo!
Click to expand...
Click to collapse
I used CF auto root to unlock the bootloader and root. I do have the NRT on my computer though.

Mongo23ny said:
When I run the command reboot bootloader, no problem. But when it is in recovery I watched it disappear from device manager.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
I used CF auto root to unlock the bootloader and root. I do have the NRT on my computer though.
Click to expand...
Click to collapse
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)

apristel said:
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
Click to expand...
Click to collapse
How do I install it properly? I got rid of some old drivers as well

Mongo23ny said:
How do I install it properly? I got rid of some old drivers as well
Click to expand...
Click to collapse
Well you can just change them in the device manager.
I'm willing to use team viewer and show you how. (you'd see everything i do) It's hard to write it out for me right now..just had hand surgery this morning and my hand is still completely numb. If you want to download this and run it http://download.teamviewer.com/download/TeamViewerQS_en.exe
PM me the id and password and i'll connect up and show ya. Just so you know, it'd be a one time thing connecting, your password changes everytime and you'd have to have that running to connect. I own a computer repair store and use it frequently.

apristel said:
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
Click to expand...
Click to collapse
I'm thinking that's the problem for me too, but I don't understand what I'm missing. When I ran Wug, I removed anything and everything that had the word "Google" next to it. Wug installed the drivers (had to do option #2 before I got no errors at all) and it reports that everything is hunky-dory. But as Mongo23ny said, that's exactly what happens... when it's at the boot menu it's in Device Manager but the moment I select Recovery it disappears.

Lucky Armpit said:
I'm thinking that's the problem for me too, but I don't understand what I'm missing. When I ran Wug, I removed anything and everything that had the word "Google" next to it. Wug installed the drivers (had to do option #2 before I got no errors at all) and it reports that everything is hunky-dory. But as Mongo23ny said, that's exactly what happens... when it's at the boot menu it's in Device Manager but the moment I select Recovery it disappears.
Click to expand...
Click to collapse
I can try to fix your drivers too, just follow the link i posted for him and send me the info. I don't have stock recovery on my phone to replicate your issue.

apristel said:
I can try to fix your drivers too, just follow the link i posted for him and send me the info. I don't have stock recovery on my phone to replicate your issue.
Click to expand...
Click to collapse
PM sent. Thanks

[How to]VS980 Confirmed Root and Recovery Installation Method

Hey guys,
Recently, I have been trying to re-root my LG G2 VS980 that was returned to lollipop stock (LG Firmware). However, all the tools I knew that previously worked, (Ioroot, Towelroot, Stumproot, Kingoroot, etc..) did not work. After months of testing, I finally found one app that currently works called KingRoot.
As far as I know, it is the only root method that acutally still works after LG patched most of the exploits so I thought I would share the info with you guys in case some of you are still interested in rooting your G2.
Instructions:
1. Install Kingroot: http://kingroot.net/ (the APK doesn't work for the G2)
2. Go to settings in your phone and click the build number 7-10 times to enable Developer Options
3. Go to Developer Options and enable USB Debugging
4. plug the phone into your computer and launch the program. Make sure you see the USB Debugging card that will pop up on your phone.
Launch the program and allow the program to root your phone.
Sidenote: The only downside to the app is it is all in Korean but it is very easy to tell what it is asking due to excellent pictures
After you receive root, download the app RootChecker just to make sure.
To Install TWRP:
1. Instructions: Go to Play Store and type in the search window, "AUTOREC".
2. Select the correct variant: ex. VS980=Verizon etc...
3. Install the app.
4. Watch TWRP Install on your phone.
5. Reward yourself on your hard work with a pat on the back.
So that's it; A fast easy, and trouble free method on getting root and installing TWRP

Thanks for this. I recently acquired a G2, and will be trying this out tonight.

tribalartgod said:
Thanks for this. I recently acquired a G2, and will be trying this out tonight.
Click to expand...
Click to collapse
No problem. Have fun with your custom ROM of choice.

Can you share the setup files? I also need to re-root my Verizon phone. The kingroot ownload links looks dead
i downlaoded it from here. I have usb dev enabled. now what? http://kingroot-pc.en.uptodown.com/download
Stuck on that step. I know its telling me to enable USB debuggin which I have, it doens' do anythong when I click Go in Korean

I managed to enable debugging mode which was by setting the 'USB Type" on the phone to "Internet -> Ethernet"
But Kingroot isn't managing to root the phone. It goes 100 percent and nothing.
Ioroot managed to get the phone into the reboot phase but the phone no longer processed the splash screen of the recover/bootloader. The splash screen which has the android mascot on its back with abdomen open.
"LG G2 One lick Tool" makes the phone go to "download mode" but its stuck at 0 percent. I disconnect and replug in hope of kickstarting it, doesn't work.
What can I do now?

y300owner said:
I managed to enable debugging mode which was by setting the 'USB Type" on the phone to "Internet -> Ethernet"
But Kingroot isn't managing to root the phone. It goes 100 percent and nothing.
Ioroot managed to get the phone into the reboot phase but the phone no longer processed the splash screen of the recover/bootloader. The splash screen which has the android mascot on its back with abdomen open.
"LG G2 One lick Tool" makes the phone go to "download mode" but its stuck at 0 percent. I disconnect and replug in hope of kickstarting it, doesn't work.
What can I do now?
Click to expand...
Click to collapse
Where you able to get it to work? I am running into the same problems.
Sent from my SM-N920V using Tapatalk

y300owner said:
Can you share the setup files? I also need to re-root my Verizon phone. The kingroot ownload links looks dead
i downlaoded it from here. I have usb dev enabled. now what? http://kingroot-pc.en.uptodown.com/download
Stuck on that step. I know its telling me to enable USB debuggin which I have, it doens' do anythong when I click Go in Korean
Click to expand...
Click to collapse
Hmm... Sorry for the late response. Try this link and see if it works: http://www.kingroot.org/

mach01 said:
Hmm... Sorry for the late response. Try this link and see if it works: http://www.kingroot.org/
Click to expand...
Click to collapse
Thanks I tried almost almost everything.
Stumbled upon Stump root last night and it brute forced it way in.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
Jshokamp said:
Where you able to get it to work? I am running into the same problems.
Sent from my SM-N920V using Tapatalk
Click to expand...
Click to collapse
What problem? Check one of the thread I started. Posted everything on it.

y300owner said:
Thanks I tried almost almost everything.
Stumbled upon Stump root last night and it brute forced it way in.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
What problem? Check one of the thread I started. Posted everything on it.
Click to expand...
Click to collapse
You on 39aa or just 39a?

Lawlrus said:
You on 39aa or just 39a?
Click to expand...
Click to collapse
No idea. I was on a downgraded stock ROM, VS980_27A or was it VS980_24A. Can't remember; 4.4.2
Whatever it was, none of the popular rooting method was working. They were managing to do 'semi root' as in root message was displayed in "hard reset mode" and in 'download mode' but there was no root when the OS fully booted. The 'stock recovery' was also corrupted as in it showed a dead android with red exclamation mark. From the searching I did, people were saying there was no recovery installed so I needed one but I could not install. No stock recovery means no 'adb'.
Stump root gave 'complete' root. I hope you understand what I'm trying to say.

Will this work if I am on the 39aa update from Verizon? I am skeptical about this because this is my only phone and don't need to mess it up.

UserofAndroid1813 said:
Will this work if I am on the 39aa update from Verizon? I am skeptical about this because this is my only phone and don't need to mess it up.
Click to expand...
Click to collapse
I don't think I've seen a way to root 39aa as of yet. One of our developers was asking about it as well, if you do find a way, please @ me so I can hook him up
I'm still looking around for a way.

Lawlrus said:
I don't think I've seen a way to root 39aa as of yet. One of our developers was asking about it as well, if you do find a way, please @ me so I can hook him up
I'm still looking around for a way.
Click to expand...
Click to collapse
I tried and failed at it. I am downgrading to VS98039A_05 and going from there. it seems VS9803AA was meant to patch root and also SF security patches.

This XML file does not appear to have any style information associated with it.
The document tree is shown below.
<Error><Code>AccountProblem</Code><Message>
Your Google account is not currently enabled for this operation. Please check https://code.google.com/apis/console/#:billing to see if you have a past due balance or if the credit card (or other payment mechanism) on your account is expired. You can find additional information at https://developers.google.com/storage/docs/signup</Message></Error>

Thanks for this. For people who don't want to mess with Korean, or if Kingroot doesn't work, LG One Click Root still works on VS9803AA, although you may have to run it 3 or 4 times. Here's the original post: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
And here's a good guide: http://webtrickz.com/how-to-root-lg-g2-running-lollipop-with-lg-one-click-root/

Interesting... I've tried that method four times and it never worked for me. Good to hear it works for other people though. I agree not to many people want to use
Korean deciphering skills just to root their phone but its just an option.

marathonjon said:
Thanks for this. For people who don't want to mess with Korean, or if Kingroot doesn't work, LG One Click Root still works on VS9803AA, although you may have to run it 3 or 4 times. Here's the original post: http://forum.xda-developers.com/lg-g...lipop-t3056951
And here's a good guide: http://webtrickz.com/how-to-root-lg-...ne-click-root/
Click to expand...
Click to collapse
Both of these links are dead.

CruelSun said:
Both of these links are dead.
Click to expand...
Click to collapse
Links are fixed. The whole URLs don't show in the post, but if you click on them, they should work.

those with the issue of kingroot not reading your phone plugged in. put your usb option on phone to PTP camera mode and it will work now.

Even doing all, i m still unable to get my phone recognized. Switched many times befween ptp
Sent from my VS980 4G using Tapatalk
---------- Post added at 05:55 AM ---------- Previous post was at 05:54 AM ----------
Furqan Ullah said:
Even doing all, i m still unable to get my phone recognized. Switched many times befween ptp
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
And other file transfer option. USB picture is displaying sometimes or sometimes circle
Sent from my VS980 4G using Tapatalk