Hi a bit back I tried flashing my SGS2 with Cyanogenmod12 and it didn't go great. No boot loops or bricking but it was supposed to be an upgrade, a dirty flash (i think thats the term) so I thought ok, I will just do a clean flash by wiping everything buuuut, no go, I tried with the new recovery thingy that apparently came with CM12 and it is not seeing the zip for the rom or gapps. I then thought I'd try flashing a few recovery rom via fastboot then retry but I can't get ADB/fastboot to work now? More accurately I can't get the driver working to see my SGS2, on two different computers, tried this adb/fastboot package and this one.
Now I can't even remember what ODIN is or if it requires that the same drivers that ADB/fastboot do but is that even an option?
Any help would really really be appreciated because I am at witts end here as I have a near useless phone that totally doesn't have to be!
This thread contains every detailed step you can try when attempting the recovery of an S2......
http://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
If it ain't in that thread, it ain't worth trying....
http://i.imgur.com/rVnFwJM.jpg
Thanks, I will take a look at it and give them a try!
gaikokujinkyofusho said:
Thanks, I will take a look at it and give them a try!
Click to expand...
Click to collapse
Good luck fella.....My advice is to read through the first post in it's entirety BEFORE starting any of the processes, then pick out the parts that seem most appropriate/relevant to your case.....If that doesn't work, then work through every applicable step in order as many times as it takes to recover your device.....
Perseverance is the name of the game here....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Good luck fella.....My advice is to read through the first post in it's entirety BEFORE starting any of the processes, then pick out the parts that seem most appropriate/relevant to your case.....If that doesn't work, then work through every applicable step in order as many times as it takes to recover your device.....
Perseverance is the name of the game here....
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Well that worked! Kinda I think. I finally managed to get ODIN to work and flashed the 4.1.2 JellyBean leaked ROM so now I have what I think is a stock recovery. My next question is can I flash CM12 with that stock recovery or do I need to somehow put something like twrp on first then flash CM12?
Thanks (so much) again!
gaikokujinkyofusho said:
Well that worked! Kinda I think. I finally managed to get ODIN to work and flashed the 4.1.2 JellyBean leaked ROM so now I have what I think is a stock recovery. My next question is can I flash CM12 with that stock recovery or do I need to somehow put something like twrp on first then flash CM12?
Thanks (so much) again!
Click to expand...
Click to collapse
Unfortunately you can't flash *any* custom roms with a stock recovery.
The only thing you *can* flash using the stock recovery is PhilZ kernel which will root your phone and provide you with a custom recovery that you can use to flash a rom.......
Here's the thread link....
http://forum.xda-developers.com/showthread.php?t=1877270
Look for the version of the kernel that matches your current on device build and then look for the ZIP version of that kernel.....All the instructions are in the OP....
http://i.imgur.com/rVnFwJM.jpg
Related
Had the PBA replaced twice now and i just got the phone back without root. I need to get it rooted but no matter how googling or odin flashing nothing works. I can communicate with Kies and odin and thats working i just need the .tar's to get it done. Can someone provide the .tar's?
Sidenote: why wont dev's make odin flashable roms anymore? its a lot easier.
http://forum.xda-developers.com/showthread.php?t=1740367
Start here:
It's the full meal deal thread, and has eveything you will need...g
gregsarg said:
http://forum.xda-developers.com/showthread.php?t=1740367
Start here:
It's the full meal deal thread, and has eveything you will need...g
Click to expand...
Click to collapse
yeah no matter what i try odin gets stuck at boot.img.
yikes....
your the 4th person this week with that same issue.....
so the odin flash process wont complete ? or you have the stock recovery back after the reboot ?
Hi Guys,
Sorry to bother you with this, but I'm out of ideas...
I decided to root my i9100 using this guide9.
As I was doing this, the recovery rom would reboot when using the volume buttons to navigate (only on the first "page") - This was easily worked around by using the touchscreen, but now I'm wondering if this was the start of my issues...
I applied the SU busy box installer, and got root. I installed rom manager, and noticed that it seemed to lock up when doing certain things. I put this down to CWM saying there was no official mod for the i9100.
The next day I decided to try and install a CM10.1 nightly, so I took a backup, wiped cache and data, and applied the rom and gapps.
When I rebooted, the phone wouldn't finished booting, it just sat at the initial logo screen.
After that, I tried following this recovery guide but the odin flash failed at around 80% (I retried and the same happened again).
Since then I've had difficulty getting in to recovery mode. I've tried flashing various stock roms with odin, and trying to restore with Kies.
In Kies I get as far as it conencting to the phone in download mode, but it pops up a "notice" in a foreign language - presumably Korean (and I can't copy the text to even attempt a google translation).
I tried flashing Siyah-s2-v5.0.1 to get a different recovery - that seemed to have a garbled progress bar, before hanging when I tried to wipe /data again.
When I use odin to flash a stock rom - is it supposed to restore absolutely everything? I'm not sure how I'm still getting problems if this is the case. Any ideas on what to try next?
(The current stock rom I'm try ing to use is this one)
Let me know if I'm missing any info, and thanks in advance for any help.
Using rom manager would have been the start of your problems-not the temp cwm recovery in the rooting guide.
If you can boot into download mode then I would download LP7 stock rom, disable kies and flash that with Odin.
{go back to your iphone since you are an android noob}
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Silly Billy said:
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Click to expand...
Click to collapse
I9100 right?
Try this:
- Download this ROM.
- Kies installed? uninstall it, re install it. Close it all up with Task manager (3 or 4 applications running).
- Flash ROM via Odin (CSC, MODEM, PHONE).
- If that doesn't fly, try another usb port & usb cable. Another PC would also be recommended.
- Repeat the process.
- Still no luck? try flashing a previous siyah version.
- No go? repeat all the above.
- Let us know how you did.
gastonw;37017081- Download this ROM.[/QUOTE said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
As a matter of interest, how far did you go with Phistachios repair guide.
{go back to your iphone since you are an android noob}
Silly Billy said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
Focus on getting a ROM to boot.
That ROM will install stock recovery.
gastonw said:
Let us know how you did.
Click to expand...
Click to collapse
For some reason, I can't get Odin to flash that rom - it just hands for a while at the start of data.img, before saying "Complete(Write) operation failed."
There a .pit file in the archive, although the link says not to repartition (so I didn't).
Some roms seem to get written, some don't, I'm not sure why...
theunderling said:
As a matter of interest, how far did you go with Phistachios repair guide.
Click to expand...
Click to collapse
Odin failed about 80% through flashing (step 4, after taking the ICS steps). I tried flashing the kernel afterwards, which flashed, but didn't help with my boot issues.
gastonw said:
Focus on getting a ROM to boot.
That ROM will install stock recovery.
Click to expand...
Click to collapse
Of course, I was just trying to get a better understanding of how things work - I'd settle for anything booting right now.
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
theunderling said:
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
Click to expand...
Click to collapse
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
gastonw said:
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
Click to expand...
Click to collapse
I guess I'll keep at it then.
I'd tried another cable with kies shut down. Just tried a different machine, and flashed the ROM you suggested with heimdall. It flashed without complaining (unlike odin), but I'm still getting a boot loop.
Looking at the initial recovery guide I was following - I suspect that I might've flashed the bootloader (the guide shows in bold which file goes in which box, so I probably loaded them all). Maybe this is the source of my troubles...
I also noticed that heimdall can pull data from the phone too - if I can pull and mount these, am I likely to find any useful log files?
For completeness (and anyone else who finds themselves with the same issue): It seems I hit the EMMC brick bug, which rendered some of my EMMC storage unusable.
This helpful chap came up with a workaround to partition around the dead space. (Please read the post carefully and make sure this really is your problem before flashing!)
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Sent from the little guy
gastonw said:
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Click to expand...
Click to collapse
Yes, that's right. IIRC, I flashed a working recovery with Odin, then did most of the work from adb shell.
I got my device back to life for the most part. I get the occasional hang but haven't investigated much (have since bought a Nexus 4, so not using the S2 so much).
Just thought I'd share for the next poor soul who has the same problem
Hey guys.
I've searched the forums for this issue, unfortunately it seems like mine is a little unique and I can't find a solution to my problem anywhere.
I'm stuck in CWM Recovery mode, and although I can navigate the menu... when pressing the Home key to select the various options, nothing happens besides the options blinking for a sec. I can access Odin Mode with Power/Volume +/- but that's it. Also it's worth noting that I'm unable to access my phone's files from my computer when in download mode (my guess is because the phone isn't set to USB storage mode which I have to do from the booted home screen, which... I can't access).
This happened after the first time entering Recovery mode on CWM, and although I have ROM Manager installed on my phone, after researching a little I found that was NOT what I wanted to use. And I did NOT use that program.. my CWM was flashed in from a .tar on Odin (the windows program). I also have a Jellybam folder placed in the phone, which was my next step.
How can I get out of CWM Recovery so that I can continue flashing the Jellybam ROM?
I apologize if I've missed anything. Please let me know if you need any other information. I'll be sure to hit the thank you button on every reply.
THANK YOU!
:crying:
um....
you are supposed to flash the ROM from CWM, so why would you want to get out of CWM to get back into CWM?
you havent mentioned what version of Android you were already running or what kernel you flashed, but have you tried using the POWER button to select things in CWM? Are you sure you used the right kernel? Are you sure you have an i777?
Hey Pirateghost, thanks for the reply! And yes, I was going into CWM Recovery to flash the ROM. The reason I wanted out of CWM was because it had no functionality... yes, I did try using the power button to select things. Seems the home button was it? In any case nothing worked. My version of Android was Gingerbread UCKH7, and I'm %100 sure it's an i777. By using the "right kernel" you mean the right version of Jellybam?
UPDATE: I got out of the bootloop by using a stock root UCKH7 kernel, bringing it in from Odin. Now I'm just trying to understand what went wrong and how I can continue to flash my Jellybam ROM in without any issues. I also found that my CWM app disappeared after I uninstalled ROM Manager after getting access back to my phone.
More info...
the kernel I installed for CWM was KH4 at this thread: http://forum.xda-developers.com/showthread.php?t=1103399
After putting the KH7 stock root kernel in via Odin and getting out of the bootloop, I deleted ROM Manager off my phone and reflashed the KH4 kernel so I could get CWM. That worked fine, but now Superuser is crashing.
??
xargis said:
More info...
the kernel I installed for CWM was KH4 at this thread: http://forum.xda-developers.com/showthread.php?t=1103399
After putting the KH7 stock root kernel in via Odin and getting out of the bootloop, I deleted ROM Manager off my phone and reflashed the KH4 kernel so I could get CWM. That worked fine, but now Superuser is crashing.
??
Click to expand...
Click to collapse
The kernel you just linked above is for the GT-I9100, not the SGH-I777. You seem to be moving forward without providing yourself with enough knowledge. If you are sure the phone is an I777 then stay away from the I9100 forums. Get what you need from here. There is lots of information in the guides linked in my signature. There is enough information there to guide you through everything you want to do.
xargis said:
More info...
the kernel I installed for CWM was KH4 at this thread: http://forum.xda-developers.com/showthread.php?t=1103399
After putting the KH7 stock root kernel in via Odin and getting out of the bootloop, I deleted ROM Manager off my phone and reflashed the KH4 kernel so I could get CWM. That worked fine, but now Superuser is crashing.
??
Click to expand...
Click to collapse
You are flashing an older kernel on a newer ROM??? why? if you want to have CMW recovery you should flash your stock rom and then get the CWM .tar file and flash it in Odin. If you happen to get a .zip CWM file you can rename it to update.zip and flash it using your stock ROM's recovery options.
Search something along these lines: CWM5.8.1.8-i777.zip or recovery-clockwork-5.0.2.3-galaxys2att.tar as examples
creepyncrawly said:
The kernel you just linked above is for the GT-I9100, not the SGH-I777. You seem to be moving forward without providing yourself with enough knowledge. If you are sure the phone is an I777 then stay away from the I9100 forums. Get what you need from here. There is lots of information in the guides linked in my signature. There is enough information there to guide you through everything you want to do.
Click to expand...
Click to collapse
WOW! I don't know how I missed that. Must pay more attention to detail...
Thank you so much for pointing that out Creepyncrawly!
Commodore 64 said:
... If you happen to get a .zip CWM file you can rename it to update.zip and flash it using your stock ROM's recovery options. ...
Click to expand...
Click to collapse
It's great having new folks around helping out.
This is bad information, however. 3e recovery will enforce signature verification on any update.zip, and it will fail.
creepyncrawly said:
It's great having new folks around helping out.
This is bad information, however. 3e recovery will enforce signature verification on any update.zip, and it will fail.
Click to expand...
Click to collapse
always a pleasure to lend a hand. you're right it used to work on 2e I think, I was trying to signify the difference between the zip and tar, but thank you so much for the correction.
So should I be using a different kernel? I'm sorry I'm not quite sure what you're saying Commodore64, my head has been spinning from all this.
xargis said:
So should I be using a different kernel? I'm sorry I'm not quite sure what you're saying Commodore64, my head has been spinning from all this.
Click to expand...
Click to collapse
you should be using a kernel intended for your phone....your phone (if branded AT&T) is either an i727 skyrocket or i777. this is the i777 forum section. you appear to have flashed a kernel for an i9100...
just follow creepy's guides and do it the right way. there is nothing you can flash in STOCK recovery that will give you CWM or a new kernel (which on this phone CWM is packed with the kernel)
xargis said:
So should I be using a different kernel? I'm sorry I'm not quite sure what you're saying Commodore64, my head has been spinning from all this.
Click to expand...
Click to collapse
There is not just one answer, you can go back to one of the stock ROMs, like the ones provided by creepyncrawly threads.
There are a lot of threads on this and I don't have my I777 anymore but I used to do this:
1- Once you flashed a stock rom, go into recovery and cleanup. data/cache reset.
2- Have the files you want to flash on your phone. (if you format the SD card you will erase your files including the ones you want to flash!)
3- Use your .tar Odin CWM that worked for you before now to flash CWM.
4- Once in the CWM flash a newer CWM version (CWM6.0.1.0-i777.zip) since your ROM is based on CM/AOKP
5- After flash Go to Advanced and reboot recovery (this will reboot your phone now with the newer version of CWM)
6- Once in the newer CWM clean up again.
7- Don't reboot, have the correct version (latest or whatever) of your Custom ROM and install it now.
This is the general idea, if you don't know what you're doing read the threads in the development section, everything you need is there.
Educate yourself before you make your phone a crippled rabbit and scream for help.
Commodore 64 said:
There is not just one answer, you can go back to one of the stock ROMs, like the ones provided by creepyncrawly threads.
There are a lot of threads on this and I don't have my I777 anymore but I used to do this:
1- Once you flashed a stock rom, go into recovery and cleanup. data/cache reset.
2- Have the files you want to flash on your phone. (if you format the SD card you will erase your files including the ones you want to flash!)
3- Use your .tar Odin CWM that worked for you before now to flash CWM.
4- Once in the CWM flash a newer CWM version (CWM6.0.1.0-i777.zip) since your ROM is based on CM/AOKP
5- After flash Go to Advanced and reboot recovery (this will reboot your phone now with the newer version of CWM)
6- Once in the newer CWM clean up again.
7- Don't reboot, have the correct version (latest or whatever) of your Custom ROM and install it now.
This is the general idea, if you don't know what you're doing read the threads in the development section, everything you need is there.
Educate yourself before you make your phone a crippled rabbit and scream for help.
Click to expand...
Click to collapse
this makes no sense, dude.
1. if he is on a stock rom, there is nothing CM/AOKP on his phone
2. on this device the recovery is packed with the kernel, flashing some other CWM doesnt really matter at all. none of this is necessary.
you can flash any kernel you want (made for this device) if you dont plan on booting the OS and only plan on flashing a rom...
you have now complicated an already easy method.
Hey everyone - just wanted to let you guys know that I am now running JellyBAM and so far everything seems fine.
Thank you all for your help, seriously. If anyone has any questions about what I did etc., just ask and I'll get back to ya.
Thanks! :good:
Glad to hear you got JellyBAM up and running xargis, and just to reiterate what pirateghost was saying, you won't get CWM by flashing a CWM.tar file lol, I don't even think one can be found for this model (SGH-i777) which is the device that I currently have, the ONLY way to get CWM onto this device is to flash the proper kernel for this device, but keep in mind that there is another factor to think about as well, depending on what type of custom rom you want to run there are different kernels out there that work best and offer different/better features for deployment into the custom rom for which you will be running, in other words some roms are kernel specific, you can only use certain kernels with CM10/AOKP/ParanoidAndroid based roms, and such is the same with only using certain kernels with Sammy based stock roms, so the choice is yours, hope this info was informative to you and that you definately find a good productive rom that you will be happy to play with and run, have fun with your i777 s2, that's one of the things this forum is all about!!
Hi I tried to root my phone using this method ( http://forum.xda-developers.com/showthread.php?t=1504218 ) and it left my phone stuck on the reboot. I then tried to flash the stock kernel via odin, and when that didn't work I flashed cwm via odin and then a rogers kernel through cwm and it is still stuck on the rogers logo.......?
could someone help me......?
AirForce 1 said:
Hi I tried to root my phone using this method ( http://forum.xda-developers.com/showthread.php?t=1504218 ) and it left my phone stuck on the reboot. I then tried to flash the stock kernel via odin, and when that didn't work I flashed cwm via odin and then a rogers kernel through cwm and it is still stuck on the rogers logo.......?
could someone help me......?
Click to expand...
Click to collapse
I see your post count and realize you cannot post in the development section yet. that should not however stop you from reading. maybe you have but you may not have read the whole thread. i know that may seem like a daunting task, it is for me. so what I o is go to the most recent post or last page and start reading backwards. that way I get the most up to date information even on an older thread as you are referring to.
if you did that you would have seen a post from AGOATTAMER.
http://rootgalaxynote.com/galaxy-note-i717-roms/how-to-root-att-galaxy-note-sgh-i717-icsgingerbreadeasiest-method/
this is also the method I used. believe me, if I can pull it off, anybody can.
more tips..............
make sure you have all the files you need
rehearse the process
I know it sounds crazy, but these phones aint cheap and if you mess it up, can be pretty screwed.
so what is more valuable???? your phone or acting crazy and talking to yourself for a few minutes.
if you can still get download mode, your good, no brick
good luck
You flashed an older incompatible kernel with a newer ROM, but I guess you know that now. Flash the stock ROM found here using odin.
http://www.hotfile.com/dl/213010140/75bf7e2/I717RUXMD1_I717RRWCMD1_RWC.zip.html
Go into recovery after install and do a factory reset. Then start over. Many have used the link that captemo has mentioned. There are newer versions of recovery than the one listed on that site but it will get you rooted. Look at this thread also. Since you are installing the stock ROM via odin you will not have to deal with the script mentioned here.
http://forum.xda-developers.com/showthread.php?t=2485336
Just flash twrp with Odin, don't reboot into android, not directly into recovery after the flash finishes...
In recovery wipe data/factory reset.
When you go to boot it'll see you're not rooted and ask if you want to.
The easiest method to root.
Edit: note to self
Self,
check links before posting to avoid repeating yourself
studacris said:
Edit: note to self
Self,
check links before posting to avoid repeating yourself
Click to expand...
Click to collapse
Good advice is always worth repeating.
Sent from my Big Ass Outlaw Phone.
I was rooted on a stock rom with n9005 CWM for kitkat. I tried flashing the deodexed version for wifi tether. I didnt realize i needed odexed instead. now i am stuck on the sprint screen upon reboot. i tried using odin to reflash that rom again as well as a Cf auto root. both flashed but still stuck on the same screen upon reboot. I then tried to wipe and clear all data and cashe as well as factory reset from recovery mode. still the same issue. ANY help will be appreciated.
NOTE: i looked for 3 days for help on XDA as well as other sites and can not find anything specific to my case, or anything that will work. Please if you offer help include links as i have searched for everything i could think of.
Have you tried to get the stock tar file and use that in Odin? That would bring you back to complete stock.
is this it
i downloaded this SM-N900P_NAB_Stock_Bootloader.tar.md5 from rwilco12's android repository
is this what you are referencing? or is there a different stock file you are refering to?
is this it?
DarkManX4lf said:
Have you tried to get the stock tar file and use that in Odin? That would bring you back to complete stock.
Click to expand...
Click to collapse
i downloaded this SM-N900P_NAB_Stock_Bootloader.tar.md5 from rwilco12's android repository
is this what you are referencing? or is there a different stock file you are refering to?
I meant this one
http://forum.xda-developers.com/showthread.php?t=2712205
twrigh5 said:
i downloaded this SM-N900P_NAB_Stock_Bootloader.tar.md5 from rwilco12's android repository
is this what you are referencing? or is there a different stock file you are refering to?
Click to expand...
Click to collapse
First, let's diagnose what's wrong, to see what you need to do to fix it.
Flashing a DeOdex Mod onto an Odex ROM.
This will mess up your system files. What you'll most-likely get is a bootloop (or stuck at startup, which is where you're at). When this happens, you should be able to still access Recovery and Download Modes. This is good news! This means you have many options to fix your phone.
Possible solutions for your problem.
Restore a backup in Recovery.
The first rule when flashing ROMs/Mods is that you read and understand the thread first.
A close second rule is to make a backup before flashing anything.
I doubt that you have a backup, since that would've been the first thing you would've tried. That's ok, we just have to do a little more work to get your phone fixed.
Reflash the custom ROM in Recovery
This doesn't apply to you too much, because you weren't running a custom ROM, just a rooted stock ROM, but I think it's good for others who might have a similar problem. If you had a bootloop issue, you can always re-flash the ROM in recovery. I'd just recommend wiping data, cache, dalvik cache, and system prior to flashing the ROM.
Reflash the Stock ROM in ODIN.
This is the last-case scenario. I'd go to this thread that micmars wrote and follow his instructions very carefully. Doing this should get your phone back to stock. Then I'd re-do the rooting like you did originally (make sure you're using the kit-kat instructions.
Once you get your phone back and running (and rooted), the first thing I'd recommend is to create a nandroid backup in recovery. This will be your life-saver whenever something gets messed up.
Hope this helps!
EDIT:
I figured that I should give you a reason why the CFAutoRoot didn't work for you:
CF Auto Root only modifies certain files. It's not flashing an entire rooted ROM onto your phone, it's just selectively modifying/replacing files so that you have root access. So, when the system is messed up due to flashing a incompatible Mod, CF Auto Root is not likely to fix those issues. Only flashing a stock Rom, like DarkManX4lf suggested.
topherk said:
First, let's diagnose what's wrong, to see what you need to do to fix it.
Flashing a DeOdex Mod onto an Odex ROM.
This will mess up your system files. What you'll most-likely get is a bootloop (or stuck at startup, which is where you're at). When this happens, you should be able to still access Recovery and Download Modes. This is good news! This means you have many options to fix your phone.
Possible solutions for your problem.
Restore a backup in Recovery.
The first rule when flashing ROMs/Mods is that you read and understand the thread first.
A close second rule is to make a backup before flashing anything.
I doubt that you have a backup, since that would've been the first thing you would've tried. That's ok, we just have to do a little more work to get your phone fixed.
Reflash the custom ROM in Recovery
This doesn't apply to you too much, because you weren't running a custom ROM, just a rooted stock ROM, but I think it's good for others who might have a similar problem. If you had a bootloop issue, you can always re-flash the ROM in recovery. I'd just recommend wiping data, cache, dalvik cache, and system prior to flashing the ROM.
Reflash the Stock ROM in ODIN.
This is the last-case scenario. I'd go to this thread that micmars wrote and follow his instructions very carefully. Doing this should get your phone back to stock. Then I'd re-do the rooting like you did originally (make sure you're using the kit-kat instructions.
Once you get your phone back and running (and rooted), the first thing I'd recommend is to create a nandroid backup in recovery. This will be your life-saver whenever something gets messed up.
Hope this helps!
Click to expand...
Click to collapse
Thanks for your fast response. Im sure as soon as the file downloads i will be just fine. Thanks again!
DarkManX4lf said:
I meant this one
http://forum.xda-developers.com/showthread.php?t=2712205
Click to expand...
Click to collapse
the download isnt working right now, but maybe it will in a few. if you know of another link id appreciate that, if not then thanks again for all youre help thus far and i will just wait and hopefully it works.
Hmm the link wasn't working either earlier this week. Try posting in the thread or messaging mcmars.
twrigh5 said:
the download isnt working right now, but maybe it will in a few. if you know of another link id appreciate that, if not then thanks again for all youre help thus far and i will just wait and hopefully it works.
Click to expand...
Click to collapse
I'm able to download it at home (currently at 10%). I'll upload it to Dropbox when it's done and PM you the link.
topherk said:
I'm able to download it at home (currently at 10%). I'll upload it to Dropbox when it's done and PM you the link.
Click to expand...
Click to collapse
thanks a lot!
twrigh5 said:
thanks a lot!
Click to expand...
Click to collapse
My upload speed is atrocious, so it might be a few hours (it's a large file!)
How did the OP make out? Let us know.
topherk said:
My upload speed is atrocious, so it might be a few hours (it's a large file!)
Click to expand...
Click to collapse
it stuck on the yellow screen for like 3 minutes and i was sad.... than it worked! THANKS SO MUCH!!!! it all worked greatly. i appreciate everyones help!
Yeah. On a full stock Odin flash, things need a little longer to initialize and set up at the first boot. Even after you boot up completely, it takes awhile for everything to finish and settle down.