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

Root Porting ClockWorkMod to the Kyocera Rise

cooldudezach

Android Enthusiast
Jun 27, 2011
556
195
First off, let me just say that I have been quite unsuccessful at getting CWM to work. I also am new to this, so I could be doing something wrong.

I picked up this phone on Black Friday for $30, what a steal! I am excited to get started in a new community and get the ball rolling for custom recoveries and ROMs. Since there hasn't been any progress on getting CWM onto the Rise, I decided to take up the helm myself and figure out what works and what doesn't work.

So far, this is what I have attempted:
-- I have made backups of recovery, boot, system just in case I screw something up. At the moment, only the recovery backup does me any good, because if I screw up boot or system, and can't boot into Android, I have no adb.
-- Wiped recovery/boot to try and get into fastboot. DONT DO THIS! You will end up with a bootlooping paperweight. So far, fastboot is out of reach.
-- adb reboot fastboot/bootloader and adb reboot-bootloader just reboot the phone normally.
-- Unpacked and then repacked recovery.img and used dd to push it to the phone. Failed to boot into recovery, it just rebooted itself back into Android.
-- Unpacked boot.img and placed the kernel from there into recovery.img. Same thing.
-- Built kernel from Kyocera's sources. placed that into stock recovery.img. Failed to boot into recovery.
-- Built CWM from source using the kernel extracted from the recovery.img. Again, failed to boot into recovery.
-- Built CWM from source using the kernel built from source. Still failed to boot into recovery.
-- Flashed boot.img to /recovery, just to see if it would do anything, and surprisingly enough it booted straight into Android. Before it was attempting to boot into recovery, then it would reboot the phone again, which brought it to Android. Replacing the recovery partition with the boot.img boots straight into Android without any reboots. This might be a clue, maybe not. I'd assume that recovery.img on the /boot partition would boot the phone into stock recovery every time the phone is rebooted.
-- I emailed Kyocera about how to unlock the bootloader. This was their response:
We are sorry to hear about the difficulties you are experiencing and appreciate the opportunity to assist you.

There are ways to unlock the boot loader but we do not recommend doing so as it will violate our company's agreement with Virgin Mobile. We apologize for the inconvenience.
Maybe if we keep emailing them, they'll tell us.

If anybody has any ideas, I'm willing to try them out, I still have another testing phone just sitting here. If anybody knows a dev who would be willing to port CWM, I could send the dev my testing phone. Let's get this ball rolling!
 
Thanks for the info.

I'm surprised more devs aren't jumping on this cheap phone. I mean it runs the same CPU/GPU class as the one v and reverb, and can be had for $29.99.

On my other device, the Acer a100, we needed to flash an a200 bootloader to unlock. As the a100 doesn't respond to the unlock command. I don't know if kyocera locks all of its bootloaders, or if a different device's bootloader would even work on the rise. But that's the only idea I have.
 
  • Like
Reactions: Hydra119
Upvote 0
Well, I just ran another test based on a theory. So the hydro is our sister phone, supposedly the same phone, just different bodies. I took the recovery and boot partitions from the hydro and flashed them onto the recovery partition of my rise. They both booted fine, with a small graphics quirk. The recovery screen was upside down, and the phone screen would flip upside down after the screen was turned off. However, the touch controls were as if the screen was not flipped. This goes to show that the hydro and rise are pretty darn compatible, the only noticeable issue is that the graphics driver is a bit screwy.

What does this mean? Well, maybe we CAN get CWM successfully on the Rise and Hydro, the drivers and config need to be properly setup. I just don't know how to do that.
 
Upvote 0
  • Like
Reactions: tresveces
Upvote 0
Hey dude, I just got the rise too, and i have to say it was quite a steal for $30. I have managed to get into stock recovery, and have backups of my system, but cannot seem to get the recovery.img. I'm interested in helping with this, and have quite a bit of experience with building android and just messing around with Stock ROMs. If you could PM me a link to the recovery.img, or instructions on how to get it, that would be great.
 
Upvote 0
Hey dude, I just got the rise too, and i have to say it was quite a steal for $30. I have managed to get into stock recovery, and have backups of my system, but cannot seem to get the recovery.img. I'm interested in helping with this, and have quite a bit of experience with building android and just messing around with Stock ROMs. If you could PM me a link to the recovery.img, or instructions on how to get it, that would be great.

The way I pulled a copy of my recovery.img was using dd.
[HIGH]//mmcblk0p15 = recovery block
dd if=/dev/block/mmcblk0p15 of=/sdcard/recovery.img
//mmcblk0p8 = boot block
dd if=/dev/block/mmcblk0p8 of=/sdcard/boot.img[/HIGH]
 
Upvote 0
The way I pulled a copy of my recovery.img was using dd.
[HIGH]//mmcblk0p15 = recovery block
dd if=/dev/block/mmcblk0p15 of=/sdcard/recovery.img
//mmcblk0p8 = boot block
dd if=/dev/block/mmcblk0p8 of=/sdcard/boot.img[/HIGH]

