[Q] Nexus 7 2013 Stuck on Google Logo - Nexus 7 Q&A, Help & Troubleshooting

Ok so my Nexus 7 2013 was working fine then it just stopped working.
I haven't fiddled with it or tried installing anything custom or rooting.
So I used snapchat to send a pic to my bro and after I did that i set the tablet down.
I was playing my ps3 when I saw something funny and I wanted to take a pic of it with my tablet.
Noticed it wasn't responding when i pressed the unlock button. I figured it was dead but realized
that couldn't be it since it was like 75%ish power left on. So i turned it on and from that point on it's been stuck on
the google screen and sometimes i get the red exclamation android guy.
As I type this the tablet is on the Google logo screen and it's been like that for 10 mins.
So again i clarify that my tablet has never been rooted or done anything custom with it.
Sadly also i don't have warranty from the store i bought it (BestBuy) and i bought it on Sept 15th of this year.
What are some steps I can take to help me fix it? Or is this thing dead for good? I read that if you can access your bootloader then it's fixable.

You should ask in the nexus 7 2013 forums. This forum is for the 2012 model
Sent from my Nexus 5

Related

[Q] Things To Do w/ Nexus 7

Hello guys, first time posting on XDA. I've been reading these forums though for a long time.
Anyway, yesterday I ordered a Nexus 7 from an Indian shopping portal. My first proper Android device. A few Q's:
Can I attach a pen-drive to the thing via OTG?
Now, I'm worried that the screen separation bug might hit me or something. Is it easily fixable or must I RMA if it happens?
How is the default JB keyboard? Is it fine or must I buy SwiftKey?
Any good cases/keyboards etc?

[Q] The Curse of the Eternal Bootloop

