[Q] Droid 4 Motofail Root Method Not Working - Motorola Droid 4

I'm trying to root my stock Droid 4 using Motofail, and I can get to the beginning of the method but then all I get is this:
Motorola universal root script ($version version)
by Dan Rosenberg (@djrbliss)
Tested on Droid 3, Droid Bionic, and Droid RAZR
Before continuing, ensure USB debugging is enabled, that your
device is in charge only mode, and your phone is connected via USB.
Press any key to continue . . .
Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
My phone is all of those things listed, and as far as I know I haven't done anything incorrectly. Anybody know how to fix this?

You do have the latest USB drivers from Motorola, right?
Aside from that and having USB mode in Charge Only, I personally can't think of any issues getting the root tool from starting up (but, hey, I'm no expert in this field).
Sent from my DROID4 using XDA

BPMOmega said:
You do have the latest USB drivers from Motorola, right?
Aside from that and having USB mode in Charge Only, I personally can't think of any issues getting the root tool from starting up (but, hey, I'm no expert in this field).
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
I was unable to find a Droid 4 ADB driver. Would a Droid RAZR one work?

wynn55 said:
I was unable to find a Droid 4 ADB driver. Would a Droid RAZR one work?
Click to expand...
Click to collapse
You can just get the drivers straight from the motorola site. They aren't phone specific. And just to share by experience the root method didn't work for me the first time either so I just ran it again and it worked. Just make sure you have usb debugging enabled and your phone is in charge only mode.

Thanks!
Grizzy3 said:
You can just get the drivers straight from the motorola site. They aren't phone specific. And just to share by experience the root method didn't work for me the first time either so I just ran it again and it worked. Just make sure you have usb debugging enabled and your phone is in charge only mode.
Click to expand...
Click to collapse
This seemed to do the trick! Thanks for the help.

wynn55 said:
This seemed to do the trick! Thanks for the help.
Click to expand...
Click to collapse
I'm glad it worked for you

BPMOmega said:
You do have the latest USB drivers from Motorola, right?
Aside from that and having USB mode in Charge Only, I personally can't think of any issues getting the root tool from starting up (but, hey, I'm no expert in this field).
Click to expand...
Click to collapse
Is "Charge Only" the same thing as "USB Debugging" (the wording used in the Rosenberg instructions)? I'm thinking about getting a D4 and would want to root but I'm doing some research first.
Thanks.

