yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Q&A] Norcalz71:
For those with a continuing issue, you can read back a few pages to see my problems as well. Seem to be right in line with what everyone else is experiencing.

I was outside of my 1-year warranty, but sent the tablet in anyways with a polite but firmly worded explanation (this was back in dec). I stated that I had already seen multiple instances of 5.0/5.0.1/5.0.2 bricking these devices via the OTA, that I was above average knowledgeable when it came to modifying and troubleshooting these devices but that this device was totally stock and not tweaked in any way. I also stated that I loved the tablet as well as my other ASUS products, but would be abandoning the company if this issue was not resolved as my tablet was in pristine condition and it just died out of nowhere which was unacceptable. I mentioned that I had also heard of others being charged $100-200 for repairs which was also unacceptable and to please notify me if they intended to make repairs as I would be declining if they were planning to charge for it. I never heard back from them, the RMA took awhile and the status was rarely updated - then boom. Tablet was shipped back to me, appeared physically good as new (save one tiny nick/chip around the bezel which I assume was from opening it, it was not from me) and the tablet fired up.

All in all the process took longer than I would have expected but ASUS did come through. Not sure if it was a fluke or the letter or what, but worth a shot for other people. A standard process such as an OTA that is recommended by the manufacturer/software provider should not be destroying units. If I had been significantly modifying this device I probably would have passed as I may have been at fault, but in this case I see nothing I could have done to prevent it. Give it a try maybe, I was just out the $15 to overnight it to Texas.
[Nexus 7 (2013) Q&A] flyinion:
I'm still holding out to see what Google/Asus come up with unless we get into July without a response. I realized the credit card I bought it with on launch day in July 2013 extends the warranty up to a year past the mfr's. So I should be able to use that for an RMA repair if needed. I may call them just to verify the timeframe of how long it's extended, but hopefully Google will make things right without having to go that route.
[Nexus 7 (2013) Q&A] jshamlet:
Is this strictly limited to people who upgrade to Lollipop via OTA, or to Lollipop in general. I upgraded by flashing a factory image of 5.0.2 via fastboot and haven't had any issues (yet).
[Nexus 7 (2013) Q&A] ejchis:
I updated by flashing the factory image, and it worked fine for a substantial time after the update before crapping out on me.
[Nexus 7 (2013) Q&A] klobkelosh:
Same here
[Nexus 7 (2013) Q&A] flyinion:
I also upgraded by flashing the factory image since I was rooted the OTA would not install.
[Nexus 7 (2013) Q&A] ShadowEO:
Flash does have a limited lifespan, it's also possible that devices which see heavy usage could have found their eMMCs die on them. It's true that they should last longer than 2 years, but it could still happen. The fact that this is happening after an update seems purely coincidence, especially since people are just now seeing this and there have been unofficial 5.x ROMs that have and still do work properly. I myself had been running on 5.0.2 with no indication of any issues and use it heavily when I do actually use the device, so it's possible that the update is pushing the NAND past it's limit in total writes.
[Nexus 7 (2013) Q&A] flyinion:
While I see your point, in my case at least, unless they used some very very poor quality NAND, mine was not caused by heavy use. My Galaxy Nexus from 2011 saw far more strenuous use during the 2 years I was on contract and then another year+ as a mini tablet/alarm clock in the bedroom and is still alive. My 1.75 year old N7 which saw very casual use is dead on the other hand of an apparent failure in being able to write to itself.

edit: I have read speculation though that something in 5.x is causing write loops and that is what is killing the flash memory. Something is bugged out and burning up all the writes in the memory.
[Nexus 7 (2013) Q&A] antmasi:
I do have a Nexus 7 2013 with Android 5.0.2 will it be safer to flash a custom rom? At least until Android 5.1 comes out?
[Nexus 7 (2013) Q&A] GFXi0N:
I have this very same question.

Does this affect ONLY stock system ? Are custom rom users safe?
[Nexus 7 (2013) Q&A] tetakpatak:
It seems so, regarding the reports.

tetakpatalked from Nexus 7 flo
[Nexus 7 (2013) Q&A] GFXi0N:
Ok, my wife has a 2013 LTE unit on stock. Going to flash cyanogenmod immediately.

