Root Porting ClockWorkMod to the Kyocera Rise

[smartmanvartan]

so mmcblk0p19 is the data parttion on the c5156 it is mmcblk0p20 on the c5155 and on the c5170(hydro)... also the display is flipped on the hydro... we're still in this together and we can still help each other out but cwm will have to be built separately on each device...

in did not include the data partiton in my system dump for obvious reasons...
there is only 19 partitions on my phone... not 20...

c5156 - Download - 4shared

 

[smartmanvartan]

I'm especially interested in the sys_boot image. If you can get into fastboot, I'd be willing to flash it onto my Rise.

Have you tried to issue any fastboot commands? Such as fastboot oem unlock?

EDIT:
Also, have you tried flashing a custom recovery?
Do you have adb access while in stock recovery?

I tried the fastboot oem unlock command, it doesn't display an error but doesn't seem to do much... i'll keep experimenting...

and i don't have adb access in recovery and the recovery i built with the builder website did not work but i also foolishly built it with your recovery instead of mine and now i don't have mine to try and build one...

 

[cooldudezach]

so mmcblk0p19 is the data parttion on the c5156 it is mmcblk0p20 on the c5155 and on the c5170(hydro)... also the display is flipped on the hydro... we're still in this together and we can still help each other out but cwm will have to be built separately on each device...

in did not include the data partiton in my system dump for obvious reasons...
there is only 19 partitions on my phone... not 20...

c5156 - Download - 4shared

I'm d'ling it now. Depending on what I find, you get to be a guinea pig! That's interesting it only has 19. I'll see what I can figure out.

Do you have a file at /cache/recovery/last_log? if so, can you get that to me as well? Thanks

 

[db2]

Do you have a file at /cache/recovery/last_log? if so, can you get that to me as well? Thanks

One of the images will be of the cache partition and it will contain that file.

 

[smartmanvartan]

One of the images will be of the cache partition and it will contain that file.

I believe it is p13....Might be wrong tho
But keep in mind that I lost my stock recovery and booted into the hydro and the c5155 recovery and that file may be inaccurate...

 

[db2]

But keep in mind that I lost my stock recovery and booted into the hydro and the c5155 recovery and that file may be inaccurate...

Did they actually work or just reboot the phone? It may still be the same file if your bootloader rejected the other recovery images before actually running them.

 

[smartmanvartan]

Did they actually work or just reboot the phone? It may still be the same file if your bootloader rejected the other recovery images before actually running them.

no it did run them with the usual /misc mound error and an additional /data mount error because of the partitions... but they did work...

 

[smartmanvartan]

this is the resulting file with the c5170 recovery...

Starting recovery on Wed Jan 16 20:31:03 2013
framebuffer: fd 4 (320 x 480)
recovery filesystem table
=========================
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
E:failed to mount /data (No such file or directory)
E:Can't mount /data/fota/ipth-muc.prop
I:fopen_path 2 /data/fota/ipth-muc.prop
E:failed to mount /data (No such file or directory)
E:Can't mount /data/fota/ipth-muc.prop
I:fopen_path 3 /data/fota/ipth-muc.prop
E:failed to mount /data (No such file or directory)
E:Can't mount /data/fota/ipth-muc.prop
I:Failed to open /data/fota/ipth-muc.prop, use default pkg location:/cache/fota
Ielta 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.20120608.154103
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Fri Jun 8 15:41:30 JST 2012
ro.build.date.utc=1339137690
ro.build.type=user
ro.build.user=release
ro.build.host=release
ro.build.tags=release-keys
ro.product.model=C5170
ro.product.brand=kyocera
ro.product.name=C5170
ro.product.device=C5170
ro.product.board=C5170
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=C5170
ro.build.description=C5170-user 4.0.4 IML77 release.20120608.154103 release-keys
ro.build.fingerprint=kyocera/C5170/C5170:4.0.4/IML77/release.20120608.154103:user/release-keys
ro.build.characteristics=default
ro.build.internalswversion=1.000BT.10.a
ro.build.swversion=1.000BT
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=true
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-boost-us
ro.com.google.clientidbase.yt=android-boost-us
ro.com.google.clientidbase.am=android-boost-us
ro.com.google.clientidbase.gmm=android-kyocera
ro.cdma.home.operator.alpha=Boost Mobile
ro.cdma.home.operator.numeric=311870
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
drm.service.enable=true
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=4.0_r2
ro.camera.sound.forced=1
drm.service.enabled=true
persist.sys.ringermode=2
persist.sys.language=en
persist.sys.country=US
persist.timed.enable=true
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=8c161108
ro.mtp.serialno=a0000027e5f7b0
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!