OhioGuy67 said:
Is "Charge Only" the same thing as "USB Debugging" (the wording used in the Rosenberg instructions)? I'm thinking about getting a D4 and would want to root but I'm doing some research first.
Thanks.
Click to expand...
Click to collapse
No. "Charge Only" is the option you will select when you connect USB (you'll see a status notification that you can tap to bring up the USB mode dialog).
Enable debugging is selected in settings under "Developer Options".

Related

HELP Nexus 7 JB 4.2 update

So I just received the Jellybean 4.2 update today. I was a little excited. However, after the update the device is now sluggish, unresponsive, it refuses to connect to any wifi or bluetooth device, and all other manner of trouble.
I want to revert back to 4.1.2 and I am using the Nexus Root Toolkit. The app cannot unlock, root, or reflash the stock 4.1.2 rom though. I always get the error Fastboot device was not found. What does this mean and how do I fix it? I've booted into the Fastboot thing where it says Start at the top.
Someone please help, I have 3 Nexus 7's here all suffering from the same issues.
EDIT:
USB debugging is on.
The drivers are installed and configured via the guide in Nexus Root Toolkit.
You are getting that error because you need to enable USB debugging. In 4.2 it is hidden. Go to settings/about and spam hit the build number until it says Congrats you are now a developer. Go into develpper options, enable USB debugging. Voila, should now be able to reflash.
Sent from my Galaxy Nexus using Tapatalk 2
It only seems to work on the main account. Not that it matters much. It says your a developer but you cannot access the options
Sent from my Nexus 7 using XDA Premium HD app
bolagnaise said:
You are getting that error because you need to enable USB debugging. In 4.2 it is hidden. Go to settings/about and spam hit the build number until it says Congrats you are now a developer. Go into develpper options, enable USB debugging. Voila, should now be able to reflash.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I've had usb debugging on the entire time and still get that same error.

New Security Features for ADB in 4.2.2

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

ADB Help

I formatted my system on Stock ROM. I found another stock ROM for sprint now i can't get the ROM i want on my phone because the PC won't read the phone (in CWM recovery). My question is...is there a way to get the ROM on the phone through ADB? Im not all that familiar with it. If so...whats the command?
adb push rom.zip /sdcard
nhizzat said:
adb push rom.zip /sdcard
Click to expand...
Click to collapse
says error device not found
Prestige_DOPE said:
says error device not found
Click to expand...
Click to collapse
You might need to go through a different set of instructions just to make sure the devices is recognized on ADB. Here are my instructions for backing up and restoring app data via ADB, and it includes pretty good instructions on setting up your phone with ADB (well, at least I'd like to think so).
DogzOfWar said:
You might need to go through a different set of instructions just to make sure the devices is recognized on ADB. Here are my instructions for backing up and restoring app data via ADB, and it includes pretty good instructions on setting up your phone with ADB (well, at least I'd like to think so).
Click to expand...
Click to collapse
Well. I have my phone right here and connected to the PC with ADB set up and all. The problem is my PC wont recognize my phone. I tried using fastboot and ADB (i guess they're the same) and it keeps saying the error i stated above your post. The plan is to get the ROM on flashed on my phone. I don't know any other way of doing that. I thought fastboot (adb) would be of assistance but i dont know much about it.
Prestige_DOPE said:
Well. I have my phone right here and connected to the PC with ADB set up and all. The problem is my PC wont recognize my phone. I tried using fastboot and ADB (i guess they're the same) and it keeps saying the error i stated above your post. The plan is to get the ROM on flashed on my phone. I don't know any other way of doing that. I thought fastboot (adb) would be of assistance but i dont know much about it.
Click to expand...
Click to collapse
What I noticed on my phone is that I had ADB working fine for my previous phone (HTC Rezound), but that same ADB install didn't work for the X. When I downloaded the Moto X Toolkit, which included its own version of the adb.exe, it worked fine.
So consider trying everything through the toolkit.
Also, just to double check your settings:
- Make sure you have enabled Developer Settings, and Enable Debugging via ADB
- I set my phone to Camera mode, which seems to work a bit better than Media
DogzOfWar said:
What I noticed on my phone is that I had ADB working fine for my previous phone (HTC Rezound), but that same ADB install didn't work for the X. When I downloaded the Moto X Toolkit, which included its own version of the adb.exe, it worked fine.
So consider trying everything through the toolkit.
Also, just to double check your settings:
- Make sure you have enabled Developer Settings, and Enable Debugging via ADB
- I set my phone to Camera mode, which seems to work a bit better than Media
Click to expand...
Click to collapse
Well my phone wont bootup so thats not going to work but im in the moto x tool kit and i selected to push the ROM onto the sdcard now the whole tool kit froze...is that because its doing something or....
Try a different USB port? Then type adb devices.
Have you downloaded the Motorola Device Manager software? It contains all the necessary drivers. How about the Android SDK?
Prestige_DOPE said:
Well my phone wont bootup so thats not going to work but im in the moto x tool kit and i selected to push the ROM onto the sdcard now the whole tool kit froze...is that because its doing something or....
Click to expand...
Click to collapse
I misunderstood you're original question, sorry. I didn't realize it won't boot at all. I have done what you are asking for my Nexus 7 (which I had messed up). Typically, when you're in the recovery and you plug it into a PC, it will install drivers (separate from the ones when Android OS is running).
Maybe consider trying to use RSD Lite to at least get a functional OS back on there? This page lists drivers to use along with RSD Lite. Maybe that would help get things recognized to the point where you can copy over a ROM?
nhizzat said:
Try a different USB port? Then type adb devices.
Have you downloaded the Motorola Device Manager software? It contains all the necessary drivers. How about the Android SDK?
Click to expand...
Click to collapse
Didnt work...the more things that arent working the more scared i become
DogzOfWar said:
What I noticed on my phone is that I had ADB working fine for my previous phone (HTC Rezound), but that same ADB install didn't work for the X. When I downloaded the Moto X Toolkit, which included its own version of the adb.exe, it worked fine.
So consider trying everything through the toolkit.
Also, just to double check your settings:
- Make sure you have enabled Developer Settings, and Enable Debugging via ADB
- I set my phone to Camera mode, which seems to work a bit better than Media
Click to expand...
Click to collapse
Installed RSDLite and literally screamed "What the hell is this". A little help here on how this is supposed to work?

[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

Trying to root using NRT and getting errors

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

Categories

Resources