I did a lot of customization to my phone, so I can't possibly list all the programs I have. Last thing I remember doing was installing Opera Mini with a JAVA client (I think JBed). It kept crashing, so I uninstalled it.
Now whenever I go to run IE, I get this error message:
The file 'MortScript' cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. If the problem persists, try reinstalling or restoring this file.
Click to expand...
Click to collapse
I've never explicitly installed MortScript before that message. I have since downloaded and installed MortScript from http://www.sto-helit.de/index.php?module=download&action=list&category=18 but it didn't solve the problem.
halp plz!
bumpination
Hi, ( i hope this is the right forum for this or if not can someone please help me or direct me to the right now to resolve this) just wondering if anyone(s) out there that had this problem after they had any of the TMOUS HD2 'Driods' hacks installed on a SD card, had it running for a while, then turn off your phone, try to restart and get this error (this is occuring on both the CLRCAD and HARET programs) "The File 'XXXX" cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. If the problem preresist, try reinstalling or restoring this file". i have already formatted and reinstalled the files on the SD card and been to most of the forums here about this issue for their resolution. (all with no luck) If there anyone out there with a simple resoultion (hopefully nothing too complex like a reg hack) can you please help me out with this issue. Thanks in advance
Crossposting, thread closed.
ive tried a new version of navigon, i quote what happend:
webwalk® said:
aww man, whats with this version...
deploy, start server -> check your internetconnection (3g still enabled but no net, shut it down after)
replug phone, restart server, start navigon.. connecting....
but then my phone connected and disconnected from usb 5 or 6 times quickly and zune couldnt find device anymore..
replug, restart... still connecting screen..
ill try one last time... the usb disconnecting freaks me out...
error deploying... 0x89731812
WTF! now replug phone: ZUNE READ ERROR, CANT READ IMPORTANT PARTS FROM DEVICE!
i hope its mango error.. phone restart seems to have fixxed it...
tried one last time.. cant connect to server, forever " connecting " dont know whats up... maybe pc restart, but chance is too low to try out..
device is tmode mozart UK language
ow shhhh... cant deploy anything anymore... error deploying... 0x89731812
Click to expand...
Click to collapse
i rememberd zune had visual problems when i came out of hibernation mode, so ive restarted PC, same problem...
dont know much more yet, maybe a phone restart fixxes it... trying now.. /edit, didnt fix it, CRY
//more info:
while the sudden disconnecting happend,
windows tried to install unknown drivers, but failed,
maybe thats causing the trouble..
i really hope its mango not hardware issue
btw, still unlocked, can start homebrew & sync zune
freaks me out.. next up:
reinstall zune & mango sdk
if not working, nodo backup
ive also read about a hd2 guy with this error but also couldnt sync with zune,
he also had the unknown drivers installed, but never got a fix,
he couldnt even flash a rom, also not after reinstalling everything...
a little scary story, surfing in dangerous grounds
homebrew Xaps in mango
Microsoft doesn't support ID_CAP_INTEROPSERVICES" in mango, but not all xaps require it, I removed it from the Navigon xap and then re-deployed it and it ran fine all my maps work on mango
A question here, what did you package .xap with?
CP-Geek said:
A question here, what did you package .xap with?
Click to expand...
Click to collapse
Use either WinRAR or 7zip to unzip the XAP. Edit the file, compress to a zip, rename zip to XAP. I have a thread on this already...
drkfngthdragnlrd said:
Use either WinRAR or 7zip to unzip the XAP. Edit the file, compress to a zip, rename zip to XAP. I have a thread on this already...
Click to expand...
Click to collapse
There's no need to decompress the archive in order to be able to edit a certain file. At least if it's text based. I for one open the xap with 7zip, then right click the xml file and choose "edit". I can then edit the file to my needs, save it and when I close 7zip it asks me to write the changes to the archive. Once this is done I can deploy the xap to my device and all is fine.
True, the result is exactly the same, but this way you save some time and reduce the amount of possible mistakes.
dkp1977 said:
There's no need to decompress the archive in order to be able to edit a certain file. At least if it's text based. I for one open the xap with 7zip, then right click the xml file and choose "edit". I can then edit the file to my needs, save it and when I close 7zip it asks me to write the changes to the archive. Once this is done I can deploy the xap to my device and all is fine.
True, the result is exactly the same, but this way you save some time and reduce the amount of possible mistakes.
Click to expand...
Click to collapse
True, never thought about that. Sometimes we just overlook the simple solutions lol...
a little offtopic
however, i successfully deployed other versions of the same app earlier on mango so i dont think it had something to do with ID_CAP_INTEROPSERVICES
it seems mango with tmode spl needs more work.
it get lots of different small bugs..
like i had 5x the same call in multitasking..
aborting calls almost crashed my phone today..
im thinking it was alround more stable on htceu spl
but i didnt try to fix anything yet..
maybe when i want to deploy something next time,
ill keep reporting..
mcsc said:
Microsoft doesn't support ID_CAP_INTEROPSERVICES" in mango, but not all xaps require it, I removed it from the Navigon xap and then re-deployed it and it ran fine all my maps work on mango
Click to expand...
Click to collapse
Did someone tried to use IC_CAP_INTEROPSERVICES in apps? Heard that too about the deactivation but I'm still looking for proof.
I have the same error 0x89731812 !
I can't deploy any XAP with Application Deployment. I can't debug too with Visual Studio Express (Failed to connect to device. Ensure the device is completly booted and connected to PC).
I have restarted PC and telephone and reinstalled SDK and Zune but the error is still here !
As far as I know the Mango update removes your unlock. I think the only method to keep it unlocked is to use the provxml method. I've got a Omnia 7 which got relocked after Mango beta update - then I restored my unlocked NoDo backup. I'll try the provxml method and tell you if it worked for me
yes its not that the device is not unlocked, it still is.
@zuifon:
did you notice at some point that windows tried to install drivers for your phone but couldnt find any?
it looks like only restore will resolve this error.. its still a beta..
but i dont know yet, i still didnt try it but thx for reporting,
so i wont have to check if reinstall the windows software fixxes it
My phone is unlocked by APPMFG.
Applications installed before Mango still work.
The message is the same if I disconnect the USB Cable, it's very curious !
Zune detects the phone but not the deployer.
I have deleted the phone in the periphal manager in Windows and driver have been redownloaded from Windows Update but the problem is the same.
zuifon said:
I have deleted the phone in the periphal manager in Windows and driver have been redownloaded from Windows Update but the problem is the same.
Click to expand...
Click to collapse
the unknown driver? or the phone driver?
my device manager does not show any unknown driver..
but it found unknown (the phone) hardware at some point..
now someone over here
reported that he also had used a different phone but can not deploy with the computer anymore. not sure if he has the same error code.
It's a phone problem. I have the same problem with a second computer.
hey guys,
i updated my dev unlocked omnia 7 to mango and re-unlocked it after having finished the update process.
for some reason, i cannot deploy any .xap to my phone, regardless of having ID_CAP_INTEROPSERVICES or not.
the software deployment software keeps telling me "the remotehost has closed the connection".
anyone have an idea? this is majorly annoying for me.
cheers,
phil
hey，I just think we have the same problem as you described，and i resolved it by my friends help. It's really easy, hey hey, just try to change it on another Universal Serial Bus. Hope can help you~~
heh actually i never tried using another usb port..
i have zuned the backup, everything working again.
maybe update to mango in some days
What on earth could be causing this? My phone (Optimus7) was in service and it got new mainboard. After it came back i did the usual tricks to unlock it etc. but now the deploying ends to this 0x89731812 error no matter what i try. Could anyone have an idea on where to start looking for the cause?
tkay564 said:
What on earth could be causing this? My phone (Optimus7) was in service and it got new mainboard. After it came back i did the usual tricks to unlock it etc. but now the deploying ends to this 0x89731812 error no matter what i try. Could anyone have an idea on where to start looking for the cause?
Click to expand...
Click to collapse
Same here, i don't know if it's warranty repair-related, i don't remember if i unlocked it after that (i relocked it way before mango, that's for sure)...but i got no new mainboard, they just replaced some components (based on repair list sheet), it seems strange they changed something so important to break developer connectivity
°Dexter° said:
Same here, i don't know if it's warranty repair-related, i don't remember if i unlocked it after that (i relocked it way before mango, that's for sure)...but i got no new mainboard, they just replaced some components (based on repair list sheet), it seems strange they changed something so important to break developer connectivity
Click to expand...
Click to collapse
Does anyone know if this could be repair-related or just software? i tried last chewron tool too, no changes, phone doesn't connect to "developer" tools.
I guess if there is any registry key related to developer connectivity, to check if they changed anything through some strange sw flash (hoping it's not really hw)
http://www.youtube.com/watch?v=JmvCpR45LKA
I have seriously searched EVERY DAMN INCH of the Internet for this. Okay, obviously, I've seen all the posts like this one:
http://forum.xda-developers.com/showthread.php?t=2351390 (I actually wanted to reply there but can't, sad)
And I've done all those steps, I've uninstalled everything, I've reinstalled everything, I've called my mom to tell her she wasn't lying to me about me being special, I've done it all ten times. This is what happens:
System stuff: Windows XP, cyanogenmod 10, ADB and Apps set to root, USB debugging on, Android 4.2.2, latest Android Commander, Galaxy S3 Sprint, Android Debug Bridge version 1.0.31
I open cmd and type adb devices, it shows me a device is available:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
ba0a8be4 device
I open Android Commander, it has a blank line that's highlighted blue, I click "OK", it says:
Connected device has status offline and cannot be used. Please reboot your device.
I reboot my device, same thing happens.
Does anyone have any ideas? I'm seriously about to just flash it to 421 but I hate just giving up. I hate it almost as much as I hate asking for help. I spent 7 hours last night (I was up until 2am!!) and then another 4 or 5 today just trying to figure this out. I'm completely lost here. Oh, another thing, since I'm at it, does anyone know how to delete the saved RSA key from my phone? I looked in that data/adb place that link said and renamed it but it didn't seem to reset the key... maybe I need to restart, I'll try restarting after I rename it. Yep, I bet that'll work. It probably had it in memory. Anyway, pointless rant about RSA done. I hope someone has some ideas before I resort to just sitting in the corner, cuddling up with my phone, and crying until my mommy tells me I'm special.
Another possibly important thing is that Droid Explorer works briefly (I can see phone's files come up) but then crashes when I try opening anything.
It also, as I was just playing with it, seems like Android Commander causes the adb server to become outdated. Does that mean anything? I just ran adb devices, then tried AC, then did adb dev again and it needed to restart the service. I don't know if that means anything. Just something I noticed.
Oops I had to update the link, I just realized I copied the wrong one from the page suggestions it does. This now has the one I meant.
Did you find a solution? I am having the same problem.
I gave up. Flashed stock, then cm 10 with system and cache wipes then cm 10.1 without wiping system. Haven't tried with my computer since I mostly use my phone. I'll check later and update this and let you know. I would have just kept stock but my god that stuff sprint puts on sickens me......
I found a solution and it works.
http://forum.xda-developers.com/showpost.php?p=40276190&postcount=1488
Yeah, I even said in my message that I made sure that was up to date. I was able to connect to adb and see it show up as a device now but Android Commander doesn't work. I did find out that adb push (and I assume pull) works but that probably worked before and I just didn't try. Anyway, I'm not too concerned. Glad you got yours figured out.
Hope this helps!
I managed to get android commander to work by installing the latest adb with the sdk manager and then I copied adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to the bin folder located where ever you install android commander!
lukesheardown said:
I managed to get android commander to work by installing the latest adb with the sdk manager and then I copied adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to the bin folder located where ever you install android commander!
Click to expand...
Click to collapse
Copying the adb files to the bin directory worked for me, thanks!
I got this Surface recently and like dozens of others the touchscreen stopped working.
I tried everything.
-Let the battery drain.
-Resetted it via its internal recovery (delete everything)
-Deinstalled Firmware Touch (2.1.15.0 - 12.08.2013) and Firmware Configuration (0.0.33.0 - 12.08.2013)
-HID Touchscreen (6.3.9600.16384 - 21.06.2006)
-Restarted
-Windows Installed just "Firmware" then and claimed its the newest one...:silly:
-I read there was Firmware 2.1.17.0 (but only for Surface 2 WiFi... (?)
-And I read about KB3172729 which led to this problem according to this link :
https://forums.windowscentral.com/microsoft-surface-2/313399-2.htm
But its a 2016 KB and my Surface got its last updates in 2014.
-I read about custom Recovery Images...but only downloaded an original recovery from MS (Surface2_BMR_20.2.19.0.zip)
which I installed (deleted TPM via F12) and only had issues whiel entering a password for the user...cursor dissapeared and it was laggy as hell.
It installed but no touchscreen.
Time to ask on xda I thought...also Id love to get back to Windows 8.0 RT if possible. (?)
Thanks in advance.
Desperately I did now try :
Stopped service "Windows Update"
Deleted all files in: C:\Windows\SoftwareDistribution\download (it did indeed have 4 temp folders with updates from today)...
-cmd (as admin)
-DISM.exe /Online /Cleanup-image /Restorehealth
100% restore operation completed succesfully
-sfc /scannow
Verification up to 100%, no problems found. -_-
Then started Windows Update. "searching for updates"...it took 10 minutes and showed all updates, including a Firmware (09.11.2015) and the "evil" KB3172729.
I just selected the Firmware thing, which turns out indeed to be the 2.1.17.0 (07.10.2015). Surface restarted and I
got the yellow exclamation Mark in the device manager at the Firmware...like many others before me...just great -_-
Additonally The Microsoft Management Console stopped working...wow...
Still, no touchscreen.
https://www.errorsolutions.tech/error/windows-update-error-code-80244010/
Trying to re-update the firmware keeps showing a "Searching online for drivers"...I cant cancel it.
Installed 1,5GB updates now, without the "evil" KB3172729.
No touchscreen.
I start to regret getting my hands on this device. Seriously Microsoft, wtf ?
Mario,
did you find any solution yet? I tried everything also and still not working.
iResmas
me too ... I got a surface 2, I tried different ways to find a solution for the problem of ''touch firmware = Yellow exclamation mark on it in Device manager'' and still not working.
I downloaded all given updates, but nothing happened, still not working.
PLZ .... guide me to find the right SOL.