Develop Bugs

[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.

What is this about bricking???

I have a few questions... I am coming from using a Nexus One and am intimately familiar with flashing Modems/Kernels/ROMs... modifying framework and other APKs for custom features... and all kinds of other fun stuff. I have been running into videos and such that I am sure their procedure works but I don't really trust that all their information is accurate. Seeing as some people putting up how-to info say I need to install 7-zip to run a self-extractable archive... they obviously don't know what they are talking about... no offense meant to them as it is a very good instructional video... I just do not feel comfortable asking them detailed questions.
With the E4GT I keep seeing people saying that you can brick your phone by flashing between GB and ICS ROMs without wiping and such. Now I would like to get a few things strait. On Nexus One the recovery kernel was held in a different partition than the normal OS. Then there was an initial bootloader that would load either the recovery or the normal OS. Now if you were to shoot yourself in the foot and do something you shouldn't with your normal OS you could always boot to recovery and start from your latest nandroid or just flash w/e you felt like. Is this not how the E4GT works? If you flash a kernel (which I would assume would goto your normal OS's boot partition being seperate from the bootloader and recovery) does it actually "brick" your phone? Do ICS ROMs mess with something in the bootloader or recovery that could prevent you from going back to recovery and reflashing whatever you want?

The permenant bricks are happening with the partitions getting screwed. Even ODINing over a stock tar will fail at that point. Normally with any device we would JTAG and write new partitions.
Only 2 things I know are. The partitions between GB and ICS are different. Our phones recovery is packed into the kernel and since we don't have the source for the ICS kernel yet I would expect their to be issues with CWM repacks on our phone with ICS.
Ive been one of the ones with no issues flashing around in ICS. But I would not dare try to flash a GB rom back. SFHUB's One Click ODIN's are a quick way to flash over an EL29 or prior tar but you can do it the old fashioned way as well.

Read here, On how to avoid
http://forum.xda-developers.com/showthread.php?t=1525495

xST4T1K said:
Read here, On how to avoid
http://forum.xda-developers.com/showthread.php?t=1525495
Click to expand...
Click to collapse
I really appreciate your informational thread. The problem is... I went through all this information as well as some other stuff prior to posting this. While the information is nice it is basically "follow these procedures and things should work according to my experience". What I am looking for is detailed information as to what is causing tons or people (relative to what i saw in the N1 community) mentioning these bricking issues. I am trying to gather and consolidate this information as I can not find it readily available.
RainMotorsports said:
The permenant bricks are happening with the partitions getting screwed. Even ODINing over a stock tar will fail at that point. Normally with any device we would JTAG and write new partitions.
Only 2 things I know are. The partitions between GB and ICS are different. Our phones recovery is packed into the kernel and since we don't have the source for the ICS kernel yet I would expect their to be issues with CWM repacks on our phone with ICS.
Ive been one of the ones with no issues flashing around in ICS. But I would not dare try to flash a GB rom back. SFHUB's One Click ODIN's are a quick way to flash over an EL29 or prior tar but you can do it the old fashioned way as well.
Click to expand...
Click to collapse
This is more along the lines of what I am looking for. So... from what I gather here:
1. As far as it is known... something having to do with partition allocation information is different between GB and ICS ROMs.
2. E4GT version of Android's recovery is not held seperate from the running OS and is dependent on the Initramfs (and contained within) that is used by the actual running OS.
3. In order to flash back to GB you must use SFHUB's One Click ODIN which uses a known procedure that works. (Why does this work where others methods do not? Possibly, when update script runs from package used in recovery [modified ICS recovery] it has to do with partition information the recovery is expecting is different from actual? ICS kernel source so its exact method of actually executing an update script is unknown?)
Please correct post to correct any information you see here which is incorrect or acknowledge what information you believe to be correct.
EDIT: Correction to 3 as I didn't read post properly and also in response to RainMotorsports post. Also, changed SGS2 in 2 to E4GT
EDIT: Changed "kernel" in 2 to "initramfs" Detailed information about all this can be found in Sfhub's detailed explanation post within this thread which you can find here:
http://forum.xda-developers.com/showpost.php?p=24398615&postcount=13

You can go back to gingerbread as many times as you want, just use the one click odin el29 above. That's the safest and simplest way. I've done it countless times.