I hope it's not too late
[Nexus 7 (2013) Q&A] antmasi:
Already done this! aparently only Android 5.0.2 units are beeing afected so i've only done this to my Nexus 7 (2013), the Nexus 5 is still running stock/rooted Android 5.1. The problem seems to be something that builds up with time! Yet is hard to determine exaclly what is causing the issue, but with so many reports after the OTA we must wonder.
[Nexus 7 (2013) Q&A] pokemaniac15:
I installed Lollipop 5.0.2 on the day when the image was available. Should I be worried that my N7 will be bricked too? Or it only affects the users who apply the update through OTA? Paranoia kicks in.
[Nexus 7 (2013) Q&A] kjdiehl:
You should be mildly worried. Yes, the bug affects ota and direct flash (adb or whatever) installs. There's no reason yet to think that this will happen to any but a hopefully small percentage of devices, though.
[Nexus 7 (2013) Q&A] jshamlet:
Well crap. I've been running my N7 with the 5.0.2 build since it came out, and mine was purchased new in Dec 2013.

I wish we knew what the root cause was, as I only actually use my tablet at night when I get home. It does stay on 24x7, though.
[Nexus 7 (2013) Q&A] flyinion:
Pretty sure it's 5.x and not normal use killing these. for about 8 months until mine died on Easter it was seeing very casual use, i.e. pick it up for a few minutes in the evening a few days a week mostly to look something up while watching TV. Before that it was more use but still pretty casual. Just in the evening a little bit of some gaming like Minion Rush or Asphalt 8 but that only lasted for about 3-4 months. I've had the tablet since launch in July 2013.
[Nexus 7 (2013) Q&A] jshamlet:
Ok, I punted and went back to KitKat until we know for sure what is causing the problem. Right now, between the memory leak and this issue, I'm beginning to not trust Lollipop. Hopefully this will be affirmatively addressed at some point, because my tablet is already out of warranty.
[Nexus 7 (2013) Q&A] jrglasson:
Mine was working fine with 5.0.2 which I flashed right after launch. Last night, mine bricked too. Can access the /cache filesystem to reset and can't unlock boot loader to flash new system image. Just hung at the Google boot screen. I really don't want the bigger Nexus 9. And without the GPE versions of LG and Samsung, I don't want those either.
[Nexus 7 (2013) Q&A] ejchis:
I'm having the same thoughts. The 2013 Nexus 7 is still the most appealing device to me. My ideal outcome here would be for Google or Asus to step up on this.
[Nexus 7 (2013) Q&A] GFXi0N:
Well, we can create a petition to complain about this in a more formal way... all we're doing now is cry a bit on the forums and on twitter.....
[Nexus 7 (2013) Q&A] jshamlet:
This.

I am increasingly convinced that Lollipop was released before it was fully cooked. Between the memory leaks, and now this, I think Google needs to ask for a mulligan.
[Nexus 7 (2013) Q&A] klobkelosh:
Anyone have any experience doing this? Know a good online petition site? Who should the petition be addressed to?
[Nexus 7 (2013) Q&A] sanogueralorenzo:
change.org?

I've been reading this and I had the same problem, in my case it was solved by installing the drivers on a new computer and repeating the process. I remember I had the same error msg, probably caused by screwed drivers on my pc.
[Nexus 7 (2013) Q&A] crazymonkey05:
So has anyone had any bricks since 5.1????
[Nexus 7 (2013) Q&A] klobkelosh:
I saw two mentions to bricks on 5.1 on the Google product forum
[Nexus 7 (2013) Q&A] 318sugarhill:
I was bricked for a time today. I'm a mac user and for some reason, terminal does not find my device unless it is up and running and I run the ./adb reboot bootloader command to put it in fastboot mode. If I just hold power + volume down buttons terminal sticks on "waiting on device".

So anyway, I flashed the new factory image of 5.1 and everything was going well. Device rebooted and then stuck on the 4 bouncing color balls.....for 45 minutes. I heard the first boot takes a long time, but that's rediculous. I tried rebooting....still stuck. I tried reflashing.....only to get the 'waiting on device' from terminal. I had read on other forums about the bricked Nexus' and thought, well, mine is not bootlooping so I'm good. Sure enough after the 5 time of rebooting trying to fix it I got stuck on the google screen. I read someone fixed theirs buy removing the back and disconnecting the motherboard. I have a crack in mine from using a cheap case (I dropped it getting out of the car months back) and it's very easy to get the back started where the crack is......so I did that. Couldn't figure out where the battery disconnects from the motherboard, and really didn't want to f around too much. I put the cover back on, (it was still stuck on Google screen at this time) and ran out of time to mess around. I put the back cover back on and when I did the whole thing went black. No power, nothing. I thought maybe the battery died so I plugged it in. No battery charge symbol, no light....nothin. I figured I touched something wrong and figured it was bricked. It didn't turn on, it didn't do anything. Later in the day I came back to it. Tried to power on, nothing. Tried plugging in, unplugging to get something.....nothing. Even used different cables. I held the power key down out of frustration for a good amount of time. Maybe 30 seconds to a minute. When I let go, the thing came back to life. Powered on, said google, booted up into the "Android is upgrading" So.....sweet. It's fixed. No clue how. No clue if taking the back off actually did anything, or if it's just placebo, but by device works and has 5.1 now. Just a tidbit of info.....it was completely wiped. I think it's supposed to be with a factory 5.1 install, but wasn't completely sure if that was the case or not. I have no need to back up the tablet as most things I use it for are cloud based anyway. The few things on there are on my computer anyway.

Long story short, I was bricked......not sure why or how, and no clue how it officially came back to life......but for a time today, I was super pissed.
[Nexus 7 (2013) Q&A] jaiunxda:
I don't understand your tip (how to disconnect the motherboard ?) but you are very lucky !

I make a post for the unlucky… like me

http://xdaforums.com/nexus-7-2013/nexus-7-2013-qa/list-dead-nexus-7-2013-stuck-logo-t3085127
[Nexus 7 (2013) Q&A] 318sugarhill:
I didn't figure out how to disconnect the battery from the board either.... That's just what another poster in another thread suggested they did. They didn't recommend it.... But I figured I had nothing to lose.
[Nexus 7 (2013) Q&A] CharlesUFC:
Same problem

My brother in law asked me to fix his n7 that bricked after he tried the 5.0 OTA. Its unrooted/locked has anyone come up with a solution yet?
[Nexus 7 (2013) Q&A] aristofeles:
Has the details ever been figured out?

1. This may still happen on 5.1. But at this point only rumors, right?

2. Are custom images less affected, or not affected at all?

3. Does this happens on 7 LTE?

4. How big is this problem?

5. ANY news from google or asus?
[Nexus 7 (2013) Q&A] SeZMehK:
I was having performance issues with my n7 so I decided to unlock it and install a custom rom. It was running stock 5.0.2. When unlocking it, it gets stuck at erasing userdata. It does not move from there. Is there anything I can do other than servicing it? :/
[Nexus 7 (2013) Q&A] klobkelosh:
From what I've read:

1. This may still happen on 5.1. But at this point only rumors, right? Correct, I've read at least two reports, but they are not very clearly the same problem.

2. Are custom images less affected, or not affected at all? It seems that custom roms are not affected. If they were, there would likely be a rash of complaints on Rom forums blaming developers.

3. Does this happens on 7 LTE? Yes.

4. How big is this problem? That remains to be seen. I've been trying to informally count the reports. My estimation is about 400 online complaints, but it's hard to know if people post to different forums and reddit under different user names, so this is only a guess of magnitude. That 400 is likely only a subset of the problem, since the device is getting old and many people might just assume it died, it's out of warranty, don't read minor tech blogs our forums, and throw it away since there's nothing they can do about it. I don't know how many nexus 7 were manufactured, but my guess is that this is a significant number.

5. ANY news from google or asus? No. I'm under the impression that Google is willing to work with owners that purchased from the Google play store, but asus is only offering to repair at $200us.

I should also point out that this happened to people on 4.4 as well, but seemingly in less numbers. The Google product forum shows an uptick in complaints around mid March, shortly after 5.0.2 ota reached many devices.
[Nexus 7 (2013) Q&A] tetakpatak:
Getting old? LOL :D the oldest razors are hardly 1,5 years old and most of people use hardly 6 months old devices.

I would say it is quite new.

tetakpatalked from Nexus 7 flo
[Nexus 7 (2013) Q&A] klobkelosh:
Yes, true, just saying that many of the people who bought the devices when they were first released may view the device as old since it is out of warranty
[Nexus 7 (2013) Q&A] GFXi0N:
At this point, the best advice I can give in order to avoid this problem is to unlock, root and install a custom rom like Cyanogenmod.

It's not difficult at all and it will save your $300 device and keep it running for another couple of years.

I'd do it before whatever is happening on the original system keeps damaging your unit.
[Nexus 7 (2013) Q&A] obaz:
I`m using Flo with cyagenmod 12 around tree month. no problems at all, but cyagenmod 12 update process is pain in the ass.

---------- Post added at 12:23 PM ---------- Previous post was at 12:22 PM ----------

BTW 5.1 rom are experiencing this issue to ?
[Nexus 7 (2013) Q&A] GFXi0N:
Flo and Deb user here: Both on 12.1 without problem. Didn't factory reset, but formatted system plus installed newest gapps
[Nexus 7 (2013) Q&A] dcrewchief:
The nexus toolkit should have all the tools needed. Just have to make sure the kit recognizes the device in fastboot mode.

---------- Post added at 11:59 AM ---------- Previous post was at 11:58 AM ----------

Try the nexus toolkit. It should have everything you need.
[Nexus 7 (2013) Q&A] mvanwey:
Nexus 7 Flo

I can't find the original thread, but Asus Social was watching the forums here, I e-mailed them direct & got an RMA. I sent mine to ASUS in Texas, tracking says they received it on 12/30.

I didn't get any movement on their service website until 1/14. As of right now it says "Product Repair is in Progress".

I'm holding off buying a new ASUS mobo for my main PC until they resolve this.

I'll post updates.
[Nexus 7 (2013) Q&A] mvanwey:
I'm Losing Faith in ASUS

Got the tablet back from ASUS via FedEx today. It has a new serial number decal on the rear. Only response from power button is white google logo. This is exactly what it was doing before I sent it in.

Pressing power+ vol- can get it into the fastboot screen, but restart bootloader/recovery/start all end up back at the white google logo. This thing is a paper weight

The packing slip says "New part No Desc ME571K MAIN_BD_2GQ806 4/16G". My serial number on the fastboot screen is different that the one I sent in. This leads me to believe they replaced the MOBO, but nothing works.

I sent an e-mail in to ASUS social to check up.
[Nexus 7 (2013) Q&A] jshamlet:
I love my Nexus 7, but dealing with Asus over my touchscreen was a complete fiasco. By the time they agreed that it had an issue, the warranty had expired, so I would have to pay for the repair. I felt that was dirty pool, since I had started my complaint while the warranty was active.

As much as I dislike iOS, Apple really takes care of Applecare users a hell of a lot better than any Android manufacturer. My wife had a similar touchscreen problem, took it to the genius bar, and walked out with a brand new tablet - no charge, no fuss. (other then the hideously long wait to move all of pictures and music to the new device)
[Nexus 7 (2013) Q&A] GFXi0N:
That's why you pay x3 for an apple product

For that difference of money, I'd rather throw the tablet away and buy a new one instead of calling apple care and I'd still save money....
[Nexus 7 (2013) Q&A] jshamlet:
That is true, but my point is that Android manufacturers don't even offer it as an option. Not a single one offers anything close to Applecare.

Of course, in my case it doesn't matter what the cost differential is. My wife and daughter strongly prefer iOS, so iPads/iPhones it is.
[Nexus 7 (2013) Q&A] mvanwey:
Update: Got the tablet back from ASUS today. Still DEAD. This is the 2nd round trip to ASUS & back for this exact problem. No matter what I press, the only thing happening is the white "Google" logo. Why would they send the tablet out the door if it won't boot?

The only good news is they have been covering the shipping. I'm asking for a 3rd RMA.

And the new MOBO i was looking for? Didn't buy an ASUS.
[Nexus 7 (2013) Q&A] gsxrman1100:
Lollipop sucks ,a disastrous rom wrecked my lenovo and nexus 7
[XDA Assist] :
Hello! Can you tell me please how do I get this page:

Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, Active, Ray, Live with Walkman

starting from http://xdaforums.com/
[XDA Assist] Razvan:
Hi there,

Here we go :

> Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, Active, Ray, Live with Walkman

But you register an account for ask/post/download anything.

Good luck
[XDA Assist] Eures:
I was afraid that I could get the direct link...-)

I mean, how do you navigate to that page starting from the home... (in which menu is the page located...)
[XDA Assist] Razvan:
Sir,

Press Forum -> All -> scroll until you will find the forum you search ...

Good luck
[XDA Assist] Eures:
But there is no order!....-) Ok, thanx.
[Android Apps and Games] azodus:
Hi everyone, we created a new game. This game focuses on the practice of short-term memory, attention and concentration. Try it by yourself and tell us what you think.

After starting the game, choose whether to play with a single-digit or double digit numbers. Initially, we recommend a single-digit numbers. Then you will see for a short period bubbles with numbers and after they disappear, you'll have to click them in the ascending order. Each game contains 10 rounds, after them the evaluation is done. From the statistics you can see how your memory and attention develops gradually.

We'll be thankful for reporting any problems and bugs and for ideas how to improve the game.

https://play.google.com/store/apps/details?id=com.azodus.brainmemex&hl=en

Thanks, have fun!
[Android Apps and Games] azodus:
Hello, add screenshot :)
[Android Apps and Games] azodus:
We fixed some bugs... Please try and give us a feedback, thanks a lot! Have a nice day
[Android Apps and Games] metalcracker:
Nice relaxing game. I like it. I just wanna say, that you can add some features to this game. It would be more interesting ;)
[Android Apps and Games] azodus:
Hi, thank for your response. We are planning to add some features. We are considering several options and the best will be added. Have a nice day.
[LG G Watch R] ox_eye:
Hello all,

is there any way or option to disable the step counter? I dont need it and I think its not good for the battery life if is allways working in the backround.
[LG G Watch R] joshmingus05:
stop step counter

i know you can turn the notification card off by going into your fit app and sliding left til you get to the settings screen and theres an option to turn step card off.
[LG G Watch R] mitchellvii:
Perhaps changing your daily step goal to "None" would disable it?

---------- Post added at 09:27 PM ---------- Previous post was at 09:25 PM ----------

You know, it always amuses me how people want to track their daily steps and heart rate. Silliness.

Wanna know if you are in shape? Get out of the shower and look in the mirror.
[Droid RAZR M Q&A, Help & Troubleshooting] Dr. Mario:
Like the title above; I was wondering how come I get the 64GB SD card I formatted with Linux EXT2 to even appear in the stock camera app and some specific apps in Jelly Beans ROM just fine, but not 100% on Kit Kat OS (no file size indicator in Storage tab in the setting panel). However, I can still access the files on it via ES File Explorer. Still not satisfactory because the vold in Kit Kat is so stubborn (hence the battery life also gets penalized).

The content of the mounter script (ext2_sd.sh file) I wrote from trials and errors (which works PERFECTLY in Jelly Beans - I use SManager to run this script):

e2fsck /dev/block/mmcblk1p1

mount -o rw -t ext2 /dev/block/mmcblk1p1 /storage/sdcard1

chown root:sdcard_rw /storage/sdcard1

busybox chmod -R 777 /storage/sdcard1

vold

Now, this is probably not the best but it worked for me on Jelly Beans, due to the frustration of the stupid FAT32 4 GB file limitations, and exFAT being a no-go.

I want some opinions on this and why Kit Kat still behave funnily even with the SD card mount fixes already applied (CyanogenMod 11 being the main subject of this discussion). And, of course you can also try this on Lollipop and report back. The only requirements are root, busybox and of course the script manager you usually use.
[Sony Xperia T2 Ultra] miki89:
Our device gets nightly from mokee rom..here is the link http://download.mokeedev.com/?device=tianchi
[Sony Xperia T2 Ultra] elektrik_66:
that does not work? bugs?
[Sony Xperia T2 Ultra] miki89:
i dont know..i didnt try yet, i m still on locked bootloader...try and tell us.. :)
[Sony Xperia T2 Ultra] Andrey Piekas:
only for the D5303 :/
[Sony Xperia T2 Ultra] miki89:
unfortunately it seems so :)
[Sony Xperia T2 Ultra] elektrik_66:
Camera not work
[Sony Xperia T2 Ultra] miki89:
do you try on dual or lte? if u try on dual does sim2 work? :)
[Sony Xperia T2 Ultra] elektrik_66:
LTE
[Android Q&A, Help & Troubleshooting] QA Bot:
Q&A for CWM recovery, Backup (Read back+CWM) and Root Micromax Canvas HD+

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for CWM recovery, Backup (Read back+CWM) and Root Micromax Canvas HD+. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Android Q&A, Help & Troubleshooting] Jet ray:
why mt6592

Some body please tell me why we need or use mt6592 scatter file on mt6591