Monthly Archives: August 2016

ATVUSB-CREATOR

If you happened to find yourself in need of Jailbreaking the 1st Generation Apple TV over the last couple years, you might have noticed that ATVUSB-CREATOR is no longer working.

This is because the project contains hard coded links to a domain that no longer exists. That domain is GoogleCode.com, and the original project developers never bothered updating the links in the project.

I’ve taken on the task of updating the code not only for myself, but for the many others crying out for this tool to be repaired. What I thought was going to be a quick patch, has turned into the realization that there are hard coded links throughout this project, and they’re not the only issues.

The more I sift though the code, the more work I see ahead of me. I have great plans for this tool, and sure you may think it’s old, and it is, but that doesn’t mean people don’t need it anymore.

Stay tuned for project updates and a release in the coming days.

-DNA64

Advertisements

Broken Links

After a problem with my previous longtime host I was forced to move everything here (till I move my domain to my new host) and just realized the links didn’t update themselves. If you come across a broken links, just change them to match this domain.

https://dna64.wordpress.com/

I’ve already fixed quite a few, but there’s bound to be some I miss.
I’m working on it.

How to change a forgotten password on a MAC

My memory isn’t as glorious as it once was, so this is more of a mental note for my future self. That is if I can remember that I wrote it here…

This will NOT tell you the current password or allow access to the keychain (without decryption). This creates a NEW password.

Let’s begin..

Power on the MAC and immediately press and hold both the CMD and the S Key. This will boot us into a terminal window.

Now type the following commands listed in BOLD:

mount -uw /

cd users

ls

passwd accountname

Now type in your new password, and then again to confirm.

reboot

Now login to the account you changed the password for with the new password.
You’ll get a warning about the keychain, if you need to recover any data from the keychain you should ignore it and DO NOT create a new one. You can decrypt the keychain if needed using keychain dumper and view it using DB Browser for SQlite.

Done! – Easy huh?

 

Guide to “auth.json” for Necrobot 0.7.x

This is just a quick guide on how to change the default device info listed in the “auth.json” file in Necrobot 0.7.x.

First let’s take a look at the default file to get a clear comparison.
Below we can see the default contents of this file..

{
“AuthType”: “ptc”,
“GoogleUsername”: null,
“GooglePassword”: null,
“PtcUsername”: “Username”,
“PtcPassword”: “Password”,
“UseProxy”: false,
“UseProxyHost”: null,
“UseProxyPort”: null,
“UseProxyAuthentication”: false,
“UseProxyUsername”: null,
“UseProxyPassword”: null,
“DeviceId”: “8525f5d8201f78b5”,
“AndroidBoardName”: “msm8994”,
“AndroidBootloader”: “unknown”,
“DeviceBrand”: “OnePlus”,
“DeviceModel”: “OnePlus2”,
“DeviceModelIdentifier”: “ONE A2003_24_160604”,
“DeviceModelBoot”: “qcom”,
“HardwareManufacturer”: “OnePlus”,
“HardwareModel”: “ONE A2003”,
“FirmwareBrand”: “OnePlus2”,
“FirmwareTags”: “dev-keys”,
“FirmwareType”: “user”,
“FirmwareFingerprint”: “OnePlus/OnePlus2/OnePlus2:6.0.1/MMB29M/1447840820:user/release-keys”
}

I’m going to break some of this down line by line.

“AuthType”: “ptc”,

AuthType
This is asking which method of Authorization you want to use, in other words, how you want to login. It can be set to either “ptc” or “google” depending on how you setup your account. PTC stands for Pokemon Trainer Account. You can create a PTC account if you don’t already have one here

.”GoogleUsername”: null,
“GooglePassword”: null,

Here the form is asking for your Pokemon Go accounts Google Login information.
Both the Username and Password should be wrapped in “Quotes” as shown directly below.

.”GoogleUsername”: “Username”,
“GooglePassword”: “Password”,

Tip: Do NOT enter your PTC & Google Account, only enter the login credentials for one of these.

The same rules apply to entering the PTC login info as in the above example for Google.

“PtcUsername”: “Username”,
“PtcPassword”: “Password”,

Proxies
These are all related to Proxy Settings. If you don’t know what these are you can leave them as is. They’re helpful for people running several bots at once from the same IP address in avoiding a ban. You can google or search YouTube for more information about Proxies.

