HI. Please help me! I wasn't able to modify an article on the WIKI (wiki.xda-developers.com).
All the time I press the "Edit" Button, FireFox give me the option to download the php file :?: :?: :shock: WEIRD
The address I was modifying was:
http://wiki.xda-developers.com/index.php?pagename=List of HimaUpgradeUt.exe Error Code
After trying it several times, I could get inside and edit the page, then I saved it, and now is BLANK!!!!
HEEEEELLPPPP
The contets of the page at the time of my edit were:
--------------------------
ERROR 100: MODEL ID ERROR
Definition: ROM image is not design for the device you are upgrading. It happens when you try to use Himalaya's ROM image into other HTC like MAGICIAN, BlueAngel or Alpine
Solution: Use appropriate ROM Upgrade image for your Device, no two device can share the same ROM
ERROR 101: CONNECTION ERROR
ERROR 102: CE IMAGE FILE CHECKSUM ERROR
ERROR 103: ROM IMAGE FILE NOT FOUND
ERROR 104: CANNOT OPEN ROM IMAGE FILE
ERROR 105: OPEN PORT FAILURE
ERROR 106: EXECUTE REMOTE COMMUNICATION PROGRAM FAILURE
WARNING 111: POWER ADAPTER NOT PLUGGED IN
ERROR 112: CE ROM UPDATE ERROR
ERROR 113: EXTENDED ROM UPDATE ERROR
ERROR 114: RADIO ROM UPDATE ERROR
ERROR 115: INVALID VERSION OF ACTIVESYNC
ERROR:116 GENERAL ERROR
ERROR 117: INVALID MODEL ID
ERROR 120: COUNTRY ID ERROR
ERROR 121: LANGUAGE ID ERROR
ERROR 122: EXTENDED IMAGE FILE CHECKSUM ERROR
ERROR 123: RADIO IMAGE FILE CHECKSUM ERROR
ERROR 130: CREATE CE ROM IMAGE ERROR
ERROR 131: ALLOCATE MEMORY ERROR
ERROR 132: WRITE DATA ERROR
ERROR 133: COMMUNICATION ERROR
ERROR 134: READ CE ROM IMAGE ERROR
ERROR 135: COMMUNICATION ERROR
ERROR 136: COMMUNICATION INTERRUPT
ERROR 137: COMMUNICATION ERROR
ERROR 150: ROM UPGRADE UTILITY ERROR
ERROR 200: WRITE EXTENDED ROM FAIL
Error 201: GET DEVICE DATA ERROR
This error is a bit misleading. The BAUpdate tool is trying to switch the phone into bootloader mode, and the phone for some reason is being uncooperative. This happens to me from time to time. The best, and quickest way around this is to force the phone into Bootloader manually. By pressing the record button, while doing a hard reset (Power + Reset) your phone will enter bootloader mode. You can verify this as the screen will say, Serial, and change to USB when you cradle it.
Once you cradle your phone, Windows will detect it as new hardware, and take a minute or two configure the right driver(Microsoft USB Sync). Once this is complete, you can run the BAUpgrade utility again, and this time you should get past error 201.
Error 202: READ IMAGE ERROR
ERROR 210: CREATE EXTENDED ROM IMAGE ERROR
ERROR 211: ALLOCATE MEMORY ERROR
ERROR 212: WRITE DATA ERROR
ERROR 213: COMMUNICATION ERROR
ERROR 214: READ EXTENDED ROM IMAGE ERROR
ERROR 215 COMMUNICATION ERROR
ERROR 216: COMMUNICATION INTERRUPT
ERROR 310: CREATE RADIO ROM IMAGE ERROR
ERROR 311: ALLOCATE MEMORY ERROR
ERROR 312: WRITE DATA ERROR
ERROR 313: COMMUNICATION ERROR
ERROR 314: READ RADIO ROM IMAGE ERROR
ERROR 315: COMMUNICATION ERROR
ERROR 316: COMMUNICATION INTERRUPT
ERROR 317: COMMUNICATION ERROR
Hi,
I tried it too & have simular probs in changing any wiki page @ the moment. IMHO there's something wrong on the serverside cause the text is still present but compilation into a page fails.
Try again later is my suggestion.
Cheers, M
Yup, I thought it was a temporary problem. Moreover, I'm having the same strange behaviour in some wiki links.
For instance:
http://wiki.xda-developers.com/index.php?pagename=BA_Versions
It is the first link on this page:
http://wiki.xda-developers.com/index.php?pagename=BA_FAQ_Upgrade_Radio
Thanks for your answer. I'll try later........
oltp said:
Hi,
I tried it too & have simular probs in changing any wiki page @ the moment. IMHO there's something wrong on the serverside cause the text is still present but compilation into a page fails.
Try again later is my suggestion.
Cheers, M
Click to expand...
Click to collapse
If the problem persists you can always pm 'peter poelman' or another moderator, maybe they can fix it.
The way it is now, we'll have a very empty wiki soon. Luckily the preview shows the same errors & peolpe should be warned by that, so as long as people don't save any changes to a page...
Luckily, I think you can allways get an older version of the page.
Cheers
oltp said:
If the problem persists you can always pm 'peter poelman' or another moderator, maybe they can fix it.
The way it is now, we'll have a very empty wiki soon. Luckily the preview shows the same errors & peolpe should be warned by that, so as long as people don't save any changes to a page...
Click to expand...
Click to collapse
arieltools said:
Luckily, I think you can allways get an older version of the page.
Click to expand...
Click to collapse
Ok learned something again, I didn't know that.
dear all,
i try to login my securities broker's site through my softbank X01, which the site requested to install microsoft VM to load on PC. I have installed JeodeForIPAQ.exe in my X01 and tried netfront/opera 8.65/IE to load the trading page, but IE/netfront both failed to load the applet successfully.
May anyone suggest what can i do in X01 to load it successfully? Thanks In advance.
https://isec.christfund.com/InternetTrading/SecureLogin_en.jsp
LOGIN ID : IW0113
PW : 12345678
Good afternoon. I've installed two different programs and after installation, trying to run them i get error messages, as follow :
1) Program EventCountdownV2.2.exe. After installation (either in device, or
storage card), when i run the program i get this error message :
There is an unexpected error in application EventCountdownV2.2.exe. Choose "End" and then run this program again or choose "Details" for more details.
Details :
EventCountdownV2.2.exe
InvalidCastException
in Microsoft.VisualBasic.CompilerServices.Conversions.ToDate()
in RFTEventCountdown.form1.ListBox1_SelectedIndexChanged()
in System.Windows.Forms.ListBox.OnSelectedIndexChanged()
in System.Windows.Forms.Control._InternalWnProc()
in Microsoft.AGL.Forms.CTL.ListBox.set_SelectedIndex()
in RFTEventCountdown.form1.form1_Load()
in System.Windows.Forms.Form.OnLoad()
in System.Windows.Forms.Form_SetVisibleNotify()
in System.Windows.Forms.Control.set_Visible()
in System.Windows.Forms.Application.Run()
in RFTEventCountdown.form1.Main()
2) Program iFonz-0.9.4.exe. After installation (either in device, or
storage card), when i run the program i get this error message :
There is an unexpected error in application iFonz.exe. Choose "End" and then run this program again or choose "Details" for more details.
The query string is incorrectly formatted.
It is not possible to show error message because it is not possible to find optional sources retention.
Details :
iFonz.exe
ArgumentException
The query string is incorrectly formatted.
It is not possible to show error message because it is not possible to find optional sources retention.
in Microsoft.WindowsMobile.PocketOutlook.AppointmentCollection.Restrict()
in iFonz.iFonz.SetTopAndBallons()
in iFonz.iFonz.iFonz_Load()
in System.Windows.Forms.Form.OnLoad()
in System.Windows.Forms.Form_SetVisibleNotify()
in System.Windows.Forms.Control.set_Visible()
in System.Windows.Forms.Application.Run()
in iFonz.iFonz.Main()
Can somebody help me ? Is there any idea why this hapen? Any solution ? I tried to update .NET Compact Framework 3.5 Redistributable (installation sucsseful), but no results. Still get errors.
Regards
Kostas
Hello guys ,
Please help me to fix this error : error: only position independent executables (PIE) are supported.
I am using DOOGEE X5S Rooted android 5.1 I have this problem when I was following this guide :
android.stackexchange.com/a/55701/171994 ( I can't post outside links yet , sorry about that ).
Anyway , I already installed the cURL on my android phone , but I'm receiving this error on Terminal emulator error : position independence executables (PIE) are supported. Please guys help me to fix this error , Thank you guys for your help and your time
So today's been a big day, Let's Encrypt original CA expired at around 15:15 UK which is precisely when private DNS on my phone decided it wasn't going to play anymore.
DST Root CA X3 Expiration (September 2021) - Let's Encrypt
Update September 30, 2021 As planned, the DST Root CA X3 cross-sign has expired, and we’re now using our own ISRG Root X1 for trust on almost all devices. For more details about the plan, keep reading! We have also updated our Production Chain Changes thread on our community forum - our team and...
letsencrypt.org
The interesting thing is that Android trusts the new Let's Encrypt CA. Sure enough, browsing to the private DNS server in a web browser works fine. DavDroid/etc also work fine (same certificate used on that endpoint).
It appears that private DNS uses its very own CA certificate trust and this IS affected by the Let's Encrypt change.
So if your private DNS server stopped working with Android at around 15:15 today then check the server is using a Let's Encrypt certificate. This will be your problem.
Anyone know where I should file this bug with AOSP please do let me know. I have searched long and hard and really want this fixed!
I'm having the same issue, my tls dns server stopped to work on android, any solution?
Same problem with stock device Android 9. And /e/ ROM Android 10 on Gigaset GS290...
Oh dear, I spent the whole day debugging my DoT adguard instance today. Following while hoping there's a solution to this
guitphreak said:
Oh dear, I spent the whole day debugging my DoT adguard instance today. Following while hoping there's a solution to this
Click to expand...
Click to collapse
Also wasted the whole last day. So sad. This was a really great feature.
Same issue, right after launching the service. Tricky timing!
I'm wondering how to solve this in a different manner than having to replace the cert with non-letsencrypt
I'm already missing this feature very much. Can we try to install/configure our Android devices to trust ' ISRG Root X1 ' ?
edit: I just downloaded and trusted x1 on my android (https://letsencrypt.org/certificates/), no succes
topic on letsencrypt.org: https://community.letsencrypt.org/t/r3-intermediate-certificate-has-expired/160797/108
I'll have a look at alternative certificates for that VM. Google comes up with ZeroSSL. Seams like it'll be tonight's project
Problem solved for me.
I am using the acme.sh client (3.0.0) and regenerated (delete and recreate) my certificates with this settings :
--server letsencrypt --preferred-chain "ISRG Root X1"
More information here : https://github.com/acmesh-official/acme.sh/issues/3723#issuecomment-932143360
And here: https://github.com/acmesh-official/acme.sh/wiki/Preferred-Chain
PS: with certbot client:
certbot renew --preferred-chain "ISRG Root X1" --force-renewal
I have exactly the same problem. I have rented several vServers on which I have installed Pi-Hole and since yesterday ~8:00 (UTC) DNS over TLS no longer works. Have used nginx as proxy. My SSL certificates are all up to date and valid. With the tool Stubby (tested on Windows) I can connect and send DNS queries, but Android does not want.
Unfortunately, this does not seem to work. The parameter
Code:
--preferred-chain="ISRG Root X1"
does not work for certbot.
Code:
certbot: error: unrecognized arguments: --preferred-chain ISRG Root X1
But if I add the parameter
Code:
preferred_chain = ISRG Root X1
in
Code:
/etc/letsencrypt/renewal/domain.conf
, the certificate will be issued via ISRG Root X1.
After creating, the entry disappeared from the configuration.
However, Android 10 and 11 still can't connect.
Firefox says that everything is fine with the certificate.
Hoerli said:
I have exactly the same problem. I have rented several vServers on which I have installed Pi-Hole and since yesterday ~8:00 (UTC) DNS over TLS no longer works. Have used nginx as proxy. My SSL certificates are all up to date and valid. With the tool Stubby (tested on Windows) I can connect and send DNS queries, but Android does not want.
Unfortunately, this does not seem to work. The parameter
Code:
--preferred-chain="ISRG Root X1"
does not work for certbot.
Code:
certbot: error: unrecognized arguments: --preferred-chain ISRG Root X1
But if I add the parameter
Code:
preferred_chain = ISRG Root X1
in
Code:
/etc/letsencrypt/renewal/domain.conf
, the certificate will be issued via ISRG Root X1.
After creating, the entry disappeared from the configuration.
However, Android 10 and 11 still can't connect.
Firefox says that everything is fine with the certificate.
Click to expand...
Click to collapse
Which version of certbot client ?
Require 1.6.0 and more.
Better if 1.12.0 and more.
Latest is 1.19.0 now.
Check Certificate chain with: openssl s_client -connect yourdomain.tld:853
For me:
---
Certificate chain
0 s:CN = mydomain.tld
i:C = US, O = Let's Encrypt, CN = R3
1 s:C = US, O = Let's Encrypt, CN = R3
i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
---
Tetsumaki said:
Which version of certbot client ?
Require 1.6.0 and more.
Better if 1.12.0 and more.
Latest is 1.19.0 now.
Check Certificate chain with: openssl s_client -connect yourdomain.tld:853
For me:
---
Certificate chain
0 s:CN = mydomain.tld
i:C = US, O = Let's Encrypt, CN = R3
1 s:C = US, O = Let's Encrypt, CN = R3
i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
---
Click to expand...
Click to collapse
Oh now it seems to work ....
I have only ever used the official package source version.
For Debian 10:
Code:
[email protected]:~# apt-cache policy certbot | grep -i Installed
Installed: 0.31.0-1+deb10u1
I have now installed the latest version via snap (which I never use).
Code:
name: certbot
summary: Automatically configure HTTPS using Let's Encrypt
publisher: Certbot Project (certbot-eff✓)
store-url: https://snapcraft.io/certbot
contact: https://github.com/certbot/certbot/issues
license: unset
description: |
The objective of Certbot, Let's Encrypt, and the ACME (Automated
Certificate Management Environment) protocol is to make it possible
to set up an HTTPS server and have it automatically obtain a
browser-trusted certificate, without any human intervention. This is
accomplished by running a certificate management agent on the web
server.
This agent is used to:
- Automatically prove to the Let's Encrypt CA that you control the website
- Obtain a browser-trusted certificate and set it up on your web server
- Keep track of when your certificate is going to expire, and renew it
- Help you revoke the certificate if that ever becomes necessary.
commands:
- certbot
services:
certbot.renew: oneshot, enabled, inactive
snap-id: wy7i66qPx4neXr6m9rTh7Y40h8EhtZFh
tracking: latest/stable
refresh-date: today at 20:31 CEST
channels:
latest/stable: 1.19.0 2021-09-07 (1434) 44MB classic
latest/candidate: ↑
latest/beta: 1.19.0 2021-09-07 (1434) 44MB classic
latest/edge: 1.20.0.dev0 2021-10-01 (1498) 44MB classic
installed: 1.19.0 (1434) 44MB classic
The result with the certbot from the package sources:
Code:
Certificate chain
0 s:CN = mydomain.tld
i:C = US, O = Let's Encrypt, CN = R3
1 s:C = US, O = Let's Encrypt, CN = R3
i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
2 s:C = US, O = Internet Security Research Group, CN = ISRG Root X1
i:O = Digital Signature Trust Co., CN = DST Root CA X3
With snap-version:
Code:
Certificate chain
0 s:CN = mydomain.tld
i:C = US, O = Let's Encrypt, CN = R3
1 s:C = US, O = Let's Encrypt, CN = R3
i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
2 s:C = US, O = Internet Security Research Group, CN = ISRG Root X1
i:O = Digital Signature Trust Co., CN = DST Root CA X3
Ok, now I ran the command with --preferred-chain="ISRG Root X1" again for all certificates already issued.
Now it works after all
... and .... it works!
The old version of Certbot, has here in 2. place still made entries, which are now gone!
Code:
Certificate chain
0 s:CN = mydomain.tld
i:C = US, O = Let's Encrypt, CN = R3
1 s:C = US, O = Let's Encrypt, CN = R3
i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
Thanks! it worked... the only think is that i had to remvoe certbot from apt on my 18.04 and add the one from snap
My pihole is up and running again