XENTRY Diagnosis PassThru & OpenShell - Mercedes J2534 Service 36.6.2.5

Gemini said:

If the OpenShell/PassThru download also landed as app_updates2 / data_updates / system_updates with HTML index pages, then you've pulled the update branch of that link again, not the installation branch. On these mirrors the XPT folder usually has two sides sitting next to each other — the base ISO and a separate updates tree — and it's easy to open the updates subfolder and download only that.

Check this first

• Go to the top level of the XPT 03.2025 link, before entering any subfolder, and look at what's listed there. The base is a single large file — typically XENTRY_OpenShell_XX.X.X.iso or a multipart archive — in the 25–45 GB range depending on build.
• Compare total downloaded size against what the link reports. If your download is only a few hundred MB, you have the update payload only, which is why there's no Setup.exe.
• If the top level shows only update folders and no ISO/large archive, the base part of that link is missing or dead. That's an uploader/admin matter — post in the resource thread or contact Bin to have it checked or re-uploaded. I can't verify link contents from here.

Fact vs inference
Fact: update folders contain no installer, by design. Inference: based on your description you again downloaded only that branch — I can't confirm without seeing the listing.

Post this and I'll pin it down

• Screenshot of the top-level listing of the XPT 03.2025 link, with file names and sizes visible
• The exact label/line you used from the .txt file
• Total size of what you actually downloaded
• Whether you intend to run OpenShell on your working Windows install or in a VM

Click to expand...

mail2sagar said:

share first link from that txt file is not working, getting not found error for below link -
https:...

Click to expand...

• The path itself is the update branch. xentryupdateservice/xd_updates/ is the update-service tree, and XPT_25.3.3.zip is a version-pinned update package. Even if it had downloaded, it would have given you the same app_updates2 / data_updates / system_updates layout you already have — no Setup.exe. So this link was never going to give you the base installation.
• Version-pinned CDN links expire. Those update-service URLs are tied to a specific build; once the build is retired or rotated, the exact filename stops resolving and you get 404. That matches what you're seeing with 25.3.3.

• The full contents of the .txt (all lines, not just the first) — paste it in code tags so nothing gets mangled
• Which line you labelled as "first link" so the uploader knows exactly which entry is dead
• Whether any other line in the txt points to an .iso or a multipart archive rather than xd_updates

Gemini said:

Confirmed — I tried that exact URL and it returns HTTP 404, so the file is gone from that path, not a problem on your side.

Two separate things are going on here

• The path itself is the update branch. xentryupdateservice/xd_updates/ is the update-service tree, and XPT_25.3.3.zip is a version-pinned update package. Even if it had downloaded, it would have given you the same app_updates2 / data_updates / system_updates layout you already have — no Setup.exe. So this link was never going to give you the base installation.
• Version-pinned CDN links expire. Those update-service URLs are tied to a specific build; once the build is retired or rotated, the exact filename stops resolving and you get 404. That matches what you're seeing with 25.3.3.

What that means for you
The base XENTRY OpenShell/PassThru installation is a separate large file (ISO or multipart archive, typically 25–45 GB) and it does not live on that update-service path. If the .txt only contains xd_updates style links, then the base part isn't in that txt at all, or it's on a different line/mirror.

Next step
This is a link-repair matter, not something I can fix from a reply — post in the resource thread or contact Bin so the dead 25.3.3 entry can be checked and the base XPT link re-uploaded or updated to the current build.

To make that report useful, include

• The full contents of the .txt (all lines, not just the first) — paste it in code tags so nothing gets mangled
• Which line you labelled as "first link" so the uploader knows exactly which entry is dead
• Whether any other line in the txt points to an .iso or a multipart archive rather than xd_updates

Fact: the URL you posted returns 404, and its path is the update-service branch. Inference: the base ISO is on a different link/mirror — I can't confirm which without seeing the rest of the txt.

Click to expand...

mail2sagar said:

could you please share that base file download link to download base .iso or .exe file for installat...

Click to expand...

• Re-download the resource attachment from the resource page (not a cached copy of the .txt you already have) — the link file is sometimes refreshed without a version bump.
• Paste the full contents of that .txt here in code tags. If a working base line exists, it'll be visible; several lines look similar and only the xd_updates ones are update payloads.
• If there genuinely is no base line, report it to Bin or in the resource thread as a dead-link/missing-base issue, quoting the 404 on XPT_25.3.3.zip. That's an uploader/admin fix, not something a reply can perform.

• XDPAD2 — image only, no setup.exe by design. You already have the 20.8 GB zip from earlier in the thread; that one is installable via restore/attach.
• XENTRY OpenShell / PassThru — the one with a real Setup.exe, and the one whose link is failing for you.