Teensy sketch for EFI and Icloud Bruteforce attack

anthonybrown123 wrote: hi any chance you can help me please

What is the problem?

I will help you but PLEAS turn the caps off.

anthonybrown123 wrote: help

That is pretty vague. Help with what?

Did you clear the PRAM?

Hey, nice work. I am glad someone found this useful. While this is not really useful to anyone now with the tools we have available at current date, i think this can be turned into an advanced brute force utility. We have had talks around this, but I just haven't seen value.

BUT...

I will make you a deal.. If you would like to continue with this I will leave the utility open source and i will contribute adding support for more devices.

I found it interesting what you said about using 2 USB ports. Are you talking about utilizing another USB port to detect the transition lines as the mac tries to boot from the device? If so, this may be pretty useful. However, I do not see a reason why we couldn't detect this from the teensy itself and use a hardware interrupt?

I have used various screens with this utility and it shouldn't be too hard to get a configurable device if you guys want to continue.

I just left a long ass reply and my session expired............

So...

The USB stick can be removed by just tieing the RX line to any digital pin and setting a hardware interrupt and creating and ISR.

OR...

You can much around with USB_COM_vect or USB_GEN_vect (for Teensy at least) to remove the need for any external USB. I have no experience in either interrupt in this case though, but it should't be too hard.

Furthermore, I feel like Teensy in this case is under utilized. I am partial to the little bugger because it is super powerful and has abundant resources. I would suggest some other tiny Arduino and just producing our own hardware design though. We could offer up the firmware and gerbers for those that want to DIY and sell assembled boards for those that don't have time for that.

How far into hardware are you? can you actually do board design etc? Because I am tired AF of just working on projects alone and wearing all the hats. I am no hardware guy, software guy, or anything else... I am just an enthusiast with the drive to create and make useful things. And was able to create a product taht helped tons of people and keep this site self-sustaining.

That unfortunately has trickled down to me paying for the site again, and spending more time maintaining than actually innovating. Also, the community is slowly transforming into a customer base instead of people who are like minded. 

Lets turn that around yea?

Great, well the code is going to depend on the hardware really, so we should start with that. I think it would be cheaper all around to use a different IC. This isn't really a job for ARM. The downside is the teensy has builtin USB communication and therefore interrupts. Others like the Atmega chips will have a FTDI or similar. Plus, for custom hardware, Teensy requires a bootloader chip who's code is proprietary. This drives costs per board up $8 right off the bat.

I guess I just need you to tell me what board or chip you would like to use (Doesn't have to be Arduino albeit it would be easier). Adn then we can move forward with design and code. 

Side note... I need someone to design the new EFI destroyer I do not have time to work on all aspects, so some help would make the release much easier and quicker.. If you are interested. Hit me on the admin email if you are interested.

I think it would be best to leverage I2C or SPI for the LCD communication. It is a bit cleaner and will leave you with more pins for future use. Not that we really have a need for it now, but forward thinking. As for the detection part, the problem is the Teensy analog pins don't have that great of a resolution so an amplifier is generally needed. I CAN and have done this through code and voltage dividers, but it is not efficient and you get really spotty readings. So i added an algorithm to do averages. This could cause the program to miss when the USB is initialized.

Just lemme know what you think and I will work on it in spare time. Just let me know what pins will be consumed and what hardware you will be choosing so I can bread board it. Not all components are created equal, so some LCD's are interfaced with differently for example.