yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Q&A] moriab:
Add me to the list

I have the same symptoms as the original poster.

Stock Android

Nexus hangs on Google logo during normal boot and also during recovery boot.

Tried 'fastboot oem unlock' and it hangs on erasing userdata (even left it overnight)

Other fastboot commands (erase, format, etc) either hang on erase or say bootloader is locked

Out of warranty

This is the output of 'fastboot getvar all'

fastboot getvar all
(bootloader) version-bootloader: FLO-04.04
(bootloader) version-baseband: none
(bootloader) version-hardware: rev_e
(bootloader) version-cdma: N/A
(bootloader) variant: flo 32G
(bootloader) serialno: 072910b1
(bootloader) product: flo
(bootloader) secure_boot: enabled
(bootloader) lock_state: locked
(bootloader) project: flo
(bootloader) off-mode-charge: yes
(bootloader) uart-on: no
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:bootloader: 0x0000000000aee000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:recovery: 0x0000000000a00000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x0000000034800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x0000000023000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x00000006a3ffbe00
all:
finished. total time: 0.133s

I figured out how to get into "Qualcomm HS-USB QDLoader 9008" mode. QPST recognizes it. It says the Nexus 7 is in "Download Mode". I think that means I can write to it, I just have no idea what files to use. I can get the partition sizes and types from the Nexus, but not sure what to do next. Can I take the img files from the Google factory image and download them with eMMC Software Download that is with QPST?

BTW, Holding all 3 buttons (Power, Up Volume and Down Volume) the screen stays black, but it goes into the Qualcomm mode.

Thanks,

-Brian
[Nexus 7 (2013) Q&A] RoOoBo:
I was also stuck at Google Boot screen today, a few days after finally flashing 5.0.2 on the 4G version. I had to power it off because it was not recognizing the SIM (has happened twice in the last weeks), so I get the SIM out 'cleaned it', put it back and power the tablet on. Stuck on Google Bot screen. When going into recovery mode (TWRP) the touch screen was not working so I couldn't even wipe or recover the flash. In bootloader mode the volume and power keys worked but it was not very useful, I could just power off the device.

Then I read the comments about 'loose' things in the back of the motherboard and I tried just pressing the screen and the back of the tablet with extra force, without even opening it, just to see if it could work again (kind of old style hitting CRT TVs to make them work ;) ). After a few attempts in TWRP recovery the touch screen was finally responsive. I tried to just boot to System and it's back working ...

So maybe this points to bad construction by part of ASUS and stuff is going loose inside the tablet and stops working making the firmware boot to get stuck waiting some response from some unresponsive hardware. I just wanted to share my experience in case it helps other. If the problem resurfaces I will come back.
[Nexus 7 (2013) Q&A] Quarlco:
I had the the same problem as you RoOoBo and tried your solution, it worked. Definitely bad hardware quality. I just pushed down on the back of the Nexus in several places, while resting it on a flat surface, then pressed the start but and it worked.

:good:
[Nexus 7 (2013) Q&A] RoOoBo:
If this issue seems to happen more frequently after updating to 5.x, and not just because of aging or low quality hardware, it could be either because the new firmware is perhaps 'heating up' some component that previous firmwares didn't stress so much. Or it could be that the new firmware is performing some hardware check at boot that affects something that already failed, perhaps not every time but frequently enough, but was not so noticeable when the system is running. From my case it could point to some touch screen problem.
[Nexus 7 (2013) Q&A] klobkelosh:
http://9to5google.com/2015/04/10/nexus-5-nexus-7-bricked-android-lollipop/
[Nexus 7 (2013) Q&A] Neffy27:
Friend gave me his Nexus 7 WiFi model to take a look at it b/c it wouldn't boot after taking the Lollipop OTA update. Its doing everything described in this thread and I feel I have tried everything to get to boot or flash anything. Gonna have to tell him the bad news tomorrow so +1 to the list.
[Nexus 7 (2013) Q&A] pezley:
Add me to the list of doom
[Nexus 7 (2013) Q&A] LUCA LUCA:
and another
[Nexus 7 (2013) Q&A] Asus_USA:
Hi there. What seems to be the issue that you are having with your Nexus 7?

In Search of Incredible

Technical Support Department

http://www.asus.com :: http://service.asus.com/​
[Nexus 7 (2013) Q&A] pezley:
Hi, the same as all the other users on this thread. The os becomes corrupt and unflashable. Not great to happen to so many people :/
[Nexus 7 (2013) Q&A] Asus_USA:
Hello there Luca Luca. What is the the issue that you are having with your Nexus 7?

