• 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

Could we potentially unlock the bootloader the same way Nexus device's bootloaders are unlocked, since are Android is pretty much vanilla? (fastboot oem unlock or something like that)
 
And here's a log of me booting into recovery
0 /tmp ramdisk (null) (null) 0
1 /sys_boot vfat /dev/block/mmcblk0p1 (null) 0
2 /boot emmc /dev/block/mmcblk0p8 (null) 0
3 /cache ext4 /dev/block/mmcblk0p13 (null) 0
4 /data ext4 /dev/block/mmcblk0p20 (null) 0
5 /recovery emmc /dev/block/mmcblk0p15 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
7 /system ext4 /dev/block/mmcblk0p12 (null) 0
8 /sysprop ext4 /dev/block/mmcblk0p17 (null) 0
9 /carrier ext4 /dev/block/mmcblk0p18 (null) 0

E:Cannot load volume /misc!
E:Cannot load volume /misc!
I:fopen_path 1 /data/fota/ipth-muc.prop
I:fopen_path 2 /data/fota/ipth-muc.prop
I:fopen_path 3 /data/fota/ipth-muc.prop
I:Failed to open /data/fota/ipth-muc.prop, use default pkg location:/cache/fota
I:Delta package does not exist /cache/fota/ipth_package.bin
Command: "/sbin/recovery"

ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
ro.build.id=IML77
ro.build.display.id=IML77
ro.build.version.incremental=release.20120629.183038
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Fri Jun 29 18:31:08 JST 2012
ro.build.date.utc=1340962268
ro.build.type=user
ro.build.user=release
ro.build.host=release
ro.build.tags=release-keys
ro.product.model=C5155
ro.product.brand=kyocera
ro.product.name=C5155
ro.product.device=C5155
ro.product.board=C5155
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=kyocera
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7630_surf
ro.build.product=C5155
ro.build.description=C5155-user 4.0.4 IML77 release.20120629.183038 release-keys
ro.build.fingerprint=kyocera/C5155/C5155:4.0.4/IML77/release.20120629.183038:user/release-keys
ro.build.characteristics=default
ro.build.internalswversion=1.000VM.05.a
ro.build.swversion=1.000VM
rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV
DEVICE_PROVISIONED=1
debug.sf.hw=1
dalvik.vm.heapsize=128m
dev.pm.dyn_samplingrate=1
persist.cne.UseCne=vendor
persist.cne.UseSwim=false
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
persist.cne.sync.swim.mode=false
lpa.decode=true
ro.hdmi.enable=true
ro.use_data_netmgrd=true
ro.emmc.sdcard.partition=16
ro.config.ehrpd=false
media.stagefright.enable-player=true
media.stagefright.enable-meta=false
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
lpa.use-stagefright=true
ro.opengles.version=131072
ro.qualcomm.bluetooth.dun=false
ro.bluetooth.remote.autoconnect=true
persist.sys.strictmode.visual=false
ro.multi.rild=false
ro.qualcomm.bluetooth.ftp=false
ro.bluetooth.request.master=true
ro.screen.layout=normal
debug.camcorder.disablemeta=0
persist.fuse_sdcard=false
debug.enabletr=false
debug.camera.landscape=true
ro.max.fling_velocity=4000
windowsmgr.max_events_per_sec=60
ro.com.google.clientidbase=android-kyocera
ro.com.google.clientidbase.ms=android-virgin-us
ro.com.google.clientidbase.yt=android-virgin-us
ro.com.google.clientidbase.am=android-virgin-us
ro.com.google.clientidbase.gmm=android-kyocera
ro.cdma.home.operator.alpha=Virgin Mobile
ro.cdma.home.operator.numeric=311490
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=36m
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=CurveBall.ogg
ro.config.notification_sound=DontPanic.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.vendor.extension_library=/system/lib/libqc-opt.so
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=4.0_r2
drm.service.enable=true
ro.camera.sound.forced=1
drm.service.enabled=true
persist.sys.ringermode=2
persist.timed.enable=true
persist.sys.language=en
persist.sys.country=US
browser.management=false
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=8e1f40
ro.mtp.serialno=a0000027b13cef
ro.bootmode=unknown
ro.baseband=msm
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=qcom
ro.revision=0
ro.emmc=1
init.svc.recovery=running
init.svc.rmt_storage=running

E:Cannot load volume /misc!
 
To the op, I plan on working on this for the hydro, which is pretty similar specs. We need to get kyocera to unlock the bootloader.
As a group, we will need to repeatedly email them.
As for cwm, as soon as my hydro arrives I will start on it.

