Compilation of Kyocera Rise Stock Images


  1. dtalley11

    dtalley11 Well-Known Member

    So I decided that it would probably be a good idea to get a thread going of all the different images (at least system, boot and recovery) for the rise. I know there are quite a few different versions of the firmware on this phone and I only have 1 phone (Sprint).

    If anybody has images to add to the list (I will write a guide for making images in the 2nt post), go ahead and post them and I'll try to get them up in the OP (they can be rooted). Although I will only be putting recovery/kernel/system images on the OP, the other partitions may still be helpful so if you wish, go ahead and post them as well (other than data and cache, we don't need to know what you do with your phone, plus they are generated).

    WARNING! Flashing images with a locked bootloader can easily Brick Your Phone! I am not responsable if you end up bricking your phone doing anything described in this thread. Don't do it unless you know what you are doing.

    WARNING! Fastboot flashing a system partition will cause the kernel not to mount the system partition on next reboot. Use the dd command for system
    Sprint:

    --1.011SP images--
    (None Yet)

    --1.003SP images--
    (None Yet)

    --1.005SP images--
    Boot: mmcblk0p8 Mirror 1
    Recovery:mmcblk0p15 Mirror 1
    System: mmcblk0p12.zip Mirror 1

    Virgin Mobile:


    --1.004VM images--
    (Thanks sneaky_1 and TechDad378)
    Boot: mmcblk0p8
    Recovery:mmcblk0p15
    System: mmcblk0p12
    Original

    --1.000VM images--
    (None Yet)


    Public Mobile:

    --1.002PM images--
    (Thanks smartmanvartan)
    Boot: mmcblk0p8 Mirror 1
    Recovery:mmcblk0p15 Mirror 1
    System: mmcblk0p12 Mirror 1
    Original

    F.A.Q

    Q. How do I know which version my phone is running?
    A. Go into settings>About Phone> and look at the Software Version field

    Q. This images says mmcblk0p* and I do not know which image is which. How do I find out?
    A. Here is a list of known partitions and their names (based on recovery.fstab in my stock recovery):
    [HIGH]boot mmcblk0p8
    cache mmcblk0p13
    data mmcblk0p20
    misc mmcblk0p17
    recovery mmcblk0p15
    sdcard mmcblk1p1
    system mmcblk0p12
    sysprop mmcblk0p17
    carrier mmcblk0p18[/HIGH]

    Q. How do I use these Images?
    Flashing images with a locked bootloader can easily brick your phone if you do not know what you are doing.
    A. 2 ways. You can either dd the images with a command similar to:
    [HIGH]dd if=/sdcard/mmcblk0p15 of=/dev/block/mmcblk0p15[/HIGH] (which works for system but not recovery or boot)
    or you can use fastboot (part of the android developer kit, like adb you have to have the drivers installed, will cause system to not boot if you use it for flashing system images)
    [HIGH]adb reboot bootloader
    (wait a few minutes for your computer to see your phone)
    fastboot flash recovery mmcblk0p15[/HIGH]
    An interesting note about fastboot: You can set up a bootimage (kernels and recoveries) for a single boot by using the command
    [HIGH]fastboot boot mmcblk0p15[/HIGH]
    and then there is adb reboot oem-unlock, which allows you to fastboot boot unsigned images after it finishes, although only for a short amount of time.

    Another interesting note: The Rise is kernel compatible with the Kyocera Hydro. For me at least, I was able to flash a hydro kernel into my recovery slot and watch it boot my phone (with understandable issues like lack of keyboard back-light). Again, don't flash any images unless you know what you are doing!

    Q. How do I make these Images?
    A. I will go through the process of making images in my post.

    Advertisement
  2. dtalley11

    dtalley11 Well-Known Member

    How To make images:

    First you need to know where the partition is. Here is a cheat sheet for that:
    [HIGH]boot /dev/block/mmcblk0p8
    cache /dev/block/mmcblk0p13
    data /dev/block/mmcblk0p20
    misc /dev/block/mmcblk0p17
    recovery /dev/block/mmcblk0p15
    sdcard /dev/block/mmcblk1p1
    system /dev/block/mmcblk0p12
    sysprop /dev/block/mmcblk0p17
    carrier /dev/block/mmcblk0p18[/HIGH]

    Now, knowing where the partition is you want to create the image of, you have to either open up adb shell or the terminal emulator app then run the command
    [HIGH]dd if=/dev/block/<partition> of=/sdcard/<partition>[/HIGH]
    so if I wanted to make an image of recovery, the command would be
    [HIGH]dd if=/dev/block/mmcblk0p15 of=/sdcard/mmcblk0p15[/HIGH]
    Then you can find the image on the root of your sdcard. From there I will let you figure out how and where you want to upload it.

    Also, I have uploaded an image of each partition on 1.005SP other than system(will do soon), data and cache.

    That can be found http://downloads.codefi.re/dtalley11/Rise_images/1005SP/
    sneaky_1 and dibblebill like this.
  3. dibblebill

    dibblebill Well-Known Member

    I must admit, the photographer in me saw this and thought "Why does he need the stock photographs of the phone?". Boy did I feel dumb once I read it.
  4. smartmanvartan

    smartmanvartan Well-Known Member Contributor

    HERE is the Public Mobile c5156... ;)... this is a great idea to have them all in the same place.

    F.Y.I: the partitions are slightly different on the c5156... it's been a while but it was /data that was on mmcblk0p18 instead of 19 I think...
    El Presidente and dtalley11 like this.
  5. dtalley11

    dtalley11 Well-Known Member

    The sizes looked right for boot, recovery and system. I didn't quite have enough time to mount them and make sure so if anybody notices something off with them, please let me know.

    Also, if you can get me the output of the mount command (either used in terminal emulator or adb shell) it would be appreciated (just to know for sure)
  6. smartmanvartan

    smartmanvartan Well-Known Member Contributor

    honestly it's been so long and i don't have the device anymore... but if you provide me with a link to stock recovery for the c5155 i can give you a fstab comparison...
  7. dtalley11

    dtalley11 Well-Known Member

    There just so happens to be a link in the op
    smartmanvartan likes this.
  8. smartmanvartan

    smartmanvartan Well-Known Member Contributor

    I don't know why but I didn't think that sprint had the Rise c5155... OK I'll check it out...
  9. smartmanvartan

    smartmanvartan Well-Known Member Contributor

    Sprint C5155 recovery fstab files...

    recovery.fstab:


    # Copyright (c) 2010, Code Aurora Forum. All rights reserved.
    #
    # Redistribution and use in source and binary forms, with or without
    # modification, are permitted provided that the following conditions are
    # met:
    # * Redistributions of source code must retain the above copyright
    # notice, this list of conditions and the following disclaimer.
    # * Redistributions in binary form must reproduce the above
    # copyright notice, this list of conditions and the following
    # disclaimer in the documentation and/or other materials provided
    # with the distribution.
    # * Neither the name of Code Aurora Forum, Inc. nor the names of its
    # contributors may be used to endorse or promote products derived
    # from this software without specific prior written permission.
    #
    # THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
    # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
    # MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
    # ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
    # BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
    # CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
    # SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
    # BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
    # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
    # OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
    # IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

    # mount point fstype device [device2]

    /boot mtd boot
    /cache yaffs2 cache
    /data yaffs2 userdata
    /misc mtd misc
    /recovery mtd recovery
    /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
    /system yaffs2 system


    recovery_mmc.fstab:

    # Copyright (c) 2011, Code Aurora Forum. All rights reserved.
    #
    # Redistribution and use in source and binary forms, with or without
    # modification, are permitted provided that the following conditions are
    # met:
    # * Redistributions of source code must retain the above copyright
    # notice, this list of conditions and the following disclaimer.
    # * Redistributions in binary form must reproduce the above
    # copyright notice, this list of conditions and the following
    # disclaimer in the documentation and/or other materials provided
    # with the distribution.
    # * Neither the name of Code Aurora Forum, Inc. nor the names of its
    # contributors may be used to endorse or promote products derived
    # from this software without specific prior written permission.
    #
    # THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
    # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
    # MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
    # ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
    # BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
    # CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
    # SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
    # BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
    # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
    # OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
    # IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

    # mount point fstype device [device2]

    /sys_boot vfat /dev/block/mmcblk0p1
    /boot emmc /dev/block/mmcblk0p8
    #/cache ext4 /dev/block/mmcblk0p15
    /cache ext4 /dev/block/mmcblk0p13
    /data ext4 /dev/block/mmcblk0p20
    #/misc emmc /dev/block/mmcblk0p17
    /recovery emmc /dev/block/mmcblk0p15
    /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
    /system ext4 /dev/block/mmcblk0p12
    /sysprop ext4 /dev/block/mmcblk0p17
    /carrier ext4 /dev/block/mmcblk0p18

    Public C5156 recovery fstab files...

    recovery.fstab:


    # Copyright (c) 2010, Code Aurora Forum. All rights reserved.
    #
    # Redistribution and use in source and binary forms, with or without
    # modification, are permitted provided that the following conditions are
    # met:
    # * Redistributions of source code must retain the above copyright
    # notice, this list of conditions and the following disclaimer.
    # * Redistributions in binary form must reproduce the above
    # copyright notice, this list of conditions and the following
    # disclaimer in the documentation and/or other materials provided
    # with the distribution.
    # * Neither the name of Code Aurora Forum, Inc. nor the names of its
    # contributors may be used to endorse or promote products derived
    # from this software without specific prior written permission.
    #
    # THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
    # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
    # MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
    # ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
    # BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
    # CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
    # SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
    # BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
    # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
    # OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
    # IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

    # mount point fstype device [device2]

    /boot mtd boot
    /cache yaffs2 cache
    /data yaffs2 userdata
    /misc mtd misc
    /recovery mtd recovery
    /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
    /system yaffs2 system

    recovery_mmc.fstab:


    # Copyright (c) 2011, Code Aurora Forum. All rights reserved.
    #
    # Redistribution and use in source and binary forms, with or without
    # modification, are permitted provided that the following conditions are
    # met:
    # * Redistributions of source code must retain the above copyright
    # notice, this list of conditions and the following disclaimer.
    # * Redistributions in binary form must reproduce the above
    # copyright notice, this list of conditions and the following
    # disclaimer in the documentation and/or other materials provided
    # with the distribution.
    # * Neither the name of Code Aurora Forum, Inc. nor the names of its
    # contributors may be used to endorse or promote products derived
    # from this software without specific prior written permission.
    #
    # THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
    # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
    # MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
    # ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
    # BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
    # CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
    # SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
    # BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
    # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
    # OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
    # IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

    # mount point fstype device [device2]

    /sys_boot vfat /dev/block/mmcblk0p1
    /boot emmc /dev/block/mmcblk0p8
    #/cache ext4 /dev/block/mmcblk0p15
    /cache ext4 /dev/block/mmcblk0p13
    /data ext4 /dev/block/mmcblk0p19
    #/misc emmc /dev/block/mmcblk0p17
    /recovery emmc /dev/block/mmcblk0p15
    /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
    /system ext4 /dev/block/mmcblk0p12
    /sysprop ext4 /dev/block/mmcblk0p17
    dtalley11 likes this.
  10. smartmanvartan

    smartmanvartan Well-Known Member Contributor

    I'm downloading the c5156 as I didn'y have it on my pc anymore but I'm starting to remember... the C5156 has 19 partitions instead 20 and our data partition is on mmcblk0p19 instead of mmcblk0p20...
  11. dtalley11

    dtalley11 Well-Known Member

    Huh, that might make it fun when custom kernels come around. Specially if anybody touches partition layouts. It looks like all the important stuff checks out (boot, recovery, system). Anyways, Thanks a ton for the fstabs, when I was building TWRP for the C5155, I found the normal fstab means nothing, since our device uses emmc, not mtd. Say if you were doing a kernel, you could just put the emmc entries in the recovery.fstab.
  12. What your doing is not gonna work and I know since me and MFIC are friends.She says you would have to decrypt the FW prior doing anything given forementioned relays their anything else besides this will brick your phone as it has embedded security
  13. dtalley11

    dtalley11 Well-Known Member

    That's the ace we have. Even if we fastboot flash system system.img, and it triggers the kernel to not mount system (which it does, so i'll make a not on the OP) we can still, because init.rc gives is adb, reboot oem-unlock, reboot bootloader and it allows us to fastboot boot unsigned boot.img or recovery.img. Directory list << so you can fastboot boot that and it puts you into TWRP. From there you can dd if=/sdcard/system.imb of=/dev/block/mmcblk0p12 and you are back in track.

    That is my first hand experience talking right there ;)
  14. Given I'm not one to lie will go ahead and say I'm MYFIC on a diff profile had to come fruition this way given my initial has a block which is obviously apparent simultaneously only here to help others no form of recompense I don't need help been modding phones before android even came into exist.Either way can't help as I dev on the phonr itself no pc but good to see some sdx members coming to fore back on my intercept I used your DTF Kernal thank you for that.Have you converse with BadSector lately?If yes tell him to come here since his prowess is somewhat(keyword) equivalent to mine and will need him also on the if no then disregard.Either way good luck
  15. sneaky_1

    sneaky_1 Well-Known Member

    dtalley11 likes this.
  16. dtalley11

    dtalley11 Well-Known Member

    Yeah, I have talked with Bads3ctor, but not in quite a while (more than a year). That was long ago, in my android development infancy.

    Thanks a ton, I totally forgot about them (sorry)! If you can a system dump would be nice. Although it doesn't need to be, if you can get itas close to stock as you can (can be rooted and all I'm not extremely worried, more or less for people to get their phone back and booting )it would help out those people who have to sell it or whatnot. Sometime soon I will go about writing an unbrick guide, but first I gotta go bricking my phone in as many ways as I think users would do
  17. smartmanvartan

    smartmanvartan Well-Known Member Contributor

    Just out of curiosity, when you boot into your TWRP recovery, do you have a time limit?... I had CWM working the same way on the Public Mobile C5156 and it would boot and everything was working except for USB mass storage. But it would only work for like 20-30 seconds and then it would reboot. Which led me to believe that there was some kind of secondary protection much like many others seem to think in these threads...
  18. Forementioned equates embedded sec I'm conversing about even if one manages to unlock or mod the bl in anyway this will kick in overwrite whatever you have and brick phone depending on what your trying to do.Kyocera is a smart company but I'm smarter which is I say decrypt actual fw prior trying anthing given the bl encryption is here not on the phone itself this why 2nd int or anything equivalent will not work
  19. Bad given your reading this thread yet not recompensing equivalent to how I was back on sdx feel free to join given your help is much appreciated especially being the only one who partially ran ICS on a SI.That was bad ass
  20. sneaky_1

    sneaky_1 Well-Known Member

    I'll get a system dump in a little bit. It is now updated to 1.04, so I will grab them all.
  21. dtalley11

    dtalley11 Well-Known Member

    Yup. I do have the issue, but it seems to be a random amount of time, long enough for me to flash my cm9 builds ;).
    smartmanvartan likes this.
  22. TechDad378

    TechDad378 Well-Known Member

    Virgin Mobile

    --1.004VM images--

    The link below has a zip file named 1.004VM.zip. The zip file contains the following...

    1. mmcblk0p8
    2. mmcblk0p12
    3. mmcblk0p15

    1.004VM.zip
  23. smartmanvartan

    smartmanvartan Well-Known Member Contributor

    Is the rise on sprint something new... back when I had the rise for public it was only vm and pm...

    Also dtalley11, how do you put your c5155 into fastboot? and can the vm c5155 do the same now?

    Are you using modified drivers like Techdad?
  24. cooldudezach

    cooldudezach Well-Known Member

    Nope, the rise on sprint was out back when I was doing my initial rise bricking, er... testing.

    Edit:
    Would one of you like to send me the usb drivers you're using, or at least walk me through how to get into fastboot on my Rise? Through all my testing, I never managed to get into fastboot, although I never used modified drivers.
    smartmanvartan likes this.
  25. smartmanvartan

    smartmanvartan Well-Known Member Contributor

    Hey man long time... Did you ever try with terminal emulator on your rooted rise?

    In terminal...
    Su
    Reboot bootloader


    If these guys have it working with modified drivers, this should work...

Share This Page