Database Info

Question re: TFlo Config Tool & HTC Cube [HTC TyTN II (Kaiser)]

Hey hey,
As my thread indicates my question is about the FTouchFlo Configuration Tool and the HTC Cube. Please, bear with me while I explain my process of failure.
A few weeks ago, I installed the HTC Cube and it was working great. I happened upon these forums and found the Config. Tool. So, I installed it. It worked great!
Then, I found SCLPC. I uninstalled the HTC Cube, and installed SCLPC. While it is a nice program, I decided it was not for me at this time. So, I uninstalled it and reinstalled HTC Cube and the FTouchFlo Configuration Tool again.
Unfortunately, now the Down-Up gesture is running the application "/Windows/saplaywm.exe" and under Command line parameters: it says, "/Program Files/SCLPF/Version 1-00.swf" which apparently-please correct me if I'm wrong-attempts to call up the SCLPC program.
The Config program and HTC Cube were working together before I tried out SCLPC. Somehow whatever command line in the Config program which called up the HTC Cube is no longer there. So, if I enable the FTouchFlo Configuration Tool, the Down-Up gesture no longer calls up HTC Cube, but that means I won't be able to use the Config program and it's Exclusions list, which is exactly why I installed it.
My question [finally ] is this: Does anyone know the correct command lines that I should input in my Config Tool? Maybe you can find it in your phone and display them for me? Also, does anyone know how to display any parameters available to a program in my phone?
Example:
For those of us that use or used DOS, remember how we used to type a command line like "Copy /?" in DOS and it would show you a screen like:
Copies one or more files to another location.
COPY [/D] [/V] [/N] [/Y | /-Y] [/Z] [/L] [/A | /B ] source [/A | /B]
[+ source [/A | /B] [+ ...]] [destination [/A | /B]]
source Specifies the file or files to be copied.
/A Indicates an ASCII text file.
/B Indicates a binary file.
/D Allow the destination file to be created decrypted
destination Specifies the directory and/or filename for the new file(s).
/V Verifies that new files are written correctly.
/N Uses short filename, if available, when copying a file with a
non-8dot3 name.
/Y Suppresses prompting to confirm you want to overwrite an
existing destination file.
/-Y Causes prompting to confirm you want to overwrite an
existing destination file.
/Z Copies networked files in restartable mode.
/L If the source is a symbolic link, copy the link to the target
instead of the actual file the source link points to.
Thanks ahead of time guys for your help!

INADYN for Android

This is simple cross compile of INADYN 1.96.2 for Android.
"INADYN is a free DynDNS client. It gives the possibility to have your own fixed hostname registered on the internet, although your IP might be changing. It checks periodically whether the IP address stored by the DNS server is the real current IP address of the machine that is running INADYN."
http://www.inatech.eu/inadyn/
To install:
1) extract inadyn.zip to your sdcard
2) copy inadyn to /system/bin
You have two ways to run it:
1) from the shell, run: inadyn --username <DynDNS username> --password <DynDNS password> --alias <DynDNS alias>
e.g. inadyn -u test -t test -a test.thruhere.net
2) create inadyn.conf in /etc with the following contents: "--username <DynDNS username> --password <DynDNS password> --alias <DynDNS alias>" then run inadyn
You may want to use the following commands
--iterations 1 (this will cause inadyn to update the ip and exit)
--background (inadyn will run in the background)
--update_period 6000 (how often the IP is checked. The period is in [ms]. Default is about 1 min. Max is 10 days)

Reserved for build instructions
Reserved for build instructions

Reserved for inadyn-mt
Reserved for inadyn-mt

Good, thank you for sharing.
Work fine on milestone, motofrenzy (froyo whit kernel eclair).

Is there any chance you would add support for zone edit?
Sent from my ADR6300 using XDA App

error
followed instructions but no joy; keep getting:
[1] Illegal instruction
Running Froyo on LG Optimus S. Any ideas?

I have not installed this, but I would like to know the answer to this question before I do:
Is this supposed to work over cellular/3G? Or is it just wifi?

Does this work on all phones ? anybody get this to connect on tmobile?

i get error too
daflores63 said:
followed instructions but no joy; keep getting:
[1] Illegal instruction
Running Froyo on LG Optimus S. Any ideas?
Click to expand...
Click to collapse
I have the same problem running Gingerbread on HTC Wildfire S
'pidof inadyn' repeats the error message
'pidof inadyn' again returns no result

[Method] Automate the Theater Mode

******************************
A late note:
below contents were written in May2015, after some days I paid my attention to other things (now Oct2015).
If you are new to read, and really interested to achieve this, you may also read the following comments, which may contain some new thoughts/ better methods.
Currently my new watch system is not rooted and am not so hungry on battery. But I promise I will be back to tidy through when I got spare time.
Thanks again for reading.
******************************
I got a way to automate the "Theater mode" of my watch.
I would like my wear to auto switch to "Theater mode" at night and exit every morning to save battery. (Just too lazy to remember to switch it when sleeping ). The real problems are ①google doesn't provide an API for developers ②currently no good method to execute native standalone command on watch.
My basic idea is to simulate a double tap on power button using shell. This would not be that difficult like ②..
Seems current apps don't provide such function: like autowear, weartasker,tasker for wear.... none of them provide a function of executing command on watch.
Then I used thread of gusano38 to apply a debugging of wear from phone (pretend as a PC).
Besides, there is another thread of joschi70 on wearshell, I don't know much about bean shell, so no idea whether it can modify wear setting rather than just retrieving info.
Here are the detailed steps:
Your phones should be rooted.
A. One time record
1. debug your watch (turn on in watch developer opition)
2. use "getevent" to find "bcmpmu_on" related event, in my case, event2
3. run command "cat /dev/input/event2 > /sdcard/doubletap", double tap your power button, then use control-C to stop the command
4. There should be a "doubletap” located in you watch /sdcard
use "cat /sdcard/doubletap > /dev/input/event2" to run and test if it is working
B. After you finish step A, you can always use the following code to trigger current Theater mode
allow bluetooth debugging
Code:
[COLOR="gray"]su
adb kill-server
export HOME=/sdcard
setprop service.adb.tcp.port 5555
stop adbd
start adbd
adb forward tcp:4444 localabstract:/adb-hub
adb connect localhost:4444
sleep 2
adb -s localhost:4444 shell "input keyevent 26; cat /sdcard/doubletap > /dev/input/event2"
setprop service.adb.tcp.port -1
stop adbd
start adbd
adb kill-server
exit[/COLOR]
Also recorded a short demo video
Note: NOT recommended for daily use, maybe you prefer a simple hardware tap, but here debugging mode may make your wear unsafe (therefore this is permanent notification)
=========================================================
It has been some time since my above post, I tried beanshell and finally solved my own problem.
The disadvantage of debug is unsafe, permanent notification, and delay(e.g. my above codes need wait 2s for adb service to be ready). No one if use wearshell.
main code
Code:
import java.lang.Runtime;
import java.io.DataOutputStream;
Process su = Runtime.getRuntime().exec("su");
DataOutputStream outputStream = new DataOutputStream(su.getOutputStream());
outputStream.writeBytes("input keyevent 26;cat /sdcard/doubletap>/dev/input/event2;");
outputStream.flush();
outputStream.writeBytes("exit\n");
outputStream.flush();
su.waitFor();
How:
Step B:
1. install wearshell
2. Prepare above main code, you can either
save to a file (e.g. doubletap.bsh) in /sdcard of watch, and call the through source("/sdcard/doubletap.bsh")
or
directly run (sometimes need to combine into one line like intent)
3. use intent to call: de.fun2code.android.wear.shell.EXEC with extra "bsh".
Now you are free to use it daily!
{
"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"
}
============================================================
This is a third update: I grayed the ADB part of first post for not confusing. This time I show how I used it.
Basically I make my watch into Theater mode and turn off Bluetooth of my phone at night. In the morning do the opposite things:
Just skip the run shell step which kills "bluetooh share" app (my phone has some problem with BT).
This is just one part pf my day/night switch tasks e.g. I also have auto airplane mode and interruption mode. By the way, I don't use airplane mode to turn off bluetooth. Simply because I want my watch to connect a little longer. To do that, you can set "airplane radios" so that you decide whether or not to turn off wifi/bluetooth/etc when you go to airplane mode.
This should save battery a little if not too much. Your decision if it helps you.
my one day sample:

I was searching a solution for this.. However this is still not a daily solution! However this puts a few steps closer at least. Thanks
Sent from my SM-G920F using Tapatalk

I have updated. wearshell worth to try.

qingtest said:
I have updated. wearshell worth to try.
Click to expand...
Click to collapse
This project looks great since it would let me automate activating theater mode with Tasker and I haven't found any other ways to do it. If I understand your post correctly, I need to save the code to a file and save on my watch's storage. How do I copy the file there?

I installed the wearshell , then placed the file with the code named doubletap.bsh in watch sdcard folder and created intent in tasker exactly like in the screenshot and nothing.. The intent goes as it should (green dot on tasker) but the watch still the same..
Sent from my SM-G920F using Tapatalk

if you have sony smart watch 3 like me, can simply plug in your usb cable, otherwise I think can use Debugging over Bluetooth.
then use "adb push" to transfer the file.

In tasker the target is Activity/Service, not BroadcastReceiver.
if this does not solve, can you just paste the codes to web shell page (can also insert 'echo xxx;'), see if there is any output or error?
If error maybe it is the root permission, as you can see my sample code needs su.
well I think the key simulation function may not necessarily need root, but I had my watch rooted (my default). You can either root watch or make a little change to the java codes (so that not requiring root permission).

qingtest said:
In tasker the target is Activity/Service, not BroadcastReceiver.
if this does not solve, can you just paste the codes to web shell page (can also insert 'echo xxx;'), see if there is any output or error?
If error maybe it is the root permission, as you can see my sample code needs su.
well I think the key simulation function may not necessarily need root, but I had my watch rooted (my default). You can either root watch or make a little change to the java codes (so that not requiring root permission).
Click to expand...
Click to collapse
I was using target as activity.
The watch wakes up the screen like if o touched it in normal mode, but nothing else.
My watch it is supposed to be rooted.. I get the # when using shell, but when I saw on code that had SU it was my first though that it might not be rooted.
What changes you suggest for the code? I'm a bit dumb on code since I'm a basic self learner...
Sent from my SM-G920F using Tapatalk

It should work. For problem shooting purpose I guest you check shell and beanshell separately.
1. Make sure adb works in the command window.
The first command "input" is to simulate power press, it should 100% work.
The second command "cat" is to simulate double press, if not working you need to redo the recording.
2. Run beanshell with any command like "echo aaa" in the webpage it should 100% work [edit: print("aaa");]
3. Run my code in webpage, should work
4. Put in tasker
Let me know which step you cannot go through.

qingtest said:
It should work. For problem shooting purpose I guest you check shell and beanshell separately.
1. Make sure adb works in the command window.
The first command "input" is to simulate power press, it should 100% work.
The second command "cat" is to simulate double press, if not working you need to redo the recording.
2. Run beanshell with any command like "echo aaa" in the webpage it should 100% work
3. Run my code in webpage, should work
4. Put in tasker
Let me know which step you cannot go through.
Click to expand...
Click to collapse
I'm having problem right on the second command... using "adb shell cat /sdcard/doubletap>/dev/input/event2" returns in command prompt "The system cannot find the path specified"... however I have triple checked and I have the file doubletap.bsh in the SDCARD folder....

I pushed the doubletap.bsh file to /sdcard and it's not working for me. Running a task with the intent doesn't do anything despite showing the green dot. My watch isn't rooted so I'm sure that's a factor. When I run the code on the web interface this is the error I get
BeanShell: error code bsh.TargetError: Sourced file: inline evaluation of: ``import java.lang.Runtime; import java.io.DataOutputStream; Process su = Runtime. . . . '' : Typed variable declaration : Method Invocation exec : at Line: 3 : in file: inline evaluation of: ``import java.lang.Runtime; import java.io.DataOutputStream; Process su = Runtime. . . . '' : .exec ( "su" )
Target exception: java.io.IOException: Error running exec(). Command: [su] Working Directory: null Environment: null
Click to expand...
Click to collapse
I tried removing what I thought was calling on su permissions but couldn't get it to work, but it may just be poor syntax. Do you know what the code would be if it's not using su?
Edit:
I can't even get the echo beanshell command to run. When I enter 'echo aaa' in the webpage I get the following:
BeanShell: error code bsh.EvalError: Sourced file: inline evaluation of: ``echo aaa ;'' : Typed variable declaration : Class: echo not found in namespace : at Line: 1 : in file: inline evaluation of: ``echo aaa ;'' : echo
Click to expand...
Click to collapse

