[ROOT EXPLOIT+PATCH][2012.12.19] ExynosAbuse APK v1.40
- Thread starter Chainfire
- Start date
I'm sorry you're having issues finding the answers you're looking for. I think I found the post that may have what you're looking for here. Good luck!
:thumbup:Bugging up my phone, so you don't have to!
Hello
I have a HYUNDAI T7s that is powered by EXYNOS quad core .
I used EXYNOSE ABUSE (EA) to root it, and it work.
When I installed for first time EA, it installed also SUPERSU app.
I had to do a factory reset, I lost Supersu but my Hyundai continue to be rooted.
I installed last version of SUPERSU by Market, and it works.
Now I would like to do a factory reset and UNROOT my tablet.
could you please explain me the difference between 4 possible options:
- Root the device (SuperSU v0.99) (I used it)
- Enable/disable the exploit at will
- Enable/disable patching the exploit at boot
- Unroot and cleanup (optionally leaving the exploit patch at boot in place)
Please consider I'm not so expert and I'm not english.
for example I suppose that an EXPLOIT is a bug in the main Operative System used to enter in main root !
if not please explain me with simple words.
thank you very much
I have a HYUNDAI T7s that is powered by EXYNOS quad core .
I used EXYNOSE ABUSE (EA) to root it, and it work.
When I installed for first time EA, it installed also SUPERSU app.
I had to do a factory reset, I lost Supersu but my Hyundai continue to be rooted.
I installed last version of SUPERSU by Market, and it works.
Now I would like to do a factory reset and UNROOT my tablet.
could you please explain me the difference between 4 possible options:
- Root the device (SuperSU v0.99) (I used it)
- Enable/disable the exploit at will
- Enable/disable patching the exploit at boot
- Unroot and cleanup (optionally leaving the exploit patch at boot in place)
Please consider I'm not so expert and I'm not english.
for example I suppose that an EXPLOIT is a bug in the main Operative System used to enter in main root !
if not please explain me with simple words.
thank you very much
09/06/2013 01:22:55
HTTP filter file
http://dl.xda-developers.com/attach.../51b3cadb/1/5/7/6/2/2/1/ExynosAbuse-v1.40.apk
Android/Exploit.Lotoor.CU trojan
Is this safe to download? my ESET stopped it with the error stated above
HTTP filter file
http://dl.xda-developers.com/attach.../51b3cadb/1/5/7/6/2/2/1/ExynosAbuse-v1.40.apk
Android/Exploit.Lotoor.CU trojan
Is this safe to download? my ESET stopped it with the error stated above
Just stumbled onto this thread from a YouTube video. Will this root and keep a locked boot loader on a sch-i605 4.1.1 VRALL4 Verizon note 2? Searched through this thread and it was confirmed but they didnt say what version they were running. Im very familiar with Casual but don't really want to unlock the boot loader or run custom ROMS. Im happy with the Samsung Touch wiz GUI, just want root to remove/freeze bloatware, etc. Thanks.
Last edited:
Just a quick question. I know it has been answered before but my situation is a little different.
I have a SGS3 i9300 and using Exynos 1.4.
I am planning to get the new i9505 and give my dad my i9300. I want to do a hard reset and clean format.
This is what I am thinking:
1) Unroot via "Disable Exploit"
2) Click "unroot device"
3) Hard reset via "Press and Hold Volume Up + Power + Home button" and hit "Select Wipe data/factor reset"
4) Register with my dad's gmail account
5) Update to 4.1.2 OTA (currently its 4.1.1)
Anything else I am forgetting?
Hi
what is happened when you click
2) Click "unroot device"?
did you receive a popo up that ask
optionally leaving the exploit patch at boot in place?
I realy do not understand the meaning of this sentence
optionally leaving the exploit patch at boot in place
I am on LT5 now and I have installed the latest APk.. But rooting and patching both failing... I have carefully read all the instructions.. Please help me..
2nd thing I want to know that did my recovery also changed to CWM after succeding?
Voyo A15
Hi from Spain.
Thanks for your work.
Yesterday I received my new tablet, a Voyo A15 with Exynos Dual Core 5250.
I try root it with several methods, include yours, but i don´t have luck.
/system is read only and i can´t do anything for read/write and copy su, busybox and superuser.
Any ideas, please?
Thanks again.
P.D. Sorry for my english
Hi from Spain.
Thanks for your work.
Yesterday I received my new tablet, a Voyo A15 with Exynos Dual Core 5250.
I try root it with several methods, include yours, but i don´t have luck.
/system is read only and i can´t do anything for read/write and copy su, busybox and superuser.
Any ideas, please?
Thanks again.
P.D. Sorry for my english
This will not root my galaxy note 2. Its on the 4.1.2. Do you have any suggestions for me?
Here is what is see. I am only looking to root, but ill unlock the bootloader if there is no other way...any help would be appreciated
Here is what is see. I am only looking to root, but ill unlock the bootloader if there is no other way...any help would be appreciated
Attachments
Will this work on old gingerbread ROM for India (DDLC1)?
PS: I have gone through DrKetan's pages and multitude of other pages. So far I have seen this as a non-rootable ROM. I would like to stay with GB for battery reasons.
ICS was OK, JB is very worse. Since my travelling has increased I have to get better battery life.
Also if someone can point me on to pre-rooting guide I can edit the stock DDLC.
Thank You
PS: I have gone through DrKetan's pages and multitude of other pages. So far I have seen this as a non-rootable ROM. I would like to stay with GB for battery reasons.
ICS was OK, JB is very worse. Since my travelling has increased I have to get better battery life.
Also if someone can point me on to pre-rooting guide I can edit the stock DDLC.
Thank You
ExynosAbuse-v1.40 not work in JB 4.2.1
Hi ChainFire Genius & All,
Thanks alot for your Good work that your ExynosAbuse-v1.40 is success rooted for my Lenovo K860i ICS 4.0.4 & JB 4.1.2...
But feel surprise that i use your ExynosAbuse root my New JB 4.2.1 is Fail
Any idea how to fix ?? i think need to update this so can rooted JB 4.2.1.. ?
Hi ChainFire Genius & All,
Thanks alot for your Good work that your ExynosAbuse-v1.40 is success rooted for my Lenovo K860i ICS 4.0.4 & JB 4.1.2...
But feel surprise that i use your ExynosAbuse root my New JB 4.2.1 is Fail
Any idea how to fix ?? i think need to update this so can rooted JB 4.2.1.. ?
Hi ChainFire Genius & All,
Thanks alot for your Good work that your ExynosAbuse-v1.40 is success rooted for my Lenovo K860i ICS 4.0.4 & JB 4.1.2...
But feel surprise that i use your ExynosAbuse root my New JB 4.2.1 is Fail
Any idea how to fix ?? i think need to update this so can rooted JB 4.2.1.. ?
Why are you surprised that it won't work on 4.2.1? It's called ExynosAbuse for a reason. It worked because it abused a security vulnerability in the Exynos drivers which is now fixed in recent updates, thus this hack won't work anymore and can't be fixed.
You'll have to find another way to root your device.
Sent from my HTC One X using xda premium
Try FRAMAROOT. SEARCH ITHi ChainFire Genius & All,
Thanks alot for your Good work that your ExynosAbuse-v1.40 is success rooted for my Lenovo K860i ICS 4.0.4 & JB 4.1.2...
But feel surprise that i use your ExynosAbuse root my New JB 4.2.1 is Fail
Any idea how to fix ?? i think need to update this so can rooted JB 4.2.1.. ?
That mean no more update for this apk anymore.....
OK Thanks man... I don't know about it if i know i no need to waste my time to ask here again... Thanks again HTC Genius... :silly: Before tried but fail in the 1st time Root..
Have somebody advise there will try again follow his method using Framaroot... Thanks Man... 
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
835This is an APK that uses the ExynosAbuse exploit (by alephzain) to be able to do various things on your Exynos4 based device.
Features for non-rooters:
- Securely patch the exploit
Features for rooters:
- Root the device (SuperSU v0.99)
- Enable/disable the exploit at will
- Enable/disable patching the exploit at boot
- Unroot and cleanup (optionally leaving the exploit patch at boot in place)
Please note that patching the exploit may break camera functionality, depending on device and firmware. Also note that if use the patch method without rooting, or keep patching the exploit at boot enabled when unrooting, you need an alternate method to re-root the device to disable this feature (like CF-Auto-Root) - you cannot use ExynosAbuse to do this since it patched the exploit. Unlike other patch authors, I do not believe in keeping an invisible rooted process running in the background while pretending you aren't rooted, to be able to unpatch this way.
While the exploit patches work (aside from possibly disabling your camera), these are more work-around than actual fixes. A proper patch would be a kernel fix, either from a third party or Samsung themselves (hopefully one day...)
My method vs Supercurio, RyanZA
Mine is the only one that is secure. Both Supercurio's and RyanZA's method leave you with easily exploitable holes any serious malware author will abuse. More details http://forum.xda-developers.com/showthread.php?t=2053824
Exploit
For more details on the exploit itself, see this thread: http://forum.xda-developers.com/showthread.php?t=2048511. The exploit is used by this APK in unmodified form. You should be very afraid of this exploit - any app can use it to gain root without asking and without any permissions on a vulnerable device. Let's hope for some fixes ASAP !
Camera
If your camera keeps working depends on your device/firmware combination. Affected are mostly the SGS3, but there is good news too, there is a potential fix here: http://forum.xda-developers.com/showthread.php?t=2052675 SGS3 I9300 ONLY. It seems to work for a number of people. It replaces some system libraries with libraries from a different firmware version that does not rely on /dev/exynos-mem. Do not attempt this unless your camera actually breaks due to the exploit, and beware it may cause you to have to reflash your firmware. Also beware that even though this change will not prevent OTAs from downloading, it can possibly prevent OTAs from flashing succesfully.
Device status
Using this patch may turn your device status into modified. There's not really a proper solution to that at the moment, but you can restore status by removing the patch (and SuperSU) again and rebooting your phone. This will however leave you unprotected again. Doing all sorts of weird stuff (like for example wiping data) to get rid of this modified status while you're still have the patch applied at boot or keep SuperSU around, is an exercise in futility. If you want to go ahead and do that, that is fine, but do not litter my thread with your comments. Because eventually, the modified status is likely to return
Compatibility:
(If your device isn't listed it could still be both compatible with the exploit as well as this fix !)
Samsung Galaxy S2 GT-I9100
Samsung Galaxy S3 GT-I9300
Samsung Galaxy S3 LTE GT-I9305
Samsung Galaxy Note GT-N7000
Samsung Galaxy Note 2 GT-N7100
Samsung Galaxy Note 2 LTE GT-N7105
AT&T Galaxy Note 2 SGH-I317
Verizon Galaxy Note 2 SCH-I605 both locked and unlocked bootloaders work
Samsung Galaxy Camera EK-GC100
Samsung Galaxy Tab Plus GT-P6210
Samsung Galaxy Note 10.1 GT-N8000, GT-N8010, GT-N8013, GT-N8020
Google Nexus 10 not compatible, Exynos5
Post in this thread if you have a device to add.
Notes
I'm not sure if this APK will work right on Android 2.x devices (not tested yet), doesn't mean the exploit doesn't work. So if you're on Android 2.x and this APK doesn't work for you, try doing the exploit manually.
Download
Please do not redistribute, link to this thread instead
v1.40 hashes:
MD5: be4a373ff2848a16bfb948d7e1d1f7d2
SHA1: 79670ab10da59ea58df222e94ad9e8ed83c791a9
(v1.00: 3786; v1.10: 6397; v1.20: 12004; v1.30: 14480)104Changelogs
2012.12.19 - v1.40
- Added check for updates functionality
- Added "current status" display
- Split into sections for non-rooters and rooters
- Added "One-click secure exploit patch" for those who just want to patch their device and forget about
- Added ability to unroot and clean up the leftovers (optionally leaving the patch code in place)
2012.12.18 - v1.30
- Adjusted many things in the shell code, the app will now properly detect an install SuperSU/Superuser with the wrong permissions as NOT having root
- Added a startup notification telling you your device/firmware is not susceptible to this exploit, if it isn't
2012.12.17 - v1.20
- Gingerbread-related fixes - note that not all Gingerbread firmwares of affected devices are vulnerable (for example, I know several SGS2 GB firmwares are not exploitable)
- Added some spam (view my apps on Play, follow me on Twitter, that sort of BS)
- Added icon
2012.12.16 - v1.10
- Added ability to disable and re-enable the exploit (which may break camera)
- Added ability to disable exploit at boot (before any Play-installed app runs, other solutions run later which means they are still vulnerable)
- Both above features require being rooted
2012.12.16 - v1.00
- Initial release18v1.10 released
Just updated to v1.10 !
This version allows you to disable the exploit (which may break camera), re-enable the exploit (if you need the camera) and to disable the exploit at boot (before any Android app runs). These options do require root (SuperSU or Superuser) to be installed as well.17I don't want to moderate 40+ pages of this thread, so please stop giving eachother bad advice.
Do not listen to anybody that is advising you to NOT use the "on boot" patch.
If you do not enable the patch at boot, and enable it manually later, you are not protected. Not even a little. Any malicious exploiter will include a run at boot, and if you run into that, you are screwed. Might as well not patch at all.
Yes, it may break OTA, it may break camera (fixable though, see 1st post) and it may trigger modified status. If you don't want that, then don't patch. It's one or the other. You can't currently have it both ways.
