• 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

Any recovery is an option. But the issue is the locked down bootloader. It requires signed imgs in order to boot.
 
K Rize said:
Has anyone considered trying TWRP as an option
Click to expand...

Short answer: Yes. Long Answer: I have, but I haven't gotten around to building the source yet. Honestly, I haven't looked into it at all, but afaik, TWRP is still based off of CWM. The issue is that we can't even get our repacked stock recovery to boot.
 
K Rize said:
Has anyone considered trying TWRP as an option
Click to expand...

Maybe we should get pants that fit before worrying about what color they are. ;)

Off topic, hey mods is it possible to block that "redigua.com" site completely? It seems to be SEO garbage leeching content from here. They don't even bother to fix bad information they swipe from us.
 
cooldudezach said:
Short answer: Yes. Long Answer: I have, but I haven't gotten around to building the source yet. Honestly, I haven't looked into it at all, but afaik, TWRP is still based off of CWM. The issue is that we can't even get our repacked stock recovery to boot.
Click to expand...

Yeah, I don't think it would matter who's recovery it is. Pretty sure that the CWM we made would work if we could get around the locked bootloader that is forcing it to bypass the altered recovery.
 
kinda a bump here &

Please only the android programer look at this i wanted too again state in this post also that i have no ideal on what iam doing when it comes too programming android devices so unless u know what your doing dont download anything iam about too post in this link
--------------------
i found this and i wanted too know if it in anyway helps you guys also was reading up on odin dunno if u can flash your custom recovery images useing that but this is info i found its not for the rise but supposedly it was a really hard down locked phone that required signed signatures and everything so in my posting this here iam hopeing maybe it will help you guys in contacting or communicating with others working together too crack this thing and get cwm recovery on our rises

Updated (4/21/2011): [Exclusive] How To Root The HTC ThunderBolt And Unlock Its Bootloader

if its of no help too any of you android pros please just disregaurd and delete this post so it doesnt confuse others thank you
 
smartmanvartan said:
Could i get a link to that recovery?
Click to expand...

I didn't keep mine, but we used the Recovery Builder to build a CWM Recovery using the recovery.img file from our phones (the stock recovery image i also posted earlier in this thread). A few people made a few other non-working recovery images as well. I'm guessing if you have a way to unlock the bootloader, you can probably get someone to work with you on a recovery image.
 
ngtwolf said:
I didn't keep mine, but we used the Recovery Builder to build a CWM Recovery using the recovery.img file from our phones (the stock recovery image i also posted earlier in this thread). A few people made a few other non-working recovery images as well. I'm guessing if you have a way to unlock the bootloader, you can probably get someone to work with you on a recovery image.
Click to expand...

Yeah, i used the online builder too, with the stock image i pulled from the phone. Same issue as everyone else haha. I think I'll try to compile the bootloader today....If one exists.....Wish me luck!

Edit: Nevermind, apparently when i go through a bunch of hassle to try to download the source, it decides not to connect to android.git.kernel.org.....strange that it should need to, but apparently without that it pulls a fatal error. Maybe i'll try again tomorrow.
 
Here's a tip that may be useful to someone, so far I can't get it to work:

With the Rise TURNED OFF, plug it in to your computer via the USB cable it came with. You will see a device with USB ID 0482:0570 - this is "KYOCERA USB Modem".

This is what we'd be using to hook in to the Qualcomm chipset, like with Kyocera Wireless PST or CDMA Workshop to get the SPC/MSL (same thing on this beast). Unfortunately it keeps installing in Win2K as a "human interface device" instead of a modem for some dumbass reason. Maybe someone else will have luck.

Kyocera Wireless has USB drivers available for download. Maybe if they were installed first, before plugging in the Rise?

How is this relevant to CWM? Because sometimes, on some phones, having access to the SPC/MSL lets you unlock it in other ways too.
 
downthemachine said:
Good find, might be a way into or to unlock the bootloader
Click to expand...

Maybe, I give up on that avenue though. There's something there but using Windows is too damned irritating anymore. :p

For anyone else, "Kyocera Phone Desktop" is irrelevant to this, Google lies.
 
db2 said:
Maybe, I give up on that avenue though. There's something there but using Windows is too damned irritating anymore. :p

For anyone else, "Kyocera Phone Desktop" is irrelevant to this, Google lies.
Click to expand...

hey i was reading something i cant do it cause i dont have adb i normally use terminal emulator but u cant use terminal emulator from rom toolbox pro in safemode , i was reading that some locked bootloaders in android 4.0.4 can be unlcocked by being in safemode useing adb and useing this code
Run the following command

fastboot oem unlock

also wanted to mention that from what i read doing that it says too backup ur data idk why it would say that but iam not brave enough too try
 
We don't have access to fastboot, unfortunately. Kyocera locked it out.

The "back up your data" thing is because it wipes out your data, all of it. The claim is that it's for "security" but I never swallowed that line, it's to deter people from unlocking.
 
AndroidHaCks said:
Would a safestrap recovery work, like the droid razr has because of it's locked bootloader?
Click to expand...

Maybe, it appears to set things up so the stock OS is acting as the host with a guest OS of your custom ROM, all that would need is root and we have that. If it came down to it it's better than nothing, but there's an inherent performance hit by running two instances of Android at once. It'd probably make our Rise about as clunky and slow as the original Samsung Transform.
 
db2 said:
Maybe, I give up on that avenue though. There's something there but using Windows is too damned irritating anymore. :p

For anyone else, "Kyocera Phone Desktop" is irrelevant to this, Google lies.
Click to expand...

On my linux install, it sees this mode when I run lsusb, but other than that it doesn't do anything. I have the same issue on Win7 that you described with Win2k (People still use that? o_0)
 
little bit of breakthrough here!!!!! got my rise into fastboot!! and just for suspense... I'm gonna wait till someone asks me how... :p

Hint: fastboot is not locked... what they call bootloader /dload is something else and and you are right none of the known command for adb refering to getting into fastboot work... so what's left...
 
once i got rooted i downloaded notification toggle and thru the reboot menu that requires root i pressed on "reboot bootloader" and voila! but i tried for hours with adb with no success before i started thinking outside the box... :D!!! working on cwm now and gonna test a flash... wish me luck
 
Interesting, good luck!

I'll have to grab a copy of that and take it apart to see what it's doing. Crash course in Java here I come!
 
smartmanvartan said:
once i got rooted i downloaded notification toggle and thru the reboot menu that requires root i pressed on "reboot bootloader" and voila! but i tried for hours with adb with no success before i started thinking outside the box... :D!!! working on cwm now and gonna test a flash... wish me luck
Click to expand...

Nice dude! This could be exactly what we need haha

Edit: Also how exactly did you get the shutdown menu in notification toggle to work? I keep pressing reboot bootloader, but every time it just still reboots to android.
 
You must log in or register to reply here.
Back
Top Bottom