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

[jim2561]

Originally Posted by nini1

First thing first, thank you ImCoKeMaN and team for creating these great tools for the community!

I've tried twice to run the unlocker couple times but running into "error 262" and both times i was able to recover by doing a soft reset and removing the battery but i'm not able to get further than that.

Also, i don't know if it's related or not but the ROM version i have is ~1.12 and the one the unlocker is "upgrading" to shows up as ~1.00.00, doesn't seems to be an upgrade or is it normal?

What should i do to avoid the 262 error and install the unlocker?

tell us exactly what you did and at what point it told you this as well.

are you guys following the directions to the letter?

[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.

[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?

[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!

[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.

[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>

[jim2561]

glad you guys got things worked out.

Originally Posted by nini1

...
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!

also, for all those that keep asking about this and are worried about this, yes, the version discrepancy is completely normal. it just means v1 of imcokemans rom.
whenever you flash a custom rom, it says whatever they want it so say in the ruu, so even if it doesnt say 1.12.651.1, that doesnt mean that it is downgraded, it is just the version of the custom rom builders rom.