Goblinlord said:
2. SGS2 version of Android's recovery is not held seperate from the running OS and is dependent on the kernel (and contained within) that is used by the actual running OS.
3. If you flash to ICS do not flash back to GB??? (though this goes against the information contained in xST4T1K's post)
Please correct post to correct any information you see here which is incorrect or acknowledge what information you believe to be correct.
Click to expand...
Click to collapse
For 3 as said just use the odin one click. Now everyone recommends using EL26 with CWM for some reason but EL29 works. When going backwards always use the version that wipes the data partition - http://forum.xda-developers.com/showthread.php?t=1433101 will take you to stock rooted EL29 and you can odin over the kernel with cwm or just use sfhubs auto rooter to gain it.
Its recommended to either use ODIN (or an odin one click) to upgrade an ICS leak or to ODIN back to EL26/29 then flash a rom. It has been possible for some of us to do it from ICS but there have been bricks its just a precaution so do it the right way for now. Mobile ODIN also has some issue but I have done 2 tar leaks using it as well.
As for 2 to the best of my knowledge its just the E4GT. The recovery partition on our phone is unused and recovery is packed into the kernel. Very stable on GB, but we don't have the ICS source and the ICS repacks have some issues. To change or gain recovery all you have to do is flash a kernel.

RainMotorsports said:
For 3 as said just use the odin one click. Now everyone recommends using EL26 with CWM for some reason but EL29 works. When going backwards always use the version that wipes the data partition - http://forum.xda-developers.com/showthread.php?t=1433101 will take you to stock rooted EL29 and you can odin over the kernel with cwm or just use sfhubs auto rooter to gain it.
Its recommended to either use ODIN (or an odin one click) to upgrade an ICS leak or to ODIN back to EL26/29 then flash a rom. It has been possible for some of us to do it from ICS but there have been bricks its just a precaution so do it the right way for now. Mobile ODIN also has some issue but I have done 2 tar leaks using it as well.
As for 2 to the best of my knowledge its just the E4GT. The recovery partition on our phone is unused and recovery is packed into the kernel. Very stable on GB, but we don't have the ICS source and the ICS repacks have some issues. To change or gain recovery all you have to do is flash a kernel.
Click to expand...
Click to collapse
Perfect ^^... thanks for the information this is exactly the type of information I was looking for.

OP, check PM.

There was actually some talk from a few that were using JTAGs to unbrick only to find out that the NAND was fried in a way you would only expect to see from something hit by an EM surge. While odd, it's not impossible and we can only speculate at the changes in 3.0.15 ICS kernels from Samsung vs. the GB ones. I'm no electrical expert so I won't speculate on what would cause it.
I know how the Nexus was coming from a G2/Desire Z a lot of things were very similar. This phone is completely different. So far as I can tell the recovery and kernel share the same space. While you could flash 4EXT as your recovery and never change it but constantly change kernels - you must flash the recovery w/ the kernel on this. Probably has something to do with us having ODIN - that might be taking up residence where the recovery or fastboot would normally reside. I could be completely wrong though. As far as the 7zip thing. I don't know what videos you're talking about specifically but I do know a lot of people tell others to install it just because it's one of the most useful things when modding. Whether it be an apk or an entire rom. This is of course when your speaking about Windows. Linux has its own built-in goodies.

KCRic said:
There was actually some talk from a few that were using JTAGs to unbrick only to find out that the NAND was fried in a way you would only expect to see from something hit by an EM surge. While odd, it's not impossible and we can only speculate at the changes in 3.0.15 ICS kernels from Samsung vs. the GB ones. I'm no electrical expert so I won't speculate on what would cause it.
I know how the Nexus was coming from a G2/Desire Z a lot of things were very similar. This phone is completely different. So far as I can tell the recovery and kernel share the same space. While you could flash 4EXT as your recovery and never change it but constantly change kernels - you must flash the recovery w/ the kernel on this. Probably has something to do with us having ODIN - that might be taking up residence where the recovery or fastboot would normally reside. I could be completely wrong though. As far as the 7zip thing. I don't know what videos you're talking about specifically but I do know a lot of people tell others to install it just because it's one of the most useful things when modding. Whether it be an apk or an entire rom. This is of course when your speaking about Windows. Linux has its own built-in goodies.
Click to expand...
Click to collapse
Thanks for the info KCRic. If you could provide a link for the thread you refer to about the NAND memory being fried it would be great. Also... I completely agree with 7-zip being useful as I have used it now for many many many years... my point was more... the person didn't even know the difference between an self-extracting executable and an archive file.

Please look at the following thread for background on the problem and speculation as to technically why the bricks are happening:
http://forum.xda-developers.com/showthread.php?t=1504808

My theory on to why restoring a gingerbread and is that the fact that on ICS the recovery actually has access/see add'l hidden partitions that the gingerbread recovery does not access or see (example the triangle away tool which needs ics) Most likely when the restore is done the nand gets rewritten to the wrong partitions due to new hidden partitions not accounted for and in a sense overwriting something crucial and ends up in either destroying the partition and bricking the device. I'm no expert on the matter though so take this with a grain of sand.

I am reading from mobile so only skimmed through this. Some questions are probably already answered. Excuse the typos, it is a pain to type long replies on mobile.
The 7zip thing is probably because i package everything as 7zip self-extractors, which on windows means you just double-click on the *-sfx.exe and choose the directory to unpack to. The roms are relatively large so compressing them makes sense and 7zip does a better job compressing and is cross platform. Anyway on platforms other than windows you just treat the -sfx.exe file like a regular 7zip archive and use 7zip or other archive tool to unpack, similar to if zip or rar was used to compress.
Regarding why there are bricks, there are two more prevalent ways of bricking this phone.
1) flashing an intl gs2 factory or leaked rom that includes the intl bootloader. On our phone, the intl bootloader disables the usb port so you can no longer recover using any tool that uses the usb port. If you happen to have custom recovery still on the phone, you can use an update.zip to update your rom, kernel, and modem, but your usb port is still useless.
2) using an ics kernel combined with a custom recovery to wipe, restore, or otherwise do partition operations that affect /data. This is not a deterministic brick in that you can have the same operation work fine many times, but then suddenly have it fail. There were some more deterministic variations of this type of brick involving a temp flashed cwm touch, where wiping/factory reset would very frequently cause the /data brick.
So what is the /data brick? Apparently a change in the ics kernel combined with certain custom recovery operations can cause a hardware failure in the emmc memory for the data partition section. This will cause all future attempts to format, overwrite, restore, the data partition to hang or fail. We know it is a hardware failure because even using jtag to bit blast the proper software fails. Often people don't realize their data partition has bricked right away because they are in the midst of wiping/factory reset or restoring a backup. Then something isn't working right so they go and use odin to get back into a known state, but find odin hangs on the data partition. This may lead them to think odin is not working right or even that odin caused the problem, but in reality, odin is just the messenger that your emmc is screwed. The damage was done earlier. We know that to be the case, because
1) in all instances it was traced back to on operation with an ics kernel and custom recovery
2) this type of brick never existed before the ics kernels (linux 3.0 kernels came out)
3) galaxy note on ics has the same type of emmc brick
4) we know there were changes to the emmc code because different areas of emm are exposed in ics kernels which were not exposed in gb kernels
Your only recourse for this type of brick is to return for replacement, as even jtag fails.
Regarding odin, if you are coming from another platform, it is basically like fastboot in that it is a failsafe type flash using low-level bootloader routines which do not depend on working kernel or rom. Most types of soft brick can be easily addressed by odin. As to why it is safer, it is using low-level bootloader routines so doesn't depend on the ics kernel which we have found to be problematic in certain situations listed above.
Regarding recovery, I also came from a platform where recovery was a separate partition. This made sense to me. Alas, this phone does not use a separate partition for recovery. Instead reckvery is packed into the initramfs of the normal android kernel. if you flash a new kernel, that comes with a new initramfs, and you will get whichever recovery was packed into its initramfs, whether that be stock or custom recovery.
Ironically, there is a separate partition labelled recovery.bin that for some reason is not used. The contents are exactly the same as the kernel, so in the current state it just serves as a backup of the active kernel.
In closing, I would suggest treating this phone as a new platform and don't make assumptions based in past experience. Being android, there are similarities, but there are also important differences/quirks to be aware of which are easily missed if assumptions are made.

