• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Rooting the Event

Wanted to note that Cydia Impactor works great on this (first or second method works without a fault). I had been rooted via the method on this thread without problem for a while but today I lost root "no idea how?" after updating binaries. Even though superuser was allowed to get root, no other app that uses it would prompt or work. I ran Cydia Impactor and immediately got root to work on all apps not just SuperUser.

If anyone needs a quick way to get this done, use that instead (be sure to do Usb > Driver Scan first in Impactor before starting it!)

Cheers
 
Upvote 0
Neither SRSROOT or the OP's method worked on the Event that I just bought at Radio Shack. What did work was the Rise directions at XDA.

I am thinking it is because of the Play Store version of Ministro

Same here, followed OPs tut had all the problems mentioned, followed the detailed instructions in quote and it worked the first time. Afterwards its safe to remove all the tools you used to root. Except superuser of course. major props
 
Upvote 0
Neither SRSROOT or the OP's method worked on the Event that I just bought at Radio Shack. What did work was the Rise directions at XDA.

I am thinking it is because of the Play Store version of Ministro

In efforts to get Xposed Framework to run (I discribed what worked in that thread) I had to reroot & the quoted method for the Rise on xda rerooted like a charm, thank you Ranhead! :thumbup:
 
Upvote 0
I never needed a PC to root my Event & Elite. When downloading what's needed to root with I would have to a good browser & request the download page in desktop mode before downloading. Next Browser, Chrome & Dolphin Browser are some I would try.. In some Browser settings I think its called User UA which can be changed to desktop mode b4 downloading needed files. Note: I would connect USB to my ps3 in debugging mode/charge only when tutorial stated connection was needed. Lol (may not be recommended though so) good luck
 
Upvote 0
First try I got the 64 error and it told me I need to restart my device. Doing so now then I will try again!

Edit: And again. lol

Edit #2: Well I have tried 4-5 times now and just keeping getting the same error n restarting my device. Should I keep trying or should I just go to the other method?

I believe you get this error code when you try to run poor without first moving it to the SD card
 
Upvote 0
Well, now. having read through everything, the OP's method did not work and WOULD NOT work; neither would the XDA variant for the Rise. Both resulted in error 22 (su binary not written). That srsroot, however, took some fiddling, but it worked BEAUTIFULLY.

Folks, if srsroot has given you problems, it's likely because you hit the button "Root Device (All Methods)". You don't want that one. Use the other one, "Root Device (Smart Root)", *then* it'll recognize that your Event is connected and work its magic. Just to confirm, I dl'ed Root Checker (since TB promptly crashed on me)...and this beast is ROOTED!!!
 
Upvote 0
For people getting errors after running poot, try running a program that requests root access. I was puzzled by the errors but then tried an app like the WIFI tether and it works beautifully! Thank you for this guide. I bought this phone specifically for tethering for $20 as a backup to when my satellite internet gets capped.
 
Upvote 0
Hey Guys I have a quite lengthy procedure to get a proper root on the Kyocera Event C5133 on Virgin Mobile USA
for those of you who have tried them one click PC Apps as well as the POOT method you may have found out that POOT does not work on the latest firmware 1.0.20VM and that using the one click free PC rooters do not give you a stable root to use root apps such as BusyBox, Lucky Patcher, Or Titanium Backup Properly lots of other root apps such as System App Uninstaller or Disable Applications also do not function right with out my method on the new firmware.

My Procedure after tons of testing does now work every time if done right and in sequence if not in sequence your root maybe unstable and unrooting it is quite difficult but it can be done becaue the SU paths in most cases are different for stable root for most modern root apps one or the other will not link the root paths properly and out of sequence will show more than one SU binary and that is why its difficult to remove. SuperSU will also not update properly with out my sequence either anything over version 2.02 will not install the SuperSU binary making the app completely useless. And in most cases the root will have absolutely no effect with out SuperSU if root is done right you will not need a superuser app for root apps to get root access which is the way it should be, but with any other method out there you do proper roots on all devices do not need a superuser app to function properly and most root apps will work with out a superuser on a proper root. I do not recommend not using a superuser on a rooted phone because of all the vulnerabilities that your rooted phone is subjected too.

