• 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

What you're suggesting is in some ways similar to the SafeStrap secondary bootloader that's used on cryotographically locked bootloaders used on Motorola devices, after almost 5 years some of the bootloaders have finally been cracked, I sincerely doubt that anyone would apply a similar expenditure of effort for this device unfortunately. :rolleyes:. OB
 
OverByter said:
What you're suggesting is in some ways similar to the SafeStrap secondary bootloader that's used on cryotographically locked bootloaders used on Motorola devices, after almost 5 years some of the bootloaders have finally been cracked, I sincerely doubt that anyone would apply a similar expenditure of effort for this device unfortunately. :rolleyes:. OB
Click to expand...
OB,Thanks for your response.also,do we have any proof that there IS a locked BL?also,a few posts back I saw something about edits in certain files disabling fastboot/bootloader access via key entry.if we modify those files to enable hardware key access,do you think that would get us any closer?
Edit:so I built CWM with the online recovery builder and recovery.fstab file found at one of the first posts.I replaced /dev/block/mmcblk0p15 with this file,and its still booting into stock recovery.is there something I'm missing?I replaced the stock recovery with the CWM built one,and backed up the original.why is it still booting stock recovery?
 
Alastor10009 said:
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
Click to expand...

rooting the rise has already been achieved by Bin4ry on xda you need to use pdanet+ for windows for the proper drivers for the rise though as the actual drivers dont work for that method i have a rooted kyocera rise c5156 from public mobile up here in canada
 
Is the Kyocera Event another sister phone to the rise and the hydro. Just wondering when we get recovery working on theses phones if it will work for the Event.
 
I have been looking into this for a while. The first step is preparing a version of clockworkmod specifically for the rise. Has anyone ported CWM for rise? If have a few solutions to install it from rooting other phones. Not sure if it will work but I will give it a shot.
 
We have tried to mod the stock recovery and build cwm. Neither will boot due to the locked bootloader's security checks. Feel free to try any tricks you might have.
 
ModifHigher said:
OB,Thanks for your response.also,do we have any proof that there IS a locked BL?also,a few posts back I saw something about edits in certain files disabling fastboot/bootloader access via key entry.if we modify those files to enable hardware key access,do you think that would get us any closer?
Edit:so I built CWM with the online recovery builder and recovery.fstab file found at one of the first posts.I replaced /dev/block/mmcblk0p15 with this file,and its still booting into stock recovery.is there something I'm missing?I replaced the stock recovery with the CWM built one,and backed up the original.why is it still booting stock recovery?
Click to expand...

There might be a script in the ramdisk that upon reboot overwrites the recovery (as seen on the Galaxy S3 and Galaxy Victory JB stock system, which the fix would be uncheck auto-reboot in Odin but we don't have that). you should backup your stock recovery just in case. But how did u get the img there (My guess dd)?



The script was /system/etc/install-recovery.sh on S3 and Victory (which you can just rename to install-recovery.sh.bak) and try your flash again
 
Question how did you extract stock recovery if bootloader is locked?
I extracted the system image but there was no recovery present.
I know the exact location of the recovery but I am interested in how you extracted the file?
Was the fw version 4.0.3 or 4.0.4?
The reason I ask these questions is because I have rooted and modded several different phones. Each time I took note on how root was done, cwm was added, etc. I think I may be able to use a combination of those other methods for a solution. No concrete method yet just need to retrieve recovery file.
 
can someone supply me with a stock recovery.img, i can get recovery booting today (if possible) through a bootstrap method. I bought a hydro from ebay so should be the same hardware wise, but it doesnt get to me until July 2nd and im tired of waiting.
 
well i have a down and dirty method that should work, at least boot, someone PM me if willing, its much like how the Droid Razr Maxx boots their kernels, except this will boot recovery. Wont brick as it doesnt edit anything on device, only things in RAM.
 
rbheromax said:
There might be a script in the ramdisk that upon reboot overwrites the recovery (as seen on the Galaxy S3 and Galaxy Victory JB stock system, which the fix would be uncheck auto-reboot in Odin but we don't have that). you should backup your stock recovery just in case. But how did u get the img there (My guess dd)?



The script was /system/etc/install-recovery.sh on S3 and Victory (which you can just rename to install-recovery.sh.bak) and try your flash again
Click to expand...

Go into system/etc and look for a file called install-recovery.sh because thats what prevented recovery from booting on my old optimus elite. It was the file that caused it to overwrite the custom recovery upon reboot, and it did so by using a hashsum check.
 
HaTrEd360 said:
Go into system/etc and look for a file called install-recovery.sh because thats what prevented recovery from booting on my old optimus elite. It was the file that caused it to overwrite the custom recovery upon reboot, and it did so by using a hashsum check.
Click to expand...


and then take the replacement its right in front of your face . . .
 
someone already talked about there is a second boot img so when you try and recovery img it goes back but if you get the replacement img you can chANGE AND YOU PLAY WITH THE BOOT. . .
 
But that depends on if the boot loader checks the boot partition for a signature, beyond that, how do we even know we have a locked boot loader? Other than failed recovery flashes where the recovery was prolly built wrong /:
 
Okay so I flashed boot over recovery and it boots, a little too scared to delete boot and see what's at the end of the rainbow /: should I do it?
 
As of right now Kyocera is the most bad ass manufacturer even more bad ass then me.As right now no end user including myself can unlock the bl only Kyocera simply because their security is embedded in the FW itself not phone lmfao even if one manages to unlocked the bl forementioned security will kick in and brick phone.Also speaking of security for those always think new is better its not if you update your FW you will have problems with no way to deter as its embedded in the FW itself not phone lmfao no user or system end app will fix you receiving double sms due to this
 
You must log in or register to reply here.
Back
Top Bottom