there are two files 1. doubletap 2. doubletap.bsh.
The first one includes is generated following my step A, did you check it?

sorry "echo" is only for bash.. if you are running beanshell it should be print("aaa"); which work 100%

qingtest said:
there are two files 1. doubletap 2. doubletap.bsh.
The first one includes is generated following my step A, did you check it?
Click to expand...
Click to collapse
Thanks but I'm still overlooking something.
A. One time record
1. debug your watch (turn on in watch developer opition)
2. use "getevent" to find "bcmpmu_on" related event, in my case, event2
3. run command "cat /dev/input/event2 > /sdcard/doubletap", double tap your power button, then use control-C to stop the command
4. There should be a "doubletap” located in you watch /sdcard
use "cat /sdcard/doubletap > /dev/input/event2" to run and test if it is working
Click to expand...
Click to collapse
I need to do the above first even if I'm not using the run shell command, correct? I have my watch set to ADB debugging on, but where am I entering the commands? I'm sure I'm just not understanding what to do.

qingtest said:
A. One time record
1. debug your watch (turn on in watch developer opition)
2. use "getevent" to find "bcmpmu_on" related event, in my case, event2
3. run command "cat /dev/input/event2 > /sdcard/doubletap", double tap your power button, then use control-C to stop the command
4. There should be a "doubletap” located in you watch /sdcard
use "cat /sdcard/doubletap > /dev/input/event2" to run and test if it is working
Click to expand...
Click to collapse
I assumed we could do B without A, so I guess this was the mistake.
Still I'm lacking some knowleage to where we do this and how..
Where we go for one time record and where we run all this steps? ADB to use the "getevent" and the command?
If you could ptovide some more baby steps would be helpfull! thanks
EDITk, I guess I figured it out partially
WIth command prompt and watch screen ON run "adb shell getevent" and while running double press the button (to induce theater mode).
In my phone it showed up like this in the command prompt when I double pressed the button:
I don't get the "bcmpmu_on" on any event but rater "gpnp_pon"
could not open /dev/input/event0, Out of memory
add device 1: /dev/input/event10
name: "ssp_context"
add device 2: /dev/input/event9
name: "tilt_wake_sensor"
add device 3: /dev/input/event8
name: "hrm_lib_sensor"
add device 4: /dev/input/event7
name: "meta_event"
add device 5: /dev/input/event6
name: "step_cnt_sensor"
add device 6: /dev/input/event5
name: "uncal_gyro_sensor"
add device 7: /dev/input/event4
name: "sig_motion_sensor"
add device 8: /dev/input/event3
name: "uncal_geomagnetic_sensor"
add device 9: /dev/input/event2
name: "geomagnetic_sensor"
add device 10: /dev/input/event1
name: "qpnp_pon"
/dev/input/event1: 0001 0074 00000001
/dev/input/event1: 0000 0000 00000000
/dev/input/event1: 0001 0074 00000000
/dev/input/event1: 0000 0000 00000000
/dev/input/event1: 0001 0074 00000001
/dev/input/event1: 0000 0000 00000000
/dev/input/event1: 0001 0074 00000000
/dev/input/event1: 0000 0000 00000000
NOw it's here I'm kind of stuck.. now Im trying to use in the command prompt :
adb shell sendevent cat /dev/input/event1 > /sdcard/doubletap
I event tried
adb shell su sendevent cat /dev/input/event1 > /sdcard/doubletap
and it's returning
"The system cannot find the specified path"
what I'm I missing?

insaned said:
I assumed we could do B without A, so I guess this was the mistake.
Still I'm lacking some knowleage to where we do this and how..
Where we go for one time record and where we run all this steps? ADB to use the "getevent" and the command?
If you could ptovide some more baby steps would be helpfull! thanks
EDITk, I guess I figured it out partially
WIth command prompt and watch screen ON run "adb shell getevent" and while running double press the button (to induce theater mode).
In my phone it showed up like this in the command prompt when I double pressed the button:
I don't get the "bcmpmu_on" on any event but rater "gpnp_pon"
could not open /dev/input/event0, Out of memory
add device 1: /dev/input/event10
name: "ssp_context"
add device 2: /dev/input/event9
name: "tilt_wake_sensor"
add device 3: /dev/input/event8
name: "hrm_lib_sensor"
add device 4: /dev/input/event7
name: "meta_event"
add device 5: /dev/input/event6
name: "step_cnt_sensor"
add device 6: /dev/input/event5
name: "uncal_gyro_sensor"
add device 7: /dev/input/event4
name: "sig_motion_sensor"
add device 8: /dev/input/event3
name: "uncal_geomagnetic_sensor"
add device 9: /dev/input/event2
name: "geomagnetic_sensor"
add device 10: /dev/input/event1
name: "qpnp_pon"
/dev/input/event1: 0001 0074 00000001
/dev/input/event1: 0000 0000 00000000
/dev/input/event1: 0001 0074 00000000
/dev/input/event1: 0000 0000 00000000
/dev/input/event1: 0001 0074 00000001
/dev/input/event1: 0000 0000 00000000
/dev/input/event1: 0001 0074 00000000
/dev/input/event1: 0000 0000 00000000
NOw it's here I'm kind of stuck.. now Im trying to use in the command prompt :
adb shell sendevent cat /dev/input/event1 > /sdcard/doubletap
I event tried
adb shell su sendevent cat /dev/input/event1 > /sdcard/doubletap
and it's returning
"The system cannot find the specified path"
what I'm I missing?
Click to expand...
Click to collapse
I'm stuck at the same place you are. When I run "adb shell getevent" from the command prompt I get results that show "gpnp_pon" for event1 and there's no "bcmpmu_on". So I've tried "adb shell sendevent cat /dev/input/event1 > /sdcard/doubletap" and "adb cat /dev/input/event1 > /sdcard/doubletap" and both give me the same error, "The system cannot find the path specified."

