Database Users

[Q] Nexus 7 hangs on Google screen (tried fixes in other threads here but no result)

Hello there everyone.
First off, I know this might seem like a subject that's already been covered. Trust me, I've spent the last few days going through every thread I could find on here trying everything out as well as other threads on tips on the net. So I'm posting this because I've tried everything and run out of troubleshooting methods to have a go with. The experts here may relish the challenge of solving this one. Or tear their hair out just like I'm doing. Hence my username. I'm worn out after countless hours of doing this.
Background:
I had a rooted Nexus 7 with superuser and TWRP. Jellybean 4.2.1 update would never work, always got an assert failed or some other error when it tried to do so. I then decided to go back to a previous backup in case something had gone wrong since in order to get on with installing the update.
Previous backup loaded fine. Unfortunately WiFi was not working and just kept on searching forever. After lots of googling and trying all the fixes with my router and so on which failed to solve anything, took the advice of going back to a factory reinstall.
Reinstalled, booted up, selected language on Google Welcome Screen then onto Wifi screen. Stuck on seaching forever. More googling and took advice. Decided to do Nexus Root Toolkit's flash stock+unroot to get back to clean state. After install there's an issue that just won't go away and that is:
Problem:
Google Nexus 7 (Wifi model) won't go past Google screen (this is not the coloured logo, just the word "Google" in white).
Associated problems:
Going into recovery just shows the same screen or sometimes an android lying on its back with a red triangle.. So no stock recovery available. Using fastboot to lock and unlock the bootoader as a recommended fix has no apparent effect with the result just being the same Google screen (padlock icon unolocked or locked depending upon locking status) even after a long wait.
Flash stock+Unroot in Nexus Root Toolkit has the same result. I left the thing on for a long time each time after a factory install because of advice saying to wait and still the same screen all that time. Longest time was 6 hours left on due to frustration and waiting to see if anything at all would happen. It didn't.
I can't access ADB in bootloader. I can only access ADB when the device is in TWRP or CWM menus. (In other words Nexus Root Toolkit complains it can't connect when I'm in the bootloader for example if I want to do any operation that requires ADB, but doesn't complain when in in those two recovery menus). Nexus Toolkit will quite happily do the Flash stock+ unroot and get to the screen where it says wait a while for device to reboot and you can press any key to exit.
I have wiped system, cache, boot, recovery, userdata using both fastboot and JROM Flasher. I can install TWRP or CWD using the Nexus Toolkit and wipe stuff using those but still no joy. I have gone through every permutation many times step by step. I have even used different Jellybean factory images from 4.1.0 to 4.2.1 as well as past backups with the same result each time.
Have used soft bricked and device is on options in Roolkit. No joy.
I have also disconnected the battery as part of the troubleshooting process.
Basically, nothing I can do using the information I've been able to get hold of can get past that screen.
Other quirks:
I have also noticed when installing a factory image a message comes up:
writing bootloader FAILED (remote: (invalid state))
It continues with the rest of the installation however as normal.
Also PdaNet comes up with the message:
Wrong WinUSB Pipes found
If I try Connect Internet (USB) option.
I have downloaded Nexus 7 tablet USB driver revision R06 and tried to use them but my PC will only recongise the device as an MTP device with failed driver install when the tablet is in that endless Google screen.
With the install of the Naked Universal Driver it only recognises the device in the Device Manager as Google Nexus 7 Bootloader Interface.
Driver tests in Nexus Root Toolkit fail. It advises enabling USB debugging as one of the fixes which of course I cannot do as I can't boot up to reach those options.
From this I surmise there is some problem with the drivers. I have tried on two different PCs as well.
Software I have used in all my efforts: Nexus Root Toolkit 1.6.2, Gnex, JROMFlasher, TWRP, CWM, PdaNet, SDK Manager, Nexus 7 tablet USB driver revision R06, Naked Universal Driver 0.72 .
I'd appreciate any advice (apart from sending the thing back), epescially if it's in a step by step easy to follow format. So basically, my question is, how do I fix this? Is it possible to fix?
Many thanks in advance!

I just thought I'd update this, mainly to let people know what to do if they find they have a similar problem to the above.
Basically, as said before none of the fixes worked. I spent a huge amount of time trying everything. So in order to save people massive amounts of time who have pretty much the same problems as I had and spending hours upon hours trying fixes like I did, then the best thing to do is to return your Nexus 7 to where you bought it for a return.
Mine was subsequently discovered to have a hardware fault so I was basically trying to fix the impossible. If you find yourself in the same boat after trying the fixes, and they don't work after a couple of tries, don't do it multiple times like I did. It's just easier, less frustrating and will save you much hair loss, anger and general irritation to let Asus fix it.
Yes, I know some of us get a bee in our bonnet about fixing it ourselves and see returning it as the last resort (like me), but anyway, trust me, just send it back, and save yourselves the trouble in a case like the above.
My tablet has arrived back repaired and works again. The hardware fault was covered by the warranty.
I hope anyone who encounters the same issues as I have manages to find this of use in the future!

Nexus 10 Random Reboots

'My Nexus 10 started to randomly reboot several times a day after the Kitkat update and because it is outside the warranty period I cannot get it replaced.'
It reboots no matter what is running and sometimes it reboots immediately after a power up but never enters a reboot loop.
I've tried a factory reset and running it in safe mode but that didn't stop it.
I've not been able to replicate the reboot fault until yesterday when I ran the BBC iplayer and downloaded a 1-hour Horozon video of about 650Mb and when I tried to play it I got a reboot and that happened consistantly.
I tried a complete power down and reboot then tried to play the downloaded video but it always rebooted.
I tried deleting and re-saving the video incase it was corrupt but it still rebooted.
I tried deleting the video and streaming it and I could watch it that way without any reboot.
I've tried downloading three 1-hour Horizon videos of about the same size and only one plays without rebooting.
A check of running apps shows just the keyboard and a couple of system apps but I still get the reboot when I try to play the saved video.
I thought about removing apps one at a time to see if that would solve it but I've basically got the same apps I had before the Kitkat update.
I wondered if I could undo the Kitkat update and flash the previous rom to see if that would solve it for Kitkat was not a big improvement.
I've never used a custom rom and not run anyting other than stock software.
I would be most grateful for any suggestions on how to fix this rebooting problem and whether going to an earlier version of Android is feasable and how would I do it.
PS. There is a BBC iplayer option to download videos using less resolution and when I choose that option the Horizon file size falls to 344Mb which is about half the size of the original and it solves the reboot problem when playing the saved video.
So it would seem that the BBC iplayer reboot problem is related to file size.

It's fairly easy to downgrade, just Google "nexus factory images" and you should find all the old versions of android straight from Google. There should be guides online for how to flash a factory image. Just make sure to back up all your files to your computer as it will wipe everything.
Sent from my SGH-I747M using xda app-developers app

gc84245 said:
It's fairly easy to downgrade, just Google "nexus factory images" and you should find all the old versions of android straight from Google. There should be guides online for how to flash a factory image. Just make sure to back up all your files to your computer as it will wipe everything.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Thanks for your help.
I've found the factory images and I'm now looking for a simple detailed guide how to do the downgrade.
My Nexus 10 is on 4.4.2 (KOT49H) and I think I'll try downgrading one level to 4.4 (KRT16S) to see if that solves the reboots problem and if not then I'll try downgrading further to 4.3 (JWR66Y).

