Related
Hello,
I ran the radio OTA, followed the instructions, and after it rebooted itself it is just stuck on the htc incredible splash screen. If I hold power down and power I do get in to the boot loader, but rebooting still hangs on that splash screen. I read through the OTA thread and I didnt see any mention of this problem, any ideas?
Also, if I put PB31IMG.zip back on and let it do its thing, it tells me the version is too old. Any ideas?
did u wipe?
did u wipe?
Click to expand...
Click to collapse
LOL. I ask my son that sometimes. Just sayin'...
Warning!
Do not start a new thread with problems/questions in Development sub-forum. If you have to start a new thread, please do so in General. Else, post in the appropriate thread to which your problem/question relates. 2nd offense results in 3 day vacation. Thanks!
I'm having the same problem, and I just ran the 2.15.00.07.28 radio zip. To be honest I didn't wipe first as I thought I didn't need to. I did run unrevoked forever prior to attempting this install. I was going to right before installing CM6.. but obviously I didn't get that far. I did run a nandroid backup before hand.
So right now I'm still staring at this htc incredible splash screen. Holding power or volume down or both doesn't change anything and I'm afraid to take out the battery. Any suggestions?!
Thanks
edit: ok so I read on the 2.15 release thread that some others were having the same problem.. Am I safe to pull out the battery and try a reflash?
Reliant said:
Also, if I put PB31IMG.zip back on and let it do its thing, it tells me the version is too old. Any ideas?
Click to expand...
Click to collapse
OK, what are you trying to do? Sounds like you are trying to install the leaked OTA from early July (the one that gives 720P video recording)?
If that IS what you are attempting, it sounds like you already have it otherwise you wouldn't be getting that main version is older message. Check your hboot version, if it is .77 that is stock, .79 is the newer one I think
Are you sure you are using the correct PB31IMG.zip? The one you want is here: http://forum.xda-developers.com/showthread.php?t=726791
If you are trying to unroot and downgrade to an earlier version then you want to follow directions per this step-by-step video:
http://www.youtube.com/watch?v=eeuiURZZZds&feature=player_embedded
htc_woe_is_me said:
Are you sure you are using the correct PB31IMG.zip? The one you want is here: http://forum.xda-developers.com/showthread.php?t=726791
Click to expand...
Click to collapse
No, I was trying to update to the most recent radio from stock radio. Or do I have to update another radio inbetween? I got the zip from http://forum.xda-developers.com/showthread.php?t=752436&highlight=stuck+splash+screen, for 2.15 radio
or were you talking to the guy before me
msmith0957 said:
No, I was trying to update to the most recent radio from stock radio. Or do I have to update another radio inbetween? I got the zip from http://forum.xda-developers.com/showthread.php?t=752436&highlight=stuck+splash+screen, for 2.15 radio
or were you talking to the guy before me
Click to expand...
Click to collapse
My fault, I misunderstood.
No you can flash any radio, just dont flash the same one twice, or step on any cracks, and never walk under a ladder!
I just went from 1.03.04... to 2.05, and now just installed 2.15.. I didn't have any problems at all.
My fix
I had this exact issue, where it hangs on the HTC Incredible boot screen after trying to update the radio. I could boot into HBOOT (voldown+power) after a battery pull, and when it tried to update my PB31IMG.zip file, it would give some type of error, and when I would try and go into recovery it would jump back to the HTC Incredible boot screen and hang again.
I determined that my problem was caused either by a bad radio or bad recovery flash from the PB31IMG.zip file I had downloaded. I pulled my SD card and plugged it into my laptop using the MicroSD-to-SD adapter, deleted the PB31IMG.zip file, REDOWNLOADED the file from my laptop and stuck it back in the root of my SD card, the put the SD card back in the phone and rebooted into HBOOT and reflashed the radio/recovery. Problem solved.
I don't know if that will work for everyone, but it is exactly what happened to me.
Hope it helps,
jakewill
jakewill said:
I had this exact issue, where it hangs on the HTC Incredible boot screen after trying to update the radio. I could boot into HBOOT (voldown+power) after a battery pull, and when it tried to update my PB31IMG.zip file, it would give some type of error, and when I would try and go into recovery it would jump back to the HTC Incredible boot screen and hang again.
I determined that my problem was caused either by a bad radio or bad recovery flash from the PB31IMG.zip file I had downloaded. I pulled my SD card and plugged it into my laptop using the MicroSD-to-SD adapter, deleted the PB31IMG.zip file, REDOWNLOADED the file from my laptop and stuck it back in the root of my SD card, the put the SD card back in the phone and rebooted into HBOOT and reflashed the radio/recovery. Problem solved.
I don't know if that will work for everyone, but it is exactly what happened to me.
Hope it helps,
jakewill
Click to expand...
Click to collapse
Yeah, unfortunately this is not going to work for everyone. I was permanently disabled after trying this method. I'm still lurking around for a sure fix to avoid the same issue on my new phone.
bagery77 said:
Yeah, unfortunately this is not going to work for everyone. I was permanently disabled after trying this method. I'm still lurking around for a sure fix to avoid the same issue on my new phone.
Click to expand...
Click to collapse
Bricked?
Sent from my HTC Incredible «•» Rooted/S-off/Skyraider v2.5.2 Vanilla «•» http://www.unrevoked.com/forever
htc_woe_is_me said:
Bricked?
Sent from my HTC Incredible «•» Rooted/S-off/Skyraider v2.5.2 Vanilla «•» http://www.unrevoked.com/forever
Click to expand...
Click to collapse
Yes my phone was bricked using that method. I'm trying not to overuse the term "bricked."
Thanks for all the help.. but once I pulled the battery and turned the phone back on, apparently it booted up just fine. I guess it just needed a little push in the right direction. Once I checked the settings, the radio was indeed flashed. I got really worried over nothing I installed CM6 and everything is just fine.
Hi all, thanks in advance for any help and my apologies if this exact problem has already been resolved. I searched through this forum and found issues *similar* to my problem but nothing exact enough for me to find a solution.
My experience with Android is limited but have quite a bit of terminal UNIX experience...so I'm not a total noob and I can follow directions pretty well.
I purchased a MT3G from someone and everything seemed to be in order when I checked it out (and the price was good, so I figured I didn't have much to lose). He was running Cyanogen Mod on there but of course I wanted to restore to factory settings and build it up from scratch on my own. Thinking that I knew what I was doing, I booted into Recovery (Home/End key simultaneously) with no issues and ran the factory reset utility, thinking that this would just drop the phone back to factory settings and I could re-root it from there. When I turn the phone back on, it just hangs at the "splash" screen and runs the animation over and over again.
I can still boot into Recovery and I can get into Fast Boot so I hope I am not bricked.
Here is the output I get from Fast Boot (attached file).
I tried to restore with a SAPPIMG.zip that I found but it said wrong device...
Any help would be GREATLY appreciated. Thanks!
http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
If you get an error, you need to download an engineering spl, and then try. (Engineering 2010 SPL)
The link and instructions are around somewhere on XDA.
Thanks for the help!
Unfortunately I already tried that and it didn't work, so I guess I'll install the Engineering SPL when I get home.
Shouldn't I in theory just be able to flash another ROM over this one and have everything be back to normal?
Vontropnats said:
Thanks for the help!
Unfortunately I already tried that and it didn't work, so I guess I'll install the Engineering SPL when I get home.
Shouldn't I in theory just be able to flash another ROM over this one and have everything be back to normal?
Click to expand...
Click to collapse
Yes sir, that is the easy way!
there are plenty of 1.6, and 2.2 roms out there.
Just download to sdcard, boot into recovery, wipe and flash
Don't flash any SPLs. Your fine as long as you've got a custom recovery. Just flash another ROM from there and make sure you wipe data, dalvik-cache, and cache before flashing. I've been running CyanogenMod 5.0.8 since the summer (CM6 ran like crap) and I've been happy with it so far.
Sent from my HTC Magic using Tapatalk
Thanks for the advice guys.
Unfortunately I already flashed a different SPL and then un-rooted my device!
It works great, but now in order to get 2.2, I have to root it again which is a royal pain because I don't have a microSD reader and based on my research, the only way to root it it to make a goldcard!
Doh well! Learn something new everyday!
Vontropnats said:
Thanks for the advice guys.
Unfortunately I already flashed a different SPL and then un-rooted my device!
It works great, but now in order to get 2.2, I have to root it again which is a royal pain because I don't have a microSD reader and based on my research, the only way to root it it to make a goldcard!
Doh well! Learn something new everyday!
Click to expand...
Click to collapse
Not true you can root using the this app then use rom manager to install clockwork mod recovery. This is how I helped my friend root his device.
attached is the app
First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !
Undeadllama said:
First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !
Click to expand...
Click to collapse
You'll need a goldcard and an RUU. Look up how to make a goldcard and let me know when you have one
Wow, thanks for the quick reply
I did try creating a goldcard yesterday (using android.modaco.com/content/software/308798/pc-application-goldcardtool/). So assume I DO have one for the time being...
however if it doesn't work and I need to create a new goldcard:
Since I can't get into adb or boot up android and therefore can't access my sd card through my phone I presume il have to go out and buy a cheap card reader tomorrow.
Also, I have to run this command again:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
But if I can't get into adb how would I go about doing this, can I get the CID of the sd card from a card reader?
As for the RUU, there's many to choose from on shipped-roms.com, does this sound about right?
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35.15.19_release_130442_signed.exe
Thank you so much for your help.
This this a decent guide from Paul over at MoDaCo.
Ok disregard my last post about a card reader... I managed to borrow a friends android phone since it appears goldcard's are specific to the sd card, not the phone. So after following the instructions I now definitely have a goldcard.
Also have the RUU mentioned in the previous post.
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35. 15.19_release_130442_signed.exe
Is this right, and what do I do with these now to get them on my phone? Ive tried running the RUU whilst in Hboot and in recovery but it wont recognise my phone, presumably because adb isn't working.
Thanks again for the help.
There is another way to do it when it can only get into hboot. I'll look today for the method and let you know.
Sent from my HTC Wildfire using XDA App
Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions
Undeadllama said:
Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions
Click to expand...
Click to collapse
Yeah that's the method I was going to suggest, glad you sorted it out.
It's the fact that they lock out fastboot and stuff. If we had S-OFF from the factory, fixing these things would be so much easier
Hi,
how were you able to do this?
"Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system. "
Thanks
I'm running Virtuous 1.1.8 ROM with latest radio (stickied-thread that shows May 11th date).
The first I did (accidentily) was make S=on. Now, whenever I try to go to bootloader to load PD15IMG.zip, it says "Main version is older. Update fail".
I believe I need to get back to S=off and first put stock recovery on before doing the pd15img.zip... Is that right? I have tried to get back to s=off without any luck.
I would appreciate ANY help. Thank you.
Legaleye3000 said:
I'm running Virtuous 1.1.8 ROM with latest radio (stickied-thread that shows May 11th date).
The first I did (accidentily) was make S=on. Now, whenever I try to go to bootloader to load PD15IMG.zip, it says "Main version is older. Update fail".
I believe I need to get back to S=off and first put stock recovery on before doing the pd15img.zip... Is that right? I have tried to get back to s=off without any luck.
I would appreciate ANY help. Thank you.
Click to expand...
Click to collapse
The file you are trying to load is a radio file. You cant flash a new radio unless you have S=off. Second, how and why are you trying to flash a new radio?
I don't know. I've read a bunch of guides and I think I'm totally confused now.
What do I need to do as step 1 in this situation? If its to get my device back to s=off, I can't figure it out. It was s=off, then I accidentily made it s=on.
I would appreciate any help. Thank you.
I remember someone else doing something similar in this thread. The thread gets a little confusing as someone else jumps in with a problem and you have 4 people talking back and forth. Read the whole thing to make sure it's identical to your problem. Something on page 4 fixed resolved one of their issues.
http://forum.xda-developers.com/showthread.php?t=1092170
Legaleye3000 said:
I'm running Virtuous 1.1.8 ROM with latest radio (stickied-thread that shows May 11th date).
The first I did (accidentily) was make S=on. Now, whenever I try to go to bootloader to load PD15IMG.zip, it says "Main version is older. Update fail".
I believe I need to get back to S=off and first put stock recovery on before doing the pd15img.zip... Is that right? I have tried to get back to s=off without any luck.
I would appreciate ANY help. Thank you.
Click to expand...
Click to collapse
what you should have done was revert back to the stock radio before flashing the stock PD15IMG. since you have the updated radio, when you flashed the PD15IMG it turned your security on and flashed the stock hboot, but since youre on the updated radio you now have a radio lockout. this happened to me and I never got mine fixed, tried every method possible, so I just bricked it. KOLOHE got his fixed, try the methods he did since youre pretty much in the same boat. post back with your results...
ps- there should be a sticky made or something of the sort stating that you should be on the stock radio before trying to flash the stock PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.140e_26.03.02.26_M
I just read your thread... I have tried everything... no luck... I now have no access to the phone except bootloader/recovery, meaning the only way to get my phone working again is through the .zip in the bootloader. I think I'm bricked
Legaleye3000 said:
I just read your thread... I have tried everything... no luck... I now have no access to the phone except bootloader/recovery, meaning the only way to get my phone working again is through the .zip in the bootloader. I think I'm bricked
Click to expand...
Click to collapse
you cant even get into recovery? are you sure? thats weird....I was still able to get into recovery and flash roms and everything, but couldnt flash in hboot
If I just turn on my phone like normal now, it gets stuck at the very first screen (white "MyTouch 4G"). I can still access recovery, but that's it. I tried flashing CM7 7.0.3 and when I reboot, still white "MyTouch 4G" screen...
Legaleye3000 said:
If I just turn on my phone like normal now, it gets stuck at the very first screen (white "MyTouch 4G"). I can still access recovery, but that's it. I tried flashing CM7 7.0.3 and when I reboot, still white "MyTouch 4G" screen...
Click to expand...
Click to collapse
the thing is, since you were on virtuous fusion the kernel from that rom will stick to every other rom (dont ask, I have no idea why lol). try flashing virtuous in recovery, that should work. since the kernel from the rom is sticking, you can only flash roms that are compatible with the kernel. you should still have total root access, but your r/w should be disabled because of the radio issue. only downsides to the problem...
Ok- so once I flash virtuous back... I'm still unable to ultimately get back to flash... correct? Thanks.
If I'm sending this phone in to T-Mobile for warranty exchange, I wonder if it will be better to put on virtuous (obviously non-stock rom), or leave it in a seemingly bricked state that only shows the "white MyTouch 4G" screen... What do you think? Thanks.
Legaleye3000 said:
Ok- so once I flash virtuous back... I'm still unable to ultimately get back to flash... correct? Thanks.
Click to expand...
Click to collapse
it will still say s=on and stock hboot, but you should still have root access when you flash virtuous. if you have tried all the methods in the other thread, then you are unfortunately out of luck...
Legaleye3000 said:
If I'm sending this phone in to T-Mobile for warranty exchange, I wonder if it will be better to put on virtuous (obviously non-stock rom), or leave it in a seemingly bricked state that only shows the "white MyTouch 4G" screen... What do you think? Thanks.
Click to expand...
Click to collapse
they can still get into hboot and recovery to see that youre using clockwork
clarknick27 said:
they can still get into hboot and recovery to see that youre using clockwork
Click to expand...
Click to collapse
Maybe he will get lucky like others who have returned rooted devices, he might give it to a not so smart person . There's always the shock treatment too if you cant flash the phone back to stock, only if OP has something to send high volts to phone.
Ace42 said:
Maybe he will get lucky like others who have returned rooted devices, he might give it to a not so smart person . There's always the shock treatment too if you cant flash the phone back to stock, only if OP has something to send high volts to phone.
Click to expand...
Click to collapse
thats how I got my replacement
Ace42 said:
Maybe he will get lucky like others who have returned rooted devices, he might give it to a not so smart person . There's always the shock treatment too if you cant flash the phone back to stock, only if OP has something to send high volts to phone.
Click to expand...
Click to collapse
And people wonder why T-mobile is charging a processing fee now for doing warranty exchanges.
You think I should be able to put stock recovery back on in my situation?
Also, where can I find that panache leaked rom? I don't understand how that's supposed to fix my problem...?
I think I got it to work! I used the hex editing method and flashed the .zip file in bootloader at the end of completing the guide (.zip that was included in that thread) and everything seems to be working like stock!
When I try to go to recovery, I get that icon with a red exclamation mark (which I think is normal for completely stock phones..??).
The only thing I'm not 100% sure about is in bootloader, it says hboot version ..86 Besides that, everything seems 100% stock. Will that .86 be an issue? Thanks.
Legaleye3000 said:
I think I got it to work! I used the hex editing method and flashed the .zip file in bootloader at the end of completing the guide (.zip that was included in that thread) and everything seems to be working like stock!
When I try to go to recovery, I get that icon with a red exclamation mark (which I think is normal for completely stock phones..??).
The only thing I'm not 100% sure about is in bootloader, it says hboot version ..86 Besides that, everything seems 100% stock. Will that .86 be an issue? Thanks.
Click to expand...
Click to collapse
.86 is the stock bootloader. I'm glad you were able to fix it. I'm not sire about the red ! maybe someone else can answer it. So are you going to keep it and start all over again?
I think the red exclamation mark is normal. If memory serves me right, the recovery was not accessible on complete stock and if you try to go to it you get this red exclamation point (someone correct me if I'm wrong).
I need to send this phone in as a warranty replacement. So it seems MISSION ACCOMPLISHED.
Thanks for your help along the way!
Have been trying my best to figure this out, but so many steps. Lame I know but...
I've got a Rogers 32A SPL 1.33.0010 SAPP50000 3.22.20.17. After buying it used with a Hero ROM almost a year ago, I managed to flash CM6-FroyoRedux-1.6-32a which worked (great!) for almost a year. Lately it has been getting really flakey with lots of FC and problems connecting to wifi.
So I thought a re-flash of ROM should fix things up. No luck, same problems. Super flakey, lots of FC (even with base install). Does that mean I have a hw problem?
So thought I would try another more up to date ROM. Tried CyanogenCARZ-7.1.0... and Ginger Yosi 1.2.1 and a few other but none would flash properly (Recovery on the phone is ClockworkMod Recovery v2.5.0.1 - is that the problem? If so can anyone direct me to easy steps to change this? Found some others but me to dumb, or they to hard to follow b/c no luck. I have done ROM messing about for years, more recently with Dell Streak, but it seemed to be much easier.)
Questions:
- If i can get this far, does it mean my phone is rooted?
- I hear I have a 'Perfect SPL', but if the Hero and the CM6 ROM could be flashed, does that matter?
Where should I go from here?
Thanks for your help, and sorry for being so dumb.
Don't worry, it's natural to have questions whwn confronted with such a confusing phone. I would recommend going to the RUU sticky in the development section, and flashing back to stock. If you still gets fcs and the like on stock, it is likely a hardware issue. Otherwise, we can just reroot and flash another custom rom. Let me know how it goes!
Sent from my Sapphire/dream using XDA App
What you need is a simple (full)wipe.
The problem when applying new roms or re-flashing the same rom is that the userdata and cache partitions are not cleaned.
Userdata = all the app and settings you have accumulated through the years.
Cache = as the name says.
When the partitions are not wiped, then complication can and most likely will occur when (re)flashing roms.
So, inside the recovery, chose to wipe all the partition you can find. Then you flash the rom you want. Wait 5-15 min for it to load and you should be good to go.
paulheth said:
Questions:
- If i can get this far, does it mean my phone is rooted?
- I hear I have a 'Perfect SPL', but if the Hero and the CM6 ROM could be flashed, does that matter?
Click to expand...
Click to collapse
Rooted = have SU binaries... my guess = YES you are rooted.
Perfect SPL does not influence rom flashing since you are working from recovery.
If you are flashing from fastboot, then SPL will have a dominant position.
Looking more like hardware.
Seems it may be a hardware issue? Even with the stock RUU rom from HTC there are still sim recognition and wifi flakiness issues.
Any chance a radio re-flash/update would help?