Hi I hoped to make it clear but was too lazy to wrote every detail where I assume readers were familiar with adb.
This is the answer for you two:
①You should know the basic idea is to simulate keypress.
The "input keyevent" does not have the ability to simulate a double tap, that's why we need to use adb to record.
The recorded data is put in the file "doubletap"
②From your question, I guess you are not so familiar with cmd right?
If you run "adb cat /dev/input/event1 > /sdcard/doubletap" in dos cmd, it will actually only run the command "cat /dev/input/event1 " and retrieve the result then write to a file "/sdcard/double" in windows. However, windows does not have such a path, that's why error is reported.
③ sorry I only have played with my own watch, I think the one ‘**on’ should be equivalent to my 'bcmpmu_on'.
④ To do it right, you need to quote the command like this: adb shell "cat /dev/input/event1 > /sdcard/doubletap"
Or first go into adb shell ,then run the command (like below picture)
↑After double press, press Ctrl+C to stop. Then adb will exit with "^C"
The file should already in /sdcard/, can check like below: (in your case doubletap)
Now you can simply run below command to test. should toggle theater mode 100%: (in your case doubletap)

qingtest said:
Hi I hoped to make it clear but was too lazy to wrote every detail where I assume readers were familiar with adb.
This is the answer for you two:
①You should know the basic idea is to simulate keypress.
The "input keyevent" does not have the ability to simulate a double tap, that's why we need to use adb to record.
The recorded data is put in the file "doubletap"
②From your question, I guess you are not so familiar with cmd right?
If you run "adb cat /dev/input/event1 > /sdcard/doubletap" in dos cmd, it will actually only run the command "cat /dev/input/event1 " and retrieve the result then write to a file "/sdcard/double" in windows. However, windows does not have such a path, that's why error is reported.
③ sorry I only have played with my own watch, I think the one ‘**on’ should be equivalent to my 'bcmpmu_on'.
④ To do it right, you need to quote the command like this: adb shell "cat /dev/input/event1 > /sdcard/doubletap"
Or first go into adb shell ,then run the command (like below picture)
↑After double press, press Ctrl+C to stop. Then adb will exit with "^C"
The file should already in /sdcard/, can check like below: (in your case doubletap)
Now you can simply run below command to test. should toggle theater mode 100%: (in your case doubletap)
Click to expand...
Click to collapse
I'm familiar with command prompt and know the basics with adb. I guess it was confusing that some of the steps were very detailed so I could do exactly what you wrote, but some steps were missing things and I didn't realize it. Thank you for your patience.
After doing what was in your last post I'm able to toggle theater mode from adb on my laptop while my laptop is connected, so that's great. However doing it from the Wearshell intent still doesn't work. I copied the code you posted and changed event2 to event1, but I'm pretty sure the problem is that your code uses su and my watch is not rooted. Do you know what the code would look like without using root?
This is the error I got from Wearshell
BeanShell: error code bsh.TargetError: Sourced file: inline evaluation of: ``import java.lang.Runtime; import java.io.DataOutputStream; Process su = Runtime. . . . '' : Typed variable declaration : Method Invocation exec : at Line: 3 : in file: inline evaluation of: ``import java.lang.Runtime; import java.io.DataOutputStream; Process su = Runtime. . . . '' : .exec ( "su" )
Target exception: java.io.IOException: Error running exec(). Command: [su] Working Directory: null Environment: null
Click to expand...
Click to collapse

I just updated my watch to 5.1.1, so lost root. The code is no longer working for me either. I confirm the input and cat do not necessarily need su permission.
However, I don't have an existing code for you ( i am relative new in beanshell too). Will try and share with my spare time (you are welcome to do so too )

Thanks a million for the patience to the detailed adb explanation which helped a lot!
Already working both in Adb, Wearshell and tasker intent. I have the Watch rooted..
However I DID a slight change to the code, I had to remove the " input keyevent 26" from the line, because it was causing only the screen to turn on and without it works great. The double tap on the button for theater mode doesn't need screen on anyway, so I gave it a shot to remove and it worked.
import java.lang.Runtime;
import java.io.DataOutputStream;
Process su = Runtime.getRuntime().exec("su");
DataOutputStream outputStream = new DataOutputStream(su.getOutputStream());
outputStream.writeBytes("cat /sdcard/doubletap>/dev/input/event1;");
outputStream.flush();
outputStream.writeBytes("exit\n");
outputStream.flush();
su.waitFor();
Click to expand...
Click to collapse

Android M with WPA-Enterprise ssl problem

I just upgrade my nexus to marshmallow and have a trouble to connecting my device to my collage wifi. It tell me that there are authentication problem on wifi setting. I try to catch some log from logcat and get this message:
wwpa_supplicant: OpenSSL: openssl_handshake - SSL_connect error:100c1069:SSL routines:ssl3_get_server_key_exchange:BAD_DH_P_LENGTHpa_supplicant: OpenSSL: openssl_handshake - SSL_connect error:100c1069:SSL routines:ssl3_get_server_key_exchange:BAD_DH_P_LENGTH
Who have the same problem withe, any solution to fix these?
Thank you.

