I have noticed that Samsung has released a few firmware updates for the T830. However, it's unclear as to what has changed amongst the different versions. A changelog number is provided, but from what I can see there are no details to be found. Does anyone know a way to determine what has changed between the different versions / gather the details? Additionally has anyone flashed a new version and continued to maintain root or ability to re-root?
I am currently on ARH5, which I successfully rooted. However, I am interested in upgrading as I hear that the screen touch delay issues, which I just started to notice, have been fixed in at least ARJ3. Was thinking of flashing ARJ3 but also noticed ARK4 now available, thus trying to determine the difference. Additionally want to ensure that I don't get locked from being able to root. Thus like to know if anyone has successfully gone down this path.
Ok, so partially answered my own question. I took the plunge and downloaded the firmware from Samsung site and updated. I successfully maintained my OEM Unlock option and was able to re-root my device. However still have the question in regards to the change logs.
I don't have an answer about changelog, but I was wondering if you rooted okay. Also, did you trip knox in doing so?
Yes, was able to root without issue. I have upgraded twice now, first to ARJ3 and then to ARK4. In both instances I didn't have any problems rooting.
Not sure on Knox, but I am pretty sure that it's tripped. I believe that will always happen when rooting.
Related
By the question you can tell that i'm rather inexperienced at this, but a buddy of mine(who has a Droid on VZW) and i were debating whether or not doing an OTA update after you root would cause you to loose your ability to root forever.
I guess it's different on both devices, but he contends that he could unroot his droid, which is running a custom 2.2 ROM, install an OTA update, decide he doesn't like it, then just go back to a 2.1 RUU from VZW or Motorola, and then re-root.
Everything i have read here about the EVO indicates that if i am already rooted, and i accept an OTA update, then i will never be able to root again. Does never, really mean never? Or is it just mean that i won't be able to root using the current methods to root the phone?
What if i had never rooted and then accepted the OTA 2.2 from sprint that may be coming this week, would i then be able to root?
What exactly does the update do to remove the ability to get /root access to the phone? Something with the bootloader, HBOOT, or what?
Thanks for the information. Hopefully, this will settle this question for my friend and I.
Chris
OTA updates typically break any existing root methods, and disable any current root access.
Some OTA's also update the phone in a manner which prevents older official roms (that have working roots) from being reinstalled.
At that point, you have an updated rom with known roots removed, that can't be rolled back, so the only option is to wait until another root exploit is found and released. Which may or may not happen depending on the device and whoever is working on it.
Hope that helps.
You can take and accept as many updates as you want....you just have to modify that update by replacing the new hboot with the engineering one.....that way you can freely flash zip files
HTC is tricksy and they dont let you roll back after the OTA. Motorolla may not have this so your friend may in fact be able to roll back to 2.1 (however he may be misinformed as well).
To root basically they find a bug to exploit that allows us to gain access as a root user. when the OTA updates come out 99% of the time they will fix this bug. HTCat least blocks roll backs so now you are on a new version of the software that you can not go backwards and the bug to root is no longer there.
While there are normally other bugs that can be exploited to get root it is possible that there isnt one or that if there is no one can find it. if they cant find it then it could remove your ability to root permanently.
snandlal said:
You can take and accept as many updates as you want....you just have to modify that update by replacing the new hboot with the engineering one.....that way you can freely flash zip files
Click to expand...
Click to collapse
while true accepting an OTA will not give you the chance to do this for most.
ok, that explains things a little better. thanks.
I'm new to all of this as well. My EVO has already been updated OTA by a Sprint employee while I was purchasing the phone. From what I've read it looks like I'm SOL until someone cracks 2.2. One quick question though... How long did it take people to be able to root the first software on the EVO's?
I had rooted my SGS3 while on 4.0.4 using the stock Samsung rom and Odin without issue no custom ROMS were installed just root access. Early August of 2013 the OTA for 4.1.2 was rolled out and I had accepted the update which was installed without issue, which apparently should not have been the case (everything I can find says OTAs will fail if you have root access, but this was not the case). I now want to either return to a full stock to get the 4.3.3 update at which point I may remain unrooted, or gain root again and update to 4.3.3 with root. I'm cautious about how to proceed here since I've read about a lot of people bricking their phones while attempting to root after 4.3.3. My primary concern is that my flash counter is tripped at 1, but I don't have root access and am not sure how to proceed with out potentially damaging my phone. So I'm essentially getting the worst of both worlds (unable to receive stock updates from carrier, no root access to update otherwise.) and don't want to be stuck on 4.1.2 for the life of this phone. I still have SuperSU installed, but when I open it it says "There is no SuperSU Binary installed and Super SU cannot install it. This is a problem!"
I have searched these forums and a few related to it, and from what I can gather I should just reroot the phone following instructions for 4.1.2, but if I want to make the jump to 4.3.3 I wasn't clear if this would be needed or not, but none of the threads I could find directly addressed the issue for the ATT SGS3 i747. The closest I found was a thread posted last month where the OP was directed to the CF Root procedures, but there was no followup after that. I'm just a little leery about what might happen if I reroot with another method and end up with duplicate files/.apks etc related to the root process on my phone.
I also wanted to be sure that rerooting using a different method wouldn't somehow damage my phone.
Can someone with some experience please advise of the safest best practice for me to either recover root and update, or remove root and update so I can start fresh later? From what I can gather this should be an easy fix, but I would prefer to rely on the expertise of someone more knowledgable as opposed to winging it on a gut feeling I will be ok.
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
Hi all, apologies if this has been answered but I've search for the last couple of days without finding the answer.
I have 2 AFTV's one on the latest update and one on 51.1.4.0_user_514005520.
I want to manually update from 51.1.4.0_user_514005520 to 51.1.4.0_user_514006420. I have the bin file but unsure if this is possible without being rooted and have su installed. Currently the latest Kodi and SPMC don't seem to work at all on this software version.
I would expect to be able to place the bin file somewhere on the machine a then do a "adb reboot recovery" but I've not had any luck in working out how this is done. It's signed after all so I see no issue in allowing the update.
The reason I'd like to not update any further than 51.1.4.0_user_514006420 is due to the fact the efuse is blown on the next increment of the updates. With all the great work been done on here to obtain root on higher firmwares has made me want to keep the efuse intact and on the lowest working updating.
Many thanks to anyone who can help.
o71g said:
Hi all, apologies if this has been answered but I've search for the last couple of days without finding the answer.
I have 2 AFTV's one on the latest update and one on 51.1.4.0_user_514005520.
I want to manually update from 51.1.4.0_user_514005520 to 51.1.4.0_user_514006420. I have the bin file but unsure if this is possible without being rooted and have su installed. Currently the latest Kodi and SPMC don't seem to work at all on this software version.
I would expect to be able to place the bin file somewhere on the machine a then do a "adb reboot recovery" but I've not had any luck in working out how this is done. It's signed after all so I see no issue in allowing the update.
The reason I'd like to not update any further than 51.1.4.0_user_514006420 is due to the fact the efuse is blown on the next increment of the updates. With all the great work been done on here to obtain root on higher firmwares has made me want to keep the efuse intact and on the lowest working updating.
Many thanks to anyone who can help.
Click to expand...
Click to collapse
If you are not rooted it is no way of doing this. Your box can only be updated OTA and that will take it to the newest update available in the stream.
I've got a nexus 7 (2013) on android 6.0. Over the two years I've spent with it, I've ran into many features that require root. Now I've finally decided to do it. Right now, I'm doing it for the multi window thing.
Q.1: How long will Nexus 7 OTA updates continue to come?
Q.2: Will I get a notification that I got a system update if I'm rooted? And will I be able to keep my root while updating?
Q.3: I found a way for rooting the Nexus on Lollipop through one click( I think wugtoolkit). Will it work on Marshmallow? If not, whats the easiest way, preferably without connecting it to a computer?
Q.4: Any risks or cons? I've heard its impossible to brick a Nexus, is it true?
Thanks 
Tranquility. said:
I've got a nexus 7 (2013) on android 6.0. Over the two years I've spent with it, I've ran into many features that require root. Now I've finally decided to do it. Right now, I'm doing it for the multi window thing.
Q.1: How long will Nexus 7 OTA updates continue to come?
Q.2: Will I get a notification that I got a system update if I'm rooted? And will I be able to keep my root while updating?
Q.3: I found a way for rooting the Nexus on Lollipop through one click( I think wugtoolkit). Will it work on Marshmallow? If not, whats the easiest way, preferably without connecting it to a computer?
Q.4: Any risks or cons? I've heard its impossible to brick a Nexus, is it true?
Thanks 
Click to expand...
Click to collapse
I'm not a dev, but I have some experience rooting the N7 (2012 and 2013).
1) Well, it looks like 6.0 isn't coming to the N7 2012, so there is a good chance support for major versions will be dropped soon (within the next year?). They might continue to release patches and security fixes for 6.x a year or two after that, like they appear to be doing with the N7 2012, but this is all speculation. There are probably number crunchers looking at the sales figures and survey results to gauge interest, and there were some rumors recently of a new N7 possibly in the works. Those will both factor into whether support will continue.
2) You will get a notification, but everything I've seen has indicated that the install will fail (won't brick the tablet, but will just show an error and reboot to its previous state). What I think most people do, including me, is just flash the stock image in 'no wipe' mode and re-root after the update. You can also sideload the OTA update, depending on rooting method (I think, but haven't done this myself). Lastly, if you don't mind reconfiguring all your apps or if you have a good backup scheme, you can just do a fresh install then root. I have never had trouble flashing stock in no-wipe and re-rooting, but I've heard some people have had problems. (It's worth noting that if your bootloader hasn't been unlocked, you will have to wipe the device anyways. The unlocking survives flashing, so it's a 'one and done' thing. You only really need to lock it again if you're sending it in for warranty service.)
3) Wug's toolkit is currently borked for most people (version 2.0.6), so avoid it until the thread in the N7 development subforum has some success stories. Also, rooting in Marshmallow is possible, but seek out instructions specifically for M and use the latest versions of any linked utilities (like SuperSU and TWRP). I used Wug's toolkit 90% of the time for updating and rooting, and when it works, it's a breeze. It might be worth waiting for it to be updated to address the current issues. You can use the previous version to do some basic things and as a launchpad for manual tweaking, but the main, one click and done options will not work - I tried and was greeted with a bootloop due to an out of date SuperSU. But, in version 2.0.5 you can unlock the bootloader and flash the latest stock (haven't tried the U or V versions, but MRA58K worked fine). From there you have to root mostly manually, but there are shortcuts for some of the steps in the Advanced Utilities section.
4) It's always possible to brick a device, but it's very rare. There are 2 kinds of 'bricks'. 'Hard' brick is what most people worry about - something happens that prevents access to even the lowest level of the device. It's as if there was a hardware failure. 'Soft' bricking is what less tech literate people equate to hard bricking because to them the device is useless. In reality, it's a software issue that prevents some early stage of the boot up process. It is almost always recoverable with enough time and research. In basic computer terms, hard bricking is failing to post and soft bricking is failure of the OS to load (basically, though there are nuances). With root, you have access to everything and you're trusting whatever you install that takes advantage of that power to use it wisely. An ad blocker shouldn't need to adjust the CPU voltages. This is rare if you don't intend to overclock or mess with low level hardware tweaks. It is much more likely, but still pretty rare, to soft brick the device, which means you just have to reflash the system image. Worst case is you have to wipe the device and start over, or spend a few hours researching exactly what caused it.
Hope that helps. I'm not an obsessive ROM flasher and my experience has been only with Nexus devices, but these are my impressions.
Thanks a lot for your detailed reply.
1) I was under the impression that 6.0 would be the last updated for Nexus 7. Guess I'm wrong.
2) How long would "flashing the stock image in no wipe mode" take?
3) I'll wait then for an updated version ._.
4) Guess if I follow the steps correctly that won't happen. Prepared to take the risk.
Tranquility. said:
Thanks a lot for your detailed reply.
1) I was under the impression that 6.0 would be the last updated for Nexus 7. Guess I'm wrong.
2) How long would "flashing the stock image in no wipe mode" take?
3) I'll wait then for an updated version ._.
4) Guess if I follow the steps correctly that won't happen. Prepared to take the risk.
Click to expand...
Click to collapse
Android M is the last official update for N7 2013, the first gen N7 is done with updates. Once rooted you will not get any OTA updates anyway.
Flashing usually takes about 3-4 minutes. Booting up can take up to 10-15 min.
Just don't root on M until a stable method has been discovered.
Kay thanks.
Could you please update me when a stable way is found? Or at least provide a link where I can check myself.
You can check the marshmallow and the beta thread for updates. http://forum.xda-developers.com/apps/supersu
Tranquility. said:
Kay thanks.
Could you please update me when a stable way is found? Or at least provide a link where I can check myself.
Click to expand...
Click to collapse
You can root 6.0 pretty easy if you have fastboot installed. I've done it and can confirm it works. You just need to download the ElementalX-N7 kernel and SuperSU to your device then flash TWRP in fastboot then flash the kernel and SuperSU in TWRP. There are threads on here I believe with instructions to help you. If you need any help you can message me.
The beta SuperSU and elementalx method worked great for me and seems totally stable. I'd recommend learning fastboot/adb as mentioned. That has saved me a few times from the dumb things I've done messing around with root access.
Sent from my Nexus 7 using XDA Free mobile app
Rooting
As I mentioned in a previous post rooting using TWRP, SU I don't think fully roots
the device. When I loaded Multi-Rom, it installed in the usual fashion but only boots to the TWRP recovery utility.
In the past, one could globally root the device but the problem appears new.
Kurt