Hello all,
So after updating my Lumia 710 from Rogers, in the "About" screen of the Diagnostic Tool I see that I am on FW revision 1600.3007.7740.11465. This is a few versions behind what seems to be the latest version out there for unlocked variants of the phone...
So I found this page:
http://www.wpcentral.com/hack-t-mobile-lumia-710-flash-windows-phone-os-8107-new-firmware
Which claims that they have flashed the latest Indian firmware (8107.12070) for the RM-803 variant of the phone onto the T-Mobile (RM-809) version. However I am somewhat reluctant to try flashing an RM-803 image onto an RM-809, especially due to the fact that they support different 3G bands. What do you guys think?
Alternatively, I can see in Navifirm+ that the latest available image for the RM-809 is the Australian 8107.12050, so that might be a safer choice?
This will be the first time I try to manually update a Windows Phone... So what do you guys think? I really want to update it since there are some GMail syncing issues on the build that I'm running now.
I updated my lumia 710 from rogers (RM-809) with the RM-803 indian rom 12070 with no problems! Nothing is missing and it's now unbranded If you follow this guide it's really simple!
Thanks, Simon!
After reading your post, I gave it a shot and everything seems to be working fine I wonder if we should be seeing any battery life improvements like the Lumia 800 users?
Just something I should mention, though: I unlocked my phone so that I could use it on Wind Mobile, but after going through the flashing process, the phone became locked again so I had to re-enter my unlock code.
I didn't know that it was even possible for a phone to become locked again, after already having been unlocked...
I am thinking about getting a Lumia 710, and I am really surprised that you guys were able to flash a firmware from another RM-### without bricking the phone.
I currently own the X7 (RM659) from the Rogers and I was told not to flash the Belle firmware from the X& (RM707) since the phone will get bricked.
Nonetheless, thanks a lot for the info.
Which software do you use to flash? Phoenix or WP7 requires other tools? Never mind I found the post detailing how to debrand it.
The weird thing is... I tried to downgrade from the Indian (RM-803) 1070 build to the Australian (RM-809) 1050 build, and I wasn't able to...
It seems there is a small battery bug (Diagnostic tool doesn't display battery info) so that's why I tried to install the Australian one instead.
Whenever the next update comes along, I hope I'll be able to switch back to an RM-809 build... It seems like the safe way to go.
xsever said:
I currently own the X7 (RM659) from the Rogers and I was told not to flash the Belle firmware from the X& (RM707) since the phone will get bricked.
Click to expand...
Click to collapse
Normally you shouldn't... But the only reason I did it is because other people had successfully done it.
Also keep in mind that Symbian phones seem to be a little pickier - you can brick them just by trying to downgrade to the previous OS.
Edit: Well that's weird... My Battery Status randomly started working!
Edit #2: I just remembered I did a battery pull, so that may have had something to do with why it is fixed now...
I never knew it was possible to downgrade the OS for Nokia phones whether it is Symbian or WP.
Would an unlocked T-Mobile Lumia 710 work fine on the Rogers network? Do the GSM bands match?
It would indeed. The RM-809 model supports HSPA 850/1700/1900/2100. So it will work on any of the North American operators. (excluding the cdma operators like Verizon and Sprint, of course)
Actually, I bought my Lumia 710 from Rogers, unlocked it, and I am using it on Wind Mobile now (same hspa band as t-mobile).
Edit: I hope you're right about the downgrading thing, since that would mean that the reason I wasn't able to flash back to RM-809 was because of the fact that it's a downgrade, as opposed to something being messed up on the phone! I guess I'll find out when the next update comes along.
I am 100% sure you cannot downgrade Nokia firmwares without bricking the phone. I read about one method somewhere, but it was very complicated.
If I were you, I wouldn't be worried, now that you have the RM-803 firmware, next time there is an RM-803 update, you should be able to update via Zune/Nokia Suite without having to go through the method you used at the beginning of the post.
Now your phone is an RM-803 so Zune will recognize it as so and update it normally hence the beauty of debranding where you don't have to wait for operators.
Hello guys i'm new to the site.
I want it to ask if i could flash my lumia 710 (t-mobile US) with the RM-809 VAR T-MOBILE BLACK version that appears in navifirm.
my nokia is DLOAD. Would that be a problem?
kortvolker said:
Hello guys i'm new to the site.
I want it to ask if i could flash my lumia 710 (t-mobile US) with the RM-809 VAR T-MOBILE BLACK version that appears in navifirm.
my nokia is DLOAD. Would that be a problem?
Click to expand...
Click to collapse
I was wondering that too.
Also, there's two T_Mobile 8773 fw's listed for each color phone. One appears to have been released 06/04/12. The other 05/29 . What's the differences?
Hello friends...,
i need to flash a lumia 900, rm-832 without a dload osbl. i can only access rm 808 from the ATF team.
please help!
thanks.
First, this is not an ATF support forum, although we do have at least one ATF developer among our members.
With that said - bootloader-wise, the RM-808 and RM-823 are the same. You can safely use RM-808 mode with the RM-823.
Note that a new release of ATC is expected soon, which will be able to install an unlocked Qualcomm OSBL. It's currently being tested internally. See the "recover/upgrade" thread.
If you accidently got a prototype Lumia device with an abnormal firmware installed, you can't use Nokia Care Suite to flash it.
Here's the characteristics of a typical Lumia prototype devices:
1. "proto.nokia.com" or "proto.microsoft.com" printed on the screen.
2. "PROTOTYPE, Property of Nokia" or "PROTOTYPE, Property of Microsoft Mobile" and something else engraved on the back cover.
3. IMEI started from 0044.
4. Lots of output info on the splash screen when booting up phone.
5. "Not for Resale" on the bottom left corner when entering OS.
6. Lots of Apps starting from letter "z", such as "zNocenter", "zBattInfo", "zFeedbackHub".
7. App "Field Medic" included.
8. The splash screen is neither Microsoft nor Nokia nor Network Carrier logo.
9. Boot into MMOS directly, in other words, the interface has a Microsoft logo on it, with some info of firmware revision, and the text "Modem offline" or "RF inactive" or something.
10. Boot into Recovery mode directly without pressing Volume Up, in other words, the interface has a white cog and a lightning.
11. Back cover has few opened hole for testing purposes.
What if you got one?
1. If it's finally released on market, you can install retail firmware into it with this command:
thor2 -mode uefiflash -ffufile <path_to_ffu_file> -skip_signature_check -skip_id_check -do_full_nvi_update -do_factory_reset -reboot
This command can be only used on prototype devices.
You can't use flashing command for retail devices on prototype devices and vice versa.
But, please make full emmc dump with dd command before flashing to prevent from flight mode loop because of baseband. If the baseband has serious problems, after you flash retail firmware on a prototype device, you'll get a flight mode loop, and the IMEI is probably started from "86483-".
2. If it's a cancelled device such as McLaren, Honjo, you can't install retail firmware for any similar devices on it.
3. If the prototype device is really early, the specification is probably different from retail device, for example, some earlier Lumia 920 prototype with Windows Phone 7 button doesn't have as much storage space as retail have.
4. Some prototype devices has their defects because of design, for example, Lumia 636 B2 has a defect that you can't recharge your phone directly, or the emmc will get locked to read-only state, because some capacitors that exists on retail devices are missing.
5. Prototype Lumia eMMCs are not as reliable as retail devices. They're really slow when you got them, and it's nearly impossible to make eMMC dump because the low transfer rate. Few of them are easily fried up.
6. Of course, you can salvage a part for your retail device's replacement, for example, the screen with "proto.nokia.com" or "proto.microsoft.com" printed.
7. DO NOT SEND YOUR PROTOTYPE DEVICE TO SERVICE CENTER IF THE MANUFACTURER HADN'T SOLD THEM IN PUBLIC PREVIOUSLY, OR THEY'LL TAKE YOUR PROTOTYPE DEVICE AWAY WITHOUT RETURN AND CHECK THE SOURCE OF YOUR PROTOTYPE DEVICE.
I have a Lumia 930 Prototype, but it was updated to insider firmware and was bricked. How can I fix it? I've never seen before something like your guide. Best regards.
Flash with WP Image Designer, WPinternals or Nokia Care Suite - dead flash
Prototypes WP Microsoft
Hello all !!! Please a need a help, I have many prototypes by microsoft:
1 Lumia 950XL / HWID3030 / Build F3 DS RD / RM-1116 / Code 059X462
2 Lumia id334-2 / HWID1130 / Build B1 BRZ RD / RM-1151 / Code 059X2J7
2 Lumia 950 / HWID2161 / Build F2 ROW DS RD / RM-1118 / Code 059X038
1 Lumia ? / HWID2110 / Build F2 ROW RD / RM-1104 / Code 059X034
1 Lumia 640XL / HWID ? / RM-1065 / Code 059W7F5
1 Lumia id333-5/ HWID2020 / Build F2 BRZ DS RD / RM-1129 / Code 059W8F1 08/2015
1 Lumia id333-5/ HWID1020 / Build B1 BRZ / RM-1129 / Code 059W8F1
And I like change the all R&D Firmware to User final firmware, someone have any instructions to me change this SW...thanks a lot!!!
FieldTesterBR said:
Hello all !!! Please a need a help, I have many prototypes by microsoft:
1 Lumia 950XL / HWID3030 / Build F3 DS RD / RM-1116 / Code 059X462
2 Lumia id334-2 / HWID1130 / Build B1 BRZ RD / RM-1151 / Code 059X2J7
2 Lumia 950 / HWID2161 / Build F2 ROW DS RD / RM-1118 / Code 059X038
1 Lumia ? / HWID2110 / Build F2 ROW RD / RM-1104 / Code 059X034
1 Lumia 640XL / HWID ? / RM-1065 / Code 059W7F5
1 Lumia id333-5/ HWID2020 / Build F2 BRZ DS RD / RM-1129 / Code 059W8F1 08/2015
1 Lumia id333-5/ HWID1020 / Build B1 BRZ / RM-1129 / Code 059W8F1
And I like change the all R&D Firmware to User final firmware, someone have any instructions to me change this SW...thanks a lot!!!
Click to expand...
Click to collapse
can you show picture of ? and id33x devices?
hikari_calyx said:
If you accidently got a prototype Lumia device with an abnormal firmware installed, you can't use Nokia Care Suite to flash it.
Here's the characteristics of a Lumia prototype devices:
1. "proto.nokia.com" or "proto.microsoft.com" printed on the screen.
2. "PROTOTYPE, Property of Nokia" or "PROTOTYPE, Property of Microsoft Mobile" and something else engraved on the back cover.
3. IMEI started from 0044.
4. Lots of output info on the splash screen when booting up phone.
5. "Not for Resale" on the bottom left corner when entering OS.
6. Lots of Apps starting from letter "z", such as "zNocenter", "zBattInfo", "zFeedbackHub".
7. App "Field Medic" included.
8. The splash screen is neither Microsoft nor Nokia nor Network Carrier logo.
9. Boot into MMOS directly, in other words, the interface has a Microsoft logo on it, with some info of firmware revision, and the text "Modem offline" or "RF inactive" or something.
10. Boot into Recovery mode directly without pressing Volume Up, in other words, the interface has a white cog and a lightning.
11. Back cover has few opened hole for testing purposes.
What if you got one?
1. If it's finally released on market, you can install retail firmware into it with this command:
thor2 -mode uefiflash -ffufile <path_to_ffu_file> -skip_signature_check -skip_id_check -do_full_nvi_update -do_factory_reset -reboot
This command can be only used on prototype devices.
You can't use flashing command for retail devices on prototype devices and vice versa.
But, please make full emmc dump with dd command before flashing to prevent from flight mode loop because of baseband. If the baseband has serious problems, after you flash retail firmware on a prototype device, you'll get a flight mode loop, and the IMEI is probably started from "86483-".
2. If it's a cancelled device such as McLaren, Honjo, you can't install retail firmware for any similar devices on it.
3. If the prototype device is really early, the specification is probably different from retail device, for example, some earlier Lumia 920 prototype with Windows Phone 7 button doesn't have as much storage space as retail have.
4. Some prototype devices has their defects because of design, for example, Lumia 636 B2 has a defect that you can't recharge your phone directly, or the emmc will get locked to read-only state, because some capacitors that exists on retail devices are missing.
5. Prototype Lumia eMMCs are not as reliable as retail devices. They're really slow when you got them, and it's nearly impossible to make eMMC dump because the low transfer rate. Few of them are easily fried up.
6. Of course, you can salvage a part for your retail device's replacement, for example, the screen with "proto.nokia.com" or "proto.microsoft.com" printed.
7. DO NOT SEND YOUR PROTOTYPE DEVICE TO SERVICE CENTER IF THE MANUFACTURER HADN'T SOLD THEM IN PUBLIC PREVIOUSLY, OR THEY'LL TAKE YOUR PROTOTYPE DEVICE AWAY WITHOUT RETURN AND CHECK THE SOURCE OF YOUR PROTOTYPE DEVICE.
Click to expand...
Click to collapse
Hi Hikari,
I have "accidentally" got a 950 proto F2. It seems to be running RTM software, i don't have any of these z- apps you list above or field medic.
Are there any issues I should be aware of with these? Can I reset it?
Cheers
madb1lly said:
Hi Hikari,
I have "accidentally" got a 950 proto F2. It seems to be running RTM software, i don't have any of these z- apps you list above or field medic.
Are there any issues I should be aware of with these? Can I reset it?
Cheers
Click to expand...
Click to collapse
Hi @hikari_calyx, any chance you can get back to me on this?
I would like to test all the phone functions but the phone isn't recognised by Lumia Phone Test Application (it's know it's a Lumia 950 RM-1104, but won't test it). Do you know how to get LPTA to work with these prototypes or know an alternative method of testing all the phone functions easily?
Cheers
madb1lly said:
Hi @hikari_calyx, any chance you can get back to me on this?
I would like to test all the phone functions but the phone isn't recognised by Lumia Phone Test Application (it's know it's a Lumia 950 RM-1104, but won't test it). Do you know how to get LPTA to work with these prototypes or know an alternative method of testing all the phone functions easily?
Cheers
Click to expand...
Click to collapse
i have few prototype fw of 950 , if you device really is prototype. reply this comment. thank
thinhx2 said:
i have few prototype fw of 950 , if you device really is prototype. reply this comment. thank
Click to expand...
Click to collapse
Hi @thinhx2, yes my 950 really is a prototype. It says Proto F2 on the inside sticker and the IMEI starts 00440. It says proto.microsoft.com on the front and Not for Resale on the boot screen.
Cheers
madb1lly said:
Hi @thinhx2, yes my 950 really is a prototype. It says Proto F2 on the inside sticker and the IMEI starts 00440. It says proto.microsoft.com on the front and Not for Resale on the boot screen.
Cheers
Click to expand...
Click to collapse
My telegram: +84904399978 . you're welcome
---------- Post added at 03:43 PM ---------- Previous post was at 03:41 PM ----------
madb1lly said:
Hi @hikari_calyx, any chance you can get back to me on this?
I would like to test all the phone functions but the phone isn't recognised by Lumia Phone Test Application (it's know it's a Lumia 950 RM-1104, but won't test it). Do you know how to get LPTA to work with these prototypes or know an alternative method of testing all the phone functions easily?
Cheers
Click to expand...
Click to collapse
Look like your proto flashed retail fw
Full emmc backup of 950
https://mega.nz/#F!zCQGkawI!Iau0OKKY02HjXy2r56iW-Q
Does anyone have a prototype firmware dump for Lumia 1320?
Ranomez said:
Does anyone have a prototype firmware dump for Lumia 1320?
Click to expand...
Click to collapse
You have 1320 prototype?
thinhx2 said:
You have 1320 prototype?
Click to expand...
Click to collapse
I will buy one but it was already flashed to retail firmware without a dump.
Ranomez said:
I will buy one but it was already flashed to retail firmware without a dump.
Click to expand...
Click to collapse
Flashed retail firmware. ??????
Now it will same retail device ??? nothing special
thinhx2 said:
Flashed retail firmware.
Now it will same retail device nothing special
Click to expand...
Click to collapse
Which is why I asked if anyone has a dump of the prototype firmware.
Ranomez said:
Which is why I asked if anyone has a dump of the prototype firmware.
Click to expand...
Click to collapse
1320 with original proto firmware hard to find now. Almost is reflashed retail firmware to resale
thinhx2 said:
1320 with original proto firmware hard to find now. Almost is reflashed retail firmware to resale
Click to expand...
Click to collapse
I have the 1320 now and I think I did a mistake, it was already on a retail firmware but updates failed to install so I flashed to a different FFU using the command in the OP and now... I seem to have lost mass storage mode although WPI says the bootloader is unlocked.
I did make a full dump with Win32DiskImager before flashing the FFU so I do have the SBL3 needed to enable it again so I thought about trying to enable it again using the bootloader unlock option from WPI... Is WPI able to extract the SBL3 from the raw image of the device if I point it towards it for the SBL3 or do I have to first extract the SBL3 myself?
ranomez said:
i have the 1320 now and i think i did a mistake, it was already on a retail firmware but updates failed to install so i flashed to a different ffu using the command in the op and now... I seem to have lost mass storage mode although wpi says the bootloader is unlocked.
I did make a full dump with win32diskimager before flashing the ffu so i do have the sbl3 needed to enable it again so i thought about trying to enable it again using the bootloader unlock option from wpi... Is wpi able to extract the sbl3 from the raw image of the device if i point it towards it for the sbl3 or do i have to first extract the sbl3 myself?
Click to expand...
Click to collapse
no. . i not sure . i dont know which firmware installed on you phone.
Can you send me compressed file of your backup emmc file?
At the moment. NO SBL3 FOR 1320 .because all 1320 proto flashed retail. We need sbl3 from proto firmware to unlock for retail. If your backup file is prototype. It good
thinhx2 said:
no. . i not sure . i dont know which firmware installed on you phone.
Can you send me compressed file of your backup emmc file?
At the moment. NO SBL3 FOR 1320 .because all 1320 proto flashed retail. We need sbl3 from proto firmware to unlock for retail. If your backup file is prototype. It good
Click to expand...
Click to collapse
The firmware is retail but the SBL3 was still prototype on it before I messed around with it.
Will send it in a few days when I get back home.
Ranomez said:
The firmware is retail but the SBL3 was still prototype on it before I messed around with it.
Will send it in a few days when I get back home.
Click to expand...
Click to collapse
Thank ?
Hello ! Any way to get my Lumia 550 straight to FCU starting from 10586.494? I mean skipping the two steps in the middle (AU and CU). There could be a way using Over the Cable Updater or is there the firmware itself somewhere in the web which I can flash?
Jeff Weight said:
Hello ! Any way to get my Lumia 550 straight to FCU starting from 10586.494? I mean skipping the two steps in the middle (AU and CU). There could be a way using Over the Cable Updater or is there the firmware itself somewhere in the web which I can flash?
Click to expand...
Click to collapse
Windows 10 Mobile has no planned feature updates past FCU. The latest build should be 15254. Last I checked, the Lumia 550 continues to be supported thru the end of this year. In April, all users running build 15063 were bumped to 15063.1029. My Lumia 830 received that update (despite being shut out of the feature2 branch). You should check for that update first. It would be best to avoid that update on a metered connection.
Microsoft Support Document
Important Information Regarding Windows 10 Mobile Support - Windows Central
furboom1240 said:
Windows 10 Mobile has no planned feature updates past FCU. The latest build should be 15254. Last I checked, the Lumia 550 continues to be supported thru the end of this year. In April, all users running build 15063 were bumped to 15063.1029. My Lumia 830 received that update (despite being shut out of the feature2 branch). You should check for that update first. It would be best to avoid that update on a metered connection.
Microsoft Support Document
Important Information Regarding Windows 10 Mobile Support - Windows Central
Click to expand...
Click to collapse
Yes I know that. I was looking for a way to avoid to get through the annoying process of update from the old November Update (because I had to recover my Lumia with WDRT) and jump straight to FCU. So flashing some FCU firmware or other ways...
Jeff Weight said:
Yes I know that. I was looking for a way to avoid to get through the annoying process of update from the old November Update (because I had to recover my Lumia with WDRT) and jump straight to FCU. So flashing some FCU firmware or other ways...
Click to expand...
Click to collapse
There is no way unless you would have someone to dump a custom ROM supporting your device from the 550 somewhere at like version 15063.297 at least or another later supported version if possible. You could always attempt to dump one your self in the event you have to completely Reset with WDRT on that device in the future. But that is up to you...You would need to read up on the Window Phone internals tool and create a custom rom that way.
edit: Actually I just looked and seems certain variants of the 550 have FW revisions all the way up to OS 10.0.10586.494. If you want further than that a custom rom is the only option.