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] After recovery screen just anything

Hi All!
I tried do root my phone but i have a problem. i follow this thread
http://forum.xda-developers.com/showthread.php?t=696189
i did old style root operation. After i run step1 everything was okey, and then i go on for second step with that command. but after that i got the following
"nohup: appending output to nohup.out" .
When i enter the recovery screen just nothing, black screen. What can i do? how can i succed. Please i need help. My phone is s-off.
C:\erim\r5-desire-root-alt>step2-windows.bat
Desire Root Step 2
Pushing required files to device...
* 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.
1396 KB/s (3709881 bytes in 2.593s)
Pushing update file to device sdcard - this may take a few minutes...
1223 KB/s (126445058 bytes in 100.891s)
Now wipe and apply rootedupdate.zip from the recovery image menu.
nohup: appending output to nohup.out

Please use the Q&A Forum for questions Thanks
Moving to Q&A

hi as you s-off did you try flash recovery via fastboot?
fastboot flash recovery "your recovery image name"

i dont have recovery image file ? Which file i should use ? can you share a link with me ?

see my signature

i tried to type fastboot but fail. "fastboot couldnt find". Where is fastboot? in which step i can command fastboot ?
i download "fastboot" but i couldnt succed again. i got this exception "fastboot: access denied"

sorry, I expected you have it... see attached or use fastboot commander from here

i get the "access is denied"? how can i pass this exception ?

can you post me info from fastboot screen please

http://postimage.org/image/vn5ah3t9j this is my fastboot screen.
image :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Sorry I have shoot off to work, try unrevoked and flash recovery with it
Sent from my HTC Sensation XL with Beats Audio X315e using XDA Premium App

i can enter recovery menu now. And also i follow the instructions again. Wipe data/factory and then install zip from sdcard. And i succed but my phone hasnt open.After reboot I can see a just white screen and htc logo. what should i do ? what is my problem ?

And Dalvik wiped?
Or do full wipe and flash rom as you like
Sent from my HTC Sensation XL with Beats Audio X315e using XDA Premium App

am i need or not? i just usefirst option. Wipe All data/factory reset. If i need i can. Then what will i do ?

You have to do it as you changed system files... What do you want to do next?
Sent from my HTC Sensation XL with Beats Audio X315e using XDA Premium App

first i want to open my phone. Then i want to install a custom rom.

As you have recovery just download your next rom, wipe and install
Sent from my HTC Sensation XL with Beats Audio X315e using XDA Premium App

kotag82 said:
You have to do it as you changed system files... What do you want to do next?
Sent from my HTC Sensation XL with Beats Audio X315e using XDA Premium App
Click to expand...
Click to collapse
I wiped Dalvik. And install .zip again but same result. i have black screen and both side have white lines.

Can you boot to recovery or fastboot
Sent from my HTC Sensation XL with Beats Audio X315e using XDA Premium App

kotag82 said:
Can you boot to recovery or fastboot
Sent from my HTC Sensation XL with Beats Audio X315e using XDA Premium App
Click to expand...
Click to collapse
yes. I think i need a suitable rom for me. Can you suggest me ? I have already downloaded this one RunnymedeMod007 from here http://acesmod.viperts.info/RunnymedeMod007/v14/RunnymedeMod007_v14_c-CM7-STOCK.zip but i dont know it is suitable or not.

Mod please delete thread thanks

I'm totallt stock 2.3.6 EK02. I'm ready to risk rooting, but I have no idea what to do. There's 5 dozen methods, modems, kernels, basebands etc. Coming from HTC and unrevoked it's a lot to swallow with odin. So i gues i kind of need a step by step to 1st get root
2nd a back up of my stock ek02,
3rd update to el29...i think??? modems? I read the forum daily but I'm completely lost honestly. To many basebands and modems and methods of doing this. Need help want to do this today

Sfhubs automated root thread in the sticky.
Run for root, then run option c for clockwork mod, backup, then flash the ROMS of your choice. Super easy, no Odin necessary
Sent from my Blazing ET4G
Edit: read twice, do the steps once
Also, look for qbking77's how to videos for complete walkthroughs

tkemack said:
Sfhubs automated root thread in the sticky.
Run for root, then run option c for clockwork mod, backup, then flash the ROMS of your choice. Super easy, no Odin necessary
Sent from my Blazing ET4G
Edit: read twice, do the steps once
Also, look for qbking77's how to videos for complete walkthroughs
Click to expand...
Click to collapse
I've actually tried this a few times now and SU never installs? Debugging checked drivers installed and still no luck yet...have ran it several times now.

Optimal Carnage said:
I've actually tried this a few times now and SU never installs? Debugging checked drivers installed and still no luck yet...have ran it several times now.
Click to expand...
Click to collapse
Use Option F on the main menu to enable the scroll buffer, then rerun Option A and post the log between BEGIN LOG and END LOG.

sfhub said:
Use Option F on the main menu to enable the scroll buffer, then rerun Option A and post the log between BEGIN LOG and END LOG.
Click to expand...
Click to collapse
---- BEGIN LOG ----
...Proceeding to copy necessary files...
push: copy2tmp/install-zerg.sh -> /data/local/tmp/install-zerg.sh
1 file pushed. 0 files skipped.
43 KB/s (447 bytes in 0.010s)
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-eg30-ek02.list -> /sdcard/000root/install-o
tachk-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-zIm
age.sh
push: copy2sd/000root/install-boot-el29.sh -> /sdcard/000root/install-boot-el29.
sh
push: copy2sd/000root/install-boot-el29-cwm.sh -> /sdcard/000root/install-boot-e
l29-cwm.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-e
l26-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-e
l13-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-e
k02-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-e
g31-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-e
g30-cwm.sh
push: copy2sd/000root/install-boot-common.sh -> /sdcard/000root/install-boot-com
mon.sh
push: copy2sd/000root/func.inc.sh -> /sdcard/000root/func.inc.sh
push: copy2sd/000root/busybox -> /sdcard/000root/busybox
27 files pushed. 0 files skipped.
1214 KB/s (2001448 bytes in 1.609s)
...Running Zerg exploit...
Unable to chmod zergrush: No such file or directory
/data/local/tmp/install-zerg.sh: ./zergrush: not found
---- STATUS of ZERG on PREVIOUS few lines ----
Waiting for device to be connected [press CTRL-C to cancel]... Found device
Installing persistent root... mount: Operation not permitted
install-root.sh: cannot create /system/app/Superuser.apk: read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
install-root.sh: cannot create /system/xbin/su: read-only file system
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
link failed Read-only file system
install-root.sh: cannot create /system/xbin/busybox: read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
install-root.sh: /system/xbin/busybox: not found
Done
Waiting for filesystem to sync... Done
---- END LOG ----

Ok thanks for looking into the log but I got it figured out...I'm pretty sure my virus protection was blocking the write. It's all good now rooted ek02 stock now to figure out how to get to el29 from here

Flash a ROM that comes with EL29 kernel and you're done. You can also flash the EL29 modem separately (no rom comes with a modem, they are separate) look at the wiki for all modem downloads. Good luck
Sent from my Blazing ET4G