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.
Related
Hello everybody,
I flashed today the Polish 4.4.2 and on every boot the phone starts off by giving me an error that "com.android.phone" has stopped working and for a while it's a bit laggy and sometimes Settings crashes too. My IMEI is alright and I also tried fixing by factory reset from both Settings and recovery. I reflashed many times and even tried the XEH Hungarian ROM which has the same problem. This was starting to get really infuriating so I flashed CWM (thus tripping Knox) and tried flashing this zip but to no avail. What's interesting is that if I remove the SIM card I don't receive the error anymore and the phone works as it should speed-wise. Also while having my SIM in the phone I noticed that it also takes a while before it manages to connect to my PC right after booting and when I try without the SIM then it connects much faster.
Other then going tomorrow to my carrier and changing my SIM what else do you recommend me to do?
Thank you for your time!
TwasBeats said:
Hello everybody,
I flashed today the Polish 4.4.2 and on every boot the phone starts off by giving me an error that "com.android.phone" has stopped working and for a while it's a bit laggy and sometimes Settings crashes too. My IMEI is alright and I also tried fixing by factory reset from both Settings and recovery. I reflashed many times and even tried the XEH Hungarian ROM which has the same problem. This was starting to get really infuriating so I flashed CWM (thus tripping Knox) and tried flashing this zip but to no avail. What's interesting is that if I remove the SIM card I don't receive the error anymore and the phone works as it should speed-wise. Also while having my SIM in the phone I noticed that it also takes a while before it manages to connect to my PC right after booting and when I try without the SIM then it connects much faster.
Other then going tomorrow to my carrier and changing my SIM what else do you recommend me to do?
Thank you for your time!
Click to expand...
Click to collapse
Did you dirty flash and keep data intact? if so you'll need to wipe and reflash, as KK has a different file system and can cause issues.
radicalisto said:
Did you dirty flash and keep data intact? if so you'll need to wipe and reflash, as KK has a different file system and can cause issues.
Click to expand...
Click to collapse
I already mentioned I reflashed and wiped countless times. At the moment I'm actually thinking of trying the Netherlands ROM.
TwasBeats said:
I already mentioned I reflashed and wiped countless times. At the moment I'm actually thinking of trying the Netherlands ROM.
Click to expand...
Click to collapse
You stated you factory reset, not wiped, the difference is data. - You could always trying wiping /system - but you'll need the PIT file incase you mess up the partitions, - Reflash it after a /system wipe. (PIT file is your fall back just in case) - If you're unsure about wiping /system then have a good read up on it, once you're confident then give it a shot, if not then don't try it.
radicalisto said:
You stated you factory reset, not wiped, the difference is data. - You could always trying wiping /system - but you'll need the PIT file incase you mess up the partitions, - Reflash it after a /system wipe. (PIT file is your fall back just in case) - If you're unsure about wiping /system then have a good read up on it, once you're confident then give it a shot, if not then don't try it.
Click to expand...
Click to collapse
I formatted /System, /Data, /Cache and /SDCard from CWM, after that rebooted in Download Mode and now I'm flashing again the ROM. If this doesn't work then I'm attempting the Netherlands ROM even though it's CSC is different then the Hungarian and Polish ROM.
Later edit: After another flash it still crashes. I'm going to try now the Netherlands ROM since it's been downloaded.
Later edit 2: Same story as before I wiped/formatted /System, /Data, /Cache and /SDCard from CWM, then flashed in Odin 3.09 the Netherlands PHN ROM and I still get crashes when it's booting. Tomorrow (it's technically today since it's 2:30AM lol) I'm getting another SIM. Hope this will be the solution still if anybody has any idea what else I can do I am more then welcome to hear your ideas.
It seems changing my sim solved the issue, which is odd because the old sim wasn't even old enough. Out of this whole ordeal I lost my Knox 0x0 status and 12$ for a new sim. Thank you Samsung for implementing Knox and making my life easy!
TwasBeats said:
It seems changing my sim solved the issue, which is odd because the old sim wasn't even old enough. Out of this whole ordeal I lost my Knox 0x0 status and 12$ for a new sim. Thank you Samsung for implementing Knox and making my life easy!
Click to expand...
Click to collapse
Nice, the typical "I messed up my device, but I am not at fault. The manufacturer is responsible" attitude.
I'm sorry, I wish I could help you
Well this is my 1st post so first of all hey everyone
I just spent a week in Amsterdam and my phone restarted twice, different times different days and I dont remember what I was doing with it back then.
But as I landed back home I put the phone back from "Airplane Mode" and went on to toggle "Cellular Data" on.
The second I pressed the cellular data shortcut on my the phone restarted itself but this time whenever it would finish the screen would be on but fully black and sometimes it'll show battery precentage at the top but then will restart again in an infinite loop.
Sometimes it'll pop up the "Optimizing Apps" window and will go through all 24, upon finishing it will restart once more and do the same.
I tried using the bootloader and it worked (the bootloader that is) but the phone would do the same thing even after Rebooting from there or shutting down from there and then turning back on.
I contacted tech support on chat but they couldnt help past telling me to go to bootloader and reboot, said I should factory wipe when it failed.
Also tried wiping cache but to no avail.
I have no backup of my phone (wanted to do one before the flight but got lazy and I suck for not doing one sooner) since probably October and google doesnt backup my contacts properly for some unknown reason.
I already downloaded Android Studio with everything included for me to try using adb to sideload stock without wiping but its my first time and I couldnt get it to do anything at all...
I already got the official stock .gz file from the motorola website.
Anyway here are the specs to my phone:
XT1575
Everything is stock. didn't root or change recovery once in my life.
Was fully updated and had plenty of drive space (I have almost 128GB with the 64GB version + 64GB SD)
I'm really lost here so help will be very appreciated.
Thanks in advance,
-Noam
Start with a full wipe and if that doesn't work flash the stock image. Not sure what your question is though as you never really say. Once fixed I would unlock and make a backup so you don't have to deal with this again.
lafester said:
Start with a full wipe and if that doesn't work flash the stock image. Not sure what your question is though as you never really say. Once fixed I would unlock and make a backup so you don't have to deal with this again.
Click to expand...
Click to collapse
The thing I pretty much want to know is if theres a way to either backup the phone now with it connected to the computer while in bootloader or recovery. or a way to flash the stock rom without wiping which I read someone did with his tablet. I cant post source normally because I'm a new user so here it is but change spaces to dots: schnouki net/posts/2014/08/13/flashing-a-stock-android-image-without-wiping-user-data/
Also while in recovery I noticed 2 options under wipe: 1. userdata only. 2. userdata+(insert something I dont remember here) and I was wondering what gets deleted in both? if I delete only userdata what data will remain? something helpful?
Sure you can try flashing without wiping data but being locked I personally wouldn't risk it. No idea about backing up in your state... somewhere I remember a thread on backing up without root try searching in q&a.
lafester said:
Sure you can try flashing without wiping data but being locked I personally wouldn't risk it. No idea about backing up in your state... somewhere I remember a thread on backing up without root try searching in q&a.
Click to expand...
Click to collapse
Out of curiosity why shouldnt I try flashing with no wipe if ill lose the data anyway? worst case wont I just have to wipe after it fails and flash again?
And I will try thank you
Do you have any knowledge about the 2 wipe options?
Thanks in advance
Well I tried turning the phone on and it took a couple of minutes before loading to a fresh start. It apparently wiped itself on its own. Managed to restore almost everything.
Anyhow the phone takes too long to boot now. Was even stuck at boot and I had to restart it.
Anyway to fix my software? Or at least check for corruption?
Sent from my XT1575 using XDA-Developers mobile app
Hey all,
First post here on XDA and I'm hoping someone with more experience than me will be able to give me a hand! Until last week or so, I was running an up-to-date version of Lollipop (5.1.1), when my tablet started randomly freezing up on me, requiring "soft resets" to get it going again, or simply shutting off on me. Thinking it was software related, I tried wiping the cache with no success, so ended up doing a full factory reset. The issues *seemed* to clear up for a day or so, but came back, and so figuring it was Lollipop related, I wiped out the OS and installed CM12.1 (which was my first experience working with ADB and fastboot, and first time installing a non-stock ROM) with a TWRP recovery. A few days later, the freezing and shutting down issues began popping up again, with the shutdowns *usually* happening during sleep, but the freezing happening at anytime from initial "Google" logo to boot animation, to the middle of running an app. I had made a backup on TWRP when I got CM12.1 configured the way I wanted it, so I performed a soft reset when it froze on me, and booted into the bootloader. The tab kept freezing in the TWRP window before I could select a restore, so out of desperation I tried just doing a factory reset from within TWRP. Long story short, something must have happened during that reset, because it kept hanging on the boot screen. I thought I may have unknowingly messed something up, so I tried downloading and flashing a stock KitKat (4.4) ROM from Google's site, but kept encountering bootloader errors during the flashing and ended up only being able to boot to the bootloader screen (apparently got a faulty 4.3 bootloader in that ROM, which gave me a headache until I was able to get straightened out). I have been able to get a stock bootloader (4.23) up and running now, along with a stock recovery (going with Lollipop now, so stock for LMY47V) going, but that's it. I've tried flashing the stock lollipop image via shell script (I'm running a Fedora 23 machine), via individual commands, and via "fastboot update -w factory_image.zip" without success. ADB sideload still works via recovery, but I wasn't able to sideload the OTA packages for 5.1 either. The common errors that pop up seem to indicate an error (corruption? fragmentation?) on the cache partition, but I'm not a dev when it comes to Android, so I'm at a loss here... I keep getting "E: failed to mount /cache (Invalid argument)", and other errors associated with accessing/opening files further down the /cache tree. Would this error be more likely to be a hardware issue, or would it be a software/firmware issue? I've had similar errors before with USB drives, when they would start to bad and partitions begin failing, but have always been able to rebuild them and get my data back. If something like this is happening on my N7 and the cache partition has indeed become somehow corrupted and failed (but not physically....), is it possible at all to rebuild partitions on Android in a similar manner? I've scoured the web, but haven't been able to find anything that can help me out with something like that, so I figured my best bet before condemning the N7 to the junk drawer was to see if any of the pros around here had any words of wisdom that *might* get me back up and running. Thoughts and advice much appreciated!!
Thanks!
(Oh, I apologize for the lengthy post, but I wanted to be sure to provide enough background info..... Sorry for the lengthy read!!)
Honestly that sounds more like a hardware problem than a software problem.
During the early stages of booting, everything that happens is extremely deterministic - meaning that it should be completely repeatable in terms of the order & timing in which activities occur.
So, for it to behave erratically during early boot suggests that it is not software, but marginal hardware. If hardware is barely meeting logic levels or timing requirements, a small amount of random noise (which is always present) can cause a fault to occur at any time - and that sounds approximately like what you are observing.
Further, you replaced your ROM entirely and the problem persists - again suggesting that the problem is hardware, not software.
The most cost effective way of dealing with repair of a $200 tablet is - unfortunately - disposing of it and buying a replacement.
Sorry.
Thanks for the reply!! Shoot, that's what I was leaning towards too. What is the life expectancy of these tablets? I mean, I got 3 good years of use out of it, so I'm not going to complain, but it seems like they should have lasted longer... Would it be worthwhile to maybe grab a cracked screen N7 off eBay for parts and try to get my tab working with those parts maybe? I'm hoping the rumors are true about Google coming out with a new tab this fall, but I'd love to get mine working before then lol...
This is on two standard Galaxy S5's, with standard ROM, etc - not rooted, or anything else.
Every time I turn off WiFi, or enable Mobile Hotspot, I get 'Unfortunately System UI has stopped'.
To fix I have to Power off/on the phone.
(Turning on WiFi is no problem, just turning it off.)
I have gone into 'Safe Mode', and same issue, so it looks to not be a bad App.
I have also uninstalled 'Google' updates, and again no change...
Any thoughts?
All of a sudden my S5 showed the exact same error message for no aparent reason... I didn't do anything, and now I can't use my phone at all because of that bug. It happens on every boot so I can't even unlock my phone. Tried reinstalling everything, ROM, recovery, kernel, with/without root = still same, what just happened here??
EDIT: Same thing if I'm in Safe Mode -_-
Seeing noone knows a solution here's what I did yesterday.
1. Backed up all my stuff from internal storage to the sd card
2. Did factory reset in TWRP recovery
3. Flashed completely stock official firmware from Samsung
4. Waited for it to boot up and try to restore some of my settings (it restored all folders on their places, made same amount of home screens as I had before the reinstall and downloaded all of my previously installed apps from the Play Store, ofcourse without the cracked ones, and it also restored most apps' data as well so it's not as bad as you may think to factory reset and reinstall everything)
5. Started rooting, flashing TWRP again, installing Dolby Audio, Xposed and everything I had before, took me one full day to set it up as it was before.
Now when I set it up I always make a nandroid backup from when things are working fine, in case it goes crazy for no reason again... Good luck!
when the wifi radio is acting weird, a dirty flash of your current ROM susually fixes is as its probably a radio issue. Id do that before doing anything drastic like the boot-n-nuke Odin flash and starting from scratch (which will fix that issue)
I don't think I have a ROM issue, as I have two S5's, and both have the same issue... and both are standard ROMs.
I will do a factory re-set on one at some point, but this looks to be a 'simpler' issue.
I have tried a full Cache delete, as well as other 'clean' processes.
Nothing works.
I tried to re-flash my stock ROM as @youdoofus said but still had that annoying popup. Try everything you can think of, if all else fails, reset.
koragg97 said:
I tried to re-flash my stock ROM as @youdoofus said but still had that annoying popup. Try everything you can think of, if all else fails, reset.
Click to expand...
Click to collapse
well, you can wipe cache, and dalvik 3x each (not kidding about the 3x each), then dirty flash the rom, pray to the gods of android, reboot. If failure occurs, its Odin Nuke time unless you want to try to flash an individual radio file by itself (not recommended)
Good morning.
After almost 3 years with no problems with a XT907, I have again an issue with it (this time, my father's one). Again, I come to you requesting help.
It all started with all apps crashing over and over. With an old XT907 I have for emergencies, the common fix method is flashing VZW_XT907_4.4.2-KDA20.62-15.1_1FF.xml.zip with RSD Lite v6.1.5 and all solved.
I tried that method with my father unit, and when it started again, all process were still crashing. I thought it was still nothing (just a harder issue), and tried flashing VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF_SVC.xml.zip, just deleting all his data, to fix it.
When the process ended, it turned on and it had still the same problem. In this point, I got worried the /system and /data partitions got locked
I re-started, went to stock Recovery, and wiped system and cache. Then, went to Fastboot a third time and tried again flashing VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF_SVC.xml.zip. Guess what? Still the same problem
The phone turns on, but ALL apps keep crashing over and over. I can't even take an screenshot, as it immediately reboots.
Someone know what happened with it? And... how to fix this issue?
To make things worse
Fastbook Locked
No Root
Last 4.4.2 stock ROM
by twrp try make Wipe Data Or Repair File System, if not done mybe your internal memory Currpted