Develop Bugs

ICS Leaks Causing Bricks?! Updated With More Info.(New Link)

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.

Why Samsung Not Allowing Downgrade?

It is a well known thing now that after updating we are not able to downgrade the modem as it alters the EFS. What could be the reason Sammies have done this? any guess? imo downgrading the modem must have been causing lots of disruptions in transmissions or the new modems may have been programmed to some new international norms. What is your opinon?:

Whatever the reason it sucks!
Nothing compares to the battery life you get on the first 4.1.1 roms and modems.
I'm glad I made a backup of the efs partition so I could get back to 4.1.1, people who didn't are kind of tied to the new modems at the moment...

victorator said:
Whatever the reason it sucks!
Nothing compares to the battery life you get on the first 4.1.1 roms and modems.
I'm glad I made a backup of the efs partition so I could get back to 4.1.1, people who didn't are kind of tied to the new modems at the moment...
Click to expand...
Click to collapse
Have you even read through those topics? The problem lies in kernels, not modems. Don't flash new kernels and you are safe, I jump around between different roms, old and new, but always flash Perseus kernel after flashing rom and never had any problem with lost IMEI. Not once had I have to restore EFS.
Beside that, with Sudden Death Syndrome, it is quite sound policy to not allow users to flash old firmware as it could result in that bug again.

The strange thing is that this problem only affects the n7100 model none of the s3 variants and n7105 had this problem with the latter kernel/modems.

mat9v said:
Have you even read through those topics? The problem lies in kernels, not modems..
Click to expand...
Click to collapse
No s hit sherlock.
Whatever the reason it's not right. Some people like me dont care about the SDS and I will use the vulnerable roms/kernels anyway.

it makes me remember when i had my old nokia 5800...
Sent from my GT-N7100 using xda premium

victorator said:
No s hit sherlock.
Whatever the reason it's not right. Some people like me dont care about the SDS and I will use the vulnerable roms/kernels anyway.
Click to expand...
Click to collapse
To each it's own, I guess. I paid enough for my phone to not endanger it more than I have to. Personally I would sooner buy bigger battery than flash older firmware with known bug and hope for some miniscule battery saving advantage.
From Samsung perspective $ are more important and anything that lowers servicing costs is golden.
The incompatibilty may also be a side effect of other changes, fixing of bug(s) we, as community, are not even aware of or some other problem we know nothing of. There is no apparent reason for Samsung to close a path to flashing old firmwares unless they have some need to do it (maybe new spyware in new kernels?). We are an additional service cost because we flash and sometimes break our phones.
Changing kernel across many platforms suggest either fixing some bug (again), creating some new spyware or some strange change in software policy. Do you have a better idea?

aka_sirok said:
it makes me remember when i had my old nokia 5800...
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Same here mate!
This reminds me of difficulties faced flashing my Nokia N8 to lower grade firmware

victorator said:
Whatever the reason it sucks!
Nothing compares to the battery life you get on the first 4.1.1 roms and modems.
I'm glad I made a backup of the efs partition so I could get back to 4.1.1, people who didn't are kind of tied to the new modems at the moment...
Click to expand...
Click to collapse
You probably had a brand new battery when you where on 4.1.1 and now your battery has wear out a bit so it's not as efficient as at the begining. Thinking the battery life was better on 4.1.1 is a myth. Ask anyone who is not on XDA and use stock ROM all the time. 4.1.1 was buggy and not stable and Sammy quickly upgraded to 4.1.2. the lastest XXMDG1 is by far the most stable Rom ever released by Samsung and the battery life is superior too.
I believe they prevent downgrading because of some security patch.

about a year ago Sonyericson xperia Arc has ICS upgrade and eventually this ICS upgrade made the phone completely not functioning in the moderate use level. hardware limitations and etc....
and of course, absolute no way to downgrade unless root + flash rom
I don't really understand why either... maybe this is to force us to pay for a new phone, and abandon the most updated but not compatible nor usable old devices. Marketing strategy? :silly:

Probably to stop people being able to easily unlock their phone, especially with the the qualcomm versions there was a service menu hack that allowed it.
Same reason Sony didn't allow PSP firmware downgrades, older firmwares had exploitable holes.
There are very few hardware vendors that allow downgrades, mostly because older versions often have more bugs, so the prefer people to be on later versions. It reduces the surface area of firmwares their support staff have to troubleshoot.
If you think Samsung care that you can't downgrade, you're living in a dream world.

