Related
So I originally rooted my s3 with the GS3_debugfs-root_r2.7z method, flashed CWM and unlocked my bootloader. Since then i have flashed several roms and all was well until a couple days ago when i decided to restore my first backup in order to retrieve some data. I was still on G7 and kept getting the notification of the HE update. Even though I excepted the OTA and let it fail in CWM i kept get getting the notice almost every time i turn on my phone. I was getting so annoyed with it that i decided to flash a rom with HE in hopes that that would stop the OTA. In this whole process of restoring my backup my bootloader must have locked and when i flashed the rom I got stock on that "unauthorized software, contact Verizon screen". It freaked me out when i couldn't boot into recovery.
I followed the whole Odin, root66 method and was able to save my phone...phew... but have a couple questions now.
1) my phone has the superuser app and it shows that it cannot be uninstalled, like a system app but yet root checker says i am not rooted? Why is this.
2) Would installing supersu and updating binaries get me rooted again?
3) This one is just for curiosity..The message when i soft bricked my phone said you have unauthorized software and to go see a Verizon store. Would they really have been able help me or just tell me i am SOL
ps. Thank you to the XDA community for sharing instructions like the one i used to save my phone.
microdot said:
1) my phone has the superuser app and it shows that it cannot be uninstalled, like a system app but yet root checker says i am not rooted? Why is this.
2) Would installing supersu and updating binaries get me rooted again?
3) This one is just for curiosity..The message when i soft bricked my phone said you have unauthorized software and to go see a Verizon store. Would they really have been able help me or just tell me i am SOL
Click to expand...
Click to collapse
2: That could work, but so should loading the default SU and updating binaries.
3: They would not have been likely to help you, and may have even voided your warranty.
Going to a store would have yielded a bunch of head scratching and them telling you to file an insurance claim.
In the future if you want to block ota's freeze sdm and fwupdate in titanium.
So I have a Sprint Galaxy S6. Until last week, I was running Android 5.1. I actively avoided upgrading to 6.0.1 because things are getting more difficult with the use of certain programs and with rooting and all that.
Something important required me to TRY upgrading to Android 6, hoping this might solve my problem. It didn't. The problem has since fixed itself (much to my confusion), but now I'm stuck with Android 6. And by upgrading I lost my custom recovery and root. I now find out that downgrading is quite a task and multiple sources say don't do it under any circumstances.
I'm (probably) fine with keeping Android 6.0 if I could just figure out how to root my phone (preferably easily). Tried PingPongRoot which is what I had previously, also tried King Root and Kingo Root and nothing worked. They all failed. PPR even put me in a catch-22 whereby I couldn't root until I got SuperSU working, but SuperSU wouldn't work because the binary wasn't installed and required root to do so. So I needed root to make SuperSU work and needed SuperSU to work in order to root. Fail.
So I got CF-Auto-Root. I figured easy, right? Then I get something I've never seen before: "Custom Binary Blocked by FRP Lock." This was not on my phone before I updated. Flashing with Odin failed instantly. Phone still works, but I'm back to square one. Looked up how to fix this problem and found that, this too, could mess me up. I'm locked out of Titanium Backup until I root and I don't want to go ruining my phone without a backup of all of my apps, for which I need TB.
1) How do I root my Galaxy S6 SM-G920P Android 6.0.1 easily? Relatively easily?
2) Is there a safe way to get rid of the FRP Lock so that I can root?
3) If rooting Android 6 is going to be dangerous, is downgrading back to Android 5 possible? Is this equally, if not more, dangerous?
I did NOT know what a pain this would be going to Android 6. I'm totally frazzled right now and out of ideas. Any help would be appreciated.
hamstrman said:
So I have a Sprint Galaxy S6. Until last week, I was running Android 5.1. I actively avoided upgrading to 6.0.1 because things are getting more difficult with the use of certain programs and with rooting and all that.
Something important required me to TRY upgrading to Android 6, hoping this might solve my problem. It didn't. The problem has since fixed itself (much to my confusion), but now I'm stuck with Android 6. And by upgrading I lost my custom recovery and root. I now find out that downgrading is quite a task and multiple sources say don't do it under any circumstances.
I'm (probably) fine with keeping Android 6.0 if I could just figure out how to root my phone (preferably easily). Tried PingPongRoot which is what I had previously, also tried King Root and Kingo Root and nothing worked. They all failed. PPR even put me in a catch-22 whereby I couldn't root until I got SuperSU working, but SuperSU wouldn't work because the binary wasn't installed and required root to do so. So I needed root to make SuperSU work and needed SuperSU to work in order to root. Fail.
So I got CF-Auto-Root. I figured easy, right? Then I get something I've never seen before: "Custom Binary Blocked by FRP Lock." This was not on my phone before I updated. Flashing with Odin failed instantly. Phone still works, but I'm back to square one. Looked up how to fix this problem and found that, this too, could mess me up. I'm locked out of Titanium Backup until I root and I don't want to go ruining my phone without a backup of all of my apps, for which I need TB.
1) How do I root my Galaxy S6 SM-G920P Android 6.0.1 easily? Relatively easily?
2) Is there a safe way to get rid of the FRP Lock so that I can root?
3) If rooting Android 6 is going to be dangerous, is downgrading back to Android 5 possible? Is this equally, if not more, dangerous?
I did NOT know what a pain this would be going to Android 6. I'm totally frazzled right now and out of ideas. Any help would be appreciated.
Click to expand...
Click to collapse
Rooting is fairly straightforward with cf-autoroot, you're main problem here is frp (factory reset protection) which is a Google security feature, you need to remove this or bypass this 1st before doing anything. I've seen a few articles and guides on Google, but as I don't have this issue I cannot say if they work or not but at a glance they do not seem very difficult. But once you get past the frp lock you can go ahead and root. If you are on a newer marshmallow bootloader then downgrading to lollipop is pretty much impossible
sofir786 said:
Rooting is fairly straightforward with cf-autoroot, you're main problem here is frp (factory reset protection) which is a Google security feature, you need to remove this or bypass this 1st before doing anything. I've seen a few articles and guides on Google, but as I don't have this issue I cannot say if they work or not but at a glance they do not seem very difficult. But once you get past the frp lock you can go ahead and root. If you are on a newer marshmallow bootloader then downgrading to lollipop is pretty much impossible
Click to expand...
Click to collapse
Thanks. I looked it up myself. Requires something called "Find my mobile," a setting under "Lock Screen and Security." I don't have that.
Samsung's website says if you don't see it, then your device is not supported. Kill me now!
I completely screwed myself by updating. If anyone else knows a way to do this with my... limitations, I would love to hear about it.
hamstrman said:
Thanks. I looked it up myself. Requires something called "Find my mobile," a setting under "Lock Screen and Security." I don't have that.
Samsung's website says if you don't see it, then your device is not supported. Kill me now!
I completely screwed myself by updating. If anyone else knows a way to do this with my... limitations, I would love to hear about it.
Click to expand...
Click to collapse
Have you had a look at method 1 on the below page?
https://www.google.ie/amp/s/www.pro...tory-reset-protection-on-samsung-devices/amp/
sofir786 said:
Have you had a look at method 1 on the below page?
https://www.google.ie/amp/s/www.pro...tory-reset-protection-on-samsung-devices/amp/
Click to expand...
Click to collapse
Method 1 being... factory reset? I'm hoping to keep my phone in tact.
I did find something stupidly simple that someone just happened to off hand comment on in an old thread. Apparently there's a switch in the settings to disable OEM protections. I didn't think it would work but it really was that easy.
Was able to root successfully using CF, but then doing a SuperSU full unroot caused a bootloop. I have to figure out the proper way to root for my needs now.
Thanks for the suggestion, though!
I've made this thread to teach T337A owners how to root their device with SuperSU. Please note that this is a system-less root, meaning it's temporary, but can be re-applied. Rooting only takes about 5-7 minutes and brings numerous tweaks and advantages to your device. Just remember that every time you reboot or shut the device down, you will need to repeat the rooting process. This tutorial was designed for Lollipop 5.1.1, but it should work on KitKat as well.
Before beginning, you will need to download the following file, unzip it on your pc, then transfer it to your device's internal storage/external sd card.
T337AUCU2BOH4 (Lollipop) firmware can be found here
Root Files can be found here
Lets start!
1) Install both the APK files in the file on your device, If prompted, allow installation from unknown sources.
2) Make sure your device is connected to WiFi, then open Kingroot.
3) Once Kingroot is "Done searching for the best root strategy", click the "Try Now" button and wait about 3 minutes for KingRoot to give you a "Root Successfully" message.
4) This is where it gets kinda tricky, immediately after receiving the root success message, go into SuperSU-me, and grant root permissions when prompted.
5) Click on the big blue button in the middle of the frame and wait about 1 minute for the process to complete. DO NOT UPDATE THE SUPERSU BINARY, IT WILL CAUSE YOUR DEVICE TO BOOTLOOP.
6) IMMEDIATELY after the process has completed, go into Settings and make sure KingRoot or Purify is not installed! This is an important step because Kingroot and Kingroot adware tends to install itself in the system partition which can cause problems and frustration.
7 - Recommended) Download a root file explorer (such as ES File Explorer) and search "King" under /data and /system to ensure that the KingRoot app and its bloatware has been wiped from the system. This is to ensure that Kingroot still works properly after a reboot.
8) Enjoy root access!
If this tutorial helped you please be sure to hit the :good: button. If you had any issues or troubles during this process please feel free to let me know down below.
Cheers!
@KingOfTheNet
will flashfire work? bc it wont with kingroot
also, could itit.d be enabled and run these off of a script for example on startup so we don't have to do this after each reboot/shutdown
but i believe you would have to capture kingroots data somehow in the process of rooting
toolhas4degrees said:
@KingOfTheNet
will flashfire work? bc it wont with kingroot
also, could itit.d be enabled and run these off of a script for example on startup so we don't have to do this after each reboot/shutdown
but i believe you would have to capture kingroots data somehow in the process of rooting
Click to expand...
Click to collapse
FlashFire does work on SuperSU, I've tested that for myself. It does not work with KingRoot.
For the second question, I'm not sure. I haven't looked through that file myself and I might look through it later but right now, I would just avoid rebooting the tablet if you wanna keep root without repeating the process over and over again. It's what I do, repeating the process over and over again can get very tedious and annoying.
Cheers!
I assume you're talking about 5.1.1? It won't work with kingroot versions higher than 4.8. Also, flashfire will load, but if you try to flash a zip you're screwed. You can actually use replace kingroot with supersu zip in terminal emulator on any version kingroot. Same deal with su binary, don't update it. Wish I could figure out how I had permanent for with kingroot. I had to go messing with things and lost it. Nothing really special about this method, unless there's a dev out there that can do something with it.
xjimmy said:
I assume you're talking about 5.1.1? It won't work with kingroot versions higher than 4.8. Also, flashfire will load, but if you try to flash a zip you're screwed. You can actually use replace kingroot with supersu zip in terminal emulator on any version kingroot. Same deal with su binary, don't update it. Wish I could figure out how I had permanent for with kingroot. I had to go messing with things and lost it. Nothing really special about this method, unless there's a dev out there that can do something with it.
Click to expand...
Click to collapse
Sorry for the late response. Yes, somethings I forgot to mention in the original post:
1)Updating the SU Binary will put your device in a bootloop
2)Flashing anything with flashfire (based on what I've seen) results in a soft brick
3) I know you can replace kingroot with SuperSU in terminal, but when you reboot, you're unrooted again.
4) I'm trying to figure out how I could altar the boot.img so we can get permanent SuperSU on this thing the same way Chainfire did it with the US and Qualcomm Samsung Galaxy S7's.
Cheers!
Hi, @KingOfTheNet, thanks for helping out with this device, i rooted my device on KK nk2 build and now updated to 5.1.1, thanks to you! now i would like to root 5.1.1 (am aware it is a temp. root)
i have superSu Pro, do i need Super Sume for this to work?
KingOfTheNet said:
Sorry for the late response. Yes, somethings I forgot to mention in the original post:
1)Updating the SU Binary will put your device in a bootloop
2)Flashing anything with flashfire (based on what I've seen) results in a soft brick
3) I know you can replace kingroot with SuperSU in terminal, but when you reboot, you're unrooted again.
4) I'm trying to figure out how I could altar the boot.img so we can get permanent SuperSU on this thing the same way Chainfire did it with the US and Qualcomm Samsung Galaxy S7's.
Cheers!
Click to expand...
Click to collapse
Somehow I had it permanently rooted with kingroot a while back. I had the 4.9.6 apk on my tab at the time, is all I know. I could've updated from an earlier version, and maybe that was the cause. I've tried so many different versions of kingroot with no luck, but one peculiar occurrence; if I open kingroot, get into the settings and uninstall kingroot without saving a backup of root, then delete all the files in the tablet's main directory, and reinstall kingroot version 4.8.0, it somehow retains a partial permanent root. At least on my T337A running 5.1.1 BOH4 it will, as long as I get a fresh install of 4.8.0, let it root, then hit the optimize button right after. Then wait until it finally tells me that kingroot has been deployed as a system app. After that, when I try to open any root apps, the screen will darken as it does when the root permission tab pops up, but it never pops up. The app just freezes. I can kill it in the task manager screen to just go back to using my tablet. After I restart the tab, sometimes it'll tell me an app has been granted superuser permissions. If I open up terminal emulator, type in the 'su' command and hit enter, the screen will turn dark again like it's going to ask me to allow or deny superuser permission, but it just freezes like that again. I've tried all kinds of stuff with 4.8.0, but I still can't get it to stick. If you don't hit the optimize button in kingroot right after rooting, and just wait for kingroot to install as a system app, the allow/deny prompt comes up without freezing, but the partial permanent root glitch doesn't remain. ugh, tired of messing with it though. lol
Edit: I may be wrong. It might need to be rooted with 4.8.0, optimized, then rebooted right away for the partial root. I'll try to do it again and let you know what I find.
bklyndiaz said:
Hi, @KingOfTheNet, thanks for helping out with this device, i rooted my device on KK nk2 build and now updated to 5.1.1, thanks to you! now i would like to root 5.1.1 (am aware it is a temp. root)
i have superSu Pro, do i need Super Sume for this to work?
Click to expand...
Click to collapse
I'm happy to help out! You'd need king root installed, root the tab with king root, then use SuperSU me to replace the kingroot binaries with the SuperSU ones. It is an automatic process and should only take about 30 seconds or less. Pro version of SUPERSUme is not required, free version should work just fine.
Cheers!
xjimmy said:
Somehow I had it permanently rooted with kingroot a while back. I had the 4.9.6 apk on my tab at the time, is all I know. I could've updated from an earlier version, and maybe that was the cause. I've tried so many different versions of kingroot with no luck, but one peculiar occurrence; if I open kingroot, get into the settings and uninstall kingroot without saving a backup of root, then delete all the files in the tablet's main directory, and reinstall kingroot version 4.8.0, it somehow retains a partial permanent root. At least on my T337A running 5.1.1 BOH4 it will, as long as I get a fresh install of 4.8.0, let it root, then hit the optimize button right after. Then wait until it finally tells me that kingroot has been deployed as a system app. After that, when I try to open any root apps, the screen will darken as it does when the root permission tab pops up, but it never pops up. The app just freezes. I can kill it in the task manager screen to just go back to using my tablet. After I restart the tab, sometimes it'll tell me an app has been granted superuser permissions. If I open up terminal emulator, type in the 'su' command and hit enter, the screen will turn dark again like it's going to ask me to allow or deny superuser permission, but it just freezes like that again. I've tried all kinds of stuff with 4.8.0, but I still can't get it to stick. If you don't hit the optimize button in kingroot right after rooting, and just wait for kingroot to install as a system app, the allow/deny prompt comes up without freezing, but the partial permanent root glitch doesn't remain. ugh, tired of messing with it though. lol
Edit: I may be wrong. It might need to be rooted with 4.8.0, optimized, then rebooted right away for the partial root. I'll try to do it again and let you know what I find.
Click to expand...
Click to collapse
Kingroot does allow your device to retain permanent root after a certain time. However, Kingroot is not as powerful as SuperSU, is very limited in terms of what It can do, and has it's own 'bloatware' titled Purify. I'd honestly stick with SuperSU because it's (probably) the most powerful and efficient way to root your phone. I'd also suggest avoiding having to reboot the tablet at all with temp root because you would have to take 5 minutes to install it again, which was a pain in the butt for me.
As for the kingroot app freezing, that's usually the result of a bad download or a bad root. Plus kingroot is very limited in terms of what you can do on your kingrooted device. SUPERSU is the equivalent of an IOS jailbreak. SUPERSU gives you full control of your device, with no bloatware and limits, unlike kingroot.
Kingroot does sometimes delete the su binaries upon rebooting, which is another reason I don't like it all that much.
Another theory I thought of is that it's not Kingroot that's deleting the binaries, it's actually something that's set to happen when the device boots up. Either the actual Android os or the bootloader searches for and deletes the su binaries to prevent root.
I don't know for sure, I've kinda slowed down work on this device mainly because of a project I've been working on with the Samsung Galaxy S7 AT&T (SM-G930A). I'll look into these things when I get the chance.
Cheers!
I understand the limitations of Kingroot, and certainly supersu by all means is better. In the case of flashfire with supersu in this scenario, it's merely the difference of being able to open and run it just enough to work improperly and brick your device vs. Kingroot not being able to open it at all. I posted in a thread long before this one, how to replace kingroot with supersu, only I use the zip file in terminal emulator. Pretty sure I went over flashfire as well. The terminal emulator method works with new versions of kingroot, unlike supersu me. Are you suggesting that the T337A running 5.1.1 BOH4 can achieve permanent root via kingroot after "a certain amount of time"? Because I'm the only one I've seen on xda who's ever posted that they had permanent root from kingroot, but I didn't know how I did it. After I messed with things, i softbricked and had to flash back to stock, which, no offense, the stock file was available way before you posted it. Anyway, it's not the kingroot app freezing per se, i was talking about after rebooting, and without re-rooting, when trying to use rooted apps, they actually start to engage in the kingroot request superuser permissions pop-up. So, no, it's not a bad download, etc. I believe an older version of kingroot somehow permanently rooted my tab, perhaps with the help of something I was messing with at the time, perhaps not. I've intentionally rebooted my tab an unimaginable amount of times, testing to see if I possibly regained permanent root to no avail, so I know how that works. And it's not about having a hard time deciding on kingroot or supersu for a temproot, it's the interest in permanent root, the possibility off something like safestrap, and/or flashing custom roms, etc. When people say temproot is better or safer, i say boo. How many custom roms include a root toggle in the settings? Anyway I wish I could've gotten hold of a developer while I had permanent root. Maybe I could've done a system dump, or even try replacing the permanent kingroot with supers and drying out that could've stuck. You say you slowed down on this device, do you mean you were pursuing permanent root for it? Are you a developer? I have the AT&T S7 Edge (G935A). What's your project on the 930? Is it something for rooted S7's? I still have my edge running the engboot with the echoRom. Anyway, thanks for your reply.
---------- Post added at 01:01 AM ---------- Previous post was at 12:51 AM ----------
https://forum.xda-developers.com/tab-4/help/t337a-temp-root-bootlp-fix-tar-official-t3473737
*https://forum.xda-developers.com/tab-4/general/permanent-root-t337a-5-1-1-kingroot-t3518334
A couple of threads I started a long time ago that may be of interest to you.
xjimmy said:
I understand the limitations of Kingroot, and certainly supersu by all means is better. In the case of flashfire with supersu in this scenario, it's merely the difference of being able to open and run it just enough to work improperly and brick your device vs. Kingroot not being able to open it at all. I posted in a thread long before this one, how to replace kingroot with supersu, only I use the zip file in terminal emulator. Pretty sure I went over flashfire as well. The terminal emulator method works with new versions of kingroot, unlike supersu me. Are you suggesting that the T337A running 5.1.1 BOH4 can achieve permanent root via kingroot after "a certain amount of time"? Because I'm the only one I've seen on xda who's ever posted that they had permanent root from kingroot, but I didn't know how I did it. After I messed with things, i softbricked and had to flash back to stock, which, no offense, the stock file was available way before you posted it. Anyway, it's not the kingroot app freezing per se, i was talking about after rebooting, and without re-rooting, when trying to use rooted apps, they actually start to engage in the kingroot request superuser permissions pop-up. So, no, it's not a bad download, etc. I believe an older version of kingroot somehow permanently rooted my tab, perhaps with the help of something I was messing with at the time, perhaps not. I've intentionally rebooted my tab an unimaginable amount of times, testing to see if I possibly regained permanent root to no avail, so I know how that works. And it's not about having a hard time deciding on kingroot or supersu for a temproot, it's the interest in permanent root, the possibility off something like safestrap, and/or flashing custom roms, etc. When people say temproot is better or safer, i say boo. How many custom roms include a root toggle in the settings? Anyway I wish I could've gotten hold of a developer while I had permanent root. Maybe I could've done a system dump, or even try replacing the permanent kingroot with supers and drying out that could've stuck. You say you slowed down on this device, do you mean you were pursuing permanent root for it? Are you a developer? I have the AT&T S7 Edge (G935A). What's your project on the 930? Is it something for rooted S7's? I still have my edge running the engboot with the echoRom. Anyway, thanks for your reply.
---------- Post added at 01:01 AM ---------- Previous post was at 12:51 AM ----------
https://forum.xda-developers.com/tab-4/help/t337a-temp-root-bootlp-fix-tar-official-t3473737
*https://forum.xda-developers.com/tab-4/general/permanent-root-t337a-5-1-1-kingroot-t3518334
A couple of threads I started a long time ago that may be of interest to you.
Click to expand...
Click to collapse
No offence taken on the firmware post, I was simply trying to spread the fact that the firmware for the device does exist but is very hard to find and is often posted on shady websites for money, unless you're looking in the right places. It only took me 5 minutes on Google to find one of those sites.
You asked if I was saying that the Tab 4 BOH4 firmware allows you to retain permanent root after some time, and yes, that's exactly what I was saying. I rooted my tablet with Kingroot 4.8.0 a while back and after about 4 - 5 reboots (I counted how many times I rebooted it, but the numbers could vary), It retained root. All I do today is avoid rebooting the tablet at all costs. I prefer SuperSU because, like we've said, there are almost no limitations of what you can do in terms of being rooted. I'm trying to find out how I can make root permanent on the tab with SuperSU by using the eng-boot method used to root all Qualcomm variants of the Galaxy S7, but that may take a while. Since my S7 has the eng-boot root method, I can reboot it all I want and it stays rooted with SuperSU. But at this point, It's just an Idea. I mainly need to find out whether or not the bootloader or the os is wiping the binaries on boot. Some older and newer versions of kingroot can retain root after reboot, but I have yet to find a version of the app that can do so.
Actually, some versions of Cyanogenmod and other custom roms had root pre-installed (not like SuperSU, but close enough), and like CM specifically, there was a section in the settings app for this pre-baked root. Even if I still used CM today, I still would've flashed SuperSU. But on a small number of devices, temp root really is better. However, most of those devices that would be on that list have very little to no development on them. Thus, they are not yet (and may never be) supported for permanent root.
I am partially on the road to becoming a developer, but I don't know how far that's gonna go (my prediction is not that far at all). I was doing research on how I could make an eng-boot for the Tab 4, but I became interested in my Galaxy S7 (AT&T). By that, I mean I wanted to make my own custom version of the stock Marshmallow rom ("Custom but stock OS"). To shorten it up, I wanted to create a .zip flashable "super package" which included SuperSU v2.79, Viper4Android, Overclock tools, and other stuff. I've kinda been on and off in terms of motivation to make this idea a reality, primarily because most of the things I wanted to include in this "package", can easily be installed by you in like 3 minutes, or maybe less. The original motive behind the idea was to lessen the work for power users who wanted to free their device "from the shackles". I've been on and off on work between both devices, but It's hard for me to continue the work without proper motivation. These projects are merely just an Idea at this point, but some drafts and copies do exist on my computer.
Creating a custom Android rom straight from my own head is basically an impossible task for me, considering most of the devices I work with have locked bootloaders. I am still learning Java and other Android programming languages in some of my free time but, again, the motivation to continue is something I struggle to find.
Cheers!
Upgrading OS and rooting
I am currently running my t337a on 4.4.2 with build NK2. I was able to root with towel root awhile ago. I want to upgrade my os to 5.1.1 and root after but would like to make sure I go about it the right way.
Any help would be greatly appreciated. Thanks in advance!
loc626 said:
I am currently running my t337a on 4.4.2 with build NK2. I was able to root with towel root awhile ago. I want to upgrade my os to 5.1.1 and root after but would like to make sure I go about it the right way.
Any help would be greatly appreciated. Thanks in advance!
Click to expand...
Click to collapse
You can root on the latest Lollipop firmware, but it's systemless supersu/temporary, meaning it will go away if you shutdown or reboot the device (you can re-root it, of course, but It can be annoying). The option to upgrade is up to you, and once you do upgrade, you can't downgrade (Locked bootloader & different bootloader versions. Lollipop has the new bootloader.) If you are going to upgrade, you can flash the Lollipop firmware via Odin or upgrade via OTA. If upgrading, I recommend taking it over the air, mainly because I'm still working up Odin packages for them. The Odin packages that I do have available are the BOH4 (the previous and the initial Lollipop update) ones, so if you upgrade OTA, it'll take away one step in the upgrade process, making your life a tad bit easier. Reply back if you need further help or have any more questions.
Cheers!
KingOfTheNet said:
You can root on the latest Lollipop firmware, but it's systemless supersu/temporary, meaning it will go away if you shutdown or reboot the device (you can re-root it, of course, but It can be annoying). The option to upgrade is up to you, and once you do upgrade, you can't downgrade (Locked bootloader & different bootloader versions. Lollipop has the new bootloader.) If you are going to upgrade, you can flash the Lollipop firmware via Odin or upgrade via OTA. If upgrading, I recommend taking it over the air, mainly because I'm still working up Odin packages for them. The Odin packages that I do have available are the BOH4 (the previous and the initial Lollipop update) ones, so if you upgrade OTA, it'll take away one step in the upgrade process, making your life a tad bit easier. Reply back if you need further help or have any more questions.
Cheers!
Click to expand...
Click to collapse
I'm highly considering an upgrade for the feel and hopefully a better performance. Also, a few apps I have need updates but only compatible on Android 5 and up. I have the OTA ready to go. Would I need to unroot before upgrading the OS?
loc626 said:
I'm highly considering an upgrade for the feel and hopefully a better performance. Also, a few apps I have need updates but only compatible on Android 5 and up. I have the OTA ready to go. Would I need to unroot before upgrading the OS?
Click to expand...
Click to collapse
It would be best to unroot before installing to avoid any issues during the installation. Other then that, you're in the clear! Just remember, you cannot downgrade after the install!
Cheers!
KingOfTheNet said:
4) I'm trying to figure out how I could altar the boot.img so we can get permanent SuperSU on this thing the same way Chainfire did it with the US and Qualcomm Samsung Galaxy S7's.
Click to expand...
Click to collapse
I have always been under the assumption that the boot.img for the locked BL on the s7 was literally an engineering kernel from Samsung, and not something Chainfire created. The reason Im saying this is because if Chainfire created a boot image that can get around a locked bootloader, then logic should state that he cracked Sprint/ATT's signature for the BL. So my way of thinking is the success of even one locked boot loader ... it should apply across the board for all, correct? Or am I waaaaay off? lol
leeboski44 said:
I have always been under the assumption that the boot.img for the locked BL on the s7 was literally an engineering kernel from Samsung, and not something Chainfire created. The reason Im saying this is because if Chainfire created a boot image that can get around a locked bootloader, then logic should state that he cracked Sprint/ATT's signature for the BL. So my way of thinking is the success of even one locked boot loader ... it should apply across the board for all, correct? Or am I waaaaay off? lol
Click to expand...
Click to collapse
(1st question) Actually yeah, lol. It was an engineering kernel, he didn't make it . I'm assuming that was used during the development of the phone so Samsung and AT&T could construct the OS without running into any issues with the phones locked bootloader. At the time, I thought that Chainfire thought of some "mad science" to altar the boot.img so that it wont check the signatures of any of the files on boot.
Now I'm thinking:
1) He found a way to obtain all the phones signatures so that way he knows what signature the desired files (like a build of TWRP, or instance) would have to have so it can flash and boot properly.
--OR--
2) He somehow obtained or reproduced the engineering kernel that, like I said, was most likely used during software development for the phone (constructing the OS and the rest of the software).
I've done a little research on what engineering kernels actually do and why they are so useful now (to most people, the name is enough, lol). Apparently, they completely skip some of the signature checks on boot, primarily for /SYSTEM (The OS), which is why we were able to achieve permanent root the Qualcomm Galaxy S7 & S7 edge models. I do not think they skip signature checks for /RECOVERY or /BOOT, but we know that if we either reproduce or obtain the engineering kernel for this tablet, we can achieve permanent root the exact same way. I could be wrong, as I do not know for certain the Ins and outs of engineering kernels and how to get them, but It is very possible.
(2nd question) Now, I do not have much knowledge of bootloaders and signature checks, but I would go to the best assumption that since Sprint & AT&T, for example, are 2 completely different companies and are not affiliated (as of writing this), their bootloaders and updates would not have the same signatures. If they did, then Sprint would have to go to AT&T to sign their updates and such, and AT&T would have to do the same thing for Sprint. It just wouldn't really make sense. Lets think of it this way, If Target wants to sell a product in their stores that's already sold at Walmart, then should Target have to go to Walmart to get that approved? Or if Walmart wanted to sell something that's already sold at Target, then should Walmart have to go to Target for approval? Absolutely not, that wouldn't make any sense. Once again, I could be wrong, but it would make the most sense.
Please, anyone, correct me if I'm wrong.
Cheers!
KingOfTheNet said:
(1st question) Actually yeah, lol. It was an engineering kernel, he didn't make it . I'm assuming that was used during the development of the phone so Samsung and AT&T could construct the OS without running into any issues with the phones locked bootloader. At the time, I thought that Chainfire thought of some "mad science" to altar the boot.img so that it wont check the signatures of any of the files on boot.
Now I'm thinking:
1) He found a way to obtain all the phones signatures so that way he knows what signature the desired files (like a build of TWRP, or instance) would have to have so it can flash and boot properly.
--OR--
2) He somehow obtained or reproduced the engineering kernel that, like I said, was most likely used during software development for the phone (constructing the OS and the rest of the software).
I've done a little research on what engineering kernels actually do and why they are so useful now (to most people, the name is enough, lol). Apparently, they completely skip some of the signature checks on boot, primarily for /SYSTEM (The OS), which is why we were able to achieve permanent root the Qualcomm Galaxy S7 & S7 edge models. I do not think they skip signature checks for /RECOVERY or /BOOT, but we know that if we either reproduce or obtain the engineering kernel for this tablet, we can achieve permanent root the exact same way. I could be wrong, as I do not know for certain the Ins and outs of engineering kernels and how to get them, but It is very possible.
(2nd question) Now, I do not have much knowledge of bootloaders and signature checks, but I would go to the best assumption that since Sprint & AT&T, for example, are 2 completely different companies and are not affiliated (as of writing this), their bootloaders and updates would not have the same signatures. If they did, then Sprint would have to go to AT&T to sign their updates and such, and AT&T would have to do the same thing for Sprint. It just wouldn't really make sense. Lets think of it this way, If Target wants to sell a product in their stores that's already sold at Walmart, then should Target have to go to Walmart to get that approved? Or if Walmart wanted to sell something that's already sold at Target, then should Walmart have to go to Target for approval? Absolutely not, that wouldn't make any sense. Once again, I could be wrong, but it would make the most sense.
Please, anyone, correct me if I'm wrong.
Cheers!
Click to expand...
Click to collapse
No that makes perfect sense and thanks for clearing it up.
The whole thing about the signature being the means by which the bootloader is locked is important. Atleast to me it is, so thank you for clearing that up. :good: And so, it makes sense that the System partitions Signature check being skipped IS what allows access to root. But where my opinion differs on this is the Boot and Recovery implementation of the Signatures. I believe that it IS the carriers implementation that does not allow the Recovery and Boot partitions to be modified. If it were Samsungs then how is Samsung going to incorporate a Universal bootloader that knows how to load all carriers data, policy, etc?
And possibly this is what you were saying above and I am misreading it...
***EDIT*** I see you said that the signatures would NOT be the same between carriers, so I am in line with your theory there as well.
leeboski44 said:
No that makes perfect sense and thanks for clearing it up.
The whole thing about the signature being the means by which the bootloader is locked is important. Atleast to me it is, so thank you for clearing that up. :good: And so, it makes sense that the System partitions Signature check being skipped IS what allows access to root. But where my opinion differs on this is the Boot and Recovery implementation of the Signatures. I believe that it IS the carriers implementation that does not allow the Recovery and Boot partitions to be modified. If it were Samsungs then how is Samsung going to incorporate a Universal bootloader that knows how to load all carriers data, policy, etc?
And possibly this is what you were saying above and I am misreading it...
***EDIT*** I see you said that the signatures would NOT be the same between carriers, so I am in line with your theory there as well.
Click to expand...
Click to collapse
I'm glad I could be of help, however I don't see where I stated that the signature implementations on the BOOT and RECOVERY partitions was Samsung's idea not the carriers, if you could point that out for me that would be great.:good:
The engineering kernels skip SOME signature checks, both when flashing and booting into partitions, but I do not know exactly which ones they skip. We know it skips some of the signatures for /SYSTEM, but it does not do the same for the 2 other main ones, those being /BOOT & /RECOVERY. We know because "one of our own" attempted to flash their own build of TWRP recovery to the device (SM-G930A to be specific) only to get a signature check fail when booting the phone, which of course means that the phone has a locked bootloader and that the signatures for the /RECOVERY partition are still checked, but I do not know for certain about /BOOT. If I had to assume I'd say that /BOOT isn't checked, given the fact that if your phone is rooted then you would have had to flash the engineering kernel, which, like I said, skips some signature checks.
I hope I've cleared most things up for you.
Cheers!
KingOfTheNet said:
I've made this thread to teach T337A owners how to root their device with SuperSU. Please note that this is a system-less root, meaning it's temporary, but can be re-applied. Rooting only takes about 5-7 minutes and brings numerous tweaks and advantages to your device. Just remember that every time you reboot or shut the device down, you will need to repeat the rooting process. This tutorial was designed for Lollipop 5.1.1, but it should work on KitKat as well.
Before beginning, you will need to download the following file, unzip it on your pc, then transfer it to your device's internal storage/external sd card.
Root File: https://mega.nz/#!74Jl0ZqY!knlHuexbYGFkk1f4wHxq16u3L38EtfR9scQ0H7hISTA
Lets start!
1) Install both the APK files in the file on your device, If prompted, allow installation from unknown sources.
2) Make sure your device is connected to WiFi, then open Kingroot.
3) Once Kingroot is "Done searching for the best root strategy", click the "Try Now" button and wait about 3 minutes for KingRoot to give you a "Root Successfully" message.
4) This is where it gets kinda tricky, immediately after receiving the root success message, go into SuperSU-me, and grant root permissions when prompted.
5) Click on the big blue button in the middle of the frame and wait about 1 minute for the process to complete. DO NOT UPDATE THE SUPERSU BINARY, IT WILL BOOTLOOP.
6) IMMEDIATELY after the process has completed, go into Settings and make sure KingRoot or Purify is not installed! This is an important step because Kingroot and Kingroot adware tends to install itself in the system partition which can cause problems and frustration.
7 - Recommended) Download a root file explorer and search "King" under /data and /system to ensure that the KingRoot app and its bloatware has been wiped from the system.
8) Enjoy root access!
If this tutorial helped you please be sure to hit the :good: button. If you had any issues or troubles during this process please feel free to let me know down below.
Need T337A firmware? Check out my thread here: https://forum.xda-developers.com/tab-4/general/download-sm-t337a-lollipop-firmware-t3536509
Cheers!
Click to expand...
Click to collapse
The firmware you provided saved my sm-t337A tablet from being soft bricked. Although I was able to gain temp root from this method, king root tried to disable the SELinux on my device and after trying to temp root again caused the app to implant itself as bloatware into the /systems folder and was non functional when using the app. Do you happen to know of a custom recovery (TWRP or CWM) which would work for this device?
Hi,
I know this is a NooB question, I know HOW to root my S4, and have a RIFF box, but I need an honest opinion.
I just bought a new mobo to replace my old one with the dead eMMC. It came with Android 4.3, Knox, and firmware version M919UVUEMK2. T-Mobile is offering me an OTA update to M919UVSFQA1 every 24 hours. I want to root my device, simply so they cannot take that ability away from me. I'm too busy really to develop my own apps now, but I don't think it's fair to tell me how I can and can't use MY phone.
If I accept the update, from what I read, it's most likely I will be able to root it, using CF Auto Root, but RegionLockAway (my phone is already unlocked from T-Mobile giving me the code - do I still need this?) may not work. Is M919UVSFQA1 still rootable? I know it will trip the KNOX bit, that's OK. If I root my M919UVUEMK2 the way it is, will it trip the KNOX bit?
Also, what are these "Security Policy Updates" offered by Google they are asking me to accept? Security policy for malware, or security policy against me?
I guess I want my cake and eat it too. I want the stability and security against malware, and the latest baseband, but I don't a security update against myself. If I root my phone the way it is (M919UVUEMK2), will it trip the KNOX bit anyway?
All I am asking is, have I got anything to lose by accepting the OTA update? Will I lose rooting / bootloader options, or is my bootloader already locked on MK2, and it will still trip the KNOX bit. If so, and nothing's different, I will accept the OTA update first so my phone is the latest OFFICIAL version, then I can be sure my new rooted phone is most stable, as I doubt T-Mobile will support a rooted phone.
My S4 employs E-Fuses (a.k.a. the "Knox" bit) and once they're blown, that's it. If you want them un-blown, you need to buy a new CPU hence a new mobo. This is why I'm wary of ANY update, especially security. (Google eFuse if you're interested in the technology). eFuse was a brilliant idea from IBM, but was abused like most other technology.
Thanks,
-Rob
filter4ever said:
Hi,
I know this is a NooB question, I know HOW to root my S4, and have a RIFF box, but I need an honest opinion.
I just bought a new mobo to replace my old one with the dead eMMC. It came with Android 4.3, Knox, and firmware version M919UVUEMK2. T-Mobile is offering me an OTA update to M919UVSFQA1 every 24 hours. I want to root my device, simply so they cannot take that ability away from me. I'm too busy really to develop my own apps now, but I don't think it's fair to tell me how I can and can't use MY phone.
If I accept the update, from what I read, it's most likely I will be able to root it, using CF Auto Root, but RegionLockAway (my phone is already unlocked from T-Mobile giving me the code - do I still need this?) may not work. Is M919UVSFQA1 still rootable? I know it will trip the KNOX bit, that's OK. If I root my M919UVUEMK2 the way it is, will it trip the KNOX bit?
Also, what are these "Security Policy Updates" offered by Google they are asking me to accept? Security policy for malware, or security policy against me?
I guess I want my cake and eat it too. I want the stability and security against malware, and the latest baseband, but I don't a security update against myself. If I root my phone the way it is (M919UVUEMK2), will it trip the KNOX bit anyway?
All I am asking is, have I got anything to lose by accepting the OTA update? Will I lose rooting / bootloader options, or is my bootloader already locked on MK2, and it will still trip the KNOX bit. If so, and nothing's different, I will accept the OTA update first so my phone is the latest OFFICIAL version, then I can be sure my new rooted phone is most stable, as I doubt T-Mobile will support a rooted phone.
My S4 employs E-Fuses (a.k.a. the "Knox" bit) and once they're blown, that's it. If you want them un-blown, you need to buy a new CPU hence a new mobo. This is why I'm wary of ANY update, especially security. (Google eFuse if you're interested in the technology). eFuse was a brilliant idea from IBM, but was abused like most other technology.
Thanks,
-Rob
Click to expand...
Click to collapse
There are several threads covering most of your questions or at least have answers somewhere in them in the Tmobile S4 forum if you take the time to search and read. I don't have Tmobile S4 so I don't know the details.
And it's called qfuse in Samsung devices, not e-fuse.
Sent from my SM-S903VL using Tapatalk
Thanks
Thanks. I've had a lot of homework so I haven't had the time to search very deep. I found a Knox less NH7 update and installed it, guess I'm just going to have to wait for the OTA to become available.
qFuse
Droidriven said:
There are several threads covering most of your questions or at least have answers somewhere in them in the Tmobile S4 forum if you take the time to search and read. I don't have Tmobile S4 so I don't know the details.
And it's called qfuse in Samsung devices, not e-fuse.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Thanks. If you're interested, I found the code that burns qfuses. Bootloader.rollback(blowFuse) at 0x00004000 (I think). Has only to do with bootloader upgrades.
Qfuse, for Qualcomm, duh. Still the same thing though. It makes me sick that they would go THAT FAR to prevent even the advanced nerds from doing with... I guess I'll say Samsung 'so phone now, I won't buy an S7 if I don't own it fully. It's the principal, I can understand if it is their network they are worried about security, but I don't see how that is an issue. if I buy it, it's mine. If I fixed it from the garbage, it's REALLY mine. Just who do they think finds these bugs and security flaws? The average user? If phones get bricked, wouldn't they want to hire someone who learned what they're doing? Using to pirate apps, OK, I can see that it not right. Running your own software and being able to repair the firmware? If I can run it over with my car and break it, I should be allowed to do anything in between.
Anyways, thats my rant about qfuses, efues, any permenent harfware changes being used this way.
filter4ever said:
Thanks. If you're interested, I found the code that burns qfuses. Bootloader.rollback(blowFuse) at 0x00004000 (I think). Has only to do with bootloader upgrades.
Qfuse, for Qualcomm, duh. Still the same thing though. It makes me sick that they would go THAT FAR to prevent even the advanced nerds from doing with... I guess I'll say Samsung 'so phone now, I won't buy an S7 if I don't own it fully. It's the principal, I can understand if it is their network they are worried about security, but I don't see how that is an issue. if I buy it, it's mine. If I fixed it from the garbage, it's REALLY mine. Just who do they think finds these bugs and security flaws? The average user? If phones get bricked, wouldn't they want to hire someone who learned what they're doing? Using to pirate apps, OK, I can see that it not right. Running your own software and being able to repair the firmware? If I can run it over with my car and break it, I should be allowed to do anything in between.
Anyways, thats my rant about qfuses, efues, any permenent harfware changes being used this way.
Click to expand...
Click to collapse
I'll check out that qfuse code just for curiosity.
The main reason they work so hard to prevent even advanced users from altering the devices is because they got tired of losing money replacing devices under warranty that had been bricked, technically the warranty is voided when a device is modified but when fully bricked they can't tell that their was any attempt to modify it.
I agree, when you buy something it is yours to do with as you wish but most devices on plan aren't owned, technically they are considered mortgaged property, these devices that are advertised as free with a plan aren't free, it's being paid for in your monthly bill. This means it's just like financing a car, you have to have full collision insurance coverage to protect their investment. That is, in effect, the thing that gives Samsung or your carrier the right to do what they've done to protect their investment.
It would be a logistical nightmare if they had it so that people that actually own the devices didn't have to worry about qfuse but at the same time have it so that customers still paying for the device do have to worry about qfuse, so they just have them all like that across the board.
Sent from my SM-S903VL using Tapatalk
It's in the partition "SBL3" at offset 0x31160. I have a dump of my phone if interested, but I would like to remove specifics (make sure I'm not signed in, did factory wipe, imei, etc)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It appears to be C code (compiled possibly encrypted) before or after the file name. Please don't let this fall into the wrong hands :0
I bought an app, "MobileODIN", that seemed a bit iffy, but I thought I'd give it a try. T-Mobile has the OTA update, they want me to use Kies (yeah, right) so I am using that stupid RapidGator thing (oh well, at least they dont ask for my credit card, I mean, WTF?, who would do such a thing)? Anyways, EverRoot - Part of the PRO version I bought as I wanted to try Loli but KitKat is the latest. T-Mo just released M919UVSFQA1 on 2/8, if I can do things like EverRoot, do you think it would successfully castrate that code? Even if it can preserve root, if I lost it, I may not be able to get it back. Right now I'm running the M919UVUFNH7 Stock Rooted, Permissive NH7, and NH7 non-hlos and it works good. Read a couple posts on mobile ODIN and it did say it would root firmware, keeping it from being lost, BUT - not a full stock image (which possibly has boot.img - just what that nasty little firebug code is looking for in SBL3). I will post in mobile ODIN, but have you heard of an unlocked boot.img, one that doesn't have this nasty little line of code?
Just took upgrade.
Well i just flashed the ota with odin and even with supersu pro 2.79 runing survival mode it took root from me. Now. I know this may be a shot in the dark here but what about doing something similar of the i337 and flashing a previous kernal rooting locking in survival and then reflashing kernal? I have thr ota file saved on my laptop if you would need it to break it down and see what is possible. I will toy around with it as i have time to. Having 4 youngins gets a little difficult to have a whole lot of time to invest myself to most of this stuff anymore. Eventually it will work right? Lol GL And let me know if we want to give this a shot or not
xXxCyanidexXx
Been playing around the with the new upgrade trying to find some sort of root method for it. I was able to run king root and got it to suscessfully get root access, after running it like 4 or 5 times in a row. However I didn't really care much for king root itself. Just the extra unnecessary garbage it has. So I tried to swap root management over to super su.... so far i have not had any luck with that part yet.... ain't giving up on it though, so as soon as I find something successfully able to get root aside from kingroot I will let you guys know.
xXxCyanide87xXx said:
Been playing around the with the new upgrade trying to find some sort of root method for it. I was able to run king root and got it to suscessfully get root access, after running it like 4 or 5 times in a row. However I didn't really care much for king root itself. Just the extra unnecessary garbage it has. So I tried to swap root management over to super su.... so far i have not had any luck with that part yet.... ain't giving up on it though, so as soon as I find something successfully able to get root aside from kingroot I will let you guys know.
Click to expand...
Click to collapse
Did you try the Supersume app? Did you try normal SuperSU or did you try systemless SuperSU?
Just make sure you get rid of everything else that came along with Kingroot, it's malware.
Sent from my SM-S903VL using Tapatalk
Switched around some...
Well I got tired of the king root app really didnt want to do the bloat removal so I switched to kingo root which so far seems to be doing OK. Still no luck on SuperSu. I tried just normal SuperSu & SuperSu Pro.. also tried 2 different apk fIles for SuperSu Me one just kept saying License Verified (no app just black screen flash then that) the other one loaded the actual app and when I clicked the blue bubble thing it said please wait whIle environment is loaded & load bar went maybe 1/20 of the way then just sets there going no further. Going to mess with it some more here later on. Have a little St. Patrick's day baby girl to prepair a 1st birthday party for. I'll keep you posted when I find out more.
xXxCyanide87xXx said:
Well I got tired of the king root app really didnt want to do the bloat removal so I switched to kingo root which so far seems to be doing OK. Still no luck on SuperSu. I tried just normal SuperSu & SuperSu Pro.. also tried 2 different apk fIles for SuperSu Me one just kept saying License Verified (no app just black screen flash then that) the other one loaded the actual app and when I clicked the blue bubble thing it said please wait whIle environment is loaded & load bar went maybe 1/20 of the way then just sets there going no further. Going to mess with it some more here later on. Have a little St. Patrick's day baby girl to prepair a 1st birthday party for. I'll keep you posted when I find out more.
Click to expand...
Click to collapse
Ok, try SuperSU in systemless mode, it'll probably work for you. Good luck.
Sent from my SM-S903VL using Tapatalk
Just got home gonna get twrp .tar for Odin and the systemless zip and see what I don't break lol
New firmware successfully rooted using Kingo Root to initially access root then flashing TWRP 3.1.0-0 using Mobile Odin Pro then flashed SuperSU 2.79 with TWRP after recovery was flashed. Rebooted no problems, then froze Kingo and removed it...
Yes I'm sure there a far easier way to do this but I am patting myself on the back for not screwing up the phone considering I have still yet to back anything up >. < So thanks for starting this post and giving me something to amuse myself with these past couple of days (-:
xXxCyanide87xXx said:
New firmware successfully rooted using Kingo Root to initially access root then flashing TWRP 3.1.0-0 using Mobile Odin Pro then flashed SuperSU 2.79 with TWRP after recovery was flashed. Rebooted no problems, then froze Kingo and removed it...
Yes I'm sure there a far easier way to do this but I am patting myself on the back for not screwing up the phone considering I have still yet to back anything up >. < So thanks for starting this post and giving me something to amuse myself with these past couple of days (-:
Click to expand...
Click to collapse
Good to go. Actually, the method you used is about the easiest, it's commonly the go-to method if Supersume doesn't work. You did good.
Sent from my SM-S903VL using Tapatalk
Thanks for the update!
So you flashed OTA at first, then re-rooted using KingoRoot? I used CF Auto Root, and CF RegionLockAway before upgrading to NH7, but I haven't tried this yet.
Here's the firmware for all who want to flash the old fashioned way using ODIN (not OTA or Kies).
Rapidgator Mirror: http://rapidgator.net/file/cc090b9fd3b077b9041ff1b6df3bf889
AltaFile Mirror: https://alfafile.net/file/vbGh
If these links don't work (I had a hell of a time), PM me or post below, I can send you a direct link.
Did you originally try to flash using Mobile Odin, regular Odin, or the OTA stock update? I don't know if mobile ODIN works yet - I'm not really into nightly builds yet. The only reason I bought mobile ODIN was because if it already HAS root, it can "castrate" the code like this:
I found in SBL3. My "new" mobo that came with M919UVUFMK2 (WITH knox ). Jellybean 4.3, I asked for a 4.2.2, but they didn't have any in stock. I disabled KNOX, but I think this is still in here.
Thank you for letting me know, I finally rooted the MK2 using CF Auto Root, T-Mo gave me the unlock code (since my previous mobo was already unlocked and IMEI changed), but I used CF Region Lock Away before upgrading. (Works GREAT, but not sure on the new firmware). I ended using this stock M919UVUFNH7, Non SE Enforcing (Permissive) Kernel, and NON-HLOS modem found here:
https://forum.xda-developers.com/ga...stock-base-4-4-4-nh7-rooted-deodexed-t2873695
If any of you developers make a modded version of this stock firmware QA1 (like NH7 above), let me know.
I just heard on the radio that Samsung (as well as other manufacturers) are desperately trying to improve the security of their devices, as they are paranoid of the govt getting in (like the story about their smart TVs), so I wouldn't be surprised of them (at least trying to) take rooting capability away soon.
SuperSU
xXxCyanide87xXx said:
Well I got tired of the king root app really didnt want to do the bloat removal so I switched to kingo root which so far seems to be doing OK. Still no luck on SuperSu. I tried just normal SuperSu & SuperSu Pro.. also tried 2 different apk fIles for SuperSu Me one just kept saying License Verified (no app just black screen flash then that) the other one loaded the actual app and when I clicked the blue bubble thing it said please wait whIle environment is loaded & load bar went maybe 1/20 of the way then just sets there going no further. Going to mess with it some more here later on. Have a little St. Patrick's day baby girl to prepair a 1st birthday party for. I'll keep you posted when I find out more.
Click to expand...
Click to collapse
I'm a NooB but the only thing I can think of is that CF may have not updated SuperSU for this kernel version. Can you post your details ("Settings" > "More" > "About Device")? I still haven't updated, NH7 works OK.
Rooting without SuperSU is scary. I make sure to turn off "Auto MMS download" as I once thought I got an MMS virus with rooted firmware and just about had to change my shorts.
Here is a screenshot of my phones info... kernel build ect. Let me know if you need anything else. Or just need help in general with your phone.
filter4ever said:
Thanks for the update!
So you flashed OTA at first, then re-rooted using KingoRoot? I used CF Auto Root, and CF RegionLockAway before upgrading to NH7, but I haven't tried this yet.
Here's the firmware for all who want to flash the old fashioned way using ODIN (not OTA or Kies).
Rapidgator Mirror: http://rapidgator.net/file/cc090b9fd3b077b9041ff1b6df3bf889
AltaFile Mirror: https://alfafile.net/file/vbGh
If these links don't work (I had a hell of a time), PM me or post below, I can send you a direct link.
Did you originally try to flash using Mobile Odin, regular Odin, or the OTA stock update? I don't know if mobile ODIN works yet - I'm not really into nightly builds yet. The only reason I bought mobile ODIN was because if it already HAS root, it can "castrate" the code like this:
I found in SBL3. My "new" mobo that came with M919UVUFMK2 (WITH knox ). Jellybean 4.3, I asked for a 4.2.2, but they didn't have any in stock. I disabled KNOX, but I think this is still in here.
Thank you for letting me know, I finally rooted the MK2 using CF Auto Root, T-Mo gave me the unlock code (since my previous mobo was already unlocked and IMEI changed), but I used CF Region Lock Away before upgrading. (Works GREAT, but not sure on the new firmware). I ended using this stock M919UVUFNH7, Non SE Enforcing (Permissive) Kernel, and NON-HLOS modem found here:
https://forum.xda-developers.com/ga...stock-base-4-4-4-nh7-rooted-deodexed-t2873695
If any of you developers make a modded version of this stock firmware QA1 (like NH7 above), let me know.
I just heard on the radio that Samsung (as well as other manufacturers) are desperately trying to improve the security of their devices, as they are paranoid of the govt getting in (like the story about their smart TVs), so I wouldn't be surprised of them (at least trying to) take rooting capability away soon.
Click to expand...
Click to collapse
Yes I flashed it first.
This is the order I did it all
1 - downloaded firmware ( rom https://samsung-firmware.org )
2 - Flashed update using Odin PC version (search forums there are links everywhere.
3- downloaded Kingo root from https://www.kingoapp.com and ran root process (may take a couple times... if it fails immediately run it again
4 - after root was successful I then downloaded Mobile Odin (lite or pro your choice. I used Mobile Odin Pro. Check forums for links to download.
5- Download Twrp 3.1.0-0 follow
https://forum.xda-developers.com/ne...recovery-twrp-2-8-7-0-touch-recovery-t3234976 follow steps to retrieve .tar file. MAKE SURE IT IS CORRECT FILE FOR INSTALLATION.
Don't flash yet
6- down load SuperSu 2.79 SR3 .zip from
h1ttps://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Now we flash.
7 run Mobile Odin and click recovery. Place Twrp there. Then scroll down to after flash and click. Set it for reboot recovery. Run.
8- After TWRP loads click on Flash .Find SuperSu 2.79 select and flash. Reboot to System (I went ahead and wiped just the regular cache partition then rebooted)
9- Run SuperSu (if prompted by Kingo for root then allow.
10- Using something abe to freeze/Remorvebe (Root Essentials, Lucky Patcher, something of that sort) then proceed to freeze and remove all the kingo junk and bloat.
11- Reboot phone and enjoy.
Now I will warn you the Samsung-firmware is slow for download. So if need be and I am allowed to. I have the firmware file I can upload on here for everyone.
I take no responsibility for any damage that can &/or may happen to your device this method worked for me. Doesn't guarantee that this method will work for you. GL and happy rooting ^__^
qFuse Code
Droidriven said:
I'll check out that qfuse code just for curiosity.
The main reason they work so hard to prevent even advanced users from altering the devices is because they got tired of losing money replacing devices under warranty that had been bricked, technically the warranty is voided when a device is modified but when fully bricked they can't tell that their was any attempt to modify it.
I agree, when you buy something it is yours to do with as you wish but most devices on plan aren't owned, technically they are considered mortgaged property, these devices that are advertised as free with a plan aren't free, it's being paid for in your monthly bill. This means it's just like financing a car, you have to have full collision insurance coverage to protect their investment. That is, in effect, the thing that gives Samsung or your carrier the right to do what they've done to protect their investment.
It would be a logistical nightmare if they had it so that people that actually own the devices didn't have to worry about qfuse but at the same time have it so that customers still paying for the device do have to worry about qfuse, so they just have them all like that across the board.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I agree, and I don't have a problem with the qFuse "Warranty Bit" for that reason... when it says "This Will Void Your Warranty" it means exactly that. Like I said, when I buy something it's mine (including, Samsung doesn't have to support it if I screw it up).
Are there any custom variations with permissive kernel of this firmware yet? Tried looking around here and searching, none yet... this post of mine appears to be my latest. If you would like this firmware I'll provide the link.
Now that I have SuperSU Pro and Mobile ODIN pro, do I still have to worry about that bootloader qFuse code (my guess is they flashed the locked bootloader and it's already been executed) I just don't want this new update to screw me, and didn't worry about it for a year, but now my phone is acting funky.... showing ads when I open the "Lock Screen" etc. I got Super SU Pro specifically because... an Android virus... with ROOT privileges = anyone's WORST nightmare. Just look at the /dev folder, not to mention "ps -l -C", or "pidstat -l -C" (and other commands I'm not familiar with yet). Listen to you, take pictures of you, steal your data, your passwords, do something illegal and blame it on you (Use your phone as a PSTN and Internet proxy).... you name it. (also it being mine applies to they don't have to support security updates as well - caveat to all rooters that's the 'Catch 22').
LOL, thats more than my Brain Can Handle
I have the same phone.. samsung s4 with the m919uvsfqa1 . It was from Tmobile, i bought the phone in canada and have it locked to Fido in Ontario , Canada. The fact the phone is Canadian, is likely irrelevant. As the Revision is the same as the phone ASHLEY has rooted.
I want to Multitask Apps, and the Samsung Apps that are Preinstalled do not offer the ones i want.
So I read, that if i Root the Phone then any app can be Multi-Window.
As I see Ashleys , rooting was quite difficult. I ask is it Possible to Root this Phone. For someone that really dont know what they are doing. I would need, a very detailed plan that i could follow but am not able to Follow Ashleys plan. Is there a New Method since your THREAD was POSTED?
I doubt any Local Tech would ROOT THIS for a Price, in Sault Ste Marie Ontario... as the stores wont void warranty and i dont know any Techs.
I need to get something done, so that i can access the Calendar app to add Information while talking on the Phone. So far i have to hang up the phone to enter information to the Calendar. That doesn't seem like a Smartphone....
I very recently purchased (as in less than a week ago) a Google Pixel (5") from the Google Play store. I would like to root it, but have a few questions that I could only seem to find vague answers to online. Firstly, does the Google Play purchased version of this phone come automatically with an unlocked bootloader? I saw several posts online that this was the case, but the posts are all pretty old (10/2016, about 9 months ago) and nothing really since then. Is there a way to verify/check if the bootloader is unlocked?
Secondly, the phone I got has Android 7.1.2 (build NKG47L). These - posts look to be the most recent info on rooting this phone, but they mention a different build number. Does anyone know if this is still an accurate process?
Unlock bootloader in developer options by toggling, then use OEM unlock in fastboot, Install TWRP, and flash latest superSU in TWRP. Done.......
Sent from my Pixel using Tapatalk
Are you the same alienjon as on FB, with the Light Whip?
Bootloader is probably locked - it was on mine when new from Google Play - Aus and about 6 months ago, but locked bootloader is part of Google policy so it probably still is. Unlock like this:
https://android.gadgethacks.com/how-to/unlock-bootloader-your-google-pixel-pixel-xl-0174627/
be aware that unlocking the bootloader will wipe your phone (would keep your data secure it someone had stolen it and was unlocking it to hack it), so do that early.
I root as per Chainfire's instructions, there's no easy way to update and keep root at the moment (Flashfire is supposed to work but it doesns't for me) so I reroot after each update, worked for the June update.
There are a few things to be aware of; TWRP is up to 302rc2 but some people have had trouble with that, I still use twrp 302 rc1 which works reliably (just boot it, to flash SU then reboot I haven't installed it). SU is currently 2.82 and as of the May update Pixel needs the boot image signed, which borked SU. Chainfire released a fix, a .zip which you need to flash after the SU zip as per this thread:
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
(apparently you can do without it for the June version of Pixel update, haven't checked that myself). Future versions of SU will include signing as part of the main install. I fine it useful to keep an eye on Chainfire's Google+ account which has links to the latest versions and any other significant changes:
https://plus.google.com/+Chainfire
Finally, did you mean to post your question twice? I think you can probably delete the second instance if you want to, save having replies scattered around.
@maulich That's perfect. Took me about an hour and a half to root, but most of that was reading and re-reading instructions to make sure I didn't mess anything up. I did notice that there is now some device protection feature that gets disabled when you unlock the bootloader. I checked online and it seems that this basically is a feature that factory resets the device in case someone tried to force themselves into a stolen device. I'll look around, but any suggestions for security features to implement for a rooted device?
@Clancy_s Sorry to disappoint, but no relation to an alienjon on FB. You are correct that it was locked, but I really love how easy it is to unlock. I'm used to phones purchased from Verizon that are beastly to unlock. My last phone (Galaxy S5) never got a workaround for the bootloader from what I recall (though after the Towel Root process stopped working it was almost a year and a half before a new rooting procedure was discovered - kudos to the devs that figured that problem out!)
In any event, thanks for the input on unlocking and rooting. I looked at a few different websites, but the procedure appears to be the same for unlocking that you found. This is the rooting procedure I used and worked fine, though the directions weren't as straightforward as you'd think; ie: the latest TWRP has a .zip but no .img to download on their website and I didn't trust anything else I found online that claimed to be the correct .img file. I used the next most recent version (RC1 - I saw several warnings against the alpha builds) and didn't have any problems. I also used the latest SuperSU (2.82, I believe). A few posts mentioned sticking with 2.79 because of bugs with the newer version, but those were from several months ago and elsewhere it stated that this issue was fixed. It seems to be working great for me
Clancy_s said:
SU is currently 2.82 and as of the May update Pixel needs the boot image signed, which borked SU. Chainfire released a fix, a .zip which you need to flash after the SU zip as per this thread:
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
(apparently you can do without it for the June version of Pixel update, haven't checked that myself). Future versions of SU will include signing as part of the main install. I fine it useful to keep an eye on Chainfire's Google+ account which has links to the latest versions and any other significant changes:
Click to expand...
Click to collapse
Unfortunately I didn't see your post until after I rooted. I can verify, though, that flashing the SuperSU zip worked fine without any additional steps. (ie: boot into TWRP image, flash TWRP and SuperSU zips, which I did together).
Clancy_s said:
Finally, did you mean to post your question twice? I think you can probably delete the second instance if you want to, save having replies scattered around.
Click to expand...
Click to collapse
I did not. When I tried to submit my initial post I got a server error. It didn't look like anything had gone through so I went back and resubmitted, which worked. I later realized that the first post did, in fact, go through but I couldn't figure out how to delete it. My apologies for the dupe.
alienjon said:
I couldn't figure out how to delete it. My apologies for the dupe.
Click to expand...
Click to collapse
In a web browser either on the PC or on the phone, click the exclamation point in the triangle /!\ in the lower left corner of the post you want to report, report it to a moderator and ask them to please delete it, or move it, if you ever post something in the wrong section.
Thanks. I'll remember that in case it comes up again.