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
Related
Hey guys I need your help
I've been using cm7 for a couple of weeks now. I havnt had problems until today.
I flashed build 32 over and for some reason it wasn't booting up. It was on the splash screen for a while (it usually does that and when I take battery out and restart it boots) so then I took the battery out. Next thing I know is that my phone is stuck on the mytouch screen... I went to recovery and when it booted into cwm 3. I got a error saying it couldn't open system/recovery/log or something like that... it still went to cwm and I checked the mounts and it said /system and /data wasn't mounted. I clicked it to mount and it gave me an error saying it couldn't ... therefore it wouldn't let me install cm7 or do a wipe... is there anything I can do to fix this? It seems to be that the nand. Is corrupted or something...
I think, based on your description, that pulling the battery at the particular instant caused the secondary problem.
A "factory reset" reformats /data and /cache. But not /system. You can do that manually from the mounts and storage menu, then either restore a nandroid backup or install cm7 and gapps.
HTC Glacier running CM7 #33
Hmm I font think its just two directories... I think my whole internal storage is messed up. I tried using the reformat option from cwm but no luck
Time to discover what you might be able to accomplish with Fastboot and a USB cable.
HTC Glacier running CM7 #33
I think a lot of people are having problems with clockwork 3 in the nexus forums, and more specifically with it screwing up partitions. I was luck just to lose my ext position on my sd...
Reformat and reflash seems to be the easiest fix...
Sent from my Nexus One using XDA App
i dont know how to repartition the phone storage :/
i tried doing it off cwm and it wouldn't let me... is there anyway to do this through adb? i think adb is working...
Reformat the whole card, and then try to repartition. This will write your data, so back up first...
Sent from my Nexus One using XDA App
how do i do that? o_o through cwm? i tried formating everything including system data cache... and i dont know how to repartition through cwm. cwm is the only thing i can get to right now :/
Sorry, looks like the only option in clockwork is to partition. Can you not do it from your pc?
Sent from my Nexus One using XDA App
yeah it gives me error when i try to do :
fastboot erase system -w :/ is there anything else?
guys... ((((( am i totally effed up? i couldn't find anything i could do.. no matter what i did, the /system and /data would NOT mount... so i cant format it
I have never tried this, but you might consider it.
In this thread is a method to return your phone to stock -- it uses the bootloader's ability to repartition and reformat everything somewhat automatically, using a file called PD15IMG.ZIP from the SD card's root folder.
http://forum.xda-developers.com/showthread.php?p=11011692&highlight=pd15img.zip#post11011692
There's a link in the thread to the .zip file -- look to post signatures. Put the file on an SD card (with another phone, or camera, or Micro-SD to SD adapter, etc.) and boot into the bootloader with that file on the SD card.
I do not know if you can rename the .zip it to update.zip and force it to flash with Fastboot's update command, because the PD15IMG.ZIP is a specific thing this phone's bootloader looks for. As stated, I have never tried this, and do not recommend this. It might work, or, it might cause more damage. Putting the file on an SD card without Fastboot will be safer.
You could try to boot your phone into fastboot,
and then type
fastboot erase -w system
Your phone wont boot after that, but you should be able to flash a new rom from clockwork.
ive tried both the pd15img.zip method. it says "partition update fail"
and i also tried the "fastboot erase system -w" and it did not work.. it says that it can't be done. i also tried to format /system through adb and cwm, and both says it can't because it must be mounted before
From your description, it seems to me that the internal flash memory has a damaged partition table -- easy enough to repair if this were a hard drive you could remove and take to a linux system somewhere. But it's a phone, and a bit of flash memory that can't be removed.
Flashboot has an "erase <partition>" command. I don't know what it does, since it's not well documented. Does it reformat an existing partition? Or does it remove the partition from the partition table? There is no commensurate "create <partition>" command, so perhaps it recreates an empty partition. But I tend to doubt it.
I would think such work might be done from an engineering bootloader or engineering recovery system -- one available to HTC service technicians, for example.
Since you're not getting a great deal of help in the MT4G subforum, you might post your question in the top level Questions and Answers forum.
Sorry I'm not much help with this.
One last thought. The bootloader itself has a Factory Reset. That might do it. Might not. But like chicken soup, it probably couldn't hurt. Boot into the bootloader (volume down while powering up), select BOOTLOADER with the volume control and then the power button, then select FACTORY RESET. Perhaps it will do something positive.
eh.. i couldnt do anything. i tried all options. its like impossible to reformat or repartition the drive..
i actually called up insurance and they'll be sending me a new mytouch 4g..
we have just told them that it doesnt go past the mytouch screen.. would they figure out that it is rooted? i mean.. choosing recovery from the bootloader menu takes it right into cwm lol
Just flash the stock recovery back via fastboot...
Sent from my Nexus One using XDA App
ive tried
dumbkkid said:
ive tried
Click to expand...
Click to collapse
you are sending the fastboot commands while in the bootloader right? I would imagine you are but I just want to make sure.
Hello !
I have a big problem with my galaxy s.
Since January i am working with my JPY firmware quiete fine. On sunday the phone rebooted without anything done by me. Afterwards my homescreen was empty.
Most of my apps are not working now. So i have done a wipe. Nothing, the same. Interesting is, that all my data was still on the device. Then i try to format the internal sd. Not working, no error message. When I delete all files and deinstalled all apps, everthing was gone. After a reboot all data is back on the internal sd as before.
OK then i tried to flash different 1 and 3 file firmware versions with odin(also with repartitioning). But no version is really working and i never get to the homescreen. So I flashed the JPY back. Then everything is like before my first steps. All data is on the phone, i can not delete anything.
I tried do delete the storage also with recovery mode. Nothing.
I tried with adb (android sdk), deleted all files in /mnt/sdcard. After a remount all data appears back.
What can i do to get my phone working ? I have found no possibility so far.
Thanks in advance for your help!
Frederik
Fred001 said:
Hello !
I have a big problem with my galaxy s.
Since January i am working with my JPY firmware quiete fine. On sunday the phone rebooted without anything done by me. Afterwards my homescreen was empty.
Most of my apps are not working now. So i have done a wipe. Nothing, the same. Interesting is, that all my data was still on the device. Then i try to format the internal sd. Not working, no error message. When I delete all files and deinstalled all apps, everthing was gone. After a reboot all data is back on the internal sd as before.
OK then i tried to flash different 1 and 3 file firmware versions with odin(also with repartitioning). But no version is really working and i never get to the homescreen. So I flashed the JPY back. Then everything is like before my first steps. All data is on the phone, i can not delete anything.
I tried do delete the storage also with recovery mode. Nothing.
I tried with adb (android sdk), deleted all files in /mnt/sdcard. After a remount all data appears back.
What can i do to get my phone working ? I have found no possibility so far.
Thanks in advance for your help!
Frederik
Click to expand...
Click to collapse
try to update it using kies or if u have latest version then try flash your device using odn flasher
Thanks for your help harmandeep45. But all this is already done. I worked on this issue little longer and can say that there is some unrepairable problem with the internal sd. I can not delete any partition neither with adb (parted /dev/block/mmcblk0p1 rm). When I do a print everything is there. I am able to mount and unmount the partitions. No problem. But it is not possible to reorganize them. Even if i write on the sdcard partition, after a remount it is as before the write. Maybe the flash memory is broken. Does anybody had the same issue? I already tried the things written in this post, but without luck : http://forum.xda-developers.com/archive/index.php/t-845708.html
I have the same problem, i had installed another firmware on my sgs and start throwing me program errors I had before in my other firmware and when it comes to memory I saw that the folders that were there had not cleared and when I trying to delete the folders and files reappeared.
Ok, what i have tested is to flash different firmware versions. Nothing worked. I used the debug console adb to log in and tried to delete the partitions from /dev/block/mmcblk0 with parted. Nothing happens. I am not able to delete them. I don't want to send the phone to the samsung service, because there is important company data on it, like emails, banking, ebay, etc. I tried to mount it in Linux as usb memory device and used gpartet to create new partitions and overwrite all with dd if=/dev/zero of=/dev/sdb1, but after reboot everything was like before. Is there any other possibility to delete the flash???
Fred001 said:
Ok, what i have tested is to flash different firmware versions. Nothing worked. I used the debug console adb to log in and tried to delete the partitions from /dev/block/mmcblk0 with parted. Nothing happens. I am not able to delete them. I don't want to send the phone to the samsung service, because there is important company data on it, like emails, banking, ebay, etc. I tried to mount it in Linux as usb memory device and used gpartet to create new partitions and overwrite all with dd if=/dev/zero of=/dev/sdb1, but after reboot everything was like before. Is there any other possibility to delete the flash???
Click to expand...
Click to collapse
you have to flash it with jtag box riff, but I doubt you have one, you have to find a place where they have the box
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?
Hi,
I have a Samsung nexus S GT-19020
I had some issues booting recently so I decided to root it and put on cyanogenmod, I'm now having issues with the SD card. I can mount the card fine and view the contents however when I delete files or add them they reappear/disappear when I remount the SD card. Does anyone have any idea on what this might be? I've used adb shell to mount it and remove the files to no avail so I've ended up with a phone that can't save anything!
Thanks in advance,
Mrpinksss
First things first, make a backup. Copy any and all important files off of the phone and onto the computer, and it would be wise to copy the entire /sdcard even if there is stuff you don't think you need. If there are specific files/settings you are unsure how to backup manually feel free to ask, these may be located in /system or /data. Furthermore, i would recommend making a backup of your /efs folder (at least copy the entire folder and save it somewhere safe on the computer - be sure to get all hidden files starting with a DOT [.]), just in case if you havn't done so already.
Once this is done and anything left to worry about is behind us, try formatting the /sdcard via clockworkmod and see if that does anything. If not, post again and i'll think of some new things to try
yeah everything is backed up, I've tried to format with clockwork multiple times now with no luck. I've also tried formatting with fdisk with no luck either
Start over from the beginning and lock/unlock your bootloader which will erase/format everything. After you have everything backed up, of course, as previously mentioned.
so I tried fastboot with the stock ice cream ROM 4.0.2 which seemed to work but it won't boot and just gets stuck at the Google logo. I also locked the bootloader but when I try and unlock it I get a
FAILED (remote: Erase Fail)
thanks for your help so far!
Sounds like a busted SDCard. These are known for giving up, often quite randomly and with no warning. It is a hardware issue and generally needs Samsung to sort out the issue for you - it should be covered by warranty so long as it is still within the warranty period.
MrPinksss said:
so I tried fastboot with the stock ice cream ROM 4.0.2 which seemed to work but it won't boot and just gets stuck at the Google logo. I also locked the bootloader but when I try and unlock it I get a
FAILED (remote: Erase Fail)
thanks for your help so far!
Click to expand...
Click to collapse
Crapola, that sucks. Hmmm...
I did a search for that error message and lots of stuff came up on xda and elsewhere and i think harbb is right, your hw might be borked. Lame-o....
Well at least I got it locked and back to a stock ROM, shall take it into Vodafone.
Many thanks!
So, being a noob. I tried to root my 1541 and ended up deleting the OS. I still have TWRP, which I believe means I am soft bricked. My PC (tried several different PCs) won't recognize the phone as a usb device. The bootloader screen always says "Connect USB data cable".
I have tried USB OTG, when I click "Select storage" it simply shows it as 0MB and wont open. Same for SD cards. Is there something super obvious I'm missing because I have researched this pretty well before asking for help. I've read all the guides, tried ubuntu etc.
I'm at the end of my rope. Any help would be very much appreciated.
Please describe exactly what you did (e.g which guide did you follow or what had you flashed etc.). And, is the system stuck at a static motorola logo (it's called bootlogo btw) or the stitching/globe animation looping over (this scenario is called bootloop)? I just wanna confirm how much of corruption has occurred and through which way, so I can suggest the easiest solution to try. Thanks.
Sent from my MotoG3 using Tapatalk
Did you install the moto drivers on your pc?
Does your phone connect with different cables ? If you can get it connected in twrp choose wipe format data then reboot to recovery mount system from recovery run terminal command fstrim -v system fstrim -v data fstrim -v cache reboot to recovery now mount your phone and clean flash the rom