Database Develop

apps2sd reboot loop

hi everyone,
***i searched and searched but i couldnt find the answer***
i had apps2sd on a previous rom and i recently switched to the mytouch rom.
after i wiped and applied update, i get stuck at the boot loop. i know that this is caused by the apps2sd and i remember seeing a set of commands that erase it from the sd card but it was deep in a thread and i dont remember which thread it was.
can someone please help me ( and others) out by posting the commands that will get it past the boot loop?
i tried this in the recovery console but it didnt work:
mount data
ln -s /system/sd/app /data/app
Thanks guys!

also tried this but it didnt work:
mount data
rm /data/app
mkdir /data/app
im still stuck on boot loop

Code:
mount -o rw /dev/block/mmcblk0p2 /system/sd
cd /system/sd
rm -r *
slyfury said:
also tried this but it didnt work:
mount data
rm /data/app
mkdir /data/app
im still stuck on boot loop
Click to expand...
Click to collapse

mount -o rw /dev/block/mmcblk0p2 /system/sd
cd /system/sd
rm -r *
does that delete everything on the sd card?
this gives me an invalid argument error:
"mount -o rw /dev/block/mmcblk0p2 /system/sd"
i can get to
/system/sd #
when i type in cd /system/sd
?????what do i do???

slyfury said:
mount -o rw /dev/block/mmcblk0p2 /system/sd
cd /system/sd
rm -r *
does that delete everything on the sd card?
this gives me an invalid argument error:
"mount -o rw /dev/block/mmcblk0p2 /system/sd"
i can get to
/system/sd #
when i type in cd /system/sd
?????what do i do???
Click to expand...
Click to collapse
said what the hell and tried the rm command and i got permision denied on everyfile it tried to erase

easiest way would be to reformat your ext partition.
then wipe and reflash
other roms can leave junk in the ext partition that causes bootloops quite often. this is a very common problem and i always find a reformat, which takes like 30 seconds with gparted live cd, fixes it

is there a way to do it through the phone?
my micro sd adapter broke and im waiting for amazon to send my a new one
found it:
http://forum.xda-developers.com/showthread.php?t=534714

Ubuntu Help !

Hey Guys wondering is someone can assist
i been using different ROMS for about 3 months now
i have several SD card that have been partitioned to FAT32 and Ext3
however i recently purcahsed an 8GB card but what i want to do it change cards but i want to copy my Ext3 partition so its just a matter of drag and drop to the new card
however via ubuntu its not letting me access Ext3 partition, it clearly shows that its there but wont let me mount it .... can mount up FAT32 with no issues
if someone could assist it would be greatly appreciated
Running latest ubuntu 9.04 from Live CD

if you have the android sdk set up I believe you can pull it, create the partition and then push the files to the partition that way. Not sure if ubuntu can mount an ext partition. Google!

not sure if it is ROM specific but I can mount ext from linux using cyanogens rom.
plug phone in and click mount usb.
from linux open console
Code:
dmesg # to find out which device (mine is /dev/sda)
sudo fdisk -l /dev/sda # or whatever dmesg said
sudo mkdir /mnt/tmp
sudo mount /dev/sda2 /mnt/tmp
ls /mnt/tmp #should show contents of ext3 if it worked
copy files
Code:
sudo umount /mnt/tmp
on phone click unmount usb or whatever.

