Related
Hello guys I was just wondering if this ACS root method, being the first root attempt is official? After reading through the xda threads for this root im seeing a lot of people seem to be having issues... Thanks!
Sent from my Epic Touch 4G using xda premium
Great question. I am holding off on mine till I see more work out.
dcraig723 said:
Hello guys I was just wondering if this ACS root method, being the first root attempt is official? After reading through the xda threads for this root im seeing a lot of people seem to be having issues... Thanks!
Sent from my Epic Touch 4G using xda premium
Click to expand...
Click to collapse
The only issue people seem to be having are issues that I have, unrooted. Though it seems to be to varying degrees of annoyance.
Sent from my SPH-D710 using XDA App
I haven't seen a method yet that is stable enough for me to make the move. Also want to see a clean unroot backout before biting. Glad to see the progress but am holding off.
xenokc said:
I haven't seen a method yet that is stable enough for me to make the move. Also want to see a clean unroot backout before biting. Glad to see the progress but am holding off.
Click to expand...
Click to collapse
This is the only thing I'm waiting on.
Sent from my SPH-D710 using XDA App
My opinion and my opinion only:
I rooted my phone the second zedo posted his first kernel. Overall it was running good. At first I thought the issues people were having with loss of signal and data lock were due to the root but have since seen unrooted phones have the same issue. I however never got the LOS or data lockup.
Yesterday I returned my phone for a new one and have not rooted it. I still havent had LOS or data lockup but what I do notice is SIGNIFICANT battery improvement over being rooted.
Rooted battery at best was draining 6% an hour. More often was average of 1o% hour. Battery after battery calibration lasted 14 hours
Unrooted battery as of this minute is draining 2% an hour. This battery should be on par to last over 2 days but realistically will be over a day Im sure.
So my personally opinion is dont root till a) theres a way out and b) it doesnt require a kernel push. Something just doesnt seem right having to replace a kernel to achieve root. Never had to do that before and dont plan on doing it again.
Also, get a usb jig before rooting to avoid the triangle splash screen and counter.
dcraig723 said:
root [...] is official
Click to expand...
Click to collapse
"Official Root" ... ROFL
Yes, samsung released official root yesterday.
In all seriousness though, root is no longer experimental when it is reversible. At the moment, it is not.
Sent from my SPH-D710 using Tapatalk
kingsway8605 said:
Yes, samsung released official root yesterday.
Click to expand...
Click to collapse
What are you talking about? Link?
xak944 said:
What are you talking about? Link?
Click to expand...
Click to collapse
Lord help me
....
Ok I am using Zedomax's V2, which is the overclockable Kernel with root and CWM. After flashing I did the Data reset which involves the ##...# code listed in the forums. My phone is rooted, overclocked, and running flawless. Most of the issues, other than the data loss(fixed with the data reset), are due to people doing things they shouldnt do... Like doing a factory reset in CWM without having a rom to flash afterward. This is what is causing the bootloops. If you follow the directions and dont get too ambitious you will be fine. That being said... if you are concerned then just wait until we get the stock tar so that if you do mess up while flashing anything you can flash right back to stock. Personally I believe most of the issues are user error.
Vegasden said:
Lord help me
....
Click to expand...
Click to collapse
Thank you for your incredibly helpful post.
Are you talking about the source code that Samsung recently released?
He was speaking sarcastically.. Samsung obviously did not release an "official" root.
xak944 said:
Thank you for your incredibly helpful post.
Are you talking about the source code that Samsung recently released?
Click to expand...
Click to collapse
Devi0124 said:
He was speaking sarcastically.. Samsung obviously did not release an "official" root.
Click to expand...
Click to collapse
Thats like apple releasing a jailbteak lmao
Sent from my SPH-D700 using xda premium
I would wait until there is a way to go back to stock. Then u could try. In reality though we should be flashing a custom recovery and not a Complete kernel. Then for root u flash the su.zip. then you can flash a custom rom/kernel or stay stock with root.
The Evo3D Killer!!!
Is root ready? Signs say no
^^^normal font just didnt carry the same effect for ya or something?
musclehead84 said:
In reality though we should be flashing a custom recovery and not a Complete kernel. Then for root u flash the su.zip. then you can flash a custom rom/kernel or stay stock with root.
The Evo3D Killer!!!
Click to expand...
Click to collapse
Exactly the way it should be done. I learned my lesson about rushing to get this thing unlocked. Sometimes being first doesnt mean being right
Ok so I have my galaxy s3 att version rooted with faux's kernel on the stock rom. I havent received any updates since the original purchase and my battery life is suffering bad due to the cell standby problem (don't know how common it is) and is taking up ALOT of battery during the day. I need to get my phone up to the latest update so I can resolve this annoying problem. I leave it on standby doing absolutely nothing at all for 7 hours everyday and is always at %40 left starting off with %100. I dont know the process I need to do to update my phone to the latest and not lose all of my stuff and also be able to have it rooted on the latest update. Also a noob question but does it matter what version your on as far as how you root it? I would assume so but I dont know, and to clarify I mean like will only certain methods work on certain firmware versions?
I have a few questions for you? Are using the most up to date faux kernel?
What do you mean by leaving your phone on standby? Screen off and leaving it alone or something else.
Try something for me. Is your phone deep sleeping? Download an app called cpu spy and see if your getting deep sleep? Then report back.
Sent from my SGSIII with the XDA Premium App
Are you on AT&T, or Telus, rogers, bell? If at&t you could flash this http://forum.xda-developers.com/showthread.php?t=1844605
through CWM. Its the latest Stock rooted AT&T leak uclah1 for the at&t s3..
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Bruce Lee said:
I have a few questions for you? Are using the most up to date faux kernel?
What do you mean by leaving your phone on standby? Screen off and leaving it alone or something else.
Try something for me. Is your phone deep sleeping? Download an app called cpu spy and see if your getting deep sleep? Then report back.
Sent from my SGSIII with the XDA Premium App
Click to expand...
Click to collapse
Ok I'm pretty sure my kernel is latest to day. By standby I mean it's on but I don't use it like you first mentioned and the screen is off and I don't do anything with it ever day for around 7 hours. I just downloaded the cpu spy and it says I am not getting deep sleep at all!
For the other post I'm gonna download that and flash it and see if it helps
rcklss1 said:
Are you on AT&T, or Telus, rogers, bell? If at&t you could flash this http://forum.xda-developers.com/showthread.php?t=1844605
through CWM. Its the latest Stock rooted AT&T leak uclah1 for the at&t s3..
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I downloaded and flashed that at stock update but there is only one problem. All my apps that require root are saying I don't have root access. I dot know what to do but that's the only problem and I need to know if I need to root it again and if so would it be the same method I did on the last firmware version I was on. And also just for more Info I still have cwm recovery too.
XxTyboxX said:
I downloaded and flashed that at stock update but there is only one problem. All my apps that require root are saying I don't have root access. I dot know what to do but that's the only problem and I need to know if I need to root it again and if so would it be the same method I did on the last firmware version I was on. And also just for more Info I still have cwm recovery too.
Click to expand...
Click to collapse
Try rebooting. Worked for me. Root came back.
Sent from my Transformer TF101 using XDA Premium App
Didn't work rebooted multiple times too
Flash the attached file in this post in CWM. This is the method I used when I first tested the H1 leak. You'll have your root access again once you reboot after flashing.
Uncle Irish said:
Flash the attached file in this post in CWM. This is the method I used when I first tested the H1 leak. You'll have your root access again once you reboot after flashing.
Click to expand...
Click to collapse
Thanks so much it gained root back!
rock on :highfive:
and for what its worth, good post on the issue you were having. I wish others would try to explain what's going on like you did. Makes it easy to help.
Uncle Irish said:
rock on :highfive:
and for what its worth, good post on the issue you were having. I wish others would try to explain what's going on like you did. Makes it easy to help.
Click to expand...
Click to collapse
Haha thanks, glad I could help you help me lol?:silly:
You don't know what u r talking about. The cell standby issue was just an incorrect value that caused it to report higher usage than actual. It had NO effect whatsoever in actual battery usage.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
lgkahn said:
You don't know what u r talking about. The cell standby issue was just an incorrect value that caused it to report higher usage than actual. It had NO effect whatsoever in actual battery usage.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I have an s3, my brother has an s3. Same exact phone. I hadn't updated mine at all, my brothers was up to date. We both go to school and font ever use it because we obviously aren't allowed to and at the end of the day I always have around %40 and he has about %75-80. Please explain to me when it says that, and under battery usage that cell standby used some %80 of my battery drainage that wasn't a cell standby issue.
Different batteries or more likely you have an ap running or poor signal or different settings than him. I have about 5 batteries all stock and some last better than others
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
I have a Samsung Galaxy SIII from AT&T (d2att ), and I have it rooted, running task650's AOKP, and TWRP 2.4.1.0 for recovery. It works fantastic, and I love it I have, however, been trying everything I can think of to try and get ktoonsez's kernel to work on it, for the features that his kernel offers. I am having a funky issue, which according to task, kt, and a few others on the boards, is device-related. It seems that my phone, individually, is the problem. This leads me to my question.
How feasible is it to get AT&T (or Samsung?) to replace my phone, based on the fact that there is something different hardware-wise between mine and the vast majority of other peoples?
It seems that nearly everyone who runs this combination of task and ktoonsez has nothing but good things to say, and I have yet to see anyone gripe about the same issues that I have had, and not be able to fix them, usually by a simple full wipe. I have tried to do full wipes with and without letting Google initialize/restore my account. I have tried going back to stock everything, and trying again. I have made sure to turn off Performance Control, so there should be no conflict there. I have tried setting up my phone in its entirety, restoring information, restoring apps with TiBu, and then installing the kernel. I have tried with and without deleting mpdecision. I am following all of the directions posted per OP for both threads, and with the gapps posted by task himself. Nothing works, and I end up in a glitchy boot loop almost immediately after flashing the kernel, even if my phone was running buttery stable before the flash.
I have come up with a couple things to try tonight, but if they don't work, I would like to pursue getting a new phone to replace this one. Is that an option?
You will need to do a warranty replacement through Samsung unless you have device insurance through att. But then you will be paying the deductable on it.
There are quite a few reports of people in ktoonsez's thread that stated they had to return their device and get a new one for his kernel to work. Not sure you searched good enough. But either way, you are not the first to have a device that cant run his kernel. I can assure you of that.
task650 said:
You will need to do a warranty replacement through Samsung unless you have device insurance through att. But then you will be paying the deductable on it.
There are quite a few reports of people in ktoonsez's thread that stated they had to return their device and get a new one for his kernel to work. Not sure you searched good enough. But either way, you are not the first to have a device that cant run his kernel. I can assure you of that.
Click to expand...
Click to collapse
Thank you. I may not have read it well enough Do you mean the deductible through Samsung or AT&T? And ho do I approach the warranty? I know, at least where I work, we wouldn't honor a warranty on something that was used for purposes outside of it's intended use (i.e. rooting). Granted, I don't work for a phone company
drinfernoo said:
Thank you. I may not have read it well enough Do you mean the deductible through Samsung or AT&T? And ho do I approach the warranty? I know, at least where I work, we wouldn't honor a warranty on something that was used for purposes outside of it's intended use (i.e. rooting). Granted, I don't work for a phone company
Click to expand...
Click to collapse
It would be the deductible through AT&T if you have device insurance. If going through Samsung, something would have to be a manufacturers defect in order for them to warrant a replacement device. I don't think either company will replace the device because you can't use a custom kernel. So you would need to get creative on your story before you go either route.
task650 said:
It would be the deductible through AT&T if you have device insurance. If going through Samsung, something would have to be a manufacturers defect in order for them to warrant a replacement device. I don't think either company will replace the device because you can't use a custom kernel. So you would need to get creative on your story before you go either route.
Click to expand...
Click to collapse
Time to get creative lol
Sent from my SGH-I747 using xda app-developers app
Settling In
I don't know if this could be a factor but, you will experience something commonly called a settling in period after installing a new kernel.
I have been through trying a couple other custom kernels for I747 plus all the progression of KT747 releases for TW ICS and TW JB since 9-23 release and have been through two phones due to warranty replacement. On both phones I have experienced significant settling in glitches for a while after flashing KT's or other kernels. These include crashing on boot, frequent screen freezes after boot, KTweaker settings not sticking, etc. These issues are far more extreme on first install of kernel than when flashing a new release to phone that already has kernel installed. First boot after first install can take about twenty problematic boot attempts to start behaving and it can take two or three days before kernel "settles in" and problems pretty much disappear.
In my feeble little mind, I envision the new kernel having to grow neurons into the guts of the phone hardware.
If you want to run this kernel and your phone will basically boot but, is all glitchy, I would say don't freak out. Have some patience, just keep rebooting, and give it time to settle in. For most the phone will straighten out in a few days.
Hope this helps.
bsam55 said:
I don't know if this could be a factor but, you will experience something commonly called a settling in period after installing a new kernel.
I have been through trying a couple other custom kernels for I747 plus all the progression of KT747 releases for TW ICS and TW JB since 9-23 release and have been through two phones due to warranty replacement. On both phones I have experienced significant settling in glitches for a while after flashing KT's or other kernels. These include crashing on boot, frequent screen freezes after boot, KTweaker settings not sticking, etc. These issues are far more extreme on first install of kernel than when flashing a new release to phone that already has kernel installed. First boot after first install can take about twenty problematic boot attempts to start behaving and it can take two or three days before kernel "settles in" and problems pretty much disappear.
In my feeble little mind, I envision the new kernel having to grow neurons into the guts of the phone hardware.
If you want to run this kernel and your phone will basically boot but, is all glitchy, I would say don't freak out. Have some patience, just keep rebooting, and give it time to settle in. For most the phone will straighten out in a few days.
Hope this helps.
Click to expand...
Click to collapse
I suppose that is possibly what's going on with mine, I'll give it a couple more tries
Sent from my SGH-I747 using xda app-developers app
Just an advice, make sure you restore everything to stock before you do
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
pcshano said:
Just an advice, make sure you restore everything to stock before you do
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I will be doing that In the meantime, any suggestions for how to explain my way into a warranty exchange? I thought about wiping everything, so it won't even boot, and saying that lol
Also, even if I flash back to stock, won't they be able to see that it had been flashed different before?
Sent from my SGH-I747 using xda app-developers app
drinfernoo said:
I will be doing that In the meantime, any suggestions for how to explain my way into a warranty exchange? I thought about wiping everything, so it won't even boot, and saying that lol
Also, even if I flash back to stock, won't they be able to see that it had been flashed different before?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Just depends on how thorough the at&t rep is. You have to Odin back to stock, triangle away, unroot and factory reset for them not to know at all.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
drinfernoo said:
I will be doing that In the meantime, any suggestions for how to explain my way into a warranty exchange? I thought about wiping everything, so it won't even boot, and saying that lol
Also, even if I flash back to stock, won't they be able to see that it had been flashed different before?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Do not intentionally brick your device. That could be just as bad as leaving your phone rooted when you take it in (depending if Samsung can see any part of the storage). As far as warranty exchange "excuse" that is on you to decide. Follow the post quoted below to help your chance at warranty exchange. This has been discussed quite a bit all over the place.
hednik said:
Just depends on how thorough the at&t rep is. You have to Odin back to stock, triangle away, unroot and factory reset for them not to know at all.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
You know, I've run tasks rom since it was still 4.1 and have always used the kernel provided in his rom. It runs great, and I wouldn't change it. My battery life and everything else is great. I can get 17 hrs with 3 hrs 34 mins screen time and have 20% battery left. I think trying to get a replacement device just to run a different kernel is absurd... just my .02 cents worth
Sent from my SGH-I747 using xda premium
G-Man. said:
You know, I've run tasks rom since it was still 4.1 and have always used the kernel provided in his rom. It runs great, and I wouldn't change it. My battery life and everything else is great. I can get 17 hrs with 3 hrs 34 mins screen time and have 20% battery left. I think trying to get a replacement device just to run a different kernel is absurd... just my .02 cents worth
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I completely agree. I'm on tasks currently using his underwear kernel provided. I've also tried KT's kernel as well. Yes you can get more customization with KT's and his custom governor, but is it worth it to go through all the hassle to get a new device? I would say no. Like I said I've tried both kernels, I'm currently using tasks underwear kernel, I may try KT's again, may not. When I did before, I didn't notice a drastic difference between the two, esp not enough to warrant going through a device replacement.
Consider this. You are running tasks rom with absolutely no issues with the kernel he provides. Is that not good enough? I know it is for me. His rom is absolutely the most stable rom I've ever tried on any device. Remember it's just a phone. Just some food for thought.
Sent from my SGH-I747 using xda app-developers app
Probably right, but i don't always run task's ROM, either. My favorite ROM so far has actually been ParanoidKANGDroid, but I wanted 4.2.1, so I went to task. I'm actually running PACman right now, and for the time being, even his PC is broken
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
No matter which rom you are running, it's crazy to exchange a device (and having to lie to do it) just to run a different kernel... think about it...
Sent from my SGH-I747 using xda premium
G-Man. said:
No matter which rom you are running, it's crazy to exchange a device (and having to lie to do it) just to run a different kernel... think about it...
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Of course, but if it allows me more flexibilities and control over my phone and what it does, I'm all over that
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Bricking your phone would be the easiest way to get a new one and I've seen plenty of people accidentally bricking their i747 and getting a new one from Samsung. They won't even check if its rooted or not.
Check this thread: http://forum.xda-developers.com/showthread.php?p=34556189
Sent from my SGH-I747 using xda app-developers app
liltitiz said:
Bricking your phone would be the easiest way to get a new one and I've seen plenty of people accidentally bricking their i747 and getting a new one from Samsung. They won't even check if its rooted or not.
Check this thread: http://forum.xda-developers.com/showthread.php?p=34556189
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
That's a douche bag move.... pain and simple.
Sent from my SGH-I747 using xda premium
G-Man. said:
That's a douche bag move.... pain and simple.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
When the s3$ first come out, a lot of people were bricking them. Trying to root or installing an international ROM. I'm pretty sure Samsung staff was aware of that but they still gave free replacement. Some people even got a replacement from att or others carriers for free.
Sent from my SGH-I747 using xda app-developers app
If I do end up getting a replacement, can I take a nandroid, and restore it to the new phone?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Yesterday I made the mistake of taking the OTA update to 4.3 while in the process of doing a clean install of the new MOAR rom. Unfortunately, I had failed to do the proper homework otherwise I would have known to avoid the update like the plague. Luckily, I didn't manage to brick my phone, by trying to revert back to an earlier bootloader, but I am stuck now with a tripped warranty bit, and a phone that drains battery at almost 1% per 5mins while being almost completely unable to maintain a cell or data signal.
Now, I know it's going to be a little time before devs have a chance to tear apart 4.3 to fix it's issues, but I'm hoping that I can get some guidance on how I might improve my phone's performance, or at least minimize the negative aspects of the new update in the meantime. Right now I am running MOAR 7 and I have already tried resetting and reinstalling the rom fresh.
Thanks for any help.
Sent from my GT-N8013 using xda app-developers app
treblesum81 said:
Yesterday I made the mistake of taking the OTA update to 4.3 while in the process of doing a clean install of the new MOAR rom. Unfortunately, I had failed to do the proper homework otherwise I would have known to avoid the update like the plague. Luckily, I didn't manage to brick my phone, by trying to revert back to an earlier bootloader, but I am stuck now with a tripped warranty bit, and a phone that drains battery at almost 1% per 5mins while being almost completely unable to maintain a cell or data signal.
Now, I know it's going to be a little time before devs have a chance to tear apart 4.3 to fix it's issues, but I'm hoping that I can get some guidance on how I might improve my phone's performance, or at least minimize the negative aspects of the new update in the meantime. Right now I am running MOAR 7 and I have already tried resetting and reinstalling the rom fresh.
Thanks for any help.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
If you're on MOAR, then your battery issues are not being caused because you tripped the warranty and flashed the OTA. You may flash any rom, mod, kernel, tweak, etc, you want through CWM, just don't try to downgrade to a different bootloader(ie 4.1.2), through Odin, or you'll brick. Try different roms, modems, combinations, just like before, until you get back to what you want. Good luck
Sent from my SPH-L710 using Tapatalk
So I can reflash the MD4 modem? I was under the impression that I was stuck with MK3. Can I basically change anything I want as long as I don't try to Odin in an older update?
Sent from my GT-N8013 using xda app-developers app
treblesum81 said:
So I can reflash the MD4 modem? I was under the impression that I was stuck with MK3. Can I basically change anything I want as long as I don't try to Odin in an older update?
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
Yes, you can flash the MD4 modem, but I tried flashing down to a 4.1.2 modem and lost data, so that may happen to you(probably will). And as long as you flash from cwm you are fine. But read any ROM OPs very carefully, because there are a few out there that flash a bootloader if I'm not mistaken. But overall, yes, you are ok flashing as long as you don't use Odin to try to downgrade to a different bootloader.
Sent from my SPH-L710 using Tapatalk
Well, I guess its good to know that I have some options, but also disappointing that I can't just Odin in a complete package to start from, since in the past that has always been the best way to ensure stability in the end result. As for the warranty bit, I'm not too worried about it, since it can only really hurt me if I need to take it to sprint for some work. That being said, if there really is no way to reset it, or completely remove Knox for that matter, I probably won't be buying another samsung phone... I really don't like the idea that the manufacturer would booby trap their product like that.
Sent from my GT-N8013 using xda app-developers app
treblesum81 said:
Well, I guess its good to know that I have some options, but also disappointing that I can't just Odin in a complete package to start from, since in the past that has always been the best way to ensure stability in the end result. As for the warranty bit, I'm not too worried about it, since it can only really hurt me if I need to take it to sprint for some work. That being said, if there really is no way to reset it, or completely remove Knox for that matter, I probably won't be buying another samsung phone... I really don't like the idea that the manufacturer would booby trap their product like that.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
I'm sure it's only a matter of time before someone cracks it. Genius devs like @Chainfire live for challenges like this
Sent from my SPH-L710 using Tapatalk
I hope they crack it soon.. I've already had the urge to throw it against a wall more than once today. Its magically unrooted itself three times already and the problems seem to multiply every time I try a different OS in the hopes that one will work well.
Sent from my GT-N8013 using Tapatalk
I'm currently on 4.3 stock rooted 0x0 flag. I'm curious about KK but heard about a HUGE flaw with apps not able to write to external sd card...Therefore rendering them practically useless.
I'm assuming I shouldn't update ota and instead flash. But what will I need? And has the sd card issue been fixed?
I'm just looking for something more stable and a little slicker. Would like to stay tw or stock/ stock debloated.
Sent from my SM-N900T using XDA Premium 4 mobile app
Since you haven't pulled the trigger yet, like me, I would hold off a little longer and wait to see what 4.4.3 brings us. It is just rumored right now but it is supposed to be a bug fix release. From what I have gathered, you really aren't missing anything big by not being on KitKat. I have had the itch to go ahead an upgrade too but I am going to wait to see when 4.4.3 is likely to hit us first.
in my humble opinion....
NO!!!!!!!!
So if I get any urges to want to change things up I should stay on 4.3?
I'm still debating breaking knox or not. I never plan to use knox and haven't decided if I plan to trade this in for jump or not. I'm loving the battery life and have no gripes but minor hiccups.
Sent from my SM-N900T using XDA Premium 4 mobile app
Naturesretard said:
I'm curious about KK but heard about a HUGE flaw with apps not able to write to external sd card...Therefore rendering them practically useless.
Click to expand...
Click to collapse
If you root KK, there is an SD fix. Otherwise don't.
krelvinaz said:
If you root KK, there is an SD fix. Otherwise don't.
Click to expand...
Click to collapse
Why are people telling me not to then? I thought the sd issue was the only issue with KK
Sent from my SM-N900T using XDA Premium 4 mobile app
A lot of people are having problems with KK. If they have rooted, the SDcard issue is not one of them since there is a fix for it. if you don' t have root, then it is a problem with no fix.
I'm one of the minority. Rooted Stock 4.42 with no real issues. Battery is fine, SDcard is fine, WiFi is good etc...
Oh so those got it pre installed have issues but those who flash while rooted are fine.
Would you say you notice any stability or noteworthy features over 4.3?
Sent from my SM-N900T using XDA Premium 4 mobile app
Yes. Absolutely no problems on stock rooted KK. Flash wicked and its even better.
Sent from my SM-N900T using xda app-developers app
Naturesretard said:
Oh so those got it pre installed have issues but those who flash while rooted are fine.
Would you say you notice any stability or noteworthy features over 4.3?
Click to expand...
Click to collapse
I didn't say that.
I was rooted before on 4.43 however, keeping root was not an option when I did the update. I used Odin to flash 4.42 and re-rooted (triggered Knox), loaded the sdcard fix and loaded TWRP in the process.
I was not having any issues on 4.43 though. KK got me better battery usage and access to new software.
If you are rooted, you can apply the sdcard fix. If you are not rooted, I don't think there it's a fix for that.
krelvinaz said:
I didn't say that.
I was rooted before on 4.43 however, keeping root was not an option when I did the update. I used Odin to flash 4.42 and re-rooted (triggered Knox), loaded the sdcard fix and loaded TWRP in the process.
I was not having any issues on 4.43 though. KK got me better battery usage and access to new software.
If you are rooted, you can apply the sdcard fix. If you are not rooted, I don't think there it's a fix for that.
Click to expand...
Click to collapse
Since you are still on 4.3, you can easily root using Kingo or de la vega method without triggering knox.
After that, upgrading to 4.4.2 is very easy and you still have root and warranty.
If you don't care about knox, then you can just update and use Chainfire to root 4.4.2 (knox warranty void). It is pretty simple.
I have 4.4.2, root (from my previous rooted 4.3) and warranty intact + SD fix and xposed mods. The phone is just amazing now.
Thats Like Saying Should I Buy These New BOSS rims for my car HAVING the money.
Sent from my SM-G900T using Tapatalk
The only issues I've heard due to the kitkat update are terrible battery life and the SD card issue. There's a flashable zip to fix the SD card issue and I believe installing the Foldermount app does some kind of fix. The battery life issue seems to be fixed after a simple factory reset, however, you'd have to root the device like others have stated. My phone runs great on KK. I'm getting awesome battery life and I have not experienced any problems whatsoever.
You can get improved battery life on 4.3 by removing bloat, and there's no need to apply a fix so you can use the sdcard normally. Is there any real improvement in 4.4.2?
Frank
After a week of hearing about the problems I just went ahead and upgraded why? Who doesn't like to have the newest? Plus there are fixes if your rooted. If not well maybe you are screwed but who wouldn't want to root? Been doing it since OG evo 4G
Sent from my SM-G900T using Tapatalk
Does anyone have any issues recording video with KK? I updated the just the modem (running Slimkat) and can't record videos or sometimes can't play youtube videos in HD. It's not a rom issues. Might go to stock KK and than try reinstalling everything.
chuko303 said:
After a week of hearing about the problems I just went ahead and upgraded why? Who doesn't like to have the newest? Plus there are fixes if your rooted. If not well maybe you are screwed but who wouldn't want to root? Been doing it since OG evo 4G
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Funny, me too. I still have my og Evo 4g. Have you noticed any difference in battery life compared to 4.3? I have root and knox In-tact and apparently it's easy to upgrade...but I don't want worse battery life.
Sent from my SM-N900T using XDA Premium 4 mobile app
You won't have worse battery life bud. I'm pretty sure that will be rom and kernel related. Theirs like 4 to 5 kit Kat toms out their now. All good. All different, over in the international forum the rom that made me go to kitkat was XNOTE v11. Was a great rom but build international of course, hyperdrive is great one too good battery life I can't complain. Lean kernel will save the most battery
Sent from my SM-G900T using Tapatalk
Alright I'll have to do some digging and find a flash able rom...and finish my root by breaking knox finally and flashing a recovery.
As easy as it makes things, I'm worried to break knox. Not because of warranty. Lol I know tmo doesn't give 2 ****s about root...
My concern is when I want to sell the device, maybe retaining knox flag will help increase the price point.
This phone is a powerhouse. Easily able to last for the next few years until EoD. Throw In the obvious office features and a still working knox (albeit being able to be reset at samsung warehouses (I'd cite the info but I'm not in front of my desktop)) who wouldn't want this phone for work?
Thoughts?
Sent from my SM-N900T using XDA Premium 4 mobile app
mike102871 said:
Yes. Absolutely no problems on stock rooted KK. Flash wicked and its even better.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
I did the same but I am having issues with my network sticking on the new baseband. Do you have any issues Mike ? I feel like my phone goes to 4G / 3G more then what it did before. LTE was working before I jump to KK. Also when I got phone calls before, my network would go from LTE to 4g on calls. Now it goes to 3G. What is going on ????