My phone was S-OFF with BAMF 2.27 bootloader, and AOKP 1.8 with Funky Kernel 1.7, newest Radios (2.22 or whatever).
Dec 12, I installed JB MIUI from a link siulmagic posted on twitter, upon boot I couldn't text or make calls. Made sense, siulmagic doesn't always support cdma, I restored my backup to AOKP and booted up. Still didn't have data. I was a little confused, did a full wipe of data, cache, system, and boot. Installed AOKP 1.8 clean, booted up, no data, I had 3 bars but it was roaming and I couldn't send or receive calls or texts. It was 2am, finals week, went to bed.
Next morning download I downloaded a full RUU (4.03.605.1) from android police
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
and flashed it. It did bootloader, system, radios, like 16 different things. It finished, booted back up into sense which I hadn't seen in months, still roaming! Gave up for 2 days.
Friday I called Verizon (using my cell phone, it could call *611 but no other numbers), they put in a ticket for their network team, this afternoon got a call (to a different number) saying everything was fixed (it was not). However now my phone wouldn't even dial *611, it couldn't dial anything. All phone requests sat at dialing forever (they used to be answered by verizon saying they couldn't connect me). After about an hour on the phone and dialing many weird numbers, *920, #832, 4 battery pulls, reading all the numbers of my phone, I got connected through to HTC because I was still under their warranty. End result, I was going to ship in my phone to have it repaired by HTC.
Means I need to S-ON right?
fastboot oem writesecureflag 3
Boot up...everything works.
I can send/receive texts, calls, it all works.
Does anybody have any idea why? My only thought is that some of the changes Verizon made finally kicked in? Writing a flag in the bootloader couldn't possibly effect that right? Android can't even see that stuff once booted!
crdnilfan said:
My phone was S-OFF with BAMF 2.27 bootloader, and AOKP 1.8 with Funky Kernel 1.7, newest Radios (2.22 or whatever).
Dec 12, I installed JB MIUI from a link siulmagic posted on twitter, upon boot I couldn't text or make calls. Made sense, siulmagic doesn't always support cdma, I restored my backup to AOKP and booted up. Still didn't have data. I was a little confused, did a full wipe of data, cache, system, and boot. Installed AOKP 1.8 clean, booted up, no data, I had 3 bars but it was roaming and I couldn't send or receive calls or texts. It was 2am, finals week, went to bed.
Next morning download I downloaded a full RUU (4.03.605.1) from android police
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
and flashed it. It did bootloader, system, radios, like 16 different things. It finished, booted back up into sense which I hadn't seen in months, still roaming! Gave up for 2 days.
Friday I called Verizon (using my cell phone, it could call *611 but no other numbers), they put in a ticket for their network team, this afternoon got a call (to a different number) saying everything was fixed (it was not). However now my phone wouldn't even dial *611, it couldn't dial anything. All phone requests sat at dialing forever (they used to be answered by verizon saying they couldn't connect me). After about an hour on the phone and dialing many weird numbers, *920, #832, 4 battery pulls, reading all the numbers of my phone, I got connected through to HTC because I was still under their warranty. End result, I was going to ship in my phone to have it repaired by HTC.
Means I need to S-ON right?
fastboot oem writesecureflag 3
Boot up...everything works.
I can send/receive texts, calls, it all works.
Does anybody have any idea why? My only thought is that some of the changes Verizon made finally kicked in? Writing a flag in the bootloader couldn't possibly effect that right? Android can't even see that stuff once booted!
Click to expand...
Click to collapse
You had to flash a cdma patch first. You'll have to do a factory reset from bootloader to fix it.
Sent from my ADR6425LVW using xda app-developers app
Obaterista93 said:
You had to flash a cdma patch first. You'll have to do a factory reset from bootloader to fix it.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Thanks for the response, but I'm not sure you read my whole post. I did a factory reset, as well as a full RUU flash from the bootloader. None of that fixed it. Also the device is now working again as I mentioned in the post, however the only change I made within 3 whole days of the device working again was switching from S-OFF to S-ON.
crdnilfan said:
Thanks for the response, but I'm not sure you read my whole post. I did a factory reset, as well as a full RUU flash from the bootloader. None of that fixed it. Also the device is now working again as I mentioned in the post, however the only change I made within 3 whole days of the device working again was switching from S-OFF to S-ON.
Click to expand...
Click to collapse
Ahhh, sorry. It's a tad late where I live >.< I haven't had that problem myself, I just remembered other users solving it by factory resetting. After rereading... I honestly have no clue. I've never heard of that happening to anyone before. Have you S-offed again since then?
Obaterista93 said:
Ahhh, sorry. It's a tad late where I live >.< I haven't had that problem myself, I just remembered other users solving it by factory resetting. After rereading... I honestly have no clue. I've never heard of that happening to anyone before. Have you S-offed again since then?
Click to expand...
Click to collapse
That's what I'm doing now, once you go s-off it's hard to live without
crdnilfan said:
That's what I'm doing now, once you go s-off it's hard to live without
Click to expand...
Click to collapse
I was fortunate and cursed at the same time. I bought my Rezound used, and when I got it the previous owner had already S-offed it, The downside is... I've never had to do it myself.
Related
Hi
So I tried the alpha version of CM7 last night. Great, but still to early for me. So this morning I went to a restored version of a previous rom I had. I have internet and texting service working. But I'm unable to make any phone calls. I was able to update my PRL without issue, but firmware update resulted in error 1233.
Anything I can do?
I've tried wiping the davlick cache and cache 3x. Wiping data. Trying a different nandback up now.
lmbebo said:
Hi
So I tried the alpha version of CM7 last night. Great, but still to early for me. So this morning I went to a restored version of a previous rom I had. I have internet and texting service working. But I'm unable to make any phone calls. I was able to update my PRL without issue, but firmware update resulted in error 1233.
Anything I can do?
I've tried wiping the davlick cache and cache 3x. Wiping data. Trying a different nandback up now.
Click to expand...
Click to collapse
Maybe a bad backup? Might have to do a full wipe and reflash whatever rom you were on and TB your apps and data.
Rootyourdroid.net. My nephews blog.
I did.
After a clean rom install, was able to a profile and PRL update. Still no changes. Can receive calls, use internet, etc. Just cannot make outgoing phone calls ...
Hmmmmm....Got me stumped. You need someone much brighter then me. Good luck. I'll be keeping an eye on this thread.
You need to call sprint and have them reprovision your phone and t service. Tell them out are roaming too often and unable to make roaming phone ccalls from Verizon's towers and should be able to. It may take 2 or 3 different people before you get a Good one. Also, try to get to tech support, not just any rep
Supra RCMix Shooter
Hi.
Thanks for the reply. What is the "t" service?
Ive called sprint already and was told it should be fixed within 24-48 hours after being elevated to a higher tech support level. I don't know if it should take that long normally or what.
P.S. I don't think I've ever roamed in NYC.
What settings do you have in your roaming settings? Home only or automatic?
Sent from my CM powered 3D
I was on sprint only. Changed it to automatic to try that. No changes.
---------- Post added at 07:33 PM ---------- Previous post was at 06:57 PM ----------
They want me to take the phone into be seen now
lmbebo said:
I was on sprint only. Changed it to automatic to try that. No changes.
---------- Post added at 07:33 PM ---------- Previous post was at 06:57 PM ----------
They want me to take the phone into be seen now
Click to expand...
Click to collapse
Hmmmmm....... Do you know how to run the ruu and return back to s-on? If not I'll link ya. It's going to suck if you get the 1.50
Before you do that, go to the dev section and download the stock rom from haus and give that a go. Seems like I heard someone else have this problem (or something very similar) and it fixed it.
Sent from my CM powered 3D
Which ROM are you using? It's usually a good idea to use the stock one while troubleshooting over the phone so they don't see anything unusual with it. If you do take it in though I would personally leave it unlocked and just flash the 2.08 RUU. The bootloader will still show "locked" with s-off so they probably won't notice it.
I went back to my stock rooted rom yesterday hoping that might fix the issue. So I've left it as that :|
So to flash the 2.08 RUU, I just take the htc update?
If you are on a stock rom, rooted or non rooted, (doesnt matter for this) go on sprint website and choose "chat". Tell them in chat that your getting "error 16" popping up on your phone when trying to call. Let them know you googled error 16 and the fix is called a "HLR Refresh", and you would like them to preform that for you. They will ask you to pull your battery, if they dont have you pull it then they are NOT doing the Refresh. This should fix your issue. If not you may have to run the RUU and head on over to sprint store. Personally I would try all I could before handing my phone to a rep, the reps solution is going to be a software update
Tried that earlier. Reset some values. All while on the stock nonrooted sprint ROM. They keep saying its a hardware issue.
Beats me how its a hardware issue.
Sent from my PG86100 using XDA App
cordell12 said:
If you are on a stock rom, rooted or non rooted, (doesnt matter for this) go on sprint website and choose "chat". Tell them in chat that your getting "error 16" popping up on your phone when trying to call. Let them know you googled error 16 and the fix is called a "HLR Refresh", and you would like them to preform that for you. They will ask you to pull your battery, if they dont have you pull it then they are NOT doing the Refresh. This should fix your issue. If not you may have to run the RUU and head on over to sprint store. Personally I would try all I could before handing my phone to a rep, the reps solution is going to be a software update
Click to expand...
Click to collapse
He's not getting error 16. I think this is something completely different. I had this happen a few weeks back and I just flashed the stock rooted Rom to fix it. BTW lmbebo, when you flashed xHausx stock rooted Rom did you update your PRL and profile?
Every time I've flashed a new rom or restored a nand backup I've updated my proflile and PRL. I've gone through the steps to redo handset activation as well.
I've pretty much made my phone stock except for the s-off status at this point with no resolution.
I'll see if I have enough time to change that back tonight and get into a sprint store tonight. If I can't I'm SOL until next week in terms of time to get into the store.
I guess just for future issues (if this ever arises again).
I've flashed the stock 513 and newest 0808 radios.
I've put rooted stock, xhausx's stock rom, cleanROM, CM alpha 7.
Dropped the phone off. Not sure in what condition or when I'll get it back. Its a network issue for sure.
Can't accèss my google voice website account now either.
Thanks for all the help everyone! appreciate it!
Google voice corrupted my account. All calls were being forwarded to google voice for some reason.
Have brand new /Locked/ e3d now.
Guess I have to wait for an update to the unlock process now? to unlock hboot 1.50 ?
Verizon is sending out replacement phone and need to restore this to stock.
This also started prior to flashing the new ICS leak and after dling ~600mb's via wireless tether.
Not sure if something burned up.
Phone is stuck on 1X only. Tried everything and can't get 3g or reliable 4g.
It get's 4G but only a minute at a time.
I tried doing the various "Fix network bootloop 1x issue threads" but still a no go.
Phone doesn't take the CDMA only option under Mobile networks, it resets back to to lte/cdma.
It never drops to 3g.
I dled the RUU but it does not update nor recover.
Any ideas?
Thanks!
Flash the stock Rom from scrosler's website.
www.scottsroms.com
Droidel said:
Verizon is sending out replacement phone and need to restore this to stock.
This also started prior to flashing the new ICS leak and after dling ~600mb's via wireless tether.
Not sure if something burned up.
Phone is stuck on 1X only. Tried everything and can't get 3g or reliable 4g.
It get's 4G but only a minute at a time.
I tried doing the various "Fix network bootloop 1x issue threads" but still a no go.
Phone doesn't take the CDMA only option under Mobile networks, it resets back to to lte/cdma.
It never drops to 3g.
I dled the RUU but it does not update nor recover.
Any ideas?
Thanks!
Click to expand...
Click to collapse
First thing I'm thinking is you can't RUU back in your situation because the version number is higher than the old RUU. My suggestion is to ROM it, and then flash back to stock RUU, because most ROMs set the version number to 1.0.0.0, therefore all RUU's are a higher version number. Then when you go to flash it, it will recognize, read and flash.
On a side note form this, you're pretty much screwed if you're trying to go to stock from something ripped, since your bootloader will show relocked or tampered, or something other than 'locked' as it shows when completely stock out of the box. This is of course unless you never unlocked it, which means you cant change version numbers, which means you're screwed either way.
Verizon will be able to look at your bootloader and know that it isnt factory stock, so chances are, they are going to charge you for your phone. I'm just trying to be honest and upfront, since I'm kind of a realist when it comes to getting screwed by big corporations like Verizon.
Good luck getting it back to an older version though.
p.s. on the note of your signal issue... the back is on the phone, right? Did you check the contacts inside the cover?
poppajules said:
First thing I'm thinking is you can't RUU back in your situation because the version number is higher than the old RUU. My suggestion is to ROM it, and then flash back to stock RUU, because most ROMs set the version number to 1.0.0.0, therefore all RUU's are a higher version number. Then when you go to flash it, it will recognize, read and flash.
On a side note form this, you're pretty much screwed if you're trying to go to stock from something ripped, since your bootloader will show relocked or tampered, or something other than 'locked' as it shows when completely stock out of the box. This is of course unless you never unlocked it, which means you cant change version numbers, which means you're screwed either way.
Verizon will be able to look at your bootloader and know that it isnt factory stock, so chances are, they are going to charge you for your phone. I'm just trying to be honest and upfront, since I'm kind of a realist when it comes to getting screwed by big corporations like Verizon.
Good luck getting it back to an older version though.
p.s. on the note of your signal issue... the back is on the phone, right? Did you check the contacts inside the cover?
Click to expand...
Click to collapse
The contacts are fine. what if the phone bricked during a software update in hboot? Can they still see relocked and tampered?
Some say that vz doesnt care as long as it has no physical damage.
I don't know about Verizon not caring, but I highly doubt they would take back all of our rooted phones..
I doubt the phone bricked if it booted up. I would flash the ICS RUU and see if the radios fix your signal issue.
Like I said before, I am running Scott's CleamROM and it sets the software versions to 1.0.0.0, so any RUU will flash over it. This is your best bet.
If VZW doesn't care about the bootloader, then you're golden, but don't count on that.
If I may pry, why are you sending it back for the replacement? If it's because of the radios, then I really doubt they are going to just take the phone back, since you could have messed up software to cause the issue.
Just try flashing some stuff before you call it busted. I would go with the ICS leak, Scott's CleanROM, and then back to your old RUU if you want. There's also a patch you have to install to downgrade from CleanROM and ICS leak back to GB, so you might want to do research, also. If you need help finding stuff, just send me a PM.
p.s. Anyone can boot your phone to bootloader (unless of course your phone is in little tiny pieces all over the street), and see that the bootloader is unlocked, possibly tampered for the custom recovery installed, and even if you lock it again, it will say relocked, indicating to everyone that it has been unlocked at one point. 'Unlocked', 'Relocked', 'Tampered', and 'Security Warning' void certain parts of your warranty (in the words of HTC dev.com). The only thing that doesn't void it is if it reads 'Locked'. Period.
Some say that vz doesnt care as long as it has no physical damage.[/QUOTE] Dude I sent two Dinc2 back completed rooted with no problems. Most times the tech at big V. couldn't care less. Most don't wouldn't know what rooting is and the ones that do, more than likely are rooted themselves. The question is if they send it to HTC? And will it meet their requirment now that they have a record that you are rooted as I'm sure if you're had to go thru HTC to unlock. However in reading alot of cases noone have posted a problem with returning a rooted or relocked phone at lease none I've read about. Good luck tho as there's always that first time.
ghostt021 said:
Dude I sent two Dinc2 back completed rooted with no problems. Most times the tech at big V. couldn't care less. Most don't wouldn't know what rooting is and the ones that do, more than likely are rooted themselves. The question is if they send it to HTC? And will it meet their requirment now that they have a record that you are rooted as I'm sure if you're had to go thru HTC to unlock. However in reading alot of cases noone have posted a problem with returning a rooted or relocked phone at lease none I've read about. Good luck tho as there's always that first time.
Click to expand...
Click to collapse
Yeah, I've never tried to send a rooted phone back, personally, but I've never asked anyone at VZW about it. (I'm paranoid that SWAT will descend from the roof and take me down if they knew my phone was rooted)
Good luck dude, just box it up and ship it off then. 'F' 'em.
No go, reflashed ICS leak, the tamper and security warning are gone.
I don't understand why it's not letting me switch to CDMA only. It goes back to CDMA/LTE. Could a bad SIM card cause 3g issues?
I doubt the SIM card would cause 3G issues, but hey, anything is possible I guess. I would say that you wouldn't get ANY signal if the SIM card were bad. Do you have another SIM card phone to test with, perhaps? Just an idea...
Did you go to a ROM instead of just the leak? Hell, you might just have signal issues where you are.. Maybe?
Maybe the antenna did burn up.. never heard of it, but that's not saying it can't happen.
I think tracing your steps back is going to be the best at figuring out the issue. When you flashed the ICS leak, you relocked and flashed, right? no errors? the install went straight down the list with no skipping around? After the install, you went through full HTC/Verizon setup? Have you tried the phone in other locations, i.e. work, groceiry store, gas station, interstate, etc.? Even outside the house will give a different strength... Forgive these sugestions as 'elementary' or 'duh' type suggestions, but something just doesn't sound right.
Also, go to your network settings and try changing the network type from automatic to home only. See what happens.
poppajules said:
I doubt the SIM card would cause 3G issues, but hey, anything is possible I guess. I would say that you wouldn't get ANY signal if the SIM card were bad. Do you have another SIM card phone to test with, perhaps? Just an idea...
Did you go to a ROM instead of just the leak? Hell, you might just have signal issues where you are.. Maybe?
Maybe the antenna did burn up.. never heard of it, but that's not saying it can't happen.
I think tracing your steps back is going to be the best at figuring out the issue. When you flashed the ICS leak, you relocked and flashed, right? no errors? the install went straight down the list with no skipping around? After the install, you went through full HTC/Verizon setup? Have you tried the phone in other locations, i.e. work, groceiry store, gas station, interstate, etc.? Even outside the house will give a different strength... Forgive these sugestions as 'elementary' or 'duh' type suggestions, but something just doesn't sound right.
Also, go to your network settings and try changing the network type from automatic to home only. See what happens.
Click to expand...
Click to collapse
I noticed this happeneng a day prior to flashing the ICS leak. I was using wifi tether do download about 600mb's and notice a couple of hours later that it dropped to 1x. Restarted phone and it went to 4g. I usually switch to 3g to save battery, that's when i notice the problem.
The ics leak flash didn't show any errors.
I am trying to flash GB to this new firmware but i'm having a hard time flashing the PH98IMG RUU from scott's site. It reads and checks it but doesnt flash it.
RUU.exe errored out with "Unknown Error"
Droidel said:
I am trying to flash GB to this new firmware but i'm having a hard time flashing the PH98IMG RUU from scott's site. It reads and checks it but doesnt flash it.
RUU.exe errored out with "Unknown Error"
Click to expand...
Click to collapse
Make SURE you are pulling the PH98IMG for the stock RUU from the android police website, NOT Scott. He didn't post up the new leak. The RUU that Scott has will NOT flash over the old ICS stuff he's put out before.
Go here to get the leaked RUU.
In this process, relock your bootloader, flash the file from A.P.(TWICE, this is important), unlock your bootloader with your unlock token from htcdev, and THEN flash what scott has. It's a time consuming process. It's up to you though. The directions are out there on A.P., Scott's website, all over Scott's thread around the 400-page range for the 4.0.1 release... and my abbreviated directions here.
Grab one of the top three selections, not the pre-rooted version.
also, try going back and re-downloading your ROM file, maybe you got a bad download.
If you upgraded to ics, you can't ruu to gingerbread at all because of the older hboot. But you can flash a gb kernel then a Rom or nandroid+ scrosler sdcard fix
Sent from my ADR6425LVW using xda premium
So, long story short, took the Phone into Sprint so they could look at my headphone jack (was cracked and left ear bud would constantly cut in and out) because its acting up.
Gave the Tech the phone without the battery in it (since he didn’t need to power up the device to clearly see the headphone jack has a huge crack in it) but I left my SD card installed. As he was walking away, I asked him if I could remove my SD card and he let me, then seen that I gave him the phone without a battery. So, I ended up giving it to him (praying he didn’t turn it on and see ViperBoys sick ass ROM booting up) and he accidently pressed the power button turning the phone on. Promptly short after, he removed the battery when the phone was on the HTC screen, didn’t even get the boot animation. I was like OHH $h!t, that gonna mess up my phone & sure as $h!t, it did… Just loops in and out of that screen resetting each time with a little vibrate then looping.
I can get into Fastboot and use ADB, I’ve flashed RUU’s, put Stock image on root of SD and let recovery restore (losing my CWM & my HBOOT 1.400), unlocked, relocked, wiped, thrown, and screamed at it with no luck.
I did do a CWM backup before even setting foot in the Store, so I do have a backup. The 1st thing I tried was restoring it through CWM recovery and that didn’t stop the looping. I can still get into fastboot via power + vol down and adb functionality is still there.
HBOOT is 1.50 and s-on is enabled..
Been reading through threads since lunch and tried many different solutions without success. It seems once a phone is this far gone, people stop responding.
Anyone have any ideas?
New phone will be here tomorrow (free of coarse courtesy of Sprint insurance) but I’ve been without a phone all day and most of yesterday. I’d like to get this one back to stock and booting before I trade it in for the replacement tomorrow
So you ran an RUU and it still didnt work? And you're sure the RUU SUCCESSFULLY ran without any parts of it failing right?
If that's true, there's no hope AFAIK. Try to get it not to show the bootanimation by bricking it further.
yousefak said:
So you ran an RUU and it still didnt work? And you're sure the RUU SUCCESSFULLY ran without any parts of it failing right?
If that's true, there's no hope AFAIK. Try to get it not to show the bootanimation by bricking it further.
Click to expand...
Click to collapse
Yup, RUU ran though fine and finished without error. Thing has been rooted since Revolutionary came out with the 1st rooting scheme for the 3D.. Flashed tons of ROM's never had this problem.
lessegr said:
Yup, RUU ran though fine and finished without error. Thing has been rooted since Revolutionary came out with the 1st rooting scheme for the 3D.. Flashed tons of ROM's never had this problem.
Click to expand...
Click to collapse
My only explanation is that while he removed the battery some of your hardware got borked. This can't possibly be a software issue.
yousefak said:
My only explanation is that while he removed the battery some of your hardware got borked. This can't possibly be a software issue.
Click to expand...
Click to collapse
BUMMER! In case the question comes up I ran "RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed" and it ran just fine.
Hmm, hardware issue. Dont see how I can check for that if it doesnt boot.
Guess I'll just have to wait for the new Phone
try to fastboot oem lock it from fastboot. Then RUU, see if that works.
Why even get this one to work if you are getting a replacement?
Sprint is just going to put the phone back to stock....
jdeoxys said:
try to fastboot oem lock it from fastboot. Then RUU, see if that works.
Click to expand...
Click to collapse
The HTC unlock went as expected. Followed the directions to the "T", then relocked, checked in fastboot (not that I could check anywhere else, LOL) and the phone says "*** RELOCKED***". Ran 2.17.651.5 RUU successfully to the finish. Still looping
WEIRD!
DarkManX4lf said:
Why even get this one to work if you are getting a replacement?
Sprint is just going to put the phone back to stock....
Click to expand...
Click to collapse
Because I just want to know WTF happened!!! Had this Phone since release, abused\used the hell out of it by flashing ROMs constantly, restoring backups, tethering like crazy, emailing, texting, FBing...
No reason for it to crap out on me from a simple mistake, not even of my responsibility, lol!
The only issue I've had with this Phone is that damn headphone jack 1/2 way failing..
Got new phone, terrified to even think about trying to flash new ROM though
lessegr said:
Got new phone, terrified to even think about trying to flash new ROM though
Click to expand...
Click to collapse
LULZ
Same problem with me happened.. Except I had hboot 1.5 and I went one month or two without rooting because I was scared to brick it. I ended up rooting it with desperation and I found my one true love ZR3D rom.
BEAUTIFUL, FAST, plus 4.0 skins ;D. Do it man
Sent from my PG86100 using XDA
Threevo said:
LULZ
Same problem with me happened.. Except I had hboot 1.5 and I went one month or two without rooting because I was scared to brick it. I ended up rooting it with desperation and I found my one true love ZR3D rom.
BEAUTIFUL, FAST, plus 4.0 skins ;D. Do it man
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
DONT TEMPT ME DAMMIT! lol! Just been without a phone for almost 3 days. I'm also seeing a lot of new threads about people experiencing what I've gone through.
Woops, sprint\HTC! once again rooted, and running viperROM.... SWWWWWET!
HBOOT 1.5 and s-on is a *****!
Not to mention... But in Linux, I never got revo recovery to flash... You can do it in windows just do it via fastboot.
Took my Orig cwm bsckup "recovery" & "boot" .img and threw them @ the phone via command prompt.
After cwm was restored, I restored my 4\29\2012 backup that I made before I entered the Sprint store, now my phone is back to the exact same way
It was. Pretty Damn sweet!
So much info here!! I'm truly thankful!!!
Sent from my PG86100 using xda premium
I recently just updated my HTC 3D to the ICS rom by ViRuS.
I used the wire technique to get s-off from hboot 1.5 unlocked
previous i had a stock rom, all i did to root it was unlock it, install cwm recovery, then su.
also i had tried to do a OTA update and broke my root in the process.
after i used the wire technique and thinking i bricked my phone in the first attempt where i left my phone back cover on and had to unplug it then i tried to reboot the phone before plugging it back in(leading me to a screen that said juopunutbear making me think i bricked it) after fixing that and in the meantime installing a new stock rom with root after i had then went to attempt the wire method again, successfuly.
After achieving s-off i went through the steps dictated by virus
--first flashing the firmware without an insue, altho i did it twice anyhow.
----second doing a superwipe
------third installing the ICS rom linked in his post.
after google finished reinstalling apps, i replastered my phonewalls, and went through my settings i discovered i could send sms but i could not recieve them. google voice gets the messages but i am unable to recieve them on my phone. direct messeges to the phone aren't recieved either.
Has anyone else come across this?
Any idea what steps i could take?
i have looked about and not a mention of it.
-------------------------Update:--------------------------
I did some updates from the system settings and no avail
But when i went to activate this phone it brought me to the sprint zone where it tested the
voice and data connections, as soon as it told me i had voice connection i received all my
old texts and then data connection was approved.
happy to have my phone updated and working great!!!!!
Special thanks to ViRuS!
stopping here before i become considered a fanboy....
Click to expand...
Click to collapse
::::::::::Edit:::::::::::
I guess i got a bit overzealous with that and jumped the gun.
Turns out i cant get texts after that and it was a fluke,
also i am getting "error number 16" messages when i try and make an outbound call
At least you can send..the zip from virus made my evo 3d a tablet..its been happening to many ppl now I wonder why noone has adressed this
Sent from my DROID2 using xda premium
Tom.Molyn said:
::::::::::Edit:::::::::::
I guess i got a bit overzealous with that and jumped the gun.
Turns out i cant get texts after that and it was a fluke,
also i am getting "error number 16" messages when i try and make an outbound call
Click to expand...
Click to collapse
Error 16 is in the stickies. Try this:
http://forum.xda-developers.com/showthread.php?t=1194460
Save the Drama for your Mama with Tapatalk 2
After realizing the error i did some
research and fixed both issues this
morning when customer care opened
Turns out sprint was blocking service
because of s-off.
Called them and they had me routed to someone who told me to reset my phone,
I did so and it works fine
Sent from my PG86100 using xda app-developers app
right in the middle of a call my phone cut off and since then i have not been able to make any calls or send texts, my signal bars show a X
i was on insertcoin but have since done the original RUU back to stock 1.15 but no change
i have never flashed the modem other than through the RUU, no ENG hboot or anyhting
my phone is s-off but like i mentioned this happened after being in a call for a minute
happen to anyone else? any clues? thanks in advance!
hyphydragon said:
right in the middle of a call my phone cut off and since then i have not been able to make any calls or send texts, my signal bars show a X
i was on insertcoin but have since done the original RUU back to stock 1.15 but no change
i have never flashed the modem other than through the RUU, no ENG hboot or anyhting
my phone is s-off but like i mentioned this happened after being in a call for a minute
happen to anyone else? any clues? thanks in advance!
Click to expand...
Click to collapse
Re-seat your simcard, might help
Yeah or you fried your SIM card. You could also go into settings > mobile network, and make sure your phone is looking for a CDMA/LTE network instead of GSM or WCDMA or whatever.
Sent from my HTC6435LVW using Tapatalk
thank you for the replies, i tried everything and nothing works, i emailed htc and got no response, so im sending a second email, next step is the trash can, i already got a S5 and i hate it! except the battery life is ungodly amazing, cannot kill it in a day no matter what i do
hyphydragon said:
thank you for the replies, i tried everything and nothing works, i emailed htc and got no response, so im sending a second email, next step is the trash can, i already got a S5 and i hate it! except the battery life is ungodly amazing, cannot kill it in a day no matter what i do
Click to expand...
Click to collapse
Try using their I've chat or calling them. They will usually request you send it in for repair. If your not under warranty they will charge you.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
so just an update in case anyone else ever has this problem, dont give up!
although i had flashed the original RUU many time in attempts to fix my dna's dead radio it had not worked but this time for some reason it did.
the steps i took were.
1, leave the dna in the closet for 2 months
2, get mad and hit it on the table
3, flash the original hboot and RUU from torrented's post
hope no one else has this problem
hyphydragon said:
so just an update in case anyone else ever has this problem, dont give up!
although i had flashed the original RUU many time in attempts to fix my dna's dead radio it had not worked but this time for some reason it did.
the steps i took were.
1, leave the dna in the closet for 2 months
2, get mad and hit it on the table
3, flash the original hboot and RUU from torrented's post
hope no one else has this problem
Click to expand...
Click to collapse
It's mandatory to do a Factory Reset from stock recovery after RUU
I thought I was in the trash can once too, turned out to be the "Mobile network settings".