RainMotorsports said:
For 3 as said just use the odin one click. Now everyone recommends using EL26 with CWM for some reason but EL29 works. When going backwards always use the version that wipes the data partition - http://forum.xda-developers.com/showthread.php?t=1433101 will take you to stock rooted EL29 and you can odin over the kernel with cwm or just use sfhubs auto rooter to gain it.
Its recommended to either use ODIN (or an odin one click) to upgrade an ICS leak or to ODIN back to EL26/29 then flash a rom. It has been possible for some of us to do it from ICS but there have been bricks its just a precaution so do it the right way for now. Mobile ODIN also has some issue but I have done 2 tar leaks using it as well.
As for 2 to the best of my knowledge its just the E4GT. The recovery partition on our phone is unused and recovery is packed into the kernel. Very stable on GB, but we don't have the ICS source and the ICS repacks have some issues. To change or gain recovery all you have to do is flash a kernel.
Click to expand...
Click to collapse
Coming from the Evo this is all new to me so I am sorry but I just wanted to double check. Right now I am still on eg30 and rooted. It is ok then to just use the odin one click to flash el26/29? Then I have to also flash cwm again correct? Sorry for the noobish questions, just trying to avoid any problems.
Sent from my SPH-D710 using xda premium

Natedog1 said:
Coming from the Evo this is all new to me so I am sorry but I just wanted to double check. Right now I am still on eg30 and rooted. It is ok then to just use the odin one click to flash el26/29? Then I have to also flash cwm again correct? Sorry for the noobish questions, just trying to avoid any problems.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Wow your on EG30 nice lol.
Yes you can one click or regular odin straight to EL29 if you want. There are one clicks for ICS up to FC24 (No FD02 yet) so if your not going to a custom rom just stock rooted you can use those too.
EL26 - http://forum.xda-developers.com/showthread.php?t=1416477
EL29 - http://forum.xda-developers.com/showthread.php?t=1433101
FC24 - http://forum.xda-developers.com/showthread.php?t=1573752
You can go from EG30 to EL29 using the no data ones and not lose anything. Going to ICS or going backwards you should always use the normal ones that erase your data.
You still need custom recovery to flash a rom. You can use sfhubs autorooter on a rooted install to gain it or odin over a kernel.

