Database Users

Is there a way to install a recovery image or root from sd card & android terminal?

Is there a way to install a recovery image or root from sd card & android terminal?
Is there a way to install a recovery image or root from sd card & android terminal?
I can't get adb on mac to recognize my phone.

yes if you are on 2.1 do the
Ok ,I figured this out when I was at work and could not use my company computer.
So we need the download.
DroidXRoot_v2.zip
After you download, use a file manager and extract on the sdcard (not in any folder on the root)
Now put the wifi widget on your home screen
Download terminal emulator from the market
Open the terminal . Now comes the fun part.!
code
type these in and hit enter after each one.
cd /sqlite_stmt_journals
cp /sdcard/exploid ./exploid
chmod 755 exploid
./exploid
Now after typing that last command hurry up and hit the home screen button and turn on wifi. After go back in the terminal and type.
rootshell
cp /sdcard/Superuser.apk /system/app/Superuser.apk
cp /sdcard/su /system/bin/su
cp /sdcard/busybox /system/bin/busybox
chmod 4755 /system/bin/su
chmod 4755 /system/bin/busybox
rm /system/bin/rootshell

all credit goes to brian from MyDroidWorld for that

2.2 do this ( credit goes to Eousphoros from droidforums)
open up your favorite terminal emulator program
- cd /tmp
- cp /sdcard/rage*.bin /tmp/
- chmod 777 rage*.bin
- ./rage*.bin
- ignore it's output, we are thinking outside of the box here, just wait for it to finish and return a $
- now go to settings -> applications -> manage applications -> running -> terminal and force close that girlie
- relaunch the terminal app and you should be greeted with the friendly # symbol. Toda you now have a root shell
- the rest is pretty much the same.
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/bin/su
* cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
* chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit

b-dub25 said:
2.2 do this ( credit goes to eousphoros from droidforums)
open up your favorite terminal emulator program
- cd /tmp
- cp /sdcard/rage*.bin /tmp/
- chmod 777 rage*.bin
- ./rage*.bin
- ignore it's output, we are thinking outside of the box here, just wait for it to finish and return a $
- now go to settings -> applications -> manage applications -> running -> terminal and force close that girlie
- relaunch the terminal app and you should be greeted with the friendly # symbol. Toda you now have a root shell
- the rest is pretty much the same.
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/superuser.apk /system/app/superuser.apk
- cp /sdcard/su /system/bin/su
* cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
* chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit
Click to expand...
Click to collapse
nice. Thank you.

What can i do to root a 2.3.4 with a Mac?

How change permissions dir APP by ADB shell?