-------------------------------------------------------------------------------------------------------
and with the c5155 recovery...

Starting recovery on Wed Jan 16 21:04:09 2013
framebuffer: fd 4 (320 x 480)
recovery filesystem table
=========================
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
E:failed to mount /data (No such file or directory)
E:Can't mount /data/fota/ipth-muc.prop
I:fopen_path 2 /data/fota/ipth-muc.prop
E:failed to mount /data (No such file or directory)
E:Can't mount /data/fota/ipth-muc.prop
I:fopen_path 3 /data/fota/ipth-muc.prop
E:failed to mount /data (No such file or directory)
E:Can't mount /data/fota/ipth-muc.prop
I:Failed to open /data/fota/ipth-muc.prop, use default pkg location:/cache/fota
Ielta 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=8c161108
ro.mtp.serialno=a0000027e5f7b0
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!

 

[cooldudezach]

I tried the fastboot oem unlock command, it doesn't display an error but doesn't seem to do much... i'll keep experimenting...

and i don't have adb access in recovery and the recovery i built with the builder website did not work but i also foolishly built it with your recovery instead of mine and now i don't have mine to try and build one...

did you issue the command from the phone or the computer? It's been awhile since I've used fastboot, but if you execute commands from the phone it may not need the fastboot command. ie: "oem unlock" If you aren't aware, fastboot oem unlock wipes your data, so back it up!

Here's a command to try:
fastboot boot <name of cwm recovery>.img

try that and see if it boots to it, it wont flash it.

 

[db2]

fastboot doesn't issue shell commands, it's more a direct protocol than adb is. adb is basically a glorified remote shell.

Just for shits:
$ oem
/system/bin/sh: oem: not found

 

[db2]

fastboot doesn't issue shell commands, it's more a direct protocol than adb is. adb is basically a glorified remote shell.

Just for shits:
$ oem
/system/bin/sh: oem: not found

Also fastboot won't do anything if it can't find the device in that mode. You can see it if you have a phone/tablet with fastboot that works, boot it in to that mode, plug it in and on your computer type "fastboot devices" and the thing should show up.

 

[cooldudezach]

Also fastboot won't do anything if it can't find the device in that mode. You can see it if you have a phone/tablet with fastboot that works, boot it in to that mode, plug it in and on your computer type "fastboot devices" and the thing should show up.

I've played with fastboot when I was using my Optimus V. I landed myself there a few times accidentally, and then a few times on purpose.

fastboot doesn't issue shell commands, it's more a direct protocol than adb is. adb is basically a glorified remote shell.

What exactly do you mean by this? I wasn't saying it did issue shell commands? fastboot oem unlock isn't a shell command, it's a fastboot internal command i thought.

 

[db2]

What exactly do you mean by this? I wasn't saying it did issue shell commands? fastboot oem unlock isn't a shell command, it's a fastboot internal command i thought.

Just going off what you'd said:

if you execute commands from the phone it may not need the fastboot command. ie: "oem unlock"

 

[smartmanvartan]

alright well I got some good news and bad news... when i boot the recovery with fastboot it works.. i was working on making myself a tweaked recovery with adb and the errors fixed... i got it working just right... then i wanted to see if i could use the adb reboot bootloader command in the recovery and it also worked... great so far!! then i fastboot reboot aaannnd bootloop ... nothing a factory data reset wouldn't fix but the recovery that is actually on my phone is the c5155 and i cant mount data.... I'm in a tough spot guys and my only option is to get a stock recovery for the c5156 and to figure out a new way to put the device in bootloader mode... so I'm out till i figure this out but at least i was able to help a little... i think if i would've flashed the recovery image to my boot partition I would've booted in to whatever recovery i made... there is definitely a lock on the recovery boot... i cant flash anything but the last thing I'm gonna do is loop mount the vfat mmcblk0p1.img(sys_boot) in terminal and see if i cant find anything interesting unless you guys are already past that point...

 

