• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Flash a recovery

I don't know the phone, but I don't see anything in that post that says that you can't.
 
Which os are you trying to use it on it won't work on kitkat as it looks just 422. Locate where the bash file is
 
Are recoveries somewhat specific to phones? Flashing a recovery meant for another phone could cause an issue? Or maybe if there is another Kyo with the same basic specs as the hydro that has a recovery, maybe that would work?
 
Are recoveries somewhat specific to phones? Flashing a recovery meant for another phone could cause an issue? Or maybe if there is another Kyo with the same basic specs as the hydro that has a recovery, maybe that would work?

Yes but I know that people have been able to build a clockworkmod but have not been able to flash it and I found this even though I already bricked mine long ago I thought they might be able to flash with that.
 
Yes but I know that people have been able to build a clockworkmod but have not been able to flash it and I found this even though I already bricked mine long ago I thought they might be able to flash with that.

what the ppl are saying is that in order for a recovery to be flashed the bootloader has to be unlocked for that to happen. the bootloader checks certain things and if they dont match it reboots the phone. so as far as custom recovery its a no go. the bootloader needs to be unlocked. it checks the md5 sum and if they dont match nothing gets flashed.
 
what the ppl are saying is that in order for a recovery to be flashed the bootloader has to be unlocked for that to happen. the bootloader checks certain things and if they dont match it reboots the phone. so as far as custom recovery its a no go. the bootloader needs to be unlocked. it checks the md5 sum and if they dont match nothing gets flashed.

That doesn't seem correct to me. I thought the only thing the blocked bootloader did was prevent you from making any changes to the kernel. Don't believe it effects the ability to throw a recovery on the phone. Just limits the tweaking to the stock kernel and prevents any custom kernels. I could be wrong though.
 
trust me on the rise forums a complete recovery was built for the phone and since all the kyocera 4.0.4 phones have the same everything on the inside ithe kernel and system blocked the recovery. look into the rise forums porting cwm to the rise and its the first thing you will see. many bricked their phones trying to port it. i flashed a recovery built for the rise and it didnt boot into recovery. so the same would go for this phone. the kernel checks everything as well. theres a layer of security that we cant get through. until that is bypassed, no recovery for us
 
what the ppl are saying is that in order for a recovery to be flashed the bootloader has to be unlocked for that to happen. the bootloader checks certain things and if they dont match it reboots the phone. so as far as custom recovery its a no go. the bootloader needs to be unlocked. it checks the md5 sum and if they dont match nothing gets flashed.

I understand that but the Motorola Defy has a locked bootloader (sorta) but still has a clockworkmod. An 2nd-init style clockworkmod can be created for this phone just like the Defy.
 
That doesn't seem correct to me. I thought the only thing the blocked bootloader did was prevent you from making any changes to the kernel. Don't believe it effects the ability to throw a recovery on the phone. Just limits the tweaking to the stock kernel and prevents any custom kernels. I could be wrong though.

Your right, cause the Defy has a locked bootloader and devs figured out a way to get a 2nd-init style recovery on the phone even though now they found a way to get custom kernels with a locked bootloader
 
I understand that but the Motorola Defy has a locked bootloader (sorta) but still has a clockworkmod. An 2nd-init style clockworkmod can be created for this phone just like the Defy.
That seems to be the norm in the rest of android land as far as I know. As I mentioned before, a locked bootloader means you're locked into the stock kernel, and there won't be any original development. You can root, put on a recovery and tweak the stock ROM, but that's pretty much it.
 
That seems to be the norm in the rest of android land as far as I know. As I mentioned before, a locked bootloader means you're locked into the stock kernel, and there won't be any original development. You can root, put on a recovery and tweak the stock ROM, but that's pretty much it.

Yeah, your right, but that's only because devs haven't even layed theirs eyes on this phone and probably never will. This phone is fast after tweaked and debloated with a snapdragon s2, which is pretty good in my book, this phone deserves cm11
 
problem isnt cwm. it can be built. thing is we have no way into the bootloader. the only way is to compile a new bootloader. but even if we do it may not work due to the security checks
 
problem isnt cwm. it can be built. thing is we have no way into the bootloader. the only way is to compile a new bootloader. but even if we do it may not work due to the security checks

I know but they will alsk help in trying to unlock the bootloader.
 
we have asked kyocera to unlock it. they keep saying that they cant. and they also give us the runaround on it. they say the carrier has to unlock the bootloader and all. so with them we wont be able to get that. so idk what to do with the bootloader
 
we have asked kyocera to unlock it. they keep saying that they cant. and they also give us the runaround on it. they say the carrier has to unlock the bootloader and all. so with them we wont be able to get that. so idk what to do with the bootloader

I know that cause I asked them myself but those devs can still help us.
 
Back
Top Bottom