Database Develop

[Q] Stop Android from updating to 2.2

Is there a way to stop my Droid from updating OTA to FroYo? I have flashed my Droid over to Cricket and have Bugless Beast v0.4 installed, and now since the 2.2 OTA update has been released I get a constant notification that the update is available. The only options I get are to install now or to install later, but what if I don't want to install it all and just get rid of the pesky notification that keeps popping up every so often after I press install later. I already have 2.2 on my system with Bugless Beast so I'm not really missing out on anything. I don't want to update and have to reroot, reinstall Bugless Beast, and reflash my Droid to Cricket again. I'm happy where my system is at

If you have a custom recovery, then as soon as you reboot into the installation your phone thinks that you've accepted, but the custom recovery blocks the installation and you stay on BB.

What do you mean by reboot into installation?
I've booted into clockwork recovery and then restarted the phone, but nothing seemed to change. Is that what you meant to do?

Flash SPRecovery. Then select "install now". It will send a notification that it has been installed on your phone to the servers that send out the OTA but SPRecovery will block the installation of it onto your phone, thus stopping the notifications of an update and keeping you on BB v.04 w/ Cricket. You can flash back to CW Recovery if you want to afterwards.
Sent from my Droid using XDA App

Im also running BB.04 and got the OTA notification today. Glad I found this thread because I was starting to get worried. I clicked 'install now', rebooted and so far no notification and I am still on BB.04. Woot!

Thank you for this!
Running BB 0.4. I saw the verizon 2.2 Froyo upgrade this morning, and for a second I was psyched verizon finally pushed it out... then I was a little worried about what was going to happen to mine since it was rooted and running a 2.2 Rom I was already happy with. Just like this thread says, I clicked install, and the phone rebooted right back up to my BB 0.4 without any issues.
I'd hate to say I'm a leech, but you guys have so much information here, and I cannot stop reading lol. I commend everyone one of you Devs for all the work you do!
Thank you again,
-Dano

Yup, it worked perfectly! Thank you!

Interesting. I was able to block it the first time but it popped up again. Anyone know why? Maybe there is another update to the 2.2 OTA update?

I was having the same issue with the ota update until I came across this:
http://www.peteralfonso.com/2010/08/how-to-stop-ota-notifications-on.html#more
it says it is for Buggles rom but I am using a different rom and it worked just fine

I had received this notification about four times before it recognized that I'm updated without rebooting the phone for it to be blocked. Nothing else had to be done except for saying yes.

stephen730 said:
whatchoo mean able to block it? You mean you clicked install later? Or you let it run and it goes away?
If you let it run/fail it will just come back again a day later, a week later, next time you reboot, next time you come out of screen off, etc... Its done it to me and it sucks cause it won't go away number 1, and number 2, i hate to keep rebooting to fail and possibly missing calls/texts... especially when you first wake up and the message is there like a nagscreen or advert.
Click to expand...
Click to collapse
I clicked install now and my recovery image blocks the installation when rebooted. It shows the Android guy with the exclamtion point but it doesnt finish the install. Reboot then im back to the way I was. Im running BBv.4 btw. I havent got another prompt yet.

[Q] Bionic won't activate Pageplus after JB upgrading

I'm a Pageplus user. After flashing 6.7.246 (ICS 4.0.4), I got OTA to 98.72.22 (JB 4.1.2) successfully.
But I'm stuck then when trying to activate Pageplus OTA by calling *22800:
I kept getting "Sorry, this SIM card is not recognized or registered..", no matter how many times I tried.
There's another notified error: "Unknown SIM card detected"
It's abnormal b/c it should fail only 2-3 times, then taking me to the activation screen.
The 4glteSIM card inside was activated before and used on the 6.7.246 stock build.
FYI, I also reflashed 6.7.246 one more time on top of 6.7.246 and didn't encounter the activation problem. So I'm superised to have this issue after upgraing.
Please advice me if you have any idea.
Thanks in advance.

