[Q] help please - General Questions and Answers

Hi, I have a Samsung Galaxy S3 international version. I would like to prove custom ROMS and I have followed a lot of steps to prepare my device for this. I have download cm-10.1-20130116-NIGHTLY-i9300.zip. but get the following error:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
My phone has this elements with ODIN:
Android Version: 4.1.2
Version: I9300BUELK1
Kernel: 3.0.31.7-672976 [email protected]#1 SMP PREEMT Mon Dec 10 14:29:49 KST 2012
Build number: JZ054K.I9300XXELL5
Please, I need some help to solve it because I can go into the next step and I would like to prove a lot of things in my new phone.
Thanks in advance!

Related

Donut Installation Problem

I have a Dream running 1.5 and I want to download 1.6 (because for some reason I can't get it OTA) and it works perfectly until it installs the update and says "E: Failure at line 2: assert file_contains("SYSTEM:buildprop", "ro.build.fingerprint=tmobile/kila/dream/trout:1.5/CRC1/150275:user/ota-rel-keys,release-keys") == "true" l l file_contains("SYSTEM:build.prop", "ro.build.fingerprint=tmobile/kila/dream/trout:1Installation aborted." Any idea what's going on?
Hello.
I have exactly the same problem.
is there any way to update system without waiting for automatic update?
Greetings
hnnknr

[q] cannot upgrade to 2.1 ...!!

HTC HERO: Official Update To 2.1 (ASIA)
This is what is happening in the android system recovery on the Update – HTC Hero Android 2.1 Firmware Over The Air (FOTA) update (Second Package)
Build: RA-hero-v1.3.2
Finding update package...
opening update package...
verifying update package...
E:No signature (221 files)
E:Verification failed
Installation aborted.
the 1st package got installed successfully but in the second, the phone restarts and goes into the recovery mode...
WHAT DO I DO....ANY SUGGESTIONS..??
Sorry to bump the thread, I could really use some help
Additional Information
Baseband Version : 63.18.55.06EU_6.35.06.18
Kernel Version : 2.6.27-8dd6deee [email protected])
Build No : 2.73.720.5 146733 CL#61267 release-keys
Software Version : 1.0.0.A6288

[Q] Trying (and failing) to load b9 ICS port onto my Nexus S 3g

Hi guys, first post. Need a little bit of help here..firstly let me apologize if i have asked this in the wrong place...ive got no idea whats going on here sorry!
Ive got a Nexus S 3g..running version 2.3.6
The baseband version is I9023XXKF1 and kernel version 2.6.35.7-gf5f63ef
I had no problems rooting the phone and getting to the clockwork recovery, and after having downloaded the new b9 build of the ICS from http://forum.xda-developers.com/showpost.php?p=18622852&postcount=1 i put it on the sd card and then tried to load it but i got this message....
Finding update package...
Opening update package...
Installing update...
assert failed: get prop ("ro.product.device") =="crespo" l l getprop (ro.build.product") == "crespo" l l getprop ("ro.product.board") == "crespo"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted
Is there something i have done wrong, or something i need to do in order to get this running alright on my phone? Any help would be much appreciated
Cheers guys

[Completed] CM13 Comparing TZ Version, assert failed Error 7 while Installing latest Nightly

Hi, noob to CM13. Currently have cm-13.0-20160604-NIGHTLY-Z00T running on my Asus Zenfone 2 (ZE551KL). I have been trying to update to a newer build with no success, any build newer than 6/14 fails, and 6/14 itself is horribly unstable. The error message from the log file is as follows:
Comparing TZ version TZ.BF.3.0.C3-00025 to TZ.BF.3.0.R2-00064script aborted: assert failed:, asus.verify_trustzone("TZ.BF.3.0.C3-00025") == "1"
Comparing TZ version TZ.BF.3.0.C3-00025 to TZ.BF.3.0.R2-00064
assert failed: asus.verify_trustzone("TZ.BF.3.0.C3-00025") == "1"
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '/data/media/0/cmupdater/cm-13.0-20160704-NIGHTLY-Z00T.zip
By the way, I am using TWRP to update.
From my google searches, other people have claimed this is an outdated firmware problem, but I couldn't find anything on how to update my firmware.
Any help is greatly appreciated.
Hi,
Thanks for using XDA assist.
Please create a XDA account and post here:
[GENERAL HELP] Post Your Questions Here Instead of Making a New Thread
Good Luck! - gsstudios

Non T-Mobile CSC on T-Mobile I9505XXUHQK1 ROM

Hi,
this is more an informative post than a question, as I found nothing googling "ASKS OTA", but if you have contradictory information I'll take it
I just tried to flash the latest I9505XXUHQK1 ROM (which has a very high changelist (& "quality base" ?), CL12538431 QB15647851, and which seems to be only released with T-Mobile CSC) with a non T-Mobile CSC (mainly to keep the Black Edition customization), and the extraction at the first boot (which is in recovery) fails, blaming a missing ASKS token :
Code:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
E: ASKS OTA| Error, ASKS token doesn't exist.
E: ASKS OTA| Error, This is official binary. Failed.
Installation aborted.
E: ensure_path_unmounted failed to unmount /cache (Device or ressource busy)
E: ensure_path_unmounted failed to unmount /cache (Device or ressource busy)
In the T-Mobile CSC, there's an additional "SEC-INF/buildinfo.xml" which seems signed. The CSC itself seems to support a very few countries.
And of course, the CSC customizations are missing.
So the latest Black Edition ROM & CSC seems to be I9505XXUHQC1 (CL5978264 QB12742647) + I9505YXXHPL1 (you can get it with LUX region).
You can also get the La Fleur edition, QXX (I9505QXXHQC1).
I couldn't find the sources for I9505XXUHQC1 by the way, are they published ?
Well, after digging a bit more I found
https://forum.xda-developers.com/showthread.php?t=1633333&page=572 which seems to relate to https://source.android.com/security/apksigning/v2
and https://android.stackexchange.com/q...curity-software-and-device-protection-manager
So this doesn't seems to be specific to T-Mobile as I thought (the "This is official binary. Failed." is weird however), but I guess there's no non-T-Mobile CSC compatible with QK1 yet.

Categories

Resources