Database Users

clockworkmod not letting me backup. Samsung Galaxy S.

Im sorry if this has been brought up before, but i couldnt find a thread with the same problem.. Whenever I try to do a backup with ClockWorkMod(before you ask yes i have flashed it) Anyway i click on the backup option, my phone then resets and boots into recovery, at which point it says "install default apk-files. please wait" and "install default apk-files. finished" and just stays there, with the normal recovery options, reboot, apply update, wipe data etc etc.. My phone is a rooted Galaxy S running stock Froyo.
Thanks in advance,
-b0s-

when you are in recovery what is the first thing it says ?? does is say android recovery system <3e> or does it have somethin like ClockWork Mod x.x.x.x (x being numbers)

It says "Android system recovery (3e)".

Had this same issue at one point, but this resolved it for me:
http://forum.xda-developers.com/show...4#post10624454
Do yourself a favor and download Root Explorer from the Market so that you can apply the the file supplied in the zip.

the link to that thread is broken.

Not sure what happened but try this one:
http://forum.xda-developers.com/showthread.php?p=10624454#post10624454

thanks for that ill give it a try and let you know how it goes.

Nope still not working, thanks for the suggestion anyway

you need 2e to flash unsigned zips, your still on stock recovery.
quickest easiest way just flash speedmod or voodoo kernel, gives the phone extra performance too.
or if you just want recovery flash CF-ROOT.

b0sanac said:
Nope still not working, thanks for the suggestion anyway
Click to expand...
Click to collapse
Can you please provide the steps of what you've done? You said that this didnt work for you but did you follow the instructions? Did you reboot your phone into android recovery and choose the option for installing the update.zip? Are you using Rom Manager?

You're most likely trying to do a backup using rommanager. Same thing happens to me. When on the 3e screen just reboot and then straight away enter recovery using the 3 button method. It then enters 2e recovery and begins to backup automatically. Or just start the backup with the 3 button method instead.
Sent from my GT-I9000 using XDA App

Xanaki said:
Can you please provide the steps of what you've done? You said that this didnt work for you but did you follow the instructions? Did you reboot your phone into android recovery and choose the option for installing the update.zip? Are you using Rom Manager?
Click to expand...
Click to collapse
I followed the instructions on the link you posted.

sxi200 said:
You're most likely trying to do a backup using rommanager. Same thing happens to me. When on the 3e screen just reboot and then straight away enter recovery using the 3 button method. It then enters 2e recovery and begins to backup automatically. Or just start the backup with the 3 button method instead.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
That is what im doing yes. I have tried the 3 button method, but it still puts me into 3e recovery.

azzledazzle said:
you need 2e to flash unsigned zips, your still on stock recovery.
quickest easiest way just flash speedmod or voodoo kernel, gives the phone extra performance too.
or if you just want recovery flash CF-ROOT.
Click to expand...
Click to collapse
ill try flashing one of those.

azzledazzle said:
you need 2e to flash unsigned zips, your still on stock recovery.
quickest easiest way just flash speedmod or voodoo kernel, gives the phone extra performance too.
or if you just want recovery flash CF-ROOT.
Click to expand...
Click to collapse
Thanks for that, i installed speedmod and now its all working flawlessly.

Xanaki said:
Can you please provide the steps of what you've done? You said that this didnt work for you but did you follow the instructions? Did you reboot your phone into android recovery and choose the option for installing the update.zip? Are you using Rom Manager?
Click to expand...
Click to collapse
i replaced the recovery file in system/bin using root explorer and then went to rom manager and tried to backup current rom..
after restart it said the same thing--failed signature etc etc..
is there any simple way to install cwm recovery for gt i9003 ...

[Q] Stock ROM->Cyanogen Via Androot and RomManager?

Is it possible to go from Stock ROM to CyanogenMod via this path:
1. Using Universial Androot to root
2. Install RomManager from the market
3. Install Clockworkmod recovery 3.0.6 from Rom Manager
4. Install CyanogenMod from RomManager
That would be very easy compared to using adb. And it does not require a PC like the various one click root methods.
It should work?

I am asking because these optiions are already in the cyanogenmod wiki (some of them put there by me)
And if it works without problems, it should probably be the recommended update path.
I might try it out myself, but it requires me to go back to stock rom, which I haven't done before. If I understand correctly, it is not possible to flash a 1.6 ROM from a new Clockworkmod recovery, I would have to go back to maverick or amon ra recevery?
I am running Cyanogenmod nb 12, and clockworkmod recovery 3.0.6 at the moment.

to get back to stock rom, you just have to connect your phone to the PC, and double click the .exe of the ROM