In Search of Incredible

Technical Support Department

http://www.asus.com :: http://service.asus.com/​

---------- Post added at 08:19 AM ---------- Previous post was at 08:00 AM ----------

We apologize for any inconvenience you have been having with your Nexus 7. Could you please email us the details along with the serial number and your location at socialsupportus@asus.com where we can provide you with better support.

Thank you,

In Search of Incredible

Technical Support Department

http://www.asus.com :: http://service.asus.com/​
[Nexus 7 (2013) Q&A] joshhud:
Another one bites the dust.. happened to me about 2 days ago... seems like we are just going to have to deal with it? How exactly do you start a class action suit lol.
[Nexus 7 (2013) Q&A] Agent5150:
Happened to my Nexus 7 2013 after taking the OTA for LMY48M build. now when I am in bootloader screen my win7 pc doesn't recognizes it and I can't use fastboot to push the stock images. tried Wug's toolkit as well.

Bootloader screen shows:

Product Name - flo

Variant - Flo 32G

HW Version - rev_e

BOOTLOADER VERSION - FLO-04.05

Carrier info - none

serial number - 04c47ed1

Signing - yes

secure boot - enabled

lock state - unlocked

is windows not recognizing it due to drivers? if so, how do I manually install them because I don't see any device in the device manager with exclamation mark.
[Nexus 7 (2013) Q&A] ArGyGG:
I accidentally flashed the 2012 version factory image instead of the 2013 now my tablet is chraging but im not sure if i can get it into bootloader or anything like this.Any solution?
[Nexus 7 (2013) Q&A] elonus:
To get into the bootloader normally you turn off your device. Then hold volume down + power button until it's done booting. Have you tried that? If you have then I unfortunately can't help you.
[Nexus 7 (2013) Q&A] ArGyGG:
Well I have but when I do it it reboots to google logo
[Nexus 7 (2013) Q&A] Haggster66:
I have to say I'm surprised that there are still unbricked Nexus 7s around: Has the issue ever occurred after flashing custom ROMs or is it only happening when updating via stock OTAs?!

