E: failure to find/misc partition after cache wipe - Samsung Galaxy Tab A series Questions & Answers

I came across this error on my Tab A 10.1 (SM-T580) after doing a cache partition wipe a few days ago. It is listed all the way at the bottom of the recovery screen just after the confirmation of the cache wipe being completed (cache formatted/wipe completed is listed twice).
I did upgrade to Nougat earlier last week and, other than this error notification, the tablet seems to be performing flawlessly.
Should I be concerned?
Thanks!

Twisted_Samsung said:
I came across this error on my Tab A 10.1 (SM-T580) after doing a cache partition wipe a few days ago. It is listed all the way at the bottom of the recovery screen just after the confirmation of the cache wipe being completed (cache formatted/wipe completed is listed twice).
I did upgrade to Nougat earlier last week and, other than this error notification, the tablet seems to be performing flawlessly.
Should I be concerned?
Thanks!
Click to expand...
Click to collapse
Hey there, i've got this problem too. I've searched the whole google to find something but no luck. Just other people facing this issue. So in my conclusion it is a Nougat bug because after downgrade to Marshmallow this message dissapears. Maybe further updates will fix it.

Thank you for responding! I was considering a factory reset, but being that my tablet is apparently showing no other problem, and that it could very well be a Nougat bug, all I can do is wait for an update.

Related

Can't mount sdcard/data/system in CWM. Solved.

Hello,
Firstly I want to apologies for creating new thread for a thing on which there already number of threads here. However when I was in this big trouble (at least it was for me) on Saturday evening I searched everything and couldn't find a working solution.
And I would like to request moderator or someone who has better knowledge of what did happen and how it got fixed can make it guide with his thoughts if there is a need to .
Let's start with my story. I unlocked bootloader first time and flashed CWM. While restarting I tried to wiped data as told in one of the tutorial and then I restarted. As long as I remember it said you would not be able to boot in CWM again and I said Yes. That's the time when it got stuck to X logo. I flashed CWM again and then tried to restart still nothing happened. I got further and flashed CM 10.1.2.
Then it got stuck to CM logo. I wiped cache, data, dalvik cache before and after; nothing helped. Then I managed to Power off phone and planned to go for sleep. I thought I have ruined my phone
This is how I fixed it:
At the last moment I thought to give it a last try before sleeping. I could not have went to sleep with that I thought Then I rebooted my Nexus 4 in CWM and went to 'Mount and Storage'. Mounted everything which were in unmount state. Formatted data. Went back a step then wiped data. And restarted. And there it got rebooted in CM 10.1.2 :highfive:

[Q] Problems with Process System on PA 3.98

Hi!
I recently updated my ROM to the Paranoid Android 3.98, I did a full wipe, flashed the ROM, latest Gapps (with TWRP) and ever since the tablet has been become really laggy on opening apps or doing anything. I realised something was wrong straight after I booted it up by how long it was taking to connect to the WIFI etc.
Anyway, its hanging a lot on the unlock screen and sometimes I get a "Process System is not Responding" prompt. I've tried going back into recovery and clearing the caches/data again and its still hanging. Ive also tried using CWM recovery to wipe the tablet, flash the ROM/Gapps etc and its still really slow. Lastly, I just tried a factory reset from the settings menu and again, its still the same!
Any ideas on whats up with it and how to sort it out? I was thinking about unrooting it back to stock although I think the problem will still probably happen. I came from the PA 3.95 build and did a clean flash.
Cheers!
Chris
I think I have fixed it by following a post by Chasmodo on how to do a super-clean install.
1) I booted into recovery.
2) Did the three wipes (Data, Cache, Dalvik) several times over.
3) Went to Mount & Storage and formatted both system & cache*.
4) Flashed PA 3.98 & latest PA-Gapps.
5) Wiped both caches again and rebooted.
As soon as connecting WIFI, signing into Google I could tell it was running a lot faster again and now the lag on the unlock screen & opening apps seems to have stopped, also haven't had the "System Process isn't Responding since."
*Chasmodos version of the super-clean install didn't say to format the cache as well although I had tried just formatting the system and it didn't fix the issue. So I thought I'd try the same process with a cache format as well and now all issues seem to have been rectified.
Cheers
Chris

[Q]Omni Xoom Wingray boot problem

