Database Develop

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.

phone will not root after software update

my droid 3 was previously rooted with no problem. i had the liberty rom on it, with safestrap, after a software update forced itself onto my phone, it pushed my phone between the root and unroot process. like it was trying to flash the stock rom back onto the phone and ended up with a mix of both. i was stuck in a setup screen and the only way to get my phone back to use was to factory reset my phone.
well now after the software update and all of that mess my phone will not root again! ive tried motofail and petestoolkit and neither worked. it told me it could not push the su, super user and busybox files onto it. it was able to edit local.prop. weird i just need a way to root my phone again, im guessing its the software update that is blocking it. it was update 5.5.1_84_d3g-66_m2-10
anyone know another method of root that my phone will allow? id think since its kind of an old phone there might be a solution :/
please and thank you

Tl;Dr but try zergrush
Sent from my GT-P5113 using xda premium

I just installed the .906 update and used MotoFail to root after the update. Worked fine.
Got it here --> vulnfactory.org/blog/2012/02/11/rooting-the-droid-4-a-failed-bounty-experiment

i tried zergrush and it did not work this is what happened
---------------------------------------------------------------
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
* daemon not running. starting it now *
* daemon started successfully *
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush"
2881 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 ! 0x00016118
[*] 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
4757 KB/s (1075144 bytes in 0.220s)
--- 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 . . .

Flash sbf, then reroot
Sent from my XT860 using xda app-developers app

go to my thread and download the 1click sbf. exe
follow the directions and sbf your device
once done download motofail also found in my thread
run it and follow the directions

[Q] Help !

Hey guys.
Well i was going to root my phone and i unlocked the bootloader..
And i was going to root but when i opens the root toolkit and press a key i gets this
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Trykk en tast for å fortsette...
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
2251 KB/s (23060 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.
[-] 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
4999 KB/s (1075144 bytes in 0.210s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
85 KB/s (439 bytes in 0.005s)
df: /data/DxDrm/fuse: Permission denied
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 70% bytes
test: 70%: bad number
--- NOT enough free space on /system!!!
--- making free space by removing Google Maps
--- 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!!!
Can someone please tell me what i have to there ???:laugh:

Did you activate debug mode?
Inviato dal mio HTC Sensation XL with Beats Audio X315e con Tapatalk 2

ParadiseCity said:
Did you activate debug mode?
Inviato dal mio HTC Sensation XL with Beats Audio X315e con Tapatalk 2
Click to expand...
Click to collapse
Yes, i did,

Well, you need to check the right ROOT method for you, if this one does not work for you, this one will surely work, check the thread.
Hope this helps

Hey, you know what i used the supersu root method, and i installed it, and everything, i got ROM manager,supersu app and even i installed i custom rom on my phone, but when i try to use those apps my phone says that i dont have root? How cant i have root when i have custom rom, CWM and all the apps ??????
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app

OmarKhatujev said:
Hey, you know what i used the supersu root method, and i installed it, and everything, i got ROM manager,supersu app and even i installed i custom rom on my phone, but when i try to use those apps my phone says that i dont have root? How cant i have root when i have custom rom, CWM and all the apps ??????
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Click to expand...
Click to collapse
Don't know for sure, you can:
-ReRoot.
-Remove and add the app again from market.
I had problems with Total Commander and Ghost Commander with root when i restored them using a backup app when i moved to a new ROM.
Hope this helps

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

Can't root on 2.3.6

Hi to all
I have this nexus one as a second phone, I always root it, but after it goes to the customer care, it was bring to me with Android 2.3.6
now I can't root I've tried with super one click and with Doomlord toolkit and nothing happend
this is what i have:
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
Premere un tasto per continuare . . .
--- 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
cannot open 'files\zergRush': No such file or directory
--- correcting permissions
--- executing zergRush
--- 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
1024 KB/s (1075144 bytes in 1.025s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
32 KB/s (439 bytes in 0.013s)
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 19128 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!!!
Premere un tasto per continuare . . .
I've installed google usb driver from the adb package... all done on w7
I don't know what to do...I really need rooting for the memory problem...it's really low...
thanks a lot in advance

Xda wiki nexus one
But really did you do
fastboot oem unlock
Then flash custom recovery
Sent from my Nexus 7 using xda premium

demkantor said:
Xda wiki nexus one
But really did you do
fastboot oem unlock
Then flash custom recovery
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
fastboot oem unlock means that I have to unlock bootloader? I don't want to beacuse the power button is in warranty, so I'd like to root and stay with stock!

try www.unlockroot.com
Sent from my Nexus One using Tapatalk