If you attempted to root your phone via any other method for the Event, attempt to unroot your Event Prior to using my root sequence to have the most stable root possible, not attempting to unroot your phone prior can still cause problems after my sequence is complete though root should still work. Rooted phone should have one of 3 root paths though only one is actually needed and one of the three is better and more stable than the others. To unroot your phone use the unroot option of SRSroot and z4root which should between the two of them removed all three root paths. Verification of root removal as well as proper rooting can be done with POOT and Ministro II's root check option if you have a root path of either /system/sbin/su or /system/bin/su your phone is not properly rooted the root path you want is /system/xbin/su multiple root paths can be stable as they redirect to /system/xbin/su and that /system/xbin/su is the first one unrooting your phone ensures that /system/xbin/su is the first and only one however my method will allow the redirects of the other root paths so you do not need to do it but I do recommend that you at least attempt to remove root altogether. If your phone is not rooted by any method POOT's root check will say root not found. otherwise will list one or more of the root paths and in the order of application seek if more than one and even if there is a path redirect on any of the root paths. roots to /system/sbin/su should work too however stability of the root will be a recurring issue.

To root your Kyocera you will need a Windows Based PC, Kyocera KC02 Drivers (Preferred, App Used Has Its Own Drivers) and a few APKs for your phone. The Windows App Needed is MobileGo by Wondershare 5.3.2 (only had 5.3.2 since i started working with it but it may work with older versions) or Newer (Demo Version is available on their website / Hacked Versions are available on P2P Networks and locations throughout the internet) and Two APKs (SuperSU, I currently run 2.46 (latest) but anything over 2.30 will work fine but in but both root apps needed have their own version of SuperSU integrated but they are rather old limited versions and the SuperSU Pro Key App v2.05 not needed but works with 2.30 and up) the other APK you need is something called RootMaster if you gotten an English version that is not the right one the one that works is one in Simplified Chinese and comes from a developer in Taiwan.

The nice thing about MobileGo by WonderShare is that can root a good variety of phones in fact it can actually root all my phone except for my Galaxy Tab 3 and my Optimus Zone 2 (Basically if it can be rooted with FramaRoot or TowelRoot it works and even then some) My Galaxy Tab 3 and Galaxy S III on Sprint Firmwares (NH4/NK1 for the T217S and the NJ2 firmware for the L710S) but previous firmwares on those phone can be rooted using TowelRoot as well as most other phones running JellyBean 4.2.x, 4.3.x or KitKat 4.4.x can too) both Needed a TWRP/CWM in order too root it and the SuperSU Update Package 2.01 or newer as well as most of my phones can be rooted using a similar method of using TWRP or CWM but MobileGo is a very Awesome Easy Solution for most phones I've happened to get my hands on. But in this case MobileGo alone does not give you a stable enough root nor does RootMaster for a proper rooted Event. RootMaster too seems to work on a good number of phone too but not one any KitKat ROMs TowelRoot is the preferred rooter of KitKat Roms. If your phone has a supported AutoRoot, FramaRoot, Or TowelRoot use that instead but this method is only for the Kyocera Event on Either Sprint or Virgin Mobile may work on other Kyocera phones on the Sprint Network as Kyocera only currently makes phones for the Sprint Network (Boost Mobile, Virgin Mobile, Sprint PCS and others) may also work on some older Kyocera Prepaids on the Verizon Network as well. Kyocera has only made Phone using Qualcomm CDMA technology as Kyocera is owned by Qualcomm. Qualcomm though is the primary radio maker of most mobile phone and 90 percent of all mobile phones have some kind of Qualcomm radio in it other use a radio by Motorola. All phones currently that support iDEN, CDMA, TDMA, AMPS, PCS, or GSM or any data modulation technology under those parent technologies use a Qualcomm Mobile Radio. PCS is actually now defined as part of the CDMA protocol AMPS (Analog), iDEN(Nextel) and TDMA(old AT&T Digital) have offically been discontinued. GSM and CDMA are the only current standards still being used today data protocols 4G-WiMAX, 1xEVDO(3g), and 1xRTT(2g) are all defined under the CDMA protocol and protocols GPRS(1g), EDGE(2g), HSPA(3g),WCDMA(early 4g) are all defined under the GSM protocol 4G-LTE is defined under both GSM and CDMA protocol since it actually operates on a different frequency of either CDMA or GSM common frequences of CDMA are 800MHz, 1600MHz and technically do not need a SIM Card for network access, GSM operates at 850MHz,900MHz,1900MHz and requires a SIM Card. So basically if your phone has a SIM Card its usually a GSM based phone newer CDMA phone with LTE support also now use a SIM card but the nano or micro versions of it. iDEN as well as some newer TDMA phones also use SIM cards as iDEN was actually a protocol created by the combination of TDMA and GSM, older TDMA, CDMA and all AMPS phones do not require a SIM card but have a built in version of a SIM card known as a UICC and that is referenced by the phones ESN in either Decimal or Hexidecimal format. MEIDs are usually reference the used of an UICC or a ICC as well and is usually only 1 number short of the IMEIs on LTE phones. All LTE phones have a MEID HEX of starting with 99 and are 17 numbers long all IMEIs are 18 numbers long and usually start of with a 00 if it doesnt have LTE Support. All Hexidecimal MEIDs with out LTE Support all start with A0 or A1 and all Decimal MEID start with a 2. Sprint devices use Decimal MEIDs while everyone else uses the Hexidecimal. ones.

