how come roms dont like me? - Epic 4G Q&A, Help & Troubleshooting

i got a new epic from assurion so it had nothing on it so i odined el30 flashed su odined acclaim and that was it then i put A rom on top of it ( the peoples rom ) and as usual it lags and doesn't open up things for up to a minute . i have always had problems with roms. what can i be doing wrong? are these the correct steps? are they incompatibility issues? or is el30 not stable yet. any help woiuld be appreciated. i really like using your masterpieces but i seem to have issues wit all of them, so clearly its me. thanks

If you don't like aosp but want stock rooted, Odin el30 ( victory pit in pit section, el30 .tar in PDA section, only have auto reboot checked), then OTA to fc09 then Odin cwm 5.x ( pit in pit section, cwm .tar in PDA section, leave everything unchecked), pull battery when Odin finishes, boot cwm, flash su.zip, boot fc09, use es file explorer(free in play store) launch es, navigate to settings> check use root explorer, grant su, check mount /system, delete /system/etc/ recovery-install.sh (or something like that to disable the script from reinstalling the stock recovery.) , Odin cwm again and your good.
Edit: or an easier way would be to Odin cwm once and flash this lol http://forum.xda-developers.com/showthread.php?p=24419155
Sent from my cm_tenderloin using Tapatalk 2 Beta-5

Also download Spare Parts and set Window and Transition Animations to FAST. You would be surprised at the difference that makes. You will lose CRT off but with that speed, who cares...LOL.

ok this was a bit much for me. i dont need stock rom i dont care about anything. i just thought i had to odin to start fresh . all id like is whatever it takes to get peoples rom (for instance) to work on my phone. btw, i can not even get the screen to turn back on now without pulling the battery. i can follow the directions but i was hoping for something alittle more simple. if thats not possible i will try to figure out those directions

Unfortunately Samsung's Gingerbread update killed the one click root option so Odin is needed to at least put on a custom recovery and then install a prerooted ROM.
Sent from my SPH-D700 using xda premium

ok i apologize i was half alseep when i read the first reply, so i opted for the second option and odined \cwm-5.0.2.7-epic4g.tar.md5
i also have a cwm 3.1.0.1
should i have used that? i usually do the acclaim in odin but i just odined the cwm but when i went into recovery of course the deoxed fc09 didnt work because it wasnt rooted but the su.zip doesn't show up on my sd card in recovery. it always does when i odin acclaim. what am i doing wrong?

When you odin cwm 5, uncheck reboot. Odin will complete but your phone will still have the triangle showing. Disconnect the cable, pop battery out and in, 3 finger salute into cwm5 and flash The People's Rom. That will put you on MTD. Then if you don't like that you can flash the deodexed FC09 from there.
Sent from my PantechP4100 using xda premium

Listen, I think most of the devs in this community work really hard to put out some great ROMS. The insight they have given me is much appreciated. But now that I've said that, here is my answer to your original question.
I have yet to use a ROM that is as reliable as stock ROMs. If you read the threads about each ROM you will see lots of comments like:
"Wow, this ROM is awesome. It's absolutely perfect.....also, sometimes my speaker doesn't work, and the system panel FCs all the time, but THIS ROM is PERFECT! Thanks".
See my point? People get religiously attached to their favorite ROMs and easily ignore the problems to avoid admitting that they aren't using the hot sh*t.
I've tried lots of ROMs, but I always end up going back to a lightly modified stock ROM because for me reliability is the number one item with me. I have yet to find one dev's ROM that doesn't have a fatal flaw, IMHO.

gorelow said:
ok i apologize i was half alseep when i read the first reply, so i opted for the second option and odined \cwm-5.0.2.7-epic4g.tar.md5
i also have a cwm 3.1.0.1
should i have used that? i usually do the acclaim in odin but i just odined the cwm but when i went into recovery of course the deoxed fc09 didnt work because it wasnt rooted but the su.zip doesn't show up on my sd card in recovery. it always does when i odin acclaim. what am i doing wrong?
Click to expand...
Click to collapse
this might help some ...look below

Related

[Q] Need help with CWM Recovery and other issues!

