Database Users

CWM not working

I have been having issues with CWM on my Fascinate for about 2 weeks now. Whenever I try to flash anything via CWM I get this message:
Samsung Recovery Utils
- for BML -
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
The "reboot system now" is highlighted and I cannot do anything to select apply update.zip
On the bottom part of the screen it says:
Install from package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Now I have flashed back to D101 and did the ota update to DL09, and flashed the CWM via odin posted on a thread from the android central forum, it is basically a version of CWM for DL05 and DL09. (can't post outside links so I havent posted enough in this forum).
I have tried to apply the update.zip but whenever I do that, after about 25% of the way through it goes back to the error.
I have completely run out of ideas and the people at the android central forums have as well. I have tried everything that I can think of but obviously I am not doing something right.
Can anyone give me some suggestions as to what I can do to try to resolve this issue? Or if there is a way to flash a rom and kernel without CWM. I really do not want to be stuck with stock Fascinate so anything would be appreciated.
Thank you

You have to go into CWM immediately after flashing in Odin, before booting up, and flash a new kernel. DL09 breaks CWM on the stock kernel
Sent from my SCH-I500 using XDA App

I had that same issue until a user on another forum informed me that right after flashing cwm, replace battery and go immediately into recovery mode, do not let the phone boot normally.
Now I am able to add kernels and roms to my hearts content.

I'm in a similar situation except my error comes while trying to back up my ROM.
I did root via pushing rage.bin via ADB
Then I used ODIN to put CWMrecovery.tar on the phone.
Flashed CWM via ROM Manager.
At this point I did a full backup with TiBu and did a ROM Backup via ROM Manager.
After that I froze bloatware, 'upgraded' to the Sywpe Beta and De-binged.
At about this point I realized that I had lost Haptic so I flashed the DL09 stock Kernel and that problem was solved. I thought I was good to go until I tried to do another backup via ROM Manager.
When I ran the backup I got the same error as the OP. I ended up in 2e recovery. Since I'm new to this I just chose reboot phone. I did some searching last night but all the posts I found dealt with people flashing custom ROMs and I was getting tired I called it a night with the plans to do more searching today but then I came across this post.
I reviewed my notes and saw the other thread about CWM Recover mode and I checked and I can't reboot into CWM Recovery (via ROM Man) either. I end up in Android (2e) recovery.
I saw the post above me and I need to search on these instructions so I understand this step better.
"I had that same issue until a user on another forum informed me that right after flashing cwm, replace battery and go immediately into recovery mode, do not let the phone boot normally."
I don't seem to be able to boot (up and down key = Power buttong) into any recovery.
It seems like I need to repush CWM via Odin and then reflash via Rom Man but I'm leaving for a trip tomorrow so I'll wait for some input before trying anything since the phone is functionally working.
I'm new to rooting phones so some help with this error would be appreciated.

ezas said:
I'm in a similar situation except my error comes while trying to back up my ROM.
My phone is updated OTA DL09. Then rooted via ADB. I installed ROM Manager and flashed CWM. Since then I've done the usual root stuff. I noticed that haptic was not working and I fixed that by flashing a stock DL09 kernel. I have not flashed a custom ROM.
After de binging yesterday I went todo a back up via ROM Manager and got the same error as the OP. I ended up in 2e recovery. I didn't want to really screw up my phone guessing so I just chose reboot phone.
I was going to do more searching tonight but came across this post first.
I have done two successful back ups via ROM Manager, so after reading this post I assume it's flashing the kernel that got me to this error.
I'm new to rooting phones so some help with this error would be appreciated.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I don't use custom roms on my phone but from what I'm gathering on this...
You will need to put it back to DL09 stock...
Flash CWM via Odin..
http://forum.androidcentral.com/ver...s-hacks/54659-how-rooting-your-fascinate.html
Post 4 here will tell you how to do it.
After flashing CWM you will need to put your phone into recovery right away instead of letting the normal rom load. You will then flash over another kernel using CWM and that is it.
List of kernels can be found here:
http://www.samsungfascinateforum.com/custom-roms/list-of-custom-dj05-kernels-for-verizon-fascinate/
I have never put a new kernel or rom on my phone but from what i've read this is the jist of it.

You shouldn't have to flash back to stock...
1. Download all necessary files and place on root of your SD card (nonstock kernel, update.zip)
Edit: also add in the superuser and busybox zips, and flash those after kernel (step 5) and this will give you root back if you lost it updating
2. Flash modified CWM .tar with Odin
3. Replace battery and boot directly into recovery by holding both volume buttons down while powering on
4. Once in recovery, apply update.zip to get into CWM
5. Flash new kernel
6. Reboot, enjoy

Kevin and Rob
I followed the instructions to the letter over at AndroidCentral (including flashing busybox_su) and I'm back up and running with Haptic feedback and I'm watching a ROM backup via ROM Manager as I type this. I have not done a lot of testing yet but everything seems to be working fine.
Thanks for all the help.

Kevin Gossett said:
You have to go into CWM immediately after flashing in Odin, before booting up, and flash a new kernel. DL09 breaks CWM on the stock kernel
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Just did that and after I select Install zip from SD car, the screen goes black. When I press the home button it goes back to the green list but when I select anything from there, the screen goes black again.
I have tried flashing back to stock, updating to DL09 and flashing cwm again, but same issue.

OK I am getting really tired of dealing with this. Nothing I try works. I am just going to give up on the idea of installing roms and kernels on my fascinate. I have no idea what the problem is and nobody knows either.
Thanks for all those that helped.

When in CWM the home button turns the screen off. Use the back button or power button to select

Kevin Gossett said:
When in CWM the home button turns the screen off. Use the back button or power button to select
Click to expand...
Click to collapse
Shh, I had no idea about that. I assumed since in order to get to cement recovery you had to press home key that that is what you use while in recovery. Everything works now, thank you.

ok, I'm ready to sell this damn Fascinate on Craigslist for a peanut butter sandwich. I'm miffed with getting CWM working. I have pushed the updated version onto the phone via ODIN, immediately booted into recovery (got the red recovery), and it won't mount my SD card. I had a similar problem in green recovery - it could see my SD card, but wouldn't show me all the files - including the download folder. So I couldn't flash anything. I've tried this 100 different ways. There's nothing wrong with the SD card. It reads fine in the phone, files working other than CWM. Please help. I'm stuck on stock. Have mercy.

gadgetmom88 said:
ok, I'm ready to sell this damn Fascinate on Craigslist for a peanut butter sandwich. I'm miffed with getting CWM working. I have pushed the updated version onto the phone via ODIN, immediately booted into recovery (got the red recovery), and it won't mount my SD card. I had a similar problem in green recovery - it could see my SD card, but wouldn't show me all the files - including the download folder. So I couldn't flash anything. I've tried this 100 different ways. There's nothing wrong with the SD card. It reads fine in the phone, files working other than CWM. Please help. I'm stuck on stock. Have mercy.
Click to expand...
Click to collapse
Download updated CWM at this post: http://forum.xda-developers.com/showthread.php?t=942021
Fixed my CWM problems.

That is the file I used. Relief
Tried both through Odin and loading onto phone. No dice.

That is the file I used. Relief
Tried both through Odin and loading onto phone. No dice.

the home key always turns the screen off, u have to hit search button to turn on and go back

OK, just to make sure I'm not crazy, I tried again. First I downloaded the SuperClean 2.2 update to my SD card. I re-downloaded the updated update.zip file and put it at the root of my SD card. I flashed DL09.tar.md5 via Odin to get back to stock. That completed with no problem. I flashed the EB01 radio, no problem. Flashed the updated CWM. Immediately booted into recovery (red). Attempted to Apply update.zip. Errored out. Attempted to apply update from SD card. Here's the error I'm getting:
-- Install from SDcard...
Finding update package...
E:Can't mount/dev/block/mmcblk1p1 (or dev/block/mmcblk0)
(Invalid Argument)
E: Can't mount SDCard:Update.zip
Installation aborted

gadgetmom88 said:
OK, just to make sure I'm not crazy, I tried again. First I downloaded the SuperClean 2.2 update to my SD card. I re-downloaded the updated update.zip file and put it at the root of my SD card. I flashed DL09.tar.md5 via Odin to get back to stock. That completed with no problem. I flashed the EB01 radio, no problem. Flashed the updated CWM. Immediately booted into recovery (red). Attempted to Apply update.zip. Errored out. Attempted to apply update from SD card. Here's the error I'm getting:
-- Install from SDcard...
Finding update package...
E:Can't mount/dev/block/mmcblk1p1 (or dev/block/mmcblk0)
(Invalid Argument)
E: Can't mount SDCard:Update.zip
Installation aborted
Click to expand...
Click to collapse
I think I see what your issue is. The red CWM that you loaded via ODIN installs onto the phone itself. You no longer need an update.zip file containing CWM on your sdcard. As long as you have successfully booted into red CWM, your next step is to do a full wipe, and then choose the "install zip from sdcard" option. You should then be able browse your sdcard and select the zip file containing the rom.
DO NOT rename the zip file containing the rom to update.zip and then select the "apply update.zip" option, as that will definitely not work. That option expects to find the CWM recovery app in the update.zip file, and errors out if it's anything else.
Posted from my EB01 SuperClean Fascinate with Voodoo

Oh, and make sure you have the most recent new CWM file from jt1134. The post from him that had the first fixed CWM I think may have required an update.zip file, but the current, updated files in it do not. If you're not sure, download the latest one from that post for Odin, and flash it from Odin again. You will them no longer need update.zip for sure.
Posted from my EB01 SuperClean Fascinate with Voodoo

Roblovesbox said:
I don't use custom roms on my phone but from what I'm gathering on this...
You will need to put it back to DL09 stock...
Flash CWM via Odin..
http://forum.androidcentral.com/ver...s-hacks/54659-how-rooting-your-fascinate.html
Post 4 here will tell you how to do it.
After flashing CWM you will need to put your phone into recovery right away instead of letting the normal rom load. You will then flash over another kernel using CWM and that is it.
List of kernels can be found here:
http://www.samsungfascinateforum.com/custom-roms/list-of-custom-dj05-kernels-for-verizon-fascinate/
I have never put a new kernel or rom on my phone but from what i've read this is the jist of it.
Click to expand...
Click to collapse
Awesome, thanks for the links.

Having problems flashing anything to my phone

I am running DL09, everything is stock. I rooted my phone, and flashed cwm via odin. Then I installed cwm from the market and from cwm flashed recovery. Via cwm i tried to flash an updated version of cwm, but it didn't work, then I tried to flash the leaked dl30 - it also didn't work. everytime i try to flash anything, i get the following error message:
E: Failed to verify whole-file signature
E: signature verification failed installation aborted.
the top of the screen (when i boot into recovery from the rom manager) says
Android system recovery (2e)
Samsung recovery Utlis
- for BML -
also, when I try to select anything, it only recognized the home soft key as enter.
my only options are
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
what has gone wrong?

I have the same problem. Adrynalyn said something about dl09 being sneaky and killing the cwm loader, so the first boot after running odin we are supposed to flash a clean kernel... I haven't tried it yet, been busy, but I will this weekend before flashing froyo.
Sent from my SCH-I500 using XDA App

I had the same blue text screen with those for options this morning when looking to wipe batt stats. I went ahead and selected the sdcard option, and next thing I know I'm looking at the gen text again with the complete list of options. Maybe try that?
Mmmmm...Froyo!

Problem on running ClockworkMod for Battery fix

Everytime I try to run the reinstall packge it says error signature failed.
I rooted my vibrant froyo 2.2 with superonelick
Then I downloaded ROM and donwloaded the clockwork got into recovery and the update.zip always fail.
Anything I did wrong?

when in recovery you need to update.zip twice

gun said:
when in recovery you need to update.zip twice
Click to expand...
Click to collapse
I did more than twice.

I installed a DISABLE E: SIGNATURE VERIFICATION ON SAMSUNG VIBRANT it says replacing stock recovery thens reboots and goes to the default did twice.

Edgar J. said:
I installed a DISABLE E: SIGNATURE VERIFICATION ON SAMSUNG VIBRANT it says replacing stock recovery thens reboots and goes to the default did twice.
Click to expand...
Click to collapse
try to delete update.zip from SD card and install Clockwork again using ROM manager
or
Odin back to stock
root with Superoneclick
reboot (always do this after rooting otherwise the root will not work)
install ROM manager
install Clockwork using ROM manager
reboot to recovery
update.zip twice
from here you can install any Froyo ROM and any fixes.

[Q] Please help me, error while flashing

Hi guys, I hope you can help me.
I have just rooted + flashed my motorola defy plus for the first time (on any device for that matter)
I installed 2nd init, version 0.6.... or something.
Put a rom, kernel and google apps on my sd-card
Then I turned usb-debugging off and rebooted my phone.
Now I can get into bootmenu, and this is what I do:
1) go to recovery
2) select custom recovery
3) then it says: Clockworkmod Recovery v2.5.1.8
E: Can't open /tmp/recovery.log
4) I then select wipe data/factory reset
5) then it says this: Formatting DATA
Formatting CACHE
FORMATTING SDEXT
No app2sd partition found. Skipping format of /sd-ext
Formatting SDCARD:/.android_secure
Data wipe complete
E: Can't open /tmp/recovery.log
6) After that i select install zip from sdcard
7) then I select choose zip from sdcard
8) then I select the zip file containing the rom
9) And it says: Finding update package
Opening update package
Installing update
E: Can't make /tmp/update_binary
Installation aborted
Now I can't go any further and can't use my phone at all
I hope u guys can help me, and that I haven't F*ed up my phone

