[Q] Unbranding a nokia 520 - Windows Phone 8 Q&A, Help & Troubleshooting

I have asked on wpcentral and wanted to get more people's opionons, I was thinking of flashing a CV rom to get updates faster. My phone is the 520 and it is SIM locked. It is using rm-915. I am wondering if it is sim locked and I used a different rom, from another country or global rom. Would I have a sim issue since it is locked to ATT.
2. How hard is it to brick a Lumia,
3. How easy is it to unbrick one
4. Voids the warranty right?
The only guy that answered my questions on wpcentral said he never has bricked one and they are easy to unbrick.
Also said I shouldn't have an issue with the sim.

The only typical way that they are bricked are when the device tries to do an update, but you get the "spinning gears of death" for hours on end. That's the update screen, but it shouldn't last more than 15 minutes.
To unbrick it, you just need to hold volup when turning on and reflash it.
It technically voids the warranty, but I have no way of knowing.
The phone would still be locked to AT&T, but it almost more useful to say on the ROM that's in it. AFAIK the US CV doesn't have the GDR3/Black update out yet for the Lumia 520.

Would I get a SIM error if I used an international rom for the 520.
For the rm915 there is a light swap eng global. Someone recommended the Brazil CV and another said Indian since they have black.
Sent from my Nokia Lumia 520

I have heard that going from a newer version firmware back to an older one would cause a brick. I was looking at the Brazil one and it says 3046.0000.1329.2002 and my current one is att 3043.0000.1324.0001
Sent from my Nokia Lumia 520

Related

Unbranded from 3 network (bootloader unlock allowed no)

I recently bought the Xz on the 3 network (uk) and straight away wanted to get on aosp but this was shortly lived when my bootloader unlock status said no!!! Arghhh!!!
After moving from the HTC one X this was a massive disappointment as I loved the IceColdJelly Rom from Lord.
So I started to look into how to get around this and came across a solution online saying you need to network unlock the device officially from your network operator this would then change the bootloader unlock allowed status to yes.
Great but I cannot get this yet as 3 state you need to be over 1 month into the contract witch I sadly am not.
I then done a bit of thinking and wondered if I managed to get onto the official unbranded software from Sony via an official method I may be able to get round it.
To do this I:
Rooted for locked bootloaders
Installed twrp for locked bootloaders
Installed one of the roms for locked bootloader (353?)
Then plugged my phone into the computer and started up the Sony update software and this gave me the option to update my phone to the latest 434? Software (something I couldn't get while on the branded stock rom)
So update done I reset the phone from within settings and preyed my bootloader unlock allowed status had been changed from no to yes. But no it hadn't .
So what's the point of this post?
Well I'm sharing my way of getting the latest update from Sony officially if anyone would ever want to do it that way.
But also I'm opening this thread to discuss if anyone had unlocked their network limitations and found that it changed the bootloader unlock allowed status.
Thank you for your time
Hi.
I renewed my contract with Three and got the XZ, and like you was hoping it had the unlockable bootloader. I knew I had the contract I needed anyway and was prepared to do whatever I had to do if the bootloader was properly locked. In the end the only thing I could do was get rid of the phone and buy one that was Sim free and bootloader unlockable. I bought it from Phones for you and checked the bootloader status before I handed over any money.
When I had my "old" XZ, I put it up for sale and in the hope of getting it sold easier I had it sim-unlocked by Three and I flashed UK unbranded firmware. As expected, unlocking the Sim and flashing unbranded firmware did not change the bootloader status.
In short, the only way to run something like CM is to sell your blower and buy one with a suitable bootloader.
Ah well that sucks surely it's not down to the carrier to impose these limitations apon the end user? There must be a way around this even if it is contacting Sony, surely if I the owner of my phone want to. Unlock my bootloader it's for me to decide, not the middle man.
Sent from my C6603 using xda app-developers app

[Q] Regarding ATT L1520 Debranding & Product Types

Ok, so im new to Windows Phone and after lots of reading I still have a few small questions if anyone wouldn't care to humor a noob. So here is my situation...
I bought a lightly used, sim unlocked, RM-940 ATT branded Lumia 1520 with the intention of flashing the latest stock firmware in order to start with a clean slate and get rid of ATT's bloat as well as be able to take developer preview updates from microsoft. I use an ATT MVNO so I need to make sure it's sim remains unlocked. From what I understand the newest RM-940 ATT firmware will relock the sim to ATT, which is exactly what I don't want. So from what im reading my best option is to flash the RM-937 Global Rom. I remember there being a Dev ROM for the Lumia 920 but I havn't seen any mention of such a thing for the L1520. Am I correct in assuming that I can go backwards from RM-940 to RM-937, or is that not possible? Would anyone care to set me straight please? I would greatly appreciate it.
I'm also interested in this info. Did you find if it's actually possible to flash a Lumia 1520 RM-940 (AT&T) with a Lumia 1520 RM-937 (Global) firmware?
Thanks.
It shouldn't be able to. AT&T and global f/w support different radios, and afaik, AT&T models always use different radios than global models. Fancy USA.

[Q] Regarding sim lock while flashing rom

I have a Lumia 520. Did register my phone for dev prieviews as you all know that wo 8.1 is due this week. I want cortana on my phone but they aren't releasing it outside of the US until the next year. My phone is an unlocked Indian variant, so I want to flash the us at&t rom on my phone. Now, the question: the phone is sim unlocked, would flashing the at&t version lock the phone to their carrier. Remember, I live in India.

MetroPCS L640LTE to WM10?

Ok, I have in my possession a Lumia 640LTE from MetroPCS and I would like to get it Window Mobile 10. I've already unlocked it from MetroPCS (got the unlock code and put in a non-MetroPCS SIM and entered the code).
I've been going through the forums and I can't quite determine the best method to go about this? That is also the easiest, sure fire way (no bricking). The only thing I have done so far is use WPInternals to unlock the boot loader, and I've tried to put "RM1073_02166.00000.15084.41001_RETAIL_prod_signed_1005_01DE1D_000-CA.ffu" on, but it fails via WPInternals.
I'm sorry if this is such a Newbie question in advance. Just please point me to the proper thread. Thanks in advance!!!
https://www.microsoft.com/en-us/download/details.aspx?id=56726
Unfortunately, it says there are "no updates for this device". Which is the same thing when I try the upgrade advisor. This has been an issue with this phone since it was from Metro PCS, as they never allowed WM10 for the Lumia 640 LTE
Flash a diferent variant then.
augustinionut said:
Flash a diferent variant then.
Click to expand...
Click to collapse
Could you recommend a different variant? I'm not sure which ones were allowed to be upgraded to WM10 in English besides the "Retail" version (I think).
The phone is the following from (w w w.lumiafirmware.com/ser/RM-1073/guid/059X0M9):
Phone model: Lumia 640 LTE
PackageTitle: RM-1073 VAR NAM US METROPCS SL
Product Code: 059X0Q4
manufacturerHardwareModel: RM-1073
I used RM-1073 VAR LTA 7R CV on my T-Mobile 640 LTE then used the OTC updater tool from Microsoft to push the update to my phone. I only use it for a Wi-Fi device though so I don't know if cell/data works or not.

Question Can the latest leak of the full international ROM be safely flashed on an NE2217 (T-Mobile)?

I've been wanting to convert to international for a while now but I heard it's very risky, I'm curious if anyone has an answer as to whether this is safe to flash since it's a full ROM
On page 2 there's a thread that should answer your questions.
Ok... Honest opinion... NO. If you are NOT sim unlocked and NOT bootloader unlocked, then when you flash to Android 13, your device will become locked completely... As in no apps will open and you will get some stupid "Contract Phone" error no matter what you tap. I'm trying to hunt down the process that activates this but it's hard considering that the only time it triggers is when you pop a TMobile sim into any other A13 firmware other than the original TMO flash. I know that they TECHNICALLY are the same model, 2217 ... 2217.... And myself am sitting here using 2215 FW on my 2217 TMobile locked phone... But I went thru nightmares and hard bricks to get mine working. I took my phone down to completely unresponsive state.... Had it revived to 2217fw, but NOT the TMO branded....and then used FB to get my unlock token for the bootloader. Once BL unlocked , I tried updating to the same 2217 android 13, and the phone did what I said earlier.... But thankfully I had FB and unlocked BL, so I just flashed the stock recovery and stock boot.img and it went back to working but on Android 13 (with A12 recovery and Boot.img). I don't recommend that at all because while yes I have had no problems doing it to several other phones with no bricks... I have had several reports that ppl didn't get the same success.... As of today I have flashed 27 ne2217 phones to 2215 then 2217. But I have had some headaches with using the exact same processes every time but getting different outcomes every time. There's SOME FILE that needs to be disabled in the system so this can be done safely, but unless you are Sim Unlocked and BL unlocked I cannot recommend you attempt this. That is the only factor I think that has made all my flashes successful, cuz ultimately it's a TMobile BRAND lock... Not region... Cuz ne2217 is NA... So the region is the same as I'm in Texas... But if it's not TMO branded fw.. the phone freaks out sometimes. But only with android 13. Kinda like how the 'Orange' state came back with the updates.... TMobile did this on purpose probably because of all the posts here about successful region swaps! Be warned! The TMO Mafia is waiting to put a brick in your hands!

Categories

Resources