Database Info

So you can no longer root p900?

I sold my p905 a while back, going to get a p900 however, the biggest factor is able to delete files on the sd card. I know I have to root it, however, from what I read there's issues and you can no longer root it?.

rirawin said:
I sold my p905 a while back, going to get a p900 however, the biggest factor is able to delete files on the sd card. I know I have to root it, however, from what I read there's issues and you can no longer root it?.
Click to expand...
Click to collapse
Use Odin to Flash TWRP then use TWRP to Flash Super SU.

nrage23 said:
Use Odin to Flash TWRP then use TWRP to Flash Super SU.
Click to expand...
Click to collapse
Thanks, so no issues with rooting with latest firmware?.

http://androidxda.net/root-samsung-galaxy-note-pro-12-2-all-variants-on-android-4-4-2-kitkat/
This guide?, been ages since I rooted.

rirawin said:
http://androidxda.net/root-samsung-galaxy-note-pro-12-2-all-variants-on-android-4-4-2-kitkat/
This guide?, been ages since I rooted.
Click to expand...
Click to collapse
I love how that guide says all variants and then makes no mention of the P907. I would love to be able to use a custom recovery. Unless the P907 falls under the LTE moniker even though the model number is different?

Yes, TWRP works with P900
I went through this a week ago (with some help) and once I figured out how to get TWRP 2.8 to flash using Odin the process of rooting and installing a custom rom was easy. There is a thread a little lower on this forum that goes through the process.
Keith

do you have the link please.
What happens if I wish to unroot?

rirawin said:
do you have the link please.
What happens if I wish to unroot?
Click to expand...
Click to collapse
I can't post a link but the thread is in this forum. I have not unrooted but there are several threads that mention going back to stock.

Please can someone link me to an up to date method to root?
I understand towelroot only works for p905 and p900/

okay
rirawin said:
Please can someone link me to an up to date method to root?
I understand towelroot only works for p905 and p900/
Click to expand...
Click to collapse
I do not have enough posts to link an email. About three weeks ago I had the same question. The thread is in this forum on page 3, 5 or so messages down. I am the op, stedmakr. Gastrom answered the thread, provided a link and helped me root the p900 and install his rom (its excellent). Sorry I can't post links. Page 3 of this forum.
Keith

http://forum.xda-developers.com/gal...reliable-root-method-p900-build-bnk1-t2986600
I still don't quite understand, I just like to root to get sd card fix

Since there's this thread... How about KNOX? Is there a way to root P900 without tripping KNOX flag? I don't care about KNOX software itself, but since here in Poland warranty problems are left to the decision of the service, it is quite important for me not to give them opportunity to refuse a repair (if something happens, which - I hope - never will).
Wytaptalkowane na notatniku

Peri Noid said:
Since there's this thread... How about KNOX? Is there a way to root P900 without tripping KNOX flag? I don't care about KNOX software itself, but since here in Poland warranty problems are left to the decision of the service, it is quite important for me not to give them opportunity to refuse a repair (if something happens, which - I hope - never will).
Wytaptalkowane na notatniku
Click to expand...
Click to collapse
Nope, no way to avoid Knox trip.
Sent from my SM-P900 using Tapatalk

can anyone confirm please, is this the method to root:
https://androidxda.net/root-samsung-galaxy-note-pro-12-2-all-variants-on-android-4-4-2-kitkat/
So after I done that, I update su user and then I install sdfix is that right?.

anyone please?

Are you having problems or just too afraid to try it?
Not sure if you realize this but one of the reasons people aren't answering you is because those of us who have rooted do so and never look back. I wish I could tell you for sure that it will work with the current version of the firmware but I cant . . I rooted 8 months ago and haven't looked back. I cant speak for others but I'm not about to flash stock and go through the whole thing again just to update an old thread so I suspect that this is part of the reason that there's no updated guide. For devices that get a ton of development things are different but this niche device doesn't have a flurry of development activity surrounding it so . . .
One thing I can say is that it is my experience that if CF Autoroot fails the worst thing you're left with is a tripped knox and the stock rom without root. I say this because I was one of the unlucky ones who had to struggle through multiple attempts to get CF Autoroot to work. Eventually it did but during that time I had multiple shots at it and each time I was able to at least recover to the point of getting stock OS and recovery working again.
I see no reason why you can't achieve root on a SM-P900. If you can't do it with CF Autoroot then just download one of Gatsrom's images of stock rooted, flash TWRP using Odin (with auto reboot option disabled), boot into TWRP and do a full wipe and flash Gatsrom's image. You'll lose your setup and apps but you'll get root.

