Database Develop

Root Failure - 2.3.5 [Sensation XL] 1.24.708.2

I own a Sensation XL and would like to capture logs via QXDM.
Hence would need to enable the diagnostic port.
I have tried to root my Sensation XL and am not successful.
I have read a lot of thread but not seems to work on Sensation XL.
Failures:
1. DooMLoRD_v4_ROOT-zergRush-busybox-su
Error:
-------
--- DEVICE FOUND
--- pushing busybox
706 KB/s (1075144 bytes in 1.486s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
2 KB/s (439 bytes in 0.144s)
df: /mnt/secure/asec: Permission denied
df: /data/DxDrm/fuse: Permission denied
--- Free space on /system : 64% bytes
test: 64%: bad number
--- NOT enough free space on /system!!!
--- making free space by removing Google Maps
rm: can't remove '/system/app/Maps.apk': Read-only file system
--- 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 . . .
2. SuperOneClickv2.3.3-ShortFuse
Error:
-------
Stuck at step # 7
3. Codes
##3424## - Does not work
*#4636#*#* - Cannot enable QXDM dump to SD card.
I doubt if the reason of the in-built storage and no SD card support.
Any help on this is appreciated.
Thanks.
// Aloprpr

That is one of the builds that we have found that cant be rooted at the minute. The only way around it is if you can find an earlier RUU build for your region and flash that, but you will need to relock bootloader first. Remember that it will have to be from your phones region because we can't get s-off yet.

Got it Mate. Thank you.
Let me work on the option you have advised and post the behavior.
Cheers!!

Ned help with this please

i didnt found a solution. i have a problem with the root. i cant root mi galaxy note.
my phone info is....
samsung gt-n7000
gingerbread 2.3.6
kernel 2.6.35.7-n7000vskl1-cl778075
[email protected] #2
compilation gingerbread.vskl1
have the same problem of many ppl here.
---------------------------------------------------------------
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
--- cleaning
--- pushing zergRush"
2251 KB/s (23056 bytes in 0.010s)
--- 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 ! 0x0002e118
[+] 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
2282 KB/s (1075144 bytes in 0.460s)
--- 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 . . .

lfcpato said:
i didnt found a solution. i have a problem with the root. i cant root mi galaxy note.
my phone info is....
samsung gt-n7000
gingerbread 2.3.6
kernel 2.6.35.7-n7000vskl1-cl778075
[email protected] #2
compilation gingerbread.vskl1
have the same problem of many ppl here.
---------------------------------------------------------------
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
--- cleaning
--- pushing zergRush"
2251 KB/s (23056 bytes in 0.010s)
--- 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 ! 0x0002e118
[+] 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
2282 KB/s (1075144 bytes in 0.460s)
--- 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 . . .
Click to expand...
Click to collapse
Flash stock rom kk9 via Odin and use root files kk9 and should be good to go as its a directly root able rom

+1 above
You are on later versions of the ROM which are not directly rootable.

problems with rooting

Im trying to root my galaxy mini 2.3.6 with DooMLoRD_v4_ROOT-zergRush-busybox-su and can't get it work. When I start rooting it shows me this msg:
Code:
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- pushing zergRush
1443 KB/s (23060 bytes in 0.015s)
--- 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
[+] 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
3831 KB/s (1075144 bytes in 0.274s)
--- 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/.lfs: Function not implemented
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 17244 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!!!
Press any key to continue . . .
what's wrong?

first, wrong section
trx it with a update.zip root package via stock recovery to get root.
cause your problem is the firmware u wanr to root!
Sent from my GT-S5660 using xda app-developers app

But my phone have no recovery. I bought it few days ago and I get it with 2.3.6 by default. what to do?

it has one, a stock samsung one,
which makes hlupdate.zip's aviable
Sent from my GT-S5660 using xda app-developers app

There's something noobs don't always understand: THERE IS A ****ING GENERAL SECTION.

how can I get that recovery?
i tried with pressing some buttons but cant get it in

wrong section
press and hold volume up AND home button, while pressing buttons turn the phone on and apply update.zip from menu

Just a reminder, the only things that belong in Development are things that you have created yourself. Not questions. Your thread has been moved.

no problem about topic

[Q] HTC Sensation XL - full unlock

Hey.
I want to change ROM in my XL
I unlocked bootloader by htcdev.com, after that i wanted to root my phone. I made it by runme.bat but cmd showed me this:
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush"
1184 KB/s (23056 bytes in 0.019s)
--- 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.
[-] Not a 2.2/2.3 Android ...
--- 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
2932 KB/s (1075144 bytes in 0.358s)
--- 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/bin/sh: /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, No such file or directory
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!!!
Ok, but i found, how to root my phone by recovery, so i wanted to install recovery. I installed this: r1-recovery-clockwork-5.0.2.7-modaco-runnymede. Next i came to bootloader, chose recovery and nothing. Phone restarted.
What's the problem?
Did i do something wrong?
Do i need s-off to launch recovery?
Please help!

dj_lsd said:
Hey.
I want to change ROM in my XL
I unlocked bootloader by htcdev.com, after that i wanted to root my phone. I made it by runme.bat but cmd showed me this:
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush"
1184 KB/s (23056 bytes in 0.019s)
--- 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.
[-] Not a 2.2/2.3 Android ...
--- 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
2932 KB/s (1075144 bytes in 0.358s)
--- 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/bin/sh: /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, No such file or directory
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!!!
Ok, but i found, how to root my phone by recovery, so i wanted to install recovery. I installed this: r1-recovery-clockwork-5.0.2.7-modaco-runnymede. Next i came to bootloader, chose recovery and nothing. Phone restarted.
What's the problem?
Did i do something wrong?
Do i need s-off to launch recovery?
Please help!
Click to expand...
Click to collapse
Use the tool provided by in the signature to install the right recovery for your hboot, because as far as i can tell, you installed the recovery for 1.25 hboot and if it doesn't work, that means you have 1.28 recovery, make your homeworks before posting this kind of questions because all the inormation you want can be found in stona's guide and in my tool.
Hope this helps

Lexmazter said:
Use the tool provided by in the signature to install the right recovery for your hboot, because as far as i can tell, you installed the recovery for 1.25 hboot and if it doesn't work, that means you have 1.28 recovery, make your homeworks before posting this kind of questions because all the inormation you want can be found in stona's guide and in my tool.
Hope this helps
Click to expand...
Click to collapse
I have hboot 1.28.0006
So which recovery can i install?
I saw your thread with your tool but i don't know how can i use it...

Root Help.

Hello all,
I just acquired a T679 and am having some trouble rooting it.
I have tried ZergRush with no luck
> USB debugging is enabled. So is 'Uknown Sources'
> Here is the output from the ZergRush session
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush"
2814 KB/s (23056 bytes in 0.008s)
--- 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 ! 0x00029118
[+] 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
4929 KB/s (1075144 bytes in 0.213s)
--- 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 . . .
Click to expand...
Click to collapse
Is it currently possible to root this phone?
To make sure we are all on teh same page, here is the About Phone info.
Model: SGH-T679
Android: 2.3.6
Build: GINGERBREAD.UVLE1
Is there an updated ZergRush?

whiteghetto said:
Hello all,
I just acquired a T679 and am having some trouble rooting it.
I have tried ZergRush with no luck
Is it currently possible to root this phone?
To make sure we are all on teh same page, here is the About Phone info.
Model: SGH-T679
Android: 2.3.6
Build: GINGERBREAD.UVLE1
Is there an updated ZergRush?
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
Install a new recovery and then flash Jocala's custom rooted kernel. Zergrush doesn't work on 2.3.6.

use the jocalas mod men
http://forum.xda-developers.com/showpost.php?p=26859796

Thanks a ton guys. This info was very hard to find in a coherant manner. I was able to flash CWM with the stock recovery. Then flashed the 'stock root' ZIP from jocale.
I am not rooted