I have a quite similar problem.
On a defy+,rooted 2ndinit installed, backup-ed first, download the new quarx05/03 ICS, put the zip on sd, wipe data, reboot and start to install ics, but the message was
''Finding update package
Installing update
E: Can't make /tmp/update_binary
Installation aborted"
Thanks to the previously backup I can use may phone as usual.
What I have done wrong with de ICS installation?
Thanks
PS. Sorry for probable a dummie question:What we have to do with md5 zip near the CM9 Jordan.zip?

A little help please about the subject?
Thank you

ics
The entire process
ClockworkMode v2.5.1.8
Wipping data...
Formatting DATA...
Formatting CACHE...
Formatting SDEXT..
No app2sd partition found.Skipping format of /sd-ext.
Formatting SDCARD: /.android_secure...
Data wipe complete
E: Can't open /tmp/recovery.log...
Installing: SDCard:download/CM9-ICS-MR1-120305-jordan.zip
Finding update package
Opening update package
Installing update
E: Can't make /tmp/update_binary
Installation aborted
if try Wipe Dalvik Cache:
E: Can't mount /dev/block/mmcblk0p2
(No such file or directory)
I guess that this is a simple and many times occured error, since nobody has any answer....

Does you disabled the usb debugging before flashing?

Yes I do, but nothing change,
Thanks

