Originally Posted by shinji257
I look forward to it. I'm running TWRP on mine but I assume at this point it is a grouper build since It is 220.127.116.11 and this thread only has a 18.104.22.168 build. I'll await your update then flash it replacing the old recovery. It seems the toolkits only install the grouper recoveries?
Well, I know that sparksco committed my patches to get TWRP to compile, so there is the possibility that there is another working tilapia build out there. The TWRP guys just added a bunch of stuff over the last week. I was kind of waiting until they finished getting it close to stable, just so I wasn't pumping out updates daily.
Even with my patches to fix the compile, I don't have TWRP working completely out of the box...the busybox in the recovery.img isn't working for some reason so I have to port over a working sbin folder by hand. But that is a very minor thing and doesn't impact how the images behave.
I also updated the CWM based on your report the other day, so thanks for that. I hadn't noticed any problems myself, but since koush had updated it seemed the thing to do.
The web builder for CWM Touch is based on the github source for CM. And since they hadn't added all the makefiles yet, it was producing a non-booting image, likely with the same binary issues. But now that tilapia roms are coming out, all those tool kits will need to add recovery. And it doesn't just build out of the box yet, so they will probably be these recoveries.
If you want to check your recovery, you can unpack it with the unpackbootimg binary in your SDK.