Ive been running a AOSP Rom for about a month. Yesterday I took it off the charger, and when it booted up It went to a black screen. Even a battery pull didn't help, so I restored a backup from last week. It worked great, but it would not recognize my external SD. I couldnt fix it so I went into recovery, did a full wipe, and restore a sense rom. That worked, my ext SD came back, but my internal storage was gone, all the data was wiped. Ive tried several data recovery apps/programs, and they dont detect anything?
Mainly, I am trying to recover voice recordings, and voice mail that I saved. So am i SOL???
Try mounting internal through recovery and run a recovery program that can recognize corrupt, deleted, and formatted partitions. Assuming you have windows, Recuva is a pretty good at recognizing the differences. Actually recovering files is hit and miss, but it's very reliable for a free program
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)?
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
I have a very odd issue.
First let me say what has happened and events leading.
I have 2 phones that have been running Milestone 4 Rom. identical builds and phones.
Phone one still uses Milestone 4 and everything works fine.
Phone two was starting to lock up on Milestone 4 after some months time of running fine,
Thinking this could be an app or possible error somewhere, decided to do a new rom after full nandroid and titanium backup.
Loaded Viper rom, after full wipes with system, cache, davlik,. Working fine for a few days then all of a sudden getting lockups and the notification bar was still active.
Did another wipe and flash, to viper.
Then noticed that the gallery would not show any recent pictures, and some odd behavior with picture messaging.
Someone mentioned to wipe the Internal and external SD. So hooked up phone with the sync mode, so both would show up as a portable device and can move all information to PC.
For some reason it shows the used data in both, but is unreadable. and only shows the SD external if I connect the phone with mount as a disk drive. ( I did back it all up that way on the external SD).
Thinking this could be my PC, I tried phone one and everything sync connects No problem in any setting. ( did try usb debugging on both phones to test).
So is there any way to see the internal storage or any ideas why it is not reading the same as phone one. ?
Thank you!!
Go to recovery then mount internal from there, one you get everything backed up format your internal memory...
Sent from my TBD753B using xda app-developers app
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.
As the title says implies, I am having trouble writing data to my external SD card - both through the phone and while connected to a PC.
Background: Got the S4 about a week ago. It was on NK1. I rooted, de-bloated, and made back-up in SafeStrap. Discovered I had to run the KK SD Card fix, but was able to write to the SD card afterwards. Yesterday, while trying to copy a file to the SD card while connected to a PC resulted in a failure (Device stopped responding or was disconnected error). After that, the whole phone went wonky - Titanium, Root Explorer, File Manager, etc... wouldn't open and/or run properly after wards. Several reboots and the problem persisted.
Figured I would just restore my back-up. Well I screwed something up and got stuck in a boot-loop - I odined back to NC5 (figured I didn't need to be on NK1), and re-rooted. Setting my phone back up I realize I can't write to the SD card again. I run the SD Fix but to no avail. Opened Root Explorer and looked at platform.xml, which has all the correct permissions (as in this post).
What's going on and how do I fix this? The SD card is a pretty important feature for me. I can write to and copy to the internal storage either through the phone and while connected to a PC, but not the SD card. FWIW, the SD card works flawlessly in my old phone, so I know it;s not the card.
Going nuts here.
Thanks,
Edit - So playing around with another (lower capacity) SD card I find that everything works perfectly. When I get time this weekend I will have to reformat and/or get a new card. Strangely, the problem card still works good in my old phone. Very weird.
Turns out the sd card was/is bad. Found a great deal on a 64gb card and it's working great.
So now for more noob questions: What is the correct procedure for restoring and or flashing roms with safestrap? On my other phones I'm used to entering recovery (TWRP) and wiping data/cache/dalvik, formatting, doing a factory reset, etc, then flashing and or restoring.
When I attempted to restore my backup on my S4 (as described above), I wiped data, dalvik, & cache. After that I either did a factory reset or format (can't remember which), the phone automatically rebooted, and that is when I got stuck in the bootloop and couldn't enter safestrap recovery. I am interested in flashing Eclipse but would like to know the exact procedures to avoid losing the ability to enter safestrap.
Thanks for the advice.