Hi all,
Although I have read xda forums quite a few times, this is my first post here, and my reason for posting is that I really don't have a clue how to proceed with my Galaxy S2.
The story is the following: I was going to sell my old Samsung Galaxy S2, so I decided to delete all data from it in a way that it is not recover friendly. After seeing that a factory reset would not delete the internal memory completely, I was worried about the new owner being able to read my ersonal information, so I plugged in the phone USB to the Mac as Mass Storage and went to disk utility in Mac and performed a formatting of the phone partition(FAT32). When I rebooted the phone it would not work properly, messages like "Usb storage damaged" and most apps would not work, like camera, file manager and so on. I assumed I deleted important system files when formatting so I went to CWM based recovery and transferred the initial content of the internal memory (previously backed up) back to the phone's memory, in an attemp to put things back to normal.
Nothing has changed and the phone is not able to read that memory. I tried many options from the CWM recovery mode but nothing seems to work. I tried reformatting USB storage from the phone options, factory and cache reset from CWM....
The Android version is 4.1.2, Model GT I9100, Kernel 3.0.31 Siyah s2 v6.0b5+
I have also tried to install a different custom ROM but that does not fix the problem either.
So my question is: Is there anything I can do to restore a recognizable file system into the internal memory?
Thank you so much,
Problem solved. After flashing with ODIN the phone repaired itself performing a USB storage format from the device.
Related
I have been using checkrom revolution hd v4 for 2 weeks with DK 2.5.2 with no problems. But after a nornal reboot today, the SD card (internal) can't be read even after several reboots. I tried to formatted it but it can't be formatted either. Just bought my SGS2 two months ago only.
What should i do to recover function of my SD card again? Is it because of the custom rom that caused this issue?
Please help. Thanks!
Sent from my GT-I9100
Try doing a full-stock restore, making sure to do a factory reset, wipe the cache and Dalvik cache along the way. If you're still having problems, take it to a Samsung service center.
That's really strange though - I'd assume that if the OS can't read/write the internal storage, then it shouldn't be able to flash a ROM, or even really load the OS?
just a thought... have you tried to: connect your phone via usb as external drive and have windows do a repair of harddrive.
i had a sdcard which was "read only" under android, after that procedure it worked again flawless
in my case the cause was a faulty titanium backup file....
screamworks said:
Try doing a full-stock restore, making sure to do a factory reset, wipe the cache and Dalvik cache along the way. If you're still having problems, take it to a Samsung service center.
That's really strange though - I'd assume that if the OS can't read/write the internal storage, then it shouldn't be able to flash a ROM, or even really load the OS?
Click to expand...
Click to collapse
matis1 said:
just a thought... have you tried to: connect your phone via usb as external drive and have windows do a repair of harddrive.
i had a sdcard which was "read only" under android, after that procedure it worked again flawless
in my case the cause was a faulty titanium backup file....
Click to expand...
Click to collapse
Thanks for the help! I suspect it might be Titanium Backup problem. The OS finally read the internal SD after a few more reboots but all the data inside is wiped out Not to mention I accidentally formatted my external SD by mistake as well. Sigh...got to restore everything bit by bit. Do you think it could be a media problem initially (i.e. problem with the internal SD)?
Hi all,
My sister-in-law hooked up her phone to her laptop and then Kies responded there was an update. I know for a fact that she was on 2.3.6 and the suggested update was the ICS one.
The phone booted in download mode and then got stuck on 12%, then she turned to me.
I'm pretty familiair with Android phones and I rooted and installed custom ROMs on quite a lot of phones. But, it was always with a full backup and I always made sure the phone numbers were on the SIM card as an extra precaution.
Now, this phone is NOT rooted, just stock 2.3.6 on it, she made no backups of any kind and there's no external SD card in it so the photo's are on the internal memory.
So, what I need first, if possible, is access to the internal memory. Normally, I can mount the memory in clockworkmod recovery, but this phone is not rooted so no CWM. Can I flash a kernel to get CWM? And if yes, which one?
Secondly, is there any way to backup the phone numbers? If I flash a new ROM I will loose al numbers, right?
Hope someone can help, she's quite desperate! (me too actually)
one part of information I forgot to give;
when I pull out the battery and reboot the phone after putting it back, I just get the phone/warning sign/pc logo and the text "firmware upgrade encountered an Issue. Please select recovery mode in Kies ans try again"
When I do that, Kies sees the phone, starts downloading a recovery image of some sort and stay on 100% for a few minutes and then closes without any error message.
Numbers are stored in Google account, and Internal memory is not formatted if you do a factory reset. I could recommend you to move your question to this thread http://forum.xda-developers.com/showthread.php?t=1648351&page=148
drraptor said:
Numbers are stored in Google account, and Internal memory is not formatted if you do a factory reset. I could recommend you to move your question to this thread http://forum.xda-developers.com/showthread.php?t=1648351&page=148
Click to expand...
Click to collapse
Hi, I just flashed a stock ROM of the same version with Odin.
Phone is ok again, nothing is lost.
Camera was set on storing photos in internal memory, I changed it.
All contacts were already stored on the SIM card so no sync to Gmail
vinz3nt said:
Hi, I just flashed a stock ROM of the same version with Odin.
Phone is ok again, nothing is lost.
Camera was set on storing photos in internal memory, I changed it.
All contacts were already stored on the SIM card so no sync to Gmail
Click to expand...
Click to collapse
So internal memory wasn't wiped ?
Just backup and flash a Stock ICS using Odin
Okay, this is quite a long story, so I apologise in advance.
I decided to update my Galaxy S2 today to a newer ROM (SuperNexus 2) with the latest version of Android. I was coming from a CM9 build. I went through the usual process of backing up data and performing a full NANDROID backup via CWM Recovery, booted the phone again and transferred the backups to my PC via USB. These files transferred fine.
I then downloaded the zip files for the new ROM and proceeded to copy them to the internal storage of my phone. The copy dialog in Windows said that it was "discovering items" and stayed like this until I turned off USB transfer mode on the phone and removed it (ie. the files failed to copy) This happened a number of times and I didn't get anywhere. I have plenty of space free on the SD card, but just to make sure I started the phone in CWM again and formatted the SD card, and since I was going to do it anyway, the data and cache partitions too. When I booted the phone again, the files still wouldn't copy. I managed to copy a text file to the phone which was about 32kb but anything larger just seemed to fail.
I then went back into CWM and decided to partition the SD card, as I thought that it may have been corrupted somehow and needed to rebuild the filesystem. This however, caused even more problems as trying to format the SD card (In CWM) now just reported "Error, can not mount E:/sdcard".
Feeling fairly frustrated, I decided to download the Stock ICS ROM for the Galaxy S2 and install it via Odin, thinking that the problem was probably with CWM. The install went fine, but upon reboot the phone just stayed on the boot animation, no matter how long I left it. To make sure the install went smoothly I decided to try and reinstall the Stock ROM via Odin again, but now Odin didnt seem to get past the "Initializing.." stage.
So all in all, I now have a phone which wont boot into Android, cant copy anything to internal storage, and Odin wont seem to connect to.
I am convinced this is a software issue and therefore fixable. But maybe the internal storage was not working correctly in the first place. I have installed many ROMs before and never had such issues.
Anyone know anything about this or how I could potentially fix it? Thanks so much in advance!
Benji1992 said:
Okay, this is quite a long story, so I apologise in advance.
I decided to update my Galaxy S2 today to a newer ROM (SuperNexus 2) with the latest version of Android. I was coming from a CM9 build. I went through the usual process of backing up data and performing a full NANDROID backup via CWM Recovery, booted the phone again and transferred the backups to my PC via USB. These files transferred fine.
I then downloaded the zip files for the new ROM and proceeded to copy them to the internal storage of my phone. The copy dialog in Windows said that it was "discovering items" and stayed like this until I turned off USB transfer mode on the phone and removed it (ie. the files failed to copy) This happened a number of times and I didn't get anywhere. I have plenty of space free on the SD card, but just to make sure I started the phone in CWM again and formatted the SD card, and since I was going to do it anyway, the data and cache partitions too. When I booted the phone again, the files still wouldn't copy. I managed to copy a text file to the phone which was about 32kb but anything larger just seemed to fail.
I then went back into CWM and decided to partition the SD card, as I thought that it may have been corrupted somehow and needed to rebuild the filesystem. This however, caused even more problems as trying to format the SD card (In CWM) now just reported "Error, can not mount E:/sdcard".
Feeling fairly frustrated, I decided to download the Stock ICS ROM for the Galaxy S2 and install it via Odin, thinking that the problem was probably with CWM. The install went fine, but upon reboot the phone just stayed on the boot animation, no matter how long I left it. To make sure the install went smoothly I decided to try and reinstall the Stock ROM via Odin again, but now Odin didnt seem to get past the "Initializing.." stage.
So all in all, I now have a phone which wont boot into Android, cant copy anything to internal storage, and Odin wont seem to connect to.
I am convinced this is a software issue and therefore fixable. But maybe the internal storage was not working correctly in the first place. I have installed many ROMs before and never had such issues.
Anyone know anything about this or how I could potentially fix it? Thanks so much in advance!
Click to expand...
Click to collapse
I9100?
Can get to DL mode?
Can get to recovery?
Get an older Odin version and flash siyah just to see if it can be flashed again.
If you can get to recovery, Nuke Script is the way to go.
It sounds to me that maybe your memory is corrupt...
Not just yet, smells like soft brick.
Sent from the little guy
First off, I am no expert so please be gentle! I previously rooted my old Samsung Galaxy S i9000 and installed ICS, which went OK, but the phone became quite slow and unstable. I was advised to install RemICS and downloaded all the zip files from this forum, and put them on the external SD card. I followed the developer's instructions to the letter, as well as reading everything I could find on the subject. The reset and data wiping went fine, but the installation of the ROM didn't. It halted with an error message -`ROM incompatible, trying to use an invalid partition'. I repeat that this is supposed to be the specific ROM for the i9000. The phone now won't boot into recovery. It stops with an orange Android logo and the text `Powered by Mackay Kernel'. It won't boot into download mode either. The Mackay screen stays there however long I leave it. I really need help from the ROM developer but I can't post to that forum. How can I either boot into recovery or into download mode? Is this ROM reliable? What could I have done wrong?
More info:
Presumably everyone is on holiday! But just in case anyone is reading, there is further news. The reason I could not start recovery mode was that the button sequence was different from what I had been told. It now boots reliably into Mackay (which of course is TWRP). I have found that the phone is unable to mount the partitions DATA and SYSTEM - they seem to be corrupted. Hence it has not wiped DATA, although TWRP wrongly reports success. I have tried updating the partitions to ext3 or ext4 but this fails every time. I could format the thing from Windows but that will wipe everything including recovery of course. I need a tool to repair these partitions, but have not found anything so far. This may well have been the reason the phone was getting creaky in the first place.
I have copied a new ROM to the external SD card, using a card reader, and inserted this into the phone. Strangely the TWRP file manager reports that EXTERNAL SD is a sub-folder of SD CARD, and that is empty. The file manager does not show the real external SD card. But the real external SD shows up on the Windows USB connection. What is going on?
When I try to mount the partitions, DATA and SYSTEM can't be checked - the other partitions (Cache, sdcard, and emmc are all checked).
kingGrn Copeland
Well for the benefit of anyone else with the same problem, I have managed to re-flash the ROM back to stock. It just took 3 days of intensive web browsing until I understood how to do it, and found software that worked - a lot of stuff out there has errors.
To summarise, the problem was:
1. Data and System partitions became damaged, so phone became unstable.
2. Attempt to upgrade ROM failed because of damaged partitions.
3. Could not boot phone into recovery or download because button combination was different from what I was told.
The solution was:
4. Boot into download mode using correct button combination.
5. Re-flash back to stock ROM and re-partition using Odin.
Yes, someone did tell me that, and I would have done that straight away if I could have gotten into download mode. We live and learn
The solution was:
4. Boot into download mode using correct button combination.
5. Re-flash back to stock ROM and re-partition using Odin.
Click to expand...
Click to collapse
Thanks this wa useful for me too.
Hello guys,
I was using DorimanX v 119 10 series along with Slim Saber 08/24 release, then yesterday when the battery was around 18% it turned off randomly.
When I turned it on, I saw I was not getting options for Dual Boot and it took me straight to Primary ROM where it showed a message Internal Memory Damaged, format it on the notification bar.
Tried opening Titanium Backup and other apps to backup but SDCARD0(internal storage) was not mounted anywhere.
Restarted the phone and now its getting stuck on DorimanX logo.
Tried mounting from recovery and doesn't seem to work..
Is there anyway possible to recover my data? There are lots of information and photos that I need in that internal memory
Any help would be appreciated.
Thank you.
had that happen to me more than once on kitkat.
are you able to mount usb in recovery?
tried this?: http://forum.xda-developers.com/showthread.php?t=1646108
i went back to my jellybean backup and copied everything over to my computer.
I would be interested to hear how you are doing on this?
I recently had a crash on my S2 with the same version of DorimanX.
Had you repartitioned?
Thanks for your input guys.
@rgomia, the internal memory still shows corrupted and not able to read from it even from Aroma file manager
Actually I tried flashing slimsaber again and I could boot but still the internal memorys not readable from any file manager. Looks like I'll have to repartition it.
Was looking to somehow recover those lost data, but doesn't look like there's a chance
Reformatting worked and everything back to normal, Since I'm gonna get Redmi 1S anyway, I'll stay on slim kernal and use this as a backup phone. 5 years of important data and photos lost in the process :/
If your phone is bootable you should just mount it on your PC and run a file recovery program.
Your pictures are usually stored on your primary SD card.