Database Develop

Adb issues

hi all
I'm trying to do the following on adb and am failing - any thoughts?
Code:
C:\Dev\Android\android-sdk-windows\tools>adb shell
# mount /system -o remount,rw
mount /system -o remount,rw
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# rm /system/app/Maps.apk
rm /system/app/Maps.apk
rm failed for /system/app/Maps.apk, Read-only file system
#

eladkatz said:
hi all
I'm trying to do the following on adb and am failing - any thoughts?
Code:
C:\Dev\Android\android-sdk-windows\tools>adb shell
# mount /system -o remount,rw
mount /system -o remount,rw
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# rm /system/app/Maps.apk
rm /system/app/Maps.apk
rm failed for /system/app/Maps.apk, Read-only file system
#
Click to expand...
Click to collapse
adb remount
adb shell rm /system/app/Maps.apk

[Q] adb mounting doesn't work

Every time i try to mount a directory on my o2x in adb it says this:
Code:
c:\sdk\platform-tools>adb shell mount -o rw,remount /system/framework /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
I just can't get to mount anything while using shell in adb

That doesn't work because you're trying to mount a folder in /system as /system
You need to remount all of /system as RW, if you're on a custom ROM then just use adb remount

Rusty! said:
That doesn't work because you're trying to mount a folder in /system as /system
You need to remount all of /system as RW, if you're on a custom ROM then just use adb remount
Click to expand...
Click to collapse
And why wouldn't that work? Works just fine on my HTC Legend
BTW: I was the one trying to push the framework-res (through teamviewer VPN connection) it has always worked on my legend and I have no idea why it doesn't work on the LG.
The LG doesn't have a security lock on the bootloader does it?
thx in advance

JonasDroid said:
And why wouldn't that work? Works just fine on my HTC Legend
BTW: I was the one trying to push the framework-res (through teamviewer VPN connection) it has always worked on my legend and I have no idea why it doesn't work on the LG.
The LG doesn't have a security lock on the bootloader does it?
thx in advance
Click to expand...
Click to collapse
I tried to backup my custom rom but it said can't mount /system xD

[Q] CWR Error: Can't mount /cache

I get this error in CWR (3.2.0.1), I have a nook with a blue sticker:
Code:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/command
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/command
Nothing, and I mean Nothing I have found in this forum solved this error, including the repartition-boot-stock+factory rest.
Any help guys? I am desperate!

adb is working but shell is not
This is what I got, anyone has an idea how to recover from this?
Code:
C:\Users\Barak>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -

reifba said:
This is what I got, anyone has an idea how to recover from this?
Code:
C:\Users\Barak>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
Nothing, and I mean Nothing I have found in this forum solved this error, including the repartition-boot-stock+factory rest.
Click to expand...
Click to collapse
If you repartitioned, that may be the reason the adb command is not working....

patruns said:
If you repartitioned, that may be the reason the adb command is not working....
Click to expand...
Click to collapse
So I have 2 two problems in which the solution to one causes the other...
In the mean time I manged to run both the Froyo and HoneyComb from the sd card, but not the CM7 (which is the one I am trying to install on the internal memory)

using ADB to restore
I tried to use the methods described in:
:http://forum.xda-developers.com/showthread.php?t=919353
However it is not clear where should the factory.zip go?
for some reason it also says that the /dev partition is only 244MB so I cannot flash the system.img, it is probably the partition in the SD card and not the memory, so not much advancement here either. I also think that because it gives me 11223344556677 as the S/N and not the real one.
The quest to restore the nook continues...

Is there a way to manually repartition through ADB?
or anything? cause nothing solves the first error posted in this thread

reifba said:
I tried to use the methods described in:
:http://forum.xda-developers.com/showthread.php?t=919353
However it is not clear where should the factory.zip go?
for some reason it also says that the /dev partition is only 244MB so I cannot flash the system.img, it is probably the partition in the SD card and not the memory, so not much advancement here either. I also think that because it gives me 11223344556677 as the S/N and not the real one.
The quest to restore the nook continues...
Click to expand...
Click to collapse
factory.zip and rombackup.zip should be located on /dev/block/mmcblk0p3
system should be written to /dev/block/mmcblk0p5
1123344556677 is normal for the device listing when adb'ing in when running CWM on the uSD
to write the img files you need to use:
dd if=(IMG FILE ON SD) of=(PARTITION ON /dev... i.e. /dev/block/mmcblk0p1)
to help you out...here's a list of what goes where:
mmcblk0p1-boot.img
mmcblk0p2-rom.img
mmcblk0p3-factory.img
mmcblk0p4-logical.img
mmcblk0p5-system.img
mmcblk0p6-data.img
mmcblk0p7-cache.img
mmcblk0p8-media.img

