Develop Bugs

Removing Apps - What mode to boot in?

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

mount: mounting /dev/block/mmcblk0p12 on /sdcard failed: Invalid argument

Any ideas?

lonelliott said:
Any ideas?
Click to expand...
Click to collapse
Which command did you send?
Sent from my Kindle Fire using Tapatalk

are you logged in on adb? Try to type "exit" then "adb shell".
You don't have to mount your sdcard after using adb shell. (at least I didn't have to on my mac)

For some reason it will not mount my sdcard, at all. I can adb shell onto it, but when I try to run the update.zip from it, I get an error saying it cannot mount the sd card.

I had the same issue on mine. Heres the fix:
In TWRP with the fire connected to the pc run:
Code:
adb shell
echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file
Windows will probably respond that the volume/device needs formatted before using it.
Thats okay. choose quick format and let it format it as fat32 block size 4096.
when its done
in twrp choose the mount option and mount USB storage then hit unmount again
tap the box next to Mount SDCard. It should now look like
[X] Unmount SDCard.
Download the 6.2.1 pre-rooted zip file from the thread in the dev section.
choose mount USB Storage
Place on SDCard
Turn off usb storage
choose wipe
choose cache
choose factory reset
choose dalvik cache
choose system
go back and choose install
choose the zip you placed on your sdcard
flash it.
reboot. if it reboots back into twrp
run
Code:
adb shell
idme ? <--that will probably tell you the bootmode is 0x5003
idme bootmode 0x4000
exit
in twrp choose reboot
choose system
enjoy! it may take a while to boot

I have the same problem. Can't mount sdcard.
I'm doing your fix step by step in Win XP. I formatted partition into Fat32. Though it didn't allow me to select block size. It just has one option "Default allocation size". Capacity is 200MB.
After that I'm trying to tap on the Mount SDCard option, but it wouldn't change to [X] Unmount SDCard. So it wouldn't mount and I'm back to the problem.
Any ideas on what could go wrong?

I finally figured it out!
The key thing is that sdcard HAS to be formatted in a certain way - FAT32 (and presumingly block size 4096 as mentioned above).
Brief history:
I followed the above instruction and formatted sdcard on a mac with Disk Utility. That didn't work. It still wouldn't mount. I tried to do the same thing in Windows XP. No luck. It wouldn't mount with the same "Invalid argument" error.
I figured that I should try and format sdcard right from the TWRP shell. I deleted and recreated partition with fdisk. Then I learned that TWRP 2 comes with pretty old busybox which doesn't have mkfs or mkfs.vfat to format the partition to FAT 32. So took the busybox binary from the pre-rooted 6.2.1 and pushed it to the KF. And I used mkfs.vfat.
Instructions:
Download and unzip pre-rooted 6.2.1..
Rename busybox to busybox1 (just not to mess up existing version) and copy it to your KF.
Code:
adb push /path_to_unzipped_6.2.1/system/xbin/busybox1 /sbin
Go to shell:
Code:
adb shell
~ # chmod 755 /sbin/busybox1
~ # busybox1 mkfs.vfat /dev/block/mmcblk0p12
~ # mount sdcard
There you go! Now your sdcard is mounted. And you can proceed with the instruction above.

death2all110, thanks for the post. This solved my issues....beer money sent!
Brad

Thanks Dmitry_G, That was exactly what I needed!

You guys are amazing and you have brought my Kindle back from the dead. Thank you sincerely.

i need someone to help me with this please i'm a newbie with the same problem

Same to me, but i got error, help me!
I follow your guide, but have error, pls help!!!
C:\>adb shell
~ # chmod 755 /sbin/busybox1
chmod 755 /sbin/busybox1
~ # busybox1 mkfs.vfat /dev/block/mmcblk0p12
busybox1 mkfs.vfat /dev/block/mmcblk0p12
mkfs.vfat: can't open '/dev/block/mmcblk0p12': No such file or directory
~ # ^

You try copy mmcblk0p12 file from another KF to your KF.
This error by mmcblk0p12 deleted

Death, I don't know if you will see this reply because this thread is so old but if you do,THANK YOU!!!!!! THANK YOU!!! THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! I had messed with kfu, unbrick utility and many other methods to try to unbrick my kindle and your guide was exactly what I needed.

death2all110 said:
I had the same issue on mine. Heres the fix:
In TWRP with the fire connected to the pc run:
Code:
adb shell
echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file
Windows will probably respond that the volume/device needs formatted before using it.
Thats okay. choose quick format and let it format it as fat32 block size 4096.
when its done
in twrp choose the mount option and mount USB storage then hit unmount again
tap the box next to Mount SDCard. It should now look like
[X] Unmount SDCard.
Download the 6.2.1 pre-rooted zip file from the thread in the dev section.
choose mount USB Storage
Place on SDCard
Turn off usb storage
choose wipe
choose cache
choose factory reset
choose dalvik cache
choose system
go back and choose install
choose the zip you placed on your sdcard
flash it.
reboot. if it reboots back into twrp
run
Code:
adb shell
idme ? <--that will probably tell you the bootmode is 0x5003
idme bootmode 0x4000
exit
in twrp choose reboot
choose system
enjoy! it may take a while to boot
Click to expand...
Click to collapse
THANK YOU! It worked! I was about to trash this thing.

