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.
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
So I bought my gf a one v and she loves it. One month after using it (stock, unrooted) it just went dead. Doesn't charge and doesn't get into bootloader (but not the QHSUSB_DLOAD and Blank Screen issue). Guy at repair told me that this was an issue with the ICS kernel causing a hard brick. Now, I naturally sent phone for repair since it is a warranty case. So far so good, lets just hope they get it done fast.
My question is though: should I root device and flash another ROM with presumably no such issues so I can avoid a future brick? I mean, I'm using a rooted desire and have no issues for over 2 years, now just didn't want to mess with the new phone of my gf and thought 'hey, lets keep it stock'... But the thought that it would die again after having it repaired is really discouraging. My gf is kind of frustraded and I don't want this to happen again. But are there such issues with custom ROMs for the One V? Like I said, I'm using the good old desire and don't know much about the one v, so I would really apreciate if you can tell me - because if such an issue is possible on custom roms, there is no point to bother flashing and voiding warranty.
Thanks for your time guys!
Well at the moment we have only modified stock ROM for this device and one custom kernel (in beta state) which is still an ICS kernel.
However you''ll never know whether this happens again or not. But one thing you can know for sure is that if you unlock the bootloader and install a custom kernel and ROM and it happens again then your are screwed because you lost your warranty.
Maybe you should wait a bit for some stable custom rom. Because an unstable and buggy ROM would make your gf even more frustrated and andgry
Oh well, thanks for the insight my friend..So, If I got this right, if I root and flash one of the current roms and it bricks again, I will still not be able to acces bootloader? And is this really a kernel issue with ICS? I'm willing to even flash a GB rom, if it is possible, in order to avoid this...gf won't mind for sure lol, if this delivers a stable phone in the future
P.S. Does this even happen with other ICS roms/on other stock ICS devices? Or did HTC just screw up on this one? I can understand a phone bricking when changing hboots or other tinkering, but just dieing like that is pretty damn stupid. And from what I read it happens to quite a few other one v users...Hope noone of you guys gets to experience this crap
falconyx said:
Oh well, thanks for the insight my friend..So, If I got this right, if I root and flash one of the current roms and it bricks again, I will still not be able to acces bootloader? And is this really a kernel issue with ICS? I'm willing to even flash a GB rom, if it is possible, in order to avoid this...gf won't mind for sure lol, if this delivers a stable phone in the future
P.S. Does this even happen with other ICS roms/on other stock ICS devices? Or did HTC just screw up on this one? I can understand a phone bricking when changing hboots or other tinkering, but just dieing like that is pretty damn stupid. And from what I read it happens to quite a few other one v users...Hope noone of you guys gets to experience this crap
Click to expand...
Click to collapse
1. In no other galaxy, no other planet... IT IS NOT A KERNEL FAULT! it may at well be a piece of poorly made phone. you should get another one from the warranty. I can 100% say that you will not have any problems. The kernel doesn't suddenly causes hard brick to your phone. If it does, do you know how many phones running ICS are there? Or One V's...
I have flashed alpha/beta/final kernels/roms for millions of times, no problems whatsoever.
in no way this is a kernel/soft problem. more likely the flash drive from your gf's phone, died!
1ceb0x said:
1. In no other galaxy, no other planet... IT IS NOT A KERNEL FAULT! it may at well be a piece of poorly made phone. you should get another one from the warranty. I can 100% say that you will not have any problems. The kernel doesn't suddenly causes hard brick to your phone. If it does, do you know how many phones running ICS are there? Or One V's...
I have flashed alpha/beta/final kernels/roms for millions of times, no problems whatsoever.
in no way this is a kernel/soft problem. more likely the flash drive from your gf's phone, died!
Click to expand...
Click to collapse
Thx dude, I was sort of wondering how this could really be a kernel problem, since the guy over at the repair told me so - 'Its a kernel issue with ICS'... well, I hope he was really wrong and the device we receive (hopefully soon) will be proper
falconyx said:
Thx dude, I was sort of wondering how this could really be a kernel problem, since the guy over at the repair told me so - 'Its a kernel issue with ICS'... well, I hope he was really wrong and the device we receive (hopefully soon) will be proper
Click to expand...
Click to collapse
That guy should really make his homework. In no way a kernel can brick the phone. If this was true, the phone will not boot and work for weeks in the first place. Its not like the kernel has a "time-bomb" inside and it triggers when it is set.
As I said, it is a phone problem, something hardware has failed.
Hopefully it will be fixed for you gf and she will not have any problems in the future.
It happens in India too
My htc one v got bricked suddenly while using it. Forums at internet says it happens if battery charge goes below certain limit. Mine it went down to 24%
It happened to me when my battery level was 14%. now I have to pay 200$ for repairs. (because I live in Iran.)
HTC ONE V dead
falconyx said:
Oh well, thanks for the insight my friend..So, If I got this right, if I root and flash one of the current roms and it bricks again, I will still not be able to acces bootloader? And is this really a kernel issue with ICS? I'm willing to even flash a GB rom, if it is possible, in order to avoid this...gf won't mind for sure lol, if this delivers a stable phone in the future
P.S. Does this even happen with other ICS roms/on other stock ICS devices? Or did HTC just screw up on this one? I can understand a phone bricking when changing hboots or other tinkering, but just dieing like that is pretty damn stupid. And from what I read it happens to quite a few other one v users...Hope noone of you guys gets to experience this crap
Click to expand...
Click to collapse
Hi My HTC one V just died , I didn't know how it was happened . 10 minutes before I made I call and just after sometime It stopped working .
Even it is not charging at all, mobile is out of warranty. don't really know what to do ..
Any suggestion would be appreciated .
Regards
Manoj
Hi,
I've got my GN for about 2 years now. It always runned fine. I use it essentially to make calls, mails, some european "anti-cop" app called "icoyote", spotify and that's it
Everything stock, full google official, no cracked bull**** apps or whatever.
Ok so now for about 1 month it became less and less stable. It literally happened from one day to another. I guarantee i didn't add/change or remove anything.
Main issues are : spotify crashes many times (~20 to 50) a day and 50% of the time the GPS fix fails to go trough, but a simple reboot and it work's instantly.
So I tought I should make a full factory reset. I did that and the issues I was experiencing remained the same.
Now comes the 1million $ question : how the heck can something stop to work from one day to another ? If it was some *unpredicted*, classic hardware failure, a simple reboot would definitely not solve it, for sure.
Leading to think it has to be software related..OK, so a factory reset should solve : it doesn't neither.
Why are those apps crashing even in a very stock/factory config? I even did skip this google restore profile bull**** to be sure i'm workng in a perfect clean state.
The only logic conclusion is that there must be some kind of hard coded counter which reached the end and is now triggering randomly something, *i don't know based on what, or activated how* making this **** happen
It's very very very frustrating because it was working like a charm those past 2 years and i thought it was a good investment. I was obviously wrong, another death scheduled device.
Now with the 4.3, I got the feeling it becomes even worse. Today, I had to reboot 4 times to get a gps fix (working 100% of the time just after the reboot) and it was a hassle to get trough 2 songs without being cut off in the middle of it.
FU samsung
But you only tried to flash 4.3. It's like giving a patient only 1 medicine and when that not works declare him dead. There maybe other ways to revive your phone..
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
But you only tried to flash 4.3
Click to expand...
Click to collapse
when did i say that ? i'm done by years flashing a tool I use to work with. i'm not using it as a toy.
i received the update ota
there's nothing left to try, since my last basic test's where made in a official google factory default situation on a google phone
it's just stock u see? everything else i could try from this point would lead to a non-default situation making every further considerations totally pointless
Well, if i'm right, the so called "crash-routine" would *maybe* not be present in a custom rom, but, again, it worked before and has to work the same way now.
I refuse to use any other workarounds than factory resetting it and, since i already did that a few times, i'm done
i'm not awaiting some kind of help here. i'm just exposing my case and the frustration i'm feeling since samsung nicely dry-fcked me ^^
Don't know why you're acting up for no reason.
It doesn't take a genius to understand and figure out that applications designed and updated for 4.2.2 will most likely not work on 4.3 until the devs update it to work on 4.3. Which, from my experience, doesn't take long at all. That's probably one of the solutions to your few problems.
Way to take things a little too far and throw a tantrum rather than seeking help.
Also, if you have no intentions of seeking a fix then you didn't need to post anything at all.
You're not waiting around here for help? Well, I'm not going to offer help to someone with that kind of attitude.
Peace out you won't be missed.
BTW, there's nothing left to try? LOL
There's about 7 things left to try and one of them would have definitely worked 100%. Figure it out on your own since you know everything.
Read this. It's called Planned Obsolescence. Manufactures purposely make devices with limited lifespan in order to upgrade to their next new device.
http://en.m.wikipedia.org/wiki/Planned_obsolescence
Sent from my Galaxy Nexus using Tapatalk 2
Fastboot, Odin, omap.. All stock..
Sent from my Galaxy Nexus using XDA Premium HD app
johno86 said:
Don't know why you're acting up for no reason.
It doesn't take a genius to understand and figure out that applications designed and updated for 4.2.2 will most likely not work on 4.3 until the devs update it to work on 4.3. Which, from my experience, doesn't take long at all. That's probably one of the solutions to your few problems.
Way to take things a little too far and throw a tantrum rather than seeking help.
Also, if you have no intentions of seeking a fix then you didn't need to post anything at all.
You're not waiting around here for help? Well, I'm not going to offer help to someone with that kind of attitude.
Peace out you won't be missed.
BTW, there's nothing left to try? LOL
There's about 7 things left to try and one of them would have definitely worked 100%. Figure it out on your own since you know everything.
Click to expand...
Click to collapse
I ain't here to help either, i just couldn't agree more with what he said above... and its 2013, everyone knows that every electronic sh*t comes with a limited life span, if you didnt know that until now, i'm not sure where you been living..
Peace \m/.
Try wiping your SD card
I was so excited to get a different phone. I had been contending with the insufferable Galaxy Note 2 for 9 months. I really believed that getting the LG Optimus G Pro would be great.
Now I come to find out that there is this locked bootloader? yes before you even start typing: I already know about Freegee. I put it on my phone, it did its work. I have CWM on my phone. I cannot install a different rom. It aborts every time.
And nobody here can help. Its not like you don't see my posts. You see them. You just see them and decide to go on to something more interesting figuring that someone else will help the poor guy.
Hey guess what. I took programming in college. Only one course in VB but I did take it. And I've put up several websites back in the day. ("back in the day is a United States colloquialism")
My point is, even though I have a bit of experience with computers (linux distros, html, visual basic) I still can't figure out the quagmire that is Android.
Once the iPhone 6 comes out, I really have no reason to stick with Android anymore. I mean, if rooting and rom-ing the phone is more boringly laborious than jailbreaking, then what is the point of Android?
For example, lets say I do clear the hurdle and then flash a rom so I can get decent sound? THEN my wifi won't work. Or Some other crucial functionality will be fubar-ed. Okay okay... you say you have a fix for that? Well when its all said and done, the time/energy costs just aren't worth it, now is it?
0 #!*! Given ?
That's interesting because I never took any classes and have never had a problem rooting or doing Roms on any android phone. Sorry your experience has been bad but my questions have always been answered by somebody in the related thread. I would try asking again in the ROM's thread to see what is happening.
Sent from my LG-E980 using XDA Premium 4 mobile app
G pro is the note 2 killer...... Just follow instructions of any op to the T and you should be fine.... It's simple lol
2SHAYNEZ
I agree. I don't post often but I really do hate Apple. Android kicks Apple's you know what many times over. Talk about being locked down.... If I've ever had a problem with a Rom someone has always helped me figure it out. Sorry about your problems though.
sent from my lgog pro. I just had to go bigger.
@Perry2547,
If CWM doesn't work then try TWRP, even i had problems with CWM.either install it from freegee or install this
copy this to sd card and then flash it in CWM and reboot.
I believe the OP just wanted to start a thread...
So you all may ignore him
Thanks @sukesh.
I tried the twrp you linked to and now my phone will let me flash.
Unfortunately, Camera has stopped.
Close thread please.
2SHAYNEZ
I don't even remember how I rooted this phone... I know I found a thread that had comprehensive instructions, links, etc and believe it was as simple as downloading/extracting an executable file on my PC and plugging the phone into USB at the right moment. I've flashed CM, stock 4.4, Slim and always find my way back to stock 4.1.2, modded to my liking. If you can't flash something in a custom recovery, it's likely your phone is protecting you from failure to completely read/follow a prior mod or a prerequisite to the ROM/Mod you wish to flash.
Sent from my LG E980 via Tapatalk Pro (and stupid-fast LTE)
But seriously y'all, I'm just glad I have another two hours if battery life left. That means I will vhave to recharge this phone only 3 more times today.
Unfortunately, Camera has stopped.
I too just got new lg ogp phone. Been trying to customize it to my liking for the past 3 days and night. All I can say about android is it is not for everybody. Sure, you can use it as it is when you first get it as a stock device, and it will work as advertise. But there is a reason that you try modifing it regardless of breaking the manufacturer's warranty (yes, once you start rooting it, you violate the agreement.) You have personality of the kind that thinks you can fix anything by yourself. Nothing wrong with that, I'm in same personality group too, many Android owners are. After all, what is the point if you can't modify the phone to your liking? Might as well get an Iphone right? Sadly though, it seems the new android trend is just heading the way of iphone, where users have to be protected from harming themselves. I noticed all the difficulties when I tried to root this LG phone, as compared to the phone I had two years ago. But android users are a persistent lot, more securities mean inventing more ways to break them. If you have problem installing ROM, try cm11 nightly build, it works for me. Post the specific problems and situations. We should be able to help each other. After all, android owners are together in a special community where we can relate to each other because of ideas we have for our phones. My advice to you is make sure you have the newest recovery and you are properly rooted. I can't use the script method where you run a msdos batch file. Since atnt suppose locked the boot.img file or something. Had to use a program called root master.
Sent from my LG-E980 using XDA Premium 4 mobile app
Nobody gives a damn, get life!
Antigen said:
Nobody gives a damn, get life!
Click to expand...
Click to collapse
Haha
2SHAYNEZ
hawkwind212 said:
I too just got new lg ogp phone. Been trying to customize it to my liking for the past 3 days and night. All I can say about android is it is not for everybody. Sure, you can use it as it is when you first get it as a stock device, and it will work as advertise. But there is a reason that you try modifing it regardless of breaking the manufacturer's warranty (yes, once you start rooting it, you violate the agreement.) You have personality of the kind that thinks you can fix anything by yourself. Nothing wrong with that, I'm in same personality group too, many Android owners are. After all, what is the point if you can't modify the phone to your liking? Might as well get an Iphone right? Sadly though, it seems the new android trend is just heading the way of iphone, where users have to be protected from harming themselves. I noticed all the difficulties when I tried to root this LG phone, as compared to the phone I had two years ago. But android users are a persistent lot, more securities mean inventing more ways to break them. If you have problem installing ROM, try cm11 nightly build, it works for me. Post the specific problems and situations. We should be able to help each other. After all, android owners are together in a special community where we can relate to each other because of ideas we have for our phones. My advice to you is make sure you have the newest recovery and you are properly rooted. I can't use the script method where you run a msdos batch file. Since atnt suppose locked the boot.img file or something. Had to use a program called root master.
Sent from my LG-E980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Exactly.
If android is going to be locked down, what is the point? With iPhone bringing in 3rd party keyboards and phablet size phones, might as well go with them instead of utilitarian design devices made by dictator led countries where creativity is frowned upon.
Unfortunately, Camera has stopped.
Perry2547 said:
Exactly.
If android is going to be locked down, what is the point? With iPhone bringing in 3rd party keyboards and phablet size phones, might as well go with them instead of utilitarian design devices made by dictator led countries where creativity is frowned upon.
Unfortunately, Camera has stopped.
Click to expand...
Click to collapse
Oh lawdy... Then go to iPhone buddy .. Lol see ya
2SHAYNEZ
But Apple has been implicated in planned obsolescence as well.
Does that matter to you?
To me, it makes me a bit upset that I could work on my vehicle twenty years ago, but now it's not possible. Planned obsolescence.
Make everything sweepstakes m disposable. Lock it down too. Keep every one buying the upgrades.
Unfortunately, Camera has stopped.
Are you still having problem installing the ROM? You have never tell us what kind of problems you ran into specifically. You just ventted your frustration here, nobody wants to hear that. If you want people to help, describe the issue. Go to this site and download the program vroot.
http://www.mobilepoint.us/2013/10/android-root-master-one-click-vroot.html#.U9XRXYfwJGo
The program is in Chinese, so you may want to watch youtube videos on the master root program first. Do a factory reset, clean wipe, run master root program, and hopefully you should be able to install the recovery. Once the recovery is properly installed, you can install the custom rom. Since there aren't many, I suggest you try cyanogenmod.
Sent from my LG-E980 using XDA Premium 4 mobile app
hawkwind212 said:
Are you still having problem installing the ROM? You have never tell us what kind of problems you ran into specifically. You just ventted your frustration here, nobody wants to hear that. If you want people to help, describe the issue. Go to this site and download the program vroot.
http://www.mobilepoint.us/2013/10/android-root-master-one-click-vroot.html#.U9XRXYfwJGo
The program is in Chinese, so you may want to watch youtube videos on the master root program first. Do a factory reset, clean wipe, run master root program, and hopefully you should be able to install the recovery. Once the recovery is properly installed, you can install the custom rom. Since there aren't many, I suggest you try cyanogenmod.
Sent from my LG-E980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I got a ROM to install. I indicated so in the thread. It was the E988 rom on the E980 thread.
I do a lot of whining and complaining but its for the best.
I hope that the complaining I did about Samsung's crappy products has saved a few people from buying...that is the only way that company will learn their lesson. Why pay $800 for a device only to get screen burn in.
But I never ever never ever BRICKED my Note 2.
I've bricked this OGP more times than I can count.
We should have the options to remove the locked boot loader. I would gladly sign an agreement acknowledging the risks.
We're going backwards. We're not making progress.
Same things is happening in desktop/laptop computers. I had to do something unusual to remove the UEFI on a Windows machine I bought last year just to install Lubuntu.
Speaking of Lubuntu, I had an ASUS Netbook with Windows 7 and an Atom processor. Needless to say, it ran slow. So I installed Lubuntu. Then , wow, the device ran so fast and smooth, and the already good battery life got three times better.
Why can't we have an option like that for our smartphones? I want to run the equivalent of Lubuntu on my OGP.
And another thing: Why are some custom roms dimming the display? Is it to make it appear as if the rom is giving better battery life?
Peace out bro.. but yeah, I'm not stopping my rants. If you don't like what I've got to say, simply don't read it.
This phone is not much more difficult to root than any Samsung phone I used. Also why didn't you do research before buying the phone? It was stated clearly that the boot loader was locked. However since day one of purchase I was able to follow a thread and have my phone rooted in ten minutes. It is really not that hard. Now there are a bunch of one click roots. This phone installs custom Roms every time with ease for me. I am no expert but I can read instructions. If you follow them, 99% of the time things will work. I love android for the fact that I have options. I am running a rooted stock ROM now but I love knowing that in ten minutes time I can have a new ROM flashed. This community has been so helpful and responsive.
Sent from my LG-E980 using XDA Premium 4 mobile app