Database Info

USCC Mesmerize Rooting on Official 2.2 (Froyo)

Okay, this was my first time trying to root my phone and it would figure that non of the automated methods worked for me. Still, I was able to get root on my US Cellular Samsung Galaxy S Mesmerize (SCH-i500 for the kids keeping track at home) and these are the steps that I took. I hope this helps others who may be scratching their head wondering what to do when the developers haven't gotten around to (read: forsaken) us.
The nice thing about this method is that it doesn't require Windows (though you still do download SuperOneClick).
NOTE: This is only for an officially updated Mesmerize. Rooting is unnecessary for the leaked version.
APOLOGY: I can't post any links to anything outside the forum as I am a newer member, so, sorry for not being able to post URLs.
1. Download the Android SDK from the Android developer website and install/unzip it. You may need to add the path to the adb tool (found under platform-tools for me) to your PATH variable.
2. Download the SuperOneClick tool and unzip it
3a. If you are using Windows, then make sure to install the drivers for your phone. I don't have Windows, so don't ask me which file to download. Sorry.
3b. Enable USB Debugging on your phone (Settings->Applications->Development->Check "USB Debugging").
4. Connect your phone to your computer using the USB cable
5. Open a shell (or command prompt on Windows) and change directories to where you unzipped SuperOneClick
6. Run the following commands to copy files to your device
A. adb push psneuter /data/local/tmp/psneuter
B. adb push busybox /sdcard/busybox
C. adb push su-v2 /sdcard/su
NOTE: A quick note of each of these files.
A. psneuter - an exploit to gain root access temporarily on your phone
B. busybox - a compilation of common unix commands to help you along the CLI world
C. su - the super-user command used to gain elevated privileges
7. Run the following command to get a command line interface to your device
adb shell
At this point, you should see a $ prompt indicating that you are on your phone.
From here, you will change directories to where you put the exploit, change the permissions so you can run it, copy over the files that we need to sustain root access, and finally, install the Superuser.apk app so that you can manage root access from the UI.
Execute the following commands:
$ cd /data/local/tmp
$ chmod 777 psneuter
$ ./psneuter
Here, you will be disconnected from your device. This is normal. Just run "adb shell" again to get back in, though now, you will notice that the prompt has changed to a #. The following commands will reflect that.
# mount -t rfs -o remount,rw /dev/block/st19 /system
# cd /system/xbin
# cat /sdcard/busybox > busybox
# cat /sdcard/su > su
# chmod 4755 busybox
# chmod 4755 su
# exit
Now, you will be back on your computer. Type the following to install the Superuser.apk app.
adb install Superuser.apk
That should do it! You now have root access. Go ahead and try to install Titanium Backup (requires root). You can also install a terminal app or anything else.
I hope this helps. Report your successes/failures in the comments.

[GUIDE][ADB]Basic Linux/Unix Commands

Basic Linux/Unix Commands
[HIGHLIGHT] DISCLAIMER - You know the drill. I don't deem myself responsible in case you screw up your phone. Always make a backup if you don't trust yourself and if you know that you screwing up is your forte[/HIGHLIGHT]
Thanks -
mihir287 for his FAQ
sweetnsour for his extensively detailed thread
Shen - advice
Zayed from www.addictivetips.com
http://www.linuxtopia.org
This guide aims to give you a background on some of the linux commands available to you once you obtain an adb shell.
In order to obtain an ADB shell, you must have adb set up on your computer (all ADB really consists of in windows is adb + 2 dlls + adb drivers.
However it makes sense to fully set up the Android SDK if you plan on developing for Android.
You need to install adb or get Terminal Emulator. To install adb and get more info about it visit here.
NOTE = All commands in linux/unix are CASE SENSITIVE.
Shell Commands
These commands are to be typed after typing
Code:
adb shell
In the Command Prompt.
Or, you can proceed normally if you are using a Terminal Emulator.
1. cd - Change Directory
To change to any directory, simply type:
Code:
cd <dirname>
dir name is the path. For instance, to switch to system/etc, type:
Code:
cd /system/etc
'..' will allow you to go back one directory. In our example, typing:
Code:
cd ..
would take you back to /system
2. ls - List Files
To list all the files in whatever directory you're in, simply type:
Code:
ls
pressing enter after, of course. This will list all NON-HIDDEN files/directories.
Code:
ls /system/etc
will list the contents of system/etc
Code:
ls -l
will list all NON-HIDDEN files in your current directory with additional details
Code:
ls -a
will list all files/directories(including hidden) within your current directory
Code:
ls *.extension
will list all the files wit the specified extension in the directory
For example i wanna list all apps -
Code:
cd /system/app
ls *.apk
3. su - SuperUser
The standard adb shell (unless you're on an insecure kernel/ramdisk), will be a non-root shell ($)
To obtain root priviliges (if your phone is rooted), simply type:
Code:
su
on obtaining superuser priviliges, you will be presented with a # symbol, which represent a root shell.
4. chmod - Change Mode
The two most commonly used 'modes' you'll come across in Android are '777' and '755'
These numerical pemissions have different meanings, of course. This can be a little confusing, so I hope this explains it in a simple to understand way.
As you can see, there are three numbers in the following example; 'chmod 755'
So, to break that down: The first number in the sequence, '7', represents the USER (aka, you). The second number in the sequence, '5', represents the GROUP (users who are members of the file's group) and the third number, '5' represents OTHERS (aka, everyone else).
Now to explain why they are 755, and the significance of those numbers, see the following list:
7 Full
6 Read/Write
5 Read/Execute
4 Read Only
3 Write/Execute
2 Write Only
1 Execute
0 None
So in the instance of 777, you can see that USER, GROUP and OTHERS have FULL access to the file in question.
To change the permissions of one file (apns-conf.xml for example, type:
Code:
chmod 777 /system/etc/apns-conf.xml
To change the permissions of all files in a directory, use the -R (recursive)option:
Code:
chmod 777 -R /system/etc
5. pwd - Print Working Directory
Couldn't be more simple. if you want to find out which dirctory you're currently in, type:
Code:
pwd
and press enter.
6. cat - Concatenate (evolved from)
The cat command if used to list a file's contents on your screen; or pass via pipeline to use with other Linux commands.
cat /proc/mounts
will output the various mount points in your android OS.
Note that there are many other uses for the cat command.
7. mount - remount as r/w or r/o
The mount command is used to mount a directory as r/w[Read-Write which allows you to modify it] or r/o[Read-Only]
Mount info -
Code:
mount
To mount as r/w and r/o respectively use -
Code:
mount -o remount rw <dirname>
or
mount -o remount ro <dirname>
To mount /system i will use
Code:
mount -o remount rw /system
or
mount -o remount ro /system
8. cp, mv, rm - Copy, Move, Remove
Use the 'cp' and 'mv' commands to copy, move a file/directory respectively and 'rm' to remove one. They are equivalent to copy+paste and cut+paste and delete
If you are planning to copy/move/remove from your android to anywhere else or viceversa you need to mount as r/w prior to this and mount as r/o after it.
They can be used as
Code:
cp <source> <destination>
or
mv <source> <destination>
or
rm <source>
For example i wanna copy/move/delete my zip file to system/media [after mounting system]
Code:
cp /sdcard/bootanimation.zip system/media
or
mv /sdcard/bootanimation.zip system/media
or
rm /sdcard/bootanimation.zip
9. Auto - Install Applications To SDCard
Type the following -
Code:
pm setInstallLocation 2
10. logcat
A logcat is basically a command to view messages in one of the system logs.
Logcat is the command to view the internal log of the Android system.
Viewing logcat is often the best way - and sometimes the only way - to diagnose a problem.
Dev's always need proper and useful feedback. So if you are testing something, you can always obtain the errors an report back to the dev who in turn can solve your problem efficiently.
Code:
su
logcat > /sdcard/log.txt
Will obtain the logcat to your sdcard as log.txt
Googlers have a sense of humour so even 'lolcat' works identically as 'logcat'
Code:
lolcat
Some dev's require extensive logcat info. To know more about it continue reading here.

ADB Commands
The following commands are to be type in your adb folder directory.
For instance, mine is in C:\android-sdk-windows\platform-tools so i will type
Code:
cd C:\android-sdk-windows\platform-tools
and then proceed with the following code lines
Alternatively you can change your PATH variable
Setting Path on Windows
For Windows XP:
Start -> Control Panel -> System -> Advanced
Click on Environment Variables, under System Variables, find PATH, and click on it.
In the Edit windows, modify PATH by adding the location of the class to the value for PATH. If you do not have the item PATH, you may select to add a new variable and add PATH as the name and the location of the class as the value.
Close the window.
For Windows Vista/Windows 7:
Right click “My Computer” icon
Choose “Properties” from context menu
Click “Advanced” tab (“Advanced system settings” link in Vista)
In the Edit windows, modify PATH by adding the location of the class to the value for PATH. If you do not have the item PATH, you may select to add a new variable and add PATH as the name and the location of the class as the value.
Click to expand...
Click to collapse
1. Check Connected Phone
To display list of available devices, type
Code:
adb devices
You will get the following output
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached 21342737ft6273
where the number indicates your devices serial number usually the one one the back of your phone[needs citation]
2. Login To Android Shell
Code:
adb shell
After pressing enter you will either see '$' or '#'
If you get ‘#’ after typing adb shell, you have already get root access on the phone, no need to type su. Otherwise if you get ‘$’ , type ’su’ to get root access (only for rooted device).
3. Install Application
This command installs the app whose directory is specified by you.
Code:
adb install appname.apk
Note that the name of the application should be without any blank spaces in between. Say i have an app called pes 12.apk, I rename it to pes_12.apk - Also don't miss out the .apk extension
example
Code:
adb install C:\programfiles\pes_12.apk
4. Files From Phone To PC And Vice Versa
For Phone - PC
Code:
adb pull <source> <destination>
For PC-Phone
Code:
adb push <source> <destination>
Example
Code:
adb pull /sdcard/bootanimation.zip C:\programfiles
Code:
adb push C:\programfiles\bootanimation.zip /sdcard
^Self Explanatory
5. Reboot To (Normal/Recovery/Bootloader)
Type the following to reboot normally or to recovery/bootloader respectively
Code:
adb reboot
Code:
adb reboot recovery
Code:
adb reboot bootloader
Some Useful Codes-
I do not know many. If you have any suggestions please do tell me
Type them in line by line and don't type in the '$' and '#'
1. Rooting
Code:
adb devices
adb shell
$ echo 1 > /data/local/lge_adb.conf
Then you can proceed onto using SuperOneClick
2. Installing Custom Recovery
The recovery.img and flash_image files must be in /sdcard
Code:
adb shell
$ su
# mount -o remount rw /system
# cat /sdcard/flash_image > /system/xbin/flash_image
# chmod 755 /system/xbin/flash_image
# flash_image recovery /sdcard/recovery.img
# mount -o remount ro /system
# exit
$ exit
adb reboot recovery

Will add FAQ later if needed

Ohh ! so much detail !
As far as i can see its very well written.
Will read tomorrow

Awesome guide! Thank you!
Sent from my LG-P500 using xda premium

MaKTaiL said:
Awesome guide! Thank you!
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Glad You Like It

Rutuj said:
Glad You Like It
Click to expand...
Click to collapse
I knew Half of this but the way you put it is basically noob written and easy to follow through. Thumbs up for this guide. I wish someone posted this when I first started playing with android. This would've made life easier for me >.<
Sent from my LG-P500 using XDA App

purple1 said:
I knew Half of this but the way you put it is basically noob written and easy to follow through. Thumbs up for this guide. I wish someone posted this when I first started playing with android. This would've made life easier for me >.<
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
This doesnt make life easier, if one command wrong, bam! A fresh brick phone...
Sent from my Nexus One using Tapatalk

and how to uninstall app from adb ?
nice guide btw

Great guide. I would suggest you add details on how to get logcat as well, since many developers will find it useful if users post logs of bugs
Code:
su
logcat > /sdcard/log.txt

mihir287 said:
Great guide. I would suggest you add details on how to get logcat as well, since many developers will find it useful if users post logs of bugs
Code:
su
logcat > /sdcard/log.txt
Click to expand...
Click to collapse
Thanks !
Added !

Bump !

Thanks commands working perfect.
Tell me onething..how did you get time to type all of this?

royalflusher9 said:
Thanks commands working perfect.
Tell me onething..how did you get time to type all of this?
Click to expand...
Click to collapse
Compiling info takes time.
Type time = 30 mins

Nice thread for n00bs like me !!!! Thanks very much!!!1

Bumping this thread

very helpful guide ......
thanxxxx

[LINUX ONLY][ADB] ADB via USB for Trekstor Ventos 8

Hi,
finally I made it to get adb working on Linux without having to struggle with Moborobo
This will be of use only for a really SMALL part of the tablet users, but anyways - it is better to share every piece of knowledge than forgetting it without having told anyone...
So, this only works on Linux (who knows why not on Windows, but the tablets of Nook have the same problem):
You need a working connection to the internet for this! Also you need to be superuser for getting adb to work correctly
1. Download the android SDK for Linux: http://dl.google.com/android/android-sdk_r21-linux.tgz
2. Unpack it and go into your terminal
3. cd into the unpacked directory into the tools folder and type
Code:
$ su
# cd ./android
4. A new window opens. Wait until it updates what it needs to update. Then check only "platform-tools" and download it. When it finished, you can close the window
5. Then type:
Code:
# cd ../platform-tools/
# cp adb /bin/adb
# echo 0x4E22 > /root/.android/adb_usb.ini
# echo 0x1E68 >> /root/.android/adb_usb.ini
# adb kill-server
# adb start-server
# adb devices
And then you should see your device
Way better than doing adb over wifi (for file transmissions, too)
This should work also for many other devices which refuse to get working on Windows machines, the only difference is that you need to get the correct vendor ID from your device (connect it and then type lsusb. The result should be like yyyy:zzzz, to be sure, just add both values in UPPERCASE into adb_usb.ini:
Code:
# echo 0xyyyy > /root/.android/adb_usb.ini
# echo 0xzzzz >> /root/.android/adb_usb.ini
I know, it's a little noobish, but the important thing is that it works
Hope this helps anyone!
Regards

[Discussion] XOLO Q2000L

About the device:
http://www.xolo.in/Q2000L
http://www.gsmarena.com/xolo_q2000l-6495.php
Stock Firmware:
Latest : S017_01-07-2014 (KitKat 4.4.2)
https://drive.google.com/uc?id=0B6xlBPoXgsR3U0JBWm5oT0J5bUU (Source)
Code:
File: Xolo Q2000L S017 01-07-2014-(by_xdafirmware.com).zip
CRC-32: eb227244
MD4: c8d1739be1fe45d43d8fd2a1615d680d
MD5: 07a484331431e523e5067186f07f0ac3
SHA-1: e808227b928fd03f0696ef6e37015432c06fade5
Flashing Instructions:
Prerequisites:
1. Broadcom MultiDownloader
(Latest one I can find is V2.0.1; Source)
2. Broadcom USB Download Device driver
(Latest one I can find is v1.0.5, mirror by @moulnisky. Broadcom uses two interfaces for flashing - one is serial/COM & another is USB but now they encourage to use the later one. Remember that the driver's digital signature isn't valid for 8.1/10 so you need to turn off driver signature enforcement to install the driver. To install the driver manually, open BRCM_WinUSB_ADB_Jungo_MTP_RNDIS_Driver_1.05.exe using 7-Zip, extract the contents & install the using bcmusbdl.inf)
Follow this tutorial, but we need some enhancements:
1. At step 8, I've chosen Download Mode as "Flash All Image" i.e the first one.
2. Skip step 9 & 10, come to step 11 i.e press 'Flash' button.
3. After that, connect the device in flashmode i.e as described in step 9. If Broadcom USB Download Device driver is properly installed, then flashing will begin. FYI, the hardware ID of the flashing interface is USB\VID_0A5C&PID_E720.
USB Debugging:
Broadcom bundles signed drivers for ADB/MTP/RNDIS interfaces along with the device itself (in the emulated CD drive). I've also mirrored it here. As an alternative, you can also use Android USB UnifL driver.
Remember that current ADB binary requires vendor ID whitelisting to detect Broadcom SoC. So execute Broadcom_SoC_Drivers.rar\AndroidPCUSBdrivers\andro id adb\brcm_adb_vendor_id.bat to do it. Otherwise ADB can't see the device, even if drivers are properly installed.
Rooting:
After you are able to communicate with the device through ADB, use iRoot to root it. Make sure to uninstall two Chinese bloatwares that came with Kinguser. I personally prefer to use SuperSU by @Chainfire, so we need to tinker with it again.
1. Install BusyBox.
2. Thanks to @idler1984, we've an easy way to switch from Kinguser to SuperSU. See here, search for "Q: I'd like switching to SuperSU, what shall I do?". I'm also providing the modified steps here which fits our needs:
2.1. Download SuperSU (I prefer the latest beta though). Open the zip, go to armv7 folder & extract the file named "su".
2.2. Use ADB to push su to /data/local/tmp:
Code:
adb push su /data/local/tmp
2.3. Start a su session and run the following commands:
Code:
adb shell
su
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/bin/busybox && chmod 0755 /system/bin/busybox
daemonsu -d &
Then keep the session running.
2.4. Open Kinguser, go to Settings -> Root authorization setting -> Remove Root permission. Click to remove root permission. It may crash but its harmless. Your su session should be still running.
2.5. Uninstall Kinguser app.
2.6. Go back to the su session and run following commands to replace su and cleanup:
Code:
cat /data/local/tmp/su >/system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/bin/ddexe
busybox chattr -ia /system/bin/ddexe_real
cat /system/bin/ddexe_real >/system/bin/ddexe
busybox chattr -ia /system/xbin/ku.sud
rm /system/xbin/ku.sud
rm /system/xbin/pidof
rm /system/xbin/supolicy
2.7. Install SuperSU; get it from SuperSU zip => common\Superuser.apk.
2.8. Open SuperSU to update files & reboot.
2.9. (Optionally) make SuperSU a system app.
Other Notes:
1. This device has fastboot interface too; you can access it by running
Code:
adb reboot bootloader
2. To force install applications in SD card, use this:
Code:
adb install -s NAME.apk

Reserved for future use.

This post is kinda hard to find. But the instructions are good. They all work on my Xolo Q2000L.

Thank u @Titokhan for great help. Please help me over internal app storage issue. This phone is lacking good internal storage even it is having 8gb (5.29 gb on board). Please help.

[TUTORIAL] Resetting a Parental Lock without Factory Resetting (no pre-root required)

So I just spent a few hours digging into this and thought someone might need it sometime down the line.
My wife's job uses a Kindle Fire HD 10 and they have a parental lock on it. Today they needed to change a Wi-Fi setting and couldn't remember the lock password.
The following tutorial will use adb to temporarily root your Fire, update the database to corrupt the lock, and create a new Parental Lock.
What you'll need:
ADB
mtk-su (Download from the first post here, don't worry about using their tutorial since I'll reiterate it here)
1. After you download mtk-su, push it to your device
Code:
adb push path/to/mtk-su /data/local/tmp/
2. Open an adb shell and cd to the data/local/tmp folder
Code:
adb shell
cd /data/local/tmp
3. Write executable permissions to the script
Code:
chmod 755 mtk-su
4. With the screen on, run the script:
Code:
./mtk-su -v
5. You should now be at a root shell (you can tell by the # instead of the $ symbol). Read the mtk-su thread for debugging if you don't get a root shell.
6. Get to your databases folder:
Code:
# cd /data/data/com.android.providers.settings/databases
7. Send some commands to your settings.db to overwrite those parental password values:
Code:
sqlite3 settings.db "insert into secure values(NULL,'parental_password_exist', '0');"
sqlite3 settings.db "insert into secure values(NULL,'parental_control', '0');"
sqlite3 settings.db "insert into secure values(NULL,'com.amazon.parentalcontrols.changed', '0');"
8. Delete the original password salt and key files via:
Code:
rm ./data/securedStorageLocation/com.amazon.parentalcontrols/files/*
9. Congrats, your parental controls are now corrupted! Your WiFi, among other things probably, will not work! Head over to your Settings and click on Parental Controls. Turn them on and create a new password. Now everything will work again.