problem:
thanks for the reply, I am studying more about andriod and adb now than during all my bachelor's.
just
adb push factory.zip /dev/block/mmcblk0p3 ??
and
adb shell dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
(in some places I saw they didn't write "/block")
and where is rombackup.zip from?
the problem is that for some reason /dev/ is only 244MB so I can't dd system.img, only the boot.img.
I wish that somewhere in the world would exist something that solves it from CWR, just some zip I would install to fix boot+factory+system in one stroke...

reifba said:
thanks for the reply, I am studying more about andriod and adb now than during all my bachelor's.
just
adb push factory.zip /dev/block/mmcblk0p3 ??
and
adb shell dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
(in some places I saw they didn't write "/block")
and where is rombackup.zip from?
the problem is that for some reason /dev/ is only 244MB so I can't dd system.img, only the boot.img.
I wish that somewhere in the world would exist something that solves it from CWR, just some zip I would install to fix boot+factory+system in one stroke...
Click to expand...
Click to collapse
to get factory and rombackup zip files on mmcblk0p3...
adb shell mkdir /sdcard/tmp3
adb shell mount /dev/block/mmcblk0p3 /sdcard/tmp3
adb push factory.zip /sdcard/tmp3
adb push rombackup.zip /sdcard/tmp3

more problems (desperation is looming)
DizzyDen said:
adb shell mount /dev/block/mmcblk0p3 /sdcard/tmp3
Click to expand...
Click to collapse
when I type the above I get
Code:
[email protected]:/ # mount /dev/block/mmcblk0p3 /sdcard/tmp3
Usage: mount [-r] [-w] [-o options] [-t type] device directory
I had to do it in the shell in order to su.

reifba said:
when I type the above I get
Code:
[email protected]:/ # mount /dev/block/mmcblk0p3 /sdcard/tmp3
Usage: mount [-r] [-w] [-o options] [-t type] device directory
I had to do it in the shell in order to su.
Click to expand...
Click to collapse
then I would use
mount rw /dev/block/mmcblk0p3 /sdcard/tmp3
If that doesn't work:
mount rw -o remout /dev/bloc/mmcblk0p3 /sdcard/tmp3
but it would appear something else is amiss... since it even shows the command should have worked... since everything other than the command (mount) the device (/dev/block/mmcblk0p3) and directory (/sdcard/tmp3) are optional parameters

[tutorial]Root any latest firmware with ease

Firstly what i would like to say is this is not a one click root like update.zip or superoneclick you will need to have some basic knowledge of adb and ubuntu and a little bit working mind which can follow the provided steps.
Requirements:-
*cwm recovery already flashed (if not refer here)
* Working linux distro (ubuntu, mint, kubuntu etc.) with atleast sudo rights
* adb setted-up (if not refer here, may not need to follow the usb drivers steps)
* must know how to use adb
* superuser package from here
Click to expand...
Click to collapse
So we are now ready to start
STEPS:-
1. Extract all file (su, busybox) from the downloaded package to the folder where you have adb setted-up
2. open a terminal
3. cd to the directory where you have placed adb and files
4. boot your phone into cwm recovery mode (home power) connect through usb
5. type "sudo chown root:shell /path to su"
6. type "sudo chmod 06755 /path to su"
7. type " sudo chmod 04755 /path to busybox"
8. type " adb devices" if you will see anything attached you are good to go
9. type " adb remount" if you get remount succedd then you can do below steps if not you are doing something wrong do again
10. type "adb push su /system/xbin"
11. type "adb push busybox /system/xbin
12. type adb push supersu.apk ( or what it is called) /system/app
13. now type "adb shell"
14. type su if accepted then you are rooted
15. now type "reboot"
Click to expand...
Click to collapse
you are successfully rooted
enjoy your phone

awesome guide buddy very useful for n0obs

First of all great guide! But please correct these:
You have to mount the system partition manually. Adb remount won't do it!
adb shell
# mount -rw -t rfs /dev/block/stl12 /system
Do chmod/chown in adb. It isn't enough to set it before copying.
# chown root:shell /system/xbin/*
# chmod 06755 /system/xbin/su
# chmod 04755 /system/xbin/busybox
# chmod 04755 /system/xbin/sqlite3
# chmod 04755 /system/xbin/ssh

if we were able to chmod with adb there was no need to use ubuntu
we cannot chmod it shows operation not permitted as as we yet dont have root
have you tried to do adb remount or just saying that i will not do the work
and thanks for chown part

dheeraj (dhlalit11) said:
if we were able to chmod with adb there was no need to use ubuntu
we cannot chmod it shows operation not permitted as as we yet dont have root
have you tried to do adb remount or just saying that i will not do the work
Click to expand...
Click to collapse
Hi!
For me, adb remount didn't work. It exited with an error code. I don't remember the exact error code... (cwm couldn't mount too)
When I experienced "operation not permitted" while chmoding, the partition was mounted as vfat! Because if you do "mount /dev/... /system" without switches, it automatically mounts it as vfat. In vfat you can't set setuid, setgid permissions.
I think it was just a coincidence that i could rooted with ubuntu. But it worked, so better to use linux (better adb perhaps?).
Rooting is a bit strange in this new firmware. For example when you do "adb shell" while the phone is in cwm, you have root access. So you have to do those things manually while you have temporary root access.

how can you mount rfs file system as vfat i dont think it can be done

dheeraj (dhlalit11) said:
how can you mount rfs file system as vfat i dont think it can be done
Click to expand...
Click to collapse
Yes it's really strange. I don't know how this thing possible too...
But I checked multiple times with "cat /proc/mounts" , and mounting without "-t rfs" it was mounted as vfat.
a bit of googling:
"You can mount as rfs as Fat in ubuntu and read/copy the files
editing them wont work at all ."
So maybe it is possible.

[GUIDE] Running ArchLinuxARM on Huawei Ascend P7

Prerequisites:
Rooted device
Busybox installed ( get it from Google Play )
Terminal emulator ( get it from Google Play )
An armv7h linux image ( see the download link below )
ArchLinuxARM images:
You can download any ArchLinuxARM image you want from this link sourceforge.net/projects/linuxonandroid/files/ArchLinux/
After downloading your image rename it to "arch.img".
Step 1:
Create the following directories on your EXTERNAL-SDcard ( works on internal too but you'll have to modify the paths in the arch.sh script ): archlinux/ and archlinux/mount/
Step 2:
Copy the arch.img file you downloaded from your computer to your EXTERNAL-SDcard and store it under archlinux/
Step 3:
Open a text editor on your computer and create a new file called arch.sh and paste the following text in it:
# path to the linux img
# change this in case it is different from your image's path
LINUX_IMG=/storage/sdcard1/archlinux/arch.img
# location where the linux image will be mounted (/storage/sdcard1/archlinux/mount/)
# change this if you want to mount it somewhere else
LINUX_DIR=/storage/sdcard1/archlinux/mount/
# create the directory where the linux image will be mounted in case it doesn't exist
mkdir -p $LINUX_DIR
# mount the image
busybox mount -o loop $LINUX_IMG $LINUX_DIR
# mount dev and proc directories
cd $LINUX_DIR
busybox mount -t proc proc proc/
busybox mount -o bind /dev/ dev/
# optionally mount sdcard and external sdcard (if you do not want to mount them simply comment the following 2 lines)
busybox mount -o bind /sdcard/ sdcard/
busybox mount -o bind /storage/sdcard1/ external_sd/
# copy resolv.conf from android environment to arch linux environment
cp /etc/resolv.conf etc/resolv.conf
# chroot into the arch linux environment
chroot $LINUX_DIR /bin/bash
Step 4:
Copy the arch.sh script from your computer to the root of your INTERNAL SDcard ( since we don't have execute permissions on the external SDcard we will store the script on the internal SDcard).
Step 5:
Unplug your AscendP7 from the computer and open the terminal emulator.
Once the terminal emulator opened type the following:
su
cd /storage/sdcard0/
./arch.sh
If you followed the above steps, after executing the above commands you should find yourself inside the ArchLinux environment.

problem with download file
MihaiChirculete said:
Prerequisites:
Rooted device
Busybox installed ( get it from Google Play )
Terminal emulator ( get it from Google Play )
An armv7h linux image ( see the download link below )
ArchLinuxARM images:
You can download any ArchLinuxARM image you want from this link nl.mirror.archlinuxarm.org/armv7h/alarm/
After downloading your image rename it to "arch.img".
Step 1:
Create the following directories on your EXTERNAL-SDcard ( works on internal too but you'll have to modify the paths in the arch.sh script ): archlinux/ and archlinux/mount/
Step 2:
Copy the arch.img file you downloaded from your computer to your EXTERNAL-SDcard and store it under archlinux/
Step 3:
Open a text editor on your computer and create a new file called arch.sh and paste the following text in it:
# path to the linux img
# change this in case it is different from your image's path
LINUX_IMG=/storage/sdcard1/archlinux/arch.img
# location where the linux image will be mounted (/storage/sdcard1/archlinux/mount/)
# change this if you want to mount it somewhere else
LINUX_DIR=/storage/sdcard1/archlinux/mount/
# create the directory where the linux image will be mounted in case it doesn't exist
mkdir -p $LINUX_DIR
# mount the image
busybox mount -o loop $LINUX_IMG $LINUX_DIR
# mount dev and proc directories
cd $LINUX_DIR
busybox mount -t proc proc proc/
busybox mount -o bind /dev/ dev/
# optionally mount sdcard and external sdcard (if you do not want to mount them simply comment the following 2 lines)
busybox mount -o bind /sdcard/ sdcard/
busybox mount -o bind /storage/sdcard1/ external_sd/
# copy resolv.conf from android environment to arch linux environment
cp /etc/resolv.conf etc/resolv.conf
# chroot into the arch linux environment
chroot $LINUX_DIR /bin/bash
Step 4:
Copy the arch.sh script from your computer to the root of your INTERNAL SDcard ( since we don't have execute permissions on the external SDcard we will store the script on the internal SDcard).
Step 5:
Unplug your AscendP7 from the computer and open the terminal emulator.
Once the terminal emulator opened type the following:
su
cd /storage/sdcard0/
./arch.sh
If you followed the above steps, after executing the above commands you should find yourself inside the ArchLinux environment.
Click to expand...
Click to collapse
which one must to download?

rahim1234 said:
which one must to download?
Click to expand...
Click to collapse
I changed the download link. Try this: sourceforge.net/projects/linuxonandroid/files/ArchLinux/

so, what is the advantage of this kernel?