Related
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
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
I just upgraded my E4GT Sprint from GB to ICS using the oneclick installer. I am trying to install the CODENAME rom from CWM but havng issues getting CWM installed. I used the the E4GT auto but FE16 isnt listed so i tried FE15 but it wont load into CWM. So i tried this link "http://forum.xda-developers.com/showthread.php?t=1390393" and flashed from ODIN and it goes into CWM but before it boots it says my phone is a gt-i9100 and has a ! on the bottom. It appears to boot though so i booted back into CWM and tried to flash the ZIP for CODENAME and the gapps file and it jsut gets stuck at the boot screen with the transformer logo. I cant get into CWM after that point and have to ODIN back to ICS. I am on ICS now and its working fine. Does anyone have any instructions on getting CWM installed and the codename rom from a fresh odin ICS install?
mazdaspeed6 said:
I just upgraded my E4GT Sprint from GB to ICS using the oneclick installer. I am trying to install the CODENAME rom from CWM but havng issues getting CWM installed. I used the the E4GT auto but FE16 isnt listed so i tried FE15 but it wont load into CWM. So i tried this link "http://forum.xda-developers.com/showthread.php?t=1390393" and flashed from ODIN and it goes into CWM but before it boots it says my phone is a gt-i9100 and has a ! on the bottom. It appears to boot though so i booted back into CWM and tried to flash the ZIP for CODENAME and the gapps file and it jsut gets stuck at the boot screen with the transformer logo. I cant get into CWM after that point and have to ODIN back to ICS. I am on ICS now and its working fine. Does anyone have any instructions on getting CWM installed and the codename rom from a fresh odin ICS install?
Click to expand...
Click to collapse
You really should read more before hopping around like that without checking. Real risk for a brick here.
-Flash EL26 stock CWM kernel via the PDA option in ODIN/Mobile ODIN
-When phone begins reboot, Hold Power + Volume up until boots into recovery.
-Wipe data/factory, cache and dalvik cache
-Flash ROM
-Flash Gapps
-Reboot
Those are the instructions right from the developer's thread. This is an AOSP rom and it sounds like you're trying to install TW kernels.
http://forum.xda-developers.com/showthread.php?t=1662295
This is the kernel repository. It links to each kernel where you can read further and find out if they are safe for flashing things.
Seems like you've done a bunch of stuff. But you really should do a whole bunch of reading first or you will brick your phone.
My suggestion would be to use sfhub's one-click http://forum.xda-developers.com/showthread.php?t=1705730 to get to a fully stock rooted device. Then use his autoroot package http://forum.xda-developers.com/showthread.php?t=1342728 to add CWM (the lates in the package is FF11+CWM Agat I believe) then you can add Agat's latest kernel with CWM http://forum.xda-developers.com/showthread.php?t=1721065
But I would be very careful when flashing ANY ROM; use the developers prefered method. Some recommend using EL26 CWM. Some a different recovery or procedure. Be especially careful with CM9 and AOKP builds to follow the directions there.
Good luck
So while i was waiting for a response i just went back to the stock GB using the one click install. I then used the autoroot package to install CWM and then restored my nandroid backup before i made in the very beginning. So my phone is back to a perfect state with GB and CWM installed. Can i just flash the ROM from CWM as is then? For some reason i thought it had to be "converted" to ICS and thats what started this whole mess. Things have changed since my old Evo
I just noticed that im running EL29 not 26...does that matter? When i try to flash that CMW EL26 stock root is when it gave me that gt-i9100 on boot and the ! at the bottom. Using the autoroot and choosing the EL29 Rogue is the only way i got it installed.
mazdaspeed6 said:
So while i was waiting for a response i just went back to the stock GB using the one click install. I then used the autoroot package to install CWM and then restored my nandroid backup before i made in the very beginning. So my phone is back to a perfect state with GB and CWM installed. Can i just flash the ROM from CWM as is then? For some reason i thought it had to be "converted" to ICS and thats what started this whole mess. Things have changed since my old Evo
I just noticed that im running EL29 not 26...does that matter? When i try to flash that CMW EL26 stock root is when it gave me that gt-i9100 on boot and the ! at the bottom. Using the autoroot and choosing the EL29 Rogue is the only way i got it installed.
Click to expand...
Click to collapse
My friend some good suggestions above your post. Give yourself a day or two and do some reading prior to flashing. This way you may not end up at Sprint making up stories about why your phone wont boot up.
Let me just echo what everybody else has said, you're gotta read more. A lot more! If you're one goal is to get CNA in your phone I would recommend reading all of the very first post on that thread. They give step by step instructions.
If you need CWM there are several options to get it on your phone. Both sfhub and I have put together several one-click and automated options to get it on your phone.
One thing that hasn't been suggested yet but I would strongly encourage you to do is to read the "How Not To Brick Your E4GT" thread. It's sticked in the General section.
Good luck!
Two more things.
1) If you're going to ask for help give it a few minutes before trying something new. It takes people a minute to reply. Sometimes waiting that extra minute or two is all you need to be saved from bricking.
2) Don't be afraid to hit your thanks button for everyone who has offered advice already. I got them once for you but it might not hurt to do it again.
Well new company gave me 20% Sprint discount and have become sick of my Tmobiles poor coverage. However I fear wimax might be sucky too here in Seattle. Anyway, long time member here and have been involved in the HTC Sensation and One forums. Both with very very stable roms and kernals.
I was excited to pick up a couple Sprint Galaxy epics and the guy at Sprint had his all rooted and claimed it was smoking fast.
However I came to this forum and see all kinds of complaints of loss of stability just from simple Root of the Epic? Also have not read any stable ICS roms and I have read all of the threads. Plus read this phone is very easy to brick under clockwork. With sensation we use Aroma and it rocks!
So before I move on, I am not looking to break rules on asking ROM questions. I simply would like some input on what ICS rom is stable and supported still as I see many devs have moved on the the sg3 here.
What kernal and radio or what you call modem is stable and how do you find what is for your phone match?
Lastly, what is safest way to ROOT and flash ROMS for this phone?
I did read the stickies but am still confused.
I may be just happy at first to simply ROOT and install the fix for Hot Spot Wi fi and go from there.
Thanks so much.
Not even sure if phones will arrive with stock ICS tomorrow or GB...
Ice
The SAFEST way to flash stock ROMs in case of emergency is using Odin.I've found both stock ROMs (GB & ICS) very stable, however I reboot my phone everyother day (windows habit).
This thread http://forum.xda-developers.com/showthread.php?t=1525495 was my starting point.
rovar said:
The SAFEST way to flash stock ROMs in case of emergency is using Odin.I've found both stock ROMs (GB & ICS) very stable, however I reboot my phone everyother day (windows habit).
This thread http://forum.xda-developers.com/showthread.php?t=1525495 was my starting point.
Click to expand...
Click to collapse
First off thank you for your reply. Interesting, I have read ODIn maybe responsible for bricking many of these phones is that incorrect? Lots of what I found seeing the people are very unstable with the custom roms so far for ICS for this phone of course stock ICS will be here soon.is there the ability to just root the phone and leave the stock ics ROM and just run the sprint hot spot mod.
Sent from my Sensation 4G using xda premium
iceshark said:
First off thank you for your reply. Interesting, I have read ODIn maybe responsible for bricking many of these phones is that incorrect? Lots of what I found seeing the people are very unstable with the custom roms so far for ICS for this phone of course stock ICS will be here soon.is there the ability to just root the phone and leave the stock ics ROM and just run the sprint hot spot mod.
Sent from my Sensation 4G using xda premium
Click to expand...
Click to collapse
Odin never causes any bricks as long as the process is not interrupted. Most of the instability is caused by user error. From my experience, all fresh (by fresh I mean wipe data/cache and format system) custom ROM installs have been rock solid stable. Also, most network issues are fixed by updating profile/prl. Official ICS is already out, it is build FF18. Stock ICS will not normally have the hotspot mod. You will have to use a hack to install it yourself. If you want a stock ICS experience, use this odin package (reset user data) to odin your phone to pre-rooted FF18:
http://forum.xda-developers.com/showthread.php?t=1721229
And here is your hotspot hack:
http://forum.xda-developers.com/showthread.php?t=1760712
Nonetheless, I see no reason why you wouldn't just save yourself the time and flash a custom ICS ROM.
Imho, there isn't any ics custom rom as of yet that is 100% stable, glitch-free, and reliable. I would wait it out until more polished versions come out. If there is a pretty good one to try, i'd say the blu kuban.
revamper said:
Odin never causes any bricks as long as the process is not interrupted. Most of the instability is caused by user error. From my experience, all fresh (by fresh I mean wipe data/cache and format system) custom ROM installs have been rock solid stable. Also, most network issues are fixed by updating profile/prl. Official ICS is already out, it is build FF18. Stock ICS will not normally have the hotspot mod. You will have to use a hack to install it yourself. If you want a stock ICS experience, use this odin package (reset user data) to odin your phone to pre-rooted FF18:
http://forum.xda-developers.com/showthread.php?t=1721229
And here is your hotspot hack:
http://forum.xda-developers.com/showthread.php?t=1760712
Nonetheless, I see no reason why you wouldn't just save yourself the time and flash a custom ICS ROM.
Click to expand...
Click to collapse
Thanks, I think we are on the same page with this!
So I just loaded the FF18 Full Restore and Samsung drivers as indicated in this thread,
http://forum.xda-developers.com/showthread.php?t=1670110
I also tested after unzipping to a folder and the ODEN program comes up waiting for me to hook up phone I dont have yet till tomorrow.
I also watched this video and it seems very easy to do if this is correct process,
http://www.youtube.com/watch?v=_IL21F8Gfbs
Still some clarifying questions,
1. If my new phone comes with ICS already pushed to it. Do I simply still install FF18 to get root for the ICS rom?
2. If phone does not come with ICS will this install ICS and Root?
3. Do I need to use this or Caulkins to wipe data first before I do this process on phone out of the box new?
http://forum.xda-developers.com/showthread.php?t=1670110
Also I am little nervous reading this post from SFHUB<, Is he saying not to do the above process thru the built in Odin recovery in the phone if it comes with stock ICS in it? What does this mean???
The Epic 4g Touch has a bug in it's emmc controller that can cause the /data partition to become inaccessible/unrecoverable sometimes thanks to the wipe process when flashing from ICS recoveries... DO NOT FLASH FROM ICS RECOVERIES!!!!
7/11/12 edit: In the FF18 source Garwynn has confirmed the presence of the offending code that triggers the emmc bug (http://forum.xda-developers.com/show...1&postcount=32) meaning that it will eventually be safe to flash from ICS as long as the offending code is removed by the dev of the kernel/rom...
- Please see this (http://forum.xda-developers.com/show....php?t=1525495) thread by xST4T1K which details how NOT to brick your device... It is slightly out of date but still very relevant... if you want a more technical understanding of what this emmc bug is and why this is happening you can see Sfhub's thread in general related to it (http://forum.xda-developers.com/show....php?t=1644364 ). The OP contains all of the information that our users have been able to figure out about this bug... Be sure to thank these people, as their hard work has made it exponentially safer for all of us to flash ICS roms on our phones...
-Every ICS rom will have a flashing guide in it's dev thread, its HIGHLY suggested you read and reread the guide for the rom you want to flash and follow it EXACTLY, taking the extra time upfront to fully understand what you're about to do will save you alot of trouble going forward.
-Put simply though you will always want to ODIN or Mobile ODIN (mobile Odin is an app made by the dev chainfire, available in the play store, that allows you to preform Odin flashes from your phone without using a PC) the el26 Gingerbread kernel/recovery and flash any ICS roms from that. NEVER FLASH FROM AN ICS RECOVERY, THAT IS HOW BRICKS ARE MADE!!!! Also do NOT use Rom Manager or Touch recovery!!!!
- Currently there are some ICS recoveries that are thought to be safe to flash from thanks to the work done on the emmc bug. If one of these is included in your rom it will be noted by the dev in the rom thread, however the safest way is still just to Odin back to el26 in order to avoid any chance of bricking!
Next, once I do this FF!8 and have root and ICS. If I want to dabble in custom roms. I am guessing they are installed by CWM from file downloaded to root of SD card like normal. I do not find CWM touch for this phone anywhere. I am sure I am missing it. It seems from reading the exploit in ICS kernal is causing the bricks. So I am guessing to use SF hubs or Claukins data wipe before loading custom roms. Are we beating to the same drum here?
Will correct radio or modem be installed automtic with FF18 or custom roms? I see many threads just on modems.
Thanks and thanks for the hot spot mod.
optimummind said:
Imho, there isn't any ics custom rom as of yet that is 100% stable, glitch-free, and reliable. I would wait it out until more polished versions come out. If there is a pretty good one to try, i'd say the blu kuban.
Click to expand...
Click to collapse
Thats what it seems from hours reading each ROM thread. Reminds me of the Sensation when GB and or ICS first leaked. Will most likely just root stock and go from there.
CWM is in the kernel. Current kernels such as chris41g's or AGAT's kernels have patched up recoveries that avoid the emmc bug, so they are completely safe. You should use calkulins format all before flashing a rom in CWM.
For odin, it wouldn't hurt to odin sfhubs wipe data/cache, but it's not necessary. As long as you use the reset user data odin package for FF18, it will take you to stock rooted FF18. Regardless of what rom your phone comes with, run that odin package. You don't need to worry about the modem either because it will install the latest one. Be sure to update your profile/prl in settings>about>system updates after.
If you want to try a custom rom, use odin to flash a kernel with cwm (agat's or chris41g's). Once you have a recovery, flash calkulins format all, and then the ROM of your choice. Modems are not installed through CWM rom zips. You'll have to flash a modem zip in recovery or odin a modem tar.
revamper said:
CWM is in the kernel. Current kernels such as chris41g's or AGAT's kernels have patched up recoveries that avoid the emmc bug, so they are completely safe. You should use calkulins format all before flashing a rom in CWM.
For odin, it wouldn't hurt to odin sfhubs wipe data/cache, but it's not necessary. As long as you use the reset user data odin package for FF18, it will take you to stock rooted FF18. Regardless of what rom your phone comes with, run that odin package. You don't need to worry about the modem either because it will install the latest one. Be sure to update your profile/prl in settings>about>system updates after.
If you want to try a custom rom, use odin to flash a kernel with cwm (agat's or chris41g's). Once you have a recovery, flash calkulins format all, and then the ROM of your choice. Modems are not installed through CWM rom zips. You'll have to flash a modem zip in recovery or odin a modem tar.
Click to expand...
Click to collapse
I was studying Sfhugs FF18 thread and it says I can do the one click root and then install option D and that puts in the FF18, with agats CWM. So is this more simple then flashing FF18 and then doing a flash for either chris or agat kernal with cwm?
Should I use Calkulins format before flashing FF18 from stock?
So when you guys flash new custom roms you have to flash current modem each time? or only if you want to have a more current one? Coming from HTC you only have to flash radio when its required to match a new base leaked. So little confused there too.
Thanks your help has been great!
iceshark said:
I was studying Sfhugs FF18 thread and it says I can do the one click root and then install option D and that puts in the FF18, with agats CWM. So is this more simple then flashing FF18 and then doing a flash for either chris or agat kernal with cwm?
Should I use Calkulins format before flashing FF18 from stock?
So when you guys flash new custom roms you have to flash current modem each time? or only if you want to have a more current one? Coming from HTC you only have to flash radio when its required to match a new base leaked. So little confused there too.
Thanks your help has been great!
Click to expand...
Click to collapse
I know I personally use Mijjahz's "GOODNESS" ROM and it runs smooth. Many mods and add ons with more added daily. I flashed agat's 2.2 kernel because I don't like the 2.3 that version 16.6.1 comes with.
I also flashed FF18 over my EL26 modem. Modems don't change between flashing I believe. Those you update yourself. A lot of folks stay on EL29 or find something that works perfectly in their area.
Sent from Konnor the E4GT.
optimummind said:
Imho, there isn't any ics custom rom as of yet that is 100% stable, glitch-free, and reliable. I would wait it out until more polished versions come out. If there is a pretty good one to try, i'd say the blu kuban.
Click to expand...
Click to collapse
not sure what you expect from a mobile os but I couldn't disagree more.... my experance on mijjahs goodness has been better and more stable than stock in every way, hell even cm9 and aokp are extremely reliable as well if you can live without dialer codes and prl/profile updates.... no software is ever going to be 100%.... I say flash away, you won't be dissapointed
Sent from my SPH-D710 using xda app-developers app
cp320703 said:
not sure what you expect from a mobile os but I couldn't disagree more.... my experance on mijjahs goodness has been better and more stable than stock in every way, hell even cm9 and aokp are extremely reliable as well if you can live without dialer codes and prl/profile updates.... no software is ever going to be 100%.... I say flash away, you won't be dissapointed
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
QFT.
ICS ROMs are very stable at this point.
iceshark said:
Thanks, I think we are on the same page with this!
So I just loaded the FF18 Full Restore and Samsung drivers as indicated in this thread,
http://forum.xda-developers.com/showthread.php?t=1670110
I also tested after unzipping to a folder and the ODEN program comes up waiting for me to hook up phone I dont have yet till tomorrow.
I also watched this video and it seems very easy to do if this is correct process,
http://www.youtube.com/watch?v=_IL21F8Gfbs
Still some clarifying questions,
1. If my new phone comes with ICS already pushed to it. Do I simply still install FF18 to get root for the ICS rom?
2. If phone does not come with ICS will this install ICS and Root?
3. Do I need to use this or Caulkins to wipe data first before I do this process on phone out of the box new?
http://forum.xda-developers.com/showthread.php?t=1670110
Also I am little nervous reading this post from SFHUB<, Is he saying not to do the above process thru the built in Odin recovery in the phone if it comes with stock ICS in it? What does this mean???
The Epic 4g Touch has a bug in it's emmc controller that can cause the /data partition to become inaccessible/unrecoverable sometimes thanks to the wipe process when flashing from ICS recoveries... DO NOT FLASH FROM ICS RECOVERIES!!!!
7/11/12 edit: In the FF18 source Garwynn has confirmed the presence of the offending code that triggers the emmc bug (http://forum.xda-developers.com/show...1&postcount=32) meaning that it will eventually be safe to flash from ICS as long as the offending code is removed by the dev of the kernel/rom...
- Please see this (http://forum.xda-developers.com/show....php?t=1525495) thread by xST4T1K which details how NOT to brick your device... It is slightly out of date but still very relevant... if you want a more technical understanding of what this emmc bug is and why this is happening you can see Sfhub's thread in general related to it (http://forum.xda-developers.com/show....php?t=1644364 ). The OP contains all of the information that our users have been able to figure out about this bug... Be sure to thank these people, as their hard work has made it exponentially safer for all of us to flash ICS roms on our phones...
-Every ICS rom will have a flashing guide in it's dev thread, its HIGHLY suggested you read and reread the guide for the rom you want to flash and follow it EXACTLY, taking the extra time upfront to fully understand what you're about to do will save you alot of trouble going forward.
-Put simply though you will always want to ODIN or Mobile ODIN (mobile Odin is an app made by the dev chainfire, available in the play store, that allows you to preform Odin flashes from your phone without using a PC) the el26 Gingerbread kernel/recovery and flash any ICS roms from that. NEVER FLASH FROM AN ICS RECOVERY, THAT IS HOW BRICKS ARE MADE!!!! Also do NOT use Rom Manager or Touch recovery!!!!
- Currently there are some ICS recoveries that are thought to be safe to flash from thanks to the work done on the emmc bug. If one of these is included in your rom it will be noted by the dev in the rom thread, however the safest way is still just to Odin back to el26 in order to avoid any chance of bricking!
Next, once I do this FF!8 and have root and ICS. If I want to dabble in custom roms. I am guessing they are installed by CWM from file downloaded to root of SD card like normal. I do not find CWM touch for this phone anywhere. I am sure I am missing it. It seems from reading the exploit in ICS kernal is causing the bricks. So I am guessing to use SF hubs or Claukins data wipe before loading custom roms. Are we beating to the same drum here?
Will correct radio or modem be installed automtic with FF18 or custom roms? I see many threads just on modems.
Thanks and thanks for the hot spot mod.
Click to expand...
Click to collapse
you're quoting some of my new user guide here, and i haven't updated it since the OTA came out so it somewhat overstates the danger of bricking (not a bad thing really, made you read, didn't it!?) which was much easir to do before we got kernel source, since then agat63 and chris41g have been killin it in kernel development since they got ICS source... their ICS kernels are safe to flash from and can be found in the dev section, if you're on the stock FF18 rooted with stock kernel i would personally ODIN (mobile or desktop) back to EL26, and from there flash whatever custom ICS rom you like, as far as I'm aware all of the roms come with a safe kernel these days but do be sure to double check and flash one if it does not... at that point going forward should you wish to flash something else you can just do it via cwm as per usual without having to odin back to gingerbread....do note however that you can't use touchwiz kernels with AOSP roms, there asr safe AOSP kernels as well however...
edit: oops, just noticed revamper addressed most of this on the last page, to answer another one of your questions though you can try as many modems as you like and decide which one works best for you, its varies phone to phone and area to area... the modem is not at all required to match the build number of the rom, (example: may people still use the el29 modem with ICS) you can use ANY modem with ANY rom
Ive flashed this phone hundreds of times. Put your rom and any other zips you have on external card. Then to do a full clean wipe go to privacy. then factory data reset then check usb storage. You can skip this step, but this is how to get it factory fresh. Download the el26 cwm kenal. Its posted everywhere. Next open Odin go to pda and select EL26 cwm kernal. Uncheck auto reboot. Have battery cover off! Flash kernal pop battery out when it starts to boot. or says pass. then use the vol up and power combo hold them down until boot screen pops up then let off. Next flash calkulins wipe all or wipe no data. . Never brick never fail. Then flash your rom and tweaks and be happy. Ive done this driving down the road its that easy. Laptop sitting in passenger seat with odin up lol. Plus i drive a 5sp full size truck. Flashing is easy. Follow directions. There is nothing wrong with this phone just read directions if your a noob. I,ll be making multi scenario flashing youtube movies soon. Like mobile tech videos does.
Flashing is easy. Follow directions. There is nothing wrong with this phone just read directions if your a noob.
Click to expand...
Click to collapse
That's all there is to say.
I have been looking around for about an hour or two trying to find a solid tutorial on how to install a custom recovery to install new Roms. I flashed my phone onto Virgin Mobile on FH13. It seems to me that there is more than meets the eye to installing a recovery on this phone. I really don't want to mess anything up at all. Could anyone guide me the right way as to how I can get CWM on my phone? I appreciate any help you can give me. Thanks!
Recovery is packed into the kernel on this phone. Flash a kernel tar through ODIN if you want, it will trigger the yellow triangle though. If your already rooted you could use Mobile ODIN. If you already have some form of custom recovery and are just trying to switch up you can flash the kernel zip in recovery.
rwilco has pretty much every kernel for every purpose but since your on stock you will either want a repacked stock or custom tw kernel - http://rwilco12.androidfilehost.com/?dir=Kernels/Recovery Kernels/ICS
If your unfamiliar then keep asking questions. Our phone has a bug in its eMMC firmware triggered during format operations on the stock kernel as of Android 4.0. The specifics are detailed but all you really need to know is grab a kernel with a safe recovery, or even going as far as AGAT's custom kernel which has more work around in place to prevent a factory reset or rom install from turning your phone into a super brick.
RainMotorsports said:
Recovery is packed into the kernel on this phone. Flash a kernel tar through ODIN if you want, it will trigger the yellow triangle though. If your already rooted you could use Mobile ODIN. If you already have some form of custom recovery and are just trying to switch up you can flash the kernel zip in recovery.
rwilco has pretty much every kernel for every purpose but since your on stock you will either want a repacked stock or custom tw kernel - http://rwilco12.androidfilehost.com/?dir=Kernels/Recovery Kernels/ICS
If your unfamiliar then keep asking questions. Our phone has a bug in its eMMC firmware triggered during format operations on the stock kernel as of Android 4.0. The specifics are detailed but all you really need to know is grab a kernel with a safe recovery, or even going as far as AGAT's custom kernel which has more work around in place to prevent a factory reset or rom install from turning your phone into a super brick.
Click to expand...
Click to collapse
Also new to the e4gt, im currently rooted on fh13.
say i want to flash paranoidandroid, which kernel (which includes recovery?) would you recommend?
also this is either flashed from odin (pc) or can be done through mobile odin?
then once kernel is flashed, i can then reboot into recovery, wipe and flash rom/gapps?
sorry for all the questions, just want to make sure!
bongzilla said:
Also new to the e4gt, im currently rooted on fh13.
say i want to flash paranoidandroid, which kernel (which includes recovery?) would you recommend?
also this is either flashed from odin (pc) or can be done through mobile odin?
then once kernel is flashed, i can then reboot into recovery, wipe and flash rom/gapps?
sorry for all the questions, just want to make sure!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1953783
RainMotorsports said:
Recovery is packed into the kernel on this phone. Flash a kernel tar through ODIN if you want, it will trigger the yellow triangle though. If your already rooted you could use Mobile ODIN. If you already have some form of custom recovery and are just trying to switch up you can flash the kernel zip in recovery.
rwilco has pretty much every kernel for every purpose but since your on stock you will either want a repacked stock or custom tw kernel - http://rwilco12.androidfilehost.com/?dir=Kernels/Recovery Kernels/ICS
If your unfamiliar then keep asking questions. Our phone has a bug in its eMMC firmware triggered during format operations on the stock kernel as of Android 4.0. The specifics are detailed but all you really need to know is grab a kernel with a safe recovery, or even going as far as AGAT's custom kernel which has more work around in place to prevent a factory reset or rom install from turning your phone into a super brick.
Click to expand...
Click to collapse
My phone already has root. Everything else is stock. 4.0.4, build FH13, with no custom recoveries.
I don't understand what you mean in your second paragraph with "repacked stock" or "custom tw kernel".
I am completely lost as to where I should be going. My plan is to install this rom: http://goo.im/devs/Shabbypenguin/E4GT-Nightlies
How would I go around to getting this on my phone?
Also, what about this rom: http://forum.xda-developers.com/showthread.php?t=1810315
I am not sure which rom runs the fastest and most efficient. There are so many kernels for so many things, I have absolutely no idea which kernel to flash and how to flash it.
EDIT: So I have done some more reading up and I THINK I can starting to understand some of it. I assume the steps are to:
1. Install Mobile Odin Lite on my phone.
2. Flash the EL26 kernel on Odin Lite. Link to kernel: http://forum.xda-developers.com/showthread.php?t=1662295 (first kernel on the page)
3. This part I am kinda lost. Not sure if that kernel installed a new recovery or not. I assume I just reboot and go into recovery.
4. Nandroid a backup of my ICS stock that is on now? Can I even go back to this stock backup after putting on a new Rom? Which kernel would I need to install backup of stock?
5. Wipe data, dalvic, and install new Rom using instruction it came with. My problem is I want to run this Rom: http://goo.im/devs/Shabbypenguin/E4GT-Nightlies and it has no instructions. I assume you just wipe data and dalvic?
6. flash Rom, then flash Gapp? It doesn't have a link for any of the Gapps, so either I have to find a link to download Gapp or that rom already comes with it? Not sure.
7. Reboot into new Rom? Not sure if I missed a step or not.
Another question I have is with the kernels. Can I just leave it on the EL26 kernel for daily use of the phone? Say I want to install maybe cm10 next, do I just keep it on EL26?
Sorry for the spam of questions. I like to be 100% certain.
Best bet if your trying to install CM9 is to go to the EL26 CWM kernel as all of the AOSP rom instructions dictate. Using the EL26 kernel means your phone will only boot to Download and Recovery as it will only boot gingerbread roms.
Download the nightly you want to the device and then flash the EL26 CWM kernel in Mobile ODIN. After its all over with you might need to battery pull if you messed up booting into recovery and then boot into recovery (power + vol up). Install the rom. Install gapps. Wipe cache/dalvik but as I will recommend below you should just backup everything and a full wipe.
You can nandroid if you want but it will be making a copy of the ICS rom you have with the EL26 kernel on it so it is literally a restore to the point your starting from not where you were just before that. Its still a good idea if your afraid of losing things. I would use Super Backup from the market to backup your Contacts, Call Logs and MMS. Wipe cache and dalvik and all that. But realisticly you should backup your apps and data if you have Titanium Backup and start fresh just factory reset after your on CM9. Restore your apps with data (no system data) after that. A clean install will present the least of issues, even the Samsung updates from one rom to another are not without issues.
You can not boot anything but gingerbread with EL26 and once you install a rom you will be on the kernel with that rom. So you will have a Linux 3 android kernel with cwm 6 if you go with a CM9 nightly. From there you can flash the next nightly or the next beta etc. Older stuff will not flash from your new setup as AOSP roms have switched to a new device name in the build.prop.
As far as gapps here it is - http://goo.im/gapps/gapps-ics-20120429-signed.zip and don't forget to put this on the device ahead of time or you will have to mount usb and transfer using the pc in recovery.
RainMotorsports said:
Best bet if your trying to install CM9 is to go to the EL26 CWM kernel as all of the AOSP rom instructions dictate. Using the EL26 kernel means your phone will only boot to Download and Recovery as it will only boot gingerbread roms.
Download the nightly you want to the device and then flash the EL26 CWM kernel in Mobile ODIN. After its all over with you might need to battery pull if you messed up booting into recovery and then boot into recovery (power + vol up). Install the rom. Install gapps. Wipe cache/dalvik but as I will recommend below you should just backup everything and a full wipe.
You can nandroid if you want but it will be making a copy of the ICS rom you have with the EL26 kernel on it so it is literally a restore to the point your starting from not where you were just before that. Its still a good idea if your afraid of losing things. I would use Super Backup from the market to backup your Contacts, Call Logs and MMS. Wipe cache and dalvik and all that. But realisticly you should backup your apps and data if you have Titanium Backup and start fresh just factory reset after your on CM9. Restore your apps with data (no system data) after that. A clean install will present the least of issues, even the Samsung updates from one rom to another are not without issues.
You can not boot anything but gingerbread with EL26 and once you install a rom you will be on the kernel with that rom. So you will have a Linux 3 android kernel with cwm 6 if you go with a CM9 nightly. From there you can flash the next nightly or the next beta etc. Older stuff will not flash from your new setup as AOSP roms have switched to a new device name in the build.prop.
As far as gapps here it is - http://goo.im/gapps/gapps-ics-20120429-signed.zip and don't forget to put this on the device ahead of time or you will have to mount usb and transfer using the pc in recovery.
Click to expand...
Click to collapse
Ah, I read it twice and now it makes more sense. I have a pretty good idea of what to do now.
Put rom and gapp on phone, install EL26, backup, full wipe, flash rom and gapp, rom will install new kernel for me, then just reboot.
Last question, I just want to make sure. What exactly is a full wipe on this phone. I have done plenty of full wipes on the evo 4g. I am just asking because I hear some people have problems when they do a full wipe.
I really appreciate your help. Thank you!
Sorry if I jumbled everything together in my post by the I was running out the door. But this Hurricanne has stopped that and I regret not taking my time.
Well what I mean is a factory reset which formats /Cache and /Data. When you install the rom its going to format /System prior to writing the new firmware/rom. /Data has all your user apps, their data and your information etc. This does not wipe the Internal SD or the External SD though at times a line saying it was does come up in CWM.
Just don't do a Factory reset on the stock kernel you are on now, its fine on EL26 its fine on the kernels that come with the CM9 nightlies. Super Backup apparently does app's now too. I have never used it since I have Titanium Backup Pro but figured its also worth mentioning.
A note on turning back. As I said before if you flash the EL26 CWM kernel you wont be able to boot the ICS rom installed on the phone. At that point to go back instead of forward you can flash the FH13 kernel in desktop ODIN or the zip in CWM and you will have the FH13 kernel instead of EL26 and be back where you were. But once you flash the EL26 CWM kernel your goal at that point is flashing your rom of choice in CWM and not things like booting the phone.
You should be "okay" coming from a dirty install just wiping cache. But you may never know if a problem your having is the rom or some left over data unless you go clean and factory reset. Its a choice and its also a choice you can make later as you can always reset later. I would back up anything important first before doing any of this. Not so much a worry about bricking, as just about any normal situation will be recoverable, but more so to the point of if you have to wipe the phone and start from scratch.
RainMotorsports said:
Sorry if I jumbled everything together in my post by the I was running out the door. But this Hurricanne has stopped that and I regret not taking my time.
Well what I mean is a factory reset which formats /Cache and /Data. When you install the rom its going to format /System prior to writing the new firmware/rom. /Data has all your user apps, their data and your information etc. This does not wipe the Internal SD or the External SD though at times a line saying it was does come up in CWM.
Just don't do a Factory reset on the stock kernel you are on now, its fine on EL26 its fine on the kernels that come with the CM9 nightlies. Super Backup apparently does app's now too. I have never used it since I have Titanium Backup Pro but figured its also worth mentioning.
A note on turning back. As I said before if you flash the EL26 CWM kernel you wont be able to boot the ICS rom installed on the phone. At that point to go back instead of forward you can flash the FH13 kernel in desktop ODIN or the zip in CWM and you will have the FH13 kernel instead of EL26 and be back where you were. But once you flash the EL26 CWM kernel your goal at that point is flashing your rom of choice in CWM and not things like booting the phone.
You should be "okay" coming from a dirty install just wiping cache. But you may never know if a problem your having is the rom or some left over data unless you go clean and factory reset. Its a choice and its also a choice you can make later as you can always reset later. I would back up anything important first before doing any of this. Not so much a worry about bricking, as just about any normal situation will be recoverable, but more so to the point of if you have to wipe the phone and start from scratch.
Click to expand...
Click to collapse
That clarified a lot, thanks.
So I did it all. I did a factory reset from the new kernel. did dalvic also. I installed the new rom and gapp. Problem is that once I reboot, it shows the Galaxy SII screen, then goes into a black screen. I can't turn it back on again, so I remove the battery and it can restart. Does the same thing though. I followed your instruction and http://e4gtcm.blogspot.com/p/cm9-install-guide.html
What did I do wrong? I am worried I messed up my phone completely.
EDIT: So I went back into recovery and it was now a new version of CWM. I did everything over again; factory reset, cache, dalvic, and it is doing the same thing. Boots up "Galaxy SII" screen, then a black screen. It seems to still be on in the black screen seeing that it doesn't "turn" on again. I can hold if for 15 second or so for it to reset and does the same thing. Why is there a black screen?
Sorry for not checking back. Your probably freaking right now lol but relax your at a good point everything is fine.
Either a bad download or the nightly you went with happens to be a baddy. I am still on 10/20 I was gonna flash 10/28 today but the weather is screwing with me. goo.im seems pretty slow today.
Download another, battery pull and hold vol up + power until it hits recovery then go into mounts and mount usb storage hook a usb cable to the pc and copy over another build. I would say try 10/20 just because it works pretty good but that won't stop another bad download in which case you have to try try again.
Worst case from here we can just odin you back to stock rooted FH13 or your choice of other. Your phone is fine from what you have told me so far. I can upload one of the builds I have if you think ti would help any.
RainMotorsports said:
Sorry for not checking back. Your probably freaking right now lol but relax your at a good point everything is fine.
Either a bad download or the nightly you went with happens to be a baddy. I am still on 10/20 I was gonna flash 10/28 today but the weather is screwing with me.
Download another, battery pull and hold vol up + power until it hits recovery then go into mounts and mount usb storage hook a usb cable to the pc and copy over another build. I would say try 10/20 just because it works pretty good but that won't stop another bad download in which case you have to try try again.
Worst case from here we can just odin you back to stock rooted FH13 or your choice of other. Your phone is fine from what you have told me so far.
Click to expand...
Click to collapse
Phew! I was pretty positive that I could still get back to something working, just my paranoid self was getting tense. I got 10/28. I guess I will do 10/20. Do you know what the other updates have? I would hate to install something that isn't working its most efficient.
Again, thank you so much. You were of great help! Good luck with the weather issue. Hope you're safe!
I stopped following chris's experimentals so i am not sure what the most recent focuses have been. The Nightlies have whatever code was commited. They are built automatically and can range from very stable to not booting at all. I dont have any of the links on me but someone can get it to you. Reading commits is not exactly 100% user friendly especially if your not a developer. But they often have clues. I would follow the CM9 Beta thread and the CM9 User Support Threads - http://forum.xda-developers.com/showthread.php?t=1874374 and http://forum.xda-developers.com/showthread.php?t=1720771
I used to DL nightlies from work over 3g or 4g all the time and would get a bad dl and end up in situations where even my experienced self felt like I couldn't fix it till I got home and always got the phone running within an hour without the assistance of a near by pc.
I am uploading 10/20 to my server just in case its in Chicago so if your away from the weather it should be unaffected for the most part. Glad its not in NY anymore.
EDIT - http://android.rainmotorsports.net/10-20-CM9-d710-KANG.zip the md5 hash as I have it is 66246125ACDBEF2EBF2144E0CBFEBB7B and it matches the md5 listed on goo.im
RainMotorsports said:
I stopped following chris's experimentals so i am not sure what the most recent focuses have been. The Nightlies have whatever code was commited. They are built automatically and can range from very stable to not booting at all. I dont have any of the links on me but someone can get it to you. Reading commits is not exactly 100% user friendly especially if your not a developer. But they often have clues. I would follow the CM9 Beta thread and the CM9 User Support Threads - http://forum.xda-developers.com/showthread.php?t=1874374 and http://forum.xda-developers.com/showthread.php?t=1720771
I used to DL nightlies from work over 3g or 4g all the time and would get a bad dl and end up in situations where even my experienced self felt like I couldn't fix it till I got home and always got the phone running within an hour without the assistance of a near by pc.
I am uploading 10/20 to my server just in case its in Chicago so if your away from the weather it should be unaffected for the most part. Glad its not in NY anymore.
EDIT - http://android.rainmotorsports.net/10-20-CM9-d710-KANG.zip the md5 hash as I have it is 66246125ACDBEF2EBF2144E0CBFEBB7B and it matches the md5 listed on goo.im
Click to expand...
Click to collapse
I just got it downloaded. It is now up and running perfectly. I appreciate all your help man, thanks a bunch. I live in Washington state. So the weather wont affect me.
Good evening all. I hope this is the right forum to post my question about recovery for my e4g touch. I recently rooted my phone and my phone is currently on the fi27 build. Is there a recovery i can put on there now to go ahead and start flashing ruins, or will i have to wait for qbkng77 to post his video on you tube on putting cwm recovery on fi27 rooted e4g touch? Thanks in advance for the help!
Sent from my SPH-D710 using xda app-developers app
n1stunna84 said:
Good evening all. I hope this is the right forum to post my question about recovery for my e4g touch. I recently rooted my phone and my phone is currently on the fi27 build. Is there a recovery i can put on there now to go ahead and start flashing ruins, or will i have to wait for qbkng77 to post his video on you tube on putting cwm recovery on fi27 rooted e4g touch? Thanks in advance for the help!
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I assume you do the same thing as I did. Get the EL26 kernel and flash it with Mobile Odin. I would wait on someone else to confirm that though.
Another really quick question. I want to overclock my phone. I tried using setcpu and the overclocker it came with. It only goes to a max of 1200 but I know it can go higher. I am guessing I need another kernel. What kernel can I use?
joshlete said:
Another really quick question. I want to overclock my phone. I tried using setcpu and the overclocker it came with. It only goes to a max of 1200 but I know it can go higher. I am guessing I need another kernel. What kernel can I use?
Click to expand...
Click to collapse
You either need a kernel with built in over clock support(you'd see the CPU slider go up to 1400-1600 automatically if it was). Or a kernel that supports over locking in tegrak, which you "load over clock module" with in tegrak.
Both Kuban kernel and some of Agats kernels have built in support, mine you need to use tegrak as I have not added built in yet
You can get them all in rwilco's (awesome) kernel repository stickied in development
Sent from my SPH-D710 using xda premium