yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Q&A, Help & Troubleshooting] Sithhy™:
Hello all Note 3 users [emoji4] I'm currently using a HTC One M7 running on CM12.1 & love it (mainly because of the stereo speakers), but I want to get a new phone because this one is getting old & boring for me... I'm debating between choosing the LG G3 & Galaxy Note 3... The biggest thing is that I don't really like screens larger than 5" but in today's standards getting a good ~5" phone, that has good developer support is getting harder & harder to do... So as I said, I'm torn between the Note 3 & G3 (have other phones selected too, with a 5" screen max, but they're kinda close to End Of Life...) . One of the reasons to get the Note 3 over G3, is that the Note 3 has great ROM support from xda, which is the biggest thing for me while choosing a phone [emoji1] (I think it has a bigger ROM support than the G3 actually, but I could be wrong). I also like the S-Pen, because it's a cool addon that helps with the big screen (but probably won't use it for more than just "replacing" my finger). I've seen that there are 2 versions of the Note 3 with a Snapdragon & Exynos processor, so I have a question to that... Is there any other big difference between them or is it the same phone with just a bit different stuff in hardware? Also, do both of them have the same model number? I live in Poland & have seen that all of them are the N9005 variant (international version I assume?). I have also heard somewhere that tripping KNOX will make you loose your cellular data & calling, so you're left with a 5,7" MP3 player... Can someone explain me that? (Just need a basic explanation, not a in depth guide). It's gonna be hard to get used to a roof tile coming from a 4,7" screen, but I think that as time passes by, I will get used to it (atleast I hope so) Thanks for your time, by reading all of this shizzle [emoji1]
[Galaxy Note 3 Q&A, Help & Troubleshooting] ithehappy:
It's a no brainer for me if I were to choose between the G3 and the Note 3. While I have used both of them, and the former being one of the most pathetic mobile phone I have ever used, the latter is one of the best I have ever used, if not the best.

Snapdragon variants are N9005, that's the International versions. Exynos variants are N900X I think, at least in India. So yes, model no. will absolutely be different. Snapdragon has way more XDA support, so I will suggest that one 100 out of 100 times. Exynos is a completely different chipset by the way, said to be faster than Snapdragon, but one can hardly notice those fastness anyway.

As soon as you root the phone KNOX will be tripped, period, and there is no way to revert to official status once its tripped. But I think there are few ways where you can keep KNOX at 0x0 and still root, but as I never cared about KNOX I never searched.

At the end of the day, ask yourself, whether you want to get a phone of 2013 in 2016 or not, I don't think investing behind it is a wise idea. I will suggest you to go for Note 4, which's price is dropping since Note 5 launch and will be a significant upgrade from your M7 and miles better than Note 3 in terms of camera and display.

Rest your choice.
[Galaxy Note 3 Q&A, Help & Troubleshooting] pete4k:
Just for the sake of clarity: tripping Knox DOES NOT affect usability of the phone except for secure mode and if you're planning to root, that secure mode would be moot point anyway. Also you may get hard time getting warranty repairs with tripped Knox, but the phone may be out of production and possibly out of warranty already. Also some programs check for root and refuse to work if present, but there are ways to root without tripping Knox and hide root as well. You need to find a model that will match frequencies used in Poland, but I can't help you with that. As far as the phone itself, I love it and I wouldn't exchange for anything else. Note 4 is a little upgrade over Note3, but nothing spectacular IMO and newest Note5 pretty much sucks without SD card and non replaceable battery.

zycze powodzenia
[Galaxy Note 3 Q&A, Help & Troubleshooting] Sithhy™:
I see... So KNOX is just a security feature that I don't have to care about, because gonna root the phone anyways [emoji1] (But eh, wouldn't even care about when I had a warranty)

Also, my One M7 is also a 2013 phone in 2016 so I don't really care about that until the phone looses developer support from xda [emoji1]

I don't really take photos with my phone & even if I do, they're like 1 or 2 per month or less... So yeah, camera isn't a big deal for me.

As for the Note 4, I don't really feel like a 2k screen on a phone is worth it anyways... Would rather stick to 1080p

