hello, I have an Archos5 unit with the firmware version 1.7.99 android 1.6 on it. i have managed to root the device but I cant figure out how to remount /system read write on the device.
I checked my root ID and its 0.
i have tried mounting with this command : mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
I get an invalid argument if i try mounting from block.
its the same if i try mounting mtdblock5 where cat /proc/mtd5 shows system being located/
i also tried mounting mtd directly but it spits out an error saying block device required.
i would try through android ADB if i could get it working on linux. the windows archos version wont let me remount (vista).
ignoore this thread. i have succeded in doing what i wanted and now have debian apt working in my archos5. since its quite hard to do I will post a how to in another thread.
Hi;
I'm looking for a safe way to root my new A5, firmware 2.0.38, Android 1.6
I want to use Wifi Helper but it requires rooting. I've yet to find how to do this on this machine. Can you help me?
Hi all--in need of some help here--have been crusing the forums for three days and still hitting a brick wall...
Have a rooted (and minimally modded) Atrix 4g in serious need of a hard reset and all the pain that comes with as nearly every app force closes on startup.
Hoping to backup some of my data (contacts, SMS, etc), but unable to do so my usual way (an app, root explorer, or the like), so I'm attempting to use ADB pull to grab the .db files. I'm relatively comfortable with linux, but running into a problem with ro/rw permissions (I think).
have tried the following:
adb pull /data/...../mmssms.db (yields Permission Denied)
# cp /data/....mmssms.db (appears to copy, but no file in destination, and can't copy out of shell)
have been able to remount /system as rw, but not /data where the files are located.
Anybody have suggestions? I'd be most apprecative!
Copy the the files as superuser to your sdcard first and adb pull them from there.
Unfortunately, the whole reason I'm needing to reset is that every app (incl superuser accesses) force closes on start--no chance to move through the phone itself. Since the .db files are not in the usb-accessible file structure I'm thinking that ADB is the only way to access.
Does that make sense?
Hi, OP here--anybody else have a suggestion? Getting a little desperate here... Any thoughts would really be appreciated!
im assuming your accessing ADB via recovery?
You should be able to use su without superuser.apk's permission in that case - however, theoretically, you should not need to use su in recovery anyway.
you can try running
Code:
adb shell ls -l /data/data/*tele*/databases/mmssms.db
and see what you get permissions wise, maybe a chmod could fix it?
Otherwise you could try
Code:
adb shell mount -o remount,rw /data
Another alternative to cp and adb pull is cat
Code:
adb shell cat /path/to/mmssms.db > /path/to/destination-file.db
might copy remote mmssms.db to a local file, while
Code:
adb shell
cat /path/to/mmssms.db > /path/to/destination-file.db
exit
would copy remote to remote
Is /data mounted at all?
This is strange, you should have read access to everything, especially in recovery.
What phone and what recovery?
Its not something as simple as geting the URIs the wrong war round ('cmd local remote' vs 'cmd remote local')?
So, still tinkering... Will give it one last try before I call it quits and just wipe the bloody thing. So, your thoughts were spot on--its probably me missing something.
Quick data dump on progress to data:
Phone: Rooted Motorola Atrix running 2.2
no trouble accessing shell or via ADB
/data is mounted, though only in Read Only mode--can't seem to change, have tried several ways in various modes (shell, su, etc)
Permissions for mmssms.db are: -rw-rw---- radio radio
chmod 777 of the file yields: "Read-only file system," which makes sense since I can't seem to change /data... to rw
Tried to remount rw:
adb shell mount -o remount,rw /data
and
mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p11 /system (for systeem
but get "Operation not permitted" in both cases.... UGH!
Hadn't thought of cat--great idea. Still no real joy however.
I seem to have managed a copy to /system, but can't seem to get it off the device or onto the SD card.
Thanks much for your help so far. Any final thoughts?
SO CLOSE!!!! (and yet...)
crags said:
Hadn't thought of cat--great idea. Still no real joy however.
I seem to have managed a copy to /system, but can't seem to get it off the device or onto the SD card.
Click to expand...
Click to collapse
SO FRUSTRATING!!!! so close, but not quite there--HELP!!!
As noted at the end above, have been able to copy the mmssms.db file to /system/ after remounting as RW
Can't seem to copy or pull off the device--still getting "Permission Denied" no matter which course I try!?!?!
It sounds as if your doing this while booted into the ROM, and (maybe) without su (root)?
su-ing might help, just type su and hit return to enter a root shell
alternatively, going in through recovery ('adb shell reboot recovery') might help as most recoveries ignore permission rules - make sure to mount the partitions your using though.
It almost sounds like the sdcard has no write permissions - you can get the NAND partitions to mount rw, but cant copy to the sdcard.
On my Desire, there is (at least) two mount points: /sdcard and /mnt/sdcard - maybe on your phone only one of your mount points has write permissions?
Otherwise i suggest going in via recovery. You can still use adb (will have to manually mount - 'mount /system' 'mount /date' and 'mount /sdcard' usually work, otherwise use the menu item in recovery )
When in recovery, and after mounting partitions/card, try adb pull, cp /sdcard and cat > sdcard (and if possible cat > computer) plus anything else i forgot (quite tired )
if these dont work something is messed up somewhere in the ROM, or likely kernel and so without ideas a reflash would be the only real solution :/
I did have a bare-minimum+apps recovery script (attached) which might be worth a read to see if your forgetting something obvious - it works on my desire
Hi, this is a blatant crosspost from the android stackexchange site, questions/24081... I posted it there and figured I wouldn't get much help, so I thought I'd try here. Let me know if this is OT or in the wrong place or whatever.
I want to remount a read-only partition in read-write mode, but I want it to be writable for all users.
So far I've got this:
Code:
mount -o bind /someplace /someplace_else
mount -o remount rw /someplace_else
The first command creates a new mount point from a directory. The second one remounts the new mount point as rewritable. This all works.
Problem is, the new mount point has uid=1000,fmask=0222,dmask=0222, so the non-root user still can't write anything, and root can't give it permission.
How do I change the fmask and uid when remounting, or is there something else I can do to make the mount writable for the normal user?
Also, note that the command that worked for me is this:
Code:
mount -o remount rw /someplace_else
...with no comma between "remount" and "rw," as I've seen in almost everything my searches turned up. Does anyone know anything about this discrepancy in syntax?
I'm doing most of this in a terminal emulator on the phone, and in SL4A.
I have this tablet from that greek label named turbo-x(model:strike ii)(not that there is any chance to know of) which there are no windows drivers for, anywhere.
Framaroot doesn't work for it,
windows root can't work for it without drivers
and for linux i tried cydia impactor since linux doesn't need the drivers, which pops up the error "mount: read only file system" when i try to root.
I'm not linux expert or expert of any kind so i messed around with the terminal as much as i could in order to make cydia impactor work, and used $sudo su $adb remount $adb root $adb shell #mount -o rw,remount /system but nothing works, i get the same read only file system on the terminal as well.
Any suggestions? Thanks in advance!
Bump
I have had problems recently with some force closes and someone suggested running fsck to check for system file errors. This was due to a logcat I posted which they browsed (thanks again Aquous).
I have never heard of doing this but after doing some googling I have gleaned some info about how to do it. I know how to connect the tablet and execute adb commands through the sdk. I was wondering if anyone would be able to talk me through doing this on this tablet as all the threads I came across were for different tabs.
I've gone into recovery and found files in /system/bin called fsck.exfat and fsck.f2fs but I am unsure exactly what mode I am supposed to be in in the recovery menu, is it the Terminal Command option or the ADB sideload option (or something else)? And what command do I need to use to run the fsck?
I saw one thread which said to use:
unmount /data
unmount /system
fsck /dev/block/stl9
fsck /dev/block/stl10
but that was for the Samsung Epic 4g, a search through the Samsung Galaxy Tab 2 forum didnt bring anything up.
Any help with this would be very gratefully received.
Cheers
Edit - I don't think I have correctly submitted this thread as a question. I cant manage to delete and re-submit, apologies in advance.