Possible NAND issue? - Samsung Galaxy Nexus

Team Vanir Jellybean v2-7, Galaxy Nexus Verizon
Last week i was having issues with the phone not booting, or just locking up not responding etc. A wipe seemed to help, and wit work for a while. I'd get my phone setup to where I wanted it again, and then the issues would come back.
I found a post that said it was possible EXT4 formatting issues because of a bad poweroff. So I downloaded all the stock 4.04 images, fastboot erased system boot recovery. Flashed the latest radios, stock system boot userdata and clockwork recovery 5.5.0.4. Booted seemed to be fine.
Rebooted into Clockwork and installed Vanir v7, ran fine for a few days. I thought the issue was gone. Until this morning when I got a text message and went to unlock the phone and it was locked up. I pulled the battery and that is when everything got extremely bad
Would not boot past the boot animation. I tried the following
I reinstalled the ROM,
i treid to wipe data,
wiped data and reinstalled the ROM.
although I was able to make a nandroid backup before I tried all of this
Then as a last resort I went into the mounts and storage and FORMATTED /system /data and /cache in CWM. Reinstalled the ROM and it actually booted.
What greeted me there is the last thing I'd EVER expect to see. I don't know how, what or why but all my data was there... every app text missed call... all of it.. even tho I had wiped AND formatted several times and did NOT restore my backup. EDIT: Even more oddness... My user apps didn't get wiped, they are all still there, but they are all acting like I had cleared their data through the applications menu....
I still don't know if this is because of a NAND issue that formatting fixed both times (flashing stock and using format in CWM) or if it will ever come back. Has any1 else had any issues of this sort? I really don't think this is a ROM issue.

you're probably causing more damage by flashing this, wiping this and that. best option is to leave it stock for now by flashing the factory image again. if it is a NAND issue then it would have stopped booting when the issue occured. but if it is still causing problems then send it back for a replacement.

Related

[Q] Freezing, FC's after nandroid restore??

So I decided to try one of the ICS roms earlier today. I nandroid backup'd my current config, flashed the ROM, played around, ran calkulin's format all, and proceeded to nandroid restore. Booted back into what was my original config only to find it's constantly locking up and random apps keep FCing. I did fix permissions, I wiped dalvik and cache multiple times. What the hell is the point of nandroid if it doesn't ****ing work right anyway?
I'm on RA 2.3 recovery. I backup the normal stuff including .android_secure and wimax.
Do you still have the rom handy?,if so,do your nandroid backup,then without wiping anything,install the rom over the top of the backup you just restored,it should help with the FC's,it worked for me,but if you installed a theme,it will convert back to stock as far as the framework goes.
Try manually wiping all options except sdcard and battery stats 3x or more and then restoring your nandroid then wipe cache and dalvik after the restore and before rebooting, sounds like you may have an errant piece of data that got left behind during the wipe
It seems that the 18 or so reboots I was forced to do have fixed something. No problems now. Strange for sure.
G+ was locking my phone up causing me to have to pull the battery, it was working fine then there was an update in the market but I was using an inverted version and didn't want to update the the bright white one and after a week of not updating it it started randomly freezing up when I would try to upload a pic or post a long message I updated and it stopped :-/ which was weird in itself maybe an app got updated and fixed your issue or maybe something uninstalled itself if your using dta2sd, sometimes when I have FCs, random reboots or have to do a battery pull some of my a2sd apps disappear when I reboot

[Q] Bad onboard Memory?

I had a weird issue today, when re-installing rom, booted into recovery, started the installation process, and let the rom (maximus 3.3) format the partitions, all went well until it started to verify the partitions, the phone rebooted. So I went back into recovery, recopied the maximus rom, started to reinstall, got the verify partitions, same thing, rebooted. Tried ARHD, same thing. Went back to Maximus, told it not to wipe the partitions, everything installed correctly.
Has anyone had/heard of this issue? Is it possible I have bad memory in the phone? I've flashed multiple roms on this phone and never had an issue, just looking for some answers.

S3 Stuck in Factory Reset HELP!

