ok heres the my situation. Before the the upgrade to xda live, wifi worked perfectly, after upgrade to xda live, wifi will not search mine or any nearby networks. Next i flashed vanilla successfully to see if that fixes the problem, it didnt! Then I downgraded to 2.06 att rom, that didnt fix the problem. Lastly I downgraded to 1.34 and once again, Wifi will not search for networks. Its seems to only do a half a sec scan then it stops completely. Can anyone help please!
princeasi said:
ok heres the my situation. Before the the upgrade to xda live, wifi worked perfectly, after upgrade to xda live, wifi will not search mine or any nearby networks. Next i flashed vanilla successfully to see if that fixes the problem, it didnt! Then I downgraded to 2.06 att rom, that didnt fix the problem. Lastly I downgraded to 1.34 and once again, Wifi will not search for networks. Its seems to only do a half a sec scan then it stops completely. Can anyone help please!
Click to expand...
Click to collapse
I have a somewhat similar issue. I thought it might have been a combination of upgrading to the new OS and the 1.35 radio. Before I was using 1.27. Maybe you can try flashing back to that radio.
Or at least it might be worth trying.
well i did try flashing back to the xda live but it still didnt help, also ive always kept the 1.16 radio! If i cant solve this thru xda, I may have to do XBM!
What might XBM be ?
princeasi said:
ok heres the my situation. Before the the upgrade to xda live, wifi worked perfectly, after upgrade to xda live, wifi will not search mine or any nearby networks. Next i flashed vanilla successfully to see if that fixes the problem, it didnt! Then I downgraded to 2.06 att rom, that didnt fix the problem. Lastly I downgraded to 1.34 and once again, Wifi will not search for networks. Its seems to only do a half a sec scan then it stops completely. Can anyone help please!
Click to expand...
Click to collapse
There is a reg entry for allow scan time. Maybe it is set to low for your wifi to pick up a router.
cyberdrakula said:
What might XBM be ?
Click to expand...
Click to collapse
XBM: Exchange by mail
The problem with this is technically your warranty is void, this is why Cingular and MS are mad at XDA. We mess with the device and still try to claim warranty.
wpbear said:
There is a reg entry for allow scan time. Maybe it is set to low for your wifi to pick up a router.
Click to expand...
Click to collapse
if it was a reg entry wouldnt that be set to default after installing the cingular rom 1.34??
wpbear said:
XBM: Exchange by mail
The problem with this is technically your warranty is void, this is why Cingular and MS are mad at XDA. We mess with the device and still try to claim warranty.
Click to expand...
Click to collapse
The only reason why i would xbm on this occasion because this possibly could be hardware issue! So im tryin to troubleshoot thru xda to see if i can narrow it to a software issue.
princeasi said:
if it was a reg entry wouldnt that be set to default after installing the cingular rom 1.34??
Click to expand...
Click to collapse
Yes but this a MS product so anything is worth checking.
princeasi said:
The only reason why i would xbm on this occasion because this possibly could be hardware issue! So im tryin to troubleshoot thru xda to see if i can narrow it to a software issue.
Click to expand...
Click to collapse
I am not going to hyjack this thread, but even if it wasnt anything you did, you still voided the warranty and this is why Cingular and MS are getting mad at XDA. I am not saying I wouldnt consider doing an XBM either, I am just being the devils advocate here.
wpbear said:
I am not going to hyjack this thread, but even if it wasnt anything you did, you still voided the warranty and this is why Cingular and MS are getting mad at XDA. I am not saying I wouldnt consider doing an XBM either, I am just being the devils advocate here.
Click to expand...
Click to collapse
oh I understand, i wasnt being defensive, i just thru that out there because i dont want other readers to get the wrong message from me, but you're right tho! BTW, would u or any of you happen to know that reg hack? would love to apply to see if solves my prob!
Actually, have you installed WiFiFoFum? This has all the options available. If you still get nothing, I bet hardware.
ok ill try that and post back results, wish me luck!
I have the same problem with just regular Vanilla though. I even tried WiFiFoFum and it didn't pick up anything. I don't even see a gprs connection. This all worked fine in WM5. Should I go back?
EDIT: Just installed XDA Live and now my wifi works again. Weird.
ok just tried using wififofum with xda live and still no network scan. Next i downgraded to 1.34, and its the same thing! The only upgrades performed on my phone were xda live, vanilla, 2.06. I never upgraded the radio or anything else! As you can see, I've done safe upgrades, and all were successful. Anything else out there that i can safely try to resolve this problem???
I'm still working on fixing this problem, but I have a question. I've read on different post that uprgarding wiith vanilla or xda live doesn't touch anything but the os on the phone, so if I'm rationalizing correctly this type of upgrade could not have possibly tampered with my wifi providing that I've never tried flashing the radio, bootloader, and that all flashing were successful, correct?
princeasi said:
I'm still working on fixing this problem, but I have a question. I've read on different post that uprgarding wiith vanilla or xda live doesn't touch anything but the os on the phone, so if I'm rationalizing correctly this type of upgrade could not have possibly tampered with my wifi providing that I've never tried flashing the radio, bootloader, and that all flashing were successful, correct?
Click to expand...
Click to collapse
The radio ROM has nothing to do with the Wifi. It sounds like your wifi is DEAD. Try a flash to original ROM SHIPPED RUU from when you bought the device. That will make it like "NEW" if it is still dead, you are screwed, time for warranty.
wpbear;1157460 said:
The radio ROM has nothing to do with the Wifi. It sounds like your wifi is DEAD. Try a flash to original ROM SHIPPED RUU from when you bought the device. That will make it like "NEW" if it is still dead, you are screwed, time for warranty.
Click to expand...
Click to collapse
actually that's how I discovered something was wrong, when I flashed back to the original because I thought it was xda live that was causing the wifi not to work correctly. After discovering that it was not working with the factory rom, I then tried flashing vanilla, and still its the same results! so from what you have confirmed with me is that more than likely hardware. XBM here I come! I've even tried troubleshooting with cingular CS, and I immediately turned down the assistance once he stated that the wifi wasn't working correctly because of the wrong data plan linked to my account lollll. How funny is that!
You may be screwed; http://forum.xda-developers.com/showthread.php?t=299451
Seems there is no fix for this at the moment if the above has happened.
Related
I've searched and didn't find an answer on this so if it has been asked and answered I apologize.
Since Sprint and HTC have released a ROM update will Verizon be following suit?
My phone is a daily worker and I can't afford to spend the time with trial and error on DCD's ROM, although it is very tempting.
Thanks
Dbl_Tap said:
I've searched and didn't find an answer on this so if it has been asked and answered I apologize.
Since Sprint and HTC have released a ROM update will Verizon be following suit?
My phone is a daily worker and I can't afford to spend the time with trial and error on DCD's ROM, although it is very tempting.
Thanks
Click to expand...
Click to collapse
I myself haven't seen any official confirmation or even hinting from VZW that they're releasing an upgrade. Sprint announced it what, back in October? I'd imagine if VZW was going to follow suit we would've heard something by now. I'm gonna check a few sites and see what I can find.
Was wondering the same thing earlier today.
I doubt it...
I asked a second level support tech that yesterday and he didn't know anything about it - but that is not a surprise to me...
Its fairly common knowledge in some circles that VZW is very secretive (or maybe they just dont let their ppl know) about this stuff.
I imagine an update is indeed in the works, but nobody you talk to at VZW will have any knowledge. Those familiar with VZW and updates also know that it will probably be some time after the other carriers have their updates out. Slow and steady must be their motto...
Why wait? Trial and error with DCD's rom? Load and go.
I'm with Sprint and can't even see myself ever running a stock ROM again.
digiblur said:
Why wait? Trial and error with DCD's rom? Load and go.
I'm with Sprint and can't even see myself ever running a stock ROM again.
Click to expand...
Click to collapse
We haven't, but there are a few little nagging issues that might be resolved by a stock ROM from Verizon w/ GPS and Rev A.
For me, anytime I run a *228, my phone goes into the 20 minute acquiring signal dance. I hate that beat.
After reading through 50+ pages in the regular ROM and the 4 pages on VZW I'm holding off because of some of the smaller problems people are having with wifi, MMS, bluetooth, etc.
I'm the kind of person that if there is a 1% chance of it happening it will happen to me and I can't afford to be without my phone.
Plus it is still a bit confusing with the radio stuff, loading 2.40 unlocker first, it gets a bit much for a dabbler like myself.
Maybe if there was a very simple cut & dried walk through of what you need to do to prepare/download/install then load I'd do it.
Heck, I didn't even know what the hell a 'kitchen' was in regards to a ROM when I first got the XV6800 and I've been a smartphone/pocket pc guy for a long time
It is very very easy to go back to the stock verizon rom and radio as well as the original bootloader if you have any of these problems....but as I've said in other threads....I've flashed 3 phones now with absolutely none of the problems you've mentioned.
In that case could you point me to the best walk through on doing it including what I need (bootloaders etc)? I've seen so many that make it seem like defusing an atomic bomb and then other that just say "run it & git er done' so I don't know which to follow.
Thanks so much
Dbl_Tap said:
In that case could you point me to the best walk through on doing it including what I need (bootloaders etc)? I've seen so many that make it seem like defusing an atomic bomb and then other that just say "run it & git er done' so I don't know which to follow.
Thanks so much
Click to expand...
Click to collapse
Search my posts. I made a good one step by step last night.
Man you have a ton of posts to search through I think I found the right one.
So you've got MMS working no problem? I use MMS all the time and don't want to loose it like some people have.
Your steps seem to involve already using a cooked ROM are the steps the same for a 'virgin' xv6800?
Dbl_Tap said:
Man you have a ton of posts to search through I think I found the right one.
So you've got MMS working no problem? I use MMS all the time and don't want to loose it like some people have.
Your steps seem to involve already using a cooked ROM are the steps the same for a 'virgin' xv6800?
Click to expand...
Click to collapse
The only additional step for a virgin xv6800 is that you need to install Olipro 2.40 unlocker first. Be sure to turn off USB in ActiveSync when done and the phone will boot back into the OS. You can then run the Sprint update (DO NOT LET THE SPRINT CUSTOMIZATIONS RUN!) followed by the cooked DCD ROM.
Be sure to check off MMS when cooking the ROM. If you don't see it, DCD left it out and you might have to find the OEM from an older version (it was left out of 3.0.0) My old GF from when I was 14 found me on MS monday and used MMS to send me old pics yesterday....it works. ;D
Dbl_Tap said:
Man you have a ton of posts to search through I think I found the right one.
So you've got MMS working no problem? I use MMS all the time and don't want to loose it like some people have.
Your steps seem to involve already using a cooked ROM are the steps the same for a 'virgin' xv6800?
Click to expand...
Click to collapse
I have a 'virgin' xv6800 enroute. It should arrive Thursday or Friday. My first task will be to see if I can get GPS working. I'm a veteran Kyocera 6035, then 7135, followed by a Treo 650 but reading about cooking the ROM, etc is truly virgin territory!
Can you post the link to the post you found? Thanks!
I know verizon isn't exactly known for giving it's users new featured readily but my guess on this is they WILL eventually offer an updated patch with this GPS and RevA so they can rent you VZNavigator on a monthly basis.
But expect them to disable normal satellite tracking and limit it to AGPS reception so your forced to use VZNav and not Google Maps!
gcincotta said:
It is very very easy to go back to the stock verizon rom and radio as well as the original bootloader if you have any of these problems....but as I've said in other threads....I've flashed 3 phones now with absolutely none of the problems you've mentioned.
Click to expand...
Click to collapse
Very easy? Would you point me in the right direction on where to find the original radio rom, as well as the OS rom? From what I understand to get back to the original bootloader, you just have to use the titan relock, right?
daniel981 said:
Very easy? Would you point me in the right direction on where to find the original radio rom, as well as the OS rom? From what I understand to get back to the original bootloader, you just have to use the titan relock, right?
Click to expand...
Click to collapse
Search my posts from yesterday. Posted a guide on this w/ links to all the files you need.
Dbl_Tap said:
Man you have a ton of posts to search through I think I found the right one.
So you've got MMS working no problem? I use MMS all the time and don't want to loose it like some people have.
Your steps seem to involve already using a cooked ROM are the steps the same for a 'virgin' xv6800?
Click to expand...
Click to collapse
Pro with the MMS? Maybe you can tell me how to hell to use it. I'd like to look at pictures for more than 5 seconds. It's such a pita to use, maybe I'm just not comfortable with it yet. I hated my last phone, but it was so easy to sent and view MMS messages.
Since you're going from the stock rom, there's a chance you won't be able to place calls after the flash.
Call verizon, tell them you did a hard reset and can't place calls. If they press for answers, make something up... installed a program and the radio went apespit, etc. They'll get you working again.
Over at hofo a user said the tech on the phone asked him if he unlocked the GPS, the caller played stupid, but the tech knew what was up and still helped him out.
SO far so good.
I installed Olipro 2.40.
I then installed the stock Sprint ROM.
I let it run until i aligned the screen and it connected to my computer then I re-set it. I didn't know when it would try to customize my device so maybe I stopped too soon.
I'm not sure what you meant by "manually set it in bootloader" after that and since nothing came up asking to set anything on the reset I continued on to the DCD ROM.
It loaded no problem and everything seems to be working but I just tried a test call after doing *228,1 and it says they can't authenticate my phone.
SO at this point I guess I need to call VZW and get some help right or did I do something wrong
Dbl_Tap said:
SO far so good.
I installed Olipro 2.40.
I then installed the stock Sprint ROM.
I let it run until i aligned the screen and it connected to my computer then I re-set it. I didn't know when it would try to customize my device so maybe I stopped too soon.
I'm not sure what you meant by "manually set it in bootloader" after that and since nothing came up asking to set anything on the reset I continued on to the DCD ROM.
It loaded no problem and everything seems to be working but I just tried a test call after doing *228,1 and it says they can't authenticate my phone.
SO at this point I guess I need to call VZW and get some help right or did I do something wrong
Click to expand...
Click to collapse
You stopped at the right time.
You will need to let Verizon know that you had to hard reset your phone and need the A Key. They will help you.
Were you following my directions?
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 one of the 5 pins in the mini-usb connection is missing. This disables any sort of data connection through usb, however I'm still able to charge the phone. Now I think I can get my phone replaced by Verizon but as it is right now I have dcd's 3.2.0 rom and the 3.42.30 radio. I have no problem flashing through my sd card as far as roms and radios go, but can the bootloader be relocked in the same fashion? I know the procedure for relocking is in the wiki but it relies on an activesync connection, which I cannot make. Am I proper f*cked or can I do this relocking?
So one of the 5 pins in the mini-usb connection is missing. This disables any sort of data connection through usb, however I'm still able to charge the phone. Now I think I can get my phone replaced by Verizon but as it is right now I have dcd's 3.2.0 rom and the 3.42.30 radio. I have no problem flashing through my sd card as far as roms and radios go, but can the bootloader be relocked in the same fashion? I know the procedure for relocking is in the wiki but it relies on an activesync connection, which I cannot make. Am I proper f*cked or can I do this relocking?
Click to expand...
Click to collapse
You can't relock unless you have an activesync connection. You can relock using nuespl, but it will relock to 2.07 which is the GPS rom stock bootloader...something that doesn't exist yet for Verizon.
I think ImCoKeMaN @ PPCGeeks has a relocker for the 1.06 bootloader that can be run from SD. It's not recommended for use after running a GPS ROM/Radio, but I've heard of a few success stories. Of course, I've also heard of a number of devices becoming completely and utterly useless after trying this. I don't think he made the version that can run from SD publicly available, but you could try shooting him a PM. He'd be able to give you all the details as well. Might be worth a shot as a last resort.
I might give that a try. If I recall, I can set up an activesync through bluetooth, which is what I'm goin to try first. If that's impossible I'll be pming ImCoKeMaN. Thanks
If you have the insurance it would be unfournate when it takes a trip in to the Shower or Tub.
Big Dawg 23 said:
If you have the insurance it would be unfournate when it takes a trip in to the Shower or Tub.
Click to expand...
Click to collapse
Or even better, falls down into the toilet. Chances are the people at Verizon won't want to poke around with it in that case.
Before I go through relocking or flushing my phone I thought I'd try to bluetooth connect it to try activesync. Well, it seems that the only connect I can make is to use it as a dial-up modem, a serial connection isn't possible. Has anyone else with dcd's rom tried to connect to a pc for file transfers and succeeded?
Honestly, I think the flashing / locking software relies on the USB connection. If I remember correctly, once the connection is made through Activesync... it disconnect Activesync. I'm not sure if this connection stays available for the flashing / locking. I personally don't want to try and brick my phone. LOL
Nitro is correct. The unlockers/relockers that run from your PC place your phone in bootloader mode, and at that point your bluetooth connection would drop.
The real issue isn't the broken USB port. There are ways to relock from SD. Your main problem is that going from a GPS ROM/Radio/SPL to a non-GPS version has been known to brick devices. You could always try and hold out until VZW releases an official GPS ROM, then you wouldn't have to worry about going back to a 1.x SPL. From what I've seen, gc14 may have some insight into when that ROM will actually be released.
I had a similar issue happen to my sprint mogul, I was able to charge but the mini-usb connector was messed up so I could not get a data connection.
I re-flashed the latest stock rom and radio from the sd card and took it in. Both the service reps and the technicians did not notice the bootloader version, and I got a replacement for free within 30 minutes or so. I would think that with all the devices they work with, the vast majority of people do not have unsupported software versions and the techs most likely do not check every time (or just do not care all that much).
Just my thoughts and experience though, yours with Verizon could obviously differ.
EDIT:
Ahh yeah I forgot that Verizon has not released their gps radio yet and that downgrading can be problematic... Best of luck to you.
VerusMaya said:
I had a similar issue happen to my sprint mogul, I was able to charge but the mini-usb connector was messed up so I could not get a data connection.
I re-flashed the latest stock rom and radio from the sd card and took it in. Both the service reps and the technicians did not notice the bootloader version, and I got a replacement for free within 30 minutes or so. I would think that with all the devices they work with, the vast majority of people do not have unsupported software versions and the techs most likely do not check every time (or just do not care all that much).
Just my thoughts and experience though, yours with Verizon could obviously differ.
Click to expand...
Click to collapse
Same exact issue here, except I did go ahead and put the 2.07 SPL back on. They are wanting to charge me $35 though. How long ago did you get your phone? I might try a few other shops and see if they'll swap me a new phone for free.
I'm going to try and make it as stock as possible and go for the return. I've found what seems to be a lot of conflicting procedures for returning to Verizon stock roms and radios, is there a 'best' one?
egrzelak said:
I'm going to try and make it as stock as possible and go for the return. I've found what seems to be a lot of conflicting procedures for returning to Verizon stock roms and radios, is there a 'best' one?
Click to expand...
Click to collapse
Yeah, this one here.
bedoig said:
Same exact issue here, except I did go ahead and put the 2.07 SPL back on. They are wanting to charge me $35 though. How long ago did you get your phone? I might try a few other shops and see if they'll swap me a new phone for free.
Click to expand...
Click to collapse
I got the original one in late December and got them swapped about two months ago. I was actually rather surprised I got it so hassle-free and without paying anything, I expected to have to pay some warranty fee or something.
I ran into this situation about a month ago, except the data port was hosed enough I couldn't charge or sync. After stressing about it I contacted a major contributor to the board and he said not to worry about it.
So I took the phone in (@ 3 mos. old) and the vzw sales guy was pretty cool about it (I didn't mention anything about flashing the software). He got on the phone with someone else at vzw tech and did some kind of exchange program. A few days later I had a new 6800 and instructions to send the old phone back.
I probably should have secured the phone better in the box when returning, but oh well. I seriously doubt anyone even looked at the rom, since it was a hardware issue.
why not just get a new cable?
deeznuts2 said:
why not just get a new cable?
Click to expand...
Click to collapse
The cable isn't the problem as the pin is missing from the phone.
Alright, so the only way to relock back to Verizon's original SPL is with a working USB. Over on ppcgeeks there seem to be some people who've flashed back to the stock radio and rom without relocking the phone. They only problem they've experienced is it being unable to wake up when it's been put in sleep mode. I think this is what I'm going to do to do the return.
egrzelak said:
I'm going to try and make it as stock as possible and go for the return. I've found what seems to be a lot of conflicting procedures for returning to Verizon stock roms and radios, is there a 'best' one?
Click to expand...
Click to collapse
Look at it this way if you brick it who cares....you are trying to get it replaced.....
ok. i flashed the hyperrom ultra v15.0 to my tmobile us hd2 and decided i wanted to flash a new radio.. just to see if i was missing the speed and agility that i hear about so much from others. i started off with a 2.10.50.26 i believe. then flashed the 2.08.50.05 with much slower speed than the original. THEN, i flashed the 2.07.51.22_2 and my phone has not powered up since. it will not go into bootloader and when the update util was done, my laptop said it needed to install a new hardware driver for qualcomm cdma. now i now this is bad. but could someone explain why it did this and why my phone isnt powering on and if ill ever be able to use it again??!!?!?! any help would be appreciated.
That sounds Bad ...
Sorry pal, you have a serious problem. The .51 radio is the culprit. I'm afraid you will have to search this out, but I am unaware of any solutions.
Good luck. Warranty?
jswllms3 said:
ok. i flashed the hyperrom ultra v15.0 to my tmobile us hd2 and decided i wanted to flash a new radio.. just to see if i was missing the speed and agility that i hear about so much from others. i started off with a 2.10.50.26 i believe. then flashed the 2.08.50.05 with much slower speed than the original. THEN, i flashed the 2.07.51.22_2 and my phone has not powered up since. it will not go into bootloader and when the update util was done, my laptop said it needed to install a new hardware driver for qualcomm cdma. now i now this is bad. but could someone explain why it did this and why my phone isnt powering on and if ill ever be able to use it again??!!?!?! any help would be appreciated.
Click to expand...
Click to collapse
jswllms3 said:
ok. i flashed the hyperrom ultra v15.0 to my tmobile us hd2 and decided i wanted to flash a new radio.. just to see if i was missing the speed and agility that i hear about so much from others. i started off with a 2.10.50.26 i believe. then flashed the 2.08.50.05 with much slower speed than the original. THEN, i flashed the 2.07.51.22_2 and my phone has not powered up since. it will not go into bootloader and when the update util was done, my laptop said it needed to install a new hardware driver for qualcomm cdma. now i now this is bad. but could someone explain why it did this and why my phone isnt powering on and if ill ever be able to use it again??!!?!?! any help would be appreciated.
Click to expand...
Click to collapse
Somebody on this forum already reported about similar problem. I don't remember whether the solution was found.
jswllms3 said:
ok. i flashed the hyperrom ultra v15.0 to my tmobile us hd2 and decided i wanted to flash a new radio.. just to see if i was missing the speed and agility that i hear about so much from others. i started off with a 2.10.50.26 i believe. then flashed the 2.08.50.05 with much slower speed than the original. THEN, i flashed the 2.07.51.22_2 and my phone has not powered up since. it will not go into bootloader and when the update util was done, my laptop said it needed to install a new hardware driver for qualcomm cdma. now i now this is bad. but could someone explain why it did this and why my phone isnt powering on and if ill ever be able to use it again??!!?!?! any help would be appreciated.
Click to expand...
Click to collapse
Why do people not read, you CANNOT FLASH A .51 RADIO ON A T-MOBILE DEVICE. LEARN TO READ AND THIS WON'T HAPPEN.
uniqs said:
Somebody on this forum already reported about similar problem. I don't remember whether the solution was found.
Click to expand...
Click to collapse
Somebody? lol, quite a few people are in that boat actually.
@jswllms3
Try searching for Jtag or .51 radio brick. And maybe post in this thread
warranty will be ok so long as you dont mention flashing.
jswllms3 said:
ok. i flashed the hyperrom ultra v15.0 to my tmobile us hd2 and decided i wanted to flash a new radio.. just to see if i was missing the speed and agility that i hear about so much from others. i started off with a 2.10.50.26 i believe. then flashed the 2.08.50.05 with much slower speed than the original. THEN, i flashed the 2.07.51.22_2 and my phone has not powered up since. it will not go into bootloader and when the update util was done, my laptop said it needed to install a new hardware driver for qualcomm cdma. now i now this is bad. but could someone explain why it did this and why my phone isnt powering on and if ill ever be able to use it again??!!?!?! any help would be appreciated.
Click to expand...
Click to collapse
How Cute
You flashed a 2.07.51 radio ! ! !
Take your phone back for warranty and never flash a .51 radio again as every one else saying...
Good luck with it.
ok. lol. so its abrick. ill search a little more butthe strange thing is, when i plug it in via usb to my comp it still shows that its searching for new hardware.. i dont think its a total loss. i have the odd feeling i can revive it. but in any case, how do i turn it in for a warranty and what would i say? lol.
jswllms3 said:
ok. lol. so its abrick. ill search a little more butthe strange thing is, when i plug it in via usb to my comp it still shows that its searching for new hardware.. i dont think its a total loss. i have the odd feeling i can revive it. but in any case, how do i turn it in for a warranty and what would i say? lol.
Click to expand...
Click to collapse
You say. I don't know what happen. I was charging it over night...and when I work up it was off. I turn it on and nothing happens.
what i meant to say is, im guessing i turn it into htc for the warranty, but other then flash custm roms and different radios, what other excuse would they take? i mean, they have ways of finding out right?
Maybe HELP YOU
jswllms3 said:
ok. i flashed the hyperrom ultra v15.0 to my tmobile us hd2 and decided i wanted to flash a new radio.. just to see if i was missing the speed and agility that i hear about so much from others. i started off with a 2.10.50.26 i believe. then flashed the 2.08.50.05 with much slower speed than the original. THEN, i flashed the 2.07.51.22_2 and my phone has not powered up since. it will not go into bootloader and when the update util was done, my laptop said it needed to install a new hardware driver for qualcomm cdma. now i now this is bad. but could someone explain why it did this and why my phone isnt powering on and if ill ever be able to use it again??!!?!?! any help would be appreciated.
Click to expand...
Click to collapse
I don't know if I can help you But you can enter in bootloader mode and via usb cable connect to your computer? If you can...and have Bepe&Cotulla HARDSPL3... Do a Task29 and when near 100% push volume down to stay in bootloader mode... then... Flash a radio 50 (my sig have a link to my current radio)... and without exit bootloader mode (when near 100% push volume down) Flash a ROM you want in your device...
Sorry... I only try help you... maybe don't have luck or... many luck
ddgarcia05 said:
You say. I don't know what happen. I was charging it over night...and when I work up it was off. I turn it on and nothing happens.
Click to expand...
Click to collapse
Say this ^^^^
Fidalgos said:
I don't know if I can help you But you can enter in bootloader mode and via usb cable connect to your computer? If you can...and have Bepe&Cotulla HARDSPL3... Do a Task29 and when near 100% push volume down to stay in bootloader mode... then... Flash a radio 50 (my sig have a link to my current radio)... and without exit bootloader mode (when near 100% push volume down) Flash a ROM you want in your device...
Sorry... I only try help you... maybe don't have luck or... many luck
Click to expand...
Click to collapse
no. it will not enter bootloader or anything. wont connect via activesync nothing. tried a hard reset, soft reset. every type of reset. nothing works. tried bootloader and.. NOTHING!!!! ah.. but its bugging me out that its trying to install new device driver. i feel like i can fix it... if christ was real i would pray to him!!!!
if you read the dozens of other people that did this, you will see they all say the pc looks for drivers for "qualcomm blah blah blah". don't kid yourself, its gone.
jswllms3 said:
ok. i flashed the hyperrom ultra v15.0 to my tmobile us hd2 and decided i wanted to flash a new radio.. just to see if i was missing the speed and agility that i hear about so much from others. i started off with a 2.10.50.26 i believe. then flashed the 2.08.50.05 with much slower speed than the original. THEN, i flashed the 2.07.51.22_2 and my phone has not powered up since. it will not go into bootloader and when the update util was done, my laptop said it needed to install a new hardware driver for qualcomm cdma. now i now this is bad. but could someone explain why it did this and why my phone isnt powering on and if ill ever be able to use it again??!!?!?! any help would be appreciated.
Click to expand...
Click to collapse
Simple: The .51 radio raped your TMOUS's internals. It will never work again. Play dumb with the warranty people.
haaahha! so i called the warranty people and told them it was dead. asked a few questions, specifically: "what voids the warranty and why would i be charged for any repairs?" i got a number of answers including, "flashing a new os, rom or radio." hahahaha!!! so essentially, im f**ked, right? i mean this is htc, how could they not find out?
so ive read part of three threads where everyone is stating that as long as they cannot get it to go into bootloader, they cannot charge me and theyll repair my phone or send me a new one. though i am worried that i havent read anything about any phones coming back to the peoples having this problem.. i dont have insurance through tmobile so im assuming i cant send it back to them, i am however still under the year manufacturers warranty provided by htc. does it matter who i send it to? and has anyone had experience with this particular problem that can acclaim to or deny me the assurance of me getting my phone back? lol.
Do not lie, as that could bite you in ways you don't want to deal with; as in fraud, etc. Our phones are around $550, a retainer for an Attorney to defend you against criminal charges would be a lot more.
I would go into tmobile, and when you go into store you simply tell them the truth that the phone doesn't work.
Definitely a drag that you bricked the phone. Could have been me, probably will be someday when I get too eager or careless.
Anyhow, let us know what happens.
jswllms3 said:
so ive read part of three threads where everyone is stating that as long as they cannot get it to go into bootloader, they cannot charge me and theyll repair my phone or send me a new one. though i am worried that i havent read anything about any phones coming back to the peoples having this problem.. i dont have insurance through tmobile so im assuming i cant send it back to them, i am however still under the year manufacturers warranty provided by htc. does it matter who i send it to? and has anyone had experience with this particular problem that can acclaim to or deny me the assurance of me getting my phone back? lol.
Click to expand...
Click to collapse
well for a start this is the regular hd2 section, have you read any of the posts in the tmous section? (Well, no, else you would have seen the myrriad warnings about flashing ..51.. radios )
Loads of people have had them repaired after this type of brick, and the only people that haven't have been those that confessed to flashing.
And no, just because it is HTC, they cant see into a broken bootloader. The best they can do is JTAG the phone, and that flashes a new bootloader anyway, wiping out any trace of what you did.
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