Dear esteemed community members of the XDA developers community website. I have a long and sad story, of which I am hoping you may be able to provide some extra insight into the troubles I have met with my Nexus 4.
I purchased my Nexus 4 (sans rubber feet) last year in August, bought from a Mediamarkt in Berlin during my first travels into Europe, when my Samsung SII met a cruel and drunken fate. When I first got the shining glittering Nexus 4, it notified me of an OTA system update, and doing as instructed I glibly pressed "Update". After the digital progress bar's needle finished injecting its panacea into the phone, it restarted and was then caught in a boot-loop. Frantic, repeated, turning off and on procedures followed, like I was trying to perform CPR at a crash scene. It was out like a light, except its light was still on in the shape of a glowing "X". After trying all the system/cache/data wipes the system tools would allow me, nothing made it budge. I resorted to flash everything to stock with fastboot to successfully get it up and running again, but it was a bad start to a troubled relationship.
A flight back to my home in Australia and some months later (about March this year) I decided to try the OTA update again. I figured after some time, surely they'd have fixed the OTA issues, no? Alas, soft-bricked again -- the glowing "X" taunting me once more. I tried and I tried with all my might to flash all number of versions of Android -- 4.2, 4.3, 4.4 -- using all manners of manual and automated (toolkit) methods, all to no avail. I put the phone in my drawer and borrowed a house mate's iPhone 4, replete with cracked screen.
Fast-forward to a few days ago: my house mate's own Nexus 4 kissed gravity and it was more an expression of a troubled break-up than any affection. She needed her iPhone back and I went back to no phone. There was some kind of bliss in being disconnected, however being a freelance designer and developer, my life-line is work and work is often received and completed via phone duties. Wondering if I could successfully defibrillate life back into this still-new and handsome looking Nexus 4, then the better I would be than without phone. I plugged it all in again, performed a manual flash of KOT49H to finally see past the rotating dots to view the android fellow lying on his back getting some much-needed TLC from some futuristic blue polyhedron tumbleweed. I was "in with a grin" -- the phone and I were back in business.
Lazing about one hung-over Saturday morning with my phone plugged into the charger, me checking out my family and friends' inane burblings on Facebook, the phone winked a red eye at me and went black. I was confused. What happened? Was it something I said? Posted? I tried to turn it on again, and yet silence persisted. It was plugged into the wall, power was on -- there should be juice present within this ripe fruit.
Holding it in my questioning hands, I shakily brought it over to my computer and plugged it into the USB. I tried turning it on again, and the eyes fluttered open, its stare fixated and blank, a rotating vision of 4 dots tumbling in an endless mocking loop. I sighed, "Not again." I tried more methods of flashing and restoring the phone's version of Android, both manual and automated. Nothing. Nada. Zip. Ziltch. Zero.
Here I am, again at the precipice of uncertainty with this phone's status and fate. No activity beyond those dots locked in an eternal dance of emptiness. The drapes of its consciousness are pulled, no vision of what's on stage or who's singing. Silence. Empty space. Lingering thoughts of my involvement bounding like playful lion cubs through the savannah: "if only I...", "if only it...", etc.
So here, dear reader of an esteemed Android developer community website, I petition you in great need and distress: if perchance you may be able to offer some insight into my troubled 'droid; if maybe there's some way to read some console output of what and where the errors are occuring; if perhaps there's something more physical that could be the cause of such pain and strife. I wish to understand my companion's feelings and thoughts more, to know why it feels such despondency in living and working, and how I may be able to coax it back to consciousness. Perhaps all it needs is to have some other sort of love and kindness, the type I'm potentially not adept at speaking in a language for it to understand. Either way, I would love any information someone may be able to proffer.
Please help me XDA developers -- you're my only hope.
lvl99 said:
Dear esteemed community members of the XDA developers community website. I have a long and sad story, of which I am hoping you may be able to provide some extra insight into the troubles I have met with my Nexus 4.
I purchased my Nexus 4 (sans rubber feet) last year in August, bought from a Mediamarkt in Berlin during my first travels into Europe, when my Samsung SII met a cruel and drunken fate. When I first got the shining glittering Nexus 4, it notified me of an OTA system update, and doing as instructed I glibly pressed "Update". After the digital progress bar's needle finished injecting its panacea into the phone, it restarted and was then caught in a boot-loop. Frantic, repeated, turning off and on procedures followed, like I was trying to perform CPR at a crash scene. It was out like a light, except its light was still on in the shape of a glowing "X". After trying all the system/cache/data wipes the system tools would allow me, nothing made it budge. I resorted to flash everything to stock with fastboot to successfully get it up and running again, but it was a bad start to a troubled relationship.
A flight back to my home in Australia and some months later (about March this year) I decided to try the OTA update again. I figured after some time, surely they'd have fixed the OTA issues, no? Alas, soft-bricked again -- the glowing "X" taunting me once more. I tried and I tried with all my might to flash all number of versions of Android -- 4.2, 4.3, 4.4 -- using all manners of manual and automated (toolkit) methods, all to no avail. I put the phone in my drawer and borrowed a house mate's iPhone 4, replete with cracked screen.
Fast-forward to a few days ago: my house mate's own Nexus 4 kissed gravity and it was more an expression of a troubled break-up than any affection. She needed her iPhone back and I went back to no phone. There was some kind of bliss in being disconnected, however being a freelance designer and developer, my life-line is work and work is often received and completed via phone duties. Wondering if I could successfully defibrillate life back into this still-new and handsome looking Nexus 4, then the better I would be than without phone. I plugged it all in again, performed a manual flash of KOT49H to finally see past the rotating dots to view the android fellow lying on his back getting some much-needed TLC from some futuristic blue polyhedron tumbleweed. I was "in with a grin" -- the phone and I were back in business.
Lazing about one hung-over Saturday morning with my phone plugged into the charger, me checking out my family and friends' inane burblings on Facebook, the phone winked a red eye at me and went black. I was confused. What happened? Was it something I said? Posted? I tried to turn it on again, and yet silence persisted. It was plugged into the wall, power was on -- there should be juice present within this ripe fruit.
Holding it in my questioning hands, I shakily brought it over to my computer and plugged it into the USB. I tried turning it on again, and the eyes fluttered open, its stare fixated and blank, a rotating vision of 4 dots tumbling in an endless mocking loop. I sighed, "Not again." I tried more methods of flashing and restoring the phone's version of Android, both manual and automated. Nothing. Nada. Zip. Ziltch. Zero.
Here I am, again at the precipice of uncertainty with this phone's status and fate. No activity beyond those dots locked in an eternal dance of emptiness. The drapes of its consciousness are pulled, no vision of what's on stage or who's singing. Silence. Empty space. Lingering thoughts of my involvement bounding like playful lion cubs through the savannah: "if only I...", "if only it...", etc.
So here, dear reader of an esteemed Android developer community website, I petition you in great need and distress: if perchance you may be able to offer some insight into my troubled 'droid; if maybe there's some way to read some console output of what and where the errors are occuring; if perhaps there's something more physical that could be the cause of such pain and strife. I wish to understand my companion's feelings and thoughts more, to know why it feels such despondency in living and working, and how I may be able to coax it back to consciousness. Perhaps all it needs is to have some other sort of love and kindness, the type I'm potentially not adept at speaking in a language for it to understand. Either way, I would love any information someone may be able to proffer.
Please help me XDA developers -- you're my only hope.
Click to expand...
Click to collapse
tl;dr is the phone rooted ?
fahadsul3man said:
tl;dr is the phone rooted ?
Click to expand...
Click to collapse
No
So after skimming through your jibber jabber the problem is the phone gets stuck in the boot loop no matter what method you used ? Try using different ROM instead of the KOT49H I am assuming you are out of warranty by now right ?
Sent from my Nexus 4 using Tapatalk

