• 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

I tried to find a changelog, but I couldn't find any. There should be one explaining what the update changes, like any software.
 
continue to look. i probably dont wanna update unless its to help either speed the phone up or the bootloader unlocking. anything else im not gonna do it.
 
Alternity said:
I tried to find a changelog, but I couldn't find any. There should be one explaining what the update changes, like any software.
Click to expand...

The update is likely a blob, and the updater expects your /system to look a certain way to apply said blob. A binary diff basically. You will not find a changelog in the update, frankly I don't even know why you'd bother looking beyond a cursory glance. Also I seem to recall something about the blob being encrypted with Kyocera's keys or something, it'd be earlier in this thread.

The only way to see what gets changed will be to have an image of an unmodified Rise and an image of an updated Rise, and compare the contents of the two images.

But is this low-end phone really worth that effort? Well, maybe, the hardware isn't that bad but it's still pretty low-end.
 
glad i am not gonna update. it looks more to me that kyocera is still trying to block root access and bootloader. they will fall off the market soon enough
 
db2 said:
The update is likely a blob, and the updater expects your /system to look a certain way to apply said blob. A binary diff basically. You will not find a changelog in the update, frankly I don't even know why you'd bother looking beyond a cursory glance. Also I seem to recall something about the blob being encrypted with Kyocera's keys or something, it'd be earlier in this thread.

The only way to see what gets changed will be to have an image of an unmodified Rise and an image of an updated Rise, and compare the contents of the two images.

But is this low-end phone really worth that effort? Well, maybe, the hardware isn't that bad but it's still pretty low-end.
Click to expand...

I think you misunderstood here. I wasn't looking IN the update for the changelog, but on the net, Kyocera's website, etc. Everything I own that has a software/firmware that can be updated, gives that information to their customers, Video game consoles, Windows, etc.

Low-end or not, it doesn't matter, I don't see your point, sorry.

For what it's worth I found this but they didn't updated it for that last update : http://support.sprint.com/support/a...dAndUpdateTheSoftwareVersionOnYourKyoceraRise

Haven't found anything for the PM Rise though.

They seem to not say everything about the update, it seems way too few information. Isn't there a law on this or something? Customers has the right to know the details.
 
Your'e right, I misunderstood what you were doing. I stand by the rest though, it's not like these things are Galaxy-quality just with craptastic software. They're plastic throwaways with craptastic software.

Alternity said:
Isn't there a law on this or something? Customers has the right to know the details.
Click to expand...

Well, like Kyocera said we're not the customer. Sprint/VM/PM are. So it'd be up to them to publish changelogs or not. Since they're not making the software changes directly they probably justify not doing so that way. Try contacting a carrier or three to ask I'd say.
 
kman9637 said:
And how are we supposed to do that? The only way to even access the file is through the kyocera updater
Click to expand...

It has to exist on the phone filesystem SOMEWHERE before the updater installs it, or maybe in one of those odd partitions. These things don't have nearly enough RAM to hold an update in memory.

Someone should let the updater do its download thing and when the confirmation thing shows up ADB in and dd every partition to their sdcard and compare to a previous image set. I would just for kicks but I managed to put my Rise in to a state where it never gets past the bootlogo animation by doing a factory reset. (and now is when I repeat these things are throwaways)
 
is there a way we can wipe the system, build the os from scratch, completely wipe the firmware and replace the firmware with something fresh? completely without the security that kyocera put on here? is there a way we can flash a stocklike rom with tweaks and modifications and we can just build our devices the way we want? i ask this because most ppl want a performance tweak or speed boost on the phones. is there a way we can build that without harming the system?
 
cooldudezach said:
Here's a question: Would we be able to use the solution in this link to disable the security check?

Azimuth Security: Exploiting Samsung Galaxy S4 Secure Boot

I might pick up some reverse engineering skills if I have to to find the memory addresses, if need be.
Click to expand...

I have looked into that. Its essentially "How Loki exploit works". I have searched the bootloader for the check_sigs() function. Its not there. If you need a second opinion, I have it already. djrbliss (creator of loki) has looked into this also. Basically loki wont work for us. I am trying to come up with a separate exploit and work off of that.

If you look at the post, it says "posted by Dan Rosenberg @ 5/23/2013 10:36:00 AM "
Dan Rosenberg is djrbliss's real name. I contacted him thru irc. I dont have the logs but when I say some REALLY good devs were helping with the hydro/rise in the background, they have. Its just nothing has come to light yet.
 
rbheromax said:
I have looked into that. Its essentially "How Loki exploit works". I have searched the bootloader for the check_sigs() function. Its not there. If you need a second opinion, I have it already. djrbliss (creator of loki) has looked into this also. Basically loki wont work for us. I am trying to come up with a separate exploit and work off of that.

If you look at the post, it says "posted by Dan Rosenberg @ 5/23/2013 10:36:00 AM "
Dan Rosenberg is djrbliss's real name. I contacted him thru irc. I dont have the logs but when I say some REALLY good devs were helping with the hydro/rise in the background, they have. Its just nothing has come to light yet.
Click to expand...

what other exploits have you looked into? is there a way to hijack our security software within the phone's FW and wipe it from the phone? has there been an exploit doing that on other phones? is there a way we can kill the security and wipe it from our phones?
 
