yashsingh1/xdaforums huggingface dataset:
[Android General] Unit7PsyClone:
Great Tutorial That Works...

Thank You to the Author of this Tutorial. This worked the very first time I did it. Even though i installed the wrong ES File Explorer Version, after installing the Correct one {ES File Explorer 1.5 Cupcate}, everything fell into place.

To others following the Tutorial, listen to the Author at the end of the Tutorial's section "A Few suggestions after Rooting..." Step 2 is key... Install the Titanium Backup and run the backup before adding more stuff after your device has Root Capability. That way you don't have to Redo the Tutorial again on your Device if something goes wrong in the future with installing Root required Apps.

Although when trying to use ROM Manager v5.5.2.8 (I downloaded this myself by the way), it's telling me i must have ClockworkMod Recovery Installed before I can Backup My current ROM. My Device is a Kycoera C5155. I'm sure they'll make one soon for my device. Or i'll find another ROM backup tool out on the App Store.

Thanks Again to the Author. Bravo :good::laugh:
[Android General] TechDad378:
I appreciate the positive feedback. Right now no one has figured out how to unlock the bootloader for the Rise. Therefore no CWM versions can be applied and/or tested.

Sooner or later someone will unlock it :D

Sent From Tweaked Kyocera
[Android General] thesane:
Problem with Ministro

Hello, thanks for the great tutorial but I am stuck at the Ministro libraries downloading, after the Poot open Ministro and it begins to download then gives an error "Invalid qt version" can you help me with that??

Thanks,
[Android General] TechDad378:
Can you please verify you are have downloaded Ministro 2 and NOT Ministro 1?

Please also verify you are connected to the internet via 3g or Wi-Fi. And you have a strong connection.

Sent From Tweaked Kyocera
[Android General] thesane:
Yes I am sure it is Ministro 2, also the connection is Wifi and it is working very fast. I also downloaded Ministro 2 Configuration Panel and set to testing repo. as mentioned in some other link when I searched for this error but still the same problem. I can see in logcat that Ministro 2 is going to the correct url (I can't post the url here bec I am still new) and then produce an error then crashes and go back to Poot which shows "Invalid Qt version".

I even tried Ministro 1 and it didn't work at all.

Thanks for your help.
[Android General] TechDad378:
OK, please follow these steps...

1. Uninstall Ministro 1, Ministro 2, and Ministro Config Panel.

2. Go To Setting - Developer Options - and verify "USB Debugging" and "Stay Awake" are checked.

3. Download ONLY "Ministro 2" from google play.

4. Once Ministro 2 has been installed plug your phone into the charger.

5. Run Poot again and it will download the correct libraries.

The problem can be cause by a few things... If your phone screen locks during the download it may also shut-off your wi-fi. This is why I had you check off "stay awake" and plug your phone into the charger. The config panel and version 1 of Ministro will cause problems which is why I had you remove them.

One other situation I noticed will cause the error you are encountering is the incorrect version of Poot. I am assuming you copied the version of Poot attached to the tutorial so I am ruling that error out.

Please let me know how you make out with the changes I suggested.

Sent From Tweaked Kyocera
[Android General] thesane:
I tried exactly the same steps here but still the same problem. and I used the POOT attached in the tutorial.
[Android General] TechDad378:
What is the percentage of the libraries downloaded when you get the error?

Sent From Tweaked Kyocera
[Android General] thesane:
I don't see any progress bar. it shows "Downloading Libraries" then "Downloading SSL Certificates" then close and go back to Poot which shows "Invalid qt version"
[Android General] TechDad378:
I have been testing a few ideas to duplicate the problem you have experienced. I was able to duplicate the problem. It looks like Ministro 2 breaks the connection with poot.

I am in the process of determining if another app is the cause or if it is Ministro causing the problem.

Since other people have recently applied root with no problems, I am leaning towards another app being the cause of the problem.

I will run a few test to determine if another app is the cause. If another app is not the cause I will upload the correct version of ministro 2 to this tutorial.

Sent From Tweaked Kyocera
[Android General] TechDad378:
QT Error with Ministro

I was able to locate the problem with the QT Error. It seems Ministro has updated the QT version they use in their apk. They are using QTv5 when Poot is looking for QTv4.

I found a version of Poot that uses QTv5 but the Ministro 2 version in the app store does not work properly either.

After doing some research it seems the Poot version I located and the Ministro 2 apk from the developer's website work properly.

The Ministro 2 version from the developer's website actually searches for the correct libraries for this version of Poot.

I will adjust the tutorial to reference the QT Error.

You will need to download the files called "Ministro II-QtFix.apk" and "Poot-debug-QtFix.apk" attached to the tutorial, then continue the tutorial with those two files.

I tested the tutorial with these two files, everything is the same except for the fact you will be using 2 different files for Poot and Ministro.
[Android General] thesane:
Thanks a lot for your support. I managed to pass these steps now but I am stuck now on step 10. SuperUser shows that Su binary not found. ES Explorer (CupCake) gave an error when I tried to enable root explorer.
[Android General] TechDad378:
I have updated the tutorial and added additional files. Please restart the tutorial and let me know if the issue continues. If it does continue please, provide answer the questions...

1. Did you restart your device before adding superuser?

2. Can you please verify you downloaded the correct superuser app?

3. Can you provide me the exact error message and when it appears?

Sent From Tweaked Kyocera
[Android General] pqcracker:
31 July 2013 -- Successfully rooted Kyocera Hydro running 4.0.4...

Greetings,

A friend of mine asked me for help rooting his Kyocera Hydro, so I followed the steps that were posted in this thread, but something was amiss because root just wasn't happening. Here is what finally did the trick for me:

1) Uninstall whatever versions of Ministro and poot that you previously installed.

2) Download and install v9.4 of Ministro directly from your phone's browser (first make sure that Settings-->Developer options-->USB Debugging is checked, as well as Settings-->Developer options-->Stay Awake and Settings-->Security-->Unknown sources). You can find "Ministro II v9.4.apk" at the website files.kde.org slash necessitas slash installer slash release (sorry, I am too new to post links so I'm doing the best I can here). Be sure the file you get is dated 02-April-2013.

3) After you download and install Ministro II v9.4, install Poot-debug(W100).apk, which is referenced at the beginning of this thread.

4) Launch Poot and allow it to grab the necessary updates, etc., then click "Press here to Poot" and hopefully you will be successful as I was in rooting your phone!

Hope this helps.

Best,

--pqc
[Android General] TechDad378:
Good work! It seems from my testing the problem is cause by the new version of Ministro II. Currently v10 is on the app store. The new version uses QT 5 which doesn't seem to work well with Poot.

I will update the tutorial when I get a chance and upload Ministro II v9.4. That version seems to do the trick with regular rooting on Kyocera devices.

Sent From Tweaked Kyocera
[Android General] TechDad378:
Thanks for the file location. The tutorial has been updated. Can you please verify what Android version you rooted on the Kyocera Hydro? I will add it to the tutorial as root verified.
[Android General] pqcracker:
Greetings,

Well, I feel a little on the lame side. I realize now this thread is about a Kyocera Rise, not a Hydro! I am hopeful that the two platforms are similar enough where my Hydo fix will take care of the same issues that are showing up on the Rise.

The details of my device are as follows:

Kyocera Hydro

Carrier: Boost Mobile

Model number: C5170

Android version: 4.0.4

Software version: 1.006BT

Hardware version: 0104

Baseband version: 1.006BT

Kernel version: 3.0.8-perf, built Sat Jan 12 21:59:25 JST 2013

Build number: IML77

A HUGE THANKS to everyone who makes these forums so incredibly helpful. I will never be able to repay xda-developers for all that I have learned during all the years I have been a "mute" member, but it sure felt great being able to post something kinda sorta useful!

Best,

--pq
[Android General] TechDad378:
No reason to feel lame. According to some user the Rise and the Hydro are almost the same device.

I am wondering if the Torque and Event from Kyocera can be rooted with this tutorial.

Thank you for the for the information!

Sent From Tweaked Kyocera
[Android General] fendergrab:
I have the Torque and I tried the method in the first post, but it did'nt work. This is what Poot gave me-

[-] can't get a handle on it: -1 Permission Denied

A demon materialized while pooting. Error Code: 18

SU binary was not written.

I did'nt copy and paste that, so the spelled may be off a little, sorry. I would love to have working root! This method seemed easier than the current root method for the Torque.
[Android General] early_riser:
Safe to remove Minstro and Poot?

Is there any reason to keep Ministro and Poot installed after successfully rooting?
[Android General] TechDad378:
It seems when you remove poot there are no problems but removing ministro causes you to lose root from time to time.

I suggest keeping a copy of the 2 files on your sdcard, just in case you need them.

Whenever changing files always back-up important files.

TD378
[Android General] montecristo1927:
works perfect!

Thanks for this accurate tutorial.

I tried and works perfectly on myRise Kyocera from Public Mobile (Canada).

Thumbs up guys!

montecristo
[Android General] TechDad378:
Thanks for the positive feedback!

TD378
[Android General] aerobic1:
Hello there, and let me start off by thanking you for making this easy to use tutorial. I previously had a rooted evo...and have swapped carriers and ended up getting this Rise, which is decent for my current needs.

OK, so the steps I've made in rooting my Rise have been seamless until I got to STEP 12 and 13. I enabled "Root Explorer" and then granted SuperUser rights to ES File Explorer. Then a little message pops up underneath saying something to the effect of "Due to security issues Google does not allow apps root access" or something like that. The message immediately disappeared, so I couldn't get the full verbiage.

I went to STEP 13, which enables Mount File System, but both Root Explorer AND Mount File System options are grayed out. I never got an error per say, but just got the message I mentioned above. I was curious if the rooting failed so I downloaded and ran the Root Checker you suggested and I received the green message “Congratulations! You have Root Access.”.

This might be a retarded question, but is my phone rooted if I got those Google message and was unable to check those boxes in ES File Explorer options? I know I received the Congrats message, but it just seemed odd that I couldn't check those Root settings options.

Is there another way to check whether my phone is rooted? I primarily wanted my phone rooted so I could remove bloat, and keep my file system clean. Help please! :)
[Android General] TechDad378:
The error message is caused by missing a step. The cause is because superuser permissions were not set-up right. Try this... open es file explorer make sure both root options are unchecked. Reboot phone. Open es file explorer then try checking the root options.

If that does not work doing the same previous steps but after rebooting phone open superuser swipe to the option screen by swiping from the left to right. You will see option to update superuser binary. Click update let it finish the open es file explorer and check root options.

If that fails you will need to restart the whole rooting process over. I suggest rereading the tutorial before restarting.

Let me know the exact error message you get from google. I have never seen that error. But i could troubleshoot it if it happens again.

Keep me posted on your results.

TD378
[Android General] aerobic1:
Thank you very much for your quick response. The reboot is all that was needed, after that I went into ES File Explorer setting and was able to to check those boxes. You dah man! :)
[Android General] TechDad378:
Great! Good to know the issue was resolved!

TD378
[Android General] Crithax:
Just Successfully did as such.

I bought a Kyocera Rise today as a "budget" cell phone and i'm waiting for titanium back up to back up my apps so I can start deleting the bloat.

Any word or update or rumor of some legendary hero to build this phone up to it's potential? I want my Paranoid Android back. lol
[Android General] TechDad378:
There are a few trying to still bypass the bootloader. Since its not a popular phone not many people have attempted bypassing the bootloader. Once the boot loader is bypassed installing CWM or TWRP wont be too difficult. Then the rom fun begins. Think of it as a WIP phone.

TD378
[Android General] Crithax:
I do understand that Qualcomm is the devil and why this phone is probably unsupported, but, how do you even begin doing such a thing?

I know a lot of people have to want it for CM to get a push, and Qualcomm is the reason. The S3 didn't get CM up front and the lead AOSP guy quit.:confused:
[Android General] TechDad378:
The problem with the bootloader is the keys to start the bootloader when powering on are locked. They disabled the keyboard upon starting the device. Once the device OS is booted then the keyboard is enabled. This means when you trigger the bootloader to load the system recognizes bootloader keys are disabled and resets the device automatically. One way to get into the bootloader is by triggering commands specific to only the current device. Which reduces the ability to make CWM for the Rise. Imagine making an install for each Rise device out there.

TD378
[Android General] Crithax:
Since hydro is a very similar phone the should be good on multiple levels of cracking boot loaders.
[Android General] thephfactor:
Thanks for the guide. It looks like everything worked for me. I was wondering, does the phone have to be in USB debugging mode still?
[Android General] TechDad378:
Glad to see the guide was helpful.

