Hi there, I never thought I would ever need to register onto a forum like this one and have to seek help directly, but it seems I have little other choice.
Anyway, I have a Nexus 7 (2012 model), and it has been working fine and dandy ever since I got it used back in June of this year. Only problems I had up until yesterday were occasional touchscreen jitters and unresponsiveness that I managed to fix with the guidance of a Youtube video. Moving along, I started to have odd problems occur yesterday that seemed to be quite the chain reaction and avalanche of even more problems that are making me awfully suspicious and paranoid.
The device kept on booting off after leaving it for a while. Turning it back on would sometimes result in the screen freezing up, prompting me to go in there and physically disconnect the battery. An antivirus scan showed no bad files of any sort. After some Google searching about the problem, I decided to go into fastboot and wipe cache partition. All seemed to be going fine until it freezes up in the process. Ok, time to forcefully remove the battery again. This time around, right before entering recovery menu, I see something a bit different. The red warning triangle still appears over the little Android mascot, but the words "No command" no longer appear. (I would provide a link, but I have not made enough posts yet.) I tried to wipe cache partition again. No avail. Ok, screw it, let's try formatting. Same result. Booting it up normally had resulted in the dreaded infinite Google logo loop.
That being said, is there any hope of me salvaging this device? I can still go into fastboot if that's any indication of hope!
Related
For some reason my note 4 (n910w8) started acting odd recently. Whenever I try to turn it on it gets stuck at the boot-loader with "Powered by Android" on the bottom of the screen and sometimes reboots only to get stuck again. I tried to go into recovery to factory wipe the device but when I do it says "E: failed to mount /preload (No such file or directory)". I can go into download mode just fine however, with no mmc error statements there that others have had. I have tried flashing different firmwares (all 6.0 that I can tell) but they all still do the same.
The weird thing is however, that if I put the phone into the fridge for awhile, it seems to work fine (albeit for a little bit while the phone is cold). When the phone starts to heat up I notice the freezes come back again until the phone just randomly reboots and the whole process of not booting starts again.
Is there any way to fix this? Thanks in advance!
It looks like your having a motherboard issue. Sad times! Im on my 2nd Note 4 (W8 model) now. 1st one has the eMMC read failure. And this one im typing on on now will lock up consistantly if i dont have a wakelock program running.
Best bet is this. Get it cold again. Then flash your rom (or just stick with what you have now). Then install this Wakelock app below And set it To 4 (Partial_Wake_lock). And then hit options amd make sure To "Autostart on boot".
https://play.google.com/store/apps/details?id=eu.thedarken.wl
Hopefully this fixes the issue for you. I dont take And credit for this. I found the same issue here on XDA And someone provided this solution.
If this does work for you, great. But its only a temp solution. Your battery will take a small hit as well since the CPU is consistantly online. You need either a motherboard replacement or time for another phone. PersonalIy i think this my last Note 4 as im seeing way too many issues. Maybe time for the Note FE or Note 8 (later this year).
As well if this does work try not to reboot of you can help it. I find my boot times are increasing. Sometimes needing a battery pull or a cache wipe in TWRP to boot again.
Hey guys, I have had my Note 4 for about 3 years now and it has never done me wrong. However, things have taken a turn for the worse... I started noticing a few days ago that it was slowing down on me, I mean, really slowing down. Big lag times when it comes to swiping to open the screen, or changing between apps, and the occasional self-shut down when the battery got down to about 15-20%. I had been putting off doing a self-update for a while, and when I finally had time to do one tonight, in hopes of cleaning it up, it is now lying on its death bed
I do not think the update ever finished (my phone is not rooted) but I was desperate enough to even do a factory reset and that has not fixed the issue.
Here are the symptoms:
As I go to boot the phone, I get past the Samsung Note logo and it looks like it is about to load properly, but then I get a popup that says "Unfortunately, the process com.android.phone has stopped" I hit ok and it keeps popping up again. I can't bypass it.. Then after I get passed that for a split second, another popup comes up that says "unfortunately system UI has stopped" It prevents me from getting to the home screen, in fact the screen behind it is black.
I have tried the following:
Clearing the cache partition from the recovery screen
I have done numerous hard restarts
I have gone through with a factory restart
That is where I have left off, and lost most hope, was with the factory restart. Now when I turn it on, I get past the logos and I can see in the background the page you would get as if it was a brand new phone (it says "Welcome! Preparing you device for first time use.." etc. But I can't do anything about it because I am still getting the same two popups that prevent me from doing absolutely everything!!!)
I have read about this happening and people seem to be able to fix this by accessing certain app setting and either resetting them, or clearing their cache. However, that is not an option for me because I can't get that far. I think something must have went wrong during the update...
Please help with any advice you can think of. I have been putting off rooting this phone pretty much because I was afraid of royally f****** it up, but at this point I am willing to try anything.
Thanks,
Eric
Hey guys, does anyone have any suggestions for my issue?? I am about to go out and buy a new phone, I have no idea what I can do to fix this. I have rooted it using Odin, but the popups are still occurring. I can't get the popups to stop, and they are preventing me from doing absolutely everything.
Is there anyway I can get it to go back to complete scratch? Again, I have done a factory reset, cleared the cache, rooted using Odin. I have done everything I can think of/what I have read I can do. I am willing to try anything at this point.
UPDATE: At this point my phone is on, and the only error message/popup I am getting is "Unfortunately, System UI has stopped." Behind that popup is a blank, black screen. The only option I have is to click ok, and the screen remains black.
Temporary solution that might work- Try logging in safe mode: Switch off the phone. Power it on and as soon as Samsung logo appears, release the power button and press and hold the volume down button. Release button when you see Safe Mode on the lower left corner of the screen. Try uninstalling all user apps in safe mode. To get back to the normal mode you can drag down from notification and disable safe mode.
You could also download the latest software for your model from samfirm and flash it via odin after factory reset. Could be a permanent solution.
why you just flash last frimware from sammobile,it will solve all your problems
SOLVED!!!
Alright guys, I was able to solve my problem, all thanks to this thread:
https://forum.xda-developers.com/note-4-sprint/general/stock-tar-odin-flashable-t3250864
I had already tried flashing a fresh stock rom, but to no prevail. I saw this thread and thought, hey why not give it a shot, and bingo! After downloading the .tar file for marshmellow and launching it through odin, she was good as new! So if anyone seems to have a problem with the system ui or the process phone.android popup, I suggest that thread.
Hello, so i've had this Note 4 for about 2 years, i had no problems with it thus far until recently ( 3 hours ago actually) i was just texting and browsing Instagram and out of no where the screen froze, it became unresponsive and the screen went black and started constantly vibrating so i quickly pulled the battery out and put it back in again, tried to start it again and it got stuck on the Samsung logo, i went for recovery mode and tried to look up latest cashe log and it froze right there too and restarted, pulled battery out and in again, tried to get into Recovery mode for a second time and a dm-verity verification failed error on the lower left corner popped up, i selected "Restart phone" and it got stuck on the Samsung logo again, battery in-out, tried to get into Recovery mode for a third time to do a factory reset but this time it got stuck whilst trying to boot onto recovery, and i had to out-in battery again, tried several times to get into recovery and it didn't work, i just gave up and started searching, then after 14 minutes i decide to give it another try and it normally booted up! i inserted in my PIN and browsed the apps for about 2mins but it froze, again, and the whole cycle kept repeating i let it cool down for 15mins and it boots up normally but freezes again after a few minutes of usage, i noticed that it insanely overheats before freezing (especially right above the SIM card area) and the four CPU cores are showing 2469MHz and on 100% (But that's also the case when the phone just boots up right?), Now i basically can't access recovery mode and i'm stuck with a Freeze-Reboot looped and i'm left with no other option but a full Stock ROM flash, the thing is i can't even get into recovery to do a full wipe before flashing in the ROM, can i just flash in again a TWRP recovery? and is there any way to fix this without having to do a full Stock ROM flash (i Tried the wake lock app it didn't work) and i'm on Android 5.0.1, this has JUST happened today and never before. i'm hoping this isn't a hardware issue.
UPDATE: i have just noticed something rather interesting, the phone immediately freezes and goes nuts with the reboots and failed recovery modes instantly after i connect it to a wifi network, and exactly when it's attempting to "send report", a sending report sign shows up in the notification bar and it immediately screws up the phone until i do another Factory reset, i just did another one without connecting to a wifi network and i've already gone 40mins with it without any issues but perhaps it's just because it's not on heavy usage?
Sounds like you have the eMMC issue.
You can try and reflash with Odin. Get the right version from Sammobile.
Do yu get to download mode in any of the scenarios you describe?
Try WakeLock again and select the level to 4
Having the same issue
I'm having the same issue and don't have any idea how to help, just hoping someone out there knows...:crying:
Cybrid013 said:
I'm having the same issue and don't have any idea how to help, just hoping someone out there knows...:crying:
Click to expand...
Click to collapse
If you have the Snapdragon version - it's highly possible to have the emmc problem. Which is a bummer and the phone is like dead.
Unless you can buy another 910C motherboard and swap it.
Sorry.
What is short name for emmc?
jjoeshua said:
What is short name for emmc?
Click to expand...
Click to collapse
embedded multimedia controller
Just been having a very similar problem. I posted this elsewhere, but it may be helpful:
"My issue was that I needed to recover data, docs, photos, phone numbers etc. When boot looping the note 4 got very hot . In particular around and to the left of the camera (looking at the rear). Thinking it could possibly be the dreaded eMMC problem which also manifests itself by creating heat, I thought cooling the device might help. I placed the Note on a cooler box freezing block and voilà! No boot loop. I was able to remove all, but necessary apps and do a full copy to my PC. Storage was reduced from around 90% to 50% and memory 80% to 60%. It's now been stable for 12 hours, but the jury is still out. Next will be full reset with he latest available firmware 6.0.1 as mine was still on 5.1.1."
Also now downloaded a eMMC bug check that says my eMMC chip is 'sane'. Guess we'll see
This is a Nexus 6P (32GB) I rooted shortly after getting it (new) in September 2016, and updated to stock 7.1.2 in August 2017, but I otherwise haven't modified it from its out-of-the-box state.
Until recently, I'd never experienced any issues - no random reboots, battery was still pretty good, etc. Then last week, the phone rebooted suddenly, and appeared to "boot loop". I hadn't yet heard about the issues the 6P has with this so I powered it down, left it alone for a while, then turned it back on later, booted without incident, and forgot about it.
Last night it happened again, at which point I searched and learned of the dreaded "boot loop of death" the 6P specifically has had issues with. Hoping that wasn't the issue, I again powered down and tried it this morning, and it only stayed awake for about 5 minutes before going into boot loop. At this point I looked up and applied the fix described in this thread, but to my dismay it had no (visible) effect - I still see the initial "bootloader is unlocked" screen, then the google + open lock icon, repeat ad nauseum.
About all I can do with the phone right now is load into fastboot. The phone has data on it I'd really like to recover, is there a way I can do that from there? If not, is there any way to connect with ADB without getting through a full boot? Are there alternative boot loop fixes, alternative steps to the fix described? I've read several threads here and can't tell if any apply to me, and can't find any answers to the above.
I've accepted that the phone is probably never going to be the same again but I need to get my data off there and do a few quick things before I consign this one to paperweight duty. Thanks in advance
chmmr said:
This is a Nexus 6P (32GB) I rooted shortly after getting it (new) in September 2016, and updated to stock 7.1.2 in August 2017, but I otherwise haven't modified it from its out-of-the-box state.
Until recently, I'd never experienced any issues - no random reboots, battery was still pretty good, etc. Then last week, the phone rebooted suddenly, and appeared to "boot loop". I hadn't yet heard about the issues the 6P has with this so I powered it down, left it alone for a while, then turned it back on later, booted without incident, and forgot about it.
Last night it happened again, at which point I searched and learned of the dreaded "boot loop of death" the 6P specifically has had issues with. Hoping that wasn't the issue, I again powered down and tried it this morning, and it only stayed awake for about 5 minutes before going into boot loop. At this point I looked up and applied the fix described in this thread, but to my dismay it had no (visible) effect - I still see the initial "bootloader is unlocked" screen, then the google + open lock icon, repeat ad nauseum.
About all I can do with the phone right now is load into fastboot. The phone has data on it I'd really like to recover, is there a way I can do that from there? If not, is there any way to connect with ADB without getting through a full boot? Are there alternative boot loop fixes, alternative steps to the fix described? I've read several threads here and can't tell if any apply to me, and can't find any answers to the above.
I've accepted that the phone is probably never going to be the same again but I need to get my data off there and do a few quick things before I consign this one to paperweight duty. Thanks in advance
Click to expand...
Click to collapse
I have the exact same issue. I run the same version operating system as you have an unlocked bootloader otherwise have not modified the typical system install. I did already have the fix applied from an earlier incident but now it is boot looping and won't stop. I have red threads here and there that have advised to apply heat to the phone and that might get it to boot at least to get your data off. Myself I have had no such luck with this technique but perhaps it will work for you otherwise I have since moved on to the OnePlus 6t. A very awesome replacement not to mention at a decent price for more horsepower and storage
Sent from my ONEPLUS A6013 using Tapatalk
Just in case it helps anyone with this phone and issue, I was able to get a couple more boots out of it, enough to rescue some data, by doing the "15 minutes in the freezer in a ziploc bag" trick.
RIP Nexus 6P, shame about the BLOD!
This is really starting to get on my nerves now. Ever since I got my new S10+ from AT&T, it's occasionally done this thing where after I reboot the phone, I unlock it, and it briefly says "starting phone" on the home screen, and then will mysteriously do a quick reset, where it skips the AT&T logo and jingle, and just shows the Samsung splash screen , then takes me back to the lockscreen and it's usually fine after that.
However, Just now I decided to reset my phone, like one should do periodically, and it did the strange double reset after unlocking... Then when I unlocked it, after the "starting phone" message I tried to open a browser, and BAM! Quick reset again! Unlocked, let it start up, tried to open an app, BAM quick reset again after the screen briefly shifted from landscape to portrait mode (even though I was still holding it long ways in landscape position). Its never done this before and I'm getting concerned. It's never randomly reset while using the phone, this only happens right after a reset.
Any ideas? I've already tried wiping partition cache after big updates, doing soft resets. I'm worried that I'm going to have to end up resorting to a factory wipe, as others suggested I do when I was having battery drain issues on the ASD3 firmware, possibly because of restoring everything from a backup of my last phone when I got this one. Because supposedly restoring from backups from AT&T, Google or Samsung has caused all sorts of problems for people. I really don't want go wipe everything and spend hours try to get it all back on here manually if i don't have to.
SinisterDev said:
This is really starting to get on my nerves now. Ever since I got my new S10+ from AT&T, it's occasionally done this thing where after I reboot the phone, I unlock it, and it briefly says "starting phone" on the home screen, and then will mysteriously do a quick reset, where it skips the AT&T logo and jingle, and just shows the Samsung splash screen , then takes me back to the lockscreen and it's usually fine after that.
However, Just now I decided to reset my phone, like one should do periodically, and it did the strange double reset after unlocking... Then when I unlocked it, after the "starting phone" message I tried to open a browser, and BAM! Quick reset again! Unlocked, let it start up, tried to open an app, BAM quick reset again after the screen briefly shifted from landscape to portrait mode (even though I was still holding it long ways in landscape position). Its never done this before and I'm getting concerned. It's never randomly reset while using the phone, this only happens right after a reset.
Any ideas? I've already tried wiping partition cache after big updates, doing soft resets. I'm worried that I'm going to have to end up resorting to a factory wipe, as others suggested I do when I was having battery drain issues on the ASD3 firmware, possibly because of restoring everything from a backup of my last phone when I got this one. Because supposedly restoring from backups from AT&T, Google or Samsung has caused all sorts of problems for people. I really don't want go wipe everything and spend hours try to get it all back on here manually if i don't have to.
Click to expand...
Click to collapse
Had an issue with this early on but seems to have been fixed at some point, I'm I'm exynos though so probably not much help!
mtm1401 said:
Had an issue with this early on but seems to have been fixed at some point, I'm I'm exynos though so probably not much help!
Click to expand...
Click to collapse
Dang... So it does appear to be an issue experienced on both Exynos and Snapdragon variants. I wonder if there is or will be a fix for this. I've been asking around and haven't gotten many responses about this problem at all. I'm concerned because it seems to be getting worse than when I first got the phone.
I'm having the exact same problem. Sometimes it goes through quick reset, full reset, a couple more quick, then back to the Verizon logo, then starts up. Opening an app at that point usually does another quick, then full, then everything works. Glad I'm not the only one, but I haven't found any solutions either.
macmanui said:
I'm having the exact same problem. Sometimes it goes through quick reset, full reset, a couple more quick, then back to the Verizon logo, then starts up. Opening an app at that point usually does another quick, then full, then everything works. Glad I'm not the only one, but I haven't found any solutions either.
Click to expand...
Click to collapse
Mine does the same. Unlocked bought directly from Samsung. I don't reboot the phone very often so it doesn't bother me that much.