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 ?
Related
Ok so I rooted this bad-boy I used the HTC unlock method, upon selection of my ROM audibly was miui I wiped and flashed but I did not flash in fastboot. I flashed in recovery and it actually took, problem is I noticed my signal had reduced to 1x speed. Upon flashing to a sense ROM which is cleanrom3.0 I used it to update prl and profile but didn't help stayed the same. So I called Sprint they tried to work some magic to no avail. I then took it upon myself to go complete stock and rid root. Once the ruu flashed and I booted, I noticed I had 3g I checked prl version number and it was the same as before I went to stock. So i didn't get to happy I still wanted more research info for the cause. I then did a speed test and oh god was it slow. Download was 0.02mb/sec upload was 0.70mb/sec strange that upload was faster. But now I would like help to see what I should do next, Sprint tried to say it was hardware. Remember my phone is brand new just died insurance claim. I was thinking flashing a now ROM but thus time make sure I do it in fastboot first. Advice would be nice?
Sent from my PG86100 using xda premium
robdeezle said:
Ok so I rooted this bad-boy I used the HTC unlock method, upon selection of my ROM audibly was miui I wiped and flashed but I did not flash in fastboot. I flashed in recovery and it actually took, problem is I noticed my signal had reduced to 1x speed. Upon flashing to a sense ROM which is cleanrom3.0 I used it to update prl and profile but didn't help stayed the same. So I called Sprint they tried to work some magic to no avail. I then took it upon myself to go complete stock and rid root. Once the ruu flashed and I booted, I noticed I had 3g I checked prl version number and it was the same as before I went to stock. So i didn't get to happy I still wanted more research info for the cause. I then did a speed test and oh god was it slow. Download was 0.02mb/sec upload was 0.70mb/sec strange that upload was faster. But now I would like help to see what I should do next, Sprint tried to say it was hardware. Remember my phone is brand new just died insurance claim. I was thinking flashing a now ROM but thus time make sure I do it in fastboot first. Advice would be nice?
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
I know if your stock sometimes you can get a lemon I had a brand new evo 3d on launch day and the radio part of the phone went bad data sucked and at times wouldn't work... I wasn't rooted.. That was in a week of using the phone....
Another thing is if you know you msl and some of the program codes you could do that reactivate your phone hands free thing it might help you...
I did it back on the EVO back in the day.....
If I remember it was something along the lines of that ##data## edit msl and somewhere in that you could do a reset...
Do this at your own risk tho.... The worst thing that would happen is your phone might not reactivate and you would have to do it again online sprints site...
Yeah sounds about right with the lemon thing, other things are going wrong now that I'm stock. I did the mos thing once before with sprint actually three times before. When I first got it and later when it started tweaking.
Sent from my PG86100 using xda premium
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
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.
eh there,
So I never really did this before and I searched for info, but came up empty.
I picked up an evo lte off of ebay that is s-off/rooted (and now running meanbean 2.9), it still has the previous users name/number in it
sprint wants me to enter: ##72786## then msl
and reset it, they said it will update with new prl/etc. Well i really don't want to do an OTA and loose my settings.
so is there another way i can do this, will i be fine to do this, or has anyone have experience in doing this before?
thanks.
DHDigital said:
eh there,
So I never really did this before and I searched for info, but came up empty.
I picked up an evo lte off of ebay that is s-off/rooted (and now running meanbean 2.9), it still has the previous users name/number in it
sprint wants me to enter: ##72786## then msl
and reset it, they said it will update with new prl/etc. Well i really don't want to do an OTA and loose my settings.
so is there another way i can do this, will i be fine to do this, or has anyone have experience in doing this before?
thanks.
Click to expand...
Click to collapse
If you're rooted, then make a backup and restore when done. Those settings are kept.
I made the backup already. I just didn't want to start this process and find out it would relock/s-on the phone some how. I'm just really inexperienced in this area. thanks
DHDigital said:
eh there,
So I never really did this before and I searched for info, but came up empty.
I picked up an evo lte off of ebay that is s-off/rooted (and now running meanbean 2.9), it still has the previous users name/number in it
sprint wants me to enter: ##72786## then msl
and reset it, they said it will update with new prl/etc. Well i really don't want to do an OTA and loose my settings.
so is there another way i can do this, will i be fine to do this, or has anyone have experience in doing this before?
thanks.
Click to expand...
Click to collapse
It shouldn't do an OTA, they should have only gave you the steps to change whoever's phone number to your own. I don't have all the steps of what u do around but I know you would need to go into something from the dialer and back out their number and enter yours. Then yeah, update prl and profile with what they already told u. I've done this twice when I gave my cuz my past 2 s-off eVos. I think they only gave you part of what needs to be done, the last half. unless your phone already is working under your own number. If that's it then just reset how they said. It won't OTA a rom and you never have to hit install even if an OTA actually downloaded. Never sit there and be one of these people that reads on xda but still takes an OTA.
Swyped from my eVo
i did the update before your reply. but following the steps it just resets identity of the phone, so yours will be loaded ota. There was no updating of the firmware/radios/etc as I was told on the phone. I should've known not to panic, but I like to try to do my research before I try something new. I already called sprint and gave them the new info. (She was nice, but asked me to pull the phone backing off and remove the battery. So I shouldn't have worried about it.)
long story short. phone works and now i'm sifting through a week of messages.
All they want u to do is update the profile and prl. It will do nothing to your rooted status or hurt anything. I would strongly recomend u go into Google wallet and make sure they don't have it set up. If so do a reset on the app. Then u can do a factory reset on the phone to wipe out all the other persons personal info and u can sign into your Google account. As long as u don't do a HTC software update u are not screwing up your root or Rom settings.
Sent from my EVO using xda app-developers app
DHDigital said:
i did the update before your reply. but following the steps it just resets identity of the phone, so yours will be loaded ota. There was no updating of the firmware/radios/etc as I was told on the phone. I should've known not to panic, but I like to try to do my research before I try something new. I already called sprint and gave them the new info. (She was nice, but asked me to pull the phone backing off and remove the battery. So I shouldn't have worried about it.)
long story short. phone works and now i'm sifting through a week of messages.
Click to expand...
Click to collapse
Remove the battery
Lol
The advice is free....the bandwidth, not so much
mods please remove
It sounds like your EFS for wiped somehow.
autoprime has a thread, it's not for our phone but it my work for you. http://forum.xda-developers.com/showthread.php?p=38348745
Your best bet is probably to call Sprint and see if they can do a reset. I can't remember what it's called but they should be able to help.
engine95 said:
It sounds like your EFS for wiped somehow.
autoprime has a thread, it's not for our phone but it my work for you. http://forum.xda-developers.com/showthread.php?p=38348745
Your best bet is probably to call Sprint and see if they can do a reset. I can't remember what it's called but they should be able to help.
Click to expand...
Click to collapse
I called Sprint and even went into the store. They said there is nothing they can do and it has to be my fault (when we have done nothing to the phone because there is no root or recovery even out for our variant). Also, it looks like all that stuff requires root access and a recovery, which we don't have :/ I'm kinda stuck here, I guess. This is ridiculous. All my years of rooting and romming and I get an issue like this on a completely stock phone.
Not sure if this will work lol but it's a full reset. Dial ##RTN# and tap Reset Default. Enter your MSL (if you have it) if it prompts you for it.
Sent from my LG G3 via Tapatalk Pro
Shouldn't they be able to confirm your esn and everything sense this phone has a removable back and it's all on the sticker under the battery?
As a a Sprint rep myself, I would try to manually program it. ANY store rep at a corporate location has access to your MSL, MDN, and MSID. They can attempt the manual programming while connected to their wifi. Not sure if it'll help, since it sounds like your device has lost its EFS.
EFS
Definitely looks like an EFS wipe probably unrepairable by anyone at Sprint try a non corporate Sprint Store (franchise store) they should be more helpful. You may want to put on TEP first you can always take it off later. I would try Best Buy anyways they may take it back. I find with Sprint it pays to try other places even other corporate stores. Sometimes going back to the same store yields different results.
Well now I've went and tried flashtool in my desperation and for some reason the Sprint tot file has given me the stock LG boot animation and initial setup won't go past "configuring your phone" so I feel that anyone that looks at it is going to think it's tampered with. Guess I'll add TEP and see what can be done. Really unhappy with Sprint at the moment. I'm not sure why none of the three guys who looked at my phone could come to a similar conclusion to you guys about the EFS wipe and how to get it back.
Im not sure this will help either but...
In the WiFi calling thread for Sprint, there's some people that had the same LG boot animation. There is a fix for that.
I'll see if I can find it and give you the link.
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
Edit. Found it. http://forum.xda-developers.com/showthread.php?p=54701099
colbyfink said:
Well now I've went and tried flashtool in my desperation and for some reason the Sprint tot file has given me the stock LG boot animation and initial setup won't go past "configuring your phone" so I feel that anyone that looks at it is going to think it's tampered with. Guess I'll add TEP and see what can be done. Really unhappy with Sprint at the moment. I'm not sure why none of the three guys who looked at my phone could come to a similar conclusion to you guys about the EFS wipe and how to get it back.
Click to expand...
Click to collapse
Well, it IS tampered with.
mods please remove
mods please remove