[Q] proscan root - Android Q&A, Help & Troubleshooting

Has anyone had a successful root on a plt7602g. I have tried a couple different methods.

Rooting the PLT7602G
sallanm said:
Has anyone had a successful root on a plt7602g. I have tried a couple different methods.
Click to expand...
Click to collapse
Here is a procedure to root the Curtis Proscan PLT7602G tablet (Build number PLT7602G-ANDROID4.2.2-v1.0.0).
1. Install adb on your computer and enable adb on the tablet. http://developer.android.com/tools/help/adb.html
2. Enable ADB on the tablet:
Settings > About Tablet > tap build number 7 times until it says "You are now a developer!"
Developer options > switch On > OK
Check "USB Debugging" > OK​
3. Connect USB and wait for ADB drivers to load on the PC. Using the Google drivers installed with ADB, your system may need manual help to find the right drivers: Go into Windows device manager > Update Driver Software > browse My Computer for driver software > 'Let me pick from a list of devices drivers...' > Pick Android ADB Interface from the model list.
4. You will see a notification "USB Debugging Connected" on the tablet.
5. If this is the first time, you will next see a dialog on the tablet asking "Allow USB debugging?" Check "Always allow from this computer" and click OK.
6. At the command prompt on the computer enter "adb devices". You should see the device listed. If not, reboot the PC and repeat steps 1 through 5 as necessary to get everything working together.
C:\Users\entropy>adb devices
List of devices attached
CD1LBROR50 device
C:\Users\entropy>​7. Download pwn.zip here: http://forum.xda-developers.com/showpost.php?p=53407127
8. Unzip "pwn" from the zip file to your windows current directory
9. At the command prompt on the computer enter the following sequence of commands:
C:\Users\entropy> adb push pwn /data/local/tmp/pwn
C:\Users\entropy> adb shell chmod 755 /data/local/tmp/pwn
C:\Users\entropy> adb shell /data/local/tmp/pwn
Beaups and jcase were here
donations may go here, pleaes say what it was for -> [email protected]​
10. After a few seconds, you should hear the USB disconnect sound, followed by the USB connection sound again.
11. At the command prompt, enter “adb devices” and ensure the device is listed as before. If not, wait a few seconds and then repeat this step.
C:\Users\entropy> adb devices​
12. At the command prompt, enter:
C:\Users\entropy> adb shell​
7. At the shell prompt, enter "su". You should now have a root prompt.
[email protected]:/ $ su
[email protected]:/ #​
8. Exit back out to the command prompt:
[email protected]:/ # exit
[email protected]:/ $ exit
C:\Users\entropy>​
9. On the tablet, go to the play store, download and install the latest SuperSU, or use the Google Play link in this thread: http://forum.xda-developers.com/show....php?t=1538053
10. Open the SuperSU that you just installed. SuperSU will prompt you to install a newer su binary when you run it, so click “Continue” do that, then “Normal”, then “OK”.
11. Reboot the tablet.
The tablet should now be fully rooted. Please let me know if you find any errors or if anything is unclear. I hope you find this useful!

I've downloaded the "Unrevoked" USB driver but the device is not being installed...

Marco Dufal said:
I've downloaded the "Unrevoked" USB driver but the device is not being installed...
Click to expand...
Click to collapse
It has been a while since I got this working and I honestly don't remember exactly what I did to make it work.
Try this... install the official Google driver and reboot:
http://developer.android.com/sdk/win-usb.html
If i still doesn't work, download the adb_usb.ini from here and replace the adb_usb.ini in c:\users\<yourusername>\.android\adb_usb.ini with this one, then reboot and try again. I verified that this adb_usb.ini contains the necessary device ID, so that should definitely do the trick.
https://github.com/apkudo/adbusbini
If you get it working, please post here so others can benefit.

