Related
Hello all,
I've searched all over XDA and Google, to give me definitive answer about issue i am about to raise, i rooted and put custom roms on all my previous samsung/htc devices, and WAS about to do the same for my Note 3 (its a beastly device, and doesnt need modifications, however it has been a routine for me to root and put custom roms into any devices that i've used)
Now the issue is this:
Yes, i've read about KNOX security system that Samsung has implemented, which would trip a counter and supposedly locked the bootloader of the phone, i've also read that due to the e-fuse that has been implemented, my Note 3 internals could be damaged due to it (?), and also i wouldnt be able to go back to the old version/bootloader as it will be parmanently locked by Samsung if i flash using Odin.
Do take note..that my Note 3 is not under warranty..so if KNOX triggers, it doesnt matter for me , as i wont be going to my local phone shop or official Samsung Officials (there isnt one here in my country) if anything would happen to my device. However i do need to know if its gonna mess with my device due to the e-fuse.
My questions are these..
1) If i root it, using CF's method as i usually do..and will definately put Custom Rom in it...and that will trigger KNOX for sure..will it destroy the internals? say the MOBO..and the phone will be rendered useless and become an expensive paperweight (i dont have warranty, so no replacements)
2) If i use for e.g Omega Rom which released two versions, one, with 4.3 JB and one, with 4.4 KitKat...will i be able to go back and forth for e.g 4.4 to 4.3 as well as jumping to different custom roms with diffrent Android versions?! as i usually do with me previous devices
Thanks and i will definately delete this thread once i'm fully convinced that rooting , putting roms should be avoided or ''Since you dont care about tripping knox, go ahead and do it as ur previous devices'' kinda answer..
Truly Sorry if you guys come across this question already..i've searched for it and come to no avail.. this is my last resort. Thnks XDA and everyone.:good:
qilrfn said:
My questions are these..
1) If i root it, using CF's method as i usually do..and will definately put Custom Rom in it...and that will trigger KNOX for sure..will it destroy the internals? say the MOBO..and the phone will be rendered useless and become an expensive paperweight (i dont have warranty, so no replacements)
2) If i use for e.g Omega Rom which released two versions, one, with 4.3 JB and one, with 4.4 KitKat...will i be able to go back and forth for e.g 4.4 to 4.3 as well as jumping to different custom roms with diffrent Android versions?! as i usually do with me previous devices
Thanks and i will definately delete this thread once i'm fully convinced that rooting , putting roms should be avoided or ''Since you dont care about tripping knox, go ahead and do it as ur previous devices'' kinda answer..
Truly Sorry if you guys come across this question already..i've searched for it and come to no avail.. this is my last resort. Thnks XDA and everyone.:good:
Click to expand...
Click to collapse
Firstly wrong section - should go to Q&A
1) -- Well you can mess up if you don't follow the right methods (not hard)
2) you can only be on one, if you use 4.3 BL you can't use 4.4 and vice versa... once you go to 4.4 you cannot downgrade back to 4.3 unless you have an N900w8
Generally, rooting/custom ROM's won't hurt your device, just make sure you have the right ROM/Kernel and make the proper backups if needed.
Disable Reactivation Lock, and read about backing up your EFS and how to get out of it if it goes mad (which it sometimes does at random)
I think Radicalisto didn't make it clear enough: I'm not aware of tripped Knox flag affecting anything else on the phone except for warranty and inability to use Knox software. Any type of phone issues would probably be due to user error, or loaded software, not the flag itself.
radicalisto said:
Firstly wrong section - should go to Q&A
1) -- Well you can mess up if you don't follow the right methods (not hard)
2) you can only be on one, if you use 4.3 BL you can't use 4.4 and vice versa... once you go to 4.4 you cannot downgrade back to 4.3 unless you have an N900w8
Generally, rooting/custom ROM's won't hurt your device, just make sure you have the right ROM/Kernel and make the proper backups if needed.
Disable Reactivation Lock, and read about backing up your EFS and how to get out of it if it goes mad (which it sometimes does at random)
Click to expand...
Click to collapse
Thanks for answering first of all..will defo hit the thnx button..
for the 1) i always make sure i read the instructions and follow steps..no problem there..
2) this one tho..is a bit weird for me..i was able to do it on my note 2..going back and forth 4.3 to 4.1.2 cus i found the 4.1.2 more stable..i guess for note 3 i cant do that anymore? even if use custom roms to up/downgrade?
thnx for ur time..and will take ur advice next time on posting it at the q and a section (still learning)
ON 4.3 you once you go to MJ7 Bootloader you cannot downgrade -- however you can go to ML and MK bootloaders and go back to MJ7 again.
For some reason Samsung blocked a downgrade to 4.3 from 4.4 (as the Note shipped with 4.3 no logical reason to allow 4.2 imo) - but if you choose to move to 4.4. bootloader do be aware it can be buggy on some devices (NEE region also Hong Kong notes have issues) - If you have a read around you will see the issues people are having and not having with stock 4.4.
There's plenty of ROMs for both bootloaders CM works on both and most of the Stock based ROM dev's have moved up to the newest NB* Bootloader from NA* - I flashed 4.4 day it leaked (the next hour to be precise and I have had no issues)
qilrfn said:
Thanks for answering first of all..will defo hit the thnx button..
for the 1) i always make sure i read the instructions and follow steps..no problem there..
2) this one tho..is a bit weird for me..i was able to do it on my note 2..going back and forth 4.3 to 4.1.2 cus i found the 4.1.2 more stable..i guess for note 3 i cant do that anymore? even if use custom roms to up/downgrade?
thnx for ur time..and will take ur advice next time on posting it at the q and a section (still learning)
Click to expand...
Click to collapse
since note 3 came with 4.3 and currently latest stock is 4.4.2. even if u wanna go back to 4.3 from what i read around it is not possible. There are alot of aosp roms and stock rooted roms with all kinds of kernel build for both stock and aosp. Im sure if u were to follow the instructions given and do it diligently surely nthg goes wrong unless u overclock ur phone too high or flashing stuff which weren't meant for ur specific device then nthg to be afraid of. I sure glad i went ahead and root. Coz to me knox is a totally BS. all down to ur own preference. u like it u root it u use it. best is to keep reading different threads.
Sent from my SM-N9005 using XDA Premium 4 mobile app
radicalisto said:
ON 4.3 you once you go to MJ7 Bootloader you cannot downgrade -- however you can go to ML and MK bootloaders and go back to MJ7 again.
For some reason Samsung blocked a downgrade to 4.3 from 4.4 (as the Note shipped with 4.3 no logical reason to allow 4.2 imo) - but if you choose to move to 4.4. bootloader do be aware it can be buggy on some devices (NEE region also Hong Kong notes have issues) - If you have a read around you will see the issues people are having and not having with stock 4.4.
There's plenty of ROMs for both bootloaders CM works on both and most of the Stock based ROM dev's have moved up to the newest NB* Bootloader from NA* - I flashed 4.4 day it leaked (the next hour to be precise and I have had no issues)
Click to expand...
Click to collapse
Okay..so i would only flash 4.4 roms when Im really really convinced that its time for KitKat..but as of right now, i can only play around with 4.3 roms..ok..understood. You've cleared my doubts man, thanks a bunch and i guess its time to root and flash.
pete4k said:
I think Radicalisto didn't make it clear enough: I'm not aware of tripped Knox flag affecting anything else on the phone except for warranty and inability to use Knox software. Any type of phone issues would probably be due to user error, or loaded software, not the flag itself.
Click to expand...
Click to collapse
I did read somewhere, the e-fuse is like an internal bomb..if i flag it, some sort of ''internal parts destroyer'' would be unleashed and mess up my device. I guess its just a rumour...hopefully.
qilrfn said:
I did read somewhere, the e-fuse is like an internal bomb..if i flag it, some sort of ''internal parts destroyer'' would be unleashed and mess up my device. I guess its just a rumour...hopefully.
Click to expand...
Click to collapse
If it's not humour, there's gonna be a lot of angry Note owners here on XDA -- Some tripped KNOX accidently lol - I wouldn't worry too much in all honesty.
I'm sure using cf root trips knox
Sent from my SM-N9005 using xda app-developers app
An e-fuse is just a silicon bridge on the processor that gets burnt out. Once you burn the bridge it can't revert back.
This is technically damaging the internal hardware BUT this is due to Samsung software doing this so I don't see how they can claim we have damaged the hardware.... There should be no other problems resulting from this....
First of all, many people already claim their phones had Knox flag reset to zero by Samsung service centers. Either they're all lying (why?), there are more than one e-fuse inside and Samsung can simply reset software to ignore burned fuse and check next one, or the whole e-fuse story is made up and not true. Personally I lean towards the last possibility, for 2 reasons: e-fuse is permanent so couldn't be reset and if they're using multiple e-fuses then it is not more secure than encrypted software code and also possibly e-fuse could be defeated from tripping: I believe e-fuse needs higher than normal voltage to be burned out (otherwise it could burn accidentally) and that voltage is probably coming on separate rail, I wonder what would happen if one would either cut this high voltage or short it out, just during flag tripping operations.
Secondly many people tripped their Knox flags already, if there was some side effects, we would know about it already.
So i've been searching for a couple days now, but can't seem to find a straight answer.
If i root my note 12.2, will it trip Knox to 0x1, or will knox only trip if i flash a custom rom?
I don't care too much for modding and such, just interested in rooting to remove blaotware. From what i've been seeing though, it looks like knox will trip just by rooting. However i'v seen others say it only tripped after installing custom roms. Maybe im just getting my references mixed up though.
AANNDD if rooting will trip knox, any idea if it will ever be possible to root without buggin knox? I have the note3 and was able to root and keep 0x0. I know they are very different when it comes to kernels, but maybe one day?
o0pyroguy0o said:
So i've been searching for a couple days now, but can't seem to find a straight answer.
If i root my note 12.2, will it trip Knox to 0x1, or will knox only trip if i flash a custom rom?
I don't care too much for modding and such, just interested in rooting to remove blaotware. From what i've been seeing though, it looks like knox will trip just by rooting. However i'v seen others say it only tripped after installing custom roms. Maybe im just getting my references mixed up though.
AANNDD if rooting will trip knox, any idea if it will ever be possible to root without buggin knox? I have the note3 and was able to root and keep 0x0. I know they are very different when it comes to kernels, but maybe one day?
Click to expand...
Click to collapse
I tripped knox trying to install TWRP... I know this doesn't exactly answer your question.
o0pyroguy0o said:
So i've been searching for a couple days now, but can't seem to find a straight answer.
If i root my note 12.2, will it trip Knox to 0x1, or will knox only trip if i flash a custom rom?
I don't care too much for modding and such, just interested in rooting to remove blaotware. From what i've been seeing though, it looks like knox will trip just by rooting. However i'v seen others say it only tripped after installing custom roms. Maybe im just getting my references mixed up though.
AANNDD if rooting will trip knox, any idea if it will ever be possible to root without buggin knox? I have the note3 and was able to root and keep 0x0. I know they are very different when it comes to kernels, but maybe one day?
Click to expand...
Click to collapse
I have root, stock recovery, stock firmware, never installed anything custom and KNOX is tripped. AFAIK, no way to achieve root without tripping KNOX, but so worth it to root. I have Exposed installed with Wanam and have my tablet set to Custom instead of Modified so I still get updates. I also have a Note 3 rooted on 4.4.2 without tripping KNOX.
It's not possible to root / flash custom ROMs or recoveries without tripping KNOX. At last for now.
And a bit off topic:
Note 3 was different since @designgears found way (URDLV) to root without triggering KNOX.. But it didn't took very long for Samsung to release a patch for that and downgrading is also impossible. So if you updated your phone via Kies or OTA when that exploit were patched, you got "bootloader of doom" and no way root without triggering KNOX flag (and since downgrading is impossible, you can't go back to "rootable" version). And I'm talking now about international Snapdragon version (since my Note 3 and NP 12.2 are international versions)
One day . . perhaps. .
I'm now on my second Note Pro having lost the first to an act of stupidity. This time around I've purchased a square trade warranty with accidental damage coverage for 2-years and as with the first I'll be rooting this tablet as well (gave it a week to settle in so that I'm sure that there's no hardware issues).
Here's my take on KNOX; Unless there were applications that I relied on that are checking on KNOX or evidence of root to stop me from using them I'm not going to worry myself at all about it. If I'm going to be sending in my device for repair it's going to be for a hardware issue NOT a software one because if I have the knowledge to be doing things like rooting and installing custom recoveries then I should be able to solve my own software issues (most likely through a factory reset if need be). Warranty coverage for hardware defect shouldn't be influenced by software.
wow, thanks for the fast replies guy!
So another quick question. (since muzzy mentioned breaking)
Lets say i root my note, knox trips 0x1, and in 3 months my volume rocker stops working (hardware problem). With other devices, i would call customer support, we troubleshoot for a bit, they decide to send me a new device (refurbished most likely) and i send my broken one to them since im still in warranty time wise. If they receive my note 12 and knox says 0x1, what do they do? Since my warranty is technically void, could they charge me for the tablet they sent me?
i think i just answered my own question as im thinking about it more.
SO knox is specifically SOFTWARE, if something hardware wise go amiss, my warranty is still good?
Root that bad boy. Get the files you need to root here:
http://forum.xda-developers.com/showthread.php?p=50492301
and when you encounter problems, go to this thread for answers:
http://forum.xda-developers.com/showthread.php?t=2710004&page=3
Russbad said:
Root that bad boy. Get the files you need to root here:
http://forum.xda-developers.com/showthread.php?p=50492301
and when you encounter problems, go to this thread for answers:
http://forum.xda-developers.com/showthread.php?t=2710004&page=3
Click to expand...
Click to collapse
awesome! I'll get this done as soon as im home then. Thanks for the quick responses everyone!
I installed CF auto root via Odin and it tripped the knox flag.
Bummer =(
oh well, as long as hardware wise, the warranty is fine, i guess its no big deal. Like muzzy said, anything software wise, i can fix. And if rooting trips KNOX and only void software warranty, i don't care too much about that.
Russbad said:
Root that bad boy. Get the files you need to root here:
http://forum.xda-developers.com/showthread.php?p=50492301
and when you encounter problems, go to this thread for answers:
http://forum.xda-developers.com/showthread.php?t=2710004&page=3
Click to expand...
Click to collapse
Unfortunately this won't work for the P905V (Verizon Variant). I've tried, since it said LTE but it's not for the Verizon LTE version. Still waiting for Root so I can at least install Xposed. I bought my device outright and couldn't care less about tripping KNOX.
I bought my device outright and couldn't care less about tripping KNOX
Click to expand...
Click to collapse
The only crappy part is if you get an actual hardware failure it sucks that they invalidate your entire warranty.
KNOX Warranty has nothing to do with the hardware warranty. The Knox warranty flag is there to make sure a device has never been tampered with in a way that could compromise their Knox services. Period.
Sent from my SM-P900 using Tapatalk
dodo99x said:
KNOX Warranty has nothing to do with the hardware warranty.
Click to expand...
Click to collapse
Well that's a relief.
dodo99x said:
KNOX Warranty has nothing to do with the hardware warranty. The Knox warranty flag is there to make sure a device has never been tampered with in a way that could compromise their Knox services. Period.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Those Knox services were the first thing I froze then deleted after root
Huh... im failing at the cache. Those recovery images have sure come in handy. Any tips?
Ive used odin 3.07/3.09 and CF-Auto-Root-v1awifi-v1awifixx-smp900? Im seeing a bunch of people getting stuck on the cache.img.
EDIT * USB debugging is on btw
EDIT* Got it! I unplugged ALL my other usb devices and changed the port i was using... stupid fix, but it worked.
Goodbye knox and all you other battery sucking memory hogging pieces of bloatware!
Thanks for you great help and suggestions! Greatly appreciated =D
Once the flag is tripped you can't even install Knox anymore
Sent from my SM-P900 using Tapatalk
o0pyroguy0o said:
Huh... im failing at the cache. Those recovery images have sure come in handy. Any tips?
Ive used odin 3.07/3.09 and CF-Auto-Root-v1awifi-v1awifixx-smp900? Im seeing a bunch of people getting stuck on the cache.img.
EDIT * USB debugging is on btw
EDIT* Got it! I unplugged ALL my other usb devices and changed the port i was using... stupid fix, but it worked.
Goodbye knox and all you other battery sucking memory hogging pieces of bloatware!
Thanks for you great help and suggestions! Greatly appreciated =D
Click to expand...
Click to collapse
Congrats to you, glad you worked it out! Enjoy your rooted tablet!
dodo99x said:
Once the flag is tripped you can't even install Knox anymore
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I REALLY don't care for knox anyways. Basically what i did right after rooting was open TB and uninstall everything that started with K and ended with NOX... removed a totall of 48 other programs too. Running smooth with no errors =D
Couldn't be happier.... well i could be happier if i could actually transfer files from my computer to my tablet... that would be nice. Good thing i have a card reader right?
o0pyroguy0o said:
I REALLY don't care for knox anyways. Basically what i did right after rooting was open TB and uninstall everything that started with K and ended with NOX... removed a totall of 48 other programs too. Running smooth with no errors =D
Couldn't be happier.... well i could be happier if i could actually transfer files from my computer to my tablet... that would be nice. Good thing i have a card reader right?
Click to expand...
Click to collapse
Hey, can you post your list of programs you uninstalled? I would love to take a look at it and compare it to the other threads about this, but I don't think anyone posted that many. I'm trying to improve my battery life, right now the screen takes the most and exchange service the next most.
On KNOX, I can't find anything at all that I would ever use it for so it didn't matter to me. Seems like Samsung could make it so that they could still have KNOX but allow us to root all the same. They even talk about CF root in their literature not installing a rootkit so they are not worried about it like other rooting methods that don't trip the KNOX circuit and DO instal a rootkit.
As we all know Knox is sort of a spyware and a p.i.t.a. A completely unnecessary pile of shiz,crammed in our devices for a very stupid reason. Knox_out will brutalize and defeat Samsung Knox for good. It has not tripped the Knox counter,and makes your device happier. Plus no more stupid Knox warnings,or SU being defeated on boot. Knox_out removes 100% of the Knox, nothing remains.
Knox_out will not remove Knox from bootloader.
Knox_out download and main page. Please use main page for support and comments.thanks.... Feel free to comment here if you really need to.
http://forum.xda-developers.com/showthread.php?t=2807064
Ultra Keaner De-bloater. Get 400+mbs free space, and free your ram.
http://forum.xda-developers.com/showthread.php?t=2809319
Changelog;
7/8/14 Added additional items to removal.
7/17/14 Added removal of annoying security policy updater
blaz1nr said:
As we all know Knox is sort of a spyware and a p.i.t.a. A completely unnecessary pile of shiz,crammed in our devices for a very stupid reason. Knox_out will brutalize and defeat Samsung Knox for good. It has not tripped the Knox counter,and makes your device happier. Plus no more stupid Knox warnings,or SU being defeated on boot. Knox_out removes 100% of the Knox, nothing remains.
Knox_out download and main page. Please use main page for support and comments.thanks.... Feel free to comment here if you really need to.
http://forum.xda-developers.com/showthread.php?t=2807064
Click to expand...
Click to collapse
So it only removes Knox apps in os,and not the Knox bootloader?
Does not remove the knox in bootloader. That seems to dangerous to do on these devices,most are still bl
locked anyway.Knox will be completely disabled with no hope of return.
Updated added new items.
Nice work, but - beg my pardon, mate,-where is the benefit?
The main problem will remain and there is no practical solution for that damn3d Bootloader Lock ?
silentscreamer said:
Nice work, but - beg my pardon, mate,-where is the benefit?
The main problem will remain and there is no practical solution for that damn3d Bootloader Lock ?
Click to expand...
Click to collapse
Without the apk's/libs blah blah blah. Knox cannot block SU access or send/log reports.Plus you get extra free space. There's pretty much no better reason's atm.If free space is what you really want,up soon will be my cleaner script.440+mb gain in free space from stock boot.
OK, ... ? that's pretty straight;... free space ?
The thread title is promising, what I am looking for is an automated solution for the complete patch at least all Knox components (Bootloader, Framework &. Apk's) because I want to go back to one of the stock Samsung Firmware.
@ time ? I don't have the new Bootloader, also no Knox and thanks to a 64 GB Micro SD Card more than enough Space on my GT-I9505 (powered by Android 4.4.4).
[emoji106]But I will subscribe your thread, maybe you are the blessed one who find a solution for the %@*¥^¦™ Bootloader Problem ?
Keep up the good work [emoji772]
If someone can point me in the direction to remove Knox from bootloader through a script. I'll take that challenge on. It's been plaguing me as it is. Since I've already made unsecured kernels, with no way to install them.
thanks for this solution i was trying to fight for it and u got it! thanks again
the results i got through this solution is :-
-more free space
-also some more free Ram due to no more knox booting with android
-feeling little more responsive when dealing with app who needs rooted device
if u would like what kernel or ROM do u i use see my signature...
updated
But will the knox flag get to 1 when flashing a custom rom with this?
Only system items get removed. The Knox counter is inside the bootloader. I don't touch anything in it. My knox counter did not trip. I've tested different variations, several times over and over again. Still no knox counter trip. I would definitely warn people if I saw that occur.
Dude this script works on i9500? or only the active model?
EduRePiN said:
Dude this script works on i9500? or only the active model?
Click to expand...
Click to collapse
Should work on all galaxy devices
blaz1nr said:
If someone can point me in the direction to remove Knox from bootloader through a script. I'll take that challenge on. It's been plaguing me as it is. Since I've already made unsecured kernels, with no way to install them.
Click to expand...
Click to collapse
From what I've read on this, the only way to remove knox from the bootloader is to reverse engineer the bootloader and rebuild it without any of the knox components. Very likely to be impossible. (Note - this is different from removing knox apps/framework or gaining root without tripping the knox counter)
ugly_bob said:
From what I've read on this, the only way to remove knox from the bootloader is to reverse engineer the bootloader and rebuild it without any of the knox components. Very likely to be impossible. (Note - this is different from removing knox apps/framework or gaining root without tripping the knox counter)
Click to expand...
Click to collapse
I had figured that. So much easier to work on HTC. It was worth the ask though.
Will this clean some space even if I already use a custom rom and kernel?
Just a noob question but how do I use this? A step by step procedure will be greatly appreciated.
download the zip.
copy to sdcard
reboot into recovery (press and hold Power + Home + Volume up Button)
choose install zip from sd card
select and let the recovery install it
One question. This will work on 4.4.2 S4 i9506?
And do phone need to be rooted? since there is no serious custom roms for i9506 I hope so someone will make some soon..
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.
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....