The phone does not need to be in usb debugging.

But if you encounter some root apps having problems turn it back on.

TD378
[Android General] biglando74:
Works on Kyocera Event

Thanks for this tutorial. Worked like a charm for my Event!!:good:
[Android General] TechDad378:
Glad to hear it was a simple process!

TD378
[Android General] luex7:
On steps 11&12 may have been error?

Am I suppose to be granting root permissions still through super user or did something go wrong, I am not sure If I had an error around step 11 or not, pretty sure I didn't do anything wrong.
[Android General] TechDad378:
Can you provide more details to your error? I need to know what is not functioning correctly in order to assist you.

TD378
[Android General] inflman:
Techdad i followed your instructions to the letter in one go in just under twenty min

:good::highfive:
[Android General] akiramaru12:
dunno what happened....

hey there. i followed your root guide and all things went great. root was acheived W00t! i installed titanium back up and so forth and but i removed it later on(couldnt afford the full version) now i've installed titanium back up again and it's tell me root access failed. what should i do? should i try and re root(if thats even possible how to do it) or what??? so confused
[Android General] doctazz:
Works for me!

I used this guide to root my Kyocera Event. I did nearly everything as described, but to check root, I opened a terminal app, typed # on the command line, and got the prompt from superuser that allows the terminal app to gain root access.

Some users have complained of not being able to root after the phone gets the latest updates (firmware, PRL and system). I got those after activating the phone. I rooted it shortly after that, and noticed no issues.

Thanks for writing this guide! :cowboy:
[Android General] ciscogee:
Just uninstall the apks in op and reinstall. Then the reroot
[Android General] yungtigger87:
my thank you

im sure its because i have no idea how to use this site i can not find the thank you button or icon but ill say it here thanx a bunch
[Android General] kendalf89:
dont work

Either trying other root methods before trying this one has broken this method for me or it simply doesn't work anymore. Also the instructions for the QT error fix were ambiguous and confusing; I ended up getting my **** caught in the ceiling fan.
[Android General] mtx thunder 9500:
thank you

thank you so much followed step by step and everything went smooth just a tip to the people trying to get the apps on their phone get an sd car reader to get the apps on your sd card makes life much easier thanks again for this root tutorial my phone is now rooted after months of trying thanks again!
[Android General] Holhat:
Perfect!

Followed the directions and it worked perfectly on my Virgin Mobile Kyocera Rise!

THANKS!
[Android General] delman420:
OK I just got this phone and am happy I can root it unhappy I can't unlock the boot loader so what can I do I need to flash some zip files to get inverted apps any way around that darn I'm missing my old school evo team nocturnal and bill Bowers but this is all I can afford now
[Android General] ciscogee:
Adb push your apks
[Android General] delman420:
I never really pushed stuff to my phone can I do it with terminal emulator or do I need a computer
[Android General] ciscogee:
Sorry not on much...

I'd use PC...

What's in the zip file?

If apks that might work on rise just unzip and install from sdcard
[Android General] QueeNxAshlee:
help please

After installing both ministro 2 and the poot file on this tutorial I don't get the same error you got which is error 64 and then it tells you to restart your device but what I do get is an error 22 and says that the su binary was not written ... I don't know what went wrong please help
[Android General] lay770:
thanks rooted three phones. going to use them as wireless video cameras
[Android General] fashes:
Help? I've read this thread and everything androidforums Rise sections and poked around XDA. All the root check apps I tried say I'm rooted but there are to things I cannot do.

1. I can't freeze apps, system or user installed. When I try to freeze, with Titanium, Link2SD, or SystemCleanup they all hang.

2. I can't (force?) move apps to SD with Install Manager (Alfred Nuemayer), SystemCleanup etc.

3. I can't change autorun features with Autorun Manager, SystemCleanup, Titanium (?). So FRUSTRATING.

Any ideas? I still have Miistro and Poot installed.
[Android General] ciscogee:
Remove superuser and start over. After reroot . Install busybox. And don't update superuser.
[Android General] AbandonAllSirens:
Kyocera rise root

