help! please. I am look to root my samsung galaxy S4 Running android 4.3 with the build MK6.
PLEASE HELP?
Thank you
Use this method : http://forum.xda-developers.com/showthread.php?t=2293800
DaveRazr said:
Use this method : http://forum.xda-developers.com/showthread.php?t=2293800
Click to expand...
Click to collapse
Anything that will actually allow the install of a custom recovery?
arrush said:
Anything that will actually allow the install of a custom recovery?
Click to expand...
Click to collapse
There's no "true" custom recovery for phones running MF3 or above. MF3 phones can run Safestrap. MDB/MDL phones still have the ability to boot into a true custom recovery using loki.
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
Mk6 can run cwm and twrp. Rogers unit isnt the same as att bud, happy flashing
Sent from my SGH-I337M
---------- Post added at 12:13 PM ---------- Previous post was at 12:09 PM ----------
jeboo said:
There's no "true" custom recovery for phones running MF3 or above. MF3 phones can run Safestrap. MDB/MDL phones still have the ability to boot into a true custom recovery using loki.
Click to expand...
Click to collapse
This is not the case at all. Mk6 is rogers / canaduan variant, and the bootloader is not locked. Root with cf auto root, and flash cwm or twrp via normal methods. You will trip knox counter, but you can run any recovery u like. MF3 is locked bootloader , mk6 is not.
Sent from my SGH-I337M
azuziel said:
Mk6 can run cwm and twrp. Rogers unit isnt the same as att bud, happy flashing
Sent from my SGH-I337M
---------- Post added at 12:13 PM ---------- Previous post was at 12:09 PM ----------
This is not the case at all. Mk6 is rogers / canaduan variant, and the bootloader is not locked. Root with cf auto root, and flash cwm or twrp via normal methods. You will trip knox counter, but you can run any recovery u like. MF3 is locked bootloader , mk6 is not.
Sent from my SGH-I337M
Click to expand...
Click to collapse
Oops, didn't even realize it was i337m...:silly:
I used kingo app. One touch root. Knox safe. I verified the vroot iemi crap is all removed in new version. After your reboot, update supersu binary via normal method, cancel any knox popups, and choose not to allow supersu to disable knox. Use titanium backup and guides found here to freeze all knox stuff. Then busybox, xposed as normal. Dont install custom recovery if you want to keep knox 0x0. If you dont care, then install cwm/twrp as per normal
Sent from my SGH-I337M
I deleted Knox completely from my phone as well as all the AT&T Bloatware. My phone is better without it.
azuziel said:
I used kingo app. One touch root. Knox safe. I verified the vroot iemi crap is all removed in new version. After your reboot, update supersu binary via normal method, cancel any knox popups, and choose not to allow supersu to disable knox. Use titanium backup and guides found here to freeze all knox stuff. Then busybox, xposed as normal. Dont install custom recovery if you want to keep knox 0x0. If you dont care, then install cwm/twrp as per normal
Sent from my SGH-I337M
Click to expand...
Click to collapse
Thanks a lot for that Kingo App, worked perfectly! I did get that Knox pop-up on 4.3 and I clicked view apps just to check it out.
2 Questions:
Anyways, how do you update supersu binary? There's no option or menu to do so and I didn't get a pop-up.
How do you choose not to allow supersu to disable Knox?
Thanks for the tip about not installing a custom recovery
azuziel said:
I used kingo app. One touch root. Knox safe. I verified the vroot iemi crap is all removed in new version. After your reboot, update supersu binary via normal method, cancel any knox popups, and choose not to allow supersu to disable knox. Use titanium backup and guides found here to freeze all knox stuff. Then busybox, xposed as normal. Dont install custom recovery if you want to keep knox 0x0. If you dont care, then install cwm/twrp as per normal
Sent from my SGH-I337M
Click to expand...
Click to collapse
Do you know if this was resolved then? http://forum.xda-developers.com/showthread.php?t=2460745&page=8 there was more going on behind the scenes than I would like to have.....
http://forum.xda-developers.com/showthread.php?t=2460745&page=8
Ramsey said:
Thanks a lot for that Kingo App, worked perfectly! I did get that Knox pop-up on 4.3 and I clicked view apps just to check it out.
2 Questions:
Anyways, how do you update supersu binary? There's no option or menu to do so and I didn't get a pop-up.
How do you choose not to allow supersu to disable Knox?
Thanks for the tip about not installing a custom recovery
Click to expand...
Click to collapse
regarding knox. It is safe to allow supersu to disable knox, i avoided it thinking it may trip bc wasn't sure how it went about freezing it. I tested, had supersu disable knox, rebooted, good to go.
Did an identical handset today, and failed to root. Did some poking and found out that kies3 appears to interfere with kingo, so uninstall temporarily when running kingo if you have issues.
Once supersu disabkes knox, you can then update the binaries via normal method. Also if kingo gets to the part where it asks about using odin method, say no, or it'll trip knox.unplug, reattach and try again. Had to do it thrice for an i377m i did today.
Heres what i did:
1 - connect usb to phone, and enable developer mode, then be sure to allow the dev prompt to always accept usb from this machine, phone will prompt to allow
2 - click root. Shouldn't get to odin question, id it does, dont allow odin method, restart the process.
3 - on successful root, you will see supersu install, grant it root, and allow it to disable knox.
4 update supersu binariez via normal method (don't need to use cwm/twrp on i377m only), it will prompt, until knox disabled, u wont be able to update binaries
5 - install busybox installer
I havent installed supersu as system app yet, i imagine its also safe to do so.
6 - check knox in download mode and ensure 0x0 for *both* knox codes
7- installed xposed and some modulez, greenify in particular, and enabled, recheck knox, still 0x0
Both phones i did with this method, once kies was removed, rooted BEFORE i had to install any camera exploits, or any other crap from play. If you habe trouble, reload samsung drivers, try another cable (i had a failure using a blackberry usb cable, switched to packaged smasung usb, worked fine), anothet usb, and even another computer. Old pc's with usb 1.1 wont work (well), usb 2/3 does work just fine.
Avoid clockworkmod, twrp, safesteap etc (or any other custom recovery) if you want to keep your warranty. If you dont care, then twrp/cwm work just fine, they will blow the knox efuse tho and set you 0x1. I work in IT and happen to know knox will work with exchange 2015 upon release. It will also screw up new versions of active sync, as your system isn't able meet the security requirements (having knox intact and not blown) of the organizations' corporate knox policies. Look for a bes like sys admin tool that expands on the remote wipe /lockz/ camera images etc, in the coming months. Exchange 2015 is still a ways away, but since you cant undo a blown efuse with any software, understand implications of blowing knox fully, not just warranty. And if you use exchange email, or plan to, keep knox untripped is best advice.
Gage_Hero said:
Do you know if this was resolved then? http://forum.xda-developers.com/showthread.php?t=2460745&page=8 there was more going on behind the scenes than I would like to have.....
http://forum.xda-developers.com/showthread.php?t=2460745&page=8
Click to expand...
Click to collapse
Yes. Ok, kingo is just an interface for all known exploits. The emei sniffing was actually being performed by vroot. Kingo was simply running existing vroot code. I talked to kingo support last week, who assured me that emei check was pulled during latest release, the vroot method is still present, however iz modified to remove those bad lines. When you run kingo, it opens a connection to kingo server to pull each exploit/patch as one method fails, pulls another, then another, as needed. This keeps package small, and allows for on the fly repo updatez on their end without having to re-release a package.
Kingo does not record emei at all any longer, it was vroot doing it, and kingo bc they simply ran vroot method without editing.
So you will see kingo go online to grab each exploit as required, in the new version, but no emei tracking any longer.
Besides the trojan that was used before in vroot, is picked up by avg free, so youd know if it were still doing it. I ran tcpview and tcpdump while flashing root to my device and didnt see any connections to china, any longer.
This can be verified on both odficial Facebook and Twitter account of kingo. Their intention is to at one point to charge a couple bucks for this app, having it exhibit malicious behaviour is bad for business. Youll notice vroot has no support or contact methods. Kingo does.
Sent from my SGH-I337M
Thanks, btw I can't seem to software update after I rooted my phone. It says my software was modified. Does anyone know how I can get it to check for updates? I'm already on 4.3 but I know our S4 will get 4.4 in a few months.
I am still good with Knox, I am at 0x0 for both lines.
Btw, I did freeze Knox in titanium, but not uninstall, just freeze. I did freeze many other apps but nothing dangerous, just normal ones like Travel, google movies, magazines, etc..
Ki Hi
Ramsey said:
Thanks, btw I can't seem to software update after I rooted my phone. It says my software was modified. Does anyone know how I can get it to check for updates? I'm already on 4.3 but I know our S4 will get 4.4 in a few months.
I am still good with Knox, I am at 0x0 for both lines.
Btw, I did freeze Knox in titanium, but not uninstall, just freeze. I did freeze many other apps but nothing dangerous, just normal ones like Travel, google movies, magazines, etc..
Click to expand...
Click to collapse
You cannot update ota when system is modified, there is an xposed module that changes modified to official tho. Not sure if it trips knox, likely. When updates come, unroot, apply, reroot. There are other guides that can be found here to update keepinng root with odin, you'll have to use the search provided.
Feezing with Titanium backup is fine. Supersu doesnt delete knox, it disables knox notifications. The whole point here is not tripping knox. That's why supersu asks if you want to disable knox, and not delete it, bc only disables, knox services still present. Feezing with tb is same result. Just supsrsu is free, tb is paid (for freezing anyway), though if youre on these forums, should be using tb anyway , titanium backup, greenify donation, and tasker are 3 must have root apps. Tasker is great. I use it to auto enable bluetooth and wifi based on gps location, or driving in the car. Lots of youtube vids on tasker if you areny familiat with it.
Sent from my SGH-I337M
There is an alternative to vroot and kingo methods. I was able to root mj6. I saw mk2 rooted as well successfully.
http://forum.xda-developers.com/showthread.php?t=2565758
If it helps any 4.3 MK6 users, I rooted using the download from this site and can confirm that it works:
http://forum.xda-developers.com/showthread.php?t=2565758
ravi_mytouch said:
There is an alternative to vroot and kingo methods. I was able to root mj6. I saw mk2 rooted as well successfully.
http://forum.xda-developers.com/showthread.php?t=2565758
Click to expand...
Click to collapse
Yep it does. Ive used it on a few i377m already. Wasn't available when i did mine. Kingo is relatively safe, latest release is, cant speak for previous or future versions. Kingo is just an interface that uses all known root methods (including vroot, and this method). Just keeps trying dif method til one works. Had this been available, would have used for mine. But it wasn't so setup a segregated lab at work, to test kingo and reports of malware. I didnt see any at that time via tcp dump and tcpview, however that could change since they just rip off other root methods/code to reuse, kingo does i mean. That said if you rooted with kingo, no need to repeat. Root is root (well, full root is full root), and no daemons u dont recognize running.
Sent from my SGH-I337M
Dear XDA,
I come from the HTC One forum and I've sold since I've had camera issues numberous of times.
I decided to switch to an SGS 4, currently on 4.4.2. I have the i9505xxufnb9 variant.
I have a question regarding root.
1. I do not have knox installed yet, should I install it or leave it as it be when using CF-auto root? I'm currently on 4.4.2.
2. Is CF auto root compatible with my variant?
3. What version of Odin should I be running? I guess this is the most important. I don't want a sketchy Odin.exe that comes pre-set up. It might have some setting on that erases something that is crucial for my device.
4. Is there some sort of bootloader unlock I need to do first? My device is unbranded GT9505 version with the above written variant.
5. How likely am I to brick my device? I mean I come from the HTC one forum which was fairly easy. Setup fastboot and unlocking the bootloader did the job.
6. I came to understand it WILL trigger knox, does it mean voided warranty here in the Netherlands?
7. I understand that SuperSU has an option to unroot at any given time. When I want to return to stock for say warranty purposes, Can I download triangleaway, run it, and then unroot using SU app?
Thank you so much for your time!!
No one?
Cf autoroot comes with correct odin, if you do not have Knox don't install it, (you automatically get it if you took an ota). And no bootloader unlock is needed almost all Samsung devices come with an unlocked bootloader, and the only way you'll brick your device is if you flash something not meant for your phone or if you have knox and try downgrading your firmware...
And if you do have knox, rooting will permanently flag your device as modified with no way of going back. If you don't have knox you can use triangle away to reset the flash counter.
Sent from my GT-I9505 using Tapatalk
aryehzev said:
Cf autoroot comes with correct odin, if you do not have Knox don't install it, (you automatically get it if you took an ota). And no bootloader unlock is needed almost all Samsung devices come with an unlocked bootloader, and the only way you'll brick your device is if you flash something not meant for your phone or if you have knox and try downgrading your firmware...
And if you do have knox, rooting will permanently flag your device as modified with no way of going back. If you don't have knox you can use triangle away to reset the flash counter.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I'll make sure to give you your thanks tomorrow . I also got alot of help from the ask everything thread, thank you!
Hello,
I've was forced to create a post about that because there is almost nothing of use that can be found about that phone in the internet.
I need to know how to check the bootloader status on this device so i can safely root it, and if there are any working ROMs. I've found out that it is possible to install 9505 roms on that phone, however the touch and other crucial features do not work while using them.
Cheers, Paweł.
Thanks in advance, i appreciate Your help!
Go into download mode and if you see Knox warranty void you have new bootloader.this has nothing hover to do with safe root or not.you can still however root the device.but counter will be tripped if flashing custom recovery and kernel.
LastStandingDroid said:
Go into download mode and if you see Knox warranty void you have new bootloader.this has nothing hover to do with safe root or not.you can still however root the device.but counter will be tripped if flashing custom recovery and kernel.
Click to expand...
Click to collapse
Oh thanks! :good: I will do so. But about that safe root. I wanted to use the CF Auto Root for that and it was said there that if the device has a locked bootloader it will brick if i'll try to unlock the root access.
Should i try another way to root my device or give it a try and see what happens if i'll root it using cf auto root. I know that almost none or all ways to root the device are not safe, but following some of them have higher chances of success than others that's what i meant by safe root.
Zebbro said:
Oh thanks! :good: I will do so. But about that safe root. I wanted to use the CF Auto Root for that and it was said there that if the device has a locked bootloader it will brick if i'll try to unlock the root access.
Should i try another way to root my device or give it a try and see what happens if i'll root it using cf auto root. I know that almost none or all ways to root the device are not safe, but following some of them have higher chances of success than others that's what i meant by safe root.
Click to expand...
Click to collapse
All the info, rooting recoveries, roms available so far for i9515
http://forum.xda-developers.com/galaxy-s4/general/i9515-value-edition-roms-development-t3002535
Zebbro said:
Oh thanks! :good: I will do so. But about that safe root. I wanted to use the CF Auto Root for that and it was said there that if the device has a locked bootloader it will brick if i'll try to unlock the root access.
Should i try another way to root my device or give it a try and see what happens if i'll root it using cf auto root. I know that almost none or all ways to root the device are not safe, but following some of them have higher chances of success than others that's what i meant by safe root.
Click to expand...
Click to collapse
I think you have misunderstood or misread.or users haven't understand that root is still possible. It isn't locked in any way. The bootloader still let's you flash custom kernels etc.
Rooting with cf root shouldn't and has never bricked your phone on newer recoveries. The bootloader isn't locked in the way of flashing in Odin you can still flash custom kernels and recoveries but it will trip the Knox counter.
However: tripping Knox will cause you being unable to use Knox apps from Samsung and might void your warranty.
Users have told different reports about them being tripped and got warranty and some haven't. I'm not sure if this lies in 3rd party repair centers repairing the phone even if it's tripped. I'm sure Samsung service center is against it.
I'd be 100% sure that my phone carrier would repair it no matter the status since it doesn't go trough Samsung service at first.
However to gain root you should try towelroot it's a one click apk and it won't trip Knox unless you flash a custom kernel or recovery.