To get started on your Windows PC Download MobileGo and Install it on your PC if you do not want to buy the full version or can not get your hands on the Crack for the Demo Version or The Full Version, The Demo is fully functional for 15 days and can root the phone in Demo Mode. Once installed on your computer put your Event in ADB mode before connecting the USB cable to your computer by enabling USB Debugging in the Developer Section of Your Settings Menu also for a better outcome I recommend that you put your phone in Charge Only Mode in the PC Connection Section of your Settings Menu. Charge only mode allows the ADB Full Access to your Event with with little problems caused by MTP or Camera Modes. Once your phone is in ADB mode connect the USB Cable to your computer. MobileGo should be running as a service and in the lower right hand corner should automatically detect the Event. If not launch MobileGo from the Start Menu and MobileGo automatically attempts to detect the Event or any other Android Phone for that matter. Once MobileGo detects your phone it should install the MobileGo App on your phone automatically. Once the App is installed on your phone you can hit the manage button on the popup on the lower right hand corner of your desktop or if you have MobileGo already running it should automatically bring up a page in the app asking if your phone is safe by clicking on the manage button on the popup it should take you to that page anyways so if you already have it running you just skipped a step.

The next part of the root procedure is to click on the left hand side of the MobileGo Windows App to a section called Toolkit once that loads the next step is quite obvious and is by clicking on the big gray button on the top of the window that says get root access and follow the self explanatory instructions within the that menu.

If you were smart enough you downloaded the APKs on your computer rather than on your event because your by default the Event has no File Manager. So how do you install the APKs with out a FileManager well the solutions is simple and that is through ADB and a nice feature of MobileGo is the automatic installation of APKs via the Apps Menu on the left hand side. To install the APKs RootMaster as well as SuperSU simply Download the APKs to your PC and Drag them into the right hand side of the MobileGo Apps Menu and thats! It once both progress bars are completed than the two apps are available in your launcher.

The next part is the tricker part and that is the part of using RootMaster since most Americans can not read Simplified Chinese here the low down. Basically Launch RootMaster from the Launcher, since everything is in Simplified Chinese you are going to select the second button from the top and that is actually displaying root phone in Simplified Chinese. Though I Am American and Not Either from either the ROC or the PRC, I can actually read Simplified Chinese. I happen to be Asian and from the South Eastern Part of the Region by Decent. I WAS BORN IN THE US and I have not been out of the country but my position with Verizon Business had forced me to learn a ton of foreign languages both forms of Chinese (Traditional and Simplified for written and many of the spoken dialects of Chinese just happened to be a few of them and I actually can speak now 23 difference South Eastern Asian Languages including the native language of both my parents (Tagalog since they are both Filipino and about 50 or so of the dialects of Tagalog as well Tagalog-Bekul and Tagalog-Pampagan are my parents Dialects and I can also speak straight Tagalog as well as a more common form of Tagalog in the US known as Filipino, US Tagalog or Tagalog for Translation which is basically straight Tagalog mixed in with Spanish and English words as and if spoken right by US standards every sentence has at least one Spanish and English word, I can even speak and read a few European languages and even Russian and many forms of Latin and Slovic Based languages since once you learn one its very easy to understand another). Anyways enough about my linguistic skills though somewhat relevant not really. To use the RootMaster App you are going to be selecting the second button from the top in the middle of the app which if you can read Simplied Chinese says Root Phone. Various two button popups come up (about four of them) but every time you see a popup tap the button on the left and keep going until a script starts to root the phone.

When done a second menu should appear with 3 buttons as well do not hit anything at this point especially not the second button which will unroot your phone but it will not unroot your phone properly. As of now your phone should be rooted and SuperSU should be installed. If you rooted it properly MobileGo should have installed SuperSU 1.94 and RootMaster should have Installed SuperSU version 2.01 and your phone is now rooted properly.

Another method which sorta works is by using KingoRoot SRSroot or RootGenius instead of MobileGo but a few of those PC root apps installed KingUser as the SuperUser and that is rather difficult to work with and most apps do not support KingUser as the SuperUser and basically makes those root methods useless until SuperSU by ChainFire or SuperUser By ChainDD are which are the only two properly recognized SuperUser apps. SuperSU has more compatibility than SuperUser and is the preferred SuperUser app of all root users SuperUser if used with KingUser does not replace KingUser's SuperUser Binary and actually causes a ton of conflicts and Installing SuperSU on top of KingUser does not disable KingUser like SuperSU does with SuperUser and KingUser will actually keep reinstalling itself and making it the default SuperUser until unrooted with the app that rooted it in the first place. SRSroot though says supports the Event actually has a rather difficult script to work with which is the root by recovery method and it doesnt work right to begin with and if you screw that up when then it access root partially can removing that partial root is near damn impossible but it can be done.

If you happen to screw up my sequence MobileGo does not have the ability to proper unroot in this situation SRSroot however can unroot any root done by any PC root application and to remove any PC based root use the unroot option of SRSroot or RootGenius if it happens to tell you that your phone is rooted if you can read the Simplified chinese you can unroot the phone using RootMaster if you dont use z4root which happens to be in english and is much easier to work with. z4root cannot root the Event and trying to is a waste of time even if it says it rooted it. To verify you unrooted actually use Ministro II and POOT by running the root check option of POOT. Also to verify your root as well and that is also working properly POOT is also useful since it can actually tell you what root binaries are being used and in what paths.

Ideally the only root path you should have is /system/xbin/su and that is the recognized root path of almost all root applications other root paths that can work is /system/sbin/su and if you happen to have more than one root path which may occur by trying several other methods before mine /system/sbin/su as well as /system/bin/su should redirect to /system/xbin/su which will make your root stable even with multiple root paths. I recommend using z4root as well as SRSroot prior to using my method to ensure a clean root to only /system/xbin/su.

Enjoy your properly rooted Event everyone hope this little post helps
 
Upvote 0
Ok geekbrain... Typing a ginormous post is not always the smartest route, except for those that can actually sift through a thesis. I'm glad you can speak and write in many languages, but this is a forum for Android devices, not linguistic mastery. ;)

So what you're saying is Rootmaster should work to root with update 1.0.20. Look for the English versions.

Mobile go is needed to push the apks to your Event. These apks are busy box and SuperSU. Otherwise these can be downloaded from Google Play. Get them before adding any apps that require root access, like Link2SD and Titanium Backup.

Kyocera KC02 drivers are needed on a Windows PC before using Mobilego.

I'm betting that doing a factory reset should remove root. I've done that with every version of the Event software, though I don't have the latest one. I keep mine as a backup.

Oh, another thing... links people can use are a good idea!

Rootmaster on XDA:
http://forum.xda-developers.com/showthread.php?t=2672150

Mobilego:
http://mobilego.wondershare.com/

Kyocera drivers:
http://www.driverscape.com/download/kyocera-usb-kc02us-modem

Done. :)
 
Upvote 0
Ok geekbrain... Typing a ginormous post is not always the smartest route, except for those that can actually sift through a thesis. I'm glad you can speak and write in many languages, but this is a forum for Android devices, not linguistic mastery. ;)

So what you're saying is Rootmaster should work to root with update 1.0.20. Look for the English versions.

Mobile go is needed to push the apks to your Event. These apks are busy box and SuperSU. Otherwise these can be downloaded from Google Play. Get them before adding any apps that require root access, like Link2SD and Titanium Backup.

Kyocera KC02 drivers are needed on a Windows PC before using Mobilego.

I'm betting that doing a factory reset should remove root. I've done that with every version of the Event software, though I don't have the latest one. I keep mine as a backup.

Oh, another thing... links people can use are a good idea!

Rootmaster on XDA:
http://forum.xda-developers.com/showthread.php?t=2672150

Mobilego:
http://mobilego.wondershare.com/

Kyocera drivers:
http://www.driverscape.com/download/kyocera-usb-kc02us-modem

Done. :)
what i'm saying is you need more than one root kit for a proper root on the new firmware mobilego and rootmaster seems to work best for me and i've tried tons of root kits but when it comes to pc roots or any other rootkit throw a root with rootmaster on top and you should have a stable root but also be aware of root kits that also use kinguser as the su app kinguser causes a whole lot of problems mobilego has a rootkit feature in it and is not just good for pushing the apps to the event mobilego and other rootkits give a basic root to the even and when used along with rootmaster it fixes the problems with the root paths tends to either redirect to the proper root path or remove them altogether and u do not need to install the kc02 drivers or any drivers for that matter to use mobilego though manufacturer drivers do tend to work alot better than mobilego's generic drivers but just using any single root kit does not give a stable root and the only rootkit that actually gives a stable root to a basic root on the event so far seems to be rootmaster and i've tried multiple rootkits and different combinations and rootmaster along with most other rootkits pc or apk based seem to work but poot does not work at all for 1.0.20vm even on a clean out of box event most rootkits work singlehandedly on the older firmwares but not on 1.0.20vm doing a factory reset doesnot always remove root depends on whether or not the root was stable to begin with if the root is stable doing a factory reset will not remove the root nor with it on any phone. root is built into the default system partition which the factory reset does not modify though a proper root with modify the system partition. factory reset only wipes the data/cache/dalvik partitions not the system partition. you also do not need root to push apps into the phone using adb you need it if you are removing system apps or adding apps or updating apps that are built into the system partition by default but you do not need root to push apps to your phone with mobilego or via native adb to the data or phone storage partitions only to the system partition one last bit of info when it comes to rooting 1.0.20 root for basic access first using a pc root or the root z2c exploit from binary root then use rootmaster afterwords otherwise it will end up at the spot you were to begin with an unstable root it seems that the majority of the pc rooters use the z2c exploit so if you have that ability to use that exploit in the apk form use it saves alot of time but my opinion mobile go works fast easy and its more or less an all in one phone setup app. does pretty much everything you can do with a whole collection of apps on your phone. roots backups apps/data/ringtones/files/games/music/pics/vids its definately worth exploring.
 
Last edited:
Upvote 0
what i'm saying is you need more than one root kit for a proper root on the new firmware mobilego and rootmaster seems to work best for me and i've tried tons of root kits but when it comes to pc roots or any other rootkit throw a root with rootmaster on top and you should have a stable root but also be aware of root kits that also use kinguser as the su app kinguser causes a whole lot of problems mobilego has a rootkit feature in it and is not just good for pushing the apps to the event mobilego and other rootkits give a basic root to the even and when used along with rootmaster it fixes the problems with the root paths tends to either redirect to the proper root path or remove them altogether and u do not need to install the kc02 drivers or any drivers for that matter to use mobilego though manufacturer drivers do tend to work alot better than mobilego's generic drivers but just using any single root kit does not give a stable root and the only rootkit that actually gives a stable root to a basic root on the event so far seems to be rootmaster and i've tried multiple rootkits and different combinations and rootmaster along with most other rootkits pc or apk based seem to work but poot does not work at all for 1.0.20vm even on a clean out of box event most rootkits work singlehandedly on the older firmwares but not on 1.0.20vm
 
Upvote 0
as for root getting reset every time you do a factory reset you didnt root your phone right. rooting when done properly will modify the system partition whether or not you saved the superuser to the system partition might be why you claim it reset your root by default superusers when installed manually do not automatically update the system partition and add itself to the system/app directory if you allowed your superuser to do that then your root should be there along side with your superuser app but once you have root whether or not your superuser has been integrated into your system partition you should have root when you factory reset your phone with or with out a superuser app busybox as well as xposed installs also modify the system partition as well and those too should also be present after a factory reset as well with or with out the installer or managing apps since busybox's and xposed's installer needs to be manually integrated into the system partition lucky patcher as well as titanium backup can do that for you or if you are savvy enough to figure out how to do it manually using root explorer or es file manager you are golden but busybox's installer once installed to system does not need to be installed as a app after installation to system xposed as well as any superuser does because you manage your root access with your superuser app and to do that your superuser app needs to be running and active and for xposed to run most of your modules you need xposed to also be running so getting rid of either of those apps is not exactly the best of ideas but busybox is different also if you have a proper root to begin with needing to use a superuser is not needed either because the root apps can access root without the need of a superuser app. how do you think the superuser app get access to the root to begin with. the super user binary just redirects the root access to the superuser app but if there is no superuser binary then all apps that can use root have access to root
 
Last edited:
Upvote 0
Wall of texts (especially with little to no punctuation) are very annoying in my opinion. Just saying.

Also, that's a really long process.

I honestly don't think anyone needs to do all those steps geekbrain outlined. Most rooting methods usually come down to pushing su, busybox, fastboot (some devices don't need fastboot) and a custom recovery like clockmod or twrp. The extra steps are typically a specially made way of exploiting the security checks of a particular device; with the Event, that was done using poot and ministro 2 (before the 1.0.20 update).

I miss guys like AndyOpie150. He was terrific with responding to anyone about rooting over at the LG Optimus V forums, newbie or expert.
 
  • Like
Reactions: Mikestony
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones