[General Questions and Answers] keifus.rahn:
So I've did some Research on your device and it seems like everyone is having the same problem and there seems that a fix hasn't been Resolved yet. But here are a few things you can try to resolve this issue... (1) If you can take the battery out plug it in to the charger / Then take the battery out and unplug /\ This is to make shure you have no power left in the device wait about a minit then place the battery back in and press the volume down for about 30 seconds and the press and hold the power button while holding the volume down key When the screen lights up let go of the power and keep holding volume down for 15 seconds that should give you some options on restoring your device if that dont work then try doing the same with vol up instead of down or try holding both volume keys and ive noticed that there is a restart hole next to the volume keys if so do the charger steps but with out the vol keys....Find somthing to press and hold the reset button and while holding the reset button power on the device and see if any luck..

(2) PC NEEDED WITH SDK if you have a pc and you have the android sdk set up u can try connecting to your device using / adb /echo/ if you dont have the sdk you can get it here with a tut on using adb= http://developer.android.com/sdk/index.html now if your ready here is a way to connect to your device threw adb... Using ADB as solution

ADB can be used to access the phone while booting, be aware that some bootloops make it unable to use ADB since they do not go further then the manufacturer logo. (In new CWM versions it’s possible to use adb)

The only tricky part about using ADB with bootloops is that you have to do it on the right time, this is different from every device, but normally it’s after the manufacturer logo that the partitions get mounted. The easiest way to enter your phone in this part is using a batch script that monitors the state of your device and connects directly when possible.

I use this script for example, called ondemand.bat (requires adb.exe and the 2 dlls)

1 [MENTION=279333]ECHO[/MENTION] off

2 cd /d %~dp0

3 echo.

4 echo Waiting for device…

5 adb wait-for-device

6 echo.

7 adb -d shell stop

8 adb push mycwmfix.zip /sdcard/mycwmfix.zip

9 adb reboot recovery

Linux Version (ondemand.sh):

1 #!/system/bin/sh

2 echo " "

3 echo "Wating for device..."

4 ./adb wait-for-device

5 echo " "

6 ./adb -d shell stop

7 ./adb push mycwmfix.zip /sdcard/mycwmfix.zip

8 ./adb reboot recovery

This script will wait for the device to become ready, when it’s ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push the specified cwmfix zip to your sdcard, and after that it will reboot in recovery so you can install the cwm fix you made. You can also make an batch script that pushes the files automatically to your phone, here is an example:

(1 [MENTION=279333]ECHO[/MENTION] off

(2)cd /d %~dp0

(3)echo.

(4)echo Waiting for device...adb wait-for-device

(5)echo.

(6)adb -d shell stop

(7)adb -d shell su -c "mount -o remount rw /system"

(8)adb push framework-res.apk /system/framework/framework-res.apk

(9)adb -d shell chmod 644 /system/framework/framework-res.apk

(10)adb push SystemUI.apk /system/app/SystemUI.apk

(11)adb -d shell chmod 644 /system/app/SystemUI.apk

(12)adb reboot

(13)Linux version:

1#!/system/bin/sh

2echo " "

3echo "Waiting for device..."

4./adb wait-for-device

5echo " "

6./adb -d shell stop

7./adb -d shell su -c "mount -o remount rw /system"

8./adb push framework-res.apk /system/framework/framework-res.apk

9./adb -d shell chmod 644 /system/framework/framework-res.apk

10./adb push SystemUI.apk /system/app/SystemUI.apk

11./adb -d shell chmod 644 /system/app/SystemUI.apk

12./adb reboot

This script will wait for the device to become ready, when it’s ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push framework-res.apk and SystemUI.apk to the directory it belongs to, after that it changes the permissions of the files to RW-R-R (644) and then it will reboot.

Please note that on some devices the command “su -c” cannot be used after using the “stop” command, it gives an error then (Segmentation Fault).

What you can do to prevent this is adding “adb remount” just under the “adb wait-for-device” line, and remove the “adb -d shell su -c “mount -o remount rw /system” line.

Save the script and run it again.

You are probably able to fix your bootloop with this guide, in some rare cases some other partitions could be damaged, then I advice you to install the stock rom (which is no .zip in most cases)

Once you master the fixing of bootloops you can fix your phone independently !

You can try this if all else fails GOOD LUCK SIR :fingers-crossed: http://www.mediafire.com/?9oghmlgoqpm44qe