Rooting my Kyocera rIse :) Need sound advice and opinions
So I'm about to root my brand new kyocera rise. I've downloaded and backed up all my apps. I believe Google should take care of backing up my contacts and simple information. Is there any other prerequisites I should take into consideration? Got it connected as media store device, usb debugging enabled, and unmounted the SD card.
Device(s): HTC One V. AOKP Jelly Bean 4.1.2. Overclock @1.7Ghz Stable.
Carrier: Not Provided
Thanks: 1
Thanked 6 Times in 6 Posts
Sounds like you got everything in order. I rooted my Rise after having it for 2 hours. Then I took it back because I hated the phone. But, to each their own. Enjoy the root access!
Only thing I would do is maybe go to your gmail account just to make sure that the Contacts are saved. Putting new contacts in your phone is such a hassle!
The Following User Says Thank You to RyanSupertramp For This Useful Post:
Sounds like you got everything in order. I rooted my Rise after having it for 2 hours. Then I took it back because I hated the phone. But, to each their own. Enjoy the root access!
Only thing I would do is maybe go to your gmail account just to make sure that the Contacts are saved. Putting new contacts in your phone is such a hassle!
Was your Kyocera RiSE running 4.0.4? I've tried several times to root this firmware version and it hasn't gone through yet... Super One Click didn't work and neither did Bin4ry's method from XDA developers.
Yup that's one of the programs I've tried No luck >.< Although I see where it's a confirmed rooted phone in the listing... My version 4.0.4 is stock. I haven't done any flashing yet.
Device(s): HTC One V. AOKP Jelly Bean 4.1.2. Overclock @1.7Ghz Stable.
Carrier: Not Provided
Thanks: 1
Thanked 6 Times in 6 Posts
Quote:
Originally Posted by jlgarr86
Yup that's one of the programs I've tried No luck >.< Although I see where it's a confirmed rooted phone in the listing... My version 4.0.4 is stock. I haven't done any flashing yet.
The link the Admin gave is the same link I used to root the Rise. It actually took me twice to root it. It didn't take on the first try, I'm not sure why..
There appears to be some sort of issue with that script and the timing with the commands it executes and our phone. I had to try it upwards of 20 times before it was successful.
So you're saying rooting 4.0 Kyocera rIse is possible it just takes a lot of tries? Could someone tell me which program they used that gave a successful root access?
Just did it in a hotel room. No fansy equipment/apks from my usual hack station at home. I use v15, the last one; had problem with the driver on 64 bit win sys. I switched to a winXP 32 bit system, and got driver from unlockroot.com. And ran it 3 times, and upgraded the superuser.apk and reboot several time. and it rooted.
Was your Kyocera RiSE running 4.0.4? I've tried several times to root this firmware version and it hasn't gone through yet... Super One Click didn't work and neither did Bin4ry's method from XDA developers.
Took me awhile to figure this out but the rise doesn't support the "prompt" setting in SuperSU. This needs switched to "always"... Just be sure to back up your rise immediately...
Took me awhile to figure this out but the rise doesn't support the "prompt" setting in SuperSU. This needs switched to "always"... Just be sure to back up your rise immediately...
Use this root method, [GUIDE] Root your Kyocera Rise! - Android Forums at AndroidCentral.com
It has a different version of superuser that works on the rise. I wouldn't update the binaries, or the superuser app, as it may break it. I haven't tried updating from this version, but the latest superuser app and binaries that I installed before broke root. I would leave well enough alone in this case. This version fixes the no prompt/no log of root access, that has been talked about in other threads.
Use this root method, [GUIDE] Root your Kyocera Rise! - Android Forums at AndroidCentral.com
It has a different version of superuser that works on the rise. I wouldn't update the binaries, or the superuser app, as it may break it. I haven't tried updating from this version, but the latest superuser app and binaries that I installed before broke root. I would leave well enough alone in this case. This version fixes the no prompt/no log of root access, that has been talked about in other threads.
Assuming the versions are from the v2 version of the rooting script, you can update the superuser app. I was able to at least.