no matter what i do i cant get out of recovery. im on cwm 3.1.0.1 (purple) i just now went into recovery to flash a new rom but when i try to select something it just show the circle with the hat on it. i pulled the battery and when i turned it back on, it went straight back to recovery.
edit...well i actually tried to get to recovery (3 finger salute) and then i could use recovery like normal. hopefully this will help someone else
Best bet is to Odin in EC05 stock, root and flash a GB ROM. Something happened to your boot partition. Use the method at the top of Development in the stickies and repaprtition your phone as well.
Sent from my SPH-D700 using XDA App
have you done a nandroid backup by chance?
id try reflashing the recovery
strat with odin ei22 and do root and then recovery 5.0.0.1
Same
I had the same problem when I was trying to restore my wife's phone. Try restoring the original stock with odin. http://forum.xda-developers.com/showthread.php?t=1357655 worked for me.
---------- Post added at 07:35 AM ---------- Previous post was at 06:58 AM ----------
Just found this one this morning. Works fantastic and even has on screen step by step guide to do it correctly. Unfortunately the forum wont let me post the link, so, google epic 4g odin tar, look for a link to pc geeks forum and they have an all in one windows based updater. Run the .exe on your pc and after it installs to your computer launch the program from the desktop icon it creates, follow the on screen prompts. Best restore program i have ever seen.
Related
I just tried to do an nandroid to a previous ROM, this has been done many times before via CWM. This time after reboot I got stuck in a bootloop as I pulled battery and manually tried to get into recovery with power/volume this time it went to odin mode and now says dowloading, do not turn off target.
I have powered down phone from ODIM mode. but now when trying to re-boot im stuck at samsung galaxy boot screen. I now have tried once or twice to manually get into recovery to see if sends me to CMW but phone resets back to the boot rather than bootloader.
I have tried to hold volume up and power to try and boot into recovery and all I get is the bootloop while holding the buttons, never gets routed to recovery. (I heard for ODIN you hold volume down and power)
Has anyone experienced this? I have never used ODIN so no sure where this is comming from.
I have tried to manually get into recovery and I get a samsung message that downloading a custom OS can be harmfull either I can proceed or re-boot. If I proceed (volume up) I get the "downloading do not run off traget" in ODIN mode if i do volume down I reboot but that back at the bootloop
If you cannot get into recovery you are probably going to have to flash through Odin. From the sound of it you never used odin before. I would flash back to the stock rooted rom and then reinstall clockwork mod. I will provide links. A file probably just got corrupt during the nand restore. Lets hope I can get ya back up and running.
Install stock rooted rom:
http://www.youtube.com/watch?v=v7pWjmKCsoc&context=C3947c01ADOEgsToPDskJI18lFujJeVrMeUHHZ0m_o
Reinstall Clockwork Mod:http://www.youtube.com/watch?v=jZRnH-_XZmM
Make sure you follow the steps exactly and do NOT pull out the cable during odin until it is complete or you WILL brick your phone!
---------- Post added at 11:27 PM ---------- Previous post was at 11:23 PM ----------
If anyone has an easier way please feel free to share it as I am not a noob but not as much of an expert as some others on this site.
rbtrucking said:
If you cannot get into recovery you are probably going to have to flash through Odin. From the sound of it you never used odin before. I would flash back to the stock rooted rom and then reinstall clockwork mod. I will provide links. A file probably just got corrupt during the nand restore. Lets hope I can get ya back up and running.
Install stock rooted rom:
http://www.youtube.com/watch?v=v7pWjmKCsoc&context=C3947c01ADOEgsToPDskJI18lFujJeVrMeUHHZ0m_o
Reinstall Clockwork Mod:http://www.youtube.com/watch?v=jZRnH-_XZmM
Make sure you follow the steps exactly and do NOT pull out the cable during odin until it is complete or you WILL brick your phone!
---------- Post added at 11:27 PM ---------- Previous post was at 11:23 PM ----------
If anyone has an easier way please feel free to share it as I am not a noob but not as much of an expert as some others on this site.
Click to expand...
Click to collapse
When I get home ill give it a shot, you are correct I never used ODIN, I came from the EVO's so CMW has been all ive dealt with.
I think you hit it on the head rbtrucking.
Odin restore + root
CWM
Flash away
Sent from my Blazing ET4G
tkemack said:
I think you hit it on the head rbtrucking.
Odin restore + root
CWM
Flash away
Sent from my Blazing ET4G
Click to expand...
Click to collapse
Thanks guys, seemed to do the trick got my phone up and running just like it was. I just need to download CMW and ive done that when firdt rooted so shouldnt be a problem. You think if I use a backup from before (other than the one i used when i initaly had issues) will be a problem?
Thanks again
you should be good.
Stuck at "Data.img" thru odin. Possible EMMC brick fix! Thanks to Jaymoon pg.#44
So here's the deal. I just couldn't help myself and I flashed shabbys ICS test build this morning. Well the more I started reading in the thread about guys having issues restoring there backups I tried it. Flashed the cwm touch recovery....did a full wipe and then went to restore my nand of Blend. Booted up and gets stuck at the Samsung boot screen. I let it sit there for about 10 minutes. Then from there I pressed volume up and power to see if i could get back into cwm. I was able to and had rogue recovery. I then went to do a full wipe again. The data wipe took about 2 minutes....which was strange...then wiped cache and dalvik. Then went to flash Blend(not the nand backup) and again stuck at the samsung boot screen.
So I then went into odin mode and attempted to odin back to stock using the D710USEL29_20120105.stock from qb777's you tube vid. All went good....got the pass and once again stuck at the Samsung boot screen. Then from there I went back into odin download mode and attempted to odin the stock rooted file(not the file to keep your data file) and it got stuck at "Data.img" in odin.
So now I sit with the battery out of my phone and have no idea what I can try from here. I think I remember reading that as long as you can get into odin download mode there should be a fix. As alot of you can probably tell from reading this I am new to odin. I should have never flashed this test build if I was not a hundred percent sure that I could get back and also should have been WAY more familiar with odin before flashing.
I'm off to hit the sack....have a fat headache from this screw up of mine. I'll be up at 6am to check in here. If anyone can help I would really appreciate it......and whatever suggestions you may offer please take into account that I just learned about odin last week, so maybe a "odin for dummies" could help me out the most.
A little freaked out about this and really hope someone knows a way they can help.
THANKS in advance
[EDIT] Looks like we may have a fix. Refer to Page numbers 44,45. Thanks to Jaymoon and everyone else involved.
nevermind 10 char
try this homie...
odin this recovery.... http://goo-inside.me/kernels/TeamRo.../rogue_ET-recoveryonly-1.1.4-rc0-odin.tar.md5
it finally allowed me to wide data which i couldnt do all this time...
im just gonna stick with this for now and try a few things
caspersfi said:
So I then went into odin mode and attempted to odin back to stock using the D710USEL29_20120105.stock from qb777's you tube vid. All went good....got the pass and once again stuck at the Samsung boot screen. Then from there I went back into odin download mode and attempted to odin the stock rooted file(not the file to keep your data file) and it got stuck at "Data.img" in odin.
Click to expand...
Click to collapse
It is possible somehow your partitions got messed up.
If you look at section A2 of the EL29 ODIN One-Click, you will find the regular ODIN tar.md5
You can use that with regular ODIN. The file you download is a self-extractor so you need to double-click and select where to unpack. That will give you a tar.md5 file. Use the *PDA* slot in ODIN to select that file. Double-check you used the *PDA* slot. Then the only option you should select in ODIN (that isn't already selected for you) is Re-Partition (so you should have Re-Partition and Auto-Reboot checked)
so sfhub,
after doing the wipe in the stock recovery.... i did a reboot system
THe "samsung Galaxy sII" screen just flashes on and off every couple of minutes.
dadoc04 said:
so sfhub,
after doing the wipe in the stock recovery.... i did a reboot system
THe "samsung Galaxy sII" screen just flashes on and off every couple of minutes.
Click to expand...
Click to collapse
So this is different that what it was doing before? Perhaps you are making progress.
Try ODIN flashing just the rooted ROM (section #B4)
Sorry it is taking so long. I'm kind of using you to debug the actual issue.
sfhub said:
So this is different that what it was doing before? Perhaps you are making progress.
Try ODIN flashing just the rooted ROM (section #B4)
Sorry it is taking so long. I'm kind of using you to debug the actual issue.
Click to expand...
Click to collapse
no problem... your help is appreciated... gimme a minute download #B4 and ODIN... ill post results
---------- Post added at 02:40 AM ---------- Previous post was at 02:38 AM ----------
I dont see a B4... maybe im looking in the wrong thread... u mind linking me?
---------- Post added at 02:42 AM ---------- Previous post was at 02:40 AM ----------
NEVERMIND>.. i was using the wrong link.. i found it
---------- Post added at 02:46 AM ---------- Previous post was at 02:42 AM ----------
do you want me to select anything in odin? or just the auto reboot?
It is a self-extractor so remember to double-click on it to extract the tar.md5 before using in ODIN.
Just auto-reboot is fine.
You've already flashed the kernel and reformated /data. The only thing needed to boot that might not be correct is the ROM, so hopefully this works.
alright... ill let you know in a few minutes what happens
It will probably take a little bit of time. The ROM is the largest image.
^ yea...
its going now... currently in FACTORYFS...
---------- Post added at 02:59 AM ---------- Previous post was at 02:55 AM ----------
it says PAss..... not sure where it did data though....
factoryfs
NAND Write Start
RQT CLose
RES OK
REmoved
Completed
All threads completed (succeed 1/ failed 0)
It didn't do /data (data.img). You already formatted that using stock recovery, so it shouldn't be necessary to flash it.
Factoryfs.img is the ROM.
You previously already flash the kernel and verified it was working because you were able to boot into stock recovery.
So that takes care of kernel, ROM, and /data. I doubt anything is wrong with the modem. So everything that is needed to boot should be in place.
its just flashing the "samsung galaxy s II" screen again
it goes to a grey battery image screen
That is usually what it does when you power down your phone. What happens when you press and hold power until something happens?
press and hold power = gray battery screen....
edit... the battery went away and "samsung galaxy s2" is back
If it is looping again, try booting into recovery and wipe data/factory reset one more time.
I wonder if you can run adb logcat as the phone goes from off state to stuck on samsung logo. You might be able to see whats going on if adb picks it up.
^ That's a good idea ^ Might provide some clues.
sfhub said:
If it is looping again, try booting into recovery and wipe data/factory reset one more time.
Click to expand...
Click to collapse
wiping data/factory reset now... ill let ya know how it goes. It took a while last time as i think it was hung up
---------- Post added at 03:17 AM ---------- Previous post was at 03:14 AM ----------
im comfortable with ADB...
tell me how/when to do it and ill give it a shot....
---------- Post added at 03:18 AM ---------- Previous post was at 03:17 AM ----------
wipe is complete...
still shows the E:file is written: not updated
in command prompt, type
adb logcat
it will more than likely say "waiting for device" . thats fine, just plug in your phone to the pc and boot up the phone as usual. if the phone is booting far enough, adb should pick up the device and start displaying the logcat.
I was trying to install one of drewgarens touchwiz roms. touchwiz milestone 5 firefly i believe. not the most recent one because i was too lazy . boy was that a mistake. everything was going smoothly until it booted and it got stuck on boot. I thought no big deal just go into recovery and use a backup. until i did so and recovery was gone and there was only download mode. I have spent the whole afternoon trying to fix it and none of it has worked. I tried flashing the stock rom and it as well got stuck on boot. I looked at all the AT&t relevant ones and also the international versions. so all in all is there anyway to fix this and has anyone had the same issue? i was flashing from cyanogenmod 10 m1 to the drewgaren rom btw. I can also go to download mode. I tried to flash stock but it still gets stuck on boot. log. I flashed the ATT boot logo and it did not work. all of which were flashed through odin.
any thanks in advance is greatly appreciated.
I think you can flash back to stock with just download mode + odin
Randomacts said:
I think you can flash back to stock with just download mode + odin
Click to expand...
Click to collapse
I already tried that. It still get stuck on the Boot logo
stuart26 said:
I already tried that. It still get stuck on the Boot logo
Click to expand...
Click to collapse
I can't help you but I wish you luck.
stuart26 said:
I already tried that. It still get stuck on the Boot logo
Click to expand...
Click to collapse
Unplug your device. Hold the power button to turn it off. Hold volume up, home, and power. It should go to recovery. If you do the same thing with volume down instead of up, you can get into download mode.
Sent from my SAMSUNG-SGH-I747 using xda premium
Sounds like you need a recovery...try this
http://forum.xda-developers.com/showthread.php?t=1746665
[SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]
Follow the instructions and you should be able to flash the recovery and continue on with what you were doing. Remember to wipe really good when going from aosp back to any stock based ROM. They are completely different and will cause boot loops if you don't wipe.
jethro650 said:
Sounds like you need a recovery...try this
http://forum.xda-developers.com/showthread.php?t=1746665
[SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]
Follow the instructions and you should be able to flash the recovery and continue on with what you were doing. Remember to wipe really good when going from aosp back to any stock based ROM. They are completely different and will cause boot loops if you don't wipe.
Click to expand...
Click to collapse
I cannot enable usb debugging
Crap...there are Odin flashable versions of cwm floating around you'll need to find one of those. If you haven't found one I'll post one up when I get home.
jethro650 said:
Crap...there are Odin flashable versions of cwm floating around you'll need to find one of those. If you haven't found one I'll post one up when I get home.
Click to expand...
Click to collapse
K I made it home lol. I'll attach a Odin flashable cwm, it's an older one but it'll get you a recovery, I hope. I just tried it on my phone with Odin, 3.07 both with usb debugging enabled and disabled on my phone and it worked both times. Crap keep getting errors uploading right to xda servers, I'll drop box it in a minute.
Ok here we go Odin cwm--> https://dl.dropbox.com/u/28590257/Odin recovery/CWM-Recovery-LTE-SGS3-v4.tar.md5
Newest twrp --> https://dl.dropbox.com/u/28590257/Odin recovery/twrp2.3.1install.zip
I'll add the newest twrp for you lol. Flash the cwm with odin, should work and then the twrp is a zip you can flash in cwm.
Hope this helps get you a recovery.
Remember in Odin use only PDA and only have auto reboot checked.
jethro650 said:
K I made it home lol. I'll attach a Odin flashable cwm, it's an older one but it'll get you a recovery, I hope. I just tried it on my phone with Odin, 3.07 both with usb debugging enabled and disabled on my phone and it worked both times. Crap keep getting errors uploading right to xda servers, I'll drop box it in a minute.
I'll add the newest twrp for you lol. Flash the cwm with odin, should work and then the twrp is a zip you can flash in cwm.
Hope this helps get you a recovery.
Remember in Odin use only PDA and only have auto reboot checked.
Click to expand...
Click to collapse
This may sound like a stupid question but what boxes do i tick in odin?
After your hooked up and Odin is open under the options on the left side check only Auto Reboot. On the right under files check PDA and use that button to browse your computer and find the cwm you downloaded from my dropbox. Then just hit start on the bottom of the Odin window and let it finish, your phone should reboot when its done. It will get stuck again like you described in your first post but pull the battery, put it back in and boot into recovery using vol up,home and power buttons. That should (if everything flashed OK) put you into cwm 5.5.0.4. Once there wipe data/factory reset then restore the back up you mentioned in your original post, that should get you running again.
---------- Post added at 06:05 PM ---------- Previous post was at 05:55 PM ----------
If something has happened to your backup then you could try the stock rooted stuff here , just pick the one for your carrier and follow the instructions. :highfive:
jethro650 said:
After your hooked up and Odin is open under the options on the left side check only Auto Reboot. On the right under files check PDA and use that button to browse your computer and find the cwm you downloaded from my dropbox. Then just hit start on the bottom of the Odin window and let it finish, your phone should reboot when its done. It will get stuck again like you described in your first post but pull the battery, put it back in and boot into recovery using vol up,home and power buttons. That should (if everything flashed OK) put you into cwm 5.5.0.4. Once there wipe data/factory reset then restore the back up you mentioned in your original post, that should get you running again.
---------- Post added at 06:05 PM ---------- Previous post was at 05:55 PM ----------
If something has happened to your backup then you could try the stock rooted stuff here , just pick the one for your carrier and follow the instructions. :highfive:
Click to expand...
Click to collapse
I was able to get it into recovery but i realized i did not have my sd card in so i turned it off and put my sd card in. unfortunately i was not able to get it back into recovery i tried flashing it again with the sd card in and no luck
That's odd. Couple of stupid questions on my part just to make sure, you had the right button combo, and, you released the buttons soon as the splash screen came on? Can you still get into download mode? Oh and did you do the wipes while in recovery?
jethro650 said:
That's odd. Couple of stupid questions on my part just to make sure, you had the right button combo, and, you released the buttons soon as the splash screen came on? Can you still get into download mode? Oh and did you do the wipes while in recovery?
Click to expand...
Click to collapse
oh my gosh THANK YOU SOOOMUCH. I was worried i would have to take it to at&t ill be sure to press the thanks button.
I take it you got your phone working lol. Glad I could help a little. Little advice, anytime you switch to a different type of ROM (aosp to stock based or the other way around) make sure you wipe data/factory reset before flashing anything. It will save you problems in the long run.
Oh and could you go back and edit your original post and just add solved in brackets to the title for people in trouble looking for info.
stuart26 said:
I already tried that. It still get stuck on the Boot logo
Click to expand...
Click to collapse
Depending on which stock ROM you flashed with odin you should now have a recovery, if not then something isn't right. The full bone stock ROM should have the factory 3e recovery, and the root injected stock ROM should have some version of CWM recovery. A factory reset will most likely fix your boot loop, if there is no recovery flash the rooted stock ROM that matches your device from this guide.
Edit - Didn't see there was a second page 0_o
Hello,
I recently received the OTA update and accepted, however it messed up some apps and I went to flash a stock LJC firmware via ODIN. The issue I have is ODIN keeps failing at the sboot.bin portion. I was previously rooted using mrRobinsons root method (flashing a rooted .tar file). I can't enter recovery mode because the phone gives me the error message "firmware upgrade encountered an issue. please select recovery in Kies and try again." I'm not at all familiar with Kies and any help would be incredibly appreciated.
If you can get into download mode and use odin, then can you download twrp 2.4.1.0 tar and use it with the PDA button in odin? Un-check auto reboot in odin, then when flash ends and sitting there a few seconds, pull the battery, hold voldown home and power, and put the battery back in while holding all 3. (Yeah I know it requires a 3rd hand haha).
It should boot into new twrp.
The download for twrp is google twrp2, then select sprint gn2, then on the download page find openrecovery*2.4.1.0*.tar
If you can do that then you should be able to flash a kernel and rom and firmware from there by just putting them on the sd card. I would use the ma7 one and not try to go back to ljc at least until you get working again and get more comfortable with flashing and recovering from bad flashes like this. I would try the ma7 rom and all-in-one firmware zips not the ma7 update.zip in your case. The update.zip requires a stock recovery to run and possibly a stock everything else too.
Sent from my SPH-L900 using xda premium
---------- Post added at 12:18 PM ---------- Previous post was at 12:08 PM ----------
Remember don't wipe data. Flashing the twrp recovery, rom, kernel and firmware should be fine.
If you want to try something even safer just on the off chance your rom is ok just not bootable, you can try flashing just twrp and kernel snd see if it boots. If not then go back into twrp and flash the rom. The data may or may not be compatible with ma7 but nothing we can do about that. If the apps all crash then you could try flashing a ljc based rom and see if the data works on that. All else fails you may have to wipe data from twrp.
In all cases always wipe cache and dalvik from twrp each time you flash anything else.
Sent from my SPH-L900 using xda premium
Thanks for info but I can't seem to find a .md5 type file when I download the zipfile for twrp recovery. I try extracting and it's just an image file. Should I just select that as the PDA file to flash via odin? And I tried using Kies in the interim but my phone was stuck on the "connecting" animation when I plug my phone in.
Might be making progress... I'm working on an emergency recovery via Kies and it's about half way through. I really hope this at least lets me boot up the phone beyond just ODIN mode. Thanks for the help again KeyofR I'm going to keep searching for a md5 file of twrp recovery in the mean time.
EDIT: I think Kies is failing at the same part as ODIN when I tried to manually flash a LJC stock recovery (the sboot.bin portion). If anyone has a link to a md5 file of twrp recovery that would be awesome, I can't seem to find that type only "image" files.
EDIT #2: Bless you lol I just ran the actual .zip file in odin and it worked. I'm hoping I can just flash a stock rom I'll live with a complete wipe, I have everything important backed up. Thank you very much again!
What I said was grab the tar file not zip or md5. And don't unpack it. Just save it. In odin next to PDA browse an select that tar file. That will flash twrp to the recovery partition. You may need to do the crazy battery pull three finger salute battery insert thing to boot into twrp the first time. I don't know why that is, it just is sometimes. If you don't it tries to boot the regular os and if that succeds it somehow puts a stock recovery back and you have to flash twrp on again. Once you've booted into twrp one time, no more problem, just a one time thing.
Sent from my SPH-L900 using xda premium
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
How is this against the rules? I'm lost. Oh well
Sent from my Amazing Galaxy Note 2!
yankees45us said:
How is this against the rules? I'm lost. Oh well
Sent from my Amazing Galaxy Note 2!
Click to expand...
Click to collapse
It was posted in the development section.... Questions or ask for help go in q&a ... that's why its not a ROM or kernel ....
Sent from my SPH-L900 using Xparent BlueTapatalk 2
Where do I get twrp2 tar
Sent from my EVO using xda app-developers app
bigbird2 said:
Where do I get twrp2 tar
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
From the twrp website ... you shouldn't need it use goo manager to install it ...
When you open goo press menu and install open recovery script ...
Sent from my SPH-L900 using Xparent BlueTapatalk 2
Thanks!!!
I bricked my GN2 today for the first time....found your solution below within a few minutes of searching XDA and bam...Im back up.
Many thanks!
KEYofR said:
If you can get into download mode and use odin, then can you download twrp 2.4.1.0 tar and use it with the PDA button in odin? Un-check auto reboot in odin, then when flash ends and sitting there a few seconds, pull the battery, hold voldown home and power, and put the battery back in while holding all 3. (Yeah I know it requires a 3rd hand haha).
It should boot into new twrp.
The download for twrp is google twrp2, then select sprint gn2, then on the download page find openrecovery*2.4.1.0*.tar
If you can do that then you should be able to flash a kernel and rom and firmware from there by just putting them on the sd card. I would use the ma7 one and not try to go back to ljc at least until you get working again and get more comfortable with flashing and recovering from bad flashes like this. I would try the ma7 rom and all-in-one firmware zips not the ma7 update.zip in your case. The update.zip requires a stock recovery to run and possibly a stock everything else too.
Sent from my SPH-L900 using xda premium
---------- Post added at 12:18 PM ---------- Previous post was at 12:08 PM ----------
Remember don't wipe data. Flashing the twrp recovery, rom, kernel and firmware should be fine.
If you want to try something even safer just on the off chance your rom is ok just not bootable, you can try flashing just twrp and kernel snd see if it boots. If not then go back into twrp and flash the rom. The data may or may not be compatible with ma7 but nothing we can do about that. If the apps all crash then you could try flashing a ljc based rom and see if the data works on that. All else fails you may have to wipe data from twrp.
In all cases always wipe cache and dalvik from twrp each time you flash anything else.
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
I installed cwm rom manager without a root, but did not flash the phone and install everything. I uninstalled cwm rom manager, and then downloaded the cyanogen installer. Then I let cyanogen mod installer attempt to install cm10 on my t989, and the computer said the install finished and i should wait for the phone to reboot.
But instead of rebooting, it went into CWM Recovery and said something to the effect of: "root access was missing, would you like to root?" I clicked back, which was no and it rebooted into the stock os (ics) instead of cm10 and the home and search buttons didn't work. I tried to reset the phone, but that didn't work and I tried to flash into the stock recovery, but the odin program failed at "<ID:0/009> Can't open the serial(COM) port."
Thank you for your help!
Odin won't work if Kies is running. Kill all kies processes first in device manager.
Also, you need to be rooted properly. After flashing recovery in Odin....you have to flash SuperSU in recovery.
And don't use rom manager...a lot of bad luck stories from it.
Search on the guides to rooting and flashing custom ROMs for help.
---------- Post added at 07:56 AM ---------- Previous post was at 07:55 AM ----------
And before flashing anything, ever....you should be doing a nandroid backup in recovery....so you can restore it if anything goes wrong.