Develop Bugs

[Q] rooting EC05 using one click root 2.5.5 hangs

Hi,
I am trying to root EC05 updated epic 4g, using 1 click root and recovery 2.5.5 as explained at http://forum.xda-developers.com/showthread.php?t=770388
The problem which I am facing is that the run.bat is running for quite a long time say like 15 minutes. The console output is
Original one click made by joeykrim and one click installer made by noobnl and f
iron
busybox by skeeterslint
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Copy and run the exploit (may take up to two minutes). Ignore messages about re-
logging in.
If more than five minutes pass, reboot the phone and try again.
5 KB/s (0 bytes in 5392.001s)
2 KB/s (0 bytes in 43.000s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={2662, 2662}
[*] Searching for adb ...
[+] Found adb as PID 5178
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
Wait for phone to reconnect...
Mount system as r/w, cleanup old files, do some basic configuration
299 KB/s (0 bytes in 4793.000s)
Copying files onto phone...
164 KB/s (0 bytes in 26264.000s)
584 KB/s (0 bytes in 196521.000s)
533 KB/s (0 bytes in 486948.000s)
3 KB/s (0 bytes in 479.000s)
Setting permissions...
Installing busybox...
Installing clockworkmod redirector
36 KB/s (0 bytes in 6473.000s)
push: recoveryfiles/recovery -> /system/bin/recoveryfiles/recovery
push: recoveryfiles/postrecoveryboot.sh -> /system/bin/recoveryfiles/postrecover
yboot.sh
push: recoveryfiles/nandroid-md5.sh -> /system/bin/recoveryfiles/nandroid-md5.sh
push: recoveryfiles/fix_permissions -> /system/bin/recoveryfiles/fix_permissions
push: recoveryfiles/adbd -> /system/bin/recoveryfiles/adbd
5 files pushed. 0 files skipped.
1165 KB/s (0 bytes in 895126.000s)
push: recoveryres/images/progress_bar_right_round.png -> /system/bin/recoveryres
/images/progress_bar_right_round.png
push: recoveryres/images/progress_bar_left_round.png -> /system/bin/recoveryres/
images/progress_bar_left_round.png
push: recoveryres/images/progress_bar_fill.png -> /system/bin/recoveryres/images
/progress_bar_fill.png
push: recoveryres/images/progress_bar_empty_right_round.png -> /system/bin/recov
eryres/images/progress_bar_empty_right_round.png
push: recoveryres/images/progress_bar_empty_left_round.png -> /system/bin/recove
ryres/images/progress_bar_empty_left_round.png
push: recoveryres/images/progress_bar_empty.png -> /system/bin/recoveryres/image
s/progress_bar_empty.png
push: recoveryres/images/indeterminate6.png -> /system/bin/recoveryres/images/in
determinate6.png
push: recoveryres/images/indeterminate5.png -> /system/bin/recoveryres/images/in
determinate5.png
push: recoveryres/images/indeterminate4.png -> /system/bin/recoveryres/images/in
determinate4.png
push: recoveryres/images/indeterminate3.png -> /system/bin/recoveryres/images/in
determinate3.png
push: recoveryres/images/indeterminate2.png -> /system/bin/recoveryres/images/in
determinate2.png
push: recoveryres/images/indeterminate1.png -> /system/bin/recoveryres/images/in
determinate1.png
push: recoveryres/images/icon_installing.png -> /system/bin/recoveryres/images/i
con_installing.png
push: recoveryres/images/icon_firmware_install.png -> /system/bin/recoveryres/im
ages/icon_firmware_install.png
push: recoveryres/images/icon_firmware_error.png -> /system/bin/recoveryres/imag
es/icon_firmware_error.png
push: recoveryres/images/icon_error.png -> /system/bin/recoveryres/images/icon_e
rror.png
push: recoveryres/keys -> /system/bin/recoveryres/keys
17 files pushed. 0 files skipped.
305 KB/s (0 bytes in 58705.000s)
Installing clockworkmod recovery...
2452 KB/s (0 bytes in 313888.000s)
I am not sure whether to disconnect the usb cable or not. Can some one please let me know what to do further.
Thanks

"If more than five minutes pass, reboot the phone and try again."
So yeah, pull the cable and reboot. try again.
It usually takes less than a minute total if it goes right. You'll hear windows make a "device unplugged" and reconnect sound.
Then it will start successfully pushing files to your phone. Phone reboots > you're rooted.

Turn off anti virus
wealthcreate said:
Hi,
I am trying to root EC05 updated epic 4g, using 1 click root and recovery 2.5.5 as explained at http://forum.xda-developers.com/showthread.php?t=770388
The problem which I am facing is that the run.bat is running for quite a long time say like 15 minutes. The console output is
Original one click made by joeykrim and one click installer made by noobnl and f
iron
busybox by skeeterslint
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Copy and run the exploit (may take up to two minutes). Ignore messages about re-
logging in.
If more than five minutes pass, reboot the phone and try again.
5 KB/s (0 bytes in 5392.001s)
2 KB/s (0 bytes in 43.000s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={2662, 2662}
[*] Searching for adb ...
[+] Found adb as PID 5178
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
Wait for phone to reconnect...
Mount system as r/w, cleanup old files, do some basic configuration
299 KB/s (0 bytes in 4793.000s)
Copying files onto phone...
164 KB/s (0 bytes in 26264.000s)
584 KB/s (0 bytes in 196521.000s)
533 KB/s (0 bytes in 486948.000s)
3 KB/s (0 bytes in 479.000s)
Setting permissions...
Installing busybox...
Installing clockworkmod redirector
36 KB/s (0 bytes in 6473.000s)
push: recoveryfiles/recovery -> /system/bin/recoveryfiles/recovery
push: recoveryfiles/postrecoveryboot.sh -> /system/bin/recoveryfiles/postrecover
yboot.sh
push: recoveryfiles/nandroid-md5.sh -> /system/bin/recoveryfiles/nandroid-md5.sh
push: recoveryfiles/fix_permissions -> /system/bin/recoveryfiles/fix_permissions
push: recoveryfiles/adbd -> /system/bin/recoveryfiles/adbd
5 files pushed. 0 files skipped.
1165 KB/s (0 bytes in 895126.000s)
push: recoveryres/images/progress_bar_right_round.png -> /system/bin/recoveryres
/images/progress_bar_right_round.png
push: recoveryres/images/progress_bar_left_round.png -> /system/bin/recoveryres/
images/progress_bar_left_round.png
push: recoveryres/images/progress_bar_fill.png -> /system/bin/recoveryres/images
/progress_bar_fill.png
push: recoveryres/images/progress_bar_empty_right_round.png -> /system/bin/recov
eryres/images/progress_bar_empty_right_round.png
push: recoveryres/images/progress_bar_empty_left_round.png -> /system/bin/recove
ryres/images/progress_bar_empty_left_round.png
push: recoveryres/images/progress_bar_empty.png -> /system/bin/recoveryres/image
s/progress_bar_empty.png
push: recoveryres/images/indeterminate6.png -> /system/bin/recoveryres/images/in
determinate6.png
push: recoveryres/images/indeterminate5.png -> /system/bin/recoveryres/images/in
determinate5.png
push: recoveryres/images/indeterminate4.png -> /system/bin/recoveryres/images/in
determinate4.png
push: recoveryres/images/indeterminate3.png -> /system/bin/recoveryres/images/in
determinate3.png
push: recoveryres/images/indeterminate2.png -> /system/bin/recoveryres/images/in
determinate2.png
push: recoveryres/images/indeterminate1.png -> /system/bin/recoveryres/images/in
determinate1.png
push: recoveryres/images/icon_installing.png -> /system/bin/recoveryres/images/i
con_installing.png
push: recoveryres/images/icon_firmware_install.png -> /system/bin/recoveryres/im
ages/icon_firmware_install.png
push: recoveryres/images/icon_firmware_error.png -> /system/bin/recoveryres/imag
es/icon_firmware_error.png
push: recoveryres/images/icon_error.png -> /system/bin/recoveryres/images/icon_e
rror.png
push: recoveryres/keys -> /system/bin/recoveryres/keys
17 files pushed. 0 files skipped.
305 KB/s (0 bytes in 58705.000s)
Installing clockworkmod recovery...
2452 KB/s (0 bytes in 313888.000s)
I am not sure whether to disconnect the usb cable or not. Can some one please let me know what to do further.
Thanks
Click to expand...
Click to collapse
Turn off the av and also try to root in safe mode.
that will disable certain programs from blocking the script from running
just disconnect from the router before you do.
when you reboot try a different usb port also in the rear if possible.

Hi,
I killed the batch file and re ran it. Was afraid whether it would brick the phone. Anyways, ran the script again and this time it succeeded.
Thanks for the help.

Last time I used one click root asphalt 5 demo went missing along with other system files. Did you lose any system file apps?
Sent from my SPH-D700 using XDA App

manaup said:
Last time I used one click root asphalt 5 demo went missing along with other system files. Did you lose any system file apps?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
The newest version removes asphalt demo and free hd demo. You can edit the batch file to remove those two lines if you don't want this. But I prefer to let our remove it and have them backed up in case I need them.
Sent from my SPH-D700 using XDA Premium App

Yes, I lost those apps.

I wasn't able to update from eb13 to ec05, I think it's because I lost the system files. So I had to odin back to di18 and then was able to update to ec05. How do you root with out losing the system apps?
Sent from my SPH-D700 using XDA App

manaup said:
I wasn't able to update from eb13 to ec05, I think it's because I lost the system files. So I had to odin back to di18 and then was able to update to ec05. How do you root with out losing the system apps?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Unfortunately the rooting process requires more space on your phones memory than is left by stock OS so it deletes those apps to make room. You can find them floating around to restore after rooting process is done.
BONSAI 4 and loving it!

Ok. Thanks!
Sent from my SPH-D700 using XDA App

Any way to unroot and remove cwm in ec05 without odin or rom reset?

ErlyD said:
Any way to unroot and remove cwm in ec05 without odin or rom reset?
Click to expand...
Click to collapse
Doesn't one click have an unroot file? On my phone now so can't check until I get home.
Do you BONSAI?

ErlyD said:
Any way to unroot and remove cwm in ec05 without odin or rom reset?
Click to expand...
Click to collapse
OK found this for you with Google:
I have never used this so....if something happens then you will have to Odin.

Problem Rooting?

One Click Root & CWM 3.0.2.5 for the Epic 4G
Updated and tweaked by Rodderik and DRockstar 5/10/2011
Original one click by joeykrim and one click installer by noobnl and firon
busybox by skeeterslint
Huge credits go out to:
koush - dual fs recovery binary
DRockstar - recovery kernel build
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Mount system as r/w, cleanup old files, do some basic configuration
88 KB/s (4793 bytes in 0.053s)
Copying files onto phone...
288 KB/s (26264 bytes in 0.089s)
668 KB/s (196521 bytes in 0.287s)
failed to copy 'busybox' to '/system/xbin/busybox': No space left on device
18 KB/s (327 bytes in 0.017s)
Setting permissions...
Unable to chmod /system/xbin/busybox: No such file or directory
Installing busybox...
/system/xbin/busybox: not found
Installing clockworkmod redirector
33 KB/s (6535 bytes in 0.193s)
push: recoveryfiles/etc/recovery.fstab -> /system/bin/recoveryfiles/etc/recovery
.fstab
push: recoveryfiles/umountums -> /system/bin/recoveryfiles/umountums
push: recoveryfiles/tune2fs -> /system/bin/recoveryfiles/tune2fs
push: recoveryfiles/sdparted -> /system/bin/recoveryfiles/sdparted
push: recoveryfiles/recovery_wrapper -> /system/bin/recoveryfiles/recovery_wrapp
er
push: recoveryfiles/recovery -> /system/bin/recoveryfiles/recovery
failed to copy 'recoveryfiles/recovery' to '/system/bin/recoveryfiles/recovery':
No space left on device
push: recoveryfiles/etc/recovery.fstab -> /system/bin/recoveryfiles/etc/recovery
.fstab
1 file pushed. 0 files skipped.
19 KB/s (515 bytes in 0.026s)
push: recoveryres/images/progress_fill.png -> /system/bin/recoveryres/images/pro
gress_fill.png
push: recoveryres/images/progress_empty.png -> /system/bin/recoveryres/images/pr
ogress_empty.png
push: recoveryres/images/progress_bar_right_round.png -> /system/bin/recoveryres
/images/progress_bar_right_round.png
push: recoveryres/images/progress_bar_left_round.png -> /system/bin/recoveryres/
images/progress_bar_left_round.png
push: recoveryres/images/progress_bar_fill.png -> /system/bin/recoveryres/images
/progress_bar_fill.png
push: recoveryres/images/progress_bar_empty_right_round.png -> /system/bin/recov
eryres/images/progress_bar_empty_right_round.png
push: recoveryres/images/progress_bar_empty_left_round.png -> /system/bin/recove
ryres/images/progress_bar_empty_left_round.png
push: recoveryres/images/progress_bar_empty.png -> /system/bin/recoveryres/image
s/progress_bar_empty.png
push: recoveryres/images/indeterminate6.png -> /system/bin/recoveryres/images/in
determinate6.png
push: recoveryres/images/indeterminate5.png -> /system/bin/recoveryres/images/in
determinate5.png
push: recoveryres/images/indeterminate4.png -> /system/bin/recoveryres/images/in
determinate4.png
push: recoveryres/images/indeterminate3.png -> /system/bin/recoveryres/images/in
determinate3.png
push: recoveryres/images/indeterminate2.png -> /system/bin/recoveryres/images/in
determinate2.png
push: recoveryres/images/indeterminate1.png -> /system/bin/recoveryres/images/in
determinate1.png
push: recoveryres/images/icon_installing.png -> /system/bin/recoveryres/images/i
con_installing.png
push: recoveryres/images/icon_firmware_install.png -> /system/bin/recoveryres/im
ages/icon_firmware_install.png
push: recoveryres/images/icon_firmware_error.png -> /system/bin/recoveryres/imag
es/icon_firmware_error.png
push: recoveryres/images/icon_error.png -> /system/bin/recoveryres/images/icon_e
rror.png
push: recoveryres/images/icon_clockwork.png -> /system/bin/recoveryres/images/ic
on_clockwork.png
push: recoveryres/keys -> /system/bin/recoveryres/keys
20 files pushed. 0 files skipped.
114 KB/s (81069 bytes in 0.690s)
busybox: not found
busybox: not found
Installing clockworkmod recovery...
333 KB/s (66884 bytes in 0.196s)
862 KB/s (5478824 bytes in 6.201s)
Cleaning up files...
All done!
If your phone did not reboot or root does not
work correctly. Please rerun the script.
Press any key to exit the script.
Press any key to continue . . .

Whats the problem?
Did superuser not get loaded? Can you not boot into recovery? Do you not have root access?
Have you re run it if you dont have root? Sometimes it takes a couple times. Try a different port or cable?
but first whats the problem lol

It looks like the new 3.0.2.5 forgot to delete Asphalt to make enough room to root. Go into settings>applications>manage applications>all and go to every app you have and see which ones you can move to sd card and do it. If you still get an insufficient space error, use CWM 2.5.5.

kennyglass123 said:
It looks like the new 3.0.2.5 forgot to delete Asphalt to make enough room to root. Go into settings>applications>manage applications>all and go to every app you have and see which ones you can move to sd card and do it. If you still get an insufficient space error, use CWM 2.5.5.
Click to expand...
Click to collapse
Good catch lol, never seen busybox so never paid attention to that part lol

Can no longer 'adb shell' PLS help!!

Since I have S-Off'ed my Desire, I can no longer use adb shell commands :-(
With my phone in recovery mode, I use the pushfiles' recovery mode batch which has the following code:
Code:
TITLE HTC Desire Recovery Mode
@ECHO OFF
CLS
adb kill-server
adb wait-for-device
adb start-server
adb push files /
adb shell busybox --install /sbin
adb shell recovery &
now this used to work perfectly, after this I could use the adb shell mount /system & adb shell ls /system/app/ perfectly, which meant I could also push & pull files to and from my desire, but now I cant, when I try i get the following on-screen:
Code:
D:\Backup\MobUtils\HTC_Desire\pushfiles>adb push files /
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
push: files/etc/mtab -> /etc/mtab
push: files/etc/fstab -> /etc/fstab
push: files/sbin/wipe -> /sbin/wipe
push: files/sbin/unyaffs -> /sbin/unyaffs
push: files/sbin/ums_toggle -> /sbin/ums_toggle
push: files/sbin/um -> /sbin/um
push: files/sbin/tune2fs -> /sbin/tune2fs
push: files/sbin/toolbox -> /sbin/toolbox
push: files/sbin/sdparted -> /sbin/sdparted
push: files/sbin/recovery -> /sbin/recovery
push: files/sbin/reboot -> /sbin/reboot
push: files/sbin/parted -> /sbin/parted
push: files/sbin/nandroid-mobile.sh -> /sbin/nandroid-mobile.sh
push: files/sbin/mkyaffs2image -> /sbin/mkyaffs2image
push: files/sbin/mke2fs -> /sbin/mke2fs
push: files/sbin/log2sd -> /sbin/log2sd
push: files/sbin/fs -> /sbin/fs
push: files/sbin/flash_image -> /sbin/flash_image
push: files/sbin/fix_permissions -> /sbin/fix_permissions
push: files/sbin/e2fsck -> /sbin/e2fsck
push: files/sbin/dump_image -> /sbin/dump_image
push: files/sbin/busybox -> /sbin/busybox
push: files/sbin/backuptool.sh -> /sbin/backuptool.sh
push: files/sbin/adbd -> /sbin/adbd
push: files/system/bin/sh -> /system/bin/sh
push: files/system/bin/linker -> /system/bin/linker
push: files/system/lib/libstdc++.so -> /system/lib/libstdc++.so
push: files/system/lib/libm.so -> /system/lib/libm.so
push: files/system/lib/liblog.so -> /system/lib/liblog.so
push: files/system/lib/libcutils.so -> /system/lib/libcutils.so
push: files/system/lib/libc.so -> /system/lib/libc.so
31 files pushed. 0 files skipped.
1326 KB/s (4719589 bytes in 3.474s)
D:\Backup\MobUtils\HTC_Desire\pushfiles>adb shell busybox --install /sbin
- exec '/sbin/sh' failed: Permission denied (13) -
D:\Backup\MobUtils\HTC_Desire\pushfiles>adb shell recovery &
- exec '/sbin/sh' failed: Permission denied (13) -
D:\Backup\MobUtils\HTC_Desire\pushfiles>
I have even tried using 'adb remount' but the following happens:
Code:
D:\Backup\MobUtils\HTC_Desire\pushfiles>adb remount
remount failed: Unknown error: 0
WHAT is causing this, and most importantly, how do I fix it so I can continue to push & pull files to and from my desire? I have a few files I need to remove & add, but without this feature, I cant and am at a loss!
I have even tried to run the commands when the phone is in fastboot mode, but this still wont work :-(
All the drivers on my PC are upto date and nothing else has changed since I done this last!
Thanks in advance & I hope for replies how to fix this real soon!
Arty.

try this http://androidcommander.com/

did you try mounting /system under mounts and storage from the recovery? and after that "adb remount" or "adb shell mount / -o rw,remount" ?

[Q] CWM install issues

I know this isn't the correct place to put this, but since I am a new user it wouldn't let me ask the question in the thread it took place in. I was trying to install CWM on my new phone which is running EL29. I followed the instructions here for options C and also watched the video by QBKing77:
http://forum.xda-developers.com/showthread.php?t=1342728
When I get to the part where i select L (Install BootImg EL29+CWM-rogue), I hit enter and it says "install-el29-cwm-rogue.bat' is not recognized as an internal or external command, operation program batch.
What am I doing wrong?

have you rebooted and tried again. Also did you root your phone with his method

My first question is, did you place the folder on the root of your c drive? (As in open my computer, click on C, then place the folder there)
Sent from my SPH-D710 using XDA App

I did root it already with his directions. But, I did not stick the folder on the root directory. I didn't see where he said to do that. In the video he put it on his desktop.

Just place it there n try its in the printed instructions, but its all good
Sent from my SPH-D710 using XDA App

Odom, thanks that worked like a charm.

Its all good man

Oh holy crap, I'm an idiot. I was booting the wrong way. Excellent, my first post is a fail.
Sorry to bump an old thread, but I'm having the same issue. I have the egtauto folder in C:\ root, my phone is running rooted el29, and the process appears to complete fine, but everytime I try to boot into the bootloader (vol dn+pwr), it goes to the ODIN screen. Log follows:
BOOTIMGNAME = EL29+CWM-Rogue
BOOTIMGFILE1 = zImage-el29
BOOTIMGFILE2 = zImage-el29-cwm-rogue
BOOTIMGSTKREC = no
BOOTIMGSCRIPT = install-boot-el29-cwm-rogue.sh
...Proceeding to copy necessary files...
push: copy2sd/000root/Superuser.apk -> /sdcard/000root/Superuser.apk
push: copy2sd/000root/su -> /sdcard/000root/su
push: copy2sd/000root/install-unroot.sh -> /sdcard/000root/install-unroot.sh
push: copy2sd/000root/install-root.sh -> /sdcard/000root/install-root.sh
push: copy2sd/000root/install-otachk.sh -> /sdcard/000root/install-otachk.sh
push: copy2sd/000root/install-otachk-ek02-el29.list -> /sdcard/000root/install-otachk-ek02-el29.list
push: copy2sd/000root/install-otachk-eg30-ek02.list -> /sdcard/000root/install-otachk-eg30-ek02.list
push: copy2sd/000root/install-cleanup.sh -> /sdcard/000root/install-cleanup.sh
push: copy2sd/000root/install-ciq-on.sh -> /sdcard/000root/install-ciq-on.sh
push: copy2sd/000root/install-ciq-off.sh -> /sdcard/000root/install-ciq-off.sh
push: copy2sd/000root/install-boot-zImage.sh -> /sdcard/000root/install-boot-zImage.sh
push: copy2sd/000root/install-boot-fc07.sh -> /sdcard/000root/install-boot-fc07.sh
push: copy2sd/000root/install-boot-fc07-cwm-rogue.sh -> /sdcard/000root/install-boot-fc07-cwm-rogue.sh
push: copy2sd/000root/install-boot-fc06.sh -> /sdcard/000root/install-boot-fc06.sh
push: copy2sd/000root/install-boot-fc06-cwm-rogue.sh -> /sdcard/000root/install-boot-fc06-cwm-rogue.sh
push: copy2sd/000root/install-boot-fc05.sh -> /sdcard/000root/install-boot-fc05.sh
push: copy2sd/000root/install-boot-fb27.sh -> /sdcard/000root/install-boot-fb27.sh
push: copy2sd/000root/install-boot-fb27-cwm-rogue.sh -> /sdcard/000root/install-boot-fb27-cwm-rogue.sh
push: copy2sd/000root/install-boot-fb21.sh -> /sdcard/000root/install-boot-fb21.sh
push: copy2sd/000root/install-boot-fb21-cwm-rogue.sh -> /sdcard/000root/install-boot-fb21-cwm-rogue.sh
push: copy2sd/000root/install-boot-fb17.sh -> /sdcard/000root/install-boot-fb17.sh
push: copy2sd/000root/install-boot-fb17-cwm-rogue.sh -> /sdcard/000root/install-boot-fb17-cwm-rogue.sh
push: copy2sd/000root/install-boot-fb15.sh -> /sdcard/000root/install-boot-fb15.sh
push: copy2sd/000root/install-boot-fb15-cwm-rogue.sh -> /sdcard/000root/install-boot-fb15-cwm-rogue.sh
push: copy2sd/000root/install-boot-el29.sh -> /sdcard/000root/install-boot-el29.sh
push: copy2sd/000root/install-boot-el29-cwm-rogue.sh -> /sdcard/000root/install-boot-el29-cwm-rogue.sh
push: copy2sd/000root/install-boot-el26.sh -> /sdcard/000root/install-boot-el26.sh
push: copy2sd/000root/install-boot-el26-cwm.sh -> /sdcard/000root/install-boot-el26-cwm.sh
push: copy2sd/000root/install-boot-el26-cwm-rogue.sh -> /sdcard/000root/install-boot-el26-cwm-rogue.sh
push: copy2sd/000root/install-boot-el13.sh -> /sdcard/000root/install-boot-el13.sh
push: copy2sd/000root/install-boot-el13-cwm.sh -> /sdcard/000root/install-boot-el13-cwm.sh
push: copy2sd/000root/install-boot-ek02.sh -> /sdcard/000root/install-boot-ek02.sh
push: copy2sd/000root/install-boot-ek02-cwm.sh -> /sdcard/000root/install-boot-ek02-cwm.sh
push: copy2sd/000root/install-boot-eg31.sh -> /sdcard/000root/install-boot-eg31.sh
push: copy2sd/000root/install-boot-eg31-cwm.sh -> /sdcard/000root/install-boot-eg31-cwm.sh
push: copy2sd/000root/install-boot-eg30.sh -> /sdcard/000root/install-boot-eg30.sh
push: copy2sd/000root/install-boot-eg30-cwm.sh -> /sdcard/000root/install-boot-eg30-cwm.sh
push: copy2sd/000root/install-boot-common.sh -> /sdcard/000root/install-boot-common.sh
push: copy2sd/000root/func.inc.sh -> /sdcard/000root/func.inc.sh
push: copy2sd/000root/busybox -> /sdcard/000root/busybox
40 files pushed. 0 files skipped.
1476 KB/s (2957938 bytes in 1.956s)
push: copy2sd-img/000root/zImage-el29 /sdcard/000root/zImage-el29
4347 KB/s (8387840 bytes in 1.884s)
push: copy2sd-img/000root/zImage-el29-cwm-rogue /sdcard/000root/zImage-el29-cwm-rogue
3895 KB/s (8387840 bytes in 2.103s)
----
Installing BootImg - EL29+CWM-Rogue... Done
----
BootImg = zImage-el29-cwm-rogue
STATUS1 = 32765+0 records in 32765+0 records out 8387840 bytes transferred in 2.901 secs (2891361 bytes/sec)
STATUS2 = 32765+0 records in 32765+0 records out 8387840 bytes transferred in 2.108 secs (3979051 bytes/sec)
----
Waiting for filesystem to sync... Done

Yeah its pwr + vol+
Sent from my SPH-D710 using XDA

pjku79 said:
I know this isn't the correct place to put this, but since I am a new user it wouldn't let me ask the question in the thread it took place in. I was trying to install CWM on my new phone which is running EL29. I followed the instructions here for options C and also watched the video by QBKing77:
http://forum.xda-developers.com/showthread.php?t=1342728
When I get to the part where i select L (Install BootImg EL29+CWM-rogue), I hit enter and it says "install-el29-cwm-rogue.bat' is not recognized as an internal or external command, operation program batch.
What am I doing wrong?
Click to expand...
Click to collapse
I'm basically having the same issue. I just rooted my GSII Epic 4g just fine based on the video from qbking77 and info on this forum posted by sfhub but I cannot get CWM to go on successfully. I've followed all directions per the video and posts as well as searched the forum for an answer to no luck. I am running EL29 and selected the EL29 + CWM Rouge option L but the e4gauto doesn't seem to be pushing the files to my phone. Goes back to main option screen when done and does not reboot phone.
It never asks for SU permission, PIN and Anti-Virus are disabled. e4gauto is in my root C: folder. Tried restarting the phone and computer multiple times. What am I doing wrong here?
Thanks much!

ok. I have my e4gt flagged to page plus now..... So I have cwm folder on phone, I got it rooted, totally new to Samsung.... Came from Motorola with locked bootloaders.... Can I put cwm and el29 rouge Kernal on it? .... Without having to reflash, having restore all data..... Can everything be restored safely?
Sent from my SPH-D710 using xda app-developers app

Please follow the install instructions in the cm9 development blog.. linked from either the cm9 discussion thread in general, or the cm9 development thread..
You can very easily permanently brick these phones due to a firmware bug, so its important to follow the instructions...
Sent from my SPH-D700 using xda app-developers app

[Q] Can't get tablet rooted

Bought an A100 off Ebay and donated a battery to it. Tried several ways (like ADB method and Terminal Emulator) and many times to root, but no go.
The ROM is Acer_AV041_A100_1.015.00_PA_CUS1
The results with Terminal Emulator working with root.sh in /mnt/sdcard are:
/system/xbin/su: No such file or directory
When I type in the commands for ADB:
adb shell /system/bin/cmdclient ec_micswitch ‘`mount -o remount,rw /system`’
adb shell /system/bin/cmdclient ec_micswitch ‘`cat /mnt/sdcard/su >/system/xbin/su`’
adb shell /system/bin/cmdclient ec_micswitch ‘`chmod 6755 /system/xbin/su`’
I get no response in the command window. I then go to Superuser, and the info menu says "su binary not found"
ADB and Fastboot seem to work OK. It returns the device number 20710676216.
adb shell cat /proc/partitions shows nine partitions
It looks like a permissions problem, but I don't know what to do next.
Who can help me figure this out?

http://forum.xda-developers.com/showthread.php?p=23285307 have you tried this?
Alao is that ICS or HC I can't ever remember by the stock firmware title?
Sent from my SCH-R760X using xda app-developers app

Working on it
chicinwang said:
http://forum.xda-developers.com/showthread.php?p=23285307 have you tried this?
Alao is that ICS or HC I can't ever remember by the stock firmware title?
Sent from my SCH-R760X using xda app-developers app
Click to expand...
Click to collapse
It is ICS. Yes, I tried the simple method earlier, but got error about no mempodroid.
I just added the precompiled version to the subfolder 'tools' and got past that error.
Now, when I run runit-win.bat, it successfully passes the preparation stage, says executing the main script, then remote object /system/bin/su doesn't exist... file su isn't created... not getting root! Error
By the way, PS#2 of the simple method says: Command "Mount ro/rw" for directory /system (partition) - works perfectly!
Is that a command I have to execute in ADB for the simple method to work at all?

One of the Droid razor maxx easy root works.
Sent from my Nexus 4

Got it fixed
myturbo1 said:
One of the Droid razor maxx easy root works.
Sent from my Nexus 4
Click to expand...
Click to collapse
Thanks for the reply. I got it fixed by reverting to HC, rooting, custom recovery, and then flashing Kebbersrom Shellshock.

WVHdls1 said:
Thanks for the reply. I got it fixed by reverting to HC, rooting, custom recovery, and then flashing Kebbersrom Shellshock.
Click to expand...
Click to collapse
How do you get back to HC?
Where can i find the HC stock file?
Can you post (link/file) please?
I have the same problem to root my a100 with ics stock :silly: .

frischeis said:
How do you get back to HC?
Where can i find the HC stock file?
Can you post (link/file) please?
I have the same problem to root my a100 with ics stock :silly: .
Click to expand...
Click to collapse
Are you using the easy root method?
Sent from my Nexus 4 using xda premium

myturbo1 said:
Are you using the easy root method?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yes of course:
When i want to root my device i get this message:
Device connected. Preparation for executing of the main script.
push: tools/su -> /data/local/tmp/su
push: tools/runit.sh -> /data/local/tmp/runit.sh
push: tools/mount.sh -> /data/local/tmp/mount.sh
push: tools/getroot.sh -> /data/local/tmp/getroot.sh
push: tools/delroot.sh -> /data/local/tmp/delroot.sh
push: tools/busybox.sh -> /data/local/tmp/busybox.sh
push: tools/busybox -> /data/local/tmp/busybox
7 files pushed. 0 files skipped.
1452 KB/s (803082 bytes in 0.540s)
Unable to chmod /data/local/tmp/mempodroid: No such file or directory
remote object '/data/local/tmp/mempodroid' does not exist
The file "mempodroid" isn't created!
-
Not getting root!
-
Error!
What is wrong and what can i do?
I have ICS stock rom 4.0.3.

frischeis said:
Yes of course:
When i want to root my device i get this message:
Device connected. Preparation for executing of the main script.
push: tools/su -> /data/local/tmp/su
push: tools/runit.sh -> /data/local/tmp/runit.sh
push: tools/mount.sh -> /data/local/tmp/mount.sh
push: tools/getroot.sh -> /data/local/tmp/getroot.sh
push: tools/delroot.sh -> /data/local/tmp/delroot.sh
push: tools/busybox.sh -> /data/local/tmp/busybox.sh
push: tools/busybox -> /data/local/tmp/busybox
7 files pushed. 0 files skipped.
1452 KB/s (803082 bytes in 0.540s)
Unable to chmod /data/local/tmp/mempodroid: No such file or directory
remote object '/data/local/tmp/mempodroid' does not exist
The file "mempodroid" isn't created!
-
Not getting root!
-
Error!
What is wrong and what can i do?
I have ICS stock rom 4.0.3.
Click to expand...
Click to collapse
From that log it never pushed what its trying to run, may need to push it manually then run the script again.
Tapatalked from my HTC DNA - PAC v22.1.1

frischeis said:
How do you get back to HC?
Where can i find the HC stock file?
Can you post (link/file) please?
I have the same problem to root my a100 with ics stock :silly: .
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=33859034&postcount=20

pio_masaki said:
From that log it never pushed what its trying to run, may need to push it manually then run the script again.
Tapatalked from my HTC DNA - PAC v22.1.1
Click to expand...
Click to collapse
Can you tell me how get it manually rootet please?
Would be very nice and it is my last chance....to root.

Open the script that you run. I did mine in Linux, and I needs root to run, so maybe try running as admin? You can copy and paste the commands from the script into the command prompt once your into your adb directory.
So
Adb push blahblah /blah/blah/blah
Kinda like that pretty simple. Good luck!
Sent from my SPH-L710 using xda app-developers app

I try it on a other pc to root the device with easy root method from ZeroNull :
http://forum.xda-developers.com/showthread.php?t=1531646
So now i have root and works like charm!!!!!!!!!!!!!!
Thanks guys :good: !!