Database Info

Help me with italian settings

I really cant find anywhere the cab file for automatic setting for my Prophet. My carrier is TIM! thank's all!

I think the follow instruction will help you
TIM Italia
Setting for Internet
2. Network Name :
Tim GPRS
3. Modem Name :
cellular,3G
4. Modem Access Point Name :
ibox.tim.it
5. Username :
""
6. Password :
""
7. Domain :
""
8. Is there a tick in the 'This network connects to the Internet' box :
No
9. Is there a tick in the 'This network uses a proxy server' box :
No
10 Proxy Server Address and port :
No
Setting For MMS
2. Network Name :
Tim MMS
3. Modem Name :
cellular,3G
4. Modem Access Point Name :
mms.tim.it
5. Username :
""
6. Password :
""
7. Domain :
""
8. Is there a tick in the 'This network connects to the Internet' box :
No
9. Is there a tick in the 'This network uses a proxy server' box :
No
10 Proxy Server Address and port :
No
MMS Settings
1. Server Name :
Tim MMS
2. Gateway :
213.230.130.89
3. Port Number :
80
4. Server Address :
http://mms.tim.it/servlets/mms
5. Connect Via :
Tim MMS
6. Size Limit :
7. WAP Version :
2.0

Thank a lot!

[HOW-TO]Change wifi mac address on mt6589

Hi everyone , this is my first how-to guide
i will try to keep it as clear as possible
NOTE : I will not be held responsible if you change your wifi mac address for illegal purposes.
A backup of your NVRAM is recommended.
Method 1(via Engineering mode)
This method does NOT require ROOT access.
1.Download MTK Engineering Mode shortcut app from here :https://play.google.com/store/apps/details?id=com.themonsterit.EngineerStarter
2.Turn Off your Wifi .Open MTK Engineering Mode shortcut app and Click MTK Settings.
(Incase you are not able to access Engineering mode, skip to alternate method below)
3.Swipe To Connectivity Tab.
4.Click Wifi
5.Click NVRAM
6.In Byte String Access put values as
addr(h,byte) : 4
length(byte) : 6
7.Click Read. The 12 Digits shown in value(h) field is your current wifi mac address.Better make a note of it.
8.Erase the value(h) field and now put your own 12 digit mac address,
IMPORTANT:
RULES FOR WIFI MAC ADDRESS
1.Should be 12 Digits long only
2.Should have hexadecimal characters only (0-F)
3.Second digit of mac address should be Even Digit only (0 or 2 or 4 or 6 or 8 or A or C or E)
valid example - 0205160F0A3E
invalid example - 016GEABCDF59
9.Click write.
10.Exit to Home, Turn Off and turn On your Wifi Again.
11.Now Check your Wifi mac address in Phone Status.It should be Changed to what you entered in Step 8.
12.To get back your original Mac address, repeat the process with original Mac address value.
Alternate Method
THIS METHOD REQUIRES ROOT ACCESS
1.Get any good File Browser with Root access (https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree)
2.Get this Hex Editor : https://play.google.com/store/apps/details?id=tuba.tools
3.Turnoff your wifi.With the File Browser, browse to /data/nvram/APCFG/APRDEB/
4.Copy the file called WIFI to sdcard twice(one for backup purpose and other to edit)
5.Also note the permissions on the WIFI file (for me it was rw-rw----)
6.Rename this file to WIFI.bak
7.Open the copied WIFI file on sdcard with Hex Editor.
8.Notice your Wifi mac Address from address 04 to 09.Change the values of addresses 04,05,06,07,08,09 each with corresponding 2 digits of your new mac address
IMPORTANT:
RULES FOR WIFI MAC ADDRESS
1.Should be 12 Digits long only
2.Should have hexadecimal characters only (0-F)
3.Second digit of mac address should be Even Digit only (0 or 2 or 4 or 6 or 8 or A or C or E)
valid example - 0205160F0A3E
invalid example - 016GEABCDF59
9.Save it.
10.Now copy this modified WIFI file to /data/nvram/APCFG/APRDEB/
11.Set the permissions you noticed in step 5 to this just copied WIFI file( rw-rw---- in my case)
12.Turn on Your Wifi And check your mac address,it should be changed.
Screenshots coming soon,
If this guide helped you ,Click THANKS button.

chiragjn said:
Hi everyone , this is my first how-to guide
i will try to keep it as clear as possible
NOTE : I will not be held responsible if you change your wifi mac address for illegal purposes.
A backup of your NVRAM is recommended.
Method 1(via Engineering mode)
This method does NOT require ROOT access.
1.Download MTK Engineering Mode shortcut app from here :https://play.google.com/store/apps/details?id=com.themonsterit.EngineerStarter
2.Turn Off your Wifi .Open MTK Engineering Mode shortcut app and Click MTK Settings
.
(Incase you are not able to access Engineering mode, skip to alternate method below)
3.Swipe To Connectivity Tab.
4.Click Wifi
5.Click NVRAM
6.In Byte String Access put values as
addr(h,byte) : 4
length(byte) : 6
7.Click Read. The 12 Digits shown in value(h) field is your current wifi mac address.Better make a note of it.
8.Erase the value(h) field and now put your own 12 digit mac address,
IMPORTANT:
RULES FOR WIFI MAC ADDRESS
1.Should be 12 Digit long only
2.Should have hexadecimal characters only (0-F)
3.Second digit of mac address should be Even Digit only (0 or 2 or 4 or 6 or 8 or A or C or E)
valid example - 0205160F0A3E
invalid example - 016GEABCDF59
9.Click write.
10.Exit to Home, Turn Off and turn On your Wifi Again.
11.Now Check your Wifi mac address in Phone Status.It should be Changed to what you entered in Step 8.
12.To get back your original Mac address, repeat the process with original Mac address value.
Alternate Method
THIS METHOD REQUIRES ROOT ACCESS
1.Get any good File Browser with Root access (https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree)
2.Get this Hex Editor : https://play.google.com/store/apps/details?id=tuba.tools
3.Turnoff your wifi.With the File Browser, browse to /data/nvram/APCFG/APRDEB/
4.Copy the file called WIFI to sdcard twice(once for backup purpose)
5.Also note the permissions on the WIFI file (for me it was rw-rw----)
6.Rename this file to WIFI.bak
7.Open the copied WIFI file on sdcard with Hex Editor.
8.Notice your Wifi mac Address from address 04 to 09.Change the values of addresses 04,05,06,07,08,09 each with corresponding 2 digits of your new mac address
IMPORTANT:
RULES FOR WIFI MAC ADDRESS
1.Should be 12 Digit long only
2.Should have hexadecimal characters only (0-F)
3.Second digit of mac address should be Even Digit only (0 or 2 or 4 or 6 or 8 or A or C or E)
valid example - 0205160F0A3E
invalid example - 016GEABCDF59
9.Save it.
10.Now copy this modified WIFI file to /data/nvram/APCFG/APRDEB/
11.Set the permissions you noticed in step 5 to this just copied WIFI file( rw-rw---- in my case)
12.Turn on Your Wifi And check your mac address,it should be changed.
Screenshots coming soon,
If this guide helped you ,Click THANKS button.
Click to expand...
Click to collapse
Lenovo S920, MT6589 device, data folder is empty. Nevertheless there's a lot of stuff in the folder /dev, but no /APCFG/APRDEB/ route at all either.
The first "non-root" method didn't worked for me either. It changes the MAC but when I am trying to connect to the router with this "new" MAC, which by the way it worked in my Galaxy Note with Cyanogenmod 10.2 installed, the phone can't get internet, although it connects to the router.

