--- SURVEY Are you satisfied with the S-D site? ---
Hello to all of you and thank you again for your loyalty,
Today I want to know if you are satisfied with the site since the change of the server and some touch-ups of the color and the change of the theme of the Forum.
Of course I am aware that there may still be work to do but the biggest part is done
Thank you for your answers
www.station-drivers.com/index.php/en/for...th-the-s-d-site#3618
NVME USB drives Realtek RTL9210/RTL9220 Firmware Version 1.xx
- sdefrwggerg
-
- Offline
- Best Poster
-
Enregistré
- Posts: 31
- Thanks: 20
- TonyP
-
- Offline
- Newbie
-
Enregistré
- Posts: 1
- Thanks: 1
- djmaniac44
-
- Offline
- Newbie
-
Enregistré
- Posts: 3
- Thanks: 3
Re: NVME USB drives Realtek RTL9210/RTL9220 Firmware Version 1.xx
1 year 2 weeks ago - 1 year 2 weeks ago
Have the same question. Most relevant settings are more or less clear and are documented here in the thread quite well...
But those 4 ones are still a miracle to me:
PINMUX1 : 0x00000000
PINMUX2 : 0x00000000
U2_MAXPWR : 0xfa
U3_MAXPWR : 0x70
Especially PINMUX1 and PINMUX12 are jumping from 0x0 for both to 7 somewere after the x.
I saw the 7 jumping in PINMUX1 or PINMUX2... Must be something relatted to Pin Multiplexing.
And as already said by user TonyP the U3_MAXPWR is sometimes 0x70 and sometime 0x00.
Maybe one of you experts have an better explanation regarding those values.
Thanks to all for this thread...
(...and of course I missed to dump my origianl settings
)
But those 4 ones are still a miracle to me:
PINMUX1 : 0x00000000
PINMUX2 : 0x00000000
U2_MAXPWR : 0xfa
U3_MAXPWR : 0x70
Especially PINMUX1 and PINMUX12 are jumping from 0x0 for both to 7 somewere after the x.
I saw the 7 jumping in PINMUX1 or PINMUX2... Must be something relatted to Pin Multiplexing.
And as already said by user TonyP the U3_MAXPWR is sometimes 0x70 and sometime 0x00.
Maybe one of you experts have an better explanation regarding those values.
Thanks to all for this thread...
(...and of course I missed to dump my origianl settings
Last edit: 1 year 2 weeks ago by djmaniac44.
Please Connexion or Create an account to join the conversation.
- djmaniac44
-
- Offline
- Newbie
-
Enregistré
- Posts: 3
- Thanks: 3
Re: NVME USB drives Realtek RTL9210/RTL9220 Firmware Version 1.xx
1 year 2 weeks ago - 1 year 2 weeks agoThanks for that - very helpfull - That makes me think about an solution to get it work with newer/latest MPTool-Versions.2. However, config serial will not appear in WMIC - if you run wmic diskdrive get name,size,model,SerialNumber command in Windows cmd, it will still show "0000000000000000" as drive serial. It is device UUID which is not possible to be changed in firmware config, but there is a way around - you can hex edit the firmware itself. UTHSB MPTool Lite ver. 1.14.8.0610 or below is required - newer versions have CRC32 check for firmware file and if you try to flash modified file it will semi-brick your device (does not work but can be reflashed without shorting pins). Save somewhere original .bin as backup, open your firmware.bin (not the GD one, you don't need to touch that at all) file in hex editor and find those 16 zeros in it - for example RTL9210B 1.32.49 firmware file has them at address 00004ea0. Replace them with anything you want (just in case better keep it the same length 16 symbols so you won't break anything else in firmware). Save, choose edited firmware file in MPTool, flash. That's it - device UUID changed and WMIC will show your new UUID if you run the command. Dump from MPTool will still show UUID as "n/a" though, that is normal.sdsdsd
Here is the way.. All in all its about faking CRC32...
Find the original CRC32 - Use CRC32-File mode anbd drop file there.
emn178.github.io/online-tools/crc32_checksum.html
For RTL9210B_v1.32.87.082923_signed.bin its 0f283ae4 - wee need it for the next step.
Modifiy your file as peer user exodus - Use Hex-Editor (HxD is easy to use) search (STRG-F) for 0000000000000000 and it jumps to those 16 digits.
Important - Overwrite those 16 digits - for example 1234567891234567. Then jump to the end of file and delete the last 4x FF - Yes - this will shorten the file! Normal not good but OK here.
Now use tool CRC-manipulator
github.com/rr-/CRC-manipulator/releases -> crcmanip-0.5.2-bin.zip -> crcmanip-gui.exe
Load your modified file (with new serial and with deleted 4x FF at the end) and use the former noted original CRC32 (for file RTL9210B_v1.32.87.082923_signed.bin its 0f283ae4) and patch it.
This will add back again 4 digits at the end with our fake CRC32 (0f283ae4).
This is the reason why I deleted those 4x FF at the end. FF means "nothing/emty/no Data" - I thing its better to keep the original filessize after patching...
You check this new patched file again with emn178.github.io/online-tools/crc32_checksum.html - It shows the same original CRC32 as file without Serial adjustments...
Maybe to much hassle for the benefit - But I like to dig deep and get things working!
Last edit: 1 year 2 weeks ago by djmaniac44.
Please Connexion or Create an account to join the conversation.
- sdefrwggerg
-
- Offline
- Best Poster
-
Enregistré
- Posts: 31
- Thanks: 20