If anyone knows where to download G920AUCU1AOCE please send me the link through PM. Many thanks.
[5/8] Beta 1 released! http://xdaforums.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
[5/8] Beta 1 will be released in 24hrs. Following ROM FP will be supported for testing:
G9200ZCU1AOD5
G9200ZHU1AOD3
G9200ZHU1AOD9
G920R4TYU1AOD3
G920IDVU1AOD1
G920FXXU1AOCV
G920PVPU1AOCF
G920TUVU1AOCG
G920VVRU1AOC3
G920FXXU1AOBN
We are throwing another party, soon... :laugh::laugh::laugh:
Root on SM-G9200 has been achieved without tripping Knox, utilising a new vulnerability just reported (https://twitter.com/grsecurity/status/594483601661505536)
ROM specific data will be required, so please let me know your current ROM fingerprint so we can extract data from them. A download link will be appreciated.
Just S6 fingerprint please. Generic root for 32-bit devices will be released in new version of Kingroot (see Q&A)
Credits:
Vulnerability: memeda, wushi
Original idea of exploit: memeda
Exploit: idl3r, Qoobee
Special thanks to:
Kingroot team for help testing and great root manager
Q&A:
[5/5] Sorry for the delay, busy paint balling and fly crossing pacific
Q: When will you release it?
A: We are currently working to make it more reliable and covering more ROMs. Please stay tuned
Q: Is this fake?
A: No. We discovered this vulnerability and we don't bother faking a root. See this answer for an explanation of the screenshot: http://xdaforums.com/showpost.php?p=60531263&postcount=34
Q: How to get a fingerprint?
A: Please follow these steps:
1. Run "adb shell"
2. Type "getprop | grep fingerprint"
3. Please copy and paste the result
Q: Why fingerprint is needed?
A: We will try to extract the kernel for certain binary gadgets to help the root.
Q: Is this a generic root?
A: Not for this particular tool.But generic root is possible for most 4.3+ devices with this vulnerability. I just bought an S6 so I decided to root it first. Stay tuned for other devices
We've been working on generic root with Kingroot team to test it out on wide range of devices. Test results just came out and it looks very positive. It will be released in Kingroot in 2-3 days, and shall cover 80%+ of post-futex kernels (may take sometime to optimize the model/FP data).
Among them are devices (32-bit for now) like Sony Xperia Z3, LG G3, Huawei Honor 6, 6Plus, Mate 7 and many other devices,with support of their latest Android L or Kitkat ROM. Stay tuned S5 and Note3 with Android L are also supported for specific FP, with new FP added in the future.
Q: S6 Edge?
A: We'll look into the kernel first. So far there are QC charging (hardware) issues for S6 Edge and potentially we will wait till this potential HW issue is fixed.
Q: Will this work for AT&T/Verizon/etc version?
A: In theory, yes. Locked bootloader doesn't affect this one. However, if bootloader locks the UFS controller for write protection (like Note4), chances are su install won't be permanent.
Q: Why you report this vulnerability? Vendor will fix it soon!
A: First of all we are researchers. Releasing 0day exp to public without notifying the vendor is non-ethical. Secondary there is no sense of hiding it since when this tool is released, vulnerability will be learnt by vendor. With all debugging tools/HW and expertise they have no software level obfuscation/encryption would help hiding the vulnerability.
Update:
[5/5] Add Q&A
[5/6] Update status of GENERIC root
[5/8] Beta 1 status update
[5/8] Beta 1 released! http://xdaforums.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
[5/8] Beta 1 will be released in 24hrs. Following ROM FP will be supported for testing:
G9200ZCU1AOD5
G9200ZHU1AOD3
G9200ZHU1AOD9
G920R4TYU1AOD3
G920IDVU1AOD1
G920FXXU1AOCV
G920PVPU1AOCF
G920TUVU1AOCG
G920VVRU1AOC3
G920FXXU1AOBN
We are throwing another party, soon... :laugh::laugh::laugh:
Root on SM-G9200 has been achieved without tripping Knox, utilising a new vulnerability just reported (https://twitter.com/grsecurity/status/594483601661505536)
ROM specific data will be required, so please let me know your current ROM fingerprint so we can extract data from them. A download link will be appreciated.
Just S6 fingerprint please. Generic root for 32-bit devices will be released in new version of Kingroot (see Q&A)
Credits:
Vulnerability: memeda, wushi
Original idea of exploit: memeda
Exploit: idl3r, Qoobee
Special thanks to:
Kingroot team for help testing and great root manager
Q&A:
[5/5] Sorry for the delay, busy paint balling and fly crossing pacific
Q: When will you release it?
A: We are currently working to make it more reliable and covering more ROMs. Please stay tuned
Q: Is this fake?
A: No. We discovered this vulnerability and we don't bother faking a root. See this answer for an explanation of the screenshot: http://xdaforums.com/showpost.php?p=60531263&postcount=34
Q: How to get a fingerprint?
A: Please follow these steps:
1. Run "adb shell"
2. Type "getprop | grep fingerprint"
3. Please copy and paste the result
Q: Why fingerprint is needed?
A: We will try to extract the kernel for certain binary gadgets to help the root.
Q: Is this a generic root?
A: Not for this particular tool.
We've been working on generic root with Kingroot team to test it out on wide range of devices. Test results just came out and it looks very positive. It will be released in Kingroot in 2-3 days, and shall cover 80%+ of post-futex kernels (may take sometime to optimize the model/FP data).
Among them are devices (32-bit for now) like Sony Xperia Z3, LG G3, Huawei Honor 6, 6Plus, Mate 7 and many other devices,with support of their latest Android L or Kitkat ROM. Stay tuned S5 and Note3 with Android L are also supported for specific FP, with new FP added in the future.
Q: S6 Edge?
A: We'll look into the kernel first. So far there are QC charging (hardware) issues for S6 Edge and potentially we will wait till this potential HW issue is fixed.
Q: Will this work for AT&T/Verizon/etc version?
A: In theory, yes. Locked bootloader doesn't affect this one. However, if bootloader locks the UFS controller for write protection (like Note4), chances are su install won't be permanent.
Q: Why you report this vulnerability? Vendor will fix it soon!
A: First of all we are researchers. Releasing 0day exp to public without notifying the vendor is non-ethical. Secondary there is no sense of hiding it since when this tool is released, vulnerability will be learnt by vendor. With all debugging tools/HW and expertise they have no software level obfuscation/encryption would help hiding the vulnerability.
Update:
[5/5] Add Q&A
[5/6] Update status of GENERIC root
[5/8] Beta 1 status update
Last edited: