Database Users

[Q] HELP!!!!!

I'm new for Galaxy S and I just rooted yesterday!
It was working fine and today I changed the system font styles.
And then problems have started!
I just rebooted the phone and then when the Samsung logo coming on, it stopped. so I did hard reset but nothing different.
So I searched google and found Odin way.
I followed the steps, it passed, then all I got were bunch of "force close" msg. like loop of force close!
so I tried Odin few more times, and then I was told to try with Vibrant Odin then I might get an error after that try Fascinate again.
So I did it.
Then more probems!!
When I turn on the phone, first thing I see is GT5000 something whatever for the Vibrant model name, and then I see Verizon Wireless.
Sometimes the phone just keep blinking( screen goes on and off and on and off)
so I turn off the phone turn back on, and then Im not able to make phone calls or network (airplane mode is on and I'm not able to turn it off)
I'm so stuck here.
Is there anyone who can help me??? PLEASE!! HELP ME!!! =[

Did you odin with phone or pda
Sent from my SCH-I500 using XDA App

I did it with PDA !!

sounds like you flashed vibrant firmware on your fascinate or vice versa...either way bad move

Yea, if you can somehow shoe horn the modem.bin, and falling up's fascinate images, you may be able to recover.
But if you flashed a rom from a different device, you may not be able to recover at all...
This is exactly how I would try to fix assuming that you didn't install voodoo.
1. Wipe in stock recovery (not in cwm, for some reason cwm recovery doesn't wipe)
2. Find a modem.bin for the di01. Flash that using odin.
3. Flash the system dump for di01.
4. Flash the kernel for di01.
5. Flash stock recovery as well just to be thorough.
If that works, then you should flash cwm recovery in odin and root again.

RacerXFD said:
Yea, if you can somehow shoe horn the modem.bin, and falling up's fascinate images, you may be able to recover.
But if you flashed a rom from a different device, you may not be able to recover at all...
This is exactly how I would try to fix assuming that you didn't install voodoo.
1. Wipe in stock recovery (not in cwm, for some reason cwm recovery doesn't wipe)
2. Find a modem.bin for the di01. Flash that using odin.
3. Flash the system dump for di01.
4. Flash the kernel for di01.
5. Flash stock recovery as well just to be thorough.
If that works, then you should flash cwm recovery in odin and root again.
Click to expand...
Click to collapse
good luck getting your phone to work again...^ that *should* work for you
but really people this is about the 500th thread on people flashing the wrong firmware on phones...geez

Yep, there are stickies for this. Maybe we should write a guide so that no one does it again. Wait, they already exist...

What's with all these threads? ..
How hard is it to read the instructions first before doing anything drastic?

http://forum.xda-developers.com/showthread.php?t=867648
This should help you. I fixed practically the same problem with this.
It's a magic wand, that'll take you back in time when you had your virgin unrooted fascinate

dun bricked myself good this time..

borked up the fascinate whilst trying to update to the devs 2.2.
i know exactly what i did wrong. i was running voodoo5, and i clicked to disable lag fix, but i forgot to restart to let it *actually* disable before trying to load the new stuff. STUPID!
when that happened, it hung on samsung screen, then after battery pull all the phone will do is boot loop.. samsung screen, then goes to robot and screen says says "wiping cache, data, ect.." and then back to samsung screen to reboot and reboot.
i have literally 30 tabs open with articles from here and other forums, nothing seems to be working. here is what i have tried.
1. tried booting back to red cwm and playing with the lagfix (enable and disable again) to see if it would work, no go. i ended up losing red cwm - had to ODIN red back.. i cant get green to flash.
2. tried flashing DL09 both the full package and each individual part via ODIN
3. tried flashing the stocki500system.md5 (from the board) and kernel via ODIN, and nothing.. same boot loop. everything i have flashed via ODIN still gives me a boot loop..
4. tried to connect via ADB but it wont let me access the phone.. NOTE: i just downloaded ADB as a last resort and know nothing about it..
the only thing i can seem to do is get to red cwm. i have several backups in the restore section, but none of them seem to work - either i get a "no file found" even though i can see the file(s), or i get an error after it does load that says ".android_secure.img not found. skipping restore of /sdcard/.android_secure"
any ideas?

Okay follow these steps. Make sure you follow them step by step. Even though you have the lagfix installed this removed it for me.
http://forum.xda-developers.com/showthread.php?t=782204
Place the PIT file where it belongs. Then ODIN the system, kernel, and recovery in that order. Don't restart the process every time. Just ODIN them one after another.

thank you very much for taking a moment to answer. i did follow that thread, however
i managed to get the stocki500 recovery but the other files (recovery, PIT) are all 404 not found errors.
ive tried that stock md5 and it still boot loops. i actually have that tab open from when i tried that route..
any other ideas and thanks again

Thats why its not working. Try this restore by adrynalyne. The file is there and everything is in one. Just ODIN in the PDA section. This should work.
http://forum.xda-developers.com/showthread.php?t=867648

I got myself into a bit of pickle too. Kept getting errors on the new_cwm file. After numerous attempts. I figured out the file hadn't downloaded correctly and the archive was damaged. Folks who havent installed Froyo yet, do yourself a favor and check the files before you save it to your sd card.

BSayre18 said:
Thats why its not working. Try this restore by adrynalyne. The file is there and everything is in one. Just ODIN in the PDA section. This should work.
http://forum.xda-developers.com/showthread.php?t=867648
Click to expand...
Click to collapse
downloading now.. thanks for the point to this file.. i hadnt found that one yet

no problem. it should work out good.

mailaliasgar said:
I got myself into a bit of pickle too. Kept getting errors on the new_cwm file. After numerous attempts. I figured out the file hadn't downloaded correctly and the archive was damaged. Folks who havent installed Froyo yet, do yourself a favor and check the files before you save it to your sd card.
Click to expand...
Click to collapse
i soft bricked doing that with a corrupt file before.. however that time i was able to restore using my backup.
this time, every time i try a method, it kicks me back to boot loop. if the file that im downloading now doesnt work, i will have to try and figure out ADB as a last resort..
thanks much for the help!

BSayre18 said:
no problem. it should work out good.
Click to expand...
Click to collapse
problem
thank you for all your help

mrjake1970 said:
problem
thank you for all your help
Click to expand...
Click to collapse
So this worked for you? You just re-rooted as normal?
def

Thank you all for your help. i applied all the info i got here, and one of them worked it finally took the ODIN flash to stock and i recovered into FROYO from there.
seriously thank you all.. its great that the community is so supportive

I did the exact same thing a couple of days ago, and recovered a similar way, odin back to D101, flashed DL09 & superclean, then restored a backup, then disabled voodoo and finally flashed DL30. I've got a couple of questions.
1: Is voodoo completely off my phone or is it just disabled (is there a difference)? When I apply update.zip from the blue recovery I get green cwm.
2: Each time I backup, restore, flash a different rom I apply update.zip, then from green recovery I flash "new_cwm.zip". Is this necessary?

Joe T said:
I did the exact same thing a couple of days ago, and recovered a similar way, odin back to D101, flashed DL09 & superclean, then restored a backup, then disabled voodoo and finally flashed DL30. I've got a couple of questions.
1: Is voodoo completely off my phone or is it just disabled (is there a difference)? When I apply update.zip from the blue recovery I get green cwm.
2: Each time I backup, restore, flash a different rom I apply update.zip, then from green recovery I flash "new_cwm.zip". Is this necessary?
Click to expand...
Click to collapse
i followed all the hints i got, and i think that the one i got about formatting helped me get out of the boot loop from hell.. it finally took my flash from ODIN, it wouldn't until i did the format(s)..
mind you i am NOT an expert, however from what i read and talked about offline, voodoo is still resident on your phone but disabled (check to see if you have the voodoo file still on your card).. if DL30 is running fine, you are ok..
from what i have read, yes.. the new cwm is required in order to get it to mesh properly with 2.2 leak.. i havent had any issues and i loaded that as well.. from one of the posts i read, if you are a serial flasher, then you need to make sure that not only you download the new cwm zip, but also should have deleted the entire clockworkmod folder from your card for best results..

I love this threadd.... I did the same damn thingg...
Sent from my SCH-I500 using XDA App

You guys are not alone. I'm just glad the peeps that know what's going on have the patience to put up with us.
Sent from my SCH-I500 using XDA App

adrynalyne's di01 odin package covers a multitude of sins.

upsidedownaaron said:
adrynalyne's di01 odin package covers a multitude of sins.
Click to expand...
Click to collapse
It will literally bring any phone back from the dead as long as its a software issue. I recommend keeping the di01 package, samsung drivers and Odin 1.3 on your computer at all times...
Sent from my SCH-I500 using XDA App

godihatework said:
It will literally bring any phone back from the dead as long as its a software issue. I recommend keeping the di01 package, samsung drivers and Odin 1.3 on your computer at all times...
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
ABSOLUTELY!! I have those on my computer at all times, adrynalynes d101 brought me back a few times.
Sent from my stock 2.1
unrooted, fully bloated (for now) Fascinate

[GUIDE] Sprint sph p100 stock firmware RECEOVERY: last resort.

Ok i decided i post what i did to recovery my sprints tab from a bad kernel flash that i didn't install clock work recovery, I thought my tab was a lost cause which i even chatted with hsn were i bought mine at for a replacement which would've took up to 30days.. So awhile i wait for that i decided to try and get it working till i get the prepaid label lol
Matter what i did it kept getting stuck at the samsung screen and couldn't get into recovery but download mode work luckly. i tried all kernels listed and it still got stuck which at the time i thought my tab was bricked or semi brick.
What i did is keep searching for the stock firmware which was hard to find but i found this thread http://forum.xda-developers.com/showthread.php?p=9753941#post9753941
Heres a direct link http://www.multiupload.com/WDKOUJSM2G
Thanks to ZoinksS2k for the tab sprint no modem firmware
And downloaded the stock no modem firmware the modem one is listed too but it will kill your gps and 3g might not work so i just did the no modem one.
So i downloaded it and odin was package with it and i couldn't get it to detect my tab in download mode ony when the tab was off it detected it..
So i tried heimdall and at first i couldn't get it to flash the start button was grayed out because i was putting the tar file into pda/code so i open the tar file and found factory.rfs param.ifs and cache.rfs and dbdata.rfs so i loaded all thoes in the heimfall boxes and than loaded the stock zimage which is in the tar too.
And than i flashed and saw the samsung screen and it went right pass it and played the samsung splash screen so i knew i was getting somewhere so it got stuck on the next samsung screen again.. So i turn it off and hold home button and volume up button than i push the power button and hold all 3 buttons till i saw the samsung screen and i left go the power button and the stock recovery loaded right up
So i did the wipe data/factory reset and i also did the wipe cache data just in case but im sure just the factory reset would work, And i restarted the tab and it went pass all screens and it loaded android!!! And everything was working 3g wifi gps and everything else.
So hopefully this guide will help others as a last resort if you ony get the samsung screen and download mode ony,If you get the receovery than just do the factory wipe.
This is worth a try first than sending it back to samsung and having to wait too get your tab back It sure saved me from having to send it back too hsn or samsung.
If you want you can thank me if this help you for providing the info

Gordesky,
Any idea how to go back to stock firmware + stock modem and all that from using the voodoo kernel? I have CWM Recovery 3.0 working.

Because, after going into Voodoo CWM Recovery, using wipe data/factory reset still keeps the kernel that I installed on - which is what makes my camera screwy.

If you want to go back to fully stock then follow his instructions and flash the stock kernel from the Zephyr thread. I actually am in the same boat as the OP and followed his instructions and now I'm fully back to stock.

Yep just do what I said which the tar file also have the stock kernel too.
Right now im on the voodoo kernel which works perfect except that cdrom problem but camera works for me so im gonna still with.this kernel so far. It seems the new sprint update doesint work right with the voodoo kernel problaby why I dont have any problems because I didint install the sprint update.
So when you go back too stock and want too give the voodoo another try dont install the sprint update when it asks you too, And everything should work other than the sdcard cdrom problems, Which I can deal with till it gets fixed because I do love the speed of this voodoo kernel
And the sound

Thank you gordesky1 for posting your experience because I was going through the exact same thing and I was at a loss as to how to resolve it. Unfortunately I did install the update but I'm pretty sure if I flash the same files again that I will go back to the original rom if that's necessary. The big problem with that is that the exchange fix in the update was something i was waiting for =\ so I think i'm going to wait and see if some of these issues are fixed in the next update but I wonder if we have to get Boushh a Sprint tab though =\ every day I curse myself for not getting a t-mobile or at least a Verizon tab *sigh*

No problem
Ya tell me about it... Bad thing for me is the sprint was my ony option which i got it because hsn were i bought it from had a flex pay on this tab which they ony have the sprint tab, and at the time i couldint pay 400 or 600$ right out. And i also got a 3years warranty on top of it from them even if i break it or drop it anywere which i pretty much got for free because they made a mistake at first with some software
The other tabs have cheaper 3g too like 5gb for 15 too 30$ a month.. But so far sprint is treating me good and the 3g has been stable so far and pretty fast loading webpages and can usely watch a youtube video but dont want too use up my monthy usage lol i usely use up too 500 too 600mbs max out of 2g and i useit every day and even download apps with it when im not near a wifi spot and listen too pandora too so i was suprized i didint get close too the 2gb limit yet.
Hopefully this thread will help more and save them from having too send it back too samsung or were they got it from, i know how it feels not having this tab which i use everyday at work.

I knew not to flash the modem from the restore package posted but when I tried to restore I used the .pit and the .tar. Failed at modem. So, being dumb I flashed the modem file. ugh.
Now I know all you need to do is flash the .tar, nothing else, no pit.

Your Post Saved Me!!!!!
10 characters

Your welcome and glad it helped I figure it was worth posting sense it brought my tab back too life which i thought i would've had too sent it back and waited a month or so, And wanted others too get there tab back too life with out playing the wait game which i really hate .. lol

this worked! I was able to get rid of CWM, my tab is 100% stock again! thanks a bunch!

well, I tried installing the update from sprint and goes back to CMW and starts doing the freaking back up again!! What the heck!!! anyone can tell me how to get back to stock recovery!! this is driving me nuts!

jcaf77 said:
this worked! I was able to get rid of CWM, my tab is 100% stock again! thanks a bunch!
Click to expand...
Click to collapse
I flash the above .tar and .pit with Odin and I still can't get rid of CWM. I had CWM 3.0 working. Then I flashed a Kernel (Khasmek) with kernel flasher and the damn thing froze on the splash screen. So I odin and it doesn't do a full factory reset. CWM folder is still there. Does anbody know how to completely revert back to stock firmware?
I basically want to start over from scratch and never use Kernel flasher.
Any help will be greatly appreciated.

lphillips80 said:
I flash the above .tar and .pit with Odin and I still can't get rid of CWM. I had CWM 3.0 working. Then I flashed a Kernel (Khasmek) with kernel flasher and the damn thing froze on the splash screen. So I odin and it doesn't do a full factory reset. CWM folder is still there. Does anbody know how to completely revert back to stock firmware?
I basically want to start over from scratch and never use Kernel flasher.
Any help will be greatly appreciated.
Click to expand...
Click to collapse
Flash the zImage from the stock rom in the recovery slot using hiemdall and it will flash the stock recovery over cwm.

I performed that action and it works it does get rid of CWM but now I am still unable to install sprint updates they fail half way into it

jcaf77 said:
I performed that action and it works it does get rid of CWM but now I am still unable to install sprint updates they fail half way into it
Click to expand...
Click to collapse
I am having the exact same problem, really wish I had read your post before I attempted to get CWM on my sprint galaxy tab.
I believe the update failed for me due to mismatch baseband (EB28) and system build (DJ30), I am looking for a roto backup copy of system build EB28, if anyone have it, please help and upload!
Many thanks.

I flashed the zImage with heimdall and it still wont do a sprint system update and also I cannot do the cwm process again to format to ext4.
Sent from my SGH-T959V using XDA Premium App

lphillips80 said:
I flashed the zImage with heimdall and it still wont do a sprint system update and also I cannot do the cwm process again to format to ext4.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Check out the newly leaked EA24 flasher, it will update both system and baseband to EA24 and you will be able to update after that.

Thanks technote. I used the above and worked awesome!
Sent from my SPH-P100 using XDA Premium App

okay, im farily new to the galaxy tab forums, only reason im here is because my friend bricked his tab and figured i could take a stab at it, i mean im good at fixing my galaxy s so i figured, how hard can this be. Wrong, my head is killing me because i cant figure this out. His tab is stuck in a boot loop mean it goes to the "samsung" screen and then stays there forever. I tried using odin with the stock firmware with no modem, everything went good but when it attemped to restart still nothing ? can someone please school me on how to do this properly please. Im a pretty good listener if im given descent instructions lol please by all means HELP lol

Soft brick trying to get into CWM Recovery?

I was wondering how it was possible to brick your phone (which somehow happened to me..) just by trying to get into CWM Recovery by doing the 3 button press.. As it is possible because it happened to me earlier today I was just wondering if it was a step that I did wrong.. Also I had nothing installed except flashing the Froyo EB01 modem which flashed successfully and than reflashed cwm recovery all which worked though I forgot I had to reboot fast or else samsung would replace cwm. So when I flashed a second time and than tried rebooting into cwm that's when it got stuck and bricked..
I got it solved earlier thanks to Adranalyne.
If anybody needs his thread for the all in one odin:
http://forum.xda-developers.com/showthread.php?p=9711053

Ensure it's not simply blank screen...hit search soft key when it ' should' go into cwm
Sent from my SCH-I500 using XDA App

Shadowchasr said:
Ensure it's not simply blank screen...hit search soft key when it ' should' go into cwm
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Naw, it was stuck on the samsung logo screen for an hour-got bricked. But i fixed it .

Can someone explain how exactly you fix it? I am having that problem as we speak...

sengokubattosai said:
Can someone explain how exactly you fix it? I am having that problem as we speak...
Click to expand...
Click to collapse
Odin it back to stock. Either Dl01 or Eb01. Both files include everything for you to recover your phone ans be able to boot back up past the samsung logo.

Taking it back to EB01 every time can be a bit extreme. There are CWM tar files that you can use to just flash CWM with Odin. I've used them when my phone would not boot into recovery. Remember the best way to get to "Download" mode is to pull the battery and while holding the down vol button plug it into your PC. I know thats common knowledge but it's always good to put it out there. Other techniques can prevent Odin from establishing a connection.
I've even seen complete Super Clean tars up to 2.6. I don't remember where but when 2.7.1 bricked my phone I just used Odin to flash a 2.6 tar and my phone was back to normal. Now I use that ROM image instead of EB01 when an update fails.
I would stress that any ROM compiled by someone else is not going to be endorsed by the Dev that created the update. I just took a chance because I was already down and it worked great.

[Q] S4 Bootloop, Can enter download but not recovery

Hi,
I have been searching and searching. I tried to install a kernel to my phone, its been forever so i don't remember which one.
It just reboots every 5 seconds without any screens coming up. I can not get into recovery mode
I can get into download mode and have flashed stock I337UCUAMDB_ATTAMDB_I337UCUAMDB with odin, but it doesnt fix anything.
What can I do to get to stock recovery and fix my phone?

What happens if you put it on download mode and then cancel with vol down

It falls back into the bootloop of restarting every 5 seconds with no screens coming up. No entry into recovery.

And if you pull the battery and put it back in does it try to boot?

What firmware were you on and was it loki'd if you were on mdl?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

I have taken the battery out and replaced it. It does not automatically try to boot. After pressing power it goes into the same boot cycle. Also, thank you for your quick attention!

megatilter said:
I have taken the battery out and replaced it. It does not automatically try to boot. After pressing power it goes into the same boot cycle. Also, thank you for your quick attention!
Click to expand...
Click to collapse
When did it start doing what's it's going. Did you do anything before hand? Do you know what firmware you where on before you tried odin? Was it mdb?

"What firmware were you on and was it loki'd if you were on mdl?"
Previous to my obvious blunder with the kernel download, I was using goldeneye rom from android develepment, sucessfully.
Dont know if that answers the question but i have also tried to flash AMDL with odin but have the same results.

megatilter said:
"What firmware were you on and was it loki'd if you were on mdl?"
Previous to my obvious blunder with the kernel download, I was using goldeneye rom from android develepment, sucessfully.
Dont know if that answers the question but i have also tried to flash AMDL with odin but have the same results.
Click to expand...
Click to collapse
When you used odin did you only have f.reset and auto-reboot checked and flashed the md5 file in PDA

jd1639 said:
When you used odin did you only have f.reset and auto-reboot checked and flashed the md5 file in PDA
Click to expand...
Click to collapse
I have done it multiple times, perhaps panicking, I checked the re-partition button. I have tried to get a PIT file downloaded and tried to use that.
However, this behavior was happening before I did that. It started boot looping as soon as i tried to use TWRP to flash the kernel (I know i am an idiot, and didn't read first). As soon as this started happening, that's when I immediately tried to flash AMDL (exactly as you described with only those options checked) through odin and it didn't do anything different. That's when i tried other options. I fear i may have broken my phone. Again thank you for your attention.

megatilter said:
I have done it multiple times, perhaps panicking, I checked the re-partition button. I have tried to get a PIT file downloaded and tried to use that.
However, this behavior was happening before I did that. It started boot looping as soon as i tried to use TWRP to flash the kernel (I know i am an idiot, and didn't read first). As soon as this started happening, that's when I immediately tried to flash AMDL (exactly as you described with only those options checked) through odin and it didn't do anything different. That's when i tried other options. I fear i may have broken my phone. Again thank you for your attention.
Click to expand...
Click to collapse
I think you've broken it too. Sounds like you flashed the wrong kernel and at that point you were more or less hosed. Look into jtag, mobiletechvideos.com. They can probably fix it. It'll cost you $60.00 +
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

jd1639 said:
I think you've broken it too. Sounds like you flashed the wrong kernel and at that point you were more or less hosed. Look into jtag, mobiletechvideos.com. They can probably fix it. It'll cost you $60.00 +
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
i've never seen a kernel hard brick a device or corrupt the recovery partition. i also rarely see a user flash a file and not remember what they just flashed. he/she possibly flashed an incompatible kernel or flashed a non-loki'd kernel without flashing loki-doki. either way, recovery would still be accessible to correct this issue. i feel that there is more to this.
OP, see jd's jtag post above.

megatilter said:
I have done it multiple times, perhaps panicking, I checked the re-partition button. I have tried to get a PIT file downloaded and tried to use that.
However, this behavior was happening before I did that. It started boot looping as soon as i tried to use TWRP to flash the kernel (I know i am an idiot, and didn't read first). As soon as this started happening, that's when I immediately tried to flash AMDL (exactly as you described with only those options checked) through odin and it didn't do anything different. That's when i tried other options. I fear i may have broken my phone. Again thank you for your attention.
Click to expand...
Click to collapse
Well I finally was able to get Kies working and did a firmware update. That gave me back regular recovery. Now Im stuck at bootloop att screen.
I then re flashed AMDL stock via odin and VIOLA!
Im back to stock baby!
And from there ill probably go back to Goldeneyes Rom and never think about this ever again. Thanks for your time. My phone is working again!
Also
Thank you for helping me at least by giving this thread attention. So much appreciation to the fine people here at XDA

megatilter said:
Well I finally was able to get Kies working and did a firmware update. That gave me back regular recovery. Now Im stuck at bootloop att screen.
I then re flashed AMDL stock via odin and VIOLA!
Im back to stock baby!
And from there ill probably go back to Goldeneyes Rom and never think about this ever again. Thanks for your time. My phone is working again!
Also
Thank you for helping me at least by giving this thread attention. So much appreciation to the fine people here at XDA
Click to expand...
Click to collapse
Great news! You got lucky, make sure you read and learn on xda. And always know what you flash.

megatilter said:
Well I finally was able to get Kies working and did a firmware update. That gave me back regular recovery. Now Im stuck at bootloop att screen.
I then re flashed AMDL stock via odin and VIOLA!
Im back to stock baby!
And from there ill probably go back to Goldeneyes Rom and never think about this ever again. Thanks for your time. My phone is working again!
Also
Thank you for helping me at least by giving this thread attention. So much appreciation to the fine people here at XDA
Click to expand...
Click to collapse
Care to share how you got Kies working? I have a similar problem and I can't get Kies to recognize my phone.

Fix!
So What you gota do
1. Pull Out Battery Put back in
2.Go To Download Mode
3. Download The TWRP.tar For Your Phone
4.Run Odin as Admin, Tick Pda, for pda select the TWRP.tar
5. Hit Start, Then Pull Out battery put it back in
6.Get A Micro Sd And Put The Cyanogenmod Rom, and the gapps the ones for your phone
7.Insert microsd in phone
8. Boot Recovery and go to mounts and mount the microsd
9, Go Advansed, file manager, ext sd, And Copy the cyanogenmod and the gapps to internal storage
10. Flash the cyanogen mod and the gapps. DO THIS PART CAREFULLY OR MIGHT HARD BRICK!
11. Reboot And youl boot to cyanogenmod! OH yeah! Replay if this helped or if you have any problems