Related
-PLEASE READ THE WHOLE THREAD BEFORE ASKING, OR STATING ANYTHING OR YOU WILL BE TROLLED (BADLY)
-YOU, AND ONLY YOU ARE RESPONSIBLE FOR YOU'RE ACTIONS. IF YOU FLASH AND BRICK YOU'RE PHONE, ONLY YOU ARE TO BLAME.
Sorry guys it's been a while since I've been able to update this thread, I'm extremely glad to see that it's being used throughout the E4GT community. Well I guess it's time to update this so lets get started, and please forgive me if I miss anything as I have been on ICS mainly for a long time.
-Are you on a rom with a stock recovery or with a kernel released prior to SOURCE? Use Odin buddy!
______________________________________________
Just because we have source now, does not mean you can't still brick you're device. In fact many people are still on ICS builds prior to FF18 or newer, this includes people using stock kernels as well. Do not use the recovery on you're phone to do anything, The stock recovery is meant for files signed by Samsung and only Samsung, Roms prior to source with a custom recovery had the dreaded EMMC bug which would brick some people with a simple wipe. If any of the above applies to you and you wish to get back to GB or ICS then click on the following link that corresponds to you're desire and follow the steps.
EL29 One Click Link Below
__________________________________________________
http://forum.xda-developers.com/showthread.php?t=1433101
__________________________________________________
ICS FF18 (Original ICS OTA update) Link Below
__________________________________________________
http://forum.xda-developers.com/showthread.php?t=1721229
__________________________________________________
ICS FI27 (Newest ICS OTA update) Link Below
__________________________________________________
http://forum.xda-developers.com/showthread.php?t=1932032
__________________________________________________
-After you install the .Tar file to you're phone, you'll need to install a custom recovery using a Auto Root Package found below, just follow the instructions. (use the FF18 Combo to install a custom recovery on the FI27 version)
http://forum.xda-developers.com/showthread.php?t=1342728
_________________________________________________________________________________________________
-Wanna flash to ICS from GB?
_______________________________________________________________________________________
Simply pick the ICS rom you wish to use and flash using the OP's instructions. The issue of flashing to ICS from GB never really existed. If you are still worried about the risks of flashing to ICS, then use the Odin One Click method above and you're guaranteed fine.
_______________________________________________________________________________________
-Wanna Flash to GB from ICS?(includes restoring backups to GB roms too)
_______________________________________________________________________________________
This is where issues began to occur, prior to source release. The EMMC bug was present during the ICS leaks leading up to source release FF18 (FF18 OTA not being the issue). If you are on a rom which already contains a source kernel (FF18 and newer) Flashing to GB is the same as flashing to another rom, just follow the OP's instructions. If you're on a leaked rom with a stock recovery, or custom recovery, use the Odin One Click method to get back to GB or ICS. DO NOT WIPE IN NON-SOURCE KERNELS--- EVER
_______________________________________________________________________________________
-Wanna Flash Good ol' CyanogenMod, or Something else AOSP?
____________________________________________________
-CyanogenMod 9 as of recent bulids has a proven SAFE RECOVERY, so you should be able to flash to, and from without issues
-I am unsure if CyanogenMod 10, or other Jellybean AOSP roms have a safe recovery, so I recommend this method below
Always use the EL26CWM kernel to flash AOSP roms. I myself, have flashed CyanogenMod 9 with multiple non-CWM kernels without issues, but better safe then sorry right? Thanks to rwilco12, we now have a repository for kernels, and modems so give him a big thanks. You can find the EL26 CWM kernel here.
http://rwilco12.androidfilehost.com/?dir=Kernels/Recovery Kernels/GB/Chris41g/Stock CWM
Simply download the rom you wish to flash, as well as the EL26CWM kernel. Flash the kernel, and reboot back into the recovery. When you're phone restarts back into recovery press up, down, up, down with you're volume buttons to enable the selection button (power on/off button). Now flash the rom USING THE RECOMMENDED FLASHING INSTRUCTIONS. Instructions of roms may differ from others so be sure to read the Original Post by the dev before flashing.
-Are you on an AOSP rom and you wish to flash to a TW rom or other?
____________________________________________________________________________
Follow the same instructions for flashing to an AOSP rom, except replace the AOSP rom with the rom of you're choice. You can also use the One Click Odin Method from before. I have used both of these methods for flashing a different rom while on AOSP multiple times without any issues whatsoever.
________________________________________________________________________________________________
-Bricking Info
_________________________________
-For more info on the EMMC chip corruption issue from kernels prior to source go here
http://forum.xda-developers.com/showthread.php?t=1644364
________________________________________________
MISC
_________________________________________________________________________________________________
-Stick with source kernels and you should be safe
-Stay away from touch recovery, unless it's source-based
-Stay away from Rom manager, It's not, and probably never will be optimized for our phone
-Thanks
__________________________________________________________________________________________________
Calkulin, Mijj,all of Team Venom, all of Team Rejectz, agat, good ol' ruj22, rwilco12, garwynn, Ja5on for the title, all devs, and themers
Hey xST4T1K, great idea for a thread man, and great accumulation of information. As it seems, I have seen quite a few bricked devices in the Q&A lately. Hopefully new members of this community will take a moment to read this and understand some of the problems that others are having in hopes that it will help at least one person from brickin' their celly. Thanks again xST4T1K...
I really think that something like this should be stickied....
jasone4gt said:
Hey xST4T1K, great idea for a thread man, and great accumulation of information. As it seems, I have seen quite a few bricked devices in the Q&A lately. Hopefully new members of this community will take a moment to read this and understand some of the problems that others are having in hopes that it will help at least one person from brickin' their celly. Thanks again xST4T1K...
Click to expand...
Click to collapse
No problem man, If you have anything to add please feel free, I know I missed some things I'm sure, but glad you like it!
shiftr182 said:
I really think that something like this should be stickied....
Click to expand...
Click to collapse
Exactly what I was thinking. With a title something along the lines of How to not brick your device.
shiftr182 said:
I really think that something like this should be stickied....
Click to expand...
Click to collapse
Agreed, I was surprised I hadn't seen any other threads like it yet
jasone4gt said:
Exactly what I was thinking. With a title something along the lines of How to not brick your device.
Click to expand...
Click to collapse
Lol renamed and gave you credit for the tittle
Some of us, myself included , bricked by using odin. I'm very experienced in modding my phones and I bricked one, so its not a lack of knowledge that caused this. I was going from one of the ics builds back to a stock rooted rom using one of sfhubs all in one odin packages and it some how screwed up the data partition. I had done it several times without issue so it surprised me when it bricked it. I think that I was using the touch recovery when it happened but I'm not positive. Hope this helps someone.
Sent from my MB855 using XDA App
xST4T1K said:
Lol renamed and gave you credit for the tittle
Click to expand...
Click to collapse
LOL nice, you didn't have to do that it's your thread, but thanks man!
jasone4gt said:
LOL nice, you didn't have to do that it's your thread, but thanks man!
Click to expand...
Click to collapse
Lol it's a way better title then mine bro, plus hopefully it will open up to more people
stonesaber said:
Some of us, myself included , bricked by using odin. I'm very experienced in modding my phones and I bricked one, so its not a lack of knowledge that caused this. I was going from one of the ics builds back to a stock rooted rom using one of sfhubs all in one odin packages and it some how screwed up the data partition. I had done it several times without issue so it surprised me when it bricked it. I think that I was using the touch recovery when it happened but I'm not positive. Hope this helps someone.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Actually, more then likely your device isn't bricked, sfhub helped someone else with the same issue unbrick they're device. Look around the q&a section and you'll find it. I also mentioned touch recovery as a possible issue, gotta read broski. Doesn't matter how experienced you are, you can still have a brick with one wrong move, even devs brick sometimes, I've been doing this for 5 years now and even I almost did the other day.
xST4T1K said:
Actually, more then likely your device isn't bricked, sfhub helped someone else with the same issue unbrick they're device. Look around the q&a section and you'll find it. I also mentioned touch recovery as a possible issue, gotta read broski. Doesn't matter how experienced you are, you can still have a brick with one wrong move, even devs brick sometimes, I've been doing this for 5 years now and even I almost did the other day.
Click to expand...
Click to collapse
There was nothing to read. I was one of the first. I tried everything before finally sending it to Josh at mobiletechvideos.com. It's on the way back and should be here @ Sat. According to him in the main tread though, even he was unable to repair it but he didn't mention mine being un-repairable in the emails he sent me. I'll find out soon and let everyone know.
stonesaber said:
There was nothing to read. I was one of the first. I tried everything before finally sending it to Josh at mobiletechvideos.com. It's on the way back and should be here @ Sat. According to him in the main tread though, even he was unable to repair it but he didn't mention mine being un-repairable in the emails he sent me. I'll find out soon and let everyone know.
Click to expand...
Click to collapse
Calm down buddy! just be more careful when flashing that's all, and stay away from touch recovery, even Steady debated pulling the link because of bricking issues.
xST4T1K said:
Calm down buddy! just be more careful when flashing that's all, and stay away from touch recovery, even Steady debated pulling the link because of bricking issues.
Click to expand...
Click to collapse
I'm perfectly calm. As stated, I was one of the first to brick using touch recovery so even if the link was pulled, it would've been too late for me. I do not need anyone jumping to conclusions without having the facts. That is all.
stonesaber said:
I'm perfectly calm. As stated, I was one of the first to brick using touch recovery so even if the link was pulled, it would've been too late for me. I do not need anyone jumping to conclusions without having the facts. That is all.
Click to expand...
Click to collapse
Completely understand now, didn't know how long ago you bricked so sorry for the assumption, hope you get it restored. I know this thread may not solve everyone's issue but please understand that I put it up so people were aware that things may be an issue
This is great to see before I start flashing thank you
Sent from my SPH-D710 using xda premium
Sheldon_ said:
This is great to see before I start flashing thank you
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
At least you took the time to read this before posting another thread that you bricked you phone doing the same thing others are doing and not reading first..... My hats off to you good sir
Sent from my SPH-D710 using Tapatalk
Epix4G said:
At least you took the time to read this before posting another thread that you bricked you phone doing the same thing others are doing and not reading first..... My hats off to you good sir
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Agreed, too many people are getting flash happy and not paying attention to the forums anymore
Haha thanks guys
Sent from my SPH-D710 using xda premium
I've bricked mine a different way. Was playing around with a CM9 test build, and bricked mine pretty good. I can get to odin and recovery, and sometimes it will loop the boot animation infinitely.
Everytime i try a OC odin, it hangs at data.img forever, i can't restore any rom, tried reflashing the rom that 'broke' my phone, not sure where else to head. looking like $35 at sprint ain't too shabby
Ok Guys i need a way to go back to stock without odin or heimdal my usb port is out of the equation. Only way to get files onto phone is through my sisters EVO. This needs to be no root no custom rom. I have to take my phone in to sprint cause 1.)the usb port 2.) My touchscreen is useless it doesn't work .
Thanks
There's a re rfs rom in android development...little busy otherwise id post it. You'll need to flash it and flash the stock recovery.
Sent From My SPH-D700 Running Android 4.0
He is talking about here:
http://forum.xda-developers.com/showthread.php?t=1027904
Make sure superuser is deleted as well. You will still be stuck on whatever modem you are on. I think if it is not EC05 it will mess up the OTA updates.
Thanks a lot guys ! And I'm on ec05 so were set
Sent from my SPH-D700 using XDA App
Seems like the links to download aren't working :\
EDIT : Had to restart browser
Sent from my SPH-D700 using XDA App
oK I flashed the zip and absolutely nothing happened it went through the installation and it was successful but it changed NOTHING
CrfEpic4g said:
oK I flashed the zip and absolutely nothing happened it went through the installation and it was successful but it changed NOTHING
Click to expand...
Click to collapse
Bad download? You flashed the ROM and it doesn't look like Froyo stock? What ROM are you on?
I'm on the latest sleeper rom
Sent from my SPH-D700 using XDA
CrfEpic4g said:
I'm on the latest sleeper rom
Sent from my SPH-D700 using XDA
Click to expand...
Click to collapse
MTD? Then you are screwed. You can't get back to stock without Odin or Heimdall. You need to repartition. BUT there is an MTD version of the FB15 leak which should look enough like stock to get you through:
http://forum.xda-developers.com/showthread.php?t=1522816
That is the best you can do. You should also do the 2 flashable modems to get you to EL30 and delete Superuser before you bring it in.
Wow just what i wanted to hear hahah alright man thanks
CrfEpic4g said:
Wow just what i wanted to hear hahah alright man thanks
Click to expand...
Click to collapse
Let me know if you need links to the modem flashables and how the "stock" ROM looks.
Do you think they will try to access the recovery?
CrfEpic4g said:
Do you think they will try to access the recovery?
Click to expand...
Click to collapse
It depends on how interested the tech is in making sure it is not a software problem. There are a few horror stories about accounts getting flagged but most of the time the techs don't care. Just smile a lot...lol.
thats didnt install either nothin changed !!!!!!!
EDIT: opps needs to be mtd lol my bad
This wont work the boot up isn't stock at all anything else u can think of?? bout to just slam the thing on a wall OOORR just break the charging prongs and let it uncharge???
CrfEpic4g said:
This wont work the boot up isn't stock at all anything else u can think of?? bout to just slam the thing on a wall OOORR just break the charging prongs and let it uncharge???
Click to expand...
Click to collapse
OK, found another one for you:
http://forum.xda-developers.com/showthread.php?t=1465066
Whatever stock-ish MTD rom you flash, make sure you flash data, (factory reset) if you're returning it, might as well.
Sent from my SPH-D700 using xda premium
This thread scares the hell out of me. A bad USB port on your epic is a fatal blow to your potential sprint insurance coverage. I cant think of anything worse, especially if your on MTD. Although, if your paying for insurance, i dont think it should really matter what firmware/rom you have on your device.
To the OP, you should be fine. As long as you can make it look at stock as possible, the average sprint employee is not smart enough to get into specifics. They are usually pretty cool about it. As a matter of fact, the tech at my local sprint store put gingerbread on my phone a week before it was released using odin (this was before I knew anything about flashing or rooting), most of the tech's do exactly what we do, so dont sweat it too much.
let me know which rom you put on i'm pretty much in the same boat i need to take my phone in because i'm having hardware failure
CrfEpic4g said:
Wow just what i wanted to hear hahah alright man thanks
Click to expand...
Click to collapse
[email protected] said:
let me know which rom you put on i'm pretty much in the same boat i need to take my phone in because i'm having hardware failure
Click to expand...
Click to collapse
The one I posted a few posts back (post 16) by Bbelos is the closest to complete stock for MTD. Just delete superuser when done. Then you are only left with CWM recovery as evidence.
So I'm still pretty new on the E4GT forums, having recently come over from a Nexus one, which was quite a bit easier to mess with as far as ROM's are concerned, and much less easy to brick. About the only thing that could brick an N1 was flashing a radio, and new radio's didn't come out that often, so no big deal.
I'm currently running Calkulins EL29 mod with an FC14 modem on my E4GT, but I'm really wanting to mess with the testing builds of CM9, I really miss CM. All the steps seems to spread out across multiple threads, so I want to make sure I do it correctly so as not to brick.
1. nandroid backup, backup, backup
2. boot to download mode
3. load stock cwm el26 through odin
4. flash cm9 zip
5. mess around with it.
Where I'm a little confused is how to get back to where I was should I decide to wait some more. How do I get back to the EL29 CWM so that I can then restore the nandroid backup? Also, will I need to flash different modems again, or can I stick with the fc14 modem through all of this?
Please understand that I'm not a total n00b at all of this, been flashing all kinds of ROM's on my old Nexus one for two years, just don't have much experience with Sammy devices.
You just want too flash roms and themes?
Sent from my SPH-D710 using xda premium
I would also like to know the answer to this.. I'm terrified to flash or odin any ics-based roms because I don't want to brick my phone like a lot of others have
Sent from my SPH-D710 using XDA Premium App
ScubaSteev said:
You just want too flash roms and themes?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Themes, not really, but ROM's yes. It's just a bit confusing cause I see things like, you need this CWM for this, you need to flash this, or you need to Odin that, you need this specific CWM for this, or you need to get back to stock before you fan flash or Odin this or that.
But what I'm really wanting help with at this moments, is the testing build of CM9, and then how to get back if I don't like it at this time.
Ok....I download roms straight from xda app and then I go to recovery......do a full wipe....wipe data/wipe dalvic/wipe cache/wipe battery stats.........then I install .zip (rom) then reboot.....that's all I do,its pretty simple
Sent from my SPH-D710 using xda premium
ScubaSteev said:
Ok....I download roms straight from xda app and then I go to recovery......do a full wipe....wipe data/wipe dalvic/wipe cache/wipe battery stats.........then I install .zip (rom) then reboot.....that's all I do,its pretty simple
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
The problem is that CM9 is an ICS ROM, you can't just flash willy nilly as there are a lot of reports of people bricking their phones cause they didn't use the right recovery. How to flash CM9 on is not my problem, it's how to get back to EL29 if I don't like the current testing build of CM9.
Ohh yeah....I don't mess with that stuff lol,can't take a chance.......but everyone says don't.
And I love cm7 can't wait for cm9 to be stable
Sent from my SPH-D710 using xda premium
Check out QBKing77 on YouTube. He has very simple videos about how to get back to stock after flashing ROMs, his guidance taught me everything. But don't let my noob-ness detour you, they are great videos.
Sent from my SPH-D710 using xda premium
xerxax said:
Check out QBKing77 on YouTube. He has very simple videos about how to get back to stock after flashing ROMs, his guidance taught me everything. But don't let my noob-ness detour you, they are great videos.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
People, please read my OP, I'm already rooted and running a custom gingerbread rom and recovery. I'm wanting to run CM9, but it may not be stable enough for me, so I'm wanting to know what the steps are to get back to my custom gingerbread rom should I decide to go back.
garfnodie said:
People, please read my OP, I'm already rooted and running a custom gingerbread rom and recovery. I'm wanting to run CM9, but it may not be stable enough for me, so I'm wanting to know what the steps are to get back to my custom gingerbread rom should I decide to go back.
Click to expand...
Click to collapse
The guy you just quoted... just told you where to find that information. :what:
This has been discussed ad nauseum all over the forums, and if you do a bit of research you will find the exact procedure. Since I'm on my phone, kinda a pain to type it all out. But he's right, the point is to get back to stock GB rom before restoring any GB nandroids. (specifically before wiping any partitions, but that's yet another long explanation.) This issue And procedure is the same for ICS leaks, for cm9, for AOKP.
Look for a sticky thread in general titled "how not to brick your phone" or something.
Or, god forbid, actually read one of the ICS/cm9/AOKP/leak threads. I swear, every third page you will see someone ask this and the process described.
And QBKING77s videos have a step by step explanation for this as well. Really the best way.
And yes, you can keep the modem, no matter what rom/kernel you run. Same thing as a "radio".
Sent from my calculator watch.
kingdazy said:
The guy you just quoted... just told you where to find that information. :what:
This has been discussed ad nauseum all over the forums, and if you do a bit of research you will find the exact procedure. Since I'm on my phone, kinda a pain to type it all out. But he's right, the point is to get back to stock GB rom before restoring any GB nandroids. (specifically before wiping any partitions, but that's yet another long explanation.) This issue And procedure is the same for ICS leaks, for cm9, for AOKP.
Look for a sticky thread in general titled "how not to brick your phone" or something.
Or, god forbid, actually read one of the ICS/cm9/AOKP/leak threads. I swear, every third page you will see someone ask this and the process described.
And QBKING77s videos have a step by step explanation for this as well. Really the best way.
And yes, you can keep the modem, no matter what rom/kernel you run. Same thing as a "radio".
Sent from my calculator watch.
Click to expand...
Click to collapse
I did some searching, and everything I found says to get back to stock, I didn't see where it said that you have to get back to stock first before you can then restore a nandroid.
This is not how it was done on the Nexus One, so it's new to me.
garfnodie said:
I did some searching, and everything I found says to get back to stock, I didn't see where it said that you have to get back to stock first before you can then restore a nandroid.
This is not how it was done on the Nexus One, so it's new to me.
Click to expand...
Click to collapse
Ics kennels with cwm have been bricking phones ....some just by wiping data ...they corrupt your data partition making it impossible to write to ..jtag doesn't even work on it...so we have been Odin back to stock GB and go from there
Sent from my SPH-D710 using xda premium
You may want to read this if you haven't already:
How Not To Brick Your E4GT
Now that it has been stickied the OP went through and updated the first post to cover most of I believe you are trying to find out. Hope this helps!
Epix4G said:
Ics kennels with cwm have been bricking phones ....some just by wiping data ...they corrupt your data partition making it impossible to write to ..jtag doesn't even work on it...so we have been Odin back to stock GB and go from there
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
That's what I've been seeing, which is why I want to make sure I do it right. I don't even know what jtag is, had to look it up. Some kind of debugging tool from I found.
garwynn said:
You may want to read this if you haven't already:
How Not To Brick Your E4GT
Now that it has been stickied the OP went through and updated the first post to cover most of I believe you are trying to find out. Hope this helps!
Click to expand...
Click to collapse
I'll definitely give it good read. Thanks.
Sorry if this is the wrong place to post at but I'm dying to know. I've been reading alot of forums saying that flashing ICS can possibly brick you to the point of no return. And there are some people who seem to flash no problem. I've used the brick bug app to check my chip version and I have the "0x19" which is, from what I've read, the most likely to brick with ICS. Im new to the E4GT (coming from the Droid X) and I really want ICS but I'm petrified of the EMMC lockup issue. Is there any flashing method that is at least 99% guaranteed that I won't brick my device?
Any thoughts or suggestions will be greatly appreciated.
Sent from my SPH-D710 using XDA
I've flashed every single ics leak out there and have basically no idea what I'm doing. No brick yet!
Just read up and follow directions exactly.
Sent from my SPH-D710 using xda premium
http://forum.xda-developers.com/showthread.php?p=27038002
[ODIN][TAR] SPH-D710.FF02_CL663858 (FF02 Modem/Kernel/ROM - Full Restore - Rooted
It's my phone...any mis takes...sry
Chew DZ said:
Sorry if this is the wrong place to post at but I'm dying to know. I've been reading alot of forums saying that flashing ICS can possibly brick you to the point of no return. And there are some people who seem to flash no problem. I've used the brick bug app to check my chip version and I have the "0x19" which is, from what I've read, the most likely to brick with ICS. Im new to the E4GT (coming from the Droid X) and I really want ICS but I'm petrified of the EMMC lockup issue. Is there any flashing method that is at least 99% guaranteed that I won't brick my device?
Any thoughts or suggestions will be greatly appreciated.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Flash the el26 kernel with cwm and you should be OK to flash any ICS rom . Just be sure to carefully read the instructions for the from you are flashing. Cm9 and aokp I think you have to flash the Google apps after the ROM. Most of the other ones include them. That's one thing about the epic touch we have plenty of great devs that give us plenty to choose from.
if you want but there's no need.
Read! Read, and re-read everything then ask questions!! You should watch some qbking77 video on how to flash the proper way!! Good luck don't brick & if you do brick well its YOUR FAULT FOR NOT READING! Don't mean to sound harsh but there's already waaaay to many "should I flash ics" if your asking that then I would suggest not to flash it! Cuz obviously you most have not read the directions properly. But if you need help or questions your in the right community.
Sent from my PaRAnO!D aNDr0id!
krazy_smokezalot said:
Read! Read, and re-read everything then ask questions!! You should watch some qbking77 video on how to flash the proper way!! Good luck don't brick & if you do brick well its YOUR FAULT FOR NOT READING! Don't mean to sound harsh but there's already waaaay to many "should I flash ics" if your asking that then I would suggest not to flash it! Cuz obviously you most have not read the directions properly. But if you need help or questions your in the right community.
Sent from my PaRAnO!D aNDr0id!
Click to expand...
Click to collapse
Reading directions is not a problem for me. I've been flashing ROMs on my Droid X for almost 2 years. Trust me, I know the value of instructions lol. I was just curious because, from what people have been saying, the EMMC lockup is pretty random & they're aren't 100% sure what factors cause the lockup to happen. But I will take your advice and continue to read.
Sent from my SPH-D710 using XDA
albertouresti said:
Flash the el26 kernel with cwm and you should be OK to flash any ICS rom . Just be sure to carefully read the instructions for the from you are flashing. Cm9 and aokp I think you have to flash the Google apps after the ROM. Most of the other ones include them. That's one thing about the epic touch we have plenty of great devs that give us plenty to choose from.
Click to expand...
Click to collapse
I can flash the EL26 kernel even tho I'm on EL29 firmware? Still getting the hang of the Epic lol
Sent from my SPH-D710 using XDA
I flashed an ICS leak FD24 no problem on my E4GT a couple weeks ago. I'm debating whether or not it is necessary to roll back (i.e: if now that I've flashed already I'm subject to the brick) I really like some of the ICS updates to my apps as well as some of the features. But from one of the posts it sounds like it can brick AFTER you've flashed.
Chew DZ said:
Reading directions is not a problem for me. I've been flashing ROMs on my Droid X for almost 2 years. Trust me, I know the value of instructions lol. I was just curious because, from what people have been saying, the EMMC lockup is pretty random & they're aren't 100% sure what factors cause the lockup to happen. But I will take your advice and continue to read.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Its not random! This how you can brick your phone! Let's say ur on ics rom and you want to flash another rom. U boot recovery there's a stock recovery and you factory reset that will cause the SUPER BRICK! That's how I bricked my first phone!!! I bricked my second phone because I used the wrong recovery by accident. I used acs recovery to flash cm9. Super brick. I was supposed to use Stock cwm el26! Stock cwm el26 is wat I use to flash EVERYTHING!!!! But good luck and hope this superbirck won't stop you from enjoying this phone! I really like ParanoidAndroid port
Sent from my PaRAnO!D aNDr0id!
If you have to ask weather you should flash ICS, then you probably shouldn't. READ READ READ READ READ!!!!! Follow instructions word for word.
Sent from Mijjah74's "the goodness" with kobridge 3.3 m tweak
Ceej64 said:
I flashed an ICS leak FD24 no problem on my E4GT a couple weeks ago. I'm debating whether or not it is necessary to roll back (i.e: if now that I've flashed already I'm subject to the brick) I really like some of the ICS updates to my apps as well as some of the features. But from one of the posts it sounds like it can brick AFTER you've flashed.
Click to expand...
Click to collapse
Wrong. If you wanna roll back to let's say gb! And u want to flash Blazer 4.1.
1. Odin or mobile Odin el26
2. Factory rest/wipe
3. Wipe cache & Davlik cache
4. Flash Blazer 4.1 and your done!!
The key is el26 cwm kernel!!!!
Edit: but if your on a ics rom and you want to flash a different ics rom! My personal suggestion is to
1. Odin or mobile Odin stock rooted el29
2. Then after it boots Odin or mobile Odin el26 cwm
3. Wipe/factory rest
4. Wipe cache/davlik cache
5. Flash your new ics rom
Sent from my PaRAnO!D aNDr0id!
fryingpan0613 said:
If you have to ask weather you should flash ICS, then you probably shouldn't. READ READ READ READ READ!!!!! Follow instructions word for word.
Sent from Mijjah74's "the goodness" with kobridge 3.3 m tweak
Click to expand...
Click to collapse
That's what I told him lol
Sent from my PaRAnO!D aNDr0id!
krazy_smokezalot said:
That's what I told him lol
Sent from my PaRAnO!D aNDr0id!
Click to expand...
Click to collapse
I just read the op and hit reply lol, but it can't be stressed enough!!!! EL26 cwm is your best friend.
Sent from Mijjah74's "the goodness" with kobridge 3.3 m tweak
What is the difference between Odin & Mobile Odin?
Sent from my SPH-D710 using XDA
Just use one of sfhubs oneclicks ff02 is the newest
Sent from my SPH-D710 using xda premium
Odin is on the computer mobile odin is on your phone
Sent from my SPH-D710 using xda premium
Ok. I'm on rooted EL29 right now. How do I get to the EL26-CWM from el29?
Sorry for all the questions guys. I appreciate everyones help getting me started.
Sent from my SPH-D710 using XDA
Just flash it through Odin. You can't mess it up. Flashing through custom recoveries is where people get bricks. That or flashing something for another phone on odin.
FF02 has basically been confirmed to be the final. Download SFhubs version and use odin. It is basically idiot proof. While your doing it watch QBkings video on how to flash through odin. His videos are a great guide and less scary then trying to read and apply what you think you just read.
Sent from my SPH-D710 using xda premium
Chew DZ said:
Ok. I'm on rooted EL29 right now. How do I get to the EL26-CWM from el29?
Sorry for all the questions guys. I appreciate everyones help getting me started.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
OK man time for you to learn how to use "search" on xda search for el26 cwm e4gt....
Edit: I use to ask all the question and everyone helped me so I'll help also, BUT my friend this should be in the Q&A
Here is what your looking for
http://forum.xda-developers.com/showthread.php?t=1662295
Also check this thread out. Be sure to read this b4 you even begin anything
http://forum.xda-developers.com/showthread.php?t=1525495
Sent from my PaRAnO!D aNDr0id!
So I just went from running pure stock rooted FI25, flashed agat's 0.5.4 source built kernel via odin, then rebooted into that custom recovery and flashed AOKP 3.1, flashed JB Gapps, and rebooted to blue LED.
We all run the risk I guess; just frustrating to see it happen on a process I've done literally hundreds of times.
Ordered a Jig and we'll see what happens.
Sorry man. That really sucks.
El26 kernel with cwm it is then.. 100% of the time.
Sent from my SPH-D710 using xda app-developers app
Are you sure that kernel was flashed? Did you see that it was agat recovery? Did you wipe? How did you wipe? What gapps did you flash? Are you sure you're actually hard bricked (not just soft)? These are just some questions I have that are useful...
Anyways, sorry to hear if you are legitimately bricked.
Sent from my SPH-D710 using Tapatalk
Click here for custom mods for your E4GT
Thanks for the warning.
Pp.
Sent from my ginger infused Mayan calculator.
sniper said:
Are you sure that kernel was flashed? Did you see that it was agat recovery? Did you wipe? How did you wipe? What gapps did you flash? Are you sure you're actually hard bricked (not just soft)? These are just some questions I have that are useful...
Anyways, sorry to hear if you are legitimately bricked.
Sent from my SPH-D710 using Tapatalk
Click here for custom mods for your E4GT
Click to expand...
Click to collapse
I odin'd to Agat source 0.5.4, rebooted.
Flashed Calk's format all script to do the wiping (did not even do factory reset)
Flashed aokp 3.1 unofficial
flashed gapps-jb-20120726
rebooted to blue led
edit
yes I saw it was agat recovery; I was running FI25 stock kernel before that (pure stock, no repack) so there's no question as to kernel version.
I still have my odin window open and have verified the file i flashed
sniper said:
Are you sure that kernel was flashed? Did you see that it was agat recovery? Did you wipe? How did you wipe? What gapps did you flash? Are you sure you're actually hard bricked (not just soft)? These are just some questions I have that are useful...
Anyways, sorry to hear if you are legitimately bricked.
Sent from my SPH-D710 using Tapatalk
Click here for custom mods for your E4GT
Click to expand...
Click to collapse
Agat's FH13 kernel isn't safe. It doesn't have the MMC_CAP_ERASE command removed.
Dude it happens ..i got screwed on that miui build that got locked ..my fault or not ..bottom line that sh*t sucks
Sent from my SPH-D710 using xda app-developers app
times_infinity said:
Agat's FH13 kernel isn't safe. It doesn't have the MMC_CAP_ERASE command removed.
Click to expand...
Click to collapse
That wouldnt matter if it were only used to install. Erase Cap is just that, an ERASE cap. To my knowledge it absolutely cannot be triggered by an install, although ot may have been present yet dormant. It sounds to me like mis-partitioning. just my $0.02..
Either way, if you cam get the power cycled you MAY be able to boot into DL mode and then after that huge IF you could find somebody who could help you set up a couple tests to find the damage and then partition around it. You may lose a gb or two but its better than Asurion getting more of our money..
This is the reason why I play it safe and keep a copy of el26 kernel zip.and tar on my sd card so when it comes to times like this doing a wiping data/factory reset. I know theres safe kernels out there but I only use them when im just wiping cache and dalvik only but when it comes down to doing a data/factory reset my safest kernel is el26.
Sent from my SPH-D710 using xda premium
PhAkEer said:
That wouldnt matter if it were only used to install. Erase Cap is just that, an ERASE cap. To my knowledge it absolutely cannot be triggered by an install, although ot may have been present yet dormant. It sounds to me like mis-partitioning. just my $0.02..
Either way, if you cam get the power cycled you MAY be able to boot into DL mode and then after that huge IF you could find somebody who could help you set up a couple tests to find the damage and then partition around it. You may lose a gb or two but its better than Asurion getting more of our money..
Click to expand...
Click to collapse
He used calk's format all. The script calls a format of the partition just like hitting factory reset in recovery. Which calls MMC_CAP_ERASE. That's what caused the brick.
Sent from my SCH-I500 using xda app-developers app
vanberge said:
So I just went from running pure stock rooted FI25, flashed agat's 0.5.4 source built kernel via odin, then rebooted into that custom recovery and flashed AOKP 3.1, flashed JB Gapps, and rebooted to blue LED.
We all run the risk I guess; just frustrating to see it happen on a process I've done literally hundreds of times.
Ordered a Jig and we'll see what happens.
Click to expand...
Click to collapse
Agat's kernals are for TW based roms only
bigdaddy619 said:
Agat's kernals are for TW based roms only
Click to expand...
Click to collapse
He flashed it for the included recovery.
Sent from my SCH-I500 using xda app-developers app
Below is a copy of the post I made in my kernel thread:
I don't think it's kernel related.
Guys I'm not saying I'm perfect nor I'm trying to defend myself.
my v0.5.4 has been downloaded:
tar format 569 times
zip format 587 times.
This totaling over 1100 times.
If kernel/recovery wouldn't be safe we would of have more of this problem.
More bricks.
I think there's something went wrong.
I can't say what and I can't say why. But knowing that the kernel has been used so many times without any hick ups or problems
makes me think there should be something not kernel related.
I really feel sorry for the brick and I hate the fact that it happened wile using my kernel.
I'll gladly fix any problem and/or brick cause.
Just checked source on my laptop.
CAP_ERASE command is not there.
Unless something went terribly wrong and it came back somehow it should not be there.
End of quote.
I might be wrong. I need any input I can get.
Please let me know if you thing there something wrong in my logic.
I wanna help and I wanna fix any possible problem but it looks like I can't do it alone.
Chip in guys and help me make our experience as safe as possible.
Thanks in advance for any input/idea/thought.
times_infinity said:
He used calk's format all. The script calls a format of the partition just like hitting factory reset in recovery. Which calls MMC_CAP_ERASE. That's what caused the brick.
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
I've used calks format all multiple times on unsafe recoveries before I knew about the brick bug and my phone was fine. I remember reading a lot of people used calks script and their phone didn't brick...
Sent from my SPH-D710 using Tapatalk 2
It could be the same reason why chris41g's AOSP kernels were vulnerable to the brick bug for a short while. You may want to reach out to him to see if he's able to provide some advice as to why it happened. Also, entropy is one of the most knowledgeable people on the brick bug, so you may want to reach out to him as well.
OP - I'm sorry you bricked man. This is the reason that even with all of these "safe" recoveries, I still do all of my flashing from stock EL26. It's tried and true and it only takes an extra 30 seconds at the most to flash using Mobile Odin.
Sent from my SPH-D710 using Tapatalk 2
Dchibro said:
It could be the same reason why chris41g's AOSP kernels were vulnerable to the brick bug for a short while. You may want to reach out to him to see if he's able to provide some advice as to why it happened. Also, entropy is one of the most knowledgeable people on the brick bug, so you may want to reach out to him as well.
OP - I'm sorry you bricked man. This is the reason that even with all of these "safe" recoveries, I still do all of my flashing from stock EL26. It's tried and true and it only takes an extra 30 seconds at the most to flash using Mobile Odin.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Yep. Seeing this thread is enough reason for me to keep using that method as well.
Sent from my SPH-D710 using xda premium
Dchibro said:
It could be the same reason why chris41g's AOSP kernels were vulnerable to the brick bug for a short while. You may want to reach out to him to see if he's able to provide some advice as to why it happened. Also, entropy is one of the most knowledgeable people on the brick bug, so you may want to reach out to him as well.
OP - I'm sorry you bricked man. This is the reason that even with all of these "safe" recoveries, I still do all of my flashing from stock EL26. It's tried and true and it only takes an extra 30 seconds at the most to flash using Mobile Odin.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
This is the first Ive heard of an Ecap on an Agat.. That being said,
Its something we are all always at risk (SLIGHTLY) because the negative effects of EraseCap a built into the phone. ICS software just so happens send a command that makes it more likely to be triggered...
El26 is only and can only be as safe as an ics source built kernel IF the source kernel has the Ecap hair trigger removed.
Sent from my SPH-D710 using Tapatalk 2
PhAkEer said:
El26 is only and can only be as safe as an ics source built kernel IF the source kernel has the Ecap hair trigger removed.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
And therein lies the rub. The only way to know it's truly safe is to dig into the code and actually know what to look for. Most people, myself included, either don't or don't want to take the time. Also, things change, kernel bases change, and since we're all human, mistakes can get made. There's no mistake that can be made when flashing from a GB based kernel.
I certainly wouldn't mind the days when I could use my current recovery for anything I wanted to do, but for me, those days are over on this phone. The alternative is barely an inconvenience anyways.
Sent from my SPH-D710 using Tapatalk 2
Dchibro said:
And therein lies the rub. The only way to know it's truly safe is to dig into the code and actually know what to look for. Most people, myself included, either don't or don't want to take the time. Also, things change, kernel bases change, and since we're all human, mistakes can get made. There's no mistake that can be made when flashing from a GB based kernel.
I certainly wouldn't mind the days when I could use my current recovery for anything I wanted to do, but for me, those days are over on this phone. The alternative is barely an inconvenience anyways.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
I dont think your quite hearing me....
the damage is done by mmc firmware that is on a level too deep for us to alter. It has been in every single epic touch since it was a wee little memory card on a little moving belt with the others...
Fy,gb,ics,jb has nothing to do do with it. If it were an Android issue it wouldve been fixed immediately and if it were a simple removal of a single line Samsung wouldve dealt with it just based on XDA forum knowledge...
It is embedded in your device.
As said, ICS just had an aspect that made it considerably more likely
Dchibro said:
And therein lies the rub. The only way to know it's truly safe is to dig into the code and actually know what to look for. Most people, myself included, either don't or don't want to take the time. Also, things change, kernel bases change, and since we're all human, mistakes can get made. There's no mistake that can be made when flashing from a GB based kernel.
I certainly wouldn't mind the days when I could use my current recovery for anything I wanted to do, but for me, those days are over on this phone. The alternative is barely an inconvenience anyways.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
PhAkEer said:
I dont think your quite hearing me....
the damage is done by mmc firmware that is on a level too deep for us to alter. It has been in every single epic touch since it was a wee little memory card on a little moving belt with the others...
Fy,gb,ics,jb has nothing to do do with it. If it were an Android issue it wouldve been fixed immediately and if it were a simple removal of a single line Samsung wouldve dealt with it just based on XDA forum knowledge...
It is embedded in your device.
As said, ICS just had an aspect that made it considerably more likely
Click to expand...
Click to collapse
the only way to keep the bug from being triggered is to remove the function that causes it in the mmc driver source.