Did you keep root? And if you did flash a rom like cm10 and then activate the rom like you did on ics. I did that and then I rebooted in stock jelly bean and it was activated. Hope that helps!
Sent from my DROID BIONIC using xda app-developers app

Thx for your reminding. I'll try this way.
Did you install the cm10 with safestrap 3? I tried to install it on the JB but failed. Does it require a rooted JB?
I tried to search but cannot find an effective way to root Bionic JB.
I'll appreciate if u can give some detail abt: A. the JB rooting method, and B. How to install cm10 (or the justed released Blurry-JB_2.4.zip) while keeping the JB stock rom.
Thanks a lot!
Wilsono1050 said:
Did you keep root? And if you did flash a rom like cm10 and then activate the rom like you did on ics. I did that and then I rebooted in stock jelly bean and it was activated. Hope that helps!
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse

Idk if there's a jelly bean root method for the droid bionic. But I kept root after the ota. Then with safestrap 3.11 I installed cm10 and activate it. It usually retrieved the activation when the phone boots up with cm10.
Sent from my DROID BIONIC using xda app-developers app

I managed to have the JB stock rom rooted anyway (by the virtual box approach).
Then I was allowed to install safestrap 3.1, then the newest Blurry JB 2.4.
I tried to "activate" from the step 2 ("2-Getting phone ready for OTA Activation") of the old instaruction:
http://www.howardforums.com/showthr...CS-OTA-Activation-TXT-MMS-3G-ROOT-on-PagePlus
But the CDMA Workshop didn't find the port. I assume the reason is that safestrap has blocked the normal bp-tools booting way.
So I can only start from "3-OTA Activation".
After changing "Network Selection" to "CDMA Only", I rebooted and dialed *22800. Still get the same error "sim card not recognized or registered".
Can you please detail how did you "activate" it under cm10?
Many thanks.
Wilsono1050 said:
Idk if there's a jelly bean root method for the droid bionic. But I kept root after the ota. Then with safestrap 3.11 I installed cm10 and activate it. It usually retrieved the activation when the phone boots up with cm10.
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse

Okay, if you install the jb blurry rom its going to be the same problem as stock because they're pretty much the same. What I did is 1. Kept root after the ota 2. Installed safestrap 3.11 3.) Rebooted into safestrap and created rom slot 1 and installed cm10 rc2 and gapps. When I booted up it activated by itself for me. I then booted up to stock rom and it was activated as well, but had to install the build prop. so I wouldn't get the unregistered sim error thing. Hope that helps!
Sent from my XT875 using xda app-developers app

I installed the cm10.1.0 rc2 into the slot 1 (with and without gapp), but reboot get a blank screen. Have to pull the battery to get reboot to ss.
Wilsono1050 said:
Okay, if you install the jb blurry rom its going to be the same problem as stock because they're pretty much the same. What I did is 1. Kept root after the ota 2. Installed safestrap 3.11 3.) Rebooted into safestrap and created rom slot 1 and installed cm10 rc2 and gapps. When I booted up it activated by itself for me. I then booted up to stock rom and it was activated as well, but had to install the build prop. so I wouldn't get the unregistered sim error thing. Hope that helps!
Sent from my XT875 using xda app-developers app
Click to expand...
Click to collapse

may thx. that work!
taller238 said:
I installed the cm10.1.0 rc2 into the slot 1 (with and without gapp), but reboot get a blank screen. Have to pull the battery to get reboot to ss.
Click to expand...
Click to collapse

taller238 said:
may thx. that work!
Click to expand...
Click to collapse
Did you get it to work?
Sent from my XT875 using xda app-developers app

did anyone get this to work?
Thinking of just saving myself the headache and getting a droidx2.
I'm running cm10.1 and safestrap 3.11 3. I'm going to try a dealer tomorrow to see if they can activate it on pageplus.
I haven't activated a phone on pageplus for a while. I've been using simple mobile, straight talk and h20

