Quote Originally Posted by julianof View Post
That's what the window reports

Spoiler: Screen gps
[Only registered and activated users can see links. ]
Good, that's what i was hoping it was. Not an error message.

Spoiler: G7toWin
[Only registered and activated users can see links. ]
I know the HWID would be reported by G7ToWin as 1106 now, but what i asked was this: "Post to confirm that you used G7ToWin to obtain HWID of 1106 before you attempted any flashing with Updater.exe".
Are you able to state 'yes' definitely to that or not?

The reason for asking is that there are 2 different hardware versions of 12xx with HWIDs of 1106 and 0971 running different firmwares. Flashing the other's fw, original or cure, will change the HWID but the device won't ever function as it should with wrong fw. I'm wanting to eliminate any chance at all that's happened. If you're not sure 100% that your device was always HWID 1106 please say so and then we can look further. I'd prefer know with certainty if the HWID was or wasn't changed inadvertently of course.

Drivers version: 2.3.1.2
Latest version so that's not the problem.

Updates correctly but does not recognize it as a drive
I'm assuming you mean after using QuickCure3 the device still isn't recognised in Windows Disk Management or File Explorer.

So flashing QC3 doesn't also result in the IOU message you saw from Updater when using Cure3?
PC(W11) and notebook(W7). On PC rear USB ports
.............
Two different cables, one longer and one shorter.
Ok, very unlikely the comms issue is due to any of those then.

In "2-" of your initial post you mentioned that you tried flashing boot.bin only as an RGN and "Windows recognizes it but does not assign a letter to the drive". Please clarify which you mean: (i) it was seen only in Device Manager; or, (ii) it was seen in Disk Management but without a drive letter allocated?

Please answer all the 3 questions underlined. Be as accurate and informative as you can. If unsure just say that but don't guess.