I have been an uduor and not properly look for the check sigs function, apparently there's this app that will help me find it. I was lookimg by using a hex editor. That was wrong. I havrnt foumd any other possible exploit yet and as for removung it completely that is impossible at the moment as it would require a bootloader rewrite.
 
rbheromax said:
I have been an uduor and not properly look for the check sigs function, apparently there's this app that will help me find it. I was lookimg by using a hex editor. That was wrong. I havrnt foumd any other possible exploit yet and as for removung it completely that is impossible at the moment as it would require a bootloader rewrite.
Click to expand...

hmm well we cant rewrite the bootloader until it gets unlocked. why not go a different way with this, instead of the bootloader why dont we zero in on the security somehow and try to exploit not the bootloader but the security itself. hasnt there been other phones with tight security and they were unlocked through the security? maybe the check sig function is located in there instead of the bootloader/FW
 
Well, I've finally given up. I've put too much effort and too many resources with minimal return. I'll keep an eye out on this thread in case it happens to have some success. I picked up a ZTE Awe on black friday (can't beat $20!). Guess what? Damn thing has an unlocked bootloader out of the box. Already have CWM working on it (First one to build it! YEAH!), and I'm working on CM. If you want to jump ship with me, feel free. It was nice knowing y'all.

./jump_overboard.sh
 
well with this phone ive customised it but yeah. we cant do anything with the phones. due to it being a signed bootloader we cant do much with that. its because of kyocera thinking we are babies why they dont comply with us. i would send a hate letter to them but they wont respond
 
Well, I made one last effort to contact Kyocera and Virgin Mobile. Here is the message I sent them. I will let you guys know what they respond with.

To whom it may concern:
I would like to make it known that there is a large community who uses the Rise and its sister phones, the Event and the Hydro. Many of the users of these phones wish to be able to have the ability to have a recovery that is able to make backups of the phone's data in case something happens to it.

As it stands right now, that is impossible. All three models have a locked bootloader which makes it impossible to install a custom recovery to make crucial backups of the phone. Most other device manufacturers offer the ability to unlock the device bootloader so that their users are able to install the custom recovery. For example: HTC. Some manufacturers do not even lock their bootloaders. For example: ZTE.

Without being able to install the custom recovery, the users of these phones are getting irritated and upset. As a result, they are switching their phones and leaving Kyocera behind. Kyocera makes great devices, and it is a waste to leave them because the bootloaders are locked down, but it remains the only choice.

Another option would be to remove just the security check that is in the bootloader that prevents the custom recovery from properly installing. The bootloader could stay locked down, while still enabling users to install a custom recovery and make crucial backups of their phone. This will protect both the manufacturer and the carrier, as it prevents the device from being able to change carriers.

We in the Kyocera community need the ability to install custom recovery, and it is only possible from Kyocera. The bootloader does not have to be in an unlocked state, the security check is all that needs to be removed to install the recovery. This prevents devices from changing carriers, as that requires an unlocked bootloader. Since the bootloader would still be locked, it is not an issue.

Thanks for your time,
Zacharry
Click to expand...
 
cooldudezach said:
Well, I made one last effort to contact Kyocera and Virgin Mobile. Here is the message I sent them. I will let you guys know what they respond with.
Click to expand...

i like it. i sent a similar message like that. hopefully we get something headway with this. we really need that completely. idc if the bootloader is locked as long as we can get cwm on this phone then id be happy.
 
Has anyone looked into bootstrapping the recovery? Like the Moto DX of old and the Thor/Loki recoveries on current Samsung devices?
 
starkraving said:
Has anyone looked into bootstrapping the recovery? Like the Moto DX of old and the Thor/Loki recoveries on current Samsung devices?
Click to expand...

we have but loki looks for a signature checking function and the phone doesnt have it and thor is new to me. it could be of use but we may find out with it.
 
another run around. they sent me this:

Thank you for contacting Kyocera Communications Inc. This message is in response to your email regarding the inconvenience that you are having with your Kyocera C5155 phone.

We appreciate the opportunity to assist you. Like we have stated on previous occasions, your request as well as the many other that we receive every week are forwarded to the corporate office for their consideration. If there comes the day that Kyocera Communication decides to Unlock the Bootloader on the lineup of devices, you will be the first to be notified.

i dont even think that they even care for us at all. guess i may have to move on from this device. talk about a waste of money with this device
 
  • Like
Reactions: db2
If you decide to move on but for what ever reason want a shitty VM phone then the OE is the way to go..
 
well i wouldnt move on if cwm can be put on this phone. ill stay and hopefully see cwm be ported on this phone
 
i took a look at the default.prop in my phone and compared it to another phone. it seems that,

galaxy precedent ro.secure=0
optimus s ro.secure=0
kyocera rise ro.secure=1

would the rises ro.secure=0 be overwritten to be ro.secure=1 if we rebooted it with it being 0? im asking this due to the others have it at 0. and it might be this that prevents some things from being booted up on. meaning it could prevent us from unlocking it. so if this value is changed would we be able to bypass the checks that the phone performs? or will it brick the phone?
 
You must log in or register to reply here.
Back
Top Bottom