Database Info

Reboot with NO service???

Can someone explain the nature of the reboots that they are experiencing? I had a reboot on Friday but it was much more then just a reboot, after the phone was finishing powering back up I had no ability to call out as if there was no service. I tried numerous battery pulls and even had Verizon do a reset on there end, nothing helped yet I was still able to receive and send data. Finally after about an hour my service was back. Then the same thing happened again yesterday, I went through the same processes with no success yet. I have tried all the different radio choices and nothing is working, does anyone have any suggestions?
Thanks!!!
Also I am rooted and using the stock rom

Bump..........

Did you do any radio flashes? I know mine rebooted on me when I was trying to flash the GB leak from yesterday and there wasn't even a signal bar...just blank space. I reflashed my radio and everything was ok.
Edit: read the last line that I missed before. I am assuming if you are on a stock rom that you didn't flash any radios (otherwise it would have been noted). Thats the only thing that I have run across causing issues. SMH

Yes, I had similar problem
I was running the Stripped Das BAMF with the new radio (same as the one that recently came out OTA) and had this no service problem twice. Since I'm in a 3G only area, I have been using CDMA auto(PRL) and use the Phoneinfo app to change it. I tried to change the network type to something else but couldn't change it. (I presume the network type is for data, but I was trying to see if changing it would affect the service). The other options were there, but I couldn't select anything other than the CDMA auto. A battery pull fixed my problem both times.
Now I'm running BAMF Remix 1.6.3 with the new radio and everything is fine. I don't change the voltages or overclock. Yesterday as I was driving around town the phone rang, but I didn't answer it. When I got home, the phone had powered down and did a reboot.

Just an additional thought. You might try doing a data wipe/factory reset to see if that helps. Of course, you lose your settings that way, so back up first.

frustrating wifi issue

Ok it started with my first triumph. got it 2 weeks ago lasted all about 3 days and it went dead locked up wouldnt even come on. But whle it was working the stock rom wouldnt connect to wifi no matter what i tried, reset, battery removal, airplane toggle, cleared everything the whole shot. then i installed froycream sandwich and cm7 reloaded and they both worked great the wifi connected no problem. until the phone died.
Enter phone number 2. i had to track down because there werent any anywhere for 100 miles in any direction besides the one i found in a outta the way radio shack. got home the wifi connected right away no problems on stock i thought to myself hmm musta been something wrong woth the first phone from the word go, anyway installed cwm 5.0.2.6, then installed cm7, got all my stuff set up and wifi was working fine. went to bed woke up and went to connect to wifi and nuthing again when you turn wifi on it scanns says connecting and then says disconnected every few mins or so it will try and connect but it just continues to loop. i flashed back to a backup of stock and it connects again. tried froyocream sandwich v1.3 and cm7 reloaded by whysor 3 different builds.

ok so ive been flashing back and forth and and clearing this and that and trying different things , doing things in different order, installing different builds, trying to get it to work.
in between custom roms i decided to restore back to stock and see if it would connect stock again or not. at first it didnt, then i rebooted and tried again and it finally connected...woohoo. i was actually afraid that if i changed anything i would lose functionabilty again. but i flashed froyocream sandwich 1.3 again and cfrossed my fingers and sure enuf it connected when i got all setup. i have successfully used it on and off wifi for the last half hour anyway so ill keep posting my results ive seen a few people have kinda similar probs maybe we can figure it out , im looking through logcat files to see if i can see anything funny but................

I had this problem once before, I had to boot into clockwork go into advanced & wipe dalvik cache, then flash the OC kernel again & all was well. That's if your running CM7 reloaded.

I've run into this issue also

[Q] Wifi Error (but not your usual error)

