Related
Hey everyone, this is my first post here so I'm not entirely sure this is the right place to pose this question. Earlier today, I made the decision to upgrade my Dash to WinMobile 6.1 using the resources here at this forum. The upgrade went nearly flawlessly with the excption that I need to copy the correct keyboard settings cab file still. However, I'm unable to do that because of Activesync.
I had 4.2 installed on my laptop and it never gave me any problems. Unfortunately, the phone displayed a message that I needed to upgrade to 4.5 in order to connect to the PC using Activesync. I downloaded the file from Microsoft's website and tried to run the install program. After clicking the "install" prompt, I get the following error message: "The System Cannot Open the Device or File Specified" Retry or Cancel. Retry gets me no where. I have spent at least 5 hours not trying to find a solution to this problem including a LOT of searching on Google, here, Microsoft's site and other places. NOTHING. I've seen a couple of references to this problem but no definitive solution to the problem.
A few things I have tried: Disable Firewall; uninstall Activesync 4.2 (curiously, after using the Add/Remove Program tool in the Control Paner, there was still an Activesync folder and dozens of files on my hard drive...I manually deleted as many of these as I could); Ran a file called "fixmapi.exe"; and I downloaded the upgrade file from multiple sources, all of which were suggestions I came across during the day.
I'm sooo frustrated because I can't update the keyboard map, I cant synchronize the hundreds of contacts and calendar items I have in Outlook, the phone feels completely useless to me at the moment and I cant believe that this is such an unusual problem (which is my conclusion based on such a complete lack of guidance on this issue).
anything anyone can offer will be HUGELY appreciated!
Disclaimer, use this at your own risk, if this voids your warranty I’m not being held responsible, blah blah all that junk.
Well, first, thanks go out for Microsoft for releasing a support tool for Windows Phone yesterday. Inside that tool, were unreal hidden gems.
Basically they’ve created a managed wrapper over the whole update process for us, rather nice of them.
So I flashed my HTC Mozart back to RTM (7004) via a ROM update HTC ship and whipped up a little application to flash pre-NoDo (7008), NoDo (7355), NoDo update 1 (7389) & NoDo update 2 (7390) all in a single process. No I don’t care which carrier you are on, which phone you have, it’ll just update your phone accordingly.
We really have to commend Microsoft here for being able to split up the OS updates into differential packs, which saves users downloading 200+ MB updates, unlike the IFruit updates.
All you need to do is run the ChevronWP7.Updater.exe console app and follow the prompts.
Make sure you select the RIGHT language for your device. To double check what your default language is, go to Settings > Keyboard and if your selected language is displayed in the Console app, you’re good to select it. If it isn’t in the list, DON’T flash it just yet.
Now, download the following files.
x86 Operating System (32 bit)
Windows Phone Support Tools
http://download.microsoft.com/download/1/5/4/15427EAF-AD42-4E4A-8179-9A3C5483E366/WPSupportTool-x86.msi
ChevronWP7.Updater
http://www.megaupload.com/?d=G1OEGML1
x64 Operating System (64 bit)
Windows Phone Support Tools
http://download.microsoft.com/downl...E4A-8179-9A3C5483E366/WPSupportTool-amd64.msi
ChevronWP7.Updater
http://www.megaupload.com/?d=40MA6F02
Once you’ve installed the support tools and extracted the ChevronWP7.Updater.zip to the desktop, plug your phone in and wait 30 seconds.
Now start ChevronWP7.Updater.exe (this should kill Zune) and follow the prompts.
If you’re updating from Version 7004, you need to run the Updater TWICE, this needs the preUpdate before we can flash NoDo.
Again, if your language isn’t in the Chevron updater, DON’T attempt to update your phone. Some of the applications won’t work otherwise.
This “might” work for HD2 owners, haven’t tried it out just yet. If it does, report below and tell me .
There is NO revert process, again, flash at your own risk.
I flashed my Samsung Omnia 7 works fine
Big Tenks to walshie
If I do so like you suggest with my HD2 (WP 7.0.7004.0), he still asks to update the february update..
And I did it twice like suggested...
Thanks anyway!
It doesn't work for me but I still have to install the February update. Does anyone know if there is already a new rom with this update included?
Thx!
Works for me, Samsung Focus AT+T and had to run it twice to get both updates.
Source
Where does this method pull the updates from? Is it the same update being tested by AT&T for the Focus?
Didn't work for me...tried 4 times and kept getting some error, then got booted from the program...not sure what the deal is. Samsung Focus, AT&T
Sent from my SGH-i917 using Board Express
Also not working for me- Samsung Focus on AT&T. Program runs, reboots phone, seems to update, but on examination I'm still at 7004.
Sadly I should've resisted. I did this on my AT&T Samsung Focus, everything is great except I have no marketplace and no Zune functionality..
LastOttoman said:
Disclaimer, use this at your own risk, if this voids your warranty I’m not being held responsible, blah blah all that junk.
Well, first, thanks go out for Microsoft for releasing a support tool for Windows Phone yesterday. Inside that tool, were unreal hidden gems.
Basically they’ve created a managed wrapper over the whole update process for us, rather nice of them.
So I flashed my HTC Mozart back to RTM (7004) via a ROM update HTC ship and whipped up a little application to flash pre-NoDo (7008), NoDo (7355), NoDo update 1 (7389) & NoDo update 2 (7390) all in a single process. No I don’t care which carrier you are on, which phone you have, it’ll just update your phone accordingly.
We really have to commend Microsoft here for being able to split up the OS updates into differential packs, which saves users downloading 200+ MB updates, unlike the IFruit updates.
All you need to do is run the ChevronWP7.Updater.exe console app and follow the prompts.
Make sure you select the RIGHT language for your device. To double check what your default language is, go to Settings > Keyboard and if your selected language is displayed in the Console app, you’re good to select it. If it isn’t in the list, DON’T flash it just yet.
Now, download the following files.
x86 Operating System (32 bit)
Windows Phone Support Tools
http://download.microsoft.com/downl...-4E4A-8179-9A3C5483E366/WPSupportTool-x86.msi
ChevronWP7.Updater
http://blog.walshie.me/Share/ChevronWP7.Updater.x86.zip
x64 Operating System (64 bit)
Windows Phone Support Tools
http://download.microsoft.com/downl...E4A-8179-9A3C5483E366/WPSupportTool-amd64.msi
ChevronWP7.Updater
http://blog.walshie.me/Share/ChevronWP7.Updater.x64.zip
Once you’ve installed the support tools and extracted the ChevronWP7.Updater.zip to the desktop, plug your phone in and wait 30 seconds.
Now start ChevronWP7.Updater.exe (this should kill Zune) and follow the prompts.
If you’re updating from Version 7004, you need to run the Updater TWICE, this needs the preUpdate before we can flash NoDo.
Again, if your language isn’t in the Chevron updater, DON’T attempt to update your phone. Some of the applications won’t work otherwise.
This “might” work for HD2 owners, haven’t tried it out just yet. If it does, report below and tell me .
There is NO revert process, again, flash at your own risk.
I flashed my Samsung Omnia 7 works fine
Big Tenks to walshie
Click to expand...
Click to collapse
In the future, just link directly to my Blog, direct linking to the installers doesn't enable me to update them if there is an issue.
so i shouldn't be doing this if i have Samsung Focus on AT&T?
mastamind518 said:
so i shouldn't be doing this if i have Samsung Focus on AT&T?
Click to expand...
Click to collapse
If you follow the post, there are detailed instructions for Samsung Focus users.
walshieau said:
If you follow the post, there are detailed instructions for Samsung Focus users.
Click to expand...
Click to collapse
thanks it worked. shows 7390.
Focus
Worked for me too on my ATT branded, locked Samsung Focus. Now running 7390.
Have an AT&T Focus, carrier unlocked, Chevron'ed and I can't seem to update. I have tried using the "Windows Support Tool" and still no luck. See log below if it looks right
UpdateWP version 4.7.1404
Applying updates to device
Id: \\?\usb#vid_045e&pid_0710#b7d536af-3362-ca4a-6b09-6f8888553bf1#{ca3d7387-f67b-11da-bbec-8000600fe800}
SN: af36d5b7 - 62334aca - 6b096f88 - 88553bf1
Name: SGH-i917
KITLName: QSD8XXX19417BBB
Manufacturer: SAMSUNG
ModelId: 1
MobileOperator:
Version: 07.00.07004.00-00000
Checking your phone's status.
Checking your phone's status: Completed in 0.01 seconds
Checking system requirements.
Checking system requirements: Completed in 0 seconds
Downloading updates.
Downloading updates: 0%
Downloading updates: Completed in 3.07 seconds
Checking system requirements.
Checking system requirements: Completed in 0 seconds
Installing updates. Please wait: 100%
Installing updates. Please wait: Completed in 5.57 seconds
Rebooting your phone..
Rebooting your phone: Completed in 42.3 seconds
Completing updates..
Completing updates: Completed in 1.28 seconds
The device has been updated to version 07.00.07004.03-00.00.00000.00-00.00.00000.00
When i look at the "About" status it still shows 7.00.07004.0
Any ideas?
Hi, HTC Surround
I am updating and it goes to downloading update but fails to go any further. just closes chevron
Any Ideas
Updated fine, but after the update anything related with messaging (SMS's, E-mail some contacts) doesn't work. Orange HTC Mozart running branded 7008...
Chevronwp7update was removed from the site. Where else can it be downloaded from?
Same here HTC Mozart telstra
Sent from my T8697 using XDA Windows Phone 7 App
Updater seems to be offline?
Anyone has got updated Links or a mirror?
Thanks in advance
Ok, I installed the Debrander xap util and it debranded to 00-88. I then ran Zune and it showed update available. It upgrade phone to 7008 from 7004. But even after that running chevron update still fails.
Maybe it was pulled from the site due to unforeseen problems.
Btw, don't reinstall debrander over your original debrander as it loses the original carrier details no I cannot rebrand to at&t unless I do a reg hack *I think*
UPDATE 274/2012
Okay. So, Nokser's FFUPartTool extracts the IMGFS partition from the FFU.
Barin's OSBuilder (here) can be used to dump the contents of the IMGFS.
The registry files can then be edited in HVEdit (link), and the IMGFS can be recreated using OSBuilder.
FFUPartTool can then be used to replace the IMGFS partition in the FFU.
This FFU now needs a Mazaa to be flashed on.
If anyone out here is brave enough to flash their phone, please report the results!
UPDATE 17/4/2012
So, as we all know we have a stock mango FFU for the Mazaa (see here if you don't).
And due to recent developments, we also have this: FFUPart Tool v1.3.1
What this means is, we can create a custom FFU for the Mazaa. Now, personally, I have never created WP7 CFW before, but Nokser, the creator of the tool above assures me the creating CFW with this tool is quite possible.
So, what are you guys waiting for? Race to the finish line?
My list of things to be done starts and ends with this: get htc connection setup to run.
That's literally all we need to kickstart the Mazaa scene. Once we have that, we can do the whole shebang.
We need a ROM image for the Mazaa before anything at all can happen.
-------------------------------------------------------------
Here are the ROMs being used by people:
7.1.7649 - Test Rom. Has lots of interesting Microsoft applications (the zApps). But lacks quite a few features and stability.
7.1.7661.wp7_5_trial(mojobld).20110607-1657 - Similar Test Rom.
7.1.7720.68 - Locked bootloader. Phone is recognized as an HTC Device, but Connection Setup doesn't run.
7.1.7720.500 - Is basically the same as .68 but with an unlocked bootloader. Phone is not recognized as an HTC Device.
7.1.7740.16 - Updated via the official CAB [WP7 Cab sender tool]
7.1.8107.79 - via the official CAB [WP7 Cab Sender Tool]
7.10.8773.98 - via the official CAB [WP7 Cab Sender Tool] - 28/06/2012
Firmware revision number: 1600.1502.7720.68
Hardware revision number: 112.1410.2.0
Radio software version: 1.6.00.15.02
Radio hardware version: 8655/DDR2
Bootloader version: 7.27.00
Chip SOC version: 0.75.2.1
If anyone has different details, please post them.
-------------------------------------------------------------
The major problem with all ROMs is the lack of drivers.
1) LED lights don't function
2) SD Card slot
3) Connection Setup drivers
4) Internet Sharing doesn't work
Secondarily, because of the lack of connection setup drivers, there's no interop unlock. Which means no homebrew. Which means this device is pretty much what a technophobe buying a smartphone for the first time needs.
-------------------------------------------------------------
Does anyone know how to edit FFU (full flash update) files? They seem to be .cab files with a signed xml .blob in them.
Is there any way to edit these files?
Alternately, has anyone been successful at obtaining a stock ROM for the Mazaa? Because otherwise the device is extremely crippled.
Once we obtain a stock ROM, it's merely the point of identifying what drivers are missing, appealing to the DFT team to test the Mazaa to check whether HSPL/RSPL works, testing whether HTC Trophy drivers (and maybe other phones' drivers) work, cooking a rom, and flashing it. Once we get the ball rolling, it should all materialise.
-------------------------------------------------------------
Finally, what other problems are people having with their Mazaas?
Here's a list of problems I've noticed across the net:
Low battery life (4 - 6 hours at most).
Inability to connect to CDMA networks
Can't use HTC Connection Setup - hence no 3g/mms on certain networks
Inability to connect to certain GSM networks - lack of a valid IMEI
Frequent restarts/hangs [2 - 3 per day in some cases]
Each of these are frustrating faults.
Here' to hoping that the hundreds of DEVELOPERS with Mazaas can put in a concerted, collective effort and get this going. EVERY other phone has been unlocked/tweaked/improved upon, so why not a limited edition developer-exclusive device?
Thanks for summarizing the various versions. As developers, with a concerted effort, we should be able to resolve the issues and make it work for us.
I think most people sold the device, even if this wasn't allowed, at least for the first batch (not those won, but those requested for mango/gyro dev)
I had hopes battery problems where in a faulty battery...
even if they're sold, someone's still using them!
And the battery problems were too widespread (more than half a dozen cases) for me to discount.
the IMEI problem on the other hand was in a single case - mine.
abhilaksh said:
even if they're sold, someone's still using them!
And the battery problems were too widespread (more than half a dozen cases) for me to discount.
the IMEI problem on the other hand was in a single case - mine.
Click to expand...
Click to collapse
That's right, but they're probably not in dev hands anymore, so chances are not very helpful hands at this, especially since there's no more access to official updates.
All summed up, since not even the gyro works correctly on mine, it's a paper weight for which I'm still waiting for import taxes refunding
As far as issues, in addition to the above:
- I cannot send/receive MMS (SMS works, though)
- No 3G (DO or 2x only)
- 2-3 crashes per day
My build is 7.1.7720.68
Sent from my Mazaa using XDA Windows Phone 7 App
I have HTC Mazaa
I have the HTC Mazaa device that exactly matches all the details given in the original post in this thread.
For me, its working perfectly, no battery problems (works for 2-3 days), no crashes at all, I can't say about 3G support problems because we don't have that in our country. The phone works perfectly fine.
I have dev unlocked the device from App Hub but would love to remove the interop lock as well...in fact thats what I came here for.
Please guide me.
Thanks.
When I first got my cdma provisioned Mazaa, it had a 7.1.7600_Main build on it. This was like the test ROM - it had the zApps. Looked to be the internal Microsoft beta for employees. I think everything worked on that, just Mango was crippled.
Does anyone have this? I flashed the ffu and the backups can't restore. It would be an interesting starting point if the oem bits are all there.
Sent from my Mazaa using XDA Windows Phone 7 App
Please guide me on I can interop-UNlock the device.
How can I update my Mazaa to 7.1.7740.16 build?
Mike48236 said:
When I first got my cdma provisioned Mazaa, it had a 7.1.7600_Main build on it. This was like the test ROM - it had the zApps. Looked to be the internal Microsoft beta for employees. I think everything worked on that, just Mango was crippled.
Does anyone have this? I flashed the ffu and the backups can't restore. It would be an interesting starting point if the oem bits are all there.
Sent from my Mazaa using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Hello there,
Currently I'm using a Mazaa sent from MS with the 7720.500 fw, It has all the zApps and the internal MS apps like FindSomeone, it has battery issues (but it's not worse than an Omnia 7 with Mango), and there are four annoying things experienced:
- volume is always a bit too loud and MP3 playback is sometimes faltering
- when you press the ON/OFF button, sometimes the screen comes back immediately after turning it off
- when you place a call, sometimes the screen turns off immediately, which can be brought back using the proximity sensor (hold close to head, then move it away)
- cannot receive MMS messages
Exact details:
OS: 7720.WM7_Main(mojobld).20110723-1640
FW: 1600.1502.7720.500
HW rev: 112.1410.2.0
Radio SW: 1.6.00.15.02
Radio HW: 8655/DDR2
Bootloader: 7.27.0.0
Chip SOC: 0.75.2.1
I'm no expert in messing with phones (only using homebrews once they become 99.999999999% safe) but if I can help in any ways I'm not breaking this phone, I can surely do my part provided I'm given step by step instructions.
To update to 7740/8701:
Use the WP7 update cab sender tool here
Okay. So, let's get this sorted: We need a ROM. MSFT has said ROM. We need MSFT to give us the ROM. So, I'm requesting everyone: Send a message to whoever your contact is in Microsoft and let them know of the many problems that everyone is facing. At the very least, ask them to provide new radios to get rid of the hardware glitches. Granted it's a test rom, all the more reason that they should actually be working on it. A phone that doesn't work as intended is more a burden than not.
abhilaksh said:
To update to 7740/8701:
Use the WP7 update cab sender tool here
Okay. So, let's get this sorted: We need a ROM. MSFT has said ROM. We need MSFT to give us the ROM. So, I'm requesting everyone: Send a message to whoever your contact is in Microsoft and let them know of the many problems that everyone is facing. At the very least, ask them to provide new radios to get rid of the hardware glitches. Granted it's a test rom, all the more reason that they should actually be working on it. A phone that doesn't work as intended is more a burden than not.
Click to expand...
Click to collapse
I'm sorry but I'm not going to be of any help in getting an updated ROM, since we are low on the supply chain. Also, the way we get each new build is by getting a new phone. (Send back old one, get one with newer software.)
I have an HTC Mazaa, running 7720. Everything is ok for a dev phone, I have no serious problems with it, except EDGE/GPRS not working and speaker emitting a loud tone when I'm calling a number outside my network. I'm thinking of installing the new updated build. How should I proceed exactly? Should I use the cab sender tool? I also want to mention that the phone is not dev unlocked, I'm still waiting for a student unlock. Thanks.
download the cab sender.
download the cab.
place the cab in the same folder as the cab sender.
run the cab sender.
send the cabs to the phone.
you're done.
I tried to update my HTC Mazaa and I got an error at the first restart. But, after that I typed *#06# on the Phone hub and I get this IMEI: 00A100000794C***.
I did it again, but this time, with my SIM card inside the phone. Unfortunately, I got the old IMEI message: Failed.
***
Even after all could not update my smartphone:
Verificando o status do telefone: Completed in 2,01 seconds
Verificando requisitos do sistema: Completed in 0,11 seconds
Fazendo o download de atualizações: Completed in 2,87 seconds
Verificando requisitos do sistema: Completed in 0,01 seconds
Transferindo atualizações: Completed in 24,65 seconds
Preparando para instalar: Completed in 46,16 seconds
Reiniciando o telefone: Completed in 231,04 seconds
Instalando atualizações: Completed in 70,15 seconds
Verificando o status do telefone: Completed in 0 seconds
Reiniciando o telefone: Completed in 34,28 seconds
Concluindo atualizações: Completed in 20,04 seconds
Error:
Update device 53d261df - cd29c761 - 4fe43c2f - 733020be Complete with error code
: 80180048, error message: Falha ao instalar IU (Image Update) devido a um erro.
■
╚══════» Done
Is there anyone on xda-devs to help us update our HTC Mazaa and also do the interop-unlock?
Mazaa ROM
Hmm...
Here.
http://hotfile.com/dl/135477621/ed2186c/FlashClean.zip.html
That's an FFU.
Which cab should I use? Or which is the recommended one? Thanks.
Thankyou for that FFU
@abhilaksh Thankyou for that FFU file it saved me from alot of messing around. So happy to get my Mazaa back in working order. It broke on me a few months ago and ive been though hell trying to get the bugger fixed. It just got stuck on the mobile operator screen.
imgur(dot)com/oBH9M
Even had it sent off to UK repair center for them to send it back in the same condition (Idiots). I was just about to send it off to a US repair center when i did some more searching. It worked a treat, really straightforward as well.
If anyone else is a noob in the same situation as i way id recommend these simple instructions:
1. Install Zune Beta Client (beta includes the UpdateWP tool)
2. Install the SetupUpdateWp.exe to get the tool
3. Follow these instructions to flash your phone
mobilitydigest(dot)com/ms-instructions-on-how-to-flash-a-windows-phone-7-device/
Thanks again, Rob
This is only confirmed working for the AT&T Lumia 1520 and may work as is for other phones but also might require tweaks to the XML (see below). It is very possible to brick your phone with this. Your mileage may vary!
From a high level this works by using FiddlerCore to intercept the traffic going to the Microsoft WPflights server that controls the Insider app and responds with our own custom data. The app accepts registry editing information from the web responses and acts upon that. This allows us to write stuff to select locations in the registry. In the case of the Windows 10 Preview, it appears to only look for your phone's PhoneManufacturerModelName to decide if it should be offered previews. Windows Update also checks this value. Other devices like Samsungs or HTCs may need different settings. My phone did revert to it's factory values after Windows 10 was installed (I actually think it might have done it after Windows 8.1 was installed but it continued with 10 nonetheless).
1. For the Lumia 1520 (and other phones?) reset your phone using the Windows Phone recovery tool. I recommend not logging in and setting everything up yet and just waiting til the end and doing a reset and letting it restore after you’re on Windows 10. This may not be required for your device but most likely is due to the space issue cited by Microsoft. You can see your available space in the About menu of the Windows Insiders app. Before resetting mine was ~200mb and after it was ~600mb. You can try without resetting but may get an error after it tries to download and install the update.
2. Install the [url=http://go.microsoft.com/fwlink/?LinkId=522524]Windows Insider app on your phone (you will need to have a store account configured)
3. Open the insiders app and go to the about options in the app bar and screenshot/make notes/email the settings to yourself. You may need this later.
4. Download and extract the WPInsidersHacks app (attached to this post) to your computer
5. Start the WPInsiderHacks app on pc, approve any firewall requests
6. Connect to the same WiFi that your PC is on. Edit the settings for the WiFi connection to turn on the Proxy and set it to use the PC’s IP address and enter 8877 for the port
7. Open Internet Explorer on your phone and navigate to http://[pc.ip.add.ress]:8877 where [pc.ip.add.ress] is the IP address of the PC running the WPInsidersHacks app
8. Tap on the link at the bottom to the fiddler root certificate
9. When prompted click open and then install to trust the cert and ok at the confirmation
10. Run the Windows Insider app and tap get preview builds
11. Tap on which custom action you’d like to perform. In my case I hit "Set to ATT Lumia 635" and click the arrow at the bottom
12. Accept the agreement and click the check mark at the bottom. the app will close
13. Now clear your proxy settings and run the insider app again
14. Tap get preview builds and login with your Microsoft account
15. Select the fast branch (if you’re reading this of course you want the fast branch) and click the arrow at the bottom
16. Go into the phone settings and check for updates. With any luck you should have Windows 10 there for you to install. On my AT&T 1520 it had to do 8.1 first but it kept going to 10 after 8.1 installed (had to check for updates again)
17. You’ll probably want to go into the settings and do another reset and then log into the phone and let it restore your previous data
The Windows Insider options are populated from the WPFlights.xml file. Feel free to edit/add stuff. I've experimented with writing to other keys but had mixed results. I wasn't able to write to the Software\Microsoft\Settings\{1DEF9B7D-2322-40eb-A007-16A75D5CDA6F} for example (seemed to not like the curly braces?). It should have all the same permissons as the preview for developers app. You'll just need to run the WPInsiderHacks app on your PC and point your phone's proxy settings to it if you want to go back and set something again (such as enabling tethering).
I just used this to install the TP on my Lumia 930 and .. it worked like a charm! phone is booting, OS is working! Thank you very much for the work you put into this! Really excited to try out the Preview now..
Edit: I did change the target device ID from ATT though.
Confirmed working for the Lumia 930
Confirmed working for the Lumia 920
I will try tomorrow on Lumia 520 and post result.
Not working on my Lumia 535
tried it on a Lumia 535. After Setting no proxy again the Windows Insider app shows that there is no update available.
the about-setting Shows RM-975 correctly instead of RM-1089, but I think the FW Version needs to be changed too.
Does anyone know a fix? Tried it several times by now.
LogString: DefaultCertMaker: GetRootCertificate() did not find the root in t
he Windows TrustStore.?
error0x0000034 said:
tried it on a Lumia 535. After Setting no proxy again the Windows Insider app shows that there is no update available.
the about-setting Shows RM-975 correctly instead of RM-1089, but I think the FW Version needs to be changed too.
Does anyone know a fix? Tried it several times by now.
Click to expand...
Click to collapse
Which carrier are you on? Sometimes you have to use device information for a phone on the same carrier as you're on for it to work.
I tried this with both a 520 and a 920. Everything works fine until I tap Get preview builds. I get the no builds message, but I know it's using the proxy because the WPInsiderHacks window gives this message:
** LogString: !SecureClientPipeDirect failed: System.IO.IOException Authenticati
on failed because the remote party has closed the transport stream. on pipe to (
CN=login.live.com, O=DO_NOT_TRUST, OU=Created by http://www.fiddler2.com)
** LogString: !SecureClientPipeDirect failed: System.IO.IOException Authenticati
on failed because the remote party has closed the transport stream. on pipe to (
CN=sn3301.storage.live.com, O=DO_NOT_TRUST, OU=Created by http://www.fiddler2.co
m)
Click to expand...
Click to collapse
Both devices get exactly the same result.
EDIT: I should clarify something: both the 920 and the 520 get this script. The 920 differs a bit on the device itself. Instead of going directly to the no builds page, an error pops up that says:
Server error
A connection error prevented us from downloading programs for you. Please check the date/time of your device and its network connection and try again.
Click to expand...
Click to collapse
Lumia 920
OK certificate installed
Windows insider no change ?
What would the registry entry for MOID be?
I have a non AT&T carrier, and I want to change that entry to be AT&T
Tried it on my Lumia 530 don't work i get we weren't able to find a preview build for you please confirm
Working fine on my 920 now.
I just installed. Working fine here on my Lumia 720.
For those asking, I've found you absolutely have to modify the WPFlights.xml PhoneManufacturerModelName to one that matches the carrier your device is from. In my case, I have a //Build/ (Rogers Canada) Lumia 920, and a Hong Kong unlocked 620 & 1520.
I managed to spoof the build check by using the following:
Unlocked/Hong Kong: RM-1027_1007
Rogers/Canada: RM-985_1004
http://twitter.com/stroughtonsmith/status/566460948291260417
Also, wiping the devices first /with the Windows Phone Recovery Tool/ (not Reset in Settings->About) for the most part isn't optional; only the 920 for me had enough space to install without doing that
Hope this helps
stroughtonsmith said:
For those asking, I've found you absolutely have to modify the WPFlights.xml PhoneManufacturerModelName to one that matches the carrier your device is from. In my case, I have a //Build/ (Rogers Canada) Lumia 920, and a Hong Kong unlocked 620 & 1520.
I managed to spoof the build check by using the following:
Unlocked/Hong Kong: RM-1027_1007
Rogers/Canada: RM-985_1004
http://twitter.com/stroughtonsmith/status/566460948291260417
Also, wiping the devices first /with the Windows Phone Recovery Tool/ (not Reset in Settings->About) for the most part isn't optional; only the 920 for me had enough space to install without doing that
Hope this helps
Click to expand...
Click to collapse
Hi, would you be able to upload your WPFlights.xml for me to have a look at what you have changed. For me it's not working. Cheers.
ajay003 said:
Hi, would you be able to upload your WPFlights.xml for me to have a look at what you have changed. For me it's not working. Cheers.
Click to expand...
Click to collapse
You just need to change the phonemanufacturermodel to whatever phone that supports windows 10 from your carrier/region.
ajay003 said:
Hi, would you be able to upload your WPFlights.xml for me to have a look at what you have changed. For me it's not working. Cheers.
Click to expand...
Click to collapse
The line in the screenshot is what you'd need to change; nothing too complicated, but finding a valid model for your phone's carrier is the hard part (took me a lot of Googling to find the two I needed), hence why I posted mine
stroughtonsmith said:
The line in the screenshot is what you'd need to change; nothing too complicated, but finding a valid model for your phone's carrier is the hard part (took me a lot of Googling to find the two I needed), hence why I posted mine
Click to expand...
Click to collapse
Not working for me. I'm having Lumia 920 and the carrier rom is RM-821_apac_australia_new_zealand_218. Here's my file attached. Am i doing something wrong?
What exactly did you google ? because the i am with is Telstra in Australia they have a prepaid Nokia Lumia 635 so where would i get the PhoneManufacturerModelName ?
German, Unlocked 830: RM-984_1002
For googling help: some forums automatically include the model variant in signatures of members, I just started with RM-984_10XX for 830 and tried increasing numbers for XX in order to find one that was posted a lot on german forums. Good luck!
ajay003 said:
Not working for me. I'm having Lumia 920 and the carrier rom is RM-821_apac_australia_new_zealand_218. Here's my file attached. Am i doing something wrong?
Click to expand...
Click to collapse
Yeah, you just placed RM-821_apac_australia_new_zealand_218 into the XML - that's your existing device. You need to use the correct form for a 63x/730/830 on same carrier, not your existing 920. That's the hard part to find.
My 1520 was "RM-937_apac_hong_kong_222", which I substituted for "RM-1027_1007" (a Hong Kong Lumia 636) - from what I could tell it doesn't need the "apac_hong_kong" part, but it needs the valid number at the end, and I don't know an easy way to find out what that should be (took me 50 mins of Googling to find that one).
---------- Post added at 12:13 PM ---------- Previous post was at 12:12 PM ----------
th0mas96 said:
German, Unlocked 830: RM-984_1002
For googling help: some forums automatically include the model variant in signatures of members, I just started with RM-984_10XX for 830 and tried increasing numbers for XX in order to find one that was posted a lot on german forums. Good luck!
Click to expand...
Click to collapse
lmfao. I was far too lazy to try bruteforcing it, but again, that's why I posted my working ones!
Hello all,
I'm in a bit of a pickle with my SWR50 that I got not long ago but as of now haven't been able to use.
As far as I've established it's got a pre-release software version on it, and not sure if that itself is the problem but I can't pair it successfully to anything and can't use it.
Tried to read up as much as I could on how I could sort this, but there's way too much info out there, too many methods because people mainly were in it to get more out of their gear, roms etc, and as I haven't had much previous experience with rom updates (unless there was some step by step, easy to follow stuff) I'm stuck.
The problem:
Pairing with phone –> phone finds watch, pairing starts
*just a minte* goes on for ~3 minutes than says: “can’t connect to the internet, swipe for options" (make sure phone has net, go to help website, retry, abort)
Then it just says Tetra BF1E – install android wear on your phone (on long press of power button I can access limited menu)
About phone:
Model: Tetra
Software Version: 4.4W
Build Number: Tetra-userdebug 4.4W KGW29E 1031 test-keys
If I try to update via Xperia Companion I eventually get a:
Startup error
"An error occurred while preparing to update your device. Device is unchanged. Try later or contact sony support"
UEGetPhoneMissingInfo
tetra 1291-6001
2.2.5.0 / Win8 64bit /wiin32 /US
Also tried factory restore from within the watch (both from menu and startup malarkey), but it didn't change anything regarding connectivity success.
Sorry for the lots of info, as a problem solver myself I like to get a good view into what's wrong & what's been tried.
All I want is to somehow upgrade to an OS that works - I don't have preferences other than I don't need anything flashy (5.1 would do), just something that offers decent battery life - I'd only use the watch to get notifications of messages, calls etc.
Any advice of what steps I should take so I can read up on them, would be appreciated!
Flash this via TWRP and after that try to restore watch from Xperia Companion