Related
Here's my problem,
I had the Droid 2 with stock ROM rooted and all was well. My phone installed the Gingerbread ROM (4.5.601) when Verizon pushed it out a few days ago. Thankfully, this did not totally jack up my phone. However, I no longer have root access.
I have tried three different 1 click root methods for the Gingerbread ROM but none of them worked. I tried un-rooting and re-rooting with one clicks and that's not working. I tried manually removing the Superuser app and rooting, no joy.
The one clicks are connecting with the phone but the phone does not seem to want to allow access to change files.
Before anyone asks, YES I have the drivers installed and the connection with the PC is good. I have attempted to run the 1 click roots in "charge only" AND "PC Mode". Debugging is on and I am set to allow non-market applications.
Suggestions?
Thanks,
Tracker
Update: in trying to manually remove old superuser file with adb shell, I just can't seem to get the # prompt to execute the commands even after running Pete Souza's exploits.
suggestions?
Hope somebody comes up with an answer - same thing happened to me.
did you use the d3 root method? thats the only one that works 100% on gingerbread.
Yes. I used the "Pete's Motorola Root Tools.exe" program on Win7:
psouza4.com/droid3/#root
I also followed the "Droid X Notes" section at the bottom even though I have the D2 and I'm not able to get the "adb shell" ending with #.
SOS!!
Thank you for such a clear, concise post! I am in the same boat with no luck. I used the one click root for D3 which says it will work for a number of Android phones, including the D2 Global, but is NOT working with my D2. I have run the application two times and both times it went through the entire process, rebooted my phone three times and said success but...no success... I am sooo bummed as the only way I get internet at home is via Wireless Tether which I can no longer use because I do not have Root access!
Desperate in Cool (the name of the town I live in), I need help!!
Thanks in advance,
Jeni
Yeah, still no joy here. I've retried everything that I mentioned in the OP and still can't get the # so I can execute an un-root and/or re-root as described on Pete's website.
I've tried it on both a Win XP and a Win 7 machine.
Anyone have any suggestions? It appears the D2 Gingerbread firmware doesn't want to allow permissions to modify certain portions that were allowed before.
Success
I didn't so much fix the problem as hit it with a bat until it shattered, then rebuilt it.
My fix was to SFB the phone back to Froyo with factory defaults, activate it with Verizon (at this point I have no software added or accounts set up on it so obviously no root), apply the OTA update to GB, perform the 1-click Root which worked this time, then setup my google accounts and install Titanium Backup which I had previously used, and restored all my data from it.
At this point I'm getting some force-close errors which I'm sure are related to the Titanium restore but I was able to ADB Shell in and SU so I know I have rooted it properly and at the very least I will do another clean wipe and restore individual applications one at a time so I know which aren't working right and go from there.
Good luck everyone!
My fix was to SFB the phone back to Froyo with factory defaults, activate it with Verizon (at this point I have no software added or accounts set up on it so obviously no root), apply the OTA update to GB, perform the 1-click Root which worked this time, then setup my google accounts and install Titanium Backup which I had previously used, and restored all my data from it.
Click to expand...
Click to collapse
I kinda figured that this would work. I'm trying to avoid a full nuke of the phone, but so far it appears that this is the only work around.
Anyone else got a plan?
Only option I was going to provide was SBF to 2.3.2 with RSDlite and re-flash the OTA, then run the Droid3 exploit.
I have a D2G and I had the exact same problem. I did an OTA upgrade without un-rooting (I was earlier rooted using z4root). I had a long discussion with Pete Souza, the guy who created 1-Click root. And he agreed to help me out. He did a remote to my computer and rooted my D2G. I am going to try to reproduce all the steps here.
Situation: Was rooted using z4root. Had Superuser and su binary both on my phone but root was not recognized by titanium Backup, SetCPU, etc.
Resolution:
Run Psouza's 1-cick root http://www.psouza4.com/droid3 (ensure u have motorola drivers)
First try the Root, and if that does not work only then continue with the following steps. I got an error after step 3 which said the phone cannot be rooted (or something like that). The first two steps were a success.
Now that the root is not working, run the Temp ADB Root from the same app. In my case even that failed - but Pete said that ignore the failure message.
Now, I need to delete the su and busybox which are leftovers from the earlier root.
Open a command prompt in the support_files folder where adb is located.
Get into the shell by typing: "adb shell"
type "/system/xbin/su"
This will pop-up a prompt on your phone to allow Superuser access - just click Okay.
The $ sign will change to #
Now type "busybox mount -o remount,rw /dev/block/mtdblock3 /system"
now type "cd /system/bin" This is where your su and busybox are.
Type "rm su"
Type "rm busybox"
After this just exit out of everything and run the 1-click root again. It should work now.
======================
All credits to psouza www.psouza4.com
======================
drumster said:
I have a D2G and I had the exact same problem. I did an OTA upgrade without un-rooting (I was earlier rooted using z4root). I had a long discussion with Pete Souza, the guy who created 1-Click root. And he agreed to help me out. He did a remote to my computer and rooted my D2G. I am going to try to reproduce all the steps here.
Situation: Was rooted using z4root. Had Superuser and su binary both on my phone but root was not recognized by titanium Backup, SetCPU, etc.
Resolution:
Run Psouza's 1-cick root http://www.psouza4.com/droid3 (ensure u have motorola drivers)
First try the Root, and if that does not work only then continue with the following steps. I got an error after step 3 which said the phone cannot be rooted (or something like that). The first two steps were a success.
Now that the root is not working, run the Temp ADB Root from the same app. In my case even that failed - but Pete said that ignore the failure message.
Now, I need to delete the su and busybox which are leftovers from the earlier root.
Open a command prompt in the support_files folder where adb is located.
Get into the shell by typing: "adb shell"
type "/system/xbin/su"
This will pop-up a prompt on your phone to allow Superuser access - just click Okay.
The $ sign will change to #
Now type "busybox mount -o remount,rw /dev/block/mtdblock3 /system"
now type "cd /system/bin" This is where your su and busybox are.
Type "rm su"
Type "rm busybox"
After this just exit out of everything and run the 1-click root again. It should work now.
======================
All credits to psouza www.psouza4.com
======================
Click to expand...
Click to collapse
IMO this instruction should be stickied.
This worked perfectly on my wife's D2G. Rooted Gingerbread = a good start to the day!
Awesome! Thanks!
Just wanted to say I think i love you...this worked for me after two tries on my Droid 2.
First time I was able to remove su and busybox...then when I applied the one click root again, it said there were a bunch of errors but still succeeded. After the reboot I didn't get superuser access yet so I went through deleting su and busybox again (but busybox wasn't found)
The second time i decided to restart my phone before running the script again and when attempting to verify if su was still installed by going into adb shell...it said my phone was already rooted.
Thanks!!
Awesome!
Thanks! This worked for me as well! (after additional reboot)
Good Info but one problem for me
Since I did the OTA Gingerbread, I cannot get into debugging mode. I have uninstalled the Moto drivers & reinstalled using my administrator profile on Windows 7. I have also sbf my phone. Wipe cache. Factory reset. Activate service (NOT download or sync w/ google). OTA Gingerbread. This is on a regualr D2. Anyone have any ideas on how I can get into debugging mode. Otherwise I can't do anything.
Thank you!
I am so glad I found this post and the directions posted by drumster. I had previously used z4root and had not unrooted before allowing the Gingerbread upgrade. Pete's application fixed my Droid 2 on the first attempt; no other steps were needed.
Thanks again,
Andrew
awesome
psouzas 1 click worked for me. Droid 2. previously had rooted with deroot method until it updated by itself to gingerbread which broke root.
enabled usb debugging
in pc mode, clicked on souza's link and followed instructions
i have win 7 64 bit computer
It works
I just got it to work. I was on rooted froyo. Sbf'd back to stock froyo. Downloaded and installed OTA G bread. Then I had to run the D3 one click root method twice but the 2nd time it worked fine.
This does not work with Droid X System Version .621.
(Information on this post was taken from Pete's website: http://www.psouza4.com/Bionic/)
NOTE: If you were rooted on the original OTA and took the update to .602 and lost root, read the 'Droid X' notes under the how-to.
-----------------------------------------------------------------------------
How to: One Click Root for Windows 7/Vista
1. Your phone must be connected via USB data cable to your computer and be recognized.
2. If your phone is connected, but not recognized, you may need to install one of these software drivers:
-Windows universal 32-bit Motorola drivers version 5.2.0
-Windows universal 64-bit Motorola drivers version 5.2.0
3. Download this one-click root package: PetesMotorolaRootTools_v1.08.zip
4. Extract the contents of the one-click root package to a new folder on your computer.
5. Make sure USB Debugging is enabled on your device. This should be under Settings -> Applications -> Development -> USB Debugging.
6. From the new folder on your computer, double-click on Pete's_Motrola_Root_Tools.exe to begin the root process.
7. Click 'Root My Phone'.
-----------------------------------------------------------------------------
Droid X Note:
Droid X Notes
Your phone may need to be in either charging mode or PC mode or you may need to toggle it a number of times for the device to recognized correctly.
If you are trying to root from the OTA Gingerbread update and you were previously rooted, you will probably experience problems with this root method because of the pre-existence of busybox and superuser.apk. For that reason, you may need to attempt both the script method (for Windows XP users) and program executable method (Windows Vista/7 users). If you are still having problems, please follow these instructions:
Open a Command Prompt in the folder where you extracted the one-click root package (see instructions for rooting). If you are using Windows 7, you can just use Shift+Right-Click on the folder you extracted the package and choose to "Open a command prompt here". For other operating systems or versions of Windows, you may require some DOS experience or need to Google how to change directories.
In the command prompt, type the following command:
adb shell
Click to expand...
Click to collapse
If you receive any kind of error, then you may not be in the folder where you extracted ADB.exe or you may need to reboot your computer, your phone, or check the connection. You should receive an ADB prompt ending with either a # or a $.
If the line ends with a $, then run the one-click exploit for Windows XP (even if you have Windows Vista or 7) and only complete step 1.
When you have adb shell ending with a #, type the following commands:
mount -o remount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
Click to expand...
Click to collapse
Ignore any messages that warn you about the file not being found/missing. We're removing old copies of su/superuser which are causing this one-click root method to fail.
(credit: KevlarGibs)
Additionally, during the parts of the one-click root that reboot your phone, your phone will most likely reboot into recovery instead of into the standard Android lock screen. If this is the case, simply unplug the cable and reboot the phone manually. When you are finished rebooting, plug the phone back in again. Some people have had to reboot their PC too.
Finally, some users have mentioned that the root isn't taking affect right away for all apps. Eventually, after several reboots, the phone finally takes root. We're not sure why this is (I don't have a Droid X -- I'm just re-posting this information for brevity).
-----------------------------------------------------------------------------
Please try the Windows Vista/7 method first! It will work better for most Windows XP users.
Only use this method if the other has not worked yet.
http://www.mediafire.com/?pj5lk8u2s0zhqo8
----------------------------------------------------------------------------
Nothing you see here is my work. All credit goes to Pete and everyone he's credited. I simply created this thread on XDA using Pete's information.
Reserved for future information.
Awesome
Great tool, thanks so much!
Confirmed OTA
Works fine!!!
Awesome! Works perfectly!
Nice, I may give it a go (may sbf to 602 for a clean start)
D.
I SBF'd to .602 on my DX and the root was successful but I can't get my phone to boot into CWM Recovery. I tried following the special DX instructions but can't get the ADB Shell to show anything but a $.
Whats next for me to try to get this working?
Hi I'm trying to unroot my x2 and it keeps saying Error: you are missing adb.exe, which was packaged with this program. The adb.exe is in the same folder as all of the other files i extracted to my restore folder. Any ideas?
I will try this at thanksgiving for my dad's X
It was rooted froyo and got the ota GB and wont root. Hopefully this works
choonami said:
I SBF'd to .602 on my DX and the root was successful but I can't get my phone to boot into CWM Recovery. I tried following the special DX instructions but can't get the ADB Shell to show anything but a $.
Whats next for me to try to get this working?
Click to expand...
Click to collapse
Your preinstall is full. With Root Explorer go to preinstall/app/ and delete something (NFS). Reflash Clockwork mod. Then try again.
Sent from my PC36100 using XDA Premium App
I have just updated from 602 to 605 ota official.
Did run the process as guided above, but nothing seemed to happen on my droidX, and I cant see any super user. and did try to instal CWM to my device, its said the device has not rooted.
Any one got the same issue?
Greatdane said:
I have just updated from 602 to 605 ota official.
Did run the process as guided above, but nothing seemed to happen on my droidX, and I cant see any super user. and did try to instal CWM to my device, its said the device has not rooted.
Any one got the same issue?
Click to expand...
Click to collapse
Were you previously rooted on .602? If so, you may need to follow the Droid X notes.
Sent from my DROIDX using XDA App
This worked perfectly on my Droid X....thanks for making it so easy!!
Finally worked up the cajones to use Pete's Tools and rooted my DX. *whew*
Doing a complete TiBu right now. Couple quick questions.......
1. Is CWM installed? If so, how does one access. If not, ROM Manager perhaps?
2. Renamed blurupdater_VZW.apk to .bak to block updates
3. Any "landmines" I should NOT uninstall?
Sorry if I sound noobish but this is my only phone number and am proceeding cautiously.
Thanks
skeeterpro said:
Finally worked up the cajones to use Pete's Tools and rooted my DX. *whew*
Doing a complete TiBu right now. Couple quick questions.......
1. Is CWM installed? If so, how does one access. If not, ROM Manager perhaps?
2. Renamed blurupdater_VZW.apk to .bak to block updates
3. Any "landmines" I should NOT uninstall?
Sorry if I sound noobish but this is my only phone number and am proceeding cautiously.
Thanks
Click to expand...
Click to collapse
First of all, let me reassure you that anything you do to your phone can be reversed with a simple SBF. ^_^
Install ClockworkMod Recovery through Droid 2 Bootstrapper, then use ROM Manager to update it to the latest version.
There is plenty of things that you can remove that will cause issues =P It's pretty much trial and error, there are lists you can look up that will tell you what can and can't be removed, but regardless, always make a backup in CWM.
Sent from my DROIDX using XDA App
Thanks again.
Droid 2 Bootstrapper via Android Market will do it, one presumes?
skeeterpro said:
Thanks again.
Droid 2 Bootstrapper via Android Market will do it, one presumes?
Click to expand...
Click to collapse
You are correct.
Sent from my DROIDX using XDA App
I amaze myself sometimes. lol
Has anyone flashed working CWM via ROM Manager?
Can't say I have interest in flashing ROMs. Just want CWM for nandroid system backups actually.
STRANGE!
DroidX, 2.3.3, original Moto ROM, LauncherPro+
First time I did Pete's it worked perfectly.
After .605 OTA it had a problem, so I re-Peted.
Each time Pete tried to reboot the phone, I had to pull the battery. Eventually, the process finished and I had a rooted Droid. It's fast, stable, has fine battery life. TitaniumPro, QuickBoot, and other root-only tools work properly. Various things ask for Superuser permission, and I give it, and they work properly.
But the SUPERUSER app has disappeared. When I go to Market, it says "Installed". It doesn't appear on my app list, and was never frozen. It's there, but invisible.
Everything else works, so should I just leave it alone?
noguru said:
DroidX, 2.3.3, original Moto ROM, LauncherPro+
First time I did Pete's it worked perfectly.
After .605 OTA it had a problem, so I re-Peted.
Each time Pete tried to reboot the phone, I had to pull the battery. Eventually, the process finished and I had a rooted Droid. It's fast, stable, has fine battery life. TitaniumPro, QuickBoot, and other root-only tools work properly. Various things ask for Superuser permission, and I give it, and they work properly.
But the SUPERUSER app has disappeared. When I go to Market, it says "Installed". It doesn't appear on my app list, and was never frozen. It's there, but invisible.
Everything else works, so should I just leave it alone?
Click to expand...
Click to collapse
You should be able to find Superuser by using the search key. It's not really important to have, it just manages the superuser permissions. I think of it as a background app.
Sent from my DROIDX using XDA App
So I'm stuck at the command prompts. I have messed around with several things, and have also updated the usb driver correctly. Where I am stuck at is getting the adb usb.ini file to show up. I can run C: START adb update usb, and something runs for a split second, but after that I'm still unable to get the ini file to show up. Is there something wrong I'm doing?
just follow this tutorial, its noob proof. I hope this helps........
http://rootkindlefire.com/kindle-fire-root/how-to-root-kindle-fire/
its easier then the tut here
Well I've tried both tutorials but for some reason I must be doing something wrong, because I'm unable to get the usb driver.ini file to show up, so that it can be copied and pasted to the .android folder. I was advised that I had to do the adb update usb command in cmd, so i tried START adb update usb but all it does is run something for a split second then nothing shows up. I'm in the correct directory as far as I know, and I tried different directories for about 3 hours last night. I was able to successfully update the usb drivers through device manager, not sure if I was supposed to run the adb usb update before actually updating through device manager?
Then you didn't follow the instructions because the file would automatically be there if you did.
Movieaddict, you are a godsend. I did attempt to do this by watching the Youtube vid, but the link you sent me actually just showed pictures of what to do. It worked! Now I just have to figure out what to do now that it's rooted lol. Thanks so much!
jtb224 said:
Well I've tried both tutorials but for some reason I must be doing something wrong, because I'm unable to get the usb driver.ini file to show up, so that it can be copied and pasted to the .android folder. I was advised that I had to do the adb update usb command in cmd, so i tried START adb update usb but all it does is run something for a split second then nothing shows up. I'm in the correct directory as far as I know, and I tried different directories for about 3 hours last night. I was able to successfully update the usb drivers through device manager, not sure if I was supposed to run the adb usb update before actually updating through device manager?
Click to expand...
Click to collapse
Ifd u follow the tut i posted u really cant go wrong, seriously!
why when im trying to install the cm7 on the kindle in the cmd appears this error:
cp: can't stat ' /sdcard/log' : No such file or directory
Please help!
are you on recovery process? I have the same situation, when I try to instal CM7, I instaled recovery first, my be there's a mistake for "log" file, now I can't exit recovery. For I have changed boot mode "idme bootmode 0x5001", it still boot into recovery process when I try to restart it.
Please help.
i am in the beginning of the process and have this error :s
Sent from my Kindle Fire using Tapatalk
Soooo...I'm back again. Finished the root process, everything went hunky-dory until I actually tried to install something from the Android Market. Now everything force closes from Android Market, though my Amazon market still works. Also my games are force closing as well. The only way I can actually get back into the Market is if I clear all data to it, then can do searches. Also with my games, I am completely unable to get to work even after reinstalling them. Any ideas?
jtb224 said:
Soooo...I'm back again. Finished the root process, everything went hunky-dory until I actually tried to install something from the Android Market. Now everything force closes from Android Market, though my Amazon market still works. Also my games are force closing as well. The only way I can actually get back into the Market is if I clear all data to it, then can do searches. Also with my games, I am completely unable to get to work even after reinstalling them. Any ideas?
Click to expand...
Click to collapse
try installing app vending.apk
Sent from my Kindle Fire using Tapatalk
The way I fixed that problem for me was updating market apk
Sent from my Kindle Fire using xda premium
FYI this is solved.
1. Install drivers can be found here: http://d-h.st/fBw or when you first plug your phone into PC, within the virtual drive: \tools\LG VZW_United_WHQL_v2.11.1.msi file
2. Next make sure to switch to Internet connection --- ethernet within PC Connection settings
3. command prompt and type adb devices, you should see your Serial Number and online.
4 Now that we know ADB is working the process is the same, download this: http://www.mgyun.com/vroot
5. Yes it is in chinese, install it, then run it while your phone is plugged into your USB port on your PC.
6, The program will do some checks once its finished it will pop a screen that has the model number of the phone LG-D800 and a check mark. Notice the button on the bottom right, it says ROOT with some chinese lettering.
7. Click it and wait, the phone will reboot after a couple minutes. Once it reboots you will be rooted. Also it will install a Chinese language Root Manager. This is temporary.
8. Now we will replace the Chinese binary with an English one. Download superuser by clockworkmod from the play store. Open it and grant root permission (right button when the window pops up in Chinese). Superuser will ask to update the binary, hit install. Now exit by swiping superuser out of recents.
9. Now open titanium backup, install from play store if you don't have it. Find the Chinese root manager app and either uninstall it or freeze it.
10. Next open superuser again and once again install the superuser binary when asked. Reboot. You should now be rooted in English.
11. Optionally you can install Busybox with Busybox installer like I did.
Initially this did not work for me....i had to take the below steps to get it to work.
After rooting with app and installing CWM superuser
-open CWM SU
-allow root
-update binaries
-go to settings -> app manager -> select cwm su and force close it (do not just swipe it away in recents)
-open titanium bu and freeze the chinese version
-open cwm su again and update binaries again
-reboot
-open titanium and uninstall the chinese version
Original Question:
Does anyone have adb properly detecting their VZW G2 on Windows 8? Windows 8 is using a driver that is built into Win8, and I haven't found a way to get ADB working because of it. It shows up and works fine as an MTP device, and in device manager (as seen below). If anyone gets this working please let me know what you did.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you tried the ones on LG's site?
http://algmcdn.lgmobile.com/dn/downloader.dev?fileKey=UW00120120425
Huskehn said:
Have you tried the ones on LG's site?
http://algmcdn.lgmobile.com/dn/downloader.dev?fileKey=UW00120120425
Click to expand...
Click to collapse
I can't even get it to see my device on windows 7...not sure you're going to get far at the moment.
Yea i've tried the drivers from LG's site and the drivers that come on the phone itself. Definitely no luck so far.
Darkestred said:
I can't even get it to see my device on windows 7...not sure you're going to get far at the moment.
Click to expand...
Click to collapse
Same here. With Dev. Options and ADB enabled, nothing shows on Windows 7 (I'm assuming all versions of Windows). It would seem to me that there is a software issue and VZW needs to give us an update ASAP. This is total bull. I'm a developer and I want to use my phone to develop, that is one of the key points of Android.
drkow19 said:
Same here. With Dev. Options and ADB enabled, nothing shows on Windows 7 (I'm assuming all versions of Windows). It would seem to me that there is a software issue and VZW needs to give us an update ASAP. This is total bull. I'm a developer and I want to use my phone to develop, that is one of the key points of Android.
Click to expand...
Click to collapse
Software update would probably break current root method though sadly.
bose301s said:
Software update would probably break current root method though sadly.
Click to expand...
Click to collapse
ADB > root! ADB is usually essential to achieve root anyway.
It turns out this seems to be an issue with the Verizon G2 not actually enabling USB Debugging mode when it's checked. Refer to the thread below.
http://forum.xda-developers.com/showthread.php?p=45556319
emplox said:
It turns out this seems to be an issue with the Verizon G2 not actually enabling USB Debugging mode when it's checked. Refer to the thread below.
http://forum.xda-developers.com/showthread.php?p=45556319
Click to expand...
Click to collapse
This sucks, now we wait for a software update... without the ability to use ADB or any way to fix it. Oh well, worse things have happened.
I just got off the phone with LG. They specifically told me that there are no drivers that currently work on the VZW G2 and they should have the released 'in less than a week' and it should solve all ADB issues. Not sure I believe it...but I guess we'll see.
emplox said:
Does anyone have adb properly detecting their VZW G2 on Windows 8? Windows 8 is using a driver that is built into Win8, and I haven't found a way to get ADB working because of it. It shows up and works fine as an MTP device, and in device manager (as seen below). If anyone gets this working please let me know what you did.
Click to expand...
Click to collapse
Can you right click the device in Device Manager, then click Properties.
I think the answer is in the Details tab, if you drop down the Property list and choose Hardware IDs.
I have a feeling the ID in there (for the VZW variant) is NOT in the driver installation file from LG (yet, anyway)
chrisexv6 said:
Can you right click the device in Device Manager, then click Properties.
I think the answer is in the Details tab, if you drop down the Property list and choose Hardware IDs.
I have a feeling the ID in there (for the VZW variant) is NOT in the driver installation file from LG (yet, anyway)
Click to expand...
Click to collapse
FYI this is solved.
1. Install drivers can be found here: http://d-h.st/fBw or when you first plug your phone into PC, within the virtual drive: \tools\LG VZW_United_WHQL_v2.11.1.msi file
2. Next make sure to switch to Internet connection --- ethernet within PC Connection settings
3. command prompt and type adb devices, you should see your Serial Number and online.
4 Now that we know ADB is working the process is the same, download this: http://www.mgyun.com/vroot
5. Yes it is in chinese, install it, then run it while your phone is plugged into your USB port on your PC.
6, The program will do some checks once its finished it will pop a screen that has the model number of the phone LG-D800 and a check mark. Notice the button on the bottom right, it says ROOT with some chinese lettering.
7. Click it and wait, the phone will reboot after a couple minutes. Once it reboots you will be rooted. Also it will install a Chinese language Root Manager. This is temporary.
8. Now we will replace the Chinese binary with an English one. Download superuser by clockworkmod from the play store. Open it and grant root permission (right button when the window pops up in Chinese). Superuser will ask to update the binary, hit install. Now exit by swiping superuser out of recents.
9. Now open titanium backup, install from play store if you don't have it. Find the Chinese root manager app and either uninstall it or freeze it.
10. Next open superuser again and once again install the superuser binary when asked. Reboot. You should now be rooted in English.
11. Optionally you can install Busybox with Busybox installer like I did.
Initially this did not work for me....i had to take the below steps to get it to work.
After rooting with app and installing CWM superuser
-open CWM SU
-allow root
-update binaries
-go to settings -> app manager -> select cwm su and force close it (do not just swipe it away in recents)
-open titanium bu and freeze the chinese version
-open cwm su again and update binaries again
-reboot
-open titanium and uninstall the chinese version
ok i'm having issues with getting adb to find my device and this is an old thread and the chinese root wasn't working right. anyway to get the phone to list in adb yet, not using the chinese method?
Edit: could drivers from my previous phone have anything to do with this?
Edit2: Still could use an answer just in case, but i just realized that i haven't had to use adb on a device since before 4.2.2 so i possibly need to update my abd from pdanet, so i'll give that a go later tonight. but any other help would be appreciated. thanks in advance
drkow19 said:
Same here. With Dev. Options and ADB enabled, nothing shows on Windows 7 (I'm assuming all versions of Windows). It would seem to me that there is a software issue and VZW needs to give us an update ASAP. This is total bull. I'm a developer and I want to use my phone to develop, that is one of the key points of Android.
Click to expand...
Click to collapse
I have the T-Mobile G2 and have the same issue, my PC won't recognize the device. Wth?!?
Sent from my LG-D801 using xda app-developers app
bigox said:
I have the T-Mobile G2 and have the same issue, my PC won't recognize the device. Wth?!?
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
We figured out how to enable ADB a while ago. You need to plug in your phone to PC, select Internet then Ethernet (or something similar) instead of Media Sync or Charge Only. Also ADB must be enabled in Settings. Then, it should show in PC devices, you can install the Google ADB driver, and use ADB. First time using it, your phone should pop up with an RSA key window to allow ADB.
1. Install drivers can be found here: http://d-h.st/fBw
downloaded this file but i dont see how to install it. no .exe or anything
how do i install drivers? http://i.imgur.com/J5dax87.png
thanks
emplox said:
FYI this is solved.
1. Install drivers can be found here: http://d-h.st/fBw or when you first plug your phone into PC, within the virtual drive: \tools\LG VZW_United_WHQL_v2.11.1.msi file
2. Next make sure to switch to Internet connection --- ethernet within PC Connection settings
3. command prompt and type adb devices, you should see your Serial Number and online.
4 Now that we know ADB is working the process is the same, download this: http://www.mgyun.com/vroot
5. Yes it is in chinese, install it, then run it while your phone is plugged into your USB port on your PC.
6, The program will do some checks once its finished it will pop a screen that has the model number of the phone LG-D800 and a check mark. Notice the button on the bottom right, it says ROOT with some chinese lettering.
7. Click it and wait, the phone will reboot after a couple minutes. Once it reboots you will be rooted. Also it will install a Chinese language Root Manager. This is temporary.
8. Now we will replace the Chinese binary with an English one. Download superuser by clockworkmod from the play store. Open it and grant root permission (right button when the window pops up in Chinese). Superuser will ask to update the binary, hit install. Now exit by swiping superuser out of recents.
9. Now open titanium backup, install from play store if you don't have it. Find the Chinese root manager app and either uninstall it or freeze it.
10. Next open superuser again and once again install the superuser binary when asked. Reboot. You should now be rooted in English.
11. Optionally you can install Busybox with Busybox installer like I did.
Initially this did not work for me....i had to take the below steps to get it to work.
After rooting with app and installing CWM superuser
-open CWM SU
-allow root
-update binaries
-go to settings -> app manager -> select cwm su and force close it (do not just swipe it away in recents)
-open titanium bu and freeze the chinese version
-open cwm su again and update binaries again
-reboot
-open titanium and uninstall the chinese version
Click to expand...
Click to collapse
Having the same problem
I have the Verizon phone and tried using the 3.1.1 driver on Windows 7 (latest driver linked on the rooting post). When I went to the LG website and downloaded the 2.11.1 driver there, everything worked perfectly and I can see the phone on the PC using ADB devices command.
question:
emplox said:
FYI this is solved.
1. Install drivers can be found here: http://d-h.st/fBw or when you first plug your phone into PC, within the virtual drive: \tools\LG VZW_United_WHQL_v2.11.1.msi file
2. Next make sure to switch to Internet connection --- ethernet within PC Connection settings
3. command prompt and type adb devices, you should see your Serial Number and online.
4 Now that we know ADB is working the process is the same, download this: http://www.mgyun.com/vroot
5. Yes it is in chinese, install it, then run it while your phone is plugged into your USB port on your PC.
6, The program will do some checks once its finished it will pop a screen that has the model number of the phone LG-D800 and a check mark. Notice the button on the bottom right, it says ROOT with some chinese lettering.
7. Click it and wait, the phone will reboot after a couple minutes. Once it reboots you will be rooted. Also it will install a Chinese language Root Manager. This is temporary.
8. Now we will replace the Chinese binary with an English one. Download superuser by clockworkmod from the play store. Open it and grant root permission (right button when the window pops up in Chinese). Superuser will ask to update the binary, hit install. Now exit by swiping superuser out of recents.
9. Now open titanium backup, install from play store if you don't have it. Find the Chinese root manager app and either uninstall it or freeze it.
10. Next open superuser again and once again install the superuser binary when asked. Reboot. You should now be rooted in English.
11. Optionally you can install Busybox with Busybox installer like I did.
Initially this did not work for me....i had to take the below steps to get it to work.
After rooting with app and installing CWM superuser
-open CWM SU
-allow root
-update binaries
-go to settings -> app manager -> select cwm su and force close it (do not just swipe it away in recents)
-open titanium bu and freeze the chinese version
-open cwm su again and update binaries again
-reboot
-open titanium and uninstall the chinese version
Original Question:
Does anyone have adb properly detecting their VZW G2 on Windows 8? Windows 8 is using a driver that is built into Win8, and I haven't found a way to get ADB working because of it. It shows up and works fine as an MTP device, and in device manager (as seen below). If anyone gets this working please let me know what you did.
Click to expand...
Click to collapse
will this work for d800 d80010o?
does this ( VZW LG G2 Drivers) work for at&t g2 also?
It will works for Sprint LS980?
Working Root Method For your Memo Pad 7
1. Extract the File from http://www.mediafire.com/download/lp7ngv5l6vm5lin/AsusIntelRootKit.zip
2. Have Debugging Mode Enable (Setting>About>Software Information>7 Clicks on the Build Number)
Back to Settings>Developer Options and select USB DEBUGGING
3. Open the extracted folder and click "Root" (Follow the instructions)
Your Rooted
Dont update the superuser app!!!!
Install Busybox from the play store
Install and Reboot
Check with root checker
ADB Driver for Asus http://www.mediafire.com/download/u46c7zwf2k2xjr8/AsusADBdrivers.zip
JarrelStudios said:
Working Root Method For your Memo Pad 7
1. Extract the File from http://www.mediafire.com/download/lp7ngv5l6vm5lin/AsusIntelRootKit.zip
2. Have Debugging Mode Enable (Setting>About>Software Information>7 Clicks on the Build Number)
Back to Settings>Developer Options and select USB DEBUGGING
3. Open the extracted folder and click "CheckBeforeActivation" (Follow the instructions)
4. When Device Restarts unlock screen and go back to the same folder and click Root....
Your Rooted
Dont update the superuser app!!!!
Install Busybox from the play store
Install and Reboot
Check with root checker
ADB Driver for Asus http://www.mediafire.com/download/u46c7zwf2k2xjr8/AsusADBdrivers.zip
Click to expand...
Click to collapse
Thanks for the completely bland and incorrect Guide! Nowhere in that ZIP archive is a file called "CheckBeforeActivation". With many hundreds of thousands of these devices in the marketplace, do your fellow XDA members and GET YOUR FACTS STRAIGHT BEFORE YOU POST!!!:silly:
The file was removed as it was it copy of another file
Sent from my K013 using XDA Free mobile app
This method works on my zenfone 4 where else fail using fastboot zip file method
Thanks for posting this!
how come you cant update supersu??
I tried this method to root my device, I have a BBY build. The application says it rooted okay. When I reboot the device and try to install BusyBox it says it doesn't get a response from the device. When I check root with Root Checker Basic it says that the device is not rooted. Any thoughts on what I might be missing?
Is the super user app installed?
Sent from my K013 using XDA Free mobile app
yay, i am now rooted, thankyou for an easy way to do this..
a few questions..
1..how come i cant update the supersu, and how can i prevent this from happening..
2..can i now uninstall the busybox app as its now downloaded the files to the device..
3, is it now safe to uninstall all the asus rubbish on the tablet(what have you uninstalled)
Memo Pad 7 ME572C:
after the latest update 11.8.3.31 (from 11.8.3.30), this root method and the rootzenfone method can no longer root the tablet.
slim_thumb said:
Memo Pad 7 ME572C:
after the latest update 11.8.3.31 (from 11.8.3.30), this root method and the rootzenfone method can no longer root the tablet.
Click to expand...
Click to collapse
Ahh, thanks for this. What I was looking for. I did the update, and now regretting it lol.
I would also like to know why we can't update SuperUser
onimorza said:
I would also like to know why we can't update SuperUser
Click to expand...
Click to collapse
its safe to update it now..before it would remove superuser and you would have to factory reset the re-root
To the OP, it looks like you just reposted the work of twenty-three pin from here:
https://translate.google.de/transla...sts/247110-merry-christmas&edit-text=&act=url
Too bad when you were stealing someone else's work you didn't work slowly enough to notice that he mentions that the Asus 572C should use V2 of his work:
http://www.mediafire.com/download/ui9ipe786dulj98/AsusIntelRootKitv2.zip
Hope this helps someone.
If you check the commands int the .bat file, you will see they are different... Its just basic fastboot commands. And as of recent updates the me572 can't be rooted using this method. So I'll head back to the drawing board as soon as I get time to
Sent from my K013 using XDA Free mobile app
I honestly haven't seen that post before
Sent from my K013 using XDA Free mobile app
JarrelStudios said:
its safe to update it now..before it would remove superuser and you would have to factory reset the re-root
Click to expand...
Click to collapse
Thanks, but meanwhile I've rooted with this method http://forum.xda-developers.com/memo-pad-7/help/rooting-memo-pad-7-rootzenfone-t3000389 and also updated without problem.
Also no need for ADB with that method.
question
abudabu said:
Ahh, thanks for this. What I was looking for. I did the update, and now regretting it lol.
Click to expand...
Click to collapse
Will this work for ASUS 16GB 8" IPS HD Android Tablet, 1.33GHz Intel Bay Trail-T Z3745 quad-core processor, with kit kat 4.4?
(ME180A-A1-WH)
zach
any method of rooting on stock LP?
will this work with latest WW_K013-12.10.1.33-20150917 ? Lolipop 5.0