Related
Ok.. I just got a new XV6800. I'm a complete newbie at this.
I installed:
SPL: 2.40
ROM: 3.2.3
Radio: 3.42.30
It was a brand new phone & not activated.
Everything seemed to go ok.
I rebooted.. Had a real difficult time getting a wireless signal.. Eventually got one.. But kept getting signal lost when trying to dial *228..
Finally got it to go through.. phone reboot.. signal didn't come back..
So what did I do wrong? Any ideas how to fix it?
*sigh* I really wish you people would search the forums.
I'm not even bothering to copy/paste the explanation, all you get is a link...
http://ppc.stoleyour.net/xv6800/#signal
Actually did search but never found that link. Appreciate it. I'll follow it and hope it works for me.
P.S. I used google to search the forums as was indicated and never found the post that way.. Only one I found was
http://forum.xda-developers.com/showpost.php?p=1944961&postcount=1
which didn't help.
Shocky0 said:
Ok.. I just got a new XV6800. I'm a complete newbie at this.
I installed:
SPL: 2.40
ROM: 3.2.3
Radio: 3.42.30
It was a brand new phone & not activated.
Everything seemed to go ok.
I rebooted.. Had a real difficult time getting a wireless signal.. Eventually got one.. But kept getting signal lost when trying to dial *228..
Finally got it to go through.. phone reboot.. signal didn't come back..
So what did I do wrong? Any ideas how to fix it?
Click to expand...
Click to collapse
I think the correct sequence is:
SPL: 2.40
Radio: 3.42.30
ROM: 3.2.3
Carrier CAB
I would also suggest to activate the phone first with your carrier and make sure that the phone works before flashing it.
jambrose said:
I would also suggest to activate the phone first with your carrier and make sure that the phone works before flashing it.
Click to expand...
Click to collapse
I flashed mine before activating it and I didn't have any problems. It saved me a phone call (didn't need to call for a new A-Key).
BTW -- Thank you.. Not sure how it happened but it actually fixed itself.. I kept trying to run ##778 & EPST and it would never work.. Finally after about 20 minutes it got a signal lock but still not EPST or ##778.. I rebooted the phone and it was working & had a signal. I rebooted again and still working with a signal.. Maybe it just needed to acquire a signal once after being activated with *228
scrawnyb said:
I flashed mine before activating it and I didn't have any problems. It saved me a phone call (didn't need to call for a new A-Key).
Click to expand...
Click to collapse
Didn't think of that. Now you don't have to worry about a new A-Key again. Sweet.
scrawnyb said:
*sigh* I really wish you people would search the forums.
I'm not even bothering to copy/paste the explanation, all you get is a link...
http://ppc.stoleyour.net/xv6800/#signal
Click to expand...
Click to collapse
Exactly the link I've been looking for...been contemplating a cooked ROM flash but there is so much information all over the place its hard to figure out exactly what you need to do.
That site provides a simple, no-nonsense how-to
I'm still going to wait and see what happens with the VZW 6.1 update that is supposed to come out within the next few weeks.
Again, thanx for posting that link
deeznuts2 said:
Exactly the link I've been looking for...been contemplating a cooked ROM flash but there is so much information all over the place its hard to figure out exactly what you need to do.
That site provides a simple, no-nonsense how-to
I'm still going to wait and see what happens with the VZW 6.1 update that is supposed to come out within the next few weeks.
Again, thanx for posting that link
Click to expand...
Click to collapse
I think the wiki is really good as well and if you asked one of us nicely we could hold your hand if need be.
jambrose said:
I think the wiki is really good as well and if you asked one of us nicely we could hold your hand if need be.
Click to expand...
Click to collapse
just not out in public
So I'm sure that the majority of the people that are going to read this thread have already read about the spacing problems that people have been experiencing with 6.5. I was one of the people that flashed the first build from Da_G that had the spacing issue, and figured I would flash another rom to solve the problem.
I flashed another rom, and the problem still existed. I was getting either no spaces between words (randomly) or two spaces. No big deal, I figured, I would just flash another rom.
So I did; and I still had the problem. This was getting annoying. Back to 6.1. So I flashed to 6.1. Still the same problem. WHAT THE %&[email protected]! I thought. I guess the chef cooked in some of the 6.5 files into 6.1 or something. Now this was getting REALLY old. I needed to end it quickly.
That brings me to tonight, when I flashed the official latest at&t fuze rom straight from htc's website. I KNEW this would be foolproof. And guess what.
IT STILL HAS THE PROBLEM!!!!!!!!!!!!!!
So my question is: after flashing numerous times, and soft resetting of course, how is it possible that this problem still exists? It happened exactly after flashing the rom that everyone else had spacing problems with, and hasn't gone away.
PLEASE. Someone help me. I can't even use the device and it's getting to the point where I'm really close to just dumping it and going to get something else. I hope someone out there has the answer.
which keyboard or input are you using, I've been on Da G's, NRG's, Shep's and the latest at&t stock rom, wm6.1 and wm6.5 and don't have any issues. I have issues with input on certain areas of the TF3D2 stuff but nothing with spaces.
flyboy009 said:
which keyboard or input are you using, I've been on Da G's, NRG's, Shep's and the latest at&t stock rom, wm6.1 and wm6.5 and don't have any issues. I have issues with input on certain areas of the TF3D2 stuff but nothing with spaces.
Click to expand...
Click to collapse
I've used almost every possible configuration with everything, and the problems I am experiencing is with the hardware keyboard. But I've used the new ezinput2, old ezinput, abc, xt9, enabling and disabling auto correct and the other options, and ive also tried a cab by monx that didnt seem to work. I'm completely out of ideas. The fact that ive flashed over the original tons of times and the problem still exists RIGHT AFTER the flash, before I even touch anything, baffles my mind.
djcaston said:
I've used almost every possible configuration with everything, and the problems I am experiencing is with the hardware keyboard. But I've used the new ezinput2, old ezinput, abc, xt9, enabling and disabling auto correct and the other options, and ive also tried a cab by monx that didnt seem to work. I'm completely out of ideas. The fact that ive flashed over the original tons of times and the problem still exists RIGHT AFTER the flash, before I even touch anything, baffles my mind.
Click to expand...
Click to collapse
Is it not possibly you've just got a duff space key on your keyboard, and it's nothing to do with the ROM?
Cheers,
Steve.
StevePritchard said:
Is it not possibly you've just got a duff space key on your keyboard, and it's nothing to do with the ROM?
Cheers,
Steve.
Click to expand...
Click to collapse
Although I've thought about this, it woul be EXTREMELY strange if my space bar decided to crap out in the exact same way and at the exact same time that everyone else started having issues
djcaston said:
Although I've thought about this, it woul be EXTREMELY strange if my space bar decided to crap out in the exact same way and at the exact same time that everyone else started having issues
Click to expand...
Click to collapse
"Its like rain on your wedding day or a free ride when you already paid"
compressed air/hair dryer with a cooling switch
"its the good advice that you just didn't take and who would of thought, it figures. isn't it ironic"
k that was lame
djcaston said:
So I'm sure that the majority of the people that are going to read this thread have already read about the spacing problems that people have been experiencing with 6.5.
Click to expand...
Click to collapse
Never heard of it and have flashed 6.5 ROMs many times.
Back to 6.1. So I flashed to 6.1. Still the same problem.
.
.
That brings me to tonight, when I flashed the official latest at&t fuze rom straight from htc's website. I KNEW this would be foolproof. And guess what.
IT STILL HAS THE PROBLEM!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Yeah, no. I think what you are experiencing is a problem that your DEVICE is retaining, not a defect in each and every ROM you happen to flash. It is either something not getting flashed correctly or a hardware problem or something else that you are installing each time. If there ARE other people with this problem, get them together in a thread like this and share notes.
I havent had any space issues.
You said you've done tons of soft resets, but have you done any hard resets? If not, that is the very first thing that I would do if I were you. I suspect it's a hardware problem, but a hard reset may cure your ills. If you do this, don't run UC or install anything until you've tested the keyboard. You haven't mentioned what you do to customize your device (like run a sprite restore, lol?), but before you blame someone else, you should do a hard investigation to make sure you're not screwing things uo yourself.
As I'm sure you already know, the Custom ROM Flash tool has been modified such that it does not issue a full wipe of the flash. Therefore, it's possible that some bits are still set. When I experience such occasional anomalies, I have resolved them by applying the official HTC 5.05.405.1 WWE (6.1) stock ROM to my device.
Here's the thread:
http://forum.xda-developers.com/showthread.php?t=478657
This will downgrade/upgrade your Radio and change the Splash; you can always re-apply your personal favorites afterwards.
Once installed, I use the CWSLayout registry entry to change the keyboard and test all of the features of the device. In your situation, if the keyboard remains "broken", it's would indicate that the keyboard has somehow failed and requires replacement or servicing.
HTH,
Anyone Else Have HW Space Bar Problems?
BigBadger said:
Never heard of [the space bar problem]...I think what you are experiencing is a problem that your DEVICE is retaining...If there ARE other people with this problem, get them together in a thread like this and share notes.
Click to expand...
Click to collapse
VERY pragmatic approach!
Farmer Ted said:
You said you've done tons of soft resets, but have you done any hard resets? If not, that is the very first thing that I would do if I were you. I suspect it's a hardware problem, but a hard reset may cure your ills. If you do this, don't run UC or install anything until you've tested the keyboard. You haven't mentioned what you do to customize your device (like run a sprite restore, lol?), but before you blame someone else, you should do a hard investigation to make sure you're not screwing things uo yourself.
Click to expand...
Click to collapse
This is the advice I was going to give as well. It's recommended that you hard reset after every ROM flash once you get to screen alignment to wipe out any data that may have been retained.
fb401 said:
This is the advice I was going to give as well. It's recommended that you hard reset after every ROM flash once you get to screen alignment to wipe out any data that may have been retained.
Click to expand...
Click to collapse
Completely agree, a hard reset pre or post ROM flash is always good practice.
I've been using the following sequence (recommended by a few senior members) for several months now and results have been positive.
Hard Reset: Volume Down & Action & Reset/Power On
Hard Reset: Volume Up
Bootloader: Volume Down
Lastly, I'm not an advocate of using Backup applications in situations where different versions of ROM's are frequently flashed. It introduces too many "unknowns".
Cheers,
Do a Task 29 in mtty
I will say if you can't figure it out and your device is till under warranty, flash back to original and ask for a new one. claiming defective product.
That's really weird I had the exact same problem. I thought it was my space key, so i got a warranty replacement saying i had lost my phone, meaning I still have the old one. I will have to test when i get home and see if it was the hardware keys or something to do with the ROM. After getting a new phone I did notice my space key was a little sloppy, so I immediately assumed this was the problem. Hopefully I was wrong and have 2 working phones.
edit: nevermind forget it.
djcaston said:
So I'm sure that the majority of the people that are going to read this thread have already read about the spacing problems that people have been experiencing with 6.5. I was one of the people that flashed the first build from Da_G that had the spacing issue, and figured I would flash another rom to solve the problem.
I flashed another rom, and the problem still existed. I was getting either no spaces between words (randomly) or two spaces. No big deal, I figured, I would just flash another rom.
So I did; and I still had the problem. This was getting annoying. Back to 6.1. So I flashed to 6.1. Still the same problem. WHAT THE %&[email protected]! I thought. I guess the chef cooked in some of the 6.5 files into 6.1 or something. Now this was getting REALLY old. I needed to end it quickly.
That brings me to tonight, when I flashed the official latest at&t fuze rom straight from htc's website. I KNEW this would be foolproof. And guess what.
IT STILL HAS THE PROBLEM!!!!!!!!!!!!!!
So my question is: after flashing numerous times, and soft resetting of course, how is it possible that this problem still exists? It happened exactly after flashing the rom that everyone else had spacing problems with, and hasn't gone away.
PLEASE. Someone help me. I can't even use the device and it's getting to the point where I'm really close to just dumping it and going to get something else. I hope someone out there has the answer.
Click to expand...
Click to collapse
Had the same problem. There is a driver issue that may have caused what you're experiencing. It was discussed in the WM6.5 ROM kitchen by the chefs. I did everything you did and still had the same issues. Best fix, call AT&T and have them ship a replacement if your device is under warranty. Others have had similar issues and haven't found a solution yet. Most likely because it's a hardware failure. Wish I had better news for you.
I know it seems more than a coincident (I thought the same thing) but I've done some extensive searching and found that this is too random of an incident to blame ROMs. If it was a ROM issue, there would be a lot more people and a thread would have existed prior to yours.
If your device is under warranty, depending on where you live, there may be an AT&T Device Support Center and they carry the FUZE and will exchange the device for you. Otherwise, you'll get it in the mail in a few business days.
Cheers!
Reefermattness said:
That's really weird I had the exact same problem. I thought it was my space key, so i got a warranty replacement saying i had lost my phone, meaning I still have the old one. I will have to test when i get home and see if it was the hardware keys or something to do with the ROM. After getting a new phone I did notice my space key was a little sloppy, so I immediately assumed this was the problem. Hopefully I was wrong and have 2 working phones.
Click to expand...
Click to collapse
What do you mean by "sloppy"? can you elaborate a little? I just got my replacement yesterday (because of the same keyboard space bar issue as mentioned here) and I'm already running NRG's Latest WM6.5 ROM. So far so good.
"Apparently (as discussed in the Kitchen thread), there's an issue with the input driver of the 21812 build ROM. I'm not sure if that's the build NRG was using on 6/13, but it's very possible. So, Da_G has included the CompIME.dll from a working build (in this case, 21731) in the kitchen to correct the error, which was isolated in that thread by pyrorob. " ~Captain_Throwback~
Here's the cab compliments of Captain_Throwback...
by "sloppy" i meant that its not as springy and clicky as my replacement, so it made me think that the button had worn out from smashing it with my fat fingers so much and that's why it was bugging out! It must have been NRG 6/12 ROM that did it to my TP as well. Good to see there is a fix. Maybe my gf will let me trade her for her G1 now to add to my collection.
this is the rom i installed: http://wmpoweruser.com/?p=12886
problem is, when i click on ANY app, weather, email, internet, anything it says <application> is not a valid pocket pc application.
what gives??
figured it out. those apps don't work when connected to activesync!
edit: I take it back. only email started working. the rest of my apps still give that error.
SilverStone641 said:
figured it out. those apps don't work when connected to activesync!
edit: I take it back. only email started working. the rest of my apps still give that error.
Click to expand...
Click to collapse
if its been like that since you flashed it, id say its a bad flash. try downloading again and flashing the newly downloaded one (in case your .rar is corrupted) or give it a hard reset..may fix it up too. but it does sound like a bad flash. ive flashed on an off his 1.04 rom a few times now and have never had that issue
eh, good call. I reflashed and everything seems to be working. Man this think is smokin quick too. awesome! thank you
SilverStone641 said:
eh, good call. I reflashed and everything seems to be working. Man this think is smokin quick too. awesome! thank you
Click to expand...
Click to collapse
anytime, glad ya got er figured out..yep thats one quick rom
GOOD!
Glad to see you figured it out, this is a nice ROM and would hate to see someone not be able to enjoy its quickness and reliability. Sorry I got here late or else I would have suggested thesame, try to flash again.
You should also try Vet's rom, I alternate between the two.. they are some of the best.
Hi All,
I have been working on my first ROM for a while, based on 2.3.5 and other goodies, and i have come to readying it for install. Is there anyone out there who would know how to go about this, and/or direct me to a guide? All help is appreciated!
Id be lying if i told you I did, but this link was given to me to study and has some interesting videos:
http://forum.xda-developers.com/showthread.php?t=1250697
Good luck!
I really dont have any idea either, but I think that Fruit Cake thing might help?? Have you looked into that?
my2cents said:
I really dont have any idea either, but I think that Fruit Cake thing might help?? Have you looked into that?
Click to expand...
Click to collapse
ya, but it just wont work. Ive gone through and it only tries to pull my system, i have the entire thing packaged, but, it is just not working right. Either way, after a few failed adb attempts i am working out a return to stock with the brick.
My DNA has just started popping up the message "com.android.phone has stopped" and crashing the dialer every time I try to make a call. It worked fine for the first couple weeks I had it, and still works fine apart from making calls. 4G works and I get data. I've tried re-inserting the SIM, doing a factory reset, flashing RUU, and I just got back from the Verizon store where the swapped out the SIM. Nothing has fixed it.
Before I call the VZ warranty department I thought I'd post here and see if anyone had an idea. I'm a little worried they'll see my "Relocked/Tampered" bootloader and tell me I'm SOL. :/
Hmm...that didn't work I think there's a tread about this issues somewhere around here
sent from my beastly powered viper DNA using Tapatalk 2
holla420 said:
Hmm...that didn't work I think there's a tread about this issues somewhere around here
sent from my beastly powered viper DNA using Tapatalk 2
Click to expand...
Click to collapse
Hmm, I didn't find anything in my (admittedly brief) search. Either way, I gave up and called Verizon warranty service. The rep was very helpful and agreed to send me a new phone.
neo_1221 said:
Hmm, I didn't find anything in my (admittedly brief) search. Either way, I gave up and called Verizon warranty service. The rep was very helpful and agreed to send me a new phone.
Click to expand...
Click to collapse
Wow, it would never be that easy to get a replacement in Australia
uppon2 said:
Wow, it would never be that easy to get a replacement in Australia
Click to expand...
Click to collapse
Just to be clear, my "new" phone is actually "recertified like-new". And I have to send the old one back or pay full price for it. And if they find evidence of damage or tampering on the old phone I'll get charged $300. But yeah, aside from that it was pretty easy.
Guys, i am having the same problem! On every call i get com.android.phone has stopped ! Does anyone had the same and found a solution?!
I tried 3 custom roms(viper hatka and another one) no work, reflashed back to stock, problem remains!
I am also living overseas! Is this a problem?
Just out of curiosity, do you still have the little flap covering your microUSB port? I got annoyed with mine and yanked it out...now I'm wondering if it damaged the antenna.
I have removed it too, no way this thing can affect the operation!
It has to do with someone on you facebook or contacts has a birthday on Feb 29 find out which one it is delete the contact sync for that person or change the birthday
Thanks for the reply, have you experienced the same problem in htc DNA?
The solution you are giving is kinda strange, as i haven't passed any contacts or fb account to my mobile and the problem persists. Of course, i had done this one in the past, lets check what you just said, thanks!
ergotelis said:
Thanks for the reply, have you experienced the same problem in htc DNA?
The solution you are giving is kinda strange, as i haven't passed any contacts or fb account to my mobile and the problem persists. Of course, i had done this one in the past, lets check what you just said, thanks!
Click to expand...
Click to collapse
sorry wrong on the one I thought it was is http://forum.xda-developers.com/showthread.php?t=2076784
android.phone.acore .. again I am sorry
I also am having this problem.
I completely wiped everything and stuff as well.
Any solutions?
any resolutions?
has anyone been able to resolve this? after S-OFF, i'd hoped that flashing the new radio may work, but it didn't. i've formatted every partition and then resintalled every rom i can think of, to no avail. sucks!!
I had stock rom, unlocked, rooted, flashed viper and had the problem. Flashed different roms, the same. Returned to stock RUU, the same. Reflashed, the same. Unlocked, rooted again, and flashed viper again, and voila, the problem solved!:laugh:
ergotelis said:
I had stock rom, unlocked, rooted, flashed viper and had the problem. Flashed different roms, the same. Returned to stock RUU, the same. Reflashed, the same. Unlocked, rooted again, and flashed viper again, and voila, the problem solved!:laugh:
Click to expand...
Click to collapse
I tried this hoping it would fix com.android.phone, no luck
If RUUing doesnt help it then it might be a hardware related issue and its getting that error because the software can not communicate with the hardware... possibly? maybe? just an idea
.torrented said:
If RUUing doesnt help it then it might be a hardware related issue and its getting that error because the software can not communicate with the hardware... possibly? maybe? just an idea
Click to expand...
Click to collapse
It's not like I'm not getting a signal, I still receive txt sms. The signal cuts as soon as I try using dialer.
ergotelis said:
I had stock rom, unlocked, rooted, flashed viper and had the problem. Flashed different roms, the same. Returned to stock RUU, the same. Reflashed, the same. Unlocked, rooted again, and flashed viper again, and voila, the problem solved!:laugh:
Click to expand...
Click to collapse
I tried following what you mentioned flashed ruu and then flashed back to viper rom. So can you please tell me what I'm doing wrong?
thanks
Have you checked md5 files for your files to be sure that you have the right ones?What recovery are you using? Are you locking-unlocking etc as you have to on every step?Try it once more but be sure for all these! I personally used cwm recovery!
ergotelis said:
Have you checked md5 files for your files to be sure that you have the right ones?What recovery are you using? Are you locking-unlocking etc as you have to on every step?Try it once more but be sure for all these! I personally used cwm recovery!
Click to expand...
Click to collapse
I am using cwm and followed step-by-step. I think it maybe a hardware issue or partitions are corrupt