when fresh released his 2.0d i flashed over to that the first day it was released, now everything was working fine until last night. i woke up in the middle of the night and the phone was on roaming, didnt think anything of it and went back to sleep. i awoke this morning to the phone still on roaming so i took the batter off put it back in, and nothing still roaming. i removed the battery again, and again nothing still roaming. so i went into recovery did a data wipe, then rebooted nothing still roaming, wiped again and installed 2.0d again, and again nothing. i wiped the phone one last time, and flashed over damagedtrev, and again still roaming what are my options besides doing an ruu or is that pretty much my best option.
what does it show as your PRI and PRL? and are you with sprint? Might need to update PRI and PRL...
Mine did the same thing. I had the latest PRL and a PRI of 1.70 and I after about a week of running fine I could not get out of roaming. I went back to stock rom.
prl 27392
pri version it says flipz_01 but i was at 1.70.....
and yes im with sprint
wow ok i did a prl update. and it works now that was stupid thanks!
what happens wen u disable roaming?
yeah prl with sprint should be 60663 for anyone else who runs into this
This happened to me but when I did the PRL update nothing would change so I went and hit it with the RUU and used the kitchen to reroot and it worked the next time. I seriously also broke my phone because I did EVERYTHING to not have to set it back to factory. I did so many NAND and BART backups yet nada worked. NOw im running fresh again and loving it =]
this actually happened to me last night. Couldnt get it out, tried putting in airplane mode and the just stuck. so I restarted the phone, it booted up in airplane mode, turned off airplane mode, and all was good again
Joecrack305 said:
and yes im with sprint
wow ok i did a prl update. and it works now that was stupid thanks!
Click to expand...
Click to collapse
you should update your OP to state the solution.
Related
So I had just finished typing a response to a thread, here on xda, when my phone suddenly, all by itself, updated its prl. Only, when it was done, it had changed my prl BACK to 60664. Wired, huh?!
Same thing here. I was surfing the net and by itself the screen turned black and then said updating prl. It then changed from 65000 to 60654.
I just tried updating manually and it said "Your PRL has been updated and changes will be applied now" or whatever it says, but it stayed at 65000.
Hmmm..........
UPDATE:
Now my PRL is the 27392 and stuck on roaming...haha. Will try again...I just want 60664 back! LOL.
UPDATE #2:
Well it said it couldn't update, but then all of the sudden it goes back to 60664....well I got what I wanted...
Okay, there is some misinformation going on.
If you are running a stock EVO, 3G works fine (I just did the 25MB speed test at testmy.net and averaged 1.1Mbps - when ROOTED, I can't get the 6MB test to finish).
When running a rooted EVO in Denver, for some reason, 3G cuts out constantly and won't last more than 2 minutes... generally about 30 seconds and then it dies for a few minutes or until you make a phone call, reboot, put it in airplane mode, etc.
I have tried literally EVERY ROM including the "stock rooted" ROM and they ALL exhibit this behavior.
The only thing I can think of is that something is amiss when flashing the new radio without using the official HTC update package but I'm not feeling like re-rooting my phone all over again with the old radio just to find out.
How many people are experiencing this?
I rooted my EVO and began having issues... Probably about the 13th as stated in the thread... Got really annoyed and flashed the stock RUU (had to take the rom.zip from the Temp folder and rename it to PC36IMG.zip in order to flash though because RUU would not find the phone)... Problem instantly was resolved. Ran the OTA update to get the new radio, thinking it was a radio problem, nope. Still works perfectly fine.
I decided I wanted to try EVOlution V8 today so I re-rooted. Right off the bat, 3G issues. I rooted manually, then NAND, then recovery, then flashed the new radio, REBOOTED, went back into recovery and flashed the ROM...
Now I just ran the RUU and flashed back to stock and everything is working fine. So there is something about the procedure to root that is causing the problem and I don't know if its Denver-specific or what...
I can tell you I didn't have any problems until I unlocked NAND and flashed the permanent recovery. Toast's original root gave me no issues... but that may just be coincidence.
If I decide to stop being lazy, I may re-root and skip updating the radio and see what that does... But for now, I have to conclude it is a rooting issue, NOT a network issue.
Hi, about 5 days ago my wifi stopped working. I'd turned it off a few days earlier since I didn't need it. When I try to turn it back on now though, it takes a few seconds and then says error. I'm not sure what's wrong with it.
Since then I've reflashed my phone rom (leedroid), factoryreset it, and updated the radio. nothing so far has fixed it. Mobile data still works so I wouldn't think it was hardware, but a software error shouldn't have survived the wipe and the radio update.
Does anyone have any suggestions?
blackied said:
Hi, about 5 days ago my wifi stopped working. I'd turned it off a few days earlier since I didn't need it. When I try to turn it back on now though, it takes a few seconds and then says error. I'm not sure what's wrong with it.
Since then I've reflashed my phone rom (leedroid), factoryreset it, and updated the radio. nothing so far has fixed it. Mobile data still works so I wouldn't think it was hardware, but a software error shouldn't have survived the wipe and the radio update.
Does anyone have any suggestions?
Click to expand...
Click to collapse
I had similar issue when flashing another kernel on my stock ROM. Maybe your kernel isn't compatible with the radio or the kernel modules haven't been applied correctly. Hardware error should be presumed after flashing original RUU.
The thing is that I hadn't played with my phone since last year. the wifi just randomly stopped working. It was still on 1.22ghz kernel 1.0.2. It got reset to stock kernel when I factory wiped it.
I've gotta go travelling again for work tomorrow so I'll try flashing the original ruu back next weekend. Would it just be a case of restoring the original nandroid backup I did before I first h-booted/rommed it?
blackied said:
The thing is that I hadn't played with my phone since last year. the wifi just randomly stopped working. It was still on 1.22ghz kernel 1.0.2. It got reset to stock kernel when I factory wiped it.
I've gotta go travelling again for work tomorrow so I'll try flashing the original ruu back next weekend. Would it just be a case of restoring the original nandroid backup I did before I first h-booted/rommed it?
Click to expand...
Click to collapse
As far as I know, factory wipe deletes just the user data. I might be wrong though, because this is my first android, so I'm still learning the basics on rooting, kernels, etc. But from your first post it seemed that you updated your radio in that period, so this might be the clue to what happened. I don't know if the nandroid backup would restore everything to stock, but I'm pretty sure that the original RUU would. Still, you should follow a procedure that would allow you to keep your root (I think if you have radio S-OFF, you'd be able to flash 1.32 RUU and just root it). Anyway, you can't return the phone for warranty services with a custom ROM, so you still need to flash a stock RUU.
Sorry, I should clarify: I did the radio update yesterday to see if it could fix it. It wasn't the cause.
So.... I was stuck at the M logo after trying to update to a newer version of MIUI. I successfully SBF'd back to stock froyo and my phone won't activate. When the activation call tells me to press "1", it simply goes silent.
Now I somehow bypassed the activation screen, I don't think that was a good idea because it forced me to connect via wifi. I just said "screw it anyway" and went ahain to reroot. Then I installed CM7 (since I current don't have the MIUI zip I was previously running on my phone). Now I am stuck at the CM7 logo. Not sure if I should SBF again or what I should do. I'm kinda freaked.
Also, I have never had a problem SBFing before. This seems more serious than before.
Update: Wiping data allowed me to boot up in CM7. Still cannot activate my phone. Whenever it prompts me to press "1", all I get is complete silence.
I'm currently at UT Dallas, so I don't think location is a problem is it? Actually it shouldn't be because I bricked my phone here before. Had to reactivate it and it worked great.
Man, this is the first time my phone won't activate.
Yes I know I am posting a lot, but since no one is here to help currently I'm trying things out on my own.
I tried restoring a nandroid I had of CM7 previously. Man I thought this was always a failsafe....
Just thinking of things I did since the last time I activated my phone. I updated something (radio version, I don't really know much about it), it was supposed to make my 3G faster or whatever. But I mean I've SBF'd, factory reset and everything, so that shouldn't be an issue?
Gosh dang, I just want my phone back the way it was 2 hours ago.
One of the reasons nandroid might not be working is that I might have a different version of clockwork on my phone. I remember before having a version where the test was blue, but I forgot the version number. Now the one I get with rom manager is green (like the one I had before I got the blue one).
Man I am sooo confused here. I am completely at a loss. I am out of ideas. I need help.
So I realized I did not have the second init version of clockwork. I just flashed that, and I'm waiting to see if I will get any errors. If I get this to work I am going to flash the version of MIUI I had and try to restore my more recent nandroid (since Ive gotten MIUI).
Yup problem solved. Not sure what was causing the problem, but at least its solved. I'm gonna be extra careful next time I flash something.
Not sure on this way. Running Stable 4.2.2 Google Edition and had 0 problems until a few hours ago. Went out after dinner, tried to google a phone #, but had no data. Rebooted (just for kicks), and still nothing and no voice. Trying to make a call I get "Mobile network not available". I tested using my daughters G3 and worked perfect so I know it's not that.
So, I would like to try 1 of 2 options, open to either.
1. Revert to the stock 4.2.2 and wait till the 4.3 comes around
2. Upgrade to test a newer ROM. I am reading up on the MF9 but a little unsure, if I am running an MD9, can I simply flash a newer MF9 ROM onto what I have?
I don't want to brick this phone, so what's the best way to move forward and hopefully fix this issue.
Thanks
Wipe your phone and flash a touchwiz ROM. Update prl and profile.
Sent from my SPH-L720 using Tapatalk 4 Beta
daniel4653 said:
Wipe your phone and flash a touchwiz ROM. Update prl and profile.
Sent from my SPH-L720 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks. Looking here http://forum.xda-developers.com/showthread.php?t=2303917 there are plenty, but as I said, I am still on the MDL ROM, so I would assume pick an MDL touchwiz, no?
Actually I have a blu-Kuban (touchwiz) nandroid, I restored to that backup, and had the same issue. No voice, and the PRL, etc. all failed to update. I am downloading the stock deoxed MDL, and will try a wipe/clean install of him.
Tnx again
xlancealotx said:
Thanks. Looking here http://forum.xda-developers.com/showthread.php?t=2303917 there are plenty, but as I said, I am still on the MDL ROM, so I would assume pick an MDL touchwiz, no?
Actually I have a blu-Kuban (touchwiz) nandroid, I restored to that backup, and had the same issue. No voice, and the PRL, etc. all failed to update. I am downloading the stock deoxed MDL, and will try a wipe/clean install of him.
Tnx again
Click to expand...
Click to collapse
I'm actually running Blu Kuban as well and I do not have this issue. Try turning the cell data toggle off and back on. Also, make sure you aren't in airplane mode. I have noticed that sometimes the toggle is on while the airplane symbol will not show in the status bar.
jaywaka2713 said:
I'm actually running Blu Kuban as well and I do not have this issue. Try turning the cell data toggle off and back on. Also, make sure you aren't in airplane mode. I have noticed that sometimes the toggle is on while the airplane symbol will not show in the status bar.
Click to expand...
Click to collapse
Thanks, but since I did try a restore, that would ensure airplane mode was not the case as I don't use it nor would I have 2 ROM's both doing the same thing. I did do a wipe/restore with no luck, so now going to do a wipe/flash. If still nothing, will have to resort to going to stock and taking it to a local sprint shop!
Thanks
xlancealotx said:
Thanks, but since I did try a restore, that would ensure airplane mode was not the case as I don't use it nor would I have 2 ROM's both doing the same thing. I did do a wipe/restore with no luck, so now going to do a wipe/flash. If still nothing, will have to resort to going to stock and taking it to a local sprint shop!
Thanks
Click to expand...
Click to collapse
if restore fails.. try ##786# > reset on stock rom. you need your SPC/MSL for this.
if the 786 reset fails.. let me know in about device > status if your phone number is still listed.. and what PRL is shown.
autoprime said:
if restore fails.. try ##786# > reset on stock rom. you need your SPC/MSL for this.
if the 786 reset fails.. let me know in about device > status if your phone number is still listed.. and what PRL is shown.
Click to expand...
Click to collapse
BAM. Worked like a charm. Naturally have all my spring bloatware and such, but I can at least make a call! Not sure how/why that happened, but it did re-activate fine, so looks like were back in business!
Thanks for all the read/replies!