taller238 said:
Still get the same error "sim card not recognized or registered.
Click to expand...
Click to collapse
I had the same problem when I went from GB to ICS. I just ignored it and kept trying and trying (based on advice/steps I found elsewhere) and after a few times it worked. So I would suggest trying it about 10-12 times in a row to see if it works.
Also, here is the method I used for GB to ICS, I'd be interested to know if they help you move from ICS to JB:
Re-activating phone
1. Remove any old Motorola Droid Bionic drivers you may have on your computer and install the newest ones.
2. Turn phone off and turn back on in BPTools mode. Then plug the phone into your computer via USB.
3. Open DFS. Click "Ports" and select the COM port for your phone. Next, click the "SPC" button.
4. Click the "Programming" tab and then the "General" tab. Change the "Ruim Config" to NV_ONLY and click "Write".
5. Click the "Data" tab. Under the "Mode" section, change the "HDR SCP force AT config" option to "RevA_MFPA" and click "Write".
6. Close DFS and unplug phone from USB port.
7. Go to the dialer and dial ##7764726 (##PROGRAM). When prompted for an SPC password, enter "000000" and hit verify.
8. Go to "06 Test Mode". Hit "Next" twice. Then, change the Network mode to "CDMA Only".
9. Back out to the home screen; the phone will automatically restart.
10. After the phone has restarted, go to the dialer and dial *22800. Ignore any SIM card error messages you may see; just keep trying *22800 until you reach the activation screen.
11. Follow the instructions to activate the phone.

I have been working on this for HOURS and tried just about every single thing I could. Root, CDMA workshop, DFS, MDN, MIN, SIN, Safestrap, CM10.1, CM10... what a mess! I can attest that it is possible to get working but might be very painful. I read the numerous new and old threads trying to piece together information. In the end it's hard to say what really worked but let me comment on a few things:
1) *22800 never worked on the stock ROM. Believe me, I tried it about 200 times.
2) You can program in your MDN/MIN/SID using DFS. However, doing so left me with no incoming calls/texts. Only outgoing... weird.
3) CM10.1 did nothing for me. There was a very annoying issue where I tried to activate it and it acted like it was going to but I couldn't "press 1" since the keypad was disabled during activation.
4) Hashcode's CM10 STOCK didn't boot at all. I tried it with both Safestrap 2.11 and 3.11. CM10 KEXEC booted.
5) I finally got the activation to work in CM10 KEXEC with Safestrap 3.11. After activation worked, incoming calls were fixed.
So... here's the kicker. After pulling my hair out and being frustrated for many, many hours I gave the phone to my wife. I had dialed *22800 and when it started to say "press 1" I handed the phone to her.
"See?!" I said.
"See what?" she said. She poked at the screen a bit.
"It wants me to press 1 and there's no dialpad."
"Hmmm..." she said.
Suddenly I heard the sound of ringing. "Wha...?! Hey, give me that. A different screen? 'Your phone is being activated now, please wait 15 minutes.' GAH! I mean... yay!"
I asked my wife what she did. She was like, "I dunno... I pressed Home Menu Back or something."
So... if I had to guess on a procedure I think it would be like:
1) Update phone to JB if not updated already.
2) Use easy Virtualbox method to root.
3) Go through CDMA/DFS rigamarole (NV only RevA_MFPA yadda yadda)
4) Reboot and set CDMA only. Use BuildProp Editor to set telephony.lteOnCdmaDevice=0.
4b?) At some point I used DFS to manually program MDN/MIN/SID, but I'm not sure this is necessary.
5) Install Safestrap 3.11
6) Install CM10 KEXEC with Safestrap 3.11 in slot 1.
7) Boot CM10 and *22800 away! Cross your fingers, hand the phone to whoever is next to you in despair.
8) ???
9) Profit!
I erased Safestrap slot, uninstalled recovery and uninstalled the app when I was done.

has anybody successfully activated the stock JB on the Bionic on PagePlus?
no progress on this yet since I can't find any success stories on Hofo either.
thanks
BD