Fair warning, another well known developer was working on the hydro when it first came out, and ended up bricking it because of the secure boot and recovery. And he had ported cwm for the prevail and zte warp.
So lets get on kyocera, HTC has an unlock on their developer site, kyocera should also with persuasion.
 
downthemachine said:
So lets get on kyocera, HTC has an unlock on their developer site, kyocera should also with persuasion.
Click to expand...

This is partially true, while the htcdev site unlocks the bootloader to allow rom installs the bootloader still retains the s-on flag which will only allow signed radios and kernels to be flashed through recovery. Also some carriers (AT&T) :mad: force HTC to remove the meid's from the database so that you can't even use the partial bootloader unlock. :banghead:
 
OverByter said:
This is partially true, while the htcdev site unlocks the bootloader to allow rom installs the bootloader still retains the s-on flag which will only allow signed radios and kernels to be flashed through recovery. Also some carriers (AT&T) :mad: force HTC to remove the meid's from the database so that you can't even use the partial bootloader unlock. :banghead:
Click to expand...

Buckets of fun :D

Well I'm new to the locked bootloader stuff. I'm sure there is a way around it. We just have to find it :mad:
 
downthemachine said:
To the op, I plan on working on this for the hydro, which is pretty similar specs. We need to get kyocera to unlock the bootloader.
As a group, we will need to repeatedly email them.
As for cwm, as soon as my hydro arrives I will start on it.

Fair warning, another well known developer was working on the hydro when it first came out, and ended up bricking it because of the secure boot and recovery. And he had ported cwm for the prevail and zte warp.
So lets get on kyocera, HTC has an unlock on their developer site, kyocera should also with persuasion.
Click to expand...

I don't know much how the recovery stuff works, but would something similar to how the bootstrap recovery works, work for us? It basically enables limited recovery on a bootloader locked device.

I don't see links to them, I'll upload the System.img, Recovery.img and Boot.img files so folks have them. I backed them up immediately after rooting and without doing anything else. Of course, the Recovery.img file is the only one of use, because if you kill the other two, theres not really any way to put them back. What I also found odd is that the stock recovery only has wipe data, wipe cache and reboot. There's not even the option of installing a signed update file. It seems that kyocera put this out as a throwaway phone for Virgin Mobile and doubtful they'll make any attempts to update anything (are there any non-throwaway phones by kyocera?). Since there are no updates available for my device, I haven't even been able to see how an update gets applied. Maybe theres something there to look at (if anyone has an updatable phone) to see how that gets applied and hijack it. Unlike the major android developers, I don't have confidence that kyocera has really locked anything down with any sincere effort, so maybe theres an option.
 
Alastor10009 said:
Even if we do unlock and add cwm we don't have any flashable roms :/
Click to expand...

Can't really make roms until we have a working CWM. Once CWM is available, people can start customizing the stock rom and maybe one day create ports from other devices (although unlikely due to this being a low activity device).
 
AndroidHaCks said:
I thought thne same thing about the no option to flash anything in recovery.. but then again the rise did get updated from 4.0.3 to 4.04
Click to expand...

Do you know how the update happened? Did it download a file? What file? Did it reboot to recovery and flash the file? or did it just do it inside the OS? I'm wondering if someone could trigger the update but not flash it, maybe we can get the update file and path for some clue into how updates occur.
 
ngtwolf said:
I don't know much how the recovery stuff works, but would something similar to how the bootstrap recovery works, work for us? It basically enables limited recovery on a bootloader locked device.

I don't see links to them, I'll upload the System.img, Recovery.img and Boot.img files so folks have them. I backed them up immediately after rooting and without doing anything else. Of course, the Recovery.img file is the only one of use, because if you kill the other two, theres not really any way to put them back. What I also found odd is that the stock recovery only has wipe data, wipe cache and reboot. There's not even the option of installing a signed update file. It seems that kyocera put this out as a throwaway phone for Virgin Mobile and doubtful they'll make any attempts to update anything (are there any non-throwaway phones by kyocera?). Since there are no updates available for my device, I haven't even been able to see how an update gets applied. Maybe theres something there to look at (if anyone has an updatable phone) to see how that gets applied and hijack it. Unlike the major android developers, I don't have confidence that kyocera has really locked anything down with any sincere effort, so maybe theres an option.
Click to expand...

Just because the option isn't there it can still flash ota updates.
 
If anyone comes across anything, no matter what your skill level, post a link. I only get a couple of hours a day to so research.
 
I'll make sure to look around. We need CWM to get a Custom Kernel! If we could just overclock this phone to 1.2-1.3 GHz, it'd be a beast (to me)
 
Well if we can get the bootloader unlocked and build cwm, I will make an oc kernel. The source is similar to the warp sequent.
 