“UseProxy”: false,
“UseProxyHost”: null,
“UseProxyPort”: null,
“UseProxyAuthentication”: false,
“UseProxyUsername”: null,
“UseProxyPassword”: null,

Now for the part I’m sure most you were waiting for…

Device Info
Let’s start with the Device ID, because I’m going to break this down into two simple steps.

“DeviceId”: “8525f5d8201f78b5”,

Above we can see the default “DeviceId”, this is probably going to get you banned 100% if you use it, and the fact that changing it wasn’t an option in the initial setup has me very worried for many users. And is why I’m working on automating this process. But for now let’s change this using either of the steps below.

I don’t have an Android Device
If you don’t have an android device don’t worry, just fake the info using the guide below.
You will of course sill need a Device ID, so let’s grab that before you continue.

[Missing information to be updated soon! – Sorry]

I have an Android and would like to get the devices “Android ID”
Getting the Android ID is simple!
In the Google Play Store search for and download “Device ID” by “Redphx”, it’s FREE!
Once you have it installed simply launch the app, and your “Device ID” will be listed right at the top in plain sight.

Now that you have a Device ID let’s move on..
Again below we have the default settings, and again we should really change these to something more unique to help avoid increasing our chances of a ban.

“AndroidBoardName”: “msm8994”,
“AndroidBootloader”: “unknown”,
“DeviceBrand”: “OnePlus”,
“DeviceModel”: “OnePlus2”,
“DeviceModelIdentifier”: “ONE A2003_24_160604”,
“DeviceModelBoot”: “qcom”,
“HardwareManufacturer”: “OnePlus”,
“HardwareModel”: “ONE A2003”,
“FirmwareBrand”: “OnePlus2”,
“FirmwareTags”: “dev-keys”,
“FirmwareType”: “user”,
“FirmwareFingerprint”: “OnePlus/OnePlus2/OnePlus2:6.0.1/MMB29M/1447840820:user/release-keys”

Using the site https://www.androiddevice.info/devices we can get all the data we need for editing our auth.json file. Simply visit the site and search for your device. Keep the search as simple as possible or your device may not show up. Instead of searching for “Samsung Edge 7” try searching for “G935” which the part of the model number. You can find your devices model number (Device Codename) in the app “Device ID” I listed and linked to above, or under the battery or in Settings > About Phone > Model Number.

Tip: If you can’t find your device listed just use the info from a similar device.

Now let’s finish this thing and get botting!
As you can see below I’ve filled in on each line the name of the field you should look for to find this information. Some devices have the bootloader listed, most I came across don’t. You can leave this set to unknown or search for it using your Google Skills.

“AndroidBoardName”:”ro.product.board”‘
“AndroidBootloader”: “unknown”,
“DeviceBrand”: “ro_product_brand”,
“DeviceModel”: “ro.product.device”,
“DeviceModelIdentifier”: “ro_build_display_id”,
“DeviceModelBoot”: “ro_boot_hardware”,
“HardwareManufacturer”: “ro.product.manufacturer”,
“HardwareModel”: “ro.product.model”,
“FirmwareBrand”: “ro.product.name”,
“FirmwareTags”: “ro_build_tags”,
“FirmwareType”: “ro_build_type”,
“FirmwareFingerprint”: “ro_build_fingerprint”

Happy Botting!
– DNA64
twitter.com/DNA64

Pokémon Go

So for the last few weeks I’ve been rather busy and getting more exercise than usual and it’s all thanks to Pokémon Go!

Not only am I a fan of this game for obvious reasons; like the exercise and social interactions that come with it, but I also have a deep interest in the game because of the large community around the game helping document the API functions.

I’m working on a few projects based on this game, and plan on making contributions to other projects as well. I’ve already donated some beer money to at least one project, and hope to soon be able to contribute some code and bug fixes to a few others.

And now a short Rant…

Of course if Niantic had anyone working for them that knew jack shit about what the community wants then most of these 3rd party applications wouldn’t even be needed.

They talk about fairness and getting out in the real world, and I can’t help but wonder if any of them even play this god dam game. In one city there’s 130+ Pokémon in a single park. Meanwhile entire cities elsewhere have 3 f***ing Pokémon. And they wonder why people want maps and the 3-step bug fixed. Players have PokéStops and Gyms accessible from the comfort of their homes, while others don’t even have any! So I don’t blame people for GPS Spoofing. The game is extremely unbalanced and unfair period.