Also, I get "new" phones by selling the one I had so it goes like: I sell one, I get one [emoji4] That's how I got my HTC One M7 coming from a Samsung Galaxy S [emoji1]
[Galaxy Note 3 Q&A, Help & Troubleshooting] szotaa:
If you care about AOSP roms, don't ever go for Exynos phone - half of stuff won't be working ( http://www.xda-developers.com/samsung-exynos-and-aosp-explained-a-story-of-betrayal/ ).

I also live in Poland and I use the N9005 variant, everything is working perfectly fine on CM12.1. I tripped my knox but it makes no difference.

On the other hand I really think that LG G3 has a better xda support and I think that it will have it for a longer time than a note 3, it just a newer and more popular device. However it lacks AMOLED screen which for me is a huge advantage.
[Windows Phone 8 General] cronojay:
Wow. As I am waiting for a T-Mobile logic board to come in...boom..I'll give it a shot tonight. Thanks for the post and hard work..::thumbs up::
[Windows Phone 8 General] smokin901:
Thanks Anubis23 it worked great I was able to successfully install T-Mobile ROM
[Windows Phone 8 General] sachin.gokhale:
I am almost sure, still confirming, I can flash any Lumia 640 LTE version ROM, right ? even India ROM ?
[Windows Phone 8 General] cronojay:
Thanks..worked beautifully and very easy to do
[Windows Phone 8 General] anubis23:
As far I know, any single sim variant, I am not sure if dual sim would work based on other threads based on the non att version. You can flash RM-1072 and RM-1073 Rom from any country.
[Windows Phone 8 General] Arndtgale:
Worked great thanks!
[Windows Phone 8 General] micallan_17:
Is there a method to debrand the Lumia 830 from AT&T?
[Windows Phone 8 General] boysie37:
Thanks for your excellent post. I have already upgraded my att&t Lumia 640 to windows 10 build 10586.63. Will I have to restore 8.1 before implementing your steps?
[Windows Phone 8 General] nunzio1961:
Can you have the three cab files for one Nokia Lumia 1520 AT & T?

Thank you.
[Windows Phone 8 General] smokin901:
I Think Yes

---------- Post added at 05:57 AM ---------- Previous post was at 05:53 AM ----------

I think you can flash only single SIM variant.

I was not able to flash RM-1024 Global swap rom on ATT Lumia. Other RM-1024 ROM worked for me even then I was not able to get LTE Band # 3.

I do not think there is Single SIM LTE variant of Lumia 640 in India.

Only DUAL SIM 3G,

DUAL SIM XL 3G

DUAL SIM XL LTE were launched in India.
[Windows Phone 8 General] sachin.gokhale:
Thank you for information. Could you please refer me to link which will have all product codes of Lumia 640. Also let me know exactly which CV Rom you have flashed successfully. Is 2G only mode selectable in that ? and any 4G Indian band support ?
[Windows Phone 8 General] rkdev30:
I appreciate your hard work and I am going to get an AT&T Lumia 640 this weekend to try it out. I wanted to ask, after flashing the 3 phone cabs, do I then change the product code to T-Mobile and then flash the T-Mobile rom using WDRT?

I see in the steps that the last process I needed to do was to make sure to change the product code so WDRT didn't redownload the AT&T image. I just wasn't sure if the steps were to flash the 3 cabs, flash T-Mobile rom with WDRT, then change product code; or flash the 3 cabs, change product code, flash T-Mobile rom with WDRT, then change product code again.

I apologize as I am new to flashing Lumia roms.

Thank you for any assistance.
[Windows Phone 8 General] smokin901:
Even t-mobile rom mentioned by op has option to select highest network type 2g 4g aka 3g for rest of the world and lte

---------- Post added at 12:52 AM ---------- Previous post was at 12:49 AM ----------

Flash 3 cabs

Change product code

Flash t-mobile rom
[Windows Phone 8 General] rkdev30:
Thanks for taking the time to clear it up.
[Windows Phone 8 General] boysie37:
Following from my previous post I have successfully de-branded my at&t lumia 640 and installed windows 10 build 10568.63.

Carried out steps 1-8 OK

Step 9 didn't work, ignored that.

My phone had a Product code of "RM-1073", using WPInternals I found it has a Platorm Name of "Nokia.MSM8926.P6204.1.1", from Navifirm+ I found a ROM for Australia with Product Code "RM-1074" so I downloaded the ffu file and using HxD was able to confirm it has the same Platform Code.

I then successfully flashed ROM "RM1074_02166.00000.15103.05002_RETAIL_prod_signed_1015_01EABB_000-AU.ffu" using the steps shown for flashing T-Mobile US ROM.

Have now updated to Windows 10 build 10568.63 and everything appears OK.

Thanks anubis23, excellent post, donation on the way.
[Windows Phone 8 General] sachin.gokhale:
I earlier used to download many flashes with Nokia DataPackage manager. But since last week it always says login error.
[Windows Phone 8 General] ombreman:
Thank you very much. I have sucess changing from ATT to EU rom. (also from RM-1073 to RM-1072) :good:
[Windows Phone 8 General] Petulinek:
U can download needed files on this website: http://www.mrcrab.net/nokia.html
[Windows Phone 8 General] qodexc:
Thank you anubis23 for your hard work. I've successfully flashed t-mobile rom on my att 640.
[Windows Phone 8 General] pankaj981:
Would you mind posting the instructions (in a different thread I guess?) whenever you get sometime? I have an AT&T 1520 which I can use for extracting those files.
[Windows Phone 8 General] Raheinm:
My de brand has working WiFi calling.
[Windows Phone 8 General] bibbin:
Couple of questions:

-Step 9. f. says, "Press the POWER BUTTON and hold down the VOLUME UP button till you see the lighting gear screen, and then connect your phone to the PC."

What is the "lighting gear screen?"

-Step 10 What is the "T-Mobile US Product Code?" Where does one find it?
[Windows Phone 8 General] boonesmi:
its a screen with a gear and a big lightning bolt displayed :)

and you can get the tmobile rom from mrcrab (link is listed in step 10) you use the product code so you can find the right rom. its product code 059X0P7
[Windows Phone 8 General] beastofexmoor:
Mine too. I wasn't able to Band 12 working, but I'm not 100% sure I have it in my area. I was a little intimidated by the process, but once I got in to it things were very straightforward.

"Lighting" should be "Lightning". As in lightning and thunder. Remember to hold the volume up key, but just tap the power button. Holding both will reboot the phone over and over.
[Windows Phone 8 General] juicer52:
Yes that is the product code for TMo US

If you look at the code in step 11 h on page one it is in that sample code used. Worked for me.

The Command below will change the product code of your phone from the AT&T product code, to the T-Mobile US Product Code.

Code:

thor2 -mode uefiflash -ffufile "C:\Lumia\RM-1073\RM1073_02177.00000.15203.26115_RETAIL_prod_signed_1001_023F70_TMO-US.ffu" -productcodeupdate 059X0P7 -skip_flash
[Windows Phone 8 General] pilot04:
still no wifi calling

I wonder if it's b/c I can't get step 9g to work on my ATT 640 gophone "Connect your phone to your PC, and go back to the Windows Phone Image Designer application. You should now see that the device is recognized as "Flash-able Devices: Nokia.MSM8926.P6204.1.1", which indicates that the process above has finished successfully." The designer app doesn't see my device so I just skip on to flashing with tmo rom.

I did a reload of the 3 cab files and reflashed yesterday to test. I did get wifi calling to work while on Windows mobile 8 as expected. Then I proceeded to upgrade to Windows mobile 10 and then hard reset as like some have done with their 640. Afterwards, the wifi calling doesn't work any more even though I still see the options in SIM settings to change wifi preferred settings. Would love to get wifi calling working on my rebranded 640.

Should restore back to Win mobile 8 and see if wifi works again for the brief period I got it to work yesterday?
[Windows Phone 8 General] boonesmi:
http://www.spectrumgateway.com/t-mobile-700a-spectrum
[Windows Phone 8 General] pilot04:
Per that 700 band 12 map, it looks like my area has band 12 but my rebranded 640 always default to band 4 LTE when checked in field test mode. Hopefully I can get wifi calling to work correctly on my 640 or maybe I can go back to ATT rom from my T-mo rom.

Is there a way to check the product code that is currently set on my 640? I ran that last command to set it but is there a command to confirm if it did it correctly...
[Windows Phone 8 General] Dibbyd:
So far I don't think there is a way to go back to the ATT ROM since we don't have the original cab files. To check which product code is currently set, connect your phone to your computer and open WDRT. It will tell you whether your firmware matches what is available on the server. It is using your product code to check that. So if your firmware matches, then you set the product code correctly.
[Windows Phone 8 General] boonesmi:
band 4 is a faster LTE band, so phones will give it higher priority. the only advantage of band 12 is the signal penetration and distance.

for testing purposes you can go into fieldtest -> settings -> network type: manual. then uncheck the boxes for all bands except the one you want to test (ie. band 12)

if you get no signal then you know that either band 12 isn't available where you live, or band 12 isn't working on your phone.
[Windows Phone 8 General] pilot04:
This is what I get when connecting to WDRT. Does this mean I have the Tmobile product code set correctly as all it provides is numbers?

Model: Lumia 640 LTE

Firmware version: 02177.0000.15203.26115

Operating System version: 10586.13080

Software available on Server

Firmware version: 02177.0000.15203.26115

Operating System version: 9651.15148

You have the latest software version.

---------- Post added at 03:14 PM ---------- Previous post was at 03:07 PM ----------

Great tip on band 4 being faster LTE. I'll try it out when I head into downtown this weekend and manually uncheck everything except band 12.
[Windows Phone 8 General] boonesmi:
yup 02177.0000.15203.26115 is the latest tmo firmware. so yeah product id is set correctly (otherwise it would have tried to get you to download the latest ATT firmware)
[Windows Phone 8 General] pilot04:
Thank you for the confirmation that my product code is properly set. Now I just need to figure out how to get wifi calling to work on my rebranded 640:confused:
[Windows Phone 8 General] Dibbyd:
I don't know if this will work on Win 10, but try setting your wifi calling preference to Wi-Fi Only, which should turn on airplane mode. Close out of the settings and wait about ten seconds, then turn airplane mode off and see if wifi calling turns on. That works on my Win 8 640 (MetroPCS flash).
[Windows Phone 8 General] juicer52:
In step 11 h. "Once your phone has finish booting up and setup process completed," does this screen present as the "Let's get started screen"?

Do I execute the change of product code before doing the initial startup ie wifi, MS account etc?

Will it matter to import from backup settings once everything else is completed in this debranding or is it best to not import from previous backups?
[Windows Phone 8 General] pilot04:
I've tried that numerous times in current Windows 10 but it never enables wifi calling even if I waited up to a minute after coming out of airplane mode. It displays "Phone off" rather than wifi calling icon once I enable wifi while in airplane mode. I've seen screen shot of person yesterday showing wifi calling working for them on win10 but not sure if their 640 is a PAYG ATT model. Mine worked with wifi calling after reinstalling the 3 cab files again until doing another reflash of tmobile rom and upgraded to Win10.
[Windows Phone 8 General] Dibbyd:
Yes, I would change the product code before doing all the initial start up, but I'm not sure that it matters. I imported my previous backup from a Lumia 521 and had no problems.
[Windows Phone 8 General] pilot04:
Has anyone gotten their ATT PAYG Lumia 640 LTE Gophone rebranded to T-Mobile rom AND wifi calling is working properly? I'm wondering if the pay as you go phone I purchased at wally world is not the same as the regular ATT 640 LTE models.

Also, do I need to complete step 9&10? I skipped step 9&10 as Lumia Flash Tool couldn't detect my phone's image so I skipped onto step 11 to flash via WDRT. If I need to redo step 9, will I have to install the non-digitally signed LumiaFlashTools drivers per Kaptaiin's tutorial? "Once that the disable driver signature enforcement is performed, you must access to the ..\LumiaFlashTools\Driver directory and execute the Install.bat batch file"

For grins, I tried reinstalling the 3 cab files again and now get error below:

[1] Transferring files started

[1] Transferred file 1/3

[1] Transferred file 2/3

[1] Transferred file 3/3

[1] Transferring files complete: 3 files

[1] Update started

[1] Installation failed (HRESULT = 0x8024a110)

[1] Failed (0x8024a110)

ERROR: 0x8024a110

Command failed. (HRESULT = 0x8024a110)
[Windows Phone 8 General] kokku:
Managed to follow all the instructions and De-branded my ATT phone and flashed the T-Mobile ROM. Command line unable to get my device, but managed to flash using WPID. After flashing wi-fi calling worked on Windows 8.1 version. But after upgraded to windows phone 10, it is not working.

Verified band 12 option using filed test with ##3282# and it is available. Please confirm for anyone in Windows phone 10 wi-fi calling works.

Thanks to OP for the detailed instructions.
[Windows Phone 8 General] pilot04:
That is exactly what happened to my ATT gophone rebrand experiment as well. Wifi calling worked on win8.1 and stopped working after upgrading to win10 ver 107.

Someone got wifi calling working on Win10 as they posted screenshot in post #184 but not sure if they have ATT PAYG 640 gophone like I purchased from Walmart to test out the rebranding.
[Windows Phone 8 General] kokku:
We can try two more options.

1) reset the phone and try configuring the phone again

2) May be changing the "product code" before performing initial setup matters. As the phone is already charge with product code, re-flash the T-mobile ROM again. But I'm not sure this will resolve the wi-fi calling problem, as i explained in 8.1 version the wi-fi calling worked very well.

Any comments/suggestions welcome.
[Windows Phone 8 General] Dibbyd:
You do not need to perform steps 9 and 10.

---------- Post added at 04:37 PM ---------- Previous post was at 04:35 PM ----------

