jakeykim
New member
Wow, 500!! It sounds scary lol. Thank you for your great information and advice, colotl. Looks like yours was real HW issue.
Jake
Jake
FYI, all, I tried this and it worked fine and my 3G seems improved so far. Hopefully no one called in threats to the government from that dummy phone account while I was registered to it for 5 minutes.BTW, ESN swapping doesn't seem to require another phone. I googled it and found a page describing how to get it done. It could be risky, i don't know. -Jake
Same here. it looks like the community rom kills your phone. tried a few different radios and still nothing. ;9
Same here. it looks like the community rom kills your phone. tried a few different radios and still nothing. ;9
For me there could be something with Com Rom 1.3. I had ED01 stock but rooted. Yesterday it froze on me and wouldn't get past the Samsung logo. So I ODIN to Dl01, OTA to stock ED03. Next I followed this thread to install Community Rom 1.3 that doesn't wipe data and didn't include a modem/radio. Once I was back up and running my 3g has been dropping and coming back as described in earlier posts.
While on stock ED03 there were no 3g issues. Did I use the correct version of Com Rom (the non-data wiping/ non modem/radio version)? I haven't tried anything with ESN swaps yet. Any suggestions are appreciated.
I went to the Verizon store and asked the guy about my problem. He wasn't aware of any current 3g outage. I asked about swapping the ESN and he didn't think it would help any. So he calls up tech support and looks at some settings (which he didn't have to change), and has support look at my phone from their end. He said that they did 4 checks of things and nothing had an alarm. So I handed me back my phone and I haven't had a drop out of 3g since this afternoon. I'm not sure what was done on Verizon's end, but whatever it was, it worked. I really would like to know the cause of it in the first place and not just have some support guy magically fix it. Now I can get back to breaking the phone again and fixing it.
has anybody actually got a replacement phone and had this issue resolved?