Related
Due to an error in the kernels we've been flashing to our devices, a lot of users have been experiencing a FULL BRICK. Full brick meaning you may as well play golf with your phone, it's dead.
I've been told there is a fix, BUT YOU MUST NOT FLASH ANYTHING FROM CWM. The bug is originating from flashing a corrupt kernel from CWM or mobile ODIN.
Here's a cut from the article:
Thanks to XDA Elite Recognized Developer Entropy512, we have learned that most devices that are receiving leaks are at a very high risk of never waking up after a flash. It turns out that there is a major bug in the leaked ICS kernel that affects the /data partition in the eMMC chip, which apparently gets corrupted during certain operations such as wiping and flashing. This was originally believed to be affecting only operations performed in custom recoveries such as CWM. However, there have been reports of hard bricks being produced from the flashing from stock recoveries as well. The affected devices are:
All Epic 4G Touch (SPH-D710) ICS leaks
All Galaxy Note (GT-N7000) ICS leaks
The AT&T Galaxy S II (SGH-I777) UCLD3 leak – and probably all others
Korean SHW-M250S/K/L official releases and any kernel built from their source
Entropy and other devs have posted several warnings scattered throughout the site, in which they explain in detail what is happening. Our suggestion is that users should stay away from flashing ICS from leaks until the bug in the kernel has been completely fixed—unless of course, you are looking to hard brick your device. Remember, this is not something that can be resurrected via Unbrickable Mod or even via JTAG, as this is a firmware error in the eMMC.
Click to expand...
Click to collapse
Just like you, I don't wish to brick my E4GT. xST4T1K has posted a comprehensive guide to find your options on removing the affected ICS kernels from your device, and hopefully resulting in you not bricking the crap out of your phone. Go check this page: http://forum.xda-developers.com/showthread.php?t=1525495
I DO NOT take credit for finding this bug, credit goes to Entropy512 and XDA TV's EGZTHUNDER1 for alerting me of this bug. I have safely removed the affected ICS kernel from my phone and custom builds, now it's your turn.
The only reason I'm requesting a sticky in the wrong forum (Yes, I know I posted in the development branch) is because most users won't know about these affected kernels before trying their newly rooted E4GT into some ICS bling.. Next thing you know, you've got a two day old brick with a shiny screen.
Please, once again, GO TO THIS PAGE and explore the options of returning your phone back to dry land.
As a reminder, DO NOT FLASH ANYTHING FROM CWM OR MOBILE ODIN.
While I have heard that flashing a non-ICS kernel from ODIN has fixed these issues, we're looking more into that now.. I have alerted xST4T1K of this, and we'll get back to you with confirmed results.
Safe flashing, XDA members.
Maybe this sticky from the general forum should just be moved over to here.
http://forum.xda-developers.com/showthread.php?p=23149990
Sent from my SPH-D710 using Tapatalk 2
Weve kinda known this for a while now since the February leaks... js. Still, safe flashing everyone lol.
first off, many have been warned by all the devs, myself and other users since these unlocked recoveries came out and then the repacked recoveries started up again...
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
If you do what is said above, you won't brick your device.
Why do you wipe from the stock when all you have to do is flash 1 file to do it all for you?
NOW again....
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
Quite Easy.
In the end, it's called following directions.
Edit: just to clarify... Wiping cache/dalvik cache from stock or cwm repacked recoveries is safe.
The issue is Wiping Data (Don't use the option)
bigpeng said:
first off, many have been warned by all the devs, myself and other users since these unlocked recoveries came out and then the repacked recoveries started up again...
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
If you do what is said above, you won't brick your device.
Why do you wipe from the stock when all you have to do is flash 1 file to do it all for you?
NOW again....
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
Quite Easy.
In the end, it's called following directions.
Click to expand...
Click to collapse
So my question is... What about flashing mod's that require only wiping cache and dalvik??? I guess I've been lucky with wiping cache and dalvik from cwm recoveries but does this mean no more mod's until source is released???
Sent from my SPH-D710 using Tapatalk 2
bigpeng said:
first off, many have been warned by all the devs, myself and other users since these unlocked recoveries came out and then the repacked recoveries started up again...
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
If you do what is said above, you won't brick your device.
Why do you wipe from the stock when all you have to do is flash 1 file to do it all for you?
NOW again....
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
Quite Easy.
In the end, it's called following directions.
Click to expand...
Click to collapse
In a world where users flash before they research, common sense doesn't have a stronghold.
DjKurt said:
So my question is... What about flashing mod's that require only wiping cache and dalvik??? I guess I've been lucky with wiping cache and dalvik from cwm recoveries but does this mean no more mod's until source is released???
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
The issue is from Wiping Data from stock and cwm recoveries, you can wipe cache and dalvik with no worries. Those don't mess with partitions.
Sent from my SPH-D710 using xda premium
You may be able to flash wipe mods and such but imsince I bricked mine doing just that. I will not flash anything in an ics recovery. I will Odin modems and will flash roms and kernels in one session and that is always coming from stock GB. Take for what its worth. Not saying the above mentioned ways aren't worth noting. But flashing the format script in blue cwm while on ICS is what bricked me.
scarmon25 said:
You may be able to flash wipe mods and such but imsince I bricked mine doing just that. I will not flash anything in an ics recovery. I will Odin modems and will flash roms and kernels in one session and that is always coming from stock GB. Take for what its worth. Not saying the above mentioned ways aren't worth noting. But flashing the format script in blue cwm while on ICS is what bricked me.
Click to expand...
Click to collapse
That sucks, sorry to hear that...
I was one of the first to test cwm repacked recoveries for agat63 since FE10 and have flashed 37 times to and from different roms and done backups and restores countless times and I've been fine.
I haven't been fearful of any bricks since I tested these repacked kernels.
Hope it does get figured out once source hits though.
Edit: btw what kernel (with or without cwm repack?) did you brick in?
Sent from my SPH-D710 using xda premium
It was back when CM9 first was released. I was using the el26 cwm kernel to flash. I was on one of the ice builds I can't remember. I odined the kernel cwm combo el26 and then ran a format all and flashed cm9 and ggot the blue light special haha
Its all good though. I have read alot of info in this including the one mentioned. One thing that was mentioned in one of them is that the bug had been triggered be deleteing a large file off the internal memory. That worried me. So I've been weary of ICS builds since. The fact that the issue seems to be that info getting wrote to a certain block of the emmc has me worried that it could be triggered by more then wiping of flashing. I have ran agats ROMs and I have to say he seems to be doing something right. Whether it is because he is staying TouchWiz or what for some reason his users seem tto not have many issues. But just keep in mind that it may not just be kernel/recovery related.
Safe flashing is key and I never want to see someone brick. Just be careful in whatever you do.
Sorry, I haven't had much of a chance to update my thread lately but I will soon. With all the leaks that were consistently being released, it wasn't feasible to update it every other day. The thread already has everything you need to know about bricking so I figured if you couldn't figure out how to prevent a brick with the information given, then you should probably buy an IPhone and never attempt flashing in the first place.
xST4T1K said:
Sorry, I haven't had much of a chance to update my thread lately but I will soon. With all the leaks that were consistently being released, it wasn't feasible to update it every other day. The thread already has everything you need to know about bricking so I figured if you couldn't figure out how to prevent a brick with the information given, then you should probably buy an IPhone and never attempt flashing in the first place.
Click to expand...
Click to collapse
I couldn't have said it any better, my friend!
As far as those who've bricked their phones, it is truly unfortunate.. Google themselves has been brought into light on this situation, and are working to correct this issue in the kernels that they've been adding in with their firmware.
As far as your useless phones go.. Try filing for an insurance claim, I guess! NOT my professionally recommended advice.. But IF someone were to have stolen that useless phone of yours and you were to never see it again.. Well, who am I to say that's not a reason to get a replacement from asurion! Lol!
By the way, xST4T1K.. Bumped you thanks count up a little more.
Thank goodness I ran into these threads before I decided to flash anything else.. Been running a solid ICS rom for a few weeks, now. But I'd rather get back to safe land on GingerBread Island and use Apex Launcher. Wouldn't care for the huge difference in the settings menu. Would miss the lockscreen, though.. Not aiming my finger at an unlock tab has gotten habitual!
crazy.. not sure i agree with this thread.. its scaring people away from trying awesome roms.. if you search in any ics rom or aosp ics rom you hear little about people bricking there phones.. there are clear instructions to install and if you dont know what your doing and cant follow instructions dont do it or you will have a brick. ive been on ics since the first leak and have had to odin many times after a "soft brick" from me not following instructions but its simple.. dont format data on any ics kernel/cwm and you'll be fine..
Sent from my SPH-D710 using XDA
elliwigy said:
crazy.. not sure i agree with this thread.. its scaring people away from trying awesome roms.. if you search in any ics rom or aosp ics rom you hear little about people bricking there phones.. there are clear instructions to install and if you dont know what your doing and cant follow instructions dont do it or you will have a brick. ive been on ics since the first leak and have had to odin many times after a "soft brick" from me not following instructions but its simple.. dont format data on any ics kernel/cwm and you'll be fine..
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I would never want to scare anyone away from trying these great builds on XDA. What I do want though is to make people aware that no matter how many tines you flash something. Always treat the flash your about to do as if it was your first. Sometimes we get to comfortable in what we're doing. We have to remember that this is a pretty expensive device and if something happens you may be buying a new one outright. Not everyone has insurance or can throw out that kind of cash. Do safe flashing practices and make sure you read the OP. When flashing leaked software make sure to flash from stock or the most current OEM released build such as EL29 in this case. Verify the right files are in the right slots of Odin. Make sure you're flashing files in the right sequence when in a custom recovery. Thing like that. I believe in the openness of android and never want to see anyone say they aren't going to flash something because they are scared. With the right ammount of reading and precautions. There is no reason to be scared.
Just for example. And this is not an exaggeration. Between this phone,my wife's phone, my last phone, my wife's last phone, and numerous friends phones. I have well over 200+ flashes. I have only had one actual brick. And that brick was because I got too comfortable in what I was doing. So, odds are if you take tthe time to do it right. You will succeed. Also.
i cant figure out why this is not locked yet....
i agree scarmon.. you said it better than i could.. if i wasnt tech savvy and i read the op i would have been scared away.. it says in all caps not to flash in cwm and says many have experienced bricks.. it can be worded differently but its freedom of speech.. when the initial leak came out and we had rogue ics kernels and the LOSt kernel we werent sure why people were having bricks until we figured out what was causing it.. we've known this for a while and since then hard bricks have dropped drastically.. and every single developer insisted not flashing from ics kernels and every rom has a disclaimer in the op for this reason.. only bricks ive read have been user error for a while ie. unplugging device during odin flash or battery dieing during mobile odin flash etc.. plus this is in the dev thread.. right now most people come here for ics roms since thats what devs are working on.. and many have gone safely back to gingerbread many times.. the ics roms have hundreds of thousands if not millions of hits and how many posts about hard bricks?
Sent from my SPH-D710 using XDA
I've been flashing ICS roms since FB17 and haven't had any bricks. I've been making sure to only flash things from EL26 and it's been smooth sailing.
Now I'm running the most recent AOKP and it's running very well.
Your credit is pretty thin too. Entropy is a big name in this issue but him and some random dude that apparently notified you very very late about this issue doesn't even cover half of it.
The front page news on the issue was pretty late as well. Just lets the general population know about it.
ijoshv2 said:
While I have heard that flashing a non-ICS kernel from ODIN has fixed these issues, we're looking more into that now.. I have alerted xST4T1K of this, and we'll get back to you with confirmed results.
Click to expand...
Click to collapse
Its things like this "While I have heard" that is the problem with your post. That and begging for a sticky, talk to a moderator if you feel its important.
Flashing a non-ics kernel through ODIN does not fix any issue. Flashing from a safe Kernel avoids the issue, If your on ICS flashing the GB Kernel from ODIN would be the safe method. Gingerbread as far as we have known and hundreds of flashes per person per hundreds of phones later. No one has been known to trigger the eMMC firmware bug though gingerbread. So yes flashing from a Gingerbread kernel as we have since the phone came out is the safest known way. You don't need anyone to tell you that.
You come in and say "Do not flash anything from CWM". This is inaccurate it suggests one can not flash from EG30+ CWM which has never been a known danger. Obviously EK02 would be more popular due to supporting full modems rather than patch. EL26 was the last to have true CWM which is why EL29 Rogue is less often suggested.
ijoshv2 said:
The only reason I'm requesting a sticky in the wrong forum (Yes, I know I posted in the development branch) is because most users won't know about these affected kernels before trying their newly rooted E4GT into some ICS bling.. Next thing you know, you've got a two day old brick with a shiny screen.
Click to expand...
Click to collapse
The danger is not in flashing ICS. The unknowing user is going to be flashing ICS from EL29 which is safe. The danger is after they are there, and they try a factory reset, or install a CWM or Unlocked Recovery Kernel and flash something, or flash an update.zip through stock recovery. Yes they need to know, the information should be accurate however.
If anyone wants details of this emmc firmware bug, there's some really knowledgeable people in this thread.
http://forum.xda-developers.com/showthread.php?t=1644364
The info is very detailed, but these are the individuals to watch. OP if your serious about helping our community with this emmc bug, I hope you join in that conversation instead of asking to sticky this thread.
Sent from my SPH-D710
I just got this phone (Samsung Galaxy S2, Epic 4G Touch) a few months ago. I'm tired of waiting for ICS to come out. I already know that I have a hard brick bug chip (from running the checker app someone here made). I think here are all of my options:
1. Install a leaked ICS ROM. Can I be safe from bricking if I do it right?
2. Install Cyanogenmod ICS. Am I safe here?
3. Wait for ICS or Jelly Bean to be released from Sprint for my phone. How long will that take??
What I want:
1. ICS
2. Better battery life: is this a kernel or ROM thing?
3. Candied Bacon
Awk34 said:
I just got this phone (Samsung Galaxy S2, Epic 4G Touch) a few months ago. I'm tired of waiting for ICS to come out. I already know that I have a hard brick bug chip (from running the checker app someone here made). I think here are all of my options:
1. Install a leaked ICS ROM. Can I be safe from bricking if I do it right?
2. Install Cyanogenmod ICS. Am I safe here?
3. Wait for ICS or Jelly Bean to be released from Sprint for my phone. How long will that take??
What I want:
1. ICS
2. Better battery life: is this a kernel or ROM thing?
3. Candied Bacon
Click to expand...
Click to collapse
I would wait, supposedly ICS is rumored to roll out by Samsung on the 20th, so I wouldn't risk it...But, if you insist, I would personally go with Cyanogen Mod Alpha 6, just make sure to flash it correctly (I recommend Flash EL26, then Cyanogen in its CWM recovery) Just make sure you read through the bug list in Cyanogen Mod Alpha 6 first to make sure that everything you need is working. Honestly though, I would just wait for the update by Samsung if you want to play it safe.
Link to Stock EL26 with CWM http://forum.xda-developers.com/showthread.php?t=1605355
Please Note: I am in to way responsible if you or anyone reading this bricks or damages their device in any way. If the reader does not agree to this, please disregard the text above immediately, and do not let it influence you and/or guide you in any way.
ICS is being released over the air starting today
There are multiple discussions here in our General section http://forum.xda-developers.com/forumdisplay.php?f=1282
2momo123 said:
I would wait, supposedly ICS is rumored to roll out by Samsung on the 20th, so I wouldn't risk it...But, if you insist, I would personally go with Cyanogen Mod Alpha 6, just make sure to flash it correctly (I recommend Flash EL26, then Cyanogen in its CWM recovery) Just make sure you read through the bug list in Cyanogen Mod Alpha 6 first to make sure that everything you need is working. Honestly though, I would just wait for the update by Samsung if you want to play it safe.
Link to Stock EL26 with CWM http://forum.xda-developers.com/showthread.php?t=1605355
Please Note: I am in to way responsible if you or anyone reading this bricks or damages their device in any way. If the reader does not agree to this, please disregard the text above immediately, and do not let it influence you and/or guide you in any way.
Click to expand...
Click to collapse
someguyatx said:
ICS is being released over the air starting today
There are multiple discussions here in our General section http://forum.xda-developers.com/forumdisplay.php?f=1282
Click to expand...
Click to collapse
Thanks guys. I've been googling articles on the release date for months and finally when I decide to ask here, it's out. :silly: Can't wait to get the update, hope I get it soon. Thanks!
You can wait for the offical ota update. but just because it started today doesn't mean you'll get it today or tomorrow. I know I had to wait a week with my old epic 4g(not touch). you can look thru the different roms to see which one would fit your needs better. If you odin the leaked FF18 version you will be safe. Battery life mostly depends on how you use your phone and what settings you have. when i was running GB i had mine undervolted, sync turned off and screen brightness turned way down. The biggest thing about flashing ICS roms is follow the OP's instuctions. Since we now have the new ICS kernel (from source code) flashing ICS to ICS should be safe. but I can't say for sure i haven't tried it yet.
What is candied bacon? never heard of it
g_ding84 said:
You can wait for the offical ota update. but just because it started today doesn't mean you'll get it today or tomorrow. I know I had to wait a week with my old epic 4g(not touch). you can look thru the different roms to see which one would fit your needs better. If you odin the leaked FF18 version you will be safe. Battery life mostly depends on how you use your phone and what settings you have. when i was running GB i had mine undervolted, sync turned off and screen brightness turned way down. The biggest thing about flashing ICS roms is follow the OP's instuctions. Since we now have the new ICS kernel (from source code) flashing ICS to ICS should be safe. but I can't say for sure i haven't tried it yet.
What is candied bacon? never heard of it
Click to expand...
Click to collapse
Candied bacon is bacon cooked with brown sugar on it.
Would me installing an FF18 today be any different than the one to be pushed out later? Does Cyanogenmod have FF18 for my phone? Or is that not how Cyanogenmod works..
So a ROM is specific to a phone, and a kernel is specific to a ROM, but is a kernel specific to a ROM for a phone, or is a kernel specific to any phones's version of a ROM? S*** just got confusing..
If I use Sprint's pushed ROM, will I become unrooted? Do new ROMs come with new accompanying kernels?
Ugh I'm so confused.
Candied bacon is bacon cooked with brown sugar on it.
AWESOME
Would me installing an FF18 today be any different than the one to be pushed out later?
Yes! If you use sfhub's One-Clicks http://forum.xda-developers.com/showthread.php?t=1721229 you will have FF18 AND root. If you update the OTA you will lose ROOT.
Does Cyanogenmod have FF18 for my phone? Or is that not how Cyanogenmod works..
Yes there is a CM9 for this phone (right now on Alpha 6). IF you plan on flashing that make absolutely sure you follow the precise instructions or you will surely paper weight your phone! http://forum.xda-developers.com/showthread.php?t=1563658
So a ROM is specific to a phone, and a kernel is specific to a ROM, but is a kernel specific to a ROM for a phone, or is a kernel specific to any phones's version of a ROM? S*** just got confusing..
Yes it can be confusing! So please, please take some time to read through the stickies and posts here! A little time spent reading through all the threads will save you killing your device.
Good luck
leaderbuilder said:
Candied bacon is bacon cooked with brown sugar on it.
AWESOME
Would me installing an FF18 today be any different than the one to be pushed out later?
Yes! If you use sfhub's One-Clicks http://forum.xda-developers.com/showthread.php?t=1721229 you will have FF18 AND root. If you update the OTA you will lose ROOT.
Does Cyanogenmod have FF18 for my phone? Or is that not how Cyanogenmod works..
Yes there is a CM9 for this phone (right now on Alpha 6). IF you plan on flashing that make absolutely sure you follow the precise instructions or you will surely paper weight your phone! http://forum.xda-developers.com/showthread.php?t=1563658
So a ROM is specific to a phone, and a kernel is specific to a ROM, but is a kernel specific to a ROM for a phone, or is a kernel specific to any phones's version of a ROM? S*** just got confusing..
Yes it can be confusing! So please, please take some time to read through the stickies and posts here! A little time spent reading through all the threads will save you killing your device.
Good luck
Click to expand...
Click to collapse
Thanks for your help! I'll be sure to browse the stickies around here.
So what do you suggest to me? Installing Cyanogenmod 9 A6, or a rooted FF18? Also, will I be able to keep all of my data when installing these?
edit: It looks like both options will reset my data. I was really hoping to avoid that. I'm wondering how to save data from things like certain games...
edit2: Also, I am wondering if I can customize my boot up screen with Cyanogenmod, because SAMSUNG doesn't allow you to do it with their dumb custom boot animation format. I havn't seen anything about being able to do it with C9 on a phone with Samsung's custom boot anim format.
If you use sfhub's one click 'no data' it will preserver your data and give you FF18 plus root.
Since you are just starting out that is what I would recommend. It will give root, keep your data and the latest modem and everything (stock) Touch Wiz
If you want CWM you can use Mobile Odin [ https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro&hl=en ] to add Agat's latest safe recovery found here http://forum.xda-developers.com/showthread.php?t=1767421 One of the best paid apps around if you plan on doing any modding. Watch the tutorial and read how to use it. Pretty simple. Biggest issue I found is that when selecting a kernel or other update you have to scroll down (way down) to click on apply update - easy to miss.
Again take the time and read through the entire posts. Many times questinon you are going to ask (or will come up with soon enough) will be answered.
Welcome and hope you enjoy the phone.
and if I or anyone else helps you out feel free to click on that 'thanks' button.
leaderbuilder said:
If you use sfhub's one click 'no data' it will preserver your data and give you FF18 plus root.
Since you are just starting out that is what I would recommend. It will give root, keep your data and the latest modem and everything (stock) Touch Wiz
If you want CWM you can use Mobile Odin [ https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro&hl=en ] to add Agat's latest safe recovery found here http://forum.xda-developers.com/showthread.php?t=1767421 One of the best paid apps around if you plan on doing any modding. Watch the tutorial and read how to use it. Pretty simple. Biggest issue I found is that when selecting a kernel or other update you have to scroll down (way down) to click on apply update - easy to miss.
Again take the time and read through the entire posts. Many times questinon you are going to ask (or will come up with soon enough) will be answered.
Welcome and hope you enjoy the phone.
and if I or anyone else helps you out feel free to click on that 'thanks' button.
Click to expand...
Click to collapse
Thanks, I'll install sfhub's NODATA. Now I'm wondering whether to give my brother the stock install or to root his... He has the same phone.
You can also download titanium backup or my backup. Both are in the market. I use it to back up all my apps. There are other programs to backup SMS and call logs. Sometimes you can have issues with not wiping the data.
Sent from my SPH-D710 using xda app-developers app
You really can't go wrong with sfhub's one-clicks. They are essentially OTAs (released to development) that sfhub as added root to and made them unbelievably simple to use. And since the Sprint OTA build is FF18 your good to go. Just don't take the OTA if you are presented with it as you'll lose root.
With root you will be able to use some great tools (Titanium Backup, Mobile Odin, WiFi tether etc.) and be able to remove loads of carrier 'bloatware'.
I'd start that way and read up on using CWM and the different tools and options here.
I flashed ICS, but personally I wish I had stayed on GB for a little while longer. ICS is going out over the air today, and it would be nice to allow the devs a little more time with it. I recommend Calkulins latest GB ROM.
Personally, I recommend MIJJz ICS. There's a couple of versions to meet your needs. I use "Goodness" which has all the bells and whistles. I imagine with the official ICS release coming out that he'll be updating his ICS Roms soon, especially Goodness. If you try it out, let us know what you think.
[ROM][TN] MIJJz ICS {GOODNESS 7/9}{MINI 6/30}{LTD 6/25}{NO-NAME}{SLIM}:
http://forum.xda-developers.com/showthread.php?t=1512419
I've been running sfhub's NODATA ICS ROM for the past day and Agat's Kernel and it's been running pretty well. Thanks all!
I have been considering Mijjs Goodness, thanks for that.
I'm currently running GB El29 and am looking to update. I've done a lot of reading around the forum, the wiki, and a few other websites, and I'd just like a little bit of clarification. I figure I'd ask now, before doing anything, as opposed to asking later, after something's gone wrong.
Looking at the Wiki, I was considering updating to Calkulin's E4GT 2 v1.6, or unrooting and then waiting for the Official ICS update (it was rerolled today, apparently.) Or, to Blazer, but I'm not sure if going to the ICS version or GB version is best.
My question - The process to update - Nandroid, Flash Format All, Flash Rom, Success? I've noticed a lot of installs say to "Wipe All", and I assume that's what Flashing Format All does, correct? I just don't want to mess up - I had no problems rooting, following that guide I mentioned, and I've done a lot of reading...I just want to confirm before doing anything. I mean, I know, wipe delvic and clear cache, but Format All does that, correct?
I rooted my phone using "How to Root Galaxy S2 Epic 4G Touch! [NEW][SPH-D710]" rom Epic4gtouchroot.com. I'd post a link, but I've fewer than 10 posts. All I've done, outside of root, is install the Beats sound files. That's really it.
Any help at all would be greatly appreciated.
Read this 10 times over then you should be fine.
http://forum.xda-developers.com/showthread.php?t=1525495
If you are interested in certin roms read threw the rom post to see if people have already answerd the questions you seek. Some devs request you flash different ways so read the OP in the post of the roms you are considering
UnOfficial
Read this once, stay with gingerbread, try Calks E4GT V. 3.0 YOU won't regret it.
Pp.
Delivered to you via Mayan technology .
PanchoPlanet said:
Read this once, stay with gingerbread, try Calks E4GT V. 3.0 YOU won't regret it.
Pp.
Delivered to you via Mayan technology .
Click to expand...
Click to collapse
Yeah, that's what I was thinking of going with. I've read over his topic several times, and even though I'm really not a fan of the transparent notification tray, most of the included mods sound really, really useful. Thanks for the heads up.
And thank you too, jugaloo. I actually have that page bookmarked on my phone lol. I've already made several nandroid backups - I plan on making a titanium backup in a moment. My only concern now is th process from going from El29 GB to E4GT 3. Rereading that thread several times has me wondering - I download the ROM, place it on the SD, boot into recovery, clear delvic and cache, run Format all, then install the ROM, correct? I already have a nandroid backup, so in case anything here goes wrong, I can just flash the backup back on, correct?
IceCatraz said:
Yeah, that's what I was thinking of going with. I've read over his topic several times, and even though I'm really not a fan of the transparent notification tray, most of the included mods sound really, really useful. Thanks for the heads up.
And thank you too, jugaloo. I actually have that page bookmarked on my phone lol. I've already made several nandroid backups - I plan on making a titanium backup in a moment. My only concern now is th process from going from El29 GB to E4GT 3. Rereading that thread several times has me wondering - I download the ROM, place it on the SD, boot into recovery, clear delvic and cache, run Format all, then install the ROM, correct? I already have a nandroid backup, so in case anything here goes wrong, I can just flash the backup back on, correct?
Click to expand...
Click to collapse
I just run the format x2 script made by ruj in the blu kuban thread. Then i follow the devs op to install. From what i see you have your feet planted and ur about to make that plunge. Id take the next step and try the flash. Id go with a different rom the the fe22 is out of date and calk has moved on. Try blu kubans rom its super stable and ita built from source. I myself like gb better.
UnOfficial
juggalo1300 said:
I just run the format x2 script made by ruj in the blu kuban thread. Then i follow the devs op to install. From what i see you have your feet planted and ur about to make that plunge. Id take the next step and try the flash. Id go with a different rom the the fe22 is out of date and calk has moved on. Try blu kubans rom its super stable and ita built from source. I myself like gb better.
UnOfficial
Click to expand...
Click to collapse
I was thinking that - Calk's topic was updated in May, while blukuban was updated in February. I mean, I can always try both, right? I'd like to go with Calk's first, then try blukuban, only because BK is heavily themed. But either way, thanks!
Edit
I didn't realize the blukuban thread had updates outside of the OP. It was very recently updated. I might check that one out first.
Yes the blu kuban ics is always up todate and he is there for the people. If you want ics builds that are more stockish id aokp they have theming going on but is nice and stable. Read all of the op and there sites for correct install. Cm9 alpha 6 is also really good. Blazers rom is also really good. Those are all stockish built from source. For gb roms id go with either calks 3.0 or UnOfifcials ics gb rom. For me gb gives me most bang for battery and bandwith. Those last two roms are highly recomended. Calks is super fast stock with options for themes. Unofficial gb ics is themed lightly and is very good for battery and the animations are nice
UnOfficial
Alright, awesome. Waiting for my battery to finish charging (my phone reset while performing a titanium backup, and the battery life dropped from 44 to 9, so I'm getting it back up to at least 50.)
So just to recap
-
To Install
Boot to recovery
Make a NAND Backup
Wipe Phone (Format All/wipe delvic/wipe cache)
Install ROM
Right? That's what Blukuban's install requires, and Calk's doesn't have any special instructions, outside of " a wipe is recommended BEFORE flashing if coming from another ROM", which is what the Format All is for, correct?
You've been insanely helpful. Thank you so much! I'm also looking into UnOfficial (it's not on the Wiki, so I didn't really know about it until you mentioned it.
IceCatraz said:
Alright, awesome. Waiting for my battery to finish charging (my phone reset while performing a titanium backup, and the battery life dropped from 44 to 9, so I'm getting it back up to at least 50.)
So just to recap
-
To Install
Boot to recovery
Make a NAND Backup
Wipe Phone (Format All/wipe delvic/wipe cache)
Install ROM
Right? That's what Blukuban's install requires, and Calk's doesn't have any special instructions, outside of " a wipe is recommended BEFORE flashing if coming from another ROM", which is what the Format All is for, correct?
You've been insanely helpful. Thank you so much! I'm also looking into UnOfficial (it's not on the Wiki, so I didn't really know about it until you mentioned it.)
Click to expand...
Click to collapse
Charge the bartery more. Use a wipe script dont touch the fomat that is built into the cwm while flashing a ics rom. If you use the wipe x2 script found here
http://forum.xda-developers.com/showthread.php?p=25448865
U should be good. It wipes everythings even both of the caches twice. If you already have a newer nandroid id just go with that instead of making a new one everytime you flash. If possible download the roms to pc check the md5 check sums make sure they match. If they match transfer to the phone. When downloading to the phone it has a higher chance of a bad download. I try and flash at 75% battery incase of error and you have to restore a previous nandroid. If you want read this post about the eMMc bug. Most roms are safe now but some are not current.
http://forum.xda-developers.com/showthread.php?t=1644364
Not trying to scare you with that last link you should know about it before hand so you know the dangers of flashing a non safe ics roms. If you have any more queations shoot. But i think your good to go
UnOfficial
One more thing. Qbking27 has install video guides for 90% of the roms in the threads of the rom. Id watch those before installing that rom you want. Some times they are buried in the op. You can use them as a step by step as you install. Best if luck to you and i want a report once you get your new custom rom on your phone.
UnOfficial
You got it!
I'm doing a GB build - from what I've come across, GB just gets better battery life, and I just feel more comfortable using it. At least, until the official ICS rolls out from Samsung. If that one is well received, and it's worth it, I'll unroot/wipe fresh and try it out.
That being said though, I'll use x2 then. Will it matter if I do both, just for good, measure? (Both x2 and FormatAll)
And yes, I'll be downloading to PC first, then transferring. I feel more comfortable doing it that way. I'll be doing Calk's 3.0 first, and if I don't like it, I'll try either Unofficial or BluKuban.
And once it's done charging more, and I perform the install, I'll report back, with a screenshot or two as well.
IceCatraz said:
You got it!
I'm doing a GB build - from what I've come across, GB just gets better battery life, and I just feel more comfortable using it. At least, until the official ICS rolls out from Samsung. If that one is well received, and it's worth it, I'll unroot/wipe fresh and try it out.
That being said though, I'll use x2 then. Will it matter if I do both, just for good, measure? (Both x2 and FormatAll)
And yes, I'll be downloading to PC first, then transferring. I feel more comfortable doing it that way. I'll be doing Calk's 3.0 first, and if I don't like it, I'll try either Unofficial or BluKuban.
And once it's done charging more, and I perform the install, I'll report back, with a screenshot or two as well.
Click to expand...
Click to collapse
Just use the wipe x2 that does everything you need. Blu kubans gb rom is good but wifi is whacky. Id go with his ics build. Well your set good luck!
UnOfficial
Alright so, I installed it, and all is working well. It's actually a bit...erm, slow? Whenever I swipe from screen to screen on the homepage it's a bit laggish. But it works! I'll run around with it for a little while and see how it works. I'm in the process of reinstalling my older apps, updating my contacts and such.
Thanks for all of your help!
Edit
A little worried, to be honest. Some of the apps I'm trying to install is giving me the "Package file is invalid" error off of the Google Market. Dropbox, Amazon, etc. Not sure what to make of it, to be honest.
Try and clear the cache for the market. If your using tb try to unmount the sd card if that dont work do fresh installs off the market place . Also go into recovery and clear the cache and dalvik.
UnOfficial
juggalo1300 said:
Try and clear the cache for the market. If your using tb try to unmount the sd card if that dont work do fresh installs off the market place . Also go into recovery and clear the cache and dalvik.
UnOfficial
Click to expand...
Click to collapse
Done. I cleared both caches, and so far, all of the problems I've had with the market is gone. (Dropbox didn't install on the first try, but it did after the second.)
I've replaced the default touchwiz interface with Launcher Pro (TW was running wicked slow - loads of lag with just basic scrolling) and it seems to be running well. And it's definitely saving on battery life.)
That being said, it's not really my cup of tea. I restored my contacts and such, but eh. I think I'll try UnOfficial, and if it's not better, either go back to el29 or update to official ics.
I'll likely keep this one until tomorrow. You've been such a huge help. Thank you so much.
Actually, with launcher pro replacing it, this is pretty good. I want to mess with it more. I'll run it for a few days and see how it fairs.
Ok wait before everyone leaves, Ive got some questions too!
I just got my replacement(after a hard brick trying JB) and figure Id ask my questions in this thread rather than starting a new one..
1. Ive decided to odin EL29 EVERY TIME I want to flash a new rom, just to be safe. If I use CMW with EL29 and decide to try out CM9, Do I always need to flash a aokp kernel? Or is that built into the CM9 install?
2. If I like CM9, and want to make a nandroid backup of it, do I need to Odin back to EL29 first to back it up? Or is it safe to do it with the recovery that comes with CM9?
3. If the answer to #2 is yes, meaning I do have to odin back to EL29, how do I restore my backup? Let me explain:
Lets say I flash CM9, make a nandroid of CM9, then decide to try out say a different rom, like a TW rom. Then I hate the TW rom and wanna restore my backup of CM9. Do I need to ODIN back to EL29 to restore the nandroid? I read in the "how not to brick my..." thread its bad to restore a ICS rom from a GB Kernel. Can someone please explain?
Ive really, really tried to search and read as much as possible before asking, but a lot of the threads are old and have contradicting information. Sorry for being so noobish, but I dont wanna brick my new phone. I come from Evo, Evo3d, Hp Touchpad, etc, where there arent as many issues to flash customs roms. Ive rooted and flashed custom roms ever since the PPC6600, 100's of times and NEVER had a problem. Sorry, this just really confuses me for some reason!!!
Can't help you with CM9 or AOKP because I've never tried either one. The OP was talking about launcher pro. I highly recommend Nova launcher or Apex. They are both specifically built for ICS and look and act like stock android with great customization features.
Was going to make another topic, but I thought I'd ask here first
- The notification tray in this rom (Calk 3.0) is transparent, and I'm not fond of the icons in the Notification Tray. I tried using Rom Tool Box lite to change it, but the tray won't change, no matter what I do. Does anyone know how to fix this? I've tried before - it just won't change.
IceCatraz said:
Was going to make another topic, but I thought I'd ask here first
- The notification tray in this rom (Calk 3.0) is transparent, and I'm not fond of the icons in the Notification Tray. I tried using Rom Tool Box lite to change it, but the tray won't change, no matter what I do. Does anyone know how to fix this? I've tried before - it just won't change.
Click to expand...
Click to collapse
I don't mess with rom tool box. I hear good and bad things about it. If you start at page 1080 and read to the end people post new system ui's but it may theme it a little bit. They have blazers UI in there and one other one I think. I'm not sure it is transparent or not. Or even make a post in the thread about it. I know its still active and you may find your answer. Sorry I can't really help you on this.
Sent from my SPH-D710 using XDA
Alright, cool. Thanks a lot. You wouldn't happen to have the link to that thread, would you? I've searched, and I'm a bit lost. Sorry for the trouble.
I am vary new at epic 4g touch my original android phone was the evo 3d and i was able to hack the **** out of it. Now i am exploring my epic 4g touch wich was alot easier to root with ff18 and i was also able to install the super galaxy rom. I then tried to install the mIjjz ics rom i downloaded Calkulins format then the mijjz rom. I then flashed them in that order and nothing happened the phone was stuck on the boot animation taht said android. I then tried installing Modified calkuns format then tried installing mijjz ics rom, and again it got stuck on samsung galaxy s2 logo. I then took out the battery and traid to install my stock backup rom but for some reason it was lost. The only other backup i had was the super galaxy rom. Now i want to know how do u flash the roms and if i could get directed to the stock ff18 rom. I did download the deodex stock from datajosh but i cant flash it i keep getting error please help i will hit the thanx botton.:good::good:
Grab sfhub's one-click FF18 Stock+Root 'Reset Data' [ http://forum.xda-developers.com/showthread.php?t=1721229 ]and you can get your system back.
Boot to download mode and then plug your phone in and run this.
Then use sfhub's Autoroot Package [ http://forum.xda-developers.com/showthread.php?t=1342728 ] to add CWM+Agat_Safe kernel.
You'll then have a working phone with a 'safe' recovery. Which you could then use to install other ROMs (as a side note; most ROMs here come packed with their own kernel. And all are pretty great and 'safe' from the eMMC brick bug.]
This phone is very different than the HTCs.
Spend a little time reading through the stickies and all the way through the entire posts: you will learn loads and save yourself from creating a very nice shinny fishing lure.
Believe me you can only get loads more enjoyment (and safety) reading through the posts.
Check out the OPs And the follow-ups to see what issues people are having and how they solved them.
The devs in the section are really freaking awesome. As are the ROMs. With a little time and patience you can give many of them a go with safety. I have been giving all the latest a try again this week and have been hard pressed to find faults with most of them. But I would recommend just checking out what ever ROM you choose for at least one full battery cycle and a couple of days to let things settle in. Find something that works for you.
Welcome to the E4GT and good luck.
Tahnx i got it goot thing i also used titanium backup now my phone is restored with all my apps now i just need to save my bookmarks.:laugh:
So when diving into the world of modifying a smart phone, there is a lot of learning one must do reading threads and watching videos prior to getting started. Otherwise instead of rooting your phone, you may end up bricking it.
So lets talk about some of these things.
First off, if you are looking to open your phone up to unlimited modification, the quintessential step is rooting it, which is to say, unlocking root access so everything can be changed from fonts and colors to CPU overclocking.
If I understand this correctly, Rooting is done by flashing a modified kernel onto the phone. I wont try to pretend I know that with any confidence, these are the terms I'd like better explanations for. so... A release comes from the manufacturer and contains everything from the operating system to the firmware and the modem. A ROM is a pre-customized variation of a release, dunno exactly what a TAR, MD5, or a kernel is. A modem is a part of a release, but just the software part that deals with how your phone uses its radios. NANDroid is a way to completely backup your phone as a NAND. Clockworkmod is a utility set that can load and manage ROMS, NAND's, themes, and all kinds of other stuff. Recovery is actually usually used as a term for a built in function for restoring your phone back to a pre-loaded state (if it's not bricked, which means something went wrong and the phone won't turn on, which is different from soft-brick which means the phone is in a startup-boot-loop) I don't know what a bootlogger is. ODIN is a program 'leaked' by samsung used for flashing updates onto phones. Download Mode or Odin mode is used for updating and what you boot into by turning off your phone, then turning it on while holding the volume down button. a OneClick is a pre-made ODIN update that that automatically updates your phone. Stock means the release is unmodified from the manufacturers original. A Tweak is a modification that can be flashed onto a ROM? A Theme I assume is an aesthetic style that can be applied to even a non-rooted phone. But I think it requires the phone to be Deodexed, which is something that can be done to a release... otherwise the release is odexed?
GA10, Fk23, FL16, etc etc. You're probably wondering what that is. It's a coding system for the date of the release. Because android released in 2007, the coding system starts at 2007. That first letter represents the year, the second letter the month, and the number represents the day of the month. So a release from january 1, 2007 would have been AA01. febuary 15th 2007 would have been AB15, which is why a release on december 16 2012 got FL16.
This may not be the end, but to wrap up the small bit that I've learned in 17 hours of reading FAQ's and stickies, cutting edge threads and archives. The last 4 things we need to talk about are the flash count, or odin counter, which tracks how many times your phone has been flashed by an external source. Then there is the yellow triangle which is an indicator thrown during startup by a phone which has detected that it is not running a stock ROM. these 2 indicators can be reset on our e4gt by using a USB Jig, a small piece of hardware which can be bought online specific to our phone, which when plugged into the microusb port, resets the odincount and gets rid of the yellow triangle. And finally, there are some special procedures that must be observed when flashing around from release to release. Flashing to the same release is relatively safe, it sounds, but flashing down or up should be done without preserving data. (restore vs nodata).
Honestly, I've spent a lot of time on learning just this, and I still feel like I'm writing words that don't add up. In fact, I know I am. So I'd honestly appreciate it if someone could take what I've tried to do here, edit it for readability, proper word usage, accuracy, add any or all missing information, and post a new sticky. One that explains these things. Because there are a lot of stickies that provide instructions for how to do things, but very few are written in a way a beginner can understand. I've bolded words that are regularly used but dont make complete sense to non-developers and novice power-user hopefuls.
Hey, I might add some of the terms and what they mean to the FAQ thread. :good:
Am I getting it? or am I wasting my time.? I feel like some of this is for advanced root users only, (like maybe flashing just a modem while using older releases ROMS) and some of this is for beginners only, like one-clicks. I'd love if somebody made just 3 very simple, very useful beginner wikis/stickies. ONE is a 'terminology' post, like the one I've haphazardly attempted to put together above. TWO is an "everybody knows you're supposed to blah blah blah" post, for things like mobile odin and modems, making a backup, how to stick to the basics if you're new, not flashing backwards with ROMs, and knowing how to recover back to warranty eligible stock (odin counter and everything), finally THIRD would be the thread that explains how to do each of the different kinds of flashes, but not just instructions, but what it means to do them.
I've combed through these threads for a day straight and I've got more questions than I started with.
So, if someone doesn't want to put these together, Questions I'd love to know definitive answers to, so this thread can continue to be helpful to others....
A) If I flash anything, or everything, a hundred times, ROMs, modems, kernels, recoveries, roots, can I find a stock release of whatever-is-current-OTA to flash and then use TriangleAway to reset everything back to warrenty elligible? if not, what about the USB jig? Is this even possible.... If so...
B) Since my phone is not rooted now (first timer), Am I able to make a complete backup of my phone un-rooted so I can flash back to it if I ever need to become warrenty elligible again. If so, do I use nandroid, or titanium backup? don't both of these require root? Can I flash back to undetectable stock?
C) obviously, disclaimers everywhere show that it is never safe to flash anything, everything is at your own risk, but is there a general rule of thumb for whether a stock release is more reliable than a customized ROM. or do ROMs tend to be more stable with problems fixed.
D) Does a phone need to be already rooted, (or already flashed up to a release number or with a release modem) in order to flash a ROM onto it, or does it just require Odin and the TAR. Is a ROM a TAR? is a ROM a Kernel? or does a phone need to be rooted to some version first, then using CWM to load a same-version ROM?
I would say stock is more stable, on average. Think about what your goal is, why you would want root, and why you would use a custom rom. Rom choice, for me anyway, is based on customization availability, and tweaks. If you are simply driven by curiosity, and that is a good thing, read, and read some more. Patience and knowledge will keep you from trashing your phone, but most importantly attention to detail when performing any of these activities. Good luck, we all started somewhere.
.: :: Sent from USC-GS2~PACman via Tapatalk 2 :: :.
Triangle away will reset the counter now even in jellybean. Just not gingerbread. For going back to stock for warranty, dont worry about that. You can use a tar file or a one click. If you want a stock backup for yourself to rely on, I need to know what version number you want so I know what to do. Yes titanium backup as well as m.o. require root. For anything below ga10 touchwuz roms, use exynos abuse.apk you can root your phone no computer needed.
sent from MY BAD A$$ ET4G
I don't understand how a recovery is different from a backup. but somehow is independent of a ROM, and build, but is included in a kernel? Apparently I need a CWM recovery kernel to flash Kobridges GA10 ROM. I see that there are repositories of all kernels, and modems, and roms. So a build is a TAR which contains a kernel, which contains a recovery, but also is the original ROM, after which other ROMs are built?
My phone, purchased October 2011, (only updated OTA to this point) is running FI27 ICS 4.0.4.
I've been trying to understand what I need to know, and need to have, to get started. I think I need FI27 to flash back to if I ever want to go back to un-rooted stock. Or do I want to flash back to something safer, (perhaps a 1click?) and then do OTA updates if desired. I think I'm reading that the CWM EL26 Recovery Kernel is the gold standard for pre-flashing before flashing any ROMs. But I don't know how that exactly works considering clockworkmod uses root, and I don't have root yet. I'm simultaniously trying to confirm what I'm trying to understand, but also find out what I don't yet have or understand, without asking somebody to just lay it all out for me (unless in the form of a wiki/sticky which could benefit anyone else like me who comes along after).
A)
So I have an e4gt.
I have backed up all essential files from internal storage to my PC, but if I understand correctly, I cannot create a nandroid.
I have SPH-D710_FI27_CL1127689_UNROOTED_NoData.exe to go back if I need stock.
Now if I want to just put TeamSextapes GA10 release on, that's pretty simple, I just flash the tar with odin. Everything is done. no root. No Rom
I can use a USB Jig to make it run as if I got the update from sprint even. But I shouldn't use the factory reset?
Going back from that, I'd use my one-click FI27 unrooted nodata.exe right, and then the USB Jig?
B) Am I right so far, from A) to B)?
All of this assumes I don't want roms or root.
When we're talking about ROMs, I'm still confused, because of how to get from where I am, to there, I gather it requires root, nandroid, clockworkmod, and CWM EL26 recovery kernel, and the process seems to double back a lot. flashing a root rom seems to require root. the process seems rather more opaque. I understand how to do a 1 click root, and older versions of root kinda make sense too, but how can someone flash kobridges GA10 ROM when it requires root, but no rooted stock GA10 is available?
Maybe I need to stay away from GA10, but my whole goal for learning all of this is to know how to get the best performance, with the least bugs, out of my phone, and signs point to GA10 for that. I had expected JB to roll out with the GSIII months ago, and all news of it has gone silent except here.
Thanks for continuing to support my inquiry. If I can come to understand how it all works, I will post a supplement to the "how to not brick your e4gt". Because as absolutely fantastic as that thread is... it still is way too deep water for a complete beginner. Regarding aspects of all this, I feel like I've learned more than I need to about some, and only enough to be dangerous about others. But still, Thanks!
I'll try to help with with what I understand. Clockworkmod or any recovery in general is packed up with the kernel. So if you want to make a backup just Odin a kernal with a recovery and it would be fine (I.e Kuban kernel). The thing is when you use Odin to flash kernel's it will cause the Samsung binary counter to increase and you will get a yellow triangle on boot. This is an easy fix but you need root access to run an app called triangle away which can be found in these forums or you can buy it off the play store if you want to support the dev. I would suggest getting the Directboot el29 kernel as it boots up directly into recovery. El29 or el26 are gingerbread kernels so if your running stock your phone won't boot up unless you are on gingerbread but you can always access recovery. I would suggest also getting an app called mobile odin (same deal as triangle away on how to get it)you can flash anything you can with regular Odin except it won't cause the counter to increase. Now for root.. I can be stock and have custom recovery just from using a custom kernel through Odin. Now 1 clicks are amazing let's say I have to take my phone in for repairs or warranty reasons. All I have to so is use the triangle away app (if I have the yellow triangle on boot) then boot my phone into download mode and use the FI27 stock no root data wipe. You can run a 1 click from your phone in any ROM ect... And bam you can take your phone to sprint for repairs or warranty. When you get your phone back just flash a 1 click for root access or a custom kernel for the recovery and then restore a nandroid and return to how your phone was. Now this is why I bought mobile Odin to support the dev.. Like in your case you want ga10. What I would do is just drag the download to my phone run mobile Odin and flash the ROM through mobile Odin.. Why? Because it can inject root to stock as it flashes. Just be careful and remember to back up your data because most jellybean leaks wipe internal data like pictures etc.. This doesn't happen when you flash a ROM and they ask you to wipe data. Now for modems stock jellybean modems don't work on ICS. You need a jellybean modem (if you do use the mobile Odin route you will have to flash a jellybean modem using regular Odin because mobile Odin doesn't seem to flash modems for our phones). When you Odin modems it will not increase the binary count and trigger the yellow triangle. Gingerbread modems and ICS modems interchange with each other so I wouldn't fear odining them.. Just see which works best. Hope this helps... I'm pretty sure you will read this cause you took the time to write a very long post lol.
Sent from my SPH-D710 using XDA
Thanks! That answers a number of my questions, now that the 1click for ga10 is out, i think ive finally got enough figured out to mess with it a bit with relative confidence.
Sent from my SPH-D710 using xda app-developers app
jt323bd said:
My phone, purchased October 2011, (only updated OTA to this point) is running FI27 ICS 4.0.4.
I've been trying to understand what I need to know, and need to have, to get started. I think I need FI27 to flash back to if I ever want to go back to un-rooted stock. Or do I want to flash back to something safer, (perhaps a 1click?) and then do OTA updates if desired. I think I'm reading that the CWM EL26 Recovery Kernel is the gold standard for pre-flashing before flashing any ROMs. But I don't know how that exactly works considering clockworkmod uses root, and I don't have root yet. I'm simultaniously trying to confirm what I'm trying to understand, but also find out what I don't yet have or understand, without asking somebody to just lay it all out for me (unless in the form of a wiki/sticky which could benefit anyone else like me who comes along after).
A)
So I have an e4gt.
I have backed up all essential files from internal storage to my PC, but if I understand correctly, I cannot create a nandroid.
I have SPH-D710_FI27_CL1127689_UNROOTED_NoData.exe to go back if I need stock.
Now if I want to just put TeamSextapes GA10 release on, that's pretty simple, I just flash the tar with odin. Everything is done. no root. No Rom
I can use a USB Jig to make it run as if I got the update from sprint even. But I shouldn't use the factory reset?
Going back from that, I'd use my one-click FI27 unrooted nodata.exe right, and then the USB Jig?
B) Am I right so far, from A) to B)?
All of this assumes I don't want roms or root.
When we're talking about ROMs, I'm still confused, because of how to get from where I am, to there, I gather it requires root, nandroid, clockworkmod, and CWM EL26 recovery kernel, and the process seems to double back a lot. flashing a root rom seems to require root. the process seems rather more opaque. I understand how to do a 1 click root, and older versions of root kinda make sense too, but how can someone flash kobridges GA10 ROM when it requires root, but no rooted stock GA10 is available?
Maybe I need to stay away from GA10, but my whole goal for learning all of this is to know how to get the best performance, with the least bugs, out of my phone, and signs point to GA10 for that. I had expected JB to roll out with the GSIII months ago, and all news of it has gone silent except here.
Thanks for continuing to support my inquiry. If I can come to understand how it all works, I will post a supplement to the "how to not brick your e4gt". Because as absolutely fantastic as that thread is... it still is way too deep water for a complete beginner. Regarding aspects of all this, I feel like I've learned more than I need to about some, and only enough to be dangerous about others. But still, Thanks!
Click to expand...
Click to collapse
You can still flash a kernel with a custom recovery using desktop odin if you are not rooted. You can they boot into custom recovery and make a nandroid of your unrooted stock rom.
Your flash counter only increases if you flash unofficial stock files using desktop odin. So if you flash a modem.bin in the phone slot in desktop odin, your flash counter will increase. If you flash a kernel.tar file in desktop odin, your flash counter will increase. Thats why you go to rwilco12's repo in dev forums and use the one-click.exe files. Oneclick.exe files do not increase flash counter. You only need jib to reset flash counter or boot to download mode if you can't normally boot to download mode.
You could flash EL26 CWM kernel in desktop odin and boot to CWM recovery to flash any rom zip file you want even if you are not rooted. Don't jump to jelly bean roms from ics without first flash a stock jellybean oneclick.