[Q] Unable to mount /sdcard as rw

I'm currently trying to use adb to push a ROM to my sdcard on my Verizon Galaxy Nexus. However, it keeps failing due to /sdcard being a read-only filesystem.
When I adb shell into the phone and type mount, i get this (among others):
Code:
/dev/block/mmcblk0p12 on /sdcard type ext4 <ro,relatime,barrier=1,data=ordered>
Attempting to mount /sdcard as read-write is not proving fruitful:
Code:
mount -o remount rw /sdcard
Can anyone help? I'm just trying to get a rom on there so i can install it. Unfortunately, the phone never leaves the google screen when i try to boot, so recovery and fastboot are my only options.

mount -o rw,remount /dev/block/mmcblk0p12 /sdcard
try that

DonDizzurp said:
mount -o rw,remount /dev/block/mmcblk0p12 /sdcard
try that
Click to expand...
Click to collapse
Thanks for the help. It now mounts as rw. However, when i try to
Code:
adb push C:\rom.zip /sdcard/rom.zip
It fails and i get a Fil I/O error.

ttremblay said:
Thanks for the help. It now mounts as rw. However, when i try to
Code:
adb push C:\rom.zip /sdcard/rom.zip
It fails and i get a Fil I/O error.
Click to expand...
Click to collapse
To make things easier, copy the .zip file to the folder where you have ADB then try
adb push ./rom.zip /sdcard/rom.zip

I never could get things to push to sdcard while in recovery mode no matter what I tried.
adb sideload was how I always did I
---------- Post added at 04:52 AM ---------- Previous post was at 04:51 AM ----------
Or maybe instead of using "/sdcard" use "/data/media"?

Hello there, my samsung galaxy s2 i9100's internal sdcard suddenly became read-only shortly after updating it to 4.1. I've tried using the command: ''mount -o remount, rw /sdcard'' which works until i reboot or connect it to an external usb storage device. I'm kindly asking if anyone knows a permanent solution to my problem. P.S- I'm a bit new to this android thing so make your explanations as easy as possible. Please help

Unbricking my Fonepad7 k00e with a currupted partition.

Here are the facts:
my tablet was throwing errors about google app and google search box crashing. I restarted the tablet and it got stuck at boot loop.
K00E with firmware,UL-K00E-WW-7.6.0.0-user, not rooted.
what I've tried:
factory reset under droidboot:
Code:
E:failed to mount /cache (Invalid argument)
unable to mount /cache! we skip check debricking
SD download of the latest RAW file under under droidboot:
again
Code:
E:failed to mount /cache (Invalid argument)
unable to mount /cache!
Installing the firmware zip file using custom recovery:
I used this to run CWM. I cleared cache, user data, factory reset and then tried to install using external SD zip file.
Code:
failed to mount /dev/block/mmcblk0p8 at /system: Invalid argument
trying to re partition the internal SD:
from here
I tried to run parted to fix it but I am getting this
Code:
~ # parted
parted
/sbin/parted: line 1: syntax error: unexpected word (expecting ")")
~ #
I added no arguments to parted, and still it is giving me this error. I even tried pushing another copy of parted and chmodding it to execute it, still the same thing occurs.
I also tried this
on running th second command I have
Code:
~ # tune2fs -O extents,uninit_bg,dir_index -C 1 /dev/block/mmcblk0p8
tune2fs -O extents,uninit_bg,dir_index -C 1 /dev/block/mmcblk0p8
tune2fs 1.41.11 (14-Mar-2010)
tune2fs: Bad magic number in super-block while trying to open /dev/block/mmcblk0
p8
Couldn't find valid filesystem superblock.
~ #
any ideas how to move forward?

Unable to mount EFI Operation not supported on transport endpoint

I have a family member's phone (N7100) that was stuck on a bootloop. This phone was never rooted or had any custom recoveries or roms installed on it. When I go into recovery I see that I'm getting the common "e:failed to mount /efs(invalid argument)". When trying to google the problem I found that common fix for it:
Code:
adb shell
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3 /efs
So I go ahead and do this but I notice that even though the phone is out of a bootloop and goes into factory mode (I already know how to get out of it), it doesn't connect to the phone network. Going back to recovery I see that EFI is still not able to be mounted but the error is different "failed to mount /efs Operation not supported on transport endpoint".
I can tell that if I ADB into the phone and do "mount -w -t ext4 /dev/block/mmcblk0p3 /efs" it will mount just fine. Anybody knows what is happening? To make everything worse he doesn't have a EFI backup so at this point I'm thinking the phone is dead no matter what. Suggestions?
Thanks

Try flashing stock ROM.

Skull97 said:
Try flashing stock ROM.
Click to expand...
Click to collapse
I already did and it didn't help. Googling the problem doesn't seem to give me any results for that particular error line.

Bump! I hate to do this but I think this is my last chance to fix it. Google is not giving me any good leads for me to latch on.