I've been trying to get a Rom on a S3 that the wife likes, so I've recently flashed the latest versions of Hyperdrive, Synergy and Wicked. I always follow the proper procedures of data wiping/factory reset, clear cache, clear dalvik, format system, and format data between each flash. I tried Hyperdrive first but had google sync errors, so went to Synergy. Synergy wouldn't connect to the nectwork so I went to flash Wicked v10 but the device wouldn't wipe/format data. I let it set for 20+ minutes and it never progressed. Pulled the battery and tried again but same result. I was able to install Wicked w/out the data wipe and it seemed to boot up ok but I was determined to get that wipe. So next I tried to restore to a backup from a week ago and it also stopped progress at the formatting data step. I re-flash Wicked v10 w/out the wipe. Once it did its thing and booted up I used went to the Factory Reset option under Settings but now the phone is stuck on the screen with the Android figure and a progress bar. Pulling the battery and trying to boot into recovery or even a normal boot all results back on the progress screen. I've managed to thoroughly piss off the wife by disabling her phone. Can anyone tell me how to fix this? I don't care if its reset back to factory rom or just anything to will allow the phone to work. Any help is appreciated.
Have you tried using Odin to flash a new original factory ROM?
IDK if you can get into Download Mode, but, if you can, it's worth a shot.
i agree with that statement. try flashing stock and unroot with odin. i have use hyperdrive since march, and i have not had that issue, so maybe its just a bad download or something. just try odin,

S3 Strange Hardware Failure. No Coming Back?

Had something really weird happen to my S3 guys.
Running teamwin and the Liquid-Smooth ROM. Been that way for 5 months since I bought it with no problems until now.
Plugged the phone up to the charger last night before bed. Woke up and wondered why the charging light was still yellow so I kicked the screen on and it was charging at an extremely slow rate (Around 40mA). Unplugged the charger and the phone made a tone I had never heard before. Noticed two small "glitches" or "artifacts" in the display rendering around the clock area on the home screen. Attempted browsing around the phone. App drawer opened and closed fine but EVERY process or app I would try to launch would crash so I rebooted, and that brings me to where I am now.
The ROM will NOT boot. The phone just sits there at the Galaxy SIII splashscreen. I can boot to Odin/recovery just fine and the internal SD filesystem appears intact and browse-able. Tried totally nuking the data section. Wiped Dalvik/Cache, did factory reset and then wiped the ROM. Tried re-installing the ROM and even re-flashing the radio and it still doesn't boot past the splashscreen.
While I was in recovery it also told me, "Your phone doesn't appear to be rooted. Would you like to install SU?", which is strange because the phone WAS rooted.
Thinking this thing mysteriously turned itself into a paperweight. Any ideas?
Please install a different Non-Liquid Rom. But for best results, First ODIN back to stock and then go from there. Use Root 66 Stock image.
agree with odin flashing root66 firmware. factory reset FIRST though. you will likely be forced to if you dont, and once stock recovery is flashed back on it will wipe internal sd.
if you still have issues after that i would suspect a hardware failure.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
Just FYI guys I got it back about an hour after posting this.
Even after wiping both caches, performing a factory reset, fixing permissions and finally nuking the ROM it still would not boot. I then put in a spare SD, used recovery to copy everything from internal to external to save all my valuable data and only after wiping the internal SD was I able to get the phone to boot again after re-installing the ROM.
I then transferred all valuable files back to internal SD, restored from a recovery backup and then was good to go. A bit strange but I got it working again.
Eventually I might upgrade from LiquidSmooth but I like it and have no reason to change for now.

Dying Flash Memory or RAM?

Hey guys ive been having weird issues on my phone. Here is the story:
Ive been running virgin GPE 4.4.4 for a long time, and all of a sudden it started crashing, lagging, and un successfully rebooting from a crash. so i thought i should just wipe everything in twrp and re-flash the rom. same issue. so i flash CyanogenMod, same issue. So i think somthing is wrong with the system memory, then i use odin to flash back to stock and it just will not boot.... so i thought it broke, but i flashed twrp again and wiped and installed CyanogenMod, it booted but still the same issues as before.
So am i right by calling it a RAM or NAND issue?
Anyone have any tips? i was going to use odin to re partition and nand erase all but people say not to do that.
You didn't mention factory reset. Try it before anything else.
Pp.
@PanchoPlanet Sorry for bumping, but if even a full wipe doesn't cut it, a factory reset won't do either.
As for your problem @grassyloki, chances are it's a NAND problem. If you've had it for over two years and flashed like crazy, that may be why.

Categories

Resources