BuonaDomenica said:
has anybody successfully activated the stock JB on the Bionic on PagePlus?
no progress on this yet since I can't find any success stories on Hofo either.
thanks
BD
Click to expand...
Click to collapse
they all claim this works
Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
This one confirmed also
Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms
My brothers bionic activated just fine also...sometimes you just have to follow the steps Exactly as written

primetime^ said:
they all claim this works
Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
This one confirmed also
Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms
My brothers bionic activated just fine also...sometimes you just have to follow the steps Exactly as written
Click to expand...
Click to collapse
well your links are not working as I want to check it out

primetime^ said:
they all claim this works
Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
This one confirmed also
Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms
My brothers bionic activated just fine also...sometimes you just have to follow the steps Exactly as written
Click to expand...
Click to collapse
BuonaDomenica said:
well your links are not working as I want to check it out
Click to expand...
Click to collapse
Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
http://www.howardforums.com/showthread.php/1794056-Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms
http://www.howardforums.com/showthread.php/1795498-Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms!
they weren't links,,, google is your friend,,, they are at howardfourms enjoy these links though...
gonna be looking them over myself
.

Kralik said:
I have been working on this for HOURS and tried just about every single thing I could. Root, CDMA workshop, DFS, MDN, MIN, SIN, Safestrap, CM10.1, CM10... what a mess! I can attest that it is possible to get working but might be very painful. I read the numerous new and old threads trying to piece together information. In the end it's hard to say what really worked but let me comment on a few things:
1) *22800 never worked on the stock ROM. Believe me, I tried it about 200 times.
2) You can program in your MDN/MIN/SID using DFS. However, doing so left me with no incoming calls/texts. Only outgoing... weird.
3) CM10.1 did nothing for me. There was a very annoying issue where I tried to activate it and it acted like it was going to but I couldn't "press 1" since the keypad was disabled during activation.
4) Hashcode's CM10 STOCK didn't boot at all. I tried it with both Safestrap 2.11 and 3.11. CM10 KEXEC booted.
5) I finally got the activation to work in CM10 KEXEC with Safestrap 3.11. After activation worked, incoming calls were fixed.
So... here's the kicker. After pulling my hair out and being frustrated for many, many hours I gave the phone to my wife. I had dialed *22800 and when it started to say "press 1" I handed the phone to her.
"See?!" I said.
"See what?" she said. She poked at the screen a bit.
"It wants me to press 1 and there's no dialpad."
"Hmmm..." she said.
Suddenly I heard the sound of ringing. "Wha...?! Hey, give me that. A different screen? 'Your phone is being activated now, please wait 15 minutes.' GAH! I mean... yay!"
I asked my wife what she did. She was like, "I dunno... I pressed Home Menu Back or something."
So... if I had to guess on a procedure I think it would be like:
1) Update phone to JB if not updated already.
2) Use easy Virtualbox method to root.
3) Go through CDMA/DFS rigamarole[/URL] (NV only RevA_MFPA yadda yadda)
4) Reboot and set CDMA only. Use BuildProp Editor to set telephony.lteOnCdmaDevice=0.
4b?) At some point I used DFS to manually program MDN/MIN/SID, but I'm not sure this is necessary.
5) Install Safestrap 3.11
6) Install CM10 KEXEC with Safestrap 3.11 in slot 1.
7) Boot CM10 and *22800 away! Cross your fingers, hand the phone to whoever is next to you in despair.
8) ???
9) Profit!
I erased Safestrap slot, uninstalled recovery and uninstalled the app when I was done.
Click to expand...
Click to collapse
THANK YOU so much for making this post! I was finally able to activate my bionic after a week of reading the internet. lol. To update this post, yes, you need to do 4b. That step was what got me over the hump.

Anyone know the reason why no 3G? 1x works just fine. When toggle cdma/evdo, it still shows 1x.

