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
Alright, since i had a couple of problems with adb remount, i decided to do some research.
I'm running the latest OTA (2.10.405.2) rooted with Unrevoked 3.21, using Clockwork Recovery Mod 2.5.0.7.
Now once i go to the adb shell and type adb remount, i get the following error: (do mind, this is fully booted, i dont know if a remount is possible while booted?)
adb devices
List of devices attached
BLA12345 device
adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
Ive read something about figuring out if adb recognizes your device as root, so i tried doing this with getprop ro.secure
It returned the following:
adb shell
$ getprop ro.secure
getprop ro.secure
1
Click to expand...
Click to collapse
This means adb does not recognize my device as root, so i booted into recovery, went to adb again and did the same. This time it returned:
adb devices
List of devices attached
BLA12345 recovery
adb shell
~# getprop ro.secure
getprop ro.secure
/sbin/sh: getprop: not found
Click to expand...
Click to collapse
Now, i can always mount the /system partition manually by going into clockworkmod recovery, but i'd like to be able to use adb remount aswell. Does anyone know what's going on and how to fix this
Thanks in advance!
Up.
10 chars
for starters we cant mount /system as r/w while booted... as it stands we dont even need to use the remount command, as we only have r/w access to system whilst in recovery, if you just use the mount /system command, it will automatically be mounted as r/w
AndroHero said:
for starters we cant mount /system as r/w while booted... as it stands we dont even need to use the remount command, as we only have r/w access to system whilst in recovery, if you just use the mount /system command, it will automatically be mounted as r/w
Click to expand...
Click to collapse
Aaah alright, i get the picture now! Seems they have released S-OFF today tho, time to start using remount?
Lunatic2 said:
Aaah alright, i get the picture now! Seems they have released S-OFF today tho, time to start using remount?
Click to expand...
Click to collapse
i only just noticed that after i replied to your post happy days
I'm not sure what I did but whenever I try to do a backup in ROM manager or use it to reboot into recovery nothing happens. I've tried re flashing clockwork mod and using the fix permissions but it gives me an error message stating that an error occurred while attempting to run privileged commands. I can still do a back up like normal if I do it from recovery but I'm a little nervous since ROM manager isn't working.
Do you have S-OFF?
Yes, running virtuous 3.0.1 and radio 2.15.00.07.28
I have the exact same problem, I can boot into clockwork but when I click on recovery it just reboots into clockwork's main page.
Edit: I tried to reflash an older recovery using ROMmanager and it worked, then I flashed the current one, so that might work.
Recovery versions 2.5.0.5 and 2.5.0.1 are OK. Anything later then that has problems and been pulled for the exact problems quoted here.
I have recovery version 2.5.0.5. I tried to flash 2.5.0.1 but I got a message that said "an error occurred while attempting to run privileged commands!"
Folks, there's been a fix posted for this I believe---and I was one of the posters.
This is what worked for me:
In ROM Manager, go to bottom of screen and select All ClockworkMod Recoveries. Simply select an earlier version of CWM. I selected 2.5.0.0. You should be good to go after selecting and hitting OK. Then, after a reboot, you should be able to reselect the latest CWM recovery.
Good luck!
I've already tried that... flashing any version of clockwork gives me the error message "An error occurred while attempting to run privileged commands!"
Check out this post from adrynalyne and see if it helps. Sounds like your issue.
http://adrynalyne.us/?p=90
Sent from my ADR6300 using XDA App
I've never used adb before, any chance someone could walk me through this or point me to a quick guide to get me started?
Look in the stickies section. There's a thread from AndroidBruce for a "How-to." There's a link covering adb. Once it's installed, it's pretty much typing exactly what's written, unless you're big on using linux.
Sent from my ADR6300 using XDA App
I tried that method but no luck. After I entered the command it gave me a message saying "/sbin/sh: system/bin/e2fck: not found"
NewUserNeedsHelp:) said:
I tried that method but no luck. After I entered the command it gave me a message saying "/sbin/sh: system/bin/e2fck: not found"
Click to expand...
Click to collapse
If your on a sense rom use e2fsck_recvy
Sent from my ADR6300 using XDA App
Again, no luck :/ this is beginning to really frustrate me. This is what I typed and what was returned to me, maybe someone can see something I did wrong with it.
C:\android-sdk-windows\tools>adb shell
~ # system/bin/e2fsck_recvy -p /dev/block/mmcblk0p2
system/bin/e2fsck_recvy -p /dev/block/mmcblk0p2
/dev/block/mmcblk0p2 has been mounted 1137 times without being chec
rced.
/dev/block/mmcblk0p2: 13/51200 files (7.7% non-contiguous), 12120/2
~ # exit
exit
Just tried again and got this:
C:\android-sdk-windows\tools>adb shell
~ # system/bin/e2fsck_recvy -p /dev/block/mmcblk-p2
system/bin/e2fsck_recvy -p /dev/block/mmcblk-p2
system/bin/e2fsck_recvy: No such file or directory while trying to open /dev/bl
ck/mmcblk-p2
/dev/block/mmcblk-p2:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
NewUserNeedsHelp:) said:
Again, no luck :/ this is beginning to really frustrate me. This is what I typed and what was returned to me, maybe someone can see something I did wrong with it.
C:\android-sdk-windows\tools>adb shell
~ # system/bin/e2fsck_recvy -p /dev/block/mmcblk0p2
system/bin/e2fsck_recvy -p /dev/block/mmcblk0p2
/dev/block/mmcblk0p2 has been mounted 1137 times without being chec
rced.
/dev/block/mmcblk0p2: 13/51200 files (7.7% non-contiguous), 12120/2
~ # exit
exit
Just tried again and got this:
C:\android-sdk-windows\tools>adb shell
~ # system/bin/e2fsck_recvy -p /dev/block/mmcblk-p2
system/bin/e2fsck_recvy -p /dev/block/mmcblk-p2
system/bin/e2fsck_recvy: No such file or directory while trying to open /dev/bl
ck/mmcblk-p2
/dev/block/mmcblk-p2:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Click to expand...
Click to collapse
the bolded is not the right command
are you adb shelling in recovery, then mounting system, then unmounting cache?
I'm unmounting chache then mounting system and then adb shelling. Does adb shelling mean starting the shell in cmd?
NewUserNeedsHelp:) said:
I'm unmounting chache then mounting system and then adb shelling. Does adb shelling mean starting the shell in cmd?
Click to expand...
Click to collapse
Do you know how to use adb? Not trying to be rude here....just trying to help
boot to recovery, then adb shell (this is in the cmd window), then mount system, then unmount cache, then run the cmd
Lol, no this is my first experience with adb and I have virtually no clue what I'm doing, I'm just trying to follow instructions the best I can. The guide that I was following had me doing things in a different order so I guess I'll have to try this now. Thanks for your assistance and patience!
NewUserNeedsHelp:) said:
Lol, no this is my first experience with adb and I have virtually no clue what I'm doing, I'm just trying to follow instructions the best I can. The guide that I was following had me doing things in a different order so I guess I'll have to try this now. Thanks for your assistance and patience!
Click to expand...
Click to collapse
you have gtalk? check your pm
In case anyone is following this; I still have not fixed the problem.
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or getting flammed because you re-rooted your phone instead of your tablet because you forgot to unplug your phone from the computer while the tablet was plugged in...
Please do some research if you have any concerns about rooting your device! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Ok, this was a pain in the arse!
I hope I can remember the steps I took in order to get this done.
By the way, I'm using windows
adb push mempodroid /data/local
adb push su /data/local
adb shell
$ chmod 777 /data/local/mempodroid
Click to expand...
Click to collapse
Then I went to here as directed,
http://rkeene.org/projects/info/wiki/210
but didn't follow the steps as they were shown because I got stuck many times and had to start over.
So here are my steps.
1.
$ /data/local/mempodroid 0xd9f0 0xaf47 sh
Click to expand...
Click to collapse
which then should turn the $ into a #
2.
# mkdir /data/x-root /data/x-root/bin
Click to expand...
Click to collapse
3. Download this,
http://www.rkeene.org/projects/info/resources/diatribes/root-toshiba-thrive/busybox
and then move the file to where you have mempodroid and su so you can adb push them easier
4.
adb push busybox /data/x-root/bin/busybox
adb push su /data/x-root/bin/su
adb shell
Click to expand...
Click to collapse
5. This is where it got tricky. If you don't pay close attention, you will most likely do what I did and put files where they aren't supposed to go. So please, PAY ATTENTION!
If you still have the # in the shell, move forward. Otherwise,
/data/local/mempodroid 0xd9f0 0xaf47 sh
Click to expand...
Click to collapse
and then move forward once # is confirmed.
# cd /data/x-root/bin
# chmod 755 busybox
# ./busybox bash
Click to expand...
Click to collapse
Now, there is no doubting it, you will get the "bash: precmd: not found" error.
# unset PS1 PROMPT_COMMAND
# ./busybox bash
# for tool in $(./busybox --list); do ln -s busybox $tool; done
# PATH="${PATH}:/data/x-root/bin"; export PATH
Click to expand...
Click to collapse
6. AGAIN, PAY CLOSE ATTENTION HERE!!
# mknod /dev/loop0 b 7 0
# losetup -o 25165824 /dev/loop0 /dev/block/mmcblk0
Click to expand...
Click to collapse
7. This is where I ran into another problem, so pay attention.
# cd /
# mkdir /dev/tmpdir
# ls -l /dev/tmpdir
Click to expand...
Click to collapse
You will see nothing as the steps describe. This is because we skipped a step. Why? Because mount -o ro -t ext4 /dev/loop0 /dev/tmpdir for some strange reason wouldn't unmount so I could mount the next step. So instead, we move on and then check again.
Here is the removed step
# mount -o ro -t ext4 /dev/loop0 /dev/tmpdir
# ls -l /dev/tmpdir
# umount /dev/tmpdir
Click to expand...
Click to collapse
You can try this but I advise not to or you could very well run into the same issue I had where you can't unmount in order to move on with the root process
# mount -t ext4 /dev/loop0 /dev/tmpdir
# ls -l /dev/tmpdir
Click to expand...
Click to collapse
And now you will see /system mounted.
8.
# cp /data/x-root/bin/su /dev/tmpdir/bin/
# chmod 4555 /dev/tmpdir/bin/su
# umount /dev/tmpdir
# losetup -d /dev/loop0
# sync
# reboot
Click to expand...
Click to collapse
9. Now once your A200 reboot and displays the home screen, we will confirm.
adb shell
[email protected]:/ $ su
Click to expand...
Click to collapse
If the $ doesn't turn into a #, you did something wrong...
Thank you hexmare, for opening this thread and giving the guidance.
Thank you d10369319, for "/data/local/mempodroid 0xd9f0 0xaf47 sh", I would have never figured this out.
Thank you RKeene, for writing out the guide to Root the Toshiba Thrive
And Thank you Saurik along with zx2c4, for mempodroid
Ok, for some reason, /system still refuses to mount with "mount -o remount,rw /system"
So my solution is this,
$ su
# cd /data/x-root/bin
# chmod 755 busybox
# unset PS1 PROMPT_COMMAND
./busybox bash
# PATH="${PATH}:/data/x-root/bin"; export PATH
# cd /
# mknod /dev/loop0 b 7 0
# losetup -o 25165824 /dev/loop0 /dev/block/mmcblk0
# mount -t ext4 /dev/loop0 /dev/tmpdir
Click to expand...
Click to collapse
You will have to go to /dev/tmpdir in order to do anything with /system but it is the secret passage way for now...
Why is there still no A200 forum?
agentfazexx said:
Why is there still no A200 forum?
Click to expand...
Click to collapse
Maybe there will be now that we have made some progress...
agentfazexx said:
Why is there still no A200 forum?
Click to expand...
Click to collapse
+1 A200 Forum
Enjoy your ICS A200 owners. I just saw a tweet from AcerAmerica that ICS is being rolling out to A200
Hello to all,
My A200 has been upgraded today 'OTA' , to ICS (V: 4.0.3) , so Europe/France seems to be available, now.
Applying this procedure, all goes fine, and my A200 is rooted.
I'm very happy
A lot of thanks to people having discovered this procedure, particularly mempodroid which set all of this possible.
Greetings
the last time when you do losetup -d /dev/loop0
returns No such device or address?????
ive been through it twice now
*EDIT* Nevermind I figured out my problem...I was typing in reboot instead of using the hardware power button. Got root now, sweet!
I am sooo glad we can now root the a200, but I cannot get mine to work. I have went through the steps 3+ times and had issues each time. I thought I had it twice and then tried Titanium backup root and it said it didn't work.
I can't see at all where I've gone wrong..
That's very strange because Titanium Backup works just fine for me...
rom toolbox pro doesnt work when changing numbers in kernel tweaks...numbers dont stick
titanium works though
ran into a mounting issue
i was attempting to root my A200 with the OTA ICS
first attempt i ran into an issue were i am unable to mount
# mount -t ext4 /dev/loop0 /dev/tmpdir
mount: invalid argument
so i then replaced ext4 to EXT4 and i then received error
# mount -t EXT4 /dev/loop0 /dev/tmpdir
mount: No such device
could some one please tell me where i went wrong thank you in advance
what i do wrong when i try adb push mempodroid /data/local i get evertime this here :/
D:\android-sdk-windows\platform-tools>adb push mempodroid /data/local
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
Ghorn
ghorn222 said:
what i do wrong when i try adb push mempodroid /data/local i get evertime this here :/
Ghorn
Click to expand...
Click to collapse
Go download the drivers from Acer's website for this device
johnsonj067 said:
i was attempting to root my A200 with the OTA ICS
first attempt i ran into an issue were i am unable to mount
# mount -t ext4 /dev/loop0 /dev/tmpdir
mount: invalid argument
so i then replaced ext4 to EXT4 and i then received error
# mount -t EXT4 /dev/loop0 /dev/tmpdir
mount: No such device
could some one please tell me where i went wrong thank you in advance
Click to expand...
Click to collapse
You have to follow the guide to the T or you will run into numerous problems and stop signs. Try again
daimerion said:
rom toolbox pro doesnt work when changing numbers in kernel tweaks...numbers dont stick
titanium works though
Click to expand...
Click to collapse
That's because we don't have a custom kernel yet. Just wait a little while.
Unfortunate the root isn't 100% cool my boot loader Is unlocked though.
Droid 3 bldr is locked down however changing numbers in rom toolbox works w/o custom kernals or modules.
http://www.acertabletforum.com/foru...iscussions/3649-how-unlock-boot-loader-4.html
^this Does work
su file?
This may be a stupid question, but where does one get the su file they're supposed to push to the tablet in the first step? I searched and searched, and finally found one that I downloaded, but when I tried this method with that su file, everything seems to work perfectly, but when I reboot and type su I get a segmentation fault. This is feels like something everyone knows but me, because every guide I can find that has anything to do with rooting from adb it seems the possession of an the su file is just assumed.
shwilson24 said:
This may be a stupid question, but where does one get the su file they're supposed to push to the tablet in the first step? I searched and searched, and finally found one that I downloaded, but when I tried this method with that su file, everything seems to work perfectly, but when I reboot and type su I get a segmentation fault. This is feels like something everyone knows but me, because every guide I can find that has anything to do with rooting from adb it seems the possession of an the su file is just assumed.
Click to expand...
Click to collapse
Did u use reboot command or the power button on the tab? It only worked for me when I used the power button to turn off then on
daimerion said:
Did u use reboot command or the power button on the tab? It only worked for me when I used the power button to turn off then on
Click to expand...
Click to collapse
I tried using the power button. Same result. Where did you get the su file from?
Hello there,
does anyone know how to mount the galaxy s4 as writeable via adb?
mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p9 /system
is the Red Coloured the right Path?
Antalor said:
Hello there,
does anyone know how to mount the galaxy s4 as writeable via adb?
mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p9 /system
is the Red Coloured the right Path?
Click to expand...
Click to collapse
omg no no no no.
if you are talking about trying to use "adb push <name of file> <destination file>"
Then you must use "adb remount" if it fails, you are not on an insecure kernel. Thus your only option is to push to the sdcard then use "adb shell" and navigate to your sd card and use "cp <name of file on sdcard> <destination file location>"
as for the commands, it is NOT what you have posted. it is simply
mount -o rw,remount /system
nothing else is needed. You will seriously mess something up if you try mounting it as yaffs2 considering we use ext4 now. FYI, the above command can only be entered AFTER first entering "adb shell" which gives you a command line on the device to execute commands.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
No, i want uninstall apk's/apps via adb and theerfore i have to mount it as writeable, and, also i want to:
pm list packages -f > file.txt and got error read only system...
What exactly is yaffs2?
Sent from my GT-I9505 using xda app-developers app
Antalor said:
No, i want uninstall apk's/apps via adb and theerfore i have to mount it as writeable, and, also i want to:
pm list packages -f > file.txt and got error read only system...
What exactly is yaffs2?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Then you need to use
adb shell mount -o rw,remount /system
thats it. To uninstall apks, use:
adb uninstall <package name>
And you are getting a read only system error because you are trying to create that "file.txt" file onto your "root" directory.
do this:
adb shell cd /data/media/0
then try to do your list packages.