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
Related
Issue: \data partititon become corrupt for no obvious reason.
Manifests itself through: Freezes followed eventually by (endless) reboots
When: Randomly when you install new apps (may be every day as it can happen only every other week/month), or setting up apps (like Twitter, mail, etc)
Temporary solution: Re-flash Samsung FW but lose ALL YOUR DATA. Attention: CWM restore will not fix the problem!
---- Here goes a link to the fabulous mskip's tutorial, you will find here everything you need to get it back up temporarily
I experienced this in 401, 402, 403 and 404, some were expecting better data integrity in 404... I confirm this is not the case
I would not go as far as saying that this is 100% the reason, but it looks like the NAND quality is craaaaaap! There is no external SD card, Android should be able to do a perfect job now at handling info and preserving quality of data.
I will contact Samsung and ask for a refund (if at all possible)... Disgusting thing to put such a piece of s''t on the market without proper testing and call it "flagship/pure Google experience". This is not an isolated issue, it happens to at least half of the people around and the others may have not seen it yet (it all depends on how often you manipulate data on the phone)...
Any advice, I am inetersted, have tried pretty much everything so far and did not solve the problem...
DO YOU HAVE THE SAME ISSUE? Let your voice heard...
DO YOU HAVE THE SAME ISSUE?
Click to expand...
Click to collapse
No. Could it be possible you're overreacting?
David Horn said:
No. Could it be possible you're overreacting?
Click to expand...
Click to collapse
Agree as well ..seems more like rubbish
Sent from my Galaxy Nexus using xda premium
David Horn said:
No. Could it be possible you're overreacting?
Click to expand...
Click to collapse
Thanks David, you're of great help :/
Overreacting? Glad you had a better sample, I bet you would "overreact" as well if you spent 500£ on a piece of junk losing all you data on a daily basis.
But hey, this is not happening to you, right ?
Community means lots of people, some are here to help, others just looking for a social life while trolling on this forum.
Sorry mate, I am trying to get through to the first category...
Umm, sounds like you need a replacement phone.
Deep breath....deep breath.
KWKSLVR said:
Umm, sounds like you need a replacement phone.
Deep breath....deep breath.
Click to expand...
Click to collapse
Right While i'm catching my breath, found another thread pointing to the same issue IMHO (didn't not see it initially):
http://forum.xda-developers.com/showthread.php?t=1490815
Attempting to contact Samsung already...
vulpy said:
Thanks David, you're of great help :/
Overreacting? Glad you had a better sample, I bet you would "overreact" as well if you spent 500£ on a piece of junk losing all you data on a daily basis.
But hey, this is not happening to you, right ?
Community means lots of people, some are here to help, others just looking for a social life while trolling on this forum.
Sorry mate, I am trying to get through to the first category...
Click to expand...
Click to collapse
Your first post came across as a hysterical rant - this is the first I've heard of the problem so it's not affecting many phones, and ultimately Samsung are going to have the occasional dodgy NAND chip. Sounds like you got one.
If you'd had several phones and they'd all exhibited this problem you'd be right to be peeved, but it simply sounds like you've been unlucky and are pissed off about it. Have you even discussed it with Samsung's tech support or taken it back to the shop you bought it from?
And accusing an XDA recognised developer of trolling is not a great start to your time here.
I've not heard of other people having this problem with the Gnex? Who are these other people having this same problem? Maybe speak with them and see if a replacement phone might solve the problem. I really hope you can get this fixed and not give up on such a great platform.
Sent from my Galaxy Nexus using Tapatalk
vulpy said:
This is not an isolated issue, it happens to at least half of the people around and the others may have not seen it yet (it all depends on how often you manipulate data on the phone)...
Click to expand...
Click to collapse
The burden of evidence is on you bro. That is a pretty bold claim.
David Horn said:
...And accusing an XDA recognized developer of trolling is not a great start to your time here.
Click to expand...
Click to collapse
Respect for your dev background (haven't used any of your ROMs yet), in all fairness I'm far less impressed with your communication skills... I must agree though, my message may have come across as too abrupt and you're right again, I am going to sort it out with Samsung...
Did not mean to get people horrified, rather to blow the whistle on a worrying and annoying bug and smth people may consider if they come across or consider a purchase.
For having worked in the mobile comm semiconductors space for years, I know just what sets apart a serious company from a me-too profile. Surprised to see Samsung having this king of issues. Normally they are ironed out easily though SW regression tests and HW stress processes (at least at serious OEMs).
I will let one of the moderators judge if my crime is so serious, your ego will survive, I'm sure I will come back when/if issue solved (or in good progress).
yeah, mine is fine. If it was a widespread problem I would back your corner, but I seems rather isolated. Rather then cause mass hysteria I would say you need to return your handset
Sent from my Galaxy Nexus using XDA
This happened to mine. But only once.
Quite frustrating, as my phone is my alarm clock and it was bootlooping when I needed to go to sleep!
However, a reflash of the 4.0.2 stock images sorted it out, and no problems since. I'm pretty sure I caused it by pulling out the battery at some sensitive point in a reboot or something.
If this happens to you frequently, then you need to exchange your phone.
Also, I think this could be a pretty good resource as opposed to a rant if you put your mind to it. I'm not a developer, but I'm also not a total n00b, and it took me a little while to figure out how to fix the problem, when I had it. I'm sure there are people out there who would appreciate a guide.
In this thread, op is going through that time of the month, when was his own modification back fires in his face, his explosive emotions reek havoc on an online forum.
If you want to see a device with bad nand memory, see the HTC Desire S forum .
Also the reboots and freezes I used to experience on my device were application related. Device hasn't frozen, nor rebooted in about *looks at up time* .. 27 days .
adrynalyne said:
The burden of evidence is on you bro. That is a pretty bold claim.
Click to expand...
Click to collapse
... I was actually referring to a poll in another thread (link in this thread) concluding that half of the people who answered have experienced freezes and reboots... it may be biased somewhat by the fact that people who experienced the issue are more likely to vote than those who didn't... maybe an overstatement from me.
Get the odd reboot (Chrome seems to provoke, strangely) but zero data corruption in 3+ months of heavy use. (4.0.3 AOKP)
Sorry, no endemic fault that I can see here (from reading these forums) and if I were you I'd be looking for a warranty replacement. Refund will depend on your location and supplier and duration of ownership.
Daern
Sent from my Galaxy Nexus using Tapatalk
First I heard about this too. I've flashed tons of roms and mods and constantly installing uninstalling apps.
The GNex has been anything but non-stable. I think I've had to pull the battery once or twice since ownership. Never heard anyone complain about randomly losing all their data... especially not daily. Perhaps on a bad flash in CWM.
Maybe you should look into a super wipe that completely erases everything, deletes the partition tables and recreates everything from scratch. Maybe it'll help but it honestly sounds defective.
Sent from my Galaxy Nexus using xda premium
Thanks Player911... Interesting idea, was thinking as well to do a total wipe and sort of a sector-by-sector reformat, but could not find a way of doing it. Is there any tool that would allow me to do it? Maybe this will isolate bad sectors...
Will check shortly with Samsung folks, thanks mate! (what slows me down is the fact that I'm currently travelling to the US and the guarantee is only European and it's Sunday= hotline is closed in Europe).
daern said:
Get the odd reboot (Chrome seems to provoke, strangely) but zero data corruption in 3+ months of heavy use. (4.0.3 AOKP)
Sorry, no endemic fault that I can see here (from reading these forums) and if I were you I'd be looking for a warranty replacement. Refund will depend on your location and supplier and duration of ownership.
Daern
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Uhh, I don't believe my reboots are due to this. Just saying. That whole thread does not point to your theory as the issue. I'm gonna go ahead and call this myth busted and suggest you go get a replacement because this is just another extremist "my phone is busted but I refuse to get a new one" thread.
Sent from my Galaxy Nexus using xda premium
You've been Samsunged
Sent from my Galaxy Nexus using xda premium
ok this has already been said to be hard bricked. i tried the JTAG and it didnt work because of a damaged EMMC chip. but how does a EMMC chip get damaged??? could it of been from shipping it to texas (place where it got JTAGged)? what about sprint could i lie and get a refurbished one???
btw it was bricked by a flash, so how could it damage the EMMC chip????
thanks
i flashed cm9 with the el26 CWM repacked ( the one in the directions) and i still bricked...
How do you know EMMC chip damaged? Just curious...
jamcar said:
ok this has already been said to be hard bricked. i tried the JTAG and it didnt work because of a damaged EMMC chip. but how does a EMMC chip get damaged??? could it of been from shipping it to texas (place where it got JTAGged)? what about sprint could i lie and get a refurbished one???
btw it was bricked by a flash, so how could it damage the EMMC chip????
thanks
Click to expand...
Click to collapse
It was damaged when you formatted the partitions in cwm....only thing you can do is go to sprint and see if they replace it if not then ship it to Samsung and see if they will do it.....it was not damaged in shipping...it was damaged by u not reading and flashing the way devs have said
The emmc is not really damaged but the partitions are screwed up and no way to fix..
Sent from my Galaxy Nexus using Tapatalk 2
What you do is post in the right section and then buy another god damn phone... I don't mean to be a **** but seriously, there have been sooo many bricking threads and warnings...
Now what? Now you go to Sprint, be honest with them, appeal to their kindness and hope for the best. If that doesn't work then you buy a new one.
I'll supplement the previous comments by this...
Once you get your new phone read up on flashing CM9 to avoid bricking it again. You can start with the sticky at the top of this thread.
No. What you do is, go to Sprint, say you were playing a game, it froze, you pulled the battery and now all it has is a steady blue LED and you don't know why. Do not mention rooting, act like you don't know what rooting is. They can't check if it's rooted anymore without wiping all software so you're fine. If you have warranty, they'll have a replacement in 3 days.
Stay away from CM9. C stands for catastrophic and m for meltdown, the nine is just a nine.
Pp.
" It is said that when He swims, dolphins appear "......... even if its in a pool!
hrffd said:
No. What you do is, go to Sprint, say you were playing a game, it froze, you pulled the battery and now all it has is a steady blue LED and you don't know why. Do not mention rooting, act like you don't know what rooting is. They can't check if it's rooted anymore without wiping all software so you're fine. If you have warranty, they'll have a replacement in 3 days.
Click to expand...
Click to collapse
Yes, by all means let's advise people how to avoid taking personal responsibility for not following instructions and screwing up their phones in the process. That's a surefire way to keep future costs down.
Bricked also, welcome to the club
I to have a bricked device. I now know that this issue resides from a defect that resides in the kernel i believe and really only happens when going from one ICS rom to another. I can't believe that this even happened in the first place. Since i first got the phone when it was released I've been flashing away completely fine up until I flashed the Slim rom and then bam, Nothing. I to sent it in for repair at mobiletechvideos.com but they were not able to fix that eMMC data issue. I've been dealing with this since May 2 now and still don't have a working phone. I"m going to be send back to Samsung for a possible repair but this issue is not because of anything that you did wrong. It's a know issue by know and hopefully in the near future other users won't have to deal this this same **** either. Sounds like a possible patch in the works to prevent this from happening at all on these phones running this particular processor.
Good luck to you
http://www.xda-developers.com/tag/att-samsung-galaxy-s-ii/
Esoteric68 said:
Yes, by all means let's advise people how to avoid taking personal responsibility for not following instructions and screwing up their phones in the process. That's a surefire way to keep future costs down.
Click to expand...
Click to collapse
I'm sorry I have to say this. First let me say that I do believe in taking responsibility for my own actions. But the arguement that people going in a lying to sprint will raise cost is mute. If one was to stop and think about this. This is a company that sells you a plan that includes unlimited data and text and then charges you an additional fee for premium data. They have a whole team at the corporate level that their whole job is to figure out ways to raise cost and pitch it to customers in a way that they will still want to buy. I really do understand what you're saying but believe me. If everyone that ever bricked a phone was honest and paid out the ass for a new phone. Sprint and Samsung would still raise the cost of their services and producst. The only thing that people lying to sprint does is give them an excuse. Maybe I've been in the tech feild too long and am just jaded. Its not just sprint. Its all companies like that. How else do you think they afford to pay their CEO's and underlings 6-7figures aa year.
I believe the issue lies with step 2 in the cm9 install directions.
I never wipe data or factory reset in CWM. Wipe cache or davlik is fine. I always use calks format all to wipe data.
Sent from my SPH-D710 using Tapatalk
jamesey said:
I believe the issue lies with step 2 in the cm9 install directions.
I never wipe data or factory reset in CWM. Wipe cache or davlik is fine. I always use calks format all to wipe data.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I do the same except I use the modified format (no data) zip as well but sounds like its only a matter of time before I get bit for being lazy
hrffd said:
No. What you do is, go to Sprint, say you were playing a game, it froze, you pulled the battery and now all it has is a steady blue LED and you don't know why. Do not mention rooting, act like you don't know what rooting is. They can't check if it's rooted anymore without wiping all software so you're fine. If you have warranty, they'll have a replacement in 3 days.
Click to expand...
Click to collapse
Completely off-topic but your signature is making me want to fire up the GBA emulator and play Pokemon Red/Blue again.
Is this issue only going to get worse when a true ICS recovery is developed? Will the new recoveries gracefully handle GB to ICS and the reverse? I hope so, or it sounds like we're in for a lot of madness.
I've always used Mobile Odin to get back to EL26 and I've never had a problem flip-flopping back and forth to roms. CM9 alpha 4 seems very refined to me and I'm going to stick with it for awhile until MIUI gets its battery issues resolved.
But I say if people want to play in the ICS pool, pay your $5 to get mobile odin pro, and only use the proper EL26 recovery for everything. It's so simple and that's a lot cheaper than a warranty replace or totally new phone.
jamesey said:
I believe the issue lies with step 2 in the cm9 install directions.
I never wipe data or factory reset in CWM. Wipe cache or davlik is fine. I always use calks format all to wipe data.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I believe the issue lies in user error. CM9 instructions are to odin el26cwm which has been safe to wipe/data since it's a Gingerbread kernel. I have installed cm9, aokp, codename, gummy, and mainly lots of nightly builds for cm9. Never had an issue and yes I followed the cm9 instructions. Somewhere along the way I believe people don't realize is that on this phone, every time you flash a rom, it comes with it's own kernel and recovery if there is one packaged. For now all instructions are pretty much the same across the board, for any flashing wiping etc it has to be done on a gingerbread recovery either el26 or el29.
scarmon25 said:
I'm sorry I have to say this. First let me say that I do believe in taking responsibility for my own actions. But the arguement that people going in a lying to sprint will raise cost is mute. If one was to stop and think about this. This is a company that sells you a plan that includes unlimited data and text and then charges you an additional fee for premium data. They have a whole team at the corporate level that their whole job is to figure out ways to raise cost and pitch it to customers in a way that they will still want to buy. I really do understand what you're saying but believe me. If everyone that ever bricked a phone was honest and paid out the ass for a new phone. Sprint and Samsung would still raise the cost of their services and producst. The only thing that people lying to sprint does is give them an excuse. Maybe I've been in the tech feild too long and am just jaded. Its not just sprint. Its all companies like that. How else do you think they afford to pay their CEO's and underlings 6-7figures aa year.
Click to expand...
Click to collapse
You're right, of course the carrier(s) and manufacturer(s) are going to continue to raise costs because they are a business and that's how they stay in business but it's a little naive (or wishful thinking?) to assume these types of events do not affect cost.
So while I agree with you on that point (they raise prices regardless) I still stand firm on people lying to cover their asses when they screw up and ruin their phones.
I can't count the number of these threads I've seen, just since January, despite there being tons of warnings, detailed installation instructions, and other threads like this alerting people what not to do. It leaves me to wonder how many people have read, but not posted, and followed the dishonest advice to obtain new phones at little or no cost.
My argument is that we are enabling an irresponsible mindset that doesn't stop with broken phones. Pointless argument perhaps but just my personal feelings.
Esoteric68 said:
You're right, of course the carrier(s) and manufacturer(s) are going to continue to raise costs because they are a business and that's how they stay in business but it's a little naive (or wishful thinking?) to assume these types of events do not affect cost.
So while I agree with you on that point (they raise prices regardless) I still stand firm on people lying to cover their asses when they screw up and ruin their phones.
I can't count the number of these threads I've seen, just since January, despite there being tons of warnings, detailed installation instructions, and other threads like this alerting people what not to do. It leaves me to wonder how many people have read, but not posted, and followed the dishonest advice to obtain new phones at little or no cost.
My argument is that we are enabling an irresponsible mindset that doesn't stop with broken phones. Pointless argument perhaps but just my personal feelings.
Click to expand...
Click to collapse
I do agree with some of your points, though I think your exaggerating the costs.
They are not going to give him a new phone just a refurbished one. The one he damaged is not beyond repair. It will be sent out and be refurbished for someone else.
I'm sure the cost of tep more then covers Sprint's costs.
PanchoPlanet said:
Stay away from CM9. C stands for catastrophic and m for meltdown, the nine is just a nine.
Pp.
" It is said that when He swims, dolphins appear "......... even if its in a pool!
Click to expand...
Click to collapse
Except that, if you actually follow instructions, it's not either of those things. I've flashed CM9 and AOKP literally dozens of times, following the instructions to the letter, and haven't had a single issue. All you have to do is make sure that when you do wipe data/factory reset, you're doing it on EL26 Stock CWM, not a Rogue repack or whatnot.
People are going to do whatever they do no matter what is said. Some feel they've been screwed over by the carriers and OEM's and this is their opportunity to get back at em. Trust me if I had an opportunity toto stick Comcast with a nice shafting I would. In all honesty though. If you know how to read people. You can go into a store and tell the tech the truth and he will still swap it for 35 bucks or free if you have the TEP. You may have to go to a few stores and talk to the tech for a few minutes to feel em out. Hell I bricked mine and me and the tech talked for a few minutes about the issues happening wwith the phone and what caused it and he had no problem swapping it out. I paid the 35 bucks and was done with it. As I said. I agree with the taking responsibility cause lord knows this nation could use a morals lesson or two. But aether your honest or you lie there is going to be people that seal these bricks out for free phones. Whether its a nice tech doing a solid or a lying customer. Not to mention the thousands Samsung has probably already bricked looking into it. My grip isn't with telling people to be honest. Its with the arguement that alot of people seem to bring that them lying and that alone will be the reason for price hikes. I know that wasn't what was said here it was just one of those deals where it was the post that caused me to respond.
Take care.
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.
I am happy with GB, don't want to upgrade to ICS (I haven't heard of any features I really want, don't want to risk 4G speed downgrade), so I wanted to get rid of the ICS update notification on my non-root E4GT. I played with killing the background processes programmatically, but it didn't help. But the following simple trick seems to have worked like a charm.
1. Make sure you close any current OTA update dialog, e.g., by tapping on Later.
2. Go to the device's Settings, and choose Date and Time.
3. Uncheck Automatic.
4. Tap on "Set date" and choose a date far into the future. Try for several years in the future, but it may not let you. (I had odd behavior when I set for several years in the future--it set it momentarily, but then changed the date back by itself. If it doesn't let you set several years in the future, you can also put it in airplane mode, which makes it more flexible with respect to time setting.)
5. After tapping on "Set", you should immediately get the OTA update dialog again. Tap on "Later". This should make the OTA update dialog come up later than the date you set in step 4, or maybe not at all. (On my device, I can't get it to come up at all, no matter what date I set. )
6. Put a checkmark beside Automatic.
And that's it.
After reboot, you still get a status bar icon (which you can clear with the Clear button), but not the annoying dialog.
I tested this by setting the date to various dates in the future. Prior to the trick, as soon as I moved the clock forward by an hour, it would pop up the dialog. Now it doesn't. I'll have to see if it pops it up if I just wait naturally. But so far so good, despite several test reboots.
or not deal with the status bar icon at all.....
http://forum.xda-developers.com/showthread.php?t=1774282
geeksmurf said:
or not deal with the status bar icon at all.....
http://forum.xda-developers.com/showthread.php?t=1774282
Click to expand...
Click to collapse
Yeah, but I think those methods need root. For instance, without root one can't access /cache. I don't have root (because despite having the phone for a couple of months I haven't found a root method that's both safe and 100% legal; the standard methods involve downloading a modified copy of the firmware from an unofficial source, and that's a likely violation of Samsung's/Sprint's/Google's copyright, though IANAL). My method doesn't need root.
arpruss said:
Yeah, but I think those methods need root. For instance, without root one can't access /cache. I don't have root (because despite having the phone for a couple of months I haven't found a root method that's both safe and 100% legal; the standard methods involve downloading a modified copy of the firmware from an unofficial source, and that's a likely violation of Samsung's/Sprint's/Google's copyright, though IANAL). My method doesn't need root.
Click to expand...
Click to collapse
Your reasons for not rooting are silly. Download the Kernel source from Samsung which they have to give you. Compile a rooted kernel and then flash it to your phone, enjoy the yellow triangle but you were "safe and legal". Taking updates over the air is as unsafe as flashing through ODIN. After your bricking trying OTA because a power fault in your phone caused it to shut off mid update you would take it to a Sprint store that services and likely have your phone flashed through ODIN as long as the bootloader is not corrupted. Though thats the free option that you can do yourself. Warranty exchange costs money Firmware updating any device you own with any method is extremely unsafe. People will always have to live with that.
Samsung must have given Galaxy S2's to the CyanogenMod team asking them to put CM on it because they wanted both Google's Open Source OS to not be on it and for them to not use Samsungs source to develop a rooted and custom os for it
But any method working would be valid for those normal users who don't wish to update. I do laugh at those poor unknowing souls who have this phone as a phone and they have an update crammed down their throat.
I was wondering how people would deal with this and while most would at some point get home and click update if the Super Brick bug had not been fixed how many would end up like Galaxy Note owners.
RainMotorsports said:
Your reasons for not rooting are silly. Download the Kernel source from Samsung which they have to give you. Compile a rooted kernel and then flash it to your phone, enjoy the yellow triangle but you were "safe and legal".
Click to expand...
Click to collapse
Unfortunately, the so-called kernel file (zImage) includes not just the Linux kernel itself, but also the initramfs. While Samsung provides complete Linux kernel source, it does not (as far as I know; I last checked in April) provide source code to all the binaries contained in the initramfs, such as redbend_ua. So if you build from Samsung-provided source, you get a zImage that won't work on the device, unless you add in the initramfs files. This is a loophole in the GPL2, it seems. Now, I guess I could pull these copyright-encumbered files from my device into the initramfs, but I am worried that I'll omit some necessary file and then get a device that won't boot, with no legal way of restoring the stock ROM (other than bringing it in to Sprint service, but Sprint would have the right to refuse service, since it'd be my own fault), since without root I can't run dd to backup the original kernel from the device. Plus I have little experience with initramfs. In any case, this is getting offtopic. Though if someone has a way around my difficulties, or is able to hand-hold me through creating a working initramfs, I would be very, very grateful for a PM.
arpruss said:
Unfortunately, the so-called kernel file (zImage) includes not just the Linux kernel itself, but also the initramfs. While Samsung provides complete Linux kernel source, it does not (as far as I know; I last checked in April) provide source code to all the binaries contained in the initramfs, such as redbend_ua. So if you build from Samsung-provided source, you get a zImage that won't work on the device, unless you add in the initramfs files. This is a loophole in the GPL2, it seems. Now, I guess I could pull these copyright-encumbered files from my device into the initramfs, but I am worried that I'll omit some necessary file and then get a device that won't boot, with no legal way of restoring the stock ROM (other than bringing it in to Sprint service, but Sprint would have the right to refuse service, since it'd be my own fault), since without root I can't run dd to backup the original kernel from the device. Plus I have little experience with initramfs.
Click to expand...
Click to collapse
So your actually afraid of legal action from Sprint or Samsung from downloading the unrooted EG30 tar and ODIN which itself is also a leak? Wow. As an end user about the only thing you have to worry about is your ISP and had you done it a couple months ago I wouldn't have worried. At this point in the US we now have to worry about an ISP falsely accusing you for downloading trial software from its distributor lol.
You will never get the source to the proprietary binaries and most often will not get replacements for them either. Sony apparently was very kind to the CM team giving them a stripped down camera driver for alot of their phones.
Compile the kernel and send it to me I will test it for you. I flash every day. Oh wait thats right you wouldn't want to distribute something I distribute 500 times a day. Nevermind.
RainMotorsports said:
So your actually afraid of legal action from Sprint or Samsung from downloading the unrooted EG30 tar and ODIN which itself is also a leak?
Click to expand...
Click to collapse
I have no fear of legal action here. However, I believe that in normal situations one has a moral duty to obey the law, except when the law is fundamentally unjust (parts of copyright law are stupid, but it's not fundamentally unjust), or something like that. But as I said, this is getting off-topic.
Compile the kernel and send it to me I will test it for you. I flash every day. Oh wait thats right you wouldn't want to distribute something I distribute 500 times a day. Nevermind.
Click to expand...
Click to collapse
If it's one copy and for testing purposes, it might qualify as fair use. I'll think about your kind offer. I'm kind of busy with other projects, though, at the moment.
Back to the original topic: it's a new day, and no update notification. It's looking like my simple method works. Plus, if I change my mind, the update is still there on the device.
Thanks for this simple fix! It worked great.
cg
@ arpruss:
Kudos to this creative yet simple workaround! Brilliant! I also applaud your conviction about right vs wrong & the moral aspect of your conduct. History has shown us that small compromises can often lead to the fall of great people & great nations. There is no shame in trying to do what is right. Good job mate!
Edit: gahhh, fixed your name, sorry!
chconser said:
@ arpuss:
Kudos to this creative yet simple workaround! Brilliant! I also applaud your conviction about right vs wrong & the moral aspect of your conduct. History has shown us that small compromises can often lead to the fall of great people & great nations. There is no shame in trying to do what is right. Good job mate!
Click to expand...
Click to collapse
Thanks!
By the way, I discovered a previously unknown exploit that let me root the phone without downloading any unofficial firmwares. Here's my report on the vulnerabilities that make the exploit possible.
arpruss said:
Thanks!
By the way, I discovered a previously unknown exploit that let me root the phone without downloading any unofficial firmwares. Here's my report on the vulnerabilities that make the exploit possible.
Click to expand...
Click to collapse
While this comment takes away from your op, and since you made it a comment here, i just have one thing to say.
Since your ethical view leaves to in a quandary of what is legal or not, you're simply rehashing an issue that dates back to 2010 and jailbreaking.
Its already been deemed appropriate for electronic devices to be made code available to the owner.
Good for you on ethics, but don't preach legalities.
:edit: And just because your ethical view leaves to question what you are doing, the above quote leaves you in hypocrisy status alone. You sir, found an exploit. Is that not the definition of hacking?
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2
While I await your undoubtedly educated response, i leave this amusing excerpt from Doc Holiday.. "My hypocrisy knows no bounds.."
http://www.youtube.com/watch?v=5v2ZBqjZyjA&feature=youtube_gdata_player
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2
MoHoGalore said:
You sir, found an exploit. Is that not the definition of hacking?
Click to expand...
Click to collapse
There is a DMCA exception for jailbreaking/rooting a phone (it's expiring this year, but hopefully the Library of Congress will renew it; even Apple isn't challenging the exemption this time around!), so as far as I know it is legal to root a phone if one can do so by legal means. My only objection is to downloading modified copyrighted firmwares without the firmware copyright holders' (Samsung and Sprint) permission. I have no objection to rooting one's phone when it can be done without such downloads. There is nothing wrong with hacking when (a) it's done by legally permissible means and (b) one's purposes aren't unethical.
p.s. I passed the vulnerabilities on to Samsung two weeks prior to publicly posting them, in accordance with responsible disclosure procedures.
Please show me, or anyone else here, where we or anyone is violating copyright laws..
The DCMA of 1998, which you are referring, has been appealed and over ruled. That is what gave (gag) Apple users the right. And undoubtedly the rest of the electronic community.
If we, or anyone else here, was violating copyright laws, do you really think XDA would be in existence?
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2
I think this off topic discussion would be better carried on privately. If you want to continue it, email me, please.
You made it public. With your response to Rain. Then again w your response about the "exploit" you found.
I just pointed out the obvious.
It is a good op. And it helps people. But don't sidestep your previous comments.. Ill leave it at this - leave the legal talk to the legal folks.
Good day sir.
:edit: Daddy told me a long time ago "Son, don't run the fence. Sooner or later you'll run into barbwire."
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2
THANKS
Thanks so much for this info!!! The OTA nag dialog was really getting old - just reset my phone back to GB after the ICS - see how fast I can drain your battery life, upgrade. I'm assuming that since you haven't posted otherwise, it is still working for you .
NLM1962 said:
Thanks so much for this info!!! The OTA nag dialog was really getting old - just reset my phone back to GB after the ICS - see how fast I can drain your battery life, upgrade. I'm assuming that since you haven't posted otherwise, it is still working for you .
Click to expand...
Click to collapse
I assume it would be working still, but ever since I got root on the device, I disabled the OTA update component of the Google Framework by using Autostarts, so it's a moot point on my device.
By the way, I get the impression that my wife's E4GT, which came from the store with ICS, has better battery life than my GB-based one. It could just be all the apps I've got installed, of course, but I get the impression that she gets a lot less drain with 4G than I do.
arpruss said:
I assume it would be working still, but ever since I got root on the device, I disabled the OTA update component of the Google Framework by using Autostarts, so it's a moot point on my device.
By the way, I get the impression that my wife's E4GT, which came from the store with ICS, has better battery life than my GB-based one. It could just be all the apps I've got installed, of course, but I get the impression that she gets a lot less drain with 4G than I do.
Click to expand...
Click to collapse
And your battery is how old?
Sent from my SPH-D710 using xda premium
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.