muzzy996 said:
Are you having problems or just too afraid to try it?
Not sure if you realize this but one of the reasons people aren't answering you is because those of us who have rooted do so and never look back. I wish I could tell you for sure that it will work with the current version of the firmware but I cant . . I rooted 8 months ago and haven't looked back. I cant speak for others but I'm not about to flash stock and go through the whole thing again just to update an old thread so I suspect that this is part of the reason that there's no updated guide. For devices that get a ton of development things are different but this niche device doesn't have a flurry of development activity surrounding it so . . .
One thing I can say is that it is my experience that if CF Autoroot fails the worst thing you're left with is a tripped knox and the stock rom without root. I say this because I was one of the unlucky ones who had to struggle through multiple attempts to get CF Autoroot to work. Eventually it did but during that time I had multiple shots at it and each time I was able to at least recover to the point of getting stock OS and recovery working again.
I see no reason why you can't achieve root on a SM-P900. If you can't do it with CF Autoroot then just download one of Gatsrom's images of stock rooted, flash TWRP using Odin (with auto reboot option disabled), boot into TWRP and do a full wipe and flash Gatsrom's image. You'll lose your setup and apps but you'll get root.
Click to expand...
Click to collapse
Well said mate! Well said.
If someone's gonna root their tablet, especially one of this caliber & price point. Then they should know how to recover it back to stock on their own. Concerning the tripping of Knox, who cares! Samsung won't turn down a hardware issue covered under warranty just because you decided to load another ROM. That topic has been discussed to death in another thread. If your going to root this thing, then root it and live on! LoL ?
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.

Android.Ninja said:
Samsung won't turn down a hardware issue covered under warranty just because you decided to load another ROM.
Click to expand...
Click to collapse
Not here in Poland...

[Completed] T-Mobile Samsung Galaxy S4 SGH-I337 root issues

I'm not usually one to make an account just to post and ask for help as I usually find it annoying on most forums I frequent, but at this point I am stuck.
I've tried the kingroot app, that didn't help. I used the desktop version, but it's in chinese and from what I could tell it wanted me to enable developer options, which I did, and it still wasn't registering my phone as being plugged in.
I've searched, and searched, google, here, a few other forums. From what I've pulled either this phone is nearly impossible to root or I'm just doing it wrong. I'd like to know what steps I need to take to root my phone, or if rooting this phone is even possible. Thank you very much for your help.

wumboisms said:
I'm not usually one to make an account just to post and ask for help as I usually find it annoying on most forums I frequent, but at this point I am stuck.
I've tried the kingroot app, that didn't help. I used the desktop version, but it's in chinese and from what I could tell it wanted me to enable developer options, which I did, and it still wasn't registering my phone as being plugged in.
I've searched, and searched, google, here, a few other forums. From what I've pulled either this phone is nearly impossible to root or I'm just doing it wrong. I'd like to know what steps I need to take to root my phone, or if rooting this phone is even possible. Thank you very much for your help.
Click to expand...
Click to collapse
Do not follow or use anything that the other member posted for you. It is not for your device, you have the T-mobile(are you sure it isn't AT&T?) I337, not the I337M. They are totally different animals.
Verify which one you actually have.

Droidriven said:
Do not follow or use anything that the other member posted for you. It is not for your device, you have the T-mobile(are you sure it isn't AT&T?) I337, not the I337M. They are totally different animals.
Click to expand...
Click to collapse
Yeah I just figured that out. Thankfully I'm really paranoid about bricking my phone.. Anyway, this was originally an AT&T phone, but I switched over to t-mobile.
Edit: For clarifications sake this is an i337 not an i337m

wumboisms said:
Yeah I just figured that out. Thankfully I'm really paranoid about bricking my phone.. Anyway, this was originally an AT&T phone, but I switched over to t-mobile.
Edit: For clarifications sake this is an i337 not an i337m
Click to expand...
Click to collapse
Yes, I was pretty sure of that anyway, that's why I asked.
Try this thread below, it has many things for your device from Returning to stock via Odin, Downgrading to KK to root, Updating, etc..
http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
Pay close attention to the rooting and consider the downgrade to root if you think you need to, I don't have the I337 so I haven't had to research that deep into it. Root on lollipop if you can or go back to kit kat if you have to as long as you understand it and you are sure it's safe, downgrading can cause problems but I don't think that applies in this case, I'm not 100% sure of that though. Good luck.

What is the latest Root Method for SM-P900 us version?

Looking through many post, all of them seem rather old, Im finally ready to root my tablet, Im tired of all of the lag I get and it seems as Samsung has let the 12.2 pro die.
Im running 5.02
Build: LRX22G.P900UEU1COL1
Kernel: 3.4.39-5574008
Knox: 2.3
I found this post by dwl99 http://forum.xda-developers.com/galaxy-note-pro-12/general/success-rooting-sm-p900-knox-0x0-t3377416
It seem only one person has tried it
Thanks for any input you may have

I'm not sure if you found your answer, but if you're willing to trip KNOX, I was able to root my p900 US version on 5.0.2 by using the method in the post found here: http://forum.xda-developers.com/galaxy-note-pro-12/general/guide-install-official-lollipop-p900-t3154362

Thanks
I will check it out, I dont care about Knox at this point since Samsung has let this tablet die

Hitch_Itch said:
Thanks
I will check it out, I dont care about Knox at this point since Samsung has let this tablet die
Click to expand...
Click to collapse
Yep. My faith in Samsung hardware is hit or miss, but my faith in them having too many models for them to keep up with is starting to wane.
Anyways, I had no problem getting TWRP on it, and flashing SU. Just follow the post and if it doesn't show up on your computer, try other USB ports. For some reason these samsungs are picky. I had to try three USB ports to get it to register in Odin. After that it was no problem. I verified it with JRummy's tool, and have run other root apps, and it took just fine.
I wasn't able to get xposed working, but that might be an issue with the stock ROM. No big deal though. Backups, moving apps to SD, and such, are all capable with root and TWRP, though it would have been more tidy to have the SD card as an extension of the on-board, I can live without it.
If you need my stock ROM build info it's P900UEU1COI1_P900XAR1COI1 (cellular south). There are two US ones I see available for 5.0.2, and have no idea what the difference is, but that one works fine for me. So if you have to Odin first, or after, that one seemed to go well for my US P900. Use that info at your discretion, because I can't see your current build info.

Thanks for the info
The tablet seem very laggy when on the net lately, Im tired of it
My Build: LRX22G.P900UEU1COL1

Hitch_Itch said:
Thanks for the info
The tablet seem very laggy when on the net lately, Im tired of it
My Build: LRX22G.P900UEU1COL1
Click to expand...
Click to collapse
Same build here.
Follow the directions carefully (you likely don't need to do the first area as you're already up to date), and you should be all set. Just remember to backup everything important first. Since you already have your info/apps in place, and aren't changing ROMS's, there isn't much to it. Don't forget to do a backup using TWRP after you have everything up and running. You'll want to download busybox from the app store, after you're rooted.
Careful if you decide to go with a custom ROM after. I didn't have much luck with cyanogen mod 13, because it knocked out a lot of my Spen needs, and there are a fair number of reports of random reboots on the one I tried. Hopefully that will change and I can update to 6.0.1 when/if it does.
For you, there shouldn't be a need to wipe data or factory reset, but if the lag continues you may want to wipe your cache's once you have your nandroid backup.
PM me if you run into any issues, or better yet, with any questions you're unsure about, before an issue happens

Will Do Blade, :good:
Thanks

build
Hello. I can't find the files for my build number. Can i use this one instead? ( Yes , I am noob.)
Build no: LRX22G.P900XXU0BPE1

Is there a reliable form of root yet?

I'm considering jumping to the S7. Is there a reliable, working root yet?

reliable yes
working yes
some issues yes
issues can be remedied for most people

sacnotsack said:
reliable yes
working yes
some issues yes
issues can be remedied for most people
Click to expand...
Click to collapse
What kind of issues? I'm getting mine tomorrow and I would like to root pretty much right away. I've been through the threads and didn't see much as far as issues.

metalfan78 said:
What kind of issues? I'm getting mine tomorrow and I would like to root pretty much right away. I've been through the threads and didn't see much as far as issues.
Click to expand...
Click to collapse
overheating, lag, extreme batter drain, but these can be fixed by setting the cpu governor to on-demand or interactive. those were the only issues I personally experienced, but was easily fixed.
occasionally I will have bad lag, but after a reboot all is well. speaking of boots....boot time is horrendous.

Well, the lag is what I'm trying to get rid of, which is what I'm currently getting with my LG G5. So, I guess switching to the S7 won't make much difference.
Sent from my LG-H830 using Tapatalk

Sounds fixable. I think I'll go stock for a day or so then root it.

I have read that if you freeze the bloat, that helps with battery and lag issues as well.

So, from what I've read, it has to do with the modified boot.img. I really just want to restore all my stuff from titanium backup
Maybe rooting isn't even worth it right now. Unless I root, restore, then flash stock boot.img, if possible.

metalfan78 said:
So, from what I've read, it has to do with the modified boot.img. I really just want to restore all my stuff from titanium backup
Maybe rooting isn't even worth it right now. Unless I root, restore, then flash stock boot.img, if possible.
Click to expand...
Click to collapse
Not really worth it... there are some workarounds. But, you will never get rid of the lag. Stay on stock until there is either a new root method or unlocked bootloader.
EDIT: Echoe Rom is out for the SMG930T and SMG935T !!!!!! No lag at all

Thats what I plan on doing for now

metalfan78 said:
Thats what I plan on doing for now
Click to expand...
Click to collapse
Flash the U firmware. Removes the bloat.

Is the bloat the only cause of the lag?

metalfan78 said:
Is the bloat the only cause of the lag?
Click to expand...
Click to collapse
No. The eng boot will cause a little lag and more battery drain than compared to stock.

lvpre said:
No. The eng boot will cause a little lag and more battery drain than compared to stock.
Click to expand...
Click to collapse
Ok, that's what I was reading. I think I'll wait it out a bit. I've had the phone for 24 hrs and that's the longest I've gone without rooting in like 7 years, lol.

https://drive.google.com/open?id=0B0yzuMcMjykeV0wwYnVmbmp0SnM
download this it will help with the CPU , lag , wifi not saving, battery drain, can log in to snapchat, debloat,.. etc

You'll brick your s7
Looks guys, if you knew anything about locked bootloaders, or rooting at all, its not as simple as an odin flash then a root.bat execution and your done. It might root for a while as did mine, then security will catch up with the phone. C'mon so many people are going to have bricked phones because of these fake postings.
I tried it for fun, knew it would brick the t-mobile S7, and it did. I just wanted to be 100% positive before I wrote this. Don't root your U.S. S7, it is impossible and will lead to nothing but problems and stuck boot because of google/samsung security. They went as far as blocking the google account registered with the S7 on google at the time. So think before you just odin then root.bat, your opening more than just a door, trust me.
On top of that, non of the so called odin flashable recovery firmwares are real. They just lead to advertising websites that collect cookie data and make you click links you don't want to click. Be advised.
Of course advertising and spam companies are going to take advantage of people like the android rooting community, who know they are taking a risk rooting in the first place, so you cannot complain when you get malware from these sites, because technically your doing something your not supposed to. Don't just go clicking random downloads because they sound legit. 90% are not.
---------- Post added at 11:08 AM ---------- Previous post was at 10:39 AM ----------
If I am wrong about the recovery file, or a flashable image file that actually roots the phone (custom recovery TWRP, cwm anything) please prove me wrong. Root is not root without the recovery. Don't try to root any android phone without an available custom recovery and legit recovery files at hand.
The S7 has a locked bootloader for a reason, attempting root without a custom recovery available to work with is plain stupid.

boobteg2 said:
Looks guys, if you knew anything about locked bootloaders, or rooting at all, its not as simple as an odin flash then a root.bat execution and your done. It might root for a while as did mine, then security will catch up with the phone. C'mon so many people are going to have bricked phones because of these fake postings.
I tried it for fun, knew it would brick the t-mobile S7, and it did. I just wanted to be 100% positive before I wrote this. Don't root your U.S. S7, it is impossible and will lead to nothing but problems and stuck boot because of google/samsung security. They went as far as blocking the google account registered with the S7 on google at the time. So think before you just odin then root.bat, your opening more than just a door, trust me.
On top of that, non of the so called odin flashable recovery firmwares are real. They just lead to advertising websites that collect cookie data and make you click links you don't want to click. Be advised.
Of course advertising and spam companies are going to take advantage of people like the android rooting community, who know they are taking a risk rooting in the first place, so you cannot complain when you get malware from these sites, because technically your doing something your not supposed to. Don't just go clicking random downloads because they sound legit. 90% are not.
---------- Post added at 11:08 AM ---------- Previous post was at 10:39 AM ----------
If I am wrong about the recovery file, or a flashable image file that actually roots the phone (custom recovery TWRP, cwm anything) please prove me wrong. Root is not root without the recovery. Don't try to root any android phone without an available custom recovery and legit recovery files at hand.
The S7 has a locked bootloader for a reason, attempting root without a custom recovery available to work with is plain stupid.
Click to expand...
Click to collapse
The US models are able to be rooted. You are not well informed if you believe otherwise. I highly doubt you "bricked" your phone, probably just a boot loop or stuck at a screen. it can be fixed.
The engineering boot is how we are able to obtain root. There are a ton of details on how it works, so I am not going to go into details.
please don't post misinformation, it only confuses the ones trying to learn.
-sent from my Rooted and stable Tmo S7

sacnotsack said:
The US models are able to be rooted. You are not well informed if you believe otherwise. I highly doubt you "bricked" your phone, probably just a boot loop or stuck at a screen. it can be fixed.
The engineering boot is how we are able to obtain root. There are a ton of details on how it works, so I am not going to go into details.
please don't post misinformation, it out lyrics confuses the ones trying to learn.
-sent from my Rooted and stable Tmo S7
Click to expand...
Click to collapse
You are right... there are working root methods... that works flawlessly with a few tweaks... In regards to the bricking, The firmware I've had the most issues with is PG1 but it is a simple fix, just disable or block security updates with titanium backup ... or alternatively you can install Echoe Rom which debloats, deodex's and deknox's. I've had zero issues with this rom. No bricks no boot loops and no lag. I hope this helps

boobteg2 said:
Looks guys, if you knew anything about locked bootloaders, or rooting at all, its not as simple as an odin flash then a root.bat execution and your done. It might root for a while as did mine, then security will catch up with the phone. C'mon so many people are going to have bricked phones because of these fake postings.
I tried it for fun, knew it would brick the t-mobile S7, and it did. I just wanted to be 100% positive before I wrote this. Don't root your U.S. S7, it is impossible and will lead to nothing but problems and stuck boot because of google/samsung security. They went as far as blocking the google account registered with the S7 on google at the time. So think before you just odin then root.bat, your opening more than just a door, trust me.
On top of that, non of the so called odin flashable recovery firmwares are real. They just lead to advertising websites that collect cookie data and make you click links you don't want to click. Be advised.
Of course advertising and spam companies are going to take advantage of people like the android rooting community, who know they are taking a risk rooting in the first place, so you cannot complain when you get malware from these sites, because technically your doing something your not supposed to. Don't just go clicking random downloads because they sound legit. 90% are not.
---------- Post added at 11:08 AM ---------- Previous post was at 10:39 AM ----------
If I am wrong about the recovery file, or a flashable image file that actually roots the phone (custom recovery TWRP, cwm anything) please prove me wrong. Root is not root without the recovery. Don't try to root any android phone without an available custom recovery and legit recovery files at hand.
The S7 has a locked bootloader for a reason, attempting root without a custom recovery available to work with is plain stupid.
Click to expand...
Click to collapse
It may not be the prettiest root, but it is a working root none-the-less. Other than the eng boot lag issues (which can be mitigated mostly through things like Govtuner, etc.), all apps that require root permissions work fine as intended. Bootloops can be avoided by disabling security policy services. Other than the random reboot every now and again, I'm running strong since the day root came out.

boobteg2 said:
Looks guys, if you knew anything about locked bootloaders, or rooting at all, its not as simple as an odin flash then a root.bat execution and your done. It might root for a while as did mine, then security will catch up with the phone. C'mon so many people are going to have bricked phones because of these fake postings.
I tried it for fun, knew it would brick the t-mobile S7, and it did. I just wanted to be 100% positive before I wrote this. Don't root your U.S. S7, it is impossible and will lead to nothing but problems and stuck boot because of google/samsung security. They went as far as blocking the google account registered with the S7 on google at the time. So think before you just odin then root.bat, your opening more than just a door, trust me.
On top of that, non of the so called odin flashable recovery firmwares are real. They just lead to advertising websites that collect cookie data and make you click links you don't want to click. Be advised.
Of course advertising and spam companies are going to take advantage of people like the android rooting community, who know they are taking a risk rooting in the first place, so you cannot complain when you get malware from these sites, because technically your doing something your not supposed to. Don't just go clicking random downloads because they sound legit. 90% are not.
---------- Post added at 11:08 AM ---------- Previous post was at 10:39 AM ----------
If I am wrong about the recovery file, or a flashable image file that actually roots the phone (custom recovery TWRP, cwm anything) please prove me wrong. Root is not root without the recovery. Don't try to root any android phone without an available custom recovery and legit recovery files at hand.
The S7 has a locked bootloader for a reason, attempting root without a custom recovery available to work with is plain stupid.
Click to expand...
Click to collapse
Wow talk about uninformed. I've been running a rooted Galaxy S7 for just about a month now. I had rooted even earlier then that but I didn't know about the security policy updating. Yeah, security caught up but it didn't brick the phone. Just reflash the stock files and everything is fine. Now that I've been able to freeze the security update policy I haven't had a problem.

T-Mobile S4 M919UVSFQA1 OTA update - Should I accept?

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....