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
Related
I'm trying to get files (my photos mostly) off the internal storage of my Vibrant. I don't care about getting the Vibrant working again, just getting my files off it. I can get into recovery mode, but mounting usb storage *does not work*, even tried unplugging and replugging the phone but no dice. I can install zips from the sd card (though it takes 5x longer than normal) but any ROM I install, stock, cyanogen, slim, etc. won't actually finish booting.
Because USB mounting doesn't work, I'd like to use CWM to copy all the files on the internal storage to the sd card. Then I can put the sd in another computer and get the files off. In CWM I can do a backup to sd, but that doesn't backup photos, just the rom. Is there a way to generally copy files from internal to the sd using CWM?
Also, the entire time I'm in recovery mode my PC makes the sound for a usb device being connected and then disconnected, assume that has something to do with the Vibrant being generally busted.
In summary:
Trying to recover files from vibrant phone storage
Can't boot any regular ROM
Can get into CWM recovery
USB mount in CWM recovery *does not work*
Can install zip from sd card
Can backup to sd card
Have a spare working vibrant for charging battery
Any ideas?
Okay I'll see if I can help any. First of all, can you successfully use Odin to return to stock firmware? Have you even attempted using Odin?
Can try using recuva or there is another one too but the XDA search is missing right now. Moped_Ryder usually recommends that one that I can't remember right now, but once the search button is back, I'll let you know what it is. Works like a charm. Droid recover or Droid Files, ahh I can't think of it but there is a solution on here somewhere.
Try a program called Android Commander.
Ive transferred files in CWM with it all the time.
Agreed with android commander. It has always worked for me. There are other solutions too with these new kernels these days. You can download Devil kernel or subzero via PC(They both include new file manager in recovery).Put it on your external card, flash, reboot back into recovery. Mount your internal and external cards from mounts and storage menu. Go to file manager and copy/paste away.
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.
I am having an issue creating backups. Last time I had issues with what seemed like the sd card, I bought a new 64 gig card and replaced my old one.
The old one still works fine with an adapter into my pc, but I wrote it off and sucked it up.
I just tried again making a backup in TWRP with an error, "unable to create backup folder". So, I switched over to CWM and tried the backup. Same issue.
I just checked with my phone plugged into my pc and the file system is defined as "Generic Hierarchal" which I've never seen before. I am almost positive I formatted it initially as either fat or ex fat. With the phone on, I have no issues with the card. I have music and other data on it and it reads just fine.
Other possibly relevant history:
previous rom was Beans 21 and was unable to update to 22 (do not remember the error)
wiped and loaded Alliance's latest V8 with no issues. Been running Alliance for a few weeks now with zero issues. (other than backup)
Do I need to wipe my card and format it in the phone? I think previously I formatted it in my win 7 pc with an adapter.
TIA for any info
Formatting the card with TWRP is probably better
I had this issue with an S3 and nothing would work. I tried mounting/remounting, formatting, and even a new SD card. It finally worked with a new SD, which is really weird because it was an old SD card compared to one of the newer ones.
Thanks for the response. I have 2 cards. Just cleaned off one and formatted in the phone. Still fails trying to do a backup. I hate the thought of buying a third 64 gig card.
I think I'll try going back to stock and see what happens. It'll be a while before I can. Sucks I can't backup first.
Thanks again for the response
interesting update, for anyone that might be watching this post: I d'loaded skips updated toolkit from here: http://forum.xda-developers.com/showthread.php?t=2052788&page=10
and was able to make a backup.
just FYI
Bought a Sammy 64 and same issue. Unless anyone has any other suggestions, I'm going to Odin back to stock, I guess.
back to stock, unlock, root fixed it. just fyi.
georgepink said:
back to stock, unlock, root fixed it. just fyi.
Click to expand...
Click to collapse
Not. Tried to load another rom and can't read from ad card. Damnit. Any help would be appreciated.
more drama...I re-loaded twrp, b/c I found an old post with roughly the same issue. It said to use cwm to fix permissions. Well, cwm doesn't offer that anymore, the comment is that it was placebo effect. twrp still does offer it. I ran it and then rebooted to android, then rebooted into twrp reco again and was able to load Alliance v8 again.
so, until 4.4 roms appear (which I will have to go back to cwm for, unless twrp gets updated) I guess I'm set.
I'd still LOVE to hear from someone who might know how this happened or what exactly happened, to know what to avoid.
Thanks again, to the one person that responded.
Back to square 1, cannot make nandroid backups.
In CWM v6.0.4.3 here's the errors:
trying to backup: Can't mount Backup Path
trying to mount external_sd: Error Mounting /external_sd
In TWRP v2.6.3.0 here's the errors:
trying to backup: backup folder: /external_sdcard/TWRP/Backups/
E:unable to create folder: /exterenal_sdcard/TWRP
E:Failed to make backup folder
Any thoughts? I know I've posted this multiple times, but not sure where to turn. I suspect if I go back to unrooted stock again and unlock / re-root, load twrp and fix permissions, it will work again for a while. But not permanently. I really want to fix this once and for all. But am not getting any clear direction to go. I have searched on and off XDA to no avail. hoping this time is the key. Thanks for reading and potentially helping.
Hi guys,
I can't work out why but when I go to wipe all settings then install custom rom from zip file in cmw recovery, it completes normally but after the reboot it just stays on the android bot. I went back into recovery and managed the phone through usb to my PC & saw that in the phone storage there was nothing where there is obviously supposed to be boot files. I have installed this custom rom before & it has been no problem. I also have tried a few other roms (all that i've tried before & they all work) and the same thing happens. I have found one rom that worked strangley and when I manged the phone on my PC i saw that it has placed the boot files on the sd card (not the phone storage).
how can i fix this.
i am very new to rooting so please no complicated talk
can someone not help? this is a big issue.
ill try and explain the problem in more detail below...
i have been messing with my phone lately using CMW TOUCH to wipe my data then install rom from zip. everything was going great until now.
i want to install a rom (that i have installed before.so i know its compatible with my phone), i go through tge same procedure of wiping data then installing from zip.all goes the way it should with it telling me its installing from zip, after a while it tells me to reboot the phone. when i do all that happens is it stay on the green android bot for 1 min then reboots. i went into CMW TOUCH to connect phone to pc & found out that it installed nothing, nothing on the phone storage and on the sd card except the custom rom.
i have tried this with few other roms all with the same results.
NOW...
ive managed to find a rom that will install so it is functional all except recently after a reboot it has stopped detecting the sim，weird.
i connected the phone to my pc to find that all boot files are stored on the sd card not phone storage like it used to.
i had an idea that i will try later today and that is to move the custom rom over to the phone storage from the sd card. remove the sd card during install. maybe that will force the install to use the phone storage for the boot files
will let you know the outcome
jamos
i have just tried to install the rom with the sdcard removed from phone & the same thing happened. even though during the installation it tells me that it is formatting system then installing it installs nothing to the phone storage.
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.