I doubt this will make much difference, but for those of you trying to get wifi calling to work on Win 10, I wonder if you tried installing the MetroPCS rom and then upgrading to Win 10 if it would work? I doubt it, since the Metro and T-Mobile roms are probably very similar, but it might be worth a try. FYI I'm using the MetroPCS rom on Win 8.
[Windows Phone 8 General] boonesmi:
as far as i know ATT only sells the 640 as a prepaid phone.. the 640xl has a "regular" version

and yes the phone i rebranded and tested/verified wifi calling was the prepaid version ATT 640 lte

---------- Post added at 02:41 PM ---------- Previous post was at 02:26 PM ----------

sounds like it might be a win10 problem with the latest release. dont forget win10 for the 640 is still a work in progress.

a quick google search found this

https://www.reddit.com/r/tmobile/comments/42gnur/lumia_640_on_windows_10_mobile_no_volte_or_wifi/

sounds like wifi calling not working for win10 on the 640 is a common problem even with an original TMO version of the 640.

since the TMO 640 and the ATT 640 both have the same sub model # (RM-1073) and the same hardware revision number (2.1.4.0) im pretty sure they are identical phones with the exception of the software. and once the ATT is rebranded to TMO they then both have the same software.
[Windows Phone 8 General] pilot04:
yep, looks like a Win10 problem as I found this on the insider community that it's a known issue.

http://answers.microsoft.com/en-us/...0166-and/1ea2a4b5-9b2d-46ad-a3ad-e160686766f4

---------- Post added at 12:39 PM ---------- Previous post was at 12:11 PM ----------

Okay, I did more testing and can confirm that I was able to get wifi calling working again when I restored back to Windows 8.1 using WDRT tool. It certainly is a Win10 issue with the internal modem drivers. I'll just upgrade again to win10 v.107 and wait till they release the fix to fast ring insiders hopefully soon.

Per http://answers.microsoft.com/en-us/...0166-and/1ea2a4b5-9b2d-46ad-a3ad-e160686766f4, it looks like there is a fix but awaiting Tmobile to test/certify before update is released for Win10.

"Here is another update on the status. A fix has been built! Any update which changes the internal modem drivers must be tested and certified by mobile operators for use on their network. The fix is currently being tested by a number of operators. After the signoff from then we can flight the update to Windows Insiders. "
[Windows Phone 8 General] juicer52:
In step 11 d. does it matter whether you include the " " marks around the download location of the rom?

It appears in the code sample given that the " marks were used.
[Windows Phone 8 General] pilot04:
I had to make a trip into downtown so drove by the T-Mobile corp HQ to test if band 12 is possible or not on my rebranded 640. I went into field test mode and manually turned off all except for band 12. Unfortunately, I was not able to get band 12 to work as icon shows no signal and status in field test mode says invalid.

Per the T-Mobile 700 spectrum map(http://www.spectrumgateway.com/t-mobile-700a-spectrum), T-Mobile corp HQ location has band 12 so kind of disappointed my 640 doesn't receive band 12.

1. For my phone, verified that I can restore back to Win8.1 to get wifi calling to work after flashing to T-Mobile rom. When upgraded to Win10, wifi calling stops working so I'll have to wait for Win10 fix that is already built to be tested/certified by T-Mobile

2. Band 12 doesn't work for my rebranded 640 for some reason
[Windows Phone 8 General] wmedrano55:
Same here. Band 12 shows up on field testing but does not work on my ATT 640. Wifi works. Was thinking of trying another 640 go phone but don't want to waste my money since I don't know which phone will have it working or not. Wonder if it is bad batch or there has been a recent change in HW. Tried other roms with band 12 with same result so its not software, at least not on my phone.
[Windows Phone 8 General] juicer52:
For those who can verify Band 12 working (not just present) can you please post HW version or whatever value might distinguish your phone.
[Windows Phone 8 General] tarindersingh100:
could you please give me a link of where you downloaded the uk firmware for Lumia 640 rm 1072. thanks a lot
[Windows Phone 8 General] ombreman:
You can find all kinds of ROM here:

lumiafirmware.com
[Windows Phone 8 General] vdanelia:
flashed RM-1072 VAR EURO BE CV ROM, 059X1B2. LTE bands stay the same. 2,4,5,7, 1, 28.

is it possible to add band 3?
[Windows Phone 8 General] thomascw:
getting parsing errors with thor when i try to change product code. Trying tmobile rom, checksums match, and phone lists as flashable in flash tools. Any pointers?

---------- Post added at 04:28 AM ---------- Previous post was at 04:01 AM ----------

i used wpid,success finally