[Q] Screen Issues Lead To Bricked Device - Samsung Galaxy Nexus

I was trying out using a keyboard with a cheap USB OTG cable, and all was good. Then all of the sudden the screen went buggy, where ever other line of pixels was shifted to the left or the right, almost like some sort of corrupted video file. It started to reboot itself, and it got to the black screen with the Google logo and then the screen fuzzed in the same way as before. It then starts to reboot and does the same thing over and over again. I find that I can get to the recovery screen with the scroll arrows. From there, if I tell it to reboot into recovery it goes back into the same Google logo bootloop. I then went back to the original recovery screen and I decide to try out adb to see if it works. Sure enough it does, and I unwisely start flashing a stock 4.2 bootloader image. However, while it is flashing the screen does the same fuzz thing and and stays fuzzed. Then it doesn't respond to anything. I take out the battery, and try to restart and with will not turn on at all, no vibration, no light from the screen, nothing. I tried a unbricking methods from there, and nothing can make it come back alive. Any ideas?
Additional info:
GSM tajkju
Bootloader unlocked
Running stock unrooted 4.2 that I flashed manually
Stock recovery

Related

Stuck on Google Screen after JB Update

Hi,
I've attempted the JB update
http://forum.xda-developers.com/showthread.php?t=1737899..
fastboot flash boot boot.img etc.. which said all was well..
But now find that my phone will not boot up, doesn't get past the Google and unlock screen.
I've tried all combinations of volume buttons, I can get to the fasboot menu where I can choose either Recovery Mode, Power Off, Start or Restart bootloader.
None of these appear to do anything, recovery goes to the google a screen followed by an Android on it's back with an exclamation mark over it.. then goes to the Google and unlocked icon screen and stays there...
I fear my phone is bricked... Please help..
bevnet said:
Hi,
I've attempted the JB update
http://forum.xda-developers.com/showthread.php?t=1737899..
fastboot flash boot boot.img etc.. which said all was well..
But now find that my phone will not boot up, doesn't get past the Google and unlock screen.
I've tried all combinations of volume buttons, I can get to the fasboot menu where I can choose either Recovery Mode, Power Off, Start or Restart bootloader.
None of these appear to do anything, recovery goes to the google a screen followed by an Android on it's back with an exclamation mark over it.. then goes to the Google and unlocked icon screen and stays there...
I fear my phone is bricked... Please help..
Click to expand...
Click to collapse
1.) Your phone is far from bricked at all. You have access to the boot loader (i.e. the screen with the options). The recovery you're seeing is stock recovery. All you need to do is go into boot loader and fastboot flash recovername (CWM) and you will have your custom recovery back to wipe data and reinstall a rom or restore a nandroid backup
Mine is doing the same thing, weird thing is, it was working since yesterday on jellybean, it just randomly froze this morning and and now won't boot..
im currently at work so i don't have admin rights to do a fastboot flash..
any idea why it would randomly stop working when i havn't flashed anything on it besides the jb rom?
Sorted..
Thanks for the comments.. yeah i was over-reacting a bit there..
I downloaded the Galaxy Nexus Toolkit, got a stock rom form gopogle, flashed it.. back to normal, well, it will be after i restore the CWM backup i took.. phew..
Thanks again
Ian.
Still stuck
I'm also stuck in the same situation(google with the unlock screen). I fear I'm a little more stuck. I also can see the recovery/restartbootloader screen. However, everything I try still comes back to that same google screen and gets hung up. Need some help!
this has happened twice today and i think it from using volume+
Steelbully said:
I'm also stuck in the same situation(google with the unlock screen). I fear I'm a little more stuck. I also can see the recovery/restartbootloader screen. However, everything I try still comes back to that same google screen and gets hung up. Need some help!
Click to expand...
Click to collapse
Boot into recovery, wipe cache, Reboot

[Q] Blank screen, constant reboots, etc

Alright so I'm guessing i might have a broken flex cable, i don't know because of what is happening.
Don't even know where a good place to buy one.
But; first off, I don't use the phone anymore, it just its on my desk, sometimes I touch it, sometimes I don't.
When I was first getting the blank screen issue, the phone just had been sitting on my desk with the screen on (stay awake), several days later, the screen would be off and refused to come on.
Back then I was using a JB rom. Which I was told JB kernels had problems.
I can boot into fastboot and flash a new kernel and it doesn't change anything.
But now if I load up Flashtool, and boot the phone into flashmode, it will reset itself while flashtool is trying to read from it, then boot itself back into flashmode, then a few seconds later reboot itself again.
Last time I got the phone's display to come on, it was because I was able to use flashmode to flash to it before it rebooted itself.
If I try to boot the device, it will display a white LED for several seconds, then flash a few colors before going back to white and the phone resetting again.
Are these all symptoms of a broken flex cable? It makes no sense to me why fastboot mode is fine, but everything else constantly reboots.
I've tried different kernels and roms to make sure there wasn't a problem in that area.
Ellises said:
Alright so I'm guessing i might have a broken flex cable, i don't know because of what is happening.
Don't even know where a good place to buy one.
But; first off, I don't use the phone anymore, it just its on my desk, sometimes I touch it, sometimes I don't.
When I was first getting the blank screen issue, the phone just had been sitting on my desk with the screen on (stay awake), several days later, the screen would be off and refused to come on.
Back then I was using a JB rom. Which I was told JB kernels had problems.
I can boot into fastboot and flash a new kernel and it doesn't change anything.
But now if I load up Flashtool, and boot the phone into flashmode, it will reset itself while flashtool is trying to read from it, then boot itself back into flashmode, then a few seconds later reboot itself again.
Last time I got the phone's display to come on, it was because I was able to use flashmode to flash to it before it rebooted itself.
If I try to boot the device, it will display a white LED for several seconds, then flash a few colors before going back to white and the phone resetting again.
Are these all symptoms of a broken flex cable? It makes no sense to me why fastboot mode is fine, but everything else constantly reboots.
I've tried different kernels and roms to make sure there wasn't a problem in that area.
Click to expand...
Click to collapse
had that problem too. you have to enter CWM and flash any room that you can

