Related
http://www.xda-developers.com/android/hard-brick-bug-on-galaxy-s-ii-and-note-leaked-ics-kernels/
Maybe someone who is a little more savvy in this field could take a look?
Here is a very good article and discussion about the issue:
http://forum.xda-developers.com/showthread.php?t=1644364
Sent from my SGH-T989 using xda premium
this is kinda scary but so far I never had any problem
We don't even have any kernel source. There is a leaked kernel but that didn't cause any brick in our devices. Also note that the article does not mention sgh t989 or sgh 727 and all its sub variants. If this was the case for us you would see many more "[Q] plz halp I haz brick " threads
Sent from my SGH-T989 using XDA
Hey guys. I just came over from the Sprint version of this phone (Epic 4G touch), and while I know that this article dosen't say that it pertains to our device specifically, one of the devs over there got in touch with samsung about the issues. You can see their progress here:
http://forum.xda-developers.com/showthread.php?t=1644364
For those who don't want to read (and I don't blame you if you don't want to, it's heavy stuff and I needed to have it explained to me), long story short: The memory chips (known as the EMMC) in the phone have their own firmware embedded in them, independent of the ROM, kernel, modem, etc. In that firmware, there's a bug that writes a string of zeros to an area of the firmware itself, kind of a self distrusting thing. It's only for certain revisions of the EMMC firmware, and it's only triggered by a specific low-level wipe function that is commonly used in recoveries (I'm not sure which, one of the partition wipes I think), and it for some reason seems to happen more with an ICS based kernel more than in a GB.
Given the nature of EMMC chips and the fact that multiple devices might share these same physical type of EMMC memory chips, it's hard to say how many different kinds of phones and devices might be affected, but it's safer to assume that we might be, rather than to think that we're safe based on this article alone.
There's no official solution as of yet, as far as I know. Samsung has started to patch their 4.x kernels to work around this specific wipe function, thus avoiding triggering the bug, and I think this is because rewriting the EMMC firmware itself is more risky and perhaps harder to do on a wide scale, but again, I'm not sure of their reasons. But, we do know that they're working to find some way around the bugs, and those who built custom kernels also removed/modified that wipe command to work around this bug with success.
Again, I know this doesn't say that it applies to our phones, but because of what was discovered on the Epic 4G touch, I believe that it *may* apply to many, many Samsung phones and devices, and just to be safe, I figure I should share this with you all.
The solution that we were using for time being was: never, ever do any recovery functions from a ICS based kernel/recovery. Always ODIN a GB based kernel/recovery to do what you need to do, then flash the proper ICS back. Kind of tedious, but it worked and prevented me from ever bricking when a LOT of other people were. Food for thought, everyone
TL;DR: You should probably avoid doing anything in an ICS based recovery/kernel on any Samsung device until we hear from them that they've worked out this bug.
kahm said:
Hey guys. I just came over from the Sprint version of this phone (Epic 4G touch), and while I know that this article dosen't say that it pertains to our device specifically, one of the devs over there got in touch with samsung about the issues. You can see their progress here:
http://forum.xda-developers.com/showthread.php?t=1644364
For those who don't want to read (and I don't blame you if you don't want to, it's heavy stuff and I needed to have it explained to me), long story short: The memory chips (known as the EMMC) in the phone have their own firmware embedded in them, independent of the ROM, kernel, modem, etc. In that firmware, there's a bug that writes a string of zeros to an area of the firmware itself, kind of a self distrusting thing. It's only for certain revisions of the EMMC firmware, and it's only triggered by a specific low-level wipe function that is commonly used in recoveries (I'm not sure which, one of the partition wipes I think), and it for some reason seems to happen more with an ICS based kernel more than in a GB.
Given the nature of EMMC chips and the fact that multiple devices might share these same physical type of EMMC memory chips, it's hard to say how many different kinds of phones and devices might be affected, but it's safer to assume that we might be, rather than to think that we're safe based on this article alone.
There's no official solution as of yet, as far as I know. Samsung has started to patch their 4.x kernels to work around this specific wipe function, thus avoiding triggering the bug, and I think this is because rewriting the EMMC firmware itself is more risky and perhaps harder to do on a wide scale, but again, I'm not sure of their reasons. But, we do know that they're working to find some way around the bugs, and those who built custom kernels also removed/modified that wipe command to work around this bug with success.
Again, I know this doesn't say that it applies to our phones, but because of what was discovered on the Epic 4G touch, I believe that it *may* apply to many, many Samsung phones and devices, and just to be safe, I figure I should share this with you all.
The solution that we were using for time being was: never, ever do any recovery functions from a ICS based kernel/recovery. Always ODIN a GB based kernel/recovery to do what you need to do, then flash the proper ICS back. Kind of tedious, but it worked and prevented me from ever bricking when a LOT of other people were. Food for thought, everyone
TL;DR: You should probably avoid doing anything in an ICS based recovery/kernel on any Samsung device until we hear from them that they've worked out this bug.
Click to expand...
Click to collapse
Finally someone with a brain! Thanks for the post
Sent from my SGH-T989 using xda premium
Scary stuff indeed, has anyone confirmed that our devices (T989) is affected by this bug?
Back on the original Epic we used Odin to get the next version. I think it was 2.1 to 2.2 roms. I've always wondered how safe it was to revert to GB by flashing after installing ICS
Sent from my SGH-T989 using xda premium
[Q] plz halp I haz brick
Disregard. Funny how you figure out your issue just seconds after you post and open yourself up to ridicule.
DOH!
mharmon said:
I seem to have hard-bricked my SGH-T989 phone after flashing task650-aokp-Build-36. I don't know if it's a superbrick, but nothing I can do seems to make any difference. The phone does not seem to respond and does not seem to power off, power on or go into download mode. I have swapped with a known good battery and I know that's not the issue. I've tried using a USB jig and that doesn't help. I've contacted Samsung and I should be shipping it to them Monday.
If anyone has any advice, I'm willing to try anything otherwise I'm going to take my lumps and ship my phone off.
Click to expand...
Click to collapse
Pull your battery sd card and sim card out. leave phone sitting with everything pulled for about an hour. put it back together and try again. make sure your battery is charged for sure. it would suck if it was nothing but a dead battery
Sent from my SAMSUNG-SGH-T989 using xda premium
Micronads said:
Pull your battery sd card and sim card out. leave phone sitting with everything pulled for about an hour. put it back together and try again. make sure your battery is charged for sure. it would suck if it was nothing but a dead battery
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Thanks for the quick response. I've tried pulling the battery, USB jig, etc. and can't get it to power on, off or go into download mode. I know what I did wrong. I made a rookie mistake and flashed a ROM meant for my AT&T I777. I feel stupid for bricking my phone.
mharmon said:
Thanks for the quick response. I've tried pulling the battery, USB jig, etc. and can't get it to power on, off or go into download mode. I know what I did wrong. I made a rookie mistake and flashed a ROM meant for my AT&T I777. I feel stupid for bricking my phone.
Click to expand...
Click to collapse
Sounds like you are fizzucked then. Sorry to hear that. That is what sucks about having different phones and flashing stuff. Got to keep track of what is what.
Sent from my Galaxy SII T-mobile using xda premium
Micronads said:
Sounds like you are fizzucked then. Sorry to hear that. That is what sucks about having different phones and flashing stuff. Got to keep track of what is what.
Sent from my Galaxy SII T-mobile using xda premium
Click to expand...
Click to collapse
Yeah sounds dead to me. Send in for warranty. Oh well, stuff happens. Good luck to you!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Id rather risk bricking than rock without 4.04
Sent from my SGH-T989 using xda premium
Nobody has said it is necessary applicable to this device.
jim93 said:
Nobody has said it is necessary applicable to this device.
Click to expand...
Click to collapse
You're right, it doesn't say it's applicable to our device. But it also doesn't say our device is one of the safe GS2 variants. As you can see in my signature, I'm also using 4.0.4. And if you read my post history, I recommend it to everyone. I'm just saying that it hasn't been proven safe yet, but there's also no proof its dangerous either.
Sent from my SGH-T989 using xda premium
ICS has been flashed to these phones probably a half million times by now. If it was causing bricks we would have heard about it.
Sent from the iPhone graveyard.
I've seen like two threads about bricking in this forum in the last two days. How could you say that there's no proof? I'm sorry to say it but I think everyone is being a little too cautiously optimistic. There's no harm in being safe. If you guys actually read about this, you'd realize that its not ICS causing bricks, its any ICS based recovery.
kahm said:
I've seen like two threads about bricking in this forum in the last two days. How could you say that there's no proof? I'm sorry to say it but I think everyone is being a little too cautiously optimistic. There's no harm in being safe. If you guys actually read about this, you'd realize that its not ICS causing bricks, its any ICS based recovery.
Click to expand...
Click to collapse
Also, people should know that the listed phones in the OP are Exynos based and T989, i727/r and i717 are Qualcomm based. This has been discussed in the skyrocket forums and some devs have explained that.
Just my 2 cents.
kahm said:
I've seen like two threads about bricking in this forum in the last two days. How could you say that there's no proof? I'm sorry to say it but I think everyone is being a little too cautiously optimistic. There's no harm in being safe. If you guys actually read about this, you'd realize that its not ICS causing bricks, its any ICS based recovery.
Click to expand...
Click to collapse
The brick in this thread was due to flashing an i777 rom to a t989. Flashing an i777 rom to t989 regardless of OS will brick your phone.
It seems to be all exynos based, but thanks for the heads up, man.
It's an article that I came across.
http://www.xda-developers.com/android/hard-brick-bug-on-galaxy-s-ii-and-note-leaked-ics-kernels/
If this article has been posted, sorry, Mods could delete this.
Sent from my SPH-D710 using Tapatalk 2
Its a non issue in my opinion. If you flash leaks, you know the chances. I flash the leaks and know o could end up with an epic doorstop. Long as its fixed when the official ota comes, it's cool
Sent from my SPH-D710 using Tapatalk 2
Nice article. Very informative. I personally never flash anything while on ICS. But based on that article that might not even be enough. It also gives us an idea that until Samsung/Google has fixed the issue we won'tbe sseeing an OTA updates. At least I would hope they wouldn't OTA an update that is going to brick a **** ton if devices.
I was victim of the superbrick towards the beginning. Whatever it did it really messed that thing up. If JTag can't repair it then it's hosed. Thanks for sharing.
It's faulty firmware from Samsung. Like was said above, until it's fixed, we likely won't see an OTA, and should never flash anything from ICS recovery.
Unlike Wizard Knight, I do see it as an issue, because it's faulty code from Samsung. People are not going to pay attention, or not read the full OP in an ICS thread and brick their phone. The fault here lies on both the person that flashed and on Sammy for their crappy code.
On the other hand, the kernel that Sbrissen is building from international GSII source is confirmed to have this code issue fixed, so we may not have to wait on Sammy to drop source to be able to use recovery again.
blackroseMD1 said:
It's faulty firmware from Samsung. Like was said above, until it's fixed, we likely won't see an OTA, and should never flash anything from ICS recovery.
Unlike Wizard Knight, I do see it as an issue, because it's faulty code from Samsung. People are not going to pay attention, or not read the full OP in an ICS thread and brick their phone. The fault here lies on both the person that flashed and on Sammy for their crappy code.
On the other hand, the kernel that Sbrissen is building from international GSII source is confirmed to have this code issue fixed, so we may not have to wait on Sammy to drop source to be able to use recovery again.
Click to expand...
Click to collapse
Yep Sbrissen and entropy got this fixed. Ive used his 3.0 Kernel and flashed about a billion times to test it lol. Its awesome and brick proof :] I just hope people wait for sbrissens 3.0 to be finished before they starting "borrowing" from it and calling it their own -_-.
Your post is a little misleading at best. This just a rehash of the conversation in two threads, including one in this forum:
http://forum.xda-developers.com/showthread.php?t=1644364
Let's avoid hype on this, OK?
garwynn said:
Your post is a little misleading at best. This just a rehash of the conversation in two threads, including one in this forum:
http://forum.xda-developers.com/showthread.php?t=1644364
Let's avoid hype on this, OK?
Click to expand...
Click to collapse
Avoid hype? This is very interesting. Ive been very very curious as to what was at the root of this since I was around for the first night of ICS leaks and a brick. Hype or not, its wonderful to see that information is being passed around and this is being worked on. Feels like a wonderful thing for the E4GT users.
HaiKaiDo said:
Avoid hype? This is very interesting. Ive been very very curious as to what was at the root of this since I was around for the first night of ICS leaks and a brick. Hype or not, its wonderful to see that information is being passed around and this is being worked on. Feels like a wonderful thing for the E4GT users.
Click to expand...
Click to collapse
My concern is that the information given to us is a big deal... It can easily be thought that someone either was negligent or worse by not addressing this sooner. I would rather see this through and hope the fix comes out soon... And hopefully without a blame game; otherwise people like Mr. Sumrall might not be willing to respond to future inquiries.
Hope that clears up why I mentioned hype.
Sent from my SPH-D710 using XDA
garwynn said:
My concern is that the information given to us is a big deal... It can easily be thought that someone either was negligent or worse by not addressing this sooner. I would rather see this through and hope the fix comes out soon... And hopefully without a blame game; otherwise people like Mr. Sumrall might not be willing to respond to future inquiries.
Hope that clears up why I mentioned hype.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Ahh yeah I got ya. I agree, I would much much rather see a fix and the knowledge that comes with it than seeing people get upset. I for one am happy to see things progressing and have no wish to blame anyone for anything. Even though it was a serious issue, we all take the risk of flashing things that are unknown upon ourselves.
blackroseMD1 said:
The fault here lies on both the person that flashed and on Sammy for their crappy code.
Click to expand...
Click to collapse
You're kidding me, right? Fault of Samsung? We are flashing ROMs that are for internal purposes only. They could introduce an unknown android virus or brick code just to test the response time of their workers, and if we flash it then it is soley our fault. I won't fault Samsung or any other company for our crazy obsessions or need to be on the cutting edge, download their internal projects, and put them on our fully functional devices before they have said to do so.
Now if they release it as official and it bricks the device it is exactly the opposite and 100% their fault, not the flasher.
Yeah. Anything other then official released software is on our heads. If I flash a leak and I brick my phone, which I did, then its my fault. I flashed Sbrissens CM9 back when he first released it. He sent me a test build. I flashed it. I bricked it. It was completely my fault. Wasn't Samsung or Sbrissens. Now if Samsung had officially released that file to the public and said oh yeah this is 100% safe to flash. Then maybe it would have been on them.
LudoGris said:
You're kidding me, right? Fault of Samsung? We are flashing ROMs that are for internal purposes only. They could introduce an unknown android virus or brick code just to test the response time of their workers, and if we flash it then it is soley our fault. I won't fault Samsung or any other company for our crazy obsessions or need to be on the cutting edge, download their internal projects, and put them on our fully functional devices before they have said to do so.
Now if they release it as official and it bricks the device it is exactly the opposite and 100% their fault, not the flasher.
Click to expand...
Click to collapse
If a person flashes a pre-release rom and bricks their phone, yes, it is their fault. However, for Samsung to be as far along as they are in development, and to still have a bug that physically destroys eMMC chips...yes, that is their fault.
The thing is, the coders at Samsung do this for a living, and a bug that's this bad should have been among the first things to be fixed. Considering that it's still present in builds, when the final should be out within the next couple months, is awful.
So yeah, again, it's the fault of the person flashing the rom if they brick their device, but to say that Sammy has no fault at all is ludicrous, because this bug is ridiculous and should have been killed through internal testing a long time ago.
blackroseMD1 said:
If a person flashes a pre-release rom and bricks their phone, yes, it is their fault. However, for Samsung to be as far along as they are in development, and to still have a bug that physically destroys eMMC chips...yes, that is their fault.
The thing is, the coders at Samsung do this for a living, and a bug that's this bad should have been among the first things to be fixed. Considering that it's still present in builds, when the final should be out within the next couple months, is awful.
So yeah, again, it's the fault of the person flashing the rom if they brick their device, but to say that Sammy has no fault at all is ludicrous, because this bug is ridiculous and should have been killed through internal testing a long time ago.
Click to expand...
Click to collapse
How are any of these leaks anything but internal testing? It is absurd to think that these bricks are of any fault to Samsung, they obviously aren't releasing these to us and then saying "Hey, flash this."
Granted, not all of us on here are adults, but for a second, let's be mature and take some ownership for our actions.
The part about it being Samsung's fault, is in regard to the Note. Not our device. They did release software that had the bug, and bricked devices.
But, that's so overblown. Replacing the device is more than enough, in my eyes, for taking responsibility. They are just required to provide a working device.
Any expectation above that, just shows impatience and naivete of the software development cycle.
Sent from my SPH-D710 using Tapatalk 2
Hey guys. I'm just coming to the 4g touch after hard bricking my Fascinate. I'm a little hesitant to flash an ICS rom on this thing after the brick. From what I'm reading here it seems ICS roms on this phone are even less stable than they are on the Fascinate and causing a lot of hard bricks.
Really the only differences I noticed in ICS were the ability to pull down the notifications bar from the lock screen(which I absolutely loved) and the panorama camera option which can be had using Camera ICS. Is there something else I'm missing?
With better battery life, better performance and stability in GB, what brings you to ICS prior to source being released?
iztel said:
Hey guys. I'm just coming to the 4g touch after hard bricking my Fascinate. I'm a little hesitant to flash an ICS rom on this thing after the brick. From what I'm reading here it seems ICS roms on this phone are even less stable than they are on the Fascinate and causing a lot of hard bricks.
Really the only differences I noticed in ICS were the ability to pull down the notifications bar from the lock screen(which I absolutely loved) and the panorama camera option which can be had using Camera ICS. Is there something else I'm missing?
With better battery life, better performance and stability in GB, what brings you to ICS prior to source being released?
Click to expand...
Click to collapse
The risk of bricking has been minimized through the hard work of our Devs and programming community. If you thoroughly read and follow posted installation instructions you aren't likely to brick.
People mainly brick when they get in a rush, or try and take short cuts or simply disregard posted instructions.
There are plenty of enhancements in ICS over GB, I'd suggest people flash a ROM and explore them for yourself. Just read, read, read and ask questions before you ever take any step you are unsure of.
I'll agree with Esoteric68 here. She's spot on about the 'brick' issue. Do you research before you do anything!
As to the why of it? This is xda developers the people here tend to be into tweaking (in the non-meth sense) with technology and like to ride the bleeding edge of technology or squeeze out the most from the old stuff.
I've like the ICS builds for some of the items you've mentioned. Plus I get to stay ahead of the curve, as it where with my technology. Myself I've only had one application that won't support ICS and found another one to supplant it. I like the smoothness and tweaks I can do with ICS.
There are some really great developers here and some awesome ROMs to play with. Just, as already mentioned, read 1st and be careful.
I was scared to flash ICS for a couple months because it wasn't official but I've done my research like everyone says to do. I can't tell you how many times I've flashed ICS roms this past week, not one scare. Just read up and do as the devs say and you'll be good. If you're not sure, ask questions.
I've got the same question as the op roughly. I know that it isn't much of a risk flashing ICS nowadays, but am wondering what in ICS was worth it for people to make the change. I've looked around and don't see too many features really that I don't see in GB so i feel like i'm missing something.
I'm also one who appreciates all the work the devs do to put together these roms for all of us with all the tweaks they put in. Like I mentioned I'm just now waiting to get my 4g touch in the mail tomorrow after bricking my Fascinate. I had been running a number of ICS roms on my Fassy prior to the brick and while I loved playing with them it seemed like the tweaks the devs put into the roms were unrelated to the actual update of the OS. I had been flashing roms for that phone since the early Froyo days so I had thought I had a pretty good idea of what I was doing and always read the proper way to flash things but then one fateful day I tried to flash the latest MIUI coming from MIUI 1.2.9 and ended up with a bootloop, I think I forgot to wipe date/cache. No problem I thought, this has happened before, just ODIN stock and start over. But then something went terribly wrong in ODIN and now I'm left with a phone that won't turn on, won't charge and comes up as "unrecognized" on my pc. If I could just get it into download mode I could save it but I haven't been able to. Now it's got me a little more cautious of what I flash and how often I'll be flashing.
Maybe the devs can answer this since they know more about insides of the OS. Are there things you can modify in ICS that were not possible in GB?
There is a very long and technical thread about the ICS 'super bricking' issue here: http://forum.xda-developers.com/showthread.php?t=1644364
Basically Sammy screwed the pooch with the way ICS kernels make(s) calls to wipe partitions, particularly the EMMC controller.
It's actually a 'hard coded' firmware thing. But since it is firmware, it should be fixable via a firmware flash. It's just we don't really have that code access from Sammy and they seem to be dragging their feet on this.
There are even OTA updates in Europe (France primarily) that are superbricking a load of Galaxy Notes!
sfhub, Entropy512, garwynn and others with way more skills than most are on it. Esoteric68, robertm2011 and a few others took the risk and spent the time to test the workarounds and fixes that were put together. And you'll see from all the activity here that if caution is used you can pretty safely flash away. Since I've had time this week I've actually flashed about 8 different ROMs and restored nandroids too.
Just keep in mind to read the OPs of any ROM and follow their flashing instructions, read the 'how not to brick' stickies etc.
sfhub, chris41g and Agat put together some great 'safe' kernels.
If you're truly worried you can always use sfhub's one-click to get you to a stock FF18 build - kernel, ROM and modem at one shot.
ICS builds are really quite different in the structure to GB. So yes, as a developer, there are a few more things you can do. It's just a matter of figuring out where things are.
Good luck and have fun!
my location services and gps were horrendous with the el29 update, on ICS its soooooo much better, that made it worth the risk to me
I read and read and read and read a little more until I no longer saw it as a risk. It became more of a "why not?" Now that I have experienced ICS I will never go back. I really like the streamlined multitasking. I think that is the prominent feature. :cyclops:
The old adage is: Don't fly higher than your willing to fall.
In this situation, practice techniques, development and ROMs on a device you're not afraid of bricking. Consider it a "tool of the trade". The OLED phones are starting to appear in pawn shops for little money.
I have asurion insurance and am trying to find a reason to use it so I didn't waste my money
Sent from my SPH-D710 using Tapatalk 2
By far my favorite feature is the swipe away notifications. The few times I have been back on GB that was the first thing that bothered me. I can never go back. Especially after tasting AOSP. TouchWiz is trash for me. I suggest you try CM9 or AOKP. Both excellent ROMs with great support right now. There are many more reasons why ICS is superior, depending on preference I suppose, but the bottom line is at this point, with safe recoveries being released, your chance of bricking are I'd say slim provided you follow instructions. I have flashed probably 40 Roms over the last few months. Only time I soft bricked was cause I tried to cowboy up and not follow directions...
Sent from my SPH-D710 using xda premium
I'm confused. Whats the risk?
ICS is dead simple to install if you know how to read.
(genuinely curious seeing as i've had ICS (in different forms) on my E4GT since it was possible. Currently on CM9.)
Yep I echo everyone's advice. Ask questions!
I got the phone a month ago and remember starting a thread asking a ton of questions and I got all the help I needed.
Flashing roms and the terminology (had never heard of Odin) was completely different from the last phone I had, so I am glad I did my homework before taking the plunge.
Sent from my SPH-D710 using XDA
There's no risk...
Sent from my SPH-D710 using Tapatalk 2
It is safe to flash ICS using ODIN and the newer recoveries. FF18 should be safe, I used it a few times, el26 is the recommend kernel/recovery to flash any cwm zip with as far as anything that includes wiping partitions.
Just remember ODIN ODIN ODIN!
Flash ICS based roms at your own risk, stay away from wipe data/factory reset on any ICS rom until it has been confirmed working on new roms. When using other ICS roms and you are not sure, DO NOT FACTORY RESET OR WIPE DATA. USE ODIN TO GET BACK TO A SAFE KERNEL.
Sent from my piece of crap Zio until i get a replacement E4GT using XDA Premium app
What risk? Read the how to's and no so how to's, and the risk gets eliminated.
Sent from my SPH-D710 using xda premium
Watch this thread... Soon there should be no risk at all!!!
http://forum.xda-developers.com/showthread.php?p=28400468
Sent from my SPH-D710 using xda premium
HELP
Can anyone tell me if it is safe to install a build version of ICS to my already flashed epic 4g touch? Any help its greatly appreciated!
Thanks
ICS isn't where you get in trouble. Its going back to gb or doing a factory reset wipe. Use calks wipe all instead of using wipes in an ICS recovery and you will be golden. Read the how not to brick my phone thread if you are really paranoid.
Blu Kuban
Its what all the cool kids are using.
Noob trolled the troll that tried to troll the Noob.
~~~coal686~~~
I am about to buy a new Samsung Galaxy Nexus on/before 25th Jan. (GSM, of course)
I am from India where the phone is not officially released. Hence, I am going to buy it from a well-known local store for $400 USD (22k INR) WITHOUT warranty (as I said, it's not officially released)
I have been lurking the Nexus sub-forums for a few days now.
I would like to know the following this:
What all things should I check as soon I buy the phone from the counter?
What do I do when the phone gets bricked or faces problems like bootlooping? What exactly would cause bricking?
I heard there are a lot of issues with 4.2.1 l(ike SOD). Should I upgrade to 4.2.1 or keep at 4.1.x? I heard t
TheMysteriousOne said:
I am about to buy a new Samsung Galaxy Nexus on/before 25th Jan. (GSM, of course)
I am from India where the phone is not officially released. Hence, I am going to buy it from a well-known local store for $400 USD (22k INR) WITHOUT warranty (as I said, it's not officially released)
I have been lurking the Nexus sub-forums for a few days now.
I would like to know the following this:
What all things should I check as soon I buy the phone from the counter?
What do I do when the phone gets bricked or faces problems like bootlooping? What exactly would cause bricking?
I heard there are a lot of issues with 4.2.1 l(ike SOD). Should I upgrade to 4.2.1 or keep at 4.1.x? I heard t
Click to expand...
Click to collapse
Well, from my point of view:
1) First of all check your screen, if you search the forum there're a couple of topics that explain how to find possible problem of it, then check with an application called eMMC Brickbug checker to see if your phone has a memory chip affected by a problem (resolved by XDA developers, if so, check the forum for the solution).
2) It's almost impossible to brick this phone, but if you fall in a bootloop you can connect your phone to your pc and use toolkit to restore backup, or just shut down the phone pulling the battery and then turn on pressing vol+ vol- and power button, then go to recovery and restore
3) It depends from your phone, in my case i've had SOD only with early trinity kernel, but i think that now every kernel is safe enough to be daily driver. So for me the 4.2.1 worth the try!
[email protected] said:
1) First of all check your screen, if you search the forum there're a couple of topics that explain how to find possible problem of it, then check with an application called eMMC Brickbug checker to see if your phone has a memory chip affected by a problem (resolved by XDA developers, if so, check the forum for the solution).!
Click to expand...
Click to collapse
I could find this:
http://forum.xda-developers.com/showthread.php?t=2093147
https://play.google.com/store/apps/details?id=com.bengigi.screen.diagnostic&hl=en
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester
Is there anything else that you suggest?
[email protected] said:
2) It's almost impossible to brick this phone, but if you fall in a bootloop you can connect your phone to your pc and use toolkit to restore backup, or just shut down the phone pulling the battery and then turn on pressing vol+ vol- and power button, then go to recovery and restore!
Click to expand...
Click to collapse
Alright, I'll search for some tutorials/guides to get information about flashing and restoring.
[email protected] said:
3) It depends from your phone, in my case i've had SOD only with early trinity kernel, but i think that now every kernel is safe enough to be daily driver. So for me the 4.2.1 worth the try!
Click to expand...
Click to collapse
I plan to use PA ROM. Haven't decided about the kernel yet.
1) I think it's enough, however if your screen has some problem you'll notice it as soon as you put your hand on your phone and turn it on... ;D
2) Yes, before doing anything that could harm your device it's better that you understand completely what you're doing.
3) Personally i use cataclysm(ROM) because it's not heavily customized but takes the android experience a leap ahead mantaining the google's look & feel, style and philosophy, and for kernel i use franco (but for the kernel you've to make some test beacuse each device react differently with each kernel)!
Now don't worry no more and enjoy your gnex (when it will arrive)
[email protected] said:
1) I think it's enough, however if your screen has some problem you'll notice it as soon as you put your hand on your phone and turn it on... ;D
2) Yes, before doing anything that could harm your device it's better that you understand completely what you're doing.
3) Personally i use cataclysm(ROM) because it's not heavily customized but takes the android experience a leap ahead mantaining the google's look & feel, style and philosophy, and for kernel i use franco (but for the kernel you've to make some test beacuse each device react differently with each kernel)!
Now don't worry no more and enjoy your gnex (when it will arrive)
Click to expand...
Click to collapse
I am thinking of shifting to CM10.1 because of CyanDelta where I don't have to download the entire nightly.
Any idea if there is similar function in PA or Cataclysm?
What is the procedure I need to follow to update my ROM?
How do I decide which is the best kernel for me? On what factors?
TheMysteriousOne said:
I would like to know the following this:
What all things should I check as soon I buy the phone from the counter?
What do I do when the phone gets bricked or faces problems like bootlooping? What exactly would cause bricking?
I heard there are a lot of issues with 4.2.1 l(ike SOD). Should I upgrade to 4.2.1 or keep at 4.1.x? I heard t
Click to expand...
Click to collapse
1) Quality check and warranty seal.
2) Flashing an incorrect rom, kernel or recovery can cause your phone to brick. You can unbrick all kind of soft bricks with the download mode and Odin, but be careful though. Some people got hard brick, and that's, as far as I know, irrecoverable (Maybe with a jig...)
3) Well, I am with Purity v4.0 and AK Kernel Purity v11 and no SoD. So far so good! If you upgrade to 4.2.1, you can flash another kernel and stay with stock rom if you like it. You just have to look which kernel is the best for your phone.
Good luck in your buy, it's an AWESOME mobile. I didn't know Android could handle soooo well (I comre from a Galaxy Ace )
TheMysteriousOne said:
I am thinking of shifting to CM10.1 because of CyanDelta where I don't have to download the entire nightly.
Any idea if there is similar function in PA or Cataclysm?
What is the procedure I need to follow to update my ROM?
How do I decide which is the best kernel for me? On what factors?
Click to expand...
Click to collapse
PA doesn't have that system but cataclysm yes, the dev produce a stable rom once a month (not always) and then just push cumulatives update (~20MB).
For the kernel it depends on you, if you prefer battery life or performance, smoothness of ui and so on, you have to try and take the one that fit best your parameters!
EDIT: i'm talking of PA before 4.2 came out since after that release i've jumped the ship to cataclysm! Maybe now has a system like this...
1. do i have enough booze at home, because you've gonna spent a lot of time with him
2. read enough before playing bad games
3. rasbean ftw
Can someone tell me what I should look out for to make sure I don't get a phone with performance issues?
Ref:http://forum.xda-developers.com/showthread.php?t=1971852
In the post you've referenced there's a section with the current workaround... that's it... install the application Got Brickbug by chainfire (linked in that thread) to ensure you've a bugged chip or not...
Hi everybody,
I bought a Note 2 in october 2012. I installed the ROM HD Revolution. Until now there was no problem.
Few days ago, my screen has swiched off and there was lot of reds pixels everywere on the screen.
The phone of course was rooted and the garantly not applicable.
So in the samsung shop, i explain that the phone was rooted... The techniciens has puted a new screen thinking that the problem was coming from a screen hardware. This new screen has well worked during 20 mn, after that, same trouble, the screen was killed....
My phone was sent to another tehcniciens ( more specialists and i think, working directly with samsung) in france, who can works on the motherboard. But just before to sent it, the technical personnal has succefuly replace the rom Revolution by another official ROM by Odin. (In order to keep my garantly.....wonderful techniciens)
Today the phone was return to me, with just a new screen. The third screen after mine who was killed in first.
No motherboard trouble, no graphic chipset trouble was fixed, only the HD Revolution ROM who is apparently , and i 'am sure now, has killed the screen
I'am not able to explain why and how, I am not found on the web or another forum the same trouble.
Somebody know what's happened?
thanks
You might want to contact the developer, but I doubt the rom was the issue.
Sent from my SAMSUNG-SGH-I317 using xda premium
silentecho13 said:
You might want to contact the developer, but I doubt the rom was the issue.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I'am sure, very sure that the problem on the screen is due to the ROM Revolution, otherwise explain me why the third screen has no trouble after changing only the ROM with the lastest samsung ROM?
The official technicians do try to convince you that a custom ROM is the cause of your problem. Not making a judgement on whether this was what happened in your case, but just my personal opinion.
I am in India, where anyway Sammy tries to avoid taking responsibility however possible. One of my friend had sds on his s3, and the guys from Samsung tried to refuse him warranty on the basis that they believed he had a custom firmware. They were adamant on this even on his pointing out that thousands had had this even on the stock ROM, and thus could not be in any way related to flashing a custom firmware. Only when he threatened them with legal action (as they couldn't prove it was flashed anyway) did they finally took it in for repairs.
My advice is, check out the devs thread for the ROM, if its a genuine problem then it is sure to be mentioned by someone there.
Sent from my GT-N7100.
Those who help noobs go to heaven. True story.
SacGuru said:
The official technicians do try to convince you that a custom ROM is the cause of your problem. Not making a judgement on whether this was what happened in your case, but just my personal opinion.
I am in India, where anyway Sammy tries to avoid taking responsibility however possible. One of my friend had sds on his s3, and the guys from Samsung tried to refuse him warranty on the basis that they believed he had a custom firmware. They were adamant on this even on his pointing out that thousands had had this even on the stock ROM, and thus could not be in any way related to flashing a custom firmware. Only when he threatened them with legal action (as they couldn't prove it was flashed anyway) did they finally took it in for repairs.
My advice is, check out the devs thread for the ROM, if its a genuine problem then it is sure to be mentioned by someone there.
Sent from my GT-N7100.
Those who help noobs go to heaven. True story.
Click to expand...
Click to collapse
I understand but, the first technicians i saw works for samsung, it's not samsung technicians, and these technicians has tried to change my ROM revolution in order to preserve my warrantly. Unfortunatly we have decided together that in first my phone will not send to Paris at Samsung.
The local technicians has received a new screen, and it was impossible for them to change the rom, anyway they has changed my screen by the new, after 20 mn the new screen has crashed...
We decided to send unfortuntly the phone to paris because we has think that the trouble was the motherbord or the graphic chipset. I was very afraid concerning my warrantly. But the local technicians has success just before to send the phone to change the revolution rom to a samsung in order to keep my warrantly. Otherwise the technicians of Paris..
At paris they has changed for the third time just the screen, anything else , and the note 2 is working perfectly....
I have the report by paper of all investigations makes... I am not a lie.. I cannot saw another reason of this trouble....
aquasirius said:
I understand but, the first technicians i saw works for samsung, it's not samsung technicians, and these technicians has tried to change my ROM revolution in order to preserve my warrantly. Unfortunatly we have decided together that in first my phone will not send to Paris at Samsung.
The local technicians has received a new screen, and it was impossible for them to change the rom, anyway they has changed my screen by the new, after 20 mn the new screen has crashed...
We decided to send unfortuntly the phone to paris because we has think that the trouble was the motherbord or the graphic chipset. I was very afraid concerning my warrantly. But the local technicians has success just before to send the phone to change the revolution rom to a samsung in order to keep my warrantly. Otherwise the technicians of Paris..
At paris they has changed for the third time just the screen, anything else , and the note 2 is working perfectly....
I have the report by paper of all investigations makes... I am not a lie.. I cannot saw another reason of this trouble....
Click to expand...
Click to collapse
I suggest you verify on the forum thread and contact the dev. I highly doubt its the rom. I imagine for what you say to be possibly its not rom related but kernel and would require some sort of color adjustment hack of sorts, even then I highly doubt it as more users would have experienced the same. As for your proof from samsung means nothing. I've sent devices and computers out to warranty and the document says one thing but when I take it apart I see things where changed that do not reflect what the work order says. Not saying its the case just saying take it with a grain of salt.
I can't seem to find the rom your talking about.
prbassplayer said:
I suggest you verify on the forum thread and contact the dev. I highly doubt its the rom. I imagine for what you say to be possibly its not rom related but kernel and would require some sort of color adjustment hack of sorts, even then I highly doubt it as more users would have experienced the same. As for your proof from samsung means nothing. I've sent devices and computers out to warranty and the document says one thing but when I take it apart I see things where changed that do not reflect what the work order says. Not saying its the case just saying take it with a grain of salt.
I can't seem to find the rom your talking about.
Click to expand...
Click to collapse
It was the REVOLUTION HD Rom.
You think that the Samsung technicians when they changed the screen after the other first technicians has not been honnest?
It's incredible, i don't believe in this idea... I cannot see the interest... But if you are talking about the kernel maybe it yes...
It's a crazy story...
HD Revolution....? wait.. isnt it for a international version of Note 2?
No wonder why your phone is acting up. Flashing almost non compatible ROM on your device doesnt give you rights to discredit Dev.
I believe he is talking about this rom that is not in the att section.
http://forum.xda-developers.com/showthread.php?t=1925402
OP, when flashing did you happen to flash anything else such as that gpu rendering thing they have on that page? Also, any extreme overclocking or anything?
Sent from the Bacon Pope's Galaxy Note 2
Well then if that is the rom there is your problem. Your lucky Note II in general share the same SoC else you would have hard bricked. I suggest you do your research correctly before saying something broke your device. In the end its your responsability to know what you are flashing and even if said rom/kernel/mod does break your device its your fault, you flashed it not the developer. Its a risk we all take when modifying our devices.
cwhitney24 said:
I believe he is talking about this rom that is not in the att section.
http://forum.xda-developers.com/showthread.php?t=1925402
OP, when flashing did you happen to flash anything else such as that gpu rendering thing they have on that page? Also, any extreme overclocking or anything?
Sent from the Bacon Pope's Galaxy Note 2
Click to expand...
Click to collapse
I use the recovery mode after have put the zip's ROM on my SD card.
And i never use the o/c
I 'am sure that the trouble has been caused by the Kernel or the ROM... I don't remember what was the kernel... i thinking...
prbassplayer said:
Well then if that is the rom there is your problem. Your lucky Note II in general share the same SoC else you would have hard bricked. I suggest you do your research correctly before saying something broke your device. In the end its your responsability to know what you are flashing and even if said rom/kernel/mod does break your device its your fault, you flashed it not the developer. Its a risk we all take when modifying our devices.
Click to expand...
Click to collapse
I know that, but on the french forum we are several with this ROM, i'am looking for the same trouble in France: nothing...
I'am wondering what's happened and i 'am not here to cry but to exlpain you this trouble and i 'am trying to have an elaborate conversation in order to find the origin, I find it normal beetween enthusiast....
aquasirius said:
I know that, but on the french forum we are several with this ROM, i'am looking for the same trouble in France: nothing...
I'am wondering what's happened and i 'am not here to cry but to exlpain you this trouble and i 'am trying to have an elaborate conversation in order to find the origin, I find it normal beetween enthusiast....
Click to expand...
Click to collapse
Well you are disproving yourself. If no other LTE variant on that rom has had similar problems then its not the rom/kernel/mod. It was a fluke of bad hardware with lazy techs (don't want to generalize its easier to blame it on an external source than actually debugging). Second your arguments are null in the end becaus:
mike1986. said:
No mate, LTE version is not supported.
Click to expand...
Click to collapse
That includes I7105, I317[M] and T889[V]. It might work, but probably not 100% and the developer simply offers no support for it.
aquasirius said:
I understand but, the first technicians i saw works for samsung, it's not samsung technicians, and these technicians has tried to change my ROM revolution in order to preserve my warrantly. Unfortunatly we have decided together that in first my phone will not send to Paris at Samsung.
The local technicians has received a new screen, and it was impossible for them to change the rom, anyway they has changed my screen by the new, after 20 mn the new screen has crashed...
We decided to send unfortuntly the phone to paris because we has think that the trouble was the motherbord or the graphic chipset. I was very afraid concerning my warrantly. But the local technicians has success just before to send the phone to change the revolution rom to a samsung in order to keep my warrantly. Otherwise the technicians of Paris..
At paris they has changed for the third time just the screen, anything else , and the note 2 is working perfectly....
I have the report by paper of all investigations makes... I am not a lie.. I cannot saw another reason of this trouble....
Click to expand...
Click to collapse
Relax man, I did not think you were lying, neither did I accuse you of it, I merely asked you to, and personally believe,that the developers on this forum (who are people like you and me) are anyday more trustworthy than repair men who are from samsung or freelancers (read people bent on profiting from me screwing up my cellphone). Thus I asked you to visit the developers thread and look for comments about the issues you were facing, that is what I would've done.
Apparently you flashed a ROM which was not meant for your particular model. Whether that is true or not, I am sorry for all the trouble you had to go through with the engineers and all. I hope your note 2 functions great from now on.
Je vous présente mes meilleurs vœux pour l'année 2013
Sent from my GT-N7100.
Those who help noobs go to heaven. True story.
prbassplayer said:
Well you are disproving yourself. If no other LTE variant on that rom has had similar problems then its not the rom/kernel/mod. It was a fluke of bad hardware with lazy techs (don't want to generalize its easier to blame it on an external source than actually debugging). Second your arguments are null in the end becaus:
That includes I7105, I317[M] and T889[V]. It might work, but probably not 100% and the developer simply offers no support for it.
Click to expand...
Click to collapse
It was the REVOLUTION HD 4, installed in november, not the 8 or the 9
I used the ROM perfectly adapted for my note 2
Now my note is working without problem with the last samsung rom with 4.1.2 android version.
Nothing has been changed into my phone (hardware etc...) just a new ROM...
And never else was happened on my phone before the trouble.
aquasirius said:
It was the REVOLUTION HD 4, installed in november, not the 8 or the 9
I used the ROM perfectly adapted for my note 2
Now my note is working without problem with the last samsung rom with 4.1.2 android version.
Nothing has been changed into my phone (hardware etc...) just a new ROM...
And never else was happened on my phone before the trouble.
Click to expand...
Click to collapse
Man you said your on a 3rd screen so don't say hardware hasn't changed. This is not counting for anything that changed when you shipped out. In the end it doesn't matter if it was a November rom, or January rom its based on the N7100 firmware not N7105 therefor although it might work probably won't work 100%. You are so caught up that it has to be the rom that you are ignoring key points in your argument. It is more likely to be a hardware problem than software. I'm not saying it wasn't the rom/kernel combination because its possible, who knows, however its a rom based on Sammy firmware that isn't made for your device. Plain and simple.
Cheers
prbassplayer said:
Man you said your on a 3rd screen so don't say hardware hasn't changed. This is not counting for anything that changed when you shipped out. In the end it doesn't matter if it was a November rom, or January rom its based on the N7100 firmware not N7105 therefor although it might work probably won't work 100%. You are so caught up that it has to be the rom that you are ignoring key points in your argument. It is more likely to be a hardware problem than software. I'm not saying it wasn't the rom/kernel combination because its possible, who knows, however its a rom based on Sammy firmware that isn't made for your device. Plain and simple.
Cheers
Click to expand...
Click to collapse
I mean hardware (motherboard, chipset,....etc) of course screens are hardware.
And I have 7100 and the ROM I used was for the 7100.
The ROM has broken something on my phone, i don't know what, maybe my english is too bad and i'am not able to do understand my story with the corrects words
I'am not a noob to choose the wrong ROM for my note 2...
we thought that the problem has came from a voltage problem beetween the screen and the GPU or the chipset...
Without any else action from me (no o/c, no brutality) i cannot see anything else....
I think several people have made good points though who knows, it's also possible some part of your os got corrupted and it killed the screens. I've seen a lot of wierd stuff happen with computers over the years. I repair phones, desktops and laptops myself and I continue to see new problems. Some of it I figure out, some I never do.
Another explanation that occurs to me - a transitory short that fried the screens. Did you drop or jar the phone? Spill fluid? Have high or extremes of temp or humidity ? **** happens. Intermitant problems are the absolute worst to track down. If it is something lurking in the hardware and they didn't fix it completely, it may say hello to you again! Problem devices often stay problem devices even after a number of "final" repairs that work for a while. That's why if something like that happened to me, I'd be happier with a replacement device.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Dumbo53 said:
I think several people have made good points though who knows, it's also possible some part of your os got corrupted and it killed the screens. I've seen a lot of wierd stuff happen with computers over the years. I repair phones, desktops and laptops myself and I continue to see new problems. Some of it I figure out, some I never do.
Another explanation that occurs to me - a transitory short that fried the screens. Did you drop or jar the phone? Spill fluid? Have high or extremes of temp or humidity ? **** happens. Intermitant problems are the absolute worst to track down. If it is something lurking in the hardware and they didn't fix it completely, it may say hello to you again! Problem devices often stay problem devices even after a number of "final" repairs that work for a while. That's why if something like that happened to me, I'd be happier with a replacement device.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Maybe you right, and the phone has been exposed every time in good condition, and never droped or jared. I will see with the time if it was a another hardware problem.
I think actually the association ROM/kernel has revealed an intrinseq hardware problem on my phone and maybe later even with a samsung rom the problem should be appear again....
aquasirius said:
I mean hardware (motherboard, chipset,....etc) of course screens are hardware.
And I have 7100 and the ROM I used was for the 7100.
The ROM has broken something on my phone, i don't know what, maybe my english is too bad and i'am not able to do understand my story with the corrects words
I'am not a noob to choose the wrong ROM for my note 2...
we thought that the problem has came from a voltage problem beetween the screen and the GPU or the chipset...
Without any else action from me (no o/c, no brutality) i cannot see anything else....
Click to expand...
Click to collapse
Wait.....Your Note 2 is an N7100? Then why did you come to an i317 forum to complain about a ROM somehow breaking your screen?
If you really think you have a legitimate concern that a ROM may have damaged your phone in some way, contact the developer. Maybe it has happened before. Maybe the developer can make changes to prevent it from happening to others. What you probably shouldn't do is to make claims that a ROM damaged your phone on a forum for a different model of phone.