I was following this thread http://en.miui.com/thread-183258-1-1.html for resizing system partition. ADB worked fine when phone was switched on and "adb shell" command worked fine. But when I rebooted into recovery mode and typed the same command I got this "/sbin/sh: su: not found" error. I tried to mount /system in recovery mode but in vain.
Please guide!
Thanks!
make sure u have rooted
boot into twrp
umount data cache and system and also disable mtp
use twrp filemanager go to system/bin chmod to 755 and copy parted to system/bin
now u can try adb shell
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
Got bored of searching and googleing... but using MoDaCo's WIP R4 FroYo ROM and Clockwork Recovery... when I flashed the ROM I lost the boot time animation (the PC BIOS one) so tried to put it back in recovery using adb push *file* /data/local (file copied ok) but still only have the htc boot screen also tried pushing the file with the phone booted, but again no dice
Anyone got any ideas?
Thanks in advance
------ Resolution ------
Ok, firstly massive thanks to those who helped - you are what xda is all about ... I finally managed to resolve this problem by
adb mount /system
adb shell
looking around and removing all bootanimation.zip's I could...
then exit the shell session and adb push the bootanimation.zip to /system/media
adb reboot and
I found this info here: http://androidforums.com/all-things-root-droid/97562-froyo-boot-animation.html
Not sure why this keeps changing? Maybe it is something specific to the Modaco R5 ROM?
Try pushing it to /system/customize/resource
yes the directory for froyo is the
/system/customize/resource
thanks for the assist guys, I tried this in recovery
"adb push bootanimation.zip /system/customize/resource" which went ok, the adb reboot and no show with the new boot screen any ideas??
Many thanks
first of all
mount the /system
then the path should be /system/customize/resource/bootanimation.zip
still cant get it to work I'm afriad
Here is what I did...
reboot to recovery (clockwork mod)
adb shell mount /system/
adb push bootanimation.zip /system/customize/resource
adb reboot
and no new boot animation
any ideas what I'm doing wrong?
Ok, found this http://forum.xda-developers.com/showthread.php?p=7239986 - booted to clockworkmod recovery and tried:
adb shell
mount /system
and got "mount: mounting /dev/block/mtdblock3 on /system failed: Device or resource busy
MadMic said:
still cant get it to work I'm afriad
He is what I did...
reboot to recovery (clockwork mod)
adb shell mount /system/
adb push bootanimation.zip /system/customize/resource
adb reboot
and no new boot animation
any ideas what I'm doing wrong?
Click to expand...
Click to collapse
Is that a typo? the path for the first adb command entry should be 'adb shell mount /system', not 'adb shell mount /system/'
Also, where are you placing the bootanimation.zip file? try placing it directly to the C: (C:\bootanimation.zip) and try executing the commands again.
MasDroid said:
Is that a typo? the path for the first adb command entry should be 'adb shell mount /system', not 'adb shell mount /system/'
Also, where are you placing the bootanimation.zip file? try placing it directly to the C: (C:\bootanimation.zip) and try executing the commands again.
Click to expand...
Click to collapse
Thanks for the reply -
The bootanimation.zip is in the same folder as adb... it says xxx bytes copied which is the same as the file size... I've tried with /system with and without the trailling / still no joy..
If I do adb shell mount /system in recovery I dont see anything... but if I do adb shell [enter] then the commands I see the error about the device being busy...
Is there anyway to do this from a terminal app in the phone directly?? I seem to recall there is but cant find it...
Thanks for the help guys
Here is the process
adb shell
cd cache
mkdir recovery
cd /
cp /sdcard/log /cache/recovery/
cp /sdcard/last_log /cache/recovery/
dd if=/sdcard/updaterecovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
idme bootmode 0x5001
reboot
The cp command doesn't work on windows, IDK why but thats how it is, i figured I substitute cat /mnt/sdcard instead of cp/sdcard, but again dd command doesn't work even with /mnt/sdcard. Can someone please help me through the rest of the process? And no i don't have linux/mac computers.
Here are the rest of the steps
Now in recovery, you will see that the first option highlighted, is Install update.zip from sdcard. Press the Power button (ok).
When prompted to install, press the Power button again. The recovery is modded because it can’t be navigated through right now. No here is actually Yes so just select that.
Once the ROM is flashed, without rebooting your phone, open up command prompt or terminal and navigate to the location where the stock recovery is.
Now enter the following commands:
adb shell
mount sdcard
exit
adb push/sbin/
dd if=/sbin/stockrecovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
adb reboot
The device will reboot twice now, and once it’s done, the CM7 logo will appear. For updates and queries,
It's simple install Ubuntu in windows using wubi .... It installs like a program and then u boot into it ... Don't be afraid of a penguin ....
You may just fall in love with a real operating system and check out mint ... Too
Sent from my SPH-D710 using xda premium
i believe you are missing a "su" command after adb shell
Yeah....you need adb shell, then SU to make the prompt go from $ to #. Try the commands then. They all work in win7, as I did it last night....three or four times.
Sent from my Kindle Fire using Tapatalk
Wrong forum!!!
I am stuck on:
Now enter the following commands:
adb shell
mount sdcard
exit
adb push/sbin/
dd if=/sbin/stockrecovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
adb reboot
it just wont mount the sdcard says its busy, nevermind i rebooted and it worked.
But now i am stuck on the sbin part, i must be missing something
Ok, once again nevermind, i just modified the first recovery command to:
dd if=/sdcard/stockrecovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
and it worked out at cm7 boot anim right now.
Try "ADB shell" then "Su" then "Mount /sdcard"
Minus the " "
Sent from my Kindle Fire using Tapatalk
After repartition of internal memory i cant enable wifi and bluetooth.From that i understand the script didnt make proper backup and restore of
:customfs.img
fsc.img
fsg.img
parinfo.img
persist.img
ssd.img
Does anyone know how to flash again these file or whole system?
I had already used:
1)nandroid restore from previous condition
2)flash stock rom from stock recovery with no success...
Every opinion will be helpful......
i flash manually the files from recovery so now im ok.
Steps
1)Download this file (has everything you need) http://d-h.st/RLS
2)Unzip it
3)Boot Into recovery
4)Open a command promt on the unziped folder
5)Copy paste one by one these commands into command promt
Code:
adb shell mkdir /storage/sdcard1
adb shell mount /dev/block/mmcblk1p1 /storage/sdcard1 -t vfat
adb push part1.sh /tmp/part1.sh
adb shell chmod 0777 /tmp/part1.sh
adb shell /tmp/part1.sh
adb push persist /storage/sdcard1/persist
adb push customfs /storage/sdcard1/customfs
adb push fsg /storage/sdcard1/fsg
adb push fsc /storage/sdcard1/fsc
adb push ssd /storage/sdcard1/ssd
adb shell busybox dd of=/dev/block/platform/msm_sdcc.1/by-name/persist if=/storage/sdcard1/persist
adb shell busybox dd of=/dev/block/platform/msm_sdcc.1/by-name/customfs if=/storage/sdcard1/customfs
adb shell busybox dd of=/dev/block/platform/msm_sdcc.1/by-name/fsg if=/storage/sdcard1/fsg
adb shell busybox dd of=/dev/block/platform/msm_sdcc.1/by-name/fsc if=/storage/sdcard1/fsc
adb shell busybox dd of=/dev/block/platform/msm_sdcc.1/by-name/ssd if=/storage/sdcard1/ssd
You are ready
i have same problem with z7 max but in mine situation i cant see sim cards
can i use the same?
Petros_tigra said:
After repartition of internal memory i cant enable wifi and bluetooth.From that i understand the script didnt make proper backup and restore of
:customfs.img
fsc.img
fsg.img
parinfo.img
persist.img
ssd.img
Does anyone know how to flash again these file or whole system?
I had already used:
1)nandroid restore from previous condition
2)flash stock rom from stock recovery with no success...
Every opinion will be helpful......
Click to expand...
Click to collapse
hi ,
i have zte nubia z7 mini and i was installing z5s mini miui rom in my phone. when the process done phone went to off and hard to turn it on. when i connect to pc it doesn't even detect the phone usb and asking for installing phones usb drivers... please help me if its possible
Thank you Sir!
Your intelligence has saved my Z7 Max running stock ROM v1.59. Now the WiFi and Bluetooth is working as usual....
Can you please help me about this, i tried to repartiton the phone and i got the same situation phone works but wifi and bluetooth doesnt work, i try to download that link but it says link doesnt work any more files are missing. can you please help me about this.
Hello,
I was browsing many topics for over 5 hours until I decided to ask this question so I hope it will not be obvious.
I'm having an Marvell PXA1920 CPU based Android 4.3 phone - Lenovo A788t.
It was rooted using some one-click application, so I did have access to superuser, SuperSU installed etc.
After some modifications done in /etc/permissions and rebooting, phone's entering an infinite loop.
All I need to do now is undo those changes, deleting those files and copying files from backup in another folder. However, for that I need access to /etc with /system remounted in rw mode.
I can access my phone using adb in "Product mode" (phone turned on with lower-volume button pressed), however it seems that from there I don't have root access, so:
I've tried following commands:
1. adb root
result: adbd cannot run as root in production builds
2. adb remount
result: remount failed: Operation not permitted
3. adb shell mount -o rw,remount /system
result: mount: Operation not permitted (in general, no matter what I'm trying to mount/remount)
4. adb shell su
result: the same as echo "su" - prints "su", but does not cause entering su
5. adb shell su -c 'mount -o rw,remount /system'
result: prints command, but does not execute proper action
6. adb shell busybox ...
result: causes the same as all above (operation not permitted)
It seems that phone doesn't support fastboot (adb reboot bootloader doesn't work)
I know that I can do hard reset, but I don't really want to lose all my data and configuration.
Is there anything else what I can do?
Thanks for help in advance