Hello All,
I have been working with my friends EPIG 4g phone for a while now. The first thing I did was use "superoneclick 1.7" to root his phone. Then he got interested in trying different roms+kernels, so he came to me for more help. Almost all the custom roms I was researching are EC05 based roms, so I looked further into it. For reasons unknown, he is still on DI18 Eclair (must not have got the OTA). I dug on forums and found the zip file that would allow him to jump from DI18 to EC05 (froyo), but I need a custom recovery to install the zip. No matter what I try, I cannot get the phone to boot into CWM recovery. (Tried both from rom manager, and using camera button+vol. down+power combination) I have tried just about everything that I can think of, to no avail.
I have also tried:
Unroot & Re-root using process found here:
http://forum.xda-developers.com/showthread.php?t=770388
Wiping all data via factory reset (really wish I wouldn't have, waste of a try)
Tried using methods found here:
http://forum.androidcentral.com/epic-4g-rooting-roms-hacks/34603-clockworkmod-recovery-rom-manager-guide.html
When trying to do anything in the stock recovery, I always get the:
e:signature verification failed errors.
Please bombard me with any and all ideas you guys have. I am currently about to try to manually install the CWM recovery by placing the update.zip file on the SD root directory. IF I can get that part done, I'm confident I will be able to get everything going. Another option I have read from other people's threads that I have not yet used is the Odin revert to stock and then flash some special .tar files. I took a look at Odin and don't remember seeing options for "stock" or anything, so if anyone can point me to a good Odin walk-through, that would be awesome.
PS: Ask me if I have failed to clarify on any aspects of the problem. Forgive me for not including more info on the problem, Ive been through like 8 hours of random stuff while trying to fix this, so Ive seen too much to remember everything I've seen.
Thanks in advance!
-Clarity
Too many words
I kinda fell a sleep in the middle so yeah
If you want to return too stock use odin
If you want to go to froyo from eclair use odin
If you want cw use I've of the one click rooters
Going to cw is just pressing every button that is not on the keyboard
(power + volume up + volume down + camera)
Sent from my SPH-D700 using XDA Premium App
Stock recovery will get you nowhere on this phone, and with all you have tried so far, I believe Odin is the best course of action. Here is a link to the Odin package-
http://www.mediafire.com/file/fn9s5cqkkwyu68d/Odin3+v1.61andepic.pit.zip
Unzip it to a folder on your desktop.
The necessary drivers and instructions for using it are here in the wiki
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SPH-D700#Odin_Stock_Flashing
Follow the instructions carefully and be sure the drivers are installed before starting. Obviously, wherever it mentions the DI18 tar, you will use the current one in it's place. You can use this one, it's pre-rooted and de-odexed.-
http://forum.xda-developers.com/showthread.php?t=1021305
That tar file is still RFS file system so you will need to install CWM 3.0.0.6 and boot into it with the 3 finger solute so it can convert the file system to ext4. Package and instructions here-
http://forum.xda-developers.com/showthread.php?t=897612
If you made it this far you should be able to install one of the current ROMs you've been shopping for.
Thanks for the responses guys, I will try that out when I get a chance. Might be a while though because I don't see my friend that often.
So I was able to use Odin and successfully flash the EC05 .tar. However, I was unable to flash the Syndicate Frozen ROM that my friend wanted. It seems to fail on the flashing kernel step, some blue text that is large and out of place shows up for a second, and it goes back into the recovery menu. When I try to reboot the phone, it is clear that it did not work (assuming the kernel install is failing). I am going to Re-flash the EC05 for now, but do you guys have any recommendations for ROM+Kernel combinations good for battery/performance? Link me up if you know of any good combo's, but I've researched it a bit myself as well.
Basically, I would like to know what I am doing wrong here. Is the CWM included from that .tar file compatible & ready to flash any custom ROM that I want? Or do I need to use that CWM 3.0.0.6+root that Mattalica suggested? The EC05 was prerooted, so I'm wondering what happens if I use the 3.0.0.6 exploit on top of this root... Let me know guys.
onlyclarity said:
So I was able to use Odin and successfully flash the EC05 .tar. However, I was unable to flash the Syndicate Frozen ROM that my friend wanted. It seems to fail on the flashing kernel step, some blue text that is large and out of place shows up for a second, and it goes back into the recovery menu. When I try to reboot the phone, it is clear that it did not work (assuming the kernel install is failing). I am going to Re-flash the EC05 for now, but do you guys have any recommendations for ROM+Kernel combinations good for battery/performance? Link me up if you know of any good combo's, but I've researched it a bit myself as well.
Click to expand...
Click to collapse
What happend when you rebooted that indicated it was not successful? If you had strange vibrations and a bootloop, that is common when trying to flash these new generation ROMs like ACS and Bonsai. A simple reflash usually fixes it.
Sent from my SPH-D700 using Tapatalk
The Syndicate one failed as the kernel step was happening, resulting in a complete ROM failure (syndicate frozen tries to install their kernel midway thru the ROM flash). I tried it more than once, with no success. It just kept failing at kernel and only letting me into the CWM recovery (probably had already erased the base ROM?)
I was able to flash Baked Snack 1.6 without trouble and he is going to try that out for now. Interestingly enough, I did try to flash the baked snack "step 2" kernel, which is supposed to be a bit better on the battery life, and guess what happened mid install: the same weird black screen with huge blue text that goes off the screen (I think it says it fails, not sure though).
Here's the kicker on that, the "about phone" section does say that the base-band is something like "baked snack 1.6 step 2", which is odd, but the kernel version section seems to boast the same kernel version number that it had before. This leads me to think that it may have worked, but again, I cannot be 100% sure. If you have any more comments/suggestions, feel free to keep posting. Thanks again for all your help with the Odin TAR stuff, I really didn't feel confident until you confirmed the method.
onlyclarity said:
The Syndicate one failed as the kernel step was happening, resulting in a complete ROM failure (syndicate frozen tries to install their kernel midway thru the ROM flash). I tried it more than once, with no success. It just kept failing at kernel and only letting me into the CWM recovery (probably had already erased the base ROM?)
I was able to flash Baked Snack 1.6 without trouble and he is going to try that out for now. Interestingly enough, I did try to flash the baked snack "step 2" kernel, which is supposed to be a bit better on the battery life, and guess what happened mid install: the same weird black screen with huge blue text that goes off the screen (I think it says it fails, not sure though).
Here's the kicker on that, the "about phone" section does say that the base-band is something like "baked snack 1.6 step 2", which is odd, but the kernel version section seems to boast the same kernel version number that it had before. This leads me to think that it may have worked, but again, I cannot be 100% sure. If you have any more comments/suggestions, feel free to keep posting. Thanks again for all your help with the Odin TAR stuff, I really didn't feel confident until you confirmed the method.
Click to expand...
Click to collapse
BakedSnack 1.6 is a RFS ROM and is DI18 based. If you installed CWM 3.0.0.6, it would have converted your filesystem to EXT4. BakedSnack 1.6 does not have kernel support for EXT4. However if you installed an older version of CWM it would explain how ACS failed to install and how BackedSnack 1.6 was able to install and boot.

Question re Clockword Mod Update for Samsung Epic

I tried to post this on the actual thread about this Update, but I was not allowed because I had not posted 10 times previously.
Anyway, I am new to rooting Android phones….new to android phones for that matter. I have had the Samsung Epic 4G for about a month. I have been looking into rooting the phone, finally decided to go for it. I downloaded the filre for Clockwork Mod version 3.0.0.5/6 - UPDATED FOR EB13 from this site. After doing one run of that bat file and getting stuck on the startup screen, I realized I needed to find a compatible ROM and Kernel and install them before rebooting.
I reset the phone to default settings, using the info on http://forum.xda-developers.com/showthread.php?t=909384 and then I used the kernel
from the original update thread, Default Stock Dual FS kernel For EB13, and the Bonzai ROM from their website. This time, the install worked properly, and when my phone rebooted, the firmware is listed as Bonsai/Kernel_v4.01. So I wanted to backup and uninstall some Samsung Bloatware from the phone,and as I understand it, the Titanium Backup is the best way to do it. Well, I installed it, and it has consistently said the program could not acquire root status. I clicked on the “problems” icon, got busybox and upgraded superuse, and that did not effect anything. I even reflashed the Bonzai Rom, but the end result is the same, I am still getting that same message. Since I have replaced my Rom and have installed Superuser, I have to assume I have rooted the phone, so what could be the problem here? The app SetCPU also says I do not have Root Access. So I am not sure what to do at this point.
Sounds like a failed root:
Root again with the oneclick 3.0.0.6, power off, 3 finger boot and ext4 will be put on automatically. After ext4 installs install bonsai before rebooting.
Sent from Bonsai 7.0.3
Is there a difference between onclick 3.0.0.6 and the one in the thread http://forum.xda-developers.com/showthread.php?t=897612,which is labelled 3.0.0.5/6? Because, if not, that is pretty much what I have done already.
Same one.
I would odin to eb13, odin ec05 modem, root, boot to recovery and allow ext4, flash bonsai 4.0.1. Can't remember if 4.0.1 adds ec05 modem during flash, but if it does you can skip the ec05 odin (sorrry, but my mind has been on 4.1.0 for the last week).
The odin process will get rid of the kernel you currently have. Flashing the rom doesn't do anything to the kernel. The odin process will give you a nice clean slate to workv with. If your phone wants to do an ec05 OTA update during this process please tell it later and don't do it.
Suggest you peruse the Bonsai Forum as you will find a lot of treats that will be able to help you. Http://www.bonsaigeeks.com
Sent from Bonsai 7.0.3
Top Nurse said:
Same one.
I would odin to eb13, odin ec05 modem, root, boot to recovery and allow ext4, flash bonsai 4.0.1. Can't remember if 4.0.1 adds ec05 modem during flash, but if it does you can skip the ec05 odin (sorrry, but my mind has been on 4.1.0 for the last week).
The odin process will get rid of the kernel you currently have. Flashing the rom doesn't do anything to the kernel. The odin process will give you a nice clean slate to workv with. If your phone wants to do an ec05 OTA update during this process please tell it later and don't do it.
Suggest you peruse the Bonsai Forum as you will find a lot of treats that will be able to help you. www.bonsaigeek.com
Sent from Bonsai 7.0.3
Click to expand...
Click to collapse
This exact thing happened to me after trying everything from the EC05 OTA. Just run the bat file again on the phone...nothing else and it will work fine.

CWM Freeze on reBoot, Odin no Dice

When I tried to switch from ACS EI22 4 to 5 my phone force close looped because of some issue with launcher pro. I went to reflash the rom from CWM and ever since my phone won't properly load roms from CWM. When the phone has a custom rom it boots right to CWM when I power them up only to freeze again when I try to boot the rom from recovery.
I have Odined to stock EC05, and one click flashed CWM. I have flashed pre-rooted EC05 roms. I Odined to EI22 & EC05 modem Tar and went on to install ACS recovery over CWM.
I have Odined multiple times on multiple stock roms and custom roms. The problem persists. Once I'm in recovery (I've tried 3 versions) and I click "reboot" the phone locks with a black screen with the home buttons on or an image of the clockwork logo (depending on which version I'm trying).
The strange thing is, all of the stock roms work just fine and I was able to install EI22 from OTA with no problems. But who wants that icky CIQ? or Sprint nascar/football/bloatware? Yuck!
I've had some limited success with simple pre-rooted deodex etc roms I flash from Odin, but sometimes recovery loads when I power up the phone. And sprint keeps wanting to force the update on me.
Does anyone have any suggestions? I've tried everything I can think of and have searched, to no avail, for a solution.
Does anyone think this is a hardware issue? One of the kernels I tried on ACS 5 was a beta.
If so, how should I go about getting it fixed since it is under warranty. I do have accidental damage coverage.
Most likely not hardware related. I say that because you said you can run stock just fine.
I would try the new CWM5 just released and see if the problem is still there.
Disregard post
Sent from my SPH-D700 using xda premium
Neckberg said:
Most likely not hardware related. I say that because you said you can run stock just fine.
I would try the new CWM5 just released and see if the problem is still there.
Click to expand...
Click to collapse
That's what I thought and why I continued to Odin and one-click root different types of CWM and ACS recovery.
I'm going to see if the repair store nearby can run a diagnostic. Otherwise I'm going to stay away from any modifications that require me to use CWM for anything since I was able to Odin a custom rom (but it was EC05).
Hopefully Samsung will release the EI22 modem tar and someone will release a pre-rooted version that I can Odin.
I tried odin flashing different recoveries yesterday. Odin gave them a pass but they wouldn't boot from the 3 finger salute (like they didn't install).
I've never tried to install CWM this way so I'm not sure if you need to be rooted before hand or you need a specific kernel.
osiris2600 said:
I tried odin flashing different recoveries yesterday. Odin gave them a pass but they wouldn't boot from the 3 finger salute (like they didn't install).
I've never tried to install CWM this way so I'm not sure if you need to be rooted before hand or you need a specific kernel.
Click to expand...
Click to collapse
So it goes back into stock recovery with 3 finger? Easiest fix is Odin in a prerooted EC05 ROM tar like EC05plus then flash a Gingerbread ROM then flash the modem delta.
Sent from my SPH-D700 using XDA App
kennyglass123 said:
So it goes back into stock recovery with 3 finger? Easiest fix is Odin in a prerooted EC05 ROM tar like EC05plus then flash a Gingerbread ROM then flash the modem delta.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Yes it goes into stock recovery. Unfortunately flashing in CWM has been the problem that lead me to flashing CWM through Odin. For more detail see the original post. Whenever I try to flash something through CWM the recovery has problems and it fails to load the rom that is installed.
I'm trying as many alternatives to pinpoint the problem. I'm going to try switching SD cards and see if the problem resulted from some kind of data corruption there. Should have an update on that sometime tonight.
If I can't figure out and fix the problem I'll be at the mercy of sprint or if I want root I'll have to wait for a pre-rooted EI22 rom complete with modem tarball so I can odin that.
I saw the OP but didn't see where you Odin'd a prerooted EC05 ROM like EC05plus. Then flash a GB ROM right after. Just 2 steps. Then if you want the modem one more step to flash the delta. It's worth a shot?
Sent from my SPH-D700 using XDA App
kennyglass123 said:
I saw the OP but didn't see where you Odin'd a prerooted EC05 ROM like EC05plus. Then flash a GB ROM right after. Just 2 steps. Then if you want the modem one more step to flash the delta. It's worth a shot?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I can't flash from CWM no matter how CWM gets on my phone. I tried exactly what you said. My original post says I Odined multiple stock and custom roms. I didn't get around to CWM flashing on a different card tonight, finals got me busy busy.
Enjoy your turkey day!
osiris2600 said:
I can't flash from CWM no matter how CWM gets on my phone. I tried exactly what you said. My original post says I Odined multiple stock and custom roms. I didn't get around to CWM flashing on a different card tonight, finals got me busy busy.
Enjoy your turkey day!
Click to expand...
Click to collapse
Thanks, you too.
So if Odining the EC05Plus ROM didn't get you a working 3 finger salute CWM, then maybe you should try ROM Manager and downloading CWM 5.X.
http://forum.xda-developers.com/showthread.php?t=1357655
It must be a hardware problem. I can odin a rom with CWM and it will boot fine. However if I ever try to open CWM the rom will never load again as the phone boots to recovery and get's stuck there.
I confirmed this by Odin flashing and then going into clockwork and not even flashing anything and it got stuck. Flashing in CWM will actually install things as I can change CWM within CWM but I still get stuck when trying to load the rom.
So the only way for me to enjoy a rooted phone is to refrain from CWM recovery.
I went back to a EH17 odined pre-rooted rom. When EI22 gets a modem tar hopefully someone will make a pre-rooted, deodexed, zipaligned odin tar (and if I'm lucky, CiQ will be removed).
Otherwise I'd like to get a replacement but explaining the problem to sprint is kind of a catch 22 since the issue only appears when I load a custom recovery.
How about flashing CWM 5.027 and downloading ROM Manager and installing 5.027 through that as well. Rom Manager actually downloads the CWM 5 and keeps it packed on your sd card and installs it everytime you use it. It allows ROM Manager to be able to update the CWM whenever a new version comes out.

[Q] Recovery Mode Lost after flashing ROM

Maybe this is by design and I'm just missing something. I got a new e4gt and proceeded to root it using instructions found on epic4gtouchroot.com. Basically I used odin to flash a stock EL29 ROM and then install team Rogue's CWM.
All went well with this process so I proceeded to the next step, which was to download and install a custom ROM. I installed the VeNuM ICE 5.5 since I'm a comic book nerd as well as a computer geek.
This wasn't my first time rooting. I've been rooting my EVO for a year of so, and I've rooted my Wife's Nook Tablet too, so I was a bit shocked to see that the Team Rogue CWM recovery program went bye-bye after flashing the VeNuM ROM.
I downloaded ROM manager and tried to flash the latest CWM recovery program from there, but that dind't work. I haven't tried to download the touch recovery, but I was able to reinstall the Rogue CWM recovery program, which then hosed up my ROM. I actually thought I bricked my phone for a minute, but I was able to go back into Rogue Recovery and re-flash the VeNuM ROM.
All went well and I'm back into my phone, but now again when I reboot into recovery mode, I have "Android System Recovery <3e>" like an abridged version of CWM. I don't have near as many options and wonder what's going on.
I never lost my recovery mode before when flashing a ROM. Is there some sort of custom recovery included with this ROM, or am I doing something wrong?
hi. im pretty new at this also, but i think i know the answer to this. well. not really the answer, but i know how to get clockwork recovery back onto the venum rom you are using now. you need Odin3-v1.85 (just google it) and the clockwork recovery StockCWM-EL26.tar (google). Then you put your phone in odin mode, volume down and power from powered off state, run the program, check the PDA option and browse for the stockcwm file, plug in usb and hit start. That'll put the recovery back on your phone.
But as I've been reading, a lot of times, you cannot just download the rom onto the phone or sd card and flash new roms using the cwm recovery. something about the gingerbread and ics and different kernels. .... =D
Please read the "How not to brick your e4gt" or how ever it goes in general. You need to stay away from rom manager and any touch recoveries. To answer your question, rogue recovery went away because the Venum ICE rom has the stock recovery packed in because of all the custom recovery/bricking issues we've been having with ICS. So the Dev left out custom recovery included with his rom
Sent from my SPH-D710 using Tapatalk
I'm not sure what recovery Venum comes with but this might be by design since custom CWM recovery is not installed by design on most ICS roms.
First of all read through this thread: http://forum.xda-developers.com/showthread.php?t=1525495
You chose to flash ICS; if you had chosen Gingerbread this would not be an issue so please read on... ROM manager should NOT be used with ICS. Since you are new, the only CWM recovery you should be using is the stockcwm-el26 posted here: http://chris41g.devphone.org/index.php?dir=EpicTouch/Stock+Repack/EL26/
Lastly and most important:
Flashing ICS can be a very dangerous thing for your phone if done improperly. Even flashing back to Gingerbread from ICS can go wrong.
Please do not do any further flashing of ICS without reading and understanding the process of flashing ICS safely!
Also, please feel free to ask lots of questions until you are comfortable with the entire process. That is why we are here.
Edit: Sorry for the very strict tone throughout. You have a very nice WORKING phone and we see a lot of newbies flashing over to ICS without a full understanding of what can go horribly wrong. We also see users asking for help here daily because they have bricked their phone (many times with no hope for repair or recovery).
Maybe I'm just lucky?
Ok, so I read a little more (two straight days of XDA has left me a bit un-productive at work) and I see now the difference between the Samsung phone and the HTC phone I had before. Samsung does partitioning a bit different, or maybe it's just ICS, but either way as you explained in your post, the recovery has to be packed into the ROM. Makes sense now. I was thinking that the recovery was a different eeProm chip, therfore flashing a ROM shouldn't affect the recovery, now I know that's not the case.
After I read, a bit more, I actually did what it's been suggested not to do, and that's install ROM manager. From ROM manager I installed the custom recovery and have successfully booted to this several times without incident, and in fact have flashed both another ROM (VeNuM Anakonda), a Theme for this Rom, and the S Voice update 4 exe file. I don't seem to be having any trouble using Rom manager to boot into recovery mode.
Venum ICE was a bit much for me, way too many bells and whistles that I could potentially blow up my phone with which still could happen. Anyway, I like the Anakonda rom and will probably stick with it a while. I can't get s Voice to stabalize, but that seems to be the only problem I've got, so I'll live with that.
BBJon said:
Ok, so I read a little more (two straight days of XDA has left me a bit un-productive at work) and I see now the difference between the Samsung phone and the HTC phone I had before. Samsung does partitioning a bit different, or maybe it's just ICS, but either way as you explained in your post, the recovery has to be packed into the ROM. Makes sense now. I was thinking that the recovery was a different eeProm chip, therfore flashing a ROM shouldn't affect the recovery, now I know that's not the case.
After I read, a bit more, I actually did what it's been suggested not to do, and that's install ROM manager. From ROM manager I installed the custom recovery and have successfully booted to this several times without incident, and in fact have flashed both another ROM (VeNuM Anakonda), a Theme for this Rom, and the S Voice update 4 exe file. I don't seem to be having any trouble using Rom manager to boot into recovery mode.
Venum ICE was a bit much for me, way too many bells and whistles that I could potentially blow up my phone with which still could happen. Anyway, I like the Anakonda rom and will probably stick with it a while. I can't get s Voice to stabalize, but that seems to be the only problem I've got, so I'll live with that.
Click to expand...
Click to collapse
Coming in late to this thread but I would like to re-iterate what was said about ROM manager and pretty much everything tdunham said. Because you have been, so far lucky, does not mean that luck will continue. Best advice is to remove it and not use it. If you read through some more posts you will see that the bricking doesn't always happen on the first, second, third flash. It can all of a sudden appear. We've had VERY experienced developers brick their phones, so to think you won't just because you've been lucky is not wise.
But some of the comanailities are clear - using ICS recovery to wipe/restore and using ROM manager. Just thought I'd point that out.
If you're coming over from a different phone (HTC etc) check out Qbking77's videos. They are very informative too.
Good luck and have fun.
I'm glad that the op did some reading and had some extra help here. Our phones can be confusing but with extra reading it can be figured out. We try to list the kernel that's in the rom and these are all listed in the development section in some form or another with explanations of what they have, ie cwm or rogue recovery... In addition most of our roms list a change log that you can read that will tell what each version of the rom has in it in case you would rather use an older version. And we keep the older roms posted too... anyway happy flashing !
I've bricked my phone a few time messing around with different ICS roms and kernals. I go back and odin EL29 rooted...start all over from scratch. Try using new recovey kernals posted on ACS. I'm on FE22 with the ACS recovery and am having no issues with flashing zips and making backups as well restoring.
Sent from my SPH-D710 using xda premium
There are some repacked recoveries that Steady used to make for ICS before he disappeared. Those were never and still aren't safe for flashing ROMs though. It's safest to Odin/Mobile ODIN CWM EL26 tar whenever you need recovery and then flash whatever and then reflash an ICS kernel without recovery so that your phone boots
Sent from my SPH-D710 using XDA

recovery stock tar file passed in odin but wont boot up!

I have flashed the boot stock recovery tar file for my Sprint sph-l900 and it says pass in odin. Then the samsung emblem comes up like its going to boot and then goes black. It wont show its charging while plugged in to charger. But if I take the battery out and hold on, home, and up buttons it will go into stock recovery. So I know that it loaded that at least. Because obviously my TWRP recovery is gone. But I don't understand why its not loading I have done this before and no the steps to take but it is not rebooting properly! I don't know if my only option left is to use ADB side load but if that is the case I do not have the faintest idea on how that is accomplished and done correctly. I woke up this morning and my phone was stuck on the boot screen of the parinoid android rom I had installed that has been working for a good while now. I installed an app to help optimize the system yesterday for better performance and it was an app for rooted phones and it had good reviews so I wasn't worried. I made sure that in the options in the app that the system files and other files that I new could not be touched by the app actions I made sure they were white listed so they would not be effected. That is the only thing that I think could have done this to my phone. And when I realized I could not recover to any nandroid backups I had, that's when I decided to just reinstall the boot recovery stock rar file but not before I wiped the correct files to get a clean install (Flash) Any way that is where I'm at and I do not know what to do...... So could any body please help PLEASE!!!!!!
:crying:
Basically your problem is the rom is incompatible with your current boot loader. You'll need to ODIN back to stock rooted MC2 then ODIN a custom recovery then modem. From there flash the rom you want. I'm not sure why you went back to stock recovery with the custom rom but it's not compatible. Or else you need to make sure the md5 is correct for the rom & other files you flashed. I'd just do what I first suggested and make sureyou have a good md5 for ythe rom you want before flashing it. Good luck.
Thanks for the reply!
tx_dbs_tx said:
Basically your problem is the rom is incompatible with your current boot loader. You'll need to ODIN back to stock rooted MC2 then ODIN a custom recovery then modem. From there flash the rom you want. I'm not sure why you went back to stock recovery with the custom rom but it's not compatible. Or else you need to make sure the md5 is correct for the rom & other files you flashed. I'd just do what I first suggested and make sureyou have a good md5 for ythe rom you want before flashing it. Good luck.
Click to expand...
Click to collapse
I don't know about that because it was already mk4 before I ever rooted it and putt the rom on and I have already had to use the same recovery stock rar file two other times to get it back to original stock. And I haven't changed the mk4 since stock not even with the root or the rom Ive installed so it doesn't make sense especially when I have done this twice with the same rar file flashed with odin and always had good result never got stuck from not booting all the way. But so far your the only person all day i have had any advice from and you are a senior member who im sure knows what they are talking about so i guess I will have to find out how to revert from mk4 that Ive never changed to a MC2 and hope that that will do something for me im just baffled that the same thing that Ive done 2 other times wont work again....
Thanks again for the reply any other advice along the way or what ever you feel like adding is more than welcome i really appreciate you now im gonna be on the hunt for this MC2 install and what is the best steps to follow and go on....
slade1style said:
I have flashed the boot stock recovery tar file for my Sprint sph-l900 and it says pass in odin. Then the samsung emblem comes up like its going to boot and then goes black. It wont show its charging while plugged in to charger. But if I take the battery out and hold on, home, and up buttons it will go into stock recovery. So I know that it loaded that at least. Because obviously my TWRP recovery is gone. But I don't understand why its not loading I have done this before and no the steps to take but it is not rebooting properly! I don't know if my only option left is to use ADB side load but if that is the case I do not have the faintest idea on how that is accomplished and done correctly. I woke up this morning and my phone was stuck on the boot screen of the parinoid android rom I had installed that has been working for a good while now. I installed an app to help optimize the system yesterday for better performance and it was an app for rooted phones and it had good reviews so I wasn't worried. I made sure that in the options in the app that the system files and other files that I new could not be touched by the app actions I made sure they were white listed so they would not be effected. That is the only thing that I think could have done this to my phone. And when I realized I could not recover to any nandroid backups I had, that's when I decided to just reinstall the boot recovery stock rar file but not before I wiped the correct files to get a clean install (Flash) Any way that is where I'm at and I do not know what to do...... So could any body please help PLEASE!!!!!!
:crying:
Click to expand...
Click to collapse
What recovery did you use? Philz 6.12. X?
Sent from my SPH-L900 using XDA Premium 4 mobile app
No TWRP 2.6.3
jlmancuso said:
What recovery did you use? Philz 6.12. X?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No I had TWRP recovery but when i realized there was no getting to flash the rom nandroid BU I went ahead and did a factory wipe and all the files your suppossed to wipe and then I used odin like I have many times before and flashed the same recovery stock rar I have used before to go back to stock and start fresh any way this time odin said pass as usu-wall and then it acted as though it were going to boot and then it lit up the silver samsung emblem for a hot sec and then went black and stayed black after that even when i plugged the charger in the led light would not even show it was charging. But if I take the battery out and back in while its plugged in to charger the screen comes on with the little green battery icon and shows it charging. if i push pwr it show samsung icon then goes dead. Now if I push all the button for recovery it will boot back to stock android recovery. and i can upload one of the backups which was my last rom but it of course act as if it will load and then fails which i know is because i dont have the custom recovery any more but it didnt work either when I did and i don't know man im baffled...
The only suggestion Ive been given so far was from the senior member above and said i need to flash a earlier firmware than mk4 but that is weird to me since I have never had any thing installed on anything other than an mk4 but it make sense that it could work I just have not found the info that makes me feel confident about choices yet...
Thanks for replying any other thought please share!
Well sounds like the odin flash had some kind of issue even though it did not state one. Try going back into download mode and flash a custom recovery (twrp) then flash billards back to stock MC2. This will restore everything back even if you have the knox bootloader. Link is below for easy access. Two things twrp is recommended and do a factory reset before installing. After install reboot (apply su when asked if you want it) the phone will reboot display a messed up screen then reboot once again (normal dont worry). After that you can flash your custom recovery via odin and you should not have any more issues.
http://forum.xda-developers.com/showthread.php?t=2086769
Let me know if that works for you.
So I found the write far file for mk4 and it flashed beautifully I tried a flash of the Mc2 in the reply from earleier post but it did not pass in Odin but I really expected that because I was pausitive that there was another mk4 rar that would work. And now I'm back to a fresh stock rom and I have all the flash file I need to get it rooted and custom romed in no time. I really do appreciate the help and suggestions it is nice to know there is help when needed! So thanks again and I got the file from TA TRUE ANDROID vpubmk4 firmware android 4.3 for the sprint sph-l900 I just had to do some hunting in order to find it. And it didn't help that my renters from the other side of the duplex were having their Internet fixed and the Tech accidently disconnected my lines out side so I was with out Internet for a long time and then when it was finally fixed I found this and flashed it no problems. Thanks again. If you don't mind I'm gonna send a friend request to you I don't have any friends or contacts in this forum and it would be nice to have another person to occasionally check in with? Ya know any way take my brother and stay cool......
Sent from my SPH-L900 using Tapatalk
slade1style said:
So I found the write far file for mk4 and it flashed beautifully I tried a flash of the Mc2 in the reply from earleier post but it did not pass in Odin but I really expected that because I was pausitive that there was another mk4 rar that would work. And now I'm back to a fresh stock rom and I have all the flash file I need to get it rooted and custom romed in no time. I really do appreciate the help and suggestions it is nice to know there is help when needed! So thanks again and I got the file from TA TRUE ANDROID vpubmk4 firmware android 4.3 for the sprint sph-l900 I just had to do some hunting in order to find it. And it didn't help that my renters from the other side of the duplex were having their Internet fixed and the Tech accidently disconnected my lines out side so I was with out Internet for a long time and then when it was finally fixed I found this and flashed it no problems. Thanks again. If you don't mind I'm gonna send a friend request to you I don't have any friends or contacts in this forum and it would be nice to have another person to occasionally check in with? Ya know any way take my brother and stay cool......
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
For the record (since people seem to still be having issues) you CANNOT DOWNGRADE THROUGH ODIN WITH THE NEW BOOTLOADER!!! You can however downgrade through (custom?) RECOVERY using the previously mentioned method.
Sent from my SPH-L900. Please hit the thanks button if I helped you out!

Categories

Resources