I found some useful information about this about a month ago and some more details recently.
The system app com.motorola.setupwizard.phoneservice (VzwPhoneService.apk) actually intercepts attempts to call the activation numbers. The manifest file hinted at it with the names of the permissions and intents it has in there, and recently looking at decompiled source code confirmed it. The app is also responsible for SIM-based activation for Verizon 4G.
This app seems safe to disable for those on Verizon MVNOs; it is also on lists online of apps that people have safely disabled. When disabled, you can freely call up the activation screen with *228 or its variants.
Note that if you disable that app with a method that is permanent, like changing file extension, moving, or deleting, you should also disable com.motorola.setupwizard.controller (VzwController.apk) by one of those methods. If you ever wipe data, this will prevent it from getting stuck after the welcome screen if you tap start instead of doing the 4-corner bypass. (VzwController gets stuck waiting forever for the disabled VzwPhoneService) A side effect of disabling the additional app is that you no longer need to do the 4-corner bypass on first boot after wiping data when the phone isn't activated.

ShadyDreamer said:
I found some useful information about this about a month ago and some more details recently.
The system app com.motorola.setupwizard.phoneservice (VzwPhoneService.apk) actually intercepts attempts to call the activation numbers. The manifest file hinted at it with the names of the permissions and intents it has in there, and recently looking at decompiled source code confirmed it. The app is also responsible for SIM-based activation for Verizon 4G.
This app seems safe to disable for those on Verizon MVNOs; it is also on lists online of apps that people have safely disabled. When disabled, you can freely call up the activation screen with *228 or its variants.
Note that if you disable that app with a method that is permanent, like changing file extension, moving, or deleting, you should also disable com.motorola.setupwizard.controller (VzwController.apk) by one of those methods. If you ever wipe data, this will prevent it from getting stuck after the welcome screen if you tap start instead of doing the 4-corner bypass. (VzwController gets stuck waiting forever for the disabled VzwPhoneService) A side effect of disabling the additional app is that you no longer need to do the 4-corner bypass on first boot after wiping data when the phone isn't activated.
Click to expand...
Click to collapse
THIS! This so much! I had given up on flashing custom rom's after successfully switching my XT912 to page plus (3g/MMS working) and from there had just given up on custom roms after such a large headache. That was a year ago when the phone was coming from ICS to Jellybean (that was a rookies worst nightmare when google is your only quick resource: wrong versions, wrong tools, old information and didn't know a damn bit better. Ugh) anyways, I recently came back to try it out but found out yet again I was trying to use old information when getting through the activation process. This solved it though. I used Titanium Backup (trial version) to delete the system app/process and activation screen popped up on first try! If anyone else has the same issue that I had, where US Cellular answered my activation call, don't fret. I imagine it has to do with the SID (CDMA Network ID) but then I had let the phone sit for a minute and noticed at the bottom "a special number needs to be called to activate this phone" hit that button then the Verizon activation system answers and its good to go from there.
I'll now install safestrap and hopefully get a version of CM11 to run properly which caused this whole re-flashing process. I had a "working" stock rom that would constantly try to activate on phone startup, but 3g would work after skipping all those annoying screens, however when booting to CM11 it was not working with 3g.
Thank you again for that information, I can confirm com.motorola.setupwizard.phoneservice is the culprit to OTA activation problems when switching to PagePlus network.

Strange issue after lates OTA update 7.4.1 and root - settings menu disappeared

Hi all,
I have a very strange issue after the latest official OTA update to version 7.4.1.
I recognized that my KFHD updated the firmware and after this, I had no root anymore. I used Root_with_Restore_by_Bin4ry_v30 and my KFHD was rooted again (confirmed with root checker). Now I see that I am no longer able to user the settings menu at the top, for wireless network connection, brightness, etc., because it is no longer available. From time to time it appears for a very short period, but disappeared at the same time and I have no chance to drop down this menu.
Anyone here with the same problem or who can help me?
Cheers,
Ingo

Guys, no one, who can help me?

arnakin said:
Guys, no one, who can help me?
Click to expand...
Click to collapse
If you have a recovery installed, I would say just grab the rooted 7.4.1 from the development section and flash that after full wiping. That should solve your issues.