[cooldudezach]

alright well I got some good news and bad news... when i boot the recovery with fastboot it works.. i was working on making myself a tweaked recovery with adb and the errors fixed... i got it working just right... then i wanted to see if i could use the adb reboot bootloader command in the recovery and it also worked... great so far!! then i fastboot reboot aaannnd bootloop ... nothing a factory data reset wouldn't fix but the recovery that is actually on my phone is the c5155 and i cant mount data.... I'm in a tough spot guys and my only option is to get a stock recovery for the c5156 and to figure out a new way to put the device in bootloader mode... so I'm out till i figure this out but at least i was able to help a little... i think if i would've flashed the recovery image to my boot partition I would've booted in to whatever recovery i made... there is definitely a lock on the recovery boot... i cant flash anything but the last thing I'm gonna do is loop mount the vfat mmcblk0p1.img(sys_boot) in terminal and see if i cant find anything interesting unless you guys are already past that point...

That sucks, fastboot reboot sent it into a bootloop? How far into the boot process does it go? One thing you could try is to spam adb reboot-bootloader while it's booting up. I've had to do that for my optimus v. Did you actually flash the recovery, or just boot into it?

It's good to know that CWM -will- work, if I'm understanding you correctly.

I've already done the sys_boot mount, and nothing in there we need i think. It's just one file AMSS.BIN, which is relating to the radio (correct me if I'm wrong, I could be) I'm pretty sure the bootloader is actually mmcblk0p5, after poking through all the files you gave me with a hex editor.

Do you have insurance on your phone, or are you able to swap it out at all?

 

[cooldudezach]

Just going off what you'd said:

Ah, gotcha. I've been kinda out of it the past couple of days, so things aren't clicking as they should.

 

[smartmanvartan]

That sucks, fastboot reboot sent it into a bootloop? How far into the boot process does it go? One thing you could try is to spam adb reboot-bootloader while it's booting up. I've had to do that for my optimus v. Did you actually flash the recovery, or just boot into it?

It's good to know that CWM -will- work, if I'm understanding you correctly.

I've already done the sys_boot mount, and nothing in there we need i think. It's just one file AMSS.BIN, which is relating to the radio (correct me if I'm wrong, I could be) I'm pretty sure the bootloader is actually mmcblk0p15, after poking through all the files you gave me with a hex editor.

Do you have insurance on your phone, or are you able to swap it out at all?

well the phone will make it all the way thru the boot animation and emits a small vibrate just before it reboots to do it again... i just booted the recovery i made and did not flash it... however it was not a cwm, it was a tweaked stock recovery because i figured if i was gonna trick it it was gonna be that way... so i tweaked the ramdisk on the stock recovery for the c5155 so that it would mount data and misc made it unsecured and enabled adb... and it worked as it was supposed to when i used the fastboot boot (name of image) command.. recovery is mmcblk0p15 so i don't think bootloader is on there as it would get erased at every flash... maybe p17... p18 is labeled carrier so radio would be there no... not sure just thinking logically... /misc is p17... whats there?

 

[we350z]

Hey i've got a Hydro and wondering if any of the Rise users have:

a) figured out how to connect your phone to CDMAWS or QPST/QXDM using custom Qualcomm USB Modem/Serial Drivers?
b) found any other way to read NV items (i.e. from /dev/block)

I'm trying to read nvram to get my profile 0/1 AAA keys...

 

[cooldudezach]

well the phone will make it all the way thru the boot animation and emits a small vibrate just before it reboots to do it again... i just booted the recovery i made and did not flash it... however it was not a cwm, it was a tweaked stock recovery because i figured if i was gonna trick it it was gonna be that way... so i tweaked the ramdisk on the stock recovery for the c5155 so that it would mount data and misc made it unsecured and enabled adb... and it worked as it was supposed to when i used the fastboot boot (name of image) command.. recovery is mmcblk0p15 so i don't think bootloader is on there as it would get erased at every flash... maybe p17... p18 is labeled carrier so radio would be there no... not sure just thinking logically... /misc is p17... whats there?

woops, I meant mmcblk0p5, not mmcblk0p15. I fixed it
while it's doing the boot animation, try connecting to the phone with adb, and issuing adb reboot-bootloader. I know you were saying that it wasn't working earlier with it plugged in to the computer, so maybe if you remove the USB cord before it actually reboots it will work?

If it does work, I'd suggest flashing the modified c5155 recovery image. Would you mind posting the modified recovery up here?


MID-POST EDIT: >.>
While it's booting up, you should be able to use adb to flash the recovery with dd, if you're quick enough. I'm not sure when the sdcard is mounted, so you might need to try pushing the recovery into a system directory.

cat /dev/zero > /dev/block/mmcblk0p15
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p15

 

[cooldudezach]

Hey i've got a Hydro and wondering if any of the Rise users have:

a) figured out how to connect your phone to CDMAWS or QPST/QXDM using custom Qualcomm USB Modem/Serial Drivers?
b) found any other way to read NV items (i.e. from /dev/block)

I'm trying to read nvram to get my profile 0/1 AAA keys...

No, and No, sorry. I follow both the Rise and Hydro forums to make sure that I stay on top of things, and I actually looked into the driver situation. However, I'm on my linux install, so it's much more difficult for me to mess with windows drivers. I forgot to get around to posting in your thread. (It's your's, right?)

On another related note: What's the purpose of getting CDMAWS or QPST/QXDM to work?

 

[cooldudezach]

I -possibly- found out the differences in partitions for the c5155(20 partitions) and the c5156 (19 partitions). I just finished comparing the relative partition images in a hex editor. Aside from minor differences expected, because they ARE different phones after all, the partition images were equal. The only confliction I found was that the c5156 had /data on mmcblk0p19,which bumped mmcblk0p19 to mmcblk0p18. mmcblk0p18 isn't present on the c5156, which is /carrier on the c5155.

Before I go flashing anything regardless, I need to look at the fstab from the c5156 recovery image.


Edit:
I haven't done a thorough comparison between the bootloaders, but I'm probably gonna do it later today. Also, I'm pretty sure it's mmcblk0p5.

 

[we350z]

OK that's what I figured. Guess I am buying a Prevail on eBay today lol. While it also cannot connect to QPST/QXDM they have a workaround where you can read the NV items from the filesystem (/dev/block). I bet we could too but I have no idea where Kyocera buried it or what to look for.

The main purpose of using those programs is they give you the ability to read and write non-volatile (NV) RAM items such as MEID/ESN, MSID, AAA/HA Passwords, etc...

Yes that would be my thread. I bet the custom drivers for the Hydro (if we had them developed) would work for the Rise by just changing the PID since the hardware is so similar.

No, and No, sorry. I follow both the Rise and Hydro forums to make sure that I stay on top of things, and I actually looked into the driver situation. However, I'm on my linux install, so it's much more difficult for me to mess with windows drivers. I forgot to get around to posting in your thread. (It's your's, right?)

On another related note: What's the purpose of getting CDMAWS or QPST/QXDM to work?

 

[DMedina559]

On another related note: What's the purpose of getting CDMAWS or QPST/QXDM to work?

Well I believe it was CDMAWS that got my MSL code from my optimus v. Not sure if that's the only purpose though.
And QPST I used to change my OV's PRL.

 

[smartmanvartan]

got it exchanged under warranty... c5156 recovery comin at you in a little bit...

Edit: Full backup of all partitions:
http://www.4shared.com/zip/T3VRP3Uj/c5156.html

 

[cooldudezach]

got it exchanged under warranty... c5156 recovery comin at you in a little bit...

Edit: Full backup of all partitions:
c5156 - Download - 4shared

Awesome! Glad to hear it worked out. Still willing to play with it?

It looks like the c5156 actually may have scrapped mmcblk0p19, rather than mmcblk0p18 as I stated earlier. I guess I was rushing.

The recovery fstab, however, isn't mounting mmcblk0p18 as /carrier like it is on the c5155. Either way, mmcblk0p18 is all 0's on both the c5155 and c5156.

Other than that, the partitions match up. I'm not sure if flashing the bootloader will throw errors with the /data partition on mmcblk0p19, but anybody up for the risk?

Edit: Oh yeah, do you still have access to fastboot on the new phone?