yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] phekno:
You and me, both. What's the warranty on these things? 1 year?

I bought it from T-Mobile last year (it's an LTE model) because of their free data promo. It's still on an equipment installment plan. I'm wondering if they'd take it in and deal with it. My guess is no, but I suppose it's worth a try.
[Nexus 7 (2013) General] klobkelosh:
yes- the warranty is 1 year. Maybe T-Mo will exchange yours. Best of Luck!
[Nexus 7 (2013) General] khaytsus:
Sorry, hardware failure due to 5.0.2 smells a bit like horse **** to me.

Has anyone actually tried to re-flash the factory image?
[Nexus 7 (2013) General] klobkelosh:
Khaytsus, yes of course. Not all of us are idiots.
[Nexus 7 (2013) General] AvgPhoneUser:
Recover from bootloop.

I posted a thread here on how to recover your nexus device from a bootloop.
[Nexus 7 (2013) General] klobkelosh:
Thanks, but this will not fix units with dead motherboard like I have.
[Nexus 7 (2013) General] cee43ja1:
I've had 5.0.2 since it was released on the Google Factory Images page, and I never had a bootloop or bricking problem. Granted, I bootloader unlocked right out of the box (bought during Christmas 2014), and ADB flashed all 5.x.x updates. So that's nearly four months with Lollipop.

Memory leak was the only problem, but rebooting fixed that. Otherwise, Nexus 7 has been working like it should. If Xposed didn't have a Lollipop beta, I'd still be on Kit Kat, but I'm glad rovo89 dedicated time to find ways to implement it.
[Nexus 7 (2013) General] klobkelosh:
Yep, same here, adb sideloaded every update from the factory images. Never had a boot loop problem. Occasionally rebooted to reclaim leaked memory. Occasionally rebooted, but nothing dreadful. Then, one day, out of the blue, device rebooted and never passed the Google logo. All attempts to revive have failed, recovery says cannot access /cache.
[Nexus 7 (2013) General] madbat99:
Yeah that seems to be what's happening to a lot of n7's. Some are saying lollipop is doing it, some think hardware failure was inevitable. Hard to say.
[Nexus 7 (2013) General] etiger13:
add me to the list with this issue. Unable to wipe user data, unable to flash new rom. Luckily I have squaretrade on it so if I still can't get it to work today, Im sending it in for a replacement/repair/money back.
[Nexus 7 (2013) General] klobkelosh:
http://www.androidpolice.com/2015/0...rate-not-likely-a-result-of-firmware-updates/

Don't necessarily agree with their explanation, but nice to see the best of the android blogs cover this.
[Nexus 7 (2013) General] MarkhamSnappy:
Yeah, I don't necessarily agree with their SPECULATION. :eek:
[Nexus 7 (2013) General] klobkelosh:
Yes, although the expansion that it was an ota update that killed so many is also speculation on our part. Sadly, we have little data.
[Nexus 7 (2013) General] godutch:
try factory resetting in the stock recovery (twrp didnt work for me), rebooting, let it hang for a while and then turning off the device and try booting again. If that doesn't work try flashing the factory image after doing a factory reset from stock recovery
[Nexus 7 (2013) General] Cobra11Murderer:
After hearing the reports I reset the device completely went to stock 5.1, keeping the bootloader unlocked though

I was on 5.02
[Nexus 7 (2013) General] relic:
Perhaps those with bricked n7 can help us conduct this poll to see which group is affected the most? http://xdaforums.com/nexus-7-2013/general/nexus-7-bricked-poll-analysis-t3087358
[Nexus 7 (2013) General] dmoss74:
does anyone seem to know if these failures are correlated with the manufacture dates? i just got a used n7 2013 (32gb wifi), and the box says it was made in china, sept of 2013. mine just gave me the notification for the ota 5.1 update, but i'm a little leery about having this thing go kaput. it's currently on 5.0.2, though, so i can assume it would have already have gone bad, if it were going to.
[Nexus 7 (2013) General] MrsKravitz:
FWIW

I bought mine on launch day, from Staples. Never rooted. Got all updates ota only.

Last week, I noticed the screen went dark. I thought the recharging cable had not been plugged in snugly, let it recharge again overnight. Next day I discovered I had a sleek new doorstop. I can get it to recovery but it gets stuck on erasing and finally reports failure. I can get it to the Google logo in white, but no further. In Recovery, I see bootloader is locked.

I'd recommend to make sure your data is backed up, so the annoyance and irritation of a bricked device that Google is disowning don't become a real disaster. Also, looking back, I would have looked at the update's promised benefits to see if I really needed them (I didn't), and just have left the old version. Of course, a hardware failure might have happened anyway.