arnakin said:
Hi all,
I have a very strange issue after the latest official OTA update to version 7.4.1.
I recognized that my KFHD updated the firmware and after this, I had no root anymore. I used Root_with_Restore_by_Bin4ry_v30 and my KFHD was rooted again (confirmed with root checker). Now I see that I am no longer able to user the settings menu at the top, for wireless network connection, brightness, etc., because it is no longer available. From time to time it appears for a very short period, but disappeared at the same time and I have no chance to drop down this menu.
Anyone here with the same problem or who can help me?
Cheers,
Ingo
Click to expand...
Click to collapse
When (if) Kinology gets updated (for 7.4.1 support), flash that and your problem will be solved. Unless you don't care about what software version you are on. In that case just flash it now.

A similar problem
-a- said:
When (if) Kinology gets updated (for 7.4.1 support), flash that and your problem will be solved. Unless you don't care about what software version you are on. In that case just flash it now.
Click to expand...
Click to collapse
The OTA updated to 7.4.1 and i tried flashing a custom ROM by Hashcode but, recovery isn't working and with a force recovery in FireFire Flash. It shows a yellow triangle with an explanation point. Also, my audio has stopped working but, i may have found a solution.
To keep in mind: Already Rooted with B4NARY's root, and Google Play Installed.
All Help is appreciated!

CVanB said:
The OTA updated to 7.4.1 and i tried flashing a custom ROM by Hashcode but, recovery isn't working and with a force recovery in FireFire Flash. It shows a yellow triangle with an explanation point. Also, my audio has stopped working but, i may have found a solution.
To keep in mind: Already Rooted with B4NARY's root, and Google Play Installed.
All Help is appreciated!
Click to expand...
Click to collapse
Personally the only tool I've ever used because I got myself in so deep at one point I had no options was the Kindle SRTool, the others seem to create problems, not because the tools were written bad or anything, but because amazon seems to like pushing out updates that don't really update much, but change things just enough to mess with the functionality of the tools. If you can get back to fast boot, you should just use the SRTool and start fresh. Then go to prokkenexxusa's rooting thread and use the manual root method not the automatic.

Solved
DroidIt! said:
Personally the only tool I've ever used because I got myself in so deep at one point I had no options was the Kindle SRTool, the others seem to create problems, not because the tools were written bad or anything, but because amazon seems to like pushing out updates that don't really update much, but change things just enough to mess with the functionality of the tools. If you can get back to fast boot, you should just use the SRTool and start fresh. Then go to prokkenexxusa's rooting thread and use the manual root method not the automatic.
Click to expand...
Click to collapse
I didn't click flash script when I rebooted into recovery from fire flash. In fire flash you have a couple options, two mandatory, using a older bootloader as the 2nd. flash a boot partition image, apply stack override, flash a recovery partition image, disable auto recovery auto update, then wipe cache wipe data wipe system install zip files, flash and install script. Lastly reboot and reboot into recovery. :victory:

So did you get your issues sorted OK, or are you still having problems?

Nexus 7 wifi constant reconnect after 4.3 upgrade

Hi,
I had a rooted first gen Nexus 7 running under stock 4.2. It was pretty good. I rooted it and had TWRP.
I upgraded to 4.3 OTA, and then rerooted using the wugfresh toolkit. Now my wifi keeps reconnecting every few seconds to every minute. I seem to be the only one reporting this issue. I'm kind of a Android newbie. Would my best chance of fixing this issue be to go back to stock 4.2? How do I downgrade? I still have TWRP, but I'm not sure if that helps.
I'm kind of an Android newbie - I only follow the guides out there, don't really know what I'm doing.

What version of the toolkit did you use to reroot? The old version's root is not meant for 4.3.

Username invalid said:
What version of the toolkit did you use to reroot? The old version's root is not meant for 4.3.
Click to expand...
Click to collapse
Try using the latest version of the toolkit, if that doesn't work and you absolutely need root then add it to your rom yourself by flashing the latest SuperSU from Chainfire, i'm sure you can find the latest version with a bit of digging.

Try DroidWall to stop things connecting that you don't want to connect. I've used it for a long time on my GS2/N7 and it's been great. Also there is an option WiFi - settings- Advanced- Scanning always available, is this turned off/un checked?

