When trying to do a BACKUP from CWM it fails with the message:
"can't mount /system"
I did the "fix permissions" but that didn't help. The recovery is version 3.0.1.0 but I also tried 3.0.0.6 with same problem.
Rooted with auto-nooter 3.0.
Any suggestions would be appreciated.
Arghhhhhh! After flashing to 3.0.0.6 and trying the backup after I reboot it goes right back into the CWM.
Now I can't even load the O/S.
Edit: I recently remapped the vol keys. Worked fine but I'm wondering if that could have caused this mess.
I tried restoring from a previous backup and it also failed with "can't mount system" and now I'm stuck at the "n" screen. Looks like it's time for a fresh install. Back to square one.
I am in the same boat. Could you please explain how I can perform a fresh install?
dragongunner86 said:
I am in the same boat. Could you please explain how I can perform a fresh install?
Click to expand...
Click to collapse
Well, I wasn't able to. It kept booting back into the recovery module.
You can try the "8 reset" method.
Power off power on. As soon as you see the "n" power it off again. Do this 8 times and on the 8th time it MIGHT reload the original Nook software. I have done that a few times before and it always worked (I had to reload 1.1 and re-root). This time I must have really f'd it up and was not able to restore.
It's going back to B&N tomorrow. It suddenly just totally died. Lucky coincidence.
I experienced the same after updating to 3.0.1.0 from rom manager. I fixed it by flashing http://muffinworld.net/android/nookcolor/clockwork/cwmr_3.0.1.0.zip from recovery -- same way you'd flash a ROM or kernel etc. It updates both recovery/kernel.
Just an idea in case you get yours powered up again.
funcrusher said:
I experienced the same after updating to 3.0.1.0 from rom manager. I fixed it by flashing http://muffinworld.net/android/nookcolor/clockwork/cwmr_3.0.1.0.zip from recovery -- same way you'd flash a ROM or kernel etc. It updates both recovery/kernel.
Just an idea in case you get yours powered up again.
Click to expand...
Click to collapse
Thanks. I wish I would have seen that earlier.
funcrusher said:
I experienced the same after updating to 3.0.1.0 from rom manager. I fixed it by flashing ... from recovery -- same way you'd flash a ROM or kernel etc. It updates both recovery/kernel.
Click to expand...
Click to collapse
I was having a similar problem. Same error of "can't mount /system", but the backup would just fail there and then I could reboot, no problem.
I used this fix by copying the linked ZIP file to my SD card and then using the clockwork recovery console to "install from ZIP file". Rebooted after and started the backup again from inside Rom Manager. It's working now.
Thanks!
I know this is a slightly old thread but I have a question.
I am just root stock and simply wanted to backup my system before trying the CM7 ROM.
When I run ROM Manager and simply try to "Backup Current ROM" it gives me the "can't mount /system" error.
I purchased ROM Manager I am unsure if any of the advice above applies to me since I am not currently running any ROMS. I just want to do a system backup.
Related
A few weeks ago I flashed the Cognition V2.2 ROM and everything was fine until it started getting twitchy a few days ago. I tried to use the ROM Manager to restore the backup that was created during the flash but I keep getting the same error message and the phone does not seem to go into the Clockwork Mod Recovery but stays in the Android system recovery. The message says that the whole-file signature has failed to verify and that the installation was aborted. Does anyone have any idea how I can get my phone back to normal?
gtcochran said:
A few weeks ago I flashed the Cognition V2.2 ROM and everything was fine until it started getting twitchy a few days ago. I tried to use the ROM Manager to restore the backup that was created during the flash but I keep getting the same error message and the phone does not seem to go into the Clockwork Mod Recovery but stays in the Android system recovery. The message says that the whole-file signature has failed to verify and that the installation was aborted. Does anyone have any idea how I can get my phone back to normal?
Click to expand...
Click to collapse
Common knowledge that the version of Cognition you are running is not supported by ROM Manager, it is 3e recovery and Clockwork needs 2e. You can update to the newer Cognition which has 2e recovery. I recommend you read the facts sheet befor flashing, the method you should use is Odin one click back to stock http://forum.xda-developers.com/showthread.php?t=731989, then master clear so that nothing is lingering from your previous setup, backup everything from your internal storage to your pc first, this will wipe everything from your internal, replace it after you finish Master clear. you should only replace the update.zip, ClockworkMod and your music, photo's and that stuff. Backup your apps using Titanium Backup.
Here's the link for the new Cognition http://forum.xda-developers.com/showthread.php?t=786532
So I tried what you recommended and got my phone back to the stock condition but I'm still not able to use ROM manager or flash another ROM. After I root the phone I install ROM Manager, flash it to the current edition and then try to reboot into recovery but when it gets to recovery it gives the following error message...
--Installing from package...
Finding update package...
Opening update package...
E:Can't open /cache/update.zip
(bad)
Installation aborted
Also the header of the screen states that I am in Android system recovery <2e>. If I am not mistaken, shouldn't I be in recovery <3e>? If so how do I get there? I've tried flashing the stock Kernel but that didn't work and I even installed the internal betas correctly but no cigar.
gtcochran said:
Also the header of the screen states that I am in Android system recovery <2e>. If I am not mistaken, shouldn't I be in recovery <3e>? If so how do I get there? I've tried flashing the stock Kernel but that didn't work and I even installed the internal betas correctly but no cigar.
Click to expand...
Click to collapse
did you really read Rhi's post?
in order to use rom manager (clockwork mod) you must be using 2e!
my brain hurts from all the lack of searching people in this forum seem to have a problem with
Pirateghost said:
did you really read Rhi's post?
in order to use rom manager (clockwork mod) you must be using 2e!
my brain hurts from all the lack of searching people in this forum seem to have a problem with
Click to expand...
Click to collapse
LOL, +1
Touche, but the error still remains. Does anyone have any positive ideas? Like I stated before, I still cannot put my phone into clockwork mod recovery.
gtcochran said:
Touche, but the error still remains. Does anyone have any positive ideas? Like I stated before, I still cannot put my phone into clockwork mod recovery.
Click to expand...
Click to collapse
so put it in download mode, and use ODIN one click back to stock...then leave it the hell alone....
Like I said, I've already used Odin. Everything is back to stock except for the Kernel and a stock kernel install with Odin doesn't seem to work. Odin says that the install passed but nothing changes on the phone itself. All things considered, the phone is stock but not capable of going into Clockwork Mod recovery.
gtcochran said:
Like I said, I've already used Odin. Everything is back to stock except for the Kernel and a stock kernel install with Odin doesn't seem to work. Odin says that the install passed but nothing changes on the phone itself. All things considered, the phone is stock but not capable of going into Clockwork Mod recovery.
Click to expand...
Click to collapse
When you go into stock recovery now is it version 2e or 3e?
gtcochran said:
Like I said, I've already used Odin. Everything is back to stock except for the Kernel and a stock kernel install with Odin doesn't seem to work. Odin says that the install passed but nothing changes on the phone itself. All things considered, the phone is stock but not capable of going into Clockwork Mod recovery.
Click to expand...
Click to collapse
if you used the one click back to stock then you are on the stock kernel.....what makes you think you are not on the stock kernel?
The recovery is 2e
I believe that the kernel is not stock because when I look at the phone information it says that the kernel is
2.6.29
[email protected] #2
I'm not sure that it is stock or not but my gut tells me that it isn't.
gtcochran said:
The recovery is 2e
I believe that the kernel is not stock because when I look at the phone information it says that the kernel is
2.6.29
[email protected] #2
I'm not sure that it is stock or not but my gut tells me that it isn't.
Click to expand...
Click to collapse
Rom manager will work just fine with 2e recovery. Just delete any update.zip files you have in your home directory - then open rom manager and reflash clockworkmod the cappy - then you should be good to go.
As for whether or not that is the stock kernel I am not sure, but how can you tell just by looking at it if you don't know which kernel is the stock one?
I've mounted my internal and external sd cards and removed any updates but it still gives the same error. After I used the odin one-click to flash the stock rom I used the master clear as recommended. Now, if I am not mistaken, shouldn't that erase all of my user data? I reinstalled my espn app so I could follow my football team and the app still remembered my preferences and favorites. This makes me think that the master clear did not finish the job. Thoughts?
gtcochran said:
I've mounted my internal and external sd cards and removed any updates but it still gives the same error. After I used the odin one-click to flash the stock rom I used the master clear as recommended. Now, if I am not mistaken, shouldn't that erase all of my user data? I reinstalled my espn app so I could follow my football team and the app still remembered my preferences and favorites. This makes me think that the master clear did not finish the job. Thoughts?
Click to expand...
Click to collapse
Master clear should've done that. If you are restoring your apps and settings using Titanium Backup then you are restoring user data which you should not do.
When you Master Clear is your device on and on the home screen, it needs to be. Don't Master Clear in Recovery mode or Download mode or it does nothing. Also you need to have debugging on.
2.6.29
[email protected] #2
That is the stock kernel. Just so you know if you are running stock with root you can simply place the update.zip from the Clockwork folder, you should have backed up before flashing and Master clear, back into your internal. ClockworkMod does fail on first attempt to flash sometimes, it happenned to me the first time I flashed it, the second time worked like a charm. Are you rooted? You need root to use ROM Manager and debugging should be on.
gtcochran said:
I've mounted my internal and external sd cards and removed any updates but it still gives the same error. After I used the odin one-click to flash the stock rom I used the master clear as recommended. Now, if I am not mistaken, shouldn't that erase all of my user data? I reinstalled my espn app so I could follow my football team and the app still remembered my preferences and favorites. This makes me think that the master clear did not finish the job. Thoughts?
Click to expand...
Click to collapse
After you deleted the update.zip then opened rom manager and flashed clockworkmod it should of put a new update.zip on your phone in your home directory - can you confirm that this is the case?
Also you may not have had a successful master clear - you may want to do it again then redo odin3 one click. Also if I am remembering correctly I believe you have the option to clear cache or user data or both in stock recovery you may want to try that as well.
It all works now. The issue was with the master clear. I guess that I did try to run it in the download mode. Thanks a million guys, i really appreciate it.
Maybe I was a bit premature on that. ROM Manager works beautifully but I cannot install updates or flash a custom ROM. The Manager was able to backup the system correctly and enter clockwork mod recovery but it cannot install the update. If the update is on the internal SD it says that...
E:Can't open /sdcard/update.zip
(bad)
and if the update is on the external SD it says that there is no such file or directory. Am I doing it wrong or is there still an underlying issue?
gtcochran said:
Maybe I was a bit premature on that. ROM Manager works beautifully but I cannot install updates or flash a custom ROM. The Manager was able to backup the system correctly and enter clockwork mod recovery but it cannot install the update. If the update is on the internal SD it says that...
E:Can't open /sdcard/update.zip
(bad)
and if the update is on the external SD it says that there is no such file or directory. Am I doing it wrong or is there still an underlying issue?
Click to expand...
Click to collapse
/sdcard/update.zip should only boot into clockwork recovery from stock recovery or boot to stock recovery from clockwork recovery if you flashed clockworkmod correctly from rom manager - and so long as you are not renaming any other files as update.zip after you flash clockworkmod recovery.
Which custom rom are you attempting to install?
I got it. The zip file was corrupted. Now, should I be able to boot into normal clockwork mod recovery with the Cognition 2.2 Beta 7 cuz when I try clockwork recovery it boots into normal recovery? I'm still a little hazy about all this.
gtcochran said:
I got it. The zip file was corrupted. Now, should I be able to boot into normal clockwork mod recovery with the Cognition 2.2 Beta 7 cuz when I try clockwork recovery it boots into normal recovery? I'm still a little hazy about all this.
Click to expand...
Click to collapse
When you first boot into recovery it should be stock recovery. While in stock recovery when you select reinstall packages it will reboot into clockwork recovery - if you flashed clockworkmod recovery correctly from rom manager and it put the appropriate update.zip into your home directory.
And just to note: don't be renaming any files as update.zip if you are using clockwork recovery to flash something.
I am having an issue with Rom Manager Premium. It won't let me backup my current ROM. I select the option and it just asks me for a filename then reboots the phone into recovery mode. I check my SD card for a backup file and nothing gets created... What gives?
I've tried googling my problem, but people say to select the "Flash Alternate Recovery" option, but it's greyed out for me. And I have the latest version of Clockwork Mod 2.5.1.2
I am running an ATT Captivate SGH-I897 with the leaked 2.2 froyo rom on the Rogers network in Canada.
Dev will also not respond to my emails.
Suggestions?
I would suggest to go into recovery then advanced I believe then choose backup. Then if you go back into rom manager you will see a backup. Rom manager is just doing the same function. I usually just use the backup or restore from recovery menu anyways and I have rom manager premium also.
Sent from MY Perception 10.1 on XDA App
I think I have this same issue with my ROM Manager now backing up. I don't have the premium version. But my phone just reboots into Recovery whenever I select "Backup Current ROM" from the ROM Manager. Then when I go back to ROM Manager and select "Manage and Restore Backups", nothing happens.
So the workaround is confusing for me.
Select "Reboot into Recovery" using the ROM Manager to go into recovery mode? I have no idea where this advanced menu is either.
I'm just a newbie to ROM Manager and trying to figure out where to see my backups of my ROM....if they even exist.
did you guys follow the directions and FLASH CLOCKWORK RECOVERY from within ROM manager?
then when it boots to regular recovery did you try REINSTALL PACKAGES?
that will put you into clockwork recovery and you can do a backup from there
Pirateghost said:
did you guys follow the directions and FLASH CLOCKWORK RECOVERY from within ROM manager?
then when it boots to regular recovery did you try REINSTALL PACKAGES?
that will put you into clockwork recovery and you can do a backup from there
Click to expand...
Click to collapse
Yes I did that first step. There is a similar post with another fix and an update.zip file attached. I tried that but it froze up during the backup. I think I ran out of space on my internal SD card. I'm not sure how much space I need to do a backup but I only have about 1200MB left on my internal. I'm trying to clear things out. My external 4Gb card is nearly maxed as well. I really want to get a 32Gb external soon.
my clockwork backups are right around 750mb
Pirateghost said:
did you guys follow the directions and FLASH CLOCKWORK RECOVERY from within ROM manager?
then when it boots to regular recovery did you try REINSTALL PACKAGES?
that will put you into clockwork recovery and you can do a backup from there
Click to expand...
Click to collapse
I found out what the problem was... the leaked 2.2 froyo rom I'm running uses the <3e> recovery which I guess is not compatable with ClockworkMod. When I try to reinstall packages it gives me a verification failed message.
So I guess I need to flash a different kernel, or find another workaround. What was the update.zip workaround mentioned before? Could you please post a link?
richuwo11 said:
I found out what the problem was... the leaked 2.2 froyo rom I'm running uses the <3e> recovery which I guess is not compatable with ClockworkMod. When I try to reinstall packages it gives me a verification failed message.
So I guess I need to flash a different kernel, or find another workaround. What was the update.zip workaround mentioned before? Could you please post a link?
Click to expand...
Click to collapse
the update.zip will not work for you if you are on the leaked 2.2 with 3e recovery.
you will need to find a kernel that allows the unsigned zips or 2e recovery...they are in these forums, i will try to find a link
So I had alot of issues rooting but im finally in, all rooted. Downloaded ROM Manager from the market and installed CWM. Says its successful, but when I manually reboot into CWM i get a error, so I cant install the 1.1 fix
Any ideas?
Really no one knows? This sucks!
This normally happens when recovery is not flashed properly. Did you try flashing again via Rom Manager? Also when you flash, does the screen show something like "Rom Manager has been granted super user permissions"?
ya, it flashes successfully through rom manager....
I think the problem is when I was trying to go back to 1.0.1 I flashed a restore through CWM. Then I whiped the /system and /data folders. The directions said to do this but I didnt realize I was supposed to do this BEFORE flashing not after. Basically I had no restore partition left so when I went and let it fail to boot 8x i got a error, and i had no OS. I ended up doing the N/Pwr, it restored, then i got a bootable CWM, booted into it and flashed the 1.0.1. But not everything seems, odd.
I can go into Rom Manager and install CWM fine, it says installation successful. But if I reboot into recovery, I get the error. I really need this fixed but im thinking it may be easier to just use a bootable CWM. Any ideas? I need to get 1.1 on here before I lose root
DroidHam said:
I think the problem is when I was trying to go back to 1.0.1 I flashed a restore through CWM. Then I whiped the /system and /data folders. The directions said to do this but I didnt realize I was supposed to do this BEFORE flashing not after. Basically I had no restore partition left so when I went and let it fail to boot 8x i got a error, and i had no OS. I ended up doing the N/Pwr, it restored, then i got a bootable CWM, booted into it and flashed the 1.0.1. But not everything seems, odd.
I can go into Rom Manager and install CWM fine, it says installation successful. But if I reboot into recovery, I get the error. I really need this fixed but im thinking it may be easier to just use a bootable CWM. Any ideas? I need to get 1.1 on here before I lose root
Click to expand...
Click to collapse
I fixed this by downloading the latest busybox from the market, installed it, then ran the "fix permissions" from Rom Manager. I then reinstalled the latest CWM, and it would allow me to reboot into recovery.
Hello all,
I have an issue with latest CWM 5.5.0.4 recovery. It says the following error:
E:Error in /cache/recovery/last_log
(Read-only file system)
and other similar errors:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
and I'm unable to reflash GalaxianSoup ROM nor restore the original backed up 3.2 factory rom.
What actually happened ?
Once bought, I managed to root, flash CWM 5.5.0.4 recovery and install the latest GalaxianSoup ROM. Everything based on the guides in development forum and successful (all latest versions). All cool! System was working fine.
Yesterday, I was using tablet, installed few apps, nothing special and later left tablet turned on and charging. When I came back, it was turned off. Okay, tried to turned on, but the system never booted and always looped (seeing only Google logo and moving gears). I rebooted into recovery and noticed the error (see above).
Now, I'm basically unable to do anything. I tried to wipe data, cache and Dalvik cache several times, and reflash GalaxianSoup again (Galaxian + Gapps) or also restore the 3.2 system backup that I've made (always fails).
I've read on some other forums that it might have something to do with damaged SD card partition or something.
I'm out of ideas. Can anyone help me pleeeeease?
EDIT: I've got european Samsung Galaxy Tab 8.9 16GB WIFI version.
EDIT: I must correct myself. After rolling back to factory rom, I was experiencing the same issues, seems there some hardware issue. I sent the tablet back for repair, seems now it had nothing to do with GalaxianSoup. No need to worry, keep up the good work.
whiplash84 said:
Hello all,
I have an issue with latest CWM 5.5.0.4 recovery. It says the following error:
E:Error in /cache/recovery/last_log
(Read-only file system)
and other similar errors:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
and I'm unable to reflash GalaxianSoup ROM nor restore the original backed up 3.2 factory rom.
What actually happened ?
Once bought, I managed to root, flash CWM 5.5.0.4 recovery and install the latest GalaxianSoup ROM. Everything based on the guides in development forum and successful (all latest versions). All cool! System was working fine.
Yesterday, I was using tablet, installed few apps, nothing special and later left tablet turned on and charging. When I came back, it was turned off. Okay, tried to turned on, but the system never booted and always looped (seeing only Google logo and moving gears). I rebooted into recovery and noticed the error (see above).
Now, I'm basically unable to do anything. I tried to wipe data, cache and Dalvik cache several times, and reflash GalaxianSoup again (Galaxian + Gapps) or also restore the 3.2 system backup that I've made (always fails).
I've read on some other forums that it might have something to do with damaged SD card partition or something.
I'm out of ideas. Can anyone help me pleeeeease?
EDIT: I've got european Samsung Galaxy Tab 8.9 16GB WIFI version.
Click to expand...
Click to collapse
Flash your recovery again through odin..
Then reflash your galaxian soup..
If not success, use odin and flash stock rom..
Dont forget backup your file from sdcard just in case if you need reset factory..
suwandiapr said:
Flash your recovery again through odin..
Then reflash your galaxian soup..
If not success, use odin and flash stock rom..
Dont forget backup your file from sdcard just in case if you need reset factory..
Click to expand...
Click to collapse
Flashing of CWM didn't help to fix the issue, installing of GalaxianSoup didnt work at all (corrupted ZIP file error...)
Thanks God, reflashing of stock ROM via Odin did work, tablet is up and running. GalaxianSoup is definitely not stable enough yet, I'll stick to the stock rom fora while. Thank you!
whiplash84 said:
Flashing of CWM didn't help to fix the issue, installing of GalaxianSoup didnt work at all (corrupted ZIP file error...)
Thanks God, reflashing of stock ROM via Odin did work, tablet is up and running. GalaxianSoup is definitely not stable enough yet, I'll stick to the stock rom fora while. Thank you!
Click to expand...
Click to collapse
Galaxian Soup is more then stable enough. Bad flashes happen and you just said you had it up and running.
bdfull3r said:
Galaxian Soup is more then stable enough. Bad flashes happen and you just said you had it up and running.
Click to expand...
Click to collapse
To be honest, it is kind of stable, but not enough, hence the beta label. Some further optimizing will be done once the team has ICS source. In my experience, it was stable, but sometimes it would turn off when in fell into Deep Sleep state. Now, the AOKP milestone 5 is giving me issues with the screen rotation. I've experienced both sides, AOSP and AOKP in their latest versions. Obviously there is more room for improvement, but I'm afraid the team is kinda stuck without source. They've done miracles without source though.
Soft brick after CM installer
Hi guys, I could really need some help here. I tried the Cyanogenmod installer and everything went fine, except my phone was stuck in
bootscreen for too long time (never booted).
In CWM recovery I did a factory reset/wipe, reboot, but to no avail; still stucked on CM bootscreen.
I then tried to flash CM11 by recovery sideloader. This goes to 100% and recovery says "Installing update", but nothing happens.
Is it supposed to install and finally reboot by itself, or should I do something?
I tried to installed zip from SD-card, but got "E:Can't mount /sdcard". I guess that means that I can't push the .zip over ADB to /sdcard
either.
What else can I try?
Edit: I wiped /data and then I could suddenly push the .zip to /data/media and the, finally flash the .zip from sdcard!
Why on earth the installer didn't wipe everything from the beginning, I don't get...
Did I miss anything obvious about the wiping thing?
A factory reset should do the trick normally. But if you ever get a message that you can't mount something you have to wipe that partition in recovery. I haven't used CWM in a long time. I prefer twrp as a recovery these days
Sent from my HTC One using XDA Premium 4 mobile app
Thanks, I'll remember that, should it ever happen again. What's the benefit for TWRP over CWM?
in Htc One i always had this problem.
I'm pretty sure you will never be able to mount SD
but its not a big problem since you can still sidepush the zip file.
and to be honest there is not much difference between TWRP and CWM . its a matter of preference.
On my Htc one i always used TWRP but on other android devices for some reason i sticked with CWM.
Ayman.y88 said:
in Htc One i always had this problem.
I'm pretty sure you will never be able to mount SD
but its not a big problem since you can still sidepush the zip file.
and to be honest there is not much difference between TWRP and CWM . its a matter of preference.
On my Htc one i always used TWRP but on other android devices for some reason i sticked with CWM.
Click to expand...
Click to collapse
Unfortunately, I was not able to sideload the image, the transfer went well, the phone said "Installing update" but nothing happened!
sblar said:
Unfortunately, I was not able to sideload the image, the transfer went well, the phone said "Installing update" but nothing happened!
Click to expand...
Click to collapse
i guess u will have to install back the official ruu and after it add the rom u want to flash on the sd card and flash it ...
let me know if it works with you.
GL
Ayman.y88 said:
i guess u will have to install back the official ruu and after it add the rom u want to flash on the sd card and flash it ...
let me know if it works with you.
GL
Click to expand...
Click to collapse
Post 2 implies op was able to flash the zip successfully after wiping /data.
Correct, and I could probably also have sideloaded after wiping /data...