Related
So ive been trying to figure out how to push files onto my eris for like a week now and im not smart enough with computer to so it. Ive downloaded the mac ADB, and have a 2.2 emulator up and running. But when i plug my phone in i cant ever find it using terminal. Im pretty sure its just cause im using the wrong commands so if anyone knows them for a mac that would be awesome. Any info would help me, Thanks.
No emulator is involved. Find the adb executable, and cmd+c to copy it. Fire up terminal and cmd+v to paste it, then type a space, then "push" (without the quotes), then a space, then drag the file you want to copy onto the terminal window, then type the location on your phone you plan on pushing to (like /system/app/ for example). And that's it! But you should do an adb remount before pushing. Again, to do a remount, paste the adb file into terminal or drag it in, then type a space, then "remount" (without the quotes).
It's been a while since I did the initial install steps, but the main difference to the commands is having to use a dot and a slash before the command "./" to specify the command you want to run is in the directory you're working in. Other than that, the PC steps are the same.
For example, my files are in a sub-directory under my user profile: /Users/<user_name>/Phone/android-sdk-mac_86/tools/ which can also be typed as ~/<user_name>/Phone/android-sdk-mac_86/tools/
So, in Finder, I go to that directory and double click the android file. That starts terminal which also starts the Android app. I go back to Terminal, press Command+T to open a new tab in Terminal (just so I won't have a ton of windows open), change directory to ~/<user_name>/Phone/android-sdk-mac_86/tools/ then I run the adb command typed as ./adb
So, to re-cap step by step:
My adb files are located in ~/<user_name>/Phone/android-sdk-mac_86/tools/
Make sure your phone is connected in USB debugging mode
In Finder, go to the above directory and double click android
Switch back to Terminal, press Command+T to open a new tab and change directory to ~/<user_name>/Phone/android-sdk-mac_86/tools/
Type: ./adb remount
Type ./adb shell (or whatever adb commands you want to run)
I am running bamf 1.6.3 remix.. I also am using Handcent sms.. I have synced and redownloaded handcent.. No matter how many times I try the sync won't catch.. The contact images remain little androids.
I Heard of a solution and tried to figure through it..
It appears the ROM Manager fix permissions script messed up the permissions on the thumbnails in the contacts folder. The files were mistakenly permissioned as 771 which meant the jpg thumbnail files were unreadable.
This is what I did to fix it:
1. Boot into clockworkmod recovery
2. Go into the mount/umount section
3. mount /system
4. mount /data
5. Connect usb data cable to computer from phone (I use linux so I don't need anything special in the way of drivers)
6. adb shell
7. mount /datadata
8. The above step may take a few seconds to mount
9. cd /datadata/com.android.providers.contacts
10. chmod og+rx *
11. cd files
12. chmod 664 *.jpg
13. cd /
14. umount /datadata
15. umount /data
16. exit
17. Reboot your phone
I ran into a problem at step 6...
I tried to access the adb shell from the command prompt on the computer I rooted my phone through..
When i typed adb shell into my prompt It could not recognize the device or the command.
-- Am I doing something wrong?? Is there Another solution? I love all the help everyone in forums give, it keeps a community running. I am just such a noob, one word lines never do me any good. A little explanation is GREATLY appreciated.
THANKS ALL.
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...
I used root explorer, made a copy of my original and named it original, then copied over another build.prop from my SGSII to play with MC3 and now the prime wont boot.
Im sure I will have to wait until i get home to use my USB cable but is this something I can fix through ADB?
how can i get the Prime into state that ADB can talk to it since now all i get is a black screen after the Eee pad splash screen?
Can you get into the recovery?
yes but it it shows the little android on his back with a red triangle.
is that because im rooted?
see if you can get adb access, if so push back an original build.prop...
note... never ever push a build.prop from a different device.. its the most stupid thing you can do.
yes i feel extremely stupid. i hope i didnt brick my prime doing something this retarded.
nextelbuddy said:
yes i feel extremely stupid. i hope i didnt brick my prime doing something this retarded.
Click to expand...
Click to collapse
i hope so to bro, although i did read someone messed up his build.prop before on his prime, dunno how that went afterwards... u might need to search for that
If you have access to either adb.. or maybe if you can flash zip files from your recovery you're good to go.
Using Adb:
Running "adb devices" should print your Device #, if it prints nothing, it won't work..
adb pull /system/build.prop build.prop.bootloop
adb pull /system/original.build.prop original.build.prop (>> Edited to original.build.prop as per your last post)
Then if you look at the files on your PC..
build.prop.bootloop would be the one you have right now that's causing loops
build.prop would be your backed up working build.prop.original
Then just push the good one:
adb push original.build.prop /system/build.prop
adb pull/push usage:
adb pull remotefile localfile
adb push localfile remotefile
You may be able to go this route and reflash the entire rom if you dont have adb access. From what I understand is you rename the update.zip file to whatever it says in the link to rename to and put on the root of sd card and do the power + volume and go into recovery.
http://forum.xda-developers.com/showthread.php?t=1492887&page=18
the latest asus update can be found here.
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+Prime+TF201&p=20&s=16
thank you very much i will get to work on this when i get home with my cable. i was just about to post where can i get another one but you posted directions on how to pull my copy that i created which i renamed original.build.prop
Also might wanna take a look at this thread
http://forum.xda-developers.com/showthread.php?t=1514088
PM_mobile said:
If you have access to either adb.. or maybe if you can flash zip files from your recovery you're good to go.
Using Adb:
Running "adb devices" should print your Device #, if it prints nothing, it won't work..
adb pull /system/build.prop build.prop.bootloop
adb pull /system/original.build.prop original.build.prop (>> Edited to original.build.prop as per your last post)
Then if you look at the files on your PC..
build.prop.bootloop would be the one you have right now that's causing loops
build.prop would be your backed up working build.prop.original
Then just push the good one:
adb push original.build.prop /system/build.prop
adb pull/push usage:
adb pull remotefile localfile
adb push localfile remotefile
Click to expand...
Click to collapse
i can get the device into APX mode because i installed the APX driver and when i hold VOl UP and Power, my windows 7 computer shows Asus Prime APX under System Devices and it goes away if i unplug it and vice versa plugging it back in however ABD stil shows Blank for connected devices.
not sure what Im doing wrong so im uninstalling my OLD SDK from last year and reinstalling the latest SDK to see if that helps.
ok so my Prime boots into APX mode according to windows 7 Device manager. it shows APX not greyed out.
however despite this, in CMD when i type ADB Devices it shows BLANK and of course any adb commands return no device found.
if i let the Prime reboot into its Boot loop, then ADB Composite appears in Device manager.
if i go to CMD and type ADB Devices, it always says ADB Server out of date killing server and then it shows Daemon starting and then says Failed.
if i try 2 times back to back i eventually get the Device Serial number.
so then i try PULL command and that works no problem
when i try the PUSH command i get an error that says READ ONLY FILE SYSTEM and it fails.
i'm stuck now
nextelbuddy said:
ok so my Prime boots into APX mode according to windows 7 Device manager. it shows APX not greyed out.
however despite this, in CMD when i type ADB Devices it shows BLANK and of course any adb commands return no device found.
if i let the Prime reboot into its Boot loop, then ADB Composite appears in Device manager.
if i go to CMD and type ADB Devices, it always says ADB Server out of date killing server and then it shows Daemon starting and then says Failed.
if i try 2 times back to back i eventually get the Device Serial number.
so then i try PULL command and that works no problem
when i try the PUSH command i get an error that says READ ONLY FILE SYSTEM and it fails.
i'm stuck now
Click to expand...
Click to collapse
I think its bricked... because from the research Swift and I did on a battery mod, he tried a mod I don't remember what and it ended up in boot loop. ADB won't work because of the boot loop it doesn't stay long enough in a booted state for ADB to send/receive the commands. If your still in your return period try for exchange.
nextelbuddy said:
when i try the PUSH command i get an error that says READ ONLY FILE SYSTEM and it fails.
i'm stuck now
Click to expand...
Click to collapse
The file system will be read only by default. You need to remount /system as read/wrire.
Regards,
Dave
Sent from my GT-N7000 using Tapatalk
Had the same problem back then.
I did a search on the problem at the forum and found this:
"I did this and that worked for me : http://forum.xda-developers.com/show...4&postcount=21"
You need a micro sd and rename a file, easy, poof, fixed.
As far as adb goes
adb remount
or
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
foxmeister said:
The file system will be read only by default. You need to remount /system as read/write.
Regards,
Dave
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Unfortunately i can not remount the system. if i try to remount it says either device not found or error it can not.
its like it never listens long enough..
for example if i type ADB Devices, it will say "ADB Server out of date killing server and then it shows Daemon starting and then says Failed"
if i try that 2-3 times then it will eventually say Devices and list my Serial number.
if i try immediately after that to go to ADB SHELL, it starts and then i type:
adb push original.build.prop /system/build.prop
as soon as i hit enter it says Device not found.
even if i try that command 5 times in a row hoping that it takes one of the times, it does not.
Brollie said:
Had the same problem back then.
I did a search on the problem at the forum and found this:
"I did this and that worked for me : http://forum.xda-developers.com/show...4&postcount=21"
You need a micro sd and rename a file, easy, poof, fixed.
Click to expand...
Click to collapse
i cant look at that link, its truncated. can you post the full link please?
i tried downloading the .15 firmware from Asus site and pasting it on a micro SD card and putting it in the Prime and then booting into recovery mode but it always shows the android laying down with a red triangle.
PM_mobile said:
As far as adb goes
adb remount
or
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
i cant remount, i can shell but if i do that then it says no devices connected.
wow, i royally screwed things up with this stupid build.prop like an idiot.
For the record, once in adb shell it's not adb push anymore..
That'd be
cp /system/original.build.prop /system/build.prop
I doubt this will do you any good, it seems you just can't stay in adb long enough because it reboots.
You don't gave a working custom recovery do you? (like clockwork mod)
I think I've seen people with custom recoveries on their primes.. that'd allow you to adb properly or flash a zip file with your build.prop..
Also, Did you look at this thread?
http://forum.xda-developers.com/showthread.php?t=1514088
They have a few unbrick solutions and something about getting adb to work from recovery. Recovery wouldn't bootloop while you're trying to adb..
aznmode said:
You may be able to go this route and reflash the entire rom if you dont have adb access. From what I understand is you rename the update.zip file to whatever it says in the link to rename to and put on the root of sd card and do the power + volume and go into recovery.
http://forum.xda-developers.com/showthread.php?t=1492887&page=18
the latest asus update can be found here.
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+Prime+TF201&p=20&s=16
Click to expand...
Click to collapse
THIS!!!
i downloaded the latest stock firmware .15 from asus support site. renamed it to
EP201_SDUPDATE.zip and copied to a micdro SD card.
held VOL DOWN + Power and when i saw the white text hit VOL UP twice
and the recovery manager detected the file on the SD card and started flashing.
no more RED triangle android anymore.
im sooo excited this worked and will definitely take more caution in regards to the build.prop file. never realized how much of an integral role it played in the android OS.
thank you very much for all your help and to the others thanks for your help with ADB. even though it didnt work, i played with ADB so much last night and today that i feel much more comfortable with it.
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