Develop Bugs

How not to brick my phone?

I should be getting my device within the next day and I am going to root, I'm hearing all this stuff about bricking and I would like to know what to do and what not to do to end up in this situation thanks!
Sent from my Nexus S using xda premium

Darrien13 said:
I should be getting my device within the next day and I am going to root, I'm hearing all this stuff about bricking and I would like to know what to do and what not to do to end up in this situation thanks!
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Follow instructions carefully. If not sure what something is or how to do it, ask instead of blindly flashing. Oh, and don't ever use CWM Touch Recovery. Good Luck

Darrien13 said:
I should be getting my device within the next day and I am going to root, I'm hearing all this stuff about bricking and I would like to know what to do and what not to do to end up in this situation thanks!
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I HIGHLY recommend you follow QBKING77's videos on youtube he has videos on how to root(use the latest) he has review videos and how to install videos on every rom on this site. Stick with his video's follow them to a T and you should be good to go. I have had this phone for a good 3 months now and I LOVE it and have never had a problem while following his videos. You will love this phone it is AMAZING!
---------- Post added at 05:03 PM ---------- Previous post was at 05:02 PM ----------
stargaterules said:
Follow instructions carefully. If not sure what something is or how to do it, ask instead of blindly flashing. Oh, and don't ever use CWM Touch Recovery. Good Luck
Click to expand...
Click to collapse
Yes I can definitely agree with that DO NOT use touch recovery, I soft bricked my phone a couple weeks back using it trying to install Phantom Hackers Blazer rom. AMAZING rom BTW!

1) Don't use ROM Manager to flash anything in its temp recovery while on a ICS kernel
2) Don't use Touch Recovery at all
3) If you want to be as safe as possible, never wipe data while on a ICS + CWM repacked kernel. Anytime you wipe data, make sure you're on a GB + CWM kernel. The EL26 stock CWM repack works nicely, but I trust the EL29 + Rogue CWM repack. Now, I've wiped data on a ICS + Rogue kernel repack twice now and it went just fine, but it does seem that this may be risky. You may never brick doing it, but some have, so it may be better to be safe than sorry.
If you don't plan to flash anything ICS related, you really don't have much to worry about besides possibly #2.

Dchibro said:
1) Don't use ROM Manager to flash anything in its temp recovery while on a ICS kernel
2) Don't use Touch Recovery at all
3) If you want to be as safe as possible, never wipe data while on a ICS + CWM repacked kernel. Anytime you wipe data, make sure you're on a GB + CWM kernel. The EL26 stock CWM repack works nicely, but I trust the EL29 + Rogue CWM repack. Now, I've wiped data on a ICS + Rogue kernel repack twice now and it went just fine, but it does seem that this may be risky. You may never brick doing it, but some have, so it may be better to be safe than sorry.
If you don't plan to flash anything ICS related, you really don't have much to worry about besides possibly #2.
Click to expand...
Click to collapse
i was on calks ics rom and wiped everything then flashed his 2.9 rom. everything went just fine.

M1nze said:
i was on calks ics rom and wiped everything then flashed his 2.9 rom. everything went just fine.
Click to expand...
Click to collapse
As I said ... I have done the same, as have many others. However, just because it worked once, or twice, or twenty times, there could always be that one time where you brick. Steady Hawkin said he used his kernel repack to wipe and flash CM9 4 or 5 times with no issues, then doing the exact same thing again his phone bricked. Here's the quote ...
Steady Hawkin said:
Here is the story fellas:
I was on CM9 Alpha4, and I was flashing our FB21 rev2 to pull some logs. I had flashed Alpha4 and our kernel about four or five times already without any kind of issue. For whatever reason the next time I went to reflash Alpha 4, I booted into recovery wiped cache and dalvik cache (as I had done four or five times already with the same recovery and rom build) and it just hung at installing update. It was at that time I knew my luck had run out. No Odin (including using the jig I have), no connection to ADB, no nothing, just the blue light of death.
These bricks are concerning for a variety of reasons. The biggest IMO, is that there does not seem to be a single constant. People are bricking on different recoveries, with different roms, with different scenarios each time. TBH at this point I have no idea what is causing it or where to even start. I will say it is possible that these stock kernels from Sammie could play a role in the chaos, but thats just a guess.
Bottom line is, playing with ICS before we have any sort of source is going to be a gamble. If you dont have insurance on your phone I would hold off. I'm going to continue to do my best to try and figure out what is going on, but I cant guarantee anything. With the help of the other dev's I hope we can get this situated so we can move forward. In the meantime Team Rogue will continue to play with fire in a quest to move development forward.
Click to expand...
Click to collapse
Whether the extra time it takes to flash back to GB is worth it or not is up to each person.