Evolve or die.

zabumba said:
The strange thing is that this problem only affects the n7100 model none of the s3 variants and n7105 had this problem with the latter kernel/modems.
Click to expand...
Click to collapse
Its called different motherboards apparently. . Sorry to be blunt..
GT N7105 with XDA Premium......that is all......

[Q] SGH-T999L Beanstalk???

I'm relatively new, but have flash a couple Galaxy S2's. But I have my personal SGH-T999L that I want to flash and would like to use the Beanstalk 4.3 here http://forum.xda-developers.com/showthread.php?t=2345663, I can't afford to brick my phone and just trying to find out if anyone out there has used it on a T999L. I could only find one reference to it which wasn't very specific.
Thanks in advance

All Custom T999 Roms will be fine to use on the T999L unless otherwise stated.
Please don't double post in multiple places.

Sorry, was just trying to find someone online to answer before i tried it. Had been searching for an answer for quite awhile and running out of patience not finding much in specific in reqards to the t999L except a few horror stories related to other attempts to use t999 software on the L model. Was hoping to get an answer from DOCHOLIDAY77 (no offense) since he seems to have the most post/experience with the differences between the 2 models. But I thank you for your response and input. I presume from your answer, that as long as I only install the system software and leave the radio and bootloader alone. I'll be okay? Am I getting that right? That seems to be what the horror stories are about, people who have flashed the entire device with software from the original T999

dwgibson2000 said:
Sorry, was just trying to find someone online to answer before i tried it. Had been searching for an answer for quite awhile and running out of patience not finding much in specific in reqards to the t999L except a few horror stories related to other attempts to use t999 software on the L model. Was hoping to get an answer from DOCHOLIDAY77 (no offense) since he seems to have the most post/experience with the differences between the 2 models. But I thank you for your response and input. I presume from your answer, that as long as I only install the system software and leave the radio and bootloader alone. I'll be okay? Am I getting that right? That seems to be what the horror stories are about, people who have flashed the entire device with software from the original T999
Click to expand...
Click to collapse
You are spot on.

Anyone else refusing the official 4.3 update?

I'm just curious if anyone else here besides me is still on the ATT 4.1.1 or 4.1.2 only because they are still skeptical about updating or just refuse to accept it, and the reasons why. I feel like I'm the bad guy around here because I refuse to rush and play with the latest toy (Ooops, I mean the 4.3 update).
I'm even reading some of the members, and even some devs here wondering why some people are refusing to update, because you can do just about anything on the new bootloader that you can do on the old ones.
Well, I always thought that us rooters who are non-developers are not suppose to accept OTA updates from our carriers, and should only be flashing the Roms from our developers (good devs by the way). OTAs tend to fix previous issues and attempt to make the phones more secure, but at the same time, create new issues and further lock down the phones.
Look at all the posts around here right now that are just filled with 4.3 issues. One of the most common for example: (I'm having issues, have soft bricked, or just don't like the update?) Is there a way to flash back to complete 4.3 stock so that I can start over? No! And without any official firmware released from AT&T, if something goes wrong with your phone, then all you have to flash is a custom ROM, which I was taught that we should be doing any way, while avoiding the OTAs.
I just want to see here if there is anyone else thinking the same way and why, or is this just going to turn into people who OTA-ed becoming defensive.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