Recently New [2013] Nexus 7

Previously bought a 2012 Nexus 7 that had a custom rom on it, damn thing had screen issues or something. Spazzed out all the time, wouldn't update or anything. Sold it for what I bought it for used.
About two weeks ago picked up a new 2013 Nexus 7, still sealed in the box for $100!
Couple already both had them and it was a company gift, guy was looking for a quick sale. Seemed to good to be true online but I went anyways and there it was, genuine in all of its glory with a clean serial.
Mostly going to use it for work purposes, being a process server taking field notes on a tablet and backing it up to my drive is far easier than writing down notes with my sloppy handwriting.
Going to research through the threads and look into a possible custom rom or playing with it more. Currently have a Unity launcher running on it which is pretty clean and nice.
Anyways just throwing myself out there, i'll be around lurking.
Ok.

Fire HD 8 7th Gen 2017 - should I grab one?

Hi,
so I am fairly new (tbh: completely new) to Amazon tablets. I just saw the new tablets announced for June and thought about replacing my old-as-f*ck Nexus 7 with a HD7 or HD8. How is the experience so far - is it likely that you can easily root/remove the ads, put on a custom rom and so on? Will this limit the tablet in any way? Or do I need to leave it stock, otherwise not be able to use Kindle/Prime Video and so on? Thanks!
fBx said:
Hi,
so I am fairly new (tbh: completely new) to Amazon tablets. I just saw the new tablets announced for June and thought about replacing my old-as-f*ck Nexus 7 with a HD7 or HD8. How is the experience so far - is it likely that you can easily root/remove the ads, put on a custom rom and so on? Will this limit the tablet in any way? Or do I need to leave it stock, otherwise not be able to use Kindle/Prime Video and so on? Thanks!
Click to expand...
Click to collapse
Most of the times as you can clearly see here on xda it takes a while or maybe even a long time, for the amazon tablets to be root able. I would buy a 6th gen right now, when your not connecting it to the internet it should be possible for you to root it right now (if it has the right software version installed).
If you want to buy a 7th gen then there is the problem that you can't connect it to the internet, because it will automatically upgrade you will have to wait until there is a method to root it before you can normally use your tablet....:crying:
Both the 6th and 7th Gen. Fire HD 8 are near if not identical specs wise, as above if your hoping for root buy the 6th Gen. as you may get lucky and get one with a pre-installed lower software version that's rootable, however you may not, the 7th Gen is very likely to come with 5.3.3 which I don't think is currently rootable.
As for custom ROMs, Amazons tablets are pretty locked down and as such there's little to no custom ROM development going on, not in recent years anyway. Go with something else if you like trying new ROMs otherwise the Fire HD tablets are pretty well made and you can sideload the Google Play Store pretty easily too.
Okay, I cross-referenced 2016 and 2017 and it's basically the same specs. Not sure it would be that much of an upgrade. I'll check what a 2016 HD 8 goes for at ebay.
Gilly10 said:
Both the 6th and 7th Gen. Fire HD 8 are near if not identical specs wise, as above if your hoping for root buy the 6th Gen. as you may get lucky and get one with a pre-installed lower software version that's rootable, however you may not, the 7th Gen is very likely to come with 5.3.3 which I don't think is currently rootable.
As for custom ROMs, Amazons tablets are pretty locked down and as such there's little to no custom ROM development going on, not in recent years anyway. Go with something else if you like trying new ROMs otherwise the Fire HD tablets are pretty well made and you can sideload the Google Play Store pretty easily too.
Click to expand...
Click to collapse
Is it expected that loading Google Play on the 7th gen will work the same way as it did for the 6th? I don't need root or a custom ROM, but I don't want to be limited to the Amazon app store.
I will say that loading google play has worked so far on the latest HD 8. Used instructions and files linked here: https://forum.xda-developers.com/amazon-fire/general/how-to-install-google-play-store-fire-t3486603. Was able to load paid version of a couple apps and they worked fine.
joshparr said:
I will say that loading google play has worked so far on the latest HD 8. Used instructions and files linked here: https://forum.xda-developers.com/amazon-fire/general/how-to-install-google-play-store-fire-t3486603. Was able to load paid version of a couple apps and they worked fine.
Click to expand...
Click to collapse
so just to confirm...
I don't need to root it to get play store working?
just need to get the Google drive suite up and running as it's mostly used for work.
is so, I'm all set to take the plunge and get myself a firehd8!
[my Nexus 7(2013) just died. :crying:]
psychoxman said:
so just to confirm...
I don't need to root it to get play store working?
just need to get the Google drive suite up and running as it's mostly used for work.
is so, I'm all set to take the plunge and get myself a firehd8!
[my Nexus 7(2013) just died. :crying:]
Click to expand...
Click to collapse
I took my HD 8 (7th Gen) straight out of it's box and followed the instructions. Now someone reported in the other thread their Fire 7 (7th Gen) had issues with the versions linked in the thread. Mine was sitting at Amazon OS 5.3.3.0 out of the box and I didn't update that first. The guy with the Fire 7 stated he was at 5.4.0. One other person with the Fire 7 ran into a similar issue, but used newer versions of the Play Store and Play Services to get it working.
I just checked on my tablet and the Play Store and Play Services on the HD 8 just updated in the last 5 minutes, they are within the same build cycles as the one guy listed as working on his Fire 7.
Google play works
I took my tablet (hd 8 2017) straight out of the box in 5.3.3, follow the instructions in the link from this thread, google play works but location services dont. Factory reset, install google play with the files from the link again, and everything works!! after that, the tablet upgrade itself to 5.4, google play and services still works perfectly fine :victory::victory:. So the method and files in the link works, for me at least, if any problem appears just factory reset the tablet and try again. Sorry for my english.
alex192004 said:
I took my tablet (hd 8 2017) straight out of the box in 5.3.3, follow the instructions in the link from this thread, google play works but location services dont. Factory reset, install google play with the files from the link again, and everything works!! after that, the tablet upgrade itself to 5.4, google play and services still works perfectly fine :victory::victory:. So the method and files in the link works, for me at least, if any problem appears just factory reset the tablet and try again. Sorry for my english.
Click to expand...
Click to collapse
Thanks for the suggestion. Did you try the Gmail app from the Playstore? Does it work correctly for you?
trovatrice said:
Thanks for the suggestion. Did you try the Gmail app from the Playstore? Does it work correctly for you?
Click to expand...
Click to collapse
Yes, Gmail from Google Play work correctly in my HD 8 2017.
so ive just found this site, only a couple days too late by the looks of it. i read (not very carefully) that it would be easy to root a kindle fire hd 8, so i just got one in the mail today (7th generation). i havent connected it to the internet, its got 5.3.3.0 on it, and my goal was to replace the stock OS with regular android. is this not currently an option?
(if not, any suggestions on what i should do/not do with it in the meantime? will connecting it to the internet begin an automatic software update that will render the device even more useless? i thought i read someone post something about that)
Fire HD 8 (2017) here on 8.4.0.0. Google apps sideload just fine. Removed lockscreen ads permanently just by submitting a help ticket.
It's a fabulous tablet for the price. I'm using mine primarily as a retro emulator although I can't find any good compact tablet gamepads (hoping to find a joycon-ish clone).
Fire HD 7thG- Screen cracked... What to do????
my FIRE HD 7th G screen cracked in a SPIDER WEB! I do not have warrenty. What to do? Is there a replacement screen for this new one?
cataldridge said:
my FIRE HD 7th G screen cracked in a SPIDER WEB! I do not have warrenty. What to do? Is there a replacement screen for this new one?
Click to expand...
Click to collapse
As far as I know, the difference between the 6th generation and 7th, is pretty much the programming and a few internal tweaks. I am about 90% sure there is nothing different about the physical hardware of the devices. So if you can find an HD 8 that's 6th generation, for real cheap, you can probably swap out the screen. There are several tutorials online if you do Google search, on how to do that. It sounds harder than it actually is. With that said, i am still looking for a cheap HD 7 so I can replace the screen in the one I have tucked away in a drawer.

