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

[Q] [psfMod] I cant install a new recovery becuase it says i dont have space!

http://psfreedom.com/wiki/index.php?title=OpenDesire4.0.4
http://www.ps3hax.net/showthread.php?p=123003
Im trying to install this recovery so i can jailbreak my PS3, but when i try to use unrEVOked, it hangs while pushing the recovery
When i try to use adb on both my phone and my computer it says i have no space!
what should i do?
EDIT:
fastboot erase recovery
fastboot flash recovery recovery.img
sounds like it would work, bu t i dont want to risk that lol

The no space error will happen if you don't mount system as writable. By default it is set as read only.
Read around to lookup the command to remount system as writable. The command varies depending on your device.
For the motorola droid I used the following:
mount -o remount,rw -t yaffs2 /dev/blockmtdblock4 /system
I think the G1 and other HTC phones use mtdblock3 instead of mtdblock4, but I'm not sure.

SwordOfWar said:
The no space error will happen if you don't mount system as writable. By default it is set as read only.
Read around to lookup the command to remount system as writable. The command varies depending on your device.
For the motorola droid I used the following:
mount -o remount,rw -t yaffs2 /dev/blockmtdblock4 /system
I think the G1 and other HTC phones use mtdblock3 instead of mtdblock4, but I'm not sure.
Click to expand...
Click to collapse
Alright, thats good to know. Ill look around

http://forum.xda-developers.com/showthread.php?t=770663
"You can only write to system on the desire via adb from recovery."
So i do what? boot into recovery, plug in my phone and adb it again?
flash_image recovery image.img?

Hmm, guess not.
I booted into recovery. Plugged my phone in and did an adb devices. It said one device called recovery
i did mount /sdcard (apparently i dont have to mount it to a location)
i cd'd into thte sdcard and did a flash_image recovery psfMod.img and it said i had no space

I was also looking at this
http://forum.xda-developers.com/showthread.php?t=770663
but i still cant get it to work.
do i have to have s-off?

[Q] SD card problem...

Hi, I've just received a 16Gb Kingston SD card (Class 4), and I immediately put it into my phone, and mounted it in recovery, then used GPart to partition it into:
Fat32 (13.5Gb)|1Gb EXT4|300mb EXT4|100mb swap
And I've come to flash a new ROM, and in recovery (CWM-AlphaRev Recovery v2.5.1.8) when I go to install a zip from SD card, then go to choose the zip, I get an error of:
"E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount /sdcard"
Anybody know the problem?
Oh, also, the fat32 partition shows up in windows when it's mounted, so it's partitioned OK...

SD brick - I had the same yesterday... But it works!
http://forum.xda-developers.com/showthread.php?t=691639

Rogi_tcz said:
SD brick - I had the same yesterday... But it works!
http://forum.xda-developers.com/showthread.php?t=691639
Click to expand...
Click to collapse
Is this the same? My sd card is mountable from recovery, but it's just not readable by recovery...

cgmorris89 said:
Is this the same? My sd card is mountable from recovery, but it's just not readable by recovery...
Click to expand...
Click to collapse
Yes, I had exactly the same issue. SD card not readable by recovery and usb, only from card reader.

OK thanks I'll take a look

Rogi_tcz said:
Yes, I had exactly the same issue. SD card not readable by recovery and usb, only from card reader.
Click to expand...
Click to collapse
Wait, my card IS readable by USB, just not recovery. I've not tried it in a card reader...

At first. I had the same like below after trying to restore backup from Amon recovery.
"E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount /sdcard"
My PC didn't recognize my SD by USB toggle in recovery but it worked by card reader in my PC. After fastboot commands again became visible by recovery, but not by USB toggle or normal mode with Android working. After restore my backup with working recovery I made the rest of the steps from tutorial and now it's fully functional again.

which fastboot command did you use?
fastboot oem enableqxdm 0 ?
I imagine I'll only need to do the "making it visible in recovery" part as it's visible by USB already

