Hello, I recently got a Motorola droid pro (Android 2.3.4) and I'm looking to root it to remove some of the bloatware on it and stuff like that. I tried using SuperOneClick but it stalls on the step:
Shell rooting device...-Step #7 WaitForDevice
With the detail text being:
mount -o rw,remount /dev/block/mmcblk1p21 /system > /data/local/tmp/output 2>&1
export TEMPRANDOM=50620
export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output
mount: Operation not permitted
END:50620
I installed the most up to date drivers via pdanet and ran SuperOneClick as an admin. Anybody know why it stalls here? Also if there's a better way to root this device I'm up for trying that. Thanks in advance for any help. ^_^
Found something that worked. This tool worked for me using the Gimli exploit.
Related
Hello,
I am a newbie on this site and android development. I want to installa nd run openvpn to my emulator. I am using these 2 sites for reference :
1)
chengdu110.wordpress com
2010/08/14
want-openvpn-work-on-android-device
2)
android.modaco
content
software
291919
openvpn-on-android/
I am facing couple of problems. From 1st site, I can't copy busybox to system/xbin folder. I get no access, permission failure, etc such messages. Am stuck at this point and thus can't proceed ahead. In Part 2 also need to access /system/lib/ where again problem comes.
In site 2, same cannot access /system/lib or /system/bin folder. Even I can't mount like this : ADB shell mount /system
Command mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system from site 1 was successful.
Even I face problems with cp cmd. Just cp libcrypto.so libcrypto-orig.so doesn't work. I got to give "/system/lib/libcrypto.so cp libcrypto.so libcrypto-orig.so" this format only it copies. Though in the above case "Permission denoed" occured for system/lib. But this foramt worked while copying busybox file.
Can anyone help me with the permission to system folders /xbin, /lib, /bin. Why is mounting required ? Why I am not able to mount directly as mount /system; I need to give full command mount -o rw, .... -t .... /system. I am not sure what all to give in the "..." place - had just copied it from site 1.
Any help, guidance is highly appreciated. I use Eclipse DDMS and Android emulator 2.3.3. Please try to help me.
I´m trying to root my phone. It has been rooted before but something messed up and i dant have root anymoore.
I use this method
Code:
adb shell
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
When i write
Code:
/bin/mount -o remount,rw /system
i get
Code:
/bin/mount: not found
if i check with Astro the file seems to be there.
Anyone know how to solve this?
Just root with : http://forum.xda-developers.com/showthread.php?t=1255548 ?
Its for 2.3.4 or earlier android system.
PakaPakaxz said:
Just root with : http://forum.xda-developers.com/showthread.php?t=1255548 ?
Its for 2.3.4 or earlier android system.
Click to expand...
Click to collapse
It doesnt work.
having the same issue...
jiggytom said:
having the same issue...
Click to expand...
Click to collapse
Did you solved this problem yet?
You might try:
/system/bin/mount -o remount,rw /system
The /bin partition is osh, perhaps you remade this in some way that adb can not read/execute it?
I'm rooted via the standard root, with CWM installed.
When I attempt to mount /system as read-write with mount -o rw,remount /dev/block/system /system, about 10 seconds later it remounts as -ro.
This means I can't change anything on there, is anyone else having this issue and is there a fix?
MrLadoodle said:
I'm rooted via the standard root, with CWM installed.
When I attempt to mount /system as read-write with mount -o rw,remount /dev/block/system /system, about 10 seconds later it remounts as -ro.
This means I can't change anything on there, is anyone else having this issue and is there a fix?
Click to expand...
Click to collapse
I had a similar problem once and I fixed it by restoring an old nandroid backup, I was never able to figure out what caused it.
I had the same issue when I installed the ota2 update, then tried to reroot. I think I was able to change permissions by installing, then opening superuser app.
Im on OTA1.
Hello,
I've got the same problem. With the following programs i have read/write access to /system only for seconds:
Esexplorer, file manager hd, root explorer, total commander , especially: adb shell
Strange thing: i have no problems with permissons when using x-plore or titanium backup.
(Currently OTA2)
Installing superuser again does not fix anything.
I have the same problem here (OTA2) :-/
A workaround I found is to chain the remount-command with the command you want to execute on /system:
Code:
$ su
# mount -o rw,remount -t ext4 /dev/block/mmcblk0p3 /system && cp /sdcard/Download/kernel_modules/cifs.ko /system/lib/modules/
# ls /system/lib/modules/
bcm4329.ko
cifs.ko
scsi_wait_scan.ko
Brilliant!
hey i flashed xxjpu Official Europe rom without bootloader on my galaxy 3 ...but when i try to root my phone with superuserclick ...it cant root my phone ..i saw the logs ..i found ..push superuser.apk failed ..because no memory left ..but i have lots of memoryy ..somebody please help ..
if u dont use Swype, conenct ur phone to ur PC :
Code:
adb shell
# mount -o remount,rw /dev/block/stl6 /system
# rm -r /system/app/Swype.apk
# rm -r /system/app/Swype.odex
You'll gain a lot of space in /system
Then, try rooting again
Maybe you can find help here
http://forum.xda-developers.com/showthread.php?t=1237297
Sent from my GT-I5800 using xda premium
I had some trouble trying to make Viper4Android v2.4.0.1 work on my Honor 5C running Android 6.0. This could be helpful…
Viper4Android didn't work after installation and reboot, the driver status showing as "abnormal". It seems related to a change in default SELinux policy.
I read that changing globally the SELlinux policy to "permissive" can solve the problem but it may be an extreme solution (SELinux is a security feature to restrict what an application can do, I don't know the potential edge effects).
I found another solution on the web, which consists in patching the SELinux policies at boot, just enough for Viper4Android to work.
If you did not make a systemless installation of SuperSU, open an adb shell and use these commands (courtesy of androiding.how):
Code:
su
mount -o rw,remount /system
cd /system/su.d
echo '#! /system/bin/sh' > 50viper.sh
echo '/system/xbin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"' >> 50viper.sh
chmod 755 50viper.sh
cd /
mount -o ro,remount /system
And reboot.
If you did make a systemless installation of SuperSU, open an adb shell and use this instead:
Code:
su
mount -o rw,remount /su
cd /su/su.d
echo '#! /system/bin/sh' > 50viper.sh
echo '/su/bin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"' >> 50viper.sh
chmod 755 50viper.sh
cd /
mount -o ro,remount /su
exit
And reboot.
Didn't work for me, tried the 2nd method as the first one gave an error at the 3rd step, completed everything, rebooted, still no luck
imrock said:
Didn't work for me, tried the 2nd method as the first one gave an error at the 3rd step, completed everything, rebooted, still no luck
Click to expand...
Click to collapse
I just noticed that in my 2nd block the characters ’ and ” were used instead of ' and ". I'm not a POSIX shell expert but since these are not the same characters it can make a difference.
I've updated the 2nd method, you can give it a try — you can use it "as it is", it will overwrite the previously created file.
This trick didn't work for me.
I ended up installing SELinuxModeChanger and now Viper is rockin' :good: