Develop Bugs

Unbricked but No Service?

Ok just recently unbricked my phone and started flashing once again. First I did the HARD SPL change from 2.03 to 2.10 Olipro. I flashed the current vp3G a few times but I was getting no phone service. I flashed the schaps and it did the same. My was getting no service and when I clicked on settings it said this.
Unknown SIM status.
Only emergency calls can be made without a PIN.
Click to expand...
Click to collapse
Did some googling and found some sources where it said my default PIN was either 1111 or 2222. I went ahead and called ATT and explained to them I was getting no service but of course never mentioned I had a cooked ROM. They said the same that the default was 1111. Of course for some reason when I was talking to them I could not get to the settings to enter it. I told them I would call them back.
Finally got to enter it in and nothing. It is still not working. I'm in some desperate need of suggestions. Thank You.
- Monty

Flash the OEM ROM from your provider. This should get your service back if your using a legit SIM

i see you have unbricked your phone, try loading up a new radio
http://rapidshare.com/files/60589318/radio1.54.07.00.rar

oh yea, thats the radio im using for my 8525, its the updated version 1.54 it works pretty well, hope that fixes your problem

I have that same problem but it seems that changing the radio does not work, although I havent tried every single radio. Some radios will give say i have no service even when i don't have the sim card in (it should be saying no sim)

This might help
If you are in USA and if you have a CINULAR sim card in your phone go to a AT&T store for a FREE AT&T sim card. It might resolve the issue as AT&T just changed some settings in some towers.
Read about in VP's 3.62
here: http://forum.xda-developers.com/showpost.php?p=1637422&postcount=445:)

fuzzvirus said:
If you are in USA and if you have a CINULAR sim card in your phone go to a AT&T store for a FREE AT&T sim card. It might resolve the issue as AT&T just changed some settings in some towers.
Read about in VP's 3.62
here: http://forum.xda-developers.com/showpost.php?p=1637422&postcount=445:)[/QUOTE
I have a new AT&T sim card and I still have the problem
Click to expand...
Click to collapse

Monty, have you found a solution?

ihavetinyballs said:
Flash the OEM ROM from your provider. This should get your service back if your using a legit SIM
Click to expand...
Click to collapse
That is how I bricked my phone in the first place. Could not flash OEM either 2.15 or the most recent 3.62 WM6 upgrade.

asianr0cker said:
oh yea, thats the radio im using for my 8525, its the updated version 1.54 it works pretty well, hope that fixes your problem
Click to expand...
Click to collapse
When I got unbricked I updated my SPL like you mentioned and now I'm running 2.10. I did try to update the radio but that also got locked up and had to hard reset to get it back. I was trying 1.54 also.

cjchriscj said:
Monty, have you found a solution?
Click to expand...
Click to collapse
No I have not.

More reading and more reading. Ok I realize I have no GSM and no Radio. When I try to install radio it gets stuck on 0% then locks me out. Then I'm stuck in the Tri-Color mode and am forced to reflash ROM. I'm thinking "Problem 5" is the problem I'm having but can anyone confirm or help me out please.
My ATT flash screen says:
R None
G None
D 3.62
Click to expand...
Click to collapse
That means I have no Radio and GSM correct? What do I do?

warranty?
How far into your warranty are you, assuming you're still under warranty? Same thing happened to me. I played stupid with AT&T tech support (then Cingular), had no distinguishable drop marks or water damage, and they replaced it under warranty I even had it stuck on the bootloader screen If you're still under warranty, try to load an oem rom back on it and see if you can get them to replace it.

kalrykh said:
How far into your warranty are you, assuming you're still under warranty? Same thing happened to me. I played stupid with AT&T tech support (then Cingular), had no distinguishable drop marks or water damage, and they replaced it under warranty I even had it stuck on the bootloader screen If you're still under warranty, try to load an oem rom back on it and see if you can get them to replace it.
Click to expand...
Click to collapse
Unfortunatley im out of warranty

Is there anyway to completely erase everything that is on the hermes at once? except for the stuff on the eeprom, i already had to deal with that

can no one help us?

