Hey guys.
I've been using my 5x for the past 6 months. So, today I installed the new version of Pure nexus which was released yesterday by the developer. After the update was installed, my phone's screen started have red and white lines.
I flashed back to stock but the problem still exists.
The phone hadn't fallen down or anything.
Any solutions?
Thanks in advance
Fang Leone said:
Hey guys.
I've been using my 5x for the past 6 months. So, today I installed the new version of Pure nexus which was released yesterday by the developer. After the update was installed, my phone's screen started have red and white lines.
I flashed back to stock but the problem still exists.
The phone hadn't fallen down or anything.
Any solutions?
Thanks in advance
Click to expand...
Click to collapse
yeah i have the same problem as well bro! someone, anyone please aid us in this predicament =/
I've started having this problem too.
Just curious what steps you guys take to flash back to stock.
Do you download stock from
https://developers.google.com/android/nexus/images#bullhead
Do you do a factory reset after flashing stock in stock recovery?
Sent from my Nexus 5X using XDA-Developers mobile app
Commodore 64 said:
Just curious what steps you guys take to flash back to stock.
Do you download stock from
https://developers.google.com/android/nexus/images#bullhead
Do you do a factory reset after flashing stock in stock recovery?
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
I wish I had this on my 5x reason want to get the screen replaced as it has scratches all over the glass dues to a fall.
Sent from my GT-I9500 using Tapatalk
Commodore 64 said:
Just curious what steps you guys take to flash back to stock.
Do you download stock from
https://developers.google.com/android/nexus/images#bullhead
Do you do a factory reset after flashing stock in stock recovery?
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
yeah i actually did do all of that, mine seems to be gone somewhat now, i installed the n preview then went back to marshmallow and flashed it 2x and then it seemed to be fixed now, didnt have the issue since.
Commodore 64 said:
Just curious what steps you guys take to flash back to stock.
Do you download stock from
https://developers.google.com/android/nexus/images#bullhead
Do you do a factory reset after flashing stock in stock recovery?
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
also when you flash it would it really be necessary to factory reset the phone? i mean doesn't it already factory reset it when you flash it with the factory images ? so why would i need to go and factory reset it again ? doesn't make sense
shakdeboss said:
also when you flash it would it really be necessary to factory reset the phone? i mean doesn't it already factory reset it when you flash it with the factory images ? so why would i need to go and factory reset it again ? doesn't make sense
Click to expand...
Click to collapse
I'm pretty sure it's not a necessity but just good practice. Sometimes the installation leaves some junk behind so it's not a bad idea to clean up after a ROM flash.
Sent from my Nexus 5X using XDA-Developers mobile app
Do you have screen glitch even in bootloader?
freq_ency said:
Do you have screen glitch even in bootloader?
Click to expand...
Click to collapse
nah, bootloader pretty much only thing without the glitchy behavior, however mine which i thought to be fixed i got a pretty surprise when i opened my camera and took a pic, it just had the line glitch and phone went off. its strange tho that whenever this happens i have to keep holding the power button and vol down button to enter bootloader to turn it back on from there. like, i have had to hold those buttons around 10+ times before it decides to boot into bootloader, so something is messing with it.
shakdeboss said:
nah, bootloader pretty much only thing without the glitchy behavior, however mine which i thought to be fixed i got a pretty surprise when i opened my camera and took a pic, it just had the line glitch and phone went off. its strange tho that whenever this happens i have to keep holding the power button and vol down button to enter bootloader to turn it back on from there. like, i have had to hold those buttons around 10+ times before it decides to boot into bootloader, so something is messing with it.
Click to expand...
Click to collapse
May be flashing stock images might help. Using TWRP erase all. Then from bootloader flash factory image. If you are fine ith screen then reflash twrp then PN.
freq_ency said:
May be flashing stock images might help. Using TWRP erase all. Then from bootloader flash factory image. If you are fine ith screen then reflash twrp then PN.
Click to expand...
Click to collapse
tried that, however when i had tried to reboot into bootloader it didnt and i had to do it manually a few times before it picked it up flash stock, then i was saying it was all good then it started to boot and glitched out at the boot
Related
I decided to install Cyanogen Mod on my Nexus. I already rooted it and downloaded rom manager + titanium back-up. I watched a tutorial on how to download and install roms using rom manager and everything seemed to go as planned and Cyanogen 9 was installed. The phone automatically rebooted and the boot animation the Cyanogen started. But after a half hour I realized it was stuck. So I tried to go into recovery mode to restore my backup (of the stock) but when I went there, the phone automatically turn off. It's not when I click, it's just after a certain period. It even turned off while restoring. To make things worse, when I turn it on now, it's stuck on the Google logo with the unlocked slot at the bottom. I hope you guys can help me because I'm starting to freak out.
Addidional info:
Additional info
I did not delete evreything when I flashed
GSM version
rom was downloaded from rom manager
I backed up my stock rom
I did google but everything leads to bootloader which is broken
Yes I'm a noob
marcusabu said:
I decided to install Cyanogen Mod on my Nexus. I already rooted it and downloaded rom manager + titanium back-up. I watched a tutorial on how to download and install roms using rom manager and everything seemed to go as planned and Cyanogen 9 was installed. The phone automatically rebooted and the boot animation the Cyanogen started. But after a half hour I realized it was stuck. So I tried to go into recovery mode to restore my backup (of the stock) but when I went there, the phone automatically turn off. It's not when I click, it's just after a certain period. It even turned off while restoring. To make things worse, when I turn it on now, it's stuck on the Google logo with the unlocked slot at the bottom. I hope you guys can help me because I'm starting to freak out.
Addidional info:
Additional info
I did not delete evreything when I flashed
GSM version
rom was downloaded from rom manager
I backed up my stock rom
I did google but everything leads to bootloader which is broken
Yes I'm a noob
Click to expand...
Click to collapse
Is your battery charged? Have you tried reflashing recovery? if not I'd try reflashing recovery, not sure what it might be hope this helps
jv2543 said:
Is your battery charged? Have you tried reflashing recovery? if not I'd try reflashing recovery, not sure what it might be hope this helps
Click to expand...
Click to collapse
Where can I find this option and what does it do exactly? I have the Nexus Toolkit too, should I do anything there?
1.Don't panic
2. Try to go on bootloader then reset factory or fastboot then from pc flash recovery
3. Try to get back recovery then factory reset and flash backup
Sent from my HTC One V using Tapatalk 2
OP, here. Learn before you do some damage with tools you don't understand.
I mean, it's the easiest thing to fix damnit if you cared to learn in the first place...
Beamed from Maguro
Odin back to stock
Sent from my Galaxy Nexus using xda app-developers app
gagb1967 said:
Odin back to stock
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I wouldn't recommend Odin to beginners. OP is better off with the fastboot guide mentioned by bk201doesntexist.
When I was a noob, Odin was the thing that save my life... a while back of course
Sent from my Galaxy Nexus using xda app-developers app
gagb1967 said:
When I was a noob, Odin was the thing that save my life... a while back of course
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
was it a nexus? maybe/probably not, but if it was, you should have used fastboot. it's officially supported by GOOGLE. if you want to flash a factory image, they tell you to use fastboot. why would we use anything else? a leak? that the community barely really knows anything about?
i'd rather use Heimdall!! (not sure i9250 is supported though.)
Sent from my i9250
So this is kind of a unique issue i'm having. I have the I-747 on AT&T and flashed AOKP rom (it was taking too long to get JB). It worked for about 3 days and then got stuck in the android boot screen (used the rom feature to get rid of the pink unicorns). after that, I booted into recovery and reset my phone, and it worked again for a few more days, then it wouldnt boot again (I dont believe I changed any settings between the boots). After this time, it wouldnt let me boot into recovery and would only boot to the android start screen and stop. I used odin to flash the stock rom, which only took me to the 2nd samsung boot screen and stopped (after the AT&T splash shows up). I looked online and saw someone say try CF-root using odin, tried that and it didnt help. Then tried using a custom kernel siyah s3, and now it will only show the initial samsung splash screen before turning off again. Any suggestions here? I figured I'd stop researching since i dont want to really mess up my phone worse than it already is
mrneilix said:
So this is kind of a unique issue i'm having. I have the I-747 on AT&T and flashed AOKP rom (it was taking too long to get JB). It worked for about 3 days and then got stuck in the android boot screen (used the rom feature to get rid of the pink unicorns). after that, I booted into recovery and reset my phone, and it worked again for a few more days, then it wouldnt boot again (I dont believe I changed any settings between the boots). After this time, it wouldnt let me boot into recovery and would only boot to the android start screen and stop. I used odin to flash the stock rom, which only took me to the 2nd samsung boot screen and stopped (after the AT&T splash shows up). I looked online and saw someone say try CF-root using odin, tried that and it didnt help. Then tried using a custom kernel siyah s3, and now it will only show the initial samsung splash screen before turning off again. Any suggestions here? I figured I'd stop researching since i dont want to really mess up my phone worse than it already is
Click to expand...
Click to collapse
I have a similar issue, someone please help
Your main issue now is that you flashed siyah. We don't have one. If you can get to download mode, you will want to flash back to stock.
Sent from my SGH-I747 using xda premium
As DeathSdoor said...flash stock.
Sent from my SAMSUNG-SGH-I747
d3athsd00r said:
Your main issue now is that you flashed siyah. We don't have one. If you can get to download mode, you will want to flash back to stock.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks guys! So I used odin to flash the stock boot loader and stock rom, but it is still hanging up on the 2nd samsung screen like it initially did (the one after the AT&T boot animation). Any other ideas on what could be the cause?
How long is the hang? Sure is just not the 1st initial boot of the new rom?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
How long is the hang? Sure is just not the 1st initial boot of the new rom?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
The first boot can take as long as 5 minutes sometimes. So, if you haven't waited that long, then try out some patience. Otherwise, try booting into recovery (stock now) and factory reset.
Sent from my SGH-I747 using xda premium
bump!
I have this same issue. I have restored to stock rom and it does the Samsung boot, then AT&T, then it goes to Samsung pulsating with a blue pulsating LED.
I have left it in that mode for at least 15 minutes and it never boots.
I can still get into download mode.
Thanks in advance for any help!
Has anyone tried booting into recovery after flashing the stock ROM and wiping caches then rebooting?
jethro650 said:
Has anyone tried booting into recovery after flashing the stock ROM and wiping caches then rebooting?
Click to expand...
Click to collapse
I let it run for 2 hours (left the house came back and i was still on. And phone wont boot into recovery at all ( i tried many times, but it just boots normally and skips recovery until it gets to the 2nd samsung screen, then stops there).
I dont know if this is relevant, but while the phone is off and plugged in, i can still see the battery meter and the Green LED (so i'm guessing it's still working, it just wont boot)
mrneilix said:
And phone wont boot into recovery at all ( i tried many times, but it just boots normally and skips recovery until it gets to the 2nd samsung screen, then stops there).
Click to expand...
Click to collapse
Same here!!!
jethro650 said:
Has anyone tried booting into recovery after flashing the stock ROM and wiping caches then rebooting?
Click to expand...
Click to collapse
As Jethro said clean everything and factory format in recovery. Your just not doing the buttons right to get in to recovery
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
As Jethro said clean everything and factory format in recovery. Your just not doing the buttons right to get in to recovery
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I went into recovery many times before, I'm definitely hitting the buttons right but it still wont go into recovery, it just tries booting like normal. I can go into download mode easily, but that's it.
jbizz, did you start getting this error after flashing AOKP rom also? trying to figure out what could have caused the issue in the first place
I'm not really skilled on these things, but I once had a similar issue with my phone not booting and had to end up using Kies to emergency restore it. Odin wouldn't recognize my phone but kies would.
Although I think my issue with odin may be stemming from my computers usb ports...
Sent from my SGH-I747 using XDA Premium HD app
I actually flashed a bad kernel and the phone wouldn't boot after that.
What is the proper way to boot into Stock Recovery?
Sent from my SAMSUNG-SGH-I777 using xda premium
Fixed it! What I did was go into Kies software and did a firmware upgrade instead of trying to flash from odin, then put it in download mode instead of recovery, but it still worked. Thanks for all the help, guys! guess it's time to move to a CM based rom?
mrneilix said:
Fixed it! What I did was go into Kies software and did a firmware upgrade instead of trying to flash from odin, then put it in download mode instead of recovery, but it still worked. Thanks for all the help, guys! guess it's time to move to a CM based rom?
Click to expand...
Click to collapse
Thats bad badassness! I will try that when I get home!
Sent from my SAMSUNG-SGH-I777 using xda premium
mrneilix:
Please give me step by step what you did! Kies is being a bastard!
Sent from my SAMSUNG-SGH-I777 using xda premium
jbizz said:
mrneilix:
Please give me step by step what you did! Kies is being a bastard!
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Sure, I'm doing this largely from memory since I mostly figured it out by throwing stuff at the wall to see what sticks.
Open Kies->tools->firmware upgrade and initialization->enter model name then serial number (they're behind the battery) -> put the phone in download mode and plug it in. it should take care of the rest.
Fair warning, this will fully wipe your phone, i lost all my pics (thank you google+'s instant upload or i'd be PISSED) and titanium backup (there goes my 3 stars on every level in angry birds and great scores in temple run), but at least you get a phone that can function as more than a paper weight, right?
mrneilix:
You're my new best friend and I don't even know you!!!
Thanks for the help, you're a legend!
Sent from my SAMSUNG-SGH-I747 using xda premium
PLEASE TAKE THE TIME TO READ, THANK YOU.
Hello,
I am a Galaxy Nexus user, non rooted, running Android version 4.3. Yesterday I was running 4.2.2 and everything was fine and running as normal. Keep in mind I never rooted my phone, although I have to others in the past. My Nexus was running pure official 4.2.2. I had been waiting for the 4.3 update and was extremely excited when I was the notification that it was ready for my phone. I quickly downloaded it and then it rebooted the phone, as any update should. That's where everything went downhill. The phone started to lag immediately when I turned it on. It was sputtering and jerking but I just thought it was getting used to the update. Then the phone would loose its onscreen buttons and turn the page that I was looking at full screen (meaning I couldn't press home or back, because they simply just weren't there). Then the phone froze all together and after waiting 20 minutes I finally took the battery out and tried again. The EXACT same thing has been happening ever since yesterday and it has made the phone unusable because it will freeze 5 minutes into turning it on. And we then screen times out, the screen will not turn back on, as if the phone was off, when it is not. I'm very frustrated because the phone was working flawlessly before the update and now I have to use my retired G1 because the phone is that unresponsive. I was just hoping someone could please help me, or has a similar story and could make this known to Google. Thank you for reading, please if you can, help me.
Justin
Wipe cache and dalvik cacheand flash stock factory images through fastboot
Then flash the latest root files superSU 1.45 and then everything will be okay again.
Carlos_Manuel said:
Wipe cache and dalvik cacheand flash stock factory images through fastboot
Then flash the latest root files superSU 1.45 and then everything will be okay again.
Click to expand...
Click to collapse
Did you even read the post? He's never rooted and 100% stock.
Sdobron said:
Did you even read the post? He's never rooted and 100% stock.
Click to expand...
Click to collapse
Whoops. Sorry I read that quickly... Anyway flashing JB 4.3 factory images should fix that...
His systemui .apk is force closing.. Reflash if ur gonna root .. Or wie data... Best method root and flash.. Seems to be a very simple fix..
ferozfero said:
His systemui .apk is force closing.. Reflash if ur gonna root .. Or wie data... Best method root and flash.. Seems to be a very simple fix..
Click to expand...
Click to collapse
Since he didn't root his Galaxy Nexus, this method should make him lose all apps data or even internal storage since he has to unlock his bootloader for root.
But it seems to be the only method.
It's time for a full wipe.
Sent from my Nexus 4 using Tapatalk 4 Beta
I had exactly the same problem so I did factory reset from phone settings 2 days ago and now is just like a new phone working great.
There are just too many changes google did in ~6 months so full wipe is necessary.
Sent from my Galaxy Nexus using xda app-developers app
Here is my advice: use Nexus toolkit from the development section. Perform the unlock and then flash the factory image. Download it before to start. I always do that way with the new updates. Wipe ewerything. It's worth it.
Sent from my Galaxy Nexus using xda premium
teddy_irish said:
Here is my advice: use Nexus toolkit from the development section. Perform the unlock and then flash the factory image. Download it before to start. I always do that way with the new updates. Wipe ewerything. It's worth it.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Please don't use a toolkit.
Just use fastboot commands.
Beauenheim said:
Please don't use a toolkit.
Just use fastboot commands.
Click to expand...
Click to collapse
Right, and it's safe.
Please backup all your data before you do it.
I was using the Cyanogenmod that recently went out to the Google Play market. I decided to go back to stock and tried to do a Firmware recovery in Samsung Kies. It all seemed to go fine but when it's time to start up I just hang on the Samsung logo.
I've been trying to fix it and even used Odin to flash a stock ROM (latest release from November 19th) which was successful, but I am still not having any luck getting the phone to start. It's just hanging every time I restart.
Does anybody have any idea what I'm doing wrong? I hate to be such a noob but I could really use a few pointers.
Thanks so much
Do a factory reset in recovery
Sent from my SGH-T999 using Tapatalk
serio22 said:
Do a factory reset in recovery
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I don't have the stock recovery or I can't access it I think. When I hold the Vol Down + Home and power it on I get the screen that says to hit Vol Up to continue. When I do that I don't have any options, just the "Downloading" screen. It also says "Odin Mode" at the top
jonno.n said:
I don't have the stock recovery or I can't access it I think. When I hold the Vol Down + Home and power it on I get the screen that says to hit Vol Up to continue. When I do that I don't have any options, just the "Downloading" screen. It also says "Odin Mode" at the top
Click to expand...
Click to collapse
ah I see my own error. I need to use Vol Up + Home to get recovery. Trying out the suggestion now. Will report. Thank you so much for responding
jonno.n said:
ah I see my own error. I need to use Vol Up + Home to get recovery. Trying out the suggestion now. Will report. Thank you so much for responding
Click to expand...
Click to collapse
Factory Reset didn't work.
The last thing I flashed using Odin was this: T999UVUEMJC_T999TMBEMJC_TMB
Not sure if that makes any difference.
jonno.n said:
Factory Reset didn't work.
The last thing I flashed using Odin was this: T999UVUEMJC_T999TMBEMJC_TMB
Not sure if that makes any difference.
Click to expand...
Click to collapse
OMG after a very long boot it finally worked. Thank you so so so so much! I really was sad I bricked my phone!!!
Yeah that first boot can sometimes take a while, nice to see you got it working
Sent from my SGH-T999 using Tapatalk
serio22 said:
Yeah that first boot can sometimes take a while, nice to see you got it working
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Any time you do a factory reset or flash a new ROM it may take 5 to 10 minutes, and this is pretty standard. The reason why is it is booting deodexed instead of odexed I believe. The distinction is clarified in the link below.
Please see "Deodex is Slower, Then Why Bother?":
http://www.redmondpie.com/odexed-vs-deodexed-the-difference-between-the-two-android-roms-explained/
Everyone started out a noob here. The difference is that some of them persisted. Keep up the tinkering :good:.
Hi,
suddenly one morning my phone in continuously rebooting. it's alive for around 10 sec and then again reboots.
What all i tried:
1. Flashing custom recovery
--- flashing successful but after then when i goto custom recovery it goes to stock recovery. (Tried TWRP 2.5, and 2.7 also CWM recovery) same result with any recovery
I have flashed recvery various times but it ain't working this time
2. Tried flashing factory image
--got stuck while flashing system.img
tried twice, then pulled the cable and removed the battery and rebootted,still having same old android, seems erasing system and flashing system
never happened.
3. Tried hard reset from stock recovery
-- reset completed sucessfully
-nothing changed, everything same as before as if reset even didn't work.
Dunno whats wrong with this phone, Someone please help ????
Sorry to be the one to bring bad news. But your emmc chip died.
Means your going to need to look for a new phone.
Sorry.
Sent from my Galaxy Nexus using XDA Free mobile app
Thymo said:
Sorry to be the one to bring bad news. But your emmc chip died.
Means your going to need to look for a new phone.
Sorry.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for atleast letting me know :'(
IS there anyway to confirm this?
can it be replaced cheaply?
Is it worth going for replacement??
dk_india_world said:
Thanks for atleast letting me know :'(
IS there anyway to confirm this?
can it be replaced cheaply?
Is it worth going for replacement??
Click to expand...
Click to collapse
You can try to lock the boot loader. If its unlocked on reboot you know for sure.. A replacement is not worth it unless you can find an extremely cheap mobo..
Sent from my Galaxy Nexus using XDA Free mobile app
Mine does that when I over heat it but is fine if I let it cool down
Sent from my Galaxy Nexus using XDA Free mobile app