Insider & registry hack for 520, 920, 1020 rebirth?

Maurizio Troso

New member
Aug 22, 2014
4,692
0
0
Visit site
I red days ago about some registry hack to fool the Update check in order to install Redstone on unsupported Lumias (it seems someone did it on a 520, I can't believe if I don't see!)

Same strategy could be used to made 520, 920 or 1020 seem like 530, 930, 1520 ? :wink:

And so make them enter in official updates stream?

EDIT: or am I totally fool?
 
Last edited:

abhishek singh21

Active member
Apr 27, 2014
2,454
2
38
Visit site
I red days ago about some registry hack to fool the Update check in order to install Redstone on not supported Lumias (it seems someone did it on a 520, I can't believe if I don't see!)

Same strategy could be used to made 520, 920 or 1020 seem like 530, 930, 1520 ? :wink:

And so made them enter in official updates stream?

EDIT: or am I totally fool?

this is indeed true and easily reversible. :)
Hack: Windows 10 Mobile Redstone Build 14267 on any Lumia

i am not sure that actually made those devices get the latest build but it did works on getting you the Redstone build at present :)
 

JIPPY422

New member
Dec 3, 2015
10
0
0
Visit site
Well i m using lumia 535 with redstone build 14291 installed and it is working really good. I did it with that registry method.
 

Maurizio Troso

New member
Aug 22, 2014
4,692
0
0
Visit site

JIPPY422

New member
Dec 3, 2015
10
0
0
Visit site
i installed RS build after upgrading to 10586.164. as i just did it as experiment and to my luck it was successful. but do it carefully, you may harm your device if you do any mistake while doing it.
GOOD LUCK BRO
 

Guytronic

Ambassador Team Leader
Nov 4, 2013
8,431
0
0
Visit site
Moved to Development and Hacking.

I'm hoping most of you aren't going to try the registry hack on phones your using daily.
You won't be happy.

Tread with caution.
 

Qtweeder

New member
Jul 19, 2013
541
0
0
Visit site
just doing this on my 1020, that was on 10.0.10586.164 insider preview

couple of things i had to do which differ from steps mentioned in the link;

vcREG_1_5_W10M.xap installed fine via application deployment from sdk

CustomPFD_0600.xap wouldn't deploy, giving error (0x81030120)

so had to deploy Root_Tool.xap

then the CustomPFD_0600.xap installed

also, i didn't need to change the PhoneManufacturerModelName of my phone at all, only changed the PhoneManufacturer in the registry from NOKIA to MicrosoftMDG

then i changed to release preview ring (not sure if i needed to do that), which downloaded a configuration update, after that, changed to fast ring and am now in the midst of receiving 10.0.14291.1001

fingers crossed.

p.s. i didnt need to hard reset or anything, just went from what i was on to the new one. all data/apps intact etc
 

ven07

New member
Jan 27, 2014
6,892
2
0
Visit site
Just adding this.. If any of you are doing the reg hack and are "emulating" one of the official supported phones, at least make sure that you turn off automatic updates. If firmware is pushed for the device you are emulating and it installs automatically there might be scaling issues or worse.

Keep in mind that unsupported phones aren't supposed to be on .14291 so don't go telling everyone that this is equal to "gold". If you know what you are doing and if the older builds behaved on your phone, go ahead and give it a shot, but if anything goes wrong, it's on you.

Like the others have stated it's probably best to do this on a backup phone and not the one you use daily
 

Members online

No members online now.

Forum statistics

Threads
322,736
Messages
2,242,598
Members
427,978
Latest member
Duouser3