I would recommend looking at this thread:
http://forum.xda-developers.com/showthread.php?t=1525495
I believe it is the intent of the OP on that thread to get it stickied if possible to avoid duplicate threads like this one.
If I may also share some advice given to me last week: Consider just rooting the stock ROM and getting familiar with it before jumping on to other ROMs. This gives you time to become more familiar with the device and stock capabilities as well as hopefully time to fully identify the brick issues and either work around them or resolve the cause.
I would also recommend keeping tabs on this thread:
http://forum.xda-developers.com/showthread.php?t=1504808
It never hurts to err on the side of caution in this case. Good luck and enjoy your E4GT when it comes in!

Flashing ICS?

OK I get my device tomorrow and I'm so happy! I plan to root it and I just wanted to know if flashing an ICS can potentially harm the device? Say that I flash back to a GB rom will everything still be perfect and work? Thanks
Sorry for all the questions just want to be sure for my device's arrival!

Do a nandroid backup first and if something goes wrong you can allways restore the back up and voila everything working perfect again. I do it all the time

Any flash can potentially harm a device...like docmarioce stated nandroid first. You can always pull one of the GB recovery ROMs from the Dev forum to go completely back to GB.
I'd highly, highly recommend watching some of qbking77's youtube videos on flashing, he's done an amazing job putting these together.

^^^ yeah, QBKing is awesome!
Darrien13 said:
OK I get my device tomorrow and I'm so happy! I plan to root it and I just wanted to know if flashing an ICS can potentially harm the device? Say that I flash back to a GB rom will everything still be perfect and work? Thanks
Sorry for all the questions just want to be sure for my device's arrival!
Click to expand...
Click to collapse
You have to Odin back to EL29 if you are on an ICS ROM and want to go back to GB.
Read, read, read before flashing any ROM
Enjoy your new phone!
Sent from my SPH-D710 using XDA

Don't use the recovery found on ANY ICS ROM. That means if you flash CM9, Calk's, Blendz, Venum (any ICS Rom leak), you will have ICS Rogue Repack Recovery which is known for BRICKING so many phones.
Note that, it's not the creator of the Rogue Recovery repack to blame, it is that Samsung is packing faulty kernels; Steady Hawkin, the creator, has even bricked his phone using his own tried and true methods. For some reason, the samsung kernels for ICS mess up the partitions on the phone when the recovery on an ICS leak is used.
So to sum things up.
1. DO NOT FLASH/WIPE/ RESTORE anything with the recovery repacked with the ICS leak ROMs.
2. If you want to flash, odin stock EL26 CWM.
(You might want to use the autoroot method by sfhub to install because odin'ing stuff gives you a yellow triangle on boot—Don't trust me on this, just a guess)
3. DO NOT FLASH/WIPE/RESTORE or even think of using the recovery found on any ICS ROM. Some CM9 users have bricked their phone simply by wiping cache on the recovery in CM9.
When you boot into recovery on an ICS ROM LEAK, and you see ROGUE, DO NOT FLASH/WIPE RESTORE! Run away!
My tone might be overexaggerated, but there have been many bricks reported on the CM9 dev thread here that I frequent. Those who used the rogue repack kernels found on ICS rom leaks instead of taking the safer route of odin'ing stock EL26 CWM and flashing/wiping/restoring on that, have bricked their phones.
CM9 thread
http://forum.xda-developers.com/showthread.php?t=1544233
More info:
http://forum.xda-developers.com/showthread.php?t=1525495
Be safe, and read read read.

Flashing ICS
I have successfully flashed a ICS ROM and then restored a backup to GB. This was before I was warned I have seen many of my friends hard brick there phone. I am waiting for a stable ICS ROM with a stable CWM.

Paden32 said:
I have successfully flashed a ICS ROM and then restored a backup to GB. This was before I was warned I have seen many of my friends hard brick there phone. I am waiting for a stable ICS ROM with a stable CWM.
Click to expand...
Click to collapse
same here. i actually wiped everything and it didnt brick. works just fine now! GB >>>> ICS

Flashing ICS
I have been hearing from people that the official ICS rom comes out March 15 I hope it does cant wait.

