+ Reply to Thread
Page 1 of 4 123 ... LastLast
Results 1 to 15 of 56

Thread: Vuze Extreme Mod by SB-Innovation 5.0.0.1_B06 Beta

  1. #1
    Coder
    DigitalDJ's Avatar
    Join Date
    26.08.07
    Location
    Australia
    P2P Client
    BiglyBT Extreme Mod
    Posts
    633
    Activity Longevity
    6/20 20/20
    Today Posts
    1/5 ssssss633

    Vuze Extreme Mod by SB-Innovation 5.0.0.1_B06 Beta

    SB-Innovation Presents

    Vuze Extreme Mod by SB-Innovation 5.0.0.1_B06 Beta



    ╔═══════════════════════════╗
    Coded by:
    ╚═══════════════════════════╝

    >>>>>> DigitalDJ & ghostfucker <<<<<<


    ╔═══════════════════════════╗
    Credits:
    ╚═══════════════════════════╝

    >>>>>> Butcho <<<<<<
    >>>>>> Rebound <<<<<<
    >>>>>> hitman <<<<<<
    >>>>>> Manas <<<<<<
    >>>>>> eudora <<<<<<
    >>>>>> ghostfucker <<<<<<
    >>>>>> anon <<<<<<
    >>>>>> Instab <<<<<<

    ╔═══════════════════════════╗
    Supplied by:
    ╚═══════════════════════════╝

    >>>>>> SB-Innovation <<<<<<

    ╔═══════════════════════════╗
    Original Mod by:
    ╚═══════════════════════════╝

    >>>>>> Shu <<<<<<


    Change Log:

    + Perfect Spoof 2
    + uTorrent ID Generator
    + Modifiable Client Files
    + Ghostleech
    + LTEP Fixes
    + Multiple peerlist entries fixed
    + More No Report Options
    + Perfect Spoof 1.0 by ghostfucker
    + (Fake Upload) Stop faking when swarm speed is zero
    + Upload Kicker
    + Ratio Tool
    + Fixed bug preventing Vuze plugin downloads
    + Synced with latest Shu Mod
    + (Upload Multiplier) Show as seeder
    + (SBI-Hack Torrentview) Scrollbars added
    + Use Swarm Peers fixed
    + Updated core to Vuze 5.0.0.1_B06


    Vuze Change Log:
    Vuze Change Log

    Installation:
    1. Download and install Vuze (if this is a Beta/CVS update, download the latest NON BETA release) (Vuze : Java BitTorrent Client - Download).
    2. BACK UP YOUR TORRENT LIST! IT IS LIKELY YOU WILL LOSE IT!
    3. Optional: If you want to make a backup of your old Vuze version. Go to the install directory and rename Azureus2.jar to Azureus2.jar.bak
    4. Extract the files using WinRAR (WinRAR archiver, a powerful tool to process RAR and ZIP files) or equivalent to %PROGRAMFILES%\Vuze (C:\Program Files\Vuze) and overwrite ALL files.
    5. Run Vuze and Enjoy!
    NOTE: For other operating systems simply replace the Azureus2.jar. For 64-bit, portable, and Vuze Plus support read the README in the appropriate package.

    Troubleshooting:
    Before posting problems please make sure:
    1. You have updated Java Runtime Environment (JRE) to version 6 (Java SE Downloads).
    2. You have removed the Vuze folder in %PROGRAMFILES% (C:\Program Files\Vuze).
    3. You have removed the Vuze folder in %APPDATA% (The folder may be hidden).
    C:\Documents and Settings\<username>\Application Data\Vuze for XP
    C:\Users\<username>\AppData\Roaming\Vuze for Vista
    4. Reinstalled Vuze using the package from Vuze : Java BitTorrent Client - Download
    5. Re-applied the hack from the downloaded archives.

    Warning: Performing steps 2 and 3 will wipe your torrent list and Vuze settings.

    Enjoy!
    Attached Files Attached Files
    Reply With QuoteReply With Quote
    Thanks

  2. Who Said Thanks:

    Aldomz89 (12.12.13) , Hunter (28.08.13) , alehk (18.08.13) , Vation (04.08.13) , icaro96 (03.08.13) , raptive (03.08.13) , pukiman (26.07.13) , rampageman (16.07.13) , jacksbi (15.07.13) , staplesowns (06.07.13) , 12321 (02.07.13) , chroniX (30.06.13) , Blocker (29.06.13) , amit (24.06.13) , trakerdgh (22.06.13) , dreamer (13.06.13) , saebrtooth (07.06.13) , GypsyMan (04.06.13) , rebyc (02.06.13) , Snitlev (02.06.13) , eMuLeecheR (30.05.13) , cDDDe (29.05.13) , bhelmas (29.05.13) , googlesky (29.05.13) , jaybowman (28.05.13) , Paranormal (27.05.13) , takomania (27.05.13) , quertiy (26.05.13) , Sazzy (26.05.13) , Freak69 (25.05.13) , Lucius (23.05.13) , mmmmm (23.05.13) , limpep121 (22.05.13) , --->HDBD<--- (22.05.13) , arteli (22.05.13) , fataka (21.05.13) , lil-fella (21.05.13) , BrianBosworth (21.05.13) , anon (21.05.13)

  3. #2
    portable support on linux i think it's not "full" portable .. the configuration directory isn't portable at all (at least that's what i'm facing here xD" but I figured out how to solve it by passing "-Dazureus.config.path" parameter to the executable and it did work like charm !

    then I modfied the "vuze" script for linux so It launchs it portably :
    ${JAVA_PROGRAM_DIR}java "${JAVA_ARGS}" \
    -cp "${CLASSPATH}" \
    -Djava.library.path="${PROGRAM_DIR}" \
    -Dazureus.install.path="${PROGRAM_DIR}" \
    -Dazureus.script="$0" \
    -Dazureus.config.path="${PROGRAM_DIR}/Azureus.conf" \
    $JAVA_PROPS \
    $START_CLASS "$@"
    where "Azureus.conf" is the folder that has the configurations for vuze .

    and now it's full portable with me .
    Reply With QuoteReply With Quote
    Thanks

  4. Who Said Thanks:

    anon (29.05.13)

  5. #3

    Join Date
    26.04.11
    Location
    Mexico
    P2P Client
    utorrent
    Posts
    5
    Activity Longevity
    0/20 16/20
    Today Posts
    0/5 ssssssss5
    First of all, thanks for this awesome mod.
    I´d like to know where do I get the info for another u torrent version? I mean for the ut 3.1.0 the prefix is UT3100-%f8g but whats the 3.3.0 prefix?

    anon, do you remember me?
    Last edited by P4r4noid; 02.06.13 at 16:40. Reason: grammatical mistake
    Reply With QuoteReply With Quote
    Thanks

  6. #4
    Moderator anon's Avatar
    Join Date
    01.02.08
    Posts
    39,386
    Activity Longevity
    11/20 19/20
    Today Posts
    1/5 ssss39386
    Quote Originally Posted by P4r4noid View Post
    anon, do you remember me?
    I never forget those who have helped me greatly.

    The prefix follows a pattern. It's -UTxxxx-yy where xxxx is the version number without dots and padded with zeros at the right when necessary (which is always at least once). So for 3.3.0, xxxx would be 3300

    yy is two bytes holding the build number in hexadecimal, and reverse order. Build number 12345 in decimal would be 3039 in hex. Then you flip the bytes and end up with 3930. Then you have to URL-encode those as necessary. uTorrent will URL-encode any character that is not:
    • a lowercase letter from a to z
    • a uppercase letter from A to Z
    • a number from 0 to 9
    • one of these: - _ . ~ /


    Otherwise, it gets transformed into its (printable) ASCII equivalent. 39 in hex is 57 in dec, which in the ASCII table matches the character "9". 30 in hex is 48 in dec, which is ASCII character "0".

    So! The final prefix is thus: -UT3330-90 (It is not valid, just an example)

    Let's try that again with a different example.

    • Version: 2.2 Build 23456
    • First part of the prefix: 2200
    • Second part of the prefix:
      23456 dec is 5BA0 hex
      Flip the bytes: A05B
      A0 is not a printable character, so we URL-encode it
      5B is a printable character ('['), but it's not part of the exceptions I listed above, so we also URL-encode it
    • Prefix is thus: -UT2200-%a0%5b (letters from A to F are always lowercase when URL-escaped, so AB became %ab and 5B is %5b)


    But due to mild paranoia and laziness, I find it much easier to just download the build number I want and sniff an announce to get the prefix.

    If you have other questions, let me know.
    "I just remembered something that happened a long time ago."
    Reply With QuoteReply With Quote
    Thanks

  7. Who Said Thanks:

    P4r4noid (03.06.13)

  8. #5
    @anon : Wow man what an answer :) .. it's damn pro one really

    one of these: - _ . ~ /
    1. Are you sure about "/" ?
    2. We can make a small tool to make all this calculations :), I will try to make it .

    @P4r4noid : you can use smartsniff to asure that you've the right prefix .
    Last edited by Lucius; 02.06.13 at 20:38.
    Reply With QuoteReply With Quote
    Thanks

  9. Who Said Thanks:

    P4r4noid (03.06.13)

  10. #6
    Moderator anon's Avatar
    Join Date
    01.02.08
    Posts
    39,386
    Activity Longevity
    11/20 19/20
    Today Posts
    1/5 ssss39386
    Quote Originally Posted by Tattah View Post
    Are you sure about "/" ?
    I don't remember the exceptions from memory, so I opened the last uTorrent client file I wrote (for mRatio) and '/' was there. Is it wrong?
    "I just remembered something that happened a long time ago."
    Reply With QuoteReply With Quote
    Thanks

  11. #7
    could be. i've never seen the '/' as plain text, but maybe they changed it in newer utorrent releases...
    Reply With QuoteReply With Quote
    Thanks

  12. #8
    Quote Originally Posted by ghostfucker View Post
    could be. i've never seen the '/' as plain text, but maybe they changed it in newer utorrent releases...
    Give me time and I'll download the last version and check the exceptions .

    ---------- Post Merged at 20:52 ---------- Previous Post was at 20:18 ----------

    uTorrent 3.3.29677 exceptions is -._~
    Reply With QuoteReply With Quote
    Thanks

  13. Who Said Thanks:

    anon (03.06.13) , ghostfucker (02.06.13)

  14. #9

    Join Date
    26.04.11
    Location
    Mexico
    P2P Client
    utorrent
    Posts
    5
    Activity Longevity
    0/20 16/20
    Today Posts
    0/5 ssssssss5
    Thanks both of you, anon and Tattah. I´ll take the short way and will use the smartsniff as anon said.
    anon, I´m sure I can help you again so just let me know ok?
    Reply With QuoteReply With Quote
    Thanks

  15. Who Said Thanks:

    Lucius (03.06.13)

  16. #10
    Moderator anon's Avatar
    Join Date
    01.02.08
    Posts
    39,386
    Activity Longevity
    11/20 19/20
    Today Posts
    1/5 ssss39386
    Quote Originally Posted by Tattah View Post
    uTorrent 3.3.29677 exceptions is -._~
    I'll remember that for future client files

    Quote Originally Posted by P4r4noid View Post
    anon, I´m sure I can help you again so just let me know ok?
    That sounds great. I haven't seen you here in a while by the way, if you have time to chat, my PM box is open
    "I just remembered something that happened a long time ago."
    Reply With QuoteReply With Quote
    Thanks

  17. Who Said Thanks:

    Lucius (03.06.13)

  18. #11
    @anon : Can you explain your calculations with 29677 build of uT
    the prefix for it is -UT3300-%eds .. I know about the %ed but what about the "s" ?

    Thanks in advance .
    Reply With QuoteReply With Quote
    Thanks

  19. #12
    Moderator anon's Avatar
    Join Date
    01.02.08
    Posts
    39,386
    Activity Longevity
    11/20 19/20
    Today Posts
    1/5 ssss39386
    In ASCII, the lowercase 's' is stored as hex 73 (dec 115). %eds is thus the URL-encoded representation of ED73 in hexadecimal. Once you flip the bytes, it becomes 73ED which is 29677 in decimal.

    uTorrent didn't always send the build number in the User-Agent in addition to these two prefix bytes. I'm guessing they started doing that because it's easier to read/parse.
    "I just remembered something that happened a long time ago."
    Reply With QuoteReply With Quote
    Thanks

  20. #13
    ok but why the 's' didn't url-encoded and it's still as s not the %73 ?

    It have guessed because it's printable and it's a letter so we haven't to url-encode it .
    and what about the old builds that has a build number consisted of just three numbers like 1.6.1.490

    [Edit]
    ok I have finished the tool, still the support for the old uT version with just three numbers

    [Edit2]
    437 decimal is 1b5 hex so we continue with the b5 and ignore the 1 ?
    that's what I've realized .. Am I wrong ?
    Last edited by Lucius; 03.06.13 at 12:28.
    Reply With QuoteReply With Quote
    Thanks

  21. #14
    Moderator anon's Avatar
    Join Date
    01.02.08
    Posts
    39,386
    Activity Longevity
    11/20 19/20
    Today Posts
    1/5 ssss39386
    Quote Originally Posted by Tattah View Post
    ok but why the 's' didn't url-encoded and it's still as s not the %73 ?

    It have guessed because it's printable and it's a letter so we haven't to url-encode it .
    Exactly, it's one of the exceptions I listed above, so it doesn't require encoding.

    and what about the old builds that has a build number consisted of just three numbers like 1.6.1.490
    In computing, any decimal number above 255 will require at least two bytes to be represented in hexadecimal. 490 dec is 1EA hex.* You should add a 0 in front of that, since the hexadecimal numbering system doesn't at all require the amount of digits to be a multiple of two (just like we don't write 0132 instead of just 132 in decimal), but in this specific context it's required.

    So build 490 = 01EA. Flip the bytes and it's EA01. EA is 'ê', which is not in the exceptions, so it gets encoded. 01 is an unprintable character, so it also gets encoded.

    The prefix for 1.6.1 build 490 is thus: -UT1610-%ea%01

    * = Now I'm curious to see what the prefix was for pre-255 builds.

    [Edit2]
    437 decimal is 1b5 hex so we continue with the b5 and ignore the 1 ?
    I'm afraid not, see what I wrote above about padding it with a 0.
    "I just remembered something that happened a long time ago."
    Reply With QuoteReply With Quote
    Thanks

  22. Who Said Thanks:

    Lucius (03.06.13)

  23. #15
    The prefix for 1.6.1 build 490 is thus: -UT1610-%ea%01
    But the prefix for this version is -UT1610-%ea%81
    Reply With QuoteReply With Quote
    Thanks

  24. Who Said Thanks:

    anon (03.06.13)

+ Reply to Thread
Page 1 of 4 123 ... LastLast

Tags for this Thread

Posting Permissions

  • You may post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts
  •