Database Users

[Q] can't get my nandroid backup to work

Hey everyone,
So i have read through many of the post about using cmw and making a nandroid backup then recovering it.
I followed the directions to put the green cwm on my phone after getting into the green cmw i made a backup and started playing around on my phone. I then went into ROM manager and wanted to get back into green cmw from there I then got a error message about my signature. So again I flashed cwm via odin and got back into it that way. I don't understand why i can't get into it through rom manager and have to flash it everytime.
My next problem is that i wiped the data on my phone and went to use my nandroid recovery that I made it got through most of it but then would freeze while revcovering the data and would sit on something like b5ece2. After waiting for 30min I just pulled the battery, but my phone is still back to stock.
This is not the end of the world for me as I have Titanium backup and got all my apps back, but for some reason can't get my contacts back using google.
Any help is very much appriciated and I am sorry about how long this question became this is my first droid and my first root.

Looks to me like your lynchpin issue is you cannot get RM to launch ClockWork mod recovery.
Solving that is your best avenue for fixing other issues.
I couldn't help but notice that you never mentioned regular (blue) recovery. Did you somehow find a guide to put in the so-called permanent CWR? I would like to understand how you are getting into recovery, because doing it through Odin doesn't parse for me.
No promises, especially without fully understanding your situation, but here is what to do if I am assuming correctly.
Best guess solution:
1. Restore recovery in odin. Get the "Odin restore file for recovery" from this guide:
http://forum.xda-developers.com/archive/index.php/t-782204.html
(a full stock restore odin should do this too, but you would have to root etc.)
2. Download CWMrecovery.tar patch ( http://goo.gl/HELdr ) from fallingup's guide, which is step two of:
http://forum.xda-developers.com/showthread.php?t=897889
3. Flash #1 then #2 as PDA in Odin. Boot. Open Rom Manager.
4. Click "Flash ClockworkMod Recovery". Click "Reboot into Recovery"
Swyped w/ XDA App. When in
doubt, mumble.

Thank you for getting back to me so quick. I will do that as soon as I get home from work and let you know if that fixes all the problems.

Stuck on MyTouch4G logo screen and can't restore nandroid - please help!

So I followed the guide to root with s=off and it seemed to work fine and I installed clockworkmod v3.0.0.5 through ROM Manager and had made 2 nandroid backups and everything seemed to be working great.
Then I tried to install CM7 RC1 through ROM Manager, thinking if anything went wrong I'd be able to restore the nandroid backups.
Something went wrong and I ended up stuck with the CM7 skateboarder animation infinitely repeating. So after pulling the battery I was able to boot into recovery. It looked like the stock recovery, but after selecting factory reset it went into Clockworkmod. From there I restored my backup, and everything seemed to work fine.
But when I reboot it just gets stuck forever at the MyTouch4G logo (the first one that comes up immediately on power up, not the second, round logo.
I've tried to restore both backups but always get stuck at the same screen.
Right now I need to get the phone working as fast as possible, hopefully to one of my backups (but if I can get it working I've also got MyBackup Pro and Titanium backups of my data and apps).
Can someone tell me what's the best way to get this working again and hopefully if it's possible to successfully restore my nandroid backup?
Thanks!!

Current:
Rom Manger (v3.0.1.0)
Recovery (v3.0.0.5)
When you go in Recovery from bootloader what color is the text green (2.x) or orange (3.x)? Keep in mind if your using 3.0.0.5 which has Recovery 2.5.1.2 then you can't flash CM7 as you need to use 2.5.1.4(Recovery) or 3.0.0.5(Recovery).
If you meet the basic requirement as you still have the rom on your SDCard. I want you to go in Recovery via bootloader. Then go in format and wipe /system, /data. Then go back in advance wipe dalvik and from main screen wipe cache, then do full factory wipe it will remount all. Once this is done select Install zip files> Choose zip files> Find and run the rom> select yes.
When you load for the first time give it some time as it will take few min but if it takes more than 5min than ya its in bootloop. If you get to the part here then it should be working but if you get stuck in mytouch 4g logo then it won't load. Now if you have green(2.x) text then what you need to do is install the Recovery 3.0.0.6.zip though Recovery as you won't be able to access Rom Manager and then try to flash CM7RC1. Let me know if you have any problem or its hard to understand. I know people always get Rom Manager and Recovery version number confused and the whole problem get started.

It says "ClockworkMod Recovery v3.0.0.5" at the top and bottom and has orange text on a black background (highlight line is white text on orange background).
This morning I managed to get it to boot by flashing PD15IMG.zip from HBOOT (took me a while to figure out I have to keep holding both down and power to get to HBOOT, just holding down and releasing power took me to ClockworkMod which wouldn't install the file).
Then I set up my account and downloaded MyBackup Pro which I used to restore visionary+ and rom manager to re-root and re-install clockworkmod then I rebooted into recovery and tried to restore my nandroid backup.
Same problem, stuck in the boot logo. So seems like these nandroid backups are useless.
Is there any way I can recover the backups? At this point I don't have much time to play with CM7 so I'd rather just get my phone back to where it was and play with CM7 a bit later when I have more time. If necessary I'll just go back to PD15IMG and manually restore using MyBackup Pro, but that backup isn't quite as fresh and it's a pain to restore the widgets, etc.
I'll try doing the wipes you suggested and see if that will bring back my backup...
Thanks!

To be clear:
ClockworkMod Recovery 3.0.0.5 -- the orange text version -- CANNOT be used with Stock ROMs, or any other Froyo-based ROM. Not backup, not restore, and not install. It is only for Gingerbread-based ROMs, like CM7.
Froyo and Gingerbread versions of Android use different filesystem structures. CWMR 3.0.0.5 is for EXT4 filesystems, which the Froyo kernel cannot mount.
At boot up, the Froyo kernel tries to mount /system, and fails, because /system is in EXT4 format that it doesn't understand. So the Froyo kernel crashes, reboots .... and fails again. And again.

That explains it. Thanks.

So I installed ClockWorkMod 3.0.0.6 and used that to restore my last nandroid backup (even though it was made in 3.0.0.5) and that seems to have worked!
CM7 does look quite nice. I look forward to playing with it when I have more time.
Thanks for your help!

Tab can't update

Sorry, i couldn't find an answer to this.
Got my Acer A500 less than a week. I've rooted it. Now trying to update Tab latest firmware to 4.010.11 but kept failing. I get the Android bee with the exclaimation mark, or update failed. I've tried unrooting it and then update, but still fail. I didn't leave the SD card in. Should i just do "factory reset", then update, then root it?
Hopefully someone can help me. Here are maybe some helpful info:
-everything stock
-use Iconiaroot 1.3 to root
-done full backup with Acer Recovery Inst. v1.5 & CWM v5.0.0
-Android 3.0.1
-kernel 2.6.36.3-0001-g9*****
-build A500_1.104.02_com_GEN1
-FLEX 02_com-gen1
-device info v 1.0
-SKU wifi

This sort of thing seems to happen with alarming regularity.
A few things to note.
The FOTA update seems to fail most often when CWM is installed (though it was fine for me). Restore your original recovery.
If that doesn't work, unroot and try again.
As a last ditch effort, do a factory reset (you'll lose your data).
Also, make sure you have plenty of storage on your external SD card.

FloatingFatMan said:
This sort of thing seems to happen with alarming regularity.
A few things to note.
The FOTA update seems to fail most often when CWM is installed (though it was fine for me). Restore your original recovery.
If that doesn't work, unroot and try again.
As a last ditch effort, do a factory reset (you'll lose your data).
Also, make sure you have plenty of storage on your external SD card.
Click to expand...
Click to collapse
thanks, will give it a shot.
and DUH, found a similar thread ...http://forum.xda-developers.com/showthread.php?t=1175139

FloatingFatMan said:
This sort of thing seems to happen with alarming regularity.
A few things to note.
The FOTA update seems to fail most often when CWM is installed (though it was fine for me). Restore your original recovery.
If that doesn't work, unroot and try again.
As a last ditch effort, do a factory reset (you'll lose your data).
Also, make sure you have plenty of storage on your external SD card.
Click to expand...
Click to collapse
I've restore the original recovery....update still fail.
Tried factory reset, but noticed CWM still in TAB when i press PWR+VOL. How do i remove CWM?

toygixxer69 said:
I've restore the original recovery....update still fail.
Tried factory reset, but noticed CWM still in TAB when i press PWR+VOL. How do i remove CWM?
Click to expand...
Click to collapse
If you use the Acer Recovery Installer, it can restore stock recovery.

FloatingFatMan said:
If you use the Acer Recovery Installer, it can restore stock recovery.
Click to expand...
Click to collapse
sorry FFM, i went into Acer Recovery Inst.
1st temp:
>Restore prev backed-up image
>Install Recovery Image
>Reboot
.....failed (droid w/triangle exclaimation)
2nd temp:
>Acer Recovery Inst.
>Stock USA 1.141.07_com_gen1 recovery
>Install Recovery Image
>Reboot
.....failed (droid w/triangle exclaimation)
On both attempts, it says "flashing tablet", the "Recovery image installed succesfully. But just don't know what to do with it from that point on.
I must be doing something wrong between steps. Trying to seek a step-by-step tutorial to remove CWM as we speak.

You might want to contact Euclid's Brother, The Acer Recovery app is his work so he might be able to help you as to why it's not restoring.

[Q] Help, solving this mystery? Bootloader/partitions?

Ok, where do I start. Here is my problem: Any of the leaked based rom get stuck at the black & white stripes (wich I flashed many time without problem) Let me explain the chain of event that got me that point.
Last week I installed the leak ( Acer_A500_1.031.00_WW_GEN1 ) and rooted it and patched the bootloader with blackthunder's apx tool that also installed a modified version of thor's cwm that work with ICS bootloader. Everything worked fine but knowing that civato's flexreaper support the ics bootloader I decided to install it...R11 worked fine (even the b&w stripes at boot was gone...thx to the ics bootloader).
This is where it got crazy, while doing simple web browsing, i got a freeze that obliged me to force shutdown. On reboot, I got a bootloop at bootanim. Decided to flash FlexR11 over it to fix. During the flash I received an error about flexrom. Rebooted and the bootloop persisted. Then cwm started to be slow responding to navigation with volume rocker, so I decided to flash Acer_A500_1.031.00_WW_GEN1 again wich didn't boot too. Cwm was still there but even more screwed, would not see any sdcard int or ext. I tried to apx push a recovery with blackthunder's tools with no success.
I finally got it back to life with TimmyDean's EUUs flashing a rooted 3.2.1. with HC bootloader. Now the only ICS rom I can install is thor's rom ..everything work fine. BUT any of the leaked based rom get stuck at the lines and even the leak itself after being installed get stuck at the acer logo...and cwm is still present where it should have been overwriten.
I think it may have something to do with flexrom (i guess thor don't use that partiton since it's for acer crapware)...but im not sure since 3.2.1 work with acer's stuff & all. Maybe the bootloader is corrupt in some way, but it was reinstalled by the EUUs tool anyway.
I tried to format everything including flexrom..tried both civato's kernel in case there are some bits of ics bootloader left... Im desesperate trying to understand what's wrong exactly and how to fix this.
Anyone have an idea? Thx in advance & sorry for my average english.

lowsum said:
Ok, where do I start. Here is my problem: Any of the leaked based rom get stuck at the black & white stripes (wich I flashed many time without problem) Let me explain the chain of event that got me that point.
Last week I installed the leak ( Acer_A500_1.031.00_WW_GEN1 ) and rooted it and patched the bootloader with blackthunder's apx tool that also installed a modified version of thor's cwm that work with ICS bootloader. Everything worked fine but knowing that civato's flexreaper support the ics bootloader I decided to install it...R11 worked fine (even the b&w stripes at boot was gone...thx to the ics bootloader).
This is where it got crazy, while doing simple web browsing, i got a freeze that obliged me to force shutdown. On reboot, I got a bootloop at bootanim. Decided to flash FlexR11 over it to fix. During the flash I received an error about flexrom. Rebooted and the bootloop persisted. Then cwm started to be slow responding to navigation with volume rocker, so I decided to flash Acer_A500_1.031.00_WW_GEN1 again wich didn't boot too. Cwm was still there but even more screwed, would not see any sdcard int or ext. I tried to apx push a recovery with blackthunder's tools with no success.
I finally got it back to life with TimmyDean's EUUs flashing a rooted 3.2.1. with HC bootloader. Now the only ICS rom I can install is thor's rom ..everything work fine. BUT any of the leaked based rom get stuck at the lines and even the leak itself after being installed get stuck at the acer logo...and cwm is still present where it should have been overwriten.
I think it may have something to do with flexrom (i guess thor don't use that partiton since it's for acer crapware)...but im not sure since 3.2.1 work with acer's stuff & all. Maybe the bootloader is corrupt in some way, but it was reinstalled by the EUUs tool anyway.
I tried to format everything including flexrom..tried both civato's kernel in case there are some bits of ics bootloader left... Im desesperate trying to understand what's wrong exactly and how to fix this.
Anyone have an idea? Thx in advance & sorry for my average english.
Click to expand...
Click to collapse
Sounds like you have data leftover (either not a good enough wipe, or corrupted data)
Try this. Note that this will reformat your entire internal memory, but will ensure all remaining data is cleaned up and removed.
Before installing your rom;
1. Wipe User Data
2. Wipe Cache
3. Wipe DalviK
4. Wipe Battery Stats
go to Backup and Restore. Select "Toggle backup and restore of internal storage (/data/media). Enable this setting by selecting it. By default, it is disabled. Then proceed to the formatting steps. This will format the Entire Internal Memory when you proceed.
Select Go Back, Goto Mounts and Storage
1. Format System
2. Format Cache
3. Format Dalvik
4. Format Flexrom
This WILL format your entire internal memory, so if you have something important, you need to copy it out. Note that this should not effect things on the Ext SD Card.

Thanks for replying, yes I already done that, the problem persist. I wonder if it could be the bootloader, but like I said, other roms works, only the leak based have problem. Is there a way to "format" the bootloader? It should have been reset to HC when I applied 3.2.1 in apx... hmmm very strange!

lowsum said:
Thanks for replying, yes I already done that, the problem persist. I wonder if it could be the bootloader, but like I said, other roms works, only the leak based have problem. Is there a way to "format" the bootloader? It should have been reset to HC when I applied 3.2.1 in apx... hmmm very strange!
Click to expand...
Click to collapse
Well, more than likely it is indeed a bootloader issue. But you must understand, all these "leaked" ICS roms are what they are... BETA. And with each new leak, there's a different bootloader. So you have to pay attention to the instructions for the specific leak. Usually involves flashing a newer or older bootloader to match the rom.
Until Acer releases an "official" ICS Rom and source code for the 500/501, these issues are going to be around for awhile.
My choice, would be to run a 3.2.1 rom. Very few issues with some of the mildly modded ones. Then wait awhile, till the official ICS updates come out.
One good thing out of this, you learned some tricks on how to recovery from some "semi-bricks"

I think the leak may not be the source of the problem, I already installed 009 when it first appeared a couple of weeks ago, and restored with EUU without problem, but this time with 031 I rooted it with blackthunder's root tool and applied a modified bootloader and cwm recovery. Even if I restore 3.2.1 with timmydean's EUU package and hc bootloader, the leak base rom get stuck at the b&w lines (where it's looking for the bootloader or loading kernel). It make no sense to me that the leak is the source of the problem. Is there a diagnosis tool that can check my partition integrity? Still wonder...!

lowsum said:
I think the leak may not be the source of the problem, I already installed 009 when it first appeared a couple of weeks ago, and restored with EUU without problem, but this time with 031 I rooted it with blackthunder's root tool and applied a modified bootloader and cwm recovery. Even if I restore 3.2.1 with timmydean's EUU package and hc bootloader, the leak base rom get stuck at the b&w lines (where it's looking for the bootloader or loading kernel). It make no sense to me that the leak is the source of the problem. Is there a diagnosis tool that can check my partition integrity? Still wonder...!
Click to expand...
Click to collapse
Well, this is one of the reasons I decided not to mess any further with the ICS builds till a good official version comes out
I'm not aware of any tools to check partition integrity. Maybe there may be something in the main Android Dev forum.
RA Recovery has an option to check your partitions, but I believe it only gives a current status whether they are EXT3 or EXT4.

Moscow Desire said:
Well, this is one of the reasons I decided not to mess any further with the ICS builds till a good official version comes out
I'm not aware of any tools to check partition integrity. Maybe there may be something in the main Android Dev forum.
RA Recovery has an option to check your partitions, but I believe it only gives a current status whether they are EXT3 or EXT4.
Click to expand...
Click to collapse
It is possible to rebuild your partition structure from scratch (using SBK + bootloader + nvflash create command + bct + flash.cfg + system image + recovery image + boot image + probably some other things) but I'm not sure of anyone that has done this and I can't say I have myself. Using timmydean's method (with a, what looks like, leaked Acer A500 Flash Tool) should, in theory, wipe it clean and start again.
I created a flash bundle to reset back to version EUUs_SBK_Acer_A500_1.016.05_COM_GEN1 (it's on the forum I use which I got tempbanned for mentioning publicly ) but it's untested. I see no reason it shouldn't work, however.

I tried another way to restore my tab, this time flashing a leak based rom with RA recovery instead. This time i had a little different behavior, during flash process, formating flexrom froze for a while outputing this error: Random Offset : 0x188 ...the rest flashed normally. At first boot it froze after 2sec during bootanimation, before it froze at the black & white lines.
I think I may have a corrupted flexrom partition, so Im wondering, does the recovery*doing a quick format erasing only the first sectors? If so, is there any way to do a deep format?

CWM crashes OS when I try and make a backup.

I managed to root the Note 3 with CF- Root. Currently on 4.4.2 EE. That was easy. I then installed CWM and it advised I needed to update the app which I do. If I then ask it to make a back up it reboots in to recovery but does not appear to do anything? If I then reboot the device the App's all crash one at a time. The only way to resolve is to wipe/Factory reset.
I am not sure what I have done wrong here? This is not a boot loop....It just bombs the current rom.

Nothing? No advice? As this is not a boot loop searching has not really helped.

o0wiz0o said:
I managed...(
Click to expand...
Click to collapse
Who do you ask to make a backup ? Which app have you installed ? Cwm Rom manager ? Did you even install cwm recovery within the app ? If you updated the app, with that you didn't install the recovery.
You must power off your phone and reboot to recovery with the 3 button combo. Then, when in recovery, make a backup (if you have a custom recovery installed ?). Don't use any "boot to recovery and make a backup" apps or such, it can screw things up.
But my advice, install the latest twrp recovery. Definitely better.

Thankyou for taking the time to answer.
Yes I installed clockwork Mod. It said it was installing Cwm and offered the option to reboot and make a current backup. Which it then seems to fail. I see no manual option to make a back either when in the boot menu.
I'll try twerp and see what happens. I used to use Cwm a long time ago on a first gen galaxy and it was great. Something is just amiss this time.

Yeah, it didn't install cwm recovery, otherwise you would have the option to backup. Stock recovery doesn't have that option.
Last time i checked, this cwm manager wasn't the best option to manage your backups and restores. The 3 button combo to boot into recovery and then make a backup or restore is the way to go.
I too had problems with cwm in the past, but then i went for twrp and all is good. Plus, imo, it has a nicer touch interface.