shortydoggg said:
I'm just curious if anyone else here besides me is still on the ATT 4.1.1 or 4.1.2 only because they are still skeptical about updating or just refuse to accept it, and the reasons why. I feel like I'm the bad guy around here because I refuse to rush and play with the latest toy (Ooops, I mean the 4.3 update).
I'm even reading some of the members, and even some devs here wondering why some people are refusing to update, because you can do just about anything on the new bootloader that you can do on the old ones.
Well, I always thought that us rooters who are non-developers are not suppose to accept OTA updates from our carriers, and should only be flashing the Roms from our developers (good devs by the way). OTAs tend to fix previous issues and attempt to make the phones more secure, but at the same time, create new issues and further lock down the phones.
Look at all the posts around here right now that are just filled with 4.3 issues. One of the most common for example: (I'm having issues, have soft bricked, or just don't like the update?) Is there a way to flash back to complete 4.3 stock so that I can start over? No! And without any official firmware released from AT&T, if something goes wrong with your phone, then all you have to flash is a custom ROM, which I was taught that we should be doing any way, while avoiding the OTAs.
I just want to see here if there is anyone else thinking the same way and why, or is this just going to turn into people who OTA-ed becoming defensive.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For starters i can't imagine why anyone who is rooted and running a custom ROM would ever dream of installing an official OTA. By the time the carrier's have had time to update their own ROM and distribute the update it will have long been incorporated into most custom ROM's. Point and case is 4.3 (which i have been running thanks to Task650 for many months)...boom all of a sudden you are stuck with a bootloader that you cannot change, or how about the case of the S4's who blindly or unknowing installed an OTA that gives them a locked bootloader that cant be downgraded (in the case of those of us with carriers who are evil bastards). The only case where i would personally find it 'acceptable' to install official OTA's is someone who has no interest in rooting or installing any custom software to their device. Yes the current S3 bootloader is rootable but one day, probably the next (if there is one) update i would imagine it will be locked down like the new devices. Its sad to say but the direction Google seems to be moving all Android devices may end up this way which will be a dark day indeed.

dntesinfrno said:
....Its sad to say but the direction Google seems to be moving all Android devices may end up this way which will be a dark day indeed.
Click to expand...
Click to collapse
I don't think it's Google locking the devices down. It's the manufacturers: Samsung, HTC, Motorola, etc... that are incorporating the locked bootloaders. I may be wrong, but that's the way it seems.

jack man said:
I don't think it's Google locking the devices down. It's the manufacturers: Samsung, HTC, Motorola, etc... that are incorporating the locked bootloaders. I may be wrong, but that's the way it seems.
Click to expand...
Click to collapse
Yes currently its the manufacturers, at the behest of the carriers...hence why att and verizon are locked on the s4 and up samsung devices but not sprint or tmo. I was simply stating that if things continue to go the way they seem to be with googles decisions moving forward with android it could end up that way.

They can lock em down but you know some talented dev will find a way in
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

rumrnr62 said:
They can lock em down but you know some talented dev will find a way in
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
True, but that can take months, and until then, you're stuck.

Can always buy a dev version or a nexus
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

I'll wait until the dev 4.3 rom stable then flash. Not much difference IMO.

ibuddler said:
I'll wait until the dev 4.3 rom stable then flash. Not much difference IMO.
Click to expand...
Click to collapse
Same here.
I wonder if for some reason another toy (Ooops, update) comes to this phone, will the rooters who OTA-ed, and then re-rooted or flashed another ROM (and tripped their new warranty bit counters in the process) be able to receive the new update, or will it be blocked because of the counter increment, and once again, will have to rely on custom ROMs, which they should already be doing?

