Related
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.
My niece has an epic. I rooted it for her and I have tried 3 different rom's so far. I have had trouble with each and I am beginning to wonder if have a defective device. Each rom ends up rebooting constantly or getting thrown into a boot loop when it tries to start the launcher. When this happens the only way to fix it is to reflash the rom. Since I don't follow this forum as much as I do others, I wondering which rom is the closest to stock that is stable and is based on froyo? I want to try to get basically get it as close to stock as possible and remain rooted and see if it is still troublesome. I have found a couple of rom's but I guess what I am asking here is there one in particular that would be considered the most stable?
Probably EC05plus. I think it is installed with Odin so you will need to backup and probably do Advanced Restore Data from the nand backup to prevent the boot loops you are getting. TWlauncher is probably your cause since most ROMs remove it. If you switch to Zeam or Launcher Pro before flashing ROMs you might not get those boot loops. Here is the link to the stock plus ROM:
http://forum.xda-developers.com/showthread.php?t=1021305
ElAguila said:
My niece has an epic. I rooted it for her and I have tried 3 different rom's so far. I have had trouble with each and I am beginning to wonder if have a defective device. Each rom ends up rebooting constantly or getting thrown into a boot loop when it tries to start the launcher. When this happens the only way to fix it is to reflash the rom. Since I don't follow this forum as much as I do others, I wondering which rom is the closest to stock that is stable and is based on froyo? I want to try to get basically get it as close to stock as possible and remain rooted and see if it is still troublesome. I have found a couple of rom's but I guess what I am asking here is there one in particular that would be considered the most stable?
Click to expand...
Click to collapse
Which ROMs have you tried? You could be flashing them wrong or forgetting to flash a kernel right after flashing the rom (only certain ones at least). SRF 1.2 is a very stable EC05 rom and works great but you need to flash a compatible kernel right after flashing it.
eao1991 said:
Which ROMs have you tried? You could be flashing them wrong or forgetting to flash a kernel right after flashing the rom (only certain ones at least). SRF 1.2 is a very stable EC05 rom and works great but you need to flash a compatible kernel right after flashing it.
Click to expand...
Click to collapse
Yes, please more info on which ROMs you are trying. Also, make sure to enable journal to prevent data corruption and force close issues. Especially if its for your niece, not someone who can flash and Odin as needed
Sent from my SPH-D700 using XDA Premium App
This is a thread where people can discuss what is working and not working for them for the boot manager app. I will begin by asking if anyone else is having problems using bootmanager with the magnolia ROM. My next question would be is anyone else having a problem not being able to turn on wifi for miui if its put as an sdROM? The only roms that really seem to be fully functional are CM7 and OMFG. What ROM are most people using for the phone ROM, and what roms do you have working fully as sd card roms?
I haven't had much luck with the Boot Manager so far... I can make the backup of my current rom (Miui) and try and install the zips of other downloaded roms and get almost all the way finished and then I will get an error message.. So I have given up and thought I'd wait for an update and see if that may help.
Got Miui Working fine.
After some work and reinstallation I was able to get miui working on the sdcard ROM, for boot manager. I will keep this updated if I notice any more fixes.
A quixk suggestion would be to clear them and reinstall boot manager and restart your phone, after doing that and reinstalling the ROMS on ext2 I noticed they worked/ installed, when they wouldn't before.
After getting the hang of it I have been able to flash any ROM, kernel, nightly or whatever. It's awesome, I think.
I do everything to the phone rom slot through regular clockwork recovery, as if the app didn't exist. Then from the phone rom I flash everything else to the other slots. I always go back and boot into the phone rom before I flash anything to the other slots. Not sure if that's right but it has worked for me.
It would be cool if you could restore an existing nandroid you had into one of the slots but I don't think they are formatted the same. Not sure.
Can someone explain the method of how to perform the setup?
To setup, run the "setup phone rom", which only takes a few seconds. What this does is make a copy of your boot file in case you screw something up. Once this is done, you can install up to 4 different ROM's on your SD card and then boot into them from this same program.
If something gets screwed up along the way and you cannot boot your phone, boot into CWR, install a zip from a file, and find the update.zip in the bootmanager/phonerom(or whatever ROM folder you want to boot) folder.
Currently I am running MIUI, TSM pool party, TSM gangbang, Skyraider Zues, and newt's 3.0 port.
So, I've been using Odin to copy over kernels that I've installed. This doesn't sound like the proper way to install a new kernel over an old kernel. It can't be that easy right?
Is there some sort of method of preping the phone first? (wiping cache..delvik cache) Or not using Odin at all but CWM?
What is the difference between using CWM and Odin to "flash" a kernel?
I ask this because I've been having frequent LOS after going from stock kernel to mod kernel and then to a third mod kernel. I know the LOS isn't related to rooting your phone. But I'm seriously thinking of starting from scratch here, back to stock kernel, ROM, and unroot. The LOS is driving me crazy!
Currently running stock rom with EG30Plus+ 2.6.35.7.
So i am new to Samsung (coming from a launch evo) and watched the QBKING77 videos and rooted and flashed Calkulins rom pretty easily. So far pretty simple but I have a question.
I am on stock EL29, What confuses me is the list of all the different modem .zip/.tar that are listed in the Caulkins thread. I couldn't really find a thread or video explaining what the difference is between the many different modems, or what the heck a modem is even. or if i should even worry about those at all. Should i just stick to the stock kernel that came with the rom? If i do decide to change the modem do i just flash/odin and im all set? or do i have to re flash the rom?
From what i learned so far, the kernel and phone radios are one in the same right?
Modem = radio. Also known as baseband under your settings - about phone. Modems are flashed independent of a ROM or kernel.
You can mix and match anytime you'd like. If you have solid service on EL29, no need to switch.
You can use any modem on any gingerbread or ics rom. If using a GB rom, you can't use an ics kernel and vice versa.
Hope that helps
.zip is for flashing via Clockwork Recovery. .tar/.bin is for flashing via ODIN. Most importantly it's vital to read and reread everything and also ask any questions before flashing, like you're doing now. I make Nandroid backups anytime I'm about to make ANY changes. Good luck.
Also keep in mind that anything with F in the version (ex FC07) is an unofficial leak. The latest official is EL29, which you are already on.
As a good practice when I switch modems, is to update PRL and profile then reboot.
Components come in the following packages. These packages will come either in .zip or .tar/.bin form.
1. Modem (Always separate, can use any Modem with any rom)
2. ROM (With Kernel or Without Kernel)
3. Kernel (With CWM or Without CWM, use ICS kernel for ICS rom. Use GB kernel for GB rom)
CWM = Flash .zip and make Nandroid backup
Odin = Download Mode flashing tool that can flash .tar/.bin. It can be used
Don't go around flashing your radio all the time. It can be dangerous and very brick easy.
Thank you guys! This is the info I needed. I'm sticking with EL29 for now since I'm having zero issues on the radio side. And I wasn't going to flash ANYTHING via Odin until I learned more about how it all worked.
Do I need to manually update the kernel when installing Calkulin's 2.9.2 ROM?
I installed Calkulins 2.9.2 ROM quite a while back and have been happy with it. I believe I am on the stock EL29 modem (my baseband version says S710.10 S.EL29).
I am confused about the kernel. When installing Calkulin's ROM, did I also install the "Rogue" kernel? Or did the kernel not change from the stock kernel that was on the phone from before.
From what I have read I believe that if I am still on the stock kernel then I would not be gaining the battery life benefits of the ROM because the scripts installed by Calkulin's ROM would not be running.
Currently my "kernel version" says "2.6.35.7-SPH-D710.EL29-CL852097". I believe that this is the stock kernel from Sprint. If I need to install the "Rogue" kernel, (1) where do I get it from and (2) how do I know I am using the right one for Calkulin's version 2.9.2 (and not V 3.0)?
Thanks for any assistance you can provide,
Kevin
You can find kernels in the wiki in the stickies in dev section. If you turn your phone off completely( no light on the buttons at them bottom). Then you push and hold volume up and power at the same time. Wait for it to go into recovery. Does it say e3 with blue letters or is there a green backround?
Sent from my SPH-D710 using Tapatalk 2
When I go into recovery on the top it says "Rogue ET Recover 1.1.2 (CWM v5.0.2.7)" and the background image says "Team Rogue". I wasn't able to find something that told me what kernel I was on.
Correct me if I'm wrong, but I believe you're on what's called a repacked stock kernel...its the stock el29 kernel with the cwm recovery added to it.
Sent from my SPH-D710 using XDA
Johnny - thats the thing I dont know; I am unsure how to tell what kernel I am on. I have always been under the impression that when I installed Calkulin's 2.9.2 ROM, that it also installed the "Rogue" kernel. But I am now under the impression that I may be on a "stock" kernel.
From what I understand about the ROM, the battery saver tweaks do not work for "stock" kernel. I never quite understood what a "repacked" kernel is.
specialkb01 said:
Johnny - thats the thing I dont know; I am unsure how to tell what kernel I am on. I have always been under the impression that when I installed Calkulin's 2.9.2 ROM, that it also installed the "Rogue" kernel. But I am now under the impression that I may be on a "stock" kernel.
From what I understand about the ROM, the battery saver tweaks do not work for "stock" kernel. I never quite understood what a "repacked" kernel is.
Click to expand...
Click to collapse
K. So there's a couple of things going on here. Let's get you some definitions.
Kernel: Essentially the backbone of the operating system. There are different stock kernels for different versions of Android (one for GB and another for ICS). A stock kernel comes with stock recovery. It is not a good idea to flash anything using this recovery (in some cases it is actually blocked so you can't).
CWM: Clock Work Mod. The original version from Chris. It is considered a "repacked" kernel. It stands apart from a regular kernel because it has a custom recovery built in. There are a few other things packed into it but the main difference is the custom recovery. The EL26 CWM is commonly referred to as stock CWM (not a stock kernel though).
Rogue: Team Rogue is the most common one you'll see for our phones. They took CWM and customized it further. They also developed custom recoveries based if the leaked ICS kernels. There was something causing bricks in the kernels they created, unfortunately we can't quite figure out why until we have source.
If you are seeing Team Rogue when opening recovery you currently have a "customized custom recovery kernel".
If you are flashing anything GB you're ok with what you have. If you're flashing ICS you'll need to use the EL26 CWM.
How this clears things up a bit.