I am sure this has been asked before but I cannot find any solutions so I am asking again. I flashed CWM v5.0.2.8 using Odin on my GM2 successfully but I have the following problems:
1. runme.bat from rootme.zip does not work. I get the below:
--- pushing busybox
error: device not found
--- correcting permissions
error: device not found
--- remounting /system
error: device not found
--- copying busybox to /system/x
error: device not found
--- correcting ownership
error: device not found
--- correcting permissions
error: device not found
--- installing busybox
error: device not found
error: device not found
--- pushing SU binary
error: device not found
--- correcting ownership
error: device not found
--- correcting permissions
error: device not found
--- correcting symlinks
error: device not found
error: device not found
--- pushing Superuser app
error: device not found
ALL DONE!!!
Press any key to continue . . .
2. I am in a CWM bootloop now - I cannot boot to OS anymore
3. And the biggest - CWM cannot view mount my int / ext sdcard (tried TWRP, same problem). Fixing permissions doesnt help. Wiping doesnt help as it stops at /sdcard/android.secure
Any help will be appreciated. Thanks.
Related
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!!
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
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...
Hi,
I have some problems with rooting my sensation xl wondering if someone can help. My sensation xl was running on 4.0.3 with sense 3.6. Hboot 1.28. (S-OFF). I successfully unlocked bootloader using htcdev site and then I tried different methods (Doomlord,HTC super tool, TPSparkyroot, OneXKit) to root but I have failed, I think I might be doing something wrong. I get errors related to the file system read/write permissions. e.g. Doomlord give these errors:
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
cannot stat 'files\zergRush': No such file or directory
--- correcting permissions
Unable to chmod /data/local/tmp/zergRush: No such file or directory
--- executing zergRush
/system/bin/sh: ./data/local/tmp/zergRush: not found
--- 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
1976 KB/s (1075144 bytes in 0.531s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
0 KB/s (439 bytes in 1.000s)
df: /data/DxDrm/fuse: Permission denied
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 73% bytes
test: 73%: 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
Also, now when I switch phone to recovery mode (volume down + power), I am not able to factory reset it. When I click on Factory Reset or Recovery, it hangs at HTC logo :crying: Only option to factory reset my phone is to lock the bootloader and unlock it again
Can anybody tell what I am doing wrong?
Any help will be appreciated.
download lexmazters XL tool and use that. perhaps you need to reflash stock rom if everything goes not working.
Thats easy
THATS EASY IF YOU ONLY NEED ROOT.Now DO A NEW FOLDER and extract this CLOCKWORKMODRECOVERY and enable usb debbugging in your phone and run flashrecovery.bat wait untill reboot boot loader and type cwm.So now weve flashed recovery now doanload this SUPER SU(ROOT) and copie it to sd card then go to bootloader and then press on recovery and go in recovery .Now in recovery go down with volume keys to install zip from sd card and press power button then press choose zip from sd card and with volume buttons search the super su file and flash it . THATS THE PERFECT WAY NO GO AND TRY IT GOOOOOOD LUCK :good: :good: :good: :good:
S.a.M.e.R_d said:
THATS EASY IF YOU ONLY NEED ROOT.Now DO A NEW FOLDER
THATS THE PERFECT WAY NO GO AND TRY IT GOOOOOOD LUCK :good: :good: :good: :good:
Click to expand...
Click to collapse
Writting with big letters means that you are yelling. Stop doing that all the time!
I like yelling
Sent from my HTC One X using xda premium
Then you will have to read the rules, it is not allowed
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