mulenguezt said:
Lenovo S920, MT6589 device, data folder is empty. Nevertheless there's a lot of stuff in the folder /dev, but no /APCFG/APRDEB/ route at all either.
Click to expand...
Click to collapse
Now I know that all these "Droids" are not created equal... But, I suspect that your unable to find the /APCFG/APRDEB/ in the /dev Folder... Is 'cause its under the /data Folder....
/data/nvram"/APCFG/APRDEB" -> WIFI & WIFI_CONFIG...
BTW:
2.Turn Off your Wifi .Open MTK Engineering Mode shortcut app and Click MTK Settings
.
(Incase you are not able to access Engineering mode, skip to alternate method below)
3.Swipe To Connectivity Tab.
4.Click Wifi
5.Click NVRAM
6.In Byte String Access put values as
addr(h,byte) : 4
BTW: You messed up... At least so with whatever version of MTK Engineering Mode is currenty on Google play...
length(h,byte) : 6
lenght(byte) : 4
That'll net you the first Four Digits plus the last Eight of your MAC Address... Such as it is.
Though I'll doubt that this too would survive a wipe. Before heading back off to 00:08:22:xx:xx:xx-random-land again...

nice guide but is there any way to permanently change MAC address. it auto Revert back to original MAC address On reboot
Thanks!

ANY IDEA ABOUT THIS ISSUE????
>>Step: Ap Meta Disconnect with target...
>>OK: Exit Meta successfully
>>----------------------------------------------------------------------<<
>>Step:Begin Scan Smart Phone data...
>>Step: Cancel scan Barcode DiagBox.
>>-------------------------------------------------------------------<<
>>Step: Enter Meta Mode && Smart Phone;
>>Step:Begin Scan Smart Phone data...
>>Step: Start to Init AP Nvram Database...
OK: Init AP Nvram Database successfully.
>>Step: Start to Connect with target...
COM port searching and preloader handshake
COM port searching and preloader handshake ok
COM port searching and Kernel handshake
COM port searching and Kernel handshake OK
SP_META_ConnectInMetaMode_r Error: maybe is META_MISC_FAIL_TO_WRITE_BACKUP_RESULT cause...
Error: Connect failed, Exit Meta Mode and turn to next phone.
ERROR!! Go to ST_END statues is: ST_AP
>>Step: Ap Meta Disconnect with target...
>>OK: Exit Meta successfully
>>----------------------------------------------------------------------<<
>>Step:Begin Scan Smart Phone data...
>>Step: Cancel scan Barcode DiagBox.

chamelemac
I know of this app
https://play.google.com/store/apps/details?id=com.cryptotel.chamelemac&hl=en
chamelemac
it changed mac adress for Leva ported Rom perfectly.And it persist through restart of phone.
It will however have "error not compatible device" if device prop is changed to something like "samsung galaxy" etc.

IcemanSR said:
I know of this app
https://play.google.com/store/apps/details?id=com.cryptotel.chamelemac&hl=en
chamelemac
it changed mac adress for Leva ported Rom perfectly.And it persist through restart of phone.
It will however have "error not compatible device" if device prop is changed to something like "samsung galaxy" etc.
Click to expand...
Click to collapse
Worked for me too!!!! Every time i reboot, the last 3 par of HEX char randomly change.
After set the original mac address with Chamelemac, and a reboot, MAC ADDRESS remains!!!!
NOTE: tested and working with MT6595 Zopo zp999 3gb RAM 32gb ROM

5.Click NVRAM
6.In Byte String Access put values as
addr(h,byte) : 4
length(byte) : 6
Ok this works but evidently my info are stored somewhere else. at 4 and 6 I have only zeroes. Programming those worked (it stick after reboot) but didn't fix the issue. Still have the 1st 6 hex the same and the other 6 randomly changed everytime I disable the wifi
Question is, do you have any idea where (at what addres) this string could be stored?
I have an ALPS w806 aka K18
thank you

How could you restore your device.prop or build.prop to its default? I'm encountering an Chamelemac error: "error not compatible device" on my Huawei Y220-U10. I wish you could enlighten me a bit because just last few months I've been able to change my mac address with the use of Chamelemac but now I can't. And i don't know why, maybe application update but it seems like chamelemac is just stuck with version 1.0 . Maybe you know something that could help me. By the way I'd rather use chamelemac other than those posted on the thread because it's easy to use just one click and i could change my mac address instantly. Hope for your response. Thanks in advance!

