Hey everybody, I was wondering if anyone could be of any assistance in helping me out with rerooting 2.3.5? I tried using Zerg, and followed all of the instructions in one of the references (SBF to 2.3.4, apply 2.3.5 update, etc.), and I'm still having no luck. Anyone know what's going on? I'd really love to flash Eclipse 2.0.1.
Do you have usb debugging enabled along with unknown sources? What problem are you having?
Sent from my Eclipsed and ICS themed X2.
Yeah...we need more details about how it's falling to help you
I am pretty sure tho it never"told me" I was rooted.
After it completed I waited a couple minutes , reboot my phone and was good to go
Might want to also point out that he should flash 2.0.2 not 2.0.1 since the OP still says 2.0.1....
I have USB debugging enabled, along with unknown sources. Also, I have the phone set to charge mode. Anything else you guys need to know? It's pretty much just throwing tons of errors during Zerg, then after a reboot, nothing has changed. It fails to install anything. I'm on 2.3.5, just like the reference post said, so I don't understand what's going on. P.S. Eclipse 2.0.1 is the one on the post still, though I have seen 2.0.2, I don't know where I could get it, since nitro's post doesn't have it.
You might want to try usb mass storage mode. That's how I always run mine with no problems.
Sent from my Eclipsed and ICS themed X2.
i believe you have to use it on pc mode if you're using windows..100% fail proof for me and I've done this countless number of times
paul_viado said:
i believe you have to use it on pc mode if you're using windows..100% fail proof for me and I've done this countless number of times
Click to expand...
Click to collapse
Yeah that's what I thought as well
paul_viado said:
i believe you have to use it on pc mode if you're using windows..100% fail proof for me and I've done this countless number of times
Click to expand...
Click to collapse
I've tried both of PC mode and USB Mass Storage, and neither one of them worked. I kept getting device not found errors. Any help there?
I have had the same problem as the op that's why I like root keeper but I have not gone to eclipse.
Did u download zergrush as a.zip correct?
Did u make sure to extract everything to the desktop?
And do u have the correct motorola drivers installed?(32bit 64 bit)
tried uninstalling and reinstalling drivers?
Reboot computer after extracting everything to desktop?
Hook phone to computer before opening zergrush?
Lots of different things to try.
If u try all that(and more) just try a different computer.
---------- Post added at 08:33 PM ---------- Previous post was at 08:29 PM ----------
After re reading thread and seeing its device not found errors it makes me suspect motorola drivers are causing the.problem somehow.
Or maybe try a different.USB port and.even a different USB cord
ashclepdia said:
Did u download zergrush as a.zip correct?
Did u make sure to extract everything to the desktop?
And do u have the correct motorola drivers installed?(32bit 64 bit)
tried uninstalling and reinstalling drivers?
Reboot computer after extracting everything to desktop?
Hook phone to computer before opening zergrush?
Lots of different things to try.
If u try all that(and more) just try a different computer.
---------- Post added at 08:33 PM ---------- Previous post was at 08:29 PM ----------
After re reading thread and seeing its device not found errors it makes me suspect motorola drivers are causing the.problem somehow.
Or maybe try a different.USB port and.even a different USB cord
Click to expand...
Click to collapse
I tried literally ALL of these things, to no avail. The drivers are fine, though, as the device not found errors only happened when it wasn't in Charge Mode. Can anyone here read the log if I copy and paste it here?
Worth a shot.
No proMises but it might help someone understand what happening.
---------------------------------------------------------------
Easy rooting toolkit (v3.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (16 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
--- cleaning
adb server is out of date. killing...
* daemon started successfully *
--- pushing zergRush"
adb server is out of date. killing...
* daemon started successfully *
206 KB/s (23056 bytes in 0.109s)
--- correcting permissions
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
--- executing zergRush
adb server is out of date. killing...
* daemon started successfully *
./data/local/tmp/zergRush: permission denied
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
adb server is out of date. killing...
* daemon started successfully *
--- pushing busybox
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
--- correcting permissions
adb server is out of date. killing...
* daemon started successfully *
Unable to chmod /data/local/tmp/busybox: No such file or directory
--- remounting /system
adb server is out of date. killing...
* daemon started successfully *
/data/local/tmp/busybox: not found
--- copying busybox to /system/xbin/
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
--- correcting ownership
adb server is out of date. killing...
* daemon started successfully *
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
adb server is out of date. killing...
* daemon started successfully *
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
rm failed for /data/local/tmp/busybox, No such file or directory
--- pushing SU binary
adb server is out of date. killing...
* daemon started successfully *
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
--- correcting permissions
adb server is out of date. killing...
* daemon started successfully *
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
adb server is out of date. killing...
* daemon started successfully *
rm failed for /system/xbin/su, Read-only file system
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
--- pushing Superuser app
adb server is out of date. killing...
* daemon started successfully *
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
--- rebooting
adb server is out of date. killing...
* daemon started successfully *
ALL DONE!!!
Press any key to continue . . .
I don't remember it telling me adb server out of date .
Could be your problem.
But I'm the last person to ask about adb sorry lol.
---------- Post added at 08:52 AM ---------- Previous post was at 08:50 AM ----------
Wait.
What 2.3.5 build are you on?
I know someone said they had problems rooting one of them...make sure its the one from Overminds thread inn development
I'm on .412, the one from Overminds post. As far as the ADB goes, I'm lost as well.
Try going to the Windows Task Manager and ending all adb.exe services and processes. Then give it a shot. From what I can gather that error comes from an old adb session being open on your computer.
Sent from my Eclipsed and ICS themed X2.
T3HBR1AN said:
Try going to the Windows Task Manager and ending all adb.exe services and processes. Then give it a shot. From what I can gather that error comes from an old adb session being open on your computer.
Sent from my Eclipsed and ICS themed X2.
Click to expand...
Click to collapse
I looked, and there was none open. I'll try again now and see if there's any difference.
What it keeps saying is that this is a Read-Only file system, and that it can't push the SU and Busybox to the right place. The only thing I'm confused about is why.
Id say thats because you haven't gained root access so the root file system is still r/o. There was one other thing I found relating to the adb out of date error but it was over my head. Where did you get your copy of zerg from?
Sent from my Eclipsed and ICS themed X2.
C:\ADBTOOLS>adb devices
List of devices attached
da4d4717 device
C:\ADBTOOLS>adb shell
[email protected]:/ $ su
su
[email protected]:/ # adb devices
adb devices
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
List of devices attached
[email protected]:/ #
my device connects to adb,
however as soon as I go into adb shell, the device is no longer found.
What is going on here?
mdelaney1986 said:
C:\ADBTOOLS>adb devices
List of devices attached
da4d4717 device
C:\ADBTOOLS>adb shell
[email protected]:/ $ su
su
[email protected]:/ # adb devices
adb devices
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
List of devices attached
[email protected]:/ #
my device connects to adb,
however as soon as I go into adb shell, the device is no longer found.
What is going on here?
Click to expand...
Click to collapse
Of course that happens when you run adb shell you are entering in your phone using the debbuging shell. You are in your phone. This happens to me also when i am using adb shell no devices will be shown. If you can run any command from adb shell then your device is there. Nothing to worry about. It is normal.
If you disconnect your device when in adb shell you will see it will automatically exit the shell!
Hit Thanks if i helped you!
Hello guys.................
This is "GOPINADH"
TODAY I'am going show you how fix adb error in ubuntu...........
This happens to me sometimes with certain devices.
This is the error i get
input
Code:
adb devices
output
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
So here is the solution for this
Step 1: Find the Vendor ID
You can do this by typing
Code:
lsusb
. My output is something like this:
Code:
Bus 001 Device 006: ID 1782:4012 Spreadtrum Communications Inc.
In this case, 1782 is the Vendor ID.
Step 2: Create an adb_usb.ini file
Run the following
Code:
echo "0x<your device's Vendor ID>" > ~/.android/adb_usb.ini
Step 3: Restart adb
Code:
adb kill-server
Code:
adb start-server
Since doing that, my devices have all shown up in adb devices.
now input
Code:
adb devices
output
Code:
List of devices attached
06320984656459 device
press thanks if helped:good:
Hi, how about the error in 16.04 with adb freezing the system (i apologize if im in the wrong place) kind of desperate now
Unfortunately it does not work for me with the same vendor "1782".
The output of
Code:
adb devices
remained empty.
helloo greetings i have a problem with adb i want to connect with IDA pro but i got error
Code:
C:\adb>adb kill-server
C:\adb>adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
C:\adb>adb shell
[email protected]:/ $ su
2|[email protected]:/ # cd data/tmp/files
[email protected]:/data/tmp/files # ls
android_server
armlinux_server
armuclinux_server
linux_server
linux_serverx64
[email protected]:/data/tmp/files # ./android_server
error: only position independent executables (PIE) are supported.
Thanks in advance sorry for bad english
Hello,
my phone (I think it is not rooted because adb shows the dollar character) is stuck into the recovery for an unknown reason. Is there a way to access the phone folders through ADB / shell commands?
I'm a newbie and I tried to do by myself but unfortunately I cannot reach my objective.
for example, I (think) I successfully reached the sdcard (is this the android folder name where all the personal data si saved?) but when I try the command adb pull -p It doesn't work. Here what it happens:
1|[email protected]:/ $ cd sdcard
[email protected]:/sdcard $ adb pull -p
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/sdcard $
Any Idea? Thanks
Howl55 said:
Hello,
my phone (i think it is not rooted because adb shows the dollar character) is stuck into the recovery for an unknown reason. Is there a way to access to phone folders through ADB / shell commands?
I'm a neewbie and I tried to do by myself. Unfortunately I cannot reach my objective.
for example, I (think) I successfully reached the sdcard (is this the android folder name where all the personal data si saved?)
but when I try the command adb pull -p It doesn't work. Here what it happens:
1|[email protected]:/ $ cd sdcard
[email protected]:/sdcard $ adb pull -p
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/sdcard $
Any Idea? Thanks
Click to expand...
Click to collapse
Is there someone who could help me???