Windows Phone Internals - Unlock bootloader, enable Root Access, create Custom ROM

Heathcliff74

Inactive Recognized Developer
Dec 1, 2010
1,646
2,609
0
If you have better understanding about the WPInternal you can manually unlock 1520.
I saw many guy's unlocked their 1520 with/without WPInternal and flashed Custom ROM's :D
I suspect that is all fake. The only possible unlocks for Lumia 1520 I am aware of are related to app-hijacking and the TFTP file-system-hack. But neither of those allow using Custom ROM's.
 
  • Like
Reactions: reeg420

Heathcliff74

Inactive Recognized Developer
Dec 1, 2010
1,646
2,609
0
Yup..thanks to provide such a powerful tool.this time got suceess to interop+capability +mass storage on my Lumia 720....working good. .no problem appear at now
Nice. What SBL3 did you use? Lumia 720 has MSM8227A. Lumia 520 and 620 have MSM8227. Not exactly the same, but SBL3 might work on Lumia 720?
 

Heathcliff74

Inactive Recognized Developer
Dec 1, 2010
1,646
2,609
0
I have a question any one in any rom with unlocked bootloader can flash a custom rom modificated and full unlock? Ex: Someone in win8.1 only unlocked bootlader , can flash lastes build of win 10 customized and full unlocked with out any probelm or he/she has to first used the legal mehtod of insider to update to the same build??
Custom ROM with Windows 10 Mobile can be flashed to a phone with an old OS version. Partition-layout can be different, but Windows Phone Internals will write a new partition-table for you. Obviously the bootloader must first be unlocked. And Custom ROM's are model-specific (just like stock ROM's). So, it must be a Custom ROM, which is created by someone with the same phone-model.
 
  • Like
Reactions: werty100

werty100

Senior Member
Aug 31, 2011
828
678
0
Probably a driver issue. Read the "Getting started" section of the tool and make sure you have all the correct drivers installed.
Win7 is not working with your tool , but the same mehtod with win10 all the same same computer same drivers yes...:confused:
I am doing a tutorial for spanish people and then i will try when i have time a custom rom thanks for helping my with this dude about customs roms
 

Heathcliff74

Inactive Recognized Developer
Dec 1, 2010
1,646
2,609
0
Win7 is not working with your tool , but the same mehtod with win10 all the same same computer same drivers yes...:confused:
I am doing a tutorial for spanish people and then i will try when i have time a custom rom thanks for helping my with this dude about customs roms
Ok. Nice that it is working on Windows 10. But the problem is not Windows 7. I'm sure it works on Windows 7 too. I still think you have a driver issue on that Windows 7 machine.
 

Dude360

Senior Member
Nov 22, 2006
1,173
903
113
Hope your all having a great Xmas :)

Having a root issue with a 520. Bootlaoder unlocked fine and Mass Storage seems to work (MainOS appears as a drive) but root fails.

Heres the log:

