As the title says, I'm having trouble pushing the busybox binary to my T-mobile G1.
I have ADB running, and have it successfully connected to my phone and can start a shell and everything. The problem is, when I type
Code:
adb push C:\busybox /data/local/busybox
All I get is
Code:
1092 KB/s (0 bytes in 1782264.001s)
and nothing writes. Any help would be greatly appreciated. Thank you.
**Edit**
If it helps to know, I've tried pushing other files, as well as pulling some, but it hasn't worked. The same "0 bytes in 1782264.001s" thing just pops up and nothing happens.
I hope someone can help.
I have my Polaris NAND flashed with 2.6.25 kernel + casacristo's RLS18 ROM.
I have updated from the market the Superuser but now I get the pessage that SU is not updated and to download the new one (3.0.3.2).
I download the new one , the Root access is granted but at the end more or less I receive this message translated from italian:
...
...
md5sum ... OK
Mod file su 06755... OK
Moving su to its final position ... failed...
TRY Again
I tryed several times but ... no chance to update it... how can I manage ?
miazza
Here is latest su binaries v3.0.3.2. Download and unzip file. Push this to /system/bin and /system/xbin and then change rights with chmod to 6755. Reboot phone. Done.
Thanks, I will try.
Shall I do via ADB or can I try with RootExplorer for example ?
miazza
ADB, unless your root explorer can set 6755 rights
whitealien said:
ADB, unless your root explorer can set 6755 rights
Click to expand...
Click to collapse
It worked great. I managed with RootExplorer but it can be done also via FTP with Filezilla.
Thanks
miazza
file permissions doesn't work
Hi,
I use a HTC wildfire S, who have been rooted, but still in original ROM.
My SU doesn't want to be updated, as described in the first post.
So I downloaded the ZIP, and put SU on the sdcard. With ROOT BROWSER I copy it on /system/bin (SU have been copied automaticaly in /system/xbin).
I tried to change the permissions files, but after reboot, permissions are ---rwxr-x.
I tried with ADB. My phone is well recognised :
C:\Program Files\Android\android-sdk\platform-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
SH191TR05136 device
When I tried to change permissions file SU :
C:\Program Files\Android\android-sdk\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
Unable to chmod /system/bin/su: Read-only file system
$ chmod 6755 /mnt/sdcard/temp/su
chmod 6755 /mnt/sdcard/temp/su
Unable to chmod /mnt/sdcard/temp/su: Operation not permitted
$ chmod 755 /mnt/sdcard/temp/su
chmod 755 /mnt/sdcard/temp/su
Unable to chmod /mnt/sdcard/temp/su: Operation not permitted
$
Do you have an idea ? Thanks by advance, because right now, my phone is not still root...
I have no idea about how ROOT BROWSER works.
With RootExplorer you can tap the su file and keep it untill the permission window appear. At that point you can change all the file rights.
Another way for doing it is via FTP by using SwiFTP.
ciao
miazza
miazza said:
I have no idea about how ROOT BROWSER works.
With RootExplorer you can tap the su file and keep it untill the permission window appear. At that point you can change all the file rights.
Another way for doing it is via FTP by using SwiFTP.
ciao
miazza
Click to expand...
Click to collapse
Root browser seems to work the same way.
How can you use FTP with a phone ? It's suppose to use an IP adress. But by USB, there is not... But I will,l try asap.
However, my apps couldn't take root permissions, so I feel bad...
Use SwiFTP (it should be free from the market).
It works over Wireless connection to your internal WLAN and provide you with an FTP address like 192.160.0.x.
While you are connected through FTP client (like Filezilla), you can see your mobile File System as well as your SD.
with a right click on the su file you can change your rights.
But I do not know if it works even if you are not rooted...
miazza
I solved my problem my re-rooting my phone, using http://forum.xda-developers.com/attachment.php?attachmentid=672519&d=1312136127.
My phone says that the binary SU was obsolete, but when I tried "AGAIN" to update it, it was successful that time.
Strange, I don't understand why now the update was ok. But all is right.
Thanks everyone for the help.
I wanted to share my experience with following this thread
http://forum.xda-developers.com/showthread.php?t=1709296
i unfortunatly do not meet the 10 post limit
Following the process i got stuck here
Code:
Now it's time to reboot
adb reboot
After phones reboots
adb remount <-----------------HERE---------------------------
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
ADB told me that i dod not have the correct permissions to push the SU file to the phone. The phone would boot, but would not load the widgets or bottom menu. Attempting to open settings would prompt Android.Core to crash.
Scary stuff
The problem was with the ADB Reboot command. It normally reboots the phone properly, but when i ran ADB Reboot, the phone cut power (off) instead of rebooting. Something did not go as intended and i needed to power on my phone, and reboot it manually without the USB cable connected (lagged too much).
After that, the ADB Remount was successful and the rest of the process ran smoothly. I am happily rooted
Thank you to all
~Can someone copy this into the actual thread? I want to help spread rootsauce.
eek:k so I have a Linsay F-7HD and it is giving me a fit trying to root it. This is a nice tablet with Google certifications and Google Play. A Cortex A-9 2.0 single core processor, 4G flash drive with 1.98G free, 512m, Android 4.1.1, micro sdcard to 64G. and usb host cable,ear phone plugs, usb cord and ac charger, very responsive,quick all for $99.00. I only want to root mainly to change vold.fstab, so as to switch internal and external. Also need to do a backup of Rom.
Problem is that it connects to usb, usb debugging is checked, can transfer files to or from device. I have SDK installed on C:, it works fine with all my other android devices but can not detect F-7HD in normal on mode. Recovery by pushing +volume and then power, gives me android down but can't get into any menu BUT ADB detects device and as being in recovery mode, I've tried adb push for superuser, su, and busybox. Busybox and su are there but not superuser. I tried chmod after is says all is transferred by abd push but comes back error. I also can't get into fastboot mode. I will list the abd commands below so maybe someone can give me a pointer or ANY help. I'm not good with adb but can usually Google and find commands that I need. I have the 3 files in my SDK platform tools folder and has worked before with any other device or files. I also can't get a adb shell or su to work, adb reboot only turns device off. Any help would be great. Thanks
adb push Superuser.apk /system/app
adb push busybox /system/xbin
adb push su /system/xbin
adb shell chmod 664 /system/app/Superuser.apk
adb shell chmod 664 /system/xbin/busybox
adb shell chmod 664 /system/xbin/su
adb shell reboot
Anyone have any ideas that I might could try.
Was hoping someone might have a suggestion.
Sent from my Nexus 7 - using xda premium
Hope some more of these device are sold, so someone will help root this 1.
Sent from my NABI2-NV7A using xda premium
Ok......... First specs
Windows 8.1 update 1
adb installed correctly
cmd in the correct folder
firewater in the correct folder
Phone will not stay online through adb reboot, I unplug the usb and then reconnect and eventually it will show up again. Then I follow the steps through to fire water says first bottle is open , chugging, opening bottle 2, chugging. Then the phone just shuts off completely and displays the charging icon... I am at a total loss for what the hell is going on, any thoughts?
I entered the command in the following way and it worked:
adb reboot
waited for the device to boot all the way up then : adb push firewater /data/local/tmp
adb shell
chmod 755 /data/local/tmp/firewater
su
/data/local/tmp/firewater
And it worked that way.
Did you grant the RSA prompt? And grant firewater root privileges?
Sent from my HTC6525LVW