RainMotorsports said:
Wow your on EG30 nice lol.
Yes you can one click or regular odin straight to EL29 if you want. There are one clicks for ICS up to FC24 (No FD02 yet) so if your not going to a custom rom just stock rooted you can use those too.
EL26 - http://forum.xda-developers.com/showthread.php?t=1416477
EL29 - http://forum.xda-developers.com/showthread.php?t=1433101
FC24 - http://forum.xda-developers.com/showthread.php?t=1573752
You can go from EG30 to EL29 using the no data ones and not lose anything. Going to ICS or going backwards you should always use the normal ones that erase your data.
You still need custom recovery to flash a rom. You can use sfhubs autorooter on a rooted install to gain it or odin over a kernel.
Click to expand...
Click to collapse
Yeah I just picked up the phone the other day after my evo crapped out. It is like learning a new language going from the evo to this. Modems, odin, triangles.... Trying read as much as I can before doing much. Thanks for your help. I appreciate it a lot.
I am a little apprehensive about flashing an ics rom after reading about all the issues everyone is having. I do miss the hell out of cm but I think I should hold off on flashing that for now. Is it "safe" to flash fc24 one click even though it is ics?
Sent from my SPH-D710 using xda premium

Yes if your going to ICS its as safe as it gets. ODIN is samsungs fastboot. The firmwares are stored on tars. SFHUB packages tars in a one click setup for odin so you dont have to deal with odin itself. Writing a full tar with odin write a whole firmware rather than just the rom or just the modem etc like when using recovery.
The other option is to flash an ICS rom through custom recovery preferably EL26 or EL29.
As far as triangles go if you want to know about those. If you flash a custom kernel or anything else not signed by samsung through ODIN it will show a triangle at boot as well as increase the counter shown in the download mode. This is just there to tell the phone company you have been messing with it.
I have never tripped the triangle myself but a USB jig on older bootloaders or the Triangle away app on ICS will take care of it.

Using ODIN to flash the FC24 + rooted is not a bad place to start *in my opinion* to try out ICS on the E4GT. But there are lessons to this too - please make sure you are using a good quality USB cable (such as the Sammy one), don't flash if your system is at risk of shutting down in the middle (such as a laptop with a sketchy battery and no A/C) and by all means, if it looks like it is hanging... give it time before resorting to unplugging the USB cable. The last part is the modem and takes several minutes, no matter how fast your PC is.
No matter what you decide, good luck and don't be afraid to ask any questions. It is far better to err towards caution and ask for advice than go on our own and risk ending up with a paperweight instead of a phone.

Thanks garwynn i was actually just coming back to add that. Yeah I always recommend to people to flash with a laptop if they have it in case of a power outage.

Thanks for the tips and the advice guys. Much appreciated. Right now the ics roms are pretty much all leaks correct?
Sent from my SPH-D710 using xda premium

CWM install fail

Ok ive invested about 7 hours of fail after fail on trying to get a non stock recovery on here so i can switch roms. I have the ff18 kernal (pretty sure thats the terminology) Usually on my old phones in the past i just do rom manager then flash cwm and its game time after ive already rooted of course... but now it just gets to the end and freezes up the rom manager.... soooo im trying to do this threw odin. i was reading that the recoveries are built into the kernal... ok so cool i looked up e4gt cmw kernals that support ff18.... load reset fail.... flash back to stock rooted. try another fail.... tired of playing this game just trying to get some recovery on there... assistance pleaeeaasseeasasaeeeeee

http://www.lmgtfy.com/?q=e4gt+kernel+repository
Sent from my awesomely EPIC Phone

Rooster85 said:
http://www.lmgtfy.com/?q=e4gt+kernel+repository
Sent from my awesomely EPIC Phone
Click to expand...
Click to collapse
cool story... as i said before ive been battling this for 7 hours... ive been on several of those sites with no luck

trithumb said:
cool story... as i said before ive been battling this for 7 hours... ive been on several of those sites with no luck
Click to expand...
Click to collapse
LOL. Rom Manager is not supported on this phone. Recoveries can not be flashed to the device since you must repack the initramfs with the recovery of your choosing and flash the kernel to the device.
The first link that comes up with the google search rooster did for you is the place I would link you - http://kernelrepo.chris41g.org/
Recovery Kernels > ICS > Stock FF18 i guess I would recommend AGAT's, Source Built even better why not, so that > TAR (since this is odin) > AGAT_v0.4.4.tar
If you don't know anything about recoveries on this phone then you should be made aware the Android 4.0 kernel triggers a bug with our phones eMMC firmware. This bug can uber hard brick the phone where a JTAG service can't even help you. The latest kernels made by community developers have made safe recoveries and source built kernels have work arounds even deeper.
Avoid older ICS repacks. Wiping and factory resetting can trigger the bug as well as flashing zips that have an unsafe updater binary.

RainMotorsports said:
LOL. Rom Manager is not supported on this phone. Recoveries can not be flashed to the device since you must repack the initramfs with the recovery of your choosing and flash the kernel to the device.
The first link that comes up with the google search rooster did for you is the place I would link you - http://kernelrepo.chris41g.org/
Recovery Kernels > ICS > Stock FF18 i guess I would recommend AGAT's, Source Built even better why not, so that > TAR (since this is odin) > AGAT_v0.4.4.tar
If you don't know anything about recoveries on this phone then you should be made aware the Android 4.0 kernel triggers a bug with our phones eMMC firmware. This bug can uber hard brick the phone where a JTAG service can't even help you. The latest kernels made by community developers have made safe recoveries and source built kernels have work arounds even deeper.
Avoid older ICS repacks. Wiping and factory resetting can trigger the bug as well as flashing zips that have an unsafe updater binary.
Click to expand...
Click to collapse
Was loading it in with odin and now its on the "zimage" step and its just hanging... trying to be patient with it... nervous about closing this if it doesnt work... doesnt seem to be failing or passing...

Should have been pretty fast. If it failed mid flash you won't have recovery but ODIN/Download mode is part of the bootloader and you should still be able to get back to download mode with only a messed up kernel flash.
If it fails twice id try a different file. Ive only flashed various ones for CM9 since I am not on stock. Another good fail safe while it wont allow you to boot an FF18 rom is the old el26 cwm which is out safe fallback for flashing roms - http://kernelrepo.chris41g.org/?act...\Stock+CWM\TAR&filename=EL26_StockCWM.tar.md5
No Data one click for FF18 will also set you straight as far as stock ff18 if you can get into download mode - http://forum.xda-developers.com/showthread.php?t=1721229 The full version will wipe data so note on that if you go that route. Should be a link for the stock ff18 kernel tar as well in there.

trithumb said:
Was loading it in with odin and now its on the "zimage" step and its just hanging... trying to be patient with it... nervous about closing this if it doesnt work... doesnt seem to be failing or passing...
Click to expand...
Click to collapse
crysis averted... i worked it out thanks for your help

[Q] about minimal by judas/zero and other firmwares in general

hi im a noob when it comes to phones, normally ill take it to a shop who will find one and install it for me, but i feel like trying this myself
are firmware in general like OSs? are kernels included as well or do i have to look for them? can I use any of them from any country? i dont mind resetting internet/MMS since theyre easy. im talking in computer terms to show how noobish i am
since i cant ask questions on the 'minimal by Judas' thread ill ask it here. is the 1.6 download a full OS with hardware stuff included or is it like a patch where i have to install that on top of an already working MG2? im interested in the zero patch since it removes most bloats, is it another OS or a patch on top of the minimal?
if it isnt too troublesome could someone write up a small walkthrough on using the aroma installer?

if you are alredy on MG2, you should have a working kernel for the minimalzero rom. alternatively you can use D-kernel.
as for the firmware itself, it's like an os. the package is a full rom (system installation, so installing it will first wipe your current system and then recreate it from scratch.
stuff like wifi passes and mms are on data tho, so u will keep that
for aosp based roms tho, the kernel needed will be included in the package, and a data wipe is required as well.
Flashing anything should be done by first flashing a temporary CWM via the stock recovery (look for temporary CWM by shaan in the development section) and then flashing zips from the temporary cwm once itl oads.

im still using stock 2.3.6 that came with the phone, would i need to install another firmware before hand?
and could i have some help finding an older version of CWM? weird thing is i rooted my phone but CWM is still not onstalled. ive reset my phone a lot, installed a few XXLD8 with CWM, tried to onstall standalone CWMs but none of them seem to work (failed to verofy whole package thing), tried via rom manager and it gives me the 'failed to verify whole package' thing.l
i even read a tutorial on that but its still not getting me through it
do i need CWM installed before i can upgrade using aroma/odin? can i use TWRP instead of CWM?

