[Q] Rooting Problem, Won't mount. Line needs correction. - Blade General

Hi, I am currently trying to room my Blade but I get this problem in cmd
$ exit
exit
C:\android-sdk-windows\platform-tools>adb kill-server
* server not running *
C:\android-sdk-windows\platform-tools>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\android-sdk-windows\platform-tools>adb shell
# mount -o rw,remount /system
mount -o rw,remount /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# exit
exit
C:\android-sdk-windows\platform-tools>adb push su /system/xbin/
failed to copy 'su' to '/system/xbin/': Is a directory
Click to expand...
Click to collapse
As you can see, I am unable to copy over su to system/xbin.
Does it have to do with the mount command line?

you dont need to use the mount command at all, you can just type 'adb remount' instead of 'adb shell', or if you want to use the mount command then the correct line is this:
mount -o remount,rw /dev/block/mtdblock5 /system
you were missing the device part of the mount command line, it's /dev/block/mtdblock5 for /system on the blade.
you've just given me an idea to post a rooting guide, there is an easier & better way, using adb, fastboot, clockworkmod & superuser.

I fixed it by just getting z4root and rom manager for clockworkmod.

pankaka said:
I fixed it by just getting z4root and rom manager for clockworkmod.
Click to expand...
Click to collapse
Cool. I've written a rough rooting guide using adb & fastboot here: http://forum.xda-developers.com/showthread.php?t=1319257
z4root uses a root exploit that only works on older versions of android. Some versions of the blade sold in some countries use newer versions of Android (2.2.2 or 2.3.5) that have that vulnerability fixed. I wrote a guide that will work on any blade, because it doesn't use any root exploits - it's bad that z4root worked, you need to update your rom!
The blade has an unlocked bootloader, so you can install clockworkmod using 3 commands
Code:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img
fastboot reboot
Then use clockworkmod to install the superuser zip file, or custom rom.

Related

[Q]What is the reason for this?——Can't mount.

hello everybody
After upgrade to the latest TW Official Sense UI for Magic,I found that I cant execute the mount command on G2,whether using adb shell or using a remote mode.
The err info:
Code:
C:\Documents and Settings\Administrator>adb shell mount /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Code:
C:\Documents and Settings\Administrator>adb shell
$ mount /system
mount /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
What hell is the reason for this?Only because there is no root access?
If the reason is root,I execute the remount command,It shows:
Code:
$ remount
remount
remount: permission denied
That means the system is not treating "mount" as an root access command?
Let's talk about it!
here is my G2's info:
SPL:1.76.0007 S-ON H
kernel:[email protected] #901
verion:3.03.751.4 CL#75468
Baseband:63.18.55.06HU_6.25.07.29
I've no idea, I just come in and look...
did you use mbybackup to restore your settings?
Nop,I have not used mybackup...
type su then type it you noob and stop cluttering the development section
Click to expand...
Click to collapse
I suggest you flash the Official Sense UI ,try to type su and then call me noob.
The Official Sense UI has no root access for now,I tried to mount system folder for attempting rooting it.What I wonder is why the terminal gave me the info of a command -grammar err instead of a "permission denied".
-------------
Too few parameters in call mount command and no remount command on G2

[Q] Root 2.2 318 without ADBshell