I recently rooted and installed OmniROM on my Xoom, but am having problems getting the tablet to boot. It makes it past the moto screen, but gets stuck on the blinking omni logo.
I followed the instructions in this thread, but I can't seem to get it to work. I have tried the entire process twice, and tried omitting gapps and even the update. Anyone have an idea what I am doing wrong?
If it means anything, TWRP is unable to wipe Dalvik, data or Internal Storage.
Thanks in advance!
Okay Scratch that. I did a reformat/reinstall and it finally booted. Now I just need to figure out that Text To Speech engine error.:good:
I have the same problem but with the Everest version
I have gone back to Gingerbread then back to EOS4
What did you do to reformat?
Did you successfully manage to wipe the dalvik cache and data etc?
OK in case anyone else had the problems I had then this repartitioning guide helped me. It was slightly different than the guide here, ie not just a wipe everything and expect it all to be ok kinda thing.
I was running my Xoom with the last EOS build and had an earlier version of TWRP. I started by upgrading in recovery to the NonBigPart TWRP and then followed the instructions from this link to repartition format etc and it worked for me.
http://forum.xda-developers.com/showthread.php?t=2506997
Same Problem - can you explain more?
Zaxxon8 said:
Okay Scratch that. I did a reformat/reinstall and it finally booted. Now I just need to figure out that Text To Speech engine error.:good:
Click to expand...
Click to collapse
I have the same problem. Can you explain what you mean by "a reformat/reinstall and it finally booted"? My Xoom is stuck on the Omni Android screen with the android blinking, but will not finish loading. My advanced wipe did not wipe all and I received a failed message. I'm guessing that is my issue, but I'm not sure what to do about it. Any help would be appreciated.
cagerbrandt said:
I have the same problem. Can you explain what you mean by "a reformat/reinstall and it finally booted"? My Xoom is stuck on the Omni Android screen with the android blinking, but will not finish loading. My advanced wipe did not wipe all and I received a failed message. I'm guessing that is my issue, but I'm not sure what to do about it. Any help would be appreciated.
Click to expand...
Click to collapse
Okay. I found out what to do. Thanks though. Persistence works.
Seriously? Can't anyone explain what they did to fix the problem? You guys are pretty quick to ask for help, but don't even take the time to explain what you did to people who have the same problem.
If there's anyone with the same problem, the solution is to go to the wipe option and instead of using advanced wipe, just use format to delete all internal storage, then reboot and clear dalvik cache, etc. then flash omni, gapps and superSU (in that order), then reboot and wait a few minutes on the omni loading screen and its done.
I am struggling to get past the blinking omni logo, tried all ways to get this to boot, am i missing some thing

FE rebooting constantly after update. Ideas?

FE is rebooting every minute after recent Dec. update. Cleared delvik cache and says "can't find /misc partition." from reading it seems clearing everything to reset will cause the phone not to start so am waiting. if some way not to lose everything I'll try that first.
Seems the only answers are:
1) ignore it, that error doesnt matter anymore. Some can. Except many wipe data and then can't restart anyway.
2) ‎others say Samsung replaced their phones (or replaced the board) because unfixable due to some weird hardware-update Matrix electro-wedgie.
3) ‎people tried to rebuild /misc and was a nightmare that didnt end with anything beside tears.
I was first thinking I could just re-do the last update and be all good like a normal update.. But that doesn't work I think tho not sure why. If so, how so?
Thank you, good sirs.
-Please respond as tho talking to your mom or a small child. Thanks
You can try flashing stock firmware in Odin.

8.1 - Unable to unlock after cache wipe

I have an old 6P that I haven't used for a few months. Noticed it was running slower than usual. Deleted apps, a few pictures, and rebooted it. Still slow.
Wiped the cache, when I woke it up it asked to unlock before continuing to screen. Proceed to connect the dots...which I've been doing for a day or two now.
Some reason it doesn't accept my password, it keeps saying wrong pattern even though I've been using it for a day or two.
Any suggestions? 8.1. updated this week.
If your rooted and have twrp can always try this. Kind of strange don't know how erasing cache could change your security. Did you update from Nougat to Oreo? I always do a factory reset especially when upgrading to a new Android version . Avoids possible issues down the road . ?
Exodusche said:
If your rooted and have twrp can always try this. Kind of strange don't know how erasing cache could change your security. Did you update from Nougat to Oreo? I always do a factory reset especially when upgrading to a new Android version . Avoids possible issues down the road .
Click to expand...
Click to collapse
8.0, then updated to 8.1. Still pretty slow, so rebooted. Still slow. Deleted stuff. Cleared Cache. Now some reason it doesn't take my pattern...which I used all day. So confused, legit feel crazy.
I rebooted it and now it won't recognize the pattern on boot. It's saying it's going to wipe it after X number of attempts.
I actually got rid of twrp after 7.1.1 fearing it might've caused issues w/ 8.0 OTA...

Categories

Resources