Root JuopunutBear failure

[youaregreat]

So yeah, I failed at S-Off.
Phone forever would boot into, and be stuck on, the JuopunutBear screen. Now it just boots right into fastboot.
I'm able to adb myself into recovery, where its actually just sitting right now.
I'm assuming if I just restore my backup of /boot I'll be all good(ish) and can boot the phone as normal. Then try S-Off all over again, maybe.

Just want to make sure this is the right action before I really screw myself.

 

[G19]

It is likely that it will fail during the s-off procedure. All you do is rerun the program until it finally goes through. Just for future reference.

 

[youaregreat]

It is likely that it will fail during the s-off procedure. All you do is rerun the program until it finally goes through. Just for future reference.

Well, failed as in for some reason it couldn't see the device, even though it had already rebooted it into its screen. Then I stupidly closed command prompt thinking I could just reboot into Evo goodness.

 

[youaregreat]

It's always only after you post about it that all your Googling pays off.
ControlBear -r would not work, couldn't find device.
But alas, theres ControlBear -f, which you run in fastboot. Voila, I'm back in action. Hopefully my issue may help other unfortunate people in the future.

The fact that ControlBear can't seem to see my phone worries me about trying again though...

 

[G19]

did you uninstall htc sync?

 

[youaregreat]

did you uninstall htc sync?

Yeah unintalled that.

I'm now stuck at
Hmmm, still no device
Open device manager and check adb and/or fastboot drivers!!

Downloaded the full Android SDK and am now in the process of installing that, as ControlBear just sits there looping. I should have unchecked documentation as this is taking forever.
And I selected 4.1 instead of 4.0 Though I doubt that will really matter if I'm just after adb drivers.

 

[Marz001]

sounds similar to what happened to me, I never flashed stock RUU because the link was dead. controlbear -f only worked in fastboot but didn't do anything, controlbear -r always said no device while it was on the JuopunutBear screen so I couldn't get it to work.

The guys over at Unlimited.io helped me get it back. You could probably just flash the RUU in recovery, re-root, install superuser, and start the process again but I don't know if that would be best.

 

[youaregreat]

When I boot into recovery it displays

E:Bad boot message
"TIME"

No idea if this could be causing an issue...
I'm at the point where I can get through the getting beer in 4 parts or whatever it is, then just sits there trying over and over to connect. tries 45 times, fails, restarts. Over and over.

Only other thing I'm really thinking. Unlimited.IO instructions say to install HTCDriver3.0.0.007.exe When I run it, it never actually displays anything, so seems perhaps it not correctly installing. Any other way I can get the drivers installed?

EDIT:
Got the [FONT=&quot] HTC Evo V 4G Drivers.zip[/FONT]
Looking in device manager, it says I have My HTC drivers 2.0.7.8 installed.
Try to update drivers, pointing at where I extracted those, and it just tells me my drviers are already up to date

 

[youaregreat]

All fixed. Much love to kgs and hyuh at Unlimited.IO Problem seems to stem from rooted stock rom. Flashing that causes issues trying to get S-Off I'm told. Had to RUU and start all over, taking a different path (leave stock rom, apply root patch).

 

[trippin]

When I boot into recovery it displays

E:Bad boot message
"TIME"

No idea if this could be causing an issue.

For future reference I kept getting this also but I was able to soff, so anyone else who comes can ignore that message as far as I know.
It freaked me out though I thought the wire trick wouldn't work.