Paden32 said:
I have been hearing from people that the official ICS rom comes out March 15 I hope it does cant wait.
Click to expand...
Click to collapse
ICS is actually being pushed to the International version now in some places. I don't honestly thing we will see a March 15th date for us however (but hey I could be wrong)
As for Flashing ICS please read carefully there have been a ton of Bricks flashing ICS roms with ICS based kernels that have a recovery added to them. Your best bet honestly is to relax and chill read for awhile or a bit and when you feel confident in doing it then do so. My words for you ALWAYS keep Odin handy and if you do want to go back to a GB based rom then Odin a GB rom (like sfhub's EL29 Stock rooted) and push a GB based kernel with his auto root package.

Some people are lucky when using the ICS kernel recovery; in fact I am one of them . But eventually that luck will run out. I'm fortunate that I learned about its dangers before I could get a chance to brick my phone.

darkfire2024 said:
Some people are lucky when using the ICS kernel recovery; in fact I am one of them . But eventually that luck will run out. I'm fortunate that I learned about its dangers before I could get a chance to brick my phone.
Click to expand...
Click to collapse
Yes some have been lucky this is true. But when I see one of our own devs Brick their device from doing it not just users (thought they do count as well) I tend to be on the safe side and give people the way not only myself but others have done things for flashing between different roms and have so far always been safe

Here is what worked for me...
Download stock rom for ics fc07
Download rogue stock fc07 kernel
Place both on external SD card
Use sfhub's one click root method
Use sfhub's clockwork method
Make a backup
Wipe everything and run calks format all zip
Flash the rom and kernel (and modem) in the same setting and ur gtg
Sent from my SPH-D710 using XDA

Would you guys recommend not flashing anything ICS?
Sent from my Nexus S using xda premium

Darrien13 said:
Would you guys recommend not flashing anything ICS?
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I would say as long as you have Odin and take your time (whether its going to ICS or back to Gingerbread) then you will have no problems. If you want to be really safe, make it a rule that you flash ICS from a Gingerbread EL26 kernel w/CWM Recovery and if you want to flash something else once on ICS, Odin flash back to stock Gingerbread, Odin flash kernel with recovery and go from there. You can always PM me and I can shoot you links as well. Some people aren't having problems flashing from ICS w/ custom recovery but many have..including some devs
Sent from my Nexus S 4G using xda premium

Mobile odin??
Edit... Never mind
Sent from my SPH-D710 using Tapatalk

after flashing AOKP, no CWM, only Android System Recovery

first time I flashed aokp it was all gravy until I tried to boot into recovery, I got the Android System Recovery. I got scared and I read around and ended up odin'ing back to stock and flashing another rom.
I really like aokp so I wanted to try it again. I made very sure I followed the directions, I did not flash from an ICS recovery. I try booting into recovery to see if it worked this time and sure enough, there is android system recovery again, what am I doing wrong?
I searched for this too and saw that someone said to reinstall the packages and reboot, and do it again or something like that and it would boot into CWM, but that was for a different phone so I wasnt gonna try that.
Can I just run the eg4tauto.zip and isntall el26 with cwm to get recovery back and be good, or do I need to odin?
Any help would be greatly appreciated.

krook250 said:
first time I flashed aokp it was all gravy until I tried to boot into recovery, I got the Android System Recovery. I got scared and I read around and ended up odin'ing back to stock and flashing another rom.
You need to read the OP in the thread.
I really like aokp so I wanted to try it again. I made very sure I followed the directions, I did not flash from an ICS recovery. I try booting into recovery to see if it worked this time and sure enough, there is android system recovery again, what am I doing wrong?
I searched for this too and saw that someone said to reinstall the packages and reboot, and do it again or something like that and it would boot into CWM, but that was for a different phone so I wasnt gonna try that.
Can I just run the eg4tauto.zip and isntall el26 with cwm to get recovery back and be good, or do I need to odin?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
There is no cwm on aokp codename etc for a reason ....to stop people from bring stupid and bricking ....don't use a ics kernel with cwm for anything .... Use el26 to flash any ROM u need and when you want to go to another use mobile Odin or regular Odin to flash el26 kernel again and boot into cwm .... El26 is a GB kernel and won't boot a ics ROM ....then you can flash anything GB or ics
Sent from my SPH-D710 using Tapatalk 2 Beta-5

thanks for your response, but I think I am more confused, I was trying to flash a different modem. when I am not connected to 4g, my data is terrible, with 4g, I am all good. I was going to try a different modem. In the OP, for modems it says this:
Modems
FC18 Modem: DOWNLOAD
Flash through Stock CWM Recovery OR pull the modem.bin out of the .zip file and flash in the Phone option in Odin(mobile Odin doesnt flash modem)
Click to expand...
Click to collapse

You probably should flash back to a touch wiz ROM.....you can Odin the el29 tar or one click from sfhub .
http://forum.xda-developers.com/showthread.php?t=1433101
you can Odin the modem and then update profile and prl in tw then you can flash the el26 cwm http://www.mediafire.com/?hkydca9ob98z89m
and go back to aokp or codename etc
Sent from my SPH-D710 using Tapatalk 2 Beta-5

sorry if this is a dumb questions, but what if I get stuck in a boot loop and I have no recovery? just go into download mode and odin my way out?
one other thing, I started flashing ics roms with venum ice and flashed to mijjz ics and caulks and others and never had a problem, was I just lucky so far? I don't recall mijjz or venum's installation instructions saying I needed to odin back to stock before flashing. Sorry for the noob questions, but I've read a bunch and just trying to piece it all together. I read so I don't brick, but then I end up with more questions.

I'm also wondering about this I've spent a good deal of time trying to put the time line of the et4g together and I think I got most of it....just got my shiny white et4g two days ago my wife has had hers. for about 4 mo. shes much less fearless when it comes to flashing on this phone. (however shes settled in on build 27 of aokp, and I doubts shes gonna be flashing anytime too soon.) I'm coming over from my NS4G which always had clear cut rules to flashing! CWM all day. The only thing(s) I ever had to watch for was is it aosp, or not? An do I do a wipe or not? (I got in the habit of wiping just to be safe, and man I flash with the best of them! At least 2 times a week)
OK, OK sorry about the ramblings of my history my real questions are:
A) So Im sitting on alpha 2 of CM9 (nice piece of work I must Say) I made sure I was in the green, and had everything lined up to flash this one! went smooth of course. It wasn't until after my flash that I tried to make a nandroid....I get why theres no clockwork! but I'm totally clueless on how to back up with out it, or if you even can make one with stock recovery?
Can I keep CM9, and flash a kernel with rouge recovery to the make a nandroid? Or is there another way to go about this (I like to make nandroid often as a easy way to restore data after I play around with stuff and brake Wifi or what have you, and scrap unneeded back ups as I find out what I can and cant do with MY phone.)
I really really love Cryogen 9 (yeah its not as far along as I would like it to be ex- cm7 for the ns4g or kangs aokp builds) But there a team I'm familiar with. An I like there stuff, but I'm really nerves about where I go from here if/when i decide to change to something else.What are the guide lines for flashing from cm9 to say another ICS build? and is CM9 compatible with other kernels or only the one that is came packed with?
B) can someone straight up make a new clean thread with proper flashing tech. and no filler or out dated info then the have a mod stick it and close it>>>>simplify this for those of us that know what were doing....until things go funk for some reason, or another and that leaves ,us we are completely lost!
Well after wrighting my first novel (joke haha) I would like to thank everyone thats put up there time and money to make phones OURS and more powerful then what hit the shelfs an allowing me to get the most customized electronic device I have ever seen with the exception of my PC. Clapping

If you want to backup your system with the stock cm9a2 kernel, just mobile odin/odin el26 kernel/recovery, boot into cwm, flash stock cm9a2 kernel, now while still in cwm do a nand backup. That way it will be a full backup.
Sent from my SPH-D710 using xda premium

I know I'm a little late, but there is CWM for the AOKP rom. The FC07 BootImg on the e4gtuato.zip file worked fine for me on the older version which was based off of FC15.

faceyourfaces said:
I know I'm a little late, but there is CWM for the AOKP rom. The FC07 BootImg on the e4gtuato.zip file worked fine for me on the older version which was based off of FC15.
Click to expand...
Click to collapse
I would try that, but these folks have me scurred about using cwm within aokp. I have flashed between caulks ics/venum ice, anakonda/mijjz goodness,xplod mini and a couple other ICS roms all from cwm with absolutely no issues so far.
I am thoroughly confused right now. I am on aokp build 28 with a few significant issues and not sure what what direction to go next. I know how to get out of aokp safely now, but not sure which rom i want to go to, little issues with each that I dont know how to fix yet.

krook250 said:
I would try that, but these folks have me scurred about using cwm within aokp. I have flashed between caulks ics/venum ice, anakonda/mijjz goodness,xplod mini and a couple other ICS roms all from cwm with absolutely no issues so far.
I am thoroughly confused right now. I am on aokp build 28 with a few significant issues and not sure what what direction to go next. I know how to get out of aokp safely now, but not sure which rom i want to go to, little issues with each that I dont know how to fix yet.
Click to expand...
Click to collapse
Read this thread it happens when using ics kernel with cwm .and then tell us u want to use cwm with a ics kernel.....it bricks phones please read it and understand
http://forum.xda-developers.com/showthread.php?t=1525495
That's why people are using Odin to get el26 GB on their phones to flash with
Sent from my SPH-D710 using Tapatalk 2 Beta-5

