Unlockers for Custom Roms on Vogue 2.31(GPS) and 0.40(nonGPS)

[jim2561]

Originally Posted by nini1

I'm getting that error after few minutes when the progress bar runs through the screen, everything works as per the word doc until then beside the discrepancy in the version # I've mentioned above.

you followed instructions through a command prompt right? and disconnected and reconnected the device at one time?

how far does the progress bar get?

[ImCoKeMaN]

Originally Posted by Scrotum

When I run the RUU it is saying that a connection to my device was not found. This is why I assumed i had to wait for the activesync to resume.

Do you see the bootloader screen? (looks like the one in my sig)

[nini1]

Originally Posted by jim2561

you followed instructions through a command prompt right? and disconnected and reconnected the device at one time?

how far does the progress bar get?

I'm following the instructions from the README.doc included in the Vogue_unlocker.exe folder and the problem occurs between step 6 and 7.

Am i looking at the right doc cause i don't see anything about "command prompt and disconnecting and reconnecting the device at one time?"

Also, is the Version # discrepancy normal? Mine says that it will be upgrading from 1.12 to 1.00 so i'm really not sure i'm doing the correct thing here.
Thanks for your help!

[Shaska]

Originally Posted by ImCoKeMaN

Do you see the bootloader screen? (looks like the one in my sig)

Same on my touch, I can see the first BL screen, And it gets to the screen showing UPDATE SUCCESS, and at that point I disconnect and reconnect and proceed to the next step, Windows then says its now an Unknown Device and the RUU updater can not connect so it errors out and closes... At this point Im stuck on that UPDATE SUCCESS screen till I soft reset at which it boots up as if nothing was done, So I then start all over...

EDIT: Ok so I removed my memory card, and it seemed to go through fine this time... So, All is well now, I suggest anyone having the same issue to attempt to remove their card before unlocking...
(Note: I also stopped the batch file half way and Instead of flashing the RUU included with the unlocker, I just went straight to a WM6 Rom and it flashed fine)

[ImCoKeMaN]

Originally Posted by nini1

I'm following the instructions from the README.doc included in the Vogue_unlocker.exe folder and the problem occurs between step 6 and 7.

Am i looking at the right doc cause i don't see anything about "command prompt and disconnecting and reconnecting the device at one time?"

Also, is the Version # discrepancy normal? Mine says that it will be upgrading from 1.12 to 1.00 so i'm really not sure i'm doing the correct thing here.
Thanks for your help!

Run the EXE don't open it. It will run the batch file and do the unlocking that way.

For everyone: The unlocker will load up the SPL in ram from the wm OS first. Then it will tell you to disconnect and reconnect. At that point activesync doesn't matter. The next steps in the batch file tell you it will run the RUU. The device is not unlocked until the RUU runs. This puts the hard SPL on the device and only takes a few seconds.

[Scrotum]

Originally Posted by jim2561

tell us exactly what you did, and when it told you this.

I hooked up my touch and ran the unlocker, Everything went smoothly until i was asked to disconnect and reconnect the device. I followed this direction and then the RUU ran, at this point i got an error message stating that my device was not connected.
________
Glass pipes cheap

[Scrotum]

Originally Posted by ImCoKeMaN

Do you see the bootloader screen? (looks like the one in my sig)

The bootloader that shows on my screen while im going through this progress shows 0.36 coke, but after i get the error and reset the phone the bootloader goes back to stock.
________
HotAlisa4U

[nini1]

Originally Posted by ImCoKeMaN

Run the EXE don't open it. It will run the batch file and do the unlocking that way.

For everyone: The unlocker will load up the SPL in ram from the wm OS first. Then it will tell you to disconnect and reconnect. At that point activesync doesn't matter. The next steps in the batch file tell you it will run the RUU. The device is not unlocked until the RUU runs. This puts the hard SPL on the device and only takes a few seconds.

Sorry about that, i did open the .exe and that was my problem.

I dropped No2Chem nueROM-V (WM 6.1) in your .exe file, removed the card just to be safe and everything worked like a charm!

Again, thank you very much for all your help.=D>

[ImCoKeMaN]

Originally Posted by Scrotum

The bootloader that shows on my screen while im going through this progress shows 0.36 coke, but after i get the error and reset the phone the bootloader goes back to stock.

Get an SD card that is formatted fat32 (put in card reader on pc to do this) then try the unlocker. It should say on phone to push power to load image. It's another method that might be able to fix your issue.

[JayMike]

Can I not just put the 105 build 6.1 on a memory card and flash it?