Strange, Ubuntu always mounts my ext3 no problems. You could try pulling the file to you fat32 on the old card, copy them to fat on the new card and push to the ext3
On the old card
cp /system/sd/app/* /sdcard/app
Cp /system/sd/app-private/* /sdcard/app-private
Then copy those 2 folder to the fat32 of the new card, then:
Cp /sdcard/app/* /system/sd/app
Cp /sdcard/app-private/* /system/sd/app-private
You will have to remount /system and mkdir's first, though.

dumfuq said:
not sure if it is ROM specific but I can mount ext from linux using cyanogens rom.
plug phone in and click mount usb.
from linux open console
Code:
dmesg # to find out which device (mine is /dev/sda)
sudo fdisk -l /dev/sda # or whatever dmesg said
sudo mkdir /mnt/tmp
sudo mount /dev/sda2 /mnt/tmp
ls /mnt/tmp #should show contents of ext3 if it worked
copy files
Code:
sudo umount /mnt/tmp
on phone click unmount usb or whatever.
Click to expand...
Click to collapse
Ill check thos out my friend
thanks , i will report bk

It's a little odd what it does with the ext partition. I noticed it did not show up except in /media. The fat partition gets a shortcut on the desktop. If you have gparted on your machine, open it up and it should tell you where it mounted it to (if it got mounted).
Good luck.

dmesg
sudo fdisk -l /dev/sdf
sudo mkdir /mnt/tmp
sudo mount /dev/sdf2 /mnt/tmp ..... SO FAR THIS WORKS
when i enter this command ..... ls /mnt/tmp ..... i get error message "ls: cannot open directory /mnt/tmp: Permission denied"
any other idea's

AdrianK said:
Strange, Ubuntu always mounts my ext3 no problems. You could try pulling the file to you fat32 on the old card, copy them to fat on the new card and push to the ext3
On the old card
cp /system/sd/app/* /sdcard/app
Cp /system/sd/app-private/* /sdcard/app-private
Then copy those 2 folder to the fat32 of the new card, then:
Cp /sdcard/app/* /system/sd/app
Cp /sdcard/app-private/* /system/sd/app-private
You will have to remount /system and mkdir's first, though.
Click to expand...
Click to collapse
through terminal ? or linux command ? or through recovery mode ?
also can you give instructions to remount system , only if you can
cheers appreciated
also any idea's why your fat 32 AND ext system auto shows so that files can be dragged and dropped ?

dumfuq said:
not sure if it is ROM specific but I can mount ext from linux using cyanogens rom.
plug phone in and click mount usb.
from linux open console
Code:
dmesg
sudo fdisk -l /dev/sda
sudo mkdir /mnt/tmp
sudo mount /dev/sda2 /mnt/tmp
ls /mnt/tmp
copy files
Code:
sudo umount /mnt/tmp
on phone click unmount usb or whatever.
Click to expand...
Click to collapse
ok managed to do this , but how then do i copy the files ?

drewno1 said:
through terminal ? or linux command ? or through recovery mode ?
also can you give instructions to remount system , only if you can
cheers appreciated
also any idea's why your fat 32 AND ext system auto shows so that files can be dragged and dropped ?
Click to expand...
Click to collapse
Was posting from my G1 late at night so I was feeling lazy
to remount /system as rw
mount -o rw,remount /dev/block/mtdblock3 /system
input those commands in to the recovery console, it's not a good idea to push apk's while your phone is on (I mean, it is in android).
No idea. I'm on Ubuntu 9.04, it auto mounts them and opens them, they also appear in the sidebar in nautilus.

drewno1 said:
ok managed to do this , but how then do i copy the files ?
Click to expand...
Click to collapse
Code:
cp -rv /mnt/tmp/* /path/to/where/you/want/the/files/
or drag and drop using nautilus file browser.

cp /system/sd/app/* /sdcard/app
Cp /system/sd/app-private/* /sdcard/app-private
Cp /sdcard/app/* /system/sd/app
Cp /sdcard/app-private/* /system/sd/app-private
mount -o rw,remount /dev/block/mtdblock3 /system
OK that never worked , anymore idea's ?

dmesg
sudo fdisk -l /dev/sdf
sudo mkdir /mnt/tmp
sudo mount /dev/sdf2 /mnt/tmp ls /mnt/tmp
cp -rv /mnt/tmp/* /sdcard/app/* /system/sd/app
cp -rv /mnt/tmp/* /sdcard/app-private/* /system/sd/app-private
sudo umount /mnt/tmp
will try this method and report bk

drewno1 said:
dmesg
sudo fdisk -l /dev/sdf
sudo mkdir /mnt/tmp
sudo mount /dev/sdf2 /mnt/tmp ls /mnt/tmp
cp -rv /mnt/tmp/* /sdcard/app/* /system/sd/app
cp -rv /mnt/tmp/* /sdcard/app-private/* /system/sd/app-private
sudo umount /mnt/tmp
will try this method and report bk
Click to expand...
Click to collapse
LMAO this never worked , i feel like pulling my hair out haha

billquinn1 said:
It's a little odd what it does with the ext partition. I noticed it did not show up except in /media. The fat partition gets a shortcut on the desktop. If you have gparted on your machine, open it up and it should tell you where it mounted it to (if it got mounted).
Good luck.
Click to expand...
Click to collapse
checked GParted and here is where it says its mounted
Path: /dev/sdf2
Status: Mounted on /media/disk-1

Since this is Ubuntu Help, i figured i'd post this here, if it is the wrong forum, let me know.
I am trying, and have been for a week now, to use
Code:
adb shell
however, it keeps giving me the message
Code:
device not found
i know it's there because i am able to mount the sd to my pc and browse the files, but adb doesn't find it. device not found....
any help?

temporizer said:
Since this is Ubuntu Help, i figured i'd post this here, if it is the wrong forum, let me know.
I am trying, and have been for a week now, to use
Code:
adb shell
however, it keeps giving me the message
Code:
device not found
i know it's there because i am able to mount the sd to my pc and browse the files, but adb doesn't find it. device not found....
any help?
Click to expand...
Click to collapse
You need to edit a couple of files first. Google is your friend.

AdrianK said:
You need to edit a couple of files first. Google is your friend.
Click to expand...
Click to collapse
I tried that. i searched for hours before i posted. and tried a couple things. but none work. thats why i ask the wonderful people here.

temporizer said:
I tried that. i searched for hours before i posted. and tried a couple things. but none work. thats why i ask the wonderful people here.
Click to expand...
Click to collapse
Hmm I didn't follow those exact intructions but something similar for jaunty and it worked fine :-S

[FIXED] Remount failed: operation not permitted

Ok, I'm not a total noob. I've been trying to return to 1.5 as cleanly as possible, but now I'm having an error when trying to remount my phone.
Code:
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9C1HF03306 device
C:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
C:\android-sdk-windows\tools>adb shell
$ su
su
#
This is what I did:
Flashed the 1.5 RUU that Flipz has had out for months. No errors
Ran the Avalaunch PRI fix to get rid of the flipz_01 PRI name
updated my profile
updated my PRL (which is now 65000??)
rooted through the normal sequence without error, I can boot to the recovery just fine, but when I adb shell into the phone I end up at $ instead of #. I have to su to get to # and at the c:\windows-sdk-windows\tools\adb remount fails with "remount failed: operation not permitted"
Is it possible that the PRI update has foiled the root exploit? I even restored a nand backup that I know had a working root and I still have the same results. This is too weird.
Anyone else have this issue? I searched the forum but I came up empty.

Try adb remount before adb shell. I'm pretty sure anythig with adb should be ran at just the command prompt.
Someone feel free to correct me if I'm wrong.

right, this is at the c:\android-sdk-windows\tools\ prompt. I guess I need to re-word that last bullet point to be more clear.
Code:
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9C1HF03306 device
C:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
C:\android-sdk-windows\tools>adb shell
$ su
su
#

Yeah the wording got me. I was hoping it was as simple as that for you tho. Defiantly Strange. Believe me I've had plenty of those moments where hours would have been saved if someone could have just said "no your just doing it wrong".
Maybe try rerunning the RUU and start from scratch the PRI fix should hold thru the RUU but if it did affect something else running the RUU again may correct it.

I RUU'd about 4 times so far on two different laptops, one with XP and one with Win7, running both versions of the HTC Sync drivers.
Something is definitely different. I'm thinking of doing the PRI fix again to see if that helps. The PRL being 65000 instead of the normal 60664 is another anomaly I'm curious about.

looks as if the 65000 PRL is a new one. I can't confirm (not with Sprint) but there is a thread over in General talking about it.
http://forum.xda-developers.com/showthread.php?t=684873

YEAH! I fixed it....well....actually Flipz fixed it for me. I created a custom ROM in the kitchen and flashed it. Now the remount miraculously works. I'm back to being happy...though I don't know why. Its not like I was using root for anything

Nextelian said:
right, this is at the c:\android-sdk-windows\tools\ prompt. I guess I need to re-word that last bullet point to be more clear.
Code:
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9C1HF03306 device
C:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
C:\android-sdk-windows\tools>adb shell
$ su
su
#
Click to expand...
Click to collapse
Can someone splain how to fix this issue w/o flashing? Like maybe from command prompt/shell? Pleeeeease?

mrsato said:
Can someone splain how to fix this issue w/o flashing? Like maybe from command prompt/shell? Pleeeeease?
Click to expand...
Click to collapse
I found something that help me and you. it properly works!!
I can't spell out instructions for the above mentioned suggestion, since I
don't know which file editor comes on the shipped device, but I have an
alternative solution.From the SDK's tools directory, run adb shell. In the
prompt run the following:
# su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 777 /system (Or any subdirectory you want to push to inside system)
# exit
adb push <local file> <device location>
and eventually you should restore the original directory permissions by:
# chmod 755 /system (Or any subdirectory you modified permissions to)
Hope this helps,
Yoav
Click to expand...
Click to collapse

still no Read/Write on /system
I tried the above, and I could not mount /system as read/write:
Code:
adb shell
$ su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Permission denied
$ mount: Operation not permitted
My Android 1.6 is rooted, so I feel like I should be able to do this. But any help would be...helpful.

mojotexas said:
I tried the above, and I could not mount /system as read/write:
Code:
adb shell
$ su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Permission denied
$ mount: Operation not permitted
My Android 1.6 is rooted, so I feel like I should be able to do this. But any help would be...helpful.
Click to expand...
Click to collapse
I'm not at my computer but I think the command is off... check to make sure its exactly how it should be... maybe the coma after the rw
Sent from my HERO200 using XDA App

mojotexas said:
I tried the above, and I could not mount /system as read/write:
Code:
adb shell
$ su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Permission denied
$ mount: Operation not permitted
My Android 1.6 is rooted, so I feel like I should be able to do this. But any help would be...helpful.
Click to expand...
Click to collapse
Just cd to your tools directory and adb remount

huedawg said:
Just cd to your tools directory and adb remount
Click to expand...
Click to collapse
Is there a solution for this?
I have a rooted HTC Desire.
When I type adb remount I get permission denied.
When I type adb shell and then su , i get permission denied!
This was a stock 2.2 rooted with unrevoked 3.
Any idea?
[edit]
i noticed root permissions pop-up on the phone and allowed so su worked.
[/edit]

Hi,
I have a Desire with stock froyo rooted with unrevocked 3 too and cannot use adb remount:
D:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
D:\android-sdk-windows\tools>adb shell
$ remount
remount
remount: permission denied
$
Click to expand...
Click to collapse
I have allowed ADB via the Super user app popup.
Any idea?
EDIT: I have set S-OFF using AlphaRev's recovery fastboot and I am now able to remount in rw (well no access denied anymore)
still missing some access as I fail to remove the Google Maps app (want to use Brut maps only)

ghost_boy1412 said:
I found something that help me and you. it properly works!!
Click to expand...
Click to collapse
This worked perfectly! Thank you!

Good freakin lord why the heck did you feel the need to bump this thread thats almost a year old just to say that!!!!!!!! I rarly shout like this, but this crap is starting to drive me crazy!!!!!!!!!!!!
Grrrrrrrrrrrrrrr

same thing for me. i get permission denied

DannyMichel said:
same thing for me. i get permission denied
Click to expand...
Click to collapse
thank you for letting us all know, and in such detail, and with new valuable information no less
/me shakes fists in rage.

Post deleted.

Don't mean to bring up this dead thread but a more simple solution would be this
adb shell
$ su
# busybox mount -o remount,rw /system (or another desired directory)
# chmod 777 (or another desired permission set) /system (or another desired directory)
# exit
$ exit

[Q]: Read-only filesystem

Hi!
I have rooted my phone (LG Optimus 2X) and mistakenly deleted some files.
I have these files, and want to push them back using adb, put my problem is, that when i try to mount the system in read / write mode using "adb remount" i get this error: "remount faileded: Operation not permitted".
I can't figure out how to fix it, i can pull files etc.
I have also tried to use the adb shell, and copy the files from the internal sdcard, but i'm getting the same error.
Only read-mode.. :/
Anybody who can help, fixing this problem?

If you want to mount /system just write:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Then you're good to go

How to unmount into read-mode only?
Thank! - You saved my day

mrhtml said:
How to unmount into read-mode only?
Thank! - You saved my day
Click to expand...
Click to collapse
A little easier to type...
Mount r/w
Code:
busybox mount -o,remount -rw /system
Mount r/only
Code:
busybox mount -o,remount -r /system
Edit: You shouldn't post stuff like this in dev

[Q] /system/vendor is read-only

Everything was tried, adb terminal, adb pc, different file explorers but that folder stays read-only, even can't change permissions, MAgisk 17.1. ANy ideas?

Stiiigg said:
Everything was tried, adb terminal, adb pc, different file explorers but that folder stays read-only, even can't change permissions, MAgisk 17.1. ANy ideas?
Click to expand...
Click to collapse
be careful what you wish for...
you need to remount the partitions. you can do this through adb shell or terminal emulator on your device.
Adb commands
Code:
adb shell
su
mount -o rw,remount -t ext4 /system
mount -o rw,remount -t ext4 /vendor

Daha3ker said:
be careful what you wish for...
you need to remount the partitions. you can do this through adb shell or terminal emulator on your device.
Adb commands
Code:
adb shell
su
mount -o rw,remount -t ext4 /system
mount -o rw,remount -t ext4 /vendor
Click to expand...
Click to collapse
In response for remount /vendor, it gives
Code:
'/dev/block/dm-0' is read-only

Roman2508 said:
In response for remount /vendor, it gives
Code:
'/dev/block/dm-0' is read-only
Click to expand...
Click to collapse
You need to unlock the other parts of your bootloader then. It will factory reset the device, but you need unlock flashing and unlock flashing critical. This let's you remount critical partitions. Vendor is a critical partition.

Daha3ker said:
You need to unlock the other parts of your bootloader then. It will factory reset the device, but you need unlock flashing and unlock flashing critical. This let's you remount critical partitions. Vendor is a critical partition.
Click to expand...
Click to collapse
It was figured out to be a Magisk problem