i heard from my friend who works at an att non corp store that just recently non corp stores were given the ability to give the new contract discounts. that he just has to make a 5 min call and it gets approved and they can offer you the 2yr discount although it might extend your contract.
reason im saying this is even if your not up for an update, any att store should be able to (if the guy chooses to be helpful) hook you up with the discount regardless of how long or how little you've been in contract.
just food for thought in case you cant find a solution.

when I reset my device i see no GSM ocassionaly, well since an hour ago, its been saying nothing but No GSM, I have tried to fix it using the unbrick direction in the wiki, but to no avail.

Before I send my phone back to TMO UK....

I can't get a GPS fix so it needs to go back for repair. Previoulsy I have rooted it with unrevoked.
Tonight, i made a gold card and flashed it with a T-Mobile rom i downloaded, which went swimmingly.
Is this all I need to do so they don't know it was rooted?

Yes!!!!!!!!!!

You wouldn't have needed the gold card to flash the T-Mobile RUU, which ROM were you originally on when you got the phone?

A tmobile rom was on the phone, but i'd ran unrevoked so I needed to get rid of that. I tried without a gold card but was getting errors like customer id, but the gold card got round that.

Goldcard always wins

Then you weren't on a T-Mobile ROM originally if you needed a gold card to flash it
A gold card is ONLY needed to flash a ROM different to the original build number, it should NOT be needed to flash a branded ROM if your phone was branded so sounds like you went through the issue for nothing

EddyOS said:
Then you weren't on a T-Mobile ROM originally if you needed a gold card to flash it
A gold card is ONLY needed to flash a ROM different to the original build number, it should NOT be needed to flash a branded ROM if your phone was branded so sounds like you went through the issue for nothing
Click to expand...
Click to collapse
Very true but as long as he has managed to flash a branded ROM with it i don't think T-Mobile will be able to tell the difference

They can if they check the IMEI and see it wasn't a T-Mobile handset

EddyOS said:
They can if they check the IMEI and see it wasn't a T-Mobile handset
Click to expand...
Click to collapse
Certainly if that's what he's trying to do. But if that were the case then he would have to show them contract details or a receipt before getting a repair anyway. It is however possible that he bought a legitimate un-branded phone from T-Mobile and therefore flashing the ROM to a T-mobile one won't make them look twice.

Not true, if that was the case I could send my unbranded one back to Vodafone for repair. They'd send it back saying 'not one of ours, off to HTC you go' which is what T-Mobile might also do

EddyOS said:
Not true, if that was the case I could send my unbranded one back to Vodafone for repair. They'd send it back saying 'not one of ours, off to HTC you go' which is what T-Mobile might also do
Click to expand...
Click to collapse
I hear what you are saying. I personally have never done it but have read on here that some people have not managed to flash back to an RUU for their carrier without using a goldcard ( not saying it has to be used maybe they did something wrong with the first flash and the goldcard did it right for them) iv'e also read that some have problems as the newer ROM they have on their phone won't allow them to flash to an older stock RUU and the goldcard has allowed them to do this.
Again only going off what i have read here

I'm just trying to make the OP aware that although it shouldn't be a problem it might be

EddyOS said:
I'm just trying to make the OP aware that although it shouldn't be a problem it might be
Click to expand...
Click to collapse
No worries just trying to get my facts straight incase i'm ever in the same predicament

Main reason why I always get unbranded handsets - deal with the manufacturer direct!

EddyOS said:
Main reason why I always get unbranded handsets - deal with the manufacturer direct!
Click to expand...
Click to collapse
Lol i was very close to doing the same - can't help playing round with ROM's and it's killing me not doing it on this one

VU2.39 Lost Radio...Out of Service????

Beautifully working VU2.39. Then decided to add new lock ring. Totally messed up phone.
Restored with ROM Manager to prior situation, but have totally lost phone radio (and therefore phone, 3g etc.) Have tried restoring many times, tried airplane mode, wiped cache...all with no solution.
Shows no service, no CDMA or other option exists in settings, phone info shows:
Signal Strength =0
Mobile Network Type unknown
Service state= out of service
What did I do here??? How to fix???

Have now done factory reset and called Verizon. They tried to change manual codes but to no avail. Seems my radio got fried by applying the Captain America launch ring. Is this possible that that was the cause. Worked perfectly before I patched this today.
Help! I don't want a new phone as it will come with 2.3.4 not rootable.

lair12 said:
Have now done factory reset and called Verizon. They tried to change manual codes but to no avail. Seems my radio got fried by applying the Captain America launch ring. Is this possible that that was the cause. Worked perfectly before I patched this today.
Help! I don't want a new phone as it will come with 2.3.4 not rootable.
Click to expand...
Click to collapse
2.3.4 is definitely rootable. And I don't think a ring would change that much. Have you tried flashing a New radio?
Sent from my Incredible 2 HD using XDA App

I tried flashing new radio. No difference.
I just can't believe that the sense link patch would have actually physically damaged the radio and killed the system, but I cannot get anything to "activate" the radio. In manual program mode ##778, the display settings say "radio version 1.09.01.0622", so the software should be there. But it cannot find the hardware.
I have matched my NAM settings and Home SID to the same as my wife (her phone is fine).

lair12 said:
I tried flashing new radio. No difference.
I just can't believe that the sense link patch would have actually physically damaged the radio and killed the system, but I cannot get anything to "activate" the radio. In manual program mode ##778, the display settings say "radio version 1.09.01.0622", so the software should be there. But it cannot find the hardware.
I have matched my NAM settings and Home SID to the same as my wife (her phone is fine).
Click to expand...
Click to collapse
Try flashing this Radio. It's the last one on the list.

No difference whatsoever! So what do you think has happened and how and why? How could flashing the Captain America htc unlock ring have caused such destruction?
Any how could it fry or totally immobilize the radio? I really do not want to replace the phone, but am giving up hope for a solution. It's got to be either something very simple, or the radio did get fried.
And I still don't see where I can unlock and root 2.3.4 on this forum or at the Revolutionary site.

lair12 said:
No difference whatsoever! So what do you think has happened and how and why? How could flashing the Captain America htc unlock ring have caused such destruction?
Any how could it fry or totally immobilize the radio? I really do not want to replace the phone, but am giving up hope for a solution. It's got to be either something very simple, or the radio did get fried.
And I still don't see where I can unlock and root 2.3.4 on this forum or at the Revolutionary site.
Click to expand...
Click to collapse
Well...... Was the lockring made for your specific ROM and phone? If not, that may be why.
Have you tried any other ROMs to make sure it's not just something interfering in the ROM itself?
To root 2.3.4, you have to downgrade the hboot v.98 to v.97 following these steps found here.

Link came from here: http://forum.xda-developers.com/archive/index.php/t-1135020.html
SHould this have bricked the radio??
Can you resend root 2.3.4 link, as the one above goes back to the radio instructions.
Many thanks.

lair12 said:
Link came from here: http://forum.xda-developers.com/archive/index.php/t-1135020.html
SHould this have bricked the radio??
Can you resend root 2.3.4 link, as the one above goes back to the radio instructions.
Many thanks.
Click to expand...
Click to collapse
Post edited so the link for 2.3.4 root should work. But, yeah, that's for Thunderbolt, not the DINC2. Try flashing another ROM or full wipe/reflash of VU 2.39. Don't apply any mods until you find out if it works, and see if someone can port the lockring to the DINC2.

Wiped twice regular and dalvik, installed the clean ROM for phone I had saved. DEAD Radio. Bummer, but thanks for you help.
Mobile Network Type= unknown
Service State= out of service
This has not changed with any fixes I have tried.

lair12 said:
Wiped twice regular and dalvik, installed the clean ROM for phone I had saved. DEAD Radio. Bummer, but thanks for you help.
Mobile Network Type= unknown
Service State= out of service
This has not changed with any fixes I have tried.
Click to expand...
Click to collapse
What about the .722 radio?? Earlier you said you had the .622 radio which is an older one. If that doesn't work, boot into hboot and factory reset (I think this works). Then you'll probably have to re-root. Otherwise, you can get a new phone, and root via the downgrade.

Absolutely no solutions anywhere. Tried everything twice! New phone on the way. Very frustrating situation.

