Related
There seem to be a couple of different methods to get root over in the android dev sections for my T-mobile T999 ... Some trip the "counter" others do not.. some seem to flash an entire rom, while others seem to do it a different way? Not being a Android veteran - I'm just a little lost and wanted to ask for guidance to avoid a goof because I'm not certain of the terms and methods being used.
ANY HELP OR GUIDANCE WOULD BE APPRECIATED.
Simply stated: What is the best method for getting ROOT? I have a T-mobile T999 which is already sim unlocked.
I have not idea what the "counter" is, and why its important (if in fact, it is important?)
In a perfect world, I'd like to get root, cmw and superuser by using something like superoneclick which was the way I rooted my last device. Doesn't get much easier than hooking up the phone and clicking a button and waiting
WHY DO I WANT ROOT?
I want to be able to flash some of the cool themes I'm seeing, the snap picture with volume key mod, get rid of carrier iq, and uninstall (debloat) some of the useless factory apps installed on my stock rom, and I'm anxiously awaiting a working Jellybean rom which I have no doubt will be available sooner or later.
THANKS.
Araltd said:
There seem to be a couple of different methods to get root over in the android dev sections for my T-mobile T999 ... Some trip the "counter" others do not.. some seem to flash an entire rom, while others seem to do it a different way? Not being a Android veteran - I'm just a little lost and wanted to ask for guidance to avoid a goof because I'm not certain of the terms and methods being used.
ANY HELP OR GUIDANCE WOULD BE APPRECIATED.
Simply stated: What is the best method for getting ROOT? I have a T-mobile T999 which is already sim unlocked.
I have not idea what the "counter" is, and why its important (if in fact, it is important?)
In a perfect world, I'd like to get root, cmw and superuser by using something like superoneclick which was the way I rooted my last device. Doesn't get much easier than hooking up the phone and clicking a button and waiting
WHY DO I WANT ROOT?
I want to be able to flash some of the cool themes I'm seeing, the snap picture with volume key mod, get rid of carrier iq, and uninstall (debloat) some of the useless factory apps installed on my stock rom, and I'm anxiously awaiting a working Jellybean rom which I have no doubt will be available sooner or later.
THANKS.
Click to expand...
Click to collapse
Counter is a method used by Samsung to see if your phone has been modified. For example, in case you need to exchange your phone with your carrier or Samsung then they would check the counter. Your warranty will automatically be voided. If this is important to you, then i suggest using the rooting method without ticking the counter number. all the rooting methods are easy as pie, its just up to you which to use. I used the one with ticking the counter because it was the very first method. There should bea counter reset work around soon so I'm not too worried
Sent from my SGH-T999
I have read (<here> and <here>)
about new firmware versions that will not allow resetting the counter (warranty flag) to initial conditions when restoring to stock after after unlocking or rooting.
If the phone developed a hardware problem, warranty repair could be denied.
The firmware version "MGG" and beyond are reported to have this problem.
Questions:
Does this also apply to the m919 T-Mobile version?
Has anybody seen it on an m919?
Is it going out with an OTA update?
Or is MGG specific to the i9505?
I am shopping for a GS4 m919, and I want confirm that it has the "pre-MGG" firmware version before purchase.
Questions:
Is the ID contained in the "Baseband" ID string in the phone information?
Are there different identifier strings used on the M919?
The T-Mobile S4 has not received the KNOX Bootloader, it will most likely come with the 4.3 update. If anyone is on stock, I would recommend you guys disable OTA updates as you may get automatically updated to 4.3 with the KNOX bootloader.
for once...im dreading an update from tmobile
If I've already rooted and installed a custom recovery (Clockwork Mod), and nothing else, does anyone know if the 4.3 update with KNOX will still be usuable? In other words, will the phone still get an automatic OTA update and will that update install correctly?
Sent from my SGH-M919 using XDA Premium 4 mobile app
DigitalHeretic said:
If I've already rooted and installed a custom recovery (Clockwork Mod), and nothing else, does anyone know if the 4.3 update with KNOX will still be usuable? In other words, will the phone still get an automatic OTA update and will that update install correctly?
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It wont let you get the update it will pop a box up saying unable to uodate your device has been modified. . Try to check for an uodate youll see what im talking about... I went back to stock just to see if there was anything for updates which there wasnt andbwent to reroot and installed su abd it didn't flash correctly thru odin said to heck with it till the am checked for an update for giggles in the am and wouldn't even check
Sent from my SGH-M919 using Tapatalk
i'm glad I read this thread. i was going to wait until i tried the stock 4.3 update before deciding to root and install custom ROMs. With KNOX coming, I'm just going to root ASAP. I like PA on my Nexus4, so I'll probably go with that for my S4.
So you guys are saying the new update with "knox" won't allow you to reset the counter and only that or will it stop you from completely rooting and installing custom roms?
Sent from my SGH-M919 using Tapatalk
futty said:
So you guys are saying the new update with "knox" won't allow you to reset the counter and only that or will it stop you from completely rooting and installing custom roms?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Let me clarify some things. The KNOX processes and functions are already on the stock ROM, most devs remove them, though. So many of you with custom ROMs haven't seen anything related to KNOX.
What the new T-Mobile update (when it gets pushed out) is most likely to come with is a "KNOX Bootloader" which will introduce a thing called "KNOX Flag" which is similar to the old counter we're all used to. This is the counter that @Chainfire was successful in resetting with his app, Triangle Away.
Unfortunately, @Chainfire or anyone else for that matter, has not been able to reset the KNOX flag.
The KNOX flags is this:
0x0 = You have not tripped the KNOX flag.
0x1 = You have tripped the KNOX flag.
Again, once you trip that flag, rooting, flashing a custom recovery, etc.. there is NO way to reset it as of now. And any KNOX functionality on your phone will not work. But the worst part is Samsung will refuse warranty on your device if they see a 0x1 in your bootloader.
Another thing.. on the new bootloader, if you try to downgrade, even with an official Samsung firmware, it will fail and you will trip the KNOX flag.
So once you're on the new bootloader, there's no going back.
There's been speculation that there's an eFuse at play here.
Anyway, this is the reason why I am suggesting you all disable OTA updates and wait until a ROM is built without the new bootloader and all the functions (Wifi, MMS, etc.) are working.
mgbotoe said:
for once...im dreading an update from tmobile
Click to expand...
Click to collapse
Hey, its sammy we have to blame for this one :/ Not T-Mobile lol.
PSSSST! Don't let them know you are dreading it, or they might put it off longer xD
As to the OP.
The KNOX Warranty counter is rumored to be what is called an eFUSE. If this is true, then resetting the KNOX warranty counter will be impossible without taking apart your phone and replacing that specific eFUSE.
However, there are rumors that some root methods DO NOT trip this new counter. Is that good? Yes, is that bad? Yes. For those users who like stock kernels and just wanna root, this is okay for them. But for 99.999999 percent of us who love to flash new kernels and get more from our devices, then it trips the counter.
I personally congratulate Samsung as well as hate them at the same time for this. I congratulate them because what seems to be happening a lot is users flash a million and 2 things to their device having not one single clue what they are doing, thus bricking their 500+ dollar smartphone then claiming it as a warranty claim and getting another one. I also feel they are trying to flex their ego muscles too -.-
I also believe that if you have insurance, this does not apply. It is only for warranty claims. Which like you stated OP, it only means Samsung can choose to deny to repair or replace it. I have read a lot of thread before where users tripped the older binary flash counter, and still were given a new device. I honestly don't know how this is going to play out for the lot of us. For me, my warranty is over in a few months anyhow so i don't really care. But its still kind of a dickish thing Samsung is doing.
I am also hoping that we can extract the contents of the new update and keep our older bootloaders and create a flashable zip with the new update stuff and have it still work. I know there were some issues with the international S4 4.3 update but im not sure if it was entirely caused by the bootloader.
Exel said:
Anyway, this is the reason why I am suggesting you all disable OTA updates and wait until a ROM is built without the new bootloader and all the functions (Wifi, MMS, etc.) are working.
Click to expand...
Click to collapse
Where do you disable OTA updates on a stock S4?
Hitting "Software Update" takes me to a Boolean"Update Now" popup with no other option than choosing Yes, No or Wifi. No option to defeat future updates is offered.
Going into developer mode doesn't seem to add any pertinent options either (correct me if I'm wrong).
Clearly, Samsung doesn't want us to be able to disable updates unless or until we root, which I'm doing this weekend on the basis of this thread.
Reignogleph MMXI said:
Where do you disable OTA updates on a stock S4?
Hitting "Software Update" takes me to a Boolean"Update Now" popup with no other option than choosing Yes, No or Wifi. No option to defeat future updates is offered.
Going into developer mode doesn't seem to add any pertinent options either (correct me if I'm wrong).
Clearly, Samsung doesn't want us to be able to disable updates unless or until we root, which I'm doing this weekend on the basis of this thread.
Click to expand...
Click to collapse
You indeed have to root to disable OTA updates.
Once the update hits im going to extract the system.img to get all the files.
Then explore where all of the Knox crap is and get rid of it.
I know I want be alone in doing this...all who develop for the S4 will be on top of it.
Someone will figure out a way to get around this Knox BS...
Sent from a Insane S4
SICK MADE DEVELOPMENT
alloycowboy said:
Once the update hits im going to extract the system.img to get all the files.
Then explore where all of the Knox crap is and get rid of it.
I know I want be alone in doing this...all who develop for the S4 will be on top of it.
Someone will figure out a way to get around this Knox BS...
Sent from a Insane S4
SICK MADE DEVELOPMENT
Click to expand...
Click to collapse
thats fine and dandy for us with existing phones.. I already removed all the knox crap from my phone, and will update but not kernel and do the same..
But what about all future phones.. If indeed the kernel is locked with knox and there is no way to remove it we are screwed for new phones coming out.
lgkahn said:
thats fine and dandy for us with existing phones.. I already removed all the know crap from my phone, and will update but not kernel and do the same..
But what about all future phones.. If indeed the kernel is locked with knox and there is no way to remove it we are screwed for new phones coming out.
Click to expand...
Click to collapse
I agree. If thats the case....then alot of people will ditch Samsung.
But I have a feeling we will figure out Knox. Its man made so it can be hacked. Who when and how is the question.
Sent from a Insane S4
SICK MADE DEVELOPMENT
that's also why I paid 400 bucks for a T-Mobile sgs 4 and I am using it on at&t... I refuse to pay or support a phone with a locked bootloader.. matter of principle...i would ditch att if T-Mobile had decent service in my area.
Sent from my SGH-M919 using Tapatalk 2
Hello!
Hope all is well. First I wanted to say i'm sorry if this is a duplicate - I searched and saw similar questions, but not exactly the same as mine .
I own a T-Mobile Samsung Galaxy S4 M919 and I had rooted it and installed a custom rom. Im having hardware problems and need to return it for repairs, so I reflashed the stock system and recovery, used triangle away to remove the binary counter, and hard reset the phone. In my download mode, my phones reads "Current Binary: Samsung Official" and "System Status: Official", as well as reads official on the device status in android so all went well.
My question is this - I got notification of a push update that is going to install Android 4.3, and apparently this "KNOX" software that I do no seem to currently have. My concern with this is that i'm reading that there is a flag with this KNOX software that is easily tripped, and once done, the download mode reads "KNOX WARRANTY VOID 0x1", which therefore voids warranties. Since I was able to get everything back to completely normal, I dont want to run any more risks since my phone really needs repairs very badly. Should I bypass this update? Though my phone is 100% official now, if I do the update, will the KNOX software catch that I had rooted/custom rom'd the phone in the past and trigger the flag automatically, or do you first have to have the update installed BEFORE you try to root it for the flag to trip? Everything is 100% stock now so when I download the update, I don't think there is anything present that would trigger anything, but I don't even have this "KNOX WARRANTY VOID" line in my download mode yet so I am wondering if I am just better off being safe than sorry?
Thanks!
It won't be tripped until you trip it so you will be OK if you update it to 4.3, But I highly advice against doing so.. Just leave it as is, and return it like that
Sent from my SGH-M919 using Tapatalk
xgreenlanternox said:
Hello!
Hope all is well. First I wanted to say i'm sorry if this is a duplicate - I searched and saw similar questions, but not exactly the same as mine .
I own a T-Mobile Samsung Galaxy S4 M919 and I had rooted it and installed a custom rom. Im having hardware problems and need to return it for repairs, so I reflashed the stock system and recovery, used triangle away to remove the binary counter, and hard reset the phone. In my download mode, my phones reads "Current Binary: Samsung Official" and "System Status: Official", as well as reads official on the device status in android so all went well.
My question is this - I got notification of a push update that is going to install Android 4.3, and apparently this "KNOX" software that I do no seem to currently have. My concern with this is that i'm reading that there is a flag with this KNOX software that is easily tripped, and once done, the download mode reads "KNOX WARRANTY VOID 0x1", which therefore voids warranties. Since I was able to get everything back to completely normal, I dont want to run any more risks since my phone really needs repairs very badly. Should I bypass this update? Though my phone is 100% official now, if I do the update, will the KNOX software catch that I had rooted/custom rom'd the phone in the past and trigger the flag automatically, or do you first have to have the update installed BEFORE you try to root it for the flag to trip? Everything is 100% stock now so when I download the update, I don't think there is anything present that would trigger anything, but I don't even have this "KNOX WARRANTY VOID" line in my download mode yet so I am wondering if I am just better off being safe than sorry?
Thanks!
Click to expand...
Click to collapse
If you are having hardware issues and are returning the phone and
your phone is 100% stock without KNOX right now then why in
the world would you want to take chances with OTA updates or
any other updates.
If it was me I would have already taken/shipped the phone back for
repair or exchange instead of worrying about OTA updates.
Good luck!
Thanks for the advice! Download mode would be the only location of that "KNOX WARRANTY VOID" flag right? If it's not there, then as long as it states both Samsung Official and Official in download mode I should be good ya think?
Thanks!
Yes.. It will also show a message at boot
Sent from my SGH-M919 using Tapatalk
serio22 said:
Yes.. It will also show a message at boot
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Awesome yep - no boot message I see either - boots just like it did the day I bought it. So I am pretty sure I have the firmware before KNOX came out - It has been rooted since the summer so I probably luckily bypassed the official update with KNOX
Thanks to all for your information! Im gonna stay away from the new firmware just to be safe until i get the phone back from warranty!
Hmm - things got even more interesting. So it seems when i reset everything back to stock as mentioned above, the screen flickering issues have now gone away and I am not seeming to replicate them in any way at all. Does this sound familiar to anyone? I was using a version of Wanamlite ROM before i reset everything. I am wondering if it was just the ROM causing the screen flicker and not a hardware defect.
xgreenlanternox said:
Hmm - things got even more interesting. So it seems when i reset everything back to stock as mentioned above, the screen flickering issues have now gone away and I am not seeming to replicate them in any way at all. Does this sound familiar to anyone? I was using a version of Wanamlite ROM before i reset everything. I am wondering if it was just the ROM causing the screen flicker and not a hardware defect.
Click to expand...
Click to collapse
It could have been
Sent from my SGH-M919 using Tapatalk
Hey guys, new member although I've lurked for a while. I have been searching up and down the last couple of days to find a way to get past KNOX and reroot my device. Me being kinda rustic and not thinking about it, accepted an OTA firmware update a few days ago. Of course I lost root access. What I didn't know about at the time was how big of a problem KNOX had become recently.Well, this firmware update introduced KNOX onto my device. I've heard stories of people being able to use Kingo and Saferoot on 4.2.2 and 4.3 after KNOX. This has not been the case with me, and I'm wondering if anyone has had success with this. Odin doesn't work either. I noticed that write protection is set as yes when in ODIN mode, and I suspect this is KNOX preventing changes to the ROM. As a result I haven't even been able to reflash the stock ROM image I have, whereas I have heard that you can reflash stock ROM's, but can't go backwards as far as version number. Thanks for your help in advance.
HansBlenkers said:
Hey guys, new member although I've lurked for a while. I have been searching up and down the last couple of days to find a way to get past KNOX and reroot my device. Me being kinda rustic and not thinking about it, accepted an OTA firmware update a few days ago. Of course I lost root access. What I didn't know about at the time was how big of a problem KNOX had become recently.Well, this firmware update introduced KNOX onto my device. I've heard stories of people being able to use Kingo and Saferoot on 4.2.2 and 4.3 after KNOX. This has not been the case with me, and I'm wondering if anyone has had success with this. Odin doesn't work either. I noticed that write protection is set as yes when in ODIN mode, and I suspect this is KNOX preventing changes to the ROM. As a result I haven't even been able to reflash the stock ROM image I have, whereas I have heard that you can reflash stock ROM's, but can't go backwards as far as version number. Thanks for your help in advance.
Click to expand...
Click to collapse
Flash anything with ODIN will trip the KNOX. Kingo is basing their root method on Saferoot, just with a GUI to make things simpler. And Saferoot should work with ROM that is before KK (4.4). If your OTA update is 4.4 than Saferoot won't work, since Saferoot is using a vulnerability prior 4.4 version. Does Kingo or Saferoot give any error message?
And just to double check, for both Saferoot or Kingo to work, you need to enable USB ADB and debugging mode.
TNCS said:
Flash anything with ODIN will trip the KNOX. Kingo is basing their root method on Saferoot, just with a GUI to make things simpler. And Saferoot should work with ROM that is before KK (4.4). If your OTA update is 4.4 than Saferoot won't work, since Saferoot is using a vulnerability prior 4.4 version. Does Kingo or Saferoot give any error message?
And just to double check, for both Saferoot or Kingo to work, you need to enable USB ADB and debugging mode.
Click to expand...
Click to collapse
Hey thanks for the reply. I do have USB ADB and debugging turned on. I've also tried reinstalling kies and the USB drivers them selves. I don't really care if an Odin flash trips Knox, as I don't think I have a warranty to worry about. The OTA update brought my firmware upto date , so I'm still on 4.2.2. This means that technically Saferoot or Kingo should work as advertised. This brings me back to the Write Protection set to Yes, and it's the only thing I could see preventing me from rooting my phone.
EDIT: Well I just found out that the Mini USB I use to charge my mouse started shorting other USB devices. Not like short then come back on, it was so bad every port on the computer shut down and I had to restart to get them working again. It was also the cable I was using to plug my phone in. Will update again when I try another cable.
EDIT 2: Just tried with the cable I usually use for charging my phone. No change on Kingo, still get a Root Failed, Need Root error.
HansBlenkers said:
Hey thanks for the reply. I do have USB ADB and debugging turned on. I've also tried reinstalling kies and the USB drivers them selves. I don't really care if an Odin flash trips Knox, as I don't think I have a warranty to worry about. The OTA update brought my firmware upto date , so I'm still on 4.2.2. This means that technically Saferoot or Kingo should work as advertised. This brings me back to the Write Protection set to Yes, and it's the only thing I could see preventing me from rooting my phone.
EDIT: Well I just found out that the Mini USB I use to charge my mouse started shorting other USB devices. Not like short then come back on, it was so bad every port on the computer shut down and I had to restart to get them working again. It was also the cable I was using to plug my phone in. Will update again when I try another cable.
EDIT 2: Just tried with the cable I usually use for charging my phone. No change on Kingo, still get a Root Failed, Need Root error.
Click to expand...
Click to collapse
At this stage I can only suggest to try on a different PC (use don't need Kies, just the Samsung driver will do) with a cable that your are 100% sure it working. If it still not working, my only guess is your network provider enable a looked boot loader in the OTA update you just did (hence the Write Protection flag). If that the case, nothing can be done at this point.
Same Boat
Im in the same boat did realize that KNOX would change so much. I need to reroot so hopefully someone can figure it out without tripping knox.
It fails because of the Security notice....Unauthorized access to a secured area has been blocked. Tap to learn more. If you notice when you check USB debugging, look below at Verify apps via USB. It is checked and grayed out. It isn't checked when USB debugging is off. I don't know how this was circumvented on the S4. But I'm peeved I let the update happen. They conveniently left out any info about security, and I'm tempted to return the phone and get one that hasn't been updated. Figure they weren't forthcoming about what the update contained so I can raise enough stink, get an old phone, download the update, pass it off to someone who can hopefully pull everything but the bootloader and create a tar to flash via odin. If that's possible and someone is willing to do it. If I had another spare line, I'd get another phone to donate for the cause.
I think if we're on Knox we need Odin to Root because anything that gets transferred via USB will be blocked. I even tried rootkeeper, and it was blocked.
The tough part is, unless it's a premium phone, it's not getting the level of dev support we're used to (well I'm used to...haha). Rooting through odin, custom recovery....used to taking it for granted. And with Sprint EOL'ing the phone, it's not really going to gain any momentum, though I did only pay 99 cents for it on a spare line. Kinda ticks me off Samsung has gone this direction when they used to be so dev friendly. Almost enough to make the S4 my last Samsung.
TNCS said:
At this stage I can only suggest to try on a different PC (use don't need Kies, just the Samsung driver will do) with a cable that your are 100% sure it working. If it still not working, my only guess is your network provider enable a looked boot loader in the OTA update you just did (hence the Write Protection flag). If that the case, nothing can be done at this point.
Click to expand...
Click to collapse
the concern is not tripping knox from the bootloader perspective. The problem is the knox security app that can't be removed without root. So for everyone that has OTA updated to NA7, going the odin route to root is the only option as far as I know. I know I don't care about tripping the counter. I just want control back of my phone. And the only way to do that at the moment is to return it for a pre knox version which I'm apt to do at the moment since there is a lack of development, and the ones that are developing don't even have the phone. Kudos to them, but there's not much help once you've updated to NA7. And unfortunately, the update doesn't tell you it's locking down your phone. Then you're stuck in a quandary, because the update also provides updates for Spark, so unless someone does a dump of the download and someone can pick it apart and provide a zip sans Knox, we'll have to deal with a stock phone.
dbpaddler said:
the concern is not tripping knox from the bootloader perspective. The problem is the knox security app that can't be removed without root. So for everyone that has OTA updated to NA7, going the odin route to root is the only option as far as I know. I know I don't care about tripping the counter. I just want control back of my phone. And the only way to do that at the moment is to return it for a pre knox version which I'm apt to do at the moment since there is a lack of development, and the ones that are developing don't even have the phone. Kudos to them, but there's not much help once you've updated to NA7. And unfortunately, the update doesn't tell you it's locking down your phone. Then you're stuck in a quandary, because the update also provides updates for Spark, so unless someone does a dump of the download and someone can pick it apart and provide a zip sans Knox, we'll have to deal with a stock phone.
Click to expand...
Click to collapse
I was (after a good bit of tinkering, and deleting my modem on accident) able to install CWM and flash a CW11 version s0be is currently developing, and it's working pretty well as far as I can tell. Unfortunately, due to the lack of support on this forsaken Sprint device, I haven't been able to find a modem I can flash onto the damned thing to get it working properly again. I don't advise the route I took, firstly because of the effort it took, but I also damned near bricked it about 5 different times, and needed to use a Linux VM. Also, because of the lack of developers on this thing, if you delete your modem and A: don't have a friend (brother in my case, has same phone) you can pull a modem.bin off of and B: don't know how to build that .bin into a working .zip or a flashable tar.md5 you might get stuck with an unusable device at the end of the day. Really, the only thing Knox has done for us is complicate things a hell of a lot more than they need to be. Although, tbh, that might (most likely) have been my stupidity that deleted the modem. In any case, check it (s0be's CM11 development) out, it's coming along nicely. Just be careful with it.
........
thank you very mach
Hey guys,
yesterday I bought a i9192 in Germany (not officially sold here --> imported).
First thing it did was to update to I9192XXUBNB1. After that, I wanted to gain root access as I want to use different software that needs root (Tasker, Titanium Backup, StickMount, ...).
Unfortunately, there are many guides but from non of them, I was able to see if it really worked for I9192XXUBNB1 and which problem appear afterwards.
Can anyone help me to find a guide that defintively works?
I'm not sure what will happen in Europe if the Knox-Flag gets triggered with an imported phone but with all the Samsung-Sw on it and without Tasker, its note really funny to use the phone. So, if there is a way withoug triggering Knox, it would be great. And if not, well, let's hope I don't need the warranty ...
Thanks and greetings,
Matthias
You should not have updated your phone so fast. I9192XXUBNB1 seems to be a version not easy to be rooted. The easiest way is to actually install a pre-rooted knox-free rom. You have now installed a stock rom with Knox and it is impossible to install a pre-rooted rom without triggering Knox.
Here is the pre-rooted rom:
http://forum.xda-developers.com/showthread.php?t=2620621
Last reminder: upon installation of any non-official rom the Knox counter will be triggered immediately
Yes, well, I know now ...
But normally, first thing I do with new devices is updating to the newest version - in this case, this was a mistake.
As a result, I flashed the version cou mentioned, triggered the flag - and everything works fine.
Busybox installed, Secure Settings and Tasker is up and running.
As I'm from Germany, I hope there won't be any problem IF I have the need for warranty.
Thanks,
Matthias
matmike said:
Yes, well, I know now ...
But normally, first thing I do with new devices is updating to the newest version - in this case, this was a mistake.
As a result, I flashed the version cou mentioned, triggered the flag - and everything works fine.
Busybox installed, Secure Settings and Tasker is up and running.
As I'm from Germany, I hope there won't be any problem IF I have the need for warranty.
Thanks,
Matthias
Click to expand...
Click to collapse
Yes we all should blame Samsung for making the stupid Knox a default installation instead of optional. Also rooting of newer firmware is more and more difficult.
In general, you're right as the new software "features" really make bad problems for the experienced users who want to use advanced functions.
But from a different point of view, I partially can understand what Samsung does: IF they have a problem with more cases of warranty with rooted/modfied devices that go back to original directly before sending them back to Samsun, the thing they did is the only way to solve that - know if a phone was modified.
Personally, I work in automotive industry and there is a similar problem: Some people alwas try to tune their cars (in more or less senseful ways). And if there is a problem with a part of the car, they just go back to the original state like "what, me, no modification at all". In the end, this would cause costs for the company. So why not implement just a flag that shows "Modified" so you can reject warranty for parts that get problems with tuning (engine, axles, clutches) if tuning caused the problem. The rest of the parts that is not involved (radio, body, ...) is still valid for normal warranty.
With my samsung phone, that means: if there is a defect, Samsung has the chance to check if the modification caused the problem or not and eventually reject a repair. Of course, "With great power comes great responsibility" so let's hope Samsung uses the power in a good way without rejecting every failure of a modified phone. If the button on the front falls out, it is very unlikely that wrong software caused the problem
Greeting,
Matthias