Some Nexus 7 have problems with Android 5.0.2 Lollipop

Nexus 7 Lollipop

It seems that there are some users who have reported serious problems on their Nexus 7 from 2013. This serious problem is that some tablets with Android 5.0.2 are being bricked.

For many, the word brickear sounds like Chinese, but when we talk about a brick, we mean that the device, be it a smartphone, console or something else, goes from being a product in which you performed thousands of actions to becoming a brick or whatever. it has been a device incapable of doing anything, a dead device.

Well, that word is being said by some users who own the smart tablet, the Nexus 7 and it is that, since the Android 5.0 Lollipop version was launched, various problems have arisen that Google has had to fix over time in its new versions and the Nexus 7 has not been spared these problems.

Some problems with Android 5.0.2 that we can find are those already known as poor battery management, the occasional lag between application transitions or problems with Wi-Fi connectivity. All the problems mentioned above are problems that are not very serious errors, but nevertheless there is one very serious one that directly affects the Nexus 7.

Some Google Nexus 7 from 2013 and 2012, which have Android 5.0.2 Lollipop installed, have been bricked. According to the sources that have reported these problems, the tablet turns on but from there it does not happen, having the Google logo until the tablet runs out of battery. So if there was a patch to fix what happens, it would have to be done manually since there would be no possibility of doing it through OTA. The worst of all this is that at the moment the cause of this problem is unknown, so those affected have created a hashtag on social networks to talk about it and find a possible solution officially.

In the hashtag in question, # nexus7bricked, users have stated that they have contacted ASUS but have encountered the problem that some tablets do not have a warranty as it has expired. So these users who own a Nexus 7, if the solution to their problems does not arrive officially, they will probably have to look for it unofficially, if there is something.

Hopefully both ASUS and the development team behind Android will quickly find a solution to this serious problem that many users with a Nexus 7 may have and thus avoid having more Nexus 7 unusable.


Follow us on Google News

Leave a Comment

Your email address will not be published. Required fields are marked with *

*

*

  1. Responsible for the data: Actualidad Blog
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.

  1.   primer123 said

    It's not just a matter of android 5.0.2, in my opinion it's a manufacturing flaw that literally scorches memories. Let's see if it sounds like, "I had the tablet turned on and when I went to pick it up, I only saw the google logo." Luckily or unfortunately it has happened to me 2 times. The first was that of my partner with version 4.4.4 after two months it happened to me with version 5.0. My mother has it too and it hasn't happened to her yet. It is also true that he does not make much effort and as soon as he plays with it, he uses it more as a work tool. Luckily ours were still under warranty.

    I do not have the logs to put you here but when trying to solve the problem with the NRT it said that the system and data memories were inaccessible, which without being understood I think it is because both are partitions of the same memory that is fried. Access to the bootloader would be accessible but could not be modified