I have my flashed my NC using dual boot with Froyo (refer to the topic here) and I cannot backup my ROM using CW 3.0.1.0 (or 3.0.0.6). It gives me the error "can't mount /system!". I think it is related to the dual boot because the partition changes. Has anyone else been having this problem? Does anyone know how to fix it?
Sorry I had to bump, but does anyone know how I can fix the "can't mount /system!" problem with CWR? I really need to backup my ROM before doing other things.
If I cannot get CWR backup to work, does anyone have have other suggestions for backing up my ROM?
Thanks
Bump. I'm having the same problem.
There is a link from "funcrusher" in another thread that apparently solves the problem. I can't post links since I'm new to the forum.
Related
So if I goto ROM Manager, I can successfully install CWM. I goto "Reboot into CWM" and I get a install error when it tries to boot. I am able to boot into CWM via MicroSD card but NOT from just my Nook device. I had some issues a few days ago where I accidentally whiped the /system and /data. I've since fixed it (i thought) but I cant help but think this issue is related.
Any ideas...?
DroidHam said:
So if I goto ROM Manager, I can successfully install CWM. I goto "Reboot into CWM" and I get a install error when it tries to boot. I am able to boot into CWM via MicroSD card but NOT from just my Nook device. I had some issues a few days ago where I accidentally whiped the /system and /data. I've since fixed it (i thought) but I cant help but think this issue is related.
Any ideas...?
Click to expand...
Click to collapse
I had this problem too. It happened to me, because I had screwed up the boot partition. I had to restore to stock, and then re-nooter to fix it.
I have the same problem running nookie froyo from emmc. I've tried a bunch of different things but have never been successful.
I was able to get it working on stock rooted fine thouhh. Has anyone successfully gotten clockwork running with nookie froyo without using the clockwork sd boot?
philburkhardt said:
I had this problem too. It happened to me, because I had screwed up the boot partition. I had to restore to stock, and then re-nooter to fix it.
Click to expand...
Click to collapse
Was it easy to restore to stock?
I would download the repartition boot from http://forum.xda-developers.com/showthread.php?t=929670 , put it on the micro sd along with CWR and flash. This should fix your boot partition, which you then can reinstall CWR if you so desire.
If that doesnt fix boot then use http://forum.xda-developers.com/showthread.php?t=931720
volwrath said:
I would download the repartition boot from http://forum.xda-developers.com/showthread.php?t=929670 , put it on the micro sd along with CWR and flash. This should fix your boot partition, which you then can reinstall CWR if you so desire.
If that doesnt fix boot then use http://forum.xda-developers.com/showthread.php?t=931720
Click to expand...
Click to collapse
will this work on my Nookie froyo on emmc?? without wiping my data?
I am struggling with the exact same issue. I used the Monster Root Pack to restore my messed up NC 1.1 this weekend. After i got everything back to 1.0.1, I have been unable to do a nandroid from CWM. It kept failing. After some searching on this forum, I found that the CWM zip that is included in Monster Root Pack isn't working. So I tried to flash the zip from CWM thread. That errored out, too! I'm glad I found this thread.
So, what does the repartitioning boot do? How would that fix the issue of CWM not flashing? Also, does flashing the repartition force me to have to go back to stock?
Anyone have any success with this?
Preston
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.
Hi everyone I really hope someone of you can help me with this issue
This is my coinfiguration
Nexus One, with the latest radio & HBoot installed, ClockWork recovey 3.0.0.5 and original SD as memory card (4GB)
After wiping everything from recovery and formatting the Mcard with 128MBswap & 512MBExt I am no longer able to install any CyanogenMod 7 release either nightly or stable. I did try to clear storage from bootloader and replacing the RA 2.2.1 without success. At the moment the only rom I can install is the MIUI and the stock one GRI40, all Cyanogen got stuck after the boot. Is any other way to do a kind of hard reset at the phone?
Many thanks in advance
EDIT: apologize I did post into a wrong area, MOD please move to the correct place
Thanks
Are you flashing a compatible gapps?
Also, try using a different recovery...
as i posted i did try both recovery (ra 2.2.1 & clockwork). i haven't flashed any google apps as I did flash the rom only
The Nexus One doesn't need a swap partition, try re-partitioning your card without that.
Try to download this: http://www.mediafire.com/?bxfijcp6f6bf1me
Then flash it from Amon-RA. It'll format your system partition too.
mindfrost82 thanks for the link but it seems not working, do you have another one available?
Many thanks
mindfrost82 said:
The Nexus One doesn't need a swap partition, try re-partitioning your card without that.
Try to download this: http://www.mediafire.com/?bxfijcp6f6bf1me
Then flash it from Amon-RA. It'll format your system partition too.
Click to expand...
Click to collapse
I can't tell you how many users PMed me after using that format utility to find out that when they try to flash a new ROM, they only can boot to recovery, no matter what they do. A nandroid backup with a system image or going thru a restore process involving fast boot img restores is the only fix. Just reporting what I have seen myself using that utility.
guys thanks for your effort but I gave up. I still don't understand why my N1 won't launch Cyanogen7, but for sure there is something wrong on my telephone. After installing without issue the Kang-o-rama 1.2 b3 I notice that after launching the market the main page is blank stating that there is no application available...O_O
Try this:
Install the recovery following what is said here in "Second Method (manual method)"
http://wiki.cyanogenmod.com/index.p...pdate_Guide#Second_Method_.28manual_method.29
BUT use this recovery http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-2.5.1.4-passion.img instead of the 3.0.0.5.
After that, flash this file
http://www.mediafire.com/?bxfijcp6f6bf1me
(it deeply wipes everything away, thank temasek for this stuff)
Then flash CM7 release and Gapps following what is said here
http://forum.cyanogenmod.com/topic/20115-cyanogenmod-7-for-nexus-one-v700-10-april-2011/
I hope this helps
I'll give a try, thanks for the tips
I am trying to create a back up of my system and the backup errors out in the data portion. It does not say why. Just says error when backing up on /data. I am currently on a rooted stock rom. I have tried using older versions of clockworkmod recovery with no success. Any help would be greatly appreciated. THANKS!
Sent from my DROID3 using XDA App
Are you using Koush's or Hashcode's versions specifically for the d3? Im asking because I thought there was only 2 versions and you said you tried older versions.
Sent from my DROID3 using XDA App
I used them both. Koush offers to flash older recoveries which is only 2 so far. I currently have hashcodes version and the same thing it going on.
I flashed the stock deodex via clockworkmod recovery and it worked like a charm. I then downloaded another zip and tried to flash it then i could no longer boot into clockwork recovery. So to solve that i deleted the d3 bootstrap then redownloaded it and i could boot into it again. So maybe try that then try a backup again? Im not sure why you would be getting an error
Sent from my DROID3 using XDA App
Well, you have to redo the bootstrap on droid 3 after every fresh install of a new ROM. I have tried deleting the bootstrap and reinstalling it with no success. It still errors out on the backup of the data portion. Maybe I might take a risky move and flash a new ROM without a backup and see if it is able to backup the data after the install. I hope I just don't brick my phone or get a bootloop. I would be screwed!
Installed Steel Droid v2 successfully but I tried a backup and it still had an error while back-up up of the data portion. I am at a loss of ideas on what to do next. Any help would be greatly appreciated. Thanks!
mothman57 said:
Installed Steel Droid v2 successfully but I tried a backup and it still had an error while back-up up of the data portion. I am at a loss of ideas on what to do next. Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
Maybe you have a corrupt fat filesystem on the backup destination...
Have you tried to do a checkdisk when connected to the pc ?
I just completed a checkdisk and I even formatted the SD Card yet still the same issue! I then tried to checkdisk the partition of the internal memory yet no success. Thanks for the help though. It is greatly appreciated.
Steel Droid 3 came out today. I installed the new ROM and still it errors out on the /data portion of the backup. Hopefully someone can help me here. Last resort is a full factory reset of the device. I am waiting before I do that.
Is anyone else experiencing these same issues?
Try SBFing, re-rooting and then using the tweaked boot-strapper. When all else fails, start from scratch. If that's still not working, I would venture to guess that your /data partition has issues (which SBFing should fix).
What OS are you using?
I'm having a different problem that maybe some can help with. I just flashed the sbf again, and I've rerooted stock, and now I'm trying to reflash SteelDroid3.
I'm running into an error I haven't had before with CWR. Everytime I try to flash any ROM (from internal or external) it fails - E:Can't open "location" (bad)
I've checked MD5 sums and tried muliple roms, all give the same error.
I started with Hashcodes tweaked Bootstrap, then uninstalled and tried koush's. Neither made a difference. I even tried CWR 5.0.2.5 vs 5.0.2.6 to see if that would make a difference. No luck there either. Even tried reflashing the SBF, still no go after getting reset up.
I can make nandroids, and I can restore nandroids, (restored a debloated I had made earlier no problem) So the only issue is flashing a new rom.
Any idea's
Thanks
I have windows 7 64bit on my computer. Android phone is the 2.3.4 with steel droid v3 ROM. As far as SBF goes, should I use the example on the android development section of RSDlite? And if I preform this, will it delete all my data/apps and restore it to like a factory reset?
Im having similar issues. Backups are not being created properly - the zip files only contain 2 files:
data.ext3
system.ext3
I have one backup that works from a week ago - it contains the following files:
.android_secure.vfat
cache.ext3
data.ext3
nandroid.md5
system.ext3
any ideas why backups wouldn't be created properly? (using the modified bootstrap and CWM)
That is exactly what I am experiencing as well. Just the system and data are being preformed, but the data is not properly finishing.
I think we just need more room on our SD cards. I cleared up a few gigs of info, and now its working just fine. give it a shot.
I dont think that is the issue. I have 14.6gb worth of free storage on my card. It has to be an issue with my internal storage or clockworkmod. I am guessing it is my internal storage.
Sent from my DROID3 using XDA App
Well, I decided to do it. I flashed the original unrooted ROM back on the phone. I have to say it sucked redoing all my phone tweaks, but it did fix the issue. I can now preform back-ups in full! Thanks for all who replied in this forum.
hay,
sorry to start another thread about this. I have been searching through the possible fix's for my gnote with the emmc problem.
Ill explain my situation. Im not exactly sure what i did wrong. I made sure to install abyss kernel and reboot recovery. wiped data and caches and installed new rom(paranoidandroid). So this is my problem. I keep getting failed attempts to do something. So i went back into recovery to try and reinstall rom and says emmc not found. I can still boot into the rom. But cannot do some tasks. It still functions as a phone and all that.
So was wondering if i should just stick to what i have, minor issues so far, or try one of the fixes.
help is greatly appreciated
cheers
EMMC meaning the microSD card?
yeh, cant access photos or music thats on there so im guessing it is the internal storage. when i try to go to install zip from sd in cwm it says emmc not found.
Ive only had the phone for a week. is it best to reset counter and flash another rom if i can and take it in and get warranty.
Flash Abyss kernel boot into its recovery and try to install any gb roms and see wat happens