if I'm not mistaken the last release of 2nd init is not compatible with defy. Try to check this on the development forum. I hope I have been of help.

I'd tried with both 1.0.7 latest and 0.6.1.
With latest, the phone is blocked.
Thanks

I had used this. Try with it
P.S. sorry for my bad english.

Tried, the same errors,
Thanks

I don't know. Sorry. By the time i had used that.

I think you need to go to stable recovery after you wipe your data from custom recovery
Sent from my MB525 using xda premium

I think you need to go to stable recovery after you wipe your data from custom recovery
What do you mean by "stable recovery"? You talk about version 0.6. of 2nd init or something else?
Can you show a step-by step procedure?
Thank you in advance.
However, which is the procedure to un-root a defy+ and to have it with the original, fresh system?

I had flash a new SBF, root with Unlockroot v2.3, anything else doesn't work, 2ndinit v2.0 stable, wipe data/cache/dalvik (same errors), try to install cm9-ics, the same error "Can't make /tmp/update_binary"
What the f.....?

cretu22 said:
I had flash a new SBF, root with Unlockroot v2.3, anything else doesn't work, 2ndinit v2.0 stable, wipe data/cache/dalvik (same errors), try to install cm9-ics, the same error "Can't make /tmp/update_binary"
What the f.....?
Click to expand...
Click to collapse
Hi, I have exactly the same problem.. Trying to find a solution but is quite difficult. First I thought it has something to do with the partitioning, as stated in THIS topic. But, in THIS topic, people say that partitioning the SD card is not necessary at all..