1. Follow this http://forum.xda-developers.com/showthread.php?p=43001497
2. Get temp CWM 6 (by Shaaan) then copy to external sdcard.
3. Reboot to recovery(you will be in stock) and chose third option from top (the line has an 'update'in it)
Find the temp CWM (will be named update.zip) and flash.
3. Make sure minimal zero file in in external/internal sd then chose flash zip from sdcard in temp CWM. And follow instructions in judas77's thread
EDIT: in 2: use power button to select
Sent from my GT-I8160 using xda app-developers app

temp CWM is working
what are the requirements for minimal/zero? im following the 'all galaxy ace 2 jelly bean firmwares' and the newest reply i saw was a person who downloaded an MF2 but requiring an MF1. seeing how zero has an MG1 CSC version and mininal has an MG2 does that mean zero is a requirement of minimal or are they both standalones? i also read elsewhere that in order to install an MG youd have ti install earlier firmwares, is that true?
sorry for such noobish questions

You can flash MB4 then MG2 to ensure 624mb ram, if you flash mg2 only most like get only 482mb ram. Follow guide to get 624mb ram on any jb rom if you have only 482mb ram after flashing your desired fw.(mc8,mg2 etc). Minimal 1.6 and minimal zero are standalone roms.
EDIT: CSC does not really matter unless you want to update through kies (what for? Use odin) and you dont need to flash another firmware just for mg2.
Sent from my GT-I8160 using xda app-developers app

thanks for the replies, theyre helping a lot
theoretically if i wanted to skip downloading other firmwares, what files for the MG2 would i have to install manually? even without a complete MG2 i could still get in to download/recovery to install them? ive so far found kernels and the 628MB (from szabys signature), would those be enough?
if i wanted to go down this road that means installing the OS first then the others right, will the order count?
*edit*
about the different CSC versions, i thought other settings would be affected as well, so its just update over kies right

Just find any fw you like (i use mg2, but may not be best either, your choice ) then flash with odin under PDA(remember to extract the .zip to obtain the .md5) different csc dont seem to do any harm for me and i dont think it should
EDIT: you must wait for the whole flashing process in odin to finish(although i have no idea what happens if you dont). Once its booted you can just head to recovery and update to temp CWM then follow instructions to flash minimal
Sent from my GT-I8160 using xda app-developers app

thanks for all the help, im not blaming you since my stupidity did it -.-
ATM i 2/3 bricked it (only download mode)
hoping the staffll keep this open since im on a side questish

If you can access download mode flash md5 again
You can ask in Q & A(new) i go there sometimes, if i can help i will
Sent from my GT-I8160 using xda app-developers app

thanks again, im currently torrenting the MG2 from szabys sig, will try flashing via odin once its done
heres the thread if youre interested http://forum.xda-developers.com/showthread.php?t=2441429

update
i feel like an ass asking how do i use this and that, but in the end i ended up flashing it to stock MG2, hope theres no hard feelings

Nope. Glad your phone works well . Just ask in Q & A next time
EDIT: but you would probably wanna learn how to flash cm10/ 4.2 roms. Stock jb is so hopelessly slow you could downgrade to gb
Sent from my GT-I8160 using xda app-developers app

again thanks for the tip, id probably try CM10.1 B2 i found on bagnzors site (full download thing ~200MB), seeing how i rarely use the things he said arent fixed yet id just jump right in
im currently using zero, do i have to reflash MG2 first or can i install it on top of zero?

littledude072 said:
again thanks for the tip, id probably try CM10.1 B2 i found on bagnzors site (full download thing ~200MB), seeing how i rarely use the things he said arent fixed yet id just jump right in
im currently using zero, do i have to reflash MG2 first or can i install it on top of zero?
Click to expand...
Click to collapse
flashing on top works fine

dont know why i waited almost a year to root but honestly CM10.1 handles like GB (both using under 200MB, whereas 412/zero uses 300, all debloated)
but there are 2 problems i cant solve, it turns on when charging and 'package access helper/fused location' always running, other than those awesome mod

[Q] How to flash ROM when not recognized by ODIN?

I am trying to flash the SuperNexus 3.0 ROM to my D710 E4GT
http://forum.xda-developers.com/showthread.php?t=2208729
I downloaded the file and tried to open it in the PDA tab of ODIN like I normally would when flashing a device.
There isn't a TAR or MD5 file to open inside of the ZIP file.
I know that I'm missing something and I've searched around but I haven't found anything that points me in the correct direction.
Could somebody point me to what I am missing? Is there a tutorial for installing ROMS from a ZIP that I missed?
Thanks!
-Mike