I have same problem here, My university uses eduroam, which is wpa enterprise. and I can not connect to wifi after 6.0 upgrade. There must be some problem with wpa_supplicant had same problem with my Linux laptop and fixed the problem after downgrading the wpa_supplicant
Code:
[ 10-14 09:39:43.666 17159:17159 I/wpa_supplicant ]
wlan0: Trying to associate with 20:bb:c0:f8:e4:75 (SSID='eduroam' freq=2412 MHz)
[ 10-14 09:39:43.834 17159:17159 I/wpa_supplicant ]
wlan0: Associated with 20:bb:c0:f8:e4:75
[ 10-14 09:39:43.834 17159:17159 I/wpa_supplicant ]
wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
[ 10-14 09:39:43.841 17159:17159 I/wpa_supplicant ]
wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25
[ 10-14 09:39:43.842 17159:17159 I/wpa_supplicant ]
wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
[ 10-14 09:39:43.872 17159:17159 I/wpa_supplicant ]
wlan0: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External CA Root' hash=687fa451382278fff0c8b11f8d43d576671c6eb2bceab413fb83d965d06d2ff2
[ 10-14 09:39:43.873 17159:17159 I/wpa_supplicant ]
wlan0: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External CA Root' hash=687fa451382278fff0c8b11f8d43d576671c6eb2bceab413fb83d965d06d2ff2
[ 10-14 09:39:43.885 17159:17159 I/wpa_supplicant ]
wlan0: CTRL-EVENT-EAP-PEER-CERT depth=1 subject='/C=US/O=Internet2/OU=InCommon/CN=InCommon Server CA' hash=623727ec472644a6bb70d240565c24223fdb0f2f5ac698027e3012489c70e817
[ 10-14 09:39:43.890 17159:17159 I/wpa_supplicant ]
wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/C=US/postalCode=70803/ST=Louisiana/L=Baton Rouge/street=110 Thomas Boyd/O=Louisiana State University/OU=LSU A & M/CN=acs-wlan.lsu.edu' hash=3b1214222f27c029417be13e02a6a422f958d470e88300f81716bc04663ae790
[ 10-14 09:39:43.892 17159:17159 I/wpa_supplicant ]
wlan0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:acs-wlan.lsu.edu
[ 10-14 09:39:43.930 17159:17159 I/wpa_supplicant ]
EAP-MSCHAPV2: Authentication succeeded
[ 10-14 09:39:43.940 17159:17159 I/wpa_supplicant ]
EAP-TLV: TLV Result - Success - EAP-TLV/Phase2 Completed
[ 10-14 09:39:43.950 17159:17159 I/wpa_supplicant ]
wlan0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
[ 10-14 09:40:53.840 17159:17159 I/wpa_supplicant ]
wlan0: Authentication with 20:bb:c0:f8:e4:75 timed out.

Your enterprise needs to update their radius servers and openssl software to fix this issue. A work around, if you are rooted, you can go to \data\misc\wifi\ and edit wpa_supplicant.conf. You need to add this line to your eduroam or wpa-eap network:
phase1="tls_disable_tlsv1_2=1"
Someone has already opened a ticket with Google: https://code.google.com/p/android/issues/detail?id=188867
Here's what my wpa_supplicant.conf looks like and I can connect to eduroam now:
disable_scan_offload=1
update_config=1
device_name=hammerhead
manufacturer=LGE
model_name=Nexus 5
model_number=Nexus 5
serial_number=066450ff0060c4a1
device_type=10-0050F204-5
config_methods=physical_display virtual_push_button
p2p_disabled=1
external_sim=1
wowlan_triggers=any
network={
ssid="eduroam"
key_mgmt=WPA-EAP IEEE8021X
eap=PEAP
identity="[email protected]"
password="mypassword"
phase1="tls_disable_tlsv1_2=1"
priority=14
proactive_key_caching=1
}

it works!!
after countless hours of researching, adding the line onto the wpa_supplicamt.conf works. thanks bro!!
slackhouse said:
Your enterprise needs to update their radius servers and openssl software to fix this issue. A work around, if you are rooted, you can go to \data\misc\wifi\ and edit wpa_supplicant.conf. You need to add this line to your eduroam or wpa-eap network:
phase1="tls_disable_tlsv1_2=1"
Someone has already opened a ticket with Google: https://code.google.com/p/android/issues/detail?id=188867
Here's what my wpa_supplicant.conf looks like and I can connect to eduroam now:
disable_scan_offload=1
update_config=1
device_name=hammerhead
manufacturer=LGE
model_name=Nexus 5
model_number=Nexus 5
serial_number=066450ff0060c4a1
device_type=10-0050F204-5
config_methods=physical_display virtual_push_button
p2p_disabled=1
external_sim=1
wowlan_triggers=any
network={
ssid="eduroam"
key_mgmt=WPA-EAP IEEE8021X
eap=PEAP
identity="[email protected]"
password="mypassword"
phase1="tls_disable_tlsv1_2=1"
priority=14
proactive_key_caching=1
}
Click to expand...
Click to collapse

slackhouse said:
Your enterprise needs to update their radius servers and openssl software to fix this issue. A work around, if you are rooted, you can go to \data\misc\wifi\ and edit wpa_supplicant.conf. You need to add this line to your eduroam or wpa-eap network:
phase1="tls_disable_tlsv1_2=1"
Click to expand...
Click to collapse
Just to confirm that this is working for me too - thanks very much! :good:

al3co said:
Just to confirm that this is working for me too - thanks very much! :good:
Click to expand...
Click to collapse
That didnt seem to work for me. Are you guys doing anything else like clicking the Dev options to use legacy lollipop DHCP? or disabling the google connectivity services? or just simply rebooting?

Nope, nothing else - I just added the line to wpa_supplicant.
I've not rooted my phone, so did it a slightly different way via adb, but I made sure that the permissions (chmod) and group/owner (chown) were both set to the original settings. Have you checked to see if changing that fixes it for you?

how did you do it without rooting your phone
al3co said:
Nope, nothing else - I just added the line to wpa_supplicant.
I've not rooted my phone, so did it a slightly different way via adb, but I made sure that the permissions (chmod) and group/owner (chown) were both set to the original settings. Have you checked to see if changing that fixes it for you?
Click to expand...
Click to collapse