lair12 said:
Absolutely no solutions anywhere. Tried everything twice! New phone on the way. Very frustrating situation.
Click to expand...
Click to collapse
Sorry to hear that.... Let us know how the rooting goes.
Sent from my Incredible 2 HD using XDA App

[Q] Two One X's - not the same?

Hi - I'm in the UK and have bought two One X's from Amazon. The first is fine, the second isn't (it was bought in the Amazon Warehouse and is pre-owned but "as-new").
1 The first phone found the 1.28 update immediately on setup after connecting to wi-fi. The second won't update, even after doing a manual check and is still on 1.26.401.2. From what I've read if the phone is "unbranded"/not originally locked to any provider it should be ready for the update. How do I check this?
2 The LED on the second is tiny - it's the size of the end of a pin whereas the other phone has a much bigger, more visible light.
Thanks in advance for any questions. I have searched for similar problems but came up with nothing (sorry if I missed answers that are already posted on here or elsewhere)

1. Flash the 1.29 RUU - job done!
2. Can't say I've noticed this but you could be right

Thanks, but I'm hoping not to flash this device. Is there any was of checking if the phone is tied to a provider or why it doesn't want to update to 1.28?

If it's running x.xx.401.x then it's an unbranded handset so flashing the RUU won't affect anything with regards to warranty as it's the official ROM file. OK, it means wiping the phone but at least you're up-to-date!

EddyOS said:
If it's running x.xx.401.x then it's an unbranded handset so flashing the RUU won't affect anything with regards to warranty as it's the official ROM file. OK, it means wiping the phone but at least you're up-to-date!
Click to expand...
Click to collapse
Ok, thanks again. I was really hoping to figure out what the problem is here so I understand how the updating works - if you say I do infact have an unbranded handset, I don't understand why it won't update. Does the update server go down occupationally or does it just mean I have an issue with the handset itself?

[Q] Radio and OpenDSP have "INVALID-VER-INFO" beside them. Is this normal? Need help

[Q] Radio and OpenDSP have "INVALID-VER-INFO" beside them. Is this normal? Need help
I just recently purchased the m8. I did lots of research learning everything I could before doing any modding. So today I decided to unlock my boot-loader so it was my first time getting into recovery. But when I get into recovery I see both radio and OpenDSP have "INVALID-VER-INFO" beside them. Its never been modified and I got it from t mobile and was the first to open the device. Not a second hand phone. Is this normal? I've been googling for hours and cant find any information. Its been sort of difficult getting any help in the htc M8 help threads honestly. If anyone can shed any information I would greatly appreciate it. I haven't noticed any thing wrong with my phone out of the box and everything about the functionality of the phone has been stellar.

ahfu25 said:
I just recently purchased the m8. I did lots of research learning everything I could before doing any modding. So today I decided to unlock my boot-loader so it was my first time getting into recovery. But when I get into recovery I see both radio and OpenDSP have "INVALID-VER-INFO" beside them. Its never been modified and I got it from t mobile and was the first to open the device. Not a second hand phone. Is this normal? I've been googling for hours and cant find any information. Its been sort of difficult getting any help in the htc M8 help threads honestly. If anyone can shed any information I would greatly appreciate it. I haven't noticed any thing wrong with my phone out of the box and everything about the functionality of the phone has been stellar.
Click to expand...
Click to collapse
Is that on the bootloader screen? What are u trying to accomplish?

twinnfamous said:
Is that on the bootloader screen? What are u trying to accomplish?
Click to expand...
Click to collapse
In the bootloader screen it says invalid ver info next to both. I want to know if this is normal on an unmodified device. I dont want to mod my phone with it saying invalid version next to radio and opendsp.

ahfu25 said:
In the bootloader screen it says invalid ver info next to both. I want to know if this is normal on an unmodified device. I dont want to mod my phone with it saying invalid version next to radio and opendsp.
Click to expand...
Click to collapse
I think something is off on that phone. I unlocked and s-offed mine and the only thing different was the os is blank but everything else was fine.
But if u have no actual problems with cell reception or audio then maybe u just need to update the firmware to latest after u s-off and that Will fix u up. More than likely.
Let me know I have done a lot on my phone allready. I even switched it to a dev edition just to get the 4.4.3 firmware and then flashed my backup back to my Rom of choice.
I'll help if I can. I notice there ain't many people helping on this forum there all on the international forum

