[Q] CWM currupts my SD card and doesn't apply update zips

[drsatan316]

I have confirmed that I have root access and that my bootloader is unlocked
I have tried flashing CWM recovery via rom manager and various img files found throughout this site and others.
Despite this, when I boot into cwm I get the android guy with the yellow ball
If I hit vol up and down I get only a few options:
Bgackup and restore, reboot, apply update, whipe data factory reset, whipe cache partition.
No advanced (this is one I've seen mentioned but didn't see on my device)
But as long as I got that far, I went through the steps to install CM9.
I whiped data then cache
Applied the CM9 zip
then rebooted

When my phone came back on I still have moto gingerbread and it just wants me to relogin to blur and sign in to google.

Also tried Another SD card with the same results. CWM couldn't see any zips on the cards after reentering cwm after a reboot. Reformatting the cards and trying again produced the same results.

What am I missing here? I've followed and refollowed letter by letter with all the guides I've been seen.

Thanks for any help and I apologize for any newb stuff as this is my first attempt at android roms.

Well it looks like this is magically solved now.
After TWRP failed earlier I decided to go back into fastboot and did a erase recovery, reboot, then reflash twrp
Then tried booting into it and it worked!
So I went back into fastboot and flashed cwm instead since I'd prefer the non touch recovery.

Thanks for all the tips

 

[nerfman100]

Please remember to post questions in the Q&A forum.

I honestly don't know what's wrong. It looks like your doing everything properly.

 

[iregados]

seem like you're not with CWM installed on your device..

try to put another one like TWRP and see what happens

 

[upndwn4par]

You are certain your bootloader is unlocked? (you see "unlocked" on the Moto splash screen)

First, try to fix permissions from Rom Manager.

If that doesn't work fastboot flash the most recent recovery. Go here and get the latest version.

 

[ravilov]

I would advise against using ROM manager. It's been known to cause many issues.

 

[upndwn4par]

I would advise against using ROM manager. It's been known to cause many issues.

Oh ravilov, you and your crazy stories. I've been using Rom Manager since the day I rooted my phone. Never had one problem (well, except for the way koush does the premium license).

 

[LavLab]

Make sure you're choosing "install zip from SD card" not "install update from SD card".

LāvLab / HostileSlothRecords

 

[CaelanT]

I would advise against using ROM manager. It's been known to cause many issues.

ROM Manager is perfectly fine for fixing permissions.

 

[ravilov]

Oh ravilov, you and your crazy stories. I've been using Rom Manager since the day I rooted my phone. Never had one problem (well, except for the way koush does the premium license).

It was reportedly the culprit of randomly appearing ".nomedia" files on some ROMs. After that I don't think I'd want to trust it.
Some people also had problems installing stuff through it, no matter what they tried. Once they switched to cmd/fastboot/manual install, everything worked fine.
So I'm not exactly pulling stuff out of my butt here.

I also don't really like it personally, I always remove it if it comes bundled with a ROM. But that's just me. To each their own. If it's working fine for you, by all means keep using it.

 

[upndwn4par]

It was reportedly the culprit of randomly appearing ".nomedia" files on some ROMs. After that I don't think I'd want to trust it.
Some people also had problems installing stuff through it, no matter what they tried. Once they switched to cmd/fastboot/manual install, everything worked fine.
So I'm not exactly pulling stuff out of my butt here.

I also don't really like it personally, I always remove it if it comes bundled with a ROM. But that's just me. To each their own. If it's working fine for you, by all means keep using it.

If I remember correctly, that was for epinter's and joker's CM10 ROMs. And it was never even close to proven that CWM was the culprit. Doesn't make sense that CWM is to blame for suddenly doing random stuff. Especially since both of those ROMs have had serious media issues since day one.

Anyway, I'm not saying that CWM is perfect - it's not. But RomRacers recovery is unsupported, and I try to never use unsupported software. TWRP is nice, but I don't like touch recoveries and old CWM backups are useless. Anyway, to each his own.

 

[ravilov]

If I remember correctly, that was for epinter's and joker's CM10 ROMs. And it was never even close to proven that CWM was the culprit. Doesn't make sense that CWM is to blame for suddenly doing random stuff. Especially since both of those ROMs have had serious media issues since day one.

Anyway, I'm not saying that CWM is perfect - it's not. But RomRacers recovery is unsupported, and I try to never use unsupported software. TWRP is nice, but I don't like touch recoveries and old CWM backups are useless. Anyway, to each his own.

Um...
I'm talking about ROM manager, not CWM. CWM is great, I'm using it too (well, I'm using RomRacer's recovery which is CWM-based).
I don't mind using older and possibly unsupported software if it's this stable and works without any problems and glitches.
I'm going to assume that was a typo and you really meant ROM manager.

But yeah, ".nomedia" files don't appear out of nowhere. People were unable to find their media files and they were indeed blaming the ROM for doing that. Then someone realized it's due to some ".nomedia" files being created randomly. Then people were deleting all such files but the files would appear again. And then someone noticed removing ROM manager made the madness stop. Now I will admit this is not proof enough, but it really seems very likely that ROM manager was to blame. I think nobody had any problems with media files since.

Oh, and as for the problem OP is mentioning... No, this is not related to ".nomedia" files, and frankly I have no idea what's going on there... :dunno:

 

[upndwn4par]

Um...
I'm talking about ROM manager, not CWM. CWM is great, I'm using it too (well, I'm using RomRacer's recovery which is CWM-based).
I don't mind using older and possibly unsupported software if it's this stable and works without any problems and glitches.
I'm going to assume that was a typo and you really meant ROM manager.

But yeah, ".nomedia" files don't appear out of nowhere. People were unable to find their media files and they were indeed blaming the ROM for doing that. Then someone realized it's due to some ".nomedia" files being created randomly. Then people were deleting all such files but the files would appear again. And then someone noticed removing ROM manager made the madness stop. Now I will admit this is not proof enough, but it really seems very likely that ROM manager was to blame. I think nobody had any problems with media files since.

Oh, and as for the problem OP is mentioning... No, this is not related to ".nomedia" files, and frankly I have no idea what's going on there... :dunno:

Yeah, you know what I meant. :cyclops:

I still think it is more likely that the ROM made RM go wacky than the other way around. Especially with the history of JB ROM media issues.

 

[pre4speed]

Um...
I'm talking about ROM manager, not CWM. CWM is great, I'm using it too (well, I'm using RomRacer's recovery which is CWM-based).
I don't mind using older and possibly unsupported software if it's this stable and works without any problems and glitches.
I'm going to assume that was a typo and you really meant ROM manager.

But yeah, ".nomedia" files don't appear out of nowhere. People were unable to find their media files and they were indeed blaming the ROM for doing that. Then someone realized it's due to some ".nomedia" files being created randomly. Then people were deleting all such files but the files would appear again. And then someone noticed removing ROM manager made the madness stop. Now I will admit this is not proof enough, but it really seems very likely that ROM manager was to blame. I think nobody had any problems with media files since.

Oh, and as for the problem OP is mentioning... No, this is not related to ".nomedia" files, and frankly I have no idea what's going on there... :dunno:

I remember this happening when rom manager updated. Then a few days later they put another update distinctly saying "fixed problem of rom manager adding .nomedia to internal and external sd" so yes rav is right that rom manager was the culprit THEN. However that being said, I had tried a jb rom (can't remember which) that added those .nomedia files to my internal and external so you both could be correct in your assumptions.

EDIT: in the changelog for ROM manger here https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager it shows that it did place those .nomedia files.

 

[drsatan316]

Yes, I am certain that my phone is unlocked or at least I think I am since it says "unlocked" in the corner when I turn it on

I didn't want to sign back into everything quite yet so I haven't been able to try the rom manager fix permissions thing yet.

I flashed the TWRP recovery instead of the CWM one and got the same result when booting into the recovery so I assume that neither CWM or TWRP was successfully installed.

Shouldn't flashing these with fastboot get them in there? (technically tried installing from rom manager once too)

 

[upndwn4par]

Yes, I am certain that my phone is unlocked or at least I think I am since it says "unlocked" in the corner when I turn it on

I didn't want to sign back into everything quite yet so I haven't been able to try the rom manager fix permissions thing yet.

I flashed the TWRP recovery instead of the CWM one and got the same result when booting into the recovery so I assume that neither CWM or TWRP was successfully installed.

Shouldn't flashing these with fastboot get them in there? (technically tried installing from rom manager once too)

Yes, fastboot should be installing recovery properly.

I see three possibilities:
1) Something happened during the unlock process, so despite seeing "unlocked" you are not fully unlocked.
2) Fastboot is not writing recovery recursively
3) You have a hardware problem

I would try the following first:
1) Check to make sure you have the correct drivers installed on your PC and you have the most recent version of fastboot
2) Erase recovery with fastboot
3) Re-flash recovery with fastboot

Next I would try unlocking your bootloader again

 

[upndwn4par]

Did you ever solve your problem?

 

[drsatan316]

Yes I got it working now.

TWRP booted after I did a fastboot erase and reflashed the recovery.
So I then reflashed CWM and that booted.
When I actually went to install a ROM a few days later it didn't boot again so I reflashed and ran the recovery on the next reboot OK again.
I was able to successfully get Joker's CM10 flahsed and running.

Not sure why I'd have to reflash every time I want to run the recovery but I think that that isn't a big deal for me anymore as this was just a test and this is no longer my primary device.

Thank you all for the help