Develop Bugs

[Q] Can't start my Galaxy Nexus

Hi evereybody.
I have a GSM galaxy nexus with 4.2.2. Since approximately a month ago the phone started to reboot itself randomly. Sometimes when I was surfing the web, other times when the phone was on standby at night. Well, since the reboots were becoming more frequent I decided to do a factory reset, because I assumed that it was a corrupt application file or something like that. One week into the factory reset it started restarting again by itself, maybe 2 times a day. I searched the web, couldn't find anything useful so I told myself that the 4.3 update should solve the problem (naive me).
Today the update popped and I intermediately installed it. What is my surprise, that in the middle of installation I get the droid icon down on his back and an ERROR message. Rebooted the phone pulling out the battery and now the phone won't pass the multicolored X screen.
I have no unlocked bootloader, and the phone isn't rooted. So I tried to do a factory reset with the default recovery mode the galaxy nexus has. I wiped the phone but I get stuck on the same screen. The funny thing is that every time I try to wipe the caché partition the phone reboots itself immediately.
I don't know what to do. I'm not an advance user, I installed the GNEX TOOLKIT and tried to flash the factory image, but seems like I don't have the USB DEBUGGING option enabled and can't complete the process.
Do I need to send my phone back? (i'm still in warranty) Or is there a way to be able to start my Gnex again?
Thanks in advance.

monwentworth said:
Hi evereybody.
I have a GSM galaxy nexus with 4.2.2. Since approximately a month ago the phone started to reboot itself randomly. Sometimes when I was surfing the web, other times when the phone was on standby at night. Well, since the reboots were becoming more frequent I decided to do a factory reset, because I assumed that it was a corrupt application file or something like that. One week into the factory reset it started restarting again by itself, maybe 2 times a day. I searched the web, couldn't find anything useful so I told myself that the 4.3 update should solve the problem (naive me).
Today the update popped and I intermediately installed it. What is my surprise, that in the middle of installation I get the droid icon down on his back and an ERROR message. Rebooted the phone pulling out the battery and now the phone won't pass the multicolored X screen.
I have no unlocked bootloader, and the phone isn't rooted. So I tried to do a factory reset with the default recovery mode the galaxy nexus has. I wiped the phone but I get stuck on the same screen. The funny thing is that every time I try to wipe the caché partition the phone reboots itself immediately.
I don't know what to do. I'm not an advance user, I installed the GNEX TOOLKIT and tried to flash the factory image, but seems like I don't have the USB DEBUGGING option enabled and can't complete the process.
Do I need to send my phone back? (i'm still in warranty) Or is there a way to be able to start my Gnex again?
Thanks in advance.
Click to expand...
Click to collapse
Try using Odin http://forum.xda-developers.com/showthread.php?t=2065470

dexviajiboy said:
Try using Odin http://forum.xda-developers.com/showthread.php?t=2065470
Click to expand...
Click to collapse
Thank You very much!!! It worked like a charm and it was super fast.
Seriously thanks!

monwentworth said:
Thank You very much!!! It worked like a charm and it was super fast.
Seriously thanks!
Click to expand...
Click to collapse
no problem...

Nexus 7 Bricked suddenly!! Stucks on Google's logo

hi all, this is my first post, I will try to be synthetic...
I've got a nexus 7 2013, then, two month ago, I've unlocked the bootloader and rooted the tablet, and it was running without problem.
This morning, the touch screen wasn't working, so I reboot the tablet holding the power button and...
Surprise!
the tablet stucks on the Google logo....
So I've search on the internet, I've perform the unroot and relock the bootloader, I've reinstalled the factory image with the Wug's tool, and manually too... nothing.. still stuck on the google logo... I can't even go in recovery....I've tried all, I've installed a different version too...
Please help me... I don't know whatelse I can do....

Nothing against Wug, but what if you tried flashing the factory images manually? (Be sure to unlock the bootloader first.)
https://developers.google.com/android/nexus/images

gm0906 said:
hi all, this is my first post, I will try to be synthetic...
I've got a nexus 7 2013, then, two month ago, I've unlocked the bootloader and rooted the tablet, and it was running without problem.
This morning, the touch screen wasn't working, so I reboot the tablet holding the power button and...
Surprise!
the tablet stucks on the Google logo....
So I've search on the internet, I've perform the unroot and relock the bootloader, I've reinstalled the factory image with the Wug's tool, and manually too... nothing.. still stuck on the google logo... I can't even go in recovery....I've tried all, I've installed a different version too...
Please help me... I don't know whatelse I can do....
Click to expand...
Click to collapse
I bad contact from the ribbon cable can do this as well. You may need to open it up & make sure the ribbon cable is secure & making good contact. There is a thread & a guide on it, pretty easy & you don't need any tools, nor do you break any warranty seals.

GSLEON3 said:
I bad contact from the ribbon cable can do this as well. You may need to open it up & make sure the ribbon cable is secure & making good contact. There is a thread & a guide on it, pretty easy & you don't need any tools, nor do you break any warranty seals.
Click to expand...
Click to collapse
Yes I was worry on this.... So it's an hardware problem... This morning he trolled me, the touch had worked for few seconds, the time to scroll in the languages and it block again :S
I will search the tread you was spoke about

[Q] Wont go past google logo UGH

ok long story short...i was playing on my tablet and i got a notification saying that i needed to update to the new lollipop so in the middle of the install it says there is an error and shuts off. i try to turn it on and it doesnt go past the google logo. i read online and someone said try pushing the volume down button and the power button until a screen pops up...i did that and it doesnt matter which option i choose it takes me back to the google screen. ive called everyone including google to see if a tech support person could help me and there has been no luck with out having to pay for it....the google guy said what probably happened is that ive wiped the OS off the tablet. and i was wondering if there is a way to fix this. ive downloaded the root tool kit but am pretty much lost when it comes to something that percise. the tablet is fully charged but its almost like my computer wont reconize it when i plug it in to do anything with it.. HELP

Goofygirl0928 said:
ok long story short...i was playing on my tablet and i got a notification saying that i needed to update to the new lollipop so in the middle of the install it says there is an error and shuts off. i try to turn it on and it doesnt go past the google logo. i read online and someone said try pushing the volume down button and the power button until a screen pops up...i did that and it doesnt matter which option i choose it takes me back to the google screen. ive called everyone including google to see if a tech support person could help me and there has been no luck with out having to pay for it....the google guy said what probably happened is that ive wiped the OS off the tablet. and i was wondering if there is a way to fix this. ive downloaded the root tool kit but am pretty much lost when it comes to something that percise. the tablet is fully charged but its almost like my computer wont reconize it when i plug it in to do anything with it.. HELP
Click to expand...
Click to collapse
If you'd searched a bit, you'd have found out that it means your motherboard is screwed, and the only solution is to replace it. But if you have to pay for it, don't let Asus cash in on their deliberate scam - knowingly putting out a buggy update that potentially bricks their device, then turn around and solicit repairs at ridiculous prices. They break it, they should fix it. The point is that they don't even know what or why and thus choose to dodge responsibility by insinuating it's your fault.

Similar thing here. I was sending a text late at night. Sent it and put it down. Next morning tablet was stuck on Google logo and nothing seems to fix it. Tried adb commands to restore. WugFresh Toolkit failed. Disappointed with both Google and Asus.

losmolinos1098 said:
Similar thing here. I was sending a text late at night. Sent it and put it down. Next morning tablet was stuck on Google logo and nothing seems to fix it. Tried adb commands to restore. WugFresh Toolkit failed. Disappointed with both Google and Asus.
Click to expand...
Click to collapse
I have the same problem.
I updated from Kit Kat to Stock Lollipop and the device worked fine then today when I turned it on it would not boot past Google Splash. Will not boot into recovery. I can get into Fastboot mode but my attempts to flash a stock 5.0.2 from google have failed. I have a Nexus 7 2013 wifi Model "Razor" and flashing it in fast boot is not resolving the issue. Just boots to "Google" and stays. From what I have found this is very common on a 5.0.2 update and needs a RMA? is that correct?
FASTBOOT MODE
PRODUCT NAME - flo
VARIANT - flo 16G
HW Version - rev_e
BOOTLOADER VERSION - FLO-04.04
CARRIER INFO - None
SERIAL NUMBER - XXXXXXX(Filtered out)
SIGNING - yes
SECURE BOOT - enabled
LOCK STAT - unlocked
Thanks,

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!

Galaxy A50 bootlooping

my phone was working normally and all of a sudden I came back to my room and it only displayed the galaxy a50 starting screen (the one before there is just "samsung" written).
Restarting it didn't help and it always gets stuck at the same display or restarts endlessly. Sometimes it makes it until the "samsung" display.
Firstly, I don't really know why it rebooted anyway and the problem started. There is a software update I should have been doing for quite some time, so maybe that got executed automatically (is that even possible?) and failed?
What I already tried:
Charging (100% charged)
Went into recovery mode and:
repaired apps (didn't help)
powered off and restarted after 20 minutes of being turned off (didn't help)
Run graphics/ locale test (didn't help, the graphics test said something about deleting so I got afraid and restarted it. Could I have lost some data because of that?)
click on mount/system (as far as I can tell nothing happened)
wiped cache partition (didn't help)
clicked reboot to bootloader (what does that do? There was written downloading but then I got scared and restarted the phone, could that have done some damage?)
Rebooted (nothing happened)
downloaded drphone, phone does not get recognized
As you might see, I'm a bit desperate and although being quite tech savvy I don't know that much about android.
What is most important to me is recovering/ not deleting the data on my phone (last backup is about one month old so not too bad but still very bad for me) so please suggest safe options first in that regard (if there are any).
Can I maybe just update the software via ADB without damaging my data?
Or use ODIN for that? Also heard something about TWRP. Don't really know how any of these three work exactly (but totally willing to learn how!)
Your help would mean the world to me

the deleting part in the graphics test is just texts it does nothing. i dunno if the usb debugging is enabled, but if it is get alternative boot partition (saved my pixel 4 like that). i used linageOS 20 recovery mode that got me to os i backed up my files and then reflashed.

KirinPixel said:
the deleting part in the graphics test is just texts it does nothing. i dunno if the usb debugging is enabled, but if it is get alternative boot partition (saved my pixel 4 like that). i used linageOS 20 recovery mode that got me to os i backed up my files and then reflashed.
Click to expand...
Click to collapse
Thanks very much for your reply! I found out quite a bit by now and it seems to me after intensely studying this thread https://forum.xda-developers.com/t/...ce-is-stuck-on-boot-loop.4536965/page-2#posts only reinstalling the software (most likely with ODIN) is the way to get back to the phone working properly. You don't know anything about that, maybe? I'm very afraid to do it wrong and wipe my data.
Can I just reinstall the already installed software version? Or should I go higher?
I restarted it once though and even put in my PIN but after the home screen appeared it fell back into the bootloop again.

I have no experiance with samsung odin. But what i say is you bring it to someone who does to back ya fils up. Then go play with flashing. Odin is far from the only way. Unfortunately i can not assist you on it because i never used it. Good luck!