twinnfamous said:
I think something is off on that phone. I unlocked and s-offed mine and the only thing different was the os is blank but everything else was fine.
But if u have no actual problems with cell reception or audio then maybe u just need to update the firmware to latest after u s-off and that Will fix u up. More than likely.
Let me know I have done a lot on my phone allready. I even switched it to a dev edition just to get the 4.4.3 firmware and then flashed my backup back to my Rom of choice.
I'll help if I can. I notice there ain't many people helping on this forum there all on the international forum
Click to expand...
Click to collapse
I appreciate that. I just didn't want to s-off since I dont do any heavy modding. I was just gonna unlock the boot-loader, install custom recovery root and flash arhd. I don't think this is normal either for a brand new phone that hasn't been touched software wise. I might go exchange it at t mobile. This is my screen

ahfu25 said:
I appreciate that. I just didn't want to s-off since I dont do any heavy modding. I was just gonna unlock the boot-loader, install custom recovery root and flash arhd. I don't think this is normal either for a brand new phone that hasn't been touched software wise. I might go exchange it at t mobile.
Click to expand...
Click to collapse
I understand about the s-off but really it's the best thing to do because if something ever goes wrong there will be nothing stopping u from fixing it.
Also I was gonna suggest taking it back but they might trip on the unlocked bootloader and if u fastboot oem lock it Will say relocked. So they will know. But it's worth a try. T-Mobile doesn't seem like they know anything about technical stuff. so if you try to explain to them they might look at you like they don't know what your talking about.
I seen the picture if it is still locked take it back. And show them
Your firmware is allready the latest so that's a factory f-up.

twinnfamous said:
I understand about the s-off but really it's the best thing to do because if something ever goes wrong there will be nothing stopping u from fixing it.
Also I was gonna suggest taking it back but they might trip on the unlocked bootloader and if u fastboot oem lock it Will say relocked. So they will know. But it's worth a try. T-Mobile doesn't seem like they know anything about technical stuff. so if you try to explain to them they might look at you like they don't know what your talking about.
I seen the picture if it is still locked take it back. And show them
Your firmware is allready the latest so that's a factory f-up.
Click to expand...
Click to collapse
How would they know the bootloader is unlocked at the tmobile store? Would they check on that before exchanging the device?

ahfu25 said:
How would they know the bootloader is unlocked at the tmobile store? Would they check on that before exchanging the device?
Click to expand...
Click to collapse
More than likely. I got charged 50 bucks one time and I couldn't even fight it because they sent it in and my Bill went up I wondered why so I asked and they said because of modifications all they did was exchange it but I still had to pay. Try it or relock it and do the ruu for that firmware. And see if it will take off the tampered flag and fix the ver info

twinnfamous said:
More than likely. I got charged 50 bucks one time and I couldn't even fight it because they sent it in and my Bill went up I wondered why so I asked and they said because of modifications all they did was exchange it but I still had to pay. Try it or relock it and do the ruu for that firmware. And see if it will take off the tampered flag and fix the ver info
Click to expand...
Click to collapse
I dont have a tampered flag in bootloader. Just "Unlocked"

ahfu25 said:
I dont have a tampered flag in bootloader. Just "Unlocked"
Click to expand...
Click to collapse
So then u never flashed recovery yet. So u should try to take it back.
If they are tripping just tell them the facts that the software was not properly installed on device.

twinnfamous said:
So then u never flashed recovery yet. So u should try to take it back.
If they are tripping just tell them the facts that the software was not properly installed on device.
Click to expand...
Click to collapse
whats that RUU you mentioned? Is there one specifically for the tmobile version that I can flash via stock recovery?

ahfu25 said:
whats that RUU you mentioned? Is there one specifically for the tmobile version that I can flash via stock recovery?
Click to expand...
Click to collapse
Sorry about taking a while.
Here's the link to what u will need http://forum.xda-developers.com/showthread.php?t=2754063