[Q] I've made a huge mistake, flashed Verizon S3 kernel on ATT, phone will not boot

I tried flashing the Zeus kernel using CWM, but I failed to realize the kernel was for the Verizon S3. When I restarted after flashing, it displayed the Samsung logo for a split second and then went to a black screen. The screen was on, but it only showed black. At this point I passed out, and when I woke up it was still on the black screen. I pulled the battery and tried to restart, and got the same black screen. Then I tried every way I know of (except using a jig) to get into download mode to no avail. Now when I turn it on, it vibrates once, flashes the logo, and then the screen shuts off and is useless. I think there's a solid chance I've ruined it this time, but if anybody has any suggestions they would be greatly appreciated. Thanks!
Put the phone in dl mode. It's possible the screen will be black and you can't actually see it's in dl mode. Plug into your computer. Odin flash a stock Rom.
The fact that it's doing something means it is not completely ruined. It just may be harder to restore to working order.
Also, take a look at this thread
http://forum.xda-developers.com/showthread.php?t=1746665

Bricked T889 I think? It seems really bad.

I was playing pokemon go and I got a facebook messenger message, and my phone just crashed and started boot looping at the Galaxy note ii screen. I tried going into the recovery and deleting the cache and factory resetting it, tried flashing it with ODIN, and nothing seems to be fixing it. I've tried flashing it to the stock rom too, but that seemed to make things worse? Now half the time when I try and turn it on it it wont turn on unless I plug it in or remove and put back the battery, when I try charging it when it's off it turns on and I can see the battery screen, but it freezes either when loading or when the animation plays. There's no red light and I'm not even sure it's charging.
I can get to the CWM menu and the recovery menu, I did have the Nandroid backup files but it seems like I mistakenly deleted it, so that's an option. I tried flashing it with different firmwares and it doesn't seem to make a difference. The first time I flash it it usually goes to the T-Mobile splash screen, which plays the little animation and sound but stays at that screen. Any Ideas?
I tried reflashing it another few times and now I actually got into the setup screen and got to the home screen. It charges somewhat normally but it still boot loops when I start it. When I plug the charger in when it's looping it boots fully and I got to the point where I installed an update. Not I'm stuck in a loop on the T-mobile splash
Try a new battery.
Bell-wether said:
I was playing pokemon go and I got a facebook messenger message, and my phone just crashed and started boot looping at the Galaxy note ii screen. I tried going into the recovery and deleting the cache and factory resetting it, tried flashing it with ODIN, and nothing seems to be fixing it. I've tried flashing it to the stock rom too, but that seemed to make things worse? Now half the time when I try and turn it on it it wont turn on unless I plug it in or remove and put back the battery, when I try charging it when it's off it turns on and I can see the battery screen, but it freezes either when loading or when the animation plays. There's no red light and I'm not even sure it's charging.
I can get to the CWM menu and the recovery menu, I did have the Nandroid backup files but it seems like I mistakenly deleted it, so that's an option. I tried flashing it with different firmwares and it doesn't seem to make a difference. The first time I flash it it usually goes to the T-Mobile splash screen, which plays the little animation and sound but stays at that screen. Any Ideas?
Click to expand...
Click to collapse
Did you try Samsung Kies' emergency recovery option yet?

HW1 Huawei logo boot loop (no droid logo), fastboot flashing does nothing

Hello all!
I just want to make sure my watch actually is toast before I shed my final tears and move on.
Here's the situation. It worked fine up till a few weeks ago, then one night after it had completely died, I went to charge it and it was in a huawei logo boot loop. To be clear, I see the red logo for a few seconds, goes black, and repeat. I never see the android logo or anything like that. Every once in a while I can get it to show the low battery (the sliver battery, not the red X one). I CAN get into fastboot no problem. I tried doing factory reset from fastboot, same thing. I didn't have any custom imgs or anything on it, all stock OTA updates etc. So then I tried flashing probably 10 different images I found around the web including stock boot and recovery, twrp, etc etc (pretty much every img I could find). Nothing changes, as soon as I reboot after flashing, same red logo bootloop.
I'm guessing it's a weird hardware issue, or _maybe_ my last hope was just my charger is bad all of a sudden (getting another one just to see).
Any other thoughts? I did take it all apart, check connections etc, everything looked fine. Put it back together and same behavior.
Thanks for any help!
Update: A new charger did not help. I'm convinced it's something hardware related. I might pick up a few broken ones on ebay and mess with building a full working one. I'll update again if I get something to work.

Categories

Resources