Hello all,
I had the eMMC bug on my galaxy s2, even by being careful and reading a lot of guides before, I didn't read about the bug until it was too late...
It is currently being repaired by a samsung repair center... thanks again to all the persons who gave me support and advice during this sad episode !
Obviously, I don't want to brick it again...
I have read a lot more since, but to be on the safe side, can you confirm or correct the following ?
When I receive it, if it is on 4.0.4 official, I should NOT attempt any wipe or format.
if I want to flash CM9.1, first thing I have to do is:
install "Siyah S2-v5.0.1"
and then, I can do all the wipes/format in the world I want from CWM, correct ?
also, what is the best way to flash Syah from a stock rom ? Odin or temp CWM ?
can you give me the pros and cons of each solutions ? Is there any other solution ?
Before bricking my s2, I did a nandroid backup.
if I restore my nandroid backup from temp CWM, will it trigger the emmc bug again while restoring it ?
What is your advice, should I flash Siyah S2-v5.0.1 then restore from Siyah CWM my nandroid backup ?
My nandroid backup was done when I had stock 4.0.4 and from CWM temp.
Lastly, is it perfectly safe to flash from Odin GB --> ICS and ICS --> GB ? I have read you can hardbrick your phone going from ICS to GB... not sure how though...
Thank you guys
Hey sorry for this bad news...
So because next steps...
1) restoring nandroid
If u want to go ahead and not use the 4.0.4 any longer, just leave it, to be sure...
2) next steps
Personally I would say u can choose between two options:
- Flash another firmware + root + flashing ahead....
- flash the named Siyah + flash another Rom (with full wipe)
3) how
Because u will have a stock phone back, at least I'm sure about this , u can do the first option with searching a firmware on: http://www.sammobile.com/firmware/?page=3
Download and flash this via odin (I think u know how u do this)
If u choose the second way, it's quite the same thing but u won't flash the firmware, because u use the .tar u find from the kernel on http://d-h.st/Bcf
So hope this brings u further, buddy
CHEERS
Sent from my GT-I9100 using xda premium
megosu said:
Hello all,
I had the eMMC bug on my galaxy s2, even by being careful and reading a lot of guides before, I didn't read about the bug until it was too late...
It is currently being repaired by a samsung repair center... thanks again to all the persons who gave me support and advice during this sad episode !
Obviously, I don't want to brick it again...
I have read a lot more since, but to be on the safe side, can you confirm or correct the following ?
When I receive it, if it is on 4.0.4 official, I should NOT attempt any wipe or format.
if I want to flash CM9.1, first thing I have to do is:
install "Siyah S2-v5.0.1"
and then, I can do all the wipes/format in the world I want from CWM, correct ?
also, what is the best way to flash Syah from a stock rom ? Odin or temp CWM ?
can you give me the pros and cons of each solutions ? Is there any other solution ?
Before bricking my s2, I did a nandroid backup.
if I restore my nandroid backup from temp CWM, will it trigger the emmc bug again while restoring it ?
What is your advice, should I flash Siyah S2-v5.0.1 then restore from Siyah CWM my nandroid backup ?
My nandroid backup was done when I had stock 4.0.4 and from CWM temp.
Lastly, is it perfectly safe to flash from Odin GB --> ICS and ICS --> GB ? I have read you can hardbrick your phone going from ICS to GB... not sure how though...
Thank you guys
Click to expand...
Click to collapse
If it is 4.0.4, flash that kernel you mentioned, it's a safe one.
Then, all you have to do is whatever it is that you wanna do with it.
You are now very experienced with odin, DL mode and Recovery mode, you kept on trying to get your old SII back to the living (I was there, I saw you tried).
With your new device you have the chance to start clean, from scratch, forget about that nandroid back up, keep reading here on XDA and I ASURE you, you'll do 5 times better than the past.
BTW: you weren't affected by the brick bug, your device was kinda faulty after all. Brick bugged devices wouldt let you go into DL mode.
I strongly recommend you read the Stickies. The questions you've asked have been answered hundreds of times on here before. And that you've asked them is indicative of not knowing 'the basics'.
Surveys show people who read them have a 84% less chance of bricking their phone than people who don't (almost everyone who visits here & jumps into doing stuff with their phone without understanding the basics/how the phone & its firmware actually works first).
I have read the stickies... thank you for that
according to your survey, one who reads the stickies still has 16% of chance to brick his device, this is why I want to be extra sure and asked for advice about specific questions, not a lecture :/
It might be obvious for you, but not for everybody, so when somebody asks a question that seems silly for you, helping the guy by answering is more helpful than telling him to read stickies, and it helps also others who come across this thread not being 100% sure of what they understood from reading stickies.
in my case, I have read on the forum the following and I would appreciate some help to confirm if I gathered the correct information.
As I said previously, it might be obvious for you but it can help me and others NOT to brick their phone !
When I receive it, if it is on 4.0.4 official, I should NOT attempt any wipe or format.
if I want to flash CM9.1, first thing I have to do is:
install "Siyah S2-v5.0.1"
and then, I can do all the wipes/format in the world I want from CWM, correct ?
Click to expand...
Click to collapse
I also think I know the answer about this:
also, what is the best way to flash Syah from a stock rom ? Odin or temp CWM ?
can you give me the pros and cons of each solutions ? Is there any other solution ?
Click to expand...
Click to collapse
I think it is safer to flash through Odin as the temp CWM has the emmc bug. But Odin will change my binary counter and add the yellow triangle...
hence why I asked your advice
I haven't found the answer in the stickies about this one... maybe you know if it is safe to restore a nandroid backup ?:
Before bricking my s2, I did a nandroid backup.
if I restore my nandroid backup from temp CWM, will it trigger the emmc bug again while restoring it ?
What is your advice, should I flash Siyah S2-v5.0.1 then restore from Siyah CWM my nandroid backup ?
My nandroid backup was done when I had stock 4.0.4 and from CWM temp.
Click to expand...
Click to collapse
and lastly,
is it perfectly safe to flash from Odin GB --> ICS and ICS --> GB ? I have read you can hardbrick your phone going from ICS to GB... not sure how though...
Click to expand...
Click to collapse
same here, didn't find it in the stickies... and I saw different answers across the forum so it is hard to get conclusions out of it.
again, sorry if it is too easy for you or if you feel like it has been said somewhere else, but your answers can make the difference for people and avoid a brick.
And it doesn't hurt to repeat a correct information, it just confirm it and make it more noticeable.
Thanks for your help,
MistahBungle said:
I strongly recommend you read the Stickies. The questions you've asked have been answered hundreds of times on here before. And that you've asked them is indicative of not knowing 'the basics'.
Surveys show people who read them have a 84% less chance of bricking their phone than people who don't (almost everyone who visits here & jumps into doing stuff with their phone without understanding the basics/how the phone & its firmware actually works first).
Click to expand...
Click to collapse
easy now, you can ask whatever you want as long as you read/search first.
If you did, then it's all good, just because you are trying very hard to not messing up with your device.
I don't know what to put here...any ideas?
anyone to confirm if I got it right ?
I'm lost here; how are you doing with your new device anyways?
still at the repair cente, it is going to take ages
but at least I have time to "prepare", if somebody can answer to my questions of course
megosu said:
still at the repair cente, it is going to take ages
but at least I have time to "prepare", if somebody can answer to my questions of course
Click to expand...
Click to collapse
thought they gave you a new one.
what was the question again?
Well, basically all questions from http://forum.xda-developers.com/showpost.php?p=36480894&postcount=5
At least the first one:
Quote:
When I receive it, if it is on 4.0.4 official, I should NOT attempt any wipe or format.
if I want to flash CM9.1, first thing I have to do is:
install "Siyah S2-v5.0.1"
and then, I can do all the wipes/format in the world I want from CWM, correct ?
I'll try and help you out with a noob-friendly solution.
Remember emmc brickbug affects ONLY AND ONLY devices running 4.0.4 STOCK kernel. if you're running anything else, then u're safe.
if your new device comes with 4.0.4 stock, then the ONLY thing you need to do to be safe is flash a safe kernel (siyah is a valid option) through ODIN.
once u've done that, you will get root+permanent CWM.
Now all you need to do is start flashing, making backups or whatever you please !
Hope I shed some light on your issue pal.
Hugs.
Thank you,
So I got it right, I'll flash siyah first.
thanks again for taking the time to help.
Take care
Related
Hi
I have not modifyed my S2 anything since I bought it, only updated via Kies.
I have read som rooting threads, but it seems to be more than 1 way to do things.
I wish to flash a custom kernel (Cognition S2, VillainROM or TK-rom)
But before I can flash a rom I need ClockworkMod Recovery.
Which methode should I use? CF-Root v4.0 or ClockworkMod Recovery 4.0.0.5
The first methode also brings root, but is this nessesary since the custom roms I wish to flash already are rooted?
Also does anyone know if Heimdal works for S2?
Thanks!!
bump
always wanted to know that too
seems to confusing to me
i did search for it and its just too confusing
from what i understand is that
( do this then this and dont forget that but before u do this do this and dont forget to do that before u start anything and when u finish that do this restart hold three buttons then do that wait for the yellow thing press next wait for it then do that and ur finished but if a triangle appears or you brick your phone u need a 301k resistor or buy a jig and then start steps RI8 to bmx23 and then your done)
sometimes i hate android
the problem is nothing is found in one thread
FAQs are scattered everywhere with not a lot of information
i wish if there was a post that has everything i need to know ive been here for a while and im still learning new stuff
i hope some one answers this for you
You can just flash the CF root kernel and download from here http://forum.xda-developers.com/showthread.php?t=1103399
Pick the kernel that correlates to the firmware you are using.
Once you flash that, you can get into recovery by holding Power, Volume Up and Home button when the phone is in an off state. Then you will be in Clockwork Mod Recovery and can flash new roms.
Its really quite easy once you get the hang of it and ODIN is quite useful as you can flash just kernels or modems using it or quickly go back to a stock ROM.
Yes this method brings root but its just an added bonus in case you want to back everything up with Titanium Backup before going into CWM to flash a new rom. Root isn't necessary but it doesnt matter if it roots before you install another rooted rom. The new ROM will normally wipe everything anyway if its a wipe rom.
Heimdel does work but I don't personally use it or know which is the newest and best version to use with SGS2
Oh and this thread was created for beginners of SGS2, it is attempting to put all information in one place to try and help make it easier to understand http://forum.xda-developers.com/showthread.php?t=1125282
blue265 said:
Oh and this thread was created for beginners of SGS2, it is attempting to put all information in one place to try and help make it easier to understand http://forum.xda-developers.com/showthread.php?t=1125282
Click to expand...
Click to collapse
oh he updated it
didnt know thanks
My phone is quote slow and laggy and it's quite surprising seeing as this phone is meant to be known for it's speed and power.
I have rooted with cf-root , I don't really know if this means if I have a custom kernel.
All I want to know is if there is a custom ROM or kernel to help with this. If yes, which one. Many developers claim there stuff speeds up phones but obviously they're bias. I want neutral opinions from people with experience of different things.
Before people tell me to search I can only access the net through my phone and the drop down search button don't work.
First of all rooting your phone is good cos it now means that you can flash a custom ROM.Something that cant be done on stock.For the moment stay with CF-Root as they are basically stock rooted kernels and at the moment I dont think you need to get into overclocking and undervolting and all that stuff that more advanced kernels can do cos if you do it wrong yourve got problems.As for ROMs your right.All Devs will say that they have the best one and all happy users,yes like myself,will say they use the best one too.The problem is that everyone has different likes and needs.No one who has spent time on this site has ever only had ONE ROM on their phone.Its impossible to not turn into a flashaholic at some stage.The best you can do is read threads and try some.Not the answer you wanted but its the best and only way to find what you want.Try mine.I love it.The link is below the big blue Omega sign.Its the one that says "GB".If you dont like it then try something else.Theres really no other way to find out what you want unless you try for yourself.
I see.. So I simply download the custom ROM and install it through clockwork mod?
Do I have to back up my phone with titanium back up before I install custom roms?
anz2k8 said:
I see.. So I simply download the custom ROM and install it through clockwork mod?
Do I have to back up my phone with titanium back up before I install custom roms?
Click to expand...
Click to collapse
Step 1 - backup with titanium.
Step 2 - reboot into cwm or with the cwm app, create a backup. So, if you flash something that you don't like or if it wont boot, you can restore it. This is a complete system and data backup. A 1:1 copy of your phone setup, excluding modem which defaults to whatever you are running at the time of restore.
Step 3 - try some custom roms. I use Checkrom (older version - v2) and phone flies.
Anyway, something must be wrong with your setup because every rom I've used has been fast, even stock.
ps : sent you a pm.
Sent from my GT-I9100T
Once you get sorted then do an EFS backup.The EFS folder contains your IMEI number and if for whatever reason you should loose it or it becomes corrupt then you are in the poo.Download the "release.zip" and follow the easy instructions.
http://forum.xda-developers.com/showthread.php?t=1308546
I was using checkrom v4 and then v6 for a little while both with SiyahKernel which worked really well.
Currently using CM9 but I wouldn't go there until your comfortable fixing things and regularly flashing.
But definately select your rom and then try changing kernels if you think it will benefit you.
Sent from my GT-I9100 using Tapatalk
@cooza when should I back up this eps, everyone time I change ROM or everyone I change kernel? I don't even know what it is lol
@sxi200 you say there must be something wrong with my setup, could you explain in a little more detail what you think I should change please?
Just thought I would *Bump* the thread as i'm slightly desperate for the random rebooting. It happens approximately once or twice a day.
did u use wipe data/factory reset while installing a new rom?
expierienced some funny things like lag etc also while trying different roms,
my fault was not wiping the cache ...
anz2k8 said:
Just thought I would *Bump* the thread as i'm slightly desperate for the random rebooting. It happens approximately once or twice a day.
Click to expand...
Click to collapse
One Factory reset the phone this will wipe all data
Two upgrade firmware via Kies if firmware is available .
Three flash a later stock Samsung rom .
Four any of the answers already posted .
Five wait for Samsungs ICS update .
i see you have rooted but dont know what root is for or even any of the basics .
Read the guides and stickies .
Guide
http://forum.xda-developers.com/showthread.php?t=1125282
Its possible that you have rooted with a wrong file .
But you give zero information .
jje
I was running the Spike Pure ICS on my SGS2, before which I had the ICS version of MIUI. I tried flashing Lite'ning Rom 3.6 through Odin, but was unsuccessful. Also, that's time I noticed the 7.2 version of CM and decided to flash that and that's when the problem occurred.
Although I could flash CM 7.2 properly and could also install the GApps through CWM, on rebboting it through the CWM, my phone got stuck and it wouldn't go into Recovery any more.
Luckily, it would boot into Download Mode and I could flash the stock rom through Odin and get my phone back to stock, thereby losing the Root and CWM.
I wanna know as to what could cause such an issue to arise. so that I can prevent it later!
Your help and time are appreciated!!
Why start a 2nd thread ?
That's because every person who replied told me how to go about the problem, but nobody told me why it occurred in the first place!
I posted this thread so that I can know how to avoid such a problem in the first place, as such a problem seemed very unique to all the people I talked to.
And you couldn't make another post to your initial post along the lines of 'Why did this occur in the first place ?' You could even easily change the title of your initial thread to reflect your desire to know the answer to this question.
One of the main rules of XDA is don't spam.
I'm extremely sorry if I've spammed as it wasn't my intention at all!
This thread was and still is a genuine question which I want to know!!
Also, could you please tell me about the occurrence of such a problem on my phone??
gadgyfreak said:
That's because every person who replied told me how to go about the problem, but nobody told me why it occurred in the first place!
I posted this thread so that I can know how to avoid such a problem in the first place, as such a problem seemed very unique to all the people I talked to.
Click to expand...
Click to collapse
I think answer was there but might be not clear......
When you flash gb over ICS you have to wipe, when you mix stuff after that, meaning trying different kernels to fix the issue it might get worse.
Because recovery is somewhat linked to kernel in s2, you won't get recovery in a messed up system.
So when you flash a complete firmware using Odin and then do data cache wipe, it get fixed.
Hope this helps.
But then how is it possible that my phone didn't get all messed up when I flashed CM 9(Nightly) over my pre-existing CM 7.1, while it happened when I tried it vice versa?
already told you, when you go from ICS newer kernel to GB older kernel, wipe is necessary. Going from GB to ICS will work but wipe is better there too.
Thanks a lot for your help.
So what exact procedure do I have to follow if I want to mover from ICS to GB?
Flash a GB rom.
gadgyfreak said:
Thanks a lot for your help.
So what exact procedure do I have to follow if I want to mover from ICS to GB?
Click to expand...
Click to collapse
save data
Wipe dial *2767*3855#
Flash GB Rom, preferably stock using Odin.
Should boot now, if not go into recovery and wipe data cache.
It will boot now.
Okay, before any of the regular contributors here say something nasty to me for asking a question that's been asked and answered, I want you to know that I have spent 2 days reading through -all- xda forums that might even -remotely- relate to my problem, without finding any answers. I also spent several hours searching all the common Android forums elsewhere, as well as, silly sites like Yahoo answers, etc., but have not been able to find the answer to my question. I'm the first to admit that reading the exorbitant amount of information in here causes my brain to short circuit due to all the numbers, versions, etc. It's like reading tax code; use C1.4.6 unless you've submitted b45.1. In that case, use d16.9, unless you've also filed a p32 in the last 2 years...if so, then....blah blah blah.
I love all you cell phone OS gurus and am quite envious of your ability to effortlessly wade through the technology involved in these phones. I wish, wholeheartedly, that I didn't have to ask any questions here because I know how irritated many of you become over people like me asking stupid questions, but I have no where else to turn. Believe me, if I could go elsewhere, I would, for your sake.
I was running 2.3.4, rooted, stock ROM. Froze the system with TB Pro to prevent the upgrade to 2.3.6. Unfroze it. Upgraded. Decided to unroot so I could sell my phone in favor of another. Ran Odin. Ran SuperOneClick. Ahhh...and there's the problem. SOC doesn't work with 2.3.6. So now, I don't know what to do. My phone is half rooted. I can't unroot and I can't reroot. I get the triangle, but TB Pro doesn't work because I'm not rooted, well. sort of not rooted. I guess I'm a little rooted. I don't know what to do next mainly because, every time I find what I think is a solution, I find another source that says, "DON'T DO IT! YOU'LL BRICK YOUR PHONE!" So, here I am, hoping someone will point me in the right direction without chastising me for asking a stupid question. I checked the solution in here and it's great, except, and I quote "Not working for KK6 2.3.6"
Thanks for any help....
So, what you need to do at this point is flash back to stock 2.3.4 using the instructions in the How to prepare your phone ... thread which is a sticky in the general section of this I777 forum. Since you were stock before, and evidently didn't flash any custom firmware, you should be fine flashing the stock distribution with Odin or Heimdall, or using the Odin one-click downloader.
First enter 3e recovery and perform a wipe data/factory reset, then do the Odin or Heimdall flash. The thread has instructions to clear your personal data as well.
Now, you know, I read that post along with all the stickies, about how to return the phone to stock, but I couldn't find any mention of whether or not it worked with a half rooted phone. I didn't want to be one of those people who blindly followed directions not intended for her situation, only to wind up bricking my phone or in a constant boot loop.
Thank you for not criticizing me for my apparent stupidity. I do my best.
Thank you so much for pointing me in the right direction.
tunie said:
Now, you know, I read that post along with all the stickies, about how to return the phone to stock, but I couldn't find any mention of whether or not it worked with a half rooted phone. I didn't want to be one of those people who blindly followed directions not intended for her situation, only to wind up bricking my phone or in a constant boot loop.
Thank you for not criticizing me for my apparent stupidity. I do my best.
Thank you so much for pointing me in the right direction.
Click to expand...
Click to collapse
You can't have a "half rooted" phone, and it wouldn't matter at all anyway since you're going to be booting into download mode in order to flash to stock.
Sent from my Zanpakuto using Getsuga Tensho!
First of all:
Understand what 'ROOT' is.
IT IS ADMINISTRATOR ACCESS TO YOUR DEVICE, NOTHING MORE, NOTHING LESS.
everything for 'root' resides in the OS under the /system partition...which means when you load a new/stock rom on it, everything in /system gets wiped...
root has nothing to do with recovery mode or download mode. you cant be 'half-rooted'. you either have administrator access or you dont, plain and simple.
When I rooted so very long ago, I used SGH-I777_ClockworkMod-Recovery_5.0.2.3 that I downloaded with su-3.0-efgh-signed. At the time, I didn't understand what this was. I only understood that this would root my phone. I didn't want to flash any custom ROM's because, to this day, I really don't understand what a ROM is. Yes, I've read about it. Still don't get it. So, did I flash a custom ROM? As far as I knew, all I did was root so I could use TBPro to backup and freeze, and use LBE to keep my information as private as possible.
<edit> So I've just reread many of your posts. You really are great at explaining this stuff and I thank you for that. It seems, from what I've read, that I can just do a factory reset and the phone should go back to its original state, with 2.3.4. Is that correct?
Thank you, again. I swear I'll be out of everyone's hair in here as soon as is humanly possible.
creepyncrawly said:
So, what you need to do at this point is flash back to stock 2.3.4 using the instructions in the How to prepare your phone ... thread which is a sticky in the general section of this I777 forum. Since you were stock before, and evidently didn't flash any custom firmware, you should be fine flashing the stock distribution with Odin or Heimdall, or using the Odin one-click downloader.
First enter 3e recovery and perform a wipe data/factory reset, then do the Odin or Heimdall flash. The thread has instructions to clear your personal data as well.
Click to expand...
Click to collapse
Pirateghost said:
First of all:
Understand what 'ROOT' is.
IT IS ADMINISTRATOR ACCESS TO YOUR DEVICE, NOTHING MORE, NOTHING LESS.
everything for 'root' resides in the OS under the /system partition...which means when you load a new/stock rom on it, everything in /system gets wiped...
root has nothing to do with recovery mode or download mode. you cant be 'half-rooted'. you either have administrator access or you dont, plain and simple.
Click to expand...
Click to collapse
Thank yes, I understood what root was which is why I did it. I just didn't understand the mechanics of getting there. Perhaps it's the same thing that made pre-med chemistry so difficult for me in college. I could do the work, but didn't get the big picture, so I couldn't build a knowledge base. Anyway, I see the triangle and GT I9100 at boot up, yet I cannot access TB Pro as it states I'm not rooted. So, I guess I did unroot, but didn't go all the way because 2.3.6 doesn't play nice with popular root/unroot apps. Thanks for explaining.
tunie said:
Thank yes, I understood what root was which is why I did it. I just didn't understand the mechanics of getting there. Perhaps it's the same thing that made pre-med chemistry so difficult for me in college. I could do the work, but didn't get the big picture, so I couldn't build a knowledge base. Anyway, I see the triangle and GT I9100 at boot up, yet I cannot access TB Pro as it states I'm not rooted. So, I guess I did unroot, but didn't go all the way because 2.3.6 doesn't play nice with popular root/unroot apps. Thanks for explaining.
Click to expand...
Click to collapse
The triangle has nothing to do with root. It only means you flashed a kernel using Odin.
Sent from my Galaxy Nexus
tunie said:
It seems, from what I've read, that I can just do a factory reset and the phone should go back to its original state, with 2.3.4. Is that correct?
Click to expand...
Click to collapse
No. When you do a wipe data/factory reset, this wipes the data partition but does not touch the system partition. So you will still have whatever firmware you started with, which in your case I believe is 2.3.6, but it will be put back to like it was when it was first installed.
That's why I recommended that you perform a wipe data/factory reset, and then flash the 2.3.4 stock firmware. The factory reset is so that when the new 2.3.4 stock firmware boots up, there will be no problems.
Pirateghost said:
The triangle has nothing to do with root. It only means you flashed a kernel using Odin.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Well thank you. I give up. Really, I do.
creepyncrawly said:
No. When you do a wipe data/factory reset, this wipes the data partition but does not touch the system partition. So you will still have whatever firmware you started with, which in your case I believe is 2.3.6, but it will be put back to like it was when it was first installed.
That's why I recommended that you perform a wipe data/factory reset, and then flash the 2.3.4 stock firmware. The factory reset is so that when the new 2.3.4 stock firmware boots up, there will be no problems.
Click to expand...
Click to collapse
Well, I actually understand that. Thank you. My concern now is whether or not I flashed a custom ROM. Clockworkmod appears to be a custom ROM, no? If it isn't, I know what to do, thanks to you. If it is a custom ROM, I don't know what to do next.
tunie said:
Well, I actually understand that. Thank you. My concern now is whether or not I flashed a custom ROM. Clockworkmod appears to be a custom ROM, no? If it isn't, I know what to do, thanks to you. If it is a custom ROM, I don't know what to do next.
Click to expand...
Click to collapse
clockwork mod is NOT a custom ROM. clockwork mod is RECOVERY and on this device it is compiled WITH the kernel.
YOU HAVE A CUSTOM/MODIFIED KERNEL
I really dont understand why you dont just follow creepyncrawly's advice and tutorials...you are making this out WAAAAAY harder than it really is.
Pirateghost said:
clockwork mod is NOT a custom ROM. clockwork mod is RECOVERY and on this device it is compiled WITH the kernel.
YOU HAVE A CUSTOM/MODIFIED KERNEL
I really dont understand why you dont just follow creepyncrawly's advice and tutorials...you are making this out WAAAAAY harder than it really is.
Click to expand...
Click to collapse
Just want to insure that I've relayed all the necessary information, correctly. I guess I have. Thank you and I'm sorry I took anyone's time.
tunie said:
Well thank you. I give up. Really, I do.
Click to expand...
Click to collapse
That dreaded yellow triangle show up when you flash a custom (non-stock) kernel. When you flash a stock kernel, it will go away. So... if you flash back to stock like I suggested, it will go away.
Pm me if you need more assistance
creepyncrawly said:
So, what you need to do at this point is flash back to stock 2.3.4 using the instructions in the How to prepare your phone ... thread which is a sticky in the general section of this I777 forum. Since you were stock before, and evidently didn't flash any custom firmware, you should be fine flashing the stock distribution with Odin or Heimdall, or using the Odin one-click downloader.
First enter 3e recovery and perform a wipe data/factory reset, then do the Odin or Heimdall flash. The thread has instructions to clear your personal data as well.
Click to expand...
Click to collapse
Thank you. It worked like a charm. Back to stock. Wonderful. Thank you so much. It wasn't as much a nail-biter as I thought it would be.
Hi guys!
My first thread, so please be gentle...
3 weeks ago I flashed the WanamLite ROM with full wipe. I was unaware to the EMMC brickbug and my phone died when reaching 10% of the installation process.
My phone is now being fixed (JTAG didn't help and thus MB is replaced), which is very expensive.
After reading some XDA threads I realized that I should have taken few steps before flashing the ROM.
When I get my fixed phone (probably today) with probably another "insane EMMC", I wanna make sure that it won't happen again. I've already read the xda threads, but still unsure and afraid that i'll miss some steps or that I didn't fully understand it.
Thus, my question are:
1) When I flashed the WanamLite ROM, I wiped it first, and only then flashed the ROM (using the Recovery). When installation reached to 10% the phone died. This goes in contrary to the XDA EMMC Threads that explains that it should happen only while wiping. How can that be ? Is this a different bug ?
2) If before ***any flasing or wipe*** I change the kernel to SIYAH (which has DISABLED CAP_ERASE) using ODIN, then no matter what kernel/ROM i am flashing after, is it totally safe from this bug ? is this the safest method ?
3) If not, what is the safest method to flash the ROM without having a brickbug (if I have the insane/unknown chip) ?
Thanks !!!
Lior
stlior said:
Hi guys!
My first thread, so please be gentle...
3 weeks ago I flashed the WanamLite ROM with full wipe. I was unaware to the EMMC brickbug and my phone died when reaching 10% of the installation process.
My phone is now being fixed (JTAG didn't help and thus MB is replaced), which is very expensive.
After reading some XDA threads I realized that I should have taken few steps before flashing the ROM.
When I get my fixed phone (probably today) with probably another "insane EMMC", I wanna make sure that it won't happen again. I've already read the xda threads, but still unsure and afraid that i'll miss some steps or that I didn't fully understand it.
Thus, my question are:
1) When I flashed the WanamLite ROM, I wiped it first, and only then flashed the ROM (using the Recovery). When installation reached to 10% the phone died. This goes in contrary to the XDA EMMC Threads that explains that it should happen only while wiping. How can that be ? Is this a different bug ?
2) If before ***any flasing or wipe*** I change the kernel to SIYAH (which has DISABLED CAP_ERASE) using ODIN, then no matter what kernel/ROM i am flashing after, is it totally safe from this bug ? is this the safest method ?
3) If not, what is the safest method to flash the ROM without having a brickbug (if I have the insane/unknown chip) ?
Thanks !!!
Lior
Click to expand...
Click to collapse
the emmc brickbug comes only with Stock android v4.0.4 (should not make any wipes in that Stock 4.0.4 recovery)
so the best way is to flash Siyah kernel v5.0.1 from odin to get rid of the brick bug issue since the emmc_cap_erase thing is disabled in siyah.
then u can use siyah kernel recovery to wipe/flash etc without any problem
in ur early case while installing the 'Wanamalite' rom u had made wipe in the stock 4.0.4 recovery which caused ur phone to brick
So the bottom line is: First root your phone, otherwise you will be screwed no matter what
Donnie Sins said:
So the bottom line is: First root your phone, otherwise you will be screwed no matter what
Click to expand...
Click to collapse
No, as long as u dont do anything silly as the OP did (wiping in stock 4.0.4 recovery) ur not affected by the emmc thing
its only when u want to install a custom rom is when u make it safe to install a brick bug free custom kernel first and then proceed
All I can say is your first bit isnt true.Ive read several threads about the problem and there are several other scenarios that people say have caused the brickbug.
Anyway,you can do what Sun says,or just avoid ever having stock 4.0.4 firmware on your phone.
eg. 4.0.3/gb/jb/custom
Thanks. So...
Sun90 said:
the emmc brickbug comes only with Stock android v4.0.4 (should not make any wipes in that Stock 4.0.4 recovery)
so the best way is to flash Siyah kernel v5.0.1 from odin to get rid of the brick bug issue since the emmc_cap_erase thing is disabled in siyah.
then u can use siyah kernel recovery to wipe/flash etc without any problem
in ur early case while installing the 'Wanamalite' rom u had made wipe in the stock 4.0.4 recovery which caused ur phone to brick
Click to expand...
Click to collapse
In my early case I indeed wiped, but isn't the "death" suppose to happen while wiping and not while installing (after wiping) ? I just want to make sure that this was the bug and I didn't do anything that have caused other bug.
I will do as you adviced (never install 4.0.4 and first install Siyah kernel). But after wiping and flashing new rom with new kernel, does it matters if the kernel is safe or not?
ThAnKs again!
stlior said:
In my early case I indeed wiped, but isn't the "death" suppose to happen while wiping and not while installing (after wiping) ? I just want to make sure that this was the bug and I didn't do anything that have caused other bug.
I will do as you adviced (never install 4.0.4 and first install Siyah kernel). But after wiping and flashing new rom with new kernel, does it matters if the kernel is safe or not?
ThAnKs again!
Click to expand...
Click to collapse
Yes, the Brick Bug appears while you're wiping. I wouldn't know what happened else... But maybe others do.
Only stock 4.0.4 kernels can be affected. Therefore you have to flash a custom kernel first, and then wipe, flash, etc. Custom roms will always be safe, so no need to worry after you've flashed Siyah or any other kernel.
The bottom line is, if you stay away from 4.0.4 & can follow instructions/learn 'how & why' before you do it so you understand why you do certain things a certain way/in a particular order, rather than post in Q&A and say 'Give me the instructions to...<insert name of phone modification here> !!' (like rooting, installing a rom, etc, etc) & someone lists a bunch of steps you don't understand, the only way you're bricking your phone is if you're unlucky, and I've seen maybe 10 people like that out of quite a few thousand on here over the past 18 mths.
Lol,theres always GB.Its the most stable and battery friendly.......thats why I use it.
To MistahBungle
MistahBungle said:
The bottom line is, if you stay away from 4.0.4 & can follow instructions/learn 'how & why' before you do it so you understand why you do certain things a certain way/in a particular order, rather than post in Q&A and say 'Give me the instructions to...<insert name of phone modification here> !!' (like rooting, installing a rom, etc, etc) & someone lists a bunch of steps you don't understand, the only way you're bricking your phone is if you're unlucky, and I've seen maybe 10 people like that out of quite a few thousand on here over the past 18 mths.
Click to expand...
Click to collapse
Well MistahBungle your post is excactly the kind i tired to avoid (sorry for bad english), so please let me defend myself.
I read the xda EMMC threads before I posted here, and my post isn't just "tell me the steps cause i'm too lazy".
I asked a few questions:
The first one i tried to understand if what I have is the standard EMMC brickbug, because as i read in the previous threads, it happens while wiping, and not while flashing as it happend to me (don't want to do the same mistake again).
The second one I asked is if it is safe to flash any kernel after I use the siyah, which is unclear from the other xda posts i read (and "on the way" i wanted to confirm that i indeed have to flash the siyah kernel).
The third question was only to answered if the assumption i made in the previous question is wrong (maybe this and only this was redundant). But you also must remmember
All the above shows that I indeed read the XDA threads and instructions, but didn't get the answers I wanted. In addition, keep in mind I've just spent few hundreds $$$ and lot of time, and I wanna be extra careful so it won't happen again.
I really think that all the rules were kept, even thought this is my first thread here.
Thanks.
To Stlior
stlior said:
-SNIP-
Click to expand...
Click to collapse
You seem to have trouble comprehending. I'll say what I said in my last post a bit more clearly for the slow kids up the back...
If you make sure you know/understand what you're doing before you do it & follow instructions, you won't brick your phone unless you're unlucky. This happens in 0.0001% of cases. You were not one of these cases.
This advice has served many thousands of XDA'ers well in the time I've been here. You broke your phone. Nobody else. All the information you could ever need is here if you're prepared to take the time to find & learn it. Thing is people like you aren't.
The end.
Happy ? (Yes you're now on my ignore list so I won't see any further posts from you).
Donnie Sins said:
Yes, the Brick Bug appears while you're wiping. I wouldn't know what happened else... But maybe others do.
Only stock 4.0.4 kernels can be affected. Therefore you have to flash a custom kernel first, and then wipe, flash, etc. Custom roms will always be safe, so no need to worry after you've flashed Siyah or any other kernel.
Click to expand...
Click to collapse
Thanks. I hope that this indeed was the brickbug and I don't have another hardware fault...
MistahBungle said:
You seem to have trouble comprehending. I'll say what I said in my last post a bit more clearly for the slow kids up the back...
If you make sure you know/understand what you're doing before you do it & follow instructions, you won't brick your phone unless you're unlucky. This happens in 0.0001% of cases. You were not one of these cases.
This advice has served many thousands of XDA'ers well in the time I've been here. You broke your phone. Nobody else. All the information you could ever need is here if you're prepared to take the time to find & learn it. Thing is people like you aren't.
The end.
Happy ? (Yes you're now on my ignore list so I won't see any further posts from you).
Click to expand...
Click to collapse
omg lol :laugh:
how much bitterness!
I explained well why i asked those specific questions, you chose not to listen and instead chose to attack and be bitter. It's ok thought this is kind of your problem. Feel well my friend ! (even if you do not see this).
Basically pal,it doesnt matter what happened in the past or whats going to happen in the future,because you should be removing samsungs stock 4.0.4 firmware.
You should be accepting experts advice rather than irritating them.
We dont know what you understand,but if you ask and get an answer/advice,then try it out.
If you want to improve your knowlege,then read guides and problems other people are having.
Man you guys been busy with this.
By reading about the brickbug you learn one thing:
If you are on 4.0.4 you either get the hell out of there or flash siyah, period.
Questions aroused?
Only if you should use Mobile Odin.
It's pretty clear I guess.
Now, you're saying that you wipped and didn't brick right away, but during flashing. I've seen that before, don't know why it happens.
Si, bottom line:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
/ CWM
Sent from the little guy
gastonw said:
Man you guys been busy with this.
By reading about the brickbug you learn one thing:
If you are on 4.0.4 you either get the hell out of there or flash siyah, period.
Questions aroused?
Only if you should use Mobile Odin.
It's pretty clear I guess.
Now, you're saying that you wipped and didn't brick right away, but during flashing. I've seen that before, don't know why it happens.
Si, bottom line:
View attachment 2017049
/ CWM
Sent from the little guy
Click to expand...
Click to collapse
I second this, stock 4.0.4 was a noob flashers nightmare, the only pure stock I ever had was gb(yeah the one it came with long back), well OP I will give you a few points that will clear some some doubts, it's not the firmware that is risky, using ics 4.0.4 ain't a problem, it's the stock kernel of 4.0.4 that comes with the firmware who is the actual troublemaker, for example if you flashed cm9 stable (yeah ics 4.0.4) with the clockworkmod kernel, you're completely safe, since the custom kernel has the emmc_cap_erase command disabled and you can safely perform any wipe you want. So basically any kernel with the command emmc_cap_erase is dangerous for devices with brickbug effected chip(I am saying this because an old Siyah kernel had this command apparently, v3.xx something) , but no worries every new custom kernels are safe as far as I know.
So to trigger the brickbug there are three conditions,
1.Brickbug effected chip
2.Kernel containing emmc_cap_erase command
3.Performing any form of wipe operation.
If any one of the above condition is not satisfied your device won't get bricked.
Sent from my GT-P6200 using xda app-developers app
king_below_my_lord said:
I second this, stock 4.0.4 was a noob flashers nightmare, the only pure stock I ever had was gb(yeah the one it came with long back), well OP I will give you a few points that will clear some some doubts, it's not the firmware that is risky, using ics 4.0.4 ain't a problem, it's the stock kernel of 4.0.4 that comes with the firmware who is the actual troublemaker, for example if you flashed cm9 stable (yeah ics 4.0.4) with the clockworkmod kernel, you're completely safe, since the custom kernel has the emmc_cap_erase command disabled and you can safely perform any wipe you want. So basically any kernel with the command emmc_cap_erase is dangerous for devices with brickbug effected chip(I am saying this because an old Siyah kernel had this command apparently, v3.xx something) , but no worries every new custom kernels are safe as far as I know.
So to trigger the brickbug there are three conditions,
1.Brickbug effected chip
2.Kernel containing emmc_cap_erase command
3.Performing any form of wipe operation.
If any one of the above condition is not satisfied your device won't get bricked.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
+ back up restore
Sent from the little guy
gastonw said:
+ back up restore
Sent from the little guy
Click to expand...
Click to collapse
Yeah lol, well that's why I said any "form" of wipe operation as a nandroid restore performs certain wipes before restoring.
Sent from my GT-P6200 using xda app-developers app
king_below_my_lord said:
I second this, stock 4.0.4 was a noob flashers nightmare, the only pure stock I ever had was gb(yeah the one it came with long back), well OP I will give you a few points that will clear some some doubts, it's not the firmware that is risky, using ics 4.0.4 ain't a problem, it's the stock kernel of 4.0.4 that comes with the firmware who is the actual troublemaker, for example if you flashed cm9 stable (yeah ics 4.0.4) with the clockworkmod kernel, you're completely safe, since the custom kernel has the emmc_cap_erase command disabled and you can safely perform any wipe you want. So basically any kernel with the command emmc_cap_erase is dangerous for devices with brickbug effected chip(I am saying this because an old Siyah kernel had this command apparently, v3.xx something) , but no worries every new custom kernels are safe as far as I know.
So to trigger the brickbug there are three conditions,
1.Brickbug effected chip
2.Kernel containing emmc_cap_erase command
3.Performing any form of wipe operation.
If any one of the above condition is not satisfied your device won't get bricked.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
Thanks king_below_my_lord,
I see the final conclusion from everyone here is "do not flash (from) 4.0.4 !!!" (got the phone a few days ago, but the display was corrupted so i returned it).
can't wait to get my phone back.
ThAnKs for everyone (even the one who ignores me...) !
Lior