ok so im so confused. I used one of those stupid youtube tutorials and at first i thought it worked. Poot said i was rooted and i was able to use screenshot apps and root explorer (not fully tho). It wont pop up asking to allow apps so i cant even go in and delete the SU file and start over. Poot says im rooted but Root check says im not. Im so confused. Do you have any ideas?

---------- Post added at 03:07 PM ---------- Previous post was at 02:07 PM ----------

I GOT IT :D:laugh:
[Android General] :
Use new su versions, or other superuser apps, on Kyocera Event/Rise 4.0.4

Hi!

Note: Event and Rise are near identical as I understand it, hence this post being in this thread.

I used the OP instructions to root my Event.

I was really annoyed I couldn't use other superuser app's, or a newer su, on my Kyocera Event 4.0.4.

So I spent all day tinkering with it, and found why this is the case, and also a workaround.

Reason:

New/other su's need 'am', which calls 'app_process'.

This apparently is linked against 'libkcjprop_jni.so', which seems a special Kyocera lib, which lives in /sysprop/kcjprop/

(BTW: I have no idea what this file is or does, I'd love to know).

This file can be found/linked using LD_LIBRARY_PATH, but for 'su' the LD_LIBRARY_PATH is wiped (for security I've been told), which means that only lib's in /system/lib will be found. So we get a nice error when starting 'app_process':

Fix:

Just in advance, I have only been messing with android since a week, so this is likely not the best/cleanest/safest way of fixing it, but for me it works great :)

With a su shell/terminal/ssh/etc. do these commands:

In short, we make a symlink in /lib/system to the library, and now it can always be found, no more error :)

Some more details here: https://github.com/koush/Superuser/issues/232

Hope this helps someone!

Cheers :)
[Android General] Bowling4Nintendo:
Problem

Yeah, im gonna feel stupid when i say this, but i have a problem.

I have a VM Kyocera Event-just got it last week-and wanted to root phone due to used space by unused apps. I have done this before with a VM LG Optimus V v.2.2.2 with gingerbreak, so i know a little on what to expect. I have heard many users with the Event say it worked, but thats not the case with me...

I have done all of the steps that you have provided up to the point of "pooting your phone" (in which were pretty easy) yet i still get the same outcome:

2012 giantpune

[+] opened device

[+] set logging mode

[+] Resolved symbols

[+] Mapped 0x10000000

[-] expected currect to be 1: ffff

[-] patching failed

A demon materialized while pooting. Error code: 22

SU Binary was not written.

Like I said, I know a little about rooting and based on the tutorial, this shouldn`t be happening. HELP!! :(
[Android General] Bowling4Nintendo:
Nevermind, im an idiot. Lol

I jumped the gun an updated the binary when i wasn't supposed to. Nonetheless, successful root for Kyocera Event. Thanks, bro!!
[Android General] Tarrnation:
This method still works as of FEB 24, 2014. The "poot" message is a bit different and it threw error "22" instead of "64". However, it does not seem to matter as I continued on with the steps and successfully completed the root process. Thanks to the OP for this fantastic tutorial! :good:
[Android General] pgringo:
i just had the same experience on march 6, 2014 with a new virgin mobile kyocera event. :thumbsup:
[Android General] RebeldeFaith:
THANK YOU!!!

OMG!!! Thank You so much for this. I've been trying to root my Kyocera Event for a couple of weeks now and I have failed every time (almost 8 to 10 times). I almost give up until I found this thread and did everything it says and it worked. I HAVE SUCCESSFULLY ROOTED MY PHONE!!! I'm so happy I feel like I can sleep now.

This is my first smatphone so this is also my first time rooting one. Thank you!!! ;)
[Android General] Handsome Jack:
Can I uninstall the Ministro II and Poot-debug(W100) after the phone is rooted?
[Android General] delman420:
Some say yes, some say no. So I just left them in my download file on my SD card. I haven't had any issues, but unfortunately my rise is screwed at the moment. My SD card is not recognized. It absolutely will not mount no matter what I try. So if anybody has any suggestions I would appreciate it. Thanx

Sent from my poot-rooted C5155 using Xparent BlueTapatalk 2
[Android General] sgirard1991:
Thanks.

Worked flawlessly first try.

:good:
[Android General] delman420:
What do ya know SD card reading again thank goodness you can't do d#@k without onr

Sent from my poot-rooted C5155 using Xparent BlueTapatalk 2