View Single Post
  #1926 (permalink)  
Old 09-28-2010, 12:25 AM
natemcnutty's Avatar
natemcnutty
VIP Member
Offline
 
Join Date: Nov 2009
Posts: 845
Reputation: 3070
natemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Wirelessly posted (Opera/9.80 (Windows Mobile; Opera Mini/5.1.21594/20.2479; U; en) Presto/2.5.25)

Quote:
Originally Posted by kitts
Quote:
Originally Posted by gary76usmc View Post
Ok, first off I want to say thanx to all the dev's that made Android possible on the TP2. I have been running the reference version for a week or so and today I tried to upgrade to both the new blazn and reference....neither worked. Both booted into Android...but no service. I reformatted my sdcard, change OC values, and removed OC values.........all to no avail. Put back the Android reference from 9/16...and voila....I have a working version of Android again. Has anyone else experienced these problems?
The new build has a cmd line setting in it, I think it is making the "No Service" bug.

The entry says "force_cdma=0" instead it should say "htc_hw.force_cdma=1"

You can try to use your old startup.txt(modified with the rhod400 and htc_hw.force_cdms=1 settings) and run Haret.exe.
That is correct. And if you use the launcher tool, it adds the cdma option twice in the list.
__________________
This post has been thanked 1 times.