Hello everyone,
I have a Memopad Me176c k013, stock rom, no root or anything like that, latest update.
All of a sudden, a few days ago that error appeared, at first it would only appear once every couple of hours, now, it's almost non stop. Sometimes I can use it for 2-3 hours, sometimes, like today, it will just appear constantly.
What I tried, in order:
Disabled most of the apps and cleared all apps cache. No luck
Booted into safe mode. No luck
Cleared cache partition from recovery menu. No luck
Factory reset from recovery menu. No luck
From what I'm reading, the firmware might be corrupted? Tablet is no longer in warranty, and it's not worth the cost to send it to asus.
Any ideas?
Thank You
Related
I just installed CM9 via the Novacom2 method. The tablet seems to reboot itself after a few minutes of being booted up for no apparent reason. I can start up the device, and not even touch one thing, and after a bit it will self reboot.
Anyone experiencing this? Should I do a reinstall? Novacom2 method, or a complete factory reset with CWM?
CM9 runs extremely smooth otherwise, but I can't have it up for more than 5 minutes with a self reboot. It's bizarre.
Thanks in advance people...
I meant ACMEInstaller2 where I wrote Novacom2 ....
The only time I got random reboot is if I try to overclock. I went to replace CWM with TWRP today, and checked in CPUspy something quick. I had 36 hours of up time (remember this only dropped 4 days ago). Initially I tried to OC, even only going one step up I got freezes, and reboots. But leaving it at stock frequencies I have zero stability issues.
I would say to start fresh. With a fresh downloaded copy. Go into CWM and wipe data / factory reset, wipe cache, advanced > wipe dalvik, mounts > format system, data, cache, then reinstall, and install the charge fix. Then don't restore anything, and see if that fixes it.
Sent from my Galaxy S II (i777)
that may be the route I go. After about 15 reboots it is currently holding steady I have not made any interventions.
As a side issue, I get email notifications but the email app crashes upon opening. Gmail works fine though....
quarlow said:
The only time I got random reboot is if I try to overclock. I went to replace CWM with TWRP today, and checked in CPUspy something quick. I had 36 hours of up time (remember this only dropped 4 days ago). Initially I tried to OC, even only going one step up I got freezes, and reboots. But leaving it at stock frequencies I have zero stability issues.
I would say to start fresh. With a fresh downloaded copy. Go into CWM and wipe data / factory reset, wipe cache, advanced > wipe dalvik, mounts > format system, data, cache, then reinstall, and install the charge fix. Then don't restore anything, and see if that fixes it.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
I did a fresh start as above and the CM9 from is running problem free and 10x better than before when I had done the acmeinstaller2 method. Thanks button hit.
gizmo2431 said:
I just installed CM9 via the Novacom2 method. The tablet seems to reboot itself after a few minutes of being booted up for no apparent reason. I can start up the device, and not even touch one thing, and after a bit it will self reboot.
Anyone experiencing this? Should I do a reinstall? Novacom2 method, or a complete factory reset with CWM?
CM9 runs extremely smooth otherwise, but I can't have it up for more than 5 minutes with a self reboot. It's bizarre.
Thanks in advance people...
Click to expand...
Click to collapse
Try fixing permissions and wiping up cache from CWM, that fixes the reboots after power-on for me.
It used to do it if I left the screen to go off, but is fine now
I too am having reboot issues, but it only happens when I'm doing something. So far trying to open the Photoshop PS Touch app will cause a reboot, clicking settings in boat browser, etc. It's strange as hell.
I as well get the stock android mail client crashing when opened but its notifacations and gmail all work. I just installed maildroid and disabled stock email and seems to work OK
gizmo2431 said:
I just installed CM9 via the Novacom2 method. The tablet seems to reboot itself after a few minutes of being booted up for no apparent reason. I can start up the device, and not even touch one thing, and after a bit it will self reboot.
Anyone experiencing this? Should I do a reinstall? Novacom2 method, or a complete factory reset with CWM?
CM9 runs extremely smooth otherwise, but I can't have it up for more than 5 minutes with a self reboot. It's bizarre.
Thanks in advance people...
Click to expand...
Click to collapse
I have the same issue, but normally when the screen is on, it always reboots when I try to connect to usb storage, I have a galaxy s2 running on stable(nightly had too many bugs). anyone has the same problem?
I usually get reboots when I let the screen turn off due to inactivity. I tried installing TWRP and doing a clean install from there but it rebooted at the setup screen for CM9. I've had reboot issues since I first installed CM9, but its improved a little bit. I did try uninstalling android completely then reinstalling, but still got reboots. Does anyone have any other suggestions?
I think the best thing to do is use ACMEUninstaller to complete remove Android from your TP, then reinstall from scratch. I had reboot issues after upgrading from CM7a2 until I did a complete wipe.
Hi all,
I really need your guys help. Out of nowhere today my phone restarted and then got stuck in a bootloop. When I went into recovery, it gave me the "android is updating" pop-up. I knew there was no update and within 20 seconds or so it said "no command". I went through to wipe the cache, and after rebooting it back up, strangely it didn't give me the "android is updating" screen that occurs after wiping cache. I went ahead and tried to factory reset through recovery and everything was fine until I got a msg "E: could not mount (file or directory could not be found) or something a long those lines. I'm assuming the EFS is fried? I rebooted it after and even at the "Welcome Screen" it started boot looping again. I'm stock lollipop unrooted. I never rooted this phone or flashed any ROMs. I called T-Mo and they will send me a replacement but I still want to see if this can be fixed. I also don't have a replacement phone so..there's that. Would anyone be able to help?
Edit: The only thing I haven't tried is flashing the stock firmware via odin. Would this trip the knox counter though? I really want to avoid that especially since I am having these issues and I don't want tmo/samsung to think I caused this issue.
Bad phone. Ur new phone will be good to go.
BAD ASS NOTE 4
Hello all. I have been in the Android root community for a little over three years, and even after tinkering with the various devices I've owned since, I cannot get my T599N to come out of its current bootloop.
A background: I had been checking some things in my settings app (running stock, rooted), and I ended up just force closing the settings app to get out of it quickly. Well, this action deleted all of my text messages, and later on it removed my notification bar and made my wallpaper go black. I ended up booting into recovery mode to try and clear the cache. After it cleared, I rebooted, and bam, the bootloop started.
Now, here's what's interesting. The phone is in a bootloop where it displays the first boot message (SGHT599N Galaxy Exhibit or whatever), and then it tries to boot into cwm recovery, displays the loading screen for that for 2 seconds, and just reboots again. I've tried installing a stock rom from ODIN with no success. The rom apparently loads onto the device but it's still in the bootloop. After this, I tried to install philz recovery to try to install a zipped rom to get the device to somehow boot. I tried to factory reset it for installing purposes, and it just reboots. The device will literally clear everything but /data, so that makes me think that it may be a file system problem. I really need to get it to work, as I am out of a phone right now.
Does anyone have any suggestions? I've tried everything I know.
Hello! My Galaxy note 5 (SM-920G) has been stuck on a boot loop for a week now, I've tried everything. I've used "wipe cache partition", "Wipe data/factory reset", even flashed stock firmware from sammobile using odin. I'm still stuck on a bootloop. I am gonna proceed to explain the events that occurred before and after the bootloop in a level of detail that I'm capable of, also one that I think should be sufficient.
Events before the bootloop:
So here's what happened. I was using my phone as usual when I noticed that I couldn't play any music. Spotify, which I was using at the time, refused to play any song. So, I checked out Phonograph(music app that uses local library) and I couldn't seem to play anything from my local library either. I then proceeded to go ahead and open YouTube only to realize that I couldn't play a video on YouTube either. After much fiddling (I don't remember what exactly I did that caused it) but a YouTube video played, but I heard no sound. From here on out, I could PLAY/VIEW any media related file and such but I heard no sound. I searched it up and apparently a cache partition wipe seemed to do the trick (I should have dug deeper into this but this is what I found). I proceeded to the recovery menu and selected "Wipe Cache Partition" (Forgive me, memories a little fuzzy from here on), If I recall correctly, I got into a bootloop and I wiped the cache partition again and it booted up fine. However, there was still no sound, since it was late at night I decided to give up and go ahead and sleep for now.
The next day, when I woke up, everything was working perfectly. I had no idea why.. but hey, I wasn't about to complain. Fast forward a few days, the sound issue popped up again, so I proceeded to wipe the cache partition again. I repeated this a few times but it didn't work, so I gave up. My phone was booting perfectly fine then. During the course of a week or so (maybe less) I had done quite a few cache partition wipes hoping that it would fix the sound issue. I also tried calling someone, only to figure out that person on the other end couldn't hear me and I couldn't hear them. So, one of these days when I did the whole cache partition wipe, my phone wouldn't boot up. This is where it got stuck in a bootloop.
Events before the bootloop:
So yeah, my phone was stuck in a bootloop. If I remember correctly I used the "cache partition wipe" a lot and even opted for the factory reset option. Which didn't work out either. I finally opted to flash stock rom today but over the course of some days I have been trying a combination of "cache partition" wipe and factory resets. Of course, my attempts were in vain. SO, I decided to flash stock rom today. I found the firmware I needed and used Odin to flash it on my phone and that didn't work either, still stuck on the bootloop. I tried a factory reset and cache wipe after the flash as well.
Relevant images:
1- Screen I'm stuck on
2- When I go to recovery mode, first screen that pops up.
3- The so called update fails, second screen that pops up
4- and finally the recovery menu pops up
So yeah, that's it. I'm currently in the midst of my A level's, so my days are pretty hectic and stressful. I apologize for the long post, first time making a thread on XDA. Please help ;-;
maskimmortalsucks said:
Hello! My Galaxy note 5 (SM-920G) has been stuck on a boot loop for a week now, I've tried everything. I've used "wipe cache partition", "Wipe data/factory reset", even flashed stock firmware from sammobile using odin. I'm still stuck on a bootloop. I am gonna proceed to explain the events that occurred before and after the bootloop in a level of detail that I'm capable of, also one that I think should be sufficient.
Events before the bootloop:
So here's what happened. I was using my phone as usual when I noticed that I couldn't play any music. Spotify, which I was using at the time, refused to play any song. So, I checked out Phonograph(music app that uses local library) and I couldn't seem to play anything from my local library either. I then proceeded to go ahead and open YouTube only to realize that I couldn't play a video on YouTube either. After much fiddling (I don't remember what exactly I did that caused it) but a YouTube video played, but I heard no sound. From here on out, I could PLAY/VIEW any media related file and such but I heard no sound. I searched it up and apparently a cache partition wipe seemed to do the trick (I should have dug deeper into this but this is what I found). I proceeded to the recovery menu and selected "Wipe Cache Partition" (Forgive me, memories a little fuzzy from here on), If I recall correctly, I got into a bootloop and I wiped the cache partition again and it booted up fine. However, there was still no sound, since it was late at night I decided to give up and go ahead and sleep for now.
The next day, when I woke up, everything was working perfectly. I had no idea why.. but hey, I wasn't about to complain. Fast forward a few days, the sound issue popped up again, so I proceeded to wipe the cache partition again. I repeated this a few times but it didn't work, so I gave up. My phone was booting perfectly fine then. During the course of a week or so (maybe less) I had done quite a few cache partition wipes hoping that it would fix the sound issue. I also tried calling someone, only to figure out that person on the other end couldn't hear me and I couldn't hear them. So, one of these days when I did the whole cache partition wipe, my phone wouldn't boot up. This is where it got stuck in a bootloop.
Events before the bootloop:
So yeah, my phone was stuck in a bootloop. If I remember correctly I used the "cache partition wipe" a lot and even opted for the factory reset option. Which didn't work out either. I finally opted to flash stock rom today but over the course of some days I have been trying a combination of "cache partition" wipe and factory resets. Of course, my attempts were in vain. SO, I decided to flash stock rom today. I found the firmware I needed and used Odin to flash it on my phone and that didn't work either, still stuck on the bootloop. I tried a factory reset and cache wipe after the flash as well.
Relevant images:
1- Screen I'm stuck on
2- When I go to recovery mode, first screen that pops up.
3- The so called update fails, second screen that pops up
4- and finally the recovery menu pops up
So yeah, that's it. I'm currently in the midst of my A level's, so my days are pretty hectic and stressful. I apologize for the long post, first time making a thread on XDA. Please help ;-;
Click to expand...
Click to collapse
Was that Lollipop or MM 6 that you were on? In Download mode what does it say on that screen? Is FRP enabled?
P.S what country are you in?
Before flashing in odin do the format in recovery.
Sent from my SM-N9208 using XDA-Developers mobile app
MrMike2182 said:
Was that Lollipop or MM 6 that you were on? In Download mode what does it say on that screen? Is FRP enabled?
P.S what country are you in?
Click to expand...
Click to collapse
I could have sworn I replied to this... I can't seem to post any links here. I pm-ed the images to you! Frp was on, yeah. I was on Marshmallow. I live in the Maldives.
maskimmortalsucks said:
I could have sworn I replied to this... I can't seem to post any links here. I pm-ed the images to you! Frp was on, yeah. I was on Marshmallow. I live in the Maldives.
Click to expand...
Click to collapse
I'm pretty sure I replied to your private message already. On the picture you showed me it said the CSC was SLK and I gave you the link to the correct firmware for the device
You can also download the firmware to flash through odin here too.
https://samsung-firmware.org/download/Galaxy Note 5/9hs6/INS/N920GDDS2BPD2/N920GODD2BPC3/
You can't post any links because you don't have enough "posts" on here yet to prove you're not just coming on here to post some crazy links lol.
MrMike2182 said:
I'm pretty sure I replied to your private message already. On the picture you showed me it said the CSC was SLK and I gave you the link to the correct firmware for the device
You can't post any links because you don't have enough "posts" on here yet to prove you're not just coming on here to post some crazy links lol.
Click to expand...
Click to collapse
Alright so, my cousin somehow managed to get rid of the bootloop with some fiddling and the audio issues still remained. So, he tried to downgrade to 5.1.1 by downloading the firmware for it and the phone got stuck in another bootloop. Tried to flash 6.0.1 again and it didn't work, still stuck on bootloop.
I tried what you have suggested but I can't seem to get into the recovery menu.
maskimmortalsucks said:
Alright so, my cousin somehow managed to get rid of the bootloop with some fiddling and the audio issues still remained. So, he tried to downgrade to 5.1.1 by downloading the firmware for it and the phone got stuck in another bootloop. Tried to flash 6.0.1 again and it didn't work, still stuck on bootloop.
I tried what you have suggested but I can't seem to get into the recovery menu.
Click to expand...
Click to collapse
Already replied to your private message.
Can you not select this directly after odin...
Flush twrp for yours model go to recovery then wape os and every think then flush firmware by odin
Sent from my SM-N920C using XDA-Developers mobile app
I'm running CM12.1 on an international M7. It's been running fine for two years, but about six months ago it crashed and got stuck in a boot loop. Wiping the cache alone didn't help because it got stuck in an "optimizing app" boot loop, so I wiped data too to make it boot again.
Since then it has been difficult to install new apps from the play store. Sometimes it will reboot after installation of a new app. If that happens then then starting newly installed app will cause an immediate reboot again. After this happens, restarting will also give me a number of "Trebuchet stopped" messages. If I'm unlucky, then it will reboot into a boot loop again after installation and I'm back where I started.
Since the rebooting occurs with different apps and always happens first after the installation, I suspect the data gets corrupted. Which may mean the flash is defective.
Is there a way to properly diagnose this? And if it is a flash storage problem, is that even fixable?
Did a full reformat of everything and reinstalled it with Resurrection Remix. So far I have not had any problems.