@Cretu22: Yes stable recovery is CWM 0.6
Don't install stable recovery! I too faced this issue when I flashed using stable recovery. In snd init install Latest recovery and then try flashing your ROM. That should work..

I did choose the stable version indeed 0.6.7.
Now i did uninstall it and installed the latest 1.0.7, but when I reboot my phone it won't get into the boot menu but just boots into android. Tried it several times, but only with 0.6.7 I seem to be able to get in the menu

fokkeh said:
I did choose the stable version indeed 0.6.7.
Now i did uninstall it and installed the latest 1.0.7, but when I reboot my phone it won't get into the boot menu but just boots into android. Tried it several times, but only with 0.6.7 I seem to be able to get in the menu
Click to expand...
Click to collapse
Okay!! I hope you were pressing the volume down button when the blue LED came?? Try doing this again all over.. I mean reinstall 2nd init and then latest recovery.. I remember doing this once(instal latest recovery after I installed stable recovery)..

pranks1989 said:
Okay!! I hope you were pressing the volume down button when the blue LED came?? Try doing this again all over.. I mean reinstall 2nd init and then latest recovery.. I remember doing this once(instal latest recovery after I installed stable recovery)..
Click to expand...
Click to collapse
Yes, its working Pressing the volume down button was not necessary with 0.6.7, that was what went wrong. Now the zips installed like a charm

i know the answer and is very simple
the problem is that you cannot create that specific folder.... because it already exist, cmp (connected music player) creates it, just delete it from SD and done!

[RESOLVED] How do I restore factory Rom (from Revolution HD 3.0.1 on TF101)?

I am running the Revolution HD rom, this is how I purchased my TF101 from a friend, and I want to restore the factory rom so I can get ICS and the update for the battery issue until mike gets it implemented into Revolution.
How can I do this?
Thanks!

-edit- nevermind, I didn't notice you were running revolution.

If you want to flash back to stock, go to the ASUS Support site and download the 9.2.1.11 firmware for your device.
Unzip it 1 time (there is a zip file within the zip) so it will still have a zip.
Put the file on a microSD or the internal /sdcard/ directory depending on your version of CWM and where it can read.
Boot to CWM.
Install zip.
Choose the zip you downloaded.
Now you will be back to stock unrooted with stock recovery.
Then you will need to check for updates and grab the latest update from ASUS OTA.
If you want to root again you will need to vipermod option 1 to get root access.

Ah, thank you Fred! I did exactly that and it failed but it was the zip within a zip that killed me!

The update is actually failing with the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
Any ideas?

gbatt said:
The update is actually failing with the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
Here's exactly what I did to go from Revolution HD 3.0.1 back to stock Asus ICS 9.2.1.11
1. Download the firmware from Asus website. The file name was US_epaduser9_2_1_11UpdateLauncher.zip. You unzip this. You get US_epad-user-9.2.1.11.zip. You put US_epad-user-9.2.1.11.zip on your microSD card.
2. Boot into CWM
3. Factory reset
4. Clear Cache
5. Clear dalvik cache
6. Mount & Storage - format /system
7. Mount & Storage - format /cache
8. Power off(from CWM menu, might be under advanced, I forgot)
9. Boot into CWM.
10. Install zip from sdcard. Choose US_epad-user-9.2.1.11.zip on your microSD.
11. Reboot after flashing is complete.
12. You should now be on Asus stock ICS with stock recovery.
13. I didn't add any of my google accounts during the initial setup because I wanted to do it after I do the 9.2.1.17 update.
14. Shut off and do a cold boot.
Worked perfectly fine for me.
What didn't work was, I was not getting the 9.2.1.17 update afterwards.
So I rooted using Vipermod, installed CWM, and manually flashed the update through CWM. I had to re-root after the update. Simply ran Vipermod again.
Been 2+ days, and it's super stable with great battery life. Not a single random reboot or crash.

gbatt said:
The update is actually failing with the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
You probably have a custom recovery that doesn't mount the staging partition. You can mount it manually through adb in recovery "mount /dev/block/mccblk0p4 /staging" or flash a repackaged stock rom. At this point, you will probably have a stock system, but not the boot.img, bootloader, or recovery. The blob will flash the those parts, including the recovery, so you will be unrooted with a stock recovery.
sent from my cyanogen(mod) vision

gee one said:
You probably have a custom recovery that doesn't mount the staging partition. You can mount it manually through adb in recovery "mount /dev/block/mccblk0p4 /staging" or flash a repackaged stock rom. At this point, you will probably have a stock system, but not the boot.img, bootloader, or recovery. The blob will flash the those parts, including the recovery, so you will be unrooted with a stock recovery.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Ya, its ClockworkMod Recovery v3.1.0.1.
I tried Horndroids steps above and its still the same error.
I'm sorry but how do I "mount manually through adb"?
Ive only ever used clockworkMod

gbatt said:
Ya, its ClockworkMod Recovery v3.1.0.1.
I tried Horndroids steps above and its still the same error.
I'm sorry but how do I "mount manually through adb"?
Ive only ever used clockworkMod
Click to expand...
Click to collapse
I am pretty sure my CWM Recovery was 3.1.0.1 too.
Try replacing your CWM with Rogue XM Recovery http://forum.xda-developers.com/showthread.php?t=1446019

Awesome! That worked great. Thanks Horndroid!