My phone is looping (on and off) during the boot sequence. The boot screen (red green yellow) says code error then goes to the update screen. It starts to flash and then shuts off for a couple of minutes and does the same sequence again. I was running Nedidum v4 and activated the lock screen. Every since then I cant boot to this rom nor can I flash the stock sprint rom. Is my phone bricked? If i take it to sprint can they tell I was running a cooked rom? Note: I reported my touch pro lost through assurion to get this tp2. Can I do it again? Helpppppppppppppp!!!!!
Related
i flashed the new deepshinning 9x about a week ago, and it was fine for a while, but in the last few days i noticed it began to slow down, and this morning i tried to reset it but it won't turn back on, it hangs at the boot logo can anybody please help, i need it for tonite
You mean you are at the boot logo or stuck at the bootloader?
If you are stuck at the boot logo try a hard reset. If that doesn't work try flashing a new rom.
the boot logo, and i couldn't flash anything else cause the phone wouldn't come on, but i did a restore, now i'm finna get this deep shinning completely off, i'm done with deep shining, any ideas on a better rom? i thought about tryin energy
im stuck at the tp2 logo atm, it makes it to tp2 then restarts. im not turning it on and cant keep it turned off.
i cant get into the boot loader (vol down on start) because it closes after about a minute in the loader
i'd love to task29 the whole damn thing but i cant get access to it via usb >.>
what can i do?
Just happened this morning, while using my non-rooted stock gsm gn. All of a sudden it turned off and rebooted, but can't get past the google screen... it goes back to black screen then google screen... pls help!
This happened to me aswell, like three hours ago.
A full battery load during night and then I used it for navigating to a customer, sent a SMS. When I check the phone later the white led is flashing to tell me I got a new notification.
But the phone won't wake up, so I pull the battery and now it is stuck at the Google logo, it never comes to the boot animation. It is freezing with the Google logo and it can't be turned off.--- without pulling the battery
I'm running OTA update 4.0.2 the phone is not rooted.
Still stuck!
This I have tried to no avail:
Via fastboot unlock the bootloader, hangs.
Via Odin reinstall image (ICL53F), hangs (aborted after 10 minutes of waiting)
Odin hangs at "NAND Write Start!!"
To me it seems like I've lost the flashmemory...
If no other solutions is recommended I guess I have to return the device... GAAH!
Also tried:
Code:
fastboot -w
Went for lunch and came back, but that command aslo hanged.
Update
Update.
My Galaxy Nexus is now running again, after a motherboard replacement done at a Samsung serviceshop.
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
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
Hello all,
My phone randomly got stuck in a boot loop (crashing after the black and white galaxy s3 splash screen) last night and is now on its last leg. I'm on stock ATT firmware; I had messed around with rooting a few months back but restored.
Now the phone will crash before entering recovery mode. I can get into Download mode and connect the phone to ODIN, but it will crash before it can begin rewriting the firmware. The phone just won't stay on for longer than ~20 seconds (I've tried with two different batteries). All I can figure is that there is a hardware power issue, but do you all have any ideas? If not, I fear I'll have to buy a new phone.
PS: I initially believed the power button was stuck and opened the phone up to make sure that wasn't the case, it was fine.