My conversation with Live chat at Kyocera Tech support. Also sent emails to Sales and Support.

Code: 
[B]Ron R:[/B] Thank you for contacting Kyocera technical support.
How may I help you today?
 
[B]Ron R:[/B] For documentation purposes, may I please have your
full name and your phone number first?
 
[B]You:[/B] *********************
 
[LEFT][B]Ron R:[/B] Thanks. How may I help you today?[/LEFT]
 
[LEFT][B]You:[/B] Hello[/LEFT]
 
[LEFT][B]You:[/B] I'm contacting you to see if the bootloader on the Rise 
will ever be unlocked?[/LEFT]
 
[LEFT][B]You:[/B] It would be great to unlock the bootloader on the
Rise. This could be a great selling phone if the Developement
could continue. The kernel source was released (very nice),
but with the locked down bootloader it is killing it.
Its not Virgin Mobile locking down the bootloader it is
Kyocera's choice. All the other Android suppliers are
releasing ways to unlock there devices, as they see
the potential of android developement to increase sales
of a particular phone (see HTC). Please pass this along
and allow developement on the Rise and its sister phones.
Thanks for your time.[/LEFT]
 
[LEFT][B]Ron R:[/B] Thank you. We have customers who also wanted
to unlock the programming of the phone. The only thing
is that if we try to, for example, root or unlock the software,
that will automatically void the warranty with Virgin Mobile.
For Kyocera phones, for example, the Kyocera/Sanyo Zio,
you just need to press the up and down volume buttons
together with the power button to enter download mode.
For the Kyocera Rise, we actually locked the bootloader. If
you press and hold the up and down volume buttons and the
power button, you will enter safe mode.[/LEFT]
 
[LEFT][B]You:[/B] I dont think we are concerned about voiding our warranties.
Will entering safe mode help in unnlocking the bootloader?

Ron R: As a troubleshooter I am actually not sure about it.
But you can always try if that will work. Just press and hold
the up and down volume buttons together with the power
button to enter safe mode.[/LEFT]
 
[LEFT][B]You:[/B] what is "safe" mode. Is the Zio's bootloader unlocked?[/LEFT]
 
[LEFT][B]You:[/B] is safe mode the stock recovery console?[/LEFT]
 
[LEFT][B]Ron R:[/B] Let me check my resources here. Hold on please.[/LEFT]
 
[LEFT][B]Ron R:[/B] Thank you for waiting. The purpose of Safe Mode is
for the system to remain unharmed if you are planning to
run/install apps that may harm the system. Yes, the bootloader
for the Zio is unlocked.[/LEFT]
 
[LEFT][B]You:[/B] Thank you.[/LEFT]
 
[LEFT][B]You:[/B] One last thing. I'm hoping you could pass it along to
whoever, that there is a growing number of people that are
trying to get the bootloader to be unlocked by Kyocera.
Were hoping that enough of a push, kinda like what happened
with HTC, will get them to release an unlock procedure.
I bet is unlocked sales would get a good boost.[/LEFT]
 
[LEFT][B]You:[/B] I do appreciate the information, Sir.[/LEFT]
 
[LEFT][B]Ron R:[/B] Yes. We are already aware of that. We already
escalated this case to our corporate office. You're welcome.
Here is your reference number: *****. Is there anything else
for today?[/LEFT]
 
[LEFT][B]You:[/B] That is all. Have a great day.[/LEFT]
 
I also emailed them and they said it would be breaking their agreement with Virgin Mobile. But i think they thought i was talking about carrier unlocking it, so i emailed them again and further explained
 
Well, you should also include that you understand that this will void warranty.
 
AndroidHaCks said:
I also emailed them and they said it would be breaking their agreement with Virgin Mobile. But i think they thought i was talking about carrier unlocking it, so i emailed them again and further explained
Click to expand...

The sad part is that you're probably right about the rep being confused , Virgin doesn't care about root, I've been on the phone numerous times with tier 1 and I told them that I was rooted, I've returned about 10 phones for warranty without un rooting before hand. Customer service reps are usually clueless without their script because if Virgin really cared about unlocked bootloaders they would have forced htcdev not to provide the unlocking tools like AT&T did last year. Another reason for his lack of knowledge is that there's no such thing as a carrier unlocked CDMA phone which is what Virgin uses. Only GSM phones can be carrier unlocked because they have sim cards instead.
 
sneaky_1 said:
I thought we knowingly void the warranties when we root and so on. Hmm.
Click to expand...

If your rooting efforts cause you to brick the phone that's one thing but if the power button or touchscreen stops working on my rooted device then they are not related and my warranty would still apply.
 
You must log in or register to reply here.
Back
Top Bottom