Cant Backup Rom Anymore -- "Cant Mount Backup Path"

[naudan]

I am having a weird issue with Clockwork - Rom Backup . I tried it twice now and it says" Can't mount backup path. unknown volume for path /emmc/clockworkmod/backup/2012-07-10-20.56.48"

Anyone have any idea why this is happening?

I am on jelly belly 2.2 - was going to upgrade, tried to run a backup twice and got this message. Its important to note that I flashed Franco Kernel. Is it possible the Franco Kernel is the cause? I was able to backup Jelly Belly 2.2 before the Franco install.

If it is the Franco, how do I go back to a stock one? Is there a general repository of Kernels?

 

[zero neck]

Did you try flashing cwm again?

If that doesn't work, you can fastboot flash a diffrebt recovery and try makinga backup with that, but the different recoveries make incompatible backups generally, so keep that in mind

Its probably not francos

 

[naudan]

I haven't really tired to do anything futher with my phone. I am afraid of installing anything in fear that it wont work.

I dont have a lot of experience in this stuff, but have leverage a lot of the guides and Dmmarck himself on installation (so I know I did it correct).

How does one reflash CWM? Do I just click the button? Is there anything else I should be doing prior to it? I flashed CWM the first time with Wugs and I have the current version installed.

 

[zero neck]

You have rom manager app? In rm, hit the button to flash latest cwm version. THats the simplest way.

Or you can DL cwm IMG and do it in fastboot but it sounds like your not at that level of comfort yet

 

[naudan]

Ok so I just reflashed CWM - Tried to run a backup, same error mesage. Rom Manager Version 5.0.0.8 ClockworkMod Recover 5.5.0.4

I am thinking it has to be the Franco Kernel, right?

 

[zero neck]

I dont know, my instinct would be it's not the kernel, but i'm just guessing. You have other backups??? If so, i would go flash a different kernel if yo uwant to test it out.

Otherwise, it could be a bunch of things less easily fixed.

 

[2defmouze]

It's not the kernel. I'd suggest as zero did, trying a different recovery such as TWRP, but this sounds like one of those issues people had earlier with the JB ports where the only real fix was a factory image restore and full wipe. You can backup whatever you don't want to lose to your computer first, then do the restore following the instructions in the Factory Images thread, lock and re-unlock the bootloader. It isn't hard, just takes a few minutes.

Sent from my Galaxy Nexus using Tapatalk 2

 

[naudan]

Ok to test my theory about the kernel -- what should I flash?

I went from 4.0 to 4.1 without changing the kernel, everything was fine. So is it OK if I flash an ice cream sandwich kernel?

or should I flash a jelly bean kernel? I found tha vicious posted a jelly bean kernel here:
Stock Flashable JellyBean kernel boot.img format:
http://developer.clo...k-JB-Kernel.zip
MD5SUM: e616cc84fdd020b1d51c9215f00f834c (This is if you prefer the stock JB Kernel)

Advice would be great

 

[2defmouze]

Ok to test my theory about the kernel -- what should I flash?

I went from 4.0 to 4.1 without changing the kernel, everything was fine. So is it OK if I flash an ice cream sandwich kernel?

or should I flash a jelly bean kernel? I found tha vicious posted a jelly bean kernel here:
Stock Flashable JellyBean kernel boot.img format:
http://developer.clo...k-JB-Kernel.zip
MD5SUM: e616cc84fdd020b1d51c9215f00f834c (This is if you prefer the stock JB Kernel)

Advice would be great

Your theory is bunk and there's no need to test it, lol. The kernel is going to have zero effect on the issue of your recovery not recognizing your external storage partition, which is what is happening here. Take my advice from earlier

Sent from my Galaxy Nexus using Tapatalk 2

Sent from my Galaxy Nexus using Tapatalk 2

 

[naudan]

Well -- I just flashed a JB Kernel -- no dice.. same issue. so you win that battle.

I just dont get it and am confused. I dont get how i was able to flash jelly belly and back it up fine, only to have the backup stop working.

I am scared to use TWRP because all the directions around this place relate to Clockwork. I dont even know where to start with it.

Is there a post on factory image restore and full wipe?

 

[naudan]

OK now more confusion -- I now tried to "backup" my system straight from ClockworkMod Recovery instead of from the "Rom Manager".

It seems to be working.. (going through the process now but no inital error).

Any reason you can see why it works from CWR and not from Rom Manager when esentially it is doing the same thing? I followed the steps in the first section of this post: http://forums.androidcentral.com/ve...backup-restore-install-roms-galaxy-nexus.html

 

[2defmouze]

Oy.. You didn't mention in the first place you had been using ROM Manager and not doing it straight through recovery, which would have been the first thing we told you to do. Uninstall rom manager and never use it again, lol.

Alright so you are able to get it to work via recovery now?

Sent from my Galaxy Nexus using Tapatalk 2

 

[dmmarck]

OK now more confusion -- I now tried to "backup" my system straight from ClockworkMod Recovery instead of from the "Rom Manager".

It seems to be working.. (going through the process now but no inital error).

Any reason you can see why it works from CWR and not from Rom Manager when esentially it is doing the same thing? I followed the steps in the first section of this post: http://forums.androidcentral.com/ve...backup-restore-install-roms-galaxy-nexus.html

And you wonder why I dissuade people from using ROM Manager .

 

[naudan]

Oy.. You didn't mention in the first place you had been using ROM Manager and not doing it straight through recovery, which would have been the first thing we told you to do. Uninstall rom manager and never use it again, lol.

Alright so you are able to get it to work via recovery now?

Sent from my Galaxy Nexus using Tapatalk 2

Yeah it was successful straight from Recovery --- Sorry for not mentioning. I have been successful using Rom Manager for creating backups (that was all I used it for, i manually flashed stuff thanks to Dmmarck).

The only error I got was "no sd-ext found" errors, but upon Googling that, it seems normal?

 

[2defmouze]

Yeah it was successful straight from Recovery --- Sorry for not mentioning. I have been successful using Rom Manager for creating backups (that was all I used it for, i manually flashed stuff thanks to Dmmarck).

The only error I got was "no sd-ext found" errors, but upon Googling that, it seems normal?

RM causes all sorts of issues. It's complete crap. No disrespect to koush, he does a lot of good stuff and deserves to be paid for it, but not with that app.

Anyway more on-topic.. Yes just get rid of it and start doing everything from flashing to backing up all within recovery.

Sent from my Galaxy Nexus using Tapatalk 2

 

[karriaravind]

guys i have some serious problem i have motorola fire xt rooted phone i tryed to back up my rom through rom manager ...., i pressed backup rom button the phone is off and dead its not starting .., i wated for 15 mins and removed battery and tryed to start it but no use its not starting plzzzzzz help me ....:''''(