krook250 said:
I would try that, but these folks have me scurred about using cwm within aokp. I have flashed between caulks ics/venum ice, anakonda/mijjz goodness,xplod mini and a couple other ICS roms all from cwm with absolutely no issues so far.
I am thoroughly confused right now. I am on aokp build 28 with a few significant issues and not sure what what direction to go next. I know how to get out of aokp safely now, but not sure which rom i want to go to, little issues with each that I dont know how to fix yet.
Click to expand...
Click to collapse
If you have been having luck thats fine but I can not see how you have not noticed int eh OP of the ICS roms and the OP of the recoveries it gives you instructions on what to do and what not to do. Also there are quite a few threads in here about the horror stories of the now infamous blue light of death. Once again if you have escaped this then maybe you should tell us your secret to success. Honestly the few extra steps it takes to ensure your phone stays your phone is well worth it.
Like Epix has posted please read up a little just incase something happens to you or anyone else who claims no problems so you know how to help yourself. Hopefully we wont have to see a I Think I just bricked my Phone thread from you.
Odin EL26 CWM and basically everything else stays the same after that... except you would need to either reflash the ICS rom you are using or have a copy of the kernel readily available

Epix4G said:
Read this thread it happens when using ics kernel with cwm .and then tell us u want to use cwm with a ics kernel.....it bricks phones please read it and understand
http://forum.xda-developers.com/showthread.php?t=1525495
That's why people are using Odin to get el26 GB on their phones to flash with
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
I've read that, hence the reason for my posts. I am not going to load cwm and start flashing away. From aokp, I will odin back to GB before I flash any new ICS roms. I also won't be flashing between other ICS roms, even ones I have done before with no problems. I odin every time now, but it is putting a serious damper on my flashing addiction.
I could flash 3 roms in the time it takes me to odin back to GB, lol!

krook250 said:
I've read that, hence the reason for my posts. I am not going to load cwm and start flashing away. From aokp, I will odin back to GB before I flash any new ICS roms. I also won't be flashing between other ICS roms, even ones I have done before with no problems. I odin every time now, but it is putting a serious damper on my flashing addiction.
I could flash 3 roms in the time it takes me to odin back to GB, lol!
Click to expand...
Click to collapse
I don't Odin to stock all the time I mobile Odin the el26 cwm kernel and then boot strait into recovery as the GB kernel won't boot the ics ROM and then I flash from there but I also u caulks format all too ....
Sent from my SPH-D710 using Tapatalk 2 Beta-5

Epix4G said:
I don't Odin to stock all the time I mobile Odin the el26 cwm kernel and then boot strait into recovery as the GB kernel won't boot the ics ROM and then I flash from there but I also u caulks format all too ....
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
Thus is what I used to do at first myself I would flash the CWM kernel then just nandroid back my old rom and keep it moving. It just basically seems that as long as you do everything in a GB kernel based recovery as long as it is not the Touch recovery you should be OK
Sent from my SPH-D710 using Tapatalk

I am gonna look into mobile Odin so i don't have to be sitting at a PC to do work. So if I go back to gb and get my modem biz straightened out then flash an ics rom, my modem changes will stick?
It seems like this issue is isolated to sprint only, right? Much buddy on att is flashing ics over ics like crazy. And he said he hasn't seen anything like this over there.
Sent from my SPH-D710 using XDA

I've only used the ICS recovery on AOKP to change modems and flash GB roms because it probably wouldn't work too well with other ICS roms.
krook250 said:
I am gonna look into mobile Odin so i don't have to be sitting at a PC to do work. So if I go back to gb and get my modem biz straightened out then flash an ics rom, my modem changes will stick?
It seems like this issue is isolated to sprint only, right? Much buddy on att is flashing ics over ics like crazy. And he said he hasn't seen anything like this over there.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
UPDATE: It seems that using recovery on Touchwiz-based ICS roms (like Blend ICS) is safe but it is much more dangerous on roms built from stock (like CM9). Your buddy must be using roms based off of leaked builds and not stock AOSP.
------------------
If you flashed back to Gingerbread to change your modems and installed an Ice Cream Sandwich rom over it the modem should stay.