ok, so weird issue for me.. and idk if anyone else is experiencing it cause it doesn't seem like it.. I'm getting wifi error (and before anyone says anything about my router, it's already configured). It just won't turn on no matter what. I hit it, it says a grayed out "Turning On..." and then error again. No attempt or anything. I go into wifi settings and everything under Wi-Fi is grayed out, that's the network notification at&t wifi hot spot setting and wifi networks. I've been trying hard and absolutely no resolution. A google search only affords me more "fixes" for my router and that's not the issue. If i can get a referral somewhere else that doesn't talk about the router being the issue then i'd greatly appreciate it.
**update**
sorry for the "vote for.." whatever it says, i didn't mean to i was trying to subscribe so please don't get upset about it. kthksgb

Vahnyyz said:
ok, so weird issue for me.. and idk if anyone else is experiencing it cause it doesn't seem like it.. I'm getting wifi error (and before anyone says anything about my router, it's already configured). It just won't turn on no matter what. I hit it, it says a grayed out "Turning On..." and then error again. No attempt or anything. I go into wifi settings and everything under Wi-Fi is grayed out, that's the network notification at&t wifi hot spot setting and wifi networks. I've been trying hard and absolutely no resolution. A google search only affords me more "fixes" for my router and that's not the issue. If i can get a referral somewhere else that doesn't talk about the router being the issue then i'd greatly appreciate it.
**update**
sorry for the "vote for.." whatever it says, i didn't mean to i was trying to subscribe so please don't get upset about it. kthksgb
Click to expand...
Click to collapse
I've never heard of that error before so I don't know. Are you rooted? What version of Android are you running? What I'd do is backup all your apps, text messgs, contacts, etc., and do a factory reset and see if that fixes it. Worst case scenario you could flash a fresh new version of 2.3.5 via RSD Lite and you'd almost surely have the problem fixed, unless it's a hardware issue.

I actually started off on 2.3.5 with the issue, and then i started having problems with my ability to actually get past FB, so i had to do a the rsd fix where i force stock on there again. From that point since it still wasn't working I went and pushed ota which took forever and got onto blaze hoping/praying that it would finally work after that. ultimately nothing worked so I'm here now at the mercy of the forum hoping some guru might have something that I could try.

Vahnyyz said:
I actually started off on 2.3.5 with the issue, and then i started having problems with my ability to actually get past FB, so i had to do a the rsd fix where i force stock on there again. From that point since it still wasn't working I went and pushed ota which took forever and got onto blaze hoping/praying that it would finally work after that. ultimately nothing worked so I'm here now at the mercy of the forum hoping some guru might have something that I could try.
Click to expand...
Click to collapse
Wow brother, if you flashed the 2.3.5 fxz to it and still had the problem, i'm thinking there's a hardware issue.

yea, i figured. so i've already contacted motorola and since i'm still under warranty i can return it and they'll send me another one. them's the break, but i got 2 weeks before i even have to decide on that so its not something i'm rushing towards lol

Try going to adb shell
su
ifconfig tiwlan0 down
(toggle airplane on then off)
ifconfig tiwlan0 up
(toggle airplane on then off)
Maybe that will bring your adapter back up. Hope that helps.

hope this doesn't mean anything bad, but it says error no such device
i did adb shell in cmd prompt, it started up went [email protected] then i did su and it changed to [email protected] and i did what you said.. and it gave me that error

Had the same error problem a few ago using blaze v3 rom. After reboot, it was solved and I could connect to my wifi again.
Have no idea what caused the problem, as I didn't do anything out of the ordinary with the device since the update from blaze 2.5.
Sent from my MB865 using XDA

I am facing same issue on Droid 3. it does not work with Stock ROM, but works with CM9 or AOKP based rom.

wifi error afterusing motofast fast script 2.3.5
i am having the same problem also. it just started right after i did the "flash back to 2.3.5 moto fast script" the first time i used it everything was fine but this time ..which i did the same process....i am getting that same error.and when i try to ota to 2.3.6 it says that i need to turn on wifi ????since then i have tried factory reset and still had the issue.then i rooted 2.3.5 and using cwm i was able to restore a backup.so now i am back on 2.3.6 and i am still having the same problem.i have tried a few wifi fixer apps from the playstore but nothing seems to work. and i still dosnt want to OTA without wifi working :confused........so it seems like there is something nthat went wrong with the motofast script or something got erased ???i hope this will help to try and figure out a solution ......btw im new to this somewhat so please bare with me

trev1134 said:
i am having the same problem also. it just started right after i did the "flash back to 2.3.5 moto fast script" the first time i used it everything was fine but this time ..which i did the same process....i am getting that same error.and when i try to ota to 2.3.6 it says that i need to turn on wifi ????since then i have tried factory reset and still had the issue.then i rooted 2.3.5 and using cwm i was able to restore a backup.so now i am back on 2.3.6 and i am still having the same problem.i have tried a few wifi fixer apps from the playstore but nothing seems to work. and i still dosnt want to OTA without wifi working :confused........so it seems like there is something nthat went wrong with the motofast script or something got erased ???i hope this will help to try and figure out a solution ......btw im new to this somewhat so please bare with me
Click to expand...
Click to collapse
only once did i have problem with wifi on this phone and i never fixed it on 2.3 ...
after a lot of trial and error though, i got it fixed with upgrading to ics.
other than that, does your bluetooth do the same? because symptoms like these usually mean water damage. you might want to check the indicators, (if the a2 has any) --- if you broke your wifi by updating rom, this probably isnt the case.

I noticed that the description for the wlan interface is different in the build.prop between GB and ICS. So you might check your /system/build.prop.
Look for this towards the top of your build.prop
Code:
# wlan interface
wifi.interface = tiwlan0
softap.interface = tiap0
In GB wifi.interface = tiwlan0
In ICS wifi.interace = wlan0
So make sure the value is correct, if the value is wrong it will show your wifi "greyed out" in the settings. Anyway, it's something to try, and I hope that helps. If you change the value, make sure you reboot then check to see if it is fixed.

Since I don't know if anyone is still looking into this at all because I haven't seen many updates to this thread, I'm wondering if anyone has checked the kernal information. I was able to do some searching (btw I haven't sent in my atrix 2 in yet because of work) and I found that there was some issues in regards to the Kernal. I don't know if thats true or not but I would like to see someone test it out or try it out or what have you and see if they can shed some light on the situation because the situation is rather bleek, and i'd rather not have to send in a perfectly good phone that was working just fine before the flash, and still wouldn't work after reflashing the AT&T rom.

[RESOLVED] OPO crashed, got hardbricked and now is having issues getting cell signal

It seems I have managed to solve it by myself. I have loaded factory image of 44S, preformed OTA upgrades and it seems the issue is gone.
The thread can be closed.
Hi, Last week I had my phone connected to power bank over night with "Sleep as Android" turned on. In the morning I got my wake up alert but I was unable to wake up my screen to turn it off... so I had to keep the power button down and shutdown the phone.
After that I have faced boot loop (phone worked fine previous evening).
I have tried rebooting phone couple of times but nothing worked so I have restored backup of last CM11s from TWRP (I was running on CM12 nightly during the crash). Phone booted up poperly and I thought everything is fine however after couple of hours I noticed my phone is asking me for my PIN so it has apparently rebooted. It appeared that it is rebooting every couple of hours and after every call (like 5 sec after call ended)...
I have tried restoring other backup but I was facing the same issue. I have done clean install of current CM12 nightly and got the same...
Facing that I decided to clean my phone completely... I have backed up all my data and did wipe and format of everything of everything I could from TWRP. Then via fastboot I have been tring loading YNG1TAS17L 64GB (from here) by flash-all.bat file. After loading bootloader I have received message <waiting for device> and my phone got hardbricked...
I managed to recover it using this guide.
Then I loaded TWRP again and installed COS 12.
On that point my phone started working stable but after a while I noticed that is started losing cell signal. Sometimes it was just for couple of seconds and sometimes it lost it for good (while tring to hardcode cell operator I was getting "error while searching for networks" and I was able to restore connectivity after couple of reboots).
I decided it could be radio/modem related so I have applied full firmware. No go. Loaded CM12 nightly - the same, loaded that modem from oxygen again - no go.
I have tried installing latest BlissPop, Mahdi ROMs and Oxygen and still facing the same issue.
Tested SIM card on other phone and it works fine, tested other SIM card on my OPO and still the same issue so it is phone related.
Getting the following in logcat during time phone is unable to connect to cell signal:
Code:
05-31 11:57:36.265 D/GsmDCT ( 2457): [0]isDataAllowed: not allowed due to - SIM not loaded and not NV subscription
05-31 11:57:36.265 D/GsmDCT ( 2457): [ApnContext:mms] getApnSetting: apnSetting=null
05-31 11:57:36.268 D/GsmDCT ( 2457): [0]isDataAllowed getRecordsLoaded=false
Anyone has any idea what could be a reason of this issue and how to fix it? At this moment everything is working fine except phone calls and Internet over network operator (Wifi works fine). Thanks in advance.

UP
Anyone has any idea? I believe I have narrowed the problem down a bit. It seems 2G/3G is affected only. As long as I'm in LTE range the connection is stable (that explains why I noticed the problem after few hours when I left home).
I have played a bit with hardcoding band and noticed that LTE is running stable (with GSM Signal Monitoring app). When switching to 3G it is dropping every couple of seconds. The strange thing is that 2G is sometimes affected and sometimes not... When switching LTE->2G it seems to be running pretty stable but when switching from 3G->2G it is acting the same way as 3G.

were you able to fix it?
I went through same experience except that I can barely connect to 4g, 3g 50% of time. Tried many radios but none worked.

spx2000 said:
were you able to fix it?
I went through same experience except that I can barely connect to 4g, 3g 50% of time. Tried many radios but none worked.
Click to expand...
Click to collapse
OP updated the post with how it was fixed. Sorry to bump the thread, but thought I'd inform spx that there was an update. Glad it worked out for you OP, I've saved this in case it ever happens to me, and good luck to spx. Hopefully someone puts this info in a sticky so others can try that if they are stuck too.

I fixed it by reflash raido of xnph52q found here. The zip contains more than the radio firmware.
http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph52q-t3025399
I flashed it before but it didn't work. The only difference is I used TWRP 2.8.6. I remember reading somewhere online that 2.8.7 has issue with OPO

artiwal said:
It seems I have managed to solve it by myself. I have loaded factory image of 44S, preformed OTA upgrades and it seems the issue is gone.
The thread can be closed.
Click to expand...
Click to collapse
Where is the 44S that OP used? I have something similar happening with my phone. I revived my phone from a hard brick and now it's not connecting to the cell network. Wifi works, IMEI shows when SIM is inserted, no EFS partition backup (I didn't know that was a thing to do until it was too late).
FWIW, my current build is KTU84Q and I'm running CM-11-20141008-SNAPSHOT-M11-bacon

Wifi keeps not working

Hi, guys.​
Some time ago, I made a post here talking about a wifi problem that happened after I installed a custom ROM on my Surya (for those who don't know, my wifi keeps disconnecting and connecting when I use ROMs that wasn't made based on MIUI). Sometime later, I reinstalled the original ROM via Mi Flash, as I was told to do. For a while it worked, but one day I turned off the wifi (I was going to school, and the wifi connection there is horrible, so I turned off wifi cause I wasn't going to use) and when I turned it on, it stopped working. Since then, I've been trying to do everything I can to get back, but nothing works. I've already spent the stock ROM on Mi Flash several times and even then, the most I could do was to make the internet work for a few days and the problem again. Does anyone know what i can do?​
At first I thought it was a firmware problem, by the way, I'm suspecting it's a problem with the modem itself, but overall I don't know where the problem is yet.