Gaugerer said:
Thanks for your help.
I've found the factory images and I'm now looking for a simple detailed guide how to do the downgrade.
My Nexus 10 is on 4.4.2 (KOT49H) and I think I'll try downgrading one level to 4.4 (KRT16S) to see if that solves the reboots problem and if not then I'll try downgrading further to 4.3 (JWR66Y).
Click to expand...
Click to collapse
Here is a good guide (sorry, I would have posted it earlier but I didn't have my computer with me at the time and was posting from my phone):
http://forum.xda-developers.com/showthread.php?t=1907796

gc84245 said:
Here is a good guide (sorry, I would have posted it earlier but I didn't have my computer with me at the time and was posting from my phone):
http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
Thanks for the guide link.
Unfortunately, my laptop is running Windows 8.1 and it is difficult to install the USB driver and Android Development Kit needed to flash previous Android versions, so I've given up until I can find the way to do it.
PS. I've found a way of installing the ADB and Fastboot drivers on my Windows 8.1 laptop and here is a link:
http://forum.xda-developers.com/showthread.php?t=2588979
So I'm back on track to solve my random reboots using an earlier version of Android.

I noticed the iPlayer hard crash thing too. I can play downloads, but as soon as I pause it and attempt to restart, or just slide the progress bar to move to a different part of the video, the tablet hangs then reboots. It's completely reproducible, and doesn't happen on any of my other devices.
Apart from that, my n10 has now gone 20 days since the last random reboot, so it's a lot more stable in general than it used to be!

I've found a easy way to downgrade to 4.3 and would be grateful for any opinion on how safe it is and if anyone has tried it.
http://forum.cyanogenmod.com/topic/83985-nexus-factory-images-to-revert-to-stock/

AleT said:
Apart from that, my n10 has now gone 20 days since the last random reboot, so it's a lot more stable in general than it used to be!
Click to expand...
Click to collapse
Arghh...this thing is a POS. I haven't used it in 2 months. Today I fired up chrome for some browsing. It hard locked within 5 minutes. I left it for an hour plus with the screen on and still locked up. Just frustrated. Worst Android device I've owned.
Sent from my XT1053 using Tapatalk

Either you have a faulty app or your tablets have a hardware defect. The random reboot issue, where the GPU driver would leak memory and force a kernel panic, has been fixed since Android 4.3 in July. This includes the Chrome reboot issue. I've had 2 reboots over 13 months, and both were cause by a ROM issue. I assure you, there is nothing wrong with the Nexus 10. Try a 4.4.2 factory image and see if that solves anything.

Koopa777 said:
Either you have a faulty app or your tablets have a hardware defect. The random reboot issue, where the GPU driver would leak memory and force a kernel panic, has been fixed since Android 4.3 in July. This includes the Chrome reboot issue. I've had 2 reboots over 13 months, and both were cause by a ROM issue. I assure you, there is nothing wrong with the Nexus 10. Try a 4.4.2 factory image and see if that solves anything.
Click to expand...
Click to collapse
I still get random re-boots in `safe mode` which is supposed to only allow apps installed with the system to run which leaves a bad 4.4.2 which could be checked by a re-flash of the factory image or faulty hardware.
I was planning to downgrade to 4.3 to see if that solved the re-boots but I might try a re-flash of 4.4.2 first to see if that works..
I'm not very confident about flashing and I've had the additional problem of working on windows 8.1 on my laptop.

I am running the factory image, 2nd one with same issues. I'm not necessarily disputing what you are saying but there were plenty of people telling me they had a perfect tablet when the memory leak wasn't fixed.
Sent from my XT1053 using Tapatalk

rxnelson said:
I am running the factory image, 2nd one with same issues. I'm not necessarily disputing what you are saying but there were plenty of people telling me they had a perfect tablet when the memory leak wasn't fixed.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
The memory leak was fixed but apparently, it's reappeared for me with the latest kitkat update. Quite frustrating, you'd think Google would be on top of these things. What's the point of fast updates if you're waiting months on end for a fix. If I don't powerdown my tablet when I'm finished using it I can guarantee a reboot during use. In the last 24hrs, it has rebooted on me twice while using Chrome. Quite irritating to be honest

It seems from previous posts that re-flashing 4.4.2 does not solve the reboots and I've not found a way to downgrade to 4.3 on Windows 8.1 to see if that works.
So I've tried another factory reset, but this time I've not allowed any non-Google apps to be installed other than the Photon browser which I need for flash Websites and the Re-boot logger app to record any reboots.
I'm using my Note 3 for the rest of my apps as that is still on 4.3 and doesn't have the reboot problem, but that might change after the KitKat upgrade.
I was getting at least 2 or 3 reboots a day so I should soon know if running 4.4.2 after a factory reset with just two 3rd party apps solves the problem and if so then that will suggest a rougue app. which I can reveal by re-installing the apps piecemeal.

I've just had another random reboot so I've done another factory reset but not signed in to Google so there have been no downloads and the only program I've run is Settings to increase the screen timeout to 30 - minutes.
If I still get random reboots then it is nothing to do with 3rd party apps or updates for I've not downloaded any.
That just leaves the hardware or the original 4.4.2 assuming the factory reset returns to that.

I didn't experience any reboots when not signed into google after a factory reset so I signed in and restored my tablet using Google backup.
I soon started to get reboots again, but I noticed that since the KitKat upgrade a website I use very often was sometimes automatically loading the Play store to try and get me to use their much inferier app. It doesn't happen on my Note 3 which is still on 4.3.
If I tried to close the Play store app to get back to the browser by swiping it away then it crashes and keeps trying to load over and over. If I hit the home button the Play store automatically re-appears still loading over and over, but after swiping it away several times it goes away or stops with an error message asking me to report the crash which I did and the browser is closed.
In order to fix this I disabled the Play store app so that it did not appear in my list of apps.and the website instead of loading the Play store app re-directed the browser to the Play store website which was better for I was still in the browser.
Since I stopped this particular website loading the Play store by removing it, I've just had one re-boot instead of several and my tablet is no longer overheating. I am a heavy user and have my tablet on many hours a day, so one re-boot is acceptable to me.
I've downloaded a Play store apk which I can install if needed but always remove it before using the website which tries to automatically load it.
It is a nuisance and I wish I'd stayed with 4.3, but I can live with the occaisional re-boot that might not be noticed if I only used my tablet lightly.
I'm annoyed that a website can automatically load the Playstore without me requesting it and that KitKat allows it.
I hope my experience helps others who are getting several re-boots a day.
PS
I did a factory reset then removed the Play store app before using the problem website so that it never loaded it in case that was needed.

Flashing the 4.3 factory image downgrades everything. For what it's worth, I noticed that the userdata partition is constructed differently than in 4.2.2(my last factory flash). That could have something to do with it. But also, I've been on custom ROMs since I got the tablet, yet I've never rebooted on 4.4.X. I guess try a vanillish ROM(like RastaKat) to see if that reboots.

Koopa777 said:
Flashing the 4.3 factory image downgrades everything. For what it's worth, I noticed that the userdata partition is constructed differently than in 4.2.2(my last factory flash). That could have something to do with it. But also, I've been on custom ROMs since I got the tablet, yet I've never rebooted on 4.4.X. I guess try a vanillish ROM(like RastaKat) to see if that reboots.
Click to expand...
Click to collapse
Now that I'm just getting one reboot a day and my tablet is running cooler I can live with that and I don't mind re-installing the Play store when needed for continuous updates can be a nuisance.

I finally managed to downgrade to 4.3 and I'm hoping that will solve all the problems I had with 4.4.2
But all seems well at the moment.
I'm not being booted from websites to the Play store, I can use the BBC iPlayer to download and run 1-hour videos and flash player works better.
Google has downloaded 4.4.2 (KitKat) but I'm not going to install it.

Stock Nexus 4 Boot Loop

Hi,
I am trying in vain to fix my friend's Nexus 4. She started having problems with a boot loop around the same time as 4.4.3 (I think) but it just went away. Two days ago it came back, possibly around the time of 4.4.4 seeding, however this time it won't go away. I have been looking at threads throughout XDA for help and tried this thread for help. I have a GS4 myself and very little experience with ADB/SDK.
All efforts have failed. As well as the boot loop issue, recovery is broken limiting my options. I tried the "not lose any data" method in the link above but this didn't work. Next the Nexus Root Toolkit, however most of the time the program fails as it says the download failed due to an MD5 mismatch. I have tried downloading the images directly from Google but still no luck - of all the 4.X images available only a couple will even allow me to try and install.
The first install didn't install, I noticed it mentioned the bootloader been locked several times - it recommended 'force flashing' providing I definitely have the right image. Several attempts later I managed to get the install working but it is still stuck on a boot loop (waited at least 15 minutes). Recovery is still broken. The only thing I have been able to do is unlock the bootloader.
So is there any hope? The device is pure stock, no alternative custom recovery or ROMs. Thanks.

I think half the problem is I can't the USB drivers installed properly as the device isn't showing in Device Manager. Without been able to turn on the phone or enable USB Debugging, it won't let me.
EDIT - I tried another toolkit and eventually managed to get 4.2.2 installed. I have just updated the phone to 4.3 but it's been on the Google X screen for a while now
EDIT 2 - Fixed the above. I needed to downgrade the radio. Updating to 4.4 - no doubt I will go through the same hurdles.
EDIT 3 - An error occurred during installation.

I think I softbricked, but only CM13 seems to fix on my N7. What did I do/how to fix

Guys,
I'm not even sure where to start with what I'm seeing, but maybe you can help me.
I have had Timur's ROM on my N7 2012 for a couple years. It's been crashing randomly, even though I have few things installed on it, and a good power supply. I took it out of my car and put it on an iPad 2 amp supply, and it still crashed a bunch so I knew I needed to wipe and reinstall. I also wanted to go from 4.2.2 to 5+, which I know takes away a lot of the good features I need (like power on/deep sleep).
I booted into TWRP and wiped my tablet, which appeared to softbrick it (I think I have the usage right from searching). I downloaded the Pure Nexus 6.0.1, CM13, and already had Autodroid ROMs to use. I tried to install Pure through ADB sideload, and got it installed. When I finished and tried to reboot, it said I had no OS. When I rebooted, I got the boot animation, and nothing else.
Long story short, I tried Autodroid and CM13, and using CM13 I got it back going. Unfortunately, every time I try to flash another ROM over it, it will no longer go past the boot screen. With CM13, it boots properly, but doesn't like the gapps pico I tried to install (error message when booted, keeps returning to the same pop up error).
I'm quite sure there's something I'm missing, but I don't know what it is.
Thanks!
Eric

Ok, before anyone goes nuclear on me, I think I better understand what happened. When I got ANYTHING to work, I stopped doing anything. As I understand, it wasn't functioning...it was just in a temporary mode of some sort.
After not being able to get it to work properly, I used this: http://forum.xda-developers.com/showthread.php?t=1781250 to try and restore the system. I followed all the directions, except for using the 5.1.1 version of the ROM, and used the corresponding file name for the zip file used.
After doing so, the bootloader won't go to TWRP, but goes to the pic as seen below. I did reboot the tablet, and after waiting quite a while, the tablet came on, but I don't understand what that picture means.
Thanks!
Eric

Ok...I realized that I lost root. I'm fixing it now. I had read before, but didn't understand what I saw.
Thanks,
Eric

Optimizing Apps on every boot.

I noticed a week or so ago that every time I reboot my Nexus 4, I have to sit through the optimizing apps every time. I have been going crazy searching for info on this and cant seem to find anything that helps. Phone is running 5.1.1, nothing custom, OTA update. I tried rolling back to 4.2 and everything seemed ok up until I got back to 5.1.1, then optimizing apps every boot again. I prefer Lollipop, but this constant half hour + delay before I can use the phone is unacceptable.
Any help would be appreciated, I really can't afford to buy another phone right now but this is driving me crazy trying to figure it out.

orangej said:
I noticed a week or so ago that every time I reboot my Nexus 4, I have to sit through the optimizing apps every time. I have been going crazy searching for info on this and cant seem to find anything that helps. Phone is running 5.1.1, nothing custom, OTA update. I tried rolling back to 4.2 and everything seemed ok up until I got back to 5.1.1, then optimizing apps every boot again. I prefer Lollipop, but this constant half hour + delay before I can use the phone is unacceptable.
Any help would be appreciated, I really can't afford to buy another phone right now but this is driving me crazy trying to figure it out.
Click to expand...
Click to collapse
I'm not an expert but I have some experience with my Nexus 4..
any root? SuperSu maybe?
You receive the 'Android is starting optimising app xx of xx'?
if you have SuperSu, install the last version...
Another cause may be some file in your internal storage, make a backup, delete all and restart 2 times to see if there is a change...
Last resort, flash the rom stock with nexus root toolkit with all wipe

I did use NRT to flash 4.2 back on and wiped it, then let it work its way through the upgrades again. Once it got back to 5.0+ the optimizing problem started. Phone was not rooted, just bootloader unlocked.
I flashed a custom rom based on Oreo on it and the problem stopped, so I am assuming this is a Lollipop problem, but I would really rather be able to run stock Lollipop on my phone.