Hi,
a pin of my USB connector is broken so I cannot get a USB data connection to a PC (but charging still works ...).
How can I root the official 318 build of froyo ? More specifically, in the new build, there doesn't seem to be any mounted filesystem on which one can copy RATC to run it.
Any hint welcome.
Have you already tried superoneclick, androot, or z4root? If so, then maybe try the below.
I don't know if this will work but you can try fard's instructions to root manually and use "Terminal Emulator" from Market instead of ADB SHELL, but i don't know what will happen when you run rageinthecage~ You will need to change the instruction a bit for your case.
http://forum.xda-developers.com/showthread.php?t=844966&highlight=rageagainstthecage
Instructions:
1. Copy all the needed files (from fards thread) into the SDCARD.
2. run Terminal Emulator
3. cd /sdcard/
4. busybox cp rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
5. busybox cp Superuser.apk /data/local/tmp/Superuser.apk
6. busybox cp su /data/local/tmp/su
7. busybox cp busybox /data/local/tmp/busybox
8. chmod 700 /data/local/tmp/rageagainstthecage
9. chmod 700 /data/local/tmp/busybox
10. cd /data/local/tmp
11. ./rageagainstthecage
12. Reset Terminal
13. Start Terminal Emulator again
14. mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system
15. follow the rest of the instructions below "mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system "
In case you can't find it in the thread, here is the original post by fards:
GET ECLAIR/FROYO version of Superuser.apk and su
from http://forum.xda-developers.com/showthread.php?t=682828 extract the two files to the directory you're working from..
GET rageagainstthecage from
http://stealth.openwall.net/xSports/RageAgainstTheCage.tgz
extract the rageagainstthecage-arm5.bin to the same directory you're working from
open a terminal/command line
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
adb push Superuser.apk /data/local/tmp/Superuser.apk
adb push su /data/local/tmp/su
adb push busybox /data/local/tmp/busybox
adb shell chmod 700 /data/local/tmp/rageagainstthecage
adb shell chmod 700 /data/local/tmp/busybox
adb shell
cd /data/local/tmp
./rageagainstthecage
******this will kill adb server but manually kill it anyway and restart it ******
adb kill-server
adb start-server
* daemon not running. starting it now *
* daemon started successfully *
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system
**********Follow the following steps to install Superuser.apk, busybox,su ****************
cd /data/local/tmp
./busybox cp busybox /system/bin/
chmod 4755 /system/bin/busybox
busybox cp Superuser.apk /system/app/
busybox cp su /system/bin/
chmod 4755 /system/bin/su
exit
exit
then reboot streak
************to remount filesystem as readonly,*************
adb shell
# su
su
#mount -o remount,ro -t yaffs2 /dev/block/mtdblock6 /system
# exit
exit
Click to expand...
Click to collapse
Well...
yes, I have tried all that.
The main problem with the last option (i.e. CLI) is that the directory /data/local/tmp/ is not user writable (actually /data permissions are 751). So I was in search of a another directory (in an executable partition) where I can copy rageagainstthecage-arm5.bin.
Finally found it : "find" was my friend. /firstboot/sqlite/jackpal.androidterm/ is owned by my user (ID 10123)! It's the only one I found in all the filesystems!
Note that "find" is available through /system/bin/busybox_1P8P1. Btw /firstboot/sqlite/jackpal.androidterm/ seems to be linked to the terminal process.
Ran rageagainstthecage-arm5.bin various times to no avail ! It didn't give me root!

Terminal command help remount help

I have an Atrix on AT&T. Which means there's a bootloader encryption, and the carrier prevents non-market apk installations, which I have resolved since my phone is rooted and I have changed the boot animation already.
In order to do these things, I found Ghost Commander that would let me chmod my system directories...which is fine, but I feel kind of gimped that I can't do it on terminal.
Basically, what I want to be able to do is remount /system as rw using terminal.
This method doesn't work on both terminal and emulator on my phone. I have done:
Terminal:
Code:
sudo su
cd [sdk directory]
./adb devices
./adb shell
su
mount -o remount,rw -t ext3 /dev/block/mmcblk0p12 /system
and this is where I get stuck because I just get an Invalid argument error.
Here is some info about my sytem -
Usage: mount [-r] [-w] [-o options] [-t type] device directory
/dev/block/mmcblk0p12 /system ext3 ro,noatime,nodiratime, data=ordered 0 0
Been searching for the answers for a while now, and now I'm here. What am I doing wrong? Thanks
there
Code:
mount -o remount,rw /dev/mmcblk0p12 /system
back
Code:
mount -o remount,ro /dev/mmcblk0p12 /system
Hmm, well at least I didn't get any errors this time.
I didn't get a confirmation or that it did anything at all. Is that normal?
Run mount with no parameters and look for the line with that device name, should see rw in that line instead of ro.
Sent from my MB860 using XDA App
Thanks guys, but I resorted to busybox chmod command instead lol
I tried this and got no errors, and using cat /proc/mounts/ I see the path as rw. But when I try to copy I still get the read only file system error.
**Lol, I had the phone in usb storage mode and had to switch it to Windows Media Sync**

Fix WiFi Channel 12-13

You can fix wifi channel 12-13 support by setting the wifi_country_code to EU.
You need a rooted device and sqlite3 to fix (attached).
Unpack the attached zip and run fix_wifichannel_EU.bat (Windows only)
or with linux:
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p3 /system
exit
adb push bin\sqlite3 /system/bin
adb shell
su
chmod 6755 /system/bin/sqlite3
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO secure (name, value) VALUES ('wifi_country_code', 'EU');"
reboot
Ohhhh it's good to see you here in the Iconia section!
I used to be a user of your great Desire Kernels/roms.
Hope to see some work from you soon.
richardtrip said:
You can fix wifi channel 12-13 support by setting the wifi_country_code to EU.
You need a rooted device and sqlite3 to fix (attached).
Unpack the attached zip and run fix_wifichannel_EU.bat (Windows only)
or with linux:
Code:
adb shell mount -o rw,remount /dev/block/mmcblk0p3 /system
adb push bin\sqlite3 /system/bin
adb shell chmod 6755 /system/bin/sqlite3
adb shell sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO secure (name, value) VALUES ('wifi_country_code', 'EU');"
adb shell reboot
Click to expand...
Click to collapse
Thank you very much and great to see you here
OT: can you help us with the recovery issues ??
Thanks in advanced. I will try sometime in the near future.
Enviado desde mi GT-I9000B usando XDA Premium App
so you got this tablet, richard =P Wonder when we will be able to start playing with custom rom =)
Btw, I notice that a huge amount of RAM is consumed and the maximum amount of RAM freed I have ever got is 440MB. Do you know what happened to the rest?
lpachuong said:
so you got this tablet, richard =P Wonder when we will be able to start playing with custom rom =)
Btw, I notice that a huge amount of RAM is consumed and the maximum amount of RAM freed I have ever got is 440MB. Do you know what happened to the rest?
Click to expand...
Click to collapse
The rest of the ram is reserved for video on boot.
I thought so, but don't you think that is too much out of 1GB ram? I found the device is laggy if ram goes under 350MB. Hope modded kernel can help optimize ram.
sweet
Nicely done! It works. Yea it is good to see you here' meaning we have somebody who knows a thing or two about android development.
W
Fix worked!
For some strange reason adb remount command didn't worked and adb wasn't able to push sqlite3 file to /system/bin even after remounting /system rw from the device itself. I had to push it to sdcard and then move it to /system/bin.
By the way, channel 13 is working fine now.
Thx
Hi Richard,
It's good to see such a great dev interested in the A500 (I have a Desire). <vbg>
EDIT: I can confirm that this works!
I cannot remount /system, either via ADB nor via a shell (on the device itself). In both cases, I get...
Code:
mount -o rw,remount /dev/block/mmcblk0p3 /system
mount: Operation not permitted
[Edit: worked with a terminal, but forgot to SU first, and I was typing mmcblkop3, not mmcblk0p3 !!]
I tried to be clever (NB: I don't have a SD card installed):
Code:
adb shell mount -rw /dev/block/mmcblk0p3 /mnt/external_sd
Usage: mount [-r] [-w] [-o options] [-t type] device directory
That's the extent of my *nix skills...
Any ideas?
-Dave
zxdavb said:
Hi Richard,
It's good to see such a great dev interested in the A500 (I have a Desire).
I cannot remount /system, either via ADB nor via a shell (on the device itself). In both cases, I get...
Code:
mount: Operation not permitted
I tried to be clever (NB: I don't have a SD card installed):
Code:
adb shell mount -rw /dev/block/mmcblk0p3 /mnt/external_sd
Usage: mount [-r] [-w] [-o options] [-t type] device directory
That's the extent of my *nix skills...
Any ideas?
-Dave
Click to expand...
Click to collapse
Try su before the mount command.
Edited the procedure in the first post so try that (should work now).
Sent from my A500 using XDA Premium App
zxdavb said:
Hi Richard,
It's good to see such a great dev interested in the A500 (I have a Desire). <vbg>
I cannot remount /system, either via ADB nor via a shell (on the device itself). In both cases, I get...
Code:
adb shell mount -o rw,remount /dev/block/mmcblk0p3 /system
mount: Operation not permitted
I tried to be clever (NB: I don't have a SD card installed):
Code:
adb shell mount -rw /dev/block/mmcblk0p3 /mnt/external_sd
Usage: mount [-r] [-w] [-o options] [-t type] device directory
That's the extent of my *nix skills...
Any ideas?
-Dave
Click to expand...
Click to collapse
Just do
Code:
su
mount -o remount,rw /system
daveba said:
Just do
Code:
su
mount -o remount,rw /system
Click to expand...
Click to collapse
Thanks!
For the beginners (like me): I noticed that /system was set back to read-only on reboot...
Works brilliantly. Thanks.
thx - but I trust editing the build.prop in Root Explorer should also do the job for those who don't want to mess with adb and commands.
hi
can anyone tell me whats this fix for?
is it going to make wifi receiver even better?
thx..
he_stheone64 said:
thx - but I trust editing the build.prop in Root Explorer should also do the job for those who don't want to mess with adb and commands.
Click to expand...
Click to collapse
yes,
add this line
ro.wifi.country=EU
and reboot.
i have this message:
'Unable to detect a device over adb'
I've connected my nexus S via usb cable, i've tryed with the usb usb storage on an off, and i get the same message.
I'm using windows / x64.
Dexter_nlb said:
yes,
add this line
ro.wifi.country=EU
and reboot.
Click to expand...
Click to collapse
i've done that but i canot save the file i get the message that it's a read only file system.
how can i gain write access to that file??
Thanks the fix_wifichannel_EU.bat in the zip worked like a charm. Channel 13 now works on my Asus Eeepad Transformer purchased from the US as well.

Problem with Relaunch

The device in question is Nook Simple Touch, rooted with NookManager.
I had deleted Relaunch.apk ver. 1.3.8 in order to install newer version.
But after de-installation, iam unable to charge the folder with apps....
How to install Relaunch again ?
gsms said:
The device in question is Nook Simple Touch, rooted with NookManager.
I had deleted Relaunch.apk ver. 1.3.8 in order to install newer version.
But after de-installation, iam unable to charge the folder with apps....
How to install Relaunch again ?
Click to expand...
Click to collapse
So, basically you are without an Android launcher or file manager?
If you made a backup with NookManager, restoring it is your best bet. If not, make sure to do so once this is sorted out. Backup early and often.
Do you have wireless ADB working? You can install (or reinstall) apps that way. Or, if you have the Market working, install any file manager that will work. That will give you access to folders again and you can copy over apps via USB and then use the file manager to install them.
I have installed adb thru usb, but now have other problem.
Trying to copy file(s), it gives me message ,that folder is read-only.
What is exact command to mount folder as read-write in adb shell ?
I tried many times - with no success...
non working-
adb remount /system/
adb remount
adb remount root/system/
and so on.................................
Please help
gsms said:
The device in question is Nook Simple Touch, rooted with NookManager.
I had deleted Relaunch.apk ver. 1.3.8 in order to install newer version.
But after de-installation, iam unable to charge the folder with apps....
How to install Relaunch again ?
Click to expand...
Click to collapse
Have you tried downloading the Relaunch.apk file via a web-browser? Once the download is completed you should get a prompt on whether you want to install it.
---------- Post added at 04:27 PM ---------- Previous post was at 04:19 PM ----------
gsms said:
I have installed adb thru usb, but now have other problem.
Trying to copy file(s), it gives me message ,that folder is read-only.
What is exact command to mount folder as read-write in adb shell ?
I tried many times - with no success...
non working-
adb remount /system/
adb remount
adb remount root/system/
and so on.................................
Please help
Click to expand...
Click to collapse
To mount /system as read+write:
Code:
adb shell
mount -o rw,remount /dev/block/mmcblk0p5 /system
exit
After you're done with copying over the desired file into /system, just reboot the nook to revert the mounting back to read-only.
After typing the first 2 rows of the code :
adb shell
mount -o rw,remount /dev/block/mmcblk0p5 /system
i receive message:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
So this row
"mount -o rw,remount /dev/block/mmcblk0p5 /system" is not correct....?
upd1:
i was able to see the permissions for folder /system
drwxr-xr-x
This means :
(755) — The owner has read, write and execute permissions; the group and others can only read and execute.
This is strange, because iam the owner...
gsms said:
After typing the first 2 rows of the code :
adb shell
mount -o rw,remount /dev/block/mmcblk0p5 /system
i receive message:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
So this row
"mount -o rw,remount /dev/block/mmcblk0p5 /system" is not correct....?
Click to expand...
Click to collapse
The mount command line I provided is the correct command for your purpose. Note that the command is to be entered on the NST itself after you get on it using "adb shell" command.
upd1:
i was able to see the permissions for folder /system
drwxr-xr-x
This means :
(755) — The owner has read, write and execute permissions; the group and others can only read and execute.
This is strange, because iam the owner...
Click to expand...
Click to collapse
The folder permission 755 is inoperative since the filesystem itself is still being mounted read-only.
gsms said:
After typing the first 2 rows of the code :
adb shell
mount -o rw,remount /dev/block/mmcblk0p5 /system
i receive message:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
So this row
"mount -o rw,remount /dev/block/mmcblk0p5 /system" is not correct....?
upd1:
i was able to see the permissions for folder /system
drwxr-xr-x
This means :
(755) — The owner has read, write and execute permissions; the group and others can only read and execute.
This is strange, because iam the owner...
Click to expand...
Click to collapse
I have been able to successfully achieve this with this command:
mount -o remount rw /system
The command is simpler and thus I am less likely to make a typo.
Thanks for your entries, but i already re-rooted my Nook.
I was out of nerves to deal with adb shell....
----------------
But using "mount" command thru adb shell could be very helpful in some critical cases....
gsms said:
Thanks for your entries, but i already re-rooted my Nook.
I was out of nerves to deal with adb shell....
----------------
But using "mount" command thru adb shell could be very helpful in some critical cases....
Click to expand...
Click to collapse
Make a backup

Categories

Resources