[SOLVED] S7 Edge SM-G935S Soft-bricked: Unable to mount any partition - Samsung Galaxy S7 Edge Questions and Answers

The problem is solved, the solution is as followed:
Problem
- The device is unable to mount every partition, this includes:
/efs
/persdata
/system
/data
/cache
Solution
Flash the stock firmware following this instruction to Repartition the device:
https://www.sammobile.com/forum/showthread.php?t=30800
The credit goes to member greenman of sammobile forum as the link above.
Thank you very much for everyone who took the time and effort to read the thread and answer my question. I appreciate it a lot.

HI there, i think you should try and grab an image for 935F from sammobile and restore with ODIN? This should restore the device into clean state. Not sure if you tried, ie to boot into download mode, and flash via odin?
**Edit, oops, i see you already tried Odin. Hope someone can assist you..

Edit. As far I have learned so far. Every root method etc will decrypt ur sd card. If you format it will be encrypted again. Because the files get reinstalled with the config. Wich can hurt allot. As I stated before try to get the first backup from efs and ur bootloader twrp makes. After make a new one and make sure they are on ur pc. I think u will need 2 freshly flash stock rom with repartition. Since it will relocate the sd card and reformats it. But im not truely sure. If I were you wait for some senior members to confirm.
I had this issue before kinda same as yours. No os etc. But I always make backups of efs and bootloader and everything else every change I make.
So I bassicly made a fresh flash. Downloaded latest stock firmware from sammobile and converted the 4 files into 1 huge file wich I putted in ap. And putted the normal once in bl and csc etc. Then Putted in hidden image for the repartion and checked reset efs.
The flash took 15 minuts and the bootup about 30 with 3 reboots.
But pls dont try this yourself. I Program whit icepicket multi flashdevice as daily job and write the coding for eepromx chips. Thats the heart of most prints with hidden coding. And controls all hardware. This method worked out for me. But like I said I rather should wait for someone to confirm this.

removed

chaopac said:
Thank you all for your answers. I appreciate your help.
Prognosis:
I agree. also think I need a repartition of some sort. Some googling of this issue shows some people use PIT files, or other files to repartition the device.
What I think happened was, since I was using the SD as adoptable storage, it has files that makes it looks like internal storage.
When I reflash the ROM and got it running, the OS and system files were correctly link (or rather installed) in the "real" internal storage. That was how I got my device to run fine.
However, when I use the app "Aparted" to format my SD, it could have mistakenly format my "real" internal storage, thinking it was my SD, since it has similar files structure (or the partition name was messed up somehow) , and this breaks the link of the system to the files, making the system think the files are non-existent.
OR, it could have formatted my real SD, but at this point in time, the system were mistakenly recognizing the SD as its internal storage, thus, showing the internal storage to be non-existent.
Now, the system are non-recognizable by any tools, either by Recovery or by system, saying they are always 0 MB in size, including all partition, system, data, efs, cache.
Assessment:
What I worry about most is since my research, some people said efs is unique to each device, and they are very specific that it is not possible to recreate. So if I lose that partition means I lose the whole thing.
To top it off, I don't even make any back up of the system. Not even the files on my adaptable storage SD.
When I was trying to reflash ROM to rescue my device I have already formatted it with my PC.
:crying:
I don't really know what else I could do. My last hope probably is the Samsung Store. I can only hope this problem is only in software, and it could be fixed. At this point I probably need to pay to get it revived.
Click to expand...
Click to collapse
Well I didnt lose efs yet using odin with re partition and efs reset. And if you already need to pay. Yes efs is an unique file.

removed