Ichijoe said:
Now I know that all these "Droids" are not created equal... But, I suspect that your unable to find the /APCFG/APRDEB/ in the /dev Folder... Is 'cause its under the /data Folder....
/data/nvram"/APCFG/APRDEB" -> WIFI & WIFI_CONFIG...
BTW:
2.Turn Off your Wifi .Open MTK Engineering Mode shortcut app and Click MTK Settings
.
(Incase you are not able to access Engineering mode, skip to alternate method below)
3.Swipe To Connectivity Tab.
4.Click Wifi
5.Click NVRAM
6.In Byte String Access put values as
addr(h,byte) : 4
BTW: You messed up... At least so with whatever version of MTK Engineering Mode is currenty on Google play...
length(h,byte) : 6
lenght(byte) : 4
That'll net you the first Four Digits plus the last Eight of your MAC Address... Such as it is.
Though I'll doubt that this too would survive a wipe. Before heading back off to 00:08:22:xx:xx:xx-random-land again...
Click to expand...
Click to collapse
Hi there. This is work to Lenovo TAB2 A8-50F. My Wi-Fi Mac Address is every time when I turn on and connect to Wi-Fi point is automatic changing. Now, I have a fixed Mac Address. Thanks.
What I am do?
Install MTK Engineering Mode app. Then turn off Wi-Fi. Launch MTK EM app > Go to Connectivity Tab > Wi-Fi > NVRAM. Then type at "Byte String Access:".
add(n,byte): 6
length(byte): 4
value(h): 11223344
Then push button Write. Turn on Wi-Fi. Go to check Wi-Fi Mac Address. There must be an 00:00:11:22:33:44. Thanks!

my phone a1 aq4501 processor MT 6582 help me

Thanks a lot. You saved me

the MTK Engineering methods doesnt works for me,, neither does any other method iam trying since past few days. Could anyone help? I have a Infinix hot 4 pro

/data/nvram does no texist in my system and nothing hapend when i create it a put the file exist another way for fix it? i try install another roms but only one work but imei wifi BT dont work, i can not intall many roms my phone and PC dont install good the preloader driver. i just can use the fastboot and only one rom can be intalled sucses whit that bug i'm sad

I click write many times but it doesn't change. Crap

TheDarkLord098 said:
I click write many times but it doesn't change. Crap
Click to expand...
Click to collapse
I too am stuck here with you.

daveburnt said:
I too am stuck here with you.
Click to expand...
Click to collapse
Sucks really ?

Thanks a lot.

Last resort
If you are unable to change your MAC with those methods, I found a working solution that should work for everyone. Try this: http://bbs.infinixmobility.com/forum.php?mod=viewthread&action=printable&tid=13678 It worked for me when anything I tried didn't work.

Hi,
I'm sorry, but the files below are not found:/data/nvram/APCFG/APRDEB/
any other solution?
Thanks

[DEV] AndroidCtrl.dll [7.1.46.0] (ADB/Fastboot/(apk/zip) Signer - Framework)

