Get it here:
http://www.t-mobile.nl/zakelijk/htdocs/page/diensten/mda_upgrade.asp
Hi there!
Is there some of the dutch brothers that can tell me if the new 1.60.36 duch version has the english language like the 1.60.00?
Thank you very very much!
how to upgrade from Dangaard 1.60.21 to the NEW TMobile ?
How to upgrade from Dangaard 1.60.21 to the RUU16036WWE_T-Mobile_NL ?
Thanks.
Does anyone already try this upgrade? Whats new on this version? Any improvement? Thanks!
Does anyone already try this upgrade? Whats new on this version? Any improvement? Thanks!
Germand MDAII
Just send e-mail to T-mobile Germany, when they will release the german upgrade, as Iam still on 1.60.00GER.
So its wait and see. otherwize I will change to the dutch one, as that seemed to work perfectly fine with me the onofficial upgrade
this update contains radio 1.10,
osrom 1.60.00WWE
and extended rom 1.60.36
decrypt upgrade files with:
Code:
xda2nbftool -x NK.nbf nk.nba 0x89124137
xda2nbftool -x Radio_.nbf radio.nba 0x12345678
xda2nbftool -x ms_.nbf ms.nba 0x25863614
All files on ext.rom is from 01.09.2003. ? :shock:
Only version number changed on ext.rom. :roll:
Telephone screen collour
Is the telephone screen collour still that disgusting pink?
Is there a need for an upgrade a new ROM from T-Mobile 1.60 to this 1.60.36? Since the radio version been upgraded thus this means we have more reliable signal strength?
THANKS!
I get a Country ID error when installing this ROM update on my Qtek 2020.
Has anyone an idea how to go on?
search for 'country AND error' in the forum.
lots of postings about that problem
What about the "big" step in the radiostack ????
I just upgraded to 1.06.01
Any expierence around ?
Any improvments ?
mjk said:
I get a Country ID error when installing this ROM update on my Qtek 2020.
Has anyone an idea how to go on?
Click to expand...
Click to collapse
xda2nbftool -x NK.nbf nk.nba 0x89124137
xda2nbftool -x ms_.nbf ms_.nba 0x25863614
xda2nbftool -x radio_.nbf radio_.nba 0x12345678
xda2nbftool -sd PH10 -so Qtek -sl ENG -v ms_.nba
xda2nbftool -sd PH10 -so Qtek -sl ENG -v Radio_.nba
xda2nbftool -sd PH10 -so Qtek -sl ENG -v nk.nba
xda2nbftool -x NK.nba nk.nbf 0x89124137
xda2nbftool -x ms_.nba ms_.nbf 0x25863614
xda2nbftool -x radio_.nba radio_.nbf 0x12345678
HimaUpgradeUt.exe
thanks a lot
i get the error when encrypting:
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
WARNING: checksum is not ok, possibly you provided the wrong password
I did it this way:
xda2nbftool -x NK.nbf nk.nba 0x89124137
xda2nbftool -x ms_.nbf ms_.nba 0x25863614
xda2nbftool -x radio_.nbf radio_.nba 0x12345678
xda2nbftool -sd PH10 -so Qtek -sl WWE -v ms_.nba
xda2nbftool -sd PH10 -so Qtek -sl WWE -v Radio_.nba
xda2nbftool -sd PH10 -so Qtek -sl WWE -v nk.nba
xda2nbftool -e NK.nba nk.nbf 921211
Del ms_.nbf
Del Radio_.nbf
Rename ms_.nba ms_.nbf
Rename radio_.nba radio_.nbf
download the upgrade.rar from this posting:
http://forum.xda-developers.com/viewtopic.php?t=4785
unpack it in the same directory, this will overwrite
HimaUpgradeUt.exe.
Run HimaUpgradeUt.exe
The strange thing is I have an original T-Mobile device, but the device ID is recognized as an Qtek.
Somehow I changed my device ID in my MDA II...
xkingz said:
The strange thing is I have an original T-Mobile device, but the device ID is recognized as an Qtek.
Somehow I changed my device ID in my MDA II...
Click to expand...
Click to collapse
that is caused by this line
xda2nbftool -sd PH10 -so Qtek -sl WWE -v ms_.nba
Click to expand...
Click to collapse
This morning i did the upgrade.
i hadn't any problem to upgrade from the previous 1.60.00WWE NL.
This release seem to work as good as the 1.60.00. Plus, it has a SMS incoming tone.
The only problem (and it isn't quite little...) is that the battery full indicator says 3h57m versus the 7h30m of the previous release i had...
By the moment, i don't think upgrade has been a great idea... :roll:
Pap
itsme said:
xkingz said:
The strange thing is I have an original T-Mobile device, but the device ID is recognized as an Qtek.
Somehow I changed my device ID in my MDA II...
Click to expand...
Click to collapse
that is caused by this line
xda2nbftool -sd PH10 -so Qtek -sl WWE -v ms_.nba
Click to expand...
Click to collapse
Click to expand...
Click to collapse
The line changes the rom ID to Qtek so it can work on the MDA II with an Qtek ID.
If i use getdevicedata trick it says it's a Qtek. While I have an original Tmobile MDA II. Original Tmobile Rom's won't work.
If there was a way to change my device ID to Tmobile (what it should be anyway), I wouldn't have to use xda2nbftool and change the rom to Qtek right?
Isn't it possible to encrypt the files again with the XOR option?
What is exaclty in the Update.rar? Are these ammended versions of the update procedure with takes the decrypted files instead?
Related
Please can anyone post just the O2 ms_.nbf for the XDAII including the O2 Bubbles at Softreset?
Thx
Mike
PS: Is thsi string correct for my german O2 XDA I: xda2nbftool -sd PH10 -so O2 -sl GER -v ms_.nbf ?
hi!!
i downloaded llbasha-WM5-AKU35pp16c3 rom
i want extract os.nb file from nk.nbf with typho5 utility (typhoonbftool_v5),i got this error:
unknow header format, and it abort work.
other way:
i want extract os.nb file from nk.nba with prepare_imgfs, and i got this error:
searching for IMGFS start.......Not found!!!
anybody know if it can extract some file from a rom already cooked ???
thank in advance
any help on this
NOW AT FILE 34 OF 34 IN system/framework: twframework.odex
Disassembling twframework.odex ...
java -Xmx512m -jar baksmali.jar -a 10 -d ../framework -x twframework.odex
UNEXPECTED TOP-LEVEL EXCEPTION:
org.jf.dexlib.Util.ExceptionWithContext: regCount does not match the number of arguments of the method
at org.jf.dexlib.Util.ExceptionWithContext.withContext(ExceptionWithContext.java:54)
at org.jf.dexlib.Code.InstructionIterator.IterateInstructions(InstructionIterator.java:92)
at org.jf.dexlib.CodeItem.readItem(CodeItem.java:154)
at org.jf.dexlib.Item.readFrom(Item.java:76)
at org.jf.dexlib.OffsettedSection.readItems(OffsettedSection.java:48)
at org.jf.dexlib.Section.readFrom(Section.java:143)
at org.jf.dexlib.DexFile.<init>(DexFile.java:431)
at org.jf.baksmali.main.main(main.java:265)
Caused by: java.lang.RuntimeException: regCount does not match the number of arguments of the method
at org.jf.dexlib.Code.Format.Instruction35c.checkItem(Instruction35c.java:160)
at org.jf.dexlib.Code.Format.Instruction35c.<init>(Instruction35c.java:93)
at org.jf.dexlib.Code.Format.Instruction35c$Factory.makeInstruction(Instruction35c.java:167)
at org.jf.dexlib.Code.InstructionIterator.IterateInstructions(InstructionIterator.java:84)
... 6 more
Error occured at code address 0
code_item @0x1cf58
-> Using brute-force method (ignore above error if successful):
Disassembling twframework.odex ...
java -Xmx512m -jar baksmali.jar -a 10 -d ../framework -c :am.jar:android.policy.jar:android.test.runner.jar:apache-xml.jar:bmgr.jar:bouncycastle.jar:bu.jar:com.android.future.usb.accessory.jar:com.android.location.provider.jar:com.google.android.maps.jar:com.google.android.media.effects.jar:com.google.widevine.software.drm.jar:com.samsung.device.jar:com.yamaha.android.media.jar:core.jar:core-junit.jar:ext.jar:filterfw.jar:framework2.jar:framework.jar:GlobalConfig.jar:ime.jar:input.jar:javax.obex.jar:libvtmanagerjar.jar:minimode.jar:monkey.jarm.jar:seccamera.jar:sec_feature.jar:secframework.jar:sechardware.jar:secmediarecorder.jar:send_bug.jar:services.jar:svc.jar:twframework.jar -x twframework.odex
UNEXPECTED TOP-LEVEL EXCEPTION:
org.jf.dexlib.Util.ExceptionWithContext: regCount does not match the number of arguments of the method
at org.jf.dexlib.Util.ExceptionWithContext.withContext(ExceptionWithContext.java:54)
at org.jf.dexlib.Code.InstructionIterator.IterateInstructions(InstructionIterator.java:92)
at org.jf.dexlib.CodeItem.readItem(CodeItem.java:154)
at org.jf.dexlib.Item.readFrom(Item.java:76)
at org.jf.dexlib.OffsettedSection.readItems(OffsettedSection.java:48)
at org.jf.dexlib.Section.readFrom(Section.java:143)
at org.jf.dexlib.DexFile.<init>(DexFile.java:431)
at org.jf.baksmali.main.main(main.java:265)
Caused by: java.lang.RuntimeException: regCount does not match the number of arguments of the method
at org.jf.dexlib.Code.Format.Instruction35c.checkItem(Instruction35c.java:160)
at org.jf.dexlib.Code.Format.Instruction35c.<init>(Instruction35c.java:93)
at org.jf.dexlib.Code.Format.Instruction35c$Factory.makeInstruction(Instruction35c.java:167)
at org.jf.dexlib.Code.InstructionIterator.IterateInstructions(InstructionIterator.java:84)
... 6 more
Error occured at code address 0
code_item @0x1cf58
ERROR: Aborting twframework.odex
Finished system/framework
Could not deodex the following (you can try to deodex these files again):
am.odex android.policy.odex android.test.runner.odex apache-xml.odex bmgr.odex bouncycastle.odex bu.odex com.android.future.usb.accessory.odex com.android.location.provider.odex com.google.widevine.software.drm.odex com.yamaha.android.media.odex core-junit.odex core.odex ext.odex filterfw.odex framework2.odex framework.odex GlobalConfig.odex ime.odex input.odex javax.obex.odex libvtmanagerjar.odex minimode.odex monkey.odex pm.odex seccamera.odex sec_feature.odex secframework.odex sechardware.odex secmediarecorder.odex send_bug.odex services.odex svc.odex twframework.odex
Click to expand...
Click to collapse
can anyone help?
API level for ICS apk's need to be set @ 14
Sent from my GT-I9100 using xda premium
UpInTheAir said:
API level for ICS apk's need to be set @ 14
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
how and where to do that
Arjav23 said:
how and where to do that
Click to expand...
Click to collapse
the syntax is java -jar baksmali.jar -a <api_level> -x <odex_file> -d <framework_dir>
so you should use -a 14
hope this helps
HeD_pE said:
the syntax is java -jar baksmali.jar -a -x -d
so you should use -a 14
hope this helps
Click to expand...
Click to collapse
I actually need for froyo which is a 8
But where do I add or modify that part??
Sent from my GT-I5800 using xda premium
Can anyone tell how to deodex it ?
PHP:
Disassembling ./system/app/Camera.odex ...
java -Xmx512m -jar baksmali.jar -a 15 -d system/framework -x ./system/app/Camera.odex
Error while disassembling method Lcom/scalado/camera/hdr/HDR$JpegCallbackHandler$1;->run()V. Continuing.
org.jf.dexlib.Code.Analysis.ValidationException: class Lcom/scalado/caps/hdrimage/HDRImage$Options; cannot be resolved.
at org.jf.dexlib.Code.Analysis.ClassPath$UnresolvedClassDef.unresolvedValidationException(ClassPath.java:535)
at org.jf.dexlib.Code.Analysis.ClassPath$UnresolvedClassDef.getClassDepth(ClassPath.java:543)
at org.jf.dexlib.Code.Analysis.ClassPath.getCommonSuperclass(ClassPath.java:384)
at org.jf.dexlib.Code.Analysis.RegisterType.merge(RegisterType.java:275)
at org.jf.dexlib.Code.Analysis.AnalyzedInstruction.mergeRegister(AnalyzedInstruction.java:185)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.propagateRegisterToSuccessors(MethodAnalyzer.java:451)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.setPostRegisterTypeAndPropagateChanges(MethodAnalyzer.java:416)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.setDestinationRegisterTypeAndPropagateChanges(MethodAnalyzer.java:403)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyzeMoveResult(MethodAnalyzer.java:1714)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyzeInstruction(MethodAnalyzer.java:654)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyze(MethodAnalyzer.java:213)
at org.jf.baksmali.Adaptors.MethodDefinition.addAnalyzedInstructionMethodItems(MethodDefinition.java:379)
at org.jf.baksmali.Adaptors.MethodDefinition.getMethodItems(MethodDefinition.java:301)
at org.jf.baksmali.Adaptors.MethodDefinition.writeTo(MethodDefinition.java:132)
at org.jf.baksmali.Adaptors.ClassDefinition.writeMethods(ClassDefinition.java:338)
at org.jf.baksmali.Adaptors.ClassDefinition.writeVirtualMethods(ClassDefinition.java:323)
at org.jf.baksmali.Adaptors.ClassDefinition.writeTo(ClassDefinition.java:152)
at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:205)
at org.jf.baksmali.main.main(main.java:293)
opcode: move-result-object
CodeAddress: 395
Method: Lcom/scalado/camera/hdr/HDR$JpegCallbackHandler$1;->run()V
in you bootclasspath use the jar from the attachment
enjoy
midnightfly said:
Can anyone tell how to deodex it ?
PHP:
Disassembling ./system/app/Camera.odex ...
java -Xmx512m -jar baksmali.jar -a 15 -d system/framework -x ./system/app/Camera.odex
Error while disassembling method Lcom/scalado/camera/hdr/HDR$JpegCallbackHandler$1;->run()V. Continuing.
org.jf.dexlib.Code.Analysis.ValidationException: class Lcom/scalado/caps/hdrimage/HDRImage$Options; cannot be resolved.
at org.jf.dexlib.Code.Analysis.ClassPath$UnresolvedClassDef.unresolvedValidationException(ClassPath.java:535)
at org.jf.dexlib.Code.Analysis.ClassPath$UnresolvedClassDef.getClassDepth(ClassPath.java:543)
at org.jf.dexlib.Code.Analysis.ClassPath.getCommonSuperclass(ClassPath.java:384)
at org.jf.dexlib.Code.Analysis.RegisterType.merge(RegisterType.java:275)
at org.jf.dexlib.Code.Analysis.AnalyzedInstruction.mergeRegister(AnalyzedInstruction.java:185)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.propagateRegisterToSuccessors(MethodAnalyzer.java:451)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.setPostRegisterTypeAndPropagateChanges(MethodAnalyzer.java:416)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.setDestinationRegisterTypeAndPropagateChanges(MethodAnalyzer.java:403)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyzeMoveResult(MethodAnalyzer.java:1714)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyzeInstruction(MethodAnalyzer.java:654)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyze(MethodAnalyzer.java:213)
at org.jf.baksmali.Adaptors.MethodDefinition.addAnalyzedInstructionMethodItems(MethodDefinition.java:379)
at org.jf.baksmali.Adaptors.MethodDefinition.getMethodItems(MethodDefinition.java:301)
at org.jf.baksmali.Adaptors.MethodDefinition.writeTo(MethodDefinition.java:132)
at org.jf.baksmali.Adaptors.ClassDefinition.writeMethods(ClassDefinition.java:338)
at org.jf.baksmali.Adaptors.ClassDefinition.writeVirtualMethods(ClassDefinition.java:323)
at org.jf.baksmali.Adaptors.ClassDefinition.writeTo(ClassDefinition.java:152)
at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:205)
at org.jf.baksmali.main.main(main.java:293)
opcode: move-result-object
CodeAddress: 395
Method: Lcom/scalado/camera/hdr/HDR$JpegCallbackHandler$1;->run()V
Click to expand...
Click to collapse
I'm trying to create an update.zip that will install a Koodo radio on my SGH-i757m since I have switched from Bell. I took DSIXDA's original Bell Modem update for the i757m and replaced the MDM/AMSS files from the stock SGH-T989D rom from Koodo. I see that the manifest's contain SHA-1 keys relating to the files. Is that another step to create those or is that what happens during APK signing?
Judging by the output of the SignApk.jar it looks like I'm missing something from the JDK but I can't figure out what.
I followed these instructions :
1. You need to download the SignApk.jar - This is the tool that signs the file download from here - a mediafire link I found on xda. Unzip the file to a convenient location, you only need the SignApk.jar that you'll find inside.
2. You will also be using OpenSSL, so head over here and download the zip on the side for your iteration of windows (32 or 64 bit).
2. Place the zip on your desktop and unzip it.
3. You have to execute these commands in command prompt:
Code:
cd location_of_openssl_folder\bin
openssl genrsa -out key.pem 1024
openssl req -new -key key.pem -config location_of_openssl_folder\openssl.cnf -out request.pem
openssl x509 -req -days 9999 -in request.pem -signkey key.pem -out certificate.pem
openssl pkcs8 -topk8 -outform DER -in key.pem -inform PEM -out key.pk8 -nocrypt
That will work. Your certificate.pem and key.pk8 will be located in the \bin folder.
4. Now, take the key.pk8 file found in the \bin folder and the certificate.pem file found also in the \bin folder and place then in the folder containing your SignApk.jar (it will overwrite the other files found in the folder, its ok).
Click to expand...
Click to collapse
After trying to sign the zip using the command:
Code:
$ java -jar SignApk.jar key.pem key.pk8 KoodoRadio.zip Update.zip
I get:
Code:
java.security.cert.CertificateParsingException: signed overrun, bytes = 463
at sun.security.x509.X509CertImpl.parse(Unknown Source)
at sun.security.x509.X509CertImpl.<init>(Unknown Source)
at sun.security.provider.X509Factory.engineGenerateCertificate(Unknown Source)
at java.security.cert.CertificateFactory.generateCertificate(Unknown Source)
at com.android.signapk.SignApk.readPublicKey(SignApk.java:75)
at com.android.signapk.SignApk.main(SignApk.java:318)