Hello, I have a Xiaomi Mi Note 3 that has crashes contants. I have already installed several roms and the crashes continues. Is there any way to erase (delete) the entire partition and partition everything again to see if it eliminates the problem?
I think it's physical, but I wanted to try.
Related
Hi all,
Just here hoping one of you who is proficient in these matters can be an absolute legend and help me out.
Ever since I had my Moto G I've had trouble with making nandroid backups - it always fails at the /data stage. In addition, I have only been able to get into recovery via adb reboot recovery. Formatting /data in recovery makes no difference.
I've also had trouble with -24 errors on installing apps. I'm aware that the solution is to delete the previous installation files from /data/data, but I am unable to delete them! (I can rename them as a workaround, but it's not a proper solution.)
All of this leads me to think that the /data partition has become corrupted. Is anyone else having this problem, and do any of you have any possible solutions? I'm still hoping that this fixable via software and isn't a hardware fail - like any xda-er, my warranty lasted literally seconds...
Thanks in advance!
I'm no proficient expert, but have you tried reflashing the stock firmware? If you want it, you can get it here http://forum.xda-developers.com/showthread.php?t=2542219 IT WILL DELETE EVERYTHING FROM YOUR PHONE. Good luck buddy!
Sent from my Moto G using XDA Free mobile app
I have indeed, it failed to flash! Downloaded a few times, and the md5 always checked out, so the file was solid.
CM11 flashed ok, and currently on Sk.D's excellent stock-based rooted Rom, but the problem persists.
Sent from my Nexus 10 using Tapatalk
Had a similar problem with the same Google play error after an abrupt low battery shutdown. Not a moto g but using titanium's batch action for removing orphan data fixed the app issues. Just be careful you Don't delete data you might want to restore later.
Sent from my SGH-T679 using Tapatalk
interessant said:
Had a similar problem with the same Google play error after an abrupt low battery shutdown. Not a moto g but using titanium's batch action for removing orphan data fixed the app issues. Just be careful you Don't delete data you might want to restore later.
Sent from my SGH-T679 using Tapatalk
Click to expand...
Click to collapse
Thanks but no luck - Titanium reports a success but the data is still there! Must be something up with the partition...
Looking at some other threads, some people on other devices are using the e2fsck command to check the integrity of the file system.
Can anyone walk me through this - syntax of the command as well as which block the /data partition is mounted as?
I has the same problem. I can't delete one file and format partition data keep failing. Until now nothing works: re-stock, adb delete, fastboot erase and recovery format.
Have you tried flashing the GPE stock firmware since it has a different partition table than normal and is ext4 compared to f2fs on normal moto g
Hello everyone!
I've some serious problems with the size of sdcard seen from OS. I don't know exactly how but, within a flash and a restore, now my 32GB N5 shows only 12,8GB, like data partition has wrong size. I have to mention that I was using MultiROM with 2 ROM in dual boot, but now installing the it doesn't whow any secondary ROM.
I've already tried to erase data, restore to stock etc. Nothing seems to work.
Any idea how to solve?
Please use the search button. This has been answered 100s of times.
OK, after many different tries, FORMATTING (non erasing) the Userdata partition via Fastboot worked.
Check as solved.
STRANGE BUT, when I recover photos from "userdata" partition with various recovery apps / PC software I get bunch of images but not one from camera.
If I edited/cropped or sent to email which caued photo to be saved by some other app it will be recovered. How is this so ???
-------------------------------------------------
Details : OnePlus One bought with CM11, OTA upgrade to CM12.
One day GSM radio stopped working. Its not SIM card isssue, or network coverage.
Tried varius stuff I could find, in desperation decided to make factory reset to see if it is helping, if not then flash OxygenOS and see if it is working.
So my **** up is that I remembered to backup photos after unlock bootloader which wiped the phone.
I tried various apps for recovery of photos directly on phone, then I tried Dr. Fone and EaseUS android recovery (only two that I found that can do recovery of lolipop OS with only Internal Storage), they require rooted phone and ADB interface, so I did everithing.
At the end I made DD raw copy of "userdata" partition and scanned on PC with Recuva, PhotoRec and at leaset thre others (ext4 specific)-
Every time I recovered more or less the same images and I get bunch of images but not one from camera.
What is s special about these files ????
They are just JPEGs on that same partition where recovery software found other files/images.
Hi, i have a problem with lost data and I'm trying to make a raw copy.... How did you do that?
Thanks
Enviado desde mi A0001 mediante Tapatalk
I have a Mi K20 and tried to find a solution to my issue on the device's sub forum. So far, I've only found a few people who are currently dealing with the same issue I'm facing. I think what caused this to happen was failing to disable verity and force encrypt before reboot after flashing a MIUI 11 ROM for our device. Right now, it takes over an hour to access TWRP, data is stubbornly encrypted so I can't format it with mkfs.ext4 or f2fs because it always hangs, formatting on TWRP doesn't do anything but make me wait 30+ minutes for failure, fastboot erase won't work because of the encryption, mkefs doesn't work, and my internal storage is gone. I've also tried a dd trick I picked up from Stack and it didn't do anything. Does anyone know of a way I can just nuke the data partition using some other commands?
My UIS7862 based unit (Atoto S8 Ultra) started a nasty habit of randomly hard resetting itself every few weeks. Once it happened even while driving! It was working fine for 9 months but once it started, it has been a pretty consistent problem.
Support has not been helpful, I'm trying to understand if this is hardware or software. I already tried leaving out third party launchers, and keeping applications down to a minimum in case any of that might be a culprit (sticking to just installing basics like Spotify). Still reset itself after a few weeks.
Support has sent me firmware updates which did not help, and obviously I also tried doing a factory reset myself (in case something needed to be cleared out and start over fresh). I was starting to think perhaps there's a hardware problem that is shorting out the storage chips or something. But I just noticed today while poking around that the internal storage still has remnants of my first setup. I see folders from apps I have not installed since before the first reset, and even some media that I downloaded and screenshots I had taken!
Please excuse my lack of experience in understanding this, but I understand that data and memory/storage are different partitions. So it seems only data is being reset, but not memory/storage, since my files are still there from many flashes and factory resets ago.
Does it make sense that a hardware fault would ONLY be resetting the data partition but not the rest of the memory/storage? Or is that a logical partition, which would imply that the problem might actually be software related?
to me it sounds wrong. on android usually only a single partition is writeable. it should never factory reset itself.
I could imagine a file corruption or a inconsistency in file system causes broken encryption, so on unsuccessful boot the android format userdata partition automatically (if the ROM is designed to do this without your confirmation).
But as you stated there are still user files existing, there must be another storage or at least another partition.
Both is very unlikely, but I don't know that ROM. if you have the possibility to install terminal emulator, you can check what partitions exist with df
A factory reset should really wipe everything. If that is not the case the FYT units obviosuly do not do a real factory reset, but I personally never tested this.
The super partition, has the system, product, vendor and a few more partions. All are read-only and only writable on on a new flash.
Next to that is the data partition and the "external SD storage". They are writable.
So again: A factory reset should wipe the data partition and the SD-storage, not the system, product and vendor partition. So it is strange that data remains on the SD storage..
And that the data partition is wiped "regularly" is completely incomprehensible. If it is "simply" corrupt, so a file system corruption, a complete full flash should repair it. If there are really bad blocks on your internal memory then that wouldn't know if a full flash would fix that. In normal SSD usage this is monitored. I do not know for the EMMC memory in those units.
Anway: Did you ever do a "test only" flash?
Only the lsec6315update binary with only the updatecfg.txt containing only the word "test"? (test without the double quotes)
surfer63 said:
A factory reset should really wipe everything. If that is not the case the FYT units obviosuly do not do a real factory reset, but I personally never tested this.
The super partition, has the system, product, vendor and a few more partions. All are read-only and only writable on on a new flash.
Next to that is the data partition and the "external SD storage". They are writable.
So again: A factory reset should wipe the data partition and the SD-storage, not the system, product and vendor partition. So it is strange that data remains on the SD storage..
And that the data partition is wiped "regularly" is completely incomprehensible. If it is "simply" corrupt, so a file system corruption, a complete full flash should repair it. If there are really bad blocks on your internal memory then that wouldn't know if a full flash would fix that. In normal SSD usage this is monitored. I do not know for the EMMC memory in those units.
Anway: Did you ever do a "test only" flash?
Only the lsec6315update binary with only the updatecfg.txt containing only the word "test"? (test without the double quotes)
Click to expand...
Click to collapse
No I have not- what does test do?
I did try the twipe all on the last one and it seems to have not reset itself again since (fingers crossed that it stays that way! It's been a few weeks but that's about how long it lasted between resets last time).
Where can I read more about the test function of the flash?
dishe2 said:
No I have not- what does test do?
I did try the twipe all on the last one and it seems to have not reset itself again since (fingers crossed that it stays that way! It's been a few weeks but that's about how long it lasted between resets last time).
Where can I read more about the test function of the flash?
Click to expand...
Click to collapse
Oh come on.
I have already pointed you a few times to my "General FYT based Spreadtrum uis7862 (unisoc ums512) - Q&A, Mods, tips, firmware".
It is described there. In this case in post #2.
surfer63 said:
Oh come on.
I have already pointed you a few times to my "General FYT based Spreadtrum uis7862 (unisoc ums512) - Q&A, Mods, tips, firmware".
It is described there. In this case in post #2.
Click to expand...
Click to collapse
It says there it tests the firmware. I knew that from the title already. I was wondering if you have more details than that but it's ok. I don't want to annoy you.
dishe2 said:
It says there it tests the firmware.
Click to expand...
Click to collapse
No it does not.
It says: test unit and firmware before flash
Also the unit will be tested