Sice I had already installed the official Google drivers I proceeded with the adb_usb.ini method, but even after rebooting my pc it didn't work... What worked for me was:
Going into window device manager -> Update Driver Software -> browse my computer for driver software -> 'let me pick from a list of devices drivers...' -> Picked Android ADB Interface (from the model list).
I don't get why it did't install it automatically since the driver is actually compatible; did the same thing with another device (Sony experia E1). I got two of them, the first one got recognized while I had to do this process for the second one... Maybe it's my pc fault..
Anyway thank you very much for your replies and the guide. Am I risking to brick the device by following it ?
P.S.
For those who have android studio installed, to run the guide prompt commands you can set an environment variable called 'adb' with this value 'C:\Users\{USERNAME}\AppData\Local\Android\sdk\platform-tools\adb.exe' and easily replacing 'adb' with '%adb%' .
For example : 'C:\Users\{any directory}>%adb% devices'

Marco Dufal said:
Sice I had already installed the official Google drivers I proceeded with the adb_usb.ini method, but even after rebooting my pc it didn't work... What worked for me was:
Going into window device manager -> Update Driver Software -> browse my computer for driver software -> 'let me pick from a list of devices drivers...' -> Picked Android ADB Interface (from the model list).
I don't get why it did't install it automatically since the driver is actually compatible; did the same thing with another device (Sony experia E1). I got two of them, the first one got recognized while I had to do this process for the second one... Maybe it's my pc fault..
Anyway thank you very much for your replies and the guide. Am I risking to brick the device by following it ?
P.S.
For those who have android studio installed, to run the guide prompt commands you can set an environment variable called 'adb' with this value 'C:\Users\{USERNAME}\AppData\Local\Android\sdk\platform-tools\adb.exe' and easily replacing 'adb' with '%adb%' .
For example : 'C:\Users\{any directory}>%adb% devices'
Click to expand...
Click to collapse
I'm glad you got ADB working. Thanks for the additional tips, I'm sure they will be useful to others.
I don't think there is any significant risk of bricking unless you make a horrible mistake, like deleting everything in /system instead of shifting the new file into place. Anything else, like accidentally picking the wrong su binary to install, should be easily recoverable by just rebooting if necessary and then trying again.

maximumentropy said:
I'm glad you got ADB working. Thanks for the additional tips, I'm sure they will be useful to others.
I don't think there is any significant risk of bricking unless you make a horrible mistake, like deleting everything in /system instead of shifting the new file into place. Anything else, like accidentally picking the wrong su binary to install, should be easily recoverable by just rebooting if necessary and then trying again.
Click to expand...
Click to collapse
Quick info. I am rooting because of the low storage. Currently this is my storage situation :
total 4GB
Firmware 2.04GB
---------------------
Total space 1.96GB
197MB Available
232MB Apps
few KB Cached data & Misc.
There must be something wrong... Anyway my question is. Should I flash a custom rom to free some of the firmware allocated memory ? How is the external card going to be used (can I install app on it) ?
EDIT
I get
`su: not found`

Marco Dufal said:
Quick info. I am rooting because of the low storage. Currently this is my storage situation :
total 4GB
Firmware 2.04GB
---------------------
Total space 1.96GB
197MB Available
232MB Apps
few KB Cached data & Misc.
There must be something wrong... Anyway my question is. Should I flash a custom rom to free some of the firmware allocated memory ? How is the external card going to be used (can I install app on it) ?
Click to expand...
Click to collapse
I haven't found any custom ROMs for this tablet. If you know of some, please speak up. You could try reflashing the original ROM but that might be overkill. You can use an app like DiskUsage to help you identify what's eating the most space.
Marco Dufal said:
EDIT
I get
`su: not found`
Click to expand...
Click to collapse
I can't help you if you give me an error message but no hint of what you entered that caused the message.

maximumentropy said:
I haven't found any custom ROMs for this tablet. If you know of some, please speak up. You could try reflashing the original ROM but that might be overkill. You can use an app like DiskUsage to help you identify what's eating the most space.
Click to expand...
Click to collapse
Thanks I will check it up.
maximumentropy said:
I can't help you if you give me an error message but no hint of what you entered that caused the message.
Click to expand...
Click to collapse
C:\Users\Marco\AppData\Local\Android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $

Marco Dufal said:
Thanks I will check it up.
C:\Users\Marco\AppData\Local\Android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
Click to expand...
Click to collapse
Please try entering it with full path:
[email protected]:/ $ /system/xbin/su

maximumentropy said:
Please try entering it with full path:
[email protected]:/ $ /system/xbin/su
Click to expand...
Click to collapse
Still negative result :
[email protected]:/ $ /system/xbin/su
/system/xbin/su
/system/bin/sh: /system/xbin/su: not found
127|[email protected]:/ $ ls /system/xbin/
ls /system/xbin/
dexdump
io
[email protected]:/ $

Marco Dufal said:
Still negative result :
Click to expand...
Click to collapse
What is your build number in Settings > About Tablet?

maximumentropy said:
What is your build number in Settings > About Tablet?
Click to expand...
Click to collapse
PLT7602G-ANDROID4.2.2-v1.0.0

Marco Dufal said:
PLT7602G-ANDROID4.2.2-v1.0.0
Click to expand...
Click to collapse
Well, I apologize for being an idiot. That's what I get for trying to document a root procedure I did last year, from memory. I have several similar cheap tablets and I misremembered this one as being pre-rooted as I described.
I just re-flashed from stock and re-rooted it. Fortunately, I had left enough breadcrumbs on my computer that I was able to reconstruct the right procedure.
I will do another full run-through within the next few days as soon as I have some time, to make sure I have everything 100% straight, and will clean this up to update the OP. Meanwhile, if you're feeling brave, here's the notes I took as I did it:
Settings > About Tablet > tap build number until it says you are a developer
Developer options > switch On > OK
USB Debugging > OK
Connect USB
see "USB Debugging Connected" notification
Wait for "Allow USB debugging?" dialog, check "Always allow from this computer" and click OK
adb devices
Download pwn.zip here: http://forum.xda-developers.com/showpost.php?p=53407127
Unzip "pwn" from the zip file to your windows current directory
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
Hear USB disconnect sound
Wait about 1 minute (may or may not need to disconnect and reconnect USB cable)
adb wait-for-device
adb shell
su (should give a root shell)
exit
Install SuperSU from Play Store
Run it
The SU binary needs to be updated. Continue?
Continue > Normal > OK
Reboot

Don't worry it's ok.. Anyway I am not felling brave at all so I think that I will wait for now...

Marco Dufal said:
Don't worry it's ok.. Anyway I am not felling brave at all so I think that I will wait for now...
Click to expand...
Click to collapse
No guts, no glory!
I updated the instructions in post #2 and did another trial run through. Give it a shot at let me know if you run into any trouble. You already have ADB functioning, so you can just skip to step 6 and go from there.
http://forum.xda-developers.com/showpost.php?p=59530490&postcount=2

maximumentropy said:
No guts, no glory!
Click to expand...
Click to collapse
Just did it and every thing worked ! It was fast and clear... Now I wonder, how many devices can I root with the same procedure ?

Marco Dufal said:
Just did it and every thing worked ! It was fast and clear... Now I wonder, how many devices can I root with the same procedure ?
Click to expand...
Click to collapse
Great, I'm glad it worked for you!
The pwn exploit will work with many JellyBean devices. Many of the cheap Chinese tablets don't even need it though, as they will either give you a root prompt immediately when you connect using ADB, or after entering "su" to ADB. The trick then is just to use that access to install an "su" from SuperSU or another full SU package, so that you get full root from the user interface as well as from ADB. You could still use the pwn method on such a device, but I personally prefer to use the least invasive method to get the required access.

