Develop Bugs

Root your DEFY+ 2.3.6 :)

Just wanted to report that DooMLoRD's easy rooting toolkit works with DEFY+ with Android 2.3.6. Droid 3 root and SuperoneClick failed to root it
Link and steps in this post : http://forum.xda-developers.com/showthread.php?t=1321582

This doesn't work for me. I get lots of errors which suggest that the exploit doesn't work:
Code:
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush"
480 KB/s (23052 bytes in 0.046s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- 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
--- pushing busybox
1562 KB/s (1075144 bytes in 0.671s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
As you say, the Droid 3 and Superoneclick methods don't work, and neither does z4root. I did have a look at the root procedure mentioned in post #1 of this thread but it's beyond my capabilities.
I just got hold of my nearly-new Defy+ this morning and I was looking forward to bringing it up to the same spec as my Defy. Without root, though, there's a lot I can't do (I've actually forgotten a lot of the things I need root for, but at a minimum SetVsel, 2ndinit and I think Clockworkmod recovery all need it ).
The phone says it's system version 45.0.1880.MB526.Retail.en.GB, build number is 4.5.1-134_DFP-188.
Anyone got any suggestions?

ejstubbs said:
This doesn't work for me. I get lots of errors which suggest that the exploit doesn't work:
Code:
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush"
480 KB/s (23052 bytes in 0.046s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- 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
--- pushing busybox
1562 KB/s (1075144 bytes in 0.671s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
As you say, the Droid 3 and Superoneclick methods don't work, and neither does z4root. I did have a look at the root procedure mentioned in post #1 of this thread but it's beyond my capabilities.
I just got hold of my nearly-new Defy+ this morning and I was looking forward to bringing it up to the same spec as my Defy. Without root, though, there's a lot I can't do (I've actually forgotten a lot of the things I need root for, but at a minimum SetVsel, 2ndinit and I think Clockworkmod recovery all need it ).
The phone says it's system version 45.0.1880.MB526.Retail.en.GB, build number is 4.5.1-134_DFP-188.
Anyone got any suggestions?
Click to expand...
Click to collapse
That means its rooted, i got the exact same text when i rooted mine a moment ago

No, it's definitely not rooted: Titanium Backup refuses to run, for example.

Sorry. I didn't read the errors lol. Maybe backup ur Apps and then factory reset.
Sent from my MB526 using XDA App

In fact,no one can root the new Chinese rom

Jades007 said:
Maybe backup ur Apps and then factory reset.
Click to expand...
Click to collapse
Tried factory reset several times, no joy. It's a new phone and I haven't put anything on it yet, still trying to root it. The version of the firmware on this phone seems to be immune to the zergrush exploit.
I've also tried flashing a few of the other 2.3.6 sbfs with no joy - in fact all I have now is a black screen. It's flashable using rsdlite, so not completely bricked, but the end result is always the same - no response to the power button (so no possibility now of doing a factor reset, either).
I'm planning to send it to the Motorola service agent and see what it somes back with.

I've got exactly the same log and problem on my Xperia Arc S. Really impossible to root it?
Code:
---------------------------------------------------------------
Easy rooting toolkit (v4.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 (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] 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
Aby kontynuować, naciśnij dowolny klawisz . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
1876 KB/s (23060 bytes in 0.012s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- 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
--- pushing busybox
2214 KB/s (1075144 bytes in 0.474s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
71 KB/s (439 bytes in 0.006s)
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 186608 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Aby kontynuować, naciśnij dowolny klawisz . . .
Phone Software Version:
1253-8238_4.0.2.A.0.62
Bootloader unlock allowed: Yes

actually i rooted my defy (green lens) with 2.3.6 build like many deceived ones ....
just search for superone click v2.3.2.0.and download it..then dismount ur SD from the device and Enable debugging mode..connect ur device to pc and choose connection to do no thing then open super one click program and press on root bottom..it last for 2 min maximum...

Defy+ 2.3.6 Rooted!
On the 4th attempt rooting my Defy+ 2.3.6 worked! Initially I tried using DoomLoRD's rooting toolkit which said it was successful but didn't install the Superuser app, nor would su work. So then I tried SuperOneClick (v 2.3.2.0). Initially got messages saying the Adb server was out of date and the root failed. Deleted the usb driver package via the sdk and then reinstalled. Tried again - no good. Copied adb.exe, adbwinapi.dll and adbwinusbapi.dll from the sdk directory into Superoneclick adb directory. Tried again - failed. Then removed Droidexplorer (which I'd previously installed). Then reran SuperOneClick and it worked! Gave the same messages as DoomLoRD's kit from the 1st attempt but the Superuser app is there now and works. So thanks (& donation) to Shortfuse and DoomLoRD.

timjaknz said:
On the 4th attempt rooting my Defy+ 2.3.6 worked!
Click to expand...
Click to collapse
That sounds vaguely promising. Can you post the system version, kernel version and build number of your Defy+? I'd like to have some idea of whether it might work for mine, when it comes back from service.

ejstubbs said:
That sounds vaguely promising. Can you post the system version, kernel version and build number of your Defy+? I'd like to have some idea of whether it might work for mine, when it comes back from service.
Click to expand...
Click to collapse
Sure, it's a TelstraClear one (sourced from Oz but using in New Zealand). System version: 45.0.1321.MB526.SLTelstra.en.AU, Kernel version: [email protected] #1, Build: 4.5.1-134_DFP-1321.

I just worked for me too!
Thanks a lot!

{n00bOrgasm}
Mouaahhaa, finally rooted the àç§è(' phone...
In fact you did the job, I just kept sat on ma a...
So I guess you might like to have some details, the phone is a Moto Defy+, none of the well known clicknwatch tools worked for me but yours, I tried doing things myself but had no time enough so tried yours, to see...
Running the script from Ubuntu 11.10
The phone is an MB526
Android 2.3.4
System v. 45.074.MB526.Retail.en.FR
Kernel v. 2.6.32.9-gbad50c3
Build # 4.5.1-134_DFP74
Root verified, updated to last su version, the phone is perfectly fast and operational.
The script didn't returned any error, things were done in a couple seconds, Maps had to be removed, the only interesting thing (or maybe not), it said "All done, you Xperia has been rooted (...)".
Verified, it's definitely a Defy+.
Thank you very much...

Questions about this firmware has been discussed long time :
http://forum.xda-developers.com/showthread.php?t=1472086&page=9
But unfortunately so far no good results

Rooted!
With last version of DooMLord V4 my defy+ mb526 2.3.6 is now rooted thank you man!

I take it Motorola still hasnt released bootloader unlocks for thier devices?

So finally which method works for defy+ 2.3.6?????? plz reply frnds
CM7 2.3.7 QME

Can anyone confirm successfully rooting with DooMLord V4?

flflfl said:
Can anyone confirm successfully rooting with DooMLord V4?
Click to expand...
Click to collapse
It's zergRush. not worked. I'm using 4.5.1-134_DFP-231.

[Q] Problems with rooting.

Hello all
Now I want to get to the point with this but I've been trying to root my arc s but to no avail.
Now I have posted a similar question before but this post is more to the point.
I've tried both of the easiest way but non of them work.
I've attached screen shots of all the errors both ways keep giving me.
If I'm missing something then please tell me because I've spent over 14hrs doing this but with the only result is a loss of my hair.

Rather than root with flashtools why not use the easy root for ics.
Also check you have phone mounted in mtp and debugging selected.
Sent from my LT18i using xda premium

I'm running ics ( the latest version that Sony has released )

zolaisugly said:
Rather than root with flashtools why not use the easy root for ics.
Also check you have phone mounted in mtp and debugging selected.
Sent from my LT18i using xda premium
Click to expand...
Click to collapse
mtp? whats that?

alex ainsley said:
mtp? whats that?
Click to expand...
Click to collapse
It's how your sd card is connected. Not sure if it makes much difference but it might help.
Also is use outside sources is that checked.
When you try the easy root method is your phone switched on?
Can you confirm you are using the correct easy root tool for ics and not gb version, again just making sure
http://forum.xda-developers.com/showthread.php?t=1601038
Use this thread
Sent from my LT18i using xda premium

yes my phone is on and unknown sources is ticked.
I'm using the latest version of easyroot I could find.
also how would I fix the sd thing, take it out or what?

In settings go to Xperia- connectivity- then select the option for mtp.
The reason I am asking this is that this is what my phone was set to, when I rooted using the ics easy root method.
Sent from my LT18i using xda premium

ok I've checked and my phone had map already ticked so it had map on when I was trying too root it.
this is getting stupid, it's like my phone is different or there's something stopping the easy root software from working but I have no clue what it could be.
in all of my time with working with android I've never had a device harder to root then my arc s . but the process is simple enough to follow but it doesn't give me the end result I want.

sorry I ment mtp, dam auto correct.

YES XDXDXDXD My phone is finale rooted, I don't know what I did differently to what I did before but I'm rooted now and that's the first thing .
Onto the next thing .

alex ainsley said:
YES XDXDXDXD My phone is finale rooted, I don't know what I did differently to what I did before but I'm rooted now and that's the first thing .
Onto the next thing .
Click to expand...
Click to collapse
Glad to hear...... With my arc I had to root it twice before it worked.
Sent from my LT18i using xda premium

Help.can't root !
i tried rooting my xperia arc with countless softwares but they all give me the same error . can you guys out there help me? thanks .
(here is a copy of the commandprompt when rooting with zerg rush)
---------------------------------------------------------------
Easy rooting toolkit (v4.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 (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] 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...
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- pushing zergRush
1608 KB/s (23060 bytes in 0.014s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- 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
--- pushing busybox
3069 KB/s (1075144 bytes in 0.342s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
85 KB/s (439 bytes in 0.005s)
export: 135544: bad variable name
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .

sandbuster said:
i tried rooting my xperia arc with countless softwares but they all give me the same error . can you guys out there help me? thanks .
(here is a copy of the commandprompt when rooting with zerg rush)
---------------------------------------------------------------
Easy rooting toolkit (v4.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 (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] 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...
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- pushing zergRush
1608 KB/s (23060 bytes in 0.014s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- 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
--- pushing busybox
3069 KB/s (1075144 bytes in 0.342s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
85 KB/s (439 bytes in 0.005s)
export: 135544: bad variable name
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Click to expand...
Click to collapse
Which firmware are you trying to root mate..?
Sent from my Xperia Pro using XDA

Have enabled the unknown sources and enabled debugging mode..... You must enable these.
Sent from my LT18i using xda premium

now.i.feel said:
Which firmware are you trying to root mate..?
Sent from my Xperia Pro using XDA
Click to expand...
Click to collapse
4.0.1.C.1.21
I have enabled debugging and development. But it still fails to root
Thank for trying to help out guys. I'm glad i switched to android .

If rooting ics you need to use easy root for ics not zergrush.
Look for post in dev section for doomlords post with ics rooting.
Sent from my LT18i using xda premium

[Q] please help ive looked everywhere xperia play

i am trying to root my xperia play 2.3.3 R800A so im trying to downgrade to 2.3.2 but cant find it anywhere and the wotan server isnt much help cause i have to pay them for it i have already bricked my phone once by flashing the wrong firmware from an arc......im not a nob buy i never had to post till now im so stumped.

Don't downgrade. This rooting guide should work with all firmwares up to November 2011. AFAIK 2.3.3 was release long before then so it should work.
http://forum.xda-developers.com/showthread.php?t=1312859

It still dont work I've tried and tried
Sent from my R800at using xda premium

That's really not enough info...
You need to post what you have tried and what happened when you tried it. Along with firmware version etc.
Also, questions should go in Q&A.

ok i have tried version 4 of zergrush and its all good till i get to the scooting
scooting...
149 zerglings...
189 zerglings...
hellions with blue flames!
thats where it fails

exact
---------------------------------------------------------------
Easy rooting toolkit (v4.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 (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] 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
* daemon not running. starting it now *
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
1023 KB/s (23060 bytes in 0.022s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- 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
--- pushing busybox
1779 KB/s (1075144 bytes in 0.590s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
47 KB/s (439 bytes in 0.009s)
export: 135548: bad variable name
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .

Hellions with blue flames does actually mean that the exploit has been patched. You'll need to grab a firmware from here http://forum.xda-developers.com/showpost.php?p=18226603&postcount=2. And flash with flashtool.
I don't know which of those links are still alive and can't check here in work so you may have to find a mirror. But the post says that zergRush works with all these firmwares so once you get one flashed, don't upgrade OTA.

there are none for the r800at (my phone) and i cant find a 2.3.2 version anywhere

And I tried super one click and it does the same as zergrush but could it be that on there page I looked under tested devices and didn't find the xperia play
Sent from my R800at using xda premium

There is a 2.3.3 R800at firmware listed. From the what the poster said, zergRush should work with it.

The links dead and this xperia play is on a fresh 2.3.3 I got off xda
Sent from my R800at using xda premium

As far as I know there are a number of AT&T firmwares on 2.3.3
Some of them work with zergRush and some of them don't.
I found this one on the forums that is dated from November.
http://multiupload.com/B9CI6MH39N
Again, I am unable to check if the link is still up in work but it looks like it's still up.

Dead. ill look around more when I get back up thnx
Sent from my R800at using xda premium

I did hear a few people mentioning that you can flash your R800at phone with R800i FW and everything will work as it should. You just need to wipe everything when flashing.
Please keep in mind that I don't know if this is possible as I don't have an R800at. Maybe someone can confirm this for you. I would definitely get confirmation before trying it

To root, try Unlock root v 2.3.1.... Download it at unlockroot.com. Its very easy, safe and efficient. No need to unlock bootloader. When yu root, all apks and phone data stays intact!
Sent from my Xperia Play R800i.

Hope it helped.
Sent from my Xperia Play R800i.

I tried it but no luck
Sent from my R800at using xda premium

Any new info
Sent from my R800at using xda premium

you can flash R800i firmware on R800a/at
see this and this
emann56 said:
NOTE 2: The Generic UK firmware works worldwide. Doesn't matter what phone you have except for the Verizon model. So if you have an AT&T R800a dev/google conference unit or UK or Rogers or France or any other phone. It will work It will not brick your phone
Click to expand...
Click to collapse

that link isnt working blank page

[Q] i cannot root my Samsung Galaxy W (I8150) using DoomLord v.3 rooting toolkit

---------------------------------------------------------------
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...
* daemon started successfully *
--- cleaning
--- pushing zergRush"
2882 KB/s (23056 bytes in 0.007s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x0002a118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- 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
--- pushing busybox
3054 KB/s (1075144 bytes in 0.343s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .

If you've read the sticky posts in this forum, you should've realized that there is only one method for rooting the W.
-- xda app / Pristine No-Mod CM9b3 / DXKL1 baseband / GT-I8150 --

root methode
pepoluan said:
If you've read the sticky posts in this forum, you should've realized that there is only one method for rooting the W.
-- xda app / Pristine No-Mod CM9b3 / DXKL1 baseband / GT-I8150 --
Click to expand...
Click to collapse
is it Via recovery mode with udapte file .zip... because im stuck, cannot find the file in recovery mode... please help

iriedrum said:
is it Via recovery mode with udapte file .zip... because im stuck, cannot find the file in recovery mode... please help
Click to expand...
Click to collapse
You need CWM or Any other custom recovery first

7amada100 said:
You need CWM or Any other custom recovery first
Click to expand...
Click to collapse
Eh? No need...
Sent from my GT-I8150 using xda app-developers app
---------- Post added at 10:27 AM ---------- Previous post was at 10:24 AM ----------
iriedrum said:
is it Via recovery mode with udapte file .zip... because im stuck, cannot find the file in recovery mode... please help
Click to expand...
Click to collapse
The file *must* be named "update.zip" and it *must* be located in the root directory of the internal SD Card.
Sent from my GT-I8150 using xda app-developers app

[Q] (Linux[xubuntu]) Trying to root, error: mount: permission denied (are you root?)

I'm trying to root my Kindle Fire - my end goal is to get Jellybean running on it. I'm running Xubuntu on my desktop. Here's the process for rooting:
---------------------------------------------------------------
Easy rooting toolkit (v2.0)
created by DooMLoRD
Modified for Kindle Fire for Linux/Mac by Max Lee at RootKindleFire.com
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 (10 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
[*] Before u begin:
(1) enable USB DEBUGGING
from (Menu\Settings\Applications\Development)
(2) enable UNKNOWN SOURCES
from (Menu\Settings\Applications)
(3) [OPTIONAL] increase screen timeout to 10 minutes
(4) connect USB cable to PHONE and then connect 2 computer
---------------------------------------------------------------
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
563 KB/s (23056 bytes in 0.039s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- 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
--- pushing busybox
4395 KB/s (1075144 bytes in 0.238s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'Superuser.apk' to '/system/app/./Superuser.apk': Read-only file system
--- cleaning
--- rebooting
--- WAITING FOR DEVICE
5139 KB/s (3104805 bytes in 0.589s)
Error: Could not access the Package Manager. Is the system running?
All Done, Kindle Fire ROOTED!!!
Check out RootKindleFire.com for more cool hacks!
Click to expand...
Click to collapse
I'm running the command with sudo. The device is recognized as follows:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
5AA6002600000001 device
Click to expand...
Click to collapse
I've tried googling to solve, and either I'm coming up with the wrong terms, or... dunno. Found a ton of pages, but most of it is from a Windows perspective. Found a link to Kindle Fire Utility port for Linux, but link was dead.
I've tried running the above both with the Fire in USB mode and not (i.e. "disconnect").
Any ideas and insight would be quite welcome. I certainly don't mind relevant links to other places, either - I may well have missed relevant resources in my searching.
edit: Also, my adb_usb.ini file did initially contain 0x1949; per some threads I found I added 0x0006, which got my farther along, at least.
subedit: sorry for the delay in this edit, 5min wait time to edit my post. d'oh.

After the device fails like that, have you tried running the root process again immediately?
Sent from my Nexus 7 using Tapatalk

SwoRNLeaDejZ said:
After the device fails like that, have you tried running the root process again immediately?
Click to expand...
Click to collapse
Alas, yes. Have run the attempt around 15-20 times now, several times back to back.

Hmm.. Seems like an error in the script somewhere, are you using a bash file? Do you have access to a windows PC? This is exactly why I dualboot
Sent from my Nexus 7 using Tapatalk

SwoRNLeaDejZ said:
Hmm.. Seems like an error in the script somewhere, are you using a bash file? Do you have access to a windows PC? This is exactly why I dualboot
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm using whatever Xubuntu set up, plus a few aliases that definitely wouldn't interfere...
I've actually just set up a Windows VM in Virtualbox, so my next step will be to try from there. Maybe that'll give me some different errors, if nothing else. hehe

I know that people have been successful using the KFU inside of a VM so you may be good to go
Sent from my Nexus 7 using Tapatalk