Yes, I used "fastboot oem enableqxdm 0" in fastboot mode.

I'm trying it now and I'm down to step 3, and in cmd.exe I'm getting "The system cannot find the path specified."

Fastboot command it's not working? Maybe you need to install this http://www.4shared.com/file/7YyQXBE6/adbfastboot.html and extract to \windows\system32\. Then start your phone in fastboot mode (back + power). I have installed SDK on C:/SDK/tools. In cmd.exe:
cd C:/SDK/tools
After that commands should work.

No, fastboot is working, as I previously used
fastboot oem enableqxdm 0
and 'fastboot oem boot' which gave me my CID
I then edited the mtd0.img with my CID in my hex editor, and attempted to move the flash_image and mtd0.img with the following command
'cat /sdcard/flash_image > /data/flash_image'
which is when I get the error

Below commands work for me:
Code:
su
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0.img > /data/mtd0.img
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd0.img
Maybe you missed "su". If still not work take a look for help in original topic maybe. I used tutorial from our polish board (more detailed). You can translate if you want.
http://bit.ly/fliTad

I wasn't having any luck whatsoever with that unfortunately...so I partitioned it through recovery (advanced>partition SD card) with a 1024mb EXT partition and 0mb swap, and recovery now recognises the SD card...we'll see how it goes

[HOWTO] Unbrick After Factory Reset From Privacy Screen

