Related
I have CWM v5 newly installed. I immediately ran a backup with it and all went well. Now, a little later, I've been looking into CyanogenMod and wanted to tiny baby steps so I was nice and confident with things.
I tried to do another backup from CWM and it said it couldn't mount /sdcard. I tried to restore and the same error. Rebooted a few times and it's the same still.
I booted normally and checked with a standard file manager and /sdcard was fine. I haven't changed anything since the time it was working but I still seem to have broken things
What can I do?
EDIT: Actually, since getting CWM on the device, I have played a little with ADB commands and replaced the bootanimation.zip. Everything works when the phone is booted normally so that can't have caused it. Can it?
You really like new threads eh?
I presume you don't have a physical micro SD card, and you've changed kernels again at some point. Now the sdcard mentioned in newer CWM recovery is the external_sd, which you don't have. Use the internal SD card option.
oinkylicious said:
You really like new threads eh?
I presume you don't have a physical micro SD card, and you've changed kernels again at some point. Now the sdcard mentioned in newer CWM recovery is the external_sd, which you don't have. Use the internal SD card option.
Click to expand...
Click to collapse
I love them I do search before hand to see if there are similar threads relating to my device but because there aren't, I thought making a new thread per issue would be helpful. I can keep it all in this thread though if that's the etiquette around here though.
I used kTool to flash the zImage from the link you pointed out in my last thread, that gave me CF-Root v5 and CWM. I haven't changed anything since that point so if it worked once, I don't understand why it won't work again. You have confused me about the sdcard/external_sd. I have a card in the device, and everything normally saves to /sdcard but there's also /sdcard/external_sd which is always empty. I also see /sdcard/usbStorage where I have put some files too, but I don't really understand the naming conventions.
As I said, look for the "internal sd card" option in CWM recovery.
I'll add a bit more in the hope you don't need to keep posting.
If you don't have a physical micro SD card in your phone and you try to use any of the "install/backup/restore to/from sdcard" in newer versions of CWM recovery, it will give an error about being unable to mount /sdcard. Also, as far as I know, /sdcard/usbStorage refers to USB OTG, so unless you've got a USB OTG cable and a memory card/HDD plugged in, you shouldn't be writing files to that location.
Backed up successfully to internal sdcard, although I wasn't able to restore from it first which I don't understand because there should be the original one from earlier somewhere.
Turns out I was wrong, I don't appear to have a card in that SD slot even though I could swear there was one. And I can create files/folders in /sdcard/external_sd/ so I give up, lol.
EDIT: Nope, just the normal USB that came with the phone. I created the files/folders directly in the phone when I tested it.
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.
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
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.
Ok, without getting into the cascading series of screwiness along the way, I think I've managed to effectively brick my phone. I'm posting in hopes that the part of my brain screaming "No, you're missing something" is right.
e970, already rooted, running CyanogenMod 10.1 and TWRP 2.6.3.0. In pursuit of a "clean slate" to deal with remnants of sloppy uninstallations, I thought I'd clear everything with TWRP and just put CM back. So, I pulled out my SD card with my saved data, and had TWRP wipe everything, including the CM zip on the root of the built-in storage. I copied the newer CM and GAPPS to a spare SD card, plugged it in...
and I found the external SD card wasn't recognized by TWRP. There's only 1 storage location listed, which is the built-in area I just wiped.
I can't get the phone to be recognized by a desktop running Windows 8.1. I have freshly installed the drivers, downloaded the SDK, rebooted, etc. from that side. The phone is never recognized by either Windows or ADB. So, I dug out the laptop I originally installed CM from some time back (last year?). Same story - no Windows or ADB recognition.
Ok, fine - maybe the USB port is dying on me. I'll try formatting the SD card and see if that's the issue. FAT32, copy the files back, still no luck. Great. Maybe it's the card, so I copy my data and put the zips on the original card I had in the phone. Still no dice.
So, here I am. No OS installed, no image on the internal drive to recover from, TWRP won't recognize my external card(s), and I can't get anything to acknowledge the phone via USB to do a sideload.
Am I missing something, or did I completely hose myself?
I forgot to mention: I did try different cables and ports on both computers before arriving at the idea the e970 USB port may have having issues.
Have you tried a different SD card?
SD card have a finite lifespan, and I've seen them fail n the middle of normal use. The first thing I'd try would be a different SD.
If that doesn't work, you may have to just LGPNST back to bone stock.
(You may want to play with the "Partition SD Card" option under "Advanced" in TWRP. It'll wipe any data on the card so back up to your computer first, but this may kick the SD card into being recognized by the phone [though I dont know how windows would react to it])
OMGMatrix said:
Have you tried a different SD card?
SD card have a finite lifespan, and I've seen them fail n the middle of normal use. The first thing I'd try would be a different SD.
Click to expand...
Click to collapse
I did, in fact. I tried it on a spare first, so I didn't have to worry about erasing the data on the SD card I pulled out of the phone. When that failed, I tried copying the zips onto my original card, which was also not picked up. I've found other posts on here that suggest this particular version of TWRP had issues reading external cards, but I don't see any way to get a different one on the phone at this point.
OMGMatrix said:
(You may want to play with the "Partition SD Card" option under "Advanced" in TWRP. It'll wipe any data on the card so back up to your computer first, but this may kick the SD card into being recognized by the phone [though I dont know how windows would react to it])
Click to expand...
Click to collapse
I might be missing the mark here, but wouldn't this format the already-empty internal storage (since it's the one selected) rather than the external card?
elvinone said:
I did, in fact. I tried it on a spare first, so I didn't have to worry about erasing the data on the SD card I pulled out of the phone. When that failed, I tried copying the zips onto my original card, which was also not picked up. I've found other posts on here that suggest this particular version of TWRP had issues reading external cards, but I don't see any way to get a different one on the phone at this point.
Click to expand...
Click to collapse
If you can boot the phone into fastboot (should be VOL UP + Power), you should be able to flash the recover that way with:
fastboot flash recovery <name of recovery>.img
You'll need to get the .img instead of a flashable zip obviously, but that can be done even by grabbing the "recovery.img" file from a flashable recovery zip.
elvinone said:
I might be missing the mark here, but wouldn't this format the already-empty internal storage (since it's the one selected) rather than the external card?
Click to expand...
Click to collapse
I've honestly not messed with this option; I just know I've solved similar problems with flash drives in the past by formatting in different ways.
OMGMatrix said:
If you can boot the phone into fastboot (should be VOL UP + Power), you should be able to flash the recover that way with:
fastboot flash recovery <name of recovery>.img
You'll need to get the .img instead of a flashable zip obviously, but that can be done even by grabbing the "recovery.img" file from a flashable recovery zip.
Click to expand...
Click to collapse
How is he going to do that? He can't get a PC to recognize the phone.
Maybe try a Linux box? You could make an Ubuntu live USB stick with some extra storage space on it, and try running adb from there.
Sent from my LG Optimus G using Tapatalk
dandrumheller said:
How is he going to do that? He can't get a PC to recognize the phone.
Maybe try a Linux box? You could make an Ubuntu live USB stick with some extra storage space on it, and try running adb from there.
Sent from my LG Optimus G using Tapatalk
Click to expand...
Click to collapse
There's a thought... I think I have a Knoppix disk around here that I could boot from. I don't have high hopes, since it's not being recognized by the laptop I did this on originally, but I'll give anything a shot at this point. I'll let you know how it goes.
No dice. ADB gives me the same response whether the phone is at the fastboot screen or the sideload inside TWRP.
[email protected]:~/Documents/android-sdk-linux/platform-tools$ ./adb start-server
[email protected]:~/Documents/android-sdk-linux/platform-tools$ ./adb devices
List of devices attached
[email protected]:~/Documents/android-sdk-linux/platform-tools$
Click to expand...
Click to collapse
OMGMatrix said:
(You may want to play with the "Partition SD Card" option under "Advanced" in TWRP. It'll wipe any data on the card so back up to your computer first, but this may kick the SD card into being recognized by the phone [though I dont know how windows would react to it])
Click to expand...
Click to collapse
I tried this but didn't have any luck. It looks like it is trying to hit the external card, but still isn't recognizing it.
E: Unknown File System: 'datamedia'
Updatition partition details...
Partitioning SD Card...
E: Unable to locate device to partition.
Click to expand...
Click to collapse
Check ALL your cords
Another update. After presuming me e970 dead, going to Best Buy to shop for an AT&T Next upgrade, running the HTC One m8 for a couple days, I get a wild hair to try the HTC cord on the old phone. Oddly enough, it works and the phone was picked up immediately. I've already pushed CM over via adb, and and working on gapps now.
Apparently both of the cords I tried previously weren't up to spec for smartphone use. I'm going to have to come up with a labelling system on what's good for trickle charges and what's good for data.
I'm not sure what a return will do to my upgrade status, but I'd rather wait on a new phone. It even looks like I know what I'll get. Thanks for the ideas along the way.
Nice, glad you found a solution. Unless things have changed with the new plans, you should be OK to return the phone within 14 days and keep your upgrade.
Sent from my LG Optimus G using Tapatalk