• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Need help!!!

D

darkster13

Lurker
Ok, so i was trying to update my epic 4g to clockworkmod to v3.0.0.5 by rerooting. idk what happend that when it finished my epic just got stuck in the samsung boot screen. I tried to restore it, but when it finished it still gets stuck at the boot screen. i can go back into the clockworkmod but only that, also i can't seem to put my device into download mode, please someone help!
 
Well i will do my best, cant promise anything. Still cant get to the bootloader at all? If not i have read where people have been there and taken out their battery for a few hours to a day and tried it and were able to get the bootloader. But before that can you get into recovery? If so what one, the green 2.5 cwm or orange 3.0.5 cwm or the blue stock?
 
rounsy222 said:
Well i will do my best, cant promise anything. Still cant get to the bootloader at all? If not i have read where people have been there and taken out their battery for a few hours to a day and tried it and were able to get the bootloader. But before that can you get into recovery? If so what one, the green 2.5 cwm or orange 3.0.5 cwm or the blue stock?
Click to expand...

Thank you! Yeah i can get into recovery, its orange 3.0.5 cwm
 
Ok do you have any ext 4 roms on your card? If not i would load one onto it. Then in either scenario try wiping cache, data(factory reset) and dalvic cache 3x each and flashing the rom.
 
rounsy222 said:
Ok do you have any ext 4 roms on your card? If not i would load one onto it. Then in either scenario try wiping cache, data(factory reset) and dalvic cache 3x each and flashing the rom.
Click to expand...

will do, going to download ViperROM [TRiNiTY v2.0] EXT4-RFS DK28 Dual 4.0.4
i already wiped the everything else.
 
rounsy222 said:
I have brought myself back a few times this way (fingers crossed)
Click to expand...

Did that with my brother's Epic today. It wouldn't reboot. Got back to recovery screen and flashed the Frozen ROM. The first flash didn't take, but flashed again and it worked like a charm!
 
rounsy222 said:
Pardon the pun here but epic feeling eh? Lol
Click to expand...

Ummmmm...yah! He just got his phone yesterday...when it was hung up on the Samsung screen and wouldn't go back to recovery I was thinking I was going to be buying him a new phone.

What's weird is his phone came with 2.2.1 so I don't know if they put it on the phone for him or what, but I think that may have been part of the problem. I actually had to Odin his phone and re-root. What was very strange is that after Odin he still had 2.2.1 on his phone. I'm pretty sure mine went back to 2.1 after Odin, unless my memory is failing me.

At any rate, after re-root instead of rebooting I wiped all data, cache, etc and flashed the ROM. It didn't take so went back to recovery, reflashed and bingo...done!
 
Droid newb, depends on what tar you put into odin. If you are like me i have multiples laying around and i catch myself sometimes putting the wrong one in there. I almost put an old moment one in a few weeks back and that would have been a for sure insta brick! And that is just odd that it came with 2.2 on it since they pulled the update.
 
rounsy222 said:
Droid newb, depends on what tar you put into odin. If you are like me i have multiples laying around and i catch myself sometimes putting the wrong one in there. I almost put an old moment one in a few weeks back and that would have been a for sure insta brick! And that is just odd that it came with 2.2 on it since they pulled the update.
Click to expand...

I used the only .tar file I had. :headscratcher:
 
Lol, dunno man. Atleast you were able to save your brothers phone. Everytime i get to that point i always tell myself never again, then i just do it all over again. This is my "crack" and can never get enough of it. :-)
 
You must log in or register to reply here.
Back
Top Bottom