Root QPST Error (attempting to change PRL)

[Dopamin3]

So, I've been following the PRL guides. I got my MSL from stock rom and alogcat, entered echo 1 > /dev/qct_diag_enable in terminal when I was back up on CM7, and found the phone in device manager (Diagnostics Over Android COM5). When I attempt to use QPST Service Programming on the COM5 device I added, it recognizes it but then gives me this error.

anyone know what gives?

 

[rivs]

So, I've been following the PRL guides. I got my MSL from stock rom and alogcat, entered echo 1 > /dev/qct_diag_enable in terminal when I was back up on CM7, and found the phone in device manager (Diagnostics Over Android COM5). When I attempt to use QPST Service Programming on the COM5 device I added, it recognizes it but then gives me this error.

anyone know what gives?

I had the same error. Are you using Windows 7 x64? If so, the solution for me was to use QPST 2.7 Build 366. The older versions don't work well with Windows 7 x64.

 

[Dopamin3]

I had the same error. Are you using Windows 7 x64? If so, the solution for me was to use QPST 2.7 Build 366. The older versions don't work well with Windows 7 x64.

Yes I am using that. I will try build 366 thanks.

 

[Jaay Dogg]

Ok first open your device manager & see what port your phone is connecting on, then open the configurator in OPST & select add new port, then add the port your hone is on. Then open OPST programming & select read from phone it will want your MSL code. If your not seeing your phone in the device manager then install triumph drivers & if still nothing reinstall OPST.

 

[Dopamin3]

Ok first open your device manager & see what port your phone is connecting on, then open the configurator in OPST & select add new port, then add the port your hone is on. Then open OPST programming & select read from phone it will want your MSL code. If your not seeing your phone in the device manager then install triumph drivers & if still nothing reinstall OPST.

Like I said in my first post I found it on COM5 in device manager and exactly did what you're saying.

Build 366 fixed the problem