Hi all.
I've recently bought a brand new Nexus S i9023, and it's awesome. Yesterday I tried to root it (unlocking bootloader and flashing ClockWorkMod recovery). But after flashing recovery, I noticed a LOT of stuck sub-pixels (they looked green). I don't know when exactly they appeared, maybe when I removed battery after a reboot, because the phone was on bootloader screen too long, I don't know why.
After that, I tried to re-lock bootloader again, and wipe the phone one more time, with no success.
Anyway, I left the device off all night long, and when I turn it on this morning the stuck sub-pixels was ALL disappeared !
I'm very confused.. is that possible?
EDIT
Ah-ah.. it seemed too good to be true.. Stuck pixels are still there. Maybe they had been there for days and I didn't notice them.
I'll return it back and probably I'll continue using my Nokia
Related
Why does my N7 seem to get stuck on the Google Splash screen constantly? I rebooted it earlier and it got stuck on the splash screen, now I can't even get it to boot up. It was running just fine, just having a problem with my works Wifi so I rebooted...
It has done this in the past a lot and the only way I was successful in getting it unstuck was by booting to bootloader and "fastboot reboot"
Am I the only one with this problem? I might have to take it back...
Your not the only one it happened to me a couple times if i recall. Sometimes it would just stay stuck on that google screen which I am really starting to dislike at the moment. starting to miss my boot animations on my atrix lol. But yea a hard reset or loading bootloader usually fixes it. Are you on custom rom? I was on Clean 1.1 before mines went dark.
So i updated my (not a year old) nexus 4 yesterday and today it died.
First off:
Ive never done any rooting, OCing or anything else fancy with my nexus, nor has anyone else.
Now, some time today the nexus got stuck in a bootloop, it was freshly recharged so it kept rebooting.
In the beginning full boots, after a while it got stuck at the 4 circles, later at the google logo, until now: completely dead, i suspect because of a drained battery.
I've been recharging the device for a few hours now, the red notification light keeps blinking and there's no hope for a (safe) reboot (yet)...
Any advice?
Do i keep charging it or is it a lost cause?
I'd rather not tinker with the device's internals, in case i would void the warranty.
Is your bootloader unlocked? Charge it up and then flash the factory image with fastboot.
Sent from my Nexus 5 using XDA Free mobile app
TehArch said:
So i updated my (not a year old) nexus 4 yesterday and today it died.
First off:
Ive never done any rooting, OCing or anything else fancy with my nexus, nor has anyone else.
Now, some time today the nexus got stuck in a bootloop, it was freshly recharged so it kept rebooting.
In the beginning full boots, after a while it got stuck at the 4 circles, later at the google logo, until now: completely dead, i suspect because of a drained battery.
I've been recharging the device for a few hours now, the red notification light keeps blinking and there's no hope for a (safe) reboot (yet)...
Any advice?
Do i keep charging it or is it a lost cause?
I'd rather not tinker with the device's internals, in case i would void the warranty.
Click to expand...
Click to collapse
My guess is that some files must have been corrupted during the update. Can you boot to fastboot mode (hold down both power and volume down)?.
My phone is acting similarly since yesterday. Stuck at bootloop even after reflashing the whole 4.4.3 factory image. Even recovery works fine, I just can't get past the boot animation :crying:
Eregoth said:
My phone is acting similarly since yesterday. Stuck at bootloop even after reflashing the whole 4.4.3 factory image. Even recovery works fine, I just can't get past the boot animation :crying:
Click to expand...
Click to collapse
have you tried wiping data/cache from stock recovery?
atulclassic said:
have you tried wiping data/cache from stock recovery?
Click to expand...
Click to collapse
this should solve ur problem !
Hey all,
Just some details before the background.
I was running a stock with a unlocked bootloader for a while now. I basically only use my nexus now to watch netflixs and HBOgo. Got the tablet over four years ago.
This morning after it's nightly charge I went to unlock it and it froze up. I rebooted it, noticed the date was off (Jan 1st) and froze after I unlocked it. Reboot again, it made it to the screen where it was optimizing my apps but the screen starting flickering and having artifacts, and powered off. Now it will power itself off 5 or so seconds into the boot animation.
I've tried going into recovery via the bootloader but when I select it and hit the power button it just turns it self off. I then used the nexus toolbox to reflash a stock rom (along with a factory reset), and TWRP. I tried booting up again and same thing. I then went into TWRP and start troubleshooting, but the screen is starting to flicker and have artifacts, then powers off.
Is the hardware dead on this?
Sorry for the jumbled mess of details, i've been bouncing around trying to troubleshoot/fix this.
PIT files
PIT files
My nexus 10 has the boot loop problem and I think I have been left with the only option of Re-Partition but I need the PIT file. Can anybody help or provide this file?
I have tried everything else (fastboot, adb, temporary custom recoveries, Nexus Root Toolkit) with no success.
Is the battery original? If so, it's possible the battery could be reaching its end.
Reddog090 said:
Hey all,
Just some details before the background.
I was running a stock with a unlocked bootloader for a while now. I basically only use my nexus now to watch netflixs and HBOgo. Got the tablet over four years ago.
This morning after it's nightly charge I went to unlock it and it froze up. I rebooted it, noticed the date was off (Jan 1st) and froze after I unlocked it. Reboot again, it made it to the screen where it was optimizing my apps but the screen starting flickering and having artifacts, and powered off. Now it will power itself off 5 or so seconds into the boot animation.
I've tried going into recovery via the bootloader but when I select it and hit the power button it just turns it self off. I then used the nexus toolbox to reflash a stock rom (along with a factory reset), and TWRP. I tried booting up again and same thing. I then went into TWRP and start troubleshooting, but the screen is starting to flicker and have artifacts, then powers off.
Is the hardware dead on this?
Sorry for the jumbled mess of details, i've been bouncing around trying to troubleshoot/fix this.
Click to expand...
Click to collapse
Hi All,
I've done a fair bit of Googling about this problem and I'm fairly certain my phones (hard) bricked, but I said I'd post just to make sure.
I have a Galaxy Note 4 N910F running a custom rom ( I cant remember which ROM, I think it was like Kyros Final Edition Note 5 Port or something) , I've been running it for a few months with no problem, last night I was uninstalling various apps from my phone, games etc... when my phone froze and turned off, when I turned it back on it was stuck in a bootloop, showing the galaxy note 4 screen vibrating twice and turning off and repeating.
I tried to boot into TWRP but it just froze on the Note 4 logo with "Warranty Bit Recover Set" or something along those lines at the top, when I took the battery out and put it back in, the phone would no longer turn on, nor will it charge, its completely dead.
I somehow managed to get it turned on again after a while, went into download mode and using Odin installed a stock rom, the install went fine however when the phone restarted after the install it said "booting to recovery" and ended up with a dead Android dude and a "no command message" , I got into recovery mode then and cleared the cache. Then I restarted the phone again and the same thing happened.
Now the phone wont turn on again, I've soft reset it, left it plugged in charging for a while and still nothing. Has anyone experienced something similar to my problem before? Any advice/help is much appreciated.
Thanks
Alan
Hi,
I picked up a second hand XT1622 super cheap the other day. It didn't seem to want to boot at first, and stuck around on the blue Motorola logo for a while, but eventually after leaving it alone for an hour or so it sprang into action.
Trouble was I then made the mistake of downloading the December OTA update, and since rebooting from that installation it's been stuck on the blue screen again.
I thought maybe something went wrong with the OTA, and flashed the December firmware through Fastboot hoping that would resurrect it, but I'm still getting the same result.
The bootloader is locked unfortunately, and I can't boot into recovery mode either - same issue.
Does anybody have suggestions other than me breaking the phone in half (which is probably going to happen today anyway)?
Phone suddenly sprang to life, but for some reason wouldn’t let me press return after entering my PIN after prompting for it in setup - maybe it’s a hardware issue and the phone’s on its way to the great G4 graveyard in the sky?
The original G destroys this nonsense of a phone.
For and download the stock firmware, and then flash it through fastboot. After that, see if it boots. If it does, unlock the bootloader so you will have b easier time if this happens again.