faceyourfaces said:
I've only used the ICS recovery on AOKP to change modems and flash GB roms because it probably wouldn't work too well with other ICS roms.
UPDATE: It seems that using recovery on Touchwiz-based ICS roms (like Blend ICS) is safe but it is much more dangerous on roms built from stock (like CM9). Your buddy must be using roms based off of leaked builds and not stock AOSP.
------------------
If you flashed back to Gingerbread to change your modems and installed an Ice Cream Sandwich rom over it the modem should stay.
Click to expand...
Click to collapse
It has nothing to do with that it's the ics kernel and aosp and tw is using the same kernel but with minor changed , because there is no source released there can't be a built from source aosp kernel ....there is no safe ics kernel with cwm when source is released they will fix it, but the note has the same problem
Sent from my SPH-D710 using Tapatalk 2 Beta-5

Epix4G said:
It has nothing to do with that it's the ics kernel and aosp and tw is using the same kernel but with minor changed , because there is no source released there can't be a built from source aosp kernel ....there is no safe ics kernel with cwm when source is released they will fix it, but the note has the same problem
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
The recovery that came with Blend ICS worked fine for me though. Trying to flash using recoveries on other ICS roms gave me soft bricks. Would you have any idea how Blend worked for me?

faceyourfaces said:
The recovery that came with Blend ICS worked fine for me though. Trying to flash using recoveries on other ICS roms gave me soft bricks. Would you have any idea how Blend worked for me?
Click to expand...
Click to collapse
It is the same recovery and soft bricks ate usually from not wiping right....but use that kernel with cwm and wipe data and your risking a b.l.o.d. It doesn't take much ....the thing is Samsung changed a couple things with how the data partition is handled and they also changed a couple other partitions and sfhub said he thinks it writes over two of the partitions at the same time when wiping and makes both unusable creating a brick
... writers thing is it damages the emmc somehow and makes it even impossible to jtag it .... Which should really never happen
Sent from my SPH-D710 using Tapatalk 2 Beta-5

Epix4G said:
It is the same recovery and soft bricks ate usually from not wiping right....but use that kernel with cwm and wipe data and your risking a b.l.o.d. It doesn't take much ....the thing is Samsung changed a couple things with how the data partition is handled and they also changed a couple other partitions and sfhub said he thinks it writes over two of the partitions at the same time when wiping and makes both unusable creating a brick
Click to expand...
Click to collapse
So the best thing I guess would be to just to avoid ICS recoveries all around.

GB>ICS......why?

Is ics worth people bricking there phone,then going to different phone because there mad?
My brother has ICS and he loves it but I'm not taking the chance of bricking phone.....i keep seeing alota people who bricked there phone.
But is anyone sticking with GB and making more Roms and themes.
Sent from my SPH-D710 using xda premium

Well as far as sticking with GB development despite working on an ICS rom, sfhub released an update to his GB rom as well.
But if you odin over a stock ics rom and don't do anything stupid you should be pretty safe from bricking. Obviously usual risks for writing firmware to a device apply. Custom rom's should be flashed from GB instead of ICS CWM. Though I have had no issues flashing from ICS, taking risks that you were told not to take is your own fault.

RainMotorsports said:
Well as far as sticking with GB development despite working on an ICS rom, sfhub released an update to his GB rom as well.
But if you odin over a stock ics rom and don't do anything stupid you should be pretty safe from bricking. Obviously usual risks for writing firmware to a device apply. Custom rom's should be flashed from GB instead of ICS CWM. Though I have had no issues flashing from ICS, taking risks that you were told not to take is your own fault.
Click to expand...
Click to collapse
Well i know....but I can't take that chance so I'm sticking with gb till its safe lol,but it seems like no one else is making any new roms or atleast themes for GB
Sent from my SPH-D710 using xda premium

ScubaSteev said:
Well i know....but I can't take that chance so I'm sticking with gb till its safe lol,but it seems like no one else is making any new roms or atleast themes for GB
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Using the 1-click ODIN method to flash an official leaked build of ICS is perfectly safe. Bricking happens when you use a recovery to wipe data and/or caches. Something about the new ICS kernel not being fully compatible with the current recoveries or something. As long as you don't mess with a custom recovery and just ODIN the stock leaked ROM, Kernel, and Recovery, you will not brick the phone. Until Samsung releases the kernel source, stay away from CWM or anything else that's not stock. Let me reiterate this point: stock Samsung leaks flashed via ODIN are safe. Do not touch any CWM/Kernel repacks or flash anything (other than stock leaks) via ODIN or otherwise until Samsung releases the kernel source.

