• 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 said:
I will state this again as I've stated before. The reason that CWM will not boot is because the bootloader is locked down. It is not as simple as replacing it. That would take months if not years of work to get a working bootloader replacement. Trust me on this, I know what I'm talking about. I have actually gone through the bootloader code, and it's not fun.

Remember, the Sprint and Public Mobile Rise had a loophole in the bootloader that allowed the images to be booted temporarily. If it was as simple as just 'gaining ownership' that would be great. However, if you actually took the time to back up what you are saying, you'd see how wrong you are.

If you want to test out that the cwm images are actually being written properly, all you need to do is use md5sum. Follow the instructions to flash the cwm image using dd, and then use md5sum on the partition and the original file, and you will see that they are the same. If you use md5sum on the partition before you write it, they will be different. This will be persistent across reboots. Also, if you were to do this, and not put your stock recovery image back, you would no longer have access to recovery since the bootloader is preventing the cwm from booting because it fails the security check.

On the issue of not having full root, what are you not able to do? I know for a fact that I was able to everything I ever wanted. Of course, I actually spent quite a bit of time finding the Superuser.apk and su binary that worked best for the phone ;)
Click to expand...

100% accurate

I have personally booted CWM recovery on the C5156... it has fastboot access... if I flash the image it results in the phone just rebooting when booting into recovery... if I boot the image it will boot in simulation but for a very limited time(30 seconds top)... so basically there are two locks that we know of, a signature check on two levels. One at initialization and one afterwards... the bootloader being compiled from scratch is probably the only thing that would get custom recovery on the rise but will require a team of highly trained dev ninjas that use to work for Kyocera and have months of free time to devote to unlocking the Kyocera flagship android phone.... but this is not the Kyocera flagship android phone and there are no ex Kyocera dev ninjas and they don't have months of time to waste... it's a harsh reality
 
smartmanvartan said:
100% accurate

I have personally booted CWM recovery on the C5156... it has fastboot access... if I flash the image it results in the phone just rebooting when booting into recovery... if I boot the image it will boot in simulation but for a very limited time(30 seconds top)... so basically there are two locks that we know of, a signature check on two levels. One at initialization and one afterwards... the bootloader being compiled from scratch is probably the only thing that would get custom recovery on the rise but will require a team of highly trained dev ninjas that use to work for Kyocera and have months of free time to devote to unlocking the Kyocera flagship android phone.... but this is not the Kyocera flagship android phone and there are no ex Kyocera dev ninjas and they don't have months of time to waste... it's a harsh reality
Click to expand...
I actually fixed the issue with it rebooting. It had to deal with it missing the remount bit in the init.rc. :P

Regardless, it still wassn't any help with getting it permanent lol
 
Hey everyone, I'm new here. I read through the first few pages (about 200 posts) before I realized that this thread has nearly 1000 posts in it, so I skipped to the last page to read some of the summaries people have posted and where everyone is currently at (Thanks to everyone who has posted.)

I'm a Network/Telecommunications Engineer by trade, and I'm working on developing some software/hardware... so I'm a bit out of my box here as far as competency is concerned. I'm looking to toy with this phone to get a 'proof of concept' shown for my project.

I see that there are root options for this phone stock, which I'll do first thing. It sounds like the security on this phone makes it pretty much impossible to alter the bootstrapper or android ROM on the device (might be wrong terminology) as they check against each other to ensure there have been no modifications. It seems like without input from the manufacturer, this will probably never be resolved.

Still - add me to the list of people who are willing to do crazy things to this phone to try and get this figured out. Being able to throw on a custom ROM on this thing would be epic.
 
i see this thread is dead. and i dont blame it. due to the locks on here its a wonder why no one wants these devices. kyocera is pricing these devices as low as possible. but it seems that no one wants these kyocera devices. oh well it was fun while it lasted.
 
Wow. Almost 2 years and 900 posts later, and the thread is finally dead. Well, if anyone works on it independently, keep us posted! I still don't understand why Kyocera is putting such heavy security on such a crappy phone. But either way guys, it's time to move on :shakehands:
 
cooldudezach said:
I will state this again as I've stated before. The reason that CWM will not boot is because the bootloader is locked down. It is not as simple as replacing it. That would take months if not years of work to get a working bootloader replacement. Trust me on this, I know what I'm talking about. I have actually gone through the bootloader code, and it's not fun.
Click to expand...

yeah its a shame too. i bought my first (and only) kyocera phone, a kyocera torque. the noobie that i was figured it would be fairly easy for someone to get cwm up and running on it. a year later and nothing materialized. so i searched and searched for the reason. it was a little puzzling at first. the torque was a decent phone for its main purpose (being waterproof and shockproof etc) and i had seen far lesser phones getting cwm.

well i came to the slow realization/discovery of what you wrote above. and that basically kyocera just sucks as a company, and its no wonder they hardly sell any phones. what makes matters worse is how they are too lazy to update their phones. whatever version of android originally comes with it, that is what it will be. the torque got a few minor updates. they could easily update some of their year old devices to kitkat but they choose not to.

i honestly don't know how a company such as kyocera doesn't go bankrupt due to such backward, archaic business practices.
 
they are basically apple in android. too bad. im done with them and all. i emailed them and they kept giving the same bs saying they dont want to breach contract. they are the ones in charge of their phones, not the carrier. they are scared of them. well they are cowards and dont even deserve to be a company. they should go back to selling printers and silverware. they dont deserve to even have phones period
 
