/diy/ - Do It Yourself

>>2699221
Funny that was my post and I also had a Zune. That was when I learned what assholes Apple users could be about anyone choosing a non-Apple product. I picked the Zune because it had more storage for the same price as the iPod and it could play WMA files, which were about half as small as MP3s, so that's what I ripped all my CDs into. Why not get more than twice as much music as I could get with an iPod? But each time an iPod owner saw me with the Zune, it was like I had shit in their mouth. They just had to come over and make a bunch of negative comments even though it wasn't their device and it didn't impact them in any way. For some reason, the very existence of something that wasn't an iPod deeply offended them.
>>2698307
>>2699198
It still can work but it's not something that would be all that useful. On much older vehicles, the keyfob sends a code specific to that vehicle. You can use a HackRF to capture that code and then replay it and open the car. Most vehicles you'll still see on the road use rolling codes, so each time you press the keyfob, it sends a new code and all old codes are invalidated. You can still open someone's car but you have to do something like this
>Be close enough to the target vehicle and the person with the keyfob to be able to jam the signal from the keyfob and receive what it was sending.
>Hope the person presses the keyfob multiple times so you can capture multiple codes.
>When you have multiple codes, before they can press the keyfob again, stop jamming and send the oldest code you received.
>The car will unlock and they'll probably just think the battery in the keyfob is weak and in need of replacement.
>Follow the person to their destination. When they get out, they'll lock the vehicle. The lock code usually isn't a rotating code and even if it were, it wouldn't be the same sequence as the unlock code.
>After they've walked away, replay one of the newer codes you captured.
>The car will unlock (just once).