Develop Bugs

[Q] Galaxy Nexus black screen of death

Basically, this: http://forum.xda-developers.com/showthread.php?t=1384415
No one responded to that thread because it was in the wrong forum.
I got the "Phone -- ! -- PC" screen, and was attempting to fix it before getting this black screen of death.
Galaxy Nexus GSM
Rooted, Codename ROM, don't think there is a Kernel in there
Carrier: Virgin Mobile
Edit: I won't be able to respond for a couple hours as I'm going to work. Any and all help is much appreciated.
Original post from above thread below:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse

What i with my little (almost nothing experience in android) would do its going to another computer with no drivers installed, would download the toolkit and install those drivers, then plug the phone and see what happen, im sure its not bricked since the computer recognice it.. I did lot of stuff with blackberry and there was a lot of ways to recover a phone like that... From here if the toolkit recognice it in any way.. Then you could try to do some of those steps.. As far as i tried doing all kind of stuff to my phone, toolkit its for much the Best Tool and way to do anything to your phone or at least for starters like me
Sent from my Galaxy Nexus using xda premium

But the computer doesn't actually recognize it. The "detection" sound it makes is for an unresponsive device. It won't charge, won't be recognized, and no matter what combo I use, it doesn't turn it.
I played dumb, called Samsung, and now I'm going to send it in. Thanks for the help though.

sometimes my screen goes blank and I have to pull the battery and everything comes back to normal

Phone Dead After Recent OTA Update