I just got an update notice for my Nexus 4 and am not going to accept it for the moment, and maybe not at all. Depending on what you expect from your devices, not all updates are essential.
[Nexus 7 (2013) General] Divine_Madcat:
Well, chalk me up as one of the users whose tablet is bricked from the update. Not sure what to do other than stare at my new brick, and be thankfully i have something else that can assume its role.. *sigh*...
[Nexus 7 (2013) General] 6-speed:
I had my N7 on 5.0.2 pretty much since it got released. It was fine until recently when it started getting laggy and stuttering. I just put 5.1 on it last night and it seemed to clear up the stutters and lag. I hope I dodged this bullet!
[Nexus 7 (2013) General] Kereke12:
This makes me kind of worry, I'm looking into buying a Nexus 7 (2013). Now I don't know...
[Nexus 7 (2013) General] rambleon84:
Ive not had any issues with 5.02 but i have always run custom roms, been using 5.02 since custom roms started using it. I have since upgraded to 5.1 and still no issues. Has anyone that used custom roms had their nexus 7's get bricked or has it been regulated to just ota updates?
[Nexus 7 (2013) General] pflorin:
non-rooted device ran fine 5.0.2... now on 5.1
[Nexus 7 (2013) General] Spades2006:
is this what happened to me? i tried to flash 5.02 from NRT and now i'm in a boot loop.
[Nexus 7 (2013) General] Gorgtech:
Try to flash a factory Image : https://developers.google.com/android/nexus/images

My device is still alive, maybe I´ve dodged a bullet too :P
[Nexus 7 (2013) General] TOT_tomdora:
I was on the developer preview right up until the day 5.1 was released, so I completely skipped 5.0.2, and my device is running beautifully.

Interestingly enough, the DP was almost more stable than 5.1 --- I got the gyroscope problem for the first time a couple days after the install.

But in the event it is 5.0.2, I'm quite glad my laziness and unwillingness to wipe my data saved me [emoji14]

