Related
My phone has been rebooting many times recently. I have read about people mentioning a logcat when connected via USB. I am keen to help shed light on reboots so want to know what I need to do after a reboot.
Do I simply hook up the phone to my PC via USB and run a command to dump some sort of error log file?
Darren
ADB is your friend
DarrenNewsgroup said:
Do I simply hook up the phone to my PC via USB and run a command to dump some sort of error log file?
Darren
Click to expand...
Click to collapse
Yes. You shall use ADB for viewing log from PC.
I use the ADB included with SuperOneClick 2.1.1
Download it from here: ftp://shortfuse.org/SuperOneClick/Packages/SuperOneClickv2.1.1-ShortFuse.zip
Inside the zip there is an ADB folder. First, if on windows, try just invoking adb.exe from a command prompt (cmd), it will spit out the parameters.
For log viewing, connect USB to phone and start "adb.exe logcat".
If you want to redirect the output to a file, you can use "adb logcat > output.log", for example.
Cheers,
timara
*****To all newebies(as quite a few new people are at this forum because they got their first device! (TFP)) any anyone who wants to learn, let’s get educated about our devices!*****
ADB (Android Debug Bridge) is an extremely useful tool that WILL help you in all of your customizing needs! You may see the need to use ADB commands to help root your device, change ROMS, or send your device a fix. Without the knowledge here, you could easily be left in the dark.
ADB is a necessity for developers and general consumers alike. Knowing this tool is a great advantage to you to help your device at the best quality possible.
Installation
Download Google SDK
Choose the correct operating system and install!
The installation REQUIRES Java JDK which can be downloaded from Here
If during installation it asks for JDK (and you have installed it) Press the back button and next again, sometimes that will fix the error.
**Note** The SDK installs to C:\Program Files (x86)\Android\android-sdk standard, chose any directory for you
Start the SDK and immediately, you will notice a few checkboxes. For the standard user, just make sure Android SDK Platform-tools (under Tools) and Google USB Driver package (under Extras) – the drivers are always good to have, latest ADB drviers.
Click install 2 packages and wait. Once installed go to your installation directory and find the platform-tools folder. This directory is your ADB and will be your lifeline!
**Do you want ADB accessible through any command prompt directory?**
You are in luck. (For Windows 7)
Right click on My Computer > Properties > Advanced System Settings >Advanced (Tab) > Environment Variables > Under System Variables scroll and dbl click on Path
TO THE END of the Variable value line add
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools
Or whatever the directory you installed to + platform-tools
Open CMD and type ADB, if you did it right, you will see proper ADB jargon regardless if you are in the correct directory or not!
Congratulations! ADB is installed!
**Make sure your device is using the latest drivers (that you just downloaded) or other ADB drivers provided by ASUS to access ADB. When connected in Debugging mode, device manager will have: ASUS Android Composite ADB Interface**
ADB Usage
**I will be talking mainly about commands/arguments that the general end-user may use or come across**
**Make sure your tablet is in USB Debugging Mode to be able to connect to ADB (Settings > Applications)**
ADB Devices : This command shows all connected android devices that will respond to an ADB command. It is useful for making sure your device is connected.
ADB Connect [IPORT] : This command will connect to your device over personal WIFI connection if your device is setup for ADB over WIFI (Requires root and NOT recommended)
ADB Push [local_file] [remote_file] : This command will push any local file to the device (only if the device is Read/Writable. Stock /system/ folders are only Readable.
ADB Pull [Remote_file or Directory] [Save file or Directory] : This command take files or an entire directory and save it to your desired location. This command only works when directory is read/Writable.
ADB Shell [command] : This command will perform most UNIX commands on the device. Without a command, you can enter several shell commands before you ‘exit’. Most will not work unless SU is applied (# instead of $). Must be rooted for SU. Only play with these commands if they are known by you or exactly copied from instructions.
ADB Logcat [ > file.txt ] : This command will display (or save per > file.txt) a log of what’s happening on the device. If you are receiving errors, turn on logcat, reproduce error, turn off, and send logcat to the developer.
ADB Install [-r][-s] [local_apk] : This command force installs (or reinstalls –r or –s installs on SD-Card) any APK provided.
ADB Uninstall [-k] [APK_Name] : This command uninstalls any APK Name provided (app.apk) and will even keep cache and other data with the –k tag.
ADB start-server : This command will start the server if the server is off or killed. (Normally server will auto-start when ADB command is used)
ADB kill-server : This command will close ADB server. Useful if ADB server is acting up or not connecting to any devices.
ADB remount : This command will mounts the /system/ partition Read/Writable pending the device is allow to. Stock TFP will NOT.
ADB root : This command will restart ADB with root permissions if the build allows for it. Stock TFP will NOT.
ADB usb : This command will restart ADB on device to use USB connection for ADB communication.
ADB tcpip [port] : This command will restart ADB on device to use TCPIP connection for ADB. Standard port is 5555. Again, this connect not recommended for file transfers.
ADB reboot [recovery/bootloader] : This command will restart your device. If either of the two options are given, the device will boot into that mode (sadly TFP does not support the two options.. yet)
ADB Tips/Tricks
When following ADB instructions, follow them WORD-BY-WORD in the EXACT ORDER GIVEN. If copy and pasting their commands (one line at a time) makes it easier, then do so.
If you have root access, do not mess around in ADB shell unless you know what you are doing
Connecting over IP can be beneficial for you for quick ADB access, but for file transfers, speed is slow and you ALWAYS risk corruption (check the md5!) One bad file and you have boot-loops!
ADB Logcat is an amazing command. If anything is wrong with your device, 9/10 you can see it in logcat. If you can find the exact problem, fixes can happen much easier. USE LOGCAT TO YOUR ADVANTAGE!
ADB reboot can be a quick reboot, sometimes you don’t feel like waiting!
Use the environmental variables! It helps exponentially, and keeps from having multiple instances of ADB running.
When multiple instances of ADB are running (different directories) ADB can get messed up! (ADB not up-to-date restarts, and connect problems). ASUS Sync service has and ADB setup. Turn it off if you are not using it. Try to stick to only ONE instance of ADB
Eventually, we may have root access in our recovery kernel. Then and only then can our devices be truly customizable!
The GUIDE is not finite. Please post anything you feel should be added/corrected to the guide. Please take notice from this, as the understanding of these simple commands could help save your device(s)!
Thanks and 5 star would make me feel good inside too!
Wow... Nice post. Lots of time went into this lol. Thanks can't give the five stars in the app though:-(
Sent from my Transformer Prime TF201 using xda premium
The link in step #1 is whack - I think you want tis? http://developer.android.com/sdk/index.html
Lock-N-Load said:
The link in step #1 is whack - I think you want tis? http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
hmm thats what was in there, i re-saved and it works now ... maybe xda error
thanks tho!
biggem001 said:
hmm thats what was in there, i re-saved and it works now ... maybe xda error
thanks tho!
Click to expand...
Click to collapse
before you fixed it, it was trying to use this http://http://developer.android.com/sdk/index.html"
note the extra parens at the end and the double http call
i noticed that too, all i did was re-save and it worked. how weird.
Thanks! I've seen a few tutorials on this but this one was by far the easiest to follow and best organized. Short and sweet. Worked on my desktop great, I've never managed to install it right D:
Re posting to give 5 stars. Thanks again OP
Quick question: Is it normal for PTP mode to be required for adb to work? Because as soon as I switch to MTP I can no longer use adb.
cmat1120 said:
Quick question: Is it normal for PTP mode to be required for adb to work? Because as soon as I switch to MTP I can no longer use adb.
Click to expand...
Click to collapse
i can do either at once.. thats weird
GPS, Wifi and BT Testing
Could someone write some basic tutorials on how to verify/test GPS, wifi and BT funtions? For those of us who are new to Android it would helpful in verifying which problems are truly present. Also perhaps show how to find the serial number - for example: some don't know you have to click status - because there are a some erroneous posts out there. There may be users who assume something works or doesn't work, based on limited knowledge and these inaccurate findings only serve to muddy up the works.
There's a lot of animosity about the influx of newbies (and trust me, as a newbie it doesn't feel good). I think the first step is to educate. If some of these troubleshooting steps are laid out, more people can contribute in an intelligent way.
I thought this would be a good thread for the Guides thread, but it is closed and I cannot send PMs.
Thanks - Great Info
One thing you can add for all us amateurs is how to use ADB to install off market apps, stuff like that. Things the non-power user can benefit from. Some simple command line structure would be great.
theandies said:
One thing you can add for all us amateurs is how to use ADB to install off market apps, stuff like that. Things the non-power user can benefit from. Some simple command line structure would be great.
Click to expand...
Click to collapse
i wont add it to the guide, because adb install is pretty self explanatory but this
make sure you can install non-market apps
Code:
adb install app.apk
jonalisa said:
Could someone write some basic tutorials on how to verify/test GPS, wifi and BT funtions? For those of us who are new to Android it would helpful in verifying which problems are truly present. Also perhaps show how to find the serial number - for example: some don't know you have to click status - because there are a some erroneous posts out there. There may be users who assume something works or doesn't work, based on limited knowledge and these inaccurate findings only serve to muddy up the works.
There's a lot of animosity about the influx of newbies (and trust me, as a newbie it doesn't feel good). I think the first step is to educate. If some of these troubleshooting steps are laid out, more people can contribute in an intelligent way.
I thought this would be a good thread for the Guides thread, but it is closed and I cannot send PMs.
Click to expand...
Click to collapse
for GPS, use GPS Test app on the market
for BT and wifi testing, i'll just connect my device via BT or adhoc wifi and do the testing on my PC itself, more accurate and better programs
Excellent howto, thanks
I have trouble connecting to my prime with adb. In the Win7 Device Manager the correct device shows up, no exclamation mark at all, but adb just won't see the Prime.
USB debugging mode is on, no Asus Sync software on the PC. I have no clue why ADB won't see my device.
Now many of us can really shoot ourself in the foot.
by far the best and quickest adb install/setup ever. thanks OP!
neo1738 said:
by far the best and quickest adb install/setup ever. thanks OP!
Click to expand...
Click to collapse
aw shucks!
THANKS!
biggem001 said:
ADB Devices : This command shows all connected android devices that will respond to an ADB command. It is useful for making sure your device is connected.
ADB Connect [IPORT] : This command will connect to your device over personal WIFI connection if your device is setup for ADB over WIFI (Requires root and NOT recommended)
ADB Push [local_file] [remote_file] : This command will push any local file to the device (only if the device is Read/Writable. Stock /system/ folders are only Readable.
ADB Pull [Remote_file or Directory] [Save file or Directory] : This command take files or an entire directory and save it to your desired location. This command only works when directory is read/Writable.
ADB Shell [command] : This command will perform most UNIX commands on the device. Without a command, you can enter several shell commands before you ‘exit’. Most will not work unless SU is applied (# instead of $). Must be rooted for SU. Only play with these commands if they are known by you or exactly copied from instructions.
ADB Logcat [ > file.txt ] : This command will display (or save per > file.txt) a log of what’s happening on the device. If you are receiving errors, turn on logcat, reproduce error, turn off, and send logcat to the developer.
ADB Install [-r][-s] [local_apk] : This command force installs (or reinstalls –r or –s installs on SD-Card) any APK provided.
ADB Uninstall [-k] [APK_Name] : This command uninstalls any APK Name provided (app.apk) and will even keep cache and other data with the –k tag.
Click to expand...
Click to collapse
Just a small suggestion, adb won't accept commands if they are capitalized.
For example "ADB devices" will work perfectly, but "ADB Devices" won't.
So, in order to help the newest of newbies, you might want to put the commands in lowercase in the first post.
So i have been trying to root my tprime for about a couple days now and i really need some help. Im trying to use Vipers tool (option 1), however every time i try to use it it just gets stuck on "daemon started successfully". Every now and then the script will flip out and tell me that it isnt connected, but that is pretty rare. I'm on 9.4.2.15, have debugging checked, no lockscreen (saw it helps somewhere), device manager recognizes it as "asus transformer prime ADB interface". I have tried 2 different scripts and restarted both my tablet and computer (windows 7 x64) several times. I am at a total loss about what to do next. Any help would be great =).
Also i have deleted splashtop from my computer and made sure that and asussync are not running on my tablet
lotsofllamas said:
So i have been trying to root my tprime for about a couple days now and i really need some help. Im trying to use Vipers tool (option 1), however every time i try to use it it just gets stuck on "daemon started successfully". Every now and then the script will flip out and tell me that it isnt connected, but that is pretty rare. I'm on 9.4.2.15, have debugging checked, no lockscreen (saw it helps somewhere), device manager recognizes it as "asus transformer prime ADB interface". I have tried 2 different scripts and restarted both my tablet and computer (windows 7 x64) several times. I am at a total loss about what to do next. Any help would be great =).
Also i have deleted splashtop from my computer and made sure that and asussync are not running on my tablet
Click to expand...
Click to collapse
Update your ADB drivers in device manager with the following
http://forum.xda-developers.com/showthread.php?t=1426502
Make sure USB Debugging is enabled within your TFP's settings (Developer options)
If that does not work then you have done something wrong.
Have a nice day
that didnt work >< but i have no idea where i couldve done something wrong...especially since i have had to re-do most steps anyway
lotsofllamas said:
that didnt work >< but i have no idea where i couldve done something wrong...especially since i have had to re-do most steps anyway
Click to expand...
Click to collapse
Well if you really want this, I would suggest the following:
We want to verify that your devices is correctly connect with ADB,(assuming you dont have adb set up) so lets set up Android SDK (which is good to do anyway).
http://developer.android.com/sdk/index.html
Download the .exe. Run it. It should create a folder in a location of your choosing, named something like "android-sdk". Browse to that folder, then to the 'tools' sub folder and run the SDK manager, install packages.
Next open the Command Prompt.
For example sake, lets say the location of your AndroidSDK is in the path
Code:
C://users/mike/android-sdk-win/
(Not sure what the sdk folder is actually called)
In the command prompt, enter
Code:
cd /users/mike/android-sdk-win/tools
(again replacing the location and name with the correct ones)
This will change the cmd location to the tools folder.
Then enter
Code:
adb devices
It will then list a device if one exists, if not then your adb drivers are probably not installed correctly.
If you need me to clear anything up, let me know
you were right i wasnt connected, im not quite sure how im doing anything wrong
installed the drives said to
unzipped
went into device manager -update driver software -browse -lemme pick -have disk-android_winusb -ok -comes up as ADB interface -next -finishes installing
try to run viperMOD PrimeTime v4.5 (option 1)
stalls on daemon started successfully
i figure if i go into as much detail as possible maybe this can get solved =(
lotsofllamas said:
you were right i wasnt connected, im not quite sure how im doing anything wrong
installed the drives said to
unzipped
went into device manager -update driver software -browse -lemme pick -have disk-android_winusb -ok -comes up as ADB interface -next -finishes installing
try to run viperMOD PrimeTime v4.5 (option 1)
stalls on daemon started successfully
i figure if i go into as much detail as possible maybe this can get solved =(
Click to expand...
Click to collapse
Hmm, I am really not sure. Sounds like you have done everything right.
adb devices is showing no devices which means viperMOD will not work.
When you plug the prime into your computer, on your prime,go to the notification bar and hit on the usb notification (not pc sync, the usb one), and when the settings menu opens up, which box is checked? MTP or PTP? if ones not working, try the other
if all else fails,
try it on another computer maybe?
lotsofllamas said:
you were right i wasnt connected, im not quite sure how im doing anything wrong
installed the drives said to
unzipped
went into device manager -update driver software -browse -lemme pick -have disk-android_winusb -ok -comes up as ADB interface -next -finishes installing
try to run viperMOD PrimeTime v4.5 (option 1)
stalls on daemon started successfully
i figure if i go into as much detail as possible maybe this can get solved =(
Click to expand...
Click to collapse
I rooted last night on latest version of primetime. I used a very old computer to do it. I had it stall on daemon started successfully at first also. I just unplugged the prime connection to PC and plugged it in again. then restarted the primetime program. worked for me. seems like everything you did is right. I guess sometimes the program acts funny. try to run and if it stalls just unplug connection to PC. close out app. then plug back up. open program and try again. it'll catch. I notice it'll stall if you keep trying to root after repeated ffailed attempts. close out the exe. then try again.
demandarin said:
I rooted last night on latest version of primetime. I used a very old computer to do it. I had it stall on daemon started successfully at first also. I just unplugged the prime connection to PC and plugged it in again. then restarted the primetime program. worked for me. seems like everything you did is right. I guess sometimes the program acts funny. try to run and if it stalls just unplug connection to PC. close out app. then plug back up. open program and try again. it'll catch. I notice it'll stall if you keep trying to root after repeated ffailed attempts. close out the exe. then try again.
Click to expand...
Click to collapse
It has nothing to do with the Prime time. As he has said, he got the android sdk setup and confirmed that "adb devices" shows no device, which lends itself to his device or drivers not being installed correctly.
Again, nothing to do with vipermod
everything to do with how he is connected (and i think he tried 'unplugging and replugging')
-------------------------------------
Lets Try this. The following may look intimidating but its very straight forward and after its done you will be more adept at adb and everything else (and hopefully be rooted)
1) Start=> Right Click "My Computer" => Properties => Advance System Settings => Advanced Tab=> Environmental Variables
---In the top box, there should be a "PATH" variable, if so hit edit and go to the end of whatever is there (make sure there is a ';' after whatever is there) and type the path to your android SDK tools folder (same folder you browsed to before in cmd)
My PATH Field looks like this
Code:
C:\Users\Mike\Downloads\android-sdk_r16-windows\android-sdk-windows\platform-tools\; C:\Program Files\Java\jre7\bin
(I also have java linked, this is okay if you do not)
If there is no PATH, just hit 'new'
The above allows you to, from command prompt, type "adb" from anywhere (ie, you dont have to be in the sdk folder which is nice)
EDIT: FLAW: the following app required root womp. I guess keep trying with the USB{
-Go to Device Manager, Uninstall Your TFP, before hitting refresh go to add new devices and select the drivers and what not.
-I will continue to try to think of an alternate method.
}
2)Download and Install this on your prime (NOTE THIS STEP REQUIRES BOTH PRIME AND PC TO BE ON SAME NETWORK)
-This method is ADB over wireless, so you dont need USB to be connected (infact just unplug it for this)
https://market.android.com/details?...251bGwsMSwyLDEsInNpaXIuZXMuYWRiV2lyZWxlc3MiXQ..
Open the app and enable it. Note the "IP: port"
type in your command prompt (again if you did step 1, you can do this from anywhere)
Code:
adb connect <yourip:port>
your ip and port should be listed in that app
=> after that, try
Code:
adb devices
It should be there! this allowed you to bypass usb issues. I dont think you can use vipermod, but there is a more manual method we can use
3) Memphroid Root
(information taken from link below)
http://forum.xda-developers.com/showthread.php?t=1461736
memphroid binary
su binary
save both those files somewhere.. for example sake, make it your desktop in a folder called 'memphroid'
Open command prompt and change to the folder memphroid on your desktop
Code:
cd Desktop/memphroid
(the above assumes command prompt defaults at c:\Users\<yourname>\. if not just type in "dir" to get a list of directories that you can cd to)
you are now in the memphroid folder
assuming you did step 2 correct, you should have already connected with "adb connect"
now enter the following in cmd
Code:
adb push mempodroid /data/local
adb push su /data/local
adb shell
One line at a time, the first 2 push the files to the correct locations, the third one puts you into the 'shell' (basically terminal) of your prime (you should see a # now before where you type)
Then enter
Code:
chmod 777 /data/local/mempodroid
/data/local/mempodroid 0xd9ec 0xaf47 sh
Copy all of that and just paste it at once (i think its both at once, not one line at a time)
then type
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
And then here is the rest from that thread. I would just do all of the following except the first two lines starting with 'rm' because you havent rooted before
** IF you have previously rooted your Prime, run the following two commands. They may throw an error that the file a file was not found.
rm /system/bin/su
rm /system/xbin/su
cat /data/local/su > /system/xbin/su
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local/mempodroid
rm /data/local/su
exit
exit
adb reboot
After your Transformer Prime comes up, install Superuser from android market.
Click to expand...
Click to collapse
look to that thread linked for reference. if you neeed anything clarified or help, just post here. Please read my post carefully, following the step. I tried to be as clear as possible. I have never done the memphroid root before but it looks easy enough
Please hit 'Thanks' button, as I have taken the time to help
Still not able to get root...just tried Debugfs automated root tool and it stalled at "daemon started successfully" im seriously stumped here...
Hi,
Did a search and someone said they were able to root with thecubed method on Mac via Terminal, but I've had no luck so far. Are there any other options for us Mac users?
Thanks
BTW I did see some instructions but it only applies to Verizon. I have the international version D802.
Any help would be greatly appreciated.
use virtual machine and use windows?
I haven't found any easy way to do it, other that running bootcamp and windows on the mac..
You can do it via adb just fine on osx (I'm on snow leopard). You can check which commands to run by opening the Windows script as a text document. It's easy to follow what's going on and has sections for each device
xdabbeb said:
You can do it via adb just fine on osx (I'm on snow leopard). You can check which commands to run by opening the Windows script as a text document. It's easy to follow what's going on and has sections for each device
Click to expand...
Click to collapse
I opened root.bat as a text file but as far as how to input the commands I'm not sure what to do as it seems to differs from the video. Sorry I'm not that familiar working with Terminal.
If you could help out that would be great.
Thanks
xdabbeb said:
You can do it via adb just fine on osx (I'm on snow leopard). You can check which commands to run by opening the Windows script as a text document. It's easy to follow what's going on and has sections for each device
Click to expand...
Click to collapse
Ahhhhh! You know Mavericks is free, right? UPGRADE THAT THING!
On another note... same issue w/ me. I ended up rooting it via my PC, but after that you can use Android File Transfer to manage files and load roms and stuff via OSX.
sell ur POS apple and get a pc...?
digitard said:
Ahhhhh! You know Mavericks is free, right? UPGRADE THAT THING!
On another note... same issue w/ me. I ended up rooting it via my PC, but after that you can use Android File Transfer to manage files and load roms and stuff via OSX.
Click to expand...
Click to collapse
Ha! I haven't upgraded because I still feel snow leopard is the best. I don't like how they've integrated so much ios in the last two, and SL is lean/efficient.
If I have some time I'll write down the commands in a reply. Do you have adb already set up?
xdabbeb said:
Ha! I haven't upgraded because I still feel snow leopard is the best. I don't like how they've integrated so much ios in the last two, and SL is lean/efficient.
If I have some time I'll write down the commands in a reply. Do you have adb already set up?
Click to expand...
Click to collapse
Yes already have adb set up. Thanks for this. Really appreciate it.
No problem. What version of the G2 do you have?
---------- Post added at 11:49 PM ---------- Previous post was at 11:48 PM ----------
Ignore that, I just saw you mentioned the international version
OK, here you go:
1) Go here here and here and thank them both for their work...and read their disclaimers about breaking your phone. The same applies here.
2) Download the attached archive and extract the contents into whatever folder you want...for the purposes of this I'll assume you did so to a directory called ~/D802_OSXroot. If you chose a different directory, modify the steps below accordingly. The archive I attached only contains the appropriate file for the international (D802) LG G2, and I used Chainfire's SuperSU instead of the older ChainsDD su binary and apk. While you're at it, go here and thank him.
3) Make sure USB Debugging is enabled on your phone in Settings>Developer Options
4) Connect your phone via usb cable. You'll get the popup asking what type of connection on your phone. Select Internet connection and then Ethernet when asked. You should see the debugging icon in the status bar of your phone
5) Open terminal on your mac
6) To verify that you are properly connected run the following command:
Code:
adb shell "ls -a /"
you should see the contents of the root of your phone...inlcuding a number of init files. If you do, proceed. If you don't, you have an adb/connection problem.
7) Execute the following in the terminal window to go to the directory where the archive has been extracted on your mac:
Code:
cd ~/D802_OSXroot
8) Execute the following to push the loki exploit file to your phone
Code:
adb push ./g2_security /sdcard/g2_security
9) Unplug your usb cable from the phone
10) On your phone go to Settings>Developer Options and disable USB Debugging
11) Re-enable USB Debugging
12) Plug in your USB cable (follow step 4)
13) Verify adb connectivity (follow step 6)
14) Go back to your terminal window, make sure you are still in the same directory with the files from the archive and execute the following commands in order:
Code:
adb shell "mount -o remount,rw /system"
Code:
adb push ./su /system/xbin/su
Code:
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
Code:
adb install superuser.apk
15) Launch the SuperSU app on your phone. It will likely prompt you to update the su binary...let it do so and then reboot your phone. You should be rooted now.
Good luck!
xdabbeb said:
OK, here you go:
1) Go here here and here and thank them both for their work...and read their disclaimers about breaking your phone. The same applies here.
2) Download the attached archive and extract the contents into whatever folder you want...for the purposes of this I'll assume you did so to a directory called ~/D802_OSXroot. If you chose a different directory, modify the steps below accordingly. The archive I attached only contains the appropriate file for the international (D802) LG G2, and I used Chainfire's SuperSU instead of the older ChainsDD su binary and apk. While you're at it, go here and thank him.
3) Make sure USB Debugging is enabled on your phone in Settings>Developer Options
4) Connect your phone via usb cable. You'll get the popup asking what type of connection on your phone. Select Internet connection and then Ethernet when asked. You should see the debugging icon in the status bar of your phone
5) Open terminal on your mac
6) To verify that you are properly connected run the following command:
Code:
adb shell "ls -a /"
you should see the contents of the root of your phone...inlcuding a number of init files. If you do, proceed. If you don't, you have an adb/connection problem.
7) Execute the following in the terminal window to go to the directory where the archive has been extracted on your mac:
Code:
cd ~/D802_OSXroot
8) Execute the following to push the loki exploit file to your phone
Code:
adb push ./g2_security /sdcard/g2_security
9) Unplug your usb cable from the phone
10) On your phone go to Settings>Developer Options and disable USB Debugging
11) Re-enable USB Debugging
12) Plug in your USB cable (follow step 4)
13) Verify adb connectivity (follow step 6)
14) Go back to your terminal window, make sure you are still in the same directory with the files from the archive and execute the following commands in order:
Code:
adb shell "mount -o remount,rw /system"
Code:
adb push ./su /system/xbin/su
Code:
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
Code:
adb install superuser.apk
15) Launch the SuperSU app on your phone. It will likely prompt you to update the su binary...let it do so and then reboot your phone. You should be rooted now.
Good luck!
Click to expand...
Click to collapse
Has anyone tried this method?
Sent from my LG-D802 using Tapatalk
xdabbeb said:
OK, here you go:
1) Go here here and here and thank them both for their work...and read their disclaimers about breaking your phone. The same applies here.
2) Download the attached archive and extract the contents into whatever folder you want...for the purposes of this I'll assume you did so to a directory called ~/D802_OSXroot. If you chose a different directory, modify the steps below accordingly. The archive I attached only contains the appropriate file for the international (D802) LG G2, and I used Chainfire's SuperSU instead of the older ChainsDD su binary and apk. While you're at it, go here and thank him.
3) Make sure USB Debugging is enabled on your phone in Settings>Developer Options
4) Connect your phone via usb cable. You'll get the popup asking what type of connection on your phone. Select Internet connection and then Ethernet when asked. You should see the debugging icon in the status bar of your phone
5) Open terminal on your mac
6) To verify that you are properly connected run the following command:
Code:
adb shell "ls -a /"
you should see the contents of the root of your phone...inlcuding a number of init files. If you do, proceed. If you don't, you have an adb/connection problem.
7) Execute the following in the terminal window to go to the directory where the archive has been extracted on your mac:
Code:
cd ~/D802_OSXroot
8) Execute the following to push the loki exploit file to your phone
Code:
adb push ./g2_security /sdcard/g2_security
9) Unplug your usb cable from the phone
10) On your phone go to Settings>Developer Options and disable USB Debugging
11) Re-enable USB Debugging
12) Plug in your USB cable (follow step 4)
13) Verify adb connectivity (follow step 6)
14) Go back to your terminal window, make sure you are still in the same directory with the files from the archive and execute the following commands in order:
Code:
adb shell "mount -o remount,rw /system"
Code:
adb push ./su /system/xbin/su
Code:
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
Code:
adb install superuser.apk
15) Launch the SuperSU app on your phone. It will likely prompt you to update the su binary...let it do so and then reboot your phone. You should be rooted now.
Good luck!
Click to expand...
Click to collapse
Thanks for this. I'm having an issue at the first step. I have tested adb when I downloaded the SDK and if I direct the command ./adb devices to that specific folder it can read my phone, but just going into terminal and entering adb shell "ls -a /" al I get is -bash: adb: command not found
Also when I connect my phone to the mac I get options on the G2 but none are internet then ethernet. I get: Charge Phone, Media Sync, Tethering, LG Software, Send Images. The Mac does not ask me what connection I want.
ck37 said:
Thanks for this. I'm having an issue at the first step. I have tested adb when I downloaded the SDK and if I direct the command ./adb devices to that specific folder it can read my phone, but just going into terminal and entering adb shell "ls -a /" al I get is -bash: adb: command not found
Also when I connect my phone to the mac I get options on the G2 but none are internet then ethernet. I get: Charge Phone, Media Sync, Tethering, LG Software, Send Images. The Mac does not ask me what connection I want.
Click to expand...
Click to collapse
It sounds like the first issue may just be due to you not having adb set up properly. If you execute "echo $PATH" in terminal and don't see the android/tools and android/platform-tools directories there, that's the problem. You can either set your path variable to include those directories or just edit the commands I listed accordingly.
The second issue may be due to a difference in the D802 rom vs the VS980. The important thing is that USB Debugging is enabled and that you can access your phone via adb. The 802 may not prompt you in the same way, but if you fix your adb setup the commands will work the same. The rooting method listed (which is the same as thecubed method) is predicated on that working properly.
xdabbeb said:
It sounds like the first issue may just be due to you not having adb set up properly. If you execute "echo $PATH" in terminal and don't see the android/tools and android/platform-tools directories there, that's the problem. You can either set your path variable to include those directories or just edit the commands I listed accordingly.
The second issue may be due to a difference in the D802 rom vs the VS980. The important thing is that USB Debugging is enabled and that you can access your phone via adb. The 802 may not prompt you in the same way, but if you fix your adb setup the commands will work the same. The rooting method listed (which is the same as thecubed method) is predicated on that working properly.
Click to expand...
Click to collapse
I think I figured it out. What I did was transfer the ADB icon from my SDK folder into this one. From there I was able to get access to adb inside the D802 folder. I did have to enter the ./adb as opposed to adb though.
As for the LG I selected tethering as that seemed to be the option similar to the internet/ ethernet choice you mentioned.
All other commands worked accordingly.
Binaries updated for SuperUser as well. At this point how do I get into recovery to upload ROMS etc?
ck37 said:
I think I figured it out. What I did was transfer the ADB icon from my SDK folder into this one. From there I was able to get access to adb inside the D802 folder. I did have to enter the ./adb as opposed to adb though.
As for the LG I selected tethering as that seemed to be the option similar to the internet/ ethernet choice you mentioned.
All other commands worked accordingly.
Binaries updated for SuperUser as well. At this point how do I get into recovery to upload ROMS etc?
Click to expand...
Click to collapse
What I did was installed flashify from the market. This app allows you to backup and then flash a new recovery. Make sure you dl the right one for your device!
Sent from my LG-VS980 using Tapatalk
Having this phone non root is driving me completely insane. No greenifying system apps, bloatware, etc.
Are there any root methods on the computer that root all android phones?
Did you get this rooted yet?
See here: http://forum.xda-developers.com/general/help/lg-transpyre-root-4-4-2-t3021836
Found this to work for me on transpyre
I found this on another web site after almost giving up on my Verizon transpyre vs810pp i followed to the tee with the exception of install su from thr google store cause after root and boot it will b installed so just follow the guide and you to shall have root enjoy and props to the ones that gave us this gift.........
This is not my exploit to take credit for in anyways; and as always do this at your OWN risk. Credits to the creator(s) (I don't know who it is), the finder jgkim, and the translator Unjustified Dev.
Original post here.
A translated post here.
The original posts do not talk about the G3, but it DOES work for the G3. See post #636 and on where it has worked for others besides myself (on this XDA thread.) Tested myself on the VS985 (Verizon G3) and it has worked flawlessly. Others have tested on AT&T G3 (D850) and it has apparently worked fine as well!
I noticed quite a few people upgrading who didn't know much about this, and also quite a few people NOT upgrading because of the lack of root access, well this easy to follow tutorial should help with that. I think the instructions on the XDA post are quite clear and easy to follow, but I decided to post one here out of boredom. Originally I was going to just share the link, but why not? Enjoy.
How to:
Install SuperSU from the Google Play store and install it.
Download these files and extract the contents. I redownloaded all files and packed them together right after to ensure this file is safe. The files are the original rooting-require files along with MFastBoot (Basically adb without the Android SDK installed, it's quick and easier for me since I have not installed the Android SDK). It also includes the latest SuperSU Binary zip straight from the Chainfire website.
Enable USB debugging on your device. (About Phone > Build Number (keep tapping it until it says you are a developer) and then go back to the main settings. Go into developer options and enable USB debugging.)
With your phone screen on: Connect it to your computer via USB cable and put it into PTP mode. (USB debugging should report as on in the status bar.)
With your phone screen on: Hold shift and right click in the folder you extracted and open a command window. (Your phone will soon ask you to allow the computer, hit remember and yes! It may have even asked your prior to this step, just allow it.)
Copy this:
adb push g2_root.sh /data/local/tmp/
Right click in the command window and paste. Hit enter, and wait until it finishes (should take a second.) Now copy this:
adb push busybox /data/local/tmp/
Paste it in the command window and hit enter. Copy this:
adb push UPDATE-SuperSU-v2.46.zip /data/local/tmp/
Paste it in the command window and hit enter.
Leave the command window open and disconnect your device. Turn off the device completely. Hold volume up and connect the USB cable to your device without touching the power button; it will go into download mode.
Find which com port your device is connected to (Device Manager > Ports > Your phone will be there, COM(Number) is what you'll need.
Go back your command prompt, and copy this:
Send_Command.exe \.\COM(CHANGEME)
Replace "(CHANGEME)" with the COM port number of your device. Now copy this:
sh /data/local/tmp/g2_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
Paste it into command prompt and hit enter.
Enjoy your root access! I don't think you can just do "adb reboot", so just disconnect your device and do a battery pull. Put the battery back in and boot up your device. Enjoy root!