Develop Bugs

[Q]Why "root" your phone ?

Hi, everyone.
I am fairly new on the forum. I keep reading about "rooting" your phone. I have a Samsung Galaxy SII T989 and my questions are:
1. What is "phone rooting" ?
2. What are the advantages of having your phone "rooted" ?
Thank you.

I'm *hoping* this is a joke, but if it isn't, here's a good place to start:
http://lmgtfy.com/?q=why+root+your+phone

unclespoon said:
I'm *hoping* this is a job, but if it isn't, here's a good place to start:
Click to expand...
Click to collapse
Wow that's pretty awesome, would have never thought about that ha ha ha
Sent from my SGH-T989 using xda premium

Yes... It is a job to think: Why would you risk to unstable your phone by "root" it?
I see that:
- people are removing the wrong apps that negatively affect their phones (e.q. a ccounts and sync).
- people's phone are missing other thinks they used to like (bars, the small flashing blue light when you scroll to the top and to the bottom of the screen).
- the pletoria of apps for rooted phone are not that great...
- the advantage you get is that you only free up some internal space?

I have no issues with my phone rooted. I am on a stock T-Mobile ROM and froze all the bloatware. You can get rids of ads in apps when rooted which is pretty damn convenient for me. Do research on what is safe to freeze and you wont have any problems. Freezing is more safe than uninstalling...
Sent from my SGH-T989 using xda premium

The reason is you then have 100% control over your system. If you know what you're doing, having root can be a very powerful tool. You can greatly speed up the phone, free up ram, theme things, it gives you total control.
Now this is a double edged sword too. All the horror stories you're hearing about root are by people who don't have the faintest idea what they're doing and are breaking things.
Think of it in terms of computers. On linux, having root is, well, having root. You have full access to the system. On windows, (vista and above mainly) it's like having an administrator account with UAC turned off. In the right hands, this is very very nice. In the wrong hands, it can cause problems.
If you don't see the benefit of rooting, then I'd highly suggest you do not do so. These devices are not windows boxes where you screw up and "oh well, guess it's time to bust out the windows cd and do a re-install. I'd also suggest perhaps looking through the market at things that require root, and the benefits they give you. (Titanium backup, for instance. Or tethering when your provider doesn't want you to.)

Sui Generis said:
Yes... It is a job to think: Why would you risk to unstable your phone by "root" it?
I see that:
- people are removing the wrong apps that negatively affect their phones (e.q. a ccounts and sync).
- people's phone are missing other thinks they used to like (bars, the small flashing blue light when you scroll to the top and to the bottom of the screen).
- the pletoria of apps for rooted phone are not that great...
- the advantage you get is that you only free up some internal space?
Click to expand...
Click to collapse
Honestly if you don't want to root your phone do not root it. A lot of the problems you mention stem from people attempting to root and don't know what they are really doing. I am one of those people who are strictly against one click root methods. Because you literally don't need to read anything to understand what exactly are you doing.
If you know what you can do with a rooted phone things like
-Better battery life by manipulating the cpu cycles and governors.
-Change the entire look of the phone to look as if it a totally different os.
-Better performance overall of your phone
-Overall better experience than what the carrier give you.
I could name endless things about why rooting is better than what the stock gives you.
A lot of people I hear just say go to xda and root your phone. Which is very ignorant. Not everyone should root. If your phone is doing what it needs to do then leave it alone. My friends who have android phones ask me to root for them i tell them no root it themselves. With one click methods people make an xda account and blame the developer saying their rom sucks and is bad battery life where as the problems stem most of the time the user side.

I agree. I haven't rooted my SGS2 yet because the stock ROM, for me, seems to be serving its purpose very well. All my benchmark scores are within standard deviation of the OC kernels and now we've got wifi calling. I use ADW for a new UI and that suits me just fine. Yes, ICS will come from CM long before it does from the carriers, but I'm ok with that - even though I'll probably end up rooting and installing ICS once it's stable. My previous Android phones were rooted within days of purchase, and yes I would like to remove bloat, but with all the internal storage and my 32gb sd card I think I'll be a happy camper. It would be nice to know carrier IQ was gone, though...

rooting = control
no root = no control over settings
they don't let you root by default to prevent noobs from damaging their phone by changing some settings they should have not touched

when i rooted my phone and got beastmod 4.0 with flaux kernal my battery life increased like 50x than stock x.x
Sent from my SGH-T989 using Tapatalk

I personally don't think I'll be rooting (at least not while the phone's still new). I'm happy with the level of customization on the stock.
One question though. So basically, when rooted, you are "logged in" to your phone as root user? Are there any security risks with this?

Killbynature said:
Honestly if you don't want to root your phone do not root it. A lot of the problems you mention stem from people attempting to root and don't know what they are really doing. I am one of those people who are strictly against one click root methods. Because you literally don't need to read anything to understand what exactly are you doing.
If you know what you can do with a rooted phone things like
-Better battery life by manipulating the cpu cycles and governors.
-Change the entire look of the phone to look as if it a totally different os.
-Better performance overall of your phone
-Overall better experience than what the carrier give you.
I could name endless things about why rooting is better than what the stock gives you.
A lot of people I hear just say go to xda and root your phone. Which is very ignorant. Not everyone should root. If your phone is doing what it needs to do then leave it alone. My friends who have android phones ask me to root for them i tell them no root it themselves. With one click methods people make an xda account and blame the developer saying their rom sucks and is bad battery life where as the problems stem most of the time the user side.
Click to expand...
Click to collapse
Agree entirely, back on the ns forums I was constantly advising people against one click.
Sent from my Hercules with xda Premium.

eMace said:
I personally don't think I'll be rooting (at least not while the phone's still new). I'm happy with the level of customization on the stock.
One question though. So basically, when rooted, you are "logged in" to your phone as root user? Are there any security risks with this?
Click to expand...
Click to collapse
Only if you use bad apps. Its just like on any other os: if you're the administrator you have to be twice as careful wity what you install
Sent from my Hercules with xda Premium.

Rooting your phone is like getting under the hood of your car.
If you have never worked on a car, it would not be wise to just start pulling out plugs/wires, moving things around and installing enhancements as you would probably ruin your car and end up paying a mechanic to fix it.
However, if you take the time to read up on any changes before you make them, then you could end up with a turbo-boosted hot rod with a custom Chrome setup that not only looks better but performs like a champ.

www.youtube.com/themrroxtar noob tutorials and rom reviews. Check it out. Plus everyone can find how to win a free Hercules at the end of this month!
Sent from my SGH-T989 using xda premium

for me, rooting is mainly removing bloatware.
just like when you buy a new laptop, they install a lot of crap and it slow your computer down.
rooting can remove bloatware and also give you more speed, but you might lose the upgrading from the OTA(official t mobile update) and need to check update in here.
but if you are ok with the performance that you can on your phone now, stay with it.

It's all about the flash (yeah, bahby!) The custom ROM's can't be flashed without root: Forget about deleting/freezing unwanted applications and find a developers ROM you like - experiment a bit and have some fun with the phone.
As well, applications that require root - quick boot and appinstaller, are a must for me, making root mandatory for my phoning pleasure.
I had an HD2 before, and while there's greater variety in the ROM's, set-up to root is a biach on the HTC devices, so we can thank our lucky stars Samsung makes this easier (prolly not on purpose, though )

TheMrRoxtar said:
www.youtube.com/themrroxtar noob tutorials and rom reviews. Check it out. Plus everyone can find how to win a free Hercules at the end of this month!
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
What's up man...wheelerhomes from YouTube.
Enjoying my rooted sg2! Have to agree with some comments ...understand what you're doing or don't do it. I learned just enough to be dangerous! But am picking up more and more as I read. I do wish the tutorials went a little more into WHY you're doing this or that vs just saying do this. It confusing to grasp what rooting is but when start downloading Odin, loading superuser, clockwork mod recovery, titanium, etc its REALLY overwhelming not knowing what each step does.
I certainly did not need to root. But like all these phones, it started out nice and snappy and within a week it was glitching like my old vibrant ...all kinds of stupid crap running in the background. Rooting was stressful because I didn't know exactly why I was doing these different steps!! Once I did it I was stoked at how fast my phone was. Just flashed wifi stock rom today that whitehawkx put up and I'm already missing my Juggernaut! But wifi calling/texting is slick for my location!

OK,
- better battery life can serve me better...
- being able to install other apps (such call recorder) can also be beneficial...
The problem is that I come from the Windows side rather than the Linux or Apple so I do not excel into this so I am afraid not to brick the phone.
Having said that, it would be VERY, VERY, VERY nice of you (or everyone else with a very rooted stable phone) to post clear and "for dummies" instructions on how to:
1. root your phone
2. install customed rom (beastmod, juggernaut or odin, etc - upon your recommendation).
Many thanks in advance !

eMace said:
I personally don't think I'll be rooting (at least not while the phone's still new).
Click to expand...
Click to collapse
Installed clockwork mod recovery on the first boot while the phone was still in the plastic wrap. Rooted via superoneclick on the 2nd boot ONLY because you have to reboot after flashing clockwork mod.
The process is easy if you read the instructions.
Sent from my Hercules using XDA App

Reasons to root?

I have never rooted a phone before(well technically I rooted an HTC Inspire, which I was asked to do, but I did nothing on it involving the Root). What are some reasons I should root, and can anything go wrong during the root process? Just putting this out there, I will not be flashing any ROMs, as I know there is a chance that the device can be bricked While flashing if something goes wrong, and I do not have a spare phone to go back to if something does go wrong.
Sent from my SPH-D710 using XDA

If your not going to use customs ROMs having root access will allow you to delete any app you desire including all the preloaded sprint ones. You will also be able to download and use any apps that require root for enhanced functionality. Beyond that, there's not a whole lot of difference you'll see.
In the early days, people would do root only to adjust memory values on phones like the g1 and hero. There were a lot of settings you could tweak on a stock phone to make it better with the addition of root. Now with today's technology and phones like the E4GT, alot of those tweaks are unnecessary. The ones that are helpful are lower level and best done by a ROM dev or someone who knows what they are changing. Custom ROMs will have these included usually.
Sent from my SPH-D710 using XDA

Removing bloatware that wastes ram and flash storage space, certain apps are smoother (tasker, some launchers, and custom lockscreens for example), ability to block ads, better backup capabilities, ability to underclock the cpu for those times you need to squeeze extra battery life out, and so on.
If none of this sounds important, then don't root. It can be a little bit of a puzzle getting back to stock sometimes, but it is extremely extremely hard to do something to your phone that is not reversible at this point. Note this statement is not true for all phones, especially newly released phones. But it is true for the epic touch.
Sent from my SPH-D710 using Tapatalk 2

Yeah.. I second what the guy above said..lol.
Wasup King..

I third the guy above the guy above me and second the guy above him... My thoughts are if you have to make a thread asking others should I root when the basic community offers all the info on the profit or lost of rooting then I say leave your phone alone.
Do yourself a favor and get an extended battery and download foxfi and you will be just fine. Most of us... ok all of us in here are flash-a-holics and can't help ourselves that's why we do it... Do some reading in here take a look at rom pics and see if you really really really like something...
Good luck

playya said:
I third the guy above the guy above me and second the guy above him... My thoughts are if you have to make a thread asking others should I root when the basic community offers all the info on the profit or lost of rooting then I say leave your phone alone.
Do yourself a favor and get an extended battery and download foxfi and you will be just fine. Most of us... ok all of us in here are flash-a-holics and can't help ourselves that's why we do it... Do some reading in here take a look at rom pics and see if you really really really like something...
Good luck
Click to expand...
Click to collapse
The truth can sometimes be cruel..lol. +1 to Playa..

The best thing about rooting for me is adblocking, I cant believe how many apps and things are bundled with intrusive ads.

Indrid Cole said:
The truth can sometimes be cruel..lol. +1 to Playa..
Click to expand...
Click to collapse
Just trying to keep it real up in herrrrre! Ya Ya!

someguyatx said:
The best thing about rooting for me is adblocking, I cant believe how many apps and things are bundled with intrusive ads.
Click to expand...
Click to collapse
Just another app that root brings to the table:
Roam control lets you force into roam when you are stuck with one bar on Sprint.
Godsend for me!
Sent from my SPH-D710 using xda premium

playya said:
I third the guy above the guy above me and second the guy above him... My thoughts are if you have to make a thread asking others should I root when the basic community offers all the info on the profit or lost of rooting then I say leave your phone alone.
Do yourself a favor and get an extended battery and download foxfi and you will be just fine. Most of us... ok all of us in here are flash-a-holics and can't help ourselves that's why we do it... Do some reading in here take a look at rom pics and see if you really really really like something...
Good luck
Click to expand...
Click to collapse
I have seen several ROMs I love the look of, including AOKP, CM9, and Caulkin's ROMs. My only issue with ROMs is the fact that things can go wrong with flashing, and they can brick the device. And from what ive heard, there is an increased chance of bricking when flashing an ICS ROM while on GB. I have no backup device to go to if something like that does happen, so thats why Im staying away from flashing for now.
Sent from my SPH-D710 using XDA

EggosEvo said:
I have seen several ROMs I love the look of, including AOKP, CM9, and Caulkin's ROMs. My only issue with ROMs is the fact that things can go wrong with flashing, and they can brick the device. And from what ive heard, there is an increased chance of bricking when flashing an ICS ROM while on GB. I have no backup device to go to if something like that does happen, so thats why Im staying away from flashing for now.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
The brick usually come from flashing to gb from ics using ics repacked kernels. There is always some risk/chance of brick from a bad flash, but El26 with cwm is fairly safe and the last kernel to have offical cwm. That is the only kernel i will use to flash anythin. I flash new roms every week. I have flashed to and from ics with no issues.
Sent on HyDrA using Tapatalk 2

EggosEvo said:
I have seen several ROMs I love the look of, including AOKP, CM9, and Caulkin's ROMs. My only issue with ROMs is the fact that things can go wrong with flashing, and they can brick the device. And from what ive heard, there is an increased chance of bricking when flashing an ICS ROM while on GB. I have no backup device to go to if something like that does happen, so thats why Im staying away from flashing for now.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
My friend you have been misinformed.... There is a risk in everything we do so like I said if worried don't do it. If you take some more time and read you will see that the tar files are pretty brick proof and problems have occurred when flashing roms on ICS and using an ICS recovery. Most developers have stopped using CWM in ICS roms.
Clearly you need to do a lil more reading if you want to root but like suggested just relax and wait for the OTA and you will be OK.... One more thing all instructions say to flashEL26 kernel which is GB to flash anything ICS..... so flashing ICS rom while on GB is wrong

EggosEvo said:
I have never rooted a phone before(well technically I rooted an HTC Inspire, which I was asked to do, but I did nothing on it involving the Root). What are some reasons I should root, and can anything go wrong during the root process? Just putting this out there, I will not be flashing any ROMs, as I know there is a chance that the device can be bricked While flashing if something goes wrong, and I do not have a spare phone to go back to if something does go wrong.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
1. Titanium Backup: remove those pesky system apps that Sprint really thinks you need.
2. File explorers: Being able to modify system folders to change things like the boot animation, etc.
3. Ad blocking: The ability to block ads (moral issues notwithstanding... but some apps have no paid version to get rid of the ads.)
4. Once you've rooted, it's just the beginning. You may change your mind about flashing and rooting your phone is the first step in learning more about your phone and the AndroidOS in general.

I have not seem anyone mention that it's also about the about the damn principal of the matter... why shouldn't you have root access for a device you bought? Also if you ODIN back to EL26 to flash, carefully read all instructions posted with the rom, and wait a day or two after the release and check the comments to make sure there hasn't been some sort of inexplicable rash of bricks thanks to the rom you won't have any problems to speak of... other than not being able to fathom how much better something like AOKP is than stock touchwiz gingerbread

Thanks to everyone. I've decided that I will root when the official ICS launches for my phone.
Sent from my SPH-D710 using XDA

Personally, I root to follow fledging developers open their ROMs. It is exhilarating to see the new stuff that people come up with and the creativity that ensues because of it.
Also enhancing my phone experience with free hotspot access and customization doesn't help. However if none of these interesting you I wouldn't recommend it.

Reason to root
I root because it can be done. It's that simple. To me, it feels like regardless of the magnitude of what you can or cannot do while rooted, or how easy or difficult it may be to root your phone, a skilled user should have access to everthing your phone is capable of.
Plus, I feel like I'm "sticking it to the man", which is an added bonus!

My main reason for rooting was to remove the bundled software that comes with the phone. But I love that fact that I don't have any ads either! If u decide to root, download AdFree from the market & u'll realize just how many "free" apps use adware

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.

Sorry but I may be leaving the root community for good

I've suspected for a long time that custom ROMs have been the source of all my frustrations with the Gnex. I unlocked and rooted on the first day and even though there wasn't much in the way of custom Roms with 4.0 I was excited to try all the different mods that were slowly flooding XDA and RootzWiki.
This wasn't my 1st experience with root either. I owned the Dinc and loved the idea of tinkering with my device. I learned a lot. Mainly that you should ALWAYS MAKE A BACKUP. and take the extra minute to wipe everything. I don't even use TI backup anymore because I wanted to start over from scratch any time I flashed a new ROM.
I say this because I know there are ppl in the forums that are smarter than I when it comes to Android. There are also some of those same ppl that will assume that I made some sort of noob mistake and I should try "wiping data" or something. Trust me, I've tried that and it doesn't fix it.
My main issues have been:
*losing data connection for no reason and eventually having to reboot in order to restore data.
*Weak network/WiFi.
Now I know there is a thread on rootz that addresses the bars and how inaccurate they are. But when two identical devices sit down in the same place and run speed test. My Gnex can slow to a snails pace at times. The wierdest thing about this is that it only seems to do it sporadically, which makes recreating it almost impossible. Although it seems most frequent at work, but that maybe because I spend an ungodly amount of time at my office.
*Lag/freezes
I know its not gonna work perfectly all the time and sometimes you have to reboot your phone just to give it a chance to reset itself and that's cool but when you do that and it doesn't fix the sluggishness of the phone then I feel there is a problem.
* problems with certain system functions like Bluetooth or GPS
Now this may be only an issue with particular Roms which may be known to have problems with certain aspects of the system. For instance, it seems pretty common from what I've seen on the forums that GPS is an issue for some on 4.2. I was actually on 4.2 this morning until I went to punch in an address from a text msg to Navigation and it wouldn't lock on my location. I got frustrated and decided to wipe and install the AOKP milestone I had saved and when I set everything back up guess what? Navigation still wouldn't lock on. I ended up having to bail out on some guys because I could find there house. I got home and found a stock ROM online. I wiped, flashed and setup my phone for the second time today. I downloaded Maps and immediately went to find the address and it was insane how fast it locked on a location.
There are other issues but I'm becoming long winded so I'll try to wrap it up.
Now I'm not one to dismiss my own part in my problems. I've certainly tried to address them when/if they arise with what little knowledge I have and the ability to learn what I can. I e emailed devs amd talked to others and sometimes it helps, but sometimes like this morning you just want things to work when you need them to without wasting your time having to revert to a nandroid or doing some other wizardry.
"Well, why don't you just go buy an iPhone then?" you might say
I've actually contemplated it but I do really like android, Google Maps are the **** (I depend on Navigation a lot )and I like to be able to customize. And I also don't really want to pay the money to terminate my contract so I'm kinda just stuck. But I thought about doing one thing.
A couple weeks ago, I unrooted and relocked my phone and flashed stock images for JB on CDMA and from there all I did was unlock and root keeping it stock and I tell you I glad I did because all my problems no longer seem to exist. My battery life might not be what I was getting on 4.2 these last couple days but I think I'm willing to stick with this for now until Verizon gets off their ass and pushes an update to us.
I'm not trying to rant to the Dev community or complain that y'all aren't living up to my satisfaction. Hell, maybe somebody might have a solution I haven't tried yet. I'm just putting this out there in case someone was having the same trouble and could get some help.
Sent from my Galaxy Nexus using XDA Premium HD app

On ParanoidAndroid 2.54 + franco.kernel r300. None of the problems you mentioned are present or has ever happened with me. Perhaps if you didn't mod your phone so much as to NOT be able to pinpoint a problem is where you went wrong.
Who knows? I surely don't. Don't know you but I don't think I'll be noticing your absence. Good luck with everything!

automaddux said:
I've suspected for a long time that custom ROMs have been the source of all my frustrations with the Gnex. I unlocked and rooted on the first day and even though there wasn't much in the way of custom Roms with 4.0 I was excited to try all the different mods that were slowly flooding XDA and RootzWiki.
This wasn't my 1st experience with root either. I owned the Dinc and loved the idea of tinkering with my device. I learned a lot. Mainly that you should ALWAYS MAKE A BACKUP. and take the extra minute to wipe everything. I don't even use TI backup anymore because I wanted to start over from scratch any time I flashed a new ROM.
I say this because I know there are ppl in the forums that are smarter than I when it comes to Android. There are also some of those same ppl that will assume that I made some sort of noob mistake and I should try "wiping data" or something. Trust me, I've tried that and it doesn't fix it.
My main issues have been:
*losing data connection for no reason and eventually having to reboot in order to restore data.
*Weak network/WiFi.
Now I know there is a thread on rootz that addresses the bars and how inaccurate they are. But when two identical devices sit down in the same place and run speed test. My Gnex can slow to a snails pace at times. The wierdest thing about this is that it only seems to do it sporadically, which makes recreating it almost impossible. Although it seems most frequent at work, but that maybe because I spend an ungodly amount of time at my office.
*Lag/freezes
I know its not gonna work perfectly all the time and sometimes you have to reboot your phone just to give it a chance to reset itself and that's cool but when you do that and it doesn't fix the sluggishness of the phone then I feel there is a problem.
* problems with certain system functions like Bluetooth or GPS
Now this may be only an issue with particular Roms which may be known to have problems with certain aspects of the system. For instance, it seems pretty common from what I've seen on the forums that GPS is an issue for some on 4.2. I was actually on 4.2 this morning until I went to punch in an address from a text msg to Navigation and it wouldn't lock on my location. I got frustrated and decided to wipe and install the AOKP milestone I had saved and when I set everything back up guess what? Navigation still wouldn't lock on. I ended up having to bail out on some guys because I could find there house. I got home and found a stock ROM online. I wiped, flashed and setup my phone for the second time today. I downloaded Maps and immediately went to find the address and it was insane how fast it locked on a location.
There are other issues but I'm becoming long winded so I'll try to wrap it up.
Now I'm not one to dismiss my own part in my problems. I've certainly tried to address them when/if they arise with what little knowledge I have and the ability to learn what I can. I e emailed devs amd talked to others and sometimes it helps, but sometimes like this morning you just want things to work when you need them to without wasting your time having to revert to a nandroid or doing some other wizardry.
"Well, why don't you just go buy an iPhone then?" you might say
I've actually contemplated it but I do really like android, Google Maps are the **** (I depend on Navigation a lot )and I like to be able to customize. And I also don't really want to pay the money to terminate my contract so I'm kinda just stuck. But I thought about doing one thing.
A couple weeks ago, I unrooted and relocked my phone and flashed stock images for JB on CDMA and from there all I did was unlock and root keeping it stock and I tell you I glad I did because all my problems no longer seem to exist. My battery life might not be what I was getting on 4.2 these last couple days but I think I'm willing to stick with this for now until Verizon gets off their ass and pushes an update to us.
I'm not trying to rant to the Dev community or complain that y'all aren't living up to my satisfaction. Hell, maybe somebody might have a solution I haven't tried yet. I'm just putting this out there in case someone was having the same trouble and could get some help.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Thats cool, you already tried your fair share of roms, if none of them worked for you the stock is the best with unsurpassed stability. Despite whats advertised about the nexus, the stock android firmware is excellent too, specially when you want something that just plain works.
Sent from my Galaxy Nexus using Tapatalk 2

Great story brother. Thanks for sharing.
Sent from my i9250

bk201doesntexist said:
Great story brother. Thanks for sharing.
Sent from my i9250
Click to expand...
Click to collapse
Keep coming..it works if you work it
Sent from my Galaxy Nexus

goodbye person ive never seen post before. hope you figure out your problems

Stock is the way to go, but you don't have to leave the xda because you no longer run a custom ROM. there is a lot of useful information that is shared here that doesn't necessarily apply to custom ROM.
I am also running stock rom from now on.
Sent from my Nexus 7 using xda premium

automaddux said:
I've suspected for a long time that custom ROMs have been the source of all my frustrations with the Gnex. I unlocked and rooted on the first day and even though there wasn't much in the way of custom Roms with 4.0 I was excited to try all the different mods that were slowly flooding XDA and RootzWiki.
This wasn't my 1st experience with root either. I owned the Dinc and loved the idea of tinkering with my device. I learned a lot. Mainly that you should ALWAYS MAKE A BACKUP. and take the extra minute to wipe everything. I don't even use TI backup anymore because I wanted to start over from scratch any time I flashed a new ROM.
I say this because I know there are ppl in the forums that are smarter than I when it comes to Android. There are also some of those same ppl that will assume that I made some sort of noob mistake and I should try "wiping data" or something. Trust me, I've tried that and it doesn't fix it.
My main issues have been:
*losing data connection for no reason and eventually having to reboot in order to restore data.
*Weak network/WiFi.
Now I know there is a thread on rootz that addresses the bars and how inaccurate they are. But when two identical devices sit down in the same place and run speed test. My Gnex can slow to a snails pace at times. The wierdest thing about this is that it only seems to do it sporadically, which makes recreating it almost impossible. Although it seems most frequent at work, but that maybe because I spend an ungodly amount of time at my office.
*Lag/freezes
I know its not gonna work perfectly all the time and sometimes you have to reboot your phone just to give it a chance to reset itself and that's cool but when you do that and it doesn't fix the sluggishness of the phone then I feel there is a problem.
* problems with certain system functions like Bluetooth or GPS
Now this may be only an issue with particular Roms which may be known to have problems with certain aspects of the system. For instance, it seems pretty common from what I've seen on the forums that GPS is an issue for some on 4.2. I was actually on 4.2 this morning until I went to punch in an address from a text msg to Navigation and it wouldn't lock on my location. I got frustrated and decided to wipe and install the AOKP milestone I had saved and when I set everything back up guess what? Navigation still wouldn't lock on. I ended up having to bail out on some guys because I could find there house. I got home and found a stock ROM online. I wiped, flashed and setup my phone for the second time today. I downloaded Maps and immediately went to find the address and it was insane how fast it locked on a location.
There are other issues but I'm becoming long winded so I'll try to wrap it up.
Now I'm not one to dismiss my own part in my problems. I've certainly tried to address them when/if they arise with what little knowledge I have and the ability to learn what I can. I e emailed devs amd talked to others and sometimes it helps, but sometimes like this morning you just want things to work when you need them to without wasting your time having to revert to a nandroid or doing some other wizardry.
"Well, why don't you just go buy an iPhone then?" you might say
I've actually contemplated it but I do really like android, Google Maps are the **** (I depend on Navigation a lot )and I like to be able to customize. And I also don't really want to pay the money to terminate my contract so I'm kinda just stuck. But I thought about doing one thing.
A couple weeks ago, I unrooted and relocked my phone and flashed stock images for JB on CDMA and from there all I did was unlock and root keeping it stock and I tell you I glad I did because all my problems no longer seem to exist. My battery life might not be what I was getting on 4.2 these last couple days but I think I'm willing to stick with this for now until Verizon gets off their ass and pushes an update to us.
I'm not trying to rant to the Dev community or complain that y'all aren't living up to my satisfaction. Hell, maybe somebody might have a solution I haven't tried yet. I'm just putting this out there in case someone was having the same trouble and could get some help.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
I hope you really didn't write all of this from your nexus lol. But just go to stock...simple :thumbup:
Sent from my Galaxy Nexus using xda premium

I see how you feel abouyt this. I have had issues as well. It really stems from what Roms are and what we expect from them. The term Night lies have lost a little bit of its worry recently because they are fairly bug free. But that doesn't mean that little tweaks and mods aren't killing battery life and deteriorate over time due to bad patches and coding.
That said I would highly recommend checking out BuglessBeast. They are not night lies by any means. They are highly stable AOSP Roms that perform much better then anything else on the market. He has few commits aside from under the hood tweaks. Reboot menu, emoji and a slight few other things are it. I have never had an issue with them and recommend checking them out. Also they are pretty much the only VZW app compatible ROM. Peter has been building BuglessBeast since Eclair on the Droid1 (almost 3 years now). Always providing an excellent experience.

spjetrovic said:
Keep coming..it works if you work it
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Flashaholics anonymous?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

Stock + root is the way to go for me on Nexus phones. On my last non Nexus (SGS3) I was always flashing new roms trying to look for something that just works, but I am tired of it. On my Nexus S and GNexus, stock rom is amazing, I don't need anything else.

automaddux said:
I've suspected for a long time that custom ROMs have been the source of all my frustrations with the Gnex. I unlocked and rooted on the first day and even though there wasn't much in the way of custom Roms with 4.0 I was excited to try all the different mods that were slowly flooding XDA and RootzWiki.
This wasn't my 1st experience with root either. I owned the Dinc and loved the idea of tinkering with my device. I learned a lot. Mainly that you should ALWAYS MAKE A BACKUP. and take the extra minute to wipe everything. I don't even use TI backup anymore because I wanted to start over from scratch any time I flashed a new ROM.
I say this because I know there are ppl in the forums that are smarter than I when it comes to Android. There are also some of those same ppl that will assume that I made some sort of noob mistake and I should try "wiping data" or something. Trust me, I've tried that and it doesn't fix it.
My main issues have been:
*losing data connection for no reason and eventually having to reboot in order to restore data.
*Weak network/WiFi.
Now I know there is a thread on rootz that addresses the bars and how inaccurate they are. But when two identical devices sit down in the same place and run speed test. My Gnex can slow to a snails pace at times. The wierdest thing about this is that it only seems to do it sporadically, which makes recreating it almost impossible. Although it seems most frequent at work, but that maybe because I spend an ungodly amount of time at my office.
*Lag/freezes
I know its not gonna work perfectly all the time and sometimes you have to reboot your phone just to give it a chance to reset itself and that's cool but when you do that and it doesn't fix the sluggishness of the phone then I feel there is a problem.
* problems with certain system functions like Bluetooth or GPS
Now this may be only an issue with particular Roms which may be known to have problems with certain aspects of the system. For instance, it seems pretty common from what I've seen on the forums that GPS is an issue for some on 4.2. I was actually on 4.2 this morning until I went to punch in an address from a text msg to Navigation and it wouldn't lock on my location. I got frustrated and decided to wipe and install the AOKP milestone I had saved and when I set everything back up guess what? Navigation still wouldn't lock on. I ended up having to bail out on some guys because I could find there house. I got home and found a stock ROM online. I wiped, flashed and setup my phone for the second time today. I downloaded Maps and immediately went to find the address and it was insane how fast it locked on a location.
There are other issues but I'm becoming long winded so I'll try to wrap it up.
Now I'm not one to dismiss my own part in my problems. I've certainly tried to address them when/if they arise with what little knowledge I have and the ability to learn what I can. I e emailed devs amd talked to others and sometimes it helps, but sometimes like this morning you just want things to work when you need them to without wasting your time having to revert to a nandroid or doing some other wizardry.
"Well, why don't you just go buy an iPhone then?" you might say
I've actually contemplated it but I do really like android, Google Maps are the **** (I depend on Navigation a lot )and I like to be able to customize. And I also don't really want to pay the money to terminate my contract so I'm kinda just stuck. But I thought about doing one thing.
A couple weeks ago, I unrooted and relocked my phone and flashed stock images for JB on CDMA and from there all I did was unlock and root keeping it stock and I tell you I glad I did because all my problems no longer seem to exist. My battery life might not be what I was getting on 4.2 these last couple days but I think I'm willing to stick with this for now until Verizon gets off their ass and pushes an update to us.
I'm not trying to rant to the Dev community or complain that y'all aren't living up to my satisfaction. Hell, maybe somebody might have a solution I haven't tried yet. I'm just putting this out there in case someone was having the same trouble and could get some help.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
I'm with this guy as well... I upgraded to a stock 4.2 rom (with root, but not a custom build).. and I have been smooth sailing since. It seems with all these custom roms and kernels there are nothing but issues. Sure, they're a TAD faster or offer little tweaks but when you need to use your device in the real world and it f*cking reboots while navigating somewhere because of a stupid tweak you made.. well, I can't see why it's even needed.

This phone runs very well with Stock+Root. I normally root devices because of different apps I like to use, and the ability to make custom backups...but I dont normally try anything bleeding edge...lol.
Partly because of my experience on an HTC phone...hated Sense and bought the GNex because of the AOSP.

akira02rex said:
I'm with this guy as well... I upgraded to a stock 4.2 rom (with root, but not a custom build).. and I have been smooth sailing since. It seems with all these custom roms and kernels there are nothing but issues. Sure, they're a TAD faster or offer little tweaks but when you need to use your device in the real world and it f*cking reboots while navigating somewhere because of a stupid tweak you made.. well, I can't see why it's even needed.
Click to expand...
Click to collapse
No need to bash the custom roms that some devs here work so hard to make, i agree that stock is amazing but android would be a boring scene without the custom roms out there
We would just be like Ios, Wp and blackberry users, stuck with what we've got
Others wouldnt even have the chance to use a newer OS version because their phone has been abandoned by official support.
Or many of u guys would have crappy colors or other issues that custom roms and kernels DID fix
I use stock but i love the fact that there are custom roms around
Sent from my Galaxy Nexus using Tapatalk 2

negrobembon said:
No need to bash the custom roms that some devs here work so hard to make, i agree that stock is amazing but android would be a boring scene without the custom roms out there
We would just be like Ios, Wp and blackberry users, stuck with what we've got
Others wouldnt even have the chance to use a newer OS version because their phone has been abandoned by official support.
Or many of u guys would have crappy colors or other issues that custom roms and kernels DID fix
I use stock but i love the fact that there are custom roms around
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No I get that, it's good to see support for older devices but c'mon have you counted the amount of 4.1.2 roms that are available for the gnex? If I build android I'm automatically called a developer? Because that's the way it seems here...

I don't know why people keep bringing up the so crappy colors. In reality, the crappy colors are the ones custom ROM offer.
Sent from my Galaxy Nexus using xda premium

Soldier 2.0 said:
I don't know why people keep bringing up the so crappy colors. In reality, the crappy colors are the ones custom ROM offer.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
its the kernels that offer the colors(the kernels that the ROM developers include too). of all the kernels available, only a very few distinguish themselves from the stock crappy colors.

This is ridiculous... who obligated you to install a custom ROM? F*cking emos.
Sent from my Galaxy Nexus using xda premium

automaddux said:
I've suspected for a long time that custom ROMs have been the source of all my...
Blah blah blah.....
Click to expand...
Click to collapse
No, please stay! We'll never survive without you! [/SARCASM]

GhoXt said:
This is ridiculous... who obligated you to install a custom ROM? F*cking emos.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Alright Captain, you keep Franco deep in your throat.
Sent from my Galaxy Nexus using xda premium

Knowledge is power

There is a lot of fear going around with people worried about bootlooping. I think it would be good to get some rough idea of what the chances are for this to occur through at least one means. So I want to find out just how many people this is effecting and how many (here) it is not.

I've rooted and flashed darthstalker on 3 different note 3's also upgraded them to v2 and no issues here. I read everything I needed on twrp, flashing, and not restoring.
All 3 devices are doing exceptionally well.
Sent from my SM-N900T using xda app-developers app

elracing21 said:
I've rooted and flashed darthstalker on 3 different note 3's also upgraded them to v2 and no issues here. I read everything I needed on twrp, flashing, and not restoring.
All 3 devices are doing exceptionally well.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Why not vote on the poll? Also have you restored?

I've flashed numerous times on my Note and never had any boot looping issues. Just followed the steps and all is well.
Sent from my SM-N900T now Free

Restoring nandroid works for me
I did a nandroid backup from my darthstalker v2 rom. Then after that I was using the phone one day and my signal went out on the phone and never come back on. I put the phone back to stock and took it to tmobile ( which tmobile never checked the bootloader to see if the knox counter was tripped ). The realized the phone was defective and gave me a brand new one. I got home and rooted the device. After that I backed up the current rom and moved the nandroid back up of darthstalker v2 to the new folder location. I installed darthstalker v2, I then did a factory reset, wiped system, cache, and dalvik cache. After that I restored the nandroid back up only restoring the system and data. The rom loaded right up and I have no problems whatsoever. All this was on the latest twrp I installed from the goomanager app. Seems that restoring nandroids is working just fine in my case.

I wonder if anyone with the boot loop restored only system and data...

I'm thinking that restoring more than those two options may play a role in this.
sgh-TWEAKED-889©

Warrior1975 said:
I'm thinking that restoring more than those two options may play a role in this.
sgh-TWEAKED-889©
Click to expand...
Click to collapse
maybe because the other people getting boot loops from doing TB restores and that has to do with data right?, only thing i believe they can recover but we couldn't. I got my new note after giving up yesterday and i wont be the one to try that theory lol.

stress1ner said:
maybe because the other people getting boot loops from doing TB restores and that has to do with data right?, only thing i believe they can recover but we couldn't. I got my new note after giving up yesterday and i wont be the one to try that theory lol.
Click to expand...
Click to collapse
Haha same here...
Sent from my SPH-L900 using Tapatalk 2

I've flashed a stock deodexed rom and both versions of Darthstalker. Restored data only w/TWRP every time w/no bootloops whatsoever. Still probably gonna play it safe & just do TB restores until they figure out exactly what's causing all this though.

HughesNet said:
There is a lot of fear going around with people worried about bootlooping. I think it would be good to get some rough idea of what the chances are for this to occur through at least one means. So I want to find out just how many people this is effecting and how many (here) it is not.
Click to expand...
Click to collapse
Knowledge is power, so know this..
DO NOT RESTORE A BACKUP, PERIOD, END OF STORY.
I'm going to attribute this issue to the Knox security Samsung decided to include on the Note 3. I am of the opinion that whether it be the Knox container, partition, security issue, it could have been avoided by Samsung offering Knox related security to people who want it, not just including it on every device sold to the masses, most of which could care less about toting around top secret documents on their devices used mostly for social entertainment.
Just a poor decision in my opinion, which they're going to realize shortly, or already have. Reason being the pending release of a "Developer's" version of the Note 3..
Sent from my SM-N900T using XDA Premium 4 mobile app

Steve Lazarus said:
Knowledge is power, so know this..
DO NOT RESTORE A BACKUP, PERIOD, END OF STORY.
I'm going to attribute this issue to the Knox security Samsung decided to include on the Note 3. I am of the opinion that whether it be the Knox container, partition, security issue, it could have been avoided by Samsung offering Knox related security to people who want it, not just including it on every device sold to the masses, most of which could care less about toting around top secret documents on their devices used mostly for social entertainment.
Just a poor decision in my opinion, which they're going to realize shortly, or already have. Reason being the pending release of a "Developer's" version of the Note 3..
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I can promise you one thing Steve I will not considering I was the first one to have a boot looping note 3. I don't want to see that happen again.
Sent from my SM-N900T using Tapatalk 4

Steve Lazarus said:
Knowledge is power, so know this..
DO NOT RESTORE A BACKUP, PERIOD, END OF STORY.
I'm going to attribute this issue to the Knox security Samsung decided to include on the Note 3. I am of the opinion that whether it be the Knox container, partition, security issue, it could have been avoided by Samsung offering Knox related security to people who want it, not just including it on every device sold to the masses, most of which could care less about toting around top secret documents on their devices used mostly for social entertainment.
Just a poor decision in my opinion, which they're going to realize shortly, or already have. Reason being the pending release of a "Developer's" version of the Note 3..
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Stuff is pretty easy to remove either way. Typical carrier stunt. Nothing new.
This only proves the point that if you are incapable of diagnosing issues on your own, you shouldn't be messing with core related system apps, messing around with beta-ish recoveries, etc. Root and leave it alone if you don't know what you are doing.
And titanium backup is terrible. Most users I see that have problems with boot looping, force closes, etc... Are causing the issue. Hard to believe the device randomly decided to start having issues on its own.

d474corruption said:
This only proves the point that if you are incapable of diagnosing issues on your own, you shouldn't be messing with core related system apps, messing around with beta-ish recoveries, etc. Root and leave it alone if you don't know what you are doing.
Click to expand...
Click to collapse
If that was the case, xda would be a very quiet place.
Sent from my SM-N900T using Tapatalk 4

d474corruption said:
Stuff is pretty easy to remove either way. Typical carrier stunt. Nothing new.
This only proves the point that if you are incapable of diagnosing issues on your own, you shouldn't be messing with core related system apps, messing around with beta-ish recoveries, etc. Root and leave it alone if you don't know what you are doing.
And titanium backup is terrible. Most users I see that have problems with boot looping, force closes, etc... Are causing the issue. Hard to believe the device randomly decided to start having issues on its own.
Click to expand...
Click to collapse
I agree and disagree.. If we were to live by your motto, Google and Android development wouldn't be where they are now. The end user has doors open in front of them once they root for the first time, or flash their first custom ROM, and from there the imagination starts working it's magic.
Some first time rooters / modders go on to become great application developers due to the unfounded landscape they discover once they delve into writing code.. It's not rocket science to root, flash, tweak, mod. However, it does get tricky once a manufacturer makes a device with features that create problems doing the most menial of things. Knox was put on a device sold to the masses, which as stated, most of which could care less about toting around top secret documents, as compared to checking Facebook, email, YouTube, their favorite sites and forums.
The end user needs to do their research before just tossing themselves into the fire . But as we've seen thus far regarding this issue, even developers are still trying to figure it out. Most dev's encourage the end user to actually understand what the cause and effect of what it is they're doing. Also how they (the end user) can do the same thing with a different outcome using an alternative route, code etc..
You start alienating people from this process, we all suffer.
Sent from my SM-N900T using XDA Premium 4 mobile app

kabuk1 said:
I've flashed a stock deodexed rom and both versions of Darthstalker. Restored data only w/TWRP every time w/no bootloops whatsoever. Still probably gonna play it safe & just do TB restores until they figure out exactly what's causing all this though.
Click to expand...
Click to collapse
They just did. Apparently TWRP doesn't restore the EFS partition properly, causing a bootloop. If you don't restore the EFS partition, you'll be fine (which you would never have to do anyway unless you somehow blew up your IMEI and modem configuration).