Koush Clockwork Mod Recovery Errors - Motorola Droid 3

When preforming a backup using Koush Clockwork Mod Recovery, the backup errors out during the backup of the data. It says "Error while backing up of /data." Any helpful hints would be appreciated. I tried installing a previous version, yet no luck. The system backs up just fine. I am using Verizons Droid 3 rooted.
Sent from my DROID3 using XDA App

Related

Revert keyboard from 2.3 keyboard to 2.2

ive been searching every where on how to do this with out reflashing my rom. i did a nandroid but i updated the recovery so i cant use that it gives me some suggestion to do it via adb. if there is no other way to get it back i guess i will go about it that way but if there is a apk available that will be much more appreciated!
Flash through recovery:
http://db.tt/A1VCXiM
Sent from my Nexus One using XDA App
will give it a shot thanks
EDIT: Works great! thank you so much
Glad it's resolved, but I don't see why an updated recovery would preclude you from restoring the nandroid backup. In Clockwork recovery you can go to Advanced Restore and restore only the System partition from the recent backup.
Sent from my Nexus One using XDA App
cmstlist said:
Glad it's resolved, but I don't see why an updated recovery would preclude you from restoring the nandroid backup. In Clockwork recovery you can go to Advanced Restore and restore only the System partition from the recent backup.
Click to expand...
Click to collapse
You can also flash another custom recovery from ROM Manager...
Sent from my Nexus One using XDA App
cmstlist said:
Glad it's resolved, but I don't see why an updated recovery would preclude you from restoring the nandroid backup. In Clockwork recovery you can go to Advanced Restore and restore only the System partition from the recent backup.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
wouldn't the restore overwrite the current recovery in place?
solidmac said:
wouldn't the restore overwrite the current recovery in place?
Click to expand...
Click to collapse
Recovery is not part of the system partition, and in typical nandroid backups it is not even imaged as part of the backup.
Tried link in OP, just goes to Drop Box login.??
That's because I remove the file after a while...
http://db.tt/A1VCXiM
Sent from my Nexus One using XDA App
@danger-rat, Thanks for putting it up again. Got it now.

[Q] CWM not flashing on my phone...PLEASE HELP!

Hi Everybody,
So it goes like this. I rooted my phone for the first time and I backed up using Titanium Backup. then i downloaded rom manager. Within rom manager i flashed CWM. When i get to recovery mode and i try to reinstall packages it starts a download and a quarter of the way it gives me an error like "Failed to verify whole file signature"...and installation was aborted. After trying other varius methods posted like uninstall rom manager and rebot your phone and try again. I still had no success. So in recovery mode i thought maybe if i delete my internal storage and user data with cache data it might work (not knowing what deleting user data did). after my process of getting the phone on track i checked to see if my phone was still rooted. In my applications folder i had superuser permissions so i assumed it was still rooted. I went straight to market and downloaded Rom Manager, and tried again to flash CWM. Went into recovery and i had no success, it still gave me the same error message. I downloaded Titanium Backup to restore my files (i copied my internal storage device so i have titanium backup's files that i backed up) and when it loaded up the application said that the phone is not rooted.
So to get to the point. HOw can i get CWM on my phone? and Why was titanium backup saying my phone is not rooted when i have superuser permissions and rom manager was also using it?
Thank you.
Is your stock recovery 3e?....
That is what it is, you need to look in the development section for the modded 3e recovery thread, and follow those directions!
Sent from my SAMSUNG-SGH-I897 using xda premium
It's in the sticky roll up on to if the general section...
b-eock said:
That is what it is, you need to look in the development section for the modded 3e recovery thread, and follow those directions!
Sent from my SAMSUNG-SGH-I897 using xda premium
Click to expand...
Click to collapse
Can you please post a link to the thread.
xhambone786x said:
Can you please post a link to the thread.
Click to expand...
Click to collapse
Yahh just. Sec!
http://forum.xda-developers.com/showthread.php?t=909213
Sent from my SAMSUNG-SGH-I897 using xda premium
Its a sticky. Look in the "Read BEFORE flashing!!" thread and "The Captivate Directory |Guides|ROMs|Themes|Etc.| READ BEFORE POSTING(Updated 9/7/11)" thread.... use the search as well....

CWM via Rom Manager NOW AVAILABLE!!!!

I just checked in Rom Manager and there it was "Motorola Droid Bionic" WOOOOHOOOO
Already made a back-up and no issues! Thanks to all the devs who helped to make this happen.
Acts like it installs but when I hit reboot to recovery it just does normal boot.
Sent from my DROID BIONIC using XDA App
I didn't have that problem. Uninstall bootstrap recovery, maybe?
Sent from my DROID BIONIC using XDA App
Koush said to make certain CVPCS' bootstrap is installed first.
That would be why then thanks
Sent from my DROID BIONIC using XDA App
kookahdoo said:
Koush said to make certain CVPCS' bootstrap is installed first.
Click to expand...
Click to collapse
This may be true, BUT when I bootstrap into recovery via ROM manager, I boot into the newest 5.0.2.4 version of CWM. If I bootstrap via the Bionic Bootstrap app, I boot into 4.0.1.5
Sent from my DROID BIONIC using Tapatalk
Remember to hit the "Thanks" button when someone helps you!
I tried to make a ackup using ROM Manager and it tries to use "sdcard", not the real "sdcard-ext" (the actual location of the SDHC Card. Does anyone have any suggestions. I can make a backup fine when I reboot into Bootstrap, but not when I do it through ROM Manager. Bootstrap uses sdcard-ext, while ROM Manager is using sdcard
kookahdoo said:
Koush said to make certain CVPCS' bootstrap is installed first.
Click to expand...
Click to collapse
That's interesting. I didn't have boot strap installed and i was fine.
Sent from my DROID BIONIC using XDA App
Koush said on twitter that he just released his official Bootstrap for the Bionic in the Android Market, might not show up as yet .
I know he released officially, that's why you don't need the bootstrap apk. I believe Koush said you needed the apk but that was before he released the official for Rom manager. Someone please correct me if I'm wrong.
Sent from my DROID BIONIC using XDA App
You can't get into recovery without Bootstrap not even with Rom Manager Bootstrap is the recovery. Koush made that clear when he released support for the Bionic in Rom Manger "you must have Bootstrap installed". Remember the Bootloader is Locked.
jawonder said:
You can't get into recovery without Bootstrap not even with Rom Manager Bootstrap is the recovery. Koush made that clear when he released support for the Bionic in Rom Manger "you must have Bootstrap installed". Remember the Bootloader is Locked.
Click to expand...
Click to collapse
That's real weird. I don't have the bootstrap apk. Only Rom manager and Koush's cwm recovery. I can boot into recovery and back up without any issues.
Sent from my DROID BIONIC using XDA App
I just froze bootstrap in titanium and used rom manager to install cwm. It installed fine. Then I used rom manager to reboot into recovery and that worked also. I didn't make a backup but it did get me into recovery.
Sent from my DROID BIONIC using Tapatalk
You have to open Bootstrap at least once before you can use Rom Manager to boot into recovery. The new boostrapp has fixes for Clockwork 5.0.2.1.
I bought the Bionic on the 8th but haven't rooted it. Just so people reading this thread (and myself) know. Koush's bootstrap is 2.99 on android market. But if you have a premium version of rom manager do you still have to download the bootstrap from the market?
cromanorn said:
That's real weird. I don't have the bootstrap apk. Only Rom manager and Koush's cwm recovery. I can boot into recovery and back up without any issues.
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
you may find that backup won't restore ...happened to me...just a heads up...I'm afraid to use Koush’s recovery now for fear it won't work.
Sent from my DROID BIONIC using XDA App
dubsx said:
you may find that backup won't restore ...happened to me...just a heads up...I'm afraid to use Koush’s recovery now for fear it won't work.
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Yup. I attempted a backup and restore as well. When restoring, the message was that the various images didn't exist (data image, system image, etc...).
I used Rom Manager to flash recovery and reboot, no success.
I used BionicBootstrap.apk to "Bootstrap Recovery"
and then Rom Manager to Flash latest Recovery
and then Bionic Bootstrap to Reboot to Recovery
and that worked great to achieve the latest version recovery!

[Q] Can't boot into CWM?

Could someone please tell me what the trick is to getting into Clockwork on my Bionic? I rooted it, installed CWM (Premium) from the market, and then from within CWM I flashed the custom recovery by picking the Bionic model from the menu.
Now when I try to reboot into recovery to do a Nandroid, etc. The phone just reboots instead. Do I need to install the bootstrapper or something else over the top or in place of CWM?
Thanks, please advise.
-Rob
I've seen this before. Try flashing cwm again and boot into recovery. If that doesn't work get the bionic bootstrapper and flash that. If that gets you into recovery. Good. But I would flash cwm via rom manager again.
Sent from my DROID BIONIC
The problem is you're not using the bootstrapper. It's required.
Sent from my DROID BIONIC using xda premium
^this. Solves your problem
Sent from my DROID BIONIC using Tapatalk
Thanks!
That clarification did the trick. It wasn't immediately clear to me the bootstrapper was required. Thank you guys.

TWRP backup error

Hi.
I 'm running SlimSabre on n7000 with kernel Asylum_Omni_4.4.2_kernel_20131227_n7000_additional_governors .
Today I tried to backup the device with TWRP nandroid backup, but during the backup of /data the device rebooted.
I installed temporary a CWM and I was able to backup everything.
So I tried to get rid of TWRP, but if I install CWM (recovery-clockwork-6.0.4.3-n7000.zip) and reboot, the device bootloop. Only re-installing Asylum I get back the TWRP and the device boot.
Anyone had the problem on TWRP nandroid backup ?
Moreover opening the various zip file (CWM, Asylum) I saw that some of them are not only boot.img or recovery.img, but also /bin and /etc are present.
Is there a way to move from TWRP to CWM in a clean way keeping Asyum as kernel ?
In my knowledge moving from TWRP to CWM keeping asylum as your kernel would be impossible....
I also got this issue, if you want I can tell you but the kernel would change....
Sent from my GT-N7000 using XDA Premium 4 mobile app
lakshesh96 said:
In my knowledge moving from TWRP to CWM keeping asylum as your kernel would be impossible....
I also got this issue, if you want I can tell you but the kernel would change....
Sent from my GT-N7000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just tell me, if you know... the backup done with CWM are ok ?
I mean, the fact that TWRP is not able to backup /data (with or without compression) does not mean that CWM backup will be invalid too, right ?
I can keep TWRP and switch on CWM from time to time only for backup. It's a boring procedure (install CWM, backup, reinstall Asylum) but not impossible.
CWM backups work with CWM only and TWRP's with TWRP only, they can't be intermixed...
And inorder to check a backup, as you are following the long/hefty method above, once install cwm and try to restore your backup throgh it, if it works, then way to go, if it doesn't then try reflashing kernel as well as recovery as well as your ROM.
If everything fails then try to shift to a CM based ROM which uses cwm, as its the best and the most reliable option.
Hope I have helped you ?
Sent from my GT-N7000 using XDA Premium 4 mobile app
---------- Post added at 04:19 AM ---------- Previous post was at 04:13 AM ----------
...also check and compare your cwm backup in the folder with some previous cwm backup if you have. If everything looks fine and the size of backup is considerable, depending on how much data you have of apps, then the backup should be OK. But this is only JUGAAD and not a confirmation, so do once restore.
Sent from my GT-N7000 using XDA Premium 4 mobile app
lakshesh96 said:
CWM backups work with CWM only and TWRP's with TWRP only, they can't be intermixed...
And inorder to check a backup, as you are following the long/hefty method above, once install cwm and try to restore your backup throgh it, if it works, then way to go, if it doesn't then try reflashing kernel as well as recovery as well as your ROM.
If everything fails then try to shift to a CM based ROM which uses cwm, as its the best and the most reliable option.
Hope I have helped you ?
Sent from my GT-N7000 using XDA Premium 4 mobile app
---------- Post added at 04:19 AM ---------- Previous post was at 04:13 AM ----------
...also check and compare your cwm backup in the folder with some previous cwm backup if you have. If everything looks fine and the size of backup is considerable, depending on how much data you have of apps, then the backup should be OK. But this is only JUGAAD and not a confirmation, so do once restore.
Sent from my GT-N7000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
First of all thanks for the info.
I remember that CWM (or perhaps PhilZ Touch) can restore TWRP backup (on the advanced option you can choose).
I'm only a little worried because trying to restore a nandroid backup and finding that it's corrupted actually means restore from a previous backup my data, and that's 2 month old.
I've checked the size of the file and they seems ok. They should be some simple tar, so I could try doing untar them and check if they are ok.
Anyway, thanks for the info.
I'll keep the kernel as long as I can. It 's ok and it has SmartassV2 governor that work very well.

Categories

Resources