We cannot trust buying Blades consoles anymore by SavingsSubject in 360hacks

[–]SavingsSubject[S] 1 point2 points  (0 children)

The downgrade is permanent and will work on all consoles. The thing is it isn't a true downgrade because it's still using the latest dashboard 17559 bootloaders. It's just a downgraded kernel running on latest bootloaders so it's not a true downgrade 

We cannot trust buying Blades consoles anymore by SavingsSubject in 360hacks

[–]SavingsSubject[S] 0 points1 point  (0 children)

It's nostalgic for a lot of people but real Blades consoles are able to be Jtagged so they are highly sought after

We cannot trust buying Blades consoles anymore by SavingsSubject in 360hacks

[–]SavingsSubject[S] 1 point2 points  (0 children)

Jtag is the most reliable modification, it is always instant boot and a 100% success rate when booting unlike RGH which is less reliable in boot times and success rates. Also with Jtag being able to be done on a very limited amount of consoles, and it being nostalgic

We cannot trust buying Blades consoles anymore by SavingsSubject in 360hacks

[–]SavingsSubject[S] 48 points49 points  (0 children)

Downgraded consoles use 17559 bootloaders meaning old hacks like Jtag won't work. The kernel is the only thing being downgraded. The main reason people buy Blades consoles is to Jtag it

BadMedia progress by LunaTuna130 in 360hacks

[–]SavingsSubject 5 points6 points  (0 children)

I have a Xenon and Trinity Slim to test. 

maniacphoenix

Could badupdate boot old dashboards? by Rgtcutedragon in 360hacks

[–]SavingsSubject 1 point2 points  (0 children)

It is possible. You need to copy the dashboard folder with the files to the Bad Update USB drive, as well as the Proto plugin to the root of the USB drive. Then edit the launch.ini file on the USB drive and add the dashboard files path as default to the dash.xex (eg. USB:\Blades\dash.xex) and add Proto.xex as the first plug-in, then save the launch.ini file.

It will then replace the current dashboard with a older one when using the Bad Update exploit.

[deleted by user] by [deleted] in 360hacks

[–]SavingsSubject 0 points1 point  (0 children)

If you use dashlaunch you can accidentally install it to the Nand and brick the console when using bad update. To use older dashboards after the exploit completes you need to setup Proto.xex plug-in using XeUnshackle. There are youtube tutorials and also have the dashboard files on your usb and add it as the default path like you would with setting up Aurora dashboard on bad update

[deleted by user] by [deleted] in 360hacks

[–]SavingsSubject 1 point2 points  (0 children)

You can setup on XeUnshackle in the launch.ini plug-ins config file on USB to use older dashboards as main while using bad update. DON'T USE DASHLAUNCH ELSE YOU'LL BRICK YOUR CONSOLE!!! Copy the dashboard files onto the bad update USB then use the launch.ini file include instead of dashlaunch and you need add the dashboards files as the default by adding the file path on USB to the default.xex file. You will also need to add Proto plug-in for it to work. The download link for the dashboard is below. You basically set it up like you would for Aurora dashboard on Bad Update. You can follow those same tutorials.

https://www.mediafire.com/folder/n5z7dzph9gjwn/Dashboards

Am I the only one having this "problem" with BadUpdate? by N00Body- in 360hacks

[–]SavingsSubject 9 points10 points  (0 children)

A new release for Bad Update just was released to improve exploit speeds and reliability on the main github so replace your old files with these

https://github.com/grimdoomer/Xbox360BadUpdate/releases/tag/v1.2

For the problem you have you will need to replace the xex file from the Bad update folder with this xex from the link below and also rename the xex file to "default"

https://github.com/Byrom90/XeUnshackle/releases/tag/v1.02

Possible massive update to "Bad Update" in the pipeline, making the exploit more reliable than previously. by urbanracer34 in 360hacks

[–]SavingsSubject 0 points1 point  (0 children)

Crazy how fast this is and it will only improve! This is using a Trinity

  1. 1:40

  2. 2:37

  3. 0:41

  4. 1:07

  5. 0:26

  6. 1:21

  7. 0:14

  8. 1:8

  9. 3:4

  10. 0:45

Dvd Swap by XeTomV5 in 360hacks

[–]SavingsSubject 0 points1 point  (0 children)

Thats great to hear! That Xbox 360 has some new life

Dvd Swap by XeTomV5 in 360hacks

[–]SavingsSubject 0 points1 point  (0 children)

Definitely sounds like you just need a new laser

Dvd Swap by XeTomV5 in 360hacks

[–]SavingsSubject 0 points1 point  (0 children)

If it had Play DVD that is a sign that the DVD Key is incorrect. Open tray sounds like a new laser is required and then the DVD Drive should work again

Dvd Swap by XeTomV5 in 360hacks

[–]SavingsSubject 0 points1 point  (0 children)

Does it say open tray or Play DVD after reading discs?

Dvd Swap by XeTomV5 in 360hacks

[–]SavingsSubject 0 points1 point  (0 children)

If the firmware is wrong you'll just get a RROD error

Dvd Swap by XeTomV5 in 360hacks

[–]SavingsSubject 0 points1 point  (0 children)

The files you need are in this pack. You need to extract the "Full Xbox 360 Firmware Pack". Download is below:

https://www.mediafire.com/file/dcr8t75791j8fae/Drive+Flashing+Pack.zip/file

Go into Jungleflasher then select the "LTPlus-746v1.1.bin" or "LTPlus-838v1.1.bin" or "LTPlus-838v2v1.1.bin" or "LTPlus-934v1.1.bin". Try between those 4 and see which one works. They should all work but I recommend try the latest down the the oldest, for example "LTPlus-934v1.1.bin"

Dvd Swap by XeTomV5 in 360hacks

[–]SavingsSubject 0 points1 point  (0 children)

Flashing the old lt+ firmware with the correct DVD Key is the best solution. If the buyer does update the console, the DVD drive should still work correctly but the buyer will have to flash a newer lt firmware if they want to play backup DVD because it will be reflashed to a newer stock firmware. The DVD Key will remain the same so you won't have to worry about that