I think you exist in a data dead zone...:D
Sorry to hear about your problems.
Printable View
I think you exist in a data dead zone...:D
Sorry to hear about your problems.
I'm back in the Tampa area so I've got plenty of solid EVDO. My problems started when I took a 30 minute drive to Appomattox VA to play disc golf last semester and needed Mapquest for directions. Since I was back in a native VZW coverage area I hopped on the web and got the authentication failed message. Aaaaaand I've been getting that ever since.
I never had a problem with the Bell firmware, but the Alltel monster firmware still has some quirks. Once I finally get my V3m fully (As much as fully can be) functional on the Bell V3c firmware, my tinkering is done. Until my upgrade in September. :D
Famous last words. :D
Hello guys, was wondering how you load the java files on the phone. I installed the files that I could from kbmans post, when I access the icon for java the phone no longer crashes. Would you please explain how to load the java files on the phone? You are most wonderfull and smarter than I could ever think of being, you are also probably better looking. PLEASE! I just want to see what the Java noise is all about.
Kbman may have an updated edition of his app pack, so I'll hold off on posting a link. For installing you simply use Bitpim to restore the zip file to the /brew/mod/jeodek/ folder.
I just read the entire thread on the Bell K1m and I think there are some valuable bits of information there that will carry over for the V3c. For instance, making and loading a modified 275a seem to unlock some Bell data seems. One thing preventing me from furthur experimentation is the lack of tethering with Bell. I never saw if they unlocked the 1xRTT address under Security>Data Connections. It seems like the Bell K1m thread is dead with the release of a Telus K1m firmware.
anyone figure out phone to phone bluetooth with the bell v3c firmware
That would be OPP... which in post #10, GoldMembr says this doesn't have.Quote:
Originally Posted by GP-SE
opps didn't see that.Quote:
Originally Posted by Mark_Venture
So going from the Alltel v3c works, eh?
These VZW to Java flashes are getting easier and easier, arn't they? :)
Quote:
Originally Posted by Stephen Soulsby
So do we have working data or no? and do we basicly follow the steps from the k1m bell conversion? I want this so bad and I am willing to take a shot but I want to know how far we are, I can live without web and mms, but I need any information you guys can give.
GoldMembr has reported that everything works except for DUN and the VZW native proxy.
That means that this is just as functional as the Bell e815 flash.
There is no definitive writeup yet so you still have to basically follow the other Java conversion threads.
There are differences between the V3c and the K1m that will impact this procedure so be aware.
so would it be closer to follow the e815 write up or the telus one that mark has for the k1m? with obvious differences for both.
Yes, the e815 is really much closer to the Bell V3c in terms of it's internal nvm and file system.
The problem is that Evade's guide is specifically tailored to the e815 so you need to manually add the Java elements to the file system rather than using the flex provided by evade for the e815.
The basic procedures and required components are the same.
could someone help me out? i have my phone flashed to bell, i have java working perfectly, but i cant get the damn outer gif to what i want. i tried editing 275a,2771,and 2772 seems, and placed the .gif on the phone. all i get is the moto gif. why is the litlle things sometimes so hard to figure out? a little help would be appreciated. thanks