Develop Bugs

[Q] Screen flickering / Bootloop -> Is my Nexus dead? Data recovery possible?

Hello,
just some hours ago my Galaxy Nexus (SC-04D) rebooted while lying on the table next to me. After several sings of vibration I noticed that the phone doesn't boot completely.
When switching on the phone I get the turn-on-vibration, then the google letters are displayed. Most times the word "google" flickers from left to right over the screen (only the line where the word is supposed to be). Sometimes it boots further and I get the colored "X" displayed. This symbol starts flickering, too and if it went so far it reboots.
Here are two pictures I took from the phone failing to boot:
picpaste.com/img_0001_01-Rmm7kDYb.jpg
picpaste.com/img_0001-eoLqVoiM.jpg
The phone is running stock Android from Docomo. The phone is about 14 months old and has never been unlocked, rooted, modded, taken a bath, ... 'til now.
I tried starting with and without SIM-card, with and without charger attached and let it lie around for several minutes without battery between my tries.
Is there any chance to get my data from the phone or even get it fixed? Please give me a hint what I can do.

Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix. This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery

Thanks GPFboy for your fast response,
GPFboyJS said:
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix.
Click to expand...
Click to collapse
As far as I understand a factory reset results in a complete loss of data on the phone, right? So without root/unlock there's no chance to get my data from the phone? That would be really bad.
GPFboyJS said:
This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
Click to expand...
Click to collapse
What is "too many"? I think there are about 35 apps installed atm. By the moment the problem arose wifi and 3g-data,BT,GPS were disabled and just a minute before I took a look how late it was. So nothing special.
GPFboyJS said:
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Click to expand...
Click to collapse
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?

BrainSD said:
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
Click to expand...
Click to collapse
thats stock recovery.
is your bootloader already unlocked or no?

Zepius said:
is your bootloader already unlocked or no?
Click to expand...
Click to collapse
It's still locked.

you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.

Zepius said:
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Click to expand...
Click to collapse
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?

BrainSD said:
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
Click to expand...
Click to collapse
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.

beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Well if I was him I would be more worried about my expensive phone instead of data. Maybe a lesson for later to have a backup
Sent from my Galaxy Nexus using XDA Premium HD app

beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Yes exactly this is the point. Since I don't have a current data backup the first thing to try is getting my data from the phone. I already tried temporary loading the clockwork recovery through fastboot - with the galaxy nexus toolkit and by hand(sdk) - but it failed ("Bootloader locked").
What I'm wondering about is the fact that the phone seems to behave normally in odin and fastbood mode but going nuts the moment it's expected to boot. Besides the flickering google logo and the "matrix-modded" dead android it even ended up in a totally green screen one time.
At the moment I don't dare trying to unlock/flash the phone because of being afraid getting stuck and ending up with the phone being in some kind of undefined / totally broken state. Initially I was in hope of being able to rescue my data but now i will try my luck with docomo support first.
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
I will try to get through 1 to 4 of the guide first and see how far I get.
If this won't work I might try to unlock, recover and try to "undelete" what's possible. (http://forum.xda-developers.com/showthread.php?t=1994705)
Does this order make sense?
Btw, having a dead phone is bad, of course, even when I got it new for 2300Yen but loosing some pictures i really liked and having no phone atm currently hurts more. Especially when knowing that I was thinking of copying all photos to my computer only one day before when I pulled only some minor important ones from the phone I needed for work and planned to do a full backup and unlock this weekend when I get back my 'Milestone' currently lent to someone else.
Once again something I learned. Backup! Even you phone.

BrainSD said:
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
Click to expand...
Click to collapse
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.
It will unlock your bootloader, bypassing fastboot. Still, it's not for the faint hearted. I refered to omapflash because its a low level tool, it doesn't require the bootloader to be unlocked, and is able to restore the bootloader to working state, and I got there because you mentioned you see graphical glitches/flickering which may indicate bootloader partition failure and/or consequent corruption.
I think that's your best shot at trying to get your data back. After unlock, boot to fastboot and 'fastboot boot custom_recovery.img', and grab your stuff (if you can) from /data/.

beekay201 said:
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.....
Click to expand...
Click to collapse
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems

BrainSD said:
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
Click to expand...
Click to collapse
Great, so far so good.
Yeah, they're ext4 images, but sparse images i believe - link

[Q] Unresponsive Screen + Bootloop

I brought my phone in to have the charger port replaced. It worked fine ad then all of a sudden the phone boots up, stays booted for a minute and then reboots. also the screen is unresponsive.
I have used a gnex kit to get into CWM and erase cache and dalvik cache and fix permission and the problem is not resolved.
with out the gnex kit i can't even get into CWM and all i get is a little droid guy with an open stomach hatch with a red mark.
i would erase all data and factory reset as a last option but i have some work photos on the device that are extremely important for me to extract. I should also mention that with the CWM kit I am unable to find the files I wish to pull yet for the few seconds I am able to boot into android my photos are there in the album.
can someone please help me find a way to extract those files so I can try to wipe the device and move on?

cardozanick said:
I brought my phone in to have the charger port replaced. It worked fine ad then all of a sudden the phone boots up, stays booted for a minute and then reboots. also the screen is unresponsive.
I have used a gnex kit to get into CWM and erase cache and dalvik cache and fix permission and the problem is not resolved.
with out the gnex kit i can't even get into CWM and all i get is a little droid guy with an open stomach hatch with a red mark.
i would erase all data and factory reset as a last option but i have some work photos on the device that are extremely important for me to extract. I should also mention that with the CWM kit I am unable to find the files I wish to pull yet for the few seconds I am able to boot into android my photos are there in the album.
can someone please help me find a way to extract those files so I can try to wipe the device and move on?
Click to expand...
Click to collapse
With factory reset your sdcard will not be touched. You will have all your files (unless youre in stock recovery I think). You can use adb pull /sdcard/ to get all youre files.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
With factory reset your sdcard will not be touched. You will have all your files (unless youre in stock recovery I think). You can use adb pull /sdcard/ to get all youre files.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
so what you're saying is if I boot into CWM with the kit, do a factory reset, all my photos will be there? can you please elaborate?

cardozanick said:
so what you're saying is if I boot into CWM with the kit, do a factory reset, all my photos will be there? can you please elaborate?
Click to expand...
Click to collapse
Yes that is correct. You can wipe everything as long as you dont wipe /sdcard. I am not a 100% sure since you are on stock but I know sure for 99%. Google is your friend
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
Yes that is correct. You can wipe everything as long as you dont wipe /sdcard. I am not a 100% sure since you are on stock but I know sure for 99%. Google is your friend
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Alright,
alright, we have 50% success!
I was able to get all the files off that I was looking to get, albeit during 20 second intervals in which the phone would allow me to before rebooting....
which brings me to my next point - Phone is stuck in bootloop after following (successfully) this guide to flash stock and unroot which, needless to say, seems strange to me.
Now I supposedly have a fully formatted i9250 maguro with a fresh flash of stock running and i'm stuck in a boot loop which if i leave sitting long enough will eventually get to the "Welcome" [choose your language] screen with an unresponsive display panel until it reboots after about 30 seconds.
please help.
EDIT: I flashed the Factory Image Android 4.2.2 (JDQ39) and still stuck in bootloop with unresponsive screen. maybe this is better as a paperweight??

cardozanick said:
Alright,
alright, we have 50% success!
I was able to get all the files off that I was looking to get, albeit during 20 second intervals in which the phone would allow me to before rebooting....
which brings me to my next point - Phone is stuck in bootloop after following (successfully) this guide to flash stock and unroot which, needless to say, seems strange to me.
Now I supposedly have a fully formatted i9250 maguro with a fresh flash of stock running and i'm stuck in a boot loop which if i leave sitting long enough will eventually get to the "Welcome" [choose your language] screen with an unresponsive display panel until it reboots after about 30 seconds.
please help.
EDIT: I flashed the Factory Image Android 4.2.2 (JDQ39) and still stuck in bootloop with unresponsive screen. maybe this is better as a paperweight??
Click to expand...
Click to collapse
Thats strange. But you have your files and you are on completely stock unrooted. If you still have warranty you can send it back. Maybe you can try this: http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop
Sent from my Galaxy Nexus using XDA Premium HD app

Strange Fix reveals deeper issue
good news and bad news
Alright, so I have swapped the motherboard with an old gnex i had laying around that has a broken screen that wouldn't turn on at all..
I found out that the motherboard on the old phone must be dead because it won't work in the newer phone so I put the guts of the newer on into the broken screen phone and it worked perfectly - albeit with a huge crack in it. so i then thought maybe the issue was solved and put the guts that worked back into the original phone and it is unresponsive and reboots... I've come to the conclusion that the screen is the issue on that device.
but is this fixable??? i have taken the whole thing apart and can't see how that screen could be shorting the device and cause it to reboot nor can i understand why it wouldn't be responsive to the touch for no reason.
anybody have a clue how i can fix that?

[Q] Maguro rebooting radomly

Dear community,
i have a reboot problem with my gnex gsm for several weeks now. The phone seems to be rebooting randomly after freezing. The only situation where no reboot occurs is when it is attached to the pc via usb docking station in developer mode.
Ususally, i had cyanogenmod nightlies installed, but i also tried stock 4.2.2 and 4.3 images. Moreover i tried several full wipes using cwm and twp recovery. After the last wipe, I did not recover anything using titanium backup. At the moment i am running on 4.3 stock image and stock recovery with no root. Bootloader is still unlocked. The phone keeps rebooting...
Has anybody an idea where to locate the problem (probably some certain log files) ?

My GNex had that problem. It started with random reboots. Then got into a boot loop from which it never recovered.
Good luck. Hope you don't have the same fate that I had.
Try flashing back to stock and lock and unlock bootloader. If that doesn't stop the reboots, IMO, time to look for a new phone.
Edit : You might want to send it to Samsung for repair, if you are still under warranty.
Sent from my Micromax A116 using Tapatalk 2

Check battery connections, replace battery
Update us later

viskon said:
My GNex had that problem. It started with random reboots. Then got into a boot loop from which it never recovered.
Good luck. Hope you don't have the same fate that I had.
Try flashing back to stock and lock and unlock bootloader. If that doesn't stop the reboots, IMO, time to look for a new phone.
Edit : You might want to send it to Samsung for repair, if you are still under warranty.
Sent from my Micromax A116 using Tapatalk 2
Click to expand...
Click to collapse
I've already tried your suggestion, but it didn't help.
Actually, I'm still under warranty, but i was hoping to solve the problem by myself to avoid being without phone for a few weeks.
beekay201 said:
Check battery connections, replace battery
Update us later
Click to expand...
Click to collapse
Already tried that, i have a replacement battery. By the way, the reboot problem also occurs when charging from the normal power supply. Only the usb connection with debug mode avoids rebooting.
Thank you for your advice.

CStauch said:
Already tried that, i have a replacement battery. By the way, the reboot problem also occurs when charging from the normal power supply. Only the usb connection with debug mode avoids rebooting.
Thank you for your advice.
Click to expand...
Click to collapse
Okay, so what do you think you can do next? That replacement battery, is it a stock battery?

beekay201 said:
Okay, so what do you think you can do next? That replacement battery, is it a stock battery?
Click to expand...
Click to collapse
Yes, it is not distiguishable from the original one.
I was hoping, that there can be any hint in some sort of log file or something.

Have you tried booting into safe mode to see if it is an app issue?
http://www.talkandroid.com/guides/b...or-tablet-into-safe-mode-for-troubleshooting/
Sent from my Micromax A116 using Tapatalk 2

viskon said:
Have you tried booting into safe mode to see if it is an app issue?
Sent from my Micromax A116 using Tapatalk 2
Click to expand...
Click to collapse
Just tried that, also no difference

Are you using the original cable to charge it? I've had problems where using cheap ebay cables made the touchscreen all jumpy and needed a reboot to fix. I changed to the original cable and it never happened again. Dont know if you could have a similar problem but with random reboot.

AzNxJoHnNy said:
Are you using the original cable to charge it? I've had problems where using cheap ebay cables made the touchscreen all jumpy and needed a reboot to fix. I changed to the original cable and it never happened again. Dont know if you could have a similar problem but with random reboot.
Click to expand...
Click to collapse
I'm using both the original cable and two docking stations from amazon, one with ac/dc adaptor and one with usb. The phone always reboots no matter if it is charging or not. Only when connected to usb in debug mode, there is no reboot.

CStauch said:
Just tried that, also no difference
Click to expand...
Click to collapse
I strongly suspect a hardware issue. You might be better off sending it for warranty repair.
Sent from my Micromax A116 using Tapatalk 2

SAME PROBLEM!
Tried with several ROMs and Kernels, also stock, disabling proximity sensor (there is someone with this sensor issue...) but nothing changed.
Now I made a fuuuul hard deep wipe, and installed AOKP ROM with Nexus Toolkit. I have to check if it will be working, if not I'm going to restore phone to stock (locked unrooted etc) and then try...

Same problem here.

This happened also to me on August... was an hardware issue for me

TKPL said:
SAME PROBLEM!
Tried with several ROMs and Kernels, also stock, disabling proximity sensor (there is someone with this sensor issue...) but nothing changed.
Now I made a fuuuul hard deep wipe, and installed AOKP ROM with Nexus Toolkit. I have to check if it will be working, if not I'm going to restore phone to stock (locked unrooted etc) and then try...
Click to expand...
Click to collapse
Still not working... I wiped everything and restored phone to stock locked, and got, in one day, "only" one reboot and two super-lag (it's better than before but it's not good). I gonna send it back to assistance...

TKPL said:
Still not working... I wiped everything and restored phone to stock locked, and got, in one day, "only" one reboot and two super-lag (it's better than before but it's not good). I gonna send it back to assistance...
Click to expand...
Click to collapse
I had the same problems... i've tried to make a clean installation of the stock factory image ... sent to assistance.. it was an hardware issue...
Have You tried to use the flash-all.bat to restore the factory image, the executable inside the factory image archive that flash the stock image automatically... try it

enricocid said:
I had the same problems... i've tried to make a clean installation of the stock factory image ... sent to assistance.. it was an hardware issue...
Have You tried to use the flash-all.bat to restore the factory image, the executable inside the factory image archive that flash the stock image automatically... try it
Click to expand...
Click to collapse
I reflashed with the Nexus Root Toolkit the factory image, so I guess it made automatically the flash-all.bat.
Tomorrow I'm sending the phone to assistance

enricocid said:
This happened also to me on August... was an hardware issue for me
Click to expand...
Click to collapse
So What was the hardware issue because i have the same problem and out of warranty..... And I would like to repair the phone.
If the costs aren't to high.

It is happening to my gnex since yesterday.
I was on shiny Rom and all of a sudden it began rebooting randomly.
Looking at the last_kmsg I found a kernel panic related to I/o error of the ext4-fs (or something similar).
I performed several wipe, thinking of a kernel issue.
It continued rebooting randomly so I completely reset to stock 4.3 including format of sdcard.
I have the feeling that reboots began when the sdcard began to fill.
I also re_locked the bootloader, but reboots still occur.
It is probably a faulty Emmc chip, I will go to the store for warranty.
Lionhe
Inviato dal mio Galaxy Nexus utilizzando Tapatalk

[Q] Nexus 7 suddenly bricked ?

Hello all, so yesterday I went on my tablet (Nexus 7 2013 WIFI ver.) and browsed the net a bit and went to sleep. I recall having around 30% battery power. This morning I wake up to an apparently flat battery (power button didn't turn on anything) so I just plugged it in and did something else. After a while, I took my tablet and started it with the power button. However, it got stuck on the Google logo and never fired up anything. I've rooted the tablet quite some time ago (months) so the cause is not from there.
Things I haven't recently done:
Installing an app.
Rooting or flashing anything.
Updating an app.
Things I have tried doing to fix the problem:
Booting into FASTBOOT then trying the recovery mode = still stuck on the Google logo.
Booting a custom recovery image using Wug's toolkit = frozen at the team logo (TWRP) / black screen (CWM).
Flash Stock + Unroot (Soft-Bricked/Bootloop) = FAILED (flash write failure).
So now I'm really stuck and desperate to make the device work again. I've been reading all day long and trying all sorts of solutions to no avail. And it seems far-fetched to me for a device like this to just instantly brick itself without any reason at all.
Can anyone help me with this case ? Or does anyone has any idea what just happened to my tablet ? :crying:
EDIT: I'm afraid that warranty might not work as the device was unlocked and rooted so it's the last solution for me.

Bumpity bump
No one has any idea what happened to the tablet and how to fix it ? I've tried doing some more flashing but to no avail. It just refuses to flash and keeps failing to write the files.

I think you need to leave out on the charger for 1/2hr without doing anything with it. You are probably using what little power it has charged by trying to reboot it, etc.
I had to do that once and it did the trick.
Sent from my Nexus 7 using XDA Free mobile app

There is no reason you should not be able to get in to recovery (power and volume down).
You could call Motorola. They have good tech support.

The exact same thing happened to me. I rooted it months ago and haven't changed a thing since then. It just froze up a few days ago. I restarted and it just gets stuck on the google screen. I can get into the bootloader, but when I try to go to recovery, the google screen comes up and won't go away. I've tried every method I can find for flashing the stock image and absolutely nothing is working. I just get stuck on the google screen.
Please update this if you find a solution!

Do u guys have the most up to date version of whatever particular recovery that you're on?

Yep. I've flashed the stock recovery multiple times to no avail. :/

nexusjas said:
Yep. I've flashed the stock recovery multiple times to no avail. :/
Click to expand...
Click to collapse
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Have you tried to see if your computer sees your N7 by typing fastboot devices if you have the sdk installed?

wantabe said:
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Click to expand...
Click to collapse
Not what I wanted to hear, but you're probably right. Thanks :/

nexusjas said:
Not what I wanted to hear, but you're probably right. Thanks :/
Click to expand...
Click to collapse
I was to slow with my update. Does your computer see your N7 with fastboot?

wantabe said:
I was to slow with my update. Does your computer see your N7 with fastboot?
Click to expand...
Click to collapse
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.

nexusjas said:
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
Click to expand...
Click to collapse
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.

wantabe said:
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
Click to expand...
Click to collapse
I'm not sure what happened, but I just ran this little utility again (I've done it many times over the last week or so to no avail) and it actually worked. Hopefully it keeps working!
Thanks for your help!

Galaxy Nexus Boot Loop

Hey, i flashed CM11 about half a year ago. The last Saturday (20/12), it started to go in an infinite loop. First it could boot in apps, but then it crashes all the time. So What I 've tried:
Reset factory data/davlik/cache
Flashing another rom via Recovery
Bring back to stock via bootloader (cmd+fastboot)
Downloading mode (ODIN)
OmapFlash
Nothing made even a little change to my phone. It boots in the same OS, and it crashes all the time. It's like its in a readonly mode. It's like it has the program for PC Deep Freeze, that restores your phone to its first condition in every simple reboot. Can you help me plz?

dannaros said:
Hey, i flashed CM11 about half a year ago. The last Saturday (20/12), it started to go in an infinite loop. First it could boot in apps, but then it crashes all the time. So What I 've tried:
Reset factory data/davlik/cache
Flashing another rom via Recovery
Bring back to stock via bootloader (cmd+fastboot)
Downloading mode (ODIN)
OmapFlash
Nothing made even a little change to my phone. It boots in the same OS, and it crashes all the time. It's like its in a readonly mode. It's like it has the program for PC Deep Freeze, that restores your phone to its first condition in every simple reboot. Can you help me plz?
Click to expand...
Click to collapse
Forget about #1 and #2 in your list.
In #3, what happens when you try to flash the images?

efrant said:
Forget about #1 and #2 in your list.
In #3, what happens when you try to flash the images?
Click to expand...
Click to collapse
Nothing, still the same CyanogenMod OS. Even if I run oem lock, after rebooting to bootloader it will shown as unlocked again.

dannaros said:
Nothing, still the same CyanogenMod OS. Even if I run oem lock, after rebooting to bootloader it will shown as unlocked again.
Click to expand...
Click to collapse
If the images appear to flash properly in fastboot, but you are still on the same ROM, then I would suspect your NAND is toast.

efrant said:
If the images appear to flash properly in fastboot, but you are still on the same ROM, then I would suspect your NAND is toast.
Click to expand...
Click to collapse
What is NAND. Is NAND phone's internal memory? And what can I do now? Is it a solution or is it a hardware issue? Thank you for your help btw

dannaros said:
What is NAND. Is NAND phone's internal memory? And what can I do now? Is it a solution or is it a hardware issue? Thank you for your help btw
Click to expand...
Click to collapse
Yes, it's your devices internal flash memory. It looks like there is something wrong with it. (Others have had similar issues in the past.) So, yes, it looks like it's a hardware issue and there's nothing you can do yourself to fix it.

efrant said:
Yes, it's your devices internal flash memory. It looks like there is something wrong with it. (Others have had similar issues in the past.) So, yes, it looks like it's a hardware issue and there's nothing you can do yourself to fix it.
Click to expand...
Click to collapse
Ok mate. thank you so much. have a nice happy new year for you and your beloved ones. Plz reply me to my pm.