I am not using windows, and do not have a rom exe file. I rooted and flashed my phone via adb on linux. I do have a nandroid backup of my stock room after it was rooted though.

Then flash back the old amonra recovery, before restoring your backup because it won t work with the latest clockworkmod

christick said:
Then flash back the old amonra recovery, before restoring your backup because it won t work with the latest clockworkmod
Click to expand...
Click to collapse
Ok thanks, I just heard from some one at cyanogen that using RomManager to flash the recorvery on a rooted stock rom won't work. So I guess the update path in the first post is not valid...

finnk said:
It should work?
Click to expand...
Click to collapse
Uhm... I think not: is missing the "insmod tattoo-hack.ko" and it will fail the "remount" operation (and then the flash).
IMHO.
Bye
Diego

diego72 said:
Uhm... I think not: is missing the "insmod tattoo-hack.ko" and it will fail the "remount" operation (and then the flash).
IMHO.
Bye
Diego
Click to expand...
Click to collapse
Yes, I think you are right. Stock rom needs the tattohack loaded before flashing a recovery.

finnk said:
Yes, I think you are right. Stock rom needs the tattohack loaded before flashing a recovery.
Click to expand...
Click to collapse
Well, i had a CyanogenMod "installed" on my tatto, and i flashed it back to the stock 1.6 rom without installing anything, without problem.
i guess that's the question, isn't it?

I used the method you're saying, Androot+Flash Recovery from Rom Manager to the latest ClockworkMod and unfortunately it's not working.
I don't know if it is because the new clockworkmod but my advice is don't use this method. I posted some questions in other threads but nobody could help me.
I reflashed Clockwork several times even to 3.0.6, but the startup recovery menu still the same.

CWM through ROM manager

Hi all,
I saw somewhere that lfashing CWM through ROM manager is unstable.
is this still the case? or can I safely flash CWM from ROM manager and have it stick through reboots?
also, do I need to factory reset when flashing custom recovery for good measure?
(currently I'm rooted with busybox only, stock ROM)
thanks

I'm not sure if it still does a "fake flash" of recovery through Rom Manager (?) The best way to install a recovery is through fastboot.
You could also install TWRP just as easily with the Goo Manager app as an alternative.

ap1618 said:
Hi all,
I saw somewhere that lfashing CWM through ROM manager is unstable.
is this still the case? or can I safely flash CWM from ROM manager and have it stick through reboots?
also, do I need to factory reset when flashing custom recovery for good measure?
(currently I'm rooted with busybox only, stock ROM)
thanks
Click to expand...
Click to collapse
I haven't had any problems installing it through ROM Manager. Installed an update to CWM about a month ago this way and it works fine. Also just reinstalled CWM this way last night after messing around going back to stock and it boots into recovery just fine. I don't flash custom ROM's just do backups and installed su so haven't thoroughly tested it out.

If I have CWM flashed, if I do an OTA update, would I lose recovery? or worse does it cause any conflicts?
thanks

ap1618 said:
If I have CWM flashed, if I do an OTA update, would I lose recovery? or worse does it cause any conflicts?
thanks
Click to expand...
Click to collapse
You won't lose recovery. an ota will not complete without the stock recovery. You'd have to reinstall your stock recovery for an ota to be successful
Sent from my Nexus 4 using xda premium

ap1618 said:
If I have CWM flashed, if I do an OTA update, would I lose recovery? or worse does it cause any conflicts?
thanks
Click to expand...
Click to collapse
It's easy enough to adb sideload an OTA zip via CWM and you have the option to retain root IIRC.
Just search for adb+sideload+OTA.

4.2.2 Update / TWRP problem

Hello. I just received my OTA notification, but when I clicked it, it rebooted and landed my on the TWRP recovery screen. Not knowing what to do, I just told it to reboot to the system.
Once rebooted, I was still on 4.2.1, and there was no update.
Any ideas why it booted to TWRP?

The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.

MacHackz said:
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
Click to expand...
Click to collapse
Maybe before you even answer, I'm sure I'll find a link on here to show me how?
One issue I have though, is that when I manually updated to 4.2.1 on my Nexus 7, I still got an OTA update a few days later, that actually ran.
I don't ever plan on flashing roms to any of my devices. Do I need to keep a custom recovery on my Nexus 4 or 7? If not, how to I revert back to the stock recovery?

If you saved the offical stock 4.2.1 images, to revert back to stock recovery, just use the 'fastboot flash recovery recovery.**************.img' command. If you haven't, you might have to flash the whole 4.2.2 rom which you can find on the google dev website. After this, if you only want to root then you don't need to flash a custom recovery, just use the 'boot' command instead of the 'flash' one.

MacHackz said:
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
Click to expand...
Click to collapse
I flashed the OTA sideload file through TWRP and it installed succesfully.

jvbferrer said:
I flashed the OTA sideload file through TWRP and it installed succesfully.
Click to expand...
Click to collapse
How did you do that? Did you sideload wrinkle's file from this thread: http://forum.xda-developers.com/showthread.php?t=2145848?
I should let you know, that while I'm not afraid to install via the custom recovery, it doesn't mean I've done it via commands. I've always used toolkits, or one click methods of rooting and installing custom recoveries.

Well, this is crazy (weird?). I tried to flash it via TWRP by downloading the zip file in the thread referenced above, and it failed. By flashing, I mean, I chose 'Install' and pointed to the zip after moving it to my phone. After failing, I wiped the Dalvik cache and rebooted, and it's telling me 'Android is upgrading'. If it means it updated, so be it. But can anyone explain? Feeling a little confused here.
Edit: Ok, so it said it was upgrading, but it's still 4.2.1.

wvcadle said:
Well, this is crazy (weird?). I tried to flash it via TWRP by downloading the zip file in the thread referenced above, and it failed. By flashing, I mean, I chose 'Install' and pointed to the zip after moving it to my phone. After failing, I wiped the Dalvik cache and rebooted, and it's telling me 'Android is upgrading'. If it means it updated, so be it. But can anyone explain? Feeling a little confused here.
Edit: Ok, so it said it was upgrading, but it's still 4.2.1.
Click to expand...
Click to collapse
It 'upgrades' when you wipe the cache. It just means it's rebuilding the cache. Are you running an unmodified stock rom? Custom kernel?

MacHackz said:
It 'upgrades' when you wipe the cache. It just means it's rebuilding the cache. Are you running an unmodified stock rom? Custom kernel?
Click to expand...
Click to collapse
Yes, stock rom, rooted and unlocked. I did install Beats today. Could this be the problem? If so, I found a revert zip that I'm assuming is supposed to revert me back to stock audio codecs.

I don't think added files matter, but I'm guessing the Beats mod has overwritten something in system, so flash the revert zip, then try again.

MacHackz said:
I don't think added files matter, but I'm guessing the Beats mod has overwritten something in system, so flash the revert zip, then try again.
Click to expand...
Click to collapse
Flashing the revert zip failed. I'm starting to think that flashing anything with TWRP will fail.
How about this. I made a backup of all system data + apps with Titanium earlier today. Could I just reset my phone back to factory defaults, restore my apps + some system data, then re-root (*without a custom recovery*) and wait for the update again? Or will it come again?
Also, I've used Wugfresh's Nexus Toolkit. I don't remember checking the custom recovery button, but ended up with TWRP anyway. What's the easiest way to root without installing a custom recovery?

You could try that, and the update will come straiht away. You can root without flashing a custom recovery, just use the 'boot recovery' instead of 'flash recovery'

MacHackz said:
flash cwm and see if there's any difference
Click to expand...
Click to collapse
How do I do that with TWRP? Can I do it with Wug's Nexus toolkit?

wvcadle said:
How do I do that with TWRP? Can I do it with Wug's Nexus toolkit?
Click to expand...
Click to collapse
I'm not familiar with any toolkits, I would recommend flashing cwm using fast boot

MacHackz said:
I'm not familiar with any toolkits, I would recommend flashing cwm using fast boot
Click to expand...
Click to collapse
Ok, I'm surely not afraid to use the command prompt. Any tutorials you can point me to? I probably already have all of the drivers I need, as the toolkit had to download install them.

wvcadle said:
Ok, I'm surely not afraid to use the command prompt. Any tutorials you can point me to? I probably already have all of the drivers I need, as the toolkit had to download install them.
Click to expand...
Click to collapse
Check out this thread. Use flash to flash and overwrite TWRP, or boot just to test. http://forum.xda-developers.com/showthread.php?t=1995440

MacHackz said:
Check out this thread. Use flash to flash and overwrite TWRP, or boot just to test. http://forum.xda-developers.com/showthread.php?t=1995440
Click to expand...
Click to collapse
Where in that thread does it show me how to flash the stock recovery back onto my device?

wvcadle said:
Hello. I just received my OTA notification, but when I clicked it, it rebooted and landed my on the TWRP recovery screen. Not knowing what to do, I just told it to reboot to the system.
Once rebooted, I was still on 4.2.1, and there was no update.
Any ideas why it booted to TWRP?
Click to expand...
Click to collapse
The same thing happened to me. I was rooted running stock ROM with TWRP recovery (used wugfresh toolkit). The problem was I forgot I was using a modified kernel (for color correction) by molesarecoming. I flashed the stock kernel back, downloaded and flashed the OTA file from the help desk thread (http://forum.xda-developers.com/showthread.php?t=2145848&highlight=beats), and it worked. Oh, and I flashed the Superuser file immediately after the OTA did it's thing (while still in TWRP) to regain root. I didn't really like how after the initial failed install of the OTA, it took my into TWRP with no error message showing or anything.
I don't think TWRP is your problem -- I think beats is your problem. It may have modified something. Try searching the above-linked thread for answers. Honestly, there's no rush to get 4.2.2, so take your time finding the answer. It's better than wiping the phone just to install a small android update and having to redo everything on your phone again.

Ok, it must have been the Beats audio drivers. I restored a Nandroid backup from right before installing the beats audio drivers, then flashed the zip and it worked. Now running 4.2.2.
I would like to know, however, how to use fastboot via commands, so that I can learn how to flash TWRP, CWM, Stock recovery, etc.

wvcadle said:
Ok, it must have been the Beats audio drivers. I restored a Nandroid backup from right before installing the beats audio drivers, then flashed the zip and it worked. Now running 4.2.2.
I would like to know, however, how to use fastboot via commands, so that I can learn how to flash TWRP, CWM, Stock recovery, etc.
Click to expand...
Click to collapse
I need some help here - I have nexus 7 with 3G and Google (takju) with 4.2.1 installed.
I had it 'rooted" and installed TWRP .
AT the time I followed instructions to chand extension of some file to .bak - to prevent 'unrooting"
I do not remember which file I unfortunately changed.
Now I cannot install the 4.2.2 upgrade - the OTA fails because it boots into TWRP and after that I rrid several selections from TWRP screen (flash, reboot, etc) - but all attempts failed.
I have the upgrade files (bot .tar and .zip) on /sdcard directory but have no idea how to update to 4.2.2.
Tried manual flashing using adb command - all fails.
I do not have beats drivers installed
Can someone tell me how to uninstall TWRP? If the CWM recovery works with this upgrade, I would like to change from TWRP to CWM.
Or any other suggestion wold be appreciated.
I am really struggling with Android operating system the way it configured on Nexus 7 by Google - any simplest is a major pain!
Hope I can get out of this and operate the device instead of continuously meddling with operating system.
Thanks in advance
[email protected]

CWM and TWRP

Hi,
It seems that I have CWM and recovery installed on my Nexus 4. I was on TWRP previously and switched to CWM, now it seems that it is stucked.
I erased recovery in command prompt and flash it with CWM after installing stock ROM but ROM Manager still detected TWRP. How do I get rid of TWRP?

Zouk18 said:
Hi,
It seems that I have CWM and recovery installed on my Nexus 4. I was on TWRP previously and switched to CWM, now it seems that it is stucked.
I erased recovery in command prompt and flash it with CWM after installing stock ROM but ROM Manager still detected TWRP. How do I get rid of TWRP?
Click to expand...
Click to collapse
try flashing stock recovery via adb

If you reboot into recovery does CWM come up or TWRP? If it's CWM then ignore ROM Manager and continue as normal

ijustzeke said:
try flashing stock recovery via adb
Click to expand...
Click to collapse
So you are suggesting that I erase and flash to stock recovery via adb and then flash custom recovery again?
EddyOS said:
If you reboot into recovery does CWM come up or TWRP? If it's CWM then ignore ROM Manager and continue as normal
Click to expand...
Click to collapse
CWM comes up as the recovery because it's the latest one I flash. I know it might now matter but this really bugs me.

Dunno why you're using ROM Manager anyway, pointless piece of software IMO. Just flash everything manually

Mine was gone when i unrooting the device
Sent from my Nexus 4

EddyOS said:
Dunno why you're using ROM Manager anyway, pointless piece of software IMO. Just flash everything manually
Click to expand...
Click to collapse
I was just checking out the app, don't really use it. That was when I saw two recoveries. I erased and flashed everything via adb previously. Just really wanna know the cause and how to get rid of it.
curtzxion said:
Mine was gone when i unrooting the device
Sent from my Nexus 4
Click to expand...
Click to collapse
Is there a way just to unroot but keep my ROM, kernel and data intact?

Zouk18 said:
I was just checking out the app, don't really use it. That was when I saw two recoveries. I erased and flashed everything via adb previously. Just really wanna know the cause and how to get rid of it.
Is there a way just to unroot but keep my ROM, kernel and data intact?
Click to expand...
Click to collapse
My rom, kernel, and data doesn't change, when i was unrooting the device(as i remember)
Sent from my Nexus 4

That's normal. I have it too. Just choose cwm on recovery already installed and leave it like that.
Sent from my Nexus 4 using xda premium