Hi,
I flashed CF-Root-XX_OXA_JW4-v4.4-CWM3RFS using ODIN and attempted to install CWM using ROM MANAGER but whenever I boot into recovery all I get is:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
About phone reveals:
Model number: GT-I9000
Firmware: 2.3.6
Baseband: I9000XXJW4
Kernel version: 2.6.35.7-I9000XXJW4-CL1043937 [email protected] #2
Build number: GINGERBREAD.XXJW4
I have read loads of different posts about fixing this but I do not want to screw up the phone. Can someone please help me before I go mad? I believe that I need a '2e' recovery but where exactly do I get it and install it?
I am not a rookie and had absolutely no problems with my HTC Desire or ZTE Blade but this Samsung is something else.
Cheers guys.
-valerebel
Check my posts in this thread
http://forum.xda-developers.com/showthread.php?t=1995831
Donovan662 said:
Check my posts in this thread
http://forum.xda-developers.com/showthread.php?t=1995831
Click to expand...
Click to collapse
Cheers, but I got there in the end.
My problem was that although I'd flashed the right Kernel with CWM 3, I kept trying to install CWM again from ROM Manager (v2.*.*.*) and this is what was causing the issue. I refashed the Kernel and got into Recovery Mode straight away. I have now installed a Cyanogen JB ROM.
Thanks,
-valerebel
valerebel said:
Hi,
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
-valerebel
Click to expand...
Click to collapse
I just got the above on everything I tried, after flashing "CWM".
Turns out I clicked the wrong link and downloaded a file labelled similarly, but was in fact not CWM recovery but a modified stock recovery.
That said, the CF-AUTOROOT package for my I9500 did work on it... I just had to go into recovery again, right away, and then install SuperSU from the market. I had to flash the proper CWM recovery to get all the other fancy ZIPs to work, such as the pretty Philz touch recovery.
Eureka!! Got answer!
Hi Dude,
I got the solution as I just faced it and came over from it.
The thing is simple. You have been trying to install the update.zip or superSU.zip from your default android recovery. thats y its showing error. That means the custom recovery has not been successfully installed on your mobile. so pls try again then it will surely install.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
fastboot flash recovery twrp.img
fastboot reboot
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
The link which i got solution and u should consider it.
http://teamw.in/devices/androidone.html
Hope this helps you dude. let me know if u have any ques.
Thanks all.
Related
I have a Nexus One for AT&T
Android Version 2.2
Baseband Version 32.26.00.24U_U4.04.00.03_2
Kernel Version 2.6.32.9-27227-g3c98b0d [email protected] #1
Build Number FRF91
Several times a day and get a message saying:
Android Update (Part 1 of 2)
Downloaded and verified 380kb
This is the first of a two-part System Update.
[blah blah blah]
Restart & install
When I click on Restart & Install I get a multicolored X
The a ! in a triangle beside a green robot droid
The text is
ClockworkMod Recovery v2.5.1.0
Finding update package ...
Opening update package ...
Verifying update package ...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
I they choose reboot system, and in a few minutes I get the update notice and the whole process starts again.
What do I need to do?
Install a custom rom that doesn't want to update. You can't install an official update with a custom recovery image.
evilkorn said:
Install a custom rom that doesn't want to update. You can't install an official update with a custom recovery image.
Click to expand...
Click to collapse
Thanks for the reply.
Is it possible to get back to stock?
Yes, read the FAQ/Wiki in the pinned post in the Dev section.
Hi guys,
I have a Nexus 7 3G tablet which was running android 4.2.1. I had flashed a custom apk to enable tethering .
Now, to enable flashing, I copied the original framework-res.apk file and replaced the modified one. Then edited the prop file to eliminate the getprop error . This enabled me to start flashing. Flashing happens all the way to the booloader then fails while flashing radio. it gives the following error
Code:
writing radio...
assert failed: batch.update_modem("/radio/SAM_6260_ALL.fls")
Error in JOP40D.zip
(Status 7)
Aborted
any suggestions would be great.
sayantandas said:
Hi guys,
I have a Nexus 7 3G tablet which was running android 4.2.1. I had flashed a custom apk to enable tethering .
Now, to enable flashing, I copied the original framework-res.apk file and replaced the modified one. Then edited the prop file to eliminate the getprop error . This enabled me to start flashing. Flashing happens all the way to the booloader then fails while flashing radio. it gives the following error
Code:
writing radio...
assert failed: batch.update_modem("/radio/SAM_6260_ALL.fls")
Error in JOP40D.zip
(Status 7)
Aborted
any suggestions would be great.
Click to expand...
Click to collapse
Flash stock recovery. Update via sideloading. Profit!
Just in case you are interested in the cause: Current custom recoveries for tilapia are missing the "bach.modem_update" function (not really sure if all of them).
frikisama said:
Flash stock recovery. Update via sideloading. Profit!
Just in case you are interested in the cause: Current custom recoveries for tilapia are missing the "bach.modem_update" function (not really sure if all of them).
Click to expand...
Click to collapse
if i flash stock recovery, i will lose all my data. any other possible solution, which would enable me to keep my data?
sayantandas said:
if i flash stock recovery, i will lose all my data. any other possible solution, which would enable me to keep my data?
Click to expand...
Click to collapse
No, you won't. I said stock RECOVERY, not stock IMAGE.
Code:
fastboot flash recovery stockrecoverysname.img
OK. So could you give me a link to download the recovery image ?
Sent from my Nexus 4 using xda app-developers app
Do you have the original factory image from google? The recovery.img is inside,
if not i will upload it somewhere, though it doesn't fixed the radio update error for me.
I now have a mixed version > the ota update installed without errors, the bootloader is 4.18 but
in settings it complains to still be at 4.2.1 JOP40D
Flashing the stock recovery only leads to an unusable recovery screen with no options for flash/sideload
with an red exclamation mark over the chest of the sweet robot..
any ideas?
maybe i have to reflash my nandroid and try again, the custom recovery was openrecovery-twrp-2.4.1.0-tilapia
here are the images for those who need them
nakasig-jop40d-factory-efcec044.tgz
http://www.share-online.biz/dl/0OWHBFIMLC
recovery.img
http://www.share-online.biz/dl/LM9JBFIMKSG8
EDIT:
Ok finally i was able to use the stock recovery. though it seemed to be dead.
By pressing power+volup showed the recovery menu for me.
Then flashing the update via sideload worked.
cheers phk
i have been downloading CM nightlys to my pc, copying them to my phone's internal storage, then flashing the zip using recovery (twerp v2.6.3.0) successfully for 3 or 4 months. I found CM Downloader app on the app store and down loaded that. I set the setting to automatically check for a new build, and download it. it did download the new builds although they failed to flash. 3 days after this started happening, CM came out with a 'snapshot' version. that one flashed ok. but the 'nighly' builds no longer flash. I have uninstalled CM downloader, and tried downloading them to the PC and copying them to the phone, that no longer works either. I have reinstalled CM downloader no change. so I think there is something changed on the phone that needs to be fixed, or reset or something. I appreciate any ideas here, I am still entry level skill level, so be gentle
blairman
TWERP failed flash message
blairan said:
i have been downloading CM nightlys to my pc, copying them to my phone's internal storage, then flashing the zip using recovery (twerp v2.6.3.0) successfully for 3 or 4 months. I found CM Downloader app on the app store and down loaded that. I set the setting to automatically check for a new build, and download it. it did download the new builds although they failed to flash. 3 days after this started happening, CM came out with a 'snapshot' version. that one flashed ok. but the 'nighly' builds no longer flash. I have uninstalled CM downloader, and tried downloading them to the PC and copying them to the phone, that no longer works either. I have reinstalled CM downloader no change. so I think there is something changed on the phone that needs to be fixed, or reset or something. I appreciate any ideas here, I am still entry level skill level, so be gentle
blairman
Click to expand...
Click to collapse
Updating partition details
Processing OpenRecoveryScript file
unable to locate zip file "/CyanogenRob_Downloa
E:Error installing zip file "/CyanogenRob_Downloa
Don processing script file
Installing ' /sdcar/CyanogenRob_Downloader/cm1
skipping MD5 check: no MD5 file found
E:Error executiong updater binary in ' /sdcar/CyanogenRob_Downloader/cm1
Error flashing zip ' /sdcar/CyanogenRob_Downloader/cm1
updating partition details
then under that in red letters "Failed'
blairan said:
Updating partition details
Processing OpenRecoveryScript file
unable to locate zip file "/CyanogenRob_Downloa
E:Error installing zip file "/CyanogenRob_Downloa
Don processing script file
Installing ' /sdcar/CyanogenRob_Downloader/cm1
skipping MD5 check: no MD5 file found
E:Error executiong updater binary in ' /sdcar/CyanogenRob_Downloader/cm1
Error flashing zip ' /sdcar/CyanogenRob_Downloader/cm1
updating partition details
then under that in red letters "Failed'
Click to expand...
Click to collapse
TWRP that works:
http://forum.xda-developers.com/showpost.php?p=50383573&postcount=3
Why (changelog):
http://forum.xda-developers.com/showpost.php?p=50383578&postcount=4
i'm part way there...
tdhite said:
TWRP that works:
http://forum.xda-developers.com/showpost.php?p=50383573&postcount=3
Why (changelog):
http://forum.xda-developers.com/showpost.php?p=50383578&postcount=4
Click to expand...
Click to collapse
OK, I have downloaded the 2 files. placed them in a directory near my root directory on my pc. placed the phone in fastboot usb, opened a command prompt window from that directory. typed in fastboot flash recovery openrecovery-m7wls-2.7.0.9-05-01-2014
and I get error: cannot load 'fastboot flash recovery openrecovery-m7wls-2.7.0.9-05-01-2014'
per a video showing how to flash recovery, I also tried the command adb reboot bootloader I get error : device not found
back to my pc, I open device manager, and I show a device labeled android device that is working properly.
stumped at this point.
is updating recovery the same as the initial install of a custom recovery?
do I need updated drivers for win 7? where are the latest? all videos say they are the latest, but that was when they were recorted.
thanks for help!
Yes u need updated drivers....any easy solution however is go and get the app flashify u will need root of course...it allows u to flash recovery that is on ur sd card. Just choose the img and flash recovery in the app then reboot into recovery and u will be good to go.
Sent from my HTCONE using Tapatalk
Thank you!
Thanks to both of you, updated TWERP did the trick and Flashify allowed me to install it without the fastboot, and PC hookup which was not working. Latest nightly installed, I am a happy camper!
Ok, let me get this straight, snag this Flashify, then snag TWRP 2.7.1.1, flash it with Flashify and I am golden????
(I am unlocked and S-Off running CM-11)
Slagathor01 said:
Ok, let me get this straight, snag this Flashify, then snag TWRP 2.7.1.1, flash it with Flashify and I am golden????
(I am unlocked and S-Off running CM-11)
Click to expand...
Click to collapse
All u have to do is update your recovery. So u can grab the latest TWRP and flash it any method u wish. Fastboot is best but flashify is the most convenient. After u flash your recovery the CM Rom should flash perfectly. Note: If u experience any failures in flashing any Rom that u know is good just downgrade your recovery via which ever method u prefer and that should flash fine now. You can always use the recovery zip floating around on the android development thread I'll see if I can find it for u.
Here u go bud http://forum.xda-developers.com/showthread.php?t=2656065
Note if the flash fails try a older zip until it works and flash the twrp by TD. Don't forget to thanks rootlinux for the zips. Might also want to keep the zips in handy on the phone storage incase the Note situation appears.
Sent from my HTCONE using Tapatalk
luigi311 said:
All u have to do is update your recovery. So u can grab the latest TWRP and flash it any method u wish. Fastboot is best but flashify is the most convenient. After u flash your recovery the CM Rom should flash perfectly. Note: If u experience any failures in flashing any Rom that u know is good just downgrade your recovery via which ever method u prefer and that should flash fine now. You can always use the recovery zip floating around on the android development thread I'll see if I can find it for u.
Here u go bud http://forum.xda-developers.com/showthread.php?t=2656065
Note if the flash fails try a older zip until it works and flash the twrp by TD. Don't forget to thanks rootlinux for the zips. Might also want to keep the zips in handy on the phone storage incase the Note situation appears.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
I got it with fastboot, I forgot I re installed windows since I did it initially, so I was pulling my hair out wondering why fastboot wouldnt see it, and I couldnt even get files to or from it till I installed HTC sync.....heh
thanks for the info.....
Hi all,
I have a bit of a problem here, whenever I try to flash a .zip file in Cyanogen Recovery (CM12) it says: E: signature verification failed. Installation aborted.
Does anyone know how to solve it?
Thanks in advance!
xChillz (C6603)
I had that issue with the same recovery on a number of zips. Have you considered using another recovery?
Parker-ivxx said:
I had that issue with the same recovery on a number of zips. Have you considered using another recovery?
Click to expand...
Click to collapse
Yes I did, noone seems to be able to answer this question, so I'm going to plan B.
I would like to know how I can install TWRP over the CM12 recovery again, because when I flash the TWRP .img file with fastboot, it replaces my whole CM12 Rom.
Could someone explain to me how I can keep both CM12 + TWRP recovery?
Thanks in advance!
xChillz said:
I would like to know how I can install TWRP over the CM12 recovery again, because when I flash the TWRP .img file with fastboot, it replaces my whole CM12 Rom.
Click to expand...
Click to collapse
It replaces your Rom with what exactly
Try formatting the FOTAKernel either using xperia recovery manager or flashtool and then flash twrp/cwm and report back.
xChillz said:
Yes I did, noone seems to be able to answer this question, so I'm going to plan B.
I would like to know how I can install TWRP over the CM12 recovery again, because when I flash the TWRP .img file with fastboot, it replaces my whole CM12 Rom.
Could someone explain to me how I can keep both CM12 + TWRP recovery?
Thanks in advance!
Click to expand...
Click to collapse
I had the same problem.And i got permission denied when flashing fotakernal in flashboot mode.
I solved it by using "[ROOT] Rashr - Flash" Tool.It is in google play.
Hi there,
Now, this issue may already been addressed but if so, I couldn't find it.
I have a T810 tablet and I was running the stock ROM. Last year I flashed a custom ROM and so I thought when I entered recovery mode I was using some kind of custom recovery tool. But I was using the system one.
I formatted everything before attempting to flash LineageOS 'Apply update from SD card', resulting in the following output:
Code:
-- Install /sdcard/lineageos-16.0-20190407-nightly-gts210vewifi-signed.zip --
Finding update package
Opening update package
Verifying update package
E:failed to verify whole-file signature
Installation aborted
Now, obviously, when I try to turn the tablet on, I'm redirected to the recovery tool because there is no OS installed.
Also, I suppose this tool isn't meant for any type of zip file and I need a specific one.
Can someone point out to me where I can download the appropriate file?
I tried for the brief moment I could make ADB work flashing a ROM but it resulted in a similar issue.
Thanks for your help!
EDIT:
I tried flashing 'T810XXU2CPD9_T810XAC2CPE2_HOME.tar.md5': E:failed to map file
Everything I flash with adb result in footer or signature error.
I would really love an insight on how I can fix my tablet now that I f-'ed up everything.
I'm sorry for bumping this but I'm still trying to figure out how to unbrick my device. If you have anything for me, please tell me. I don't want to lose my tablet.
Can you enter download mode after reboot?
If you can,you can flash an official rom with Odin.
Cheers