Posted by on under fiber cement siding, carbide teeth, bosch power tools, nbsp nbsp nbsp nbsp nbsp, vacuum attachments, cement products, lg life, dense materials, rigorous demands, gullets, circular saw blades, rsquo, ventilated area, pricy, compas, saws, blade, amp, job | 
Recently Bosch has introduced 2 new circular saw blades specifically designed for cutting fiber cement siding and backerboard. The CB704FC & CB706FC blades are specifically designed for cutting through this tough material and also to keep dust to a minimum. One of the most common problems working with fiber cement products is the large amount of dust produced when making cuts. To combat the problem other companies have actually produced saws with vacuum attachments. This is a good solution but pricy and you end up with more tools on the job.
The new Bosch Fiber Cement Blades are much more cost effective and do a significantly better job at reducing dust when compared to traditional blades. The new blades feature less contact points and deep gullets to divert the dust. You can see in the video below the dust in a well ventilated area is kept to a minimum.
CB704FC - $50.40
4 Diamond Impregnated Carbide Teeth
Extra Long Life
CB706FC - $11.65
6 C4 Carbide Teeth
Long Life
“Professionals who cut single sheets have been looking for a cost-effective blade that can meet the rigorous demands of cutting these dense materials affordably and productively,” states Jon Howell, Product Manager, Bosch Power Tools and Accessories. “Almost everyone has a circular saw so users don’t have to buy any new equipment.”
Tagi: fiber cement siding, carbide teeth, bosch power tools, nbsp nbsp nbsp nbsp nbsp, vacuum attachments, cement products, lg life, dense materials, rigorous demands, gullets, circular saw blades, rsquo, ventilated area, pricy, compas, saws, blade, amp, job
Posted by on under george hotz, iphe |
This is NOT my release, but enough of you e-mail me about unlocking iPhones that I figured I should blog about it. Thanks to George Hotz who released this method.
So, if you're looking for how to unlock your new iPhone right out of the box (as of the 1.1.3 firmware), head to this post at The Unofficial Apple Weblog:
Software-only Unlock for iPhone
UPDATE: Zibri released an even easier unlock.
http://zibree.blogspot.com/
Tagi: george hotz, iphe
Posted by planetbeing on under large data structures, iphe, ftl, comex, iboot, redundancies, dev team, underbrush, pumpkin, pointers, insight, job |
I don't know how I was talked into reversing a FTL, but we're actually on our way. I've managed to enlist the aid of CPICH (who has been helping with the lower layers as well, he's our human HexRays) and just recently, pumpkin, who you will know from the Dev Team. pumpkin will be the heavy support that's necessary to take down _FTLRestore, which is the most complex function I've seen in 1.1.4 iBoot (and I've pretty much have seen all of it). pumpkin is very good, so this task should be now be cut down to "fairly difficult" from "completely impossible".
The strategy so far has been me methodically hacking through the functions in the order that they are called, completely decompiling them, understanding them, and assimilating them into openiboot. Toward this end, I've been working on FTL_Open, which is a fairly large (but as it turns out, boring) function, but has been useful in enlightening us on several of the large data structures FTL uses.
Meanwhile, CPICH works on functions ahead of me, so that when I reach them, a lot of the thorny underbrush has been cleared out and my job becomes much easier and faster. Toward this end, he has been working on FTL_Read, which uses the data structures that the now-completed FTL_Open should populate.
_FTLRestore is sort of a "bonus", since it's not normally called if the iPhone was shut down normally and everything is cleaned up. However, since recovering faulty data structures require all redundancies to be exploited, reversing this would let us gain a lot of insight into how the FTL works. It's also, naturally, an enormously complex function, and hence I wisely delegated it to pumpkin. =P (We will probably end up working on it together)
The one thing that troubled me was that the code we were reversing is for 1.1.4 whereas we primarily need it to work on 2.0. However, due to the fact that I had it better mapped out than the 2.0 iBoot, and the fact that the equivalent 2.0 code was much more complex (lots of function pointers flying around, and a weird switch idiom I haven't quite figured out yet), We decided to stick to the 1.1.4 iBoot.
After completing FTL_Open, I had a bit of a panic when I discovered it did not work at all on my 2.1 phone, and I could not find any obvious bugs with it. This might've meant that all our work on 1.1.4's FTL was for naught. Forgoing sleep, I tore through the 2.1 iBoot, locating the analogues to my already reversed 1.1.4 functions (I had given up trying to trace through the function pointers the first time around), and called them directly with my special version of iBoot (patched so that one of the commands was able to call arbitrary iBoot functions with arbitrary arguments). I managed to find a couple of bugs with my VFL code, and after having fixed them, FTL_Open appears to have worked. I think. It just finds and reads several data structures from NAND. It remains to be seen if I'm even reading the right thing.
Now for some sleep.
Tagi: large data structures, iphe, ftl, comex, iboot, redundancies, dev team, underbrush, pumpkin, pointers, insight, job
Posted by George Hotz on under clock cycle, iphe, google, eda, rerun, debugger, fridays, ace, cambridge, open source, demo, memory, job |
When I made the last post, I started thinking about EDA again. EDA was going to be amazing. But it suffered from cruft buildup and a lack of a good design plan. And such bad source I didn't even want to release it.
Two fridays ago, posixninja and I started talking about the design. A picture started coming together in my head. EDA 2.0; completely new code base, C++ instead of C, and a beautiful foundation.
For a quick idea of what EDA is, imagine a simulator that logs *every* state change and allows you to view the system state from any clock cycle. It's a debugger with an extra dimension. And with a really simple, IDA-like, web based frontend.
Say you are reversing a function and have no idea what it does. Run the code that calls it. Now see the data passed to and returned from the function. If you still don't know what the function does, change the input and rerun. Forget xrefs, think about viewing every time a piece of memory was accessed.
I want people to get excited about this and contribute, since I leave for my job at Google in Cambridge today and won't be able to contribute for a bit. Let's harness the power of open source to make the reversing world a better place.
See a
demo video, the
iPhone wiki entry, and
the source.
Tagi: clock cycle, iphe, google, eda, rerun, debugger, fridays, ace, cambridge, open source, demo, memory, job
Posted by blogs@bobvila.com (Greg) on under recycling bin, junk mail, phone books, doorstep, oxygen, earth, trees, blogs, job |
Having a phone book land on my doorstep is like receiving 1,000 pieces of junk mail at the same time. A tremendous waste of paper and resources. I try to be green. But I wonder how many trees were taken out of doing their job of producing oxygen for the Earth so I could get a book I put directly in the recycling bin. I often talk about recycling in my blogs and I honestly can't tell if the city is happy or not about phone book day in my town. They collect the recycling and if they sell these ...
Tagi: recycling bin, junk mail, phone books, doorstep, oxygen, earth, trees, blogs, job