You're probably the only person I know that doesn't flash using zips lol. Just boot up recovery and install zip. Pretty simple to navigate. This will explain it better http://forum.xda-developers.com/showthread.php?t=1761666
Sent from my SPH-D710 using Tapatalk 4

FuMMoD said:
You're probably the only person I know that doesn't flash using zips lol. Just boot up recovery and install zip. Pretty simple to navigate. This will explain it better http://forum.xda-developers.com/showthread.php?t=1761666
Sent from my SPH-D710 using Tapatalk 4
Click to expand...
Click to collapse
Thanks for the reply I'll check the page out that you posted.
I am a total noob. I've crept the forums and used Odin to flash a lot.
I guess, I'm surprised by the .zip comment. Not because I know anything about anything (By now this should be obvious) but because when you look at a tutorial on flashing your phone, it always points at using odin.

It's one thing to root your phone with Odin and another to flash a custom Rom. All the custom roms are zip files and in the original post of the threads they tell you exactly the best way to flash the Rom.
Sent from my SPH-D710 using Tapatalk 4

FuMMoD said:
It's one thing to root your phone with Odin and another to flash a custom Rom. All the custom roms are zip files and in the original post of the threads they tell you exactly the best way to flash the Rom.
Sent from my SPH-D710 using Tapatalk 4
Click to expand...
Click to collapse
OK. That makes sense. I'm reading that now in the thread you handed to me.
Thanks again!
I knew the info existed, I needed some help getting to it and wrapping my head around it.
It's refreshing to ask an honest question because I'm over-whelmed and not get flamed out.

Yeah the instructions in that thread are not noob friendly. I hope the sticky can help you out. Use the el26 or el29 kernel packed with clockwork mod available in the kernel repo. You can find it in the Android development forum at the top. Use that kernel and recovery combo to safely flash any rom. Also going to jb you need to do an Odin rooted restore of a stock jb Rom in order to partition everything correctly. You'll be able to find this in Android development too. Sorry I can't provide much links im on my phone at work so it'll take me a bit to link.
Sent from my SPH-D710 using Tapatalk 4

