• 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

got in contact with kyocera again and unfortunately this is what they said, "Thank you for contacting Kyocera Communications Inc. This email message is in regards your request to unlock the bootloader.

At this time we are sad to inform you that there are no plans from Kyocera Corporation to unlock the bootloader of any Kyocera devices.

And Just to let you know, the decision to lock the bootloader on our devices is not to cause discomfort to our customers, on the contrary is to avoid any harm to your device. Although Android its an open source Operating System, we want you to stick to the Android OS version specifically designed for the device since this is the version that has been fully tested and approved by Kyocera Corporation and the service provider as well.

In regards of your phone receiving the latest updates, you would have to get in touch with your service provider since they are the ones that push the updates Over The Air."

what can we do to get them to unlock the bootloader?
 
mel4787 said:
got in contact with kyocera again and unfortunately this is what they said, "Thank you for contacting Kyocera Communications Inc. This email message is in regards your request to unlock the bootloader.

At this time we are sad to inform you that there are no plans from Kyocera Corporation to unlock the bootloader of any Kyocera devices.

And Just to let you know, the decision to lock the bootloader on our devices is not to cause discomfort to our customers, on the contrary is to avoid any harm to your device. Although Android its an open source Operating System, we want you to stick to the Android OS version specifically designed for the device since this is the version that has been fully tested and approved by Kyocera Corporation and the service provider as well.

In regards of your phone receiving the latest updates, you would have to get in touch with your service provider since they are the ones that push the updates Over The Air."

what can we do to get them to unlock the bootloader?
Click to expand...

at least they didnt give you the standard "let me tell you something most people dont know" message
 
true. well the only way for us to get the bootloader unlocked is a stretch. we may have to show kyocera what a custom rom can do. we may have to show them a pic or video to them on what these devices can do.
 
I have recently contacted Kyocera and Virgin Mobile via phone and via email. Virgin Mobile told me that Kyocera Will contact me with in 24-72 hours about the bootloader being unlocked.
 
well due to our recovery and all its highly unlikely. if there were an update.zip in the stock it could be possible since all we would need to do is flash a firmware on this device. in other words the only way would be finding a way to get it to fastboot which we cant do.
 
mel4787 said:
well due to our recovery and all its highly unlikely. if there were an update.zip in the stock it could be possible since all we would need to do is flash a firmware on this device. in other words the only way would be finding a way to get it to fastboot which we cant do.
Click to expand...

I have an update.zip file on my computer, but its not on my phone.
 
is it for this phone specifically. if so good. but still a problem is our recovery is stripped down. there isnt an update.zip option in the recovery for us to get into. kyocera didnt include this in the recovery.
 
i am beginning to hate kyocera even more now. heres what they sent me,

(Dear Melvin Stevenson,

Thank you for contacting Kyocera Communications Inc. This email message is in regards of your inquiry.

It is a pleasure for me to answer your questions once again Melvin.

Like I have explained to you in previous e-mails. Kyocera has no plans to unlock the bootloader or to enable fastboot in the device lineup. Should something go wrong with an update that leaves you device unusable, our devices come with a one year limited warranty and you should contact your point of purchase or service provider for warranty assistance.

I understand that you are an advanced user, but Kyocera Communications base their decisions taking in consideration the majority of the users, and the majority of Kyocera users are basic user and user that just upgraded from a feature phone to a smart phone.

Once again we apologize for any inconvenience and appreciate that you are enjoying your Kyocera device.)

sigh i hate the fact that they are stubborn on this. honestly we have no choice but to show kyocera what other phones can do on a custom rom firmware. they are thinking like apple and its pissing me off to the max. like these are androids for development purposes. why cant they see it from our point of view. its like they want to lose our services. they wont yield to me on this at all. and its sickening me.
 
Its their product, their choice, ultimately. I don't like their choice, but they do have the right to say "No." if htey want to. I doubt showing htem custom ROMs will change their mind.
 
In a nut shell here is the problem...

Kyocera makes the device.

Various Carriers use different Kyocera phones.

The carriers requested to have the phone assigned to its own service. Which prevents anyone from switching Kyocera phones to other networks.

In return Kyocera developed code to provide each carrier. The code prevents any changes to the kernel and bootloader.

If certain criteria is triggered the phone reboots into factory default. When it cannot reboot properly you get a bootloop or black screen.

The carriers then assigns encrypted keys to prevent access to bootloader/fastboot.

Now the keys are stored on the Carriers server-side and the key is assigned when you activate the device.

Carriers wont unlock anything for fear of losing the device to another network.

Kyocera wont unlock for fear of losing Carrier support.

The question becomes why not unlock it?

The device can then be modded and unleash the true potential.

The answer is because its a cheap phone they rather have you upgrade to a new device than alter the device.

Seems like we are fighting a battle with no reasonable solution given by Carriers or Kyocera.

I did find a way to add features of some custom roms to the Rise if you are rooted. I will post a small tut when I get a chance.

It is the closes thing to modding the device without changing the bootloader.
 
well they will lose more customers with this. no matter how many phones they make if the phones are locked then no development to those phones and loss of profit. its their loss. they act like apple completely
 
TechDad378 said:
In a nut shell here is the problem...

Kyocera makes the device.

Various Carriers use different Kyocera phones.

The carriers requested to have the phone assigned to its own service. Which prevents anyone from switching Kyocera phones to other networks.

In return Kyocera developed code to provide each carrier. The code prevents any changes to the kernel and bootloader.

If certain criteria is triggered the phone reboots into factory default. When it cannot reboot properly you get a bootloop or black screen.

The carriers then assigns encrypted keys to prevent access to bootloader/fastboot.

Now the keys are stored on the Carriers server-side and the key is assigned when you activate the device.

Carriers wont unlock anything for fear of losing the device to another network.

Kyocera wont unlock for fear of losing Carrier support.

The question becomes why not unlock it?

The device can then be modded and unleash the true potential.

The answer is because its a cheap phone they rather have you upgrade to a new device than alter the device.

Seems like we are fighting a battle with no reasonable solution given by Carriers or Kyocera.

I did find a way to add features of some custom roms to the Rise if you are rooted. I will post a small tut when I get a chance.

It is the closes thing to modding the device without changing the bootloader.
Click to expand...

guess that makes sense. too bad we cant add things like cyanogenmod things to this without cwm. it would have been great for this phone. oh well
 
mel4787 said:
well they will lose more customers with this. no matter how many phones they make if the phones are locked then no development to those phones and loss of profit. its their loss. they act like apple completely
Click to expand...

Most of their customers probably don't care that they can't root/mod it.
 
i see on that now. but to me and other people this phone is being wasted due to a locked bootloader. and besides its not like that virgin mobile cant give is their encryption keys to their bootloader anyway
 
smartmanvartan said:
this is all research. ..its not even on my device yet... just simulation....

IMG_20130118_015756 - Download - 4shared

Still needs work but it's a vision of things to come....

I'm out for the night... i'll see you guys tomorrow :)
Click to expand...

i seen this image and noticed it was booted into fastboot. interesting. i know you dont have this phone anymore abd all but it booted this image it seems. now with the brick that happened it was due to the bootloader. i looked more into our bootloader and noticed there was more than one bootloader it seems. it was compared to a galaxy exibit and the partition table is as shows

Partition Table
/dev/block/mmcblk0p1 secboot2 partition map
/dev/block/mmcblk0p2 dbl.mbn (boot loader)
/dev/block/mmcblk0p3 osbl.mbn (boot loader)
/dev/block/mmcblk0p4 MBR extended partition table
/dev/block/mmcblk0p5 EMMCBOOT.MBN (boot loader, has odin download mode)
/dev/block/mmcblk0p6 amss.mbn
/dev/block/mmcblk0p7 emmcparam.bin
/dev/block/mmcblk0p8 boot.img (linux kernel)
/dev/block/mmcblk0p9 adsp.mbn (baseband)
/dev/block/mmcblk0p10 rmt
/dev/block/mmcblk0p11 rmt
/dev/block/mmcblk0p12 persist.ext4
/dev/block/mmcblk0p13 recovery.img (linux kernel+initrd for recovery mode)
/dev/block/mmcblk0p14 param
/dev/block/mmcblk0p15 system.ext4
/dev/block/mmcblk0p16 cache.ext4
/dev/block/mmcblk0p17 data.ext4
/dev/block/mmcblk0p18 preload.ext4
/dev/block/mmcblk0p19
/dev/block/mmcblk0p20 all 0's
/dev/block/mmcblk0p21 all 0's
/dev/block/mmcblk0p22 all 0's
/dev/block/mmcblk0p23 all 0's
/dev/block/mmcblk0p24 all 0's
/dev/block/mmcblk0p25 all 0's
/dev/block/mmcblk0p26 all 0's
/dev/block/mmcblk0p27 efs (encrypted fs)
/dev/block/mmcblk0p28 /mnt/sdcard

what do you think on this
 
mel4787 said:
i seen this image and noticed it was booted into fastboot. interesting. i know you dont have this phone anymore abd all but it booted this image it seems. now with the brick that happened it was due to the bootloader. i looked more into our bootloader and noticed there was more than one bootloader it seems. it was compared to a galaxy exibit and the partition table is as shows

Partition Table
/dev/block/mmcblk0p1 secboot2 partition map
/dev/block/mmcblk0p2 dbl.mbn (boot loader)
/dev/block/mmcblk0p3 osbl.mbn (boot loader)
/dev/block/mmcblk0p4 MBR extended partition table
/dev/block/mmcblk0p5 EMMCBOOT.MBN (boot loader, has odin download mode)
/dev/block/mmcblk0p6 amss.mbn
/dev/block/mmcblk0p7 emmcparam.bin
/dev/block/mmcblk0p8 boot.img (linux kernel)
/dev/block/mmcblk0p9 adsp.mbn (baseband)
/dev/block/mmcblk0p10 rmt
/dev/block/mmcblk0p11 rmt
/dev/block/mmcblk0p12 persist.ext4
/dev/block/mmcblk0p13 recovery.img (linux kernel+initrd for recovery mode)
/dev/block/mmcblk0p14 param
/dev/block/mmcblk0p15 system.ext4
/dev/block/mmcblk0p16 cache.ext4
/dev/block/mmcblk0p17 data.ext4
/dev/block/mmcblk0p18 preload.ext4
/dev/block/mmcblk0p19
/dev/block/mmcblk0p20 all 0's
/dev/block/mmcblk0p21 all 0's
/dev/block/mmcblk0p22 all 0's
/dev/block/mmcblk0p23 all 0's
/dev/block/mmcblk0p24 all 0's
/dev/block/mmcblk0p25 all 0's
/dev/block/mmcblk0p26 all 0's
/dev/block/mmcblk0p27 efs (encrypted fs)
/dev/block/mmcblk0p28 /mnt/sdcard

what do you think on this
Click to expand...

This is semi-common knowledge at this point. I've mapped out a pretty accurate list of every partition on the device, and even have a copy of TWRP and CWM that both fully boot, and back everything up properly. (I refuse to test restoring it, for obvious reasons. Not that there is a point to doing so, anyway) The only problem, is that only the Sprint and Public Mobile versions of the Rise are able to boot into it because they have a semi-unlocked bootloader.

EDIT:
Here's the link to the post where I'll keep updated partition lists.
http://androidforums.com/rise-all-t...on-kyocera-rise-stock-images.html#post6152366
 
is there a way to trick the device in any way? like flash gordon apk. is there a way to use flash gordon to reinstall stock 4.0.3 firmware on this device and remove (mmcblk0p8, mmcblk0p12, and mmcblk0p15) and replace them with the original found in the rise 4.0.3 version? is it possible to so this?
 
now heres something for everyone,

I looked into this more and I noticed one thing, this build number is not of kyocera’s but of motorolas number for a tablet called Motorola xoom. And to make things more interesting is that its original os is of 4.0.3. but in our device its labeled as 4.0.4. I think Kyocera did this on purpose to make sure we didn’t get the build number or the source for the phone.

One person said on here that Kyocera gave out a broken source. Well it seems to me that their source doesn’t exist at all. The source code is from the motorola xoom. Hence forth the build number of IML77. It’s the same as the xoom. So I think that Kyocera violated something on here. Maybe Motorola or google can do something to them after all. They are violating us of the source code and they say the same thing on not wanting to give us fastboot or something. All android devices I know of have fastboot on them and vm rise doesn’t have fastboot accessed. They probably illegally sent out updates to halt fastboot for us.
 
You should carefully re-read GPL and Android licensing, then- even if htey used the Motorola Source, they only have to give out the source to the original portions of the code concerning the OS- concerning the boot loader, fastboot, drivers, etc., they can lal be closed-source.
 
You must log in or register to reply here.
Back
Top Bottom