Wow, I'm stupid. I spent hours trying to mount one of the partitions in Ubuntu, only to realize that it's impossible, and it wasn't even recovery. Anyways, using the right partition this time, i tried using The Online CWM Recovery Builder, and It built succesfully. I have no idea how to flash it to the recovery partition though, because i'm not familiar with flashing to partitions. How would i accomplish this, and how can i make/restore backups so i don't brick this thing?


Edit: I flashed the Recovery, and It wouldn't boot into recovery. Black screened until i let go of the buttons, then rebooted into android. Maybe Kyocera did lock the bootloader.....
 
  • Like
Reactions: cooldudezach
Upvote 0
Wow, I'm stupid. I spent hours trying to mount one of the partitions in Ubuntu, only to realize that it's impossible, and it wasn't even recovery. Anyways, using the right partition this time, i tried using The Online CWM Recovery Builder, and It built succesfully. I have no idea how to flash it to the recovery partition though, because i'm not familiar with flashing to partitions. How would i accomplish this, and how can i make/restore backups so i don't brick this thing?


Edit: I flashed the Recovery, and It wouldn't boot into recovery. Black screened until i let go of the buttons, then rebooted into android. Maybe Kyocera did lock the bootloader.....
Same thing happened for me. I manually built it using the ics tree, and automatically built it using the online builder which uses the jellybean tree. neither worked. Like you said, it just blackscreens and reboots. As i've stated, the boot and recovery images for the Rise and the Hydro both booth properly. It could be a simple fix, maybe not.

Rom manager should be able to flash it if its a cwm recovery you made but I'm not sure but yet again I think it would work
Again, no. I HAVE flashed two custom builds of CWM, outside of rom manager, for the rise but neither booted. They just blackscreen and reboot. I've also flashed a few versions of stock that have just been repacked. Even if you used rom manager, there is no guarantee that it would flash. Most likely you could very easily just brick your phone.


I think I'm just going to go on a flashing spree to see if I can get a recovery to boot. :dontknow:
 
  • Like
Reactions: sneaky_1
Upvote 0
ROM manager is a death trap for alot of devices. I would stay away from it like the plaque, and do everything with adb.

The only time I use ROM Manager is to flash CWM to my Optimus V, if I ever do anymore. I've been using Cannibal Open Touch for quite some time on it now, so I haven't touch ROM Manager for awhile. ADB and Terminal Emulator are my best friends.

Anyway, I still haven't had any luck getting a recovery to work. I'm stock out of ideas.
 
Upvote 0
Well when I was monkeying around it said if I had flashed a cwm based recovery click yes

Just don't play with ROM Manager. ever. It's not a good idea, unless ROM Manager has a listing for the phone. If you picked a random phone model, then chose to flash the recovery, most likely it would not even flash to our recovery partition. This is because different phones have different partition setups. I've seen phones with the recovery on mmcblk0p15, mmcblk0p8, mmcblk0p17, etc. Other phones run on a different partition system altogether. You won't know what the harm is until it's been done.
 
Upvote 0
The only time I use ROM Manager is to flash CWM to my Optimus V, if I ever do anymore. I've been using Cannibal Open Touch for quite some time on it now, so I haven't touch ROM Manager for awhile. ADB and Terminal Emulator are my best friends.

Anyway, I still haven't had any luck getting a recovery to work. I'm stock out of ideas.

I emailed Kyocera, and they said i should contact Virgin Mobile about the bootloader, assuming it is locked. Virgin Mobile still hasnt responded. Guess im not really their priority right now.
 
Upvote 0
Can someone explain to me what this is
q5cFQTylbazVblKTdG0RfB4P+jK+gScR8R1M+kcRD84c8mMy38wH8/QJbSlg7SoLJWdWmmRRzKRFmIwDnnBhHWhyDZ1yRaGKqRa0htApG05IqmB9WOmx1uO3Hr/1urE/hJmQKKJgYXhNJgQTwiIcKRGzqJ8LWKpdBJxJnlDLrd7fmyFPteHV/w3rhR+PHf56PnprwfQFtP2oNLt48Xe5/r00v7fwALPaJSNjariVp5loFJZRWLXi+eXs7X35/rg0pJ11FMyt9FyThjzP1mHItg1XtYZ62ztbh72mz/Oavoq8MjKzv9NMtu1mnjv4mWy4qjW0ebRbzzMVd9D0VXTkmFTQzhUVYwVqVIyTmN3sdfGMJ9mYShzo+2B9zTsubmRKAqrvGQoeh3hNk6TwKWHIM4WKiIgqTAUPs0Ch62w6Dgoa8AkVBQrOFUo/ZhgG3Y39rp/Jwuf5/BebpPjDcwIAAA==Symlink: /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/C5155/recovery/root/sbin/dc -> busybox
Symlink: /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/C5155/recovery/root/sbin/dd -> busybox
Symlink: /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/C5155/recovery/root/sbin/dedupe -> recovery
Symlink: /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/C5155/recovery/root/sbin/depmod -> busy

I can't. Where/what is it from?
 
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