Related
I'm trying to remove some of the stock apps on my Hero, including Rosie (Sense UI) and such. What mode do I boot in before doing this?
I know all of the steps to remove apps using adb (at least I think I do), I'm fully rooted, etc. But I can't seem to get it to work.
This is the command I'm using in adb
Code:
# rm /system/app/something.apk
(replacing something.apk with the actual apk name of course)
When I boot in Recovery, it says "File not found". When I boot in Fastboot, I can't connect to adb it seems. And when I boot into Android, it says "rm failed for something.apk, Read-only file system"
So am I missing a step? What should I be doing differently?
Boot into recovery, then do a "mount -a" to mount the filesystems.
marinierb said:
Boot into recovery, then do a "mount -a" to mount the filesystems.
Click to expand...
Click to collapse
It doesn't seem to work, here's the output:
Code:
C:\asdk\tools>adb devices
List of devices attached
HT9ALNT00557 recovery
C:\asdk\tools>adb shell
/ # mount -a
mount -a
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or direc
tory
/ #
Thanks for the reply though.
Edit: Got it working, typing in "mount" alone without the -a switch worked Thanks marinierb
in normal mode you cold have just done
adb remount
adb rm /system/app/something.apk
garok89 said:
in normal mode you cold have just done
adb remount
adb rm /system/app/something.apk
Click to expand...
Click to collapse
That doesn't seem to work for me. This is what it outputs:
Code:
remount failed: Operation not permitted
If you can't remount it doesn't sound like you've rooted.
callummr said:
If you can't remount it doesn't sound like you've rooted.
Click to expand...
Click to collapse
I've performed other operations that would normally require it, so I should be rooted.
Is there a way I can confirm if it's properly rooted or not?
shell prompt:
$ .. no root
# .. root
..try typing "su" once in the shell (abd shell or adb-windows.exe shell) and see what it brings up
~David said:
It doesn't seem to work, here's the output:
Code:
C:\asdk\tools>adb devices
List of devices attached
HT9ALNT00557 recovery
C:\asdk\tools>adb shell
/ # mount -a
mount -a
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or direc
tory
/ #
Thanks for the reply though.
Edit: Got it working, typing in "mount" alone without the -a switch worked Thanks marinierb
Click to expand...
Click to collapse
typing only "mount" just list the mounted partitions, it will not mount anything. if your partition is ext4 you need to downgrade it to ext2 or ext3 or set the testflag, see "if you're having issues with ext4" in the first post of the recovery image thread.
Make sure you have run a Nandroid backup first so that if you accidentally remove something important.
Boot into normal mode. (full GUI)
Then:
Code:
C:\ADB MOUNT
C:\ADB SHELL
# rm /system/app/something.apk
reboot
You have to reboot at the end so that the apps are taken out of RAM, you may get FC (errors) if you try to do stuff after removing the apps before rebooting.
I removed (actually moved) *Twit*, Stock*, Launcher*, and a few other things.
HTH,
Unconn
This howto is for those people who are unable to root their Galaxy Tab using any of the automated procedures and do not suffer from CLPS (command-line-phobia-syndrome).
My story: After upgrading my EURO (GSM) Galaxy Tab to JM6 my persistent efforts to root the device using either the z4root or SuperOnClick methods have all been unsuccessful. z4root (v1.3.0) kept crashing at different stages, apparently depending on which and how many background apps were running. With SuperOneClick I never managed to get beyond the "changing permissions" stage.
Since both methods are basically wrappers of the rageagainstthecage application, I tried to perform the rooting procedure manually. Guess what, that worked without any problem and it is pretty easy to do.
The basic steps of the rooting process are:
1) use rageagainstthecage to get a temporary root shell
2) use the temporary root shell to copy three files to the read-only system partition the device
While I find the outlined procedure straightforward, you may not. Anyhow, try this at your own risk.
==== Prerequisites ====
I used Ubuntu 10.10 for this, but it should work on any other distro and on Windows just as well. Whatever OS you use, you need a working adb connection to your Galaxy Tab. Odin or Kies are of no use here.
You need the following binaries
* su
* busybox
* Superuser.apk
* rageagainstthecage
To get the all required files, simply download "SuperOneClickv1.5.5-ShortFuse.zip". That's what I used.
Get it here: http://forum.xda-developers.com/showthread.php?t=803682
Extract the contents of the ZIP, open a command-prompt on your computer and change to the directory where the extracted files are located.
Some advice if shell commands are not your regular cup of tea.
The following instructions show the shell commands. Some are executed on the host computer. Others are executed on the Galaxy Tab. You can differentiate between the two easily: All commands which start with "> " need to be executed in a shell on the host computer. Commands which are prefixed with "$ " are executed on the Galaxy Tab. In both case the ">" and the "$" must not be typed. If you copy+paste from this howto, make sure only to copy the commands and leave out the prompt.
==== Step 1: getting a temporary root shell ====
Copy the rageagainstthecage exploit to a temporary directory.
Code:
> adb push rageagainstthecage /data/local/tmp
263 KB/s (5392 bytes in 0.020s)
Change the file permissions and execute the exploit.
Code:
> adb shell
$ cd /data/local/tmp
$ chmod 777 rageagainstthecage
$ ./rageagainstthecage
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
(other output truncated)
Your shell session will be terminated which will throw you back to the regular command prompt of your host computer.
==== Step 2: restart adb server ====
Now stop and restart the adb server process.
Code:
> adb kill-server
> adb start-server
* daemon not running. starting it now *
* daemon started successfully *
Now reconnect to the Galaxy Tab again. Notice the '#' prompt. This means you have a temporary root shell now. We use this to execute some privileged commands which make the rooting permanent.
==== Step 3: making it permanent ====
First, make the system partition writeable. We need this to be able to copy su, busybox and Superuser.apk to the required locations. Then exit the android shell again.
Code:
> adb shell
# mount -o remount,rw -t rfs /dev/block/stl9 /system
# exit
Now we push busybox and su via adb. Then we install Superuser.apk.
Code:
> adb push busybox /system/bin
> adb push su /system/bin
> adb install Superuser.apk
The final steps are to change the file permissions for su and busybox and then remount the system partition as read-only again.
Code:
> adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/stl9 /system
# exit
That should be all. Try a reboot and some apps which require root, like Titanium Backup. The Superuser.apk should popup a dialog requesting permission.
Hope this helps. Happy rooting.
[update]
This process worked for JMA and JMD as well.
"adb install" Superuser.apk instead of "adb push"
[/update]
It will help me !
Merci ;-)
Fantastic! This is just what I was looking for, thank you! I feel dumb now, because I started a thread of my own right as you posted this. You must just type faster than me
I ran a quick test, and it all looks good. One quick question actually. Why do you mount like this:
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
When most instructions for the Galaxy Tab have you doing something like this:
Code:
# mount -o remount,rw -t rfs /dev/block/stl9 /system
I'm not saying it is wrong, in fact, it actually worked for me. I'm just curious as to why it works like that? My understanding of mounting partitions and such in Linux is a little bit weak, so I like to indulge my curiousity by bugging fine people like yourself
Anyway, thanks again, this did exactly what I needed it to. Well done, I appreciate it.
DavidThompson256 said:
One quick question actually. Why do you mount like this:
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
When most instructions for the Galaxy Tab have you doing something like this:
Code:
# mount -o remount,rw -t rfs /dev/block/stl9 /system
I'm not saying it is wrong, in fact, it actually worked for me. I'm just curious as to why it works like that? My understanding of mounting partitions and such in Linux is a little bit weak, so I like to indulge my curiousity by bugging fine people like yourself
Click to expand...
Click to collapse
Thanks for pointing that out! Actually both the filesystem type and blockdevice name were totally wrong. Apparently the mount command ignores both parameters - at least when they are wrong.
I just verified this as self-punishment for not paying attention:
Code:
# mount
(...)
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
(...)
/system is mounted read-only to /dev/block/stl9. This is the normal state of things.
Now I remount this without the fstype parameter and using a wrong blockdevice name:
Code:
# mount -o remount,rw /dev/block/xyz /system
# mount
(...)
/dev/block/stl9 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
(...)
Surprise, this actually remounts /system in read-write mode. This is why my original howto worked despite using the wrong parameters.
Thanks again. I corrected the HOWTO.
It works for me, but i get now error message: The application calendar save (proces com.android.providers.calendar) is unexpecly stopt. Try again. Forced closing
I had this also with SuperOneClick.
When i want to start the calender in the applications i get it also.
The application wil not run anymore.
How can i resolved this.
Thnx
leonreijnders said:
It works for me, but i get now error message: The application calendar save (proces com.android.providers.calendar) is unexpecly stopt. Try again. Forced closing
I had this also with SuperOneClick.
When i want to start the calender in the applications i get it also.
The application wil not run anymore.
How can i resolved this.
Thnx
Click to expand...
Click to collapse
That is strange. The result of the rooting process is just adding three files to the system partition. I find it hard to believe that this could lead to the problem you describe. However, while experimenting with z4root I had the the effect that there were many rageagainstthecage processes running in the background and the Galaxy Tab slowed down considerably. Perhaps there is something similar going on.
Have you tried rebooting after completing the rooting process?
Try shutting down the Tab completely.After rebooting get a shell on the Tab with "adb shell" and execute "ps". That shows the process list. If that looks normal, I would try a factory reset of the device. Which ROM version are you running?
BlackLevel: Thank you soooooooooo much... I don't get how to hit the Thanks Meter thing, but here is the old fashioned way. I used a MacBook to accomplish your perfect, step by step rooting of an AT&T Galaxy Tab i987. It helps that I'm more comfortable at the command line than with most GUI systems.
I could put this into a bash script, but that could be dangerous. People really need to look at whats happening with 'adb' and have some idea of what adb is for. I did renamed your 'adbmac' to 'adb', then I could cut and paste from your instructions except for adding ./ before the adb... ie. ./adb shell
Again, wonderful work at pulling this all together in one place.
Jeff
This guide worked perfectly! I love a nice quiet clean root and it doesn't get any better than this. You my friend deserve a cookie!
Hi Guys,
I flashed to JMA, rooted it with One Click Root, and everxthing seemdet to be okay, but activating OCLF failed....is there anybody with the same problem?
Jan
Thanks a lot !. It's clean and doesn't need a kies ...
Just a question : after reboot I have to use "su" after "adb shell" to become root.
Is there any way to be root directly after adb shell ?
And thanks again ...
Mike
mbaroukh said:
Just a question : after reboot I have to use "su" after "adb shell" to become root.
Is there any way to be root directly after adb shell ?
Click to expand...
Click to collapse
The reason is that "/sbin/adbd" (the adb daemon) is running as the shell user. It would need to run as root user instead. This requires changes to the initial ram disk where adbd the relevant settings are stored.
Dealing with "insufficient permissions for device"
Thanks, this worked for me.
One small thing: running from a Linux sustem (Ubuntu 9.04), to overcome a "insufficient permissions for device" problem, I had to put my Ubuntu terminal session into su mode and restart the ADB server -- cf. groups.google.com /group/android-discuss/browse_thread/thread/f85a795644e65b59?pli=1 :
[[
adb kill-server
sudo adb start-server
adb devices
]]
gklyne said:
One small thing: running from a Linux sustem (Ubuntu 9.04), to overcome a "insufficient permissions for device" problem, I had to put my Ubuntu terminal session into su mode and restart the ADB server -- cf. groups.google.com /group/android-discuss/browse_thread/thread/f85a795644e65b59?pli=1 :
[[
adb kill-server
sudo adb start-server
adb devices
]]
Click to expand...
Click to collapse
Thanks for the feedback. On my Ubuntu 10.10 adb runs under my regular user-id (1000) and I do not have to use sudo or run the local adb server as root. That might be due to the way the udev rules are set up. Mine are rather unrestrictive and look like this:
Code:
$ cat /etc/udev/rules.d/51-android.rules
SUBSYSTEMS=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEMS=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
How do yours look like?
Which is the more simple method for root of galaxy tab euro ?are there ?
the incredible said:
Which is the more simple method for root of galaxy tab euro ?are there ?
Click to expand...
Click to collapse
Try z4root or SuperOneClick. Both methods are wrappers of the rageagainstthecage exploit and try to automate the manual process outlined here.
This thread should be a sticky. Worked like a charm.
z4root is very simple method..thanks.
thanks to Germany...
I agree, this thread should be sticky. Finaly some sense in android devel section...
Thank you very much for your guide!
I followed all the instructions in your guide, everything seems fine until I try to push the busybox and su to my Galaxy Tab.
blacklevel said:
Now we push busybox and su via adb. Then we install Superuser.apk.
Code:
> adb push busybox /system/bin
> adb push su /system/bin
> adb install Superuser.apk
[/update]
Click to expand...
Click to collapse
I received an error: "failed to copy 'busybox' to '/system/bin/busybox' : No space left on device\"
the same error for the 'su' too
(No space left on device) is impossible, my tab is brand new sealed when i got it.
I have been trying the z4root and SuperOneClick procedure to root this tab but are all unsuccessful.
I am not sure if it is because of my tab needed a "NAND unlock" (I cannot find any guide about the NAND unlock) because I received this message when I tried to install busybox from the market.
Please help! My tab is carrier locked to Bell Canada, I really wanna to unlock it and root it~
Thanks!
gummo6869 said:
I received an error: "failed to copy 'busybox' to '/system/bin/busybox' : No space left on device\"
the same error for the 'su' too,
Click to expand...
Click to collapse
The `no space left on device` message indicates that the /system partition is still read-only. That means the mount command in step 3 was unsuccessful. Did you get any error message when you executed it?
I just upgraded my GNex GSM yesterday.
It's now smoother than ever before...
But one thing is I wanna get root access on my GNex
GSM 4.0.4 IMM76D.
Is there any CF-Root or something available now...?
here it comes in 3...2....1........
.4 is unrootable. Would've known if you searched.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
zeyarwynntun said:
I just upgraded my GNex GSM yesterday.
It's now smoother than ever before...
But one thing is I wanna get root access on my GNex
GSM 4.0.4 IMM76D.
Is there any CF-Root or something available now...?
Click to expand...
Click to collapse
This question sounds more like: I just lost my glassess and I don't know how to read!
http://forum.xda-developers.com/showthread.php?t=1382163
Try a search, You might find one of the 20ish threads that have an answer in it on how to root your Gnex.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
@rbiter said:
.4 is unrootable. Would've known if you searched.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Click to expand...
Click to collapse
10/char
Galaxy Nexus Toolkit v5.6
Oh, yes, I've lost my glasses...
I just have my GNex rooted with Galaxy Nexus Toolkit v5.6
zeyarwynntun said:
Oh, yes, I've lost my glasses...
I just have my GNex rooted with Galaxy Nexus Toolkit v5.6
Click to expand...
Click to collapse
Is it possible to root without using cwm?
I'm not interested in flashing non stock images.
sblantipodi said:
Is it possible to root without using cwm?
I'm not interested in flashing non stock images.
Click to expand...
Click to collapse
No, it is not possible to root IMM76D without using CWM.
That said, you DO NOT have to flash CWM to be able to use it...
EDIT: j.go (who posted below me) is right. You can root by booting an insecure kernel (which by the way is what CWM is), and copying the two files over using ADB (which is essentially what CWM does, but much easier).
efrant said:
No, it is not possible to root IMM76D without using CWM.
That said, you DO NOT have to flash CWM to be able to use it...
Click to expand...
Click to collapse
You can root without CWM. Fastboot boot with unsecure boot image. Adb push su and superuser.apk. Reboot. Congratulations, you are rooted.
j.go said:
You can root without CWM. Fastboot boot with unsecure boot image. Adb push su and superuser.apk. Reboot. Congratulations, you are rooted.
Click to expand...
Click to collapse
I don't understood, can you make a step by step guide please?
I want to root my phone leaving as much as stock items as possible.
How to root ANY build, on a GN with an unlocked bootloader
Note: There is currently no way to root IMM76D (i.e., 4.0.4) without an unlocked bootloader. The following method is for devices with unlocked bootloaders.
Method 1
1) Download CWM from here to your computer: http://forum.xda-developers.com/showthread.php?t=1357642 and rename it cwm.img.
2) Download the attachments from here to your computer: http://forum.xda-developers.com/showpost.php?p=23290676&postcount=1
3) Download this to your /sdcard on your device: http://www.box.com/s/jvcf196j7x8f8vrc9cyt
4) Extract all the files into one directory, and put cwm.img in there
5) Restart your device in fastboot mode and plug into computer
6) Open a command prompt in the directory mentioned above and type: fastboot boot cwm.img
7) Wait for it to boot
8) Navigate the menus. There is an option like "update zip from sdcard". Find the zip that you downloaded, and apply it.
9) Reboot. Done.
Method 2 (more manual)
1) Download CWM from here: http://forum.xda-developers.com/showthread.php?t=1357642 and rename it cwm.img If you are having problems, download the attachment from here and use it instead of CWM.
2) Download the attachments from here: http://forum.xda-developers.com/showpost.php?p=23290676&postcount=1
3) Extract all the files into one directory, and put cwm.img in there
4) Restart your device in fastboot mode and plug into computer
5) Open a command prompt in the directory mentioned above and type: fastboot boot cwm.img
6) Wait for it to boot
7) In the command prompt, type the following:
adb push su /data/local/tmp/su
adb push Superuser.apk /data/local/tmp/Superuser.apk
adb shell
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
cat /data/local/tmp/su > /system/bin/su
cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
exit
8) Done.
Note: if you are having problems mounting /system in CWM, try doing it in CWM itself (on device via the menu), instead of typing in the command.
EDIT: Added title and note.
efrant said:
1) Download CWM from here: http://forum.xda-developers.com/showthread.php?t=1357642 and rename it cwm.img
2) Download the attachments from here: http://forum.xda-developers.com/showpost.php?p=23290676&postcount=1
3) Extract all the files into one directory, and put cwm.img in there
4) Restart your device in fastboot mode and plug into computer
5) Open a command prompt in the directory mentioned above and type: fastboot boot cwm.img
6) Wait for it to boot
7) In the command prompt, type the following:
adb push su /data/local/tmp/su
adb push Superuser.apk /data/local/tmp/Superuser.apk
adb shell
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
cat /data/local/tmp/su > /system/bin/su
cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
exit
8) Done.
Click to expand...
Click to collapse
this will give me the root access on a stock 4.0.4 phone?
in the thread at point 2) is wrote that this does not work on 4.0.4.
sblantipodi said:
this will give me the root access on a stock 4.0.4 phone?
Click to expand...
Click to collapse
Yes.
sblantipodi said:
in the thread at point 2) is wrote that this does not work on 4.0.4.
Click to expand...
Click to collapse
That is why you are not following the directions in that thread. You are following the directions in this thread, right?
efrant said:
Yes.
That is why you are not following the directions in that thread. You are following the directions in this thread, right?
Click to expand...
Click to collapse
lol... great
do you think that this way of rooting will create problem in future OTA notifications?
sblantipodi said:
lol... great
do you think that this way of rooting will create problem in future OTA notifications?
Click to expand...
Click to collapse
No, it will not. Rooting by ANY method does not affect OTAs...
P.S. There is a slightly easier method that I will add to the previous post soon. (I wanted to put in the fully manual method so you can see what is happening.)
Another question, I am an app developer so adb and fastboot are in my default path from the original SDK.
Can I use my ADB and FastBoot from my SDK?
sblantipodi said:
Another question, I am an app developer so adb and fastboot are in my default path from the original SDK.
Can I use my ADB and FastBoot from my SDK?
Click to expand...
Click to collapse
Yes.
10 char
Hey efrant, if I wanted to remove the Superuser.apk and su files already on the device, could I follow Method 2 and fastboot boot cwm.img then do the following in step 7:
adb shell
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
rm /system/bin/su
rm /system/app/Superuser.apk
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
exit
Then once done, disconnect usb cable and reboot the device?
This would essentially leave me with stock recovery, locked bootloader and no root - correct?
ruffneckc said:
Hey efrant, if I wanted to remove the Superuser.apk and su files already on the device, could I follow Method 2 and fastboot boot cwm.img then do the following in step 7:
adb shell
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
rm /system/bin/su
rm /system/app/Superuser.apk
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
exit
Then once done, disconnect usb cable and reboot the device?
This would essentially leave me with stock recovery, locked bootloader and no root - correct?
Click to expand...
Click to collapse
Is your bootloader locked or unlocked currently? You cannot use fastboot commands if your bootloader is locked.
Assuming that your bootloader is unlocked, your procedure is correct, although you would have to relock you bootloader afterwards by booting into fastboot mode, and typing: fastboot oem lock
However, re-locking is something that I never recommend to anyone.
efrant said:
Is your bootloader locked or unlocked currently? You cannot use fastboot commands if your bootloader is locked.
Assuming that your bootloader is unlocked, your procedure is correct, although you would have to relock you bootloader afterwards by booting into fastboot mode, and typing: fastboot oem lock
However, re-locking is something that I never recommend to anyone.
Click to expand...
Click to collapse
My bootloader is currently locked. Regarding re-locking it, I'm just curious as to why you don't recommend it? Essentially, I want keep the option of getting OTAs and get rid of the "Unsupported Device" message in Google Wallet. I read that the app checks for root by looking for the two files and whether the device release keys are modified.
I really appreciate your help.
i have made a CWM flashable su.
if anyone wants. instead of going through all the mount, and copy process,
you will just need to flash the su from the zip file,
go to play store and install the Superuser.apk and then from that update su to the latest version.
if interested, let me know.
Hey all,
I was trying to push nano to my phone and I get this:
C:\>adb push nano /system/bin
failed to copy 'nano' to '/system/bin/nano': Read-only file system
Trying remount:
C:\>adb remount
remount failed: Operation not permitted
Then from ADB shell, I try:
c:\>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o rw,remount /system
mount -o rw,remount /system
[email protected]:/ #
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
c:\>adb push nano /system/bin
failed to copy 'nano' to '/system/bin/nano': Permission denied
Any ideas? I'm rooted the superuser and busybox installed.
I rooted using this method:
http://forum.xda-developers.com/showthread.php?t=1956432
Apps get elevated privileges without error. Terminal emulator allows me to view system files. Unfortunately I need to edit some program files in /data/data and there doesn't seem to be any editor available (vi is acting very glitchy). I discovered this problem when I tried to push nano to my phone.
I also tried to access /data using gEditor and it says:
file list
/data
cannot change the directory.
Something is very wrong here. Do I need to re-root using a different method? Please advise. Thanks!
Update: I was able to get adb to work. It turns out I never flashed an unsecured boot image.
However, my nano installation doesn't work and gEditor crashes when I try to access the data folder. That will be for another thread.
For remount and push/pull commands to work, download adbd insecure from playstore . That's the only way you will be able to do the aforementioned commands.
Thanks for the tip. After rerooting the phone with an unsecured image I was able to use adb. I am able to use adb right now without adbd installed however.
Sent from my SGH-T889 using xda app-developers app
I was going crazy allover looking for an answer, and found it here...
Thanks.
Not compatible
teshxx said:
For remount and push/pull commands to work, download adbd insecure from playstore . That's the only way you will be able to do the aforementioned commands.
Click to expand...
Click to collapse
Is there any other option?? That software is not compatible with my android!!
You will have to flash a kernel which has adb secure set to 0.
Sent from my SGH-T889 using xda app-developers app
I have been trying for hours now to remount the /system partition rw using terminal emulator with no luck. I can do it just fine using root explorer, but thats not what im after. Im trying to make it so that system is mounted rw on boot. But every command i have known to work in the past, and every one i found thru googling has not worked. The command finishes with no errors, but /system is still ro. I even went as far as to unpack the boot img and change /system to be rw on mount. But again when i boot up /system is still ro. Its like something is protecting it or remounting it ro again. By editing the boot.img i was able to mount the root directory (/) rw on boot, but doing the same edit to the /system mount point seems to have no effect. Anyone know what im missing here? I am s-off, unlocked, i have an insecure boot.img, i have root, i dont know how much more insecure my phone could be. If root explorer and other apps are able to do it, there has to be a way to do it thru a shell.
cmlusco said:
I have been trying for hours now to remount the /system partition rw using terminal emulator with no luck. I can do it just fine using root explorer, but thats not what im after. Im trying to make it so that system is mounted rw on boot. But every command i have known to work in the past, and every one i found thru googling has not worked. The command finishes with no errors, but /system is still ro. I even went as far as to unpack the boot img and change /system to be rw on mount. But again when i boot up /system is still ro. Its like something is protecting it or remounting it ro again. By editing the boot.img i was able to mount the root directory (/) rw on boot, but doing the same edit to the /system mount point seems to have no effect. Anyone know what im missing here? I am s-off, unlocked, i have an insecure boot.img, i have root, i dont know how much more insecure my phone could be. If root explorer and other apps are able to do it, there has to be a way to do it thru a shell.
Click to expand...
Click to collapse
Try this:
Create an executable script - like this one:
Code:
#!/system/bin/sh
# Make system rw
chmod 666 /system;
mount("ext4", "EMMC", "/dev/block/mmcblk0p35", "/system");
Save it in your storage location as systemmount (or whatever).
Open terminal, type su.
Type:cd /sdcard/
Type: systemmount
Exit and see if that works. I have not tested it.
Thanks but no luck
Code:
exec /system/bin/sh '/storage/emulated/legacy/Download/scripts/00remount'
/Download/scripts/00remount' <
Unable to chmod /system: Read-only file system
/storage/emulated/legacy/Download/scripts/00remount[4]: syntax error: '"ext4",' unexpected
Put the mount first before chmod. Delete ext4 and emmc
Sent from my Lunar Ecliptic One.
Thanks, but i figured it out. It turns out the command i had used in the first place was correct. (mount -o remount,rw /system). After i ran the command i would check with root explorer to see if it worked, and it always showed it did not. But when you check it the correct way, the way i shoukd have been in the first place, by typing 'mount' in terminal it shows it did indeed get remounted rw. So its an issue with root explorer, not with the command i was using.
Incidently if you do the command 'mount' without su permission, it shows sysyem as ro, but if you do it under an su prompt it shows it as rw.
cmlusco said:
Thanks, but i figured it out. It turns out the command i had used in the first place was correct. (mount -o remount,rw /system). After i ran the command i would check with root explorer to see if it worked, and it always showed it did not. But when you check it the correct way, the way i shoukd have been in the first place, by typing 'mount' in terminal it shows it did indeed get remounted rw. So its an issue with root explorer, not with the command i was using.
Incidently if you do the command 'mount' without su permission, it shows sysyem as ro, but if you do it under an su prompt it shows it as rw.
Click to expand...
Click to collapse
Nice work.
Sent from my Lunar Ecliptic One.