"Rom Manager"
I successfully downloaded the current recovery: ClockworkMod 2.5.1.2
I'm trying to backup my current rom then this happens
Android System Recovery <3e>
E:failed to verify from whole-file signature
i tried removing OCLF, unfortunately it didn't work... i didn't get problem before with 2.1 thought!!! not sure also if i need to delete my update.zip? honestly i'm not sure if rom manager is the one creating this?
thanks in advance
samsung i9000
fimware: 2.2 DXJPA
Looks like its only me having this problem.
Recovery 3e will not work for flashing unsigned update.zip's. You have to change it to 2e recovery. follow this thread
http://forum.xda-developers.com/showthread.php?t=788108
Hope this helps.
I am trying to flash ARHD now, but halfway through it "stuck" in recovery and says: /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. please open ROM Manager to report the issue.
What happen here? =/
Recently I got a problem flashing 2.5.1.3(disappeared in ROM Manager, I do not know why) and 2.5.1.4 (it is in ROM Manager, but it says error in flashing). Only can flash those 3xxxx that is available.
Then I came about to flash 2.5.1.3 using the tool from this http://forum.xda-developers.com/showthread.php?t=1003723 by replacing the 3.0.2.8 to 2.5.1.3.
Flashed 2.5.1.3 successfully. But in ROM Manager it still says current version I am still using is 3.0.0.6. But when I boot into recover, 2.5.1.3 has actually installed.
Any idea about the error?
This is a common issue when you manually change recoveries.
Go into Menu and press the "Manual Flash Override" button. Doesn't always show the exact version but is better than what you have. Mostly.
Hi Mr_JMM
Erm.. where is that menu from? ROM Manager? I did not see them there. =/
Press "menu" when in ROM Manager.
"menu" being the second touch sensitive button along the bottom.
Or do you mean that the "manual Flash Override" option is missing from the menu?
LOL. Yeap. The "Manual Flash Override" option. I do not see that option in ROM Manager.
Hi, I have a S-Off'd Wildfire (done with XTC-Clip) in version 2.2.1 and I asked a user from this forum how could I root. He answered me with this message:
Code:
hi poinu glad you managed S-off now you can put on any rom you want.
first you must get a custom recovery on your machine I use ClockworkMod 3.0.0.6
this should be fine to flash cyanogenmod7.
here is the file to it (http ://www . mediafire . com /?i09yp4r7odhlzws)
put this PC49IMG.zip on the root of your sd card. (not in a folder)
put the cyanogenmod update zip also on your sd card.
Reboot your phone into Hboot Mode by pressing Volume Down and Power.
It will now ask if you want to update the firmware select Volume Up for Yes.
wenn its done remove thePC49IMG.zip from your sd card.
Reboot your phone into Hboot Mode again.
it will look for the PC49IMG.zip again let that finish and ignore.
Then go with volume down to recovery and push power button, clockwordmod will start.
Do a wipe cache partition, wipe data/factory reset and under advanced wipe Dalvik cache.
go to install zip from sdcard / choose zip from sd card and choose your cyanogen mod update zip and install.
reboot wen finished don't worry if it takes some time first reboot always is slower.
hope i helped you enjoy your mod.
kind regards ab65
I've downloaded the PC49IMG.zip file and copied at the root next to the cm7.zip file (picture: http : //i55 . tinypic . com/ egai5s. png) but when I enter the HBOOT and looks for the PC49IMG.zip file, it finds nothing (and yes, the file is PC49IMG.zip not PC49IMG.zip.zip, I've already checked this )
I don`t know what I have done wrong (I have done nearly anything!) any ideas?
Thank you very much for having a look on the threat
here is what i suggest simply,
***** Ur memory card must be formatted with fat32 partition before doing this.......
go to this link and download the attached file at the bottom PC49IMG.ZIP
http://forum.xda-developers.com/showpost.php?p=12188132&postcount=15
Since security flag is turned of (by xtc clip) , the recovery partition is no longer protected. U can install custom recovery without any exploits. That downloaded PC49IMG.ZIP file is nothing but "ClockworkMod Custom Recovery". Put it in the root of the memory card (fat32). Then go to hboot menu. It definately finds the file and prompts u to install. Go with it. At the end u will have custom recovery.
then u can install custom roms. Custom roms will be packed in zip files and can be installed from recovery menu. Its not needed to put the custom rom zip file only in the root of memory card. And the most important thing is, remember to clear data/factory reset and clear cache (both done frm recovery menu) before installing a custom rom. Thats all
Oh god, i didn`t know that.... succesfully done
but now... there's another problem, I installed the CyanogenMod7 and there are some things that I pretty dislike and I would like to install another ROM I have (it's a 2.2.1 rooted ROM) and I tried to do what I did to install the CM7 but when I installed it from the recovery this error message appeared:
"Installing update...
Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5. It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Installation aborted."
Is it really possible to root this ROM or do I have to stay in the CM7? :S
Any suggestion? Thank you very much for the support
poinu said:
Oh god, i didn`t know that.... succesfully done
but now... there's another problem, I installed the CyanogenMod7 and there are some things that I pretty dislike and I would like to install another ROM I have (it's a 2.2.1 rooted ROM) and I tried to do what I did to install the CM7 but when I installed it from the recovery this error message appeared:
"Installing update...
Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5. It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Installation aborted."
Is it really possible to root this ROM or do I have to stay in the CM7? :S
Any suggestion? Thank you very much for the support
Click to expand...
Click to collapse
CLockworkmod 3 is a must for the gingerbread CM7 roms.
And clockworkmod3 recovery will not support "amend - scripting"
What u need to do is, to install the CM7 custom rom. Then install "Rom Manager" from market. Then use a different version of clockworkmod (downgrade to 2.5 version or try different versions). Then reboot to recovery from Rom manager itself. Then try to install the 2.2.1 rooted rom. It should work. If u have any issues with installing custom roms, then try different version of clockworkmod recovery (from Rom Manager). That's all.
explanation: http://forum.xda-developers.com/showthread.php?t=897026
it surely worked, thank you very much
I done the Alpharev s-off method but now when I try to install CM7 from CWM 3.0.0.6 it get stuck on "Installing update"
Any ideas?
diarmaid said:
I done the Alpharev s-off method but now when I try to install CM7 from CWM 3.0.0.6 it get stuck on "Installing update"
Any ideas?
Click to expand...
Click to collapse
what recovery do you use? did you dowloaded the zip correctly?
I upgraded to cwm4 and it worked perfectly.
That was a close one, it was a birthday present for the missus and i finally got it working on the morning of the birthday
Sent from my HTC Desire S using XDA App
ATTENTION: Custom Android 3.2 ROM available! Both 3G and Wi-Fi users can enjoy Team Tiamat Xoom Rom 2.0.1 Manta Ray. If you want the latest features implemented by Team Tiamat, install Manta Ray; otherwise, if you want stock 3.2 with root, continue below.
IMPORTANT NOTE: This update is for the US Xoom Wi-Fi MZ604 with Android 3.1 ONLY!!! As of v05 of this update, the update script performs NO CHECKS of files before flashing rooted stock 3.2 system and boot images. This means it won't stop you from flashing on a Xoom 3G; it will just flash and you're left with the mess, if any. Please proceed only if you're tech-savvy with Android and the Xoom, ready to restore to stock 3.1 in case of issues, and good at troubleshooting. Please provide feedback and corrections, and I'll update the post as quickly as I can. Thanks!
WARNING: Following this procedure may damage or permamently destroy your device. This procedure is provided with NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Perform this procedure at your own risk.
COMPATIBILITY NOTE: I have personally tested this procedure ONLY ON THE US XOOM WI-FI MZ604 with Android 3.1 HMJ37. If you have a non-US Xoom Wi-Fi, this procedure may break your device. If you have a Xoom 3G, this procedure may break your device. If you're running a version of Android prior to 3.1, this procedure may break your device (update to 3.1 first).
[size=+1]SUMMARY[/size]
Here's a run-down on the current procedure:
Updates the Xoom Wi-Fi from 3.1 HMJ37 to 3.2 HTJ85B using ClockworkMod Recovery (update.zip)
Flashes system partition with rooted stock 3.2 image (minus the recovery overwrite script)
Includes Superuser.apk and su binary to enable functioning root (thanks, chainsdd)
Flashes the boot (kernel) partition with rooted stock 3.2 kernel (thanks, solarnz)
Stock kernel means no extras (overclocking, etc.) from custom kernels
Leaves existing recovery partition intact (stock 3.2 update overwrites it on every reboot)
Leaves user data intact
Includes Android 3.2 support for hardware SDCard (shows in Settings|Storage, /mnt/external1)
Outstanding Issues:
Too many steps: Include the edited updater-script, su, Superuser.apk in a custom update.zip
Requires stock 3.1 Boot partition (kernel): Need to include solarnz's stock rooted 3.2 boot.img and just flash that over whatever is there
Requires stock 3.1 HMJ37 System partition (ROM): Might include a stock 3.2 system.img and remove the checks for stock 3.1 system files, but it will make the .zip huge
Users with custom ROM's report issues after update: users suggest factory reset/full wipe (including user data) in ClockworkMod Recovery prior to updating (read through the thread for more info)
Superuser update available in market, but update fails: my bad for not including the latest and putting the apk in /system/app makes upgrading less easy. Delete superuser.apk using adb, terminal, or rootish file manager app, and the upgrade should work (thanks, GeekyGuy)
Now, without further ado...
[size=+1]ASSUMPTIONS[/size]
You are currently running Android 3.1 (stock 3.1 images here, thanks, bwcorvus)
You've downloaded the modded Xoom Wi-Fi Android 3.2 update v05 (thanks to kurt5510 for the original OTA, thanks to solarnz for the rooted stock boot.img)
You've flashed ClockworkMod Recovery (thanks, solarnz, bigrushdog, koush, et al)
You've installed a physical SDCard in your Xoom (required for ClockworkMod Recovery updates) and have it functioning properly
[size=+1]PROCEDURE[/size]
Rename the modded Android 3.2 Update file to update.zip
Reboot into recovery
Reboot your Xoom
When the Motorola logo splash screen appears, press the Volume Down button to scroll through boot options and select "--> Android Recovery"
Press the Volume Up button to enter Android recovery
Perform update
Note that in recovery, you use the hardware volume buttons to navigate up and down, and the power button to select. Note also if you are coming over from a custom ROM, users suggest doing a factory reset/full wipe (including user data) ClockworkMod Recovery prior to performing the following steps (read the thread for more info).
In ClockworkMod Recovery, select "mounts and storage"
Ensure your Xoom is connected to your PC via USB, then select "mount USB storage"
On your PC, copy update.zip to the root of the Xoom's SDCard ("Removable Disk" in Windows)
In ClockworkModRecovery (still on the "USB Mass Storage device" screen) select "Unmount"
In the "Mounts and Storage Menu" screen, if the option "unmount /sdcard" is present, continue to the next step; if "mount /sdcard" is present, select it then continue
Select "+++++Go Back+++++"
Select "apply update from sdcard"
Select "Yes - Install /sdcard/update.zip"
"Install from sdcard complete." will indicate that the update is completed.
.
Select "reboot system now"
Enjoy your rooted Xoom Wi-Fi, running on Android 3.2!
[size=+1]POST-UPDATE NOTES[/size]
Custom kernels: [KERNEL][AOSP]Tiamat Xoom 2.0.0 "Katana" [Update: 07/14]
[size=+1]CHANGELOG[/size]
v05: Removed system file checks and patches; instead flashes 3.2 system image with Superuser.apk and su binary preinstalled and recovery overwrite removed.
v04: Included Superuser.apk and su binary; no need to have them prior to updating. Still requires stock 3.1 HMJ37 system/ROM.
v03: First release of modded update.zip, removes check for stock 3.1 boot partition, flashes solarnz rooted stock 3.2 boot.img
v02: Added su symlink to updater-script
v01: First release, modded updater-script for manual mod to update.zip file
Excellent work! Guide stuck for the time being.
Nice. Had just finished "downgrading" to stock 3.1 and was about to try my luck with the original update file. Then i saw this. Installs fine, but i do not seem to have root nor will superuser from market update su. (i did replace the file in the .zip and installed via cwm).
But damn 3.2 seems fast at first glance, but might just be me
If you have your Xoom powered down before you start, can you drag and drop the update.zip file to the SD card on your PC rather than doing the mount-and-copy? (If this seems like a stupid question, I only just rooted last weekend and don't want to take anything for granted!)
LynnL said:
If you have your Xoom powered down before you start, can you drag and drop the update.zip file to the SD card on your PC rather than doing the mount-and-copy?
Click to expand...
Click to collapse
As long as the file is there, you're good to go.
Can't seem to make it work. I have tried several different times.
My output is always:
"Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.1/HMJ37/124251:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.2/HTJ85B/140714:user/release-keys"
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted."
are you on stock 3.1? afaik this only works on stock roms. thats the same error i get, and im running tiamat 1.1
By the way, i have a UK Xoom but i went to 3.1 via stock US FW.
eliteone said:
are you on stock 3.1? afaik this only works on stock roms. thats the same error i get, and im running tiamat 1.1
Click to expand...
Click to collapse
I'm running stock with a custom kernel and getting the same error.
you need to be running stock kernel i believe
eliteone said:
you need to be running stock kernel i believe
Click to expand...
Click to collapse
At this time, yes. solarnz made a rooted stock boot.img which i'm working on including in an update.zip.
xMemphisx said:
Can't seem to make it work. I have tried several different times.
My output is always:
"Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.1/HMJ37/124251:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.2/HTJ85B/140714:user/release-keys"
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted."
Click to expand...
Click to collapse
Xoom 3G users will likely get this error.
Xoom Wi-Fi users on any ROM other than stock 3.1 HMJ37 will likely get this error.
You need to be Wi-Fi on stock 3.1 HMJ37 at this point.
I'm getting some corby apk error when trying to run the update. Using stock 3.1 but rooted.
Xoom wi-fi US version.
Oh never mind. I missed that i needed to be rooted on stock 3.1... I will await solarnz boot.img or start over tomorrow if i get too impatient
will this method wipe any of my data ?
Were do i find the stock 3.1 Kernel?
getting same problem as above
"Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.1/HMJ37/124251:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.2/HTJ85B/140714:user/release-keys"
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted."
i'm on stock 3.1 wifi us rooted
Sk8er Boi said:
will this method wipe any of my data ?
Click to expand...
Click to collapse
It currently flashes over your boot partition and updates your system partition. User data is not affected.
jzun223 said:
Were do i find the stock 3.1 Kernel?
Click to expand...
Click to collapse
[IMAGES] HMJ37 (USA WiFi 3.1)
Sk8er Boi said:
getting same problem as above
"Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.1/HMJ37/124251:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.2/HTJ85B/140714:user/release-keys"
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted."
i'm on stock 3.1 wifi us rooted
Click to expand...
Click to collapse
What does it say on Settings | About tablet? Looking for Android version, Kernel version, and Build number.
EDIT: Also, through a terminal or ADB, look at /system/build.prop
What's the value for ro.build.fingerprint?
stachre said:
It currently flashes over your boot partition and updates your system partition. User data is not affected.
[IMAGES] HMJ37 (USA WiFi 3.1)
What does it say on Settings | About tablet? Looking for Android version, Kernel version, and Build number.
Click to expand...
Click to collapse
this is also happening to me my data is
build# hmj37
kernel 2.6.36.3-gc2bee64 [email protected]#1
version3.1
v03 posted, see OP.
Ok i flashed my S2 to XXKG1 then flashed with CF-Root-SGS2_XX_OXA_KG1-v4.1-CWM4.tar
I then flashed with GT-I9100_ClockworkMod-Recovery_4.0.1.4.tar
I have CWM app and SuperUser App and Rom Manager Premium.
I backed up my ROM fine using CWM app. I downloaded CyanogenMod from Rom Manager. Picked Install from SD. my phone askes me to backup and clear cach, when the phone reboots it just reboots to android with a (/!\ android man) Image. If i press vol key the menu will appear clockworkmod recovery v4.0.1.4 (its orange).
error:
E:failed to verify whole-file signature
E:signature verification failed
Installation aboarted
Thats as far as i can get, if i chose install zip from sd and select the cm_galaxys2_full-64.zip
error:
E:failed to verify whole-file signature
E:signature verification failed
Installation aboarted
What am i doing wrong here? Im rooted, i have CWM, i have the ROM, ????
Now i'm not a SGS2 user, but IMHO you should:
a) try to download the ROM file again, maybe something went wrong and the file you have downloaded is incomplete or damaged;
b) disable signature check from CWM.
Thanks for replying. wers disable sig check in cwm i cant see it lol
elemen7al said:
Ok i flashed my S2 to XXKG1 then flashed with CF-Root-SGS2_XX_OXA_KG1-v4.1-CWM4.tar
I then flashed with GT-I9100_ClockworkMod-Recovery_4.0.1.4.tar
I have CWM app and SuperUser App and Rom Manager Premium.
I backed up my ROM fine using CWM app. I downloaded CyanogenMod from Rom Manager. Picked Install from SD. my phone askes me to backup and clear cach, when the phone reboots it just reboots to android with a (/!\ android man) Image. If i press vol key the menu will appear clockworkmod recovery v4.0.1.4 (its orange).
error:
E:failed to verify whole-file signature
E:signature verification failed
Installation aboarted
Thats as far as i can get, if i chose install zip from sd and select the cm_galaxys2_full-64.zip
error:
E:failed to verify whole-file signature
E:signature verification failed
Installation aboarted
What am i doing wrong here? Im rooted, i have CWM, i have the ROM, ????
Click to expand...
Click to collapse
Do you have premium version of RomManager? I heard doing stuff from recovery can cause problems through there. And CM7 is still in beta debugging mode so i would not install till there is a stable version. Bluetooth does not work on it everything else does but still not as stable as it should be...
Try flashing a different rom you can find quite a few close to cm7 in the thread section of gs2
Tried a different rom got exactly the same,
I bought rom manager yes
Hi, I'm facing the same problem with SGS2 GT I9100 running on XXKG6
I'm new, so can't post links, Please google disabling CWM Signature check.
Supposedly disabling the signature verification on CWM should fix the issue.
I'll need to get home and check if this fixes the problem or not.
please let me know if this works for you!!