Help rooting! - Motorola Atrix 2

Alright I'm on the atrix 2 ics leak . Everythings fine except for one thing , I can't get root!!:crying: It's driving me crazy
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
You are rooted!
Press any key to continue . . .
That's the error I keep getting. Please help !

marquavious said:
Alright I'm on the atrix 2 ics leak . Everythings fine except for one thing , I can't get root!!:crying: It's driving me crazy
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
You are rooted!
Press any key to continue . . .
That's the error I keep getting. Please help !
Click to expand...
Click to collapse
i keep getting the same error, if i move the .bat file to the root path of my computer i get this.
it says im root at the bottom but obviously im not.
i have tried 2-3 different root methods.
no luck as of yet
C:\Android>adb kill-server
* server not running *
C:\Android>adb wait-for-device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Android>adb shell mv /data/local/12m/batch /data/local/12m/batch.bak
C:\Android>adb shell ln -s /data /data/local/12m/batch
C:\Android>adb reboot
C:\Android>adb wait-for-device
C:\Android>adb.exe shell rm /data/local.prop
C:\Android>adb.exe shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
C:\Android>adb.exe reboot
C:\Android>adb.exe wait-for-device
C:\Android>adb.exe remount
remount succeeded
C:\Android>adb.exe push su /system/bin/su
cannot stat 'su': No such file or directory
C:\Android>adb.exe shell chmod 04755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Android>adb.exe push Superuser.apk /system/app
cannot stat 'Superuser.apk': No such file or directory
C:\Android>adb.exe shell chmod 0666 /system/app/Superuser.apk
Unable to chmod /system/app/Superuser.apk: No such file or directory
C:\Android>adb.exe shell "echo \"ro.kernel.qemu=0\" > /data/local.prop"
C:\Android>adb.exe shell rm /data/local.prop
C:\Android>adb.exe shell rm /data/local/12m/batch
C:\Android>adb.exe shell mv /data/local/12m/batch.bak /data/local/12m/batch
C:\Android>adb reboot
C:\Android>echo You are rooted!
You are rooted!
C:\Android>PAUSE
Press any key to continue . . .

matt99017d said:
i keep getting the same error, if i move the .bat file to the root path of my computer i get this.
it says im root at the bottom but obviously im not.
i have tried 2-3 different root methods.
no luck as of yet
C:\Android>adb kill-server
* server not running *
C:\Android>adb wait-for-device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Android>adb shell mv /data/local/12m/batch /data/local/12m/batch.bak
C:\Android>adb shell ln -s /data /data/local/12m/batch
C:\Android>adb reboot
C:\Android>adb wait-for-device
C:\Android>adb.exe shell rm /data/local.prop
C:\Android>adb.exe shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
C:\Android>adb.exe reboot
C:\Android>adb.exe wait-for-device
C:\Android>adb.exe remount
remount succeeded
C:\Android>adb.exe push su /system/bin/su
cannot stat 'su': No such file or directory
C:\Android>adb.exe shell chmod 04755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Android>adb.exe push Superuser.apk /system/app
cannot stat 'Superuser.apk': No such file or directory
C:\Android>adb.exe shell chmod 0666 /system/app/Superuser.apk
Unable to chmod /system/app/Superuser.apk: No such file or directory
C:\Android>adb.exe shell "echo \"ro.kernel.qemu=0\" > /data/local.prop"
C:\Android>adb.exe shell rm /data/local.prop
C:\Android>adb.exe shell rm /data/local/12m/batch
C:\Android>adb.exe shell mv /data/local/12m/batch.bak /data/local/12m/batch
C:\Android>adb reboot
C:\Android>echo You are rooted!
You are rooted!
C:\Android>PAUSE
Press any key to continue . . .
Click to expand...
Click to collapse
Your issue, is that when you move the script to C:\ you also need to move su and Superuser.apk to the same directory as well, or it will not find those files like it is complaining about. the bat file and the su and superuser.apk MUST all be in the same dir. Try moving them all to your root path.

jimbridgman said:
Your issue, is that when you move the script to C:\ you also need to move su and Superuser.apk to the same directory as well, or it will not find those files like it is complaining about. the bat file and the su and superuser.apk MUST all be in the same dir. Try moving them all to your root path.
Click to expand...
Click to collapse
OK when i moved the whole folder into c:\ android it worked!
thank you so much jim.
Now how to overclock? or do are we waiting for int't? {think thats what its called}

It worked for me too! Thanks Jim. Love you dude
Sent from my MB865 using xda app-developers app

matt99017d said:
i keep getting the same error, if i move the .bat file to the root path of my computer i get this.
it says im root at the bottom but obviously im not.
i have tried 2-3 different root methods.
no luck as of yet
C:\Android>adb kill-server
* server not running *
C:\Android>adb wait-for-device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Android>adb shell mv /data/local/12m/batch /data/local/12m/batch.bak
C:\Android>adb shell ln -s /data /data/local/12m/batch
C:\Android>adb reboot
C:\Android>adb wait-for-device
C:\Android>adb.exe shell rm /data/local.prop
C:\Android>adb.exe shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
C:\Android>adb.exe reboot
C:\Android>adb.exe wait-for-device
C:\Android>adb.exe remount
remount succeeded
C:\Android>adb.exe push su /system/bin/su
cannot stat 'su': No such file or directory
C:\Android>adb.exe shell chmod 04755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Android>adb.exe push Superuser.apk /system/app
cannot stat 'Superuser.apk': No such file or directory
C:\Android>adb.exe shell chmod 0666 /system/app/Superuser.apk
Unable to chmod /system/app/Superuser.apk: No such file or directory
C:\Android>adb.exe shell "echo \"ro.kernel.qemu=0\" > /data/local.prop"
C:\Android>adb.exe shell rm /data/local.prop
C:\Android>adb.exe shell rm /data/local/12m/batch
C:\Android>adb.exe shell mv /data/local/12m/batch.bak /data/local/12m/batch
C:\Android>adb reboot
C:\Android>echo You are rooted!
You are rooted!
C:\Android>PAUSE
Press any key to continue . . .
Click to expand...
Click to collapse
For some reason it took me several tries as well. Try moving the zip to your desktop then extracting it there and running the .bat file from the extracted folder and see if that helps. To the OP it looks like you dont have ADB set up in your path correctly

matt99017d said:
OK when i moved the whole folder into c:\ android it worked!
thank you so much jim.
Now how to overclock? or do are we waiting for int't? {think thats what its called}
Click to expand...
Click to collapse
Yeah we are waiting for init.d, there are a few of us looking at it right now, so hopefully not long.

Is there any partition that is preserved across such OTA/recovery updates? If I rooted 2.3.6 and installed a suid-root binary "su" in /system/xbin, and then applied the ICS update, it'll be probably gone as /system will be cleaned up by the update. Is there any other safe place I can park the suid binary so that post update it is available? If my SD card has a ext3 partition, I can put it there, only if the partition is mounted by root at startup. I wonder how OTA Rootkeeper works, where does it safely store suid su binary across updates?

hello
i'm a french guy so my english is very poor
Thank's for all too install ics on atris2 but i can(t root it.
I have the doo the same thing of this thread but nothing his right
what i can do?
what is the mod chouse when i plug the A2 with USB
thank's
when i launch root.bat i have
* daemon not running. starting it now *
* daemon starting successfull *
it's ok I just forgot to put debugging usb
thank's for all

kousik said:
Is there any partition that is preserved across such OTA/recovery updates? If I rooted 2.3.6 and installed a suid-root binary "su" in /system/xbin, and then applied the ICS update, it'll be probably gone as /system will be cleaned up by the update. Is there any other safe place I can park the suid binary so that post update it is available? If my SD card has a ext3 partition, I can put it there, only if the partition is mounted by root at startup. I wonder how OTA Rootkeeper works, where does it safely store suid su binary across updates?
Click to expand...
Click to collapse
No OTA rootkeeper did not work for this update. You CAN'T be rooted, it can cause the update to fail.
You really need to do it as I posted it. This root script works, but you must unzip it and put the folder on the desktop or in c:\. For Linux adb just need to be in your PATH, so it can be unzipped anywhere.
Oh and everything gets wiped when you do the fxz, so no place is safe to store su.
Sent from my SAMSUNG-SGH-I747 using xda premium