chaopac said:
Thank you all for your answers. I appreciate your help.
Prognosis:
I agree. also think I need a repartition of some sort. Some googling of this issue shows some people use PIT files, or other files to repartition the device.
What I think happened was, since I was using the SD as adoptable storage, it has files that makes it looks like internal storage.
When I reflash the ROM and got it running, the OS and system files were correctly link (or rather installed) in the "real" internal storage. That was how I got my device to run fine.
However, when I use the app "Aparted" to format my SD, it could have mistakenly format my "real" internal storage, thinking it was my SD, since it has similar files structure (or the partition name was messed up somehow) , and this breaks the link of the system to the files, making the system think the files are non-existent.
OR, it could have formatted my real SD, but at this point in time, the system were mistakenly recognizing the SD as its internal storage, thus, showing the internal storage to be non-existent.
Now, the system are non-recognizable by any tools, either by Recovery or by system, saying they are always 0 MB in size, including all partition, system, data, efs, cache.
Assessment:
What I worry about most is since my research, some people said efs is unique to each device, and they are very specific that it is not possible to recreate. So if I lose that partition means I lose the whole thing.
To top it off, I don't even make any back up of the system. Not even the files on my adaptable storage SD.
When I was trying to reflash ROM to rescue my device I have already formatted it with my PC.
:crying:
I don't really know what else I could do. My last hope probably is the Samsung Store. I can only hope this problem is only in software, and it could be fixed. At this point I probably need to pay to get it revived.
Click to expand...
Click to collapse
chaopac said:
After some more reading, I think my last resort is to perform a "Full Firmware" flash, with options such as NAND erase, PIT file flash and EFS clear.
However, I am not entirely sure what they will do, and if in my device situation they will help fix the issue or make it worse. Information I've found so far on the net are quite vague.
So I guess I will wait until someone who is familiar with this so called "Flash Full Firmware" process to point me in the right direction to move forward. Until then, I will keep searching.
Thank you for your input. I appreciate your time.
Click to expand...
Click to collapse
Edit I have typed this and readed it back. There are allot of grammar corrections to make. But I had a shift of 9 hours and due a traffic jam I also had to drive 4 hours. Also im dutch and my keyboard trys to correct stuf to Dutch. Hope you will understand what I wrote. Im just to tired now to correct it haha.
Repartion is ussualy used when you change from a multi csc to a single csc with the open pit file from the csc file. It hold how your mobile provider app instaltion etc etc.
Efs clear will bassicly wipe the cache of that part. It hold the previous versions of your mobile provider allowed things and system apl version. Also the history of previous settings. When you set up the mobile first time with a sim and add your google account there is an option restore previous backup and seetings of accounts amd system app versions of last reset. Wich always be turned on after factory reset. If you tick clear efs in odin it will wipe that. The unique codes in the efs part are not wipeable easily. Only when you really start messing arround with fully system root acces.
When a print is flashed the mainbord it is done with a flash device. In this case the one I have is used by big corporations. Every print has an hardcode. With unique codes.
To acces these or flash a new one you need sich device. Then u also need the right method. From 5 pins to uart usb in this case. Them u need the right port nuber and flash time etc etc etc. Also corporations use those special devices since we can connect different cables mini usb rs245 and so on. Wich give use another layer of protection for people who try to steal our hard code.
To ecplain lets say I made a print and the flash will be on a mini usb. Lets say the cable has 3 wires to the mini usb amd the mino usb has 5 connectors we can connect to. This gives us the oppertunity to lets say we put wire 1 and 2 on connector 3 and wire 3 on connector 1. We have allot of options. Since we can also program eich wire will transfer the data. We even can put resistors on them as a safery check.
That is one of the reasons why its damn hard to read the coding and unlock a new bootloader or efs file to root stuf. It takes allot of time to get it done. And im not sure if great programmers like chainfire do it this way. But it takes them allot of effort and time to deliver us the great rooted software.

The issue is resolved. The solution is updated at the post #1.
Thank you for everyone who read the thread and participated in.

Related

Install internal archive

Is there a way to recognize the windows like a memeoria internal 16gb usb stick? Why I accidentally formatted everything and so I wanted to retrieve data
Thanks in advance
The information is gone. When you ran the superwipe script it deleted it completely
No, because it is impossible that in less than a minute to be able to perform a full format of the memory and then a possible recovery is still possible
You were given your answer. Stop spamming. No further answers are needed.
is not true because it is impossible to have formatted 16 GB in less than a minute so there was a full format so the data are potentially recoverable
Just Google file recovery. There's plenty if free and paid software that can do this. I doubt there's one for android but if there is Google is your friend.
Oh wait...you meant tthe internal storage...why did you call it a USB stick. Youvd need a more raw access to the data..which I dont think you'd get with the tfs standard USB protocol (mtp?).
There's brute force methods to do this if indeed your data still exist...but if you don't know about them now...you wouldn't be able to do them even if you did.
Perhaps you can extract the data partition of the tf via nvflash..mount it to your computer and try few recovery on that...but that's a bit of a longshot
Just a tip... key to get good answers is asking your questions properly. Your question was very badly laid out.
Sent from my Transformer TF101 using Tapatalk
Thank you for your very thorough answer, I thought I'd try to make sure to connect the memory of 16 GB of disk drives as a tablet with special software so that I can try data recovery, I am sure that it is possible because the formatting I've done has put too little to be complete then can not be recovered

[Q] How to partition, root, install CWM, ROM, and Kernal

OK, so let me first apologise for being new to this and completely dumb. I am currently using an iphone and looking to move over to a SGN. I am pretty competent with computers, phones etc, and jailbreaking iPhone. I have messed with Linux in my spare time, so I am not afraid of detailed technical work. I have also done dozens of hours of research on how to hack android phones. The basic issue I have is that I haven’t found a single guide that explains it all clearly in one place, and also exploits are getting patched and being outdated (Zergrush for example)
I am reasonably comfortable with the threads on how to root, install CWM, and the different ROM’s explain how to install them, or at least there are multiple ways to attempt these things. It is a bit confusing because there is different advice on using or not using Odin, Mobile Odin, Kies etc, and their effect on the binary counter.
I have a few questions though, and I thought posting here might get some responses:
1). I would like to change the partition size for apps stored on the internal SD card. I have watched lots of youtube videos on this, and people suggest it can be done with ROM, CWM, Odin, and also directly on a PC with partition magic. What I don’t get is the partition structure within the phone. If this is done won’t it wipe the space where CWM and the recovery console is stored and brick the phone? Could someone explain what the partition structure is, and the best way to manage partition sizes. I believe that the SGN come with 1.8gig size for apps, and the rest for storage of music, pictures etc. I would rather have a much bigger size for apps internally, and keep music and pictures on the external SD card. I have seen the use of apps like Link2SD, Move2SD etc, but I want to sort out the partition sizes first.
2). Could someone also please explain what occasion might cause you to upgrade the Kernal. My assumption would be that everyone would want to be running the latest kernel, but it seems that people are running different kernals. Is this because they are closely tied with the ROM/firmware, and they are upgraded when the custom ROM is installed, so some suit different ROMS?
3). I would welcome any link to a page that explains all of the topics in order and really clearly e.g How to Root, then install CWM, then partition. Whether to use Odin, Mobile Odin, Kies etc.
You advice would be appreciated.
chriswilson_m3 said:
OK, so let me first apologise for being new to this and completely dumb. I am currently using an iphone and looking to move over to a SGN. I am pretty competent with computers, phones etc, and jailbreaking iPhone. I have messed with Linux in my spare time, so I am not afraid of detailed technical work. I have also done dozens of hours of research on how to hack android phones. The basic issue I have is that I haven’t found a single guide that explains it all clearly in one place, and also exploits are getting patched and being outdated (Zergrush for example)
I am reasonably comfortable with the threads on how to root, install CWM, and the different ROM’s explain how to install them, or at least there are multiple ways to attempt these things. It is a bit confusing because there is different advice on using or not using Odin, Mobile Odin, Kies etc, and their effect on the binary counter.
I have a few questions though, and I thought posting here might get some responses:
1). I would like to change the partition size for apps stored on the internal SD card. I have watched lots of youtube videos on this, and people suggest it can be done with ROM, CWM, Odin, and also directly on a PC with partition magic. What I don’t get is the partition structure within the phone. If this is done won’t it wipe the space where CWM and the recovery console is stored and brick the phone? Could someone explain what the partition structure is, and the best way to manage partition sizes. I believe that the SGN come with 1.8gig size for apps, and the rest for storage of music, pictures etc. I would rather have a much bigger size for apps internally, and keep music and pictures on the external SD card. I have seen the use of apps like Link2SD, Move2SD etc, but I want to sort out the partition sizes first.
2). Could someone also please explain what occasion might cause you to upgrade the Kernal. My assumption would be that everyone would want to be running the latest kernel, but it seems that people are running different kernals. Is this because they are closely tied with the ROM/firmware, and they are upgraded when the custom ROM is installed, so some suit different ROMS?
3). I would welcome any link to a page that explains all of the topics in order and really clearly e.g How to Root, then install CWM, then partition. Whether to use Odin, Mobile Odin, Kies etc.
You advice would be appreciated.
Click to expand...
Click to collapse
The time it took you to write this thread is almost the same as searching on xda for finding most of your answers
1. Partition is set with pit file, which is available with ROM, when you flash ROM with Odin, there you may see the option to re-partition, though you dont have choice to select the size manually on odin, you have to select the .pit (partition index table)file, which design the partition. As I know it comes default, some one make it manually i dont know. BUT listen carefully it is not without risk to brick phone, and thats why pit file in normal case you can't see in ROM package.
2. Most of near ROM kernel are alike. e.g. I M on LA4, safely using kernel KL7. ROM package it self contains kernel, so when you update it, it gets updated too. BUT in case of getting CWM you may need to select near kernel when exact kernel not available. More when you flash your ROM with CWM, you will given option to keep old kernel (to keep Root intact)
3. most of question regarding ROM , Installation , Rooting you will find on links on my signature.
Thanks Dr Ketan for your detailed response. I have actually read and bookmarked many of your threads as there are very informative and detailed.
I understand your response about the ROM and the Kernal, and also the PIT file setting the size of the partitions.
I guess then if you want to change the partition size of the internal memory, then that is something that is not normally done. It seems that most people partition the external SD card, and use link2SD to utilise the space as part of the extended memory. Would you say that is the best approach?
I can say it is safest way.
why do you feel the need to try to repartition?
1gb rom size is sufficent for any rom
2gb internal data is more than sufficient unless you like to install 100's of apps

on-chip data recovery

Hi fellow xda-members,
I've already posted this in the One XL section, but I realized it is a more generic problem/more generic technical question.
Thats why I post this again to maybe reach the real experienced guys from xda whom maybe know an answer to my specific question.
Ive summarized the most important points to not double-post the question.
I recently wiped my One XL 32GB with the HBOOT Factory Reset,
didnt know that it wipes the internal storage aswell...
Needless to say that I work with the phone and the data is priceless...
I already piped the whole block device(mmcblk0) via netcat and dd,
opened it with a hex editor and found out the whole fat-partition is nulled.
From what I know and heard, the only way to really secure delete any storage device
is to overwrite the data several(Mostly heared 7 times) times to avoid unwanted recovery.
The Partition wasnt formatted and neither mounted yet, there should be no changes made from android since the wipe.
If you take that into account, there's a hope to recover the data.
Does someone have experience with jtag raw data recovery?
Is there any way to gather other/deeper data with jtag?
Thanks for all replys
criestr
Its possible that the external storage is on a second MMC device.

[Q] Android can't find internal storage, TWRP can find it!

Hi all,
I have the weirdest problem. Ever since changing to another kernel, Android can't seem to access the internal storage (where all my files are stored) of my Nexus 4 (which is kind of a fake sdcard). The root system, with all the android files seems to be fine.
So, you might think, that's not that big of a deal. Just flash a new rom and all will be fine.
But the weirdest part is; TWRP actually has no problem loading up the internal storage. If I boot up TWRP everything is simply there, I can even acess the files from my PC.
But as soon as I boot up Android, it's gone.
So now I simply refuse to flash a clean rom, because I know for a fact all my files are still there and I don't see why Android can't mount, see or smell (or whatever it does) the internal "fake" sdcard.
What could possibly be going on here? I already tried multiple kernels, to no avail. I also tried to repair permissions from within TWRP, which led to no errors or anomalities whatsoever.
Thank you in advance,
Niels

MicroSD corrupted only on Marshmallow update.

When the Samsung Galaxy S5 (SM-G900F) received official Android 6.0.1, I have manually installed that firmware on my device. Within few weeks ago it shows that my microSD card (64GB) corrupted. At that time if i connect to the PC I can access the SD card without any error. When I tap on "fix it" it format the SD and again it shows the exact same issue.
If I connect this sd card to a PC or a another Android device (runs ICS), these devices are not detect any error. Then I rebooted my S5 into a safe mode and again it shows that issue. However, this issue will fix if I reset the phone. After few days left it again appear that error.
So how do I fix this matter?
My wifes phone has the same issue.
Non rooted phone - 100% stock. Never messed with it.
After the MM update the sdcard just says corrupted.
As soon as a photo is stored or if google play music downloads a track to it it is corrupted.
Really annoying.
Going to try a full wipe now but I'm glad it's not just her phone. I thought the SD card had died and we haven't had it long.
Looks like it's something samsung have done.
Tried formatting the SDCard with a PC?
My SDCard is the same one I've had since I got the phone, through KitKat > Lollipop > MarshMallow, and has never been wiped or formatted, still got the very first photo I ever took with the phone on it
ownjoouk said:
My wifes phone has the same issue.
Non rooted phone - 100% stock. Never messed with it.
After the MM update the sdcard just says corrupted.
As soon as a photo is stored or if google play music downloads a track to it it is corrupted.
Really annoying.
Going to try a full wipe now but I'm glad it's not just her phone. I thought the SD card had died and we haven't had it long.
Looks like it's something samsung have done.
Click to expand...
Click to collapse
No need to wipe SD. Connect that SD to a PC and copy all the files.
*Detection* said:
Tried formatting the SDCard with a PC?
My SDCard is the same one I've had since I got the phone, through KitKat > Lollipop > MarshMallow, and has never been wiped or formatted, still got the very first photo I ever took with the phone on it
Click to expand...
Click to collapse
I think this issue caused by some sort of app or its a firmware issue.
Yeah it's been formatted. I did pop it into a pc to try and save everything but it demanded a wipe.
So I did.
It worked for a little bit and corrupted again. Now when I pit it in the pc it struggles to read it and the phone won't "fix it" either.
Tried to wipe it in a few different programs but it appears the card is corrupted.
It's a 64gb Samsung card. Only had it since January this year. Bought brand new from amazon.
I have another in my note 3 and that is still perfect.
The only saving grace is that Google photos had all the photos synced.
So i'm going to email Samsung about it as there has been no issues with the card until the moment the MM update hit.
ownjoouk said:
Yeah it's been formatted. I did pop it into a pc to try and save everything but it demanded a wipe.
So I did.
It worked for a little bit and corrupted again. Now when I pit it in the pc it struggles to read it and the phone won't "fix it" either.
Tried to wipe it in a few different programs but it appears the card is corrupted.
It's a 64gb Samsung card. Only had it since January this year. Bought brand new from amazon.
I have another in my note 3 and that is still perfect.
The only saving grace is that Google photos had all the photos synced.
So i'm going to email Samsung about it as there has been no issues with the card until the moment the MM update hit.
Click to expand...
Click to collapse
Try MiniTool Partition Wizard
Delete all partitions on the card > create new primary partition > Format to FAT32
MiniTool Partition Wizard free
https://www.partitionwizard.com/free-partition-manager.html
Used that to repair SDCards and USB drives a few times
You can also do it manually with elevated CMD: (Hit enter after each)
------------
diskpart
list disk
select disk x (x = being the disk number of your USB drive/card)
clean
create partition primary
active
format fs=fat32 quick
assign
exit
--------------
Try the card again
*Detection* said:
Try MiniTool Partition Wizard
Delete all partitions on the card > create new primary partition > Format to FAT32
MiniTool Partition Wizard free
https://www.partitionwizard.com/free-partition-manager.html
Used that to repair SDCards and USB drives a few times
You can also do it manually with elevated CMD: (Hit enter after each)
------------
diskpart
list disk
select disk x (x = being the disk number of your USB drive/card)
clean
create partition primary
active
format fs=fat32 quick
assign
exit
--------------
Try the card again
Click to expand...
Click to collapse
Already tried diskpart. No dice.
Just tried MiniTool Partition Manager. Still nothing. It lets you delete the partition and then creates a new partition instantly.
It has however now loaded in windows and shows 4 android folders but even after a delete on the partition and create new it makes no changes to the card.
It also wont let me add anything. Almost as if it is locked to read only.
So thanks for the advice as I can now see the card in windows "sort of". It's really slow though. But I can't put anything on it or wipe it or do anything with it really!
Windows 10 also says there are errors and when you let it error check it just stops responding.
ownjoouk said:
Already tried diskpart. No dice.
Just tried MiniTool Partition Manager. Still nothing. It lets you delete the partition and then creates a new partition instantly.
It has however now loaded in windows and shows 4 android folders but even after a delete on the partition and create new it makes no changes to the card.
It also wont let me add anything. Almost as if it is locked to read only.
So thanks for the advice as I can now see the card in windows "sort of". It's really slow though. But I can't put anything on it or wipe it or do anything with it really!
Windows 10 also says there are errors and when you let it error check it just stops responding.
Click to expand...
Click to collapse
If it still shows android folders on it, then none of the partition commands you've used, nor minitool have done anything, as you'll know, deleting all partitions on a disk completely wipes it
With MiniTool, it works a weird way, you have to basically tell it what you want to do, all steps, and then hit apply at the top, once you hit apply, it then performs the steps it looked like you had already done manually
EDIT - Just a thought, a live Linux CD/DVD/USB might have more luck, Linux doesn't care about permissions etc
*Detection* said:
If it still shows android folders on it, then none of the partition commands you've used, nor minitool have done anything, as you'll know, deleting all partitions on a disk completely wipes it
With MiniTool, it works a weird way, you have to basically tell it what you want to do, all steps, and then hit apply at the top, once you hit apply, it then performs the steps it looked like you had already done manually
EDIT - Just a thought, a live Linux CD/DVD/USB might have more luck, Linux doesn't care about permissions etc
Click to expand...
Click to collapse
I see... I have used Partition Magic in the past and if I recall you had to do this back in the old version. Completely forgot.
I've done that and it's trying to do it. It's going very sloooooooow. But it is getting further than diskpart did!
Will update when it decides to finish.
Good luck, might find it takes a few runs to undo whatever the phone/droid did to it
Unless of course it is physically damaged, but I've not had any problems with MM and my SD
EDIT - Found this from way back in 2010 in my repair folder, "Pen drive repair"
Code:
https://mega.nz/#!XdAW2R5I!sSVna0O4av5rnkTPpGuh_bkXatZpcfmr6X-R-3yjrzw
I tend to keep random programs that have fixed something difficult in the past, and put them in that repair folder, worth a shot
*Detection* said:
Good luck, might find it takes a few runs to undo whatever the phone/droid did to it
Unless of course it is physically damaged, but I've not had any problems with MM and my SD
EDIT - Found this from way back in 2010 in my repair folder, "Pen drive repair"
Code:
https://mega.nz/#!XdAW2R5I!sSVna0O4av5rnkTPpGuh_bkXatZpcfmr6X-R-3yjrzw
I tend to keep random programs that have fixed something difficult in the past, and put them in that repair folder, worth a shot
Click to expand...
Click to collapse
Will take a look at that tomorrow.
It formatted the card but as soon as it finished and mounted it Windows popped up and said there was a problem and it needed scanning.
Once it opened there were still 4 android folders on it....
Annoying.
Yea very, well it's definitely not deleting the partitions if it's still got all the old folders on it
Running the tool as Admin?
It does sound like it's physically damaged, but I thought that about a 16GB flash drive I had, and another 8GB I'd left in a tub on my desk for years because it was dead, then I used diskpart and repaired both of them the same day, and since then, minitool has fixed them
Tell you what you could try, Win32DiskImager, grab any image, say a Raspberry Pi image, and use Win32DiskImager to write the image to the card, I think that uses disk/device rather than partitions to write to, so it should overwrite absolutely everything
Then you can use Minitool to wipe and format back to FAT32 (Hopefully)
*Detection* said:
Yea very, well it's definitely not deleting the partitions if it's still got all the old folders on it
Running the tool as Admin?
It does sound like it's physically damaged, but I thought that about a 16GB flash drive I had, and another 8GB I'd left in a tub on my desk for years because it was dead, then I used diskpart and repaired both of them the same day, and since then, minitool has fixed them
Tell you what you could try, Win32DiskImager, grab any image, say a Raspberry Pi image, and use Win32DiskImager to write the image to the card, I think that uses disk/device rather than partitions to write to, so it should overwrite absolutely everything
Then you can use Minitool to wipe and format back to FAT32 (Hopefully)
Click to expand...
Click to collapse
The trouble with that is I can't write anything to it. It gives an i/o error ever time I try.
I'm tired now so i'm going to head to bed but tomorrow when I have a fresher head i'll take another look.
Will let you know how I go on. Will try that other tool you suggested.
The way Win32DiskImager writes to the disk is different to how Windows tries to write to it, basically like burning an ISO, vs copying files to a DVD
Yea, get some shut-eye, things are usually much simpler after a good nights sleep
Hi, i lost a kingstom 9GB after take out this card from a Samsung. I formatted, and after a few days , i disvovered, that card was set to be encrypted inside the phone, if someone takes out, and formats without unencrypt, on 2 or 3 cycles mor, the card will die, or lock, io root, i never found a solution for this, in my case, the card was locked, (ro), without any error in the partition.
Sent from my XT687 using XDA Premium 4 mobile app
---------- Post added at 11:33 PM ---------- Previous post was at 11:08 PM ----------
Sorry, i wrote wrong, is 8Gb, was the second sdcard lost by me, the first, was a 2Gb used on a nokia e7, that, after format this card the card was locked (ro) at all on all type of sdcard reader , usb, pc. The name, i found, is Cyclic Redundance Error, (formatted without unencrypt the filesystem)
Sent from my XT687 using XDA Premium 4 mobile app
*Detection* said:
The way Win32DiskImager writes to the disk is different to how Windows tries to write to it, basically like burning an ISO, vs copying files to a DVD
Yea, get some shut-eye, things are usually much simpler after a good nights sleep
Click to expand...
Click to collapse
Pen Drive Repair does nothing. Can't even find it.
Tried it another 2 times in MiniTool but still goes through all the motions but returns with the same four folder on the card.
I did a surface test and it found no errors. So reading it is fine. It's the writing to it where it fails.
EDIT: What I have just noticed is MiniTool states:
Capacity 59.64 Used 59.64 Unused 0B
So the card thinks it's full but there is nothing on it.
EDIT 2: And now in MiniTool is just says BadDisk. Looks like it is completely dead.
Well, there's nothing to lose by trying Win32 DI, unlikely to work,. but might as well try before writing it off
*Detection* said:
Well, there's nothing to lose by trying Win32 DI, unlikely to work,. but might as well try before writing it off
Click to expand...
Click to collapse
Gave it a shot. It wont even let me pick it as a device. Windows has stopped adding it to the "My Computer" list also.
I've wasted enough time with it. Only bought it in January this year so I've emailed Samsung both about the warranty on it and also that there is a possibility the upgrade to MM caused it on the S5.
It seems to have happened to the OP and me so I thought I would mention it to them in case.

Categories

Resources