slackhouse said:
Your enterprise needs to update their radius servers and openssl software to fix this issue. A work around, if you are rooted, you can go to \data\misc\wifi\ and edit wpa_supplicant.conf. You need to add this line to your eduroam or wpa-eap network:
phase1="tls_disable_tlsv1_2=1"
}
Click to expand...
Click to collapse
something strange is happening when i try this. once i edited the wpa_supplicant.conf file and tried to connect to my work network a 'wpa_supplicant.conf.tmp' file is created which effectively deletes the added line.
the only difference i can see is that the network requires mschapv2 so my (edited) wpa_supplicant.conf. files reads:
network={
ssid="D Wireless"
key_mgmt=WPA-EAP IEEE8021X
eap=PEAP
identity="####"
password="#####"
phase1="tls_disable_tlsv1_2=1"
phase2="auth=MSCHAPV2"
priority=3
proactive_key_caching=1
disabled=5
Any ideas?

Here's the steps I took, though I am rooted:
1. Disabled WiFi.
2. Edited the wpa_supplicant.conf file via using ES File Explorer.
3. Verified permissions on .conf file were correct using Terminal Emulator.
4. Rebooted phone.
5. Enabled WiFi and connected.
If I enabled WiFi with incorrect permissions or prior to rebooting, the conf file reverted to its original state.

slackhouse said:
Here's the steps I took, though I am rooted:
1. Disabled WiFi.
2. Edited the wpa_supplicant.conf file via using ES File Explorer.
3. Verified permissions on .conf file were correct using Terminal Emulator.
4. Rebooted phone.
5. Enabled WiFi and connected.
If I enabled WiFi with incorrect permissions or prior to rebooting, the conf file reverted to its original state.
Click to expand...
Click to collapse
thanks for such a swift reply.
Any chance you could post the command to use in the terminal to set the permissions (i suspect this is the issue).
at the moment the wpa_supplicant.conf file is showing permissions of:
-rw-rw---- wifi wifi 566
is this correct?
Despite using linux for the last 10 years i'm useless at getting this right!
many thanks

westy123 said:
thanks for such a swift reply.
Any chance you could post the command to use in the terminal to set the permissions (i suspect this is the issue).
at the moment the wpa_supplicant.conf file is showing permissions of:
-rw-rw---- wifi wifi 566
is this correct?
Despite using linux for the last 10 years i'm useless at getting this right!
many thanks
Click to expand...
Click to collapse
i just used "ls -la" to see the permissions. and if the rw, rw, isn't right, you'd use a chmod and if the owner or group wasn't right you'd use a chown. My organization has updated our radius servers, so I don't have to do this anymore. Here's what mine looks like without making any changes to it:"
-rw-r--r-- root root
To change owner:group, you'd do this: "chown root:root wpa_supplicant.conf"
To change permissions, you'd use: "chmod wpa_supplicant.conf 644"
Just make sure you have WiFi disabled, and once you save the file, reboot prior to enabling WiFi.

Wow, that's great, I'll try it first thing tomorrow (as son as I get back to work)
Thanks very much
update: unfortunately i still can't get it to work, despite setting permissions etc. either the file become corrupted and wifi doesn't work, or a new .tmp file is created.
Anyway, the IT people got back to me today, and assured me that they'd be updating the university servers etc. in the very near future, so it shouldn't be an issue for much longer.
But thanks for the help anyway, it's been a useful learning experience.

slackhouse said:
Your enterprise needs to update their radius servers and openssl software to fix this issue. A work around, if you are rooted, you can go to \data\misc\wifi\ and edit wpa_supplicant.conf. You need to add this line to your eduroam or wpa-eap network:
phase1="tls_disable_tlsv1_2=1"
Someone has already opened a ticket with Google: https://code.google.com/p/android/issues/detail?id=188867
Here's what my wpa_supplicant.conf looks like and I can connect to eduroam now:
disable_scan_offload=1
update_config=1
device_name=hammerhead
manufacturer=LGE
model_name=Nexus 5
model_number=Nexus 5
serial_number=066450ff0060c4a1
device_type=10-0050F204-5
config_methods=physical_display virtual_push_button
p2p_disabled=1
external_sim=1
wowlan_triggers=any
network={
ssid="eduroam"
key_mgmt=WPA-EAP IEEE8021X
eap=PEAP
identity="[email protected]"
password="mypassword"
phase1="tls_disable_tlsv1_2=1"
priority=14
proactive_key_caching=1
}
Click to expand...
Click to collapse
Didn't work for me. This issue is making me crazy

slackhouse said:
Here's the steps I took, though I am rooted:
1. Disabled WiFi.
2. Edited the wpa_supplicant.conf file via using ES File Explorer.
3. Verified permissions on .conf file were correct using Terminal Emulator.
4. Rebooted phone.
5. Enabled WiFi and connected.
If I enabled WiFi with incorrect permissions or prior to rebooting, the conf file reverted to its original state.
Click to expand...
Click to collapse
Doesn't work for me. Once rebooted It tries to connect automatically without success and then appears a pop up that wants me to enter the password again

For those still with problems, I found the solution on another website. Apparently the line you must add to the config file is a little bigger, here it is:
phase1="tls_disable_tlsv1_1=1 tls_disable_tlsv1_2=1"
It finally worked for me.

MaKTaiL said:
For those still with problems, I found the solution on another website. Apparently the line you must add to the config file is a little bigger, here it is:
phase1="tls_disable_tlsv1_1=1 tls_disable_tlsv1_2=1"
It finally worked for me.
Click to expand...
Click to collapse
Same issue for me, it made me crazy! finally i solved it... thanks thanks thanks!

doesn't work for me :crying:
Moto G2 xt1068 with cm13.. any work around?

Summary: what worked for me
I have a Motorola Moto E (condor) that I've just updated to LineageOS 14.1 (Nougat). Here's what I had to do, partly for my own reference and hopefully this will help others with the same problem. I couldn't connect to eduroam at my workplace due to a faulty RADIUS server that doesn't handshake correctly with TLS 1.2.
First, install ADB & Fastboot. Make sure USB debugging is enabled on your device, and allow root as ADB (Developer Options > Android debugging, and Root access: ADB only).
With your device plugged in to your PC, open an ADB command prompt on your PC (Start > Minimal ADB and Fastboot). Type:
Code:
adb root
adb pull /data/misc/wifi/wpa_supplicant.conf
This will put the wpa_supplicant.conf file on your computer (on my PC, it's located in "%localappdata%\VirtualStore\Program Files (x86)\Minimal ADB and Fastboot\wpa_supplicant.conf"). Edit it with your favourite text editor (NOT Notepad, as it won't recognise the Linux newline format. I prefer metapad). Find the configuration section for your WiFi network. Mine looks like this:
Code:
network={
ssid="eduroam"
bssid=<deleted>
key_mgmt=WPA-EAP IEEE8021X
eap=PEAP
identity="[email protected]"
password=<deleted>
[B] phase1="tls_disable_tlsv1_2=1"
[/B] ca_cert="keystore://CACERT_stfc"
phase2="auth=MSCHAPV2"
priority=51
proactive_key_caching=1
id_str="%7B%22creatorUid%22%3A%221000%22%2C%22configKey%22%3A%22%5C%22eduroam%5C%22WPA_EAP%22%7D"
}
To disable TLS v2.1 and get the connection working, you'll need to insert the highlighted line. Save the file in the same location.
Now turn off wifi on your device, go back to your ADB shell and type:
Code:
adb push wpa_supplicant.conf /data/misc/wpa_supplicant_new.conf
adb shell
This will open a debug prompt for your device. You're now altering files on your device as root, so be careful! Type
Code:
cd /data/misc/wifi
ls -la
You should see a directory listing, including wpa_supplicant.conf and wpa_supplicant_new.conf:
Code:
-rw-rw---- 1 wifi wifi 5412 2017-03-07 08:30 wpa_supplicant.conf
-rw-rw-rw- 1 root root 5432 2017-03-07 08:18 wpa_supplicant_new.conf
You need to overwrite the old version with the new. First make a copy of the old file:
Code:
cp wpa_supplicant.conf wpa_supplicant_old.conf
Now we need to ensure the new file has the same permissions as the old. Type:
Code:
chmod 660 wpa_supplicant_new.conf
chown wifi wpa_supplicant_new.conf
chgrp wifi wpa_supplicant_new.conf
Now to overwrite the old version:
Code:
rm wpa_supplicant.conf
mv wpa_supplicant_new.conf wpa_supplicant.conf
Type ls -la again to check the permissions are correct. You should see something like:
Code:
-rw-rw---- 1 wifi wifi 5412 2017-03-07 08:30 wpa_supplicant.conf
Finally, exit from the ADB prompt (just type exit), reboot your device, enable wifi, and try to connect again.
I hope that helps!

MaKTaiL said:
For those still with problems, I found the solution on another website. Apparently the line you must add to the config file is a little bigger, here it is:
phase1="tls_disable_tlsv1_1=1 tls_disable_tlsv1_2=1"
It finally worked for me.
Click to expand...
Click to collapse
Am on Lineage 15.1 and want to add it, but under Oreo Android is using WifiConfigStore.xml to store the config. How must the line look like in my case?

[UNBRICK]Fire HD8 2016 (giza)

This guide is only for the Fire HD8 2016 (codenamed giza.)
This will not unlock your tablet, it will clear RPMB and flash original LK,TZ & preloader for restore it from ANTI-ROLLBACK.
I am not responsable of any physical damage in your tablet, YOU choose to make this modifications.
WARNING: Short the resistor with a lot of caution! A lot of people broke it and the only way to recovery it is doing a bridge!
NOTE: You will need to open the tablet so be prepared.
MATERIAL NEEDED:
Linux based system
USB Cable
Something conductive (paperclip, tweezers etc)
Something to open the tablet.
Install python3, PySerial, adb, fastboot:
Code:
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot
Disable/Uninstall modemmanager:
Code:
sudo systemctl stop ModemManager
sudo systemctl disable ModemManager
UNBRICK PROCEDURE:
1. Open the case of the tablet.
2. Now flip off the tablet, we need to access on the other pad.
3. You have two options; Desolder the shield, or do a hole were the point is located (see attatchments).
4. Now go to the Computer and download amonet-giza-v.X.zip and extract it.
5. Open the unpacked folder of amonet-giza-1, open a terminal inside it and type:
Code:
sudo ./bootrom-step.sh
6. When you see:
Code:
[2019-02-07 14:35:59.478924] Waiting for bootrom
Short the point with the ground (Metal shield for example) and wait until the script starts.
7. The script will say to remove the short. When this happens, stop shorting the BootROM point and then press enter.
8. Wait until the script finishes, you will see something like:
Code:
Reboot.
9. Now your tablet should start booting back to FireOS.
Next time, be carefully with downgrade.
THANKS:
- @chamuc0 for finding the B-ROM point, providing the screenies and test the method.
- @t0x1cSH for the help with boot0-short.bin.
- @xyz` for his original exploit for the HD8 2018.
- @k4y0z
DOWNLOAD:
amonet-giza-v1.3.zip

Reserved

Thanks for working on a 2016 Fire 8, i understand this is rescue procedure but how can we get in this problem, only downgrading?

Oco said:
Thanks for working on a 2016 Fire 8, i understand this is rescue procedure but how can we get in this problem, only downgrading?
Click to expand...
Click to collapse
Yeah or flashing partitions were they not should be with mtk-su.
Regards!

thanks flashed it

Got Error
Hello.
Tired it and this is the output I got. Is mine a gonner or is there something I am doing wrong?
[2019-09-27 13:23:28.046514] Init crypto engine
[2019-09-27 13:23:28.062501] Disable caches
[2019-09-27 13:23:28.062883] Disable bootrom range checks
[2019-09-27 13:23:28.075597] Load payload from ../brom-payload/build/payload.bin = 0x4690 bytes
[2019-09-27 13:23:28.079826] Send payload
[2019-09-27 13:23:28.661813] Let's rock
[2019-09-27 13:23:28.662601] Wait for the payload to come online...
Traceback (most recent call last):
File "main.py", line 121, in <module>
main()
File "main.py", line 57, in main
load_payload(dev, "../brom-payload/build/payload.bin")
File "/home/twocrows/Downloads/unbrick giza/modules/load_payload.py", line 115, in load_payload
dev.wait_payload()
File "/home/twocrows/Downloads/unbrick giza/modules/common.py", line 168, in wait_payload
raise RuntimeError("received {} instead of expected pattern".format(data))
RuntimeError: received b'' instead of expected pattern
Thanks for any help!

twocrows said:
Hello.
Tired it and this is the output I got. Is mine a gonner or is there something I am doing wrong?
[2019-09-27 13:23:28.046514] Init crypto engine
[2019-09-27 13:23:28.062501] Disable caches
[2019-09-27 13:23:28.062883] Disable bootrom range checks
[2019-09-27 13:23:28.075597] Load payload from ../brom-payload/build/payload.bin = 0x4690 bytes
[2019-09-27 13:23:28.079826] Send payload
[2019-09-27 13:23:28.661813] Let's rock
[2019-09-27 13:23:28.662601] Wait for the payload to come online...
Traceback (most recent call last):
File "main.py", line 121, in <module>
main()
File "main.py", line 57, in main
load_payload(dev, "../brom-payload/build/payload.bin")
File "/home/twocrows/Downloads/unbrick giza/modules/load_payload.py", line 115, in load_payload
dev.wait_payload()
File "/home/twocrows/Downloads/unbrick giza/modules/common.py", line 168, in wait_payload
raise RuntimeError("received {} instead of expected pattern".format(data))
RuntimeError: received b'' instead of expected pattern
Thanks for any help!
Click to expand...
Click to collapse
Yeah normal problem. I need to set timeout to 10. I will upload new version later.
Regards.
EDIT: Try v1.2. Is in first post.

New Error?
Rortiz2 said:
Yeah normal problem. I need to set timeout to 10. I will upload new version later.
Regards.
EDIT: Try v1.2. Is in first post.
Click to expand...
Click to collapse
Here's the output from using v1.2:
"[2019-09-28 14:19:47.198801] Init crypto engine
[2019-09-28 14:19:47.218089] Disable caches
[2019-09-28 14:19:47.218521] Disable bootrom range checks
[2019-09-28 14:19:47.232121] Load payload from ../brom-payload/build/payload.bin = 0x4690 bytes
[2019-09-28 14:19:47.235220] Send payload
[2019-09-28 14:19:47.862758] Let's rock
[2019-09-28 14:19:47.863516] Wait for the payload to come online...
Traceback (most recent call last):
File "main.py", line 121, in <module>
main()
File "main.py", line 57, in main
load_payload(dev, "../brom-payload/build/payload.bin")
File "/home/twocrows/Downloads/unbrick giza/modules/load_payload.py", line 115, in load_payload
dev.wait_payload()
File "/home/twocrows/Downloads/unbrick giza/modules/common.py", line 168, in wait_payload
raise RuntimeError("received {} instead of expected pattern".format(data))
RuntimeError: received b'' instead of expected pattern"
Any thoughts?

twocrows said:
Here's the output from using v1.2:
Code:
"[2019-09-28 14:19:47.198801] Init crypto engine
[2019-09-28 14:19:47.218089] Disable caches
[2019-09-28 14:19:47.218521] Disable bootrom range checks
[2019-09-28 14:19:47.232121] Load payload from ../brom-payload/build/payload.bin = 0x4690 bytes
[2019-09-28 14:19:47.235220] Send payload
[2019-09-28 14:19:47.862758] Let's rock
[2019-09-28 14:19:47.863516] Wait for the payload to come online...
Traceback (most recent call last):
File "main.py", line 121, in <module>
main()
File "main.py", line 57, in main
load_payload(dev, "../brom-payload/build/payload.bin")
File "/home/twocrows/Downloads/unbrick giza/modules/load_payload.py", line 115, in load_payload
dev.wait_payload()
File "/home/twocrows/Downloads/unbrick giza/modules/common.py", line 168, in wait_payload
raise RuntimeError("received {} instead of expected pattern".format(data))
RuntimeError: received b'' instead of expected pattern"
Any thoughts?
Click to expand...
Click to collapse
Something is wrong with payload.
It seems to load it but somehow it can't detect it.
How did you bricked your tablet? Downgrading?
EDIT: I checked the adresses of the scripts and are OK. I think you are doing something wrong.

Rortiz2 said:
Something is wrong with payload.
It seems to load it but somehow it can't detect it.
How did you bricked your tablet? Downgrading?
EDIT: I checked the adresses of the scripts and are OK. I think you are doing something wrong.
Click to expand...
Click to collapse
I was afraid of that.
Will do some more checking on my end, but am afraid I nicked the board when I cut off top plate
Will post pic if it will help to see what *NOT* to do

twocrows said:
I was afraid of that.
Will do some more checking on my end, but am afraid I nicked the board when I cut off top plate
Will post pic if it will help to see what *NOT* to do
Click to expand...
Click to collapse
Check and post results. But if you tablet is detected as preloader without shorting the point, then it's not hardware problem. Try doing the process without battery connected.
Regards.

Here is a pic of my board, which I think is damaged.

twocrows said:
Here is a pic of my board, which I think is damaged.
Click to expand...
Click to collapse
Yes, definelety, seems that you damaged it. I'm sorry.
Regards.

twocrows said:
Here is a pic of my board, which I think is damaged.
Click to expand...
Click to collapse
Can you desolder it to remove the soldered shield using hot air gun.

just to confirm, it works!!! now I can use my tablet again! just wondering is anyone working on getting the bootloader unlock for 2016? i will be a volunteer to test it, since i bricked my tablet once already.

bluedisc said:
just to confirm, it works!!! now I can use my tablet again! just wondering is anyone working on getting the bootloader unlock for 2016? i will be a volunteer to test it, since i bricked my tablet once already.
Click to expand...
Click to collapse
Hey man,
Glad that you unbricked your tablet.
Regarding to bootloader unlock it can be ported from douglas I think.
I'm sorry but I'm not enought smart to port lk payload, etc.
The only person that can do that is k4y0z.
Cheers.

Rortiz2 said:
Hey man,
Glad that you unbricked your tablet.
Regarding to bootloader unlock it can be ported from douglas I think.
I'm sorry but I'm not enought smart to port lk payload, etc.
The only person that can do that is k4y0z.
Cheers.
Click to expand...
Click to collapse
It's okay, you did a great job at figuring out how to unbrick the tablet, and I appreciate your hard work. :good: Thank you.

bluedisc said:
just to confirm, it works!!! now I can use my tablet again! just wondering is anyone working on getting the bootloader unlock for 2016? i will be a volunteer to test it, since i bricked my tablet once already.
Click to expand...
Click to collapse
@k4y0z is the author of several unlock threads but he wrote in another thread that he hasn't a 2016 HD8 tablet and that he thinks that we are not so many ones.

Oco said:
@k4y0z is the author of several unlock threads but he wrote in another thread that he hasn't a 2016 HD8 tablet and that he thinks that we are not so many ones.
Click to expand...
Click to collapse
So donate to him
Maybe he can get a second hand Fire HD8 2016 like with HD10
Cheers.

I tried amazon and ebay without success, where can we get one? How much could it cost? Thanks for the idea