Hi All,
First of all I'm not a native english speaker and I'm a noob in this stuff o rom's .
I recently bought a phone and on update it to JB 4.1.1 with Sense 4+ . Everything went ok and the phone apparently was working ok.
The next day I just noticed that the bluetooth was not 100% because I had some cuts in the sound when connected to a bluetooth headset. Because of this I looked for another OTA update and it found one that said somethink like "General System Improvement" or something like that.
I've installed it but this update didn't went till the end since I get stucked on the "red sign" indicating some fail. I try to reboot the phone but apparently he was dead.
After a lots of tries and key combinations I was able to enter the boot mode and choose to restore to factory mode, but apparently it was not successful. Then I tried and option to check for CRC of img files I think (not sure because don't remeber). It check for 3 images files showing the CRC code, then I think the phone get stucked on one because I still have the waiting message but nothing else happens.
I pressed power button again trying to reboot the phone but since then then phone died completly. The only sign of life is when I connect to the PC windows emits the sound of detecting something but gives an error related to the drives.
Sometimes I get a message saying that a ARX device was found but not anymore.
Tried almost everything that I could read on this forum but nothing seems to work...I think the phone is looping on the boot or doesn't have any battery...not sure.
I've tried some RRU but they fail to find the phone saying not connected or not detected.
Any help will be greatly appreciated, Thanks
Johny

Sent it back for warranty repair as soon as you can this is a known fault as it happened to me recently.
Similar problems: http://forum.xda-developers.com/showthread.php?t=2075862
Getting out of APX mode

Your bootloader isn't locked right? Or were you ever rooted? If the answer is no, just send it to HTC and your warranty will do the rest.
Sent from my HTC One X using xda app-developers app

[Q] Nexuz 7 stuck at the google logo

Hello I need a but of help my Nexus 7 is showing my nothing but the google logo and at the store earlier it showed the android with his chest up and a red triangle. it doesnt even show the moving colors after i turn it on it just sits and says google like a paper weight. i can turn it off and on but nothing more. the geek squad at best buy told me to ask for help here at Xda. last thing i was doing with it was opening deer hunter 2013 and next i go to see if it opened and it stuck on the google logo. can anyone help me fix my tablet? its not under store warranty only manufactures.

Well, sucks to be you.....just kidding...but that does suck. Now, on to more serious matters...
Do you have access to your bootloader? (hold the power button + the vol up button at the same time) If you do, you might want to look into rooting the tablet. Based on the content of your post, I am assuming that you haven't. There is plenty information about rooting the Nexus 7.2 tablet (and just about every other Android device). Simply Google "root Nexus 7 2013" and you will quickly find your answer.
Also, how much do you know about rooting and the sort? I want to know before I waste my time giving details about info that you are aware of.

aarsyl said:
Well, sucks to be you.....just kidding...but that does suck. Now, on to more serious matters...
Do you have access to your bootloader? (hold the power button + the vol up button at the same time) If you do, you might want to look into rooting the tablet. Based on the content of your post, I am assuming that you haven't. There is plenty information about rooting the Nexus 7.2 tablet (and just about every other Android device). Simply Google "root Nexus 7 2013" and you will quickly find your answer.
Also, how much do you know about rooting and the sort? I want to know before I waste my time giving details about info that you are aware of.
Click to expand...
Click to collapse
i dont know anything about rooting. i dont have access to the boot loader. i did a few days ago now it wont even show up, the guy and best buy tried to bring it up and its like it was showing a dead android or something chest open with a red triangle above it. he said someting about maybe have to flash a new or or something like that on to it, it wont show me anything just stays off or shows the google logo when its on

Sigh...that is the bootloader. Maybe...he could have booted into the stock recovery, which shows this or something similar for most devices. Please remember, they are reps...they may know about the software, but usually they speak from their experience or their perspective. I'm glad that he sent you here for a second opinion.
Hold the volume down button and power button to get into the bootloader. You should see some options at the top of the screen saying Start, Restart bootloader, Recovery Mode, Power Off. Not sure if those are the exact options, but it's pretty close.
Also, you need to look into rooting your device. You need to download some files first. You'll need adb, fastboot, and drivers for your Nexus.
And one last thing....what Computer OS do you use? The rooting process is slightly different for each one (Windows 7, 8/8.1, Mac OS, & Linux). If you are into computers, and you have Linux installed on a device, good for you. That is my preference when rooting, as Android is built from Linux, and naturally supported without the need for drivers.

I had similar problems when I first bought it. Going into recovery and resetting the tablet cured it. You will lost all your data BTW.

He's facing the loss of his entire tablet, so I'm sure that data loss isn't the biggest thing to worry about.
But yes, just about every solution involves a clean wipe of data.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________

I'm stuck on the google logo too. I had my tablet plugged in over night and when I opened the cover this morning it woke up, but as soon I tried to access anything it rebooted and stuck.
I'm unlocked and have tried various thing. NRT doesn't recognize it as an ADB device so I don't think that will work. Fastboot works, but I keep getting "FAILED (remote: flash write failure)" when I try to use the factory flash all, or the instructions found here: http://forum.xda-developers.com/showthread.php?t=2381582
I can use fastboot to query the device and get it to return "flo" but it seems like the flash storage has failed.
if it's truly horked, can I use "fastboot oem lock" to relock it and attempt a warranty replacement?

sean67854 said:
I'm stuck on the google logo too. I had my tablet plugged in over night and when I opened the cover this morning it woke up, but as soon I tried to access anything it rebooted and stuck.
I'm unlocked and have tried various thing. NRT doesn't recognize it as an ADB device so I don't think that will work. Fastboot works, but I keep getting "FAILED (remote: flash write failure)" when I try to use the factory flash all, or the instructions found here: http://forum.xda-developers.com/showthread.php?t=2381582
I can use fastboot to query the device and get it to return "flo" but it seems like the flash storage has failed.
if it's truly horked, can I use "fastboot oem lock" to relock it and attempt a warranty replacement?
Click to expand...
Click to collapse
You can try Method 2 from this post: http://forum.xda-developers.com/showthread.php?t=2513701
I know it's for the N5, but I used this one for both my Galaxy Nexus, N5 and N7. Since they are all Nexuses (Nexi?), the same general procedures apply. I always prefer to do it all manually, step-by-step, which is why I went with Method 2 in the OP of that thread. Obviously, since this is the N7, just skip the radio flashing command. Everything else is the pretty much exactly the same. If this doesn't work in fastboot, then it's probably a hardware failure.

Emergency Assistance Required!!! - Phone Bricked?

All,
I was having issues flashing nightlies of CM 12.1, I was getting assert errors and forced reboots, so I did my research and found I needed to flash the Sprint MB1 to MD4 bootloader as instructed in order to get rid of these errors. Flashing with CWM, again as instructed, it said the flash was successful, and to reboot. I hit reboot and now the phone does not even power on, no logo, no battery charging indicator, no vibrate, no nothing. Only thing it does is make my computer tell me a device has been connected. What can I do? I need this fixed yesterday! I do not have a spare phone on hand to use, my M9 is out for repair for over a week. School starts Monday, I have job applications floating around with my cell # on them. This is a big problem.
I have an unknown device in Device Manager called QHUSB_DLOAD. I know this is the phone, and, in theory, should be able to do something with it. But what?

I have an 8 or a 32GB SD card available to use to try to force the phone into download mode, but I see a lot of people saying you need a 16. Can't afford one.
Edit: It really is looking like it needs a JTAG, I don't believe i have all of the supplies required for this so... yeah...

Touch Screen not working at all

Device is fine and can be used via bluetooth mouse / keyboard - however, touchscreen went completly dead
formatted it - changed image, same result
anyone have any idea how to fix it , like a link to a video - part needed - or even a UK store
thanks

I have a similar issue.
I've had my Pixel C for around 11 Months, purchased direct from the google store in November 2017.
Last week I opened the tablet and the screen was totally unresponsive. The physical buttons were working so after several forced reboots which did not help I went for the Nuclear option and restored the device to factory defaults. This didn't work either and I was still unable to interact with the screen so logged a call with Google. I was about to invoke the warranty when suddenly the device responded again after a further reboot. I agreed with the support person that I would keep it for the time being, hoping it was just a glitch
Unfortunately the problem has recurred twice again and the only way to recover seems to be to power the device off, leave it for a "while" and power on.. not exactly scientific.
Has anyone else experienced similar issues? The device received a security update mid last week so I wonder if this is more than coincidence.
Any road, in this state the device is completely unreliable so I'll be looking to return it. I'm assuming google will not have any new replacements so I need to find an alternative android tablet

touch screen pixel c unreliable
owens2000 said:
I have a similar issue.
Has anyone else experienced similar issues? The device received a security update mid last week so I wonder if this is more than coincidence.
Any road, in this state the device is completely unreliable so I'll be looking to return it. I'm assuming google will not have any new replacements so I need to find an alternative android tablet
Click to expand...
Click to collapse
Same for me. The touchscreen is unresponsive, thought it would be hardware damaged, but did a couple of restarts, and all of a sudden I was able to type ten letters, then unresponsive again. Were you able to resolve this issue? Thanks!

after the last few updates the screen would respond less and less. This last update last night killed the screen completely. Zero response! I honestly think this is an error on their part but even if they fixed it in an update I cant get in to install the update!
I wanted to root and install a custom rom to see if that would fix it but honestly Ive been out of the loop for so long and without going into dev mode Im not sure I can at all.

tevil said:
I wanted to root and install a custom rom to see if that would fix it but honestly Ive been out of the loop for so long and without going into dev mode Im not sure I can at all.
Click to expand...
Click to collapse
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks

milgrave said:
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
Click to expand...
Click to collapse
Im working on trying to unlock the bootloader right now. I tried the toolkit but its giving me a syntax error on trying to flash in fastboot since thats the only thing I can get to. Whats crazy is even the android recovery option is corrupt and this is a stock tablet. I really think google did this to these devices on purpose or unintentionally but has no intention on fixing them. I couldnt even run the update any since there is no way for me to get to anything.
Im looking for instructions on how to do everything from fastboot and ADB but everything is so outdated.

milgrave said:
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
Click to expand...
Click to collapse
Hey sorry to post twice but try these. I just tried these steps and got my tablet fully wiped (do caches first) and working. Im enabling USB debugging and bootloader unlock and doing it all now. This was proven to be a google update issue to me.
Perform a master reset
https://thedroidguy.com/2019/08/how...3-xl-touchscreen-not-responding-issue-1094388
To factory reset your Google Pixel 3 XL:
Turn off your Google Pixel 3 XL.
Press and hold the Power+Volume Down buttons until bootloader mode (image of an Android with Start above it) appears, then release.
Select Recovery mode. You can use the Volume buttons to cycle through the available options and the Power button to select. The device will flash the Google start screen momentarily and then restarts in Recovery mode.
If presented with an image of a broken Android with “No Command” printed on the screen, press and hold the Power button. Press the Volume Up button once. Then release the Power button.
From the Android Recovery screen, select Wipe data/factory reset.
Select Yes. Wait for several minutes for the factory data reset process to complete.
Select Reboot system now. Allow several minutes for the factory data reset and reboot processes to complete.
Set the phone up again.
from there I just now used wugfreshs tool kit to unlock the bootloader and Im going to install TWRP and probably a custom rom to avoid updating again.
Update: def a software issue. I worked fine with this tablet for a few hours. Installed 1 app then it locked again. Opera browser. I've had my suspicions of the app for a while which is why I tested this app first. I'm using those same steps again to wipe and seeing if the touchscreen works again. I had trouble getting twrp and a room loaded due to encryption. There is apparently a decrypt file you need to install recovery and root. I can't seem to locate the correct one but wugs toolbox sees the device fine once the drivers are installed.
Ill keep this running and updated with results.
Full wipe and reset again and the screens not working again. What stinks is I once again can't get it into dev mode. I guess maybe it is a hardware issue. Sad, this thing has always been in a case and babied. I still think tho it's a bug with newer releases and the hardware in certain C's. It's beyond warranty though so what can we say to Google at this point. It's not even an old tablet and was pretty pricey. My Nexus 9 still runs perfectly!