sputnik767 said:
Using the 1-click ODIN method to flash an official leaked build of ICS is perfectly safe. Bricking happens when you use a recovery to wipe data and/or caches. Something about the new ICS kernel not being fully compatible with the current recoveries or something. As long as you don't mess with a custom recovery and just ODIN the stock leaked ROM, Kernel, and Recovery, you will not brick the phone. Until Samsung releases the kernel source, stay away from CWM or anything else that's not stock. Let me reiterate this point: stock Samsung leaks flashed via ODIN are safe. Do not touch any CWM/Kernel repacks or flash anything (other than stock leaks) via ODIN or otherwise until Samsung releases the kernel source.
Click to expand...
Click to collapse
Well i might try it.....i don't have a computer though so i still wont beable to try ics
Sent from my SPH-D710 using xda premium

I've flash a ROM through an ICS Rogue Recovery several times, I just use Calkunlin's format-all ZIP.
I think most of the bricks happened with people flashing over AOKP/CM9/Codename through CWM. I've only flashed TW leaked based ROMs and had no issues, but of course ODIN would be the safest way to go about flashing ICS. All the ICS I flashed were from Rujelus22 (beta's) and FD05 from Agat63 (last night but for a little bit, then format all and flashed back to the previous ICS ROM).
You could always just revert to GB through ODIN, and flash an ICS ROM that way. ICS is great, but if GB is working perfectly fine for you and you don't mind waiting, I say stay on it.

As the poster above stated most bricks happen when coming from CM9/AOKP/AOSP/Codename. I've flashed through fb21 rogue repacked kernel multiple times. I just stay with the leaks(Blend ICS, Blend ICS XPLOD, Venums Anakonda, and Calkulins E4GT 2 ROMs). They work great and I really haven't had any bad experiences with them. I use stock(no cwm) kernels and mobile odin back to fb21 repack to flash new ROMS. I'm a flashaholic and flash back and forth when new versions come out.
Sent from my SPH-D710 using Tapatalk 2 Beta-5

Well when i get a laptop ill have to try it out
Sent from my SPH-D710 using xda premium

Pick up mobile odin, you can flash sfhub's one-click packages but you'll have to do the modem separately.

Esoteric68 said:
Pick up mobile odin, you can flash sfhub's one-click packages but you'll have to do the modem separately.
Click to expand...
Click to collapse
There is that and a good program it is but he can also flash from cwm on gingerbread if he has a kernel installed and id find that preferable. Of course if not can always flash a rogue kernel using mobile odin.
Remember don't use touch recovery!

quick questions can i restore a GB backup on ICS or should i odin back to EL29?

Odin
Sent from my SPH-D710 using XDA

tykalx said:
quick questions can i restore a GB backup on ICS or should i odin back to EL29?
Click to expand...
Click to collapse
ODIN only. Don't even think about restoring a GB backup on ICS.
---------- Post added at 04:00 AM ---------- Previous post was at 03:54 AM ----------
Mark.J.Linskiy said:
I've flash a ROM through an ICS Rogue Recovery several times, I just use Calkunlin's format-all ZIP.
I think most of the bricks happened with people flashing over AOKP/CM9/Codename through CWM. I've only flashed TW leaked based ROMs and had no issues, but of course ODIN would be the safest way to go about flashing ICS. All the ICS I flashed were from Rujelus22 (beta's) and FD05 from Agat63 (last night but for a little bit, then format all and flashed back to the previous ICS ROM).
You could always just revert to GB through ODIN, and flash an ICS ROM that way. ICS is great, but if GB is working perfectly fine for you and you don't mind waiting, I say stay on it.
Click to expand...
Click to collapse
I don't think the bricks have anything to do with AOKP/CM9, etc but rather formatting caches from within a GB recovery packed with an ICS kernel. Calk's format-all zip may be a safe way to do it, but from what I've read, it was the format process through recovery that caused the MMC chip failure. And even the AOKP instructions specifically say to flash from GB kernel/recovery because doing it from an ICS kernel/recovery can brick the phone. It's the ICS kernel at fault here, but we're not going to know specifically why until the source is released. Until then, I'd recommend not messing with repacked ICS kernels.