I have checked all Q&A threads that might be related but haven't found any official brick avoidance strategy in order to prevent this from happening.
[Nexus 7 (2013) Q&A] N7_TDK:
I... think I am on the same list :( I don't understand what is going on here. It's all the more strange because the previous Nexus 7 that I bought in 2013 was fine with rooting and flashing. I had to get a new one because I dropped it and the screen wouldn't function. I bought one off of Ebay that looks to be made in 2015, according to the barcode.

So the issue with mine is...

It came with 5.0.2, and after turning it on, it installed a bunch of updates that eventually got me to 5.1.1. Cool beans. But for some off reason, the tablet would freeze randomly and reboot. I thought maybe something was wrong with the OS, so I tried to restore it to factory settings. Still got random reboots. So I thought I would try to flash back to KitKat. Downloaded the image from Google's list of factory images, but it would never get past the Google screen. I then redownloaded 5.0.2 and that seemed to get it to work. Updated again to 5.1.1. and the tablet ran fine for about a day.

Now today...I left it to charge. About an hour later, I checked the tablet and it was again, stuck on the Google screen. I never turned it off or anything, so I don't know what happened. Every time I turn it off, it would just turn right back on. I tried to go to recover mode, but like the OP, it just hangs on the Google screen, never gets to the Android lying on its back. Tried to turn it off again, nope, keeps on turning on.

Since it wouldn't go back to recovery mode, I left it at the bootloader, and tried to flash 5.0.2 and 5.1.1 using BOTH WUG's Nexus Root Toolkit, and just a regular adb cmd window. There are no errors in the logs, but neither one gets me past the Google screen.

So... on a scale of 1 to 10, how screwed am I?
[Nexus 7 (2013) Q&A] Divine_Madcat:
As far as anyone seems to be able to tel, a 10. I dont know how crazy people have went with diagnosis, but it appears to be an issue with the EMMC corrupting/dying for one reason. When it happens, your only choice is a new motherboard, and cross your fingers that it doesn't happen again.
[Nexus 7 (2013) Q&A] Haggster66:
A couple of days ago I posted some questions regarding this bricking issue in another thread, especially regarding whether anybody knows how the prevent a Nexus 7 from bricking (as there are obviously enough people around here who's devices are still running fine).

As there were no answers here are my own conclusions:

You need to avoid any official OTAs: It's obvious when googling this (and checking e.g. twitter (#nexus7bricked) that over the last weeks there have been a lot of new complaints about bricked devices - this coincides with the recent security OTAs for 5.1.1 that Google has rolled out. OTAs like these will now be rolled out monthly, which means we'll see more bricked Nexus 7s every single month.

So one could come to the conclusion that those bricks are caused directly by the OTAs. BUT: A lot of people report that after an OTA they were operating their device normally - until their devices "spontaneously" bricked. I have however not read any reports of custom ROM users who have experienced these issues; maybe I missed those posts or those people just didn't mention it. Anyway, I've got the impression that this is only caused by the official firmware and especially in relation to applying official OTAs.

Therefore, if you don't want to brick your device again: Don't use the official stock firmware at all. If it's currently still on an official stock firmware: under any circumstances, don't apply any OTA, ever, at all. Only flash custom ROMs, and to be save, flash a custom ROM and kernel that is F2FS capable, with first formatting everything - even /system (and /cache) - with F2FS. Once you have done that, you might want to use trim sometimes (yes, F2FS takes care of trimming, however it is still possible to manually trim F2FS partitions nowadays with the latest F2FS implementations and it *will* have an effect). There's a proper trimming app out now that doesn't want your money nor any crazy permissions as it was the case with the only available trimming app in the past. You can find it here: https://play.google.com/store/apps/details?id=com.fifthelement.trimmer (root obviously required).

Unfortunately people mostly focus on F2FS support only for the old Nexus 7 2012 tablet which suffers from degrading storage anyway, for which F2FS is merely a damage control measure so that you can keep using it for a while longer until the device will permanently be close to unusable.
[Nexus 7 (2013) Q&A] Que_Ball:
Buy a Tablet with higher quality flash controller and flash memory is solution. Premature wear on flash chip exhaust write cycles leading to failure. If bug in memory controller firmware they may have fixed it in one of the 5.1.x builds but your chips are already damaged if you ran previous build or that firmware failed to update and it is still running buggy wear levelling routine.

Smell a lawsuit if Asus does not keep fixing those affected for free. Mine was fixed free out of warranty. Had to dispute the invoice they tried to stick me with. Only cost me shipping.
[Nexus 7 (2013) Q&A] oldcarpilot:
Fix for hanging at "google"

I found it on another site. Power down and then back on. When it gets to the google screen tap the back of the device a bunch and it will move on and continue to boot. I've had it going for about 3 hrs now and a few reboots and so far it is working normally.
[Nexus 7 (2013) Q&A] mvanwey:
Got one as a gift from employer, completely stock. Same issue as OP.

Google logo only. Even from recovery, won't start, or enter recovery.

No hope?
[Nexus 7 (2013) Q&A] Tmzdroid:
I recently traded in my old 2012 Nexus for a 2013 which wouldn't boot up , had lots of random reboots and a very dodgy touchscreen. I took the back off and taped down the 2 ribbon cables to the battery. It sort - of worked but it was never 100%. I now have a replacement and it feels like a totally different tablet. It feels better made and works perfectly. Definitely hardware issues with too many 2013 Nexus 7s which Google have chosen to ignore.
[Nexus 7 (2013) Q&A] ooofest:
Resurrecting an old topic, I suppose . . . I replaced the display for one of our stock Nexus 7 (2nd generation) tablets recently and it was great for a couple of days, then got the dreaded Google logo hang on a reboot after battery was accidentally drained.

I have replaced the display on our other N7 tablet and it is still working fine, so I am not sure if something changed in my process this time around. Opened it up again and nothing seems to be loose, so not sure of the issue.

This video seems to indicate possible connection issues or it's simply a normal bootup sequence being offered as a miracle cure:

https://www.youtube.com/watch?v=0C5tpeNA4xg

Any clues/updates to resolve this bootup hang since a year ago, perhaps?

- ooofest
[Nexus 7 (2013) Q&A] design.maddie:
I have had this boot hang with all the symptoms as everyone else happen 3 times to my Nexus 7 flo. The first time (I was not on stock ROM) I was able to resolve it by doing multiple back to back soft resets. (something like 10 in a row) Also this was on Christmas eve of 2016. The second time (happened a month later) ((Still not on stock ROM)) I was able to somehow get everything back working by banging "gently" on the back then using WugFresh and flashing back to stock Lollipop. Third time, which I assume was the charm, happened about 2 days ago and have not figured out any way to get it back up. Funny part is it time was the first time I had run into the problem while running a stock ROM. Go figure it is the one time I can't find a work around. It is honestly the only time I had ever ran a stock ROM on the Nexus 7 flo since I bought it in 2013.

I guess in short my point is I do not believe there has been a true solution to the issue. Sorry
[Nexus 7 (2013) Q&A] tonasc:
I know its been years since your post RoOoBo, but I've just revived my old Nexus 7 using this trick, so wanted to say thanks!
[Galaxy S 4 Q&A, Help & Troubleshooting] :
Hi, so this may sound like a stupid question, but I have searched and searched via google even, and I don't know if im searching the terms incorrectly, or getting incorrect information...

I want to buy a Carrier-Free, Bloatware Free Galaxy S4 (Or 5 when it comes out, or even an HTC One)

I want to use it on AT&T GoPhone with LTE.

I see the different variants only working with AT&T 2G/3G or only H+, or only LTE.

When looking for a bloatware, and carrier free S4, what model should I be looking at?

Thanks in advance!
[Galaxy S 4 Q&A, Help & Troubleshooting] :
Bump
[Galaxy S 4 Q&A, Help & Troubleshooting] ExjeetzZ:
i9505

I'm assuming you live in the US since you are talking about AT&T LTE , Only possible answer i can get for you is to get the i9505 (No contract) & then rooting it and removing all the bloatware you do not like.

i9500 does not have LTE therefore i9505 is the most suitable for you

Alternatively You can get i9505 and install a custom rom which basically removes much of the unwanted apps & even then if you want to remove some more bloatware you can always do that.
[Galaxy S 4 Q&A, Help & Troubleshooting] lolo9393:
You will get full and better support in this XDA forum 100% dedicated to AT&T Galaxy S4.

http://xdaforums.com/galaxy-s4-att

great isn't it?
[Galaxy S 4 Q&A, Help & Troubleshooting] :
Unfortunately, that's not what I'm looking for. I am not looking for the AT&T variant of the s4, since I would like a carrier free phone. Hence why I was posting in this forum and not the AT&T.

So the i9505 is an unlocked version? Do the unlocked phones also come with bloatware?
[Galaxy S 4 Q&A, Help & Troubleshooting] :
I think every S4 is coming with bloatware. Root and remove the bloatware is the only way to get rid of it.

What do you mean with unlocked? The bootloader? In this case you have to look for a I-9505 with android 4.2.2 and firmware older than mh5. (Germany) every newer firmware has a locked bootloader.
[Nexus 5 Q&A, Help & Troubleshooting] dmatherl:
I'm having trouble finding out which kernels will support the knock knock feature that the G2 has. Do any kernels besides the bricked-kernel support knockknock. Thanks.
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Look for the feature "double tap 2wake" and other "2wake" functions, as described in the threads features
[Nexus 5 Q&A, Help & Troubleshooting] Sensamic:
ElementalX.
[Sony Xperia Z Ultra] adrienned:
Any update on root for the GPe? I'm about to purchase and don't want to be necessarily locked out of root apps like Adaway.

Can't find any info on the forum either. I swore I read somewhere a guy had the GPe and had root but cannot find that thread. Does it exist? Do any of the devs even have this device?
[Sony Xperia Z Ultra] LordManhattan:
Yeah, you can root it. Just follow the steps here. Jump down to "Rooting GPe".
[Sony Xperia Z Ultra] adrienned:
Thank you! :good:
[XPERIA X8 Q&A, Help & Troubleshooting] tharghan:
Hi... I got a problem with my gf's old X8. Basically it's locked with her old phone operator... there's no way to get the 16 digits cods (she would have to send it to them to get it unlocked and pay the shipping back... not worth for an old cellular). Is there a way to unlock it by myself? Is there a guide i can read? Thanks in advance!
[Android Apps and Games] ACCUSED24:
Hi,

I made a Flappy Bird's remake(How original right?). I plan to add more to it in future. I want people to be able to challenge their friends through google games. Not sure how to do that yet though.

Let me know what you think.

https://play.google.com/store/apps/details?id=com.twistedfirmware.jabg
[G2 Q&A, Help & Troubleshooting] Schyler67:
If I have rooted my LG G2 running on 4.2.2 will I safely be able to update my phone to KitKat without messing it up?

I haven't installed any custom ROMs or anything that I know of, so im assuming that is whats called a stock root.

I have installed and use G2 tweaks (G2 Xposed and G2 Settings)

So my question is when KitKat is released will I be able to safely update my phone without bricking it or anything?

I am with Sprint also!
[G2 Q&A, Help & Troubleshooting] GalaxySIIII:
i recon just stay with 4.2.2 it is best OS android today .. kitkat is ... crap :silly:
[G2 Q&A, Help & Troubleshooting] Schyler67:
Okay thanks but does that mean I can or can't?
[G2 Q&A, Help & Troubleshooting] GalaxySIIII:
what
[HTC Sensation] Topol-Ms:
Hi everyone

I have this htc sensation it is stack in bootllop and I don't know why!! anyway I tried to fix it with a RUU file but can't find the correct file to my phone.

I belive it is a T-Mobile phone from NL and here the info from my bootloader

also I got this by cheking my version and CID

If anyone can help me with the link to the correct RUU file it would be nice

thanks guys
[HTC Sensation] JJeamy:
if you still can't find your RUU...you can try another RUU (different CID) that have a same or higher version than yours...but ofcourse you must modified first android-info.txt in that rom.zip file..you can follow completed guide from here.. especially read at step 4. Flashing RUU manually

or alternative way..you must make a goldcard..

hope this help...
[HTC Sensation] Topol-Ms:
thanks but how to modify the android-info.txt I add my CID like this :

it does not flash
[HTC Sensation] JJeamy:
yap..that's correct...but..what's your MID anyway..?

how do you to change that...did you already extracted the rom.zip file then modified that android-info.txt file..?

because you don't need to extract that rom.zip (because if you extracting that file first that will broken a compiled that rom.zip)...just open it that archive then open it android-info.txt from there..then edited that file and save it

also try open it and edited that file with notepad++..

hope this help..
[HTC Sensation] Topol-Ms:
sry what what you mean with MID? and the winrare says the file is curopted I can't cahnge it
[HTC Sensation] JJeamy:
MID = model id ...to know that just using command "fastboot getvar mid" or "fastboot getvar all"

just try open it that archive with Windows Archive Manager (Windows built in ZIP program), then copied android-info.txt to outside (don't extracted) then edited with nopad++ then save it...then deleted original android-info.txt from that archive then drag and drop the new one to that archive..
[HTC Sensation] Far_SighT:
He's already posted it:

FYI, you can't flash unsigned or missing-cid firmware without S-OFF.

Try these:

http://www.tsar3000.com/Joomla/inde...riginal-roms&catid=65:htc-downloads&Itemid=98

http://www.shipped-roms.com/index.php?category=android&model=Pyramid

Use this thread to look for an RUU. Nearly all RUUs are present on above two links. Your CID is included, so I guess an RUU should be available.
[HTC Sensation] JJeamy:
1. what he's already posted it is android-info.txt from ruu that he want changed it..not MID from the phone that he has..that's why i ask him to see his mid and changed it too to android-info.txt from that RUU..

2. he can't find the right RUU for his phone...so that's why i suggest it to him to flashing another RUU and try change it cid and mid in android-info.txt from that other RUU to match with his phone..

3. you can see that i've already suggest it him to the same link thread about related RUU that you give it again to him too..

4. so you're already guessing that the right RUU for his phone is available from the two link that you're give it to him above...so can you show me and posting it in here exactly the link for that RUU (i mean the correct RUU that have CID and MID that are suitable for his phone and have equal or higher version than he was had right now)..ofcourse this is for helped him..then make an more easy and a simple way to fix his sensation..

so for [MENTION=4282625]Topol-Ms[/MENTION] if that's RUU way fail..maybe you can try it a way to unlocking your bootloader first via htcdev.com.. then after that you can continued to flashing custom recovery..then flashing custom rom..

hope this help...and good luck..
[HTC Sensation] Topol-Ms:
thanks man I tried to unlock my phone with htcdev.com everything go smooth untill I get the email with unlock_code.bin and when I try to flash it it says this :

I hate this phone!!
[HTC Sensation] JJeamy:
what you choice while in the list of "select your device" to unlock in the first gate in htcdev.com..?

that you already choice "All Other Supported Models" ..?
[HTC Sensation] Topol-Ms:
I tried 3 kind of sensation phones in the list and also all other supported models but nothing everytime I get the same message
[HTC Sensation] JJeamy:
did you already tried...i think maybe you can try it if don't..just try factory reset from bootloader first..let me know what happen..
[HTC Sensation] Topol-Ms:
factory reset and then I unlock again?