Syndicate
Just got my "firmware bitch" V3c...
Well, as a sort of "New Year gift", my cousin lent me her old Movilnet V3c, for my firmware crossflashing experiments.
The phone, physically is in a bad shape (lots of scratches, broken camera lens, bad speaker, and better let's don't talk about the keyboard), but at least it works, it does pick signal, and sends and receives calls/SMS.
Now, let's start flashing this sucker! (Since the phone is almost dead, i would not mind if it bricks, so i have nothing to loss, and anywyay, his owner now has another phone). It came preloaded with Movilnet' GATW_04.05.something... a FW version that has not been leaked yet. So i've tested with the only and one Movilnet monsterpack available on the net: GATW_03.18.02P. After doing my backups with RSD CDMA General 5.2.9, i flashed the thing with RSD Lite 4.4.1 (that was on a loaned laptop with Windows XP Pro). Fine, it worked!
But while restoring the service programming.. BIG PROBLEMO! The phone didn't registered with the carrier (dialing anything resulted in a "Welcome to Movilnet blah blah blah" answer machine), and after some fiddling, i've discovered the problem: phone was using NAM1, while Movilnet uses NAM2. I didn't find a way to change the active NAM via the phone menus, so i had to use QPST (2.7b310) to fix that. SUCCESS! Phone was fully working again in Movilnet! (except for data, but because the owner has a negative balance)
But since Movilnet FW is soooo boring, i decided to flash the thing to the latest Motorola DST FW (GATW_04.06.00R). Total success again 
DST has some spelling errors in MMA_UCP for Spanish menus (that can be easily fixed on MMA Advanced Editor), but it's very nice to have a 100% unbranded phone In this flash, i decided to restore the service programming using QPST (to avoid that stupid NAM2 error), but i had to use RSD General to restore the browser settings...
All nice, but DST is also sooooo lame... Now let's try something more... fun. I want Java! I want Telus! Nice, i grabbed Telus 06.04.00 update flash, and flashed the sucker with it... Oh-no... problems again! Just before starting to load the seems and files (post-flash requirements) he phone started to act weird: keyboard didn't worked, displays go crazy... like a phone with a broken flex 
Did i just bricked the phone? NOOOOOOOOO!!!!
Bah, back to home, on my own laptop (with almost the same software versions: XP Home, RSDLite 3.9.1, RSDGeneral 5.2.9, QPST 2.7b264) i flashed again back to plain DST, and the phone is again working fine. Sooooo... what's happening there? Updating DST with Telus is a bad idea? Should i use another carrier MP prior to flashing with Telus? What about another Java FW? Bell? Or those deadly Sprint MPs? I skipped the whole seem backup process, and i have no way to test if data works (remember: negative balance)...
I will have so much fun with this litte poor V3c...
(I got another semi-brick while trying to flash from Movilnet to a older DST: the flasher halted at the middle of the process, ending with a phone that only booted to bootloader... and REFUSED to pick any other FW. After rebooting the host PC, i was able to flash sucessfully)
OK, i've done more
Posted: Thu, 01/01/2009 - 21:17 by tommanOK, i've done more experiments here with that V3c...
DST->Telus = semi-brick...
DST->Bell = mostly works. No OBEX Object Push (only OBEX FTP), phone is stuck in NAM1, and even worse, i can't change it! (trying to do so on QPST ends with an error). Also, NO SEEM EDITOR works anymore with this phone when using this flash. This really, REALLY sucks
Trying to load service programming with RSD General ends with a V3c stuck in a infinite reboot loop... that can only be cured with a reflash. Java works (FINALLY!), but i don't know how the hell i can install apps there...
DST->Bell->Telus = same as Bell.
And it seems that, since Sprint never released the V3c, there are no matching monsterpacks to try.
Well, back to DST
At least the phone works with it.
Try using a DST Monster,
Posted: Fri, 01/02/2009 - 14:39 by pyde_pypperTry using a DST Monster, then go with the Alltel upgrade 4.04 or 4.06, not a Alltel Monster flash tho unless you just decide to start with an Alltel Monster and skip the DST file whihc is what I would do myself. To lastly move forward to Telus 06.04, do not use the leaked 06.08 Telus upgrade you'll end up with more troubles.
Bell is a total was of time IMO as it has less features anyways, and odds are you will not get data working with it anyways.
Currently using a Moto Q9n (A4500 Napoleon Smartphone)
______________________________________________________
Support our troop and piss on the rat bastards in D.C.
SUCCESS at least! First on
Posted: Fri, 01/02/2009 - 14:48 by tommanSUCCESS at least!
First on Movilnet: a V3c with Java
Well, after some research, i did as you: flashed the Alltel monster, then flashed Telus 06.04 over it. I restored service programming, a couple of seems, and voila, the phone is working fine
Voice/SMS are working, and since the phone has no balance, i'm unable to try data, but it should work. I did no ESN switch, neither those fancy procedures that Verizon users have to do. Score that for Movilnet crossflashers
(i'm not the first crossflashing CDMA Motos on Venezuela: a few people have flashed their E815s from Movilnet/Movistar to Bell: Movil*->AMP'd->Bell, and i even have heard of E815s CROSSFLASHED to E816!)
However, for some weird reason, i'm not able to use this phone with P2KCommander: the thing just freezes when trying to access the phone. Tried running RSD... no luck, still freezes, AND, in some cases, i even get a BSOD! (blame USBPORT.SYS, it was on ALL the BSODs that i got, and in two different computers!). Anyway, i can now upload apps using BREW Selector Editor + BitPim
Next target: Sprint V3m on my Movilnet V3m?
Yes! Glad to hear your
Posted: Fri, 01/02/2009 - 21:37 by teddyearpYes! Glad to hear your success. I tried to flash the Telus 06.04.xx upgrade on my USCC phone over the USCC V3c monster and had similar problems that you were reporting. Then, just for kicks, I re-flashed back to the USCC V3c monster, and found that DATA didn't even work then.
So, I reckon I'll have to use the Altell monster, then go from there and see what happens.
As for your p2kc problem, which version are you using? I found that for this v3c f/w's, I had to use the older p2kc 3.x.x, p2k seem, and I use RSD CDMA General 5.1.6.
thx and good luck
Also a V3m VZW->Vivo flash
Also a V9m VZW->USCC SPARKO_etc (sold)
Currently on the Moto A855 Droid
P2KCommander 4.9.E. It works
Posted: Fri, 01/02/2009 - 23:05 by tommanP2KCommander 4.9.E. It works fine with my V3m, but freezes with my V3c (and creates BSODs in rare cases). I will try with an older version...
It's weird that the Telus update only works on Alltel... DST fails, USC fails... I wonder if it will also fail on Movilnet (or Movistar or Iusacell) too
Now i'm getting another mildly-annoying issue: each time that i power up the phone i see a "Registering Applications" screen, covering the boot logo. It sometimes dissapears itself after a few seconds, while other times it quits after closing and opening the flip. During this screen, i see that the phone ATTEMPTS to connect to the data network... and fails (maybe because of the "no balance" stuff). I've thinked at first "Well, it should be the Java stuff...", but after some googling, this screen is from BREW, NOT from Java... Odd...
Huh, as for the p2kc, I have
Posted: Sat, 01/03/2009 - 08:24 by teddyearpHuh, as for the p2kc, I have the exact same results, and on the SAME phone mind you. I've been playing with a V3m, and when it's running non-VZW f/w, 4.9.E works just fine, as well as p2k05 seem, but once I put V3c f/w on it, I have to roll back to the older p2kc and p2k seem.
So, you say that the Telus update does NOT work over the DST Monster? Hmm, I'll have to remember that when I try starting up this process here in a day or three.
thanks.
Also a V3m VZW->Vivo flash
Also a V9m VZW->USCC SPARKO_etc (sold)
Currently on the Moto A855 Droid
Glad to see you were able to
Posted: Sat, 01/03/2009 - 12:33 by pyde_pypperGlad to see you were able to get it to work out. The issues with the flashes comes from the bootlaoders and chipsets of the 2 differnt phones. Also with that said you have to use the older software because of the chip set and firmware that the v3c uses. It's nothing odd and is normal. One of the reason I have all the old software and new software installed on my comps.
As for the registerig app issue yes that is a Brew problem. Here is the kicker you will never get it to go away unless you were able to flash back to a VZW firmware and then log into GIN. The problem is that the last time GIN was used or the phone was activated it couldn't find the VZW network. So now it looks for it to close the session out correctly but can not find it. It has no affect except takes longer for the phone to bootup is all.
Another FYI give up on any Brew stuff with the phone now that you have Telus running on it. Any apps or games will now have to run under Java once you get it all setup. And what I mean is just becasue you have flashed with the Telus firmware Java is not fully on the phone yet. You have to manually add all the Java stuff to the correct folder using p2kcommander. All the files can be grabbed from the Telus filesystem dump as an fyi. You also have to add the java icons and put the correct MMA files on the phone for it to function correctly. Lastly you can then add games or apps one by one, or grab and install one of the Java paks that has been put together by kbamn or Goldmembr over at Hofo.
Currently using a Moto Q9n (A4500 Napoleon Smartphone)
______________________________________________________
Support our troop and piss on the rat bastards in D.C.
Well, i suppose that i will
Posted: Sat, 01/03/2009 - 13:36 by tommanWell, i suppose that i will stay with my current "Alltel/Telus/Movilnet" hybrid for the next days
Java support is quite funky:
- it's slow (but not as slow, like GSM V3/U6)
- Installing apps/games is annoying hard, and sometimes, midlets will refuse to boot. I had to try a few times to get Opera Mini working on my V3c, but finally it worked.
- Some APIs (A.K.A. JSRs) are not supported, most notably: bluetooth, and some sound JSRs.
But it's damn better than that ca$h-cow called "BR€W"
As for "crossflashing" E815s, i've found this thread:
http://foros.cantv.net/forum_posts.asp?TID=29685 (Spanish only, sorry)
There are some users that have "upgraded" their E815s to E816 with only a simple reflash... without bricking them
Also there are some dumbasses that flashed from Movilnet to Verizon, losing OBEX in the way 
(that's what you would call a "downgrade"?)
Well, I just gotta chime in
Posted: Sat, 01/03/2009 - 22:19 by teddyearpWell, I just gotta chime in again here. I'm happier that a puppy with two peters right now. I got'er done. Used the Alltel monster -> Telus upgrade method. Then to jump start getting some Java apps on the phone I used a Java pack that kbman posted over at HoFo some time ago.
Maybe, I'll write a little guide over at my site with the files and such to do what I've done, but that's a bit down the road. I've got one little wrinkle to iron out and that is not having to redo my 1XRTT data every time I might have to power cycle my phone, but I know there's a possible seem edit to fix this. Then it's all about finishing the personalization. The only thing I might miss is the TF card slot, maybe?
The only other wrinkle is when I use the Openwave browser pointed to my HTR proxy, it comes up to BTS Sound system, pasadena, CA? Huhh??
oh well, lovin' it so far. . . . .
Also a V3m VZW->Vivo flash
Also a V9m VZW->USCC SPARKO_etc (sold)
Currently on the Moto A855 Droid
Ok, i now fixed DATA... and
Posted: Wed, 01/07/2009 - 17:49 by tommanOk, i now fixed DATA... and f*cked voice/SMS
The phone had no balance, so i recharged it, to kill the current active plan (it was a "unlimited SMS" plan), and have some $$$ to surf the web. But... it didn't worked. Neither Opera Mini nor Openwave were able to connect!
Well, in a act of... stupidity, i concluded that my flashing have done something to the settings to the phone, and decided to rewrite the AKEY (!). Movilnet AKEYs start with 20 straight zeros, but the checksum must be generated with a AKEY calculator, starting with your ESN. OK, fine, i generated a valid AKEY, and... BAM! Everything was broken: no data, no voice, no text, no nada!
Then i reflashed the crap again back to Movilnet, in hope to get the AKEY "repaired", or something... Well, this is now odd: data WORKS (Openwave connects just fine), but voice/SMS DON'T (i can't make calls or send/receive SMS, and phone drops all incoming calls). I reflashed again to the Alltel+Telus combo, and Openwave refuses to connect (it just stays waiting... and waiting... and finally it throws a timeout error). But, i was now able to connect using Opera Mini
So... My conclusions:
- I now have to pay a visit to Movilnet' CS to get my AKEY reset (this means: reflash again to Movilnet, and unlike some USA carriers, those dumbasses don't bother to fix your troubles via phone)
- Monster flashes DO NOT touch the AKEY?
- I now have data (and ONLY DATA) working... but only in Java apps
- Opera Mini rocks