maximumentropy said:
Great, I'm glad it worked for you!
The pwn exploit will work with many JellyBean devices. Many of the cheap Chinese tablets don't even need it though, as they will either give you a root prompt immediately when you connect using ADB, or after entering "su" to ADB. The trick then is just to use that access to install an "su" from SuperSU or another full SU package, so that you get full root from the user interface as well as from ADB. You could still use the pwn method on such a device, but I personally prefer to use the least invasive method to get the required access.
Click to expand...
Click to collapse
Sorry if this is a newb question but can this be done if your microusb port is broken? I can get the file on the tablet via sd card but I can't seem to perform the steps with Terminal Emulator like I had hoped. This is using the same ProScan PLT7602G as in the OP.
Thanks

Ian1331 said:
Sorry if this is a newb question but can this be done if your microusb port is broken? I can get the file on the tablet via sd card but I can't seem to perform the steps with Terminal Emulator like I had hoped. This is using the same ProScan PLT7602G as in the OP.
Thanks
Click to expand...
Click to collapse
I don't think it will work in a terminal emulator because you need to run with uid 2000 (shell) for permission on the /data/local/tmp directory.

Related

SU request issue, help please

ok so on most roms this happens. i need a SU request but my phone freezes obn a black screen and on the top in gray it says SU request. i wait paciently and maybe 1-2 mins later is asks to FC because its not responding. is there a fix or what am i doing wrong. usb debugging is on and so is install nonmarket apps idk wtf im doing wrong or if somthing is just not working. any input??
I've heard su is not working properly until you activate it once via adb. In your teriminal (cmd or similar)
Code:
adb shell
$su
You should get a working super user request after which all other su requests should work fine.
Marisa said:
I've heard su is not working properly until you activate it once via adb. In your teriminal (cmd or similar)
Code:
adb shell
$su
You should get a working super user request after which all other su requests should work fine.
Click to expand...
Click to collapse
yes same thing happens to me
plug in your phone
goto your android sdk tools
and input adb shell
now go back to your phone and try it while still plugged
thats what i have been doing...
the same thing is happening for me and the instructions of simply input adb shell into terminal arent helping really. if someone could tell me exactly where to be aiming the command prompt and what the exact commands are in order to fix this I would greatly appreciate it.
WalkingTaco said:
the same thing is happening for me and the instructions of simply input adb shell into terminal arent helping really. if someone could tell me exactly where to be aiming the command prompt and what the exact commands are in order to fix this I would greatly appreciate it.
Click to expand...
Click to collapse
Are you getting the same crshes and things, but when you do the adb shell # pops up instead of $?
whenever i do adb shell I get #, so that means SU is already activated, but it's actually not on my phone, so i have no idea what's going on and no one seems to know how to fix it.
no. my Su permissions always force close after a minute of black screen. there is a fix posted above but my nerd level is not high enough to.infer the rest
Sent from my Eris using the XDA mobile application powered by Tapatalk
I don't know the exact command prompt setup, I'm running linux. However, when you originally rooted your phone you used the Android SDK correct?
With your phone plugged in, and USB Debugging enabled on your phone (Settings -> Applications -> Development -> USB Debugging) Open command prompt and get to the tools directory you used during rooting, I don't know where you installed it, so I cannot guide you through that part. If you used Ivan's guide http://forum.xda-developers.com/showthread.php?t=647707 it's probably best to refresh yourself there.
Once you've found your SDK /tools/ in command prompt, it should be as easy as running the code I mentioned earlier
Code:
adb shell
$su
in the command prompt.
The superuser prompt should show up on your phone, tell it to allow it and it should work without fail until you flash a new ROM that has the bug.
thanks very much. I used Ivans guide. I rooted it yesterday when o got my replacement from Verizon in store. I had been using the 2.1 leak on my old one and complained in store for thirty seconds. they didn't even look at it gave me a replacement in ten minutes
Sent from my Eris using the XDA mobile application powered by Tapatalk
Rock out thanks for the Super Help

Easiest Step-by-Step Tutorial on HOW TO GET ROOTED ANDROID 2.1 ON X8(Newbies!)

