Hello – does the 5.02 OTA notification pop up right away now for all 2013 Nexus 7s that haven’t yet been updated to Lollipop?
I want to factory reset my wife’s 4.4.4 Nexus 7 before upgrading to 5.02. It currently has the notification to upgrade, but I’ve ignored it (actually I disabled notifications for Google Play Services to avoid the nag for the past several weeks).
I want to avoid doing the factory reset and then not being offered the OTA notification for a day, week, or longer.
Will doing a factory reset right after updating to 5.0.2 make the device just as pristine as doing it just before? Maybe I should avoid worrying about when I’ll get the offer to go to 5.0.2 and do it now while I have it, and then factory reset – if the end results will be the same.
I want to ensure the tablet will work the best it can with 5.0.2. We had some really bad experiences with the original Nexus 7 2012 and I want to avoid having the update from 4.4.4 make things worse. We have a couple Nexus 5s that are working good enough with 5.0.1.
Thanks in advance.
GaryP2 said:
Hello – does the 5.02 OTA notification pop up right away now for all 2013 Nexus 7s that haven’t yet been updated to Lollipop?
I want to factory reset my wife’s 4.4.4 Nexus 7 before upgrading to 5.02. It currently has the notification to upgrade, but I’ve ignored it (actually I disabled notifications for Google Play Services to avoid the nag for the past several weeks).
I want to avoid doing the factory reset and then not being offered the OTA notification for a day, week, or longer.
Will doing a factory reset right after updating to 5.0.2 make the device just as pristine as doing it just before? Maybe I should avoid worrying about when I’ll get the offer to go to 5.0.2 and do it now while I have it, and then factory reset – if the end results will be the same.
I want to ensure the tablet will work the best it can with 5.0.2. We had some really bad experiences with the original Nexus 7 2012 and I want to avoid having the update from 4.4.4 make things worse. We have a couple Nexus 5s that are working good enough with 5.0.1.
Thanks in advance.
Click to expand...
Click to collapse
If you're gonna do a factory reset, you might as well just flash the factory image. That will guarantee that you'll have the possible install.
_MetalHead_ said:
If you're gonna do a factory reset, you might as well just flash the factory image. That will guarantee that you'll have the possible install.
Click to expand...
Click to collapse
Thanks for the advice - that's what I ended up doing this morning and it went well!
Although I had adb working on a Windows box for some time, I hadn't taken the opportunity to flash a factory image until now.
Just bought a N7 2013 and I'm afraid it bricks after update and wanted to know if I could avoid it by flashing Marshmallow factory image instead of updating via OTA, skipping lollipop, or if there is any precaution to not brick it...
carpamagica said:
Just bought a N7 2013 and I'm afraid it bricks after update and wanted to know if I could avoid it by flashing Marshmallow factory image instead of updating via OTA, skipping lollipop, or if there is any precaution to not brick it...
Click to expand...
Click to collapse
why would it brick via OTA? almost all N7s are updated that way.
the best precaution for not bricking it is if you follow the instructions that are given for manually flashing factory image, although I don't think it is necessary to do it manually. I did it OTA and it works perfectly normal.
Hard Brick
FWIW,
I've used Ubuntu with the adb utility and if I "bricked" my N7 2013, I found when I got to the bootloader "START"
window, I could simply do the sudo ./Install-all.sh command that comes in the package for the "stock" Android
kernel without any prerequisite commands and the ROM would load.
Of course anything that was on there previously was wiped out but at least I had a new system to start from.
I discovered this when I had my "bricked" device at the START window and the "adb devices" command showed that the N7 2013 was recognized at the USB port. Just went ahead and did the Install-all.sh command and away it went.
I tried to get Android 6 installed, rooted and with MultiROM operating but no dice. When I got to the point of installing MultiROM on Marshmallow, the device would perpetually boot into TWRP, never booting Marshmallow. I ditched it and went back to KitKat 4.4.4 and got it settled and then loaded a Cyanogenmod
snapshot. I'm liking CM more and more.
I'm just a script kiddie that's dinked with Linux since '93 and am by no means an expert. The background has helped when slogging away with my N7 2103 Flo. Kurt
reso91 said:
why would it brick via OTA? almost all N7s are updated that way.
Click to expand...
Click to collapse
Huh... back when Lollipop was released I heard a lot of N7s hard bricked because of the update(5.0.2), causing a motherboard problem, idk, but no one could flash anything, and I thought I could avoid this problem with lollipop skipping it (ex: N7 come with JB and I flash Marshmallow factory image instead of going through KK,LP till MM)
carpamagica said:
Huh... back when Lollipop was released I heard a lot of N7s hard bricked because of the update(5.0.2), causing a motherboard problem, idk, but no one could flash anything, and I thought I could avoid this problem with lollipop skipping it (ex: N7 come with JB and I flash Marshmallow factory image instead of going through KK,LP till MM)
Click to expand...
Click to collapse
Sigh. The issue was widely reported as being caused or exacerbated by the OTA update to the initial release of lollipop. The best way to avoid the issue, if there ever truly was one, is to simply use custom ROMs, or stock rooted ROMs, which can be installed via custom recovery as opposed to through installing the factory image...
One of the nice things about Nexus devices is that Google posts factory images on their site. I generally prefer to use those, rather than OTA updates, as it guarantees a fresh install. I use a variety of other methods to backup/restore data and apps, but I've had pretty good luck doing it that way.
There's a really simple way to not hard brick your N7 with an OTA update:
If your present Android version is working okay, is stable, and does what you want it to do...wait for it...LEAVE IT ALONE!
Seriously. Other than for additional stability and MAYBE security enhancements, stick with what you have. Don't fall for all the hype out there.
The bricking caused by lollipop was due to a bug in the update causing a excessive amount of read/writes to the NAND and caused premature failure of the chip, this has long since been fixed and lollipop is safe for use again.
Sent from my Nexus 7 2013 using Tapatalk
I have recently traded in my old Nexus 7 2012 for a 2013 model and since day one its been rebooting (a lot) also struggling to boot up (most of the time), It is running android 6.0.1 and after rooting TWRP recovery is not sticking either it seems to revert to stock recovery. After browsing the internet im not sure if its suffering hardware or software problems any help would be much appreciated thanks.
Twrp issue is discussed a lot recently in several threads. Late manufactured N7-13's, the ones preloaded with LP and not JB, have other Emmc chip. Regular Twrp not compatible. But a multirom Twrp is.
Concerning the reboot and boot issue. If already done a factor reset I don't know. Normally Ota's to new version leave a mess with bugs and decreased battery life. I always factory reset before and after big updates. (And easy restore everything with Tiranium). Sometimes via recovery only wiping cache partition is sufficient. Try that first.
Thanks I got TWRP to stick using Flashify and have tried resetting and reflashing but am still suffering from reboots/not booting up im beginning to think its a hardware issue from what ive read online.
Could installing lollipop help maybe then updating to Marshmallow?
After a bit of poking around inside and applying some insulating tape on the ribbon connectors I now have a usable device. Reboots once or twice a day and suffering with issues when typing (getting ip instead of o in portrait mode) so still not 100%. Am now waiting for a replacement tab. Just out of curiosity does anyone know how to find the date of manufacture without the box?
Got a replacement yesterday and what a difference. 100% better than the last one so it was definitely a hardware issue, and I got a refund for the waiting so basically its been a straight swap - my 16gb 2012 for this 32gb 2013 ?
Hi,
I've taken all of the OTA updates up until June 2017. I have 6.0.1, May 1st 2017 Security Path Level and Baseband Version of N910VVRS2CQE1, Build Number of MMB29M.N910VVRS2CQE1.
Can I root and use a version of CM or go back to Kit Kat 4.4.4?
I'm hoping that I can still get some play out of the phone, it's incredibly slow. I've done a factory restore once or twice as well.
Thanks!
Have you tried looking through the various posts within the forum to find your answer? I just scrolled through and found a few without searching. Exerting a bit of effort could yield amazing results, at least that's what I've had happen over my years on here
bumperjeep said:
Hi,
I've taken all of the OTA updates up until June 2017. I have 6.0.1, May 1st 2017 Security Path Level and Baseband Version of N910VVRS2CQE1, Build Number of MMB29M.N910VVRS2CQE1.
Can I root and use a version of CM or go back to Kit Kat 4.4.4?
I'm hoping that I can still get some play out of the phone, it's incredibly slow. I've done a factory restore once or twice as well.
Thanks!
Click to expand...
Click to collapse
My Verizon Note 4 is exactly at the same update level as yours and it is working great.
When you did the factory reset did you completely wipe all user data on both the phone and the SD card? If not I would give that a try.
I would also suggest that you not let Android restore any applications when you first start the phone after the factory reset. You could have an errant app causing problems. If it seems to work phone without any user installed apps I would then reinstall apps one by one and make sure the phone continues to work fine. It it starts to run incredibly slow again then the last app you installed is likely the culprit.
If these options don't work I would take the phone to a local Best Buy. Go to the Samsung Experience counter and talk to them. They can do a deep factory reset that will completely reinstall the firmware and thereby restore the phone to a pristine factory image.
If these options do not fix the problem you may be in the early stages of hardware failure. The Note 4 has developed a bad reputation for the motherboard slowly failing and causing progressively worse problems. That is what happened to me and the phone eventually became unusable. I finally had to contact Samsung technical support (1-800-SAMSUNG) and they had me send the phone in. They replaced the motherboard and other printed circuit boards. It did cost me $70 since the phone was out of warranty, but it works like new now.
Good luck. The Note 4 is still a great phone and worth the effort (and possibly cost) to get it fixed.
Can anyone confirm that Foxfi tethering works (not usb) on a non rooted Verizon Note 4 phone (marshmallows 6.0.1) with the following security update installed (mmb29m.n910vvrs2cqe1)
bumperjeep said:
Hi,
I've taken all of the OTA updates up until June 2017. I have 6.0.1, May 1st 2017 Security Path Level and Baseband Version of N910VVRS2CQE1, Build Number of MMB29M.N910VVRS2CQE1.
Can I root and use a version of CM or go back to Kit Kat 4.4.4?
I'm hoping that I can still get some play out of the phone, it's incredibly slow. I've done a factory restore once or twice as well.
Thanks!
Click to expand...
Click to collapse
Yeah im thinking the problem is this phone came just packed with bloatware nobody uses a third of the garbage that came preloaded (200+ apps you use 10 of). You can root but you have to downgrade with odin back 5.1.1. bpa1 . you could also try a less invasive approach and just disable the bejeezus out of pretty much anything allowable there is an easy disable option that lets you do it in batches from the apps drawer. I did this to root the phone given the unstable root method.
I just started receiving the error "Bluetooth keeps stopping" on my Pixel 3 XL a week ago. It comes and goes seemingly completely at random, sometimes clicking close app will work and other times it will just keep coming back over and over until I restart my phone. It's a huge problem because it takes my wifi and sometimes I think even my mobile data down with it. I've read a bunch of posts and it seems like many people have been having this issue.
I've tried turning off Wi-fi and Bluetooth scanning.
updating Google Play system update.
Clearing cache and storage of Bluetooth.
resetting every bluetooth device I own
Factory Reset
sideloading an OTA image
Flashing a factory image
I'm all out of ideas. The only thing I can come up with is it's a hardware issue, but generally hardware issues I run into are not so sporadic and random. Usually it's either broke, or not broke. It doesn't seem to correlate to how hot the phone gets. I feel like Google broke something with an Android update. I've tried to warranty it through Google but I purchased it new on Ebay and they want the original purchasers name, email and order number. Anyone know of a way around that for Google's warranty?
As a last ditch effort I just flashed the Sep 18th Android 9 factory image, crossing my fingers that for some reason that does something.
My only other idea is google has driver binaries posted for pixel devices. Do these binaries get written over/rolled back when the factory image is flashed? Or are they isolated and not touched when flashing a factory image? Could flashing new driver binaries fix the problem? If so, does anyone have a guide on how to flash the driver binaries, google gives documentation for sideloading the OTA or flashing factory images, but nothing for how to install the driver binaries.
iwestfall7062 said:
I just started receiving the error "Bluetooth keeps stopping" on my Pixel 3 XL a week ago. It comes and goes seemingly completely at random, sometimes clicking close app will work and other times it will just keep coming back over and over until I restart my phone. It's a huge problem because it takes my wifi and sometimes I think even my mobile data down with it. I've read a bunch of posts and it seems like many people have been having this issue.
I've tried turning off Wi-fi and Bluetooth scanning.
updating Google Play system update.
Clearing cache and storage of Bluetooth.
resetting every bluetooth device I own
Factory Reset
sideloading an OTA image
Flashing a factory image
I'm all out of ideas. The only thing I can come up with is it's a hardware issue, but generally hardware issues I run into are not so sporadic and random. Usually it's either broke, or not broke. It doesn't seem to correlate to how hot the phone gets. I feel like Google broke something with an Android update. I've tried to warranty it through Google but I purchased it new on Ebay and they want the original purchasers name, email and order number. Anyone know of a way around that for Google's warranty?
As a last ditch effort I just flashed the Sep 18th Android 9 factory image, crossing my fingers that for some reason that does something.
My only other idea is google has driver binaries posted for pixel devices. Do these binaries get written over/rolled back when the factory image is flashed? Or are they isolated and not touched when flashing a factory image? Could flashing new driver binaries fix the problem? If so, does anyone have a guide on how to flash the driver binaries, google gives documentation for sideloading the OTA or flashing factory images, but nothing for how to install the driver binaries.
Click to expand...
Click to collapse
Try flashing the dec/Jan build then lock bootloader then start phone as normal setup then unlock bootloader. There's also some Bluetooth settings in the developer ootions. Also check battery settings for the app maybe try turning off optizmation for it. There's also a setting somewhere that will let you turn off the ble236a scan it's always on mine new pair list. But the drivers are usually flash with the update or ota. I needed to flash those when flashing Dirty Unicorns. Fastboot flash vendor_a vendor.img and same for vendor_b believe the other is the radio img you would need to extract them with 7zip if using Windows.
Mine did this as well but I was using naptime,and servicly to kill and or deep sleep quicker. Which is what made me think of the battery optizmation
billyt1 said:
Try flashing the dec/Jan build then lock bootloader then start phone as normal setup then unlock bootloader. There's also some Bluetooth settings in the developer ootions. Also check battery settings for the app maybe try turning off optizmation for it. There's also a setting somewhere that will let you turn off the ble236a scan it's always on mine new pair list. But the drivers are usually flash with the update or ota. I needed to flash those when flashing Dirty Unicorns. Fastboot flash vendor_a vendor.img and same for vendor_b believe the other is the radio img you would need to extract them with 7zip if using Windows.
Mine did this as well but I was using naptime,and servicly to kill and or deep sleep quicker. Which is what made me think of the battery optizmation
Click to expand...
Click to collapse
Just a precaution, as soon as you start locking and unlocking bootloader you're going to be doing a complete wipe of your device. So backup before hand. You'll also want to do a complete install of the factory image, with the wipe option, before you attempt to lock the bootloader. If you lock the bootloader and you are not 100% stock of something goes wrong you could end up with an expensive paper weight.
billyt1 said:
Try flashing the dec/Jan build then lock bootloader then start phone as normal setup then unlock bootloader. There's also some Bluetooth settings in the developer ootions. Also check battery settings for the app maybe try turning off optizmation for it. There's also a setting somewhere that will let you turn off the ble236a scan it's always on mine new pair list. But the drivers are usually flash with the update or ota. I needed to flash those when flashing Dirty Unicorns. Fastboot flash vendor_a vendor.img and same for vendor_b believe the other is the radio img you would need to extract them with 7zip if using Windows.
Mine did this as well but I was using naptime,and servicly to kill and or deep sleep quicker. Which is what made me think of the battery optizmation
Click to expand...
Click to collapse
The error happened once immediately after a full factory image flash before I had downloaded a single program or changed a single setting, so I don't see how it could be bluetooth settings, battery optimization, wifi/bluetooth scanning, or a rogue app. Oddly enough, since posting this last night I've managed to go 12 hours without an errors after flashing the Sept 2018 factory image. buuuuuuuut now I'm afraid to upgrade to Android 10 again.
jd1639 said:
Just a precaution, as soon as you start locking and unlocking bootloader you're going to be doing a complete wipe of your device. So backup before hand. You'll also want to do a complete install of the factory image, with the wipe option, before you attempt to lock the bootloader. If you lock the bootloader and you are not 100% stock of something goes wrong you could end up with an expensive paper weight.
Click to expand...
Click to collapse
Thank you for making sure I understood this. Yeah, I generally factory reset my phone and laptop once a year so I always back everything up before a reset. And yeah, I haven't changed anything from stock on this phone since I've had it, so unlocking and locking the bootloader should never cause any issues. As I told Billy, the Sept 2018 image seems to have fixed the problem, fingers crossed.
Is it probable that upgrading once again to Android 10 will cause the issue to return? The Sept 2018 image must have changed an internal setting or driver that wasn't functioning properly.
iwestfall7062 said:
Is it probable that upgrading once again to Android 10 will cause the issue to return? The Sept 2018 image must have changed an internal setting or driver that wasn't functioning properly.
Click to expand...
Click to collapse
I can't tell you for sure, but i would think the latest firmware should work. There have been a number of Bluetooth fixes since the original firmware, which it appears you're on now. That, and lots of security fixes.
jd1639 said:
I can't tell you for sure, but i would think the latest firmware should work. There have been a number of Bluetooth fixes since the original firmware, which it appears you're on now. That, and lots of security fixes.
Click to expand...
Click to collapse
Yeah, I mean I would much prefer being on Android 10 and having the latest updates, I normally update as soon as they come out. But, given that I flashed the Jan 2020 image and bluetooth was still broken, and then flashed the Sep 2018 which seems to have fixed it, I'm hesitant to go back to the Jan 2020 updates. Kind of tending towards the if it isn't broken, don't fix it philosophy right now. If I had time to monkey around with my phone all the time I wouldn't mind, but the semester just started and I use my phone for everything at school so I don't really have time for it to be not working. >.< Such an odd issue and odd fix.
Looks hardware related, like the cable is loose.
wangdaning said:
Looks hardware related, like the cable is loose.
Click to expand...
Click to collapse
And it's continuing to happen even with the Sept 2018 factory image flash.
Why do you think it's hardware related and that a cable is loose when a reboot fixes it? If the cable is loose a reboot shouldn't fix it.
iwestfall7062 said:
And it's continuing to happen even with the Sept 2018 factory image flash.
Why do you think it's hardware related and that a cable is loose when a reboot fixes it? If the cable is loose a reboot shouldn't fix it.
Click to expand...
Click to collapse
What do you have Bluetooth connected to when it happens?
jd1639 said:
What do you have Bluetooth connected to when it happens?
Click to expand...
Click to collapse
Nothing. It doesn't matter whether anything is connected or not. It literally happened on first boot up of a fresh flashed Jan 2020 factory image, before I had put a single thing on the phone.
Generally I have my Fitbit Versa connected, I got 2 tiles awhile ago, but first troubleshooting thing I did was remove the app and delete those from bluetooth since those were my latest additions to bluetooth. I have backbeat fit headphones I use sometimes, the same with bose soundlink ii headphones, ps4 controllers, a jbl pulse 3, my car radio. But I factory restored all of those items so they weren't trying to connect to my phone, and then flashed the factory image. So I don't see how it has anything to do with an actual bluetooth connection.
Im having this same exact issue. Android 9 was always super smooth. It all started with the Android 10 update. I was having all kinds of Radio related (wifi/bluetooth/data) issues ever since. I noticed sometime in Nov/Dec that google released some kind of radio system app update and things got a little better. But I still have the Bluetooth problem (like today, which prompted me to find this thread) or every once in a while ill lose all data connectivity and have to reboot my phone for everything to come back. I LOVE the dark theme, but this has to be the worst Android update from a stability standpoint ive ever experienced.
Just want you to know it isnt just you. Its something to do with some phones on Android 10
JJT211 said:
Im having this same exact issue. Android 9 was always super smooth. It all started with the Android 10 update. I was having all kinds of Radio related (wifi/bluetooth/data) issues ever since. I noticed sometime in Nov/Dec that google released some kind of radio system app update and things got a little better. But I still have the Bluetooth problem (like today, which prompted me to find this thread) or every once in a while ill lose all data connectivity and have to reboot my phone for everything to come back. I LOVE the dark theme, but this has to be the worst Android update from a stability standpoint ive ever experienced.
Just want you to know it isnt just you. Its something to do with some phones on Android 10
Click to expand...
Click to collapse
Yeah, I wish this thread held a solution for you. I've searched and searched and tried every solution I've found on google and nothing has worked, and really none of the threads I have found have ever had a concrete solution either, just one or two people going "well I did THIS and it worked", and a bunch of people saying it didn't work for them. I just cannot fathom how a full factory flash back to the very first image would not revert the changes that came with Android 10. That's why I was questioning whether or not a factory flash replaces driver binaries. It's the only way I could see the factory flash to Sept 2018 not fixing our issue. (Other than it really being a hardware issue, but that doesn't seem possible to me.)
Oh wow, you're still having same issues on Android 9??
Im still on Android 10, most recent update. I did do a full factory flash a few weeks ago and it was quite the improvement. But I still do have the Bluetooth/radio issue every once in a while, like yesterday.
I wonder if it's a hardware issue and/or substandard hardware performance that Android 10 made more prevalent? That's something we'll probably never know
I only pointed to hardware as I had a similar issue years ago. The radio connections were slightly loose so it would come and go. I do hope you are able to figure out what is wrong, was not trying to be rude.
wangdaning said:
I only pointed to hardware as I had a similar issue years ago. The radio connections were slightly loose so it would come and go. I do hope you are able to figure out what is wrong, was not trying to be rude.
Click to expand...
Click to collapse
Oh no, I didn't think for a second you were being rude. And I appreciate your idea, just with what I'm experiencing with my specific phone it doesn't seem to be a hardware issue.
Strangely enough, the issue has been tapering off as of late, after the factory resets I just continued to use my phone while I wait to figure out if I can get a refund or a warranty replacement, etc. The issue has been occurring with much less frequency since then. Still happens, but not like it was.
Damn, the Bluetooth bug is back again. It was so bad the other day, my phone kept bootlooping for like 20 mins while I was on the road.
I finally just let phone sit for a while and it fixed itself. Man this is completely sporadic.
JJT211 said:
Damn, the Bluetooth bug is back again. It was so bad the other day, my phone kept bootlooping for like 20 mins while I was on the road.
I finally just let phone sit for a while and it fixed itself. Man this is completely sporadic.
Click to expand...
Click to collapse
Yeah, mines been better for like 4 days, and then it just crashed and rebooted by itself earlier today.
has anyone gotten to the bottom of this yet? it seems to be a result of the play store system update being "stuck" on Sept 1st...even if you get it to download to the current version, currently March 1st, after a reboot it will not show the March update has been applied. And should it actually show that the March update has been applies, within a day the phone will reboot and the bluetooth bug will return, strangely the update to the play store system reverts to Sept 1st.
I'm having this issue with my son's phone. I tried unlocking the bootloader and flashing the factory img from April but of course the bug is still there, and after signing in the Play Store system is of course dated Sept 1st
There is no fix. I made an official Android Issue Tracker thread.
https://issuetracker.google.com/issues/151033055
and a Google Pixel Phone Help thread.
https://support.google.com/pixelphone/thread/32828289?hl=en
Google's being ****ty about it. I eventually just bought a new Pixel 4 XL. I needed a functional phone for school and work, and as much as I hate to spend money on another Google product after this mess, they do make the most powerful pure android phones with the best camera. Ebay FTW, $600, never giving them another penny directly.
If you still have warranty, get it warrantied immediately, and don't take no for an answer. I dawdled around thinking it would get fixed and even though I reported that I was having issues with it directly to Google's phone support BEFORE the warranty expired, by the time I called a second time and pushed a manager to see if they could warranty it, my warranty had expired so they told me to go jump in a lake.
to make it worse, Google told me the phone still has an extended warranty but I'm not the original owner and have no way to contact that individual. But you need that person's email address for it to work. So it was purchased but because of this technicality it's null and void. I get the security of it but it's still garbage