twinnfamous said:
Sorry about taking a while.
Here's the link to what u will need http://forum.xda-developers.com/showthread.php?t=2754063
Click to expand...
Click to collapse
No apology needed. Thank you for helping me out. I was able to s-off and get everything back to stock. Boot loader locked not "relocked" , s-on, unrooted. But the "invalid version" message was still there. I just came back from the tmobile store and they ran some diagnostics and said there was a problem with the software. They exchanged it for me and I checked it before I left the store and this one is perfect. I even asked for them to run the same diagnostics and everything checked out fine. I'm gonna do even a little more research before modding this one. I'm a little nervous now ..lol....but again thank you!!! I really love the M8. I came from the galaxy note 3 from att and sadly att locks the boot-loader on it. I love the note 3 just not on AT&T. I'm trying to sell my AT&T note 3 to buy a tmo version.

ahfu25 said:
No apology needed. Thank you for helping me out. I was able to s-off and get everything back to stock. Boot loader locked not "relocked" , s-on, unrooted. But the "invalid version" message was still there. I just came back from the tmobile store and they ran some diagnostics and said there was a problem with the software. They exchanged it for me and I checked it before I left the store and this one is perfect. I even asked for them to run the same diagnostics and everything checked out fine. I'm gonna do even a little more research before modding this one. I'm a little nervous now ..lol....but again thank you!!! I really love the M8. I came from the galaxy note 3 from att and sadly att locks the boot-loader on it. I love the note 3 just not on AT&T. I'm trying to sell my AT&T note 3 to buy a tmo version.
Click to expand...
Click to collapse
That's great problem solved.
now u know u got a good device.
I love the m8 too. I got mine first day it came out at T-Mobile.
First thing I did was unlock and s-off then recovery and root. Till some roms came out then I went to Bad Seed Customs Rom and that's it.
I've tried a lot of the roms even the new stock with elementalx kernel will last all day.
There's a whole lot u can do but most of the info is in the international forum.
Anyways glad I could help.

twinnfamous said:
That's great problem solved.
now u know u got a good device.
I love the m8 too. I got mine first day it came out at T-Mobile.
First thing I did was unlock and s-off then recovery and root. Till some roms came out then I went to Bad Seed Customs Rom and that's it.
I've tried a lot of the roms even the new stock with elementalx kernel will last all day.
There's a whole lot u can do but most of the info is in the international forum.
Anyways glad I could help.
Click to expand...
Click to collapse
Weird bro...now I go into boot loader with this phone and I'm getting the invalid ver message again. I'm still unmodified with bootloader still locked. I haven't even connected the phone to my computer yet.

ahfu25 said:
Weird bro...now I go into boot loader with this phone and I'm getting the invalid ver message again. I'm still unmodified with bootloader still locked. I haven't even connected the phone to my computer yet.
Click to expand...
Click to collapse
That's crazy what are you gonna do?

twinnfamous said:
That's crazy what are you gonna do?
Click to expand...
Click to collapse
Lol....I'm gonna keep it. I think it's software related. Nothing wrong functionality wise just like the other one. And I went to a different tmobile store for inventory purposes and lessen the chances of me getting a bad phone. Like I said I checked it at the store it didn't have that message. And they ran diagnostics and it read clean. I'm just gonna flash away lol

ahfu25 said:
Lol....I'm gonna keep it. I think it's software related. Nothing wrong functionality wise just like the other one. And I went to a different tmobile store for inventory purposes and lessen the chances of me getting a bad phone. Like I said I checked it at the store it didn't have that message. And they ran diagnostics and it read clean. I'm just gonna flash away lol
Click to expand...
Click to collapse
That's cool. I would do the same thing. Have a great time

twinnfamous said:
That's cool. I would do the same thing. Have a great time
Click to expand...
Click to collapse
Some research needs to be done to figure it out. I know I'm not the only one

ahfu25 said:
Some research needs to be done to figure it out. I know I'm not the only one
Click to expand...
Click to collapse
Probably not but everybody just gets to unlocking and s-offing so fast they probably don't notice.
It's probably just the ones coming with that firmware out of the box.
When I got mine it had a different version.