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

**colonel** · #**251** (**permalink**) 04-25-2008, 02:38 PM

Quote:

Originally Posted by clockcycle

Coke, this is named MFG.. Does that mean it is like the MFG bootloader on the Mogul, takes rtask cmds?

thanks,

-CC

I know you know the answer, but yes it does support rtask commands for those people who know what they are and how to use them.

bsoder · #**252** (**permalink**) 04-25-2008, 02:46 PM

Quote:

Originally Posted by colonel

I understand perfectly. The new SPL is affecting you phone. You will need to flash a rom designed for the new SPL and radio. This will fix this problem.

Ah, I think I understand. The 2.31 unlocker isn't designed to be used with the stock Verizon ROM then, it seems? I've reflashed using the older unlocker (.40 I think) and the stock ROM and things are back to normal. Thanks very much for the pointers. I didn't realize that the 2.31 unlocker wasn't a superset/replacement for the .40 unlocker.

What does SPL stand for?

Red49er · #**253** (**permalink**) 04-25-2008, 02:48 PM

In good news, I was able to get my phone to display the RUU screen, but it just sits at 0%.

Edit: The RUU fails (at 0%, after several minutes) and gives me a 262: Update Error. Going through the recovery process and getting myself back to the bootloader yields a rinse and repeat process. :/

Edit2: I've tried using the .40 unlocker, and just a standard custom rom, but the RUU always gives the same error.
In case it helps, windows can recognize my device as a wince whatever if its in the bootloader, but in any other mode its just an unknown device. This means I can run titan_exitbl.exe and it will reboot my device into normal mode (although it doesn't boot).

hoby · #**254** (**permalink**) 04-25-2008, 04:04 PM

Quote:

Originally Posted by Red49er

In good news, I was able to get my phone to display the RUU screen, but it just sits at 0%.

Edit: The RUU fails (at 0%, after several minutes) and gives me a 262: Update Error. Going through the recovery process and getting myself back to the bootloader yields a rinse and repeat process. :/

Edit2: I've tried using the .40 unlocker, and just a standard custom rom, but the RUU always gives the same error.
In case it helps, windows can recognize my device as a wince whatever if its in the bootloader, but in any other mode its just an unknown device. This means I can run titan_exitbl.exe and it will reboot my device into normal mode (although it doesn't boot).

I am having the exact same problem... BRICKED...

Red49er · #**255** (**permalink**) 04-25-2008, 04:10 PM

Anyone tried to flash the old unlocker via SDcard?

hoby · #**256** (**permalink**) 04-25-2008, 04:16 PM

I am trying with my 4gb SD Card and I am having no luck...

Red49er · #**257** (**permalink**) 04-25-2008, 04:27 PM

Yeah I can't figure out how to force it to use the one on the SD Card....I think you might only be able to flash from SD if you start in WinMo. Did you put the nbh file on ur Fat32 card and rename it to VOGUIMG.nbh? (I also have a 4gb card)

Red49er · #**258** (**permalink**) 04-25-2008, 04:58 PM

Does anyone know if we can run rtask-type commands from this stock mfg bootloader? Any links to a walkthrough would be appreciated, although a link to the software is probably enough.

jim2561 · #**259** (**permalink**) 04-25-2008, 05:18 PM

Quote:

Originally Posted by mardukeme

That is a similar problem I had, I have created a post with instructions to get you going. http://forum.ppcgeeks.com/showthread.php?t=24906

have you guys checked out/read this thread then for possible help?

**ImCoKeMaN** · #**260** (**permalink**) 04-25-2008, 06:25 PM

Quote:

Originally Posted by Red49er

Yeah I can't figure out how to force it to use the one on the SD Card....I think you might only be able to flash from SD if you start in WinMo. Did you put the nbh file on ur Fat32 card and rename it to VOGUIMG.nbh? (I also have a 4gb card)

Try using a smaller (non SDHC) card. it does need to be fat32 and in root of the SD card.