easy life said:
Try DroidWall to stop things connecting that you don't want to connect. I've used it for a long time on my GS2/N7 and it's been great. Also there is an option WiFi - settings- Advanced- Scanning always available, is this turned off/un checked?
Click to expand...
Click to collapse
Not relevant to the OP. The problem is the system Wi-Fi, not individual apps. The scanning always available setting doesn't cause reconnections either, since it just leaves the antenna live to passively grab SSID data when the device is sleeping.
OP, Wi-Fi's been a bit flaky on this device with 4.3 in particular, but a clean flash has resolved most of the trouble for me.

Wipe Clean and ReROM and ReRoot
Ive been running 4.3 OTA and rooted with chainfires .zip in TWRP
I would suggest since you have root to back up with Titanium Backup. Backup your apps and data then use Wug's toolkit to flash back to stock clean. Then root with the new version of the toolkit and all should be well! Then restore your apps and data with TiBu again!
Good Luck!

freddy0872 said:
Ive been running 4.3 OTA and rooted with chainfires .zip in TWRP
I would suggest since you have root to back up with Titanium Backup. Backup your apps and data then use Wug's toolkit to flash back to stock clean. Then root with the new version of the toolkit and all should be well! Then restore your apps and data with TiBu again!
Good Luck!
Click to expand...
Click to collapse
EDIT!!! My Nexus was in MTP mode instead of the camera mode. That's why I couldn't ADB.
I don't really need to backup any apps on it. No apps I want to back up. But, I just tried the latest 1.6.8 of Wug's toolkit, and I couldn't get the ADB working! Weirdest thing. I had it working just the other day!
So...now I'm stuck. I can see the button on Wug's toolkit that let's me flash the factory 4.2.2 rom, but since ADB isn't working, I can't do anything. I've got USB debug mode checked. I've tried going through the driver install process a few times now. I don't know what's going on. Using the original USB cable. When I plug the tablet in, I see the ADB mode message on the windows task bar.
Ugh.

The lastest OTA won't install - sends my phone into a recovery loop

Hi all, I was running a CM ROM on my Droid Turbo and recently flashed back to stock using a backup I created with TWRP, because I was tired of not having GPS capabilities.
Now that I’m running stock (still rooted), I’ve been getting a notification to do an OTA update. When I allow the update to install, it restarts my phone and sends me straight to the TWRP recovery and does nothing else. Rebooting gets me stuck in a loop where it keeps sending me to recovery. Clearing out my cache got me out of the loop but after a day or so, the annoying install message comes back.
I noticed an error message when I looked at the log screen in TWRP. As best I can transcribe it, it says:
Package expects build fingerprint of motorola/quark_verizon/quark:5.1/SU4TL-44/44:user/release-keys or Motorola/quark…. ; this device has Motorola/omni_quark/quark:5.1.1/LYZ28E/1:eng/test-keys
Does anyone have any idea what’s going on with my phone – why I can’t take the OTA? Any advice on how to fix the problem or get this stupid upgrade notification to go away? The notification takes over the device every time you unlock the screen so it’s driving me crazy.
Thanks in advance for any help!

I think you need stock recovery and bootloader.

GPS issues have long been solved, using the "clear modem" file. You sent back to stock for nothing.
If you really want SUTL-49 there's plenty of downloads to manually flash it. You don't need the OTA.

Thanks for the replies. I think I'm going to stick with stock now. Have been enjoying the Motorola features like the hands-free driving thing and I wasn't seeing any advantage running CM anymore. Can I flash SUTL-49 using TWRP or do I have to hook to a PC and use ADB?

shinydiamond said:
Thanks for the replies. I think I'm going to stick with stock now. Have been enjoying the Motorola features like the hands-free driving thing and I wasn't seeing any advantage running CM anymore. Can I flash SUTL-49 using TWRP or do I have to hook to a PC and use ADB?
Click to expand...
Click to collapse
You can flash it with TWRP from here:
http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041

Thank you!