So everyone says never do this, but what can I say, I was curious
My Optimus was previously rooted using sublimewolf's method: http://forum.xda-developers.com/showthread.php?t=935312
I then proceeded to brick it by using the Factory Reset found in the Privacy Screen. This forced my phone into a recovery loop.
If you can't even get to your custom recovery, your phone might be your newest paperweight But as long as you can both get to recovery and access the phone via adb, you'll be okay.
So here's how to unbrick it:
This is the flash_image: http://www.mediafire.com/?bx14hzq5i2pq3ps
And here's the stock recovery image + nand backup: http://www.mediafire.com/?ac0e2ksq0eslytk
(In my case, I was able to skip to Step 4 in the Nandroid Instructions because I had performed a Nand Backup when I rooted, therefore the necessary files were already in place)
Nandroid Instructions:
1) Unzip both downloaded archives
2) Move the BCDS-20110203-0357 dir into /sdcard/nandroid/mem=477M (also extract recovery.img and flash_image to root dir of your SD card, as you will need to later anyway)
2a) For Clockwork Recovery, place the BCDS-20110203-0357 dir into /sdcard/clockworkmod/backup
3) Mount SD into phone if it isn't already, boot into recovery if your phone isn't already there
4) Go into the "Backup/Restore" menu, and select "nand restore", confirm and wait
5) Reboot, proceed to Recovery Instructions below
Recovery Instructions:
1) Extract recovery.img and flash_image to root dir of your SD card if you haven't already done so
2) Connect to your phone via the adb shell and input the following commands:
# su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5
# flash_image recovery /sdcard/recovery.img
# reboot recovery
3) If everything was done correctly, your phone should boot up normally to the OS
If the links above go down, let me know and I'll re-up
(thanks to tankhull for putting this info together)
(oh and you're welcome for being a guinea pig )

Thank you very much for putting this together
I am one of the curious one too.
You saved me....

If you can't get into recovery, I'm sure you can flash one through fastboot. No?
Sent from my VM670 using XDA App

Hi!
I had stock rom, but my phone was rooted.
So if whenever I turn my phone on, it goes to Clockwork Mod, does that mean it is bricked?
And will there be any way to unroot my phone after I do this? BC my 3G wasn't working at all, it should be working, but its not, so I did a factory reset.

Didn't work for me
when typing su after nand restore i get
/sbin/sh: su: not found

Ok so I have followed the instructions to the letter. And am attemptingto access adb shell. But in cmd prompt when I type adb devices it comes up with list of devices attached and says nothing. So how are we supposed to be accessing adb shell?

In clockworkmod, I went to the option for mounting and mounted the sd card, and a folder popped up on my comp, and there was no folder called Nandroid or clockworkmod

Any help guys?

I don't understand how to do the Nandroid instructions part... do I have to go to ADB?

atr0phy said:
So everyone says never do this, but what can I say, I was curious
My Optimus was previously rooted using sublimewolf's method: http://forum.xda-developers.com/showthread.php?t=935312
I then proceeded to brick it by using the Factory Reset found in the Privacy Screen. This forced my phone into a recovery loop.
If you can't even get to your custom recovery, your phone might be your newest paperweight But as long as you can both get to recovery and access the phone via adb, you'll be okay.
So here's how to unbrick it:
This is the flash_image: http://www.mediafire.com/?bx14hzq5i2pq3ps
And here's the stock recovery image + nand backup: http://www.mediafire.com/?ac0e2ksq0eslytk
(In my case, I was able to skip to Step 4 in the Nandroid Instructions because I had performed a Nand Backup when I rooted, therefore the necessary files were already in place)
Nandroid Instructions:
1) Unzip both downloaded archives
2) Move the BCDS-20110203-0357 dir into /sdcard/nandroid/mem=477M (also extract recovery.img and flash_image to root dir of your SD card, as you will need to later anyway)
2a) For Clockwork Recovery, place the BCDS-20110203-0357 dir into /sdcard/clockworkmod/backup
3) Mount SD into phone if it isn't already, boot into recovery if your phone isn't already there
4) Go into the "Backup/Restore" menu, and select "nand restore", confirm and wait
5) Reboot, proceed to Recovery Instructions below
Recovery Instructions:
1) Extract recovery.img and flash_image to root dir of your SD card if you haven't already done so
2) Connect to your phone via the adb shell and input the following commands:
# su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5
# flash_image recovery /sdcard/recovery.img
# reboot recovery
3) If everything was done correctly, your phone should boot up normally to the OS
If the links above go down, let me know and I'll re-up
(thanks to tankhull for putting this info together)
(oh and you're welcome for being a guinea pig )
Click to expand...
Click to collapse
In the nandroid instructions, for placing BCDS-20110203-0357 into the /sdcard/nandroid/mem=477M
Do I have to do that, or step 2a if I have Clockworkrecoverymod, "For Clockwork Recovery, place the BCDS-20110203-0357 dir into /sdcard/clockworkmod/backup"
Also, how do I put this directory into the /sdcard/clockworkmod/backup folder or /sdcard/nandroid/mem=477M
Do I use ADB? And if so, how do I, because I have no idea about what commands/etc to use.. or could somebody please link me to a guide on how to push a file/folder into a folder like the ones I previously mentioned (/sdcard/clockworkmod/backup folder or /sdcard/nandroid/mem=477M)
Thank you in advance for your help!

Wreak_Peace said:
In the nandroid instructions, for placing BCDS-20110203-0357 into the /sdcard/nandroid/mem=477M
Do I have to do that, or step 2a if I have Clockworkrecoverymod, "For Clockwork Recovery, place the BCDS-20110203-0357 dir into /sdcard/clockworkmod/backup"
Also, how do I put this directory into the /sdcard/clockworkmod/backup folder or /sdcard/nandroid/mem=477M
Do I use ADB? And if so, how do I, because I have no idea about what commands/etc to use.. or could somebody please link me to a guide on how to push a file/folder into a folder like the ones I previously mentioned (/sdcard/clockworkmod/backup folder or /sdcard/nandroid/mem=477M)
Thank you in advance for your help!
Click to expand...
Click to collapse
You are making this harder than it has to be. All you are trying to do is place a folder and some files on your micro sdcard. Place the micro sd card on your computer. Grab the folder "BCDS-20110203-0357" and drag it to "/sdcard/clockworkmod/backup" (yes, that one because you have the clockworkmod recovery). If you have no way of placing the micro sd card onto your computer (card reader, micro sd to sdcard converter), then leave the card in the phone, connect the phone to your compter via USB, boot into the recovery, and then turn on USB massstorage mode through the recovery options. This should make the micro sd card pop up on your computer like a usb harddrive. Drag and drop the files.

mmarz said:
You are making this harder than it has to be. All you are trying to do is place a folder and some files on your micro sdcard. Place the micro sd card on your computer. Grab the folder "BCDS-20110203-0357" and drag it to "/sdcard/clockworkmod/backup" (yes, that one because you have the clockworkmod recovery). If you have no way of placing the micro sd card onto your computer (card reader, micro sd to sdcard converter), then leave the card in the phone, connect the phone to your compter via USB, boot into the recovery, and then turn on USB massstorage mode through the recovery options. This should make the micro sd card pop up on your computer like a usb harddrive. Drag and drop the files.
Click to expand...
Click to collapse
I put my microsd card into my computer, and there are no folders called sdcard, clockworkmod, or nandroid :/

Wreak_Peace said:
I put my microsd card into my computer, and there are no folders called sdcard, clockworkmod, or nandroid :/
Click to expand...
Click to collapse
Lol, first off, the sd card IS the folder "sdcard". That will only show up on your phone. Secondly, if the folders aren't there, just make them. They are not magic folders. Just right click, and select new -> folder, and name them as described.
clockworkmod\backup\
And then copy "BCDS-20110203-0357" into the "backup" folder.
You do have the Clockworkmod Recovery, right?

I do, and now, when i opened up my cmd
I did "cd c:\android\platform-tools"
then "adb shell"
then this came up "~#"
so even then, I went ahead and did "su"
and it said,
"su
/sbin/sh: su: not found"
So, what do I do now?
and I went ahead anyways did the next step
i typed in "mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system"
then it said
"mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
(next line) mount: mounting /dev/block/mtdblock5 on /system failed: invalid arguement"

Try doing only the last two lines,
Code:
flash_image recovery /sdcard/recovery.img
reboot recovery

So I just do
"cd C:\android\platform-tools
adb shell
flash_image recovery /sdcard/recovery.img
reboot recovery"
Or do i add the su in an additional line after adb shell
?

Wreak_Peace said:
So I just do
"cd C:\android\platform-tools
adb shell
flash_image recovery /sdcard/recovery.img
reboot recovery"
Or do i add the su in an additional line after adb shell
?
Click to expand...
Click to collapse
You don't need the su because you already have the "#" sign. That means you have super user privileges.

mmarz said:
Try doing only the last two lines,
Code:
flash_image recovery /sdcard/recovery.img
reboot recovery
Click to expand...
Click to collapse
K, so this is what I came out with when doing what you said.. this is without typing in su after adb shell.
Code:
cd c:\android\platform-tools
c:\Android\platform-tools>adb shell
~ # flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
failed with error: -1
error opening /sdcard/recovery.img~ # flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
failed with error: -1
error opening /sdcard/recovery.img~ # reboot recovery
reboot recovery
This is what I came up with when i did type su after adb shell..
Code:
cd c:\android\platform-tools
c:\Android\platform-tools>adb shell
~ # flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
failed with error: -1
error opening /sdcard/recovery.img~ # flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
failed with error: -1
error opening /sdcard/recovery.img~ # reboot recovery
reboot recovery
c:\Android\platform-tools>adb shell

I've never done this method so I can't tell you why it is not working or how it should work. Sorry.
I do have my own method for solving the bootloop issue. Try flashing this with your recovery: http://www.mediafire.com/?fbaoutnaw717pnb
Place it on your SD card and then use your recovery's flash zip option to flash it. It has helped others. It will replace your recovery with the Xionia recovery. If it works, you should boot into the LG logo. Once you can do that, boot into your recovery by using the correct button combo and flash any rom that you want to use.

mmarz said:
I've never done this method so I can't tell you why it is not working or how it should work. Sorry.
I do have my own method for solving the bootloop issue. Try flashing this with your recovery: http://www.mediafire.com/?fbaoutnaw717pnb
Place it on your SD card and then use your recovery's flash zip option to flash it. It has helped others. It will replace your recovery with the Xionia recovery. If it works, you should boot into the LG logo. Once you can do that, boot into your recovery by using the correct button combo and flash any rom that you want to use.
Click to expand...
Click to collapse
So i extract it to root of the micro sd? all of it? and then instead of recovery.img its vrecovery.img?
And so if it replaces my recovery with xionias recovery, it will boot into android and I can use my phone normally?

[Q]HOX Stuck on quietly brilliant screen

I put ARHD ROM and everything was fine, until i put Fonter module and changed font and then HOX stuck at quietly brilliant screen..
I was in panic and i wiped everything, and sdcard, and data, and system, everything.. And then i f**** up all..
So now i can go into recovery, i can go in fastboot, everything is working, just i cannot get sdcard to work. I think that it should be formatted but it won't work.. I tried several ways that i googled and on every i stuck
I tried put TWRP but it stuck on swipe to unlock and it won't work, i tried several versions, still nothing..
I tried this How to: Fix a corrupted DATA partition on the HTC One on ARHD webpage ( I cannot put links )
And when i put this
Code:
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37
It say
Code:
Could not stat /dev/block/mmcblk0p37 --- No such file or directory
Then i tried this
Code:
Here's what you'll need:
Working recovery, basic knowledge of adb & the shell
Parted (download here)
stock PB31IMG.zip
Note also that I had run unrevoked forever (so my phone was S-OFF) ... I'm not sure if that's required or not.
So, grab parted from the link above. Now you need to extract the individual binaries from the .zip (the 6 files in the sdparted folder within the zip), ideally to your android-sdk\tools directory. Now push all 6 files (adb push [file] /sbin/). Next, we need to make them useable, so go into the shell (adb shell). Change to your /sbin/ directory, and run: chmod 0755 <file> on each of the 6 files.
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Once all that's done, your recovery program should be able to mount both the /data and /cache partitions. If that's true, you're pretty much done! One thing I found was that I couldn't directly install a new OS (I tried both Cyanogen and Ultimate). In both cases, it would look for stuff in the davik-cache that it couldn't find, so something wasn't installing correctly I think. So, if that happens, flash back to the stock PB31IMG.zip (put it in the root of your /sdcard/ and let hboot install it), and then root your phone anew. That's what I ended up doing.
Again, huge credit for this goes to -Steveo- and ciwrl for helping me figure out which partitions were the right ones (and for supplying parted, which I hadn't been able to find anywhere). If something doesn't end up working, just drop me a pm and we'll see what we can do.
And here it wont when i put command
Code:
parted /dev/block/mmcblk0 mkfs ext2
it say
Code:
Error: /dev/block/mmcblk0: unrecognised disk label
But when i do this
Code:
fdisk -l /dev/block/mmcblk0
it say
Code:
Disk /dev/block/mmcblk0: 31.2 GB, 31268536320 bytes
4 heads, 16 sectors/track, 954240 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
I am sorry for bad english, but i really need help, i were searching the web for 10hours and nothing worked.. I need to full format sdcard, so could anyone help me?
Thanks

Please help someone, i need my phone

So nobody wants to help me??

lepi991 said:
So nobody wants to help me??
Click to expand...
Click to collapse
Flash Philz recovery 5.15.9 and mount sd card search in Q&A section I sheared via google drive

I tried that and when i go to Mount SD card it give me only to choose UnMount

lepi991 said:
I tried that and when i go to Mount SD card it give me only to choose UnMount
Click to expand...
Click to collapse
un mount and mount and wait 2 minutes or unmount and wait 2 minutes work with sure on 5.15.9

That didnt worked, when i enter sd card there is only unmount and when i choose that nothing happend..
Finnaly i fixed with busybox and formated card completely and then through adb shell pushed ROM and installed it..
You can lock thread