Hi,
As the title says:
Have a Nexus 5 running the latest lollipop build that has been working properly for a while (Phone is a Google refurb from November 2014, replacing my original N5 that had battery issues; Warranty expired Feb 2015)
4 days ago, it randomly rebooted and then got stuck on the "Optimizing apps" page on initial bootup - would never go past a certain app number
First tried wiping cache - which didn't complete even after 48 hours
Next tried full wipe from recovery, which worked but then shutdowns still happened
Reflashed all stock images (Phone is stock, not rooted) last night - problem still exists with random shutdown - but I can always get past initial setup; shutdown problems happen a little while later during use
Wiping cache from recovery now gives a "Could not mount /cache/" error in recovery
My hypothesis - that there's sector(s) on the eMMC that's borked. It's a 32GB phone - is there a way I can flag off a certain sector as "bad" and put the cache partition somewhere else? Also open to other suggestions, including replacing the eMMC chip if needed (I can find someone set up for BGA work).
I considered doing a file check from Philz / TWRP, but since the issue persists after a full reflash/reformat I assume that it's not a software bug.
Thanks in advance for the help, let me know if there's any other information I can provide that might be useful.
Anyone?
Related
I previously posted in the local Galaxy S3 i747M section with the same problem, but now the issue is worse than before.
Here's my previous thread:
http://forum.xda-developers.com/galaxy-s3-att/help/boot-loop-plugged-to-ac-twrp-wipe-data-t3070064
A note that I'm no stranger to flashing and the inner workings of Android architecture (ROMs and general hardware), . But for the sake of this issue, please feel free to treat me like a noob if you think it would help elaborate any procedures I should follow or troubleshooting steps I should take, or just throw ideas at me like the software dev that I am and expect me to figure it out on my own.
Some background:
Recently (around beginning of April), my phone began to exhibit strange behaviour - reboots when reading/writing from internal memory (not uSD card), unable to wipe /data partition in TWRP or CWM. I would also get bootloops when I was plugged into direct AC charging (no problems if plugged into a computer for charging, though).
When in TWRP, CWM, and Philz, I would not be able to wipe the /data partition or anything in it. Installing anything to /system also caused a crash (though wiping it didn't cause any issues). Doing a factory reset wipe would also cause the recovery to "crash" - the recovery would freeze up and the phone would reboot. I could not restore a NANdroid, I could not install a new custom ROM. In TWRP, if I opened up a terminal window and manually tried to repair the /data and /system partitions with the e2fsck command, it would still freeze up and crash.
At that point, I downloaded the stock 4.4 firmware image (I think it was NF2?) from Sam Mobile and flashed it via Download Mode + Odin. Booted it up and ran the phone stock for probably a week. Then, I carefully used Odin to flash a freshly downloaded (and MD5 verified) TWRP 2.8.6.0 TAR image and SuperSU. Flashed both via Odin just fine. From there, I mounted the microSD card - I didn't want to touch the internal memory for now - and copied over a fresh downloaded copy of a CM12 based ROM (also MD5 verf'd) to it. From there, still in TWRP, I successfully flashed a 4.4.x TouchWiz-based ROM.
Take note that at this point, doing anything to attempt to wipe /data still leads to crashing the recovery. Nothing I have done has resolved this issue. I left that issue alone, just happy to have a working phone.
That above procedure seemed to work. I could then use the phone for about 2 weeks. Then my phone started crashing again, same as before: only when I was doing something that was reading/writing the internal memory. E.g. music, podcasts, etc.
I followed the same procedure with Odin + stock firmware > reboot > Odin + TWRP + SuperSU > flash custom ROM. Worked fine again for 2 more weeks.
Here I am 1 month later, same problem as the last 2 times. This time, however, after flashing the custom ROM, it does not boot up now. My phone is at home because I cannot use it. Last night, upon trying to boot up S3rx and PAC 5.1, I literally let it sit at the boot animation for 1 hour, each, and neither got past the boot animation. I'm familiar with ROMs sometimes taking say 10 minutes upon very first boot on a clean flash, but I gave up after about 1 hour (in fact, 1.5 hours for PAC 5.1, which was my second attempt last night). It's to the point where I'm certain if I left my phone plugged into the AC, it would still be at the boot animation over 12 hours later.
I know of the NAND memory corruption issue that S3's had previously, and I did flash the stock firmware that came out at the time (I think it was an Lxx based bootloader+firmware). But that was years ago, end of 2012 if memory serves me correct.
Thoughts on what I am facing? What I should try and do next? Where to go from here? If this is a hardware issue that is beyond fixing with flashing things in fastboot/ADB/Odin, then I'll face defeat and look for a new phone. But if I can hang on to this phone for just a little bit longer...
Thanks!
Hi there
Please note the following sticky from the top of the Assist section,
> General discussion > XDA Assist > The Purpose of XDA Assist [Please Read]
As a senior member on XDA, I am quite confident that you know where your device section is (you already asked something there) and where to ask for help.
Thanks for understanding
Good luck
I am probably facing a very common issue, please clear my doubts regarding the issue. I have flashed my tab with cm10.2 and used it for about a year, then switched to cm11 nightly. 2 months ago i flashed TWRP and unofficial cm12 and my tab became weird. Boot loops, over heating were the symptoms. I did a wipe switched back to cm11. It was fine for few hours and then all apps and process started failing, my tab went into 3 min boot loops. It would over heat and go on and on until the battery gives out. I thought I can fix it, but the recovery was gone. When I go into recovery mode it just stays on Samsung Logo. I can access download mode, so I tried to flash cwm recovery, odin prompted PASS but the 'Custom Binary Count' stayed 2, I tried with TWRP, same, odin says PASS but counter stays the same. I searched for similar issues here, and found that the cause might be emmc bug. So my tab is in a read-only state. To verify that I tried creating folders in the 3 min boot loop sessions, it was gone at next restart. Being convinced that my tab is dead or the read-only state made it an invincible brick I deleted the system folder. It crashed, but when I restarted everything was normal.
So is it emmc related issue? Since my tab is in read-only state all apps are crashing, I tried installing new apps and it never succeeds, there are no JTAG services nearby, also I need to be sure if it's the superbrick bug or a hardware fault. Please provide me some clarification. I can try experimenting with it as I have recovered my data. If it can be fixed then it would help other tab owners as well. Any ideas, clarifications or instructions are much appreciated.
Thanks
Note : It all started after I flashed twrp-2.8.7.0-p3100.img and unofficial cm12 by Android-Andi. I flashed the rom knowing the risks and Bricking my tab is my fault not the rom-builder's.
anshu_6187 said:
I am probably facing a very common issue, please clear my doubts regarding the issue. I have flashed my tab with cm10.2 and used it for about a year, then switched to cm11 nightly. 2 months ago i flashed TWRP and unofficial cm12 and my tab became weird. Boot loops, over heating were the symptoms. I did a wipe switched back to cm11. It was fine for few hours and then all apps and process started failing, my tab went into 3 min boot loops. It would over heat and go on and on until the battery gives out. I thought I can fix it, but the recovery was gone. When I go into recovery mode it just stays on Samsung Logo. I can access download mode, so I tried to flash cwm recovery, odin prompted PASS but the 'Custom Binary Count' stayed 2, I tried with TWRP, same, odin says PASS but counter stays the same. I searched for similar issues here, and found that the cause might be emmc bug. So my tab is in a read-only state. To verify that I tried creating folders in the 3 min boot loop sessions, it was gone at next restart. Being convinced that my tab is dead or the read-only state made it an invincible brick I deleted the system folder. It crashed, but when I restarted everything was normal.
So is it emmc related issue? Since my tab is in read-only state all apps are crashing, I tried installing new apps and it never succeeds, there are no JTAG services nearby, also I need to be sure if it's the superbrick bug or a hardware fault. Please provide me some clarification. I can try experimenting with it as I have recovered my data. If it can be fixed then it would help other tab owners as well. Any ideas, clarifications or instructions are much appreciated.
Thanks
Note : It all started after I flashed twrp-2.8.7.0-p3100.img and unofficial cm12 by Android-Andi. I flashed the rom knowing the risks and Bricking my tab is my fault not the rom-builder's.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63868220&postcount=27
It's strange that this has happened mostly to the tab 2 owners, even those who were at stock rom, and changed nothing in their tab. So, it's not rom developers mistake neither its yours. Blame it on the emmc and Samsung.
QUOTED Android-andi "All latest Roms & Recoveries have MMC_CAP_ERASE disabled kernel side, to
prevent 16GB Tabs from damage because of
MAG2GA EMMC which is known for TRIM BUG."
http://wiki.cyanogenmod.org/w/EMMC_Bugs
If this is true, the latest versions you have the better.
I too have been keeping my tab updated and never gone stock again after upgrade.
billysam said:
http://forum.xda-developers.com/showpost.php?p=63868220&postcount=27
It's strange that this has happened mostly to the tab 2 owners, even those who were at stock rom, and changed nothing in their tab. So, it's not rom developers mistake neither its yours. Blame it on the emmc and Samsung.
QUOTED Android-andi "All latest Roms & Recoveries have MMC_CAP_ERASE disabled kernel side, to
prevent 16GB Tabs from damage because of
MAG2GA EMMC which is known for TRIM BUG."
http://wiki.cyanogenmod.org/w/EMMC_Bugs
If this is true, the latest versions you have the better.
I too have been keeping my tab updated and never gone stock again after upgrade.
Click to expand...
Click to collapse
Yeah, this TRIM bug appeared like an epidemic. I guess JTAG is the only option or the emmc in my device has reached it's end. I think it is time to put my tab to rest. Thanks for the link billysam.
I can access the shell even when my device is off. The device connects as OMAP4430 USB Device for a second and vanishes, after that in "Device Manager" it shows as "Samsung Android adb interface", though the internal storage can not be accessed this way, but I can see the filesystem, is there anyway to change the readonly mode so that I can attempt some sort of way to recover my tab?
Hi!
My Nexus 5 device seems to have many issues, some that I have resolved, some that appeared next. Here is some history.
- The first issue that I had was that some sensors were not detected, and the others were not working. Sensor testing applications found some of them (but they didn't work), and others like the accelerometer didn't even show up in the list.
- For a couple of months now, once in a while (at each ~2 weeks), I find my Nexus 5 powered off, and bricked (the boot process stops at the Google logo)
- Each time, flashing the original images worked (simply using flash-all.sh)
- After one of these flashes, I had no wifi. Flashing the original image did not work. Rooting/installing TWRP recovery, erasing cache, etc. did not work. I finally got it to work by installing a custom ROM, and never understood why it worked.
- Device bricked again, flashed the original image back. Wifi still works, but no SIM card detected. Absolutely no sensors are detected. The device reboots after a couple of minutes. This is where I am now.
What I tested so far :
- Rooting the device, running e2fsck on the partitions, some of them showed errors. None of them show bad sectors.
- Moving the content of /persist (to try to fix the SIM card problem)
- Flashing custom ROM, stock ROM, old ROM, different radio, etc.
- Removing/inserting the SIM card
I really am out of ideas, does anybody have ideas that I could test? I'm starting to think that I have an hardware issue but I still hope to repair the device... The issues started to appear right after the guarantee was expired.
EDIT: I found many threads about power button issues, however right now if I boot to Android the device reboots after few minutes, but when the phone is in TWRP recovery it stays open and never reboot. I therefore think that the reboot problem is not related with the power button.
Hi, I bought a used Nexus 5 and it has been causing quite some problem when booting. I flashed Cyanogenmod in it and it works fine for a few days. After that it keeps having the same problems in the following order:
- It would restart on its own, sometimes some random app will fail functioning (it's never the same app).
- Turns off on itself without restarting. Can still be turned on normally.
- From there it gets worse and start bootlooping. On CM it loops around the part where it initialises the apps. On stock its the colourful stuff that happens right after the Google logo.
- Finally it just gets stuck in boot. On CM it's stuck where it initialises apps while for stock it turns off right after the Google logo appears.
I have tried the following:
- The persist partition fix described at https://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
- Cleaning the power button and made sure it wasn't stuck.
- Re-flashing CM, did a checksum to make sure the files are okay
- Went back to stock, did a checksum too.
It's a used phone so I have no idea what it went through in the past. Anything I can do to fix it?
Try running the phone with a stock ROM without root. If the problem still happens, it's probably a hardware problem.
It didn't have root but I flashed a factory image (plus another round of factory reset too) and even locked the bootloader + reset the tamper flag this time. It's working fine now but the problems normally start a few hours/days later so I can't be sure at the moment.
If it does fail again which hardware is the one with the problem? The warranty's long gone so will it be easy to buy a new part and replace it myself?
The cheapest solution may be to buy a used Nexus 5 with a smashed screen and working internal components to swap out components.
So I have this n5110 tablet which has performed without problems since I bought it last year in December. Device is running TWRP recovery and Resurrection Remix 5.7.4 (CM13 based).
The symptom: first time it happened was during an "apps upgrade" session. Google Play Store updated a bunch of apps and all in sudden the tablet froze. Completely. Dead. Clock in status bar stopped working. After an hour I gave it a reset (hold power until it reboots). The result: boot loop. After finishing the boot process, it showed the lock screen for couple of seconds, then reboot ... and so on.
Went into recovery, did a wipe of data & cache & dalvik & system and started all over. After restoring the system, i started installing apps. All in a sudden ... BOOM ... same problem again.
You can imagine - I went through this process about 7 times. Then I realized, no matter what I do, if free storage has decreased to about 7.6 GByte, the big boom happenes and the phone is dead (boot loop).
I began to suspect a nand problem. So after restoring the system (without reinstalling all my apps) I installed “eMMC Brickbug Check” which also does a memory check. The app showed no problem. All good.
So back to recovery, into terminal and there I tried to “zero” the data, cache and dalvik partitions using “dd if=/dev/zero bs=1M of=/dev/block/mmc...” - you get the idea. No error messages here so all 3 partitions did not cause a nand writing problem.
So I'm stuck now. Before I try to replace the motherboard ... does anyone have an idea on how to really “test” the nand to confirm my suspected nand write problem?
Thanks for any help!
Markus.
oldschool63 said:
So I have this n5110 tablet which has performed without problems since I bought it last year in December. Device is running TWRP recovery and Resurrection Remix 5.7.4 (CM13 based).
The symptom: first time it happened was during an "apps upgrade" session. Google Play Store updated a bunch of apps and all in sudden the tablet froze. Completely. Dead. Clock in status bar stopped working. After an hour I gave it a reset (hold power until it reboots). The result: boot loop. After finishing the boot process, it showed the lock screen for couple of seconds, then reboot ... and so on.
Went into recovery, did a wipe of data & cache & dalvik & system and started all over. After restoring the system, i started installing apps. All in a sudden ... BOOM ... same problem again.
You can imagine - I went through this process about 7 times. Then I realized, no matter what I do, if free storage has decreased to about 7.6 GByte, the big boom happenes and the phone is dead (boot loop).
I began to suspect a nand problem. So after restoring the system (without reinstalling all my apps) I installed “eMMC Brickbug Check” which also does a memory check. The app showed no problem. All good.
So back to recovery, into terminal and there I tried to “zero” the data, cache and dalvik partitions using “dd if=/dev/zero bs=1M of=/dev/block/mmc...” - you get the idea. No error messages here so all 3 partitions did not cause a nand writing problem.
So I'm stuck now. Before I try to replace the motherboard ... does anyone have an idea on how to really “test” the nand to confirm my suspected nand write problem?
Thanks for any help!
Markus.
Click to expand...
Click to collapse
Answering my own question here: after quite some hours of trying it turned out that my tablet seems to be just fine. The problem is something totally different and weird. If you are interested in what's going on, please continue reading here: https://forum.xda-developers.com/android/help/help-app-bricks-samsung-tablet-try-to-t3661516