Hey everyone! I just wondered if there was anyone out there still messing with their Nexus Q’s! I Just tried to install CM11 on my Nexus Q and it failed on installing CWM. Then it wouldn’t load and only showed a black screen with the spinning Blue LED’s. Tried to install an older recovery but same result. Tried to factory reset but only get spinning blue LED’s and a bootloop in logcat. Did I brick it or is there hope? Willing to pay to help me through this haha!!
Figured it out!
If you’re having this issue too the easiest thing to do is start over by flashing a factory reset. You can get the image from https://developers.google.com/android/images and scroll down to Nexus Q. They have good instructions on the page as well. From there, I followed this guide exactly https://forum.xda-developers.com/showthread.php?t=2408799
The issue I was having with the black screen was solved by changing my monitor I was using to troubleshoot. CWM on Nexus Q has a different input timing than a regular boot of the Q so it just doesn’t work with some TV’s and monitors for some reason. So if you get the black screen issue don’t be afraid to try several monitors or even [email protected] http://droid-at-screen.org/
Now that it is running I have no issues. Chances are you didn’t brick your device.
Saisai
Related
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!
Hey guys!
I'm in deep **** over here, my Nexus 4 is completely ****ed. Basically, I was trying to flash clockworkmod via TWRP when some weird things began to happen. Whenever the phone booted, it acted as if there was no free storage - gallery wouldn't work, it wouldn't connect to my carrier - etc.
So I decided to go back to stock via fastboot. I've flashed all the images now, but something strage is happening in that the phone just won't boot. Once I turn it on, it just says at a grey screen .
I've tried flashing the factory bootloader on top, but this wont work either - fastboot says 'invalid bootloader img'.
So now I have a problem. I can either RMA this phone for one of its previous problems, or I can try to fix it. If anyone can help me, that would be much appreciated. BTW - I am on a mac. Thanks for any help,
Kartik
Flash the ENTIRE factory image from Google (see efrant's guide if you don't know how to do this, but tbh you should know what you're doing before trying to mod your phone). If it still doesn't work then return it
Hi All,
I've searched across forum to find also similar cases, but no results so far.
I have a N4 with TWRP and CM (previously running 10.1.2)
Today I decided to install the new 10.2.
Installation went fine but after the restart I've noticed some strange behaviour with some applications (missing from phone, but installed for my play store account)
I've decided to reboot again the phone, and since that time I'm stuck with the black start up Google screen (the one with the lock at the bottom).
Entered recovery mode, I've wiped Dalvik, Cache and System, but no results, rebooting is always stuck on Google screen (I've also left it there for 15+ minutes, no changes)
I've tried to install a previous ROM (zip available on phone storage) but no result even in this case.
Any help or suggestion would be much appreciated, even a link pointing to similar case happened in the past.
Let me know if any further detail may be needed to better understand the situation
Thanks!
mh a wipe/factory reset should be working...
Try pushing a different rom with ADB to your device, then flash it.
Sent from my Nexus 4 with Tapatalk 4
This is usually happening when you don't flash something right. I'd go back, flash it all again with wiping everything and flashing it by the right order and stuff. If it doesn't work, as written above, flash other ROM through ADB or something similar.
Besides, you could always restore your nandroid backup, and if you don't have one, learn from your mistake
Good luck
Sent from my Nexus 4 using xda app-developers app
To be honest, I've already tried to revert back to previous CM and even to the factory image from Google, but it always hang on the google screen.
I've not yet Format/completely wiped the phone, and that's my last option.
Once I'm done with the manual backup I'm doing via adb shell, I will try again to flash a new ROM, and see what happen.
Definitely I'm learning from my mistakes
Hi Everyone
First post on this forum and first time trying to fool around with android.
I just replaced a new lcd + touch+ frame to an N4 its build was JOP40C
1) I said to myself why not trying to update manually to lollipop, well the N4 stayed stuck while booting with the colored dots.
2) I said to myself lets go back to JOP40c but that does not exist on google anymore so tried for hours many until JDQ39 and finally could get into my phone, but the number 6 and 7 where missing on the touch (???).
3) I said to myself well lets reinstall again and got totally my touch working.
4) Once done I received automatically an OTA from google, said to myself well lets do google, well the same happened again the phone was kind in a bootloop with the colored X.
Any help would be appreciated on why I am not able to update this phone, do I miss something that I should know and not found over all what I have read over the internet.
I have spent at least 3 working days on this and now I have to go back, make a living and hope that a pro will help.
I assume you're flashing the factory image and then you get a bootloop? Go into the stock recovery after flashing and do a factory reset.
Sent from my Nexus 5 using XDA Free mobile app
Tried that too lots of post over the internet about that but nothing keep getting blocked on the colored cross or bowls.
Tried also with Nexus Root Toolkit
Just received again the google update to 4.3 jelly beans on the N4 pressed restart and install then got the green robot and saying installing system update.
Then the phone got stuck in his bootloop and tird again the factory reset.
Still stays stuck in its bootloop.
invitro59 said:
Tried that too lots of post over the internet about that but nothing keep getting blocked on the colored cross or bowls.
Tried also with Nexus Root Toolkit
Just received again the google update to 4.3 jelly beans on the N4 pressed restart and install then got the green robot and saying installing system update.
Then the phone got stuck in his bootloop and tird again the factory reset.
Still stays stuck in its bootloop.
Click to expand...
Click to collapse
Try checking the SkipSoft.net Android Tool Kit
I hope that helps
You ever check all sensors work?
Maybe the same problems with this http://forum.xda-developers.com/nexus-4/help/issue-sensors-update-t2973047#post60470486
HI
I have checked with another N4, installed a software and checked the differences.
Well you are wright on this one the luminosity and proximity sensors are not showing any sign of life.
It is already past midnight here in France, so I will check tomorrow if I can do something on these sensors.
Will keep you posted if I can fix the sensors and do an update after that.
Hi
How stupid I am, after screen change connector sensor was not pluged in and since I had placed the plastic cover with the screws, could not see it anymore.
At least after have lost so much time, next time I will post a little earlier and at least tonight I will go bed less stupid than yesterday
Google just send the 4.3 upgrade and everything went smooth just no touch anymore so cannot use the phone.
ok installed lollipop but still the same no touch, but now I can install an update but not use the phone.
Anyone on that touch problem
Hi guys,
I have Vava Chroma UST projector and I was trying to adjust colors with Projectivy Launcher app and in After sale menu, ive clikced on Switch to factory test. Now each time I reboot I get that screen first. Also after I messed this up Ive cliked on one more test and now that one is showing on boot as well .
Can anyone please help me with advice on how to disable those test modes.
I tried with factory reset, tried to clear the cache of those system apps but they still show on boot.
the os is broken, you should replace the device
mikimile said:
Hi guys,
I have Vava Chroma UST projector and I was trying to adjust colors with Projectivy Launcher app and in After sale menu, ive clikced on Switch to factory test. Now each time I reboot I get that screen first. Also after I messed this up Ive cliked on one more test and now that one is showing on boot as well .
Can anyone please help me with advice on how to disable those test modes.
I tried with factory reset, tried to clear the cache of those system apps but they still show on boot.
Click to expand...
Click to collapse
Were you ever able to figure out a solution to this? I find myself in a similar situation and their tech support is next to useless. They just tell you to wait so they can send the issue over to their engineers and never end up getting back to you.