Hi all,
I've done everything I could but I can't get the OTA to work. I'm in the Netherlands and I still don't have the 3.1 OTA (also not with manual checking, router forwarded to Transformer IP in DMZ etc.). Does anyone know how I can force to detect it or where I can get the 3.1 update as Asus still didn't update their website...
Thanks!
P.s. I'm on the WW SKU
flight777 said:
Hi all,
I've done everything I could but I can't get the OTA to work. I'm in the Netherlands and I still don't have the 3.1 OTA (also not with manual checking, router forwarded to Transformer IP in DMZ etc.). Does anyone know how I can force to detect it or where I can get the 3.1 update as Asus still didn't update their website...
Thanks!
P.s. I'm on the WW SKU
Click to expand...
Click to collapse
are you rooted?
I don't need a signature.
Nope and never have been
same issue here, wassup with that? I'm in US, got my TF from Newegg on Thurs and been using it every day since, have rebooted a few times, updated the firmware on my TF and dock to get my dock working right, and so far everytime I check for updates it says there are none, so how the hell do we get 3.1 on here!? I'm not rooted, and currently on 3.01 which is how it came.
You're not the only ones... Got mine on Friday (03 June 2011) and so far zippo for the update (Italy). Guess we have to wait.
No need to wait
Just flash the un-official leaked version that came out before the OTA. It's the same build and everything to the released version. However make sure you have a US tablet if not you will have issues updating in regards to some applications not working properly.
i ended up doing a Google search and finding the update. I was only able to find the US version... but that was what i was looking for anyways. Good luck....
ya I ended up just downloading the US one and doing it manually and it worked fine.
That is the problem, I cant find a WW update
Sent from my Hero using XDA App
same problem here, having ch region. but as long as my tf is working fine, don't really need to update
strange i got my OTA last tuesday here in NL(basicly the moment i turned it on for the first time )
same here still on 3.01 not sure why and can only find the US version of the update unable to find and WW releases anywhere
Got my TF a couple of days ago, came home, updated to 3.1 as soon as I connected to the network.
Noticed pretty bad creaking in my bezel, brought TF back for replacement.
Got new TF home, connected to network, no update.
I had also installed a new router, right after updating the TF, but all the settings are exactly the same.
Is there a role for ОТА update,only for version A (16Gb) or for both A & B (32Gb)
I have the 32GB version...
the same here (UK)
Have the same problem here in UK.
I tried everything recommended on this forum (including hard reset, battery fully charged, DMZ, soft resets etc).
Settings / About always tells me that there are no updates available.
I hope ASUS will post 3.1 onto their support site so it can be downloaded manually (what are you waiting for guys!).
Disappointing...
I simply left my tablet on over night (with wifi enabled), and somewhere in there the tablet found and downloaded the update. I'd tried everything in the FOTA the previous evening and nothing worked. I'm in Ireland, by the way. That's all I can suggest.
*Daedalus said:
I simply left my tablet on over night (with wifi enabled), and somewhere in there the tablet found and downloaded the update. I'd tried everything in the FOTA the previous evening and nothing worked. I'm in Ireland, by the way. That's all I can suggest.
Click to expand...
Click to collapse
Yes - I tried this last two nights running (tablet plugged to charger, wifi on) - still no luck. But maybe this will happen sometime later this week.
Cheers,
Irek
I just received my Transformer yesterday, and did everything I could to try and force the 3.1 OTA (Followed instructions in the firmware update thread http://forum.xda-developers.com/showthread.php?t=1041502). The last thing I tried was I went to the Asus support site (HERE and downloaded the V8.2.3.13 update (choose the correct country) and applied it (not sure if this actually helped).
About 30 minutes later, I received my OTA notification in the status bar. What happens is, the device actually downloads the OTA in the background without you knowing, and then pushes a notification when it's finished to update the device. So the only other thing I would recommend is to try to stay on a fast wifi connection.
Hope this helps.
Before I got the 3.1 update, I tried the same thing. Flashed twice, each time, the updater would tell me the update was successful, and each time, my firmware version would still be 8.2.3.9.
Related
Please help out my coworker has a stock Hero on sprint and we are unable to update the firmware. I was able to update mine, our demo and one other co-worker's phone but on hers, every time I actually go into the firmware update it states no updates available. Sadly we work for a sprint store and hers is the only one giving us an error. I've already gone to the point of wiping the device to restore to factory but with no avail. Aside from having her swap out the phone at our repair center, I wanted to see if anyone has had the same problem and was able to get passed it. I saw a couple of posts stating to use the RUU utility, but on a stock rom that we already "RTN'd" I don't know how that would help. Any help would be greatly appreciated.
I've seen something similar. A coworker of mine just got a hero last week (after the MR release) and her phone shows the older software version but it will not recognize a firmware update is needed. I checked the phone's awake time and it was low, indicating the messaging app was not keeping the phone awake or draining the battery so I assumed it must not need the MR update even though it shows the old software version.
A couple others have metioned this... For some reason, some phones shipped with older firmware, version 1.22.651.1 instead of 1.29.651.1. Doing a hard reset on the 1.22 version wouldn't help, but updating the firmware to the 1.29 should. After that, check for the official MR.
You can find the file over here:
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
http://forum.xda-developers.com/showthread.php?t=559622
the guy at the sprint store (3rd party store) where i got mine from , his hero will not update or even flash back to the stock sprint ruu everytime it downloads the update and goes to apply it it shuts the phone down and thats it no reboot have to pull the batt to get it to power back on again
I had the same problem. I got my Hero on the first day it came out. Every time I tried to download the firmware update it would say no update available. Took it to the Sprint store and no luck either. They finally swapped out my original Hero for a new one and I was past my 30 days.
Hi,
Yesterday or so I read on the net HTC europe released a new rom. But when I try to update my Legens says there is no update available for my device. I tried with both 3g and wifi on as I read somewhere that could make a difference.
I used a goldcard to unbrand my vodafone legend but the last OTA update worked fine so I assume this cant be a problem now? (as far as I can see my Legend is totally stock).
Are there more people having this problem or now how to fix it?
I got an ota popup yesterday, downloaded and installed the update, and since then the phone has been restarting randomly all the time (no other difference that I've noticed so far), so I wouldn't be in a hurry to update if I were you
Update working for me..
I got the OTA update as well yesterday. Updated succesfully, legend works without problems.
I tried to update with my rooted phone, but the update stops after a while and an image of a phone with a question mark is shown.. Then the phone reboots like nothing happened.. Anyone else has this problem?
yeh it had the phone with the question mark and then it shows the phone without a question mark. i downloaded the update and installed it but when i checked the software info its still 1.405.4. my phone is rooted too
Same here, question mark ... no way to upgrade... we need Help from Paul
I gather these firmware updates are not documented anywhere what they fix?
After updating my Omnia 7 to Nodo I got another update notification about a "Samsung Update".
When I try to install it it hangs at step 6 of 10: rebooting your phone (the phone shows the omnia logo but doesn't boot).
Was anybody able to install this update? What does it do?
You say you updated to NoDo...how? Did you receive a notification or use one of the tricks to get the update? Not had anything myself. Also how long after the NoDo update did you get the other update, was it via Zune or a phone notification.
Sounds interesting given the odd display I've now got, wondering if we have some updated drivers on the way.
gc48067 said:
You say you updated to NoDo...how? Did you receive a notification or use one of the tricks to get the update? Not had anything myself. Also how long after the NoDo update did you get the other update, was it via Zune or a phone notification.
Sounds interesting given the odd display I've now got, wondering if we have some updated drivers on the way.
Click to expand...
Click to collapse
I forced the update (via Hungary) but got the new notification as soon as I connected the phone to Zune (it also shows up on the phone).
There is a 'more information' link on the first page but sadly it does not give more information.
Getting the same update after NoDo. Doesn't update though, stuck at rebooting just like you. Weird..
Didn't get my update via Hungary BTW, just the regular way (A1 branded).
Hmmm this is worrying. I assume there were no problems after this update failed?
Freypal said:
Hmmm this is worrying. I assume there were no problems after this update failed?
Click to expand...
Click to collapse
No, I don't think anything happened yet. The PC is waiting for the phone to reboot, and the phone is stuck on boot..
How long did you leave it?
Not sure, 30-45 mins maybe the first time. The second time I tried just a couple of minutes. It said the update would take 32 mins, but since it just said rebooting and not updating I reckoned the process hadn't even started yet.
Cheekbone said:
Not sure, 30-45 mins maybe the first time. The second time I tried just a couple of minutes. It said the update would take 32 mins, but since it just said rebooting and not updating I reckoned the process hadn't even started yet.
Click to expand...
Click to collapse
You just unplugged it then and it carried on workig OK?
That sounds about right, when i did pre-nodo the reboot took about a minute or so of displaying the Omnia logo then went to the pc plug screen whilst it updated.
I did read about device specific updates, seems odd though as some people are saying that they updated to NoDo and it works fine and had no future updates.
Freypal said:
You just unplugged it then and it carried on workig OK?
That sounds about right, when i did pre-nodo the reboot took about a minute or so of displaying the Omnia logo then went to the pc plug screen whilst it updated.
I did read about device specific updates, seems odd though as some people are saying that they updated to NoDo and it works fine and had no future updates.
Click to expand...
Click to collapse
Unplugged it and had to take the battery out to reboot. Notice how it says 'Samsung update for Windows Phone' though. I'll try one more time. My phone bugged me a couple of times about the update as well ('An Update is available').
I wonder if this is a firmware update?
Edit - Looks like it is http://forum.xda-developers.com/showpost.php?p=12516155&postcount=56
Yeah, guessed so. Still not working for me though. Waited for about an hour for it to reboot.
My mistake - Edited
Can i know which firmware version do you have on your Omnia 7? I got a JK1 and i haven't recieved this kind of update
PS
To view firmware version go in phone then open the numeric pad and call ##634# to enter diagnosis then type these combination: *#1234#
For me:
PDA: ends with JID
Phone: ends with JIC
CSC: ends with JID
Curious to see what Cheekbone has as its trying to update it
All end with JJ6
Well I guess the majority is already on JK1, so the samsung update only pops up for some.
It would be great if there would be further samsung firmware updates before major MSFT ones.
It does seem that JK1 is the norm. I guess it means I will be offered the further update...
Worrying!
Hey mine says
JID
JIC
JID
is this old? Is there any point to updating the firmware? Zune gives me no update. but i have been wondering about my FW Version for some time.
Any help is appreciated.
ProficienTWP7 said:
Hey mine says
JID
JIC
JID
is this old? Is there any point to updating the firmware? Zune gives me no update. but i have been wondering about my FW Version for some time.
Any help is appreciated.
Click to expand...
Click to collapse
Have you updated to Pre-NoDo (.7008) or NoDo (.7390) ?
Hi all.. I have a Galaxy Tab 10.1 gt p7500 one month old, and I saw that there is finally an update to ICS. I still dont got it try mobile netowork (t-mobile - Macedonia), so i read that I can update thru kies. The problem is, I cannot connect mu tab to kies??? I dont have an USB option on Wireless and Networks and it connects in MTP mode. Is there any way to fix this problem and if not, how can I update my tablet to stock version of ICS in some other way? Please help...
Regards
It sucks that kies won't work now that ics is out. I'm having trouble updating mine as well.
Kies is not a product
I have tried for almost a year now to get my tab recognised by Kies, but only a factory reset will get Kies to recognise my tablet. The moment I install my own software on it again that disappears.
Kies via Wifi has no firmware upgrade option, sad to say, so best wait for OTA upgrade.
I am waiting too for the OTA as that POS named Kies is not working for me. But it is coming, just be a little more patient. It is rolling out in the US, maybe even in Canada. The rest of Europe will follow, or you can download from samfirmware.com, and do it over USB via Odin (lots of threads covering that)...
Best of luck!
I did a reset in anticipation of the update and was able to do the update through Kies
with no problem.
I had 2 Galaxy 10.1, one of them could only connect wireless for update, not with Kies, the other one could not update OTA, only with Kies... and to connect I had to reset the device, Kies is really worth nothing...
One of the reasons why I am only using custom ROM
I fought with it for a couple hours last night, and finally resorted to a factory wipe. Then it was fine. Just means a few hours of reinstalling and configuring widgets, but still annoying as hell that after 2 years Kies doesn't work with 3.2 stock rom.
ProximaC said:
I fought with it for a couple hours last night, and finally resorted to a factory wipe. Then it was fine. Just means a few hours of reinstalling and configuring widgets, but still annoying as hell that after 2 years Kies doesn't work with 3.2 stock rom.
Click to expand...
Click to collapse
It's far worse: I could never connect to Kies. One day I just wanted to test connecting to Kies, so I did a Backup with Titanium Backup and then a factory reset. Thereafter I could connect without any issues. So I restored all settings - user and system data with everything! - from my TB and expected not to be able to connect after doing that. But oh wonder! I still could connect to Kies!
But about a week later it was again like before: No connection to Kies :silly: That was the last time I started the software on my PC :cyclops:
After the update, and after I updated the apps that are included with the tab, and after I reinstalled all of my apps,
I tied Kies again. Tab connected wih no problems.
Looks like that's one of the things fixed in ICS.
From what I gathered from the internet and other forums the problem with Kies apparetly is that if there is a file with a filename that kies doesn't like, it won't connect. The big problem is find that file or files
Sent from my GT-P7510 using xda app-developers app
Kies kies bye bye
digitalundertaker said:
From what I gathered from the internet and other forums the problem with Kies apparetly is that if there is a file with a filename that kies doesn't like, it won't connect. The big problem is find that file or files
Click to expand...
Click to collapse
That is my understanding too. But when I remove all non-essential files (i.e. "personal" files) from the system it still did not work... So it must be one of the files related to a product.
To find out which one (or which ones...) will take a lot of time, and I do not want to spend that much time on a POS product like Kies... So for now I will wait for the OTA update, or the end of August 2012, whatever comes first. If it still is not there at the end of this month I will go to one of the custom ROMs, and never look back.
XDA is no longer worth my time.
TimOster said:
It doesn't have to connect to Kies in order to do the update. Mine didn't.
Put it in download mode, have Kies running, connect the cable and run the Firmware upgrade and initialization from the tools menu.
Click to expand...
Click to collapse
That IS an interesting concept. Never thought that might work. I have given up, surrendered to Kies, reset the GTab, got Kies working, but alas, no update here in Canuck Territory... So all for naught!
I will try your approach on the other GTabs I've got...
Thanks for the tip!
-- EDIT --
Guess what? When running Firmware upgrade and initialization I get the message: "'GT-P7510' does not support initializing."
And that is all I can do, no upgrade via that path possible...
I did a factory data reset and upgraded to ICS via wi-fi. And my 7510 was still rooted
My new A2017G B08 has no problem finding and connecting with my old LG G2 - but when trying to connect it with my trusty Bluetooth speaker, the Axon doesn't even see it. And while I can find the Axon within just 1-2 seconds from my PC with a BT-Stick, the other way around the Axon doesn't see the PC.
I can life with not finding the PC, but what can I do to make it work with the speaker? The G2 has no issues with that either so the speaker's bluetooth does work.
Go into settings/location and ensure high accuracy is selected. It can improve bluetooth scanning.
RobboW said:
Go into settings/location and ensure high accuracy is selected. It can improve bluetooth scanning.
Click to expand...
Click to collapse
That didn't help. Still, the speaker does not show up when searching for devices.
had the same issue ! b09 fixed it
Mine was fine on B04 and B08 and is still fine on B09 but I don't use any old BT speakers, most devices are fairly new. The car stereo is probably the oldest. It dates back to 2010 with a 2012 firmware update on the BT module.
caesar170988 said:
had the same issue ! b09 fixed it
Click to expand...
Click to collapse
Well, B08 is the latest version I'm getting via OTA update. I guess if nobody else comes up with a solution/tips that might work there's nothing I can do but wait for (hopefully) an Android 8 update that has the issue fixed for my device
Eiion said:
Well, B08 is the latest version I'm getting via OTA update. I guess if nobody else comes up with a solution/tips that might work there's nothing I can do but wait for (hopefully) an Android 8 update that has the issue fixed for my device
Click to expand...
Click to collapse
Don't rely on OTAs... If your bootloader is locked just go to the download center, download the B09 zip, put it in the internal storage and go to the Updates tab, it should appear there
Yeah, if I waited for an OTA my phone would still be on Marshmallow. They had problems with OTA and stopped doing them and advised to do SD updates so you have to download. Could be that a SD update may fix it.
Even then, the latest on the Australian web site is B04. I got B08 from Germany and B09 from Switzerland. It's an international ROM. I don't download from anywhere but ZTE websites.
We rely on other XDA members finding the updates and posting here that it's available.
RobboW said:
Yeah, if I waited for an OTA my phone would still be on Marshmallow. They had problems with OTA and stopped doing them and advised to do SD updates so you have to download. Could be that a SD update may fix it.
Even then, the latest on the Australian web site is B04. I got B08 from Germany and B09 from Switzerland. It's an international ROM. I don't download from anywhere but ZTE websites.
We rely on other XDA members finding the updates and posting here that it's available.
Click to expand...
Click to collapse
The download center is basically all of those but unpacked and uploaded to androidfilehost. And all of that is made by @raystef66 . It's not like you're downloading them from some shady Russian torrent website
RobboW said:
Yeah, if I waited for an OTA my phone would still be on Marshmallow. They had problems with OTA and stopped doing them and advised to do SD updates so you have to download. Could be that a SD update may fix it. [...]
Click to expand...
Click to collapse
Choose an username... said:
The download center is basically all of those but unpacked and uploaded to androidfilehost. And all of that is made by @raystef66 . It's not like you're downloading them from some shady Russian torrent website [...]
Click to expand...
Click to collapse
Guys, I have no idea how to do that and although I did root my G2 I'm not feeling very comfortable updating to anything but the official version for my German Axon 7. Meaning, if updating to the swiss version I'm pretty sure I'd lose my warranty.
Also, I'd need a very basic step by step instruction without too many technical terms (and a link to where to get the file) to feel save enough to do it. It's just that I cannot afford another phone should something go wrong.
So, I'd totally be interested in doing an update to a new firmware version since that might possibly indeed fix my problem (and possibly 1-2 others I have with the phone) - but I'm scared to brick it/lose warranty. Any thoughts on that?
EDIT: I've just checked the ZTE website for downloads and I'm a bit confused... version B10 was Android 6 and version B08 is Android 7.1? So... version B09 is older than mine? Is that what you were suggesting, going back to an older version? Can I even update backwards? Usually devices say something like "The software installed on your device is already the newest version" or something along those lines whenever trying to install a previous software version.
EDIT 2: Found "AXON 7(ZTE A2017G )SD card software package(344070B1405ZTE A2017GV1.2.0B09)N Version" on the ZTE website - but what does "N version" mean? Mine says on its back "ZTE A2017G".
Eiion said:
Guys, I have no idea how to do that and although I did root my G2 I'm not feeling very comfortable updating to anything but the official version for my German Axon 7. Meaning, if updating to the swiss version I'm pretty sure I'd lose my warranty.
Also, I'd need a very basic step by step instruction without too many technical terms (and a link to where to get the file) to feel save enough to do it. It's just that I cannot afford another phone should something go wrong.
So, I'd totally be interested in doing an update to a new firmware version since that might possibly indeed fix my problem (and possibly 1-2 others I have with the phone) - but I'm scared to brick it/lose warranty. Any thoughts on that?
EDIT: I've just checked the ZTE website for downloads and I'm a bit confused... version B10 was Android 6 and version B08 is Android 7.1? So... version B09 is older than mine? Is that what you were suggesting, going back to an older version? Can I even update backwards? Usually devices say something like "The software installed on your device is already the newest version" or something along those lines whenever trying to install a previous software version.
EDIT 2: Found "AXON 7(ZTE A2017G )SD card software package(344070B1405ZTE A2017GV1.2.0B09)N Version" on the ZTE website - but what does "N version" mean? Mine says on its back "ZTE A2017G".
Click to expand...
Click to collapse
You're confusing everything... That is not swiss, it's international. The only thing that COULD void your warranty is unlocking the bootloader, and in some cases people have been able to still claim hardware warranty on their phones by saying that they have not touched the hardware. Also, ZTE provides those updates.
If something happens (it would be basically your fault, such as trying to update with 10% battery or updating with an A2017 or A2017U package) and your phone stops working, just call ZTE and claim warranty. Their update method failed, etc. etc. Although it is borderline impossible to mess up your phone with the stock update method... I think it even tells you that you can't update with less than X% of battery.
The updates are as follows: A2017GV1.0.0B01 to B11 was Marshmallow, and then came A2017GV1.2.0B01 to B09 which is Nougat. I have thought many times that it would have been a lot better if they called them, say, M11 and N09. But this is what we have.
It's not hard at all: Go to the Guides section, there you will find Raystef66's download center. Download the file called A2017G-N-B09 (??), NOT the one under "TWRP flashable Bootstack/Stocksystem images". Those won't work.
After it gets downloaded, connect your phone to the PC. allow MTP transfer from the phone. "Internal Storage" should appear as a folder. If you have an SD card it will appear as another folder beside that on your PC. Open Internal storage. Now that is called the root of the internal storage, where all the folders are located. Just take the zip and throw it there, outside of all the folders (outside of DCIM, Android, and all those).
Then go to the phone, Settings, Update, and select the update.
@RobboW @Choose an username... (thank you very much for writing down all the information on updating the phone!)
Ok, so I did the update directly downloaded from their website. The update worked - indeed though, as somebody else has mentioned elsewhere, the phone now seems slightly slower to react to inputs when scrolling/tapping through the menu. Anyways, that's besides the point.
I tried connecting to the speaker, but still, it does not show up when searching for devices. Interestingly though I tried to make a new connection from my old phone (where I had deleted the connection) and the G2 now also can't find it (although it worked fine when the connection was already set up).
I'm back to trying to get one or the other device connected again. If nothing works, I guess I'm screwed then.
Eiion said:
@[email protected] an username...
Ok, so I did the update directly downloaded from their website - followed their PDF instruction for Update via SD. The update worked - indeed though, as somebody else has mentioned elsewhere, the phone seems slightly slower to react to inputs when scrolling/tapping through the menu. Anyways, that's besides the point.
I tried connecting to the speaker, but still, it does not show up when searching for devices. Interestingly though I tried to make a new connection from my old phone (where I had deleted the connection) and the G2 now also can't find it (although it worked fine when the connection was already set up).
I'm back to trying to get one or the other device connected again. If nothing works, I guess I'm screwed then.
Click to expand...
Click to collapse
Can you find the speaker with your PC?
Did you actually go into the PC's bluetooth settings to allow it to be visible?
Choose an username... said:
Can you find the speaker with your PC?
Did you actually go into the PC's bluetooth settings to allow it to be visible?
Click to expand...
Click to collapse
Sure, I did that when trying to connect it to the PC.
Anyways, I was trying 10-15 more minutes and don't ask me how or why... I did nothing different from all the times before but I finally was able to find the speaker on the Axon 7 and set up the connection. After that I wanted to connect the Axon 7 to the G2 - and while the G2 found the A7 within a second, the A7 did not see the G2. And after that I also tried to connect the G2 again with the speaker which worked as well.
So, all that's left is connecting the PC to the BT speaker - but I guess that's no topic for this forum.
So, thank you guys for your contribution, without I might have given up a few days ago already. Now I made it and have an updated phone. :good:
Eiion said:
Sure, I did that when trying to connect it to the PC.
Anyways, I was trying 10-15 more minutes and don't ask me how or why... I did nothing different from all the times before but I finally was able to find the speaker on the Axon 7 and set up the connection. After that I wanted to connect the Axon 7 to the G2 - and while the G2 found the A7 within a second, the A7 did not see the G2. After I also tried to connect the G2 again with the speaker and that worked as well.
So, all that's left is connecting the PC to the BT speaker - but I guess that's no topic for this forum.
So, thanks for you guys for your contribution, without I might have given up a few days ago already. Now I made it and have an updated phone. :good:
Click to expand...
Click to collapse
Semi-updated... you on B08?
The latest security patch is Dec. 1 and it's on B09. Just informing if you decide to update again
Choose an username... said:
Semi-updated... you on B08?
The latest security patch is Dec. 1 and it's on B09. Just informing if you decide to update again
Click to expand...
Click to collapse
As I had mentioned I was on B08 before the update. I'm on B09 now.
Good stuff, my next suggestion was going to be if you have an option to reset the speaker. No need now.
Sometimes you could get stuck with too many pairings. It's good to delete un-needed pairings on the phone but on a speaker you generally can only reset.
RobboW said:
Good stuff, my next suggestion was going to be if you have an option to reset the speaker. No need now.
Sometimes you could get stuck with too many pairings. It's good to delete un-needed pairings on the phone but on a speaker you generally can only reset.
Click to expand...
Click to collapse
Yeah, I thought of that too and searched the manual for it - but didn't find anything. Then I tried several button press combinations while on or while turning it on... you know, sometimes they simply don't put every function in the manual. But nothing seemed to do it. Or maybe it did - how would I know, it has no display.
But anyways, it works and that's all that matters
@ Eiion,
Have you fixed your phone's problem? I experience the same problem, so have you try other different PC and Bluetooth?
Delete all synced devices in bluetooth list. Then try to sync your device. Seems to work for me.