mel4787 said:
they are basically apple in android. too bad. im done with them and all. i emailed them and they kept giving the same bs saying they dont want to breach contract. they are the ones in charge of their phones, not the carrier. they are scared of them. well they are cowards and dont even deserve to be a company. they should go back to selling printers and silverware. they dont deserve to even have phones period
Click to expand...

You clearly don't understand how building and selling phones works.
 
mel4787 said:
i do understand but to me they should at least update the phones at least once to a new os version. but hey its them. we cant get what we want. oh well.
Click to expand...

You aren't their customer- the phone company is. They sign off on contracts for specific items and specific features.

Same for any other company. HTC signs contracts, for example, for the m8vzw, m8att, m8tmo, etc. Those are sold under contract, with agreement terms, to those companies. If they violate them, they are open to legal repercussions. ON the other hand, they can sell the unlocked m8 however they like, as well as the developer edition. The GPE has to be sold according to their contracts with Google. In the case of some phones, there is no unbraned version, so they only sell them via the carrier. And that's when you get phones like the Rise.
 
i understand that part completely. but with htc many complained to them on the bootloaders and sure enough they were unlocked by their website. but its the recovery that most ppl want on this phone. thats why many ppl complained to kyocera on it. and they dont comply. these phones should be at least on jelly bean. but it isnt. and the carrier dont really update the phones. not all ppl have money to be wasting on a phone to have the latest version. thats why root is here in the first place and why recovery exists. and without that and something goes wrong either user error or manufacturer error then the phone is done.
 
mel4787 said:
i understand that part completely. but with htc many complained to them on the bootloaders and sure enough they were unlocked by their website. but its the recovery that most ppl want on this phone. thats why many ppl complained to kyocera on it. and they dont comply. these phones should be at least on jelly bean. but it isnt. and the carrier dont really update the phones. not all ppl have money to be wasting on a phone to have the latest version. thats why root is here in the first place and why recovery exists. and without that and something goes wrong either user error or manufacturer error then the phone is done.
Click to expand...

I hear you, but we should be glad that most Android phones can even be at least rooted at all. I can understand it from the companies' standpoint; they need to make a decent profit on their sales or else they wouldn't bother making the investment to build these phones. That's simply how it rolls. That's not to say the phone/device companies don't want to take risks. It's just that they put plenty of time and effort onto whatever they design and build.

Also, you have to remember that the majority of phone users actually don't care or want to alter their devices beyond stock form. They just want their phones to work well without spending a lot of time tweaking them. We who love to root are in the minority, though a lot of users are aware that such solutions exist. Device hacking isn't for everyone.
 
I understand that. Well I hope this phone can be cracked. Has anyone took the time to see what the kernel checks and has someone built a custom kernel to flash
 
I tried to root this new kyrocera and now it just powers uo the logo over and over. Can someone help me turn the phone on or tell me how to fix the phone??? . Can we get it working????
 
El Presidente said:
There's no point in a custom kernel without an unlocked bootloader so I'm not entirely sure what that would achieve.
Click to expand...

what im saying is since there is a kernel source on kyoceras website is there a way to decompile everything with it and see what files the kernel checks. ik it checks the whole phone and its in there where it checks the bootloader. like i said in an earlier post the bootloader can be unlocked but the kernel sees this and bricks the phone. so if we can decipher the kernel source and see what checks it is using is it possible to disable those checks that is being done. i would do that but my current rise is bricked due to the kernel.
 
mel4787 said:
what im saying is since there is a kernel source on kyoceras website is there a way to decompile everything with it and see what files the kernel checks. ik it checks the whole phone and its in there where it checks the bootloader. like i said in an earlier post the bootloader can be unlocked but the kernel sees this and bricks the phone. so if we can decipher the kernel source and see what checks it is using is it possible to disable those checks that is being done. i would do that but my current rise is bricked due to the kernel.
Click to expand...

You have the food chain totally backwards.

The bootloader, if it passes its own integrity checks, vectors to the boot image where the kernel lives.

You break the bootloader, you're done.





jonhperrin said:
I tried to root this new kyrocera and now it just powers uo the logo over and over. Can someone help me turn the phone on or tell me how to fix the phone??? . Can we get it working????
Click to expand...

Let's get you moved to your own thread.

I take it you replaced your Hydro with this one?
 
ahh i understand now. thanks for clarifying that and updating me on that. ive exhausted everything i could think of. why would kyocera put up a kernel source if we could not use it
 
mel4787 said:
i see. but the kernel is useless to us. nothing can be done to unlock it at all the security that is
Click to expand...

The kernel is probably the last thing you care about.

It ties hardware to software - it's why software can make a phone call, so it's not worthless. Neither is it worthless to have Kyocera respect copyright laws.

The kernel is not locked.

You're getting hypnotized by a kernel fixation.

The bootloader is locked, it's prevented getting a custom recovery like CWM.

That's preventing all sorts of other things.

The least of which is kernel tinkering.
 
i see. thanks again. also the bootloader has been unlocked, but it bricks the moment you turn it off. so idk what to do on that one. and the security sheesh thats for another day
 
mel4787 said:
i see. thanks again. also the bootloader has been unlocked, but it bricks the moment you turn it off. so idk what to do on that one. and the security sheesh thats for another day
Click to expand...

So the bootloader has had a crack pushed open, whether it's been unlocked is a matter of semantics for the devs at this point, imo.

The security issue is really the whole day here. ;) :)

It's the bootloader that decides if it's OK to run the kernel.

Integrity checks, security, whatever, there is only one sky.
 
You must log in or register to reply here.
Back
Top Bottom