Code:
25/12/2015 18:00:41.626: Starting Windows Phone Internals version 1.1.5835.1923
25/12/2015 18:00:41.891: Found device on interface: 0fd3b15c-d457-45d8-a779-c2b2c9f9d0fd
25/12/2015 18:00:41.891:   Device path: \\?\usb#vid_0421&pid_0661&mi_02#6&1540b622&0&0002#{0fd3b15c-d457-45d8-a779-c2b2c9f9d0fd}
25/12/2015 18:00:41.906: Found device on interface: 7eaff726-34cc-4204-b09d-f95471b873cf
25/12/2015 18:00:41.906:   Device path: \\?\usb#vid_0421&pid_0661&mi_03#6&1540b622&0&0003#{7eaff726-34cc-4204-b09d-f95471b873cf}
25/12/2015 18:00:42.31: Found Lumia. Mode: Normal.
25/12/2015 18:00:42.62: Found device on interface: 53f56307-b6bf-11d0-94f2-00a0c91efb8b
25/12/2015 18:00:42.62:   Device path: \\?\ide#diskwdc_wd1002faex-00z3a0___________________05.01d05#5&f437ab5&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
25/12/2015 18:00:42.78: Found device on interface: 86e0d1e0-8089-11d0-9ce4-08003e301f73
25/12/2015 18:00:42.78:   Device path: \\?\acpi#pnp0501#1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
25/12/2015 18:00:43.388: Operator: 000-GB
25/12/2015 18:00:43.404: Manufacturer Model Name: RM-914_eu_euro1_327
25/12/2015 18:00:43.404: Product Code: 059S3T5
25/12/2015 18:00:43.420: Firmware: 3058.50000.1425.0006
25/12/2015 18:00:43.420: IMEI: XXXXX
25/12/2015 18:00:43.451: Public ID: XXXXX
25/12/2015 18:00:43.466: Bluetooth MAC: XXXXX
25/12/2015 18:00:43.482: WLAN MAC: XXXXX
25/12/2015 18:00:43.529: Bootloader Security: Enabled
25/12/2015 18:00:43.544: Simlock: Unlocked
25/12/2015 18:00:49.320: First rebooting phone to Flash mode (then attempt Mass Storage mode
25/12/2015 18:00:49.352: First rebooting phone to Flash mode...
25/12/2015 18:01:05.662: Phone disconnected.
25/12/2015 18:01:12.524: Found device on interface: 0fd3b15c-d457-45d8-a779-c2b2c9f9d0fd
25/12/2015 18:01:12.524:   Device path: \\?\USB#VID_0421&PID_066E#5&1dda42a3&0&1#{0fd3b15c-d457-45d8-a779-c2b2c9f9d0fd}
25/12/2015 18:01:12.548: Found Lumia. Mode: Flash.
25/12/2015 18:01:12.571: Effective Bootloader Security Status: False
25/12/2015 18:01:13.15: Rebooting phone to Mass Storage mode
25/12/2015 18:01:13.16: And now rebooting phone to Mass Storage mode...
25/12/2015 18:01:13.17: Reading status from Flash interface was aborted.
25/12/2015 18:01:13.146: Phone disconnected.
25/12/2015 18:01:15.501: Found device on interface: 53f56307-b6bf-11d0-94f2-00a0c91efb8b
25/12/2015 18:01:15.501:   Device path: \\?\USBSTOR#Disk&Ven_Qualcomm&Prod_MMC_Storage&Rev_1.00#7&5313ab4&0&1234567890ABCDEF&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
25/12/2015 18:01:16.849: Found device on interface: 53f56307-b6bf-11d0-94f2-00a0c91efb8b
25/12/2015 18:01:16.850:   Device path: \\.\F:
25/12/2015 18:01:22.960: Found Lumia. Mode: Mass storage.
25/12/2015 18:01:22.989: Applying Root Unlock to EFIESP...
25/12/2015 18:01:23.21: Attempt patch: RootAccess-EFIESP
25/12/2015 18:01:23.201: Apply: 8.10.12393.890
25/12/2015 18:01:23.206: Applying Root Unlock to MainOS...
25/12/2015 18:01:23.206: Attempt patch: RootAccess-MainOS
25/12/2015 18:01:24.210: Apply: 8.10.12393.890
25/12/2015 18:01:24.301: Attempted to perform an unauthorized operation.
25/12/2015 18:01:24.305:    at System.Security.AccessControl.Win32.SetSecurityInfo(ResourceType type, String name, SafeHandle handle, SecurityInfos securityInformation, SecurityIdentifier owner, SecurityIdentifier group, GenericAcl sacl, GenericAcl dacl)
   at System.Security.AccessControl.NativeObjectSecurity.Persist(String name, SafeHandle handle, AccessControlSections includeSections, Object exceptionContext)
   at System.Security.AccessControl.NativeObjectSecurity.Persist(String name, AccessControlSections includeSections, Object exceptionContext)
   at System.Security.AccessControl.FileSystemSecurity.Persist(String fullPath)
   at ..( )
   at WPinternals.PatchEngine.(String )
25/12/2015 18:01:24.307: Failed to apply Root Unlock on MainOS!
25/12/2015 18:01:33.63: Applying Root Unlock to EFIESP...
25/12/2015 18:01:33.63: Attempt patch: RootAccess-EFIESP
25/12/2015 18:01:33.112: Apply: 8.10.12393.890
25/12/2015 18:01:33.112: Applying Root Unlock to MainOS...
25/12/2015 18:01:33.112: Attempt patch: RootAccess-MainOS
25/12/2015 18:01:33.426: Apply: 8.10.12393.890
25/12/2015 18:01:33.431: Attempted to perform an unauthorized operation.
25/12/2015 18:01:33.432:    at System.Security.AccessControl.Win32.SetSecurityInfo(ResourceType type, String name, SafeHandle handle, SecurityInfos securityInformation, SecurityIdentifier owner, SecurityIdentifier group, GenericAcl sacl, GenericAcl dacl)
   at System.Security.AccessControl.NativeObjectSecurity.Persist(String name, SafeHandle handle, AccessControlSections includeSections, Object exceptionContext)
   at System.Security.AccessControl.NativeObjectSecurity.Persist(String name, AccessControlSections includeSections, Object exceptionContext)
   at System.Security.AccessControl.FileSystemSecurity.Persist(String fullPath)
   at ..( )
   at WPinternals.PatchEngine.(String )
25/12/2015 18:01:33.432: Failed to apply Root Unlock on MainOS!
Just for the record, my process if it helps

Reflashed a stock ffu (RM914_3058.50000.1425.0006_RETAIL_eu_euro1_327_06_452364_prd_signed) before starting, ran through the usual setup nonsense (didnt sign in) and rebooted a couple of times to make sure the stock ffu was working fine.

Used the same ffu in WPI, Engineering-SBL3-Lumia-520 from a previous post and selected the folder full of hex files.

Ran the bootloader unlock and all seemed well, Mass storage mode worked. Made a backup from within WPI



Enjoy the rest of your holidays people :)
 

pdaimatejam

Inactive Recognized Developer
Mar 7, 2009
689
1,767
0
Sinop/Boyabat
www.ctrlpda.com
@pdaimatejam: I don't understand what you're saying.
read:https://www.microsoft.com/en-us/download/details.aspx?id=13209

Run legacy applications without changing language of non-Unicode applications (system locale).
Details
Version:
1.0
File Name:
apploc.msi
Date Published:
6/14/2004
File Size:
1.3 MB
Unicode based platforms, such as Windows XP, emulate the language environment required to run non-Unicode applications by internally converting application's non-Unicode text data to Unicode using a system-wide variable commonly called the system local (or language for non-Unicode applications). The language of the non-Unicode applications should be of the same script or family as the one defined by the system locale. Failing to meet this condition results in display of garbage characters in the UI of the application.

This approach has few usability limitations:
Only an administrator has the ability of setting the system locale value.
Setting the system locale requires a system reboot.
Only one system locale can be set at a time.

AppLocale (or Application Locale) is a temporary solution to these limitations caused by non-Unicode applications running on the Unicode (UTF-16) based Windows XP. AppLocale detects the language of the legacy application and simulates a corresponding system locale for code-page to/from Unicode conversions.

IMPORTANT NOTES:
AppLocale is based on the new application compatibility technology introduced in Windows XP and can only be installed on these two operating systems.
If you frequently use non-Unicode applications in a given script (or set of languages), it is strongly recommended to set your system locale variable to the language of the target application and not to use AppLocale.
Application developers should not consider AppLocale as an alternative to migrate their product to Unicode. Today, with Microsoft Layer for Unicode (MSLU), creating pure Unicode applications that can also be deployed on non-Unicode platforms -- such as Windows 98 -- has been made possible.
System Requirements
Supported Operating System
Windows Server 2003, Windows XP
Language support already installed.

AppLocale runs on both English and localized versions of Windows XP or Server 2003. The user interface is English-only and won't be localized.
Install Instructions
Click the Download link to start the download, or choose a different language from the drop-down list and click Go.
Do one of the following:
To start the installation immediately, click Open or Run this program from its current location.
To copy the download to your computer for installation at a later time, click Save or Save this program to disk.
Click the apploc.msi file to start the AppLocale Installation Wizard.
Follow the instructions on the wizard.


The AppLocale setup program installs a shortcut to AppLocale wizard under Start menu/All Programs menu. Use this wizard to launch a desired application. If you don't know the path of the target application, you can simply drag & drop its icon to the "path" edit control.
Additional Information
AppLocale runs on both English and localized versions of Windows XP or Server 2003. The user interface is English-only and won't be localized.
 

Heathcliff74

Inactive Recognized Developer
Dec 1, 2010
1,646
2,609
0
Hope your all having a great Xmas :)

Having a root issue with a 520. Bootlaoder unlocked fine and Mass Storage seems to work (MainOS appears as a drive) but root fails.

Enjoy the rest of your holidays people :)
This is a problem with your account on the PC. Your account doesn't seem to have administrator-privileges. What OS are you using? Try these:

- Start wpinternals.exe by right-click and "run as admin"
- Log in windows with a different account with Localadmin privileges
- Temporary disable anti-virus
- Or try on a completely different computer.

Please let me know the results.
 

djamol

Senior Member
Jun 3, 2014
444
405
0
29
Pune
www.twitter.com
I suspect that is all fake. The only possible unlocks for Lumia 1520 I am aware of are related to app-hijacking and the TFTP file-system-hack. But neither of those allow using Custom ROM's.
1. Flashing same concept as WPInternal through emergency protocol might be possible though.
2. One of public hack which allows you to flash custom ffu image without unlocking SB. That wojtek already said that's possible in many threads.
3. Some of private hack that I can't tell in public.
But of course your tool.. Hats offffff...!
 

Heathcliff74

Inactive Recognized Developer
Dec 1, 2010
1,646
2,609
0
1. Flashing same concept as WPInternal through emergency protocol might be possible though.
Emergency mode has MANY limitations. Emergency mode on MSM8974 and higher have even more limitations. You can write only specific locations on the phone (full flash is not possible). Payload has integrity checks (custom payload cannot be flashed). Once flashed to the device, there is still SecureBoot, so phone will not boot custom code.

2. One of public hack which allows you to flash custom ffu image without unlocking SB. That wojtek already said that's possible in many threads.
3. Some of private hack that I can't tell in public.
I have not seen these in action. I believe it when I see it. If Lumia 1520 was hacked, wouldn't it be big news by now?
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone