Hey guys,
i just created this account because i'm really lost right now.
since 3 days i'm trying to flash a new version of cyanogenmod on my phone, but it always failed because of an TWRP error (error status 7).
it wasn't really a problem because i just flashed the working version(cm-11-20131222-Nightly-i9305) back on and everything was alright.
but now i accidentally deleted this version and the cyanogenmod site doesn't list it anymore.
i've been trying to install a new version on the phone with always the same error no matter which version i try.
after i looked it up here, i deleted the assert part in the updater-script. doesn't work either.
so i upgraded the TWRP to the current version via Odin because i read it could help.
and now it only saids:
set_metadata_recursive: some changes failed.
E: Error executing updater binary in zip <PATH>
Error flashing zip <PATH>
and i can only boot into the download or recovery mode now.
i hope anybody can help me with that. i also could offer the recovery.log from TWRP if it would help.
Wrong forum, i9305 has a specific section where you're most likely to receive an answer. Report your own post and ask a moderator to move it.
Usual advice is to flash a full stock rom using odin then start over, check the md5 of any downloads.
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,
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.
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
Hello
I received a notice to install the new KitKat on my rooted HTC one with TWRP 2.7.0.0
"OTA_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.11-3.62.401.1_release_356395e7z2lsr0msqontmw.zip" 3XX,XX MB
When I tried to install the update from the recovery it tells me that no MD5 file was found
then
E:Signature Verification failed :1
and update is aborted ...
How can I solve this problem ?
Should I save a backup before starting solving ?
Will I lose my files ?
And thanks by the way
xsodia said:
Hello
I received a notice to install the new KitKat on my rooted HTC one with TWRP 2.7.0.0
"OTA_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.11-3.62.401.1_release_356395e7z2lsr0msqontmw.zip" 3XX,XX MB
When I tried to install the update from the recovery it tells me that no MD5 file was found
then
E:Signature Verification failed :1
and update is aborted ...
How can I solve this problem ?
Should I save a backup before starting solving ?
Will I lose my files ?
And thanks by the way
Click to expand...
Click to collapse
There are many threads to do with this subject already.
You need stock recovery to install OTA. Find the one that is for your existing OS and flash it. Redownload the ota and it should install. If you have made any mods to your existing rom, that can also prevent the ota from installing properly.
Any yes I would make a nandroid first!
Ah that's all I needed !
this word key : Stock Recovery !
Thanks a lot my problem is solved and I'm eating the Kitkat now thanks
I had to "FIX Fastboot for win 8.1 x64"
Then "S-OFF my phone with hboot 1.55"
Then Flash the recovery with "Stock Recovery signed"
Last but not least,My kitkat is awesome !
Solved
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