jimbridgman said:
No OTA rootkeeper did not work for this update. You CAN'T be rooted, it can cause the update to fail.
You really need to do it as I posted it. This root script works, but you must unzip it and put the folder on the desktop or in c:\. For Linux adb just need to be in your PATH, so it can be unzipped anywhere.
Oh and everything gets wiped when you do the fxz, so no place is safe to store su.
Click to expand...
Click to collapse
The update generally won't fail just because of rooting. Problem is, post rooting we install a lot of hacks, change a lot of system files. The updater-script notices them and refuse to update. I see updater-script checking the signature of 616 files, almost all files of /system/app, /system/bin, /system/app, /system/lib etc. However it recursively delete /system/data, /system/usr/bin, /system/data. If you touched any of these 616 files update will fail. Even if we didn't change the binaries, people play with build.prop and the updater-script would look for a sha1sum of 9ff9faedeb74bd02b3fe6a912e758f55d1437538.
However it does not sweep clean /system. It removes specific files; and then adds new ones. The root doesn't remain because of the following:
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
So the setuid bit of binary su is not retained. So we have to find another file system which is safe from these operations. Maybe I'll leave the suid- su binary at /

kousik said:
The update generally won't fail just because of rooting. Problem is, post rooting we install a lot of hacks, change a lot of system files. The updater-script notices them and refuse to update. I see updater-script checking the signature of 616 files, almost all files of /system/app, /system/bin, /system/app, /system/lib etc. However it recursively delete /system/data, /system/usr/bin, /system/data. If you touched any of these 616 files update will fail. Even if we didn't change the binaries, people play with build.prop and the updater-script would look for a sha1sum of 9ff9faedeb74bd02b3fe6a912e758f55d1437538.
However it does not sweep clean /system. It removes specific files; and then adds new ones. The root doesn't remain because of the following:
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
So the setuid bit of binary su is not retained. So we have to find another file system which is safe from these operations. Maybe I'll leave the suid- su binary at /
Click to expand...
Click to collapse
Don't tell people this, because what we have found is the safest method is to fxz back to stock before any OTA.
We don't want to confuse people here. I am not saying what you said is wrong, just that we all need to stay on the same page here... I am trying to get everyone to have the same abilities to update here... as well as you are posting this in the wrong place, this is someone asking for help rooting the ICS leak.

Related

delete app manually

Ive done adb push with no problems. Now, I couldn't find a command to delete a file from /system/app.
Please help. I want to get rid of Sprint_Core.apk and some others.
rm Sprint_Core.apk
also http://ss64.com/bash/
thematrixkid17 said:
rm Sprint_Core.apk
also http://ss64.com/bash/
Click to expand...
Click to collapse
thankyou but i get an error:
'rm' is not recognized as an internal or external command, operable program or batch file.
This is what i did after I cd c:/android-sdk-windows/tools
adb remount
rm Sprint_Core.apk
energizer1389 said:
thankyou but i get an error:
'rm' is not recognized as an internal or external command, operable program or batch file.
This is what i did after I cd c:/android-sdk-windows/tools
adb remount
rm Sprint_Core.apk
Click to expand...
Click to collapse
you need to:
adb remount
adb shell
cd system
cd app
rm Sprint_Core.apk
exit
R
adb remount
adb shell
rm /system/app/Sprint_Core.apk
energizer1389 said:
thankyou but i get an error:
'rm' is not recognized as an internal or external command, operable program or batch file.
This is what i did after I cd c:/android-sdk-windows/tools
adb remount
rm Sprint_Core.apk
Click to expand...
Click to collapse
I dont know the exact location, but you need to do something like adb shell, then cd (and type the location of the program you want to delete) and then rm Sprint_Core.apk
adb remount
adb shell
rm /system/app/Sprint_Core.apk
Click to expand...
Click to collapse
Awesome guys. Thankyou.
Originally Posted by thematrixkid17
rm Sprint_Core.apk
also http://ss64.com/bash/
Click to expand...
Click to collapse
Great link. Are all those adb shell commands?
energizer1389 said:
Great link. Are all those adb shell commands?
Click to expand...
Click to collapse
No. These are Linux commands for the BASH shell.
In Linux, if you open a terminal and run the command:
Code:
man <command-you-want-more-info-on>
This will give you the "manual" (man) -- for the command you're looking for.
If you want a list of ADB commands, go HERE

[Q] adb shell in batch

Hi,
I'm making a batch file (*.bat) for myself to try make some things easier file where I enter commands with adb.exe.
The problem is, any code after 'adb shell' is not executed in the batch.
So if I had a batch with the following:
Code:
adb shell
su
'su' will not be executed and stays at '$'.
It seems like it's too deep for a batch file to enter codes.
I also tried pushing a sh with the same script and run it from adb but then all I get it permission denied.
I have also tried 'adb shell su' without any luck.
Anyone with a solution?
Anyone? Or how about a .rc file that gets su and runs commands...
Sent from my HTC
To execute a script, you can always push your script and then execute it:
Code:
adb push script /sdcard/script
adb shell sh /sdcard/script
As for the commands you have shown, keep in mind that su doesn't simply change the running shell's permissions or the like but creates a new child environment within its own shell. You leave your script and after the new shell has finished, you're back in your old environment and the script continues.
mizch said:
To execute a script, you can always push your script and then execute it:
Code:
adb push script /sdcard/script
adb shell sh /sdcard/script
As for the commands you have shown, keep in mind that su doesn't simply change the running shell's permissions or the like but creates a new child environment within its own shell. You leave your script and after the new shell has finished, you're back in your old environment and the script continues.
Click to expand...
Click to collapse
yes, is there any way to automate the script inside the shell and use exit to finally go back to the batch script.
Can you provide me with an example of what you want to achieve?
To execute shell commands from a batch, it doesn't matter if I have to push a script and execute it. It's so that I get su and automate commands after that. Like flash_image, remount, chmod etc..
you will need to use the 'adb shell command' ad 'sh' files
I am trying to create a unix script file that copies files from /dbdata/databases to another folder as a backup.
When I try running the script in adb shell as SU, I get
cd: can't cd to /dbdata/databases
This is on a rooted Captivate. Any help would be greatly appreciated!
Hi,
su -c "command" should do the job for you. You will need to enclose the whole of the command in quotes however, otherwise su will be expecting the command to execute, doing nothing.
Example: adb shell "su -c 'sqlite3 /data/data/my.db/databases/mydb.db < /sdcard/dump.sql'" (run from a Unix or Windows(?) shell). Notice the use of "" and ''.
(in this case dump.sql contains .dump, for instance)
Of course the sqlite3 command could be placed within another script on the android device.
Hope that helps.
I looked around a bit and found the answer.
The simple answer is, wrap the command
Code:
cp "source" "destination"
in double quotes!
Thank you grindingbob for the adb shell "su -c 'sh /mnt/sdcard/tmp/2.sh'" command.
No probs I was more referring to executing commands as a su without interacting with adb shell.
As a side-note, cp might not be a good idea, unless you're sure no db accessing is taking place at the same time.
I am pretty sure well as sure as a novice can be! The files I am backing up are log files, call history and text message history.
The results from running a unix script which contains
Code:
cp "/dbdata/databases/com.android.providers.contacts/contacts2.db" "/mnt/sdcard/tmp4/contacts2.db"
cp "/dbdata/databases/com.android.providers.telephony/mmssms.db" "/mnt/sdcard/tmp4/mmssms.db"
cp "/dbdata/databases/com.sec.android.provider.logsprovider/logs.db" "/mnt/sdcard/tmp4/logs.db"
are only the logs.db file is copied, the other two are not.
grindingbob said:
No probs I was more referring to executing commands as a su without interacting with adb shell.
As a side-note, cp might not be a good idea, unless you're sure no db accessing is taking place at the same time.
Click to expand...
Click to collapse
Permission issues for *.sh files from ADB
Dear All,
I have a 3.2 device with Root permissions & Busybox.
I created a sample *.sh file, Pushed to SDcard, and gave '777' Permissions. When i Try to run it from ADB shell its not working Any help...
CMD prompt Traces:
Step -1: Created a sh file
cat TAB.sh
#!/bin/sh
cd /data/data/com.android.gallery/shared_prefs
Step -2 Pushed the file to SDcard
# ls -l *.sh
ls -l *.sh
-rw-rw-r-- root sdcard_rw 56 2012-03-13 15:06 SP.sh
-rw-rw-r-- root sdcard_rw 62 2012-03-13 15:05 TAB.sh
Step -3 Gave 777 permission for *.sh files
# chmod 777 *.sh
chmod 777 *.sh
# ls -l
ls -l
-rw-rw-r-- root sdcard_rw 56 2012-03-13 15:06 SP.sh
-rw-rw-r-- root sdcard_rw 62 2012-03-13 15:05 TAB.sh
Execute permission not applied
Tried other operations, dint workout
Step 4 other options:
# chmod +X *.sh
chmod +X *.sh
Bad mode
# chmod +x *.sh
chmod +x *.sh
Bad mode
# chmod u+x *.sh
chmod u+x *.sh
Bad mode
Any Help?