(If it's device age like AP was suggesting then I got mine 11 months ago, so I should be good in that regard too)
[Nexus 7 (2013) General] Aerobatic:
In another forum community came to conclusion that the device affected with infamous EMMC failure bug (after factory reset or unlock) is Nexus 7 2013 WiFi 32Gb, and common opinion is that problem is hardware-related, while upgrade to 5.0.x either has nothing to do with the memory layout corruption, or is a trigger to initially poor hardware.

As Nexus 7 2013 WiFi 32Gb is rare device in the country housing the forum I mentioned, statistics are rater non-presentable. E.g. my Nexus 7 2013 WiFi 16Gb is fine.

Unfortunately participants of this thread do not specify the model of N7 being bricked.

So the question is: do we encounter buggy hardware model (Nexus 7 2013 WiFi 32Gb) or do we encounter buggy 04-04 bootloader?
[Nexus 7 (2013) General] Telyx:
My N7 2013 WiFi 32GB is working fine after upgrading using scrosler's recovery-flashable 5.1 ROM and bootloader zip.
[Nexus 7 (2013) General] sschick77:
My Nexus 7 2013 32 Gb died a week ago. Was in the middle of writing an email, the screen froze, then a reboot went to the Google screen. Tried clearing cache and fastboot prior to checking the forums and seeing others experiencing the same thing. All the error logs pointed to not being able to read/write to any memory. I picked up a new motherboard ($25 on eBay) and replaced. Had to drop down to 16Gb as I couldn't find any 32 available, but the swap worked and my 7 is working again. As a former Transformer Prime owner and the owner of 3 Nexus 7s, this will be my last Asus purchase. (Fool me once shame on you. Fool me 4 times, well...)
[Nexus 7 (2013) General] klobkelosh:
I also picked up a 16 gb motherboard on eBay to replace my 32 gb brick. Hopefully the install goes well once it arrives. Took me a while as I waited several weeks while amex investigated my extended warranty claim. Full refund.
[Nexus 7 (2013) General] klobkelosh:
And...fixed. Very easy repair.
[Nexus 7 (2013) General] Cobra11Murderer:
What I find weird is I ran 5.02 when it came out on my nexus 7 2013 32gb I did noticed a bit of a battery drain and heat but flashed at the time a different kernel and that seemed to help, fast forward today Im running 5.1 stock no heat issues and when I did flash it I noticed the boot loader was updated? Looks like there's more at play then we know.. Its possible that the boot loader that came with 5.02 wasn't helpful but harmful
[Nexus 7 (2013) General] valentinrascu:
Ex owner transformer prime. Asus i think is the worst on emmc choice. :(
[Nexus 7 (2013) General] madbat99:
Same bootloader. Boot loader is not a problem.
[Nexus 7 (2013) General] Cobra11Murderer:
mine sure wasnt it went up by one
[Nexus 7 (2013) General] madbat99:
From 5.0.2 to 5.1? Maybe I was thinking of 5.1 to 5.1.1, can't remember now, lol. At any rate the bootloader isn't the problem.
[Nexus 7 (2013) General] Ditchrat69:
So is this a 32gb issue, or is it with the 16gb model too
[Nexus 7 (2013) General] madbat99:
Seems to be 32.
[Nexus 7 (2013) General] Ditchrat69:
Thank you. Just got my nexus, 16 model, and was trying to decide on this
[Nexus 7 (2013) General] Cynagen:
What are the reports on 5.1 right now? Still failing? I got my 2013 LTE used and it had 5.0.2, I could feel the tablet get hot while propped up in a stand to keep it off the table. I downgraded to 4.4.4 and turned on ART, and I seem to be doing okay, just wanted to upgrade to Lollipop and wondered if the official 5.1 was still risky or not. I'm completely cool with doing custom ROMs, I usually use customs anyways.
[Nexus 7 (2013) General] Cobra11Murderer:
Whatever was causing the issues in 5.02 doesn't seem to be in 5.1.1 my tablet hasn't warmed up or battery drain like it did so its prob safe to move to it also haven't heard any reports of any during on 5.1.1
[Nexus 7 (2013) General] MattG987:
Well, here's your report of it happening on 5.1.1. Mine just updated to 5.1.1, on full battery, etc., totally ideal OTA update scenario. Update finished, and bam, bricked. Won't boot past the Google screen, and any attempt to flash the factory image results in the following:
[Nexus 7 (2013) General] TOT_tomdora:
Fairly similar situation here.

My tablet's gyroscope stopped working (on 5.1), so I rebooted, and found the 5.1.1 OTA waiting. Installed, everything seemed fine --- tablet was even snappier than on 5.1.

Then I turned on the screen an hour later to find the touchscreen unresponsive, but the software itself still worked, so I rebooted, only for it to get stuck. I re-flashed 5.1.1, no errors returned, but it's still stuck on the google screen right now.

I'm sorely disappointed in Asus, and reconsidering my decision to get the Zenfone 2.
[Nexus 7 (2013) General] Gorgtech:
Maybe there is something wrong with the OTA updates in some cases but I always use Factory Images when available.

Did you try to flash the latest TWRP recovery and also clear the cache & Dalvik cache ?

I won´t touch another Anus device again :p
[Nexus 7 (2013) General] TOT_tomdora:
I'm not entirely sure how I'd go about doing this. Recovery mode is still stuck, so no clearing any caches, and what would installing TWRP do to help? I'm fairly new to the flashing scene, having only done it a couple times, and only ever with stock images.
[Nexus 7 (2013) General] Gorgtech:
You need to learn how to use ADB and FASTBOOT in order to flash the stuff or try to use some of the toolkits available for the Nexus 7 ( 2013 ).

Check eg. this one : http://xdaforums.com/showthread.php?t=2389107

If you cannot flash TWRP ( even with the help of a Toolkit ), maybe your NAND storage is already damaged.

But if you can flash this custom recovery and boot it up, clear the cache & Dalvik cache only, you might still have a chance.

It is not always easy to tell if a device is soft- or hardbricked.
[Nexus 7 (2013) General] TOT_tomdora:
No worries, I know how to use ADB and Fastboot, if only enough to type in the few commands I know and hit enter :P

However, I don't know what the problem actually is --- when I flash the stock image, I don't get any of the errors I hear of everyone else getting.

As for TWRP, I'm assuming I flash the twrp-2.8.6.0-flo.img to my N7? It is the most recent version, although I reinstalled 4.4.4 to see if it would boot up on an earlier version of android.
[Nexus 7 (2013) General] Gorgtech:
Exactly, flash the proper TWRP for your device and see if you can mount all partitions with it.
[Nexus 7 (2013) General] TOT_tomdora:
Unfortunately, my Nexus 7 no longer seems to be recognised. ADB devices shows nothing. It was working half an hour ago, so not sure what happened.
[Nexus 7 (2013) General] TOT_tomdora:
Interestingly enough, I can still use the flash-all command, while ADB devices continues to show up a negative --- which sadly means I can't seem to flash the TWRP.
[Nexus 7 (2013) General] Cynagen:
Flash the correct bootloader, flash from stock image download for matching firmware.
[Nexus 7 (2013) General] TOT_tomdora:
I'd like to clarify that my issue was not at all software related, and that 5.1.1 is perfectly fine to install, going by what I have.

My issue was the touchscreen; it wasn't working, so android wouldn't boot, leading me to believe it was the brick. All I had to do was smack it on the back, and the touchscreen started working again.

Many, many thanks to cynagen for his hours of help and realizing what the actual problem was!
[Nexus 7 (2013) General] insink71:
This issue in a nutshell

Basically, everyone who got affected by this [update to 5.02 unrepairable bootloop], regardless of hardware speculation, had one thing in common. They hadn't factory unlocked their devices [or had re-locked them]. The update came through, and from what I can surmise, screwed up the partition reference table. Why do I surmise this? Welp, booting does just show the Google screen, but guess what else just shows the Google screen? Try dropping into recovery from the bootloader [hard button way].. yep, that's right it can't find the stock recovery either. So factory resetting is impossible and so is trying to force an additional update. It can't rewrite or find userdata; so, factory oem unlock fails, and users who have experienced this quickly realize that they have an oversized paperweight on account of an OTA update. Honestly, this is a Google issue more than an ASUS issue, but either way.. someone SHOULD fix it, but both don't seem to be interested in it. I don't own the device, but had a friend that brought me his sick puppy. Sad, but I dunno how to jtag [this device specifically], get into QDM on these devices, or anything. So, I suppose it stays broke, and I admit failure.. but if anyone can point me to some alternative documentation [for this device], I'll gladly work on some kind of solution.
[Nexus 7 (2013) General] madbat99:
Fastboot flashing the entire factory image fails as well, and that reformats all partitions.
[Nexus 7 (2013) General] OnGiantsShoulders:
Fixed (for now)

Hi folks , first post here so go easy please . I am a complete amateur . And I wasn't taking notes.

In a nutshell I had to go back to 4.4.4 as current image would not work (using Nexus Root Toolkit).

Had huge problems with drivers , usb debugging was not enabled before boot loop so every reboot caused usually bad or failed connection (?), halting progress . I wonder if this was due to low battery level (unable to check )

Backup & restore - pointless.

Unlock and install custom recovery would hang on " temporarily running boot.img to enable running elevated commands " . Unlock was successful but no recovery installed afaik .

Installing current image (soft brick) would complete with occasional error but no access to recovery , only google screen.

In the end could not even get into bootloader . Just that google and unlocked padlock again . Battery level ?

Anyway on one occasion when drivers were ok I tried 4.4.4 and tablet was working in under 15 minutes .

Any thoughts ?
[Nexus 7 (2013) General] madbat99:
Huge problems with drivers? That's usually easy. All the instructions in the toolkit are pretty clear.

But have you tried to flash the factory image without the toolkit? Maybe you borked the drivers. Or try a different cable or port.
[Nexus 7 (2013) General] OnGiantsShoulders:
Thank you for your reply . Yes , drivers are usually not a problem and the instructions are clear. That's why I mentioned it . Like I said I am fairly new to this , as will be many who encounter this problem . That is why I'm posting .

I did not have USB debugging enabled after the latest update before the boot loop . Steps 1/4 to 4/4 of driver configuration require access to these settings .

I found my device would either be invisible/wrongly/differently configured/ after each boot loader reboot generally giving waiting for device or time out messages . Normal button combos did not work ~80% of the time , I could not always get anything other than off/ charging or google screen , which would not continue the process .

Cables , I've tried 4 . 1 laptop . 1 PC . About 5 USB ports .

I did briefly try to flash with Minimal ADB and Fastboot . I didn't even find a device so skipped in favour of NRT which I tried first and got me at least somewhere . ( pushed for time )

I did have the SDK installed previously and tried the new android studio but have not had the time to check out properly so did not use .

Maybe I did bork the drivers , my PC seemed to think it was a different device type depending on stage of modification , or ignored as malfunctioning .

Anyway , I hope this helps in some way .
[Nexus 7 (2013) General] MattG987:
That is not correct. It happened to mine upon updating to 5.1 via the OTA, and mine WAS unlocked (though running entirely stock 5.0.2 prior to the update).
[Nexus 7 (2013) General] insink71:
if you are unlocked, you have recourse; it's repairable. if you are locked, it's an OTA brick... at least for now.
[Nexus 7 (2013) General] MattG987:
How is it repairable when it is not possible to write to flash storage, nor read it? Attempting to use fastboot to flash the factory image yields a remote flash write failure; loading TWRP directly into memory to attempt to mount storage yields a no storage found error.
[Nexus 7 (2013) General] insink71:
from what I've read, you can fastboot flash a known good bootloader [even rolling back]. If [correct] partition reference info is restored, you are back in the game. I may have read wrong, but it's what led me to believe data is not screwed.. only the partition map that bootloader is accessing [thus it can't find data, recovery, etc]. With an unlocked bootloader, one can flash previous bootloader and experiment, but all locked up.. one can only hypothesize.
[Nexus 7 (2013) General] Detecter:
Would it be correct to say that the best way of prevent google nexus 7 "brick" it's mine ceep locked, and do not erase userdata, right? or what?
[Nexus 7 (2013) General] Gorgtech:
Who knows, I unlocked my device on the first day after I bought it and never ever flashed a OTA update ( only used Factory Images instead, even if I had to wait a few days longer for them to be released ).

Maybe some devices had faulty NAND storage ? I remember that other devices had similar problems too ( eg. the Samsung Galaxy S3 ) and needed a patched bootloader.

My device is one of the very first batches and still lives. :p
[Nexus 7 (2013) General] MattG987:
Yeah, that sounds like the safest option to me, aside from running custom ROMs.
[Nexus 7 (2013) General] magnamentis:
try this if you still have the problem
[Nexus 7 (2013) General] OnGiantsShoulders:
4.4.4 to 5.02 OTA to 5.1.1 OTA . No problems so far . Fingers crossed .
[Nexus 7 (2013) General] MattG987:
Okay. So, those of you who keep saying "go flash the factory image to fix it!"... you *clearly* do not understand the issue, nor have you bothered to actually read the contents of this thread.

Any Nexus 7 bricked by the update *has unwritable storage*, meaning the factory image *cannot* be flashed.
[Nexus 7 (2013) General] kjdiehl:
Senior Member Fuser-Invent has started a thread to deeply investigate this issue. If a solution is ever arrived at, it will come from here, if anywhere. See here: http://xdaforums.com/nexus-7-2013/general/rd-thread-trying-to-solve-ota-brick-t3117495
[Nexus 7 (2013) General] pokemaniac15:
EDIT: Nope. Nevermind. I don't know why but somehow it just lagged on the Google screen. Which is weird since I didn't do anything wrong. I just panicked, that's all. Sorry.
[Nexus 7 (2013) General] athulele:
I was thinking of buying this tablet. Should I be worried of this bug?
[Nexus 7 (2013) General] klobkelosh:
There was some question for a while if this was a universal hardware failure or if it was a firmware version 5.0.2 issue. Bricks seem to have all but died off, strongly suggesting that it was the firmware that caused the bricking. So, avoid 5.0.2 and you'll probably avoid bricking.
[Xperia Z2 Themes and Apps] FERAS ALHALLAK:
Hi gys

I have experience of how to install the Recovery of my device z2 d6503

and I have worked correctly

And by applying : XZRecovery 4.0.apk

The first step : install Recovery

[IMG="the first step"]http://i1.wp.com/xq55.ws/wp-content/uploads/2015/03/Screenshot_2015-04-08-22-57-34.png[/IMG]

The second step : root access

[IMG="root access"]http://i1.wp.com/xq55.ws/wp-content/uploads/2015/03/Screenshot_2015-04-08-22-57-21.png[/IMG]

The third step : Reboot

[IMG="reboot"]http://i1.wp.com/xq55.ws/wp-content/uploads/2015/03/Screenshot_2015-04-08-23-03-44.png[/IMG]

[IMG="reboot"]http://i1.wp.com/xq55.ws/wp-content/uploads/2015/03/Screenshot_2015-04-08-23-05-23.png[/IMG]

enjoy recovery TWRP

[IMG="recovery"]http://i0.wp.com/xq55.ws/wp-content/uploads/2015/03/Screenshot_2015-04-08-23-05-51.png[/IMG]

Sorry for bad my English

Way transferred from site xq55.ws
[Xperia Z2 Themes and Apps] skellum:
thank you very much! it's working!!!! ;)
[Xperia Z2 Themes and Apps] juliheavy:
? really?
[Xperia Z2 Themes and Apps] FERAS ALHALLAK:
yes my bro
[Xperia Z2 Themes and Apps] chesterr:
Good job broo.. I will be using this on my Z2, hope you're planning on other devices as well :)
[Xperia Z2 Themes and Apps] a.hamameh96:
And how did you root it?

by downgrading to 4.4.2 then flashing 5.0.2 via recovery?

or you used another method
[Xperia Z2 Themes and Apps] shockss:
Is this works on UNLOCKED Bootloaders ? I tried Nuts last version of dual recovery but it didn't work for me.

//EDIT: IT Works on UNLOCKED Bootloader. Sweet! Now we have RECOVERY on LOLLIPOP! HELL YEAH.
[Xperia Z2 Themes and Apps] Isley_:
Thanks for this.

Sent from the 4th Reich
[Xperia Z2 Themes and Apps] juliheavy:
This is for UB only, you post says LB!
[Xperia Z2 Themes and Apps] skellum:
It works with my rooted 5.0.2 LB ;)
[Xperia Z2 Themes and Apps] sankoranga:
also working in LB ....
[Xperia Z2 Themes and Apps] FERAS ALHALLAK:
yes you need downgrading to 4.4.2 then flashing 5.0.2 rooted via recovery and install recovery by XZRecovery 4.0
[Xperia Z2 Themes and Apps] FERAS ALHALLAK:
It works with rooted 5.0.2 LB ;)
[Xperia Z2 Themes and Apps] shehab medhat:
شكرا ليك

راااااااائع

انا بقالي شهر بدور على ريكفري مايكنش فيه مشاكل والحمد لله انت حليت المشكله بكل سهوله

Thanks
[Xperia Z2 Themes and Apps] romdroid.:
Is xposed working?