Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,729,324 Members 42,544 Now Online
XDA Developers Android and Mobile Development Forum

[TUTORIAL] Full Steps to Acheive Root + ClockwordMod Recovery with new KA6 2.2

Tip us?
 
bomb0708
Old
#171  
Junior Member
Thanks Meter 0
Posts: 1
Join Date: Aug 2010
i dont understand step 2...could u explain more plz?
 
timtimbobtim
Old
#172  
Junior Member
Thanks Meter 0
Posts: 1
Join Date: Mar 2011
Default Everything works but clockworkmod reboot

Thanks for the instructions!

Everything works but clockworkmod reboot. It keeps rebooting with blue text. Tried blowing away update.zip and the clockworkmod folder and re-installing ROM Manager, then re-doing the ROM Manager steps, to no avail.
 
rbcamping
Old
#173  
Member
Thanks Meter 1
Posts: 61
Join Date: Aug 2010
I tried down loading this to us and root my phone and I cant down load the program. I keep getting an error message?

C:\Users\owner\AppData\Local\Temp\d2T5ZR24.zip.par t could not be saved, because the source file could not be read.

Try again later, or contact the server administrator.

Whats up or what do I do, or what did I do wrong?
 
eddydy
Old
#174  
Junior Member
Thanks Meter 1
Posts: 15
Join Date: Aug 2008
I can literally kiss you, e-kiss that is, man finally I'm able to overcome this ClockworkMod Recovery problem.
Thank you thank you
 
NoPants
Old
#175  
Junior Member
Thanks Meter 0
Posts: 12
Join Date: Mar 2011
Pretty self explanatory...at first I cut corners cos I couldn't understand just re read it a couple times. It works well.
 
boardbunny_79
Old
(Last edited by boardbunny_79; 2nd April 2011 at 04:58 PM.)
#176  
Junior Member
Thanks Meter 0
Posts: 21
Join Date: Aug 2010
I have only made it to step 2. This is what happens...
Installing busybox (/system/xbin/)...
busybox: /system/xbin/rpm2cpio: No space left on device
busybox: /system/xbin/rtcwake: No space left on device
busybox: /system/xbin/run-parts: No space left on device
busybox: /system/xbin/runlevel: No space left on device
busybox: /system/xbin/runsv: No space left on device
busybox: /system/xbin/runsvdir: No space left on device
busybox: /system/xbin/rx: No space left on device
busybox: /system/xbin/script: No space left on device
busybox: /system/xbin/scriptreplay: No space left on device
busybox: /system/xbin/sed: No space left on device

THEN FINALLY IS SAYS:
Pushing Superuser.apk...
failed to copy 'C:\xxxxx\SuperOneClickv1.7-ShortFuse\Superuser.apk' to '/system/app/Superuser.apk': No space left on device

how can i fix this? i deleted everything on the sd card i think
 
kawika
Old
#177  
kawika's Avatar
Senior Member
Thanks Meter 77
Posts: 683
Join Date: Nov 2010
Location: Loveland, OH

 
DONATE TO ME
Quote:
Originally Posted by boardbunny_79 View Post
I have only made it to step 2. This is what happens...
Installing busybox (/system/xbin/)...
busybox: /system/xbin/rpm2cpio: No space left on device
busybox: /system/xbin/rtcwake: No space left on device
busybox: /system/xbin/run-parts: No space left on device
busybox: /system/xbin/runlevel: No space left on device
busybox: /system/xbin/runsv: No space left on device
busybox: /system/xbin/runsvdir: No space left on device
busybox: /system/xbin/rx: No space left on device
busybox: /system/xbin/script: No space left on device
busybox: /system/xbin/scriptreplay: No space left on device
busybox: /system/xbin/sed: No space left on device

THEN FINALLY IS SAYS:
Pushing Superuser.apk...
failed to copy 'C:\xxxxx\SuperOneClickv1.7-ShortFuse\Superuser.apk' to '/system/app/Superuser.apk': No space left on device

how can i fix this? i deleted everything on the sd card i think
everytime i run into "No space left on device" error its always in /system and is usually in /system/media/audio never any problems anywhere else usually. I'd check it still for me its always some ringtones or notifications that i just move onto my internal or external SD and that frees up enough space to write to /system files. Good luck!
Device 1:
* Model number - Nexus 4 * Android version - 4.2.1 * Baseband version - M9615A *
* Kernel version - 3.4.0-perf-ge039dcb * Build number - JOP40D *

Device 2:
* Model number - T959 * Firmware version - 4.1.1 * Baseband version - T959UVKB5 *
* Kernel version - Dirty Devil3_1.1.8_HB_vibrant * CyanogenMod version - helly_bean_vibrant *
* Date on box - 09/30/2010 *

Mornin sunshine
 
m11c3
Old
#178  
Member
Thanks Meter 5
Posts: 97
Join Date: Nov 2010
Location: bandung
amazing.... i try any method failed, but use this method success
 
murrayrs5
Old
#179  
Junior Member
Thanks Meter 0
Posts: 17
Join Date: Dec 2010
Location: spokane
omg thank you been trying to root my vibrant for hours tonight and this did it tytyty....
 
bhspakiboi786
Old
#180  
Junior Member
Thanks Meter 0
Posts: 3
Join Date: Nov 2008
Default not turning green

i did all the steps and everything but it still shows up blue and it isnt turning green. i deleted clockwork folder and reboot and still no change. any suggestion or what im doing wrong?

Tags
2.2, ka6, recovery, root, vibrant
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes