XV6700 - Error 102 (Country Code) - Help Needed
 

I am new to this forum, but have been trying for days to upgrade my device to ANY of the AKU3.5 ROMs. (It started with me trying to make it work under Vista, but that failed misserably. So, I moved the work to an XP box and I am using that now.)

I have a Verizon XV6700 and live in Ohio.

The following have been tried and ALL give an Error 102 Country Code.
1. Helmi 3.5
2. Saridnour Custom
3. Colonel's Custom
4. Verizon Guys

My phone is running the latest Verizon patch, which I believe upgraded it to AKU 2.2 and upgraded its Radio and Extended ROMs. The filename on that upgrade (found on Verizon's site) is APAC_VZW_20720_200_11000_Ship.exe

My hunch is that the changes to the Radio are causing the Country Code problems. However, there are a lot of items added to the Extended (and improvements to Radio) that I don't want to miss when I upgrade to AKU3.5.

Is there a way that one can query the country code and change the AKUs to support that code. (This may be beyond my skill, but I am willing to play.)

Any assistance would be appreciated, as I am too much of a newbie to work around the problem.

Thank you VERY much for any help!

Bradford

P.S. I have tried both the prebuild ROM installs, and manual installs in bootloader mode. I have read here and there about doing a "Hard Reset" before you do the upgrade. How is this done on the XV6700 and do I need to write anything down ahead of time?

I'm having similar difficulties. All the ROM images I try complain with error 102 on upgrade. Also Verizon user, also with v2.2 ROM in place.

On a semi-related note, is there a way to copy the running ROM image from the 6700 to a file so that in the event everything goes to hell I can dump a "known good" ROM back onto the system?

Thanks!

Dakota Smith

You didn't mention putting the phone in bootloader mode. Have you been doing that? If not, you need to (power button + button 5 [above volume slider] + soft reset). That needs to be done before initiating the flashing process with the MAUPGRADE_NOID app.

Can't speak to miopea, but yes, my phone is in boot loader mode. It's how I got the 2.2 image on it.

It's the PC upgrade program that complains with the error message. It scans the phone and then complains and doesn't allow you to do anything other than exit the program.

Dakota Smith

I have tried the "automated" installation of the ROMs AND the method of putting the phone into bootloader mode and using the NOID app. (MaUpgrade_NoID is the application included in all of the automated updates, which I have tried running their EXE and uncompressing them and running manually.)

Well even in the automated updates, you need to put your phone ine bootloader first. That's required any time you use the MA_UPGRADE app.

That said, when you get the country code error (and exit) immediately re-run the app and try again (without touching the phone).

Barring that try a different:

1. USB Port
2. USB Cable (and try with/without the cradle)
3. Computer

It worked. Apparently, it was not happy doing the upgrade last week. I plugged in the phone and ran the upgrade and it was fine. It is just grabbing all the Verizon specific data now.

Very, very illogical process. But who cares because it works!

SAme situation and problem for me but no combination of USB cables/cradles/new ports/dif computer etc have worked for me. I am 99% sure I'm following the directions correctly regarding bootloader mode etc.

If anyone has any other suggestions, I'd love to hear them.

Edit: Wildly guessing here but has anyone got a newer XV6700 to load of any of these ROMS? Did VZ sneak something in that would throw a wrench into things recently?

I received this error when trying to install the roms from here as well. (Got a Verizon XV6700) All I did, after getting that error, was re-start the rom installer, and it would install fine the second time around.

Yeah, no luck there for me. I've tried it ~15 times over the last couple of days on various PCs. Downloading fresh files, using different cradle/cable combos plus two completely different cables/cradles. Also various number of resets/hardresets/paths to bootloader mode all with no love yet.

Will be trying more next week. Hopefully I'll catch a break and something will happen.