help!!

hiya everyone, im new on here and really need some help.
im trying to downgrade my android software so im able to root it. only problem being ive never used command prompt lol!!
the guide im using says:
Launch a Command Prompt window and browse to the location of the files extracted in Step 1.
Enter the following commands:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
You should now get the # prompt, indicating temporary root.
Enter these commands:
cd /data/local/tmp
./misc_version -s 1.31.405.6
but how do i browse for the files if ive stored them in my documents and in a folder called downgrade android.
many thanks
keeps saying not a batch file :s
Moving them into the SDK tools folder temporarily would make things easier and would mean only the file name needs to be typed rather than the specific location, try it out, I hope I remembered correctly
dannysissons said:
hiya everyone, im new on here and really need some help.
im trying to downgrade my android software so im able to root it. only problem being ive never used command prompt lol!!
the guide im using says:
Launch a Command Prompt window and browse to the location of the files extracted in Step 1.
Enter the following commands:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
You should now get the # prompt, indicating temporary root.
Enter these commands:
cd /data/local/tmp
./misc_version -s 1.31.405.6
but how do i browse for the files if ive stored them in my documents and in a folder called downgrade android.
many thanks
Click to expand...
Click to collapse
you can either modify the command like this:
adb push C:\users\[YOURUSERNAME]\My documents\downgrade\psneuter /data/local/tmp
or setup a locale path variable to the dir, where adb is stored as mentioned in THIS thread. (step 4)
Then you can simply cd to the dir, where your files are stored, and run adb from there (actually you can run adb from any dir then)

How do I install netflix patch

Hi,
I am rooted now (I guess/hope) I would like to fix it, I have the patch and have tried to copy the libnvomx.so to the lib dir n my TF using file manager HD, but it wont let me paste it, I dont have or seem to have access.
also, is the libnvomx.so the only one I need to copy from the patch?
does this mean I am not rooted?
Is there somewhere/link where I can learn how to, and what terms like adb, push, clear the cache sideload, quickboot, recovery, etc... mean? (search hasnt helped me much with the ones I have looked for, too many results or too few)
thanks for any help,
John
use the terminal emulator, and make sure you "su" before you try to copy.
Another option is Root Explorer: https://market.android.com/details?id=com.speedsoftware.rootexplorer
Root Explorer will allow you to establish write access to system files. It's what I used to get Netflix working on my Transformer
AustinMartin said:
use the terminal emulator, and make sure you "su" before you try to copy.
Click to expand...
Click to collapse
Hi,
Thanks, what is su?
I tried using adb (at dos prompt) I tried
adb push libnvomx.so /system/lib/
it said read only access
will the su give me access? how do I su?
I am not even sure what the terminal emu is?
thanks,
John
I don't know if your rooting added the terminal app to the tf101.
You need to run the su(superuser) command to gain access to the system files.
I think you can run it from adb as well, if you used adb to root, then you probably already used this command.
you can also just download the netflix patch zip to the microsd card, and install the zip from cwm recovery mode.
Xerravon said:
Hi,
Thanks, what is su?
I tried using adb (at dos prompt) I tried
adb push libnvomx.so /system/lib/
it said read only access
will the su give me access? how do I su?
I am not even sure what the terminal emu is?
thanks,
John
Click to expand...
Click to collapse
Close, no cigar:
try this:
adb remount
adb pull /system/lib/libnvomx.so libnvomx.so.orig
adb push libnvomx.so /system/lib/
adb chmod 644 /system/lib/libnvomx.so
adb remount
adb reboot
----
I'm not recalling if you can do an adb chmod, but probably you can so I'll add that in up there just in case it works: Also I added a bit where you get a copy of the original in case this all somehow goes bad.
hachamacha said:
Close, no cigar:
try this:
adb remount
adb pull /system/lib/libnvomx.so libnvomx.so.orig
adb push libnvomx.so /system/lib/
adb chmod 644 /system/lib/libnvomx.so
adb remount
adb reboot
----
I'm not recalling if you can do an adb chmod, but probably you can so I'll add that in up there just in case it works: Also I added a bit where you get a copy of the original in case this all somehow goes bad.
Click to expand...
Click to collapse
hI,
Thanks,
I havnt tried yet but will asap. Where did you learn this stuff? I was reading this thread (I finally looked in general)
http://forum.xda-developers.com/showthread.php?t=872128
It has some info but real detailed, like in your script, the "chmod 644" the 644 part. I guess it takes time, I ave only had this TF for a week or so and it is my first android OS.
thanks again, (I will let you know when I try,
John
edit
Just wondering before I try this, the pull command (Is that backing up the libnvomx file to the pc?
after reading the thread linked above, wont I have to be in adb shell to geet permission to copy the file to the lib dir?
AustinMartin said:
I don't know if your rooting added the terminal app to the tf101.
You need to run the su(superuser) command to gain access to the system files.
I think you can run it from adb as well, if you used adb to root, then you probably already used this command.
Click to expand...
Click to collapse
I used nvflash and adb to install busybox and superuser and su.
I dont know anything about su or superuser, I havent found any threads with info on them yet.
thanks,
It might sound confusing but this is just all basic linux.
when you're running the adb shell just enter su. This gives you permission to edit the /system files
Then pull(copy) the file from your tf101, to your local machine. this is a backup.
Then change the permissions on the file on your tf101.
Then push the new file from your local machine to your tf101.
AustinMartin said:
It might sound confusing but this is just all basic linux.
when you're running the adb shell just enter su. This gives you permission to edit the /system files
Then pull(copy) the file from your tf101, to your local machine. this is a backup.
Then change the permissions on the file on your tf101.
Then push the new file from your local machine to your tf101.
Click to expand...
Click to collapse
Hi,
I broke down and used your script, I tried doing it on my own but kept getting errors. I did seem to get one error in this line of yours
adb chmod 644 /system/lib/libnvomx.so
when I ran it (and I copy and pasted it to dos window)) it gave an error, well not an error but it listed commands and switches like if there is a typo. I dont know if it took the command or not here is a paste
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Kerr Avon>cd adb
The system cannot find the path specified.
C:\Users\Kerr Avon>
C:\Users\Kerr Avon>cd\adb
C:\ADB>adb remount
remount succeeded
C:\ADB>adb pull /system/lib/libnvomx.so libnvomx.so.orig
3429 KB/s (189660 bytes in 0.054s)
C:\ADB>adb push libnvomx.so /system/lib/
1174 KB/s (164764 bytes in 0.137s)
C:\ADB>adb chmod 644 /system/lib/libnvomx.so
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storag
e)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or
recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specifie
d port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition
is updated.
C:\ADB>remount
'remount' is not recognized as an internal or external command,
operable program or batch file.
C:\ADB>adb remount
remount succeeded
C:\ADB>adb reboot
C:\ADB>adb reboot
Click to expand...
Click to collapse
Looks like it probably did work, anyway netflix is running.
some of the lines I tried that didnt work (and did) are here, not sure what was wrong.
adb push libnvomx.so /system/lib/
adb pull /system/lib/libnvomx.so libnvomx.so.orig
(I think push and pull wont work under shell)
*******************************************
cp /system/lib/libnvomx.so removable/microsd/isoa/libnvomx.so.orig
cp /system/lib/libnvomx.so removable/microsd/isoa/libnvomx.so.orig
cp isoa/libnvomx.so /system/lib/libnvomx.so
(dont know why these didnt work, I did su first)
***************************************************************
this worked!!!
cp /system/lib/libnvomx.so sdcard/isoa/libnvomx.so.orig
***************************************************************
cp sdcard/isoa/libnvomx.so system/lib/libnvomx.so
file exists error
********************************************************
Click to expand...
Click to collapse
Oh, so the android runs linux, or a version of it (like ubuntu, freebsd, etc...)? that should help me a lot. I installed ubuntu on one of my PC's a few years back but they didnt have drivers for sli and raid for my system at the time, I played with it a day or 2 and went back to MS. It has always been on the list to do. I am going to have to try it again.
I just looked, it looks like there are lots of new "distro's" (versions) now a day from back when I tried it.
anyway, thank you very much for the help,
John
once you did this:
C:\ADB>adb push libnvomx.so /system/lib/
1174 KB/s (164764 bytes in 0.137s)
you already copied it, so you must have already had permissions. Therefore this next command:
C:\ADB>adb chmod 644 /system/lib/libnvomx.so
Android Debug Bridge version 1.0.26
was redundant anyways. I suspect you needed to run
adb shell chmod 664 /system/lib/libnvomx.so
for adb to run the command on the transformer(shell) rather than in the dos directory.
AustinMartin said:
once you did this:
C:\ADB>adb push libnvomx.so /system/lib/
1174 KB/s (164764 bytes in 0.137s)
you already copied it, so you must have already had permissions. Therefore this next command:
C:\ADB>adb chmod 644 /system/lib/libnvomx.so
Android Debug Bridge version 1.0.26
was redundant anyways. I suspect you needed to run
adb shell chmod 664 /system/lib/libnvomx.so
for adb to run the command on the transformer(shell) rather than in the dos directory.
Click to expand...
Click to collapse
I see, so shell is like I am running it in/from the TF. I guess that is why push and pull doesn't work in shell, it could be confusing??
I downloaded/installed root explorer but I would rather learn it the harder way.
thanks again for your help!!
John
Cool. I wasn't sure about the "adb chmod" working since I'd only done that from a linux shell before this, but it was worth a shot. If you went into adb shell, then typed "mount -o rw,remount /system"; chmod 644 /system/lib/{whatever that file name was}; and mount -o remount,ro the thatt that would work", or I suspect he is right about how you can use "adb shell chmod 644 /../../.....".
Anyway, glad it worked out.
hachamacha said:
Cool. I wasn't sure about the "adb chmod" working since I'd only done that from a linux shell before this, but it was worth a shot. If you went into adb shell, then typed "mount -o rw,remount /system"; chmod 644 /system/lib/{whatever that file name was}; and mount -o remount,ro the thatt that would work", or I suspect he is right about how you can use "adb shell chmod 644 /../../.....".
Anyway, glad it worked out.
Click to expand...
Click to collapse
Hi,
If I shell, do su, then exit the shell (which I couldn't figure out how to do) do the su rights still apply, if I then use adb commands?
mount and remount, I see those are for mounting partitions, do the partitions each have different rights? and what does chmod do?
thanks again,
John
Xerravon said:
Hi,
If I shell, do su, then exit the shell (which I couldn't figure out how to do) do the su rights still apply, if I then use adb commands?
mount and remount, I see those are for mounting partitions, do the partitions each have different rights? and what does chmod do?
thanks again,
John
Click to expand...
Click to collapse
If you did an $su ; # inside the shell (adb shell), then when you typed in exit, that'd exit the shell, and cause any subshell's kicked off with a command (like "su" to pick one from a hat), to 'go away', So no, you wouldn't still be su.
But: There is a 'switch' or setting somewhere that brings up the adb shell in # su mode, but it escapes me right now.
Mount -o remount,rw||ro /{mountshare} (one command) will just remount some partition like system as you direct it to. It will 'outlast' the adb session. If you leave adb after doing a mount -o remount,rw /system, then you've left /system mounted rw. It doesn't hurt anything, but in theory you type in $sync; sync and $ mount -o remount,ro, and then the clean police will be happier.
chmod changes permissions. You could look up the man page on google, and it'll show you that you have 3 groups, owner, group and world. You could do the command in a couple forms, like #chmod {permission mask like 777} {filename} or chmod w+x {filename} where first one gave all permissions (rwe/rwe/rwe) to some file, 2nd gave the world execute permission.
hachamacha said:
If you did an $su ; # inside the shell (adb shell), then when you typed in exit, that'd exit the shell, and cause any subshell's kicked off with a command (like "su" to pick one from a hat), to 'go away', So no, you wouldn't still be su.
But: There is a 'switch' or setting somewhere that brings up the adb shell in # su mode, but it escapes me right now.
Mount -o remount,rw||ro /{mountshare} (one command) will just remount some partition like system as you direct it to. It will 'outlast' the adb session. If you leave adb after doing a mount -o remount,rw /system, then you've left /system mounted rw. It doesn't hurt anything, but in theory you type in $sync; sync and $ mount -o remount,ro, and then the clean police will be happier.
chmod changes permissions. You could look up the man page on google, and it'll show you that you have 3 groups, owner, group and world. You could do the command in a couple forms, like #chmod {permission mask like 777} {filename} or chmod w+x {filename} where first one gave all permissions (rwe/rwe/rwe) to some file, 2nd gave the world execute permission.
Click to expand...
Click to collapse
hI,
Thanks again, this is over my head right now, I am going to do like you say and search Google for a good beginners site. I am thinking about putting linux on my pc also, been wanting to for a while, I think that will help. I do know a lot more than I did when I started the thread
thank you,
John

ADB Issue

its been over a year since i last used ADB and this is the first time using adb on the optimus 3d but i cannot seem to pull anything off of the phone.
this is the command im using on command line
adb pull /data/app app & adb pull /data/app-private app-private
but i just get this returned
pull: building file list...
0 files pulled. 0 files skipped.
pull: building file list...
0 files pulled. 0 files skipped.
now i can tell you that there are many apks inside that folder.
i cant even list what files are in that directory by using the 'ls' parameter
the only way i can actually view the files is if i
adb shell su
# cd data/app
ls
then it will list the files but i still cannot pull the files it just says data/app/filename.apk cannot find specified file
is this some kind of lock lg have put on or has the adb been updated and no longer allow you to do this?
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
Im guessing no one knows or has not bothered with adb themselves
i did like this
(rooted phone)
enter in adb shell
su
mkdir app1
cp /data/app/*.apk app1
exit from shell
then try adb pull /app1 app
and its working
to remove files and folder from app1 folder in adb shell
rm -r app1 (deletes app folder)
pls note rm -r will delete folders with files so dont delete wrong folder.
cheers didnt think about creating a different directory in an attempt to get round the system, cool will try this many thanks

Categories

Resources