shortydoggg said:
I'm just curious if anyone else here besides me is still on the ATT 4.1.1 or 4.1.2 only because they are still skeptical about updating or just refuse to accept it, and the reasons why. I feel like I'm the bad guy around here because I refuse to rush and play with the latest toy (Ooops, I mean the 4.3 update).
I'm even reading some of the members, and even some devs here wondering why some people are refusing to update, because you can do just about anything on the new bootloader that you can do on the old ones.
Click to expand...
Click to collapse
...Anything, except flashing back to stock for reflashing purposes or for warranty service or resetting the Knox warranty bit. OTA may also damage resale value, among other downsides.
shortydoggg said:
Well, I always thought that us rooters who are non-developers are not suppose to accept OTA updates from our carriers, and should only be flashing the Roms from our developers (good devs by the way). OTAs tend to fix previous issues and attempt to make the phones more secure, but at the same time, create new issues and further lock down the phones.
Look at all the posts around here right now that are just filled with 4.3 issues. One of the most common for example: (I'm having issues, have soft bricked, or just don't like the update?) Is there a way to flash back to complete 4.3 stock so that I can start over? No! And without any official firmware released from AT&T, if something goes wrong with your phone, then all you have to flash is a custom ROM, which I was taught that we should be doing any way, while avoiding the OTAs.
I just want to see here if there is anyone else thinking the same way and why, or is this just going to turn into people who OTA-ed becoming defensive..
Click to expand...
Click to collapse
There are diverse camps among the rooters & other members here. Through my GS1, GS2 & GS3 I've used mostly debloated stock TW roms; for work, on the road constantly & needing a maximum stable daily driver; like other stock TW enthusiasts.
Apart from user (flashing) errors, the stability, the flexibility & connectivity complaints you cited are what I measured against when deciding to flash a 4.3 rom, kernel & modem from |ROM|Bootloader|Kernel|Modem| AT&T Official 4.3 MJB |24 Nov 2013| .
What designgears, upndwn4par, loserskater & the others have posted on multiple threads I read & reread here before flashing allowed me to attempt the 4.3 upgrade with a solid backout plan & maximum control, reaching my desired result:
Stable, debloated (by me, it's personal) permission edited (using App Ops) battery optimized 4.3 using the same bootloader as on 4.1.2.
The resources exposed in that one thread I linked, plus miles of reading in prep here on XDA showed me how to have the upgrade my way, so even stock a enthusiast can get a first class passage thanks to our devs. Buy them a drink when you can!

SM-G925T problems. Please help ASAP. Thanks

I have yet to find a answer to this question anywhere. Any help would be greatly appreciated.
I have a SM-G925T and I had rooted and flashed roms to this device in the past and have been able fix all of the problems I have run into until now. I am not currently able to use my phone for texting/caling/mobile data until I connect to wifi (with wifi calling on t-mobile) I am not able to do anything, but when I do connect to wifi I can make calls and tests. I have been looking everywhere and not seen anyone with the same problem. I feel as though I corrupt the EFS folder or IMEI as my IMEI now shows 360000000000006 and the actual IMEI is entirely different. If anyone has an answer to this that doesn't involve sending it to Samsung I would love the help.

What have you tried to fix this problem? Reset APN? Reflash rom? What rom are you using? Also dont sent it to Samsung, just ask for tmobile to replace it unless you dont have insurance.
Sent from my SM-G925T using Tapatalk

The problem is rooting.
Returning to stock will fix and solve all your problems.
Pp.

i ran into the same issue 2 days ago and searched this plus many other sites for a solution. i kept getting answers saying something about a root key needed to be fixed. or the other answer i was getting told was to flash [KERNEL] UniKernel v8-0002 COH9. i ultimately ended up taking it back to t-mobile and got a new phone. but the manager told me it was missing certificates and the stock kernel. i hope this little piece of information helps, and i hope you have better luck in restoring your phone than i did.

Every time this phone S6edge, gets an update it becomes harder and riskier to root the S6e and still have a working phone.
This top of the line device (until the S7 gets here) isn't your average phone to experiment with, try a plain android like a nexus Google phone, there's probably a handful of developers working on the Nexus alone Vs one (maybe) for the S6e?
I know xda forums are all about taking control of your phone but not this puppy, you must surrender to Samsung on this one.
My phone is 6 months old and works great, even after updates it just gets better and better and after marshmallow gets here this phone will be a greater device.
I have stayed stock and never attempted to root because I was following and reading all threads started on the S6e and it was a hot mess, a lot of stuff and phones going wrong at first and as soon as some one found an exploit Samsung had it removed and safe root went right out the window.
I have learned to like stock and I'm ok with it. And my phone works all the time.
Pp.

PanchoPlanet said:
Every time this phone S6edge, gets an update it becomes harder and riskier to root the S6e and still have a working phone.
This top of the line device (until the S7 gets here) isn't your average phone to experiment with, try a plain android like a nexus Google phone, there's probably a handful of developers working on the Nexus alone Vs one (maybe) for the S6e?
I know xda forums are all about taking control of your phone but not this puppy, you must surrender to Samsung on this one.
My phone is 6 months old and works great, even after updates it just gets better and better and after marshmallow gets here this phone will be a greater device.
I have stayed stock and never attempted to root because I was following and reading all threads started on the S6e and it was a hot mess, a lot of stuff and phones going wrong at first and as soon as some one found an exploit Samsung had it removed and safe root went right out the window.
I have learned to like stock and I'm ok with it. And my phone works all the time.
Pp.
Click to expand...
Click to collapse
Totally agree!

+2!!!!!

I personally have had no problems with rooting my phone or with custom roms. The only time I had an issue was when I changed my boot splash. The first time I bricked my phone and had to use emergency recovery with Smart Switch. I am also going to suggest you try that before you return your phone. Make sure you backup you internal SD first though because Smart Switch will erase everything. I think it will fix your problem be cause the emergency recovery is started with your serial number. so I do believe it will fix your efs issue. It is definitely worth a try.
Future reference. TWRP does backup your EFS if you click the checkbox for it.