sputnik767 said:
ODIN only. Don't even think about restoring a GB backup on ICS.
---------- Post added at 04:00 AM ---------- Previous post was at 03:54 AM ----------
I don't think the bricks have anything to do with AOKP/CM9, etc but rather formatting caches from within a GB recovery packed with an ICS kernel. Calk's format-all zip may be a safe way to do it, but from what I've read, it was the format process through recovery that caused the MMC chip failure. And even the AOKP instructions specifically say to flash from GB kernel/recovery because doing it from an ICS kernel/recovery can brick the phone. It's the ICS kernel at fault here, but we're not going to know specifically why until the source is released. Until then, I'd recommend not messing with repacked ICS kernels.
Click to expand...
Click to collapse
Most of the bricks were caused by people flashing over AOPK/CM9/etc, I know it has to do with the Kernel as well but I'm saying that chances are much higher if you're flashing over those ROMs. Thing is, to flash a TW ICS leaked based ROM, I only use Calkulin's format all, but I've also flashed Kernels/Modems through the Rogue repacked after wiping dalvik/cache and haven't had an issue. I know for sure that formatting manually before a ROM flash will probably cause a brick as well and flashing the AOSP based ROMs in an ICS recovery will most likely do the same. Either way, Odin is the safest and best way, especially if some is hesitant.
Hope you don't take it as me being a jerk or anything, just saying it how I know it, even though I may be wrong.

Mark.J.Linskiy said:
Most of the bricks were caused by people flashing over AOPK/CM9/etc, I know it has to do with the Kernel as well but I'm saying that chances are much higher if you're flashing over those ROMs. Thing is, to flash a TW ICS leaked based ROM, I only use Calkulin's format all, but I've also flashed Kernels/Modems through the Rogue repacked after wiping dalvik/cache and haven't had an issue. I know for sure that formatting manually before a ROM flash will probably cause a brick as well and flashing the AOSP based ROMs in an ICS recovery will most likely do the same. Either way, Odin is the safest and best way, especially if some is hesitant.
Hope you don't take it as me being a jerk or anything, just saying it how I know it, even though I may be wrong.
Click to expand...
Click to collapse
No, I don't think you are being a jerk at all, and I'm trying to learn something along the way as well. We are both simply trying to prevent another bricked device, I just tend to be extremely cautious, perhaps even unnecessarily cautious. But I came here from an Evo 4G that was bricked by a bad recovery (Team Win Recovery Project touch recovery killed quite a few Evos), so I only use the absolute safest method possible for myself, which is ODIN and stock leaks. I will go back to CWM once the source is released and we know what's actually going on.

sputnik767 said:
No, I don't think you are being a jerk at all, and I'm trying to learn something along the way as well. We are both simply trying to prevent another bricked device, I just tend to be extremely cautious, perhaps even unnecessarily cautious. But I came here from an Evo 4G that was bricked by a bad recovery (Team Win Recovery Project touch recovery killed quite a few Evos), so I only use the absolute safest method possible for myself, which is ODIN and stock leaks. I will go back to CWM once the source is released and we know what's actually going on.
Click to expand...
Click to collapse
Yeah, I completely understand. I didn't touch a single ICS ROM until I was asked to do some testing, and even when updated the Beta I would Odin back to GB then flash it. The developer told me he had no issues with flashing the format ZIP and flashing his Betas so I tried it and no issues. It's always good to stay cautious, and there's absolutely nothing wrong with what you're doing, since after-all, it is your personal device. I recommend people use Odin as well, especially for those who aren't completely sure what they're doing. Makes perfect sense for staying away from CWM until the source is out.

All so understandable......better to have more people then less people asking question.s and giving answers....its helping me alot
Sent from my SPH-D710 using xda premium

ScubaSteev said:
All so understandable......better to have more people then less people asking question.s and giving answers....its helping me alot
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Yup, that's what makes it a good community. Glad it's helping you out, and if you decide to flash, good luck!

Mark.J.Linskiy said:
Yup, that's what makes it a good community. Glad it's helping you out, and if you decide to flash, good luck!
Click to expand...
Click to collapse
Ima try to learn a little more then flash....thanks for all info guys/gals
Sent from my SPH-D710 using xda premium

I've been on ICS roms for about a month (Calkulin's with ICS4ICS theme) and I have to admit that the battery life is absolutely horrible compared to GB roms

I thought we were past this (bricked)

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.