Hi i have problem with Kindle Fire,
i changed permissions folder system/app with app Root explorer and then I restart Kindle Fire and now dont want start. I think this is problem permissons for this directory.
Pleas can you send me setting permissions folder APP and how i can change it by ADB SHELL?
I have tried:
adb shell
su
chmod 644 app
Unable to chmod app: Read-only file system
THX very much .-(
Sory my english is very bad.

adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
or look here:
http://forum.xda-developers.com/showthread.php?t=1356257
guys please use the search function !

I have tried it but:
$ mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount: Operation not permitted
$ chmod 755 /system/app
chmod 755 /system/app
Unable to chmod /system/app: Read-only file system
THX I'm a little desperate

pitrsonek said:
I have tried it but:
$ mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount: Operation not permitted
$ chmod 755 /system/app
chmod 755 /system/app
Unable to chmod /system/app: Read-only file system
THX I'm a little desperate
Click to expand...
Click to collapse
you need root before you can do any of those (i.e. su)

But i think i have root because I install Google market and other app. Or how i can check if i have root?
THX!
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
4D1A002600000001 device
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ ls
ls
config
dropbox
cache
sdcard
acct
mnt
vendor
d
etc
ueventd.rc
ueventd.omap4430.rc
ueventd.goldfish.rc
system
sys
sbin
proc
init.rc
init.omap4430.rc
init.goldfish.rc
init
default.prop
data
root
dev
$

at the $ prompt type
su
should turn to # instead of $
Then you are Root.

krelvinaz said:
at the $ prompt type
su
should turn to # instead of $
Then you are Root.
Click to expand...
Click to collapse
Yes, what he said...you're confusing having root on the command line for "I installed su and superuser to their correct locations"

adb shell
$ su
su
[1] + Stopped (signal) su
$ su
su
[2] + Stopped (signal) su
[1] Segmentation fault su
$
I have try install root by this manual: http://rootkindlefire.com/kindle-fire-root/how-to-root-kindle-fire/
I see device when i write: adb devices
I have executed runme.bat
but SU dont go

pitrsonek said:
adb shell
$ su
su
[1] + Stopped (signal) su
$ su
su
[2] + Stopped (signal) su
[1] Segmentation fault su
$
I have try install root by this manual: http://rootkindlefire.com/kindle-fire-root/how-to-root-kindle-fire/
I see device when i write: adb devices
I have executed runme.bat
but SU dont go
Click to expand...
Click to collapse
Something is wrong with your device then.

as a first step look if you have superuser.apk in \system\app\

Ho i dont have Superuser.apk in /system/app/

b63 said:
as a first step look if you have superuser.apk in \system\app\
Click to expand...
Click to collapse
Doesn't really matter if su is not working. Superuser.apk is just a wrapper for su and he's trying to do things on the command line so su is what he's calling to, not SuperUser.apk.
He either didnt root correctly to begin with or he did something after that messed things up. Temp rooting with zergRush and redoing things is most likely what he needs to do.

Is ther somebody who can help me online on gtalk? I will pay you by PayPal. If anybody has freetime send me PM. THX
Ther is content dir app:
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ ls /system/app
ls /system/app
-------------------------------------------------------------------------
ATVAndroidClient.apk
AccountAndSyncSettings.apk
AmazonVenezia.apk
ApplicationsProvider.apk
AudibleAndroidApplication-venezia.apk
CSApp-unsigned.apk
CalendarProvider.apk
CertInstaller.apk
Cloud9-unsigned.apk
Cloud9SystemBrowserProvider-unsigned.apk
Contacts.apk
ContactsProvider.apk
DefaultContainerService.apk
DownloadProvider.apk
DownloadProviderUi.apk
DrmProvider.apk
Email.apk
Facebook.apk
Gallery3D.apk
HTMLViewer.apk
IMDb-2.3.apk
KindleForOtter.apk
LatinIME.apk
Launcher.apk
LiveWallpapers.apk
LiveWallpapersPicker.apk
MagicSmokeWallpapers.apk
MarketIntentProxy.apk
MediaProvider.apk
MyAccount-unsigned.apk
OOBE-unsigned.apk
OTASilentInstall.apk
OtterAppManager.apk
OtterTutorial.apk
PackageInstaller.apk
PicoTts.apk
Provision.apk
Pulse-amazon.apk
QuickSearchBox.apk
QuickSettings.apk
Quickoffice_AMAZON_4.1.408_VC.apk
Settings.apk
SettingsProvider.apk
SystemUI.apk
TtsService.apk
UserDictionaryProvider.apk
VisualizationWallpapers.apk
VpnServices.apk
Windowshop.apk
air_runtime.apk
amazonmp3-unsigned.apk
com.amazon.dcp.apk
oem_install_flash_player_signed.apk
Superuser.apk
Vending.apk
$

agree - but it's an indication that his device is not rooted
i would suggest to install superoneclick to the computer and root again
all you need is here : http://forum.xda-developers.com/showpost.php?p=19789892&postcount=35

pitrsonek said:
Is ther somebody who can help me online on gtalk? I will pay you by PayPal. If anybody has freetime send me PM. THX
$
Click to expand...
Click to collapse
Maybe on Thursday I can. Busy until then.

I just run SuperOneClick and there is log http://jsfiddle.net/tVnDv/ from this program.

Kindle Fire is Back
Jupiiie Kindle Fire is back.
So first i try SuperOneClikck install root, but this code doesnt go:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
Then i tried unroot and this code go?
How my Kindle Fire start ,-) Its crazy but true.
Thank you very much guys...

glad to help ...

pitrsonek said:
Jupiiie Kindle Fire is back.
So first i try SuperOneClikck install root, but this code doesnt go:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
Then i tried unroot and this code go?
How my Kindle Fire start ,-) Its crazy but true.
Thank you very much guys...
Click to expand...
Click to collapse
I'm having the same issue, but when I go to change the mount permissions I get permission denied. Anyone care to give me some insight on how to fix it?

you have the $ prompt !!!
type su - the prompt has to change to #
then do the commands ...

[GUIDE] Root Nexus-S 4.0.3 stock firmware without BL unlock

Thanks to nice Kernel exploid found by zx2c4 http://blog.zx2c4.com/749 and sauriks mempodroid https://github.com/saurik/mempodroid its now very easy to root the nexus-s 4.0.3 firmware without unlooking the BL.
You can just follow this howto http://forum.xda-developers.com/showthread.php?t=1461736 but with this offsets kindly provided by saurik: 0xd7cc 0xad27
If you need a clockworkmod just download rom manager from the market and klick install clock work mod.
have fun

Thanks derpeter, I am looking for the related topic for several days!!!
Will try it later, thanks!!!

thank u dear <3

Worked great! Thanks!

Tested and works. Now running stock OTA rooted ICS.

Checked out the link. Though it stated that it is in the transformer prime thread, the adb commands are still the exact same for nexus s?

Yes the same process works you just have to replace the offsets as it says in the first post.
So the process for the Nexus S would be as follows...
Downloads:
mempodroid
su binary
adb push mempodroid /data/local
adb push su /data/local
adb shell
chmod 777 /data/local/mempodroid
/data/local/mempodroid 0xd7cc 0xad27 sh
** You should now be in a remote shell session with root (indicated by #)
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
** IF you have previously rooted your Android, 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
Click to expand...
Click to collapse

Doesn't work for me. And it's annoying. These are the comands. I had done something bad?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Sergiu>cd C:/
C:\>adb push mempodroid /data/local
adb server is out of date. killing...
* daemon started successfully *
627 KB/s (37273 bytes in 0.058s)
C:\>adb push su /data/local
2426 KB/s (22364 bytes in 0.009s)
C:\>adb shell
[email protected]:/ $ chmod 777 /data/local/mempodroid /data/local/mempodroid 0xd7cc
0xad27 sh
id /data/local/mempodroid 0xd7cc 0xad27 sh <
Unable to chmod 0xd7cc: No such file or directory
10|[email protected]:/ $ chmod 777 /data/local/mempodroid/data/local/mempodroid 0xd7
cc 0xad27 sh
oid/data/local/mempodroid 0xd7cc 0xad27 sh <
Unable to chmod /data/local/mempodroid/data/local/mempodroid: Not a directory
10|[email protected]:/ $ chmod 777 /data/local/mempodroid
/data/local/mempodroid 0xd7cc 0xad27 sh
chmod 777 /data/local/mempodroid
/data/local/mempodroid 0xd7cc 0xad27 sh
[email protected]:/ $ /data/local/mempodroid 0xd7cc 0xad27 sh
[email protected]:/ # mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
[email protected]:/ # cat /data/local/su > /system/xbin/su
cat /data/local/su > /system/xbin/su
[email protected]:/ # chown 0.0 /system/xbin/su
chown 0.0 /system/xbin/su
[email protected]:/ # chmod 06755 /system/xbin/su
chmod 06755 /system/xbin/su
[email protected]:/ # rm /data/local/mempodroid
rm /data/local/mempodroid
[email protected]:/ # rm /data/local/su
rm /data/local/su
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\>adb reboot
C:\>
Please help me, I find this metod so f...ing good. I have an i9023, never rooted.

sergiu_s said:
Please help me, I find this metod so f...ing good. I have an i9023, never rooted.
Click to expand...
Click to collapse
I also had trouble following the guide, but then discovered this script, which made the whole process completely automatic.
I'm running stock ICS on i9023.

The script doesn't work for me. I tried it even in Linux. I have stock ics 4.0.3
Sent from my Nexus S using xda premium

Mate u just gain a root. # u log in as root
Sent from my Nexus S using Tapatalk

I saw that, (#), but I don't have root privileges in any application. That's my problem.
Sent from my Nexus S using xda premium

I am not an expert in Android but I think to gain access to app as root would have to go via su app did u try superuser app? I would try it myself but my phone is already rooted via clock mod
Sent from my Nexus S using Tapatalk

I was right mate I just read how to . U haven't got superuser installed obviously. Download from the market and should work.
Sent from my Nexus S using Tapatalk

It worked great guys, thanks to the dev's

I installed superuser and it's works. Thanks guys.
Sent from my Nexus S using xda premium

FYI, this no longer works in 4.0.4. Found out the hard way when I forgot to re-enable the save root option in SuperSU after a nandroid.

The guide works perfectly. I have upgraded my I9020T to 4.0.4 from a AWS 4.0.3 WITHOUT wiping data! Thanks so much!

lethalp1mp said:
FYI, this no longer works in 4.0.4. Found out the hard way when I forgot to re-enable the save root option in SuperSU after a nandroid.
Click to expand...
Click to collapse
ya i did the same thing (didnt run voodoo ota before the 4.0.4 OTA)....looks like google patched this exploit...hope another one comes up so i can root 4.0.4 (without wiping)

nolook said:
ya i did the same thing (didnt run voodoo ota before the 4.0.4 OTA)....looks like google patched this exploit...hope another one comes up so i can root 4.0.4 (without wiping)
Click to expand...
Click to collapse
Yeah i'm also waiting for that!
Sent from my GT-P7300 using XDA

[Q] Mount system in adb to read and write on Nexus 7?

Hi guys,
For the Nexus 7, is there a command I can execute in adb shell root to mount the /system/ to enable reading and writing?
For example for the Galaxy Nexus it was...
mount -o rw,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by- name/system /system
What is it for the Nexus 7?
Thanks!

mdrdroid said:
Hi guys,
For the Nexus 7, is there a command I can execute in adb shell root to mount the /system/ to enable reading and writing?
For example for the Galaxy Nexus it was...
mount -o rw,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by- name/system /system
What is it for the Nexus 7?
Thanks!
Click to expand...
Click to collapse
Shot in the dark:
Code:
adb shell
su
mount -o remount rw /system
then, for example, you should be able to do:
Code:
cp /system/build.prop [destination]
cp [source] /system/

cwoggon said:
Shot in the dark:
Code:
adb shell
su
mount -o remount rw /system
then, for example, you should be able to do:
Code:
cp /system/build.prop [destination]
cp [source] /system/
Click to expand...
Click to collapse
Thank you for replying!
I did try your shot in the dark, however when I tried to do a mkdir test for example I still got:
[email protected]:/ # mkdir test
mkdir failed for test, Read-only file system
I believe the format is like:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
But I don't know the specifics. Any thoughts is appreciated!

What I posted above works on my GNex, was /system your active directory when you tried to mkdir?
I would try on my N7, but its ready to be RMA'd...
Code:
[email protected]:/system # mount -o remount rw /system
mount -o remount rw /system
[email protected]:/system # mkdir test
mkdir test
[email protected]:/system # ls
ls
app
bin
build.prop
etc
fonts
framework
lib
media
test
usr
vendor
xbin
[email protected]:/system # rmdir test
rmdir test
[email protected]:/system # ls
ls
app
bin
build.prop
etc
fonts
framework
lib
media
usr
vendor
xbin
[email protected]:/system #

cwoggon said:
What I posted above works on my GNex, was /system your active directory when you tried to mkdir?
I would try on my N7, but its ready to be RMA'd...
Code:
[email protected]:/system # mount -o remount rw /system
mount -o remount rw /system
[email protected]:/system # mkdir test
mkdir test
[email protected]:/system # ls
ls
app
bin
build.prop
etc
fonts
framework
lib
media
test
usr
vendor
xbin
[email protected]:/system # rmdir test
rmdir test
[email protected]:/system # ls
ls
app
bin
build.prop
etc
fonts
framework
lib
media
usr
vendor
xbin
[email protected]:/system #
Click to expand...
Click to collapse
Your advice worked, I over complicated it. I just did this again on my N7 and worked perfectly. Thank you very much!!!

[Q] Code means Deodex

Hi. What is the meaning of the following code? I mean, what is she?
This is the work that could paste the file or files. Odex to remove that?
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/done_frame/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot

Re: Code means Deodex
"adb shell
su
stop
mount -o rw,remount /system/ /system/" are the commands to get superuser permissions and remount "/system/"
"cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/done_frame/* /system/framework/
rm /system/framework/*.odex" are the commands to push the deodexed .apk files and .jar files from "/sdcard/done_app/" and "\sdcard\done_frame\" to "\system\app\" and "\system\framework\" respectively. The odex files are not required and this also deletes them
"mount -o ro,remount /system/ /system/
reboot" remounts system and reboots your cell phone.
These commands need deodexed system files put in the required directories.
Search the forums or google on how to pull system files and deodex them :good: