Root Bootloader issues

I am often too tired to do walk throughs i rather just follow a guide so i dont bug you asking the same thing over and over again. lol

There is no guide. it's all going to be step by step. Test, if it works, next test. If that works, next test, etc.. if something breaks, try something else. It's all about learning what you can and can't do.

If you can get your own stock recovery to flash onto your phone and have it boot, I can devise a partial unbrick flashable zip for your phone.

To create temp recovery.img from recovery partition:

To pull temp recovery.img file from phone to computer as backup:

To re-flash recovery.img to recovery partition:

To remove temp recovery.img file from phone:

Turn off phone and then attempt to boot into recovery by holding Power button, and Volume Down button. When the phone vibrates, let go of the Power button but keep holding the Volume down button until recovery boots.

Disclamer: This may make it so you can't boot, or boot into your recovery. This would be a first attempt at flashing any type of firmware for this phone. Keep in mind that if it doesn't boot into recovery, or boot, you may need to take it back to your phone provider and have them fix it.

Most likely if it doesn't work, simply wipe it with:

And use Fastboot: (You'll need fastboot on your computer just like you need adb)
fastboot recovery stock_recovery.img

idk. maybe ill try later. but for now ill pass. really tired. and if i end up having to send it back ill just sell it for parts if its not recoverable on my end. the phone is out of warranty now.

Here's how they flash phil Z custom recovery on the Kyocera Hydro XTRM:
http://androidforums.com/threads/recovery-phil-z-computer-dependent.860852/

And here's a nice link to adb and fastboot commands:
http://www.rootjunky.com/learn-android/adb-and-fastboot-setup-commands/

well it might be awhile till I attempt this. i think the phone felt something was about to happen and ran away. i cant find it. and for the moment its just a WiFi Device and last i saw it i had the WiFi off. so i cant remote ring it. lol

--
nvm found it. but after finding it started feeling ehhh.. not sure again.

Yeah, dont blame you. I dont know enough myself about bootloaders except that its the code executing either OS start sequence or custom recovery. So seems to me thats were we should ve looking first butmy knowledge and luck is limited so I wont try just yet either.

Looks like they put KK on the Devs page now on http://www.kyoceramobile.com/support/developers/ They messed up the title but its there. lol

I know i haven't posted on this matter in awhile, but lately i been looking into it more. I been thinking about ways to maybe help those still stuck with boot loop but not sure if it doable for them.

Stock recovery is just entirely useless expect to clear cache and factory reset. That's if you can really call it that. From what i can tell ether way you reset it. Via recovery or from within Android all it does is a data and cache clear. But I was playing around with adb, and started to enter "adb devices" over and over again as I powered my phone on to see if it enables during boot, and it does like a few secs after the "Power by android" screen appears.

So I was thinking about the possibility if this is still happening for those boot looped. Its could be non the less a opening but a short opening, as after the boot fails it reboots. But so far attempting to do a "adb backup -f vibe.ab -system" does not seem to make good results. It completes too fast and gives me a vibe.ab file with zero file size. It seems to start backing up properly when I tell it -all instead of -system, but yeah... not what i wanna upload and publish, and it would be too big to beat the bootloop. So yea.... least my phone not being helpful at the moment. lol

The phone during boot or in recovery has no fastboot what so every or even a download mode. So there no way to use fastboot flash commands. only adb. and have to been fast about it and hope the file(s) aren't so big it take longer then the boot attempt.

I also mentioned in another post that i pulled a backup of the recovery.img from the phone tore it open along with a twrp recovery.img to compare them see whats different, everything looked the same aside from the cmdline file with slight diffs which I could of handled. but once I looked at the ramdisk archive my eyes just glossed over. But I am still trying to look at them seeing if there a way I can merge twrp into the current recovery.img backup I got and phase out the stock, then re-flash it back to the phone. But atm no where near ready to even make a prototype recovery using the original as a base and merge twrp into it, and from looking at my phone it has partitions galore and feel like it should be OK to attempt and even fail. it should still boot up, just break recovery. but too scared to temp that theory.

My only vibe is my backup, and it works still so me no risky. If I had a spare, even if it was bootlooped I still use it as a learning tool to try to recovery it, and then publish the guide once I get it back from boot loop, then move on to trying to port twrp to it. I think I might have a chance to get them out of a boot loop the more i study the issue. But again that's a might. But I don't have one. Too bad i am way too poor or i just say screw it and get the used vibe i saw on ebay for dirt cheap. but super poor so not gonna happen.