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.
Related
I booted into Clockworkmod Recovery (3.0.0.5) and did a successful backup but when I REBOOT after it is complete it keeps going back into the recovery screen again.
This is driving me nuts. This was a brand new (received today) NC rooted with Auto-Nooter 3.0. I set it up the way I wanted it then did a full backup. Now I can't get out of the backup screen after a reboot.
How can I fix this so I can get back into the O/S?
This happened to me too. I'm still new and dont know why there are specific versions of CWR for specific ROMs... Or why the same version of CWR cannot restore its own backup.
But reinstalling http://forum.xda-developers.com/showthread.php?t=947071 via a sdcard image worked. If your nandroid/cwr backup does not work I hope you have a titanium backup.
MisterEdF said:
I booted into Clockworkmod Recovery (3.0.0.5) and did a successful backup but when I REBOOT after it is complete it keeps going back into the recovery screen again.
This is driving me nuts. This was a brand new (received today) NC rooted with Auto-Nooter 3.0. I set it up the way I wanted it then did a full backup. Now I can't get out of the backup screen after a reboot.
How can I fix this so I can get back into the O/S?
Click to expand...
Click to collapse
Place the file I attached in root of your SDCard and run it from CWR and it will remove CWR and restore you to Autonooter 3.0.0
Apparently CWR has issues with 1.1.0 ROM. This worked for me, when I had the very same issue. I wish I could find the original post I got this from so I could give them the credit.
http://forum.xda-developers.com/showthread.php?t=914690
Ok, this is where I originally got the cwr-removal.zip file, author was samuelhalff
migrax
Same thing happened to mine i ended usinthe removal tool and clearing the cach and then reinstalling the stock zip. I probably spent a good 3 hours figuring it out.
Sent from my LogicPD Zoom2 using XDA App
Ok, so I installed cyanogen and wanted to go back to cupcake (some problems with compatibility for some apps). Made backups but lost them from file corruption. Even recent backups come up with MD5 sums mismatch on ClockworkMod Recovery. Can get cyanogen running again, but can't get back to ORIGINAL state.
I've tried hard booting 8x, I've tried running the script to change the bootcount but this just gets me to clockworkmod. I try running the factory reset/data wipe option, but it clearly doesn't remove cyanogen. When I reboot after this, I get stuck on the word ANDROID in blue. I've also tried sideloading a 1.1 version zip, all to no avail. Any suggestions? Would uninstalling clockworkmod help? Thanks.
Did you flash the 1.1 stock nook image with win32? Remember that in the 1.1 restore you just install "update.zip" through CWM. Are you sure that your original version was 1.1 and not 1.0.1? If all else fails, try a different SD card. Sometimes the SD card itself is the source of problems like this.
Factory resets won't do anything once you have flashed a new rom. You will have to restore it to stock. Nooks are very difficult to hard brick, so something should work.
No, I didn't flash it, just installed the update. My original version was 1.0, but would that make a difference? I wanted to go to 1.1 anyway. Tried a diff sd card, same problem. Any other suggestions?
No matter what I try, it seems cyanogen simply WON'T wipe. Even after formatting via clockwork, and after clockwork tells me it's successfully formatted, it still boots up as normal. I believe it's interfering with restoring to stock.
Solved
MUST uninstall clockwork mod. Finally worked after this step http://forum.xda-developers.com/showthread.php?t=960542&page=16 as per instructions here. Thanks everyone!
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
So I just got this phone, and I've been trying to get it up to ICS. I've gone through and was able to complete the ICS update the first time completely, installed Safestrap, etc. Now this is where the issues came in. I did a backup, and then I started restoring some apps from titanium, from an old phone. This is where I started getting constant force closes. Tried fix permissions, went through again, same issue. So I wiped the phone, and went to restore with safestrap - it failed. Now on bootup, it refuses to even boot into safestrap anymore. All I can get is either a blank screen, or motorola recovery menu. By the fact that I can get into the motorola recovery menu, I presume it's not fully bricked, but I know there can be issues with installing on top of Safestrap.
Long story short, my question: In this condition, will flashing the same file I did during the ICS leak installation through Moto Recovery allow the phone to boot? Or will that cause a brick like downgrading from ICS does?
So, just to be sure, you installed one of the ICS leaks correct? Then you installed safestrap 2.0?
Sent from my Droid 4
Yes, that's exactly what I did. Was able to boot up into Safestrap (2.0) and restore through Safestrap, but after wiping /data I got errors with restoring a backup, and after rebooting to attempt it again, Safestrap splash screen no longer appears for me. It has the initial splash, and where the Safestrap splash should be, it just stays blank screen.
Not sure what would have caused this. I don't think you'll be able to flash the zip again since it looks for a .219 system build. Might be worth a shot though. You could also try booting into recovery and doing a factory reset. If neither of those work, try following the instructions for upgrading from one leak build to another.
Sent from my Droid 4
Tried Factory reset already, and attempted just flashing the update anyways - got an error saying build.prop file was invalid/missing?
Now I'm going through the tool steps to swap between ICS builds. At least I'll hopefully get something working.
Though I did do a step I forgot to mention, if that explains why it happened. After the Safestrap restore failed, I tried to do a partial restore of /system and /data. /system restored fine, when I went to do /data it said it was restoring /system in the log - could that have been an issue? A possible mistake in safestrap that overwrote the wrong folder? Or just an issue with the menu?
Doing the ICS switch got it working for me. Now to attempt round 2 and see if I can get into CM9, and Safestrap works right.
More research, root cause : Forgot to install busy box when doing the initial root.
Glad you got it working!
Sent from my Droid 4
Hi everybody! I recently installed safestrap 3.72 and installed a couple KitKat roms, everything worked great until I tried to install AzureRom it said E: Unable to mount ' /system'. After that it can no longer mount the system partition... I've tried multiple things and I can't find anything that will work including wiping, formatting, and fix permissions. I also cant flash any roms because of this. I figured out how to use ROM-Slot-1 and able to boot SlimNote but it is very, very buggy and I have zero memory whats so ever. I tried to uninstall Safestrap through the apk but it did nothing. Please help and give me any ideas!!! Thank you so much for all your help!!
antnyhills said:
Hi everybody! I recently installed safestrap 3.72 and installed a couple KitKat roms, everything worked great until I tried to install AzureRom it said E: Unable to mount ' /system'. After that it can no longer mount the system partition... I've tried multiple things and I can't find anything that will work including wiping, formatting, and fix permissions. I also cant flash any roms because of this. I figured out how to use ROM-Slot-1 and able to boot SlimNote but it is very, very buggy and I have zero memory whats so ever. I tried to uninstall Safestrap through the apk but it did nothing. Please help and give me any ideas!!! Thank you so much for all your help!!
Click to expand...
Click to collapse
Because azurerom is 4.3 and you are on 4.4. Boot to slimnote on your slot and try to load up a 4.4 rom on your sd or internal memory. Boot to ss then go to stock slot and advanced wipe and wipe everything EXCEPT sd card then flash the 4.4 rom you loaded.
Last time I checked I wasn't able to flash roms, even after wiping but I'll try it. Thank you
antnyhills said:
Last time I checked I wasn't able to flash roms, even after wiping but I'll try it. Thank you
Click to expand...
Click to collapse
Hope you get it figured out, if anything you can restore to mj5 and start out fresh.
posersk8r said:
Hope you get it figured out, if anything you can restore to mj5 and start out fresh.
Click to expand...
Click to collapse
How can I do that? Odin?
http://forum.xda-developers.com/showthread.php?t=2559715
Im Having the same issue I cant install ANY rom they all say
E:unable to mount '/system
E:unable to mount '/systemorig
Please help!?!?
mrmead2 said:
Im Having the same issue I cant install ANY rom they all say
E:unable to mount '/system
E:unable to mount '/systemorig
Please help!?!?
Click to expand...
Click to collapse
Are you on jb? Kk? What rom you trying to flash?
i Have no rom installed now...I was running Dynamic Kat 3.0
I have safestrap 3.72...
was trying to install URDroid
mrmead2 said:
i Have no rom installed now...I was running Dynamic Kat 3.0
I have safestrap 3.72...
was trying to install URDroid
Click to expand...
Click to collapse
That's weird, never had that mounting error before. If you can boot to ss 3.72 try doing a full wipe EXCEPT sd or ex sd. If you still have urdroid saved or kk backup try to flash or restore for kk backup. If it still doesn't work, read 4 posts up.
mrmead2 said:
Im Having the same issue I cant install ANY rom they all say
E:unable to mount '/system
E:unable to mount '/systemorig
Please help!?!?
Click to expand...
Click to collapse
i have this issue on my stock slot in safestrap. i don't think it's even able to wipe /system. for some reason, it can't touch /system at all.
i'm googling around and came across this thread. i'll post again if i am able to find a resolution.
If nothing else works, go back to MJ5 (link on page 1).
If that fails, bring the phone to an AT&T Device Support Center. What will most likely happen is that they'll try to reflash it, fail and replace the phone. (If evilpotatoman's MJ5 restore fails, it's usually a bad motherboard.)
isharted said:
i have this issue on my stock slot in safestrap. i don't think it's even able to wipe /system. for some reason, it can't touch /system at all.
i'm googling around and came across this thread. i'll post again if i am able to find a resolution.
Click to expand...
Click to collapse
I have the same problem! I achieved root yesterday (finally) and tried to install the Firenote rom. It wouldn't take, so I restored my backup to try again. But when I tried again, it wouldn't mount E:. It wouldn't even allow me to restore backup. It failed to mount every time in stock slot. Eventually, it wouldn't even let me create a slot at all!
Out of desperation, I entered recovery and wiped data, and when I booted into safestrap again, I was able to create a slot, where I installed Alliance KK to have a functioning phone. Wifi works, although it's buggy (wifi doesn't work on Dynamic 3.2). So I'm stuck.
I tried downloading safestrap again and uninstalling/installing it, hoping that would work, but it didn't. The only thing I can think of that I did wrong was that I took the micro SD card out a few times while in safestrap without properly ejecting it, but I'm not sure if that had anything to do with it.
CPT Crunch said:
I have the same problem! I achieved root yesterday (finally) and tried to install the Firenote rom. It wouldn't take, so I restored my backup to try again. But when I tried again, it wouldn't mount E:. It wouldn't even allow me to restore backup. It failed to mount every time in stock slot. Eventually, it wouldn't even let me create a slot at all!
Out of desperation, I entered recovery and wiped data, and when I booted into safestrap again, I was able to create a slot, where I installed Alliance KK to have a functioning phone. Wifi works, although it's buggy (wifi doesn't work on Dynamic 3.2). So I'm stuck.
I tried downloading safestrap again and uninstalling/installing it, hoping that would work, but it didn't. The only thing I can think of that I did wrong was that I took the micro SD card out a few times while in safestrap without properly ejecting it, but I'm not sure if that had anything to do with it.
Click to expand...
Click to collapse
Yo fire rom is mj5, read up before you go flash happy. You can't go back to 4.3 once you are on 4.4 with the 4.4 bootloader...
Sent from my SM-N900A using XDA Free mobile app
tylerholbrook said:
Yo fire rom is mj5, read up before you go flash happy. You can't go back to 4.3 once you are on 4.4 with the 4.4 bootloader...
Sent from my SM-N900A using XDA Free mobile app
Click to expand...
Click to collapse
Doh! Sorry! That explains a lot.Would that have screwed up my stock slot in safestrap?
isharted said:
i have this issue on my stock slot in safestrap. i don't think it's even able to wipe /system. for some reason, it can't touch /system at all.
i'm googling around and came across this thread. i'll post again if i am able to find a resolution.
Click to expand...
Click to collapse
I had this same problem until yesterday, I followed the instructions found here . I was able to restore my phone back to KK goodness, root, install busybox and safestrap, then flash a rom to my (previously untouchable) root slot. It worked perfectly