Bricked ONN 8" Model 10003561 Android 10

I was following the root method for tablet 8" but it was an older version. Now I can no longer boot up the tablet since I flashed the wrong boot.img. I unlocked the bootloader but that's the furthest I can get.
Anyone have any luck rooting on these 100003561 Onn 8" Tablet Pro Android 10 devices? Maybe post a guide for beginners to show what is possible?
No luck here either
Andenthu said:
Anyone have any luck rooting on these 100003561 Onn 8" Tablet Pro Android 10 devices? Maybe post a guide for beginners to show what is possible?
Click to expand...
Click to collapse
I tried it last night, and got the code orange loop. I'm going to try to restore factory and go another route
I have that model, too. Doesn't come pre-loaded with junk, fortunately -- mostly I just want to remap the stupid dedicated Walmart app button. It's a present for an elderly relatively that lives without a car in a town nowhere near any Walmart business -- never used a smart phone before (and I'm guessing even though she's pushing 90 she's never been in a Walmart).
Kind of annoying they put the Walmart button in the very location you normally press to see which tasks are running.
PS: I've only had it for less than a day, haven't played with it much, but so far, it's much nicer than I was expecting, at least in terms of how the build quality "feels."
It's really not a bad cheapie choice if you prefer to avoid the Amazon ecosystem.

Categories

Resources