Develop Bugs

los root acces

hi all. after restoring to original rom routed from http://forum.xda-developers.com/showthread.php?t=616991 9the second one, I lost the root access. I was trying the following commands
adb shell mount /system
adb push su /system/bin/
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app/
adb shell reboot
but I got this :
what can I do in order to restore my root access? I was trying to re flash with FlashRek, but use less. I still have the Recovery Image when I boot in recovery mode......Help

try in recovery, instead of "mount /system" use "mount -a".

This doesn't necessarily mean you lost root.
It's not an error, for example, "permission denied". You just need an additional parameter, in this case, the mtdblock device (mtdblock3)
To facilitate your life if you mount/umount often, add the appropriate entries to the fstab, ergo, create one.
This is a full valid entry:
/dev/block/mtdblock3 /system yaffs2 rw
or, if you want it your way:
adb shell mount -t yaffs2 -o rw /dev/block/mtdblock3 /system (you might not need -o rw, since it's mounted as rw by default)

Phone stuck in reboot recovery... Help!

I was trying to follow the steps below to install the optical trackpad wake-up. I did the first step "adb reboot recovery". Couldn't get past there. Now my phone is stuck in reboot recovery. How do I get it out and can I do this without reformatting the phone?
zerf said:
I installed this and it worked perfect. Download the file and put the qwerty.kl file in your directory that adb is located. Then follow the commands below.
while phone is powered on plug it in and then do
Code:
adb reboot recovery
Once booted in to recovery do
Code:
adb shell
mount -a
(it will give error saying it couldnt mount curtain things. This is OK)
Looks like this
Code:
~ # mount -a
mount -a
mount: mounting /dev/block/mmcblk1 on /sdcard failed: Invalid argument
mount: mounting /dev/block/mmcblk1p2 on /sd-ext failed: No such file or directory
Now run
Code:
df
to make sure that /system is in the list that it outputs.
Should look like this.
Code:
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted
tmpfs 206848 0 206848 0% /dev
/dev/block/mmcblk0p2 198337 7453 190884 4% /cache
/dev/block/mmcblk0p1 765992 153464 612528 20% /data
/dev/block/mtdblock6 152576 122712 29864 80% /datadat
/dev/block/mtdblock3 253952 180320 73632 71% /system
then
Code:
cd /system/usr/keylayout
cp qwerty.kl qwerty.kl.old
(do this so we have a backup incase we need to go back)
now type exit and then run this
Code:
adb push qwerty.kl /system/usr/keylayout
adb reboot
once booted you should be able to power the screen on with your trackpad.
**** I have noticed that if your phone isn't waking by the trackpad try pressing a little harder or holding the button down for a little longer and then it usually works fine****
Click to expand...
Click to collapse

Sorry MODS for making this thread! I figured it out.

[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] Correct path in Terminal Emulator?

I have spent hours trying to find an answer to what I thought was a simple question, but I just can't seem to find it...
I wanted to familiarize myself more with Terminal Emulator, so I used it to delete a system app that needed to go.
I used these commands:
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblk3 /system
# rm /system/app/xxx.apk
It appears to have worked perfectly after a reboot, but my question is: what is the correct code to mount your system partition in TE? I have seen several variations of the line I used. Often they vary at 'mtdblk3.' I have seen it 'mtdblock5,' for example. Is there a particular line I should use for my specific device? Is it dependent on what I am specifically trying to do?
Any information is greatly appreciated; even/especially a link toward my answer. Thank you very much.

I've always used 'mount -o remount,rw /dev/block/mmcblk0p25 /system'
as far as 'correct' code I don't think there is as such. But I think different devices would have different partitions and mount points for system.
-Nipqer

I think it will depend on where your system is mounted, although I don't know why that would vary for the G2. It might be different for the DZ and certainly for other devices.
You can type "mount" in the terminal to see where everything is mounted.

Ditamae said:
I have spent hours trying to find an answer to what I thought was a simple question, but I just can't seem to find it...
I wanted to familiarize myself more with Terminal Emulator, so I used it to delete a system app that needed to go.
I used the code:
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblk3 /system
# rm /system/app/xxx.apk
It appears to have worked perfectly after a reboot, but my question is: what is the correct code to mount your system partition in TE? I have seen several variations of the line I used. Often they vary at 'mtdblk3.' I have seen it 'mtdblock5,' for example. Is there a particular line I should use for my specific device? Is it dependent on what I am specifically trying to do?
Any information is greatly appreciated; even/especially a link toward my answer. Thank you very much.
Click to expand...
Click to collapse
i use this command:
# mount -w -o remount /dev/block/mmcblk0p25 /system

Thanks for the replies... I see now, that the path I should have used is: /dev/block/mmcblk0p25 /system. And that "code" was the wrong word. I was asking about commands & paths not code. Sorry - still learning.
edit: If anyone knows of a good and thorough resource of Terminal commands, I'd love it if you'd share... I've found bits and pieces of info, but something more comprehensive would be great. Thanks again.

Wow you guys are going about it using the long hand method. If you're just deleting a system app, to mount the /system as rw just enter:
Code:
$su
#mount -o remount,rw /system
#rm -f /system/app/xxxx.apk
The -f command isn't really needed but I use it to make sure the job gets done. Not sure if the pm uninstall command is used anymore. I'll have to look into that. I know some phones required you to mount yaffs and mmcblockXX but for just deleting an app I don't believe it's required. Never had an issue not typing that.

Here's the correct way to delete the app:
mount -o rw,remount /system
rm /path/to/app
reboot
Click to expand...
Click to collapse
Or you could use remount,rw. It's the same command. I threw reboot in there to reload the app list in your launcher correctly.

Mount /system rw using terminal.

I have been trying for hours now to remount the /system partition rw using terminal emulator with no luck. I can do it just fine using root explorer, but thats not what im after. Im trying to make it so that system is mounted rw on boot. But every command i have known to work in the past, and every one i found thru googling has not worked. The command finishes with no errors, but /system is still ro. I even went as far as to unpack the boot img and change /system to be rw on mount. But again when i boot up /system is still ro. Its like something is protecting it or remounting it ro again. By editing the boot.img i was able to mount the root directory (/) rw on boot, but doing the same edit to the /system mount point seems to have no effect. Anyone know what im missing here? I am s-off, unlocked, i have an insecure boot.img, i have root, i dont know how much more insecure my phone could be. If root explorer and other apps are able to do it, there has to be a way to do it thru a shell.

cmlusco said:
I have been trying for hours now to remount the /system partition rw using terminal emulator with no luck. I can do it just fine using root explorer, but thats not what im after. Im trying to make it so that system is mounted rw on boot. But every command i have known to work in the past, and every one i found thru googling has not worked. The command finishes with no errors, but /system is still ro. I even went as far as to unpack the boot img and change /system to be rw on mount. But again when i boot up /system is still ro. Its like something is protecting it or remounting it ro again. By editing the boot.img i was able to mount the root directory (/) rw on boot, but doing the same edit to the /system mount point seems to have no effect. Anyone know what im missing here? I am s-off, unlocked, i have an insecure boot.img, i have root, i dont know how much more insecure my phone could be. If root explorer and other apps are able to do it, there has to be a way to do it thru a shell.
Click to expand...
Click to collapse
Try this:
Create an executable script - like this one:
Code:
#!/system/bin/sh
# Make system rw
chmod 666 /system;
mount("ext4", "EMMC", "/dev/block/mmcblk0p35", "/system");
Save it in your storage location as systemmount (or whatever).
Open terminal, type su.
Type:cd /sdcard/
Type: systemmount
Exit and see if that works. I have not tested it.

Thanks but no luck
Code:
exec /system/bin/sh '/storage/emulated/legacy/Download/scripts/00remount'
/Download/scripts/00remount' <
Unable to chmod /system: Read-only file system
/storage/emulated/legacy/Download/scripts/00remount[4]: syntax error: '"ext4",' unexpected

Put the mount first before chmod. Delete ext4 and emmc
Sent from my Lunar Ecliptic One.

Thanks, but i figured it out. It turns out the command i had used in the first place was correct. (mount -o remount,rw /system). After i ran the command i would check with root explorer to see if it worked, and it always showed it did not. But when you check it the correct way, the way i shoukd have been in the first place, by typing 'mount' in terminal it shows it did indeed get remounted rw. So its an issue with root explorer, not with the command i was using.
Incidently if you do the command 'mount' without su permission, it shows sysyem as ro, but if you do it under an su prompt it shows it as rw.

cmlusco said:
Thanks, but i figured it out. It turns out the command i had used in the first place was correct. (mount -o remount,rw /system). After i ran the command i would check with root explorer to see if it worked, and it always showed it did not. But when you check it the correct way, the way i shoukd have been in the first place, by typing 'mount' in terminal it shows it did indeed get remounted rw. So its an issue with root explorer, not with the command i was using.
Incidently if you do the command 'mount' without su permission, it shows sysyem as ro, but if you do it under an su prompt it shows it as rw.
Click to expand...
Click to collapse
Nice work.
Sent from my Lunar Ecliptic One.