Update 1: Thank you all the members for making this thread more simpler.
I will do some more edits as instructed by others to make it more understandable.
As we all know it, this guide is no more "easiest".
First of all, thank you to all the members for the Pre-Rooted ROM's, Tutorials, Ideas etc.
I have just made it simpler for the newbies to understand what the devs are doing to get a rooted-Eclair phone.
It has been discussed many times that the current guides are very difficult for newbies to understand.
So I will tell you step-by-step how to do the stuff.
Though it needs many downloads, bit of thinking, but in the end you will be successful!
Make sure to put the phone in USB Debugging Mode everytime.
For that go to -Settings>Applications>Development>USB Debugging(Tick the option)
And maximize the Screen Timeout Limit.
Settings>Sound & Display>Screen Timeout(Set it to 30 minutes).
Update: Many people don't know what "Flashmode" is,
For this you need to unplug the phone from PC, take out phone battery for 5-10 seconds, after that put the battery back, keep holding the Back button and plug the phone back(the notification light will turn Green).
First of all Flash Android 1.6 Link and Root it Link.
Download the files required-
(1) Download the latest Firmware files by propc.
Link 1
Link 2
(2) Download newx8rooted.yaffs.7z Link
(3) Extract newx8rooted.unyaffs.7z to the root of your sdcard(there should be 3 files- (i) newx8rooted.yaffs.img
(ii) busybox
(iii) unyaffs)
(4) Download install.sh.zip(see the attachments)
How to get in the ADB Shell-
(1) First of all we need the ADB files. I have put the files in the folder. See the attachments please.
(2) Extract the files and save them in C: drive.
(3) Now open cmd(Command Prompt).
(4) Type-
cd C:\android
Click to expand...
Click to collapse
Hit Enter.
(5) Now type-
adb shell
Click to expand...
Click to collapse
(6) Remember you must be having Rooted Android 1.6 and 4 files(install.sh, newx8rooted.yaffs.img, busybox, unyaffs) in your SD card at this stage.
After this step the command prompt should be something like this-
C:\android>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$
Click to expand...
Click to collapse
(7) Now type-
su
Click to expand...
Click to collapse
**NOW HAVE A LOOK AT PHONE SCREEN, SUPERUSER MUST BE ASKING FOR PERMISSION, CLICK ON "Allow".(And yes, maximize the Screen timeout time for no spoilling.)**
**NOW THERE SHOULD BE A "#" SIGN IN COMMAND PROMPT.
Sometimes the command takes some time to execute so you need to wait for the "#" prompt before typing next command.**
(8) Now type
cd /sdcard
Click to expand...
Click to collapse
(9) Now type
sh install.sh
Click to expand...
Click to collapse
Update: Many people are facing the problem saying-
# sh install.sh
sh install.sh
sh: Can't open install.sh
#
Click to expand...
Click to collapse
For this, you need to take care of few things.
First of all that you don't miss any commands.
Secondly you must have the drivers installed on your PC. If you don't have please see the attachments, and install it via Device Manager.
Thirdly, make sure that the phone is in USB Debugging Mode.
The phone storage should be turned off.
Sometimes if the error repeats itself, it is always advisable to either Restart both PC and device, or try it on another PC.
There should be a lot of line scrolling, Now sit for sometime and relax!
After all this, it should say-
Reboot phone!
Flash 2.1 now, but remove system.sin
Click to expand...
Click to collapse
Now just Flash Android 2.1 Flasher by Bin4ry works well! and REMEMBER TO REMOVE "system.sin" from the folder of the firmware!!!
Sit back and relax!!
Now just reboot the phone(1st Reboot will take 5-10 mins.).
And you are done!
Hope that I am helpful!
Edit:Many people don't know what "Root of SD Card is"
This means that the files should be on your SD Card directly, do not put these files in any Folder, simply paste them in you SD Card.
Any suggestions and queries are welcomed.
Update 2:
Guys it is really very difficult to know exactly what the problem is. Because it is working for many and not for few, it is hard to know the
exact mistake.
So I advice you people to please repeat the process again, or try it on another PC, if you dont mind that, I am not a pro, I am here just to sort out few problems.
I am sorry but i really ain't able to get solution for random problems.
Can any other "Senior" help this out?
Special Thanks to-
propc
Bin4ry
a-k-t-w
pullpoff2
You can always appreciate my work by just clicking "Thanks"!
Cheers!
you don't need the Android SDK. ADB shell is already in superoneclick.
thanks for instruction
Botoxopfer said:
you don't need the Android SDK. ADB shell is already in superoneclick.
Click to expand...
Click to collapse
I didn't noticed that!!
God! I need to edit it!!
mohakrastogi said:
I didn't noticed that!!
God! I need to edit it!!
Click to expand...
Click to collapse
Also change it to , Copy and paste the three adb files into the /system32 folder, that way adb shell can be accessed without cding, (makes it even simpler )
timk1764 said:
Also change it to , Copy and paste the three adb files into the /system32 folder, that way adb shell can be accessed without cding, (makes it even simpler )
Click to expand...
Click to collapse
Thank you for the suggestion!
Now that you've put the "$" sign after adb shell, you can also put the "#" sign after su, so they will know when to type again. Sometimes the command takes some time to execute so tell them you need to wait for the "#" prompt before typing next command.
Special thanks for this, it's done.
Now i have rooted 2.1 and Gingerbread Theme.
What I'm doing wrong ?
# sh install.sh
sh install.sh
sh: Can't open install.sh
#
Arkaeris said:
What I'm doing wrong ?
# sh install.sh
sh install.sh
sh: Can't open install.sh
#
Click to expand...
Click to collapse
Code:
cd /sdcard
sh install.sh
and make sure your sdcard is not mounted. turn off usb storage on your PC
This guide is great...
But after the last step, flashing 2.1 without system.sin.. My X8 is stuck on "Sony Ericsson" without the logo...
"turn off usb storage on your PC"
sorry, but how to do that ?
Arkaeris said:
"turn off usb storage on your PC"
sorry, but how to do that ?
Click to expand...
Click to collapse
ops, turn off USB storage on your phone. drag down the status bar, press Turn off USB storage. press turn off
I have unmount sd card, I have turn off usb storage but..
C:\android>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\android>
Arkaeris said:
I have unmount sd card, I have turn off usb storage but..
C:\android>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\android>
Click to expand...
Click to collapse
Install Update Service and PC companion. or download X8 driver at http://developer.sonyericsson.com/
propc said:
Install Update Service and PC companion. or download X8 driver at http://developer.sonyericsson.com/
Click to expand...
Click to collapse
okey I have install update service and reinstall pc companion and download x8 drivers.
C:\android>adb shell
$ su
su
# cd /sdcard
cd /sdcard
# sh install.sh
sh install.sh
sh: Can't open install.sh
#
I don't understand where I go wrong.....
Arkaeris said:
okey I have install update service and reinstall pc companion and download x8 drivers.
C:\android>adb shell
$ su
su
# cd /sdcard
cd /sdcard
# sh install.sh
sh install.sh
sh: Can't open install.sh
#
I don't understand where I go wrong.....
Click to expand...
Click to collapse
check that you had turn off USB storage, check that you copied the files to the root of your sdcard
propc said:
check that you had turn off USB storage, check that you copied the files to the root of your sdcard
Click to expand...
Click to collapse
what does it mean "to the root of your sdcard" ?
is folder name or something like that ?
Maybe my computer has some windows problems ?
Root of SD-Card means that u only put it into the sdcard into no folder. Just click on the sdcard and copy the file in it.
[email protected] said:
Root of SD-Card means that u only put it into the sdcard into no folder. Just click on the sdcard and copy the file in it.
Click to expand...
Click to collapse
I'm doing just you said but.. It still Can't open install.sh

[GUIDE] ADB - Usage, Tips, Tricks and More!

*****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.

[Q]Major issues with rooting my prime

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...

How to Root on Mac OSX

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

Categories

Resources