This (C# .NET 4.6|4.7|4.8) dll is a kind of ADB/Fastboot/(apk/zip) Signer - Framework, it provides a lot of predefined .NET functions to communicate with an Android device. It's designed to work in 1st case with any non-root device but you can also use it with any rooted device (A few functions requires root access).
License
This project is licensed under the Apache License Version 2.0.
The latest build 7.1.46.0 is currently only via FTP, GoogleDrive or Dropbox available, the DevDB has currently some upload issues!
The following (N)amespaces, (C)lasses & (I)nterfaces are currently available:
(N) ADB
(N) Binary (This is the binary/exe implementation of ADB)
(C) ADB (static Management Class for the ADBClient's)
(C) ADBClient (Implementation of IADBClient)
(C) Channel (Implementation of IChannel)
(N) Device
(N) BusyBox
(C) BusyBox
(C) Find
(C) Tar
(N) Dumpsys
(C) Battery
(C) Dumpsys
(I) IBattery
(N) Input
(I) IKeyEvent
(C) Input
(C) InputExtensions
(C) KeyEvent (Implementation of IKeyEvent)
(N) IO
(NS) Compression
(NS) BrotliSharp (Only available in .NET 4.6|4.7|4.8 - In .NET Standard >= 2.1 you have to use the native .NET implementation)
(C) ADirectoryInfo (Similar to .NET Directory/-Info)
(C) AFileInfo (Similar to .NET File/-Info)
(C) AFileStream (Similar to .NET FileStream)
(C) AFileSystemInfo (Similar to .NET FileSystemInfo, it's the abstract base for ADirectoryInfo & AFileInfo)
(C) AMountPointInfo (Similar to ADirectoryInfo & AFileInfo but only for mounts)
(C) FileSystemCache (A cache object for ADirectoryInfo & AFileInfo)
(I) IFileSystemCache (Interface for FileSystemCache)
(C) IO
(I) ITransferMessage
(C) MediaScanner (Manage the Android MediaScanner, useful after some file-transfers via ADB)
(C) Mount (Requires Root and manage the mounts)
(C) Stat (stat class for the ADB-Protocol)
(C) SyncStream (Base implementation of the ADB sync service. Utilized by AFileStream)
(C) TransferMessage
(C) UPath (Similar to .Net Path but for unix paths)
(N) Logcat
(I) ILogEntry
(C) Logcat
(C) LogEntry
(N) Manager
(C) ActivityManager
(I) IInstrumentation
(C) Instrumentation
(I) IPackage
(I) IPermission
(C) Manager
(C) Package
(C) PackageManager
(C) Permission
(N) Provider
(C) Contacts (Contacts provider)
(C) ContactsDataField
(C) ContactsEmail
(C) ContactsEvent
(C) ContactsGroup
(C) ContactsIdentity
(C) ContactsIM
(C) ContactsName
(C) ContactsNickname
(C) ContactsNote
(C) ContactsOrganization
(C) ContactsPhone
(C) ContactsPhoto
(C) ContactsPostalAddress
(C) ContactsRelation
(C) ContactsSipAddress
(C) ContactsWebsite
(I) IContactsDataField
(C) Provider
(C) Telephony (Telephony provider)
(N) Screen
(C) Framebuffer (Implementation of IFramebuffer)
(C) FramebufferInfo
(I) IFramebuffer (Interface of an RAW framebuffer)
(I) IFramebufferInfo
(I) IScreenDimension
(I) IScreenFocus
(C) Screen
(C) ScreenDimension
(C) ScreenFocus
(N) Shell
(I) IShell (Interface of an shell with in-/output abilities)
(C) Shell (Implementation of IShell)
(N) SQLite
(C) Options
(C) QueryTools
(C) SQLite3 (SQLite3 database connector)
(C) BuildProperties
(C) Daemon (Manage the daemon on the device)
(C) Device
(C) Forensics (ALFA-State)
(I) IUptime
(C) OpenRecoveryScript (Manage the OpenRecoveryScript)
(C) Phone (Start a call, dial a number, add a contact or send a sms)
(C) Su
(C) Uptime
(C) Wipe
(N) Shares
(C) Monitor (Implementation of IMonitor)
(N) Socket (This is the IP based implementation of ADB - Here is NO binary/exe required)
(C) ADB (static Management Class for the ADBClient's)
(C) ADBClient (Implementation of IADBClient)
(C) ADBSocket (IP based connector - Mimics the ADB-Server)
(C) Channel (Implementation of IChannel)
(C) ADBridge (Unified access to Binary.ADB and Socket.ADB)
(I) IADBClient (Interface for nearly all ADB commands)
(I) IChannel (Interface of an RAW data channel)
(N) Fastboot
(C) Backdoor (Some backdoor commands)
(C) Fastboot (static Management Class for the FastbootClient's)
(C) FastbootClient (Includes nearly all fastboot.exe commands)
(I) IFastbootClient (Interface for FastbootClient)
(C) Monitor (Implementation of IMonitor)
(C) OEM (Some OEM commands)
(C) Wipe
(N) ProcessModels
(C) General (Includes some predefined process models)
(I) IRealTimeBG (Interface of an background process with in-/output abilities)
(C) RealTimeBGExeV2 (Implementation of IRealTimeBG)
(N) Signer
(C) Signer (signapk.jar Interface)
(N) Tools
(C) CRC
(C) Deploy (Deploy the AAPT/ADB/Fastboot/Signer files needed by this dll)
(C) Hash
(C) Hex
(C) IMEI (Some helper to verify and rebuild a valid IMEI)
(C) ToolBox
(C) Cleanup (Delete the files/folders which were created by this dll)
(C) Config
(C) DeviceInfo (Basic device info, the return from "(Binary/Socket).ADB.Devices()" and "Fastboot.Devices()")
(I) IDeviceInfo (Interface for DeviceInfo)
(I) IMonitor (Interface for the ADB.Binary, ADB.Socket and Fastboot.Fastboot monitor)
Special
Ready-To-Go MVVM's for WPF, XAML via my AndroidCtrlUI.dll
Multi-Device compatible, you can manage unlimited devices at the same time with this dll. Each device gets it's own instance. (Thread-Safe, the dll use lock() for critical sections)
UTF8-File/Folder Transfer you can transfer files/folders with containing special chars (ü, ö, ä, €, @, à, è, etc.)
On-the-fly Device to Device copy (Binary <-> Binary | Binary <-> Socket | Socket <-> Socket)
Device-Monitor, if activated, it will check every 10 sec. ADB & Fastboot for new connected devices and call an defined callback, if something changed. So your program get's an info if an device is connected or removed.
All Android key-events as (int)enum and the ability to send them as single or stack.
Hint
You can use all ADB methods/commands via USB or W-Lan/Lan, if your Rom supports ADB via W-Lan/Lan (Settings/Developer Settings)
If you want to use all sub-classes of IADBClient with BusyBox instead of the Shell, you have to set IADBClient.UseBusyBox to true. This will tell the instance to use the BusyBox commands inside each method, if the device has BusyBox installed.
Referenced .NET assembly's
System
System.Numerics
System.XML
Used Code-analysis rules:
Basic & Advanced Microsoft-Rules for Accuracy
Microsoft-managed minimum & recommended rules
Microsoft Security Rules
About the usage, the namespaces (ADB, Fastboot, Signer) have one basic instance. For example, ADB.Instance(), Fastboot.Instance(), Signer.Instance. As you can see ADB.Instance() and Fastboot.Instance() can have a parameter. This parameter is in both cases an (string) DeviceID, an IDeviceInfo or null, if you use for example null, both classes will return it's Selected client. If you use the DeviceID or the IDeviceInfo the return is a fresh instance of the client or the already created instance. So, in any case, before you call ADB/Fastboot.Instance(). Check with ADB/Fastboot.Devices() if you have a connected device. If so, use the IDeviceInfo object to start your device instance or simply pass the serial to the Instance(). All instances which you have created on this way, will be hold inside an Dictionary<string, ADBClient>, so you can configure each device instance to it's needs and call it when ever you need it. This is also the point where i say it's multi-device and multi-thread safe. Because, if you always use ADB/Fastboot.Instance() you can't reach the wrong device. Also, all classes using lock() for critical sections, because [MethodImpl(MethodImplOptions.Synchronized)] is not longer available under .NET Standard.
If you have any wishes like new features, how-to's or something else, let me know! :cyclops:
Tested OS
Win Vista | 7 | 8 | 8.1 | 10 (32Bit/64Bit in VM-Ware)
Win 7 | 8 | 8.1 | 10 (64Bit Native)
Win XP is not longer supported by ADB! (But, if you have a old ADB binary, the dll will do it's job)
Tested Devices
Android Emulator some Versions (min. 2.x) in AVD
Android x86
HTC Sensation -/ XE (non-/rooted)
HTC One M9 (non-/rooted)
Huawei P9 Lite (VNS-L21,22,23,31,etc.) (non-/rooted)
Huawei P10 Lite (WAS-LX1A,etc.) (non-/rooted)
Samsung Galaxy 2-5 (non-/rooted)
Samsung Galaxy S Plus (non-rooted)
A few Samsung Tabs (non-/rooted)
Google Pixel 4 (Android 11) (non-/rooted)
Requirements
Android: min. 2.x
Platform: x86/x64 (Windows)
Frameworks: min. .NET 4.6 and JRE (only for the Signer)
(Installed ADB/Fastboot device driver)
Download
Mirror: XDA-DevDB (since 29.01.2019 no uploads possible)
Mirror #1: My FTP (Build archiv)
Mirror #2: GoogleDrive
Mirror #3: Dropbox
Each zip-archiv contains the AndroidCtrl.dll, its markup file AndroidCtrl.xml and the program debug database AndroidCtrl.pdb for .NET 4.6|4.7|4.8 and .NET Standard 2.1 (beta)
Examples (Updated to dll version 7.1.46.0) (Updated in the next 24 h)
Mirror: My FTP
Mirror #1: GoogleDrive
Mirror #2: Dropbox
(Contains a simple exe and its source written in C# WPF)
Source
N/A (If you want to have a look at it, send me a PM or simply decompile it.)
DO NOT MIRROR MY FILES! DO NOT COPY MY THREADS!
XDA:DevDB Information
AndroidCtrl.dll, Tool/Utility for the Android General
Contributors
k1ll3r8e, squabbi, Krystanos
Version Information
Status: Stable
Current Stable Version: 7.1.46.0
Stable Release Date: 2020-09-19
Created 2016-07-24
Last Updated 2020-09-19

How - To
0. Complete How-To
1. Getting Started (General)
2. Config & Deploy
3. Individual Call (ADB/Fastboot/Signer)
4. Start/Stop (ADB/Fastboot)
5. Reboot (ADB/Fastboot)
6. DeviceConnectionMonitor
7. Device state check
8. Send KeyEvents (ADB)

Problems & Solutions
1. Windows 8.x | 10.x
NOTE
If u use any callback functions, u have to invoke any UI-/ variable-interaction from an dispatcher like the following example:
Code:
public void Monitor(Added|Changed|Removed)EventHandler(object sender, Monitor(Added|Changed|Removed)EventArgs e)
{
App.Current.Dispatcher.Invoke((Action)delegate
{
// IDeviceInfo[] e.Devices
// Here u can interact with an UI-Element or an variable in ur program code
});
}
if u do it without dispatcher, u'll get an "Thread Exception".
More examples coming soon...
(If u need a specific example, just let me know, i'll try my best to provide one.)

Changelog
DD.MM.YYYY | (A) = Added | (C) = Changed | (D) = Deleted | (F) = Fixed | (R) = Recoded | (U) Updated
----------------------------------------------------------------------------------------------------------------------------------------------------
26.07.2020 [7.0.46.0]
(A) Some new Async overloads to the AFileInfo, AFileSystemInfo, ADirectoryInfo and AMountpointInfo.
(F) A few little bugs
01.02.2020 [6.7.46.0]
(A) ADB.IADBClient{} (The old IADB interface)
(A) ADB.Binary.ADB{} (The old ADB class - only the statics)
(A) ADB.Binary.ADBClient{} (The old ADB class - without any statics)
(A) ADB.Socket.ADB{} (The old ADB class - only the statics)
(A) ADB.Socket.ADBClient{} (The old ADB class - without any statics)
(A) ADB.Device.ADirectoryInfo{}
(A) ADB.Device.AFileInfo{}
(A) ADB.Device.AFileStream{}
(A) ADB.Device.AMountPointInfo{}
(A) ADB.Device.FileSystemCache{}
(A) ADB.Device.IFileSystemCache{}
(D) ADB.Device.Directories{}
(D) ADB.Device.Files{}
(D) ADB.Device.FileSystem{}
(D) ADB.Device.FileSystemItem{}
(D) ADB.Device.IFileSystemItem{}
And everything related to those classes... Directories has been replaced with ADirectoryInfo, Files has been replaced with AFileInfo and FileSystem has been replaced with AMountPointInfo.
31.05.2019 [6.0.46.0]
(C) The Framework Version from 4.0 to 4.6
(C) The versioning:
6 = Major
0 = Minor
46 = Framework Version (4.6)
0 = Hotfix
(A) (int) ADB.Instance().Device.Screen.GetAutoBrightness()
(A) (int) ADB.Instance().Device.Screen.GetBrightness()
(A) (ScreenBrightnessMode) ADB.Instance().Device.Screen.GetBrightnessMode()
(A) (ScreenRotation) ADB.Instance().Device.Screen.GetRotation()
(A) (ScreenRotationMode) ADB.Instance().Device.Screen.GetRotationMode()
(A) (bool) ADB.Instance().Device.Screen.SetBrightness(int brightness)
(A) (bool) ADB.Instance().Device.Screen.SetBrightnessMode(ScreenBrightnessMode mode)
(A) (bool) ADB.Instance().Device.Screen.SetRotation(ScreenRotation rotation)
(A) (bool) ADB.Instance().Device.Screen.SetRotationMode(ScreenRotationMode mode)
(D) ASDK (enum)
(C From) (ASDK) ADB.Instance().Device.GetSDK()
(C To) (int) ADB.Instance().Device. GetSDK()
10.04.2019 [0.0.5.2]
(A) A workaround for older SU binaries
Code:
// (Source ADB.Device.Su {})
///<summary>
/// Enables an (W)ork(A)round for older SU binaries, which needs the command as an single argument.
///<para/>For example, the latest SU binaries support a syntax like [su -c id -u] where older binaries need [su -c "id -u"]
///<para/>If u deactivate this workaround by enabled <see cref="IADB.UseSu"/>, <see cref="IADB.UseSu"/> gets also disabled!
///<para/>This workaround is by default disabled
///<para/>Affected Methods:
///<para/><see cref="ShellCmd(string, int)"/>, <see cref="ShellCmd(string, CancellationToken, int)"/>, <see cref="ShellCmd(string, ShellDataEventHandler, int)"/>, <see cref="ShellCmd(string, ShellDataEventHandler, CancellationToken, int)"/>
///<para/><see cref="ShellCmdHRes(string, int)"/>, <see cref="ShellCmdHRes(string, CancellationToken, int)"/>, <see cref="ShellCmdHRes(string, ShellDataEventHandler, int)"/>, <see cref="ShellCmdHRes(string, ShellDataEventHandler, CancellationToken, int)"/>
///</summary>
public bool WA_SingleArgument
(A) A fix for unresponsive interactive shells. This happened to me on Lineage on my HTC Sensation, where the device sends an "resize" request... Sending a command in this state caused the command getting cut at the 1st byte, for example, u send "id -u" the delivered command was "d -u".
(A) Added "feature" detection for Binary.ADB, now u can get the "features" of the device like: cmd, stat, stat_v2, shell, shell_v2, etc. in the "IChannel.Features".
(R) Removed the last bit of code duplication and optimized some internal logic's. For example, the "Socket.IChannel" got a speed boost from ~1.920.000 bytes during an transfer of 14.400.000 bytes.
06.03.2019 [0.0.5.1]
(C) ADB.Device structure (see 1st post)
(R) ADB.Device.Provider (Decreased the loading time of the contacts and their data)
(D) AAPT completely
Older Changes:
16.02.2019 [0.0.4.2]
(A) DNS lookup for ADB.Socket
(R) Reduced code duplication
07.02.2019 [0.0.4.1]
(F) An issue inside the ADB.Binary, the problem was that "ADB.Devices()" returned nothing, if more than one device was connected. Reason for the issue was the "(int)IChannel.ReadHexLength()" function, there i read an Int16 but it was an UInt16 which caused an overflow.
29.01.2019 [0.0.4.0]
(U) AAPT, ADB, Fastboot binaries and the required dlls to the latest version (1.0.40)
(A) ADB.ADBridge - Unified access to ADB.Binary and ADB.Socket
(A) ADB.IADB - Interface for ADB-/Socket with nearly all ADB commands
(A) ADB.IChannel - Interface of an ADB-/Socket RAW-data channel
(A) ADB.IFramebuffer - Interface for the ADB-/Socket framebuffer
(A) ADB.IShell - Interface for the ADB-/Socket Shell v1 & v2
(A) IMonitor - Interface for the ADB-/Socket and Fastboot device-monitor
(A) On-the-fly device to device copy (ADB.Binary <-> ADB.Binary | ADB.Binary <-> ADB.Socket | ADB.Socket <-> ADB.Socket)
Reordered the ADB namespace... The old layout was:
ADB - Binary based ADB
ADB.Device - Device helper
ADBSocket - Socket based ADB
The new layout is:
ADB - Main ADB
ADB.Binary - Binary based ADB
ADB.Device - Device helper
ADB.Shared - Shared helper, extensions for ADB.Binary and ADB.Socket
ADB.Socket - Socket based ADB
Implemented the framebuffer for ADB.Binary and ADB.Socket (A ready-to-go Remote-Desktop is available via my AndroidCtrlUI.dll)
09.04.2018 [0.0.3.1]
This is a complete new version!
-
I added a lot of new stuff like the "CancellationToken" overload, the "MediaScanner" class and also some fine tunes to the "Screen" class, there u can now also get the Screen dimensions. Also a lot models like the old MemDumpxxx_4xx have been removed (we are now 4 versions higher and the outputs are not longer available or have changed to much).
15.02.2018 [0.0.2.5]
(F) A problem where a NULL exception was raised during directory parsing
(F) A few UI freezes and applied a few tweaks to some logic's.
(D) Tools.Icons {}
(D) Tools.TrayNotify {}
Reason for this is the upcoming compatibility to .NET Core. BUT, the functions are not lost, i added those not .NET Core compatible calls to the AndroidCtrlUI.dll... Because the UI dll will be never migrated to .NET Core.
03.11.2017 [0.0.2.4]
Nearly full new build
-
Sadly my notes are lost, based on a data loss on my Dev Environment...

Showcase
ADB-Overlay made by me
The XDA-Thread and Download can be found here
P10 Lite Toolkit made by me
The XDA-Thread and Download can be found here
P9 Lite Toolkit made by me
The XDA-Thread and Download can be found here
HTC One Toolkit from our Member @squabbi
The XDA-Thread and Download can be found here
--
U use this dll in ur project?
Send me a PM with:
Project Name
Small image
Short description
Download link
then i'll link it here.

An interesting library, time to change Droid Manager code base to use this one ^__^
Thanks for your hard work :highfive:

Could you put an example of how to use the adb and fastboot commands?
such as adb reboot
and fastboot reboot

squabbi said:
Could you put an example of how to use the adb and fastboot commands?
such as adb reboot
and fastboot reboot
Click to expand...
Click to collapse
Yup i'll do it right now
#EDIT:
Added:
Start/Stop ADB/Fastboot
Check if ADB/Fastboot is running
Device Reboot ADB/Fastboot
Sending KeyEvents ADB

Hey another question. How would I use for example:
Code:
Fastboot.Instance().OEM.ReadCid();
I would presume there would need to be a 'string' for it to save to.
Code:
private string _cid
??
EDIT: So i deciced to try this:
Code:
MessageBox.Show("cid: " + Fastboot.Instance().OEM.ReadCid());
When I press the button it shows:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks!

squabbi said:
Hey another question. How would I use for example:
Code:
Fastboot.Instance().OEM.ReadCid();
I would presume there would need to be a 'string' for it to save to.
Code:
private string _cid
??
EDIT: So i deciced to try this:
Code:
MessageBox.Show("cid: " + Fastboot.Instance().OEM.ReadCid());
When I press the button it shows:
Thanks!
Click to expand...
Click to collapse
Hey there
Methods/functions like "ReadCid()" returns a "List<string>" so u can do like:
Code:
string cid = string.Join(" ", Fastboot.Instance().OEM.ReadCid().ToArray());
// or
// The return are 3 lines, so we need to get the 2cnd
string cid = Fastboot.Instance().OEM.ReadCid()[1];
NOTE
I return there a "List<string> (the raw output)" coz i dun know if the output will be the same on each device.
In this case u have filter the right line ur self
Hope this helps

k1ll3r8e said:
Hey there
Methods/functions like "ReadCid()" returns a "List<string>" so u can do like:
Code:
string cid = string.Join(" ", Fastboot.Instance().OEM.ReadCid().ToArray());
// or
// The return are 3 lines, so we need to get the 2cnd
string cid = Fastboot.Instance().OEM.ReadCid()[1];
NOTE
I return there a "List<string> (the raw output)" coz i dun know if the output will be the same on each device.
In this case u have filter the right line ur self
Hope this helps
Click to expand...
Click to collapse
Thanks again!
It worked perfectly! Another question. I'm now using a textbox to show the output like this:
Code:
MainWindow mainWin = (MainWindow)App.Current.MainWindow;
mainWin.tBOutput.AppendText(String.Join("", "\n", Fastboot.Instance().OEM.ReadCid()[1]));
mainWin.tBOutput.ScrollToEnd();
How can I do this but in a seperate window? Like one that is seperate from the MainWindow.
Thanks! :good:

squabbi said:
Thanks again!
It worked perfectly! Another question. I'm now using a textbox to show the output like this:
Code:
MainWindow mainWin = (MainWindow)App.Current.MainWindow;
mainWin.tBOutput.AppendText(String.Join("", "\n", Fastboot.Instance().OEM.ReadCid()[1]));
mainWin.tBOutput.ScrollToEnd();
How can I do this but in a seperate window? Like one that is seperate from the MainWindow.
Thanks! :good:
Click to expand...
Click to collapse
Hey there
There are 3 and more options how u can handle this...
1. Simple "MessageBox"
Code:
MessageBox.Show(string.Join("\n", Fastboot.Instance().OEM.ReadCid().ToArray()));
2. Extra Window
XAML
Code:
<Window x:Class="Multi_Explorer.viewmodel.android.fastboottools.htc.CidDialog"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
Title="Show CID" Height="410" Width="300" ResizeMode="NoResize" WindowStartupLocation="CenterScreen">
<Grid>
<RichTextBox x:Name="TokenOutput" IsReadOnly="True" ScrollViewer.VerticalScrollBarVisibility="Auto">
<RichTextBox.Resources>
<Style TargetType="{x:Type Paragraph}">
<Setter Property="Margin" Value="0,0,0,0"/>
</Style>
</RichTextBox.Resources>
<FlowDocument>
</FlowDocument>
</RichTextBox>
</Grid>
</Window>
CS
Code:
using System;
using System.Collections.Generic;
using System.Windows;
using System.Windows.Documents;
namespace Multi_Explorer.viewmodel.android.fastboottools.htc
{
/// <summary>
/// Interaktionslogik für CidDialog.xaml
/// </summary>
public partial class CidDialog : Window
{
#region Instance
private static CidDialog _instance = null;
public static CidDialog Instance
{
get
{
if (_instance != null)
{
return _instance;
}
else
{
_instance = new CidDialog();
return _instance;
}
}
}
#endregion
public CidDialog()
{
InitializeComponent();
this.Closing += WindowClosing;
App.Current.ShutdownMode = ShutdownMode.OnMainWindowClose;
}
#region WindowClosing
///<summary>
/// Clean exit
///</summary>
private void WindowClosing(object sender, System.ComponentModel.CancelEventArgs e)
{
_instance = null;
}
#endregion
#region Add
public void Add(List<string> msg)
{
foreach (string tmp in msg)
{
TokenOutput.Document.Blocks.Add(new Paragraph(new Run(tmp)));
}
TokenOutput.ScrollToEnd();
}
#endregion
#region Clear
public void Clear()
{
TokenOutput.Document.Blocks.Clear();
}
#endregion
}
}
Usage
Code:
CidDialog ciddiag = CidDialog.Instance;
ciddiag.Add(Fastboot.Instance().OEM.ReadCid());
// As window
ciddiag.Show();
// As dialog window (this will freeze the complete application until it's closed)
ciddiag.ShowDialog();
3. Extra Window with ADB/Fastboot instance
XAML
Code:
<Window x:Class="Multi_Explorer.viewmodel.android.fastboottools.htc.CidDialog"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
Title="Show CID" Height="410" Width="300" ResizeMode="NoResize" WindowStartupLocation="CenterScreen">
<Grid>
<RichTextBox x:Name="TokenOutput" IsReadOnly="True" ScrollViewer.VerticalScrollBarVisibility="Auto">
<RichTextBox.Resources>
<Style TargetType="{x:Type Paragraph}">
<Setter Property="Margin" Value="0,0,0,0"/>
</Style>
</RichTextBox.Resources>
<FlowDocument>
</FlowDocument>
</RichTextBox>
</Grid>
</Window>
CS
Code:
using System;
using System.Collections.Generic;
using System.Windows;
using System.Windows.Documents;
using AndroidCtrl;
using AndroidCtrl.ADB;
using AndroidCtrl.Tools;
using AndroidCtrl.Fastboot;
namespace Multi_Explorer.viewmodel.android.fastboottools.htc
{
/// <summary>
/// Interaktionslogik für CidDialog.xaml
/// </summary>
public partial class CidDialog : Window
{
public CidDialog()
{
InitializeComponent();
this.Closing += WindowClosing;
App.Current.ShutdownMode = ShutdownMode.OnMainWindowClose;
// If u have a selected device this will work in all sub-windows
Add(Fastboot.Instance().OEM.ReadCid());
}
#region WindowClosing
///<summary>
/// Clean exit
///</summary>
private void WindowClosing(object sender, System.ComponentModel.CancelEventArgs e)
{
_instance = null;
}
#endregion
#region Add
public void Add(List<string> msg)
{
foreach (string tmp in msg)
{
TokenOutput.Document.Blocks.Add(new Paragraph(new Run(tmp)));
}
TokenOutput.ScrollToEnd();
}
#endregion
#region Clear
public void Clear()
{
TokenOutput.Document.Blocks.Clear();
}
#endregion
}
}
Usage
Code:
CidDialog ciddiag = CidDialog.Instance;
// Optional
// ciddiag.Add(Fastboot.Instance().OEM.ReadCid());
// As window
ciddiag.Show();
// As dialog window (this will freeze the complete application until it's closed)
ciddiag.ShowDialog();

k1ll3r8e said:
Hey there
There are 3 and more options how u can handle this...
Click to expand...
Click to collapse
Thanks for clarifying! What if i want to get the identifier code? it has multiple strings? how can i choose to show all of them?
EDIT: (More questions! )
Is it possible to use:
Code:
foreach (DataModelDevicesItem device in adbDevices)
{
App.Current.Dispatcher.Invoke((Action)delegate
{
// here goes the add command ;)
deviceselector.Items.Add(device);
});
}
foreach (DataModelDevicesItem device in fastbootDevices)
{
App.Current.Dispatcher.Invoke((Action)delegate
{
deviceselector.Items.Add(device);
});
}
to check if the device is in fastboot or adb? e.g
I press a button to flash recovery. i can have my phone in adb or fastboot and it will check to see which it is in. Then it wil lcarry out a specific command?

Hey there
squabbi said:
Thanks for clarifying! What if i want to get the identifier code? it has multiple strings? how can i choose to show all of them?
Click to expand...
Click to collapse
If u mean the HTC-Bootloader unlock code, u can use the described 2 or 3.
(Both window examples have an "foreach loop" to print out each line from the List<string> into the RichTextBox)
If u want also replace the "(bootloader) " tag u can use this line:
Code:
TokenOutput.Document.Blocks.Add(new Paragraph(new Run(tmp.Replace("(bootloader) ", ""))));
just replace it in the CS code with the one in the "foreach loop".
squabbi said:
EDIT: (More questions! )
Is it possible to use:
Code:
foreach (DataModelDevicesItem device in adbDevices)
{
App.Current.Dispatcher.Invoke((Action)delegate
{
// here goes the add command ;)
deviceselector.Items.Add(device);
});
}
foreach (DataModelDevicesItem device in fastbootDevices)
{
App.Current.Dispatcher.Invoke((Action)delegate
{
deviceselector.Items.Add(device);
});
}
to check if the device is in fastboot or adb? e.g
Click to expand...
Click to collapse
Yes, so i do it in my projects also.
squabbi said:
I press a button to flash recovery. i can have my phone in adb or fastboot and it will check to see which it is in. Then it wil lcarry out a specific command?
Click to expand...
Click to collapse
For this scenario, u need a function which checks which state have the current device serial. After u have the state ADB or Fastboot, u can call 2 different methods from my dll:
ADB
Code:
// This requires Root in any case!
ADB.Instance().Device.FlashImage(IDDevicePartition partition, string localPath, bool tmpToSD = true, int timeOut = -1);
Fastboot
Code:
Fastboot.Instance().Flash(IDDevicePartition partition, string file, int timeOut = -1);
NOTE
I will build a function which will do the work in the future, next release will include it.
#EDIT:
Release it out
Code:
AndroidCtrl.Tools.General.CheckDeviceState(string deviceID);
// return is a IDDeviceState
Hope this helps

k1ll3r8e said:
Hey there
If u mean the HTC-Bootloader unlock code, u can use the described 2 or 3.
(Both window examples have an "foreach loop" to print out each line from the List<string> into the RichTextBox)
If u want also replace the "(bootloader) " tag u can use this line:
Code:
TokenOutput.Document.Blocks.Add(new Paragraph(new Run(tmp.Replace("(bootloader) ", ""))));
just replace it in the CS code with the one in the "foreach loop".
Yes, so i do it in my projects also.
For this scenario, u need a function which checks which state have the current device serial. After u have the state ADB or Fastboot, u can call 2 different methods from my dll:
ADB
Code:
// This requires Root in any case!
ADB.Instance().Device.FlashImage(IDDevicePartition partition, string localPath, bool tmpToSD = true, int timeOut = -1);
Fastboot
Code:
Fastboot.Instance().Flash(IDDevicePartition partition, string file, int timeOut = -1);
NOTE
I will build a function which will do the work in the future, next release will include it.
#EDIT:
Release it out
Code:
AndroidCtrl.Tools.General.CheckDeviceState(string deviceID);
// return is a IDDeviceState
Hope this helps
Click to expand...
Click to collapse
Hey there!
Im using this for the output:
Code:
IDDeviceState state = General.CheckDeviceState(ADB.Instance().DeviceID);
if (state == IDDeviceState.DEVICE)
{
ADB.Instance().Reboot(IDBoot.BOOTLOADER);
CidDialog ciddiag = CidDialog.Instance;
ciddiag.Add(Fastboot.Instance().OEM.GetIdentifierToken());
ciddiag.Show();
}
else if (state == IDDeviceState.FASTBOOT)
{
CidDialog ciddiag = CidDialog.Instance;
ciddiag.Add(Fastboot.Instance().OEM.GetIdentifierToken());
ciddiag.Show();
}
When I first press the button the output window shows. When I close it and press the button again it gives me this error - even if I wait a couple of seconds.
Thanks for your help! :fingers-crossed::good:

squabbi said:
Hey there!
Im using this for the output:
Code:
IDDeviceState state = General.CheckDeviceState(ADB.Instance().DeviceID);
if (state == IDDeviceState.DEVICE)
{
ADB.Instance().Reboot(IDBoot.BOOTLOADER);
CidDialog ciddiag = CidDialog.Instance;
ciddiag.Add(Fastboot.Instance().OEM.GetIdentifierToken());
ciddiag.Show();
}
else if (state == IDDeviceState.FASTBOOT)
{
CidDialog ciddiag = CidDialog.Instance;
ciddiag.Add(Fastboot.Instance().OEM.GetIdentifierToken());
ciddiag.Show();
}
When I first press the button the output window shows. When I close it and press the button again it gives me this error - even if I wait a couple of seconds.
Thanks for your help! :fingers-crossed::good:
Click to expand...
Click to collapse
Hey there
oh yes, that is my fault
U have to add this to ur Window constructor "CidDialog(){}"
Code:
this.Closing += WindowClosing;
And this is the "WindowClosing method"
Code:
#region WindowClosing
///<summary>
/// Clean exit
///</summary>
private void WindowClosing(object sender, System.ComponentModel.CancelEventArgs e)
{
_instance = null;
}
#endregion
Explain
"CidDialog.Instance" create a new instance of the window. But on close the instance will not be set to null. So u can't open it again, coz the system think it's still open.
Hope this helps
#EDIT:
I updated the examples 2 and 3 also.

k1ll3r8e said:
Hey there
oh yes, that is my fault
U have to add this to ur Window constructor "CidDialog(){}"
Code:
this.Closing += WindowClosing;
And this is the "WindowClosing method"
Code:
#region WindowClosing
///<summary>
/// Clean exit
///</summary>
private void WindowClosing(object sender, System.ComponentModel.CancelEventArgs e)
{
_instance = null;
}
#endregion
Explain
"CidDialog.Instance" create a new instance of the window. But on close the instance will not be set to null. So u can't open it again, coz the system think it's still open.
Hope this helps
#EDIT:
I updated the examples 2 and 3 also.
Click to expand...
Click to collapse
Thanks a lot man! Time to put everything in full motion! ?
Sent from my HTC One_M8 using Tapatalk

squabbi said:
Thanks a lot man! Time to put everything in full motion! ?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Np dude
Good Luck!

Hey there! I may be over looking, but where can I use the 'fastboot boot image.img' command?
Thanks!

squabbi said:
Hey there! I may be over looking, but where can I use the 'fastboot boot image.img' command?
Thanks!
Click to expand...
Click to collapse
Hey bro,
I dun implemented it sry... Next build will include it.
Upload starts tonight
Sent from my HTC Sensation using XDA Free mobile app

No Password Identifiers option for WPA3(SAE) in the Wi-Fi manager | Android 11

Hey,
In the latest Wi-Fi encryption standard WPA3(SAE) there is an option for "Password Identifiers" [search for "sae_password_id" in LINK] which is a label that indicates to the AP which password is being used, the required code do exist in the WPA Supplicant in the android tree [Android source code] but the issue that I can't see any option to enter this value when I am connecting to a network with WPA3 enabled using the Wi-Fi Manager[Based on Android 11 on Galaxy Tab s7 tablet].
So my question is where I can find the required field that can be used to fill this value in the Wi-Fi manager ?

[ALL DEVICES] Private DNS broken with Let's Encrypt even on new devices

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