FuMMoD said:
Yeah the instructions in that thread are not noob friendly. I hope the sticky can help you out. Use the el26 or el29 kernel packed with clockwork mod available in the kernel repo. You can find it in the Android development forum at the top. Use that kernel and recovery combo to safely flash any rom. Also going to jb you need to do an Odin rooted restore of a stock jb Rom in order to partition everything correctly. You'll be able to find this in Android development too. Sorry I can't provide much links im on my phone at work so it'll take me a bit to link.
Sent from my SPH-D710 using Tapatalk 4
Click to expand...
Click to collapse
So I went to the Kernel Download Page and all of the links to el26 with CWM were dead.
I dug around some more and found this:
w w w. rwilco12.com/Files/Devices/Samsung%20Galaxy%20S2%20%28Sprint%29%20%28SPH-D710%29/Tutorials/SPHD710-Root. p h p
[Can't post URL, new user]
I went with Chris41g's EL26 Stock CWM5 Repack
It looked like what I needed to root with recovery so that I could install the SuperNexus ROM.
Now, my phone has been stuck at the Samsung Galaxy S II screen with the yellow triangle for a half an hour.
Did I miss something else?

HighSeraphim said:
So I went to the Kernel Download Page and all of the links to el26 with CWM were dead.
I dug around some more and found this:
w w w. rwilco12.com/Files/Devices/Samsung%20Galaxy%20S2%20%28Sprint%29%20%28SPH-D710%29/Tutorials/SPHD710-Root. p h p
[Can't post URL, new user]
I went with Chris41g's EL26 Stock CWM5 Repack
It looked like what I needed to root with recovery so that I could install the SuperNexus ROM.
Now, my phone has been stuck at the Samsung Galaxy S II screen with the yellow triangle for a half an hour.
Did I miss something else?
Click to expand...
Click to collapse
Pull your battery, put it back in, hold the vol up and power until it loads up in recovery. Clean cache, then clean Dalvic cache(in Advanced Menu), Find the zip you want on your sd card install zip. It should boot into your new rom. The CWM repack you used is not the one I would have, but it probably is just the repack kernal and cant boot your phone.

byrdcfmma said:
Pull your battery, put it back in, hold the vol up and power until it loads up in recovery. Clean cache, then clean Dalvic cache(in Advanced Menu), Find the zip you want on your sd card install zip. It should boot into your new rom. The CWM repack you used is not the one I would have, but it probably is just the repack kernal and cant boot your phone.
Click to expand...
Click to collapse
Sweet! I'm figuring some things out now!
I actually had GB on the device. I got it from the factory yesterday. Apparently it had a higher OS on it. So I had to go put a GB kernel on it.
I couldn't find the one with CWM but this one has AGAT

HighSeraphim said:
Sweet! I'm figuring some things out now!
I actually had GB on the device. I got it from the factory yesterday. Apparently it had a higher OS on it. So I had to go put a GB kernel on it.
I couldn't find the one with CWM but this one has AGAT
Click to expand...
Click to collapse
once you get the phone set up, get Mobile Odin and keep this .tar files on your sd card. If I Mobile Odin back to this .tar then I can get a clean install on any new rom. this is the name of the file you are looking for, we have been requested not to provide direct links
StockCWM-EL26.tar.md5
If you phone boot loops again have thie zip as well. Pull batt, then press vol up and power to get to CWM recovery then clean and flash
EL26_StockCWM.zip
As you will see when you get more experienced, there is more than one way to skin the cat. This is what I do and it works every time.

byrdcfmma said:
once you get the phone set up, get Mobile Odin and keep this .tar files on your sd card. If I Mobile Odin back to this .tar then I can get a clean install on any new rom. this is the name of the file you are looking for, we have been requested not to provide direct links
StockCWM-EL26.tar.md5
If you phone boot loops again have thie zip as well. Pull batt, then press vol up and power to get to CWM recovery then clean and flash
EL26_StockCWM.zip
As you will see when you get more experienced, there is more than one way to skin the cat. This is what I do and it works every time.
Click to expand...
Click to collapse
That's great! Thank you!
I picked up the Stock EL26 loads.
To make sure I understand when you say that you can get a clean install on any new rom, you mean that you can install StockCWM-EL26 first and then throw the ROM on and it works right?
Also as a note, I have gotten the SuperNexus ROM running on my machine. I don't have 3G data yet. I'm still working on it. I installed the latest ICS modem and changed the xml file that was suggested. I then updated the permissions on the file to what the other files in the directory had and rebooted. Still nothing... I'm not sure if this is your wheel-house and you've already helped me tremendously! I'm digging around trying to find answers.
(I can't post on the SuperNexus dev forum yet. I'm going to look for a support forum or something to post on.)

HighSeraphim said:
That's great! Thank you!
I picked up the Stock EL26 loads.
To make sure I understand when you say that you can get a clean install on any new rom, you mean that you can install StockCWM-EL26 first and then throw the ROM on and it works right?
Also as a note, I have gotten the SuperNexus ROM running on my machine. I don't have 3G data yet. I'm still working on it. I installed the latest ICS modem and changed the xml file that was suggested. I then updated the permissions on the file to what the other files in the directory had and rebooted. Still nothing... I'm not sure if this is your wheel-house and you've already helped me tremendously! I'm digging around trying to find answers.
(I can't post on the SuperNexus dev forum yet. I'm going to look for a support forum or something to post on.)
Click to expand...
Click to collapse
First - Yes, when I want to change roms, I use mobile odin to flash the .tar EL26 CWM kernal. Pull Batt if needed and then Vol up and power to get to CWM. Then I follow the ROM developer's instructions. reboot and almost always get a good clean install.
Second - I use my phone all day for work so I dont mess with the AOSP Roms much. I like them a lot, but I cant have data/connection issues interfere with my lively-hood so I mostly stay on the TW side of things. Cant help you there, sorry...

HighSeraphim said:
That's great! Thank you!
I picked up the Stock EL26 loads.
To make sure I understand when you say that you can get a clean install on any new rom, you mean that you can install StockCWM-EL26 first and then throw the ROM on and it works right?
Also as a note, I have gotten the SuperNexus ROM running on my machine. I don't have 3G data yet. I'm still working on it. I installed the latest ICS modem and changed the xml file that was suggested. I then updated the permissions on the file to what the other files in the directory had and rebooted. Still nothing... I'm not sure if this is your wheel-house and you've already helped me tremendously! I'm digging around trying to find answers.
(I can't post on the SuperNexus dev forum yet. I'm going to look for a support forum or something to post on.)
Click to expand...
Click to collapse
In this step for SN, what rom did you get the xml from? "NAVIGATE TO system/etc and look for apns-conf.XML and delete it. Then grab one from another ROM that has working data then paste it into the same directory and fix permissions and reboot".
That might be the issue. You need to make sure that a) you have an ICS modem(FL24) is the latest, and make sure you're not flashing it through mobile Odin, it won't take, and b) you have a working apn-conf.xml file from a rom with working data. Dastin15's Wild For The Night is also 4.2.2, and last I checked, had working data. Might give that a go. Good luck!
Sent from my SPH-D710BST using xda premium