• 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

downthemachine said:
nice!
Click to expand...

You might like this then, or maybe it'll help someone else get started. I'm venturing beyond my element at this point.

edit: To many 5's in the filename, you get the idea though.

edit 2: As EarlyMon pointed out, DO NOT FLASH THESE FILES. You'll trash your phone, they aren't updates or in any way end-user usable. Flashing 'em won't work anyway.
 

Attachments

How irritating. Looking in to the recovery ramdisk I see Kyocera left adbd in there, but just didn't bother to let us use it. Sure would have made life easier with my first Rise handset had that been available in recovery!
 
downthemachine said:
can someone confirm if the rise can go into bootloader?
Click to expand...

Nobody has figured out a key combo that can do it. I for one don't have the patience to try every possible combo with the hardware keyboard, but I did try a few to no avail out of sheer stubbornness.

Holding power and vol- gets to recovery so it would make sense if bootloader were power and vol+ but that just makes it boot normally. It probably IS the right key combo but bootloader mode is disabled, and 'adb reboot bootloader' making it just boot normally would seem to back that up. No fastboot for us for now it seems, unless Kyocera decides to let us unlock the bootloader... if it weren't for that we'd probably already have a custom ROM.
 
downthemachine said:
i just got the hydro from ebay today, can someone confirm if the rise can go into bootloader?
adb reboot-bootloader just restarts the phone. recovery is exactly the same as the rise, so i think we can build this side by side.
i need the recovery or recovery.fstab from the phone if someone could pm me it.
so far i have been informed that this phone is running this bootloader:
(L)ittle (K)ernel based Android bootloader
this may be the direction we need to take to crack it open.
PLEASE REMEMBER TO NOT FLASH ANYTHING TO EITHER OF THESE PHONES, IT WILL BRICK YOUR DEVICE
Click to expand...

With my limited knowledge of bootloaders, this seems like a viable option. It looks like it supports our processor.

Q2) How do I disable
Click to expand...
 

Attachments

cooldudezach said:
With my limited knowledge of bootloaders, this seems like a viable option. It looks like it supports our processor.




Well, that makes a ton of sense. Kyocera probably did this to prevent key/usb access into the bootloader/fastboot. -_-


I uploaded a zip with the recovery.fstab and the recovery_mmc.fstab. I figured I would upload them rather than PM you so that others would have them handy.
Click to expand...

I'm Assuming this means a possible way to enable recoveries would be to somehow modify the source code of this bootloader to fit the Rise, and then see how that turns out? But I've never heard of any bootloader unlocking that requires flashing a bootloader, nor have I ever done anything close to that on an Android device, so maybe i'm just thinking too much and our answer is much simpler.
 
daygen4545 said:
I'm Assuming this means a possible way to enable recoveries would be to somehow modify the source code of this bootloader to fit the Rise, and then see how that turns out? But I've never heard of any bootloader unlocking that requires flashing a bootloader, nor have I ever done anything close to that on an Android device, so maybe i'm just thinking too much and our answer is much simpler.
Click to expand...

It describes how Kyocera's hardware handles initialization and hands over control to the Linux kernel. Any unlock would have to be on that level, so the phone itself would accept an alternative boot (or recovery) image. I think there's some confusion being introduced, there's the hardware bootloader that does the basic initialization and security checking, similar to a BIOS, and there's the Android bootloader... we need to have the first unlocked to change the second.

As it is we can change the Android bootloader all we want, if it's rejected by Kyocera's locked hardware bootloader it'll just bootloop.

edit: That's discounting the possibility of an exploitable security goof on Kyocera's part. We're not far enough in to it to even know if such a thing exists yet.
 
gonna let the head chief guys & ha*kers look at this and see if it would help them in any way & then iam gonna sit back and letcha guys work ill still follow but i wanna let the readers whos reading my post know that i am just a idealist windows computer geek and some ubuntu and zorion not this level of android but would love to have lessons from some of you pros since this seems to be the way of the future anyhow these 2 files below iam sure alot of u guys can get and its supposedly shows you the exact boot processes as its happening for your phone and the video shows by touching ur touchpad you can stop the screen scroll down and read the entire boot process as its happening doesnt help someone like me but i hope it helps u true android masters -- goodluck guys as i sit back and wait now

https://play.google.com/store/apps/details?id=eu.chainfire.livelogcat.lite&hl=en

https://play.google.com/store/apps/details?id=eu.chainfire.livedmesg.lite
 
Those are a couple neat looking apps, I think I'll use them on other devices. By all apearances though, messing with the boot animation on the Rise seems to be as bad as mucking with the boot partition. Those that have tried (that I've seen) end up in a bootloop.

Definitely looking forward to being able to use them in the future though. Also looking forward to silencing the noisy stock boot animation *grr*.
 
db2 said:
It describes how Kyocera's hardware handles initialization and hands over control to the Linux kernel. Any unlock would have to be on that level, so the phone itself would accept an alternative boot (or recovery) image. I think there's some confusion being introduced, there's the hardware bootloader that does the basic initialization and security checking, similar to a BIOS, and there's the Android bootloader... we need to have the first unlocked to change the second.

As it is we can change the Android bootloader all we want, if it's rejected by Kyocera's locked hardware bootloader it'll just bootloop.

edit: That's discounting the possibility of an exploitable security goof on Kyocera's part. We're not far enough in to it to even know if such a thing exists yet.
Click to expand...

I was referring to the hardware bootloader, assumed (yeah, I know) that all references to bootloader follow the Android convention and stick to that.

I am under the impression that everything here is aiming at an exploit.

PS - my point earlier was that replacing the (hardware) bootloader is quite extraordinary, having done it. I very much doubt that will ever happen here.
 
I know next to nothing about low level Android stuff, so this may not be helpful, but I noticed something in the Subreddit dedicated to the Rise that looked like it might be useful, so I'm sharing it here:

Partition Information (self.krise)
submitted 21 hours ago* by db2
I dd'd all 20 mmcblk0 parts in to images and then put them on my computer and simply tried to mount them, for example with:
mount mmcblk0p1.img ./mnt -o loop
The results of that, plus information from /proc/mounts and the recovery log in the cache partition, is below.
Device Size (bytes) Name Mount (if any) FS Other Information
/dev/block/mmcblk0p1 33554432 amss vfat recovery calls it sys_boot
/dev/block/mmcblk0p2 524288 Would not mount
/dev/block/mmcblk0p3 1310720 Would not mount
/dev/block/mmcblk0p4 1024 Would not mount
/dev/block/mmcblk0p5 4194304 Would not mount
/dev/block/mmcblk0p6 4194304 Would not mount
/dev/block/mmcblk0p7 4194304 Would not mount
/dev/block/mmcblk0p8 8388608 boot Boot partition
/dev/block/mmcblk0p9 8388608 Would not mount
/dev/block/mmcblk0p10 4194304 Would not mount
/dev/block/mmcblk0p11 4194304 Would not mount
/dev/block/mmcblk0p12 318767104 system /system ext4
/dev/block/mmcblk0p13 419430400 cache /cache ext4
/dev/block/mmcblk0p14 8388608 /persist ext4 Something to do with wifi, contains the file WCN1314_qcom_wlan_nv.bin
/dev/block/mmcblk0p15 8388608 recovery Recovery partition
/dev/block/mmcblk0p16 58720256 Would not mount
/dev/block/mmcblk0p17 8388608 sysprop /sysprop ext4
/dev/block/mmcblk0p18 41943040 carrier /carrier ext4 The filesystem is empty
/dev/block/mmcblk0p19 12582912 Would not mount
/dev/block/mmcblk0p20 699125760 data /data ext4
Click to expand...

I would include the link to the original post, which is much better formatted and needs to be in there for credit anyway, but apparently since I made the account to share this, I can't post links just yet.

Edit: And then I scroll up and realize that the person who posted it on Reddit is already posting in this thread, judging by the matching username XD

Good luck getting the bootloader unlocked, this is a great little phone for the price and I'd love to be able to get a custom rom on it.
 
I think that we are able to unlock the bootloader if we can see how the htc dev site works and mimic there stuff into the virgin mobile kyocera rise if that doesn't help. Then we could just get the phone go outside and throooowwww.it to outerspace lol just kidding well I think that if we could find some of the people that developed this phone and email them and ask them how to unlock the bootloader that could help. Or we could find someone who can go through the system files with a cmd window and do it manually. And wipe the entire phone automatically. Another thing propabaly if we have a rooted phone we could download the es file explorer and go in the dephths of what makes the entire phone and check on every folder such as updates and stuff anything else ill post up thanks :D
 
Igot an idea. Now this might blow your minds in how to unlock the bootloader. But ima buy a new kyocera rise and test t out Ithink if we wipe the entire phone and then see what happens. Will it go into safe mode in its stock rom. Or will it give us the option for the bootloader
 
  • Like
Reactions: db2
Wipe it out completely? OP tried wiping recovery/boot and it didn't help. Maybe wiping it all out might trick the bootloader in to thinking it's getting an initial flash, is that your thought?

Wouldn't that be something if that's all it took to defeat the bootloader lock. I'm not going to hold my breath but it's worth a shot if you're willing to "waste" the money on a procedure likely to brick it.

I wonder if the Rise will sing Daisy as it happens.
 
Alastor10009 said:
Igot an idea. Now this might blow your minds in how to unlock the bootloader. But ima buy a new kyocera rise and test t out Ithink if we wipe the entire phone and then see what happens. Will it go into safe mode in its stock rom. Or will it give us the option for the bootloader
Click to expand...

Yeah, I've tried to wipe boot/recovery. I ended up with a paperweight. If you erase everything, every block except for the bootloader, I wonder what would happen. Probably a brick, but if you want to throw some money away, I say go for it. who knows?
 
Well it does seem like a waste but even if it becomes a paperwight then even so wouldn't it have." A backup rom" in safe mode? If that's true then we could trace how this is possible and create our own way of linking commands into the ssafe mode rom.? Anyone have an idea?
 
You must log in or register to reply here.
Back
Top Bottom