Root Porting ClockWorkMod to the Kyocera Rise

dtalley11 · Sep 10, 2013

naked_ferret said:
Can you upload the img of the bootloader and recovery of your Sprint Rise? I wanna try it also on my back up Rise

I flashed mmcblk0p5 but there is still some ambiguity in which partition actually is the bootloader. Flashing p5 from the sprint rise did in fact brick Rise #2 (flashes the Rise logo for almost a second the restarts)

Also, all the sprint partitions have been uploaded and on the compilation of images thread (http://androidforums.com/rise-all-things-root/760556-compilation-kyocera-rise-stock-images.html)

cooldudezach · Sep 11, 2013

dtalley11 said:
I flashed mmcblk0p5 but there is still some ambiguity in which partition actually is the bootloader. Flashing p5 from the sprint rise did in fact brick Rise #2 (flashes the Rise logo for almost a second the restarts)

Also, all the sprint partitions have been uploaded and on the compilation of images thread (http://androidforums.com/rise-all-things-root/760556-compilation-kyocera-rise-stock-images.html)

I think I'm going to try to flash p2, p3, and p5 and see what happens. Would amss.mbn differ between the sprint rise and the vm rise? If it doesn't work, I'll try all but system I guess.

On a side note: I figured I'd update the thread. i have a 'working' TWRP (dtalley11 built it!) that doesn't reboot every 2 minutes. However, it still can only boot using fastboot. So the Sprint and presumably the Public Mobile Rise can use it, but VM Rise is still no go. I need to pick up a Hydro and Event. Maybe their bootloaders might give better results, since they all share the same hardware.

Edit: Just bought an Event. Shipping from same state, so I should get it in about 2 days from now. Can't wait to get my hands dirty with it! Is there any dev work being done on it at all? I couldn't find anything myself.

It looks like a decent phone. Same hardware as the Rise/Hydro - minus the keyboard and waterproofing - but it has 4GB internal storage! (Compared to 2GB in the Hydro and Rise)

Also, Kyocera does not have the Kernel source on their website for the Event yet. o_0

dtalley11 · Sep 11, 2013

cooldudezach said:
Also, Kyocera does not have the Kernel source on their website for the Event yet. o_0

Yeah, I noticed that and was thinking about requesting they post it, but it wouldn't matter much if it is really as similar to the rise as the hydro is

cooldudezach · Sep 11, 2013

dtalley11 said:
Yeah, I noticed that and was thinking about requesting they post it, but it wouldn't matter much if it is really as similar to the rise as the hydro is

It would be good to compare them though. You never know what they might have changed.

smartmanvartan · Sep 11, 2013

cooldudezach said:
It would be good to compare them though. You never know what they might have changed.

Amss is your radio...the band configuration...So yes they would differ between vm and Sprint... that being said in my experience, it is safer to flash the entire firmware package(amss, adsp, osbl, dbl, EMMCBOOT)

Alternity · Sep 13, 2013

I might've found how to unlock the bootloader: showthread.php?t=2310573 on the xda developpers website (Sorry I can't post links it looks like)

Last post there is an app, that appear to have worked. I unfortunately flashed a wrong image to my phone and now it's caught in a bootloop, that doesn't let me connect via either adb or fastboot. I'm going to Public Mobile today to try to get it replaced since I bought it about 2 weeks ago. The reason I flashed it is because I was getting error 110 upon installing any apps, from anywhere, and a factory reset didn't helped at all. I was able to still use the app on the xda thread via adb push.

Yes I am positive the image was wrong, I'm still kinda new to android, and one of my friends who has experience with flashing roms told me I took the wrong imagine. :\

My phone is a Kyocera Rise c5156, just to confirm things.

TechDad378 · Sep 13, 2013

The app was created for another device. Without knowing how the app achieves boot unlock how can you verify it works for the Rise?

The phone is set with checks and balances to verify the integrity of the filesystem.

Without determining how the app works, I can say whether the app or img caused the problem.

Where did the img you use come from?

Alternity · Sep 13, 2013

TechDad378 said:
The app was created for another device. Without knowing how the app achieves boot unlock how can you verify it works for the Rise?

The phone is set with checks and balances to verify the integrity of the filesystem.

Without determining how the app works, I can say whether the app or img caused the problem.

Where did the img you use come from?

When I first launched the app, Bootloader status was ''Unknown'' inside the app, once I tapped unlocked and rebooted the phone, the app stated ''Unlocked''

The IMG was the wrong one, I took it from the thread with the images, without knowing what I was really doing I tried to flash the c5156.zip image to system, some thing I shouldn't have done.

By the way, Public Mobile did gave me a new phone. I played innocent and told them the phone just stopped working. I don't know if they always do that that easily but if something like this ever happens, you can try if you still are on warranty, it was easy.

OverByter · Sep 13, 2013

Actually that's called fraud, manufacturers warranty covers device defects, not user error. It's called taking one for the team. :rolleyes:

OB

TechDad378 · Sep 13, 2013

I need to find out how the app works. Then i can determine if it is a viable solution.

Will give it a shot when I get a chance.

oliver · Sep 13, 2013

apologies if this is a dummies question, but how do you verify the bootloader is locked? Is it from trial-and-error of failure or is there some code you can look at to say 'here's where it requests an image with this sig' (or whatever it would be)?

smartmanvartan · Sep 14, 2013

Alternity said:
When I first launched the app, Bootloader status was ''Unknown'' inside the app, once I tapped unlocked and rebooted the phone, the app stated ''Unlocked''

The IMG was the wrong one, I took it from the thread with the images, without knowing what I was really doing I tried to flash the c5156.zip image to system, some thing I shouldn't have done.

By the way, Public Mobile did gave me a new phone. I played innocent and told them the phone just stopped working. I don't know if they always do that that easily but if something like this ever happens, you can try if you still are on warranty, it was easy.

If you are with public mobile, the c5156 is the right image for you... could you perform a factory reset? maybe thats all you needed...

Alternity · Sep 14, 2013

smartmanvartan said:
If you are with public mobile, the c5156 is the right image for you... could you perform a factory reset? maybe thats all you needed...

I did try that, but that didn't do nothing, the phone was still in bootloop. I did got told that I should've gone with the image ''mmcblk0p15'' from that page http://androidforums.com/rise-all-things-root/760556-compilation-kyocera-rise-stock-images.html instead of the c5156.zip file that the link below provides. So if I did flash the rigth image it would probably mean that the bootloader was still locked?

smartmanvartan · Sep 14, 2013

These images are stock images so they work with the locked bootloader. However the partitions are different on the c5156 compared to the c5155 so that's why it's important to flash the right one in this case. But my guess is you needed to perform a factory reset afterwards because you had data from apps that are not in this system image and it had apps that had no data so it was boot looped. A factory reset would've done the job I'm sure and essentially the people at public should've tried this and they might do so now that you returned the phone and when it boots they will know you rooted it...

cooldudezach · Sep 15, 2013

Alternity said:
I did try that, but that didn't do nothing, the phone was still in bootloop. I did got told that I should've gone with the image ''mmcblk0p15'' from that page http://androidforums.com/rise-all-things-root/760556-compilation-kyocera-rise-stock-images.html instead of the c5156.zip file that the link below provides. So if I did flash the rigth image it would probably mean that the bootloader was still locked?

Did you try to flash the entire c5156.zip file, or the correct image from within the zip file?

Alternity · Sep 15, 2013

cooldudezach said:
Did you try to flash the entire c5156.zip file, or the correct image from within the zip file?

That's the thing I didn't do right, I flashed the whole thing.

smartmanvartan said:
These images are stock images so they work with the locked bootloader. However the partitions are different on the c5156 compared to the c5155 so that's why it's important to flash the right one in this case. But my guess is you needed to perform a factory reset afterwards because you had data from apps that are not in this system image and it had apps that had no data so it was boot looped. A factory reset would've done the job I'm sure and essentially the people at public should've tried this and they might do so now that you returned the phone and when it boots they will know you rooted it...

I did try the factory reset, and more than one time, even before I flashed it (to try to fix the error 110 problem), it never worked. They tried it too, two times, before giving me the new phone.

So you're telling me that even with a locked bootloader I can flash stock images? That's good to know. I'm wondering if any of you found the key combination to enter in bootloader mode, I couldn't do it from any other way than adb reboot bootloader, there must be a button combination. I tried every buttons around the phone, and some on the keyboard, I can't seem to find it.

dtalley11 · Sep 16, 2013

oliver said:
apologies if this is a dummies question, but how do you verify the bootloader is locked? Is it from trial-and-error of failure or is there some code you can look at to say 'here's where it requests an image with this sig' (or whatever it would be)?

adb status-window sometimes works but the fact that we can't load non Kyocera kernels or recoveries also proves it. I've compiled fully working kernels and recoveries (tested with the sprint rise's tethered unlock method) yet they do not work normally

Alternity · Sep 16, 2013

dtalley11 said:
adb status-window sometimes works but the fact that we can't load non Kyocera kernels or recoveries also proves it. I've compiled fully working kernels and recoveries (tested with the sprint rise's tethered unlock method) yet they do not work normally

I heard you can test images before flashing them via fastboot, for a one time boot. If is true? I would like to know the command if it is.

Also, have you looked at the app I linked in my first post? I'm looking for feedback on this, when any of you guys that knows android better than me can look at it

.

dtalley11 · Sep 16, 2013

Alternity said:
I heard you can test images before flashing them via fastboot, for a one time boot. If is true? I would like to know the command if it is.

Also, have you looked at the app I linked in my first post? I'm looking for feedback on this, when any of you guys that knows android better than me can look at it .

adb reboot bootloader (known to work only on sprint)
#wait for it to stay on the rise logo
fastboot boot /path/to/boot.img

I have not looked at your app but I will as sonn as I get some free time

TechDad378 · Sep 16, 2013

The best way to check an img before flashing a device is to create a vm (virtual machine) where you can load the image. This can reduce any unwanted results. Creating a VM will take some time to do and is outside the scope of this post.

You will not be able to flash an img file to the device until a solution is created in the kernel which stops the device from reverting to stock img.

The kernel has some pretty interesting checks and balances in order to keep the integrity of the filesystem.

Some how those checks have to bypassed or removed. Which is why the device reboots automatically or gets stuck in a boot-loop when you flash anything.

Their source files say any changes will be caught and reverted back to stock. Which is pretty much one hell of a challenge for all of us!

smartmanvartan · Sep 16, 2013

Alternity said:
That's the thing I didn't do right, I flashed the whole thing.

I did try the factory reset, and more than one time, even before I flashed it (to try to fix the error 110 problem), it never worked. They tried it too, two times, before giving me the new phone.

So you're telling me that even with a locked bootloader I can flash stock images? That's good to know. I'm wondering if any of you found the key combination to enter in bootloader mode, I couldn't do it from any other way than adb reboot bootloader, there must be a button combination. I tried every buttons around the phone, and some on the keyboard, I can't seem to find it.

If you flashed the whole zip rather than just the appropriate partition then yeah... that wont work... I was going on the assumption you flashed the mmcblk0p15 partition from inside the c5156.zip....

as for getting into fastboot on the C5156, you can do it with terminal emulator by first typing "su" then typing "reboot bootloader". or downloading this app. Once you have fastboot and the appropriate drivers, the command for one time boot is "fastboot boot <file>" but it only works with a recovery.img or a boot.img appropriate to your system partition. to my knowledge you can not boot a system partition using this method but you can boot into a custom recovery. BE AWARE THAT THE PARTITIONS ARE DIFFERENT ON THE C5156 AND THAT THE TWRP RECOVERY AVAILABLE FOR THE C5155 WILL NOT WORK PROPERLY. The data partition is on mmcblkp19 on the c5156 but it is on mmcblk0p20 for the c5155...

Alternity · Sep 16, 2013

Thanks for the answer. That's sad that so far you can't boot into bootloader via a button combination. There must be a way....

smartmanvartan · Sep 16, 2013

Alternity said:
Thanks for the answer. That's sad that so far you can't boot into bootloader via a button combination. There must be a way....

trust me there isn't... however if someone where to build the bootloader from source, it could be programed into it....

TechDad378 · Sep 16, 2013

Can you verify what partition stores the cache on c5156?

dtalley11 · Sep 16, 2013

I'm still looking to 2nd-init as the answer for this phone until somebody smarter than me gets around to cracking the bootloader

Root Porting ClockWorkMod to the Kyocera Rise

Member

Android Enthusiast

Member

Android Enthusiast

Android Expert

Newbie

Well-Known Member

Newbie

Resident Slide Rule Guru

Well-Known Member

Newbie

Android Expert

Newbie

Android Expert

Android Enthusiast

Newbie

Member

Newbie

Member

Well-Known Member

Android Expert

Newbie

Android Expert

Well-Known Member

Member

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads