Current OTA system?

[sicario666]

There is no full sbf for .340 at this time. The way you get to it is by installing the full .320 sbf (from that link) and then running the .340 update file. I know that's the file that put you in this state, but I think if you flash the full .320, all you files will be current except for a few system files that make up the .340 update, so that update will go smoothly. This is exactly what the dude from the other thread (http://forum.androidcentral.com/motorola-x-roms-hacks/48296-bricked-help.html) about a bricked phone (also stuck in bootoader) ended up doing today to get his back up.

ok...i'll follow what youve got posted above.

 

[sicario666]

ok... up and running now. just waiting to be signed into google's servers. SBFn to 340 didnt work for me, but an sbf to 320 did. will check for system updates and be as current as can be. Now im a happy camper.

 

[sicario666]

This is just a forewarning for anyone flashing roms...make sure the rom is .340 compatible. If not...the system will reflash back to. 320 or whatever the rom wants to make it work. This happened to me last night after I SBF'd to. 340,flashed jrummys rumm rx rom. And was magically back on. 320. Gotta love that SBF'n!

DXmeatclaws via talkatap

 

[Skatedawg]

I believe we finally concluded last night on gtalk that it was probably your ROM that was causing it to switch back to the .320. Because now your able to update it to the new version before the ROM.