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
Related
Code:
[B]E:unknown volume for path [/sd-ext] [/B]
This is the error I get using Revolutionary and am flashing a new rom using the 'correct' method spoken of here.
This error message occurs after I've wiped Dalvic Cache. The phone still performs as normal without any issues. But I'd like to get rid of this error if i can.
Can anyone help with this or has anyone had or seen it before?
BigPickle80 said:
Code:
[B]E:unknown volume for path [/sd-ext] [/B]
This is the error I get using Revolutionary and am flashing a new rom using the 'correct' method spoken of here.
This error message occurs after I've wiped Dalvic Cache. The phone still performs as normal without any issues. But I'd like to get rid of this error if i can.
Can anyone help with this or has anyone had or seen it before?
Click to expand...
Click to collapse
Try re-formatting the sd-ext partition using 4EXT recovery. Failing that, backup your entire SD card contents and re-format the whole thing, then copy your files back. I had a 512MB EXT3 partition on my card for ages from my old Desire days and A2SD+ ROMs. Never got your message but that's what I would try.
Isn't that SD partition? I also have that (when flashing, or doing backup) and I thought it was normal coz I don't have partition of my SD.
BigPickle80 said:
Code:
[B]E:unknown volume for path [/sd-ext] [/B]
This is the error I get using Revolutionary and am flashing a new rom using the 'correct' method spoken of here.
This error message occurs after I've wiped Dalvic Cache. The phone still performs as normal without any issues. But I'd like to get rid of this error if i can.
Can anyone help with this or has anyone had or seen it before?
Click to expand...
Click to collapse
Thanks for your answers guys.
@wnp_79 I always format my sd card when i flash a new rom.
@MarlIX I'll try formatting again and making a partition using the whole sd card size to see if it solves it.
I guess that it depends on situation in which you're extending main partition with SD card (as HTC Desire users have to do in order to install ROM which doesn't fit on internal memory). In normal cases you'll have such warning because you don't have extended partition on SD (But someone please correct me if I'm wrong)
ah ok so i shouldnt worry about it then really unless the rom i want to flash requires extended partition?
I can make a partition on Revolutionary i get these options 128m,256m,512m etc etc and then i brings up a menu saying swap size 0m,32m,64m,128m or 256m.
Any guesses on the best way to set my card up?
If you are not using it then use either choose the smallest size, our use 4ext recovery to remove it.
Whenever i did it, a 0MB swap was just fine.
Sent from my HTC Desire S using xda premium
I see an option to remove all partitions and start from scratch so next time i flash i'll select that and maybe that will sort it out.
So I installed the latest wingray ICS nightly for my xoom, #48 and after that it wasn't responding so I went to restore from a nandroid backup. After the backup I noticed that none of my apps where there so I did a factory reset and it's giving me the error in the title. It gives me the same error with anything that has to format /data. I managed to delete the file but it seems to appear again when I try to format. Some help would be appreciated because I'm out of ideas. I'm using the reccomended recovery and everything like that, nothing fancy, I just had the rom and Gapps installed and it had all worked fine up until that point.
Thanks
Well I ended up using fastboot to format it. Got rid of everything on my sd card but at least I can use my xoom now. Still wondering if anyone knows why that happened or a better way to deal with it next time if it happens again.
GET YOUR DATA /data/media WITHOUT loss: error in /data/system/packages.xml format
did you try using adb pull C:\xoommedia /data/media/ ? that wouldve recursively grabbed it all.. i had to do something similar recently.. so long as the partition isnt corrupt it can be pulled recursively using adb pull command and dumping it into a local directory. i pulled my data, then tried using eraseData in /sdcard/clockworkmod/ as solarnz mentioned in the clockworkmod thread but that still didnt format /data fully to the point of rewrite so i did like you and fastboot -w ..
sorry i realize this may have come too late but hopefully it will help someone else.
if this ever helps you hit thanks! thanks!
I actually had it working enough that I could transfer files from in the actual OS. Forgot to copy over my wallpapers though Ah oh well. Thanks anyway
mz601 same xml error
What fastboot commands did you use ? Help can't install properly ..no market ..arrrrrr
fastboot erase userdata
It'll format your entire internal sd
"Error removing /data/system/packages.xml"
I had the same exactly on this file.
In CWM, Factory reset didn't work, restoring a backup neither, only a lower level operation with fastboot did the trick
Probably ext4 corruption?
My problems began when the tablet started rebooting while being in market..
h ttps://github.com/TDR/android_bootable_recovery/blob/stingray/roots.c#L302
ret = remove (path) returned -1.
remove() from stdio.h:
On success, zero is returned. On error, -1 is returned, and errno is set appropriately.
Adding a display of errno could help. Or fsck before formating?
P6800 running Zeta
I was browsing facebook the other night when... shaboom - everything froze. No biggie I thought, I'll just do a little reset (I was getting a few FCs here and there anyway lately) and I'll be good to go...
NOPE. It started bootlooping at the initial Samsung Galaxy Tab 7.7 screen. I'm able to enter CWM recovery and even wipe the cache and flash ZIP files, but when I try to wipe data/factory reset, wipe the Dalvik cache or restore a Nandroid backupI get a System Error. It doesn't look good.
Is there a way to fix my seemingly funked /system without losing all my internal SD card data (where my Titanium backups reside) or to recover it before a full Odin flash?
Just tried again - it reboots and goes into a loop when I try to wipe data and dalvik, and when I try to restore a previous backup it gives me "Error while restoring /system!"
Any help greatly appreciated before it becomes a $600 door stop
Do you dare to wipe the system folder and follow by flashing another ROM?
Sent from my GT-P6800 using xda app-developers app
iena said:
Just tried again - it reboots and goes into a loop when I try to wipe data and dalvik, and when I try to restore a previous backup it gives me "Error while restoring /system!"
Any help greatly appreciated before it becomes a $600 door stop
Click to expand...
Click to collapse
ok... try go long way... download old HC stock rom and install that... then try go to stock recovery in hc and wipe your data
Thread moved to Q & A section, post in the relevant section next time.
edan1979 said:
ok... try go long way... download old HC stock rom and install that... then try go to stock recovery in hc and wipe your data
Click to expand...
Click to collapse
Do you mean via Odin? Will I lose the data on my internal SD card by doing that? Is there any way of mounting the device in its current state as external storage on my PC to copy all data before a wipe?
ZhenMing: I'm not sure what you mean, but as I wrote above I am not able to wipe the system folder.
yes you will loose your data... i can give you another advice... but do this one carefully... the reason why your device cant wipe any /system or /data is because the corrupted partition... you need to check it... follow the guide in this thread...
USE ONLY PART 3... follow the guide start from this para to check your device...
Code:
Now we are going to use e2fsck to check our new partitions for errors, but not only, it also fixes some erros and it will even for example create lost & found in /data
So let's go, we'll begin with /system. If you're still in the (parted) shell, use ctrl+c and type "adb shell", then issue the following :
http://forum.xda-developers.com/showthread.php?t=1862294
iena said:
Do you mean via Odin? Will I lose the data on my internal SD card by doing that? Is there any way of mounting the device in its current state as external storage on my PC to copy all data before a wipe?
ZhenMing: I'm not sure what you mean, but as I wrote above I am not able to wipe the system folder.
Click to expand...
Click to collapse
Since you can go into cwm, you can mount your storage and then connect to PC to copy all you want.
edan1979 said:
yes you will loose your data... i can give you another advice... but do this one carefully... the reason why your device cant wipe any /system or /data is because the corrupted partition... you need to check it... follow the guide in this thread...
USE ONLY PART 3... follow the guide start from this para to check your device...
Code:
Now we are going to use e2fsck to check our new partitions for errors, but not only, it also fixes some erros and it will even for example create lost & found in /data
So let's go, we'll begin with /system. If you're still in the (parted) shell, use ctrl+c and type "adb shell", then issue the following :
http://forum.xda-developers.com/showthread.php?t=1862294
Click to expand...
Click to collapse
But won't it downsize the int sd size, if OP tab still under warranty, better to get it fix by samsung for free and not lost any space.
Just reading the 1st post of the ZETA rom thread.
He says he is using stock Kernel.
He says every 5 lines, that you should full wipe...
without giving any sort of warning that it will eventually brick your device.
friedje said:
Since you can go into cwm, you can mount your storage and then connect to PC to copy all you want.
Click to expand...
Click to collapse
Tried that one, but it won't mount unfortunately. The external will no problem, but when I try with the internal it just... well it does nothing. It's a bummer cause all my most recent backups are on the internal. Any other way of retrieving my data short of extracting the chip?
Giving it back to Samsung sounds like the best option, but I'm worried cause it has a custom ROM and it's rooted. Anyone has experience doing that?
Also I thought full wipes were good, but you're saying they eventually brick the device? How come? I thought having a custom recovery meant it would be virtually impossible to brick my device... and the weird thing is that it happened during normal usage, not while flashing.
Anyway, my priority is obviously to get my tab working again, but retrieving my internal data is second highest. Isn't there a flashable ZIP that would copy the contents of the internal SD into an external SD card? Surely this has happened to someone before me?
Thanks for all the answers, really appreciated!
bruce16878 said:
But won't it downsize the int sd size, if OP tab still under warranty, better to get it fix by samsung for free and not lost any space.
Click to expand...
Click to collapse
nope it wont... the 3rd stage on that thread command for just check and fix the corrupted partition... its like when we force boot windows... it will run on a little diagnostic software to check the drive... same concept.
Oh I see, Thanks for the explanation. Learn something new today.
Sent from my LT18i using xda app-developers app
friedje said:
Since you can go into cwm, you can mount your storage and then connect to PC to copy all you want.
Click to expand...
Click to collapse
edan1979 said:
nope it wont... the 3rd stage on that thread command for just check and fix the corrupted partition... its like when we force boot windows... it will run on a little diagnostic software to check the drive... same concept.
Click to expand...
Click to collapse
Gotcha! Will try that one and post result - thanks!
how did your partition check go?
i'm annoyed that some partitions can be corrupted randomly even doing some mundane stuffs
even on stock ICS fw, i encountered DATA corruption by just deleting a contact
i guess you have softbrick..
here is what i did:
-flash stock Honeycomb firmware using Odin
-forced tablet into stock recovery mode
-wipe Cache/Data/Factory Reset
- reboot
when your tab is working again you could backup files from your internal EMMC and you could flash ROMS from there
JAYZE said:
how did your partition check go?
i'm annoyed that some partitions can be corrupted randomly even doing some mundane stuffs
even on stock ICS fw, i encountered DATA corruption by just deleting a contact
i guess you have softbrick..
here is what i did:
-flash stock Honeycomb firmware using Odin
-forced tablet into stock recovery mode
-wipe Cache/Data/Factory Reset
- reboot
when your tab is working again you could backup files from your internal EMMC and you could flash ROMS from there
Click to expand...
Click to collapse
Thanks for that. I haven't tried anything yet as I'm away till Weds, but I will then and let you know. So you're saying by flashing stock HC via Odin and wiping/resetting everything through stock recovery I won't lose my internal storage data?
that's what i experienced..but i could not guarantee that it will be the same for your device
i noticed that because old folder are not deleted when i rebooted, but i haven't checked if the system folders are cleared
to have a clean reflash i also format/sdcard on recovery..but don't do this on stocl ICS recovery since you might risk increasing the damage
try to format via odin the Honeycomb fw first [don't put PIT file neither enable Repartion, just normal flash]
then force it to enter recovery mode when it bootloops after reset
you might fix your device this way if it has softbrick
just resort to using PIT/repartition as your last option
Again I would not recommend repartition when tab still under warranty. Repartition the last resort only if the tab is without warranty after failing all other alternatives.
JAYZE said:
how did your partition check go?
i'm annoyed that some partitions can be corrupted randomly even doing some mundane stuffs
even on stock ICS fw, i encountered DATA corruption by just deleting a contact
i guess you have softbrick..
here is what i did:
-flash stock Honeycomb firmware using Odin
-forced tablet into stock recovery mode
-wipe Cache/Data/Factory Reset
- reboot
when your tab is working again you could backup files from your internal EMMC and you could flash ROMS from there
Click to expand...
Click to collapse
+1
After a full hangup, your stock hc is your first step out of the dark!
Best of luck
al128 said:
+1
After a full hangup, your stock hc is your first step out of the dark!
Best of luck
Click to expand...
Click to collapse
Ok I'm gonna do it. There are dozens of versions of HC for the 6800 though, can I just pick any or do I need to find out what it was running out of the box? Mine came from Singapore.
About a month ago my Xoom (MZ605, EOS 3.0) froze and I had to do a hard reset. After that the tablet became unusable due to the neverending stream of Closed Force dialogs. First I thought the fs and or partition table were buggered, but now I have discovered that whatever I do to the emmc, nothing changes at all: Fastboot flash, SBF flashing, fsck and gdisk in recovery (using adb shell). In all cases, the writing and flashing completes without any errors, but when checking for the results, nothing has changed at all.
Any idea on what might have caused this? Or even better: how to make to emmc writable again? If necessary I'm willing to open it up and mess with the hardware.
Thanks!
Have you tried locking and then re-unlocking the boot loader? Just a suggestion, not promising anything.
It will, normally, wipe your internal storage so make sure you backup any necessary data to a computer.
Sent from my SAMSUNG-SGH-I747 using xda premium
Hi d3athsd00r,
I tried that several times, but just be sure I tried it again. Unfortunately it didnt help Thanks for the suggestion anyway! If you or anyone else has any other ideas, please let me know. The personal data on the tablet isn't important btw (just music), so there's no problem if everything is lost.
Have you tried to format everything in cwm under the mounts menu? (Remove sdcard before doing so)
Sent by Samsung Galaxy Nexus (SCH-I515 Verizon LTE) using Tapa2
I use TWRP, but that one seems to do an rm -rf instead of a real format. Either way it has no effect: even after wiping everything several times, nothing changes: all files are still there. The same goes for using an adb shell in recovery and manually doing an ext4 format. No matter what I do, the data on the internal storage seems frozen or write protected.
ioish said:
I use TWRP, but that one seems to do an rm -rf instead of a real format. Either way it has no effect: even after wiping everything several times, nothing changes: all files are still there. The same goes for using an adb shell in recovery and manually doing an ext4 format. No matter what I do, the data on the internal storage seems frozen or write protected.
Click to expand...
Click to collapse
I would say your recovery is faulty. Try an earlier version or a different kind
Sent from my Xoom
Hi cdexsw
The problem is that flashing has no effect: when I do a fastboot flash or even RSD Lite, the commands complete without error. However after that nothing seems to have changed: the recovery stays the same, the rom (EOS 3 at the moment) stays the same and all my personal data is still there even although I did an oem lock and then oem unlock several times. It seems that whatever I do, the internal storage doesn't change a single byte. I even used dd if=/dev/zero =/dev/block/mmcblk0p10 (and also on the system and cache partitions) in an adb shell to wipe the userdata completely, but it doesn't do anything at all. So I simply can't seem to replace the recovery since not even flashing has any effect.
ioish said:
Hi cdexsw
The problem is that flashing has no effect: when I do a fastboot flash or even RSD Lite, the commands complete without error. However after that nothing seems to have changed: the recovery stays the same, the rom (EOS 3 at the moment) stays the same and all my personal data is still there even although I did an oem lock and then oem unlock several times. It seems that whatever I do, the internal storage doesn't change a single byte. I even used dd if=/dev/zero =/dev/block/mmcblk0p10 (and also on the system and cache partitions) in an adb shell to wipe the userdata completely, but it doesn't do anything at all. So I simply can't seem to replace the recovery since not even flashing has any effect.
Click to expand...
Click to collapse
odd indeed....have u looked to see if any other devices from other makes have had a similar issue?
Sent by Samsung Galaxy Nexus (SCH-I515 Verizon LTE) using Tapa2
I looked a lot on google, but didn't find anything relevant to my case. I even tried to find the datasheet of the chip to if there's a pin (ball) that controls the read-only, like a switch would. Unfortunately it doesn't seem to be publicly available on the internet.
The only topics I found to remotely relevant is:
http://discussions.nokia.com/t5/Maemo-and-MeeGo-Devices/Memory-In-Readonly-Cannot-Flash-EMMC/td-p/1030885
bu that doesn't have any relevant info.
Are you familiar with linux?
If you are, check out the first post on page 2 of this thread.
http://forum.xda-developers.com/showthread.php?t=1609825&page=2
Sent from my SGH-I747 using xda premium
Yep, quite familiar
That indeed sounds the same as my problem, but I already ran fsck a million times and everytime it complains that there are problems with the journal and won't continue. Either way, there do seem to be FS errors, because when mounting the partition it says it's fixing certain errors (very few) and then continues to mount it RW. After trying to change anything, the kernel drops the partition into RO mode. "mount" continues to show it as rw though.
That's why I tried doing an mke2fs, which completes succesfully, but it seems that the changes are only in RAM and never persisted to emmc.
ioish said:
Yep, quite familiar
That indeed sounds the same as my problem, but I already ran fsck a million times and everytime it complains that there are problems with the journal and won't continue. Either way, there do seem to be FS errors, because when mounting the partition it says it's fixing certain errors (very few) and then continues to mount it RW. After trying to change anything, the kernel drops the partition into RO mode. "mount" continues to show it as rw though.
That's why I tried doing an mke2fs, which completes succesfully, but it seems that the changes are only in RAM and never persisted to emmc.
Click to expand...
Click to collapse
Very odd indeed. I might have missed this but have you tried installing CWM (not TWRP as it only does the rm) and attempting to do a format from there?
Sent from my SGH-I747 using xda premium
I did try installing CWM using fastboot flash and also a newer version of TWRP and the command completes succesfully, no errors on the screen. When booting into recovery, the same TWRP is still there, as if I never flashed anything
Same problem with my Moto G. Nothing gets flashed. emmc is just write protected and I cannot mount anything
So guys, I think I'm in a real big problem. When I flash PAC Rom on my i9500 and reboot, it says "System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
I rebooted into TWRP recovery, Fixed Permissions, and the problem disappeared. However, after that, when I tried to install Apps from File Manager, it said Application Not Installed. I believe this has something to do with the partition thingy. Is there anyway I can overcome these problems?
The problem started when I wanted to install LiquidSmooth on my device. When I tried to do Nandroid backup through TWRP, it failed. Twice. So I used adb for the backup, but it was copying the whole block, 3-4GB+, was taking too much time, so I aborted it in the middle of the process. I then went to TWRP, and flashed LiquidSmooth without wiping (I forgot to wipe). The ROM didn't work, got stuck into Android is Upgrading, even after I wiped, still had the same problem. So I decided to restore my failed backup of the previous ROM (AICP). When rebooted, everything was crashing, System UIDs Inconsistent and stuff. Flashed PAC ROM, still the System UIDs problem, but fixed that with Fixing Permissions.
Is there anyway I can get my phone back to normal? Will I have to re-partition? What are the possible fixes?
Is there no one who can help me?
krtk6160 said:
Is there no one who can help me?
Click to expand...
Click to collapse
I think you partitioned your card as Logical make the partition as type primary.. then flash the ROM..
shubhojit89 said:
I think you partitioned your card as Logical make the partition as type primary.. then flash the ROM..
Click to expand...
Click to collapse
I had recently erased the SD card THROUGH the option available in the phone settings. But the System UIDS problem was there before I did this. I didn't change the partition type. And the SD card contained some android data and obb files. Might that be the problem?
Also, should I just put it into the SD card slot in my laptop and format with the Windows Utility?
krtk6160 said:
I had recently erased the SD card THROUGH the option available in the phone settings. But the System UIDS problem was there before I did this. I didn't change the partition type. And the SD card contained some android data and obb files. Might that be the problem?
Also, should I just put it into the SD card slot in my laptop and format with the Windows Utility?
Click to expand...
Click to collapse
I don't think android data and obb files are responsible for this system uid problem.. Yes format it using windows utility.. If still facing prob try flashing ROM using any other recovery .. Yes before flashing ROM you know the needed steps so I won't tell it again.. Do the steps manually..
Sent from my Explorer A310e using XDA Premium 4 mobile app