Have I bricked my Phonak Aid?

So did this just happen as soon as you tried to connect to target,or were you making some adjustments to the HA at the time and went to save and got that message, I’ve seen it before a few times using iCube “the bug” it can have (it’s the main reason I dumped iCube for iCube ll) the wireless connection gets interrupted, but as @andreanboea has mentioned HiPro is a possibility, but it definitely looks to me like “bricked”
Just out of curiosity, what version of target are you using.

@andreanboea

@tenkan

I’ve definitely been in luck.

I spoke to an audiologist who’s helped me loads since I stated self programming in 2011.

He said Target 8.0.2 (it’s the latest, not 100% if numbers are correct but it’s 8.?.?) was not good when this problem arises.

He told me to go back to 6.2 and the reset worked straight away to solve this issue.

I use a iCube II and was just connecting my Aids rather than trying to do anything else.

I’m gong to stick with 6.2 as l only have the V70 and M70 so it’ll work for me.

I’m confused by your post @pvc

iCube II works both on 6.2 and 8 which I have both.

I’ve been using a iCube II for 7, nearly 8 years.

Yea a bit of pure luck @tenkan

I really wasn’t expecting it to work.

The audiologist who helped me said it would work but I was thinking how can a software version make any difference especially as iCube II works on the latest Target as well.

Which part are you confused about? That iCubeII is going obsolete but you can still use it? You can say the exact same thing about iCube.

All wireless proprietary hearing aid programming devices are going obsolete. They are not yet completely obsolete. But they will be!

@pvc said:

Your solution, even though you are programming with (iCube II and current versions of Target 8 for months) is to revert back to an older version of the fitting software.

Yes but not because Target 8 doesn’t work with iCube II!

That wasn’t the issue!

It’s to do with how the factory reset works!

@pvc said:

I posted to this thread because I believe that others, should be made aware of these Phonak/Unitron version issues related to their going-obsolete proprietary wireless hearing aid programming devices. I don’t believe it should be kept secret just because you have a bricked-hearing-aid-workaround of reverting back to an older version of the fitting software.

It’s nothing to do with the fantastic “not going obsolete” going nowhere for a long time iCubes, it’s software as @Zebras mentioned,but regardless for all those people who like to buy older versions of HAs and DIY this is the perfect solution.

@pvc said:

don’t believe it should be kept secret just because you have a bricked-hearing-aid-workaround of reverting back to an older version of the fitting software.

Well this was the solution given to the issue and explained by @Zebras for all to see on the forum, no dirty little “secrets” from anyone.

Yep, I get it that for this specific instance of your bricked hearing aids;

• factory reset using iCubeII with Phonak Target 8.? does not work
• factory reset using iCubeII with Phonak Target 6.2 works

Also at issue is why were the hearing aids bricked in the first place? You said;

• I was not even trying to do the firmware as the firmware has not been updated for a long time.
• I had a new battery in it as I always do.
• I’m going to stick with 6.2 as l only have the V70 and M70 so it’ll work for me.

So, back to my point I was trying to make. These are Phonak/Unitron version issues related to their going-obsolete proprietary wireless hearing aid programming devices, and I believe other members should be aware of these issues and the workarounds. Not just your workaround. But all of them.

• Phonak Target 6.2 can fix some bricked hearing aids
• Phonak Target 6.1 can facilitate the use of obsolete iCube
• Unitron TrueFit 5.0 can facilitate the use of obsolete iCube

@Zebras said:

6.2 can fix a bricked Aid with the same fault that only works with Noahlink Wireless if you have the Marvel according to the audiologist so again nothing to do with the iCube II, it’s software based.

@pvc said:

Software based? So your hearing aids got bricked by Target 8, and the bricking has nothing to do with iCubeII?

Read again and then you may understand.

How can it be an iCube II issue when the same happens to Marvels and NL Wireless?!

@pvc said:

Shouldn’t everyone try putting a stop to this software based bricking of hearing aids by reverting back to Target 6.2? Whoa, wait another minute? I don’t think that Target 6.2 can program Paradise hearing aids.

Like I said before, I was talking about the Marvels. Mentioned nothing to do with Paradise.

The audiologist was only helping me with my V70 and M70!

@Zebras said:

Read again and then you may understand.

How can it be an iCube II issue when the same happens to Marvels and NL Wireless?!

Are you saying that Target 8 (using Noahlink Wireless) can brick your hearing aids? Of, course not! You are ignoring the bricking event to bolster your argument.

Dear Readers; Move on. Nothing to see here. That is, until your hearing aids get bricked by a going-obsolete proprietary hearing aid programming device, namely iCubeII.

@pvc said:

Are you saying that Target 8 (using Noahlink Wireless) can brick your hearing aids? Of, course not! You are ignoring the bricking event to bolster your argument.

No I’m just passing on information from an audiologist of nearly 40 years!!!

He’s more likely to be correct than a user like you! I realise you have a lot of info but come on, 40 years of experience!!

You’re the only one who’s not understanding this situation!!