I have the Verizon S4 i545, obviously. Rooted right after getting it in June. Still on Android 4.2.2, kernel 3.4.0-562219, build number i545VRUAMDK. I have never updated anything. Tried, tbh, but OTA fails. But whatever. I have never had an issue with anything, until a few days ago. Now, whenever my phone turns on, regardless of whether it was restarted or powered down then on, It hangs at the Verizon animation, then finally goes to my lockscreen with no notification bar. Phone is essentially useless at this point because when I unlock my phone, I get a black screen that does nothing. Only way to fix it, is to pull the battery, then power on. Works every time. I have no idea what happened to cause this. I have not removed anything system related recently. Any ideas?
I would like to fix the problem and leave it. But if I can't, I might be flashing a new rom.
Kasper DG said:
I have the Verizon S4 i545, obviously. Rooted right after getting it in June. Still on Android 4.2.2, kernel 3.4.0-562219, build number i545VRUAMDK. I have never updated anything. Tried, tbh, but OTA fails. But whatever. I have never had an issue with anything, until a few days ago. Now, whenever my phone turns on, regardless of whether it was restarted or powered down then on, It hangs at the Verizon animation, then finally goes to my lockscreen with no notification bar. Phone is essentially useless at this point because when I unlock my phone, I get a black screen that does nothing. Only way to fix it, is to pull the battery, then power on. Works every time. I have no idea what happened to cause this. I have not removed anything system related recently. Any ideas?
I would like to fix the problem and leave it. But if I can't, I might be flashing a new rom.
Click to expand...
Click to collapse
Are you running a custom rom.
No I'm not. Everything is untouched except for the root process. That's it.
Kasper DG said:
No I'm not. Everything is untouched except for the root process. That's it.
Click to expand...
Click to collapse
I would guess to flash VRUAMDK no wipe factory image.
http://forum.xda-developers.com/showthread.php?t=2301259
Any idea why I'm randomly having this problem?
Kasper DG said:
Any idea why I'm randomly having this problem?
Click to expand...
Click to collapse
I don't really know, I've never encountered a problem like that yet.
Ok. Might try flashing the factory image.
Related
I have the US version of galaxy s3, but it won't let me post in any of the US version's forums for some reason. Anyway, on to the problem.
When i turn my phone on, it boots, i unlock lock screen, and touchwiz home repeatedly force closes about every 5 seconds, along with contacts. I was rooted, but haven't flashed anything. haven't done anything other than root the phone, and it has been about 2-3 weeks since that was done, and have not had a problem until tonight. The problem was completely random, i pulled the phone out of my pocket and turned the screen on and it rebooted. I have the logcat in my dropbox if anyone can look at it and see what might have happened? http://dl.dropbox.com/u/91650856/LogCat_Default_Sat0728_05326.txt
Help please!
Better start a thread in the US forum, this forum is for the International S3.
MattO said:
I have the US version of galaxy s3, but it won't let me post in any of the US version's forums for some reason. Anyway, on to the problem.
When i turn my phone on, it boots, i unlock lock screen, and touchwiz home repeatedly force closes about every 5 seconds, along with contacts. I was rooted, but haven't flashed anything. haven't done anything other than root the phone, and it has been about 2-3 weeks since that was done, and have not had a problem until tonight. The problem was completely random, i pulled the phone out of my pocket and turned the screen on and it rebooted. I have the logcat in my dropbox if anyone can look at it and see what might have happened? http://dl.dropbox.com/u/91650856/LogCat_Default_Sat0728_05326.txt
Help please!
Click to expand...
Click to collapse
Factory reset .
jje
gee2012 said:
Better start a thread in the US forum, this forum is for the International S3.
Click to expand...
Click to collapse
MattO said:
I have the US version of galaxy s3, but it won't let me post in any of the US version's forums for some reason. Anyway, on to the problem.
When i turn my phone on, it boots, i unlock lock screen, and touchwiz home repeatedly force closes about every 5 seconds, along with contacts. I was rooted, but haven't flashed anything. haven't done anything other than root the phone, and it has been about 2-3 weeks since that was done, and have not had a problem until tonight. The problem was completely random, i pulled the phone out of my pocket and turned the screen on and it rebooted. I have the logcat in my dropbox if anyone can look at it and see what might have happened? http://dl.dropbox.com/u/91650856/LogCat_Default_Sat0728_05326.txt
Help please!
Click to expand...
Click to collapse
i was able to ODIN the phone back to stock i was just curious what might have went wrong.
MattO said:
i was able to ODIN the phone back to stock i was just curious what might have went wrong.
Click to expand...
Click to collapse
Sometimes things just don't write properly. Installation of software is always a game of chance, it just usually comes out correctly!
Hi guys,
Lately I've been having problems with the WiFi and BT.
I know it has been like that for a while but I only noticed it yesterday.
The BT on the phone doesnt work - when I try to turn in on it just doesnt... I press the button and it stays the same way.
The WiFi doesnt work - when I try turning it on it says ERROR. and stays like that... not on and not of.
And not only that, another thing is that my phone started crushing A LOT.
I have no idea what's going on... it can crash at any moment without worning... not always coming back (sometimes I have to pull the battery out).
it can happen after 1 minute or after 3 hours...
the 2 things that changed on the phone lately are:
1. swiched from neutrino 2.8EE to 2.9EE.
2. I was in a vecation and when I tried to charge the battery it got only upto 82%. didn't cross it no matter how long it was in...(it was like that for a week).
I have to phone for like a year and a half.
help? anybody?
This is a known problem and it's been reported countless times already. Unfortunately the most likely reason is that your wifi/bt chip is fried. This is a hardware issue (more specifically, a design flaw) and there is no workaround. It has affected many others and they are just as pissed off about it as I'm sure you are. Some even say all Atrixes will sooner or later end up this way because of this design flaw.
Not sure about the crashing, but it could be related to broken wifi/bt.
Hi
I have same problem. I have Atrix 4G from UK Tmobile, with stock froyo. I flashed the stock 2.3.4 with RSD successfully, and i unl*cked the carrier.
Then i noticed, that Wifi don't work good. I don't know turn on: Wifi (error). The other problem, that the finger print scanner isnt work...
These actions do not help: factory reset, unlock BL, custom ROM (i tested Nottachtrix, any ICS ROM, stock froyo), erase all at fastboot, full wipe with CWM...
I am sure, that it is a software bug! (before flash 2.3.4 and carrier unlck, phone works fine...)
Some solutions? (I think, if we restore back to stock, the problem is solve) How can i make a fully reset, which is stronger than RSD flash stock sbf?
edit: http://forum.xda-developers.com/showthread.php?p=13754274#post13754274
or
http://forum.xda-developers.com/showthread.php?t=1035139
rain91x said:
Hi
I have same problem. I have Atrix 4G from UK Tmobile, with stock froyo. I flashed the stock 2.3.4 with RSD successfully, and i unl*cked the carrier.
Then i noticed, that Wifi don't work good. I don't know turn on: Wifi (error). The other problem, that the finger print scanner isnt work...
These actions do not help: factory reset, unlock BL, custom ROM (i tested Nottachtrix, any ICS ROM, stock froyo), erase all at fastboot, full wipe with CWM...
I am sure, that it is a software bug! (before flash 2.3.4 and carrier unlck, phone works fine...)
Some solutions? (I think, if we restore back to stock, the problem is solve) How can i make a fully reset, which is stronger than RSD flash stock sbf?
edit: http://forum.xda-developers.com/showthread.php?p=13754274#post13754274
or
http://forum.xda-developers.com/showthread.php?t=1035139
Click to expand...
Click to collapse
looks promising... did you try it?
I donnot if I can even try it... the first step is "close WiFi"... and I can't. it doesnt go off and doesnt go on... just stays on "Error".
should I just except the fact that I have to get a new phone?
should I send it to Motorola?
Alonleibo said:
looks promising... did you try it?
I donnot if I can even try it... the first step is "close WiFi"... and I can't. it doesnt go off and doesnt go on... just stays on "Error".
should I just except the fact that I have to get a new phone?
should I send it to Motorola?
Click to expand...
Click to collapse
I try it later, but i dont know now SD card. I hope, that it is a correctable bug.
edit: i tryd it, but still not good. Other solutions?
I have the same problem (wifi error, bt does not open). I guess it is a hardware problem but when I installed TopSmart rom (coming from Neutrino) they worked for 10 minutes then they crashed again. If it is a software problem (but i dont think so) there must be the answer that everyone's looking for. I hope it ends up as a software problem.
Sent from my Motorola Atrix 4G
It's most certainly a hardware problem. Clearly the WiFi chip in this phone just dies. This is also why your phone is crashing. You'll just have to leave WiFi off (if you can get to the switch before the phone crashes).
This issue started a couple months ago for me, and today I managed to accidentally flip the WiFi switch on again, sending my phone into an endless cycle of crashing and rebooting. I had to factory reset and re-flash CM10 about three times just to get it to stop rebooting repeatedly (which sucks because I didn't have a recent TiBu backup...). You might have to do this as well if your phone doesn't stop crashing.
I'd say just get a new phone. Don't send it in to Moto because even if you're in warranty they'll likely send you back a unit with a permanently locked bootloader, which isn't worth it.
It is frequent bug on Android phones. (wifi - error)
https://www.google.hu/#hl=hu&gs_nf=1&tok=EBl1OHx7E49rfa9s8zPj_A&cp=13&gs_id=1f&xhr=t&q=android+wifi+error&pf=p&output=search&sclient=psy-ab&oq=android+wifi+&gs_l=&pbx=1&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.&fp=aee7b1a090091e6a&biw=1680&bih=949
MdX MaxX said:
It's most certainly a hardware problem. Clearly the WiFi chip in this phone just dies. This is also why your phone is crashing. You'll just have to leave WiFi off (if you can get to the switch before the phone crashes).
This issue started a couple months ago for me, and today I managed to accidentally flip the WiFi switch on again, sending my phone into an endless cycle of crashing and rebooting. I had to factory reset and re-flash CM10 about three times just to get it to stop rebooting repeatedly (which sucks because I didn't have a recent TiBu backup...). You might have to do this as well if your phone doesn't stop crashing.
I'd say just get a new phone. Don't send it in to Moto because even if you're in warranty they'll likely send you back a unit with a permanently locked bootloader, which isn't worth it.
Click to expand...
Click to collapse
I did turn it off... eventually.
but my phone still crashes... at the same frequency...
*added alogcat files of 2 of the crashes... if anybody can understand it...
For the past week or so the wifi radio on my phone has been acting up. Once or twice a day it will start to constantly cycle on and off. If I manually turn it off while it's in the "on" phase, it usually stays off. But when I go to turn it back on it just goes back into the loop, even if I wait an hour. The only way to fix it is to reset the phone, sometimes more than once (hard reset holding power and volume up). I rooted my phone over a month ago and haven't done anything else root-related since (no ROMs, mods, not even deodex). I did install AdAway, but that was at the time I rooted it and this just started happening. Not sure what could be causing this or if I just need to contact Verizon for a replacement.
Wifi cycling
Spaded21 said:
For the past week or so the wifi radio on my phone has been acting up. Once or twice a day it will start to constantly cycle on and off. If I manually turn it off while it's in the "on" phase, it usually stays off. But when I go to turn it back on it just goes back into the loop, even if I wait an hour. The only way to fix it is to reset the phone, sometimes more than once (hard reset holding power and volume up). I rooted my phone over a month ago and haven't done anything else root-related since (no ROMs, mods, not even deodex). I did install AdAway, but that was at the time I rooted it and this just started happening. Not sure what could be causing this or if I just need to contact Verizon for a replacement.
Click to expand...
Click to collapse
I got a DNA last week and lose wifi when I'm on my patio, which never happened with my Galaxy Nexus LTE. In the house, the wifi cycles a couple of times a day. I would appreciate any input.
This happens to me no matter what network I try to connect to or where I am at.
Anyone else have this happen? I am ready to do a factory reset and I really don't want to since this phone doesn't have an SD card.
any one with same prob?
sandeep.mjs said:
any one with same prob?
Click to expand...
Click to collapse
Did you install a custom ROM and/or kernel?
If custom, a kernel change may help.
If you did any tweaks like overclock, undo those changes.
But to answer your question, this hasn't happened to me.
yearn2burn said:
Did you install a custom ROM and/or kernel?
If custom, a kernel change may help.
If you did any tweaks like overclock, undo those changes.
But to answer your question, this hasn't happened to me.
Click to expand...
Click to collapse
I rooted my phone but have not done anything else besides install AdAway. I planned on installing a few tweaks like the battery percent indicator and location icon remover but honestly the whole odex/deodex thing really confused me so I haven't done anything else.
I am going to get a new SIM card today because my phone keeps saying it doesn't have one and I have to reboot once or twice to get it to come back up, but I doubt that could be the cause of my wifi issues.
As the title suggests, suddenly I started getting force closes with com.android.phone when I'd receive a call. I immediately tried to call out, same story. I've been troubleshooting for the past few hours, and had no luck finding anything relevant on XDA or any other site.
Firstly I switched kernels, since I'd updated to DSB's latest, though I'd had no issues with it until then. That failed, so I reverted to Viper's stock build.prop, undoing some changed I'd been running for a while (and hadn't modified at all today).
With no luck there, I backed up my sdcard and did a full factory reset and formatted the sdcard in twrp and then in cwm, followed by a reinstall of the latest Viper ROM. Even that didn't work, so I relocked and RUU'd back. Twice. Same exact issue. I can text anyone just fine, data over LTE goes on as normal, but anytime I try to make a call, be it with the stock dialer or through a diff one from the play store (for kicks, last resort). I reseated the SIM card a multitude of times, to no avail. I get full functionality with my SIM in my other phone, so I'm sure it must be the hardware itself on the phone. Every time com.android.phone stops, the SIM initialization happens like when you physically re-seat the SIM.
The troubling thing is that I haven't done anything, save for a simple kernel and recovery update, which would've been negated by two RUU runs to stock. I haven't touched the SIM card or anything, at least until that started happening. Furthermore confusing is how all other functionality can remain except for actually making phone calls.
Removing the SIM entirely and dialing a number does the exact same thing, just as an FYI.
Has anyone seen this? Any ideas?
As I've unlocked my phone, my last resort is to go into a VZW store and act like an idiot so they don't check to see if i unlocked it. Further complicating that is the fact that the DNA was actually purchased on my own account, which I closed, and brought to an unlimited data line that was preexisting. I'm half tempted to wait for the official OTA and see if that will remedy the issue, but my fear is this may be a physical issue beyond the remedy of a firmware update.
http://forum.xda-developers.com/showthread.php?t=2126386
Check this thread, me and another member faced the same problem. I can get 3g/2g data, sms and all other functions just right. Just no phonecalls, every time i make a call i get a crash of the app.
So, i am pretty sure this is a software bug. For god's sake, what a strange problem!Did your phone used to work right?
I bought my phone from ebay, did not check if phonecalls are working(i couldn't imagine such a bug) and went straight away to rooting/other kernels/roms etc. But can't find a solution too,tried everything as you, and the worst, i am overseas!!!
Is the update coming soon?
edit1: i have seen lots of threads about sim errors,a very common issue of DNA, i am believing that these two bugs have something in common. No hardware defect, just software bugs.
ergotelis said:
http://forum.xda-developers.com/showthread.php?t=2126386
Check this thread, me and another member faced the same problem. I can get 3g/2g data, sms and all other functions just right. Just no phonecalls, every time i make a call i get a crash of the app.
So, i am pretty sure this is a software bug. For god's sake, what a strange problem!Did your phone used to work right?
I bought my phone from ebay, did not check if phonecalls are working(i couldn't imagine such a bug) and went straight away to rooting/other kernels/roms etc. But can't find a solution too,tried everything as you, and the worst, i am overseas!!!
Is the update coming soon?
edit1: i have seen lots of threads about sim errors,a very common issue of DNA, i am believing that these two bugs have something in common. No hardware defect, just software bugs.
Click to expand...
Click to collapse
thanks for the thread, for the life of me i couldn't find anything exactly relating to what i described. that is spot on though, and def makes me feel a bit more at ease that maybe it can be resolved with an update to the firmware that's due soon.
yea, the funny thing is that it worked flawlessly, i never even got the SIM error message, i'd been texting my gf, a few friends, and my parents and then my pops called in the evening and it immediately closed out the call before it really even rang. i called him right back and that's when the force closes started happening, calls never working agian thereafter. however, i was able to still text everyone i was before and data was working flawlessly as always, just no calls, not even after all the crap i did to troubleshoot.
the update is hopefully going to be out soon. the support documents came out a few days ago. i def can't survive on this galaxy nexus after having used my DNA since launch!
I will wait for the update too, hopefully it will be uploaded today or tomorrow i think. But just because i can't get on the air update, i need to download from a server the update and install it on my own.
If anyone finds a solution or have an idea of what to look/do, please post here. I am pretty sure it is a software bug, something is stucking the application from working properly. The other solution is RMA, but it is a very difficult to send it back and get it back again.
ergotelis said:
I will wait for the update too, hopefully it will be uploaded today or tomorrow i think. But just because i can't get on the air update, i need to download from a server the update and install it on my own.
If anyone finds a solution or have an idea of what to look/do, please post here. I am pretty sure it is a software bug, something is stucking the application from working properly. The other solution is RMA, but it is a very difficult to send it back and get it back again.
Click to expand...
Click to collapse
The update is out now, can someone send it to me too? I am overseas, trying to find a way to download it.
OP, can you test this one to see if you get a fix?Thanks!!!
Ok, I had the same exact issue. I was stock then went to viper Dna then tried going to hatka and soft bricked my phone. I went back to stock using the RUU. That's when I got the com. Android. Phone crash message. So I had to re unlock reboot and then flash viper Dna again. Everything works as it should now.
After saying all that I just got the new update from Verizon. I assume I shouldn't flash this since I'm on a custom rom.
Sent from my Nexus 7 using xda premium
Thanks for the input, really interesting!Will try it right away! Hope you won't have any problems with the update now!
msturner79 said:
Ok, I had the same exact issue. I was stock then went to viper Dna then tried going to hatka and soft bricked my phone. I went back to stock using the RUU. That's when I got the com. Android. Phone crash message. So I had to re unlock reboot and then flash viper Dna again. Everything works as it should now.
Click to expand...
Click to collapse
THIS IS THE SOLUTION!Now working! A HUGE HUGE HUGE THANKS TO YOU!!!! :victory:
ergotelis said:
THIS IS THE SOLUTION!Now working! A HUGE HUGE HUGE THANKS TO YOU!!!! :victory:
Click to expand...
Click to collapse
Hi guys i got a similar problem. My DNA was perfect since yesterday but now i can use data connection for internet. All the other stuff is working fine....SMS,call, wifi, the only thing that is not working is the 3g data. All of this problem came when i flashed the viper DNA, so i flashed the supercharged hoping it was an issue of the rom. Olso with the supercharged the problem was always here.... So i decide to came back to stock and i re-lock my bootloader and flasched stock RUU. But data connection is still not working :crying:
can anyone please tell me what can i do?
Did you install patches 1.1.1& 1.1.2 from viper?They fix some gsm problems.
As I've unlocked my phone
ergotelis said:
Did you install patches 1.1.1& 1.1.2 from viper?They fix some gsm problems.
Click to expand...
Click to collapse
yes but notthing changed.... :'(
Now i'm compleatly stock and the problem is still here.
flash again the viper rom, do the whole procedure again, at least this is what i did and fixed the problem!(stock->viper->stock-> viper and then OK)
ergotelis said:
flash again the viper rom, do the whole procedure again, at least this is what i did and fixed the problem!(stock->viper->stock-> viper and then OK)
Click to expand...
Click to collapse
Which version of viper worked for you?
hard problem
Has any one figured out this problem? I have not been able to received any phone calls since I did s-off. I have tried everything that has been wrote so with no luck. I have relocked my phone and flashed stock RUU no change. Unlocked and tried several roms still no calls. formatted everything under CWM not change. Fixed permissions. Went back and re-locked and reflashed stock RUU. I know that some of the things above have fixed others phones and some still have problems. I also found a script someone wrote lock my phone which now it says locked and flashed stock rom after that still have problem. Does anyone here here a idea that I have not already mentione above? I like my droid dna but if I can't get it to make and take calls it is a paperweight.:crying:
jimmydee62 said:
Has any one figured out this problem? I have not been able to received any phone calls since I did s-off. I have tried everything that has been wrote so with no luck. I have relocked my phone and flashed stock RUU no change. Unlocked and tried several roms still no calls. formatted everything under CWM not change. Fixed permissions. Went back and re-locked and reflashed stock RUU. I know that some of the things above have fixed others phones and some still have problems. I also found a script someone wrote lock my phone which now it says locked and flashed stock rom after that still have problem. Does anyone here here a idea that I have not already mentione above? I like my droid dna but if I can't get it to make and take calls it is a paperweight.:crying:
Click to expand...
Click to collapse
Still broke?
Sent from my HTC6435LVW using xda app-developers app
kaliblazin707 said:
Still broke?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yes it is still broke I just don't know what to do at this point paper weight right now.
Been having a problem with Task's latest ROM (4-14) and the previous version (4-1). Both take several minutes to obtain carrier signal (AT&T) after booting. I've tried flashing with full wipe several times, different modems, and adjusting APN settings, but nothing fixed it. My phone usually picks up service after about 5 minutes, but sometimes I've waited 10+ minutes and had to reboot again, because it still hadn't connected. Also, maybe this is just how it's supposed to work, but I've noticed that while my phone has no service, if I go to System Settings->More->Mobile networks->Access Point Names there's nothing there at all. Just a blank window until it finally connects. Is anyone else having this problem or know of any possible solutions? Thanks!
Samsung Galaxy S II SGH-i777
Android Version: 4.2.2
ROM: Task650
Build: 4.14.2013
Modem: UCLL6
Have you tries rebooting with airplane mode enabled and then disabling it when fully booted? This has worked for me in the past, although I've never had to wait as long as you've stated you have for a signal.
Phalanx7621 said:
Have you tries rebooting with airplane mode enabled and then disabling it when fully booted? This has worked for me in the past, although I've never had to wait as long as you've stated you have for a signal.
Click to expand...
Click to collapse
I tried this method and it didn't work for me , I even did a complete wipe and re-flashed the rom and gapps, I also re-flashed two separate modems amd was never able to connect to the mobile network. when I first flashed the ROM everything worked great, but when my device went to deep sleep it never came back
Phalanx7621 said:
Have you tries rebooting with airplane mode enabled and then disabling it when fully booted? This has worked for me in the past, although I've never had to wait as long as you've stated you have for a signal.
Click to expand...
Click to collapse
Thanks for the advice, but it's a no go. I reboot with airplane mode enabled, but when I disable it my phone still takes forever to get a signal.
maninblack86 said:
Thanks for the advice, but it's a no go. I reboot with airplane mode enabled, but when I disable it my phone still takes forever to get a signal.
Click to expand...
Click to collapse
I have the same problem despite wiping everything many times. mine take approx two minutes to get back the signals and meanwhile emei and baseband remains unknown.
chacha123 said:
I have the same problem despite wiping everything many times. mine take approx two minutes to get back the signals and meanwhile emei and baseband remains unknown.
Click to expand...
Click to collapse
Mine does exactly the same. Baseband is unknown and there's no IMEI info until it finally connects. I also noticed that under service state it said "radio off" until it connects and then changes to "in service".
That's very odd. It's not just this rom it does this on is it?
Phalanx7621 said:
That's very odd. It's not just this rom it does this on is it?
Click to expand...
Click to collapse
I went to the Jedi ROM with no issues....I've used tasks ROM since its infancy and never had one issue until this latest update. Kind of bummed. But in the same hand I'm liking the Jedi ROM also...:thumbup:
Phalanx7621 said:
That's very odd. It's not just this rom it does this on is it?
Click to expand...
Click to collapse
Yeah dude, I've been using Task's ROM for a while now and this has only started happening since the 4-1 version. I even flashed back to the 3-13 build just to make sure and this problem doesn't happen with that build. I was hoping the 4-14 build would fix it, but it didn't. I did see on Task's developer thread someone made a post about having this issue, but it looks like they never posted a logcat or anything to help Task resolve it. I would gladly post one if I could, but I'm new to XDA and they won't let me post on a developer thread.
i have same issues. along with my time going screwy from time to time.
phermey said:
i have same issues. along with my time going screwy from time to time.
Click to expand...
Click to collapse
I no longer have any issues with the time zone changing in the newest build (4-14). I don't know if you're on that build, but the workaround for that problem was to set your own time zone manually.
maninblack86 said:
I no longer have any issues with the time zone changing in the newest build (4-14). I don't know if you're on that build, but the workaround for that problem was to set your own time zone manually.
Click to expand...
Click to collapse
i am still on 4.1. i am not prepared for a full wipe yet.
Apparently, what's happening is the radio doesn't turn on during boot (Radio baseband not recognized error or something). I fixed this problem by turning on the wifi temporarily then turning it off. Apparently this will turn on the radio and should stay that way. I hope this works for you.
epicstar1 said:
Apparently, what's happening is the radio doesn't turn on during boot (Radio baseband not recognized error or something). I fixed this problem by turning on the wifi temporarily then turning it off. Apparently this will turn on the radio and should stay that way. I hope this works for you.
Click to expand...
Click to collapse
That worked dude, thanks! It took me a couple tries, I probably didn't give my phone enough time to boot, but I got it. Definitely a lot faster than waiting for it to connect on it's own.
I wonder why this only seems to affect some of our phones, but not the majority? If I didn't know any better, I'd say it almost seems like they have slightly different hardware. I bought mine directly from AT&T the first week it was released. Don't know if they possibly made any hardware revisions since?
phermey said:
i have same issues. along with my time going screwy from time to time.
Click to expand...
Click to collapse
Did you try turning off the "Automatic Time Zone" option in the Date & Time settings? My phone always sets the time to GMT+0 when I have that turned on.
maninblack86 said:
That worked dude, thanks! It took me a couple tries, I probably didn't give my phone enough time to boot, but I got it. Definitely a lot faster than waiting for it to connect on it's own.
I wonder why this only seems to affect some of our phones, but not the majority? If I didn't know any better, I'd say it almost seems like they have slightly different hardware. I bought mine directly from AT&T the first week it was released. Don't know if they possibly made any hardware revisions since?
Click to expand...
Click to collapse
I have been having this problem as well.
Yesterday I did another wipe and reinstall. I did a full wipe (and in mounts formatted everything except my external SD which was temporarily removed.) after flashing the rom, I rebooted recovery and did another wipe data/factory reset and wiped dalvik, then I installed gapps. I then formatted the cache and data again and rebooted the phone. It seems to have fixed the issue for me.
Kasdarack said:
I have been having this problem as well.
Yesterday I did another wipe and reinstall. I did a full wipe (and in mounts formatted everything except my external SD which was temporarily removed.) after flashing the rom, I rebooted recovery and did another wipe data/factory reset and wiped dalvik, then I installed gapps. I then formatted the cache and data again and rebooted the phone. It seems to have fixed the issue for me.
Click to expand...
Click to collapse
Thanks for the suggestion, but this didn't work for me. Tried it exactly as you said, but still have the problem.
phermey said:
i have same issues. along with my time going screwy from time to time.
Click to expand...
Click to collapse
Same issues here, Ive just resorted to manually entering the time zone, but no solution for the delayed connection.
Caligula36 said:
Same issues here, Ive just resorted to manually entering the time zone, but no solution for the delayed connection.
Click to expand...
Click to collapse
Known issue for months now about the time zone. And apparently some others have experienced a longer than normal connection delay too. Weird.
maninblack86 said:
Been having a problem with Task's latest ROM (4-14) and the previous version (4-1). Both take several minutes to obtain carrier signal (AT&T) after booting. I've tried flashing with full wipe several times, different modems, and adjusting APN settings, but nothing fixed it. My phone usually picks up service after about 5 minutes, but sometimes I've waited 10+ minutes and had to reboot again, because it still hadn't connected. Also, maybe this is just how it's supposed to work, but I've noticed that while my phone has no service, if I go to System Settings->More->Mobile networks->Access Point Names there's nothing there at all. Just a blank window until it finally connects. Is anyone else having this problem or know of any possible solutions? Thanks!
Samsung Galaxy S II SGH-i777
Android Version: 4.2.2
ROM: Task650
Build: 4.14.2013
Modem: UCLL6
Click to expand...
Click to collapse
I have the same problem. I have been using Task's ROM for a few months now and I never had any problems.
updated to version 4-14 and was enjoying it until today. Lost my phone service, for some reason the IMEI got corrupted...I don't even have the access point names choice in mobile networks...no amount of rebooting fixed it...had to flash the phone with a backup file and so far its doing fine..