Skip to content

ABadAvatar v1.3-beta

Pre-release
Pre-release

Choose a tag to compare

View all tags
@bibarub bibarub released this 29 Aug 16:51
avatar-v1.3-beta
79e4887

What is this?

This is a fork of grimdoomer's BadUpdate v1.3 with shutterbug2000's ABadAvatar entry point ported onto it, with a few extra changes of my own.
Mainly published here to have a somewhat proper "release" before this is merged into shutterbug2000's original repository.

Note that this is still in beta. Don't expect this to work perfectly. I am not responsible for any damage done to your console.

DISCONNECT FROM THE INTERNET BEFORE RUNNING THE EXPLOIT! Otherwise you risk getting your console banned from Xbox Live and potentially lowering the success rate of the exploit.

Credits

  • grimdoomer — BadUpdate exploit
  • shutterbug2000 — ABadAvatar exploit
  • Brent — testing and some help ;)
  • Nadaman, Aris — testing

Main changes compared to ABadAvatar Public Beta 1.0

  • Rebased on top of BadUpdate 1.3. Full changelog here, but long story short, this drastically improves the success rate and speed of the exploit.
  • Renamed Stage2 and Stage3 binary files in BadUpdatePayload. What this does is preserve compatibility with other releases of BadUpdate, so you can technically have both ABadAvatar and BadUpdate on your storage device at the same time. For whatever reason.
  • Made Stage1 look for subsequent payload data on three devices: Usb0, Mu0, and Hdd (in this same order). With this, you can use the same build of ABadAvatar on these storage devices, essentially making forks like ABadAvatarHDD obsolete.

Known issues

  • The success rate of the exploit is not 100%, but around ~95%. Higher and much faster than ABadAvatar 1.0, but nowhere near perfect.
  • Having a Kinect connected on boot will dramatically lower the success rate of the exploit.
  • The ABadAvatar profile and BadUpdatePayload folder cannot be moved/deleted after the exploit has been executed.

How to use?

I would recommend following the guide at ConsoleMods, substituting the ABadAvatar files from there with this release, but for those who want a quick rundown:

  1. Make sure you have the Avatar Data from the 17559 System Update installed.
  2. Unpack the contents of the attached zip file to the root of a FAT32-formatted MBR flash drive.
  3. Put the payload of your preference on the USB stick. Usually, this would be FreeMyXe, XeUnshackle, or one of their forks.
  4. Turn off auto sign-in on the console.
  5. Disconnect your console from the Internet. Insert the flash drive and turn on the console. Once it ends up at the profile selection screen, the exploit should trigger. This usually takes somewhere around 2 seconds.
  6. Once FreeMyXe or XeUnshackle applying their patches, you can reconnect to the Internet. Note that before the next boot, you will have to disconnect from the Internet again.

Bypassing running the exploit

If you need to bypass running the exploit on console boot-up without disconnecting the storage device with it for some reason, you can do so by connecting the controller and spamming the B button as it loads into the profile selection screen.

Moving the exploit to HDD/Memory Unit

The v1.3-beta build can also be used on HDD and the external Memory Unit (the one for Phat consoles; also make sure you have it in the left slot). In order to move the exploit there:

  1. Turn on the console without the USB drive attached, or bypass exploit execution as stated in the previous section.
  2. Navigate to the Storage Settings. Insert the flash drive.
  3. Move the ABadAvatar profile from USB to HDD or Memory Unit.
  4. Reboot the console. Wait until the exploit is successful.
  5. Use Aurora, XeXMenu, or any other file manager of your preference to copy the BadUpdatePayload directory from USB to HDD or Memory Unit.
  6. Done! You'll be able to remove the BadUpdatePayload folder from USB on next boot.
Assets 3
Loading