• 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

rbheromax said:
The recovery.img has a ramdisk offset, u gotta set mkbootimg account for that for it to work
Click to expand...

Here's the stock recovery.img:
[HIGH]
Android Boot Image Info:


* load addresses:
kernel: 0x00208000
ramdisk: 0x01500000
tags: 0x00200100[/HIGH]And here's the cwm recovery.img:

[HIGH]

* load addresses:
kernel: 0x00208000
ramdisk: 0x01200000
tags: 0x00200100

* cmdline = no_console_suspend=1 console=ttyDCC0 androidboot.hardware=qcom
[/HIGH]It seems to be set to 0x01200000 instead of 0x01500000. I can set it to 0x01500000 but I don't have a rise so someone has to risk bricking their rise to test the recovery.img. Let me know if you
 
Let me get that, I'm a hydro user but it should work. There is no risk of bricking unless you cant type because your just flashing the recovery partition . Lol :D
 
rbheromax said:
No luck. It just loops back to system.
Click to expand...
Okay, I just looked at the ramdisk in the recovery and it's very different than what's in the stock recovery so I am going to do some switching around and when I'm done I'll post the new recovery.img.
 
Haven't forgot about you guys, just been really busy. I'll start working on cwm tomorrow.
 
Once I get enough to buy a F3 in my account I'll be up for testing out any ideas you guys have on the rise. Should be about a week or two.
 
Just figured I'd poke my head in... this thread has had multiple generations... I had the rise and got CWM to boot on it using a cwm built from the builder website and the command fastboot boot c:\recovery.img ... if I flashed it it wouldn't boot... I had the c5156 and it had the capability to boot into fastboot using a rebooter type app. the adb reboot bootloader command did not work. I flashed over recoveries from the c5155 and the hydro and they worked although had errors because some partitions are different on all three phones and the hydro has an up side down screen(or vise versa)... all of this is fact and its all in the thread but it's always good to have a refresher when a new generation picks up a thread... cheers and good luck ;)

P.S. I bricked my rise on the hunch that the boot partition was not locked like the recovery partition... it is...
 
Nobody said unlocking. Loki has been ported. Look it up. It just doesn't work but needs a code change which is what I'm doing. Djrbliss did his part. I'm doing mine.
Loki doesn't unlock but instead bypasses. Tells the BL to look elsewhere for the signature.
The BL would be aboot (mmcblk0p5) then patches modified boot.img to work with it
 
You must log in or register to reply here.
Back
Top Bottom