Database Info

LG Viper Root

So this is probably the wrong place, but I don't see anywhere more applicable, so please move if necessary.
Bought a LG Viper for the wife today, so had to root it
I found a post elsewhere (can't post URLs yet, but it's on androidcentral) that stated how using SuperOneClick, but personally I'm a CLI kind of guy, so this is for anyone using linux (probably could easily be used on Windows, I think you'd need the "LG Universal Drivers", but )
Getting right to the point, you must have adb installed and working.
Notes: Make sure you've got USB Debugging enabled at this point. Might as well make sure "Unknown Sources" are allowed as well.
Go ahead and plug your phone in to your computer now.
Step 1) Find the device on your computer
In /etc/udev/rules.d/51-android.rules add the following (editing as root):
* Note: I had recently rooted a Kindle Fire and had other config in this file, if you do to you can just prefix the lines with a "#" and it will be ignored. You can find the vendor ID by running 'lsusb'
SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666", OWNER="YOUR-USERNAME", GROUP="YOUR-USERNAME"
Reboot at this point (or restart udev and logout/in)
Step 2) Grab a copy of "rageagaintthecage" and do the following
adb push rageagainstthecage /data/local/tmp
Step 3) Shell time
adb shell
Once you're in the prompt:
chmod 755 /data/local/tmp/rageagainstthecage
/data/local/tmp/rageagainstthecage
* Note: You'll be kicked out out the prompt at this point, as expected.
Step 4) You've got temporary root (if that's all you want, stop now), otherwise let's make it permanent
adb kill-server
adb start-server
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p27 /system
adb push su /system/bin
adb shell chmod 755 /system/bin/su
Step 5) Install tools
On your phone, download "Superuser" and "Busybox Installer"
Run Busybox Installer
Step 6) Enjoy
Post up any questions, glad to help if possible

Which version of su did you use to push to the device?
The temp root has worked but when I go to install Superuser and update I get this error:
Getting exe path failed with 13: Permission denied
Any ideas? Thank.
-Shaun

When I run RATC, how long do I leave it running? I see the adb shell prompt ($) come up, but then the console feeds a line, and doesn't respond. I eventually press ^C to get back to the windows cmd prompt, but I don't know if I'm doing that too soon (it hasn't spawned all the proc it needs to yet) or if it just doesn't work.
when I type "su" into the adb shell after restarting the server, I get
[email protected]:/ $ su
su
/system/bin/sh: su: not found
I pushed a copy of su into /data/local/tmp and made it executable, but that doesn't work.
127|[email protected]:/ $ /data/local/tmp/su
/data/local/tmp/su
reloc_library[1285]: 15938 cannot locate '_mktemp'...
CANNOT LINK EXECUTABLE
255|[email protected]:/ $
Any suggestions?

ADB problem

Hello,
I have a TF300t tablet and i have broken it`s digitizer and changed it myself afterwards. I have changed it with the same type of digitizer but it doesn`t work correctly. I read load of threads and i found a way to repair it by changing the touchscreen pcb firmware. I have rooted the tablet and installed adb on my computer. I tried lots of commands and methods but i can`t push the ekt file to the tablet and i can`t remove the older touch screen firmwares. I will summarise everything i am trying in this picture. I will be very thankfull if somebody can figure out where is the problem. I have installed the newest google usb drivers. The ADB finds the device before i get into the shell but not after that, i think that is the main problem but i`m not sure.
Thank you!
Code:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Бойчо>cd C:\adb
C:\ADB>adb devices
List of devices attached
C5OKCT123824 device
C:\ADB>adb shell
[email protected]:/ $ su
su
[email protected]:/ # adb devices
adb devices
List of devices attached
[email protected]:/ # adb push ss.rar /system/etc/firmware/touch
adb push ss.rar /system/etc/firmware/touch
error: device not found
1|[email protected]:/ # rm /system/etc/firmware/touch *.ekt
rm /system/etc/firmware/touch *.ekt
rm failed for /system/etc/firmware/touch, Is a directory
255|[email protected]:/ # rm /system/etc/firmware/touch/*.ekt
rm /system/etc/firmware/touch/*.ekt
rm failed for /system/etc/firmware/touch/*.ekt, No such file or directory
255|[email protected]:/ #

NapsterEps said:
Hello,
I have a TF300t tablet and i have broken it`s digitizer and changed it myself afterwards. I have changed it with the same type of digitizer but it doesn`t work correctly. I read load of threads and i found a way to repair it by changing the touchscreen pcb firmware. I have rooted the tablet and installed adb on my computer. I tried lots of commands and methods but i can`t push the ekt file to the tablet and i can`t remove the older touch screen firmwares. I will summarise everything i am trying in this picture. I will be very thankfull if somebody can figure out where is the problem. I have installed the newest google usb drivers. The ADB finds the device before i get into the shell but not after that, i think that is the main problem but i`m not sure.
Thank you!
Code:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Бойчо>cd C:\adb
C:\ADB>adb devices
List of devices attached
C5OKCT123824 device
C:\ADB>adb shell
[email protected]:/ $ su
su
[COLOR="Red"][email protected]:/ # adb devices
adb devices
List of devices attached
[email protected]:/ # adb push ss.rar /system/etc/firmware/touch
adb push ss.rar /system/etc/firmware/touch
error: device not found[/COLOR]
1|[email protected]:/ # rm /system/etc/firmware/touch *.ekt
rm /system/etc/firmware/touch *.ekt
rm failed for /system/etc/firmware/touch, Is a directory
255|[email protected]:/ # rm /system/etc/firmware/touch/*.ekt
rm /system/etc/firmware/touch/*.ekt
rm failed for /system/etc/firmware/touch/*.ekt, No such file or directory
255|[email protected]:/ #
Click to expand...
Click to collapse
The red area is where you went wrong, to push a file with adb you cannot be running in shell .....
So from C:\ADB> run adb push ss.rar /system/etc/firmware/touch/
I am not sure why you are pushing a .rar file to your tablet but this is not for me to decide .....
You may have better luck with that .....

Recovering mmssms.db via ADB on Xperia with broken screen

Hi Guys,
My phone's screen has broken and I can't see anything, although the touch still works. I have been able to connect it to the PC to take my music and photos off the internal storage, and my contacts are backed up to Google, but my texts are not and I'd like to recover them.
I've read that they normally reside in /data/data/com.android.providers.telephony/databases/mmssms.db and I should be able to pull this via ADB.
When the phone is booted to the OS it is not detected by ADB at all with 'error: device not found'. I thought USB debugging was on, but obviously not. I can boot to recovery (custom CWM) and now adb will connect to the device. However, when I try to pull the sms db I get 'No such file or directory'
Code:
[email protected] ~ $ sudo adb start-server
[sudo] password for james:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected] ~ $ adb shell
error: device not found
[email protected] ~ $ adb devices
List of devices attached
[email protected] ~ $ adb devices
List of devices attached
CB5122TH5B device
[email protected] ~ $ adb shell
~ # mkdir /mnt/sdcard/tmp
~ # cat /data/data/com.android.providers.telephony/databases/mmssms.db > /mnt/sdcard/tmp/mmssms.db
cat: can't open '/data/data/com.android.providers.telephony/databases/mmssms.db': No such file or directory
~ # su cat /data/data/com.android.providers.telephony/databases/mmssms.db > /mnt/sdcard/tmp/mmssms.db
cat: can't open '/data/data/com.android.providers.telephony/databases/mmssms.db': No such file or directory
/sbin/sh: su: not found
~ # exit
[email protected] ~ $ adb pull su /data/data/com.android.providers.telephony/databases/mmssms.db
remote object 'su' does not exist
~ # ls /data
~ #
It would appear the directory /data is empty but I bet that's because I don't have permissions to view the contents. I'm guessing this is also why su is not found.
Can anyone help me to get over this hurdle? Please bear in mind I'm not familiar with ADB and not great in a Linux shell either; the above commands took a bit of reading to find, but I do understand what they're trying to do.
My phone is a Sony Xperia T LT30p and is rooted running Xperiment 3.5 and Clockworkmod recovery 6.0.4.6 and I'm running ABD on Linux.
Any help would be appreciated! Cheers :good:

adb shell OK yet 'adb logcat -s ...' freezes at "--------- beginning of main"

Code:
adb shell ls
Is OK and lists files. adb devices sees the phone no problem too.
Yet:
Code:
adb logcat -s (any input)
freezes at 'beginning of main'.
For example:
Code:
>adb logcat -s dirtysanta
- waiting for device -
--------- beginning of system
--------- beginning of main
(no more output. tried for hours)
What can I try next? This doesn't really seem like a v20 problem but the xdadevs forum needs me to post here afaik.
edit: I think it was Mcafee, bundled by default and preventing run-as com. After a OTA update I managed to get a temp root prompt.

Is there someone I can pay to help me with this?

Permission denied [cat /proc/partitions]

Dear all,
The Redmi S2 is
- rooted;
- bootloader unlocked;
- oem unlocked;
- on PTP default (Photo transfer).
In ADB debugging,
C:\platform-tools>adb shell
ysl:/ $ cat /proc/partitions
cat: /proc/partitions: Permission denied
How to solve it?
Thanks in advance.
Regards,

Run cmd in Android shell's root mode
Code:
adb shell 'su -c "cat /proc/partitions"'

xXx yYy said:
Run cmd in Android shell's root mode
Code:
adb shell 'su -c "cat /proc/partitions"'
Click to expand...
Click to collapse
Thanks for the reply.
After "adb root", it prompts "adbd cannot run as root in production builds".
And installation of an app "adbd insecure" as below, it produced the same result.
[2014.11.10][ROOT] adbd Insecure v2.00
adbd Insecure lets you run adbd in root mode if your device is rooted. (Note that if you are running a custom kernel, it is likely that it already implements this functionality) If you are running a stock (made by the phone manufacturer) kernel...
forum.xda-developers.com
But "adb shell" apparently works.

On production builds the ADBD server on phone doesn't use root permission. You can't change this.
Simply try what suggested by me.

xXx yYy said:
On production builds the ADBD server on phone doesn't use root permission. You can't change this.
Simply try what suggested by me.
Click to expand...
Click to collapse
I just tried your code in CMD. It returns as follows:
C:\platform-tools>adb shell 'su -c "cat /proc/partitions"'
/system/bin/sh: su -c cat /proc/partitions: not found

That's a complete other issue.

Under "adb shell su", after granting the super privilege, AND then "cat /proc/partitions", I was able to view the partitions.
Thanks.