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

[Heathcliff74]

The Lumia 950 uses a Snapdragon 808 while the Lumia 640 XL uses a Snapdragon 400. Does that mean that there is a good chance that the 640 XL will be supported soon too, or are they completely different beasts?

The bootloader architecture is roughly the same.

 

[mybabysexy]

Did you enable Root Access first??

of course yes, that's why I can't figure out why it caused problems. Have you check the files I attached yet?

 

[afi1982]

That's not what i meant. There are many boot stages: PBL, SBL, UEFI, OS. Every stage has it own implementation of emergency charging. When the phone is still in an early boot stage, it might not even have a display-driver loaded. And charging will be done without showing anything. I just meant that when you charge by connecting to PC, charging is very slow. So you need to give it some time to properly charge (if that actually works).

so i gave it time to charge and now phone is only vibrating but it's no longer recognize it even not as usb input device.

 

[_wook_]

so i gave it time to charge and now phone is only vibrating but it's no longer recognize it even not as usb input device.

Try:
Run WPInternals and keep it running.
Attach the phone to the PC.
Press and hold volume down and power button until you hear vibration and release power button.
Device should be detected now.

Retry the procedure several times if it fails in first try.
Good luck again.

 

[Heathcliff74]

of course yes, that's why I can't figure out why it caused problems. Have you check the files I attached yet?

I had a quick look. At first glance I did not see anything wrong with it. But I don't know what went wrong with your dll. I downloaded a trial version of Bome Restorator and I was able to replace an icon and load the dll back onto the phone and the phone still boots.

Maybe you should try to replace only one icon first. Then another one. Then a couple more, until everything works or fails. If it fails you know which icons were replaced right before it fails and then you know where the problem is.

 

[mybabysexy]

I had a quick look. At first glance I did not see anything wrong with it. But I don't know what went wrong with your dll. I downloaded a trial version of Bome Restorator and I was able to replace an icon and load the dll back onto the phone and the phone still boots.

Maybe you should try to replace only one icon first. Then another one. Then a couple more, until everything works or fails. If it fails you know which icons were replaced right before it fails and then you know where the problem is.

thx. I will try that again. But for now I don't know why windows phone internals and my PC cannot recognize my phone after installing visual studio SDK IDE

 

[Heathcliff74]

I found a solution for the Audio-issue when enabling Root Access. It is actually a work-around. It needs a better solution. But for now, it will do. Will take me a bit of time to implement it, but a new version of the tool is in the making.

 

[titi66200]

Good news Thanks

 

[nscxp2005]

Hi guys,

I apologise in advance if this has already been asked. Do you know if the 630, 635, or 535 are supported by this tool?

Thanks

Nscxp2005

Sent from my SM-G928F using Tapatalk

 

[titi66200]

@Heathcliff74

Having unlock the bootloader can prevent the installation of packages with iutool?
can't sent packages, error HRESULT = 0x8024a110

 

[augustinionut]

The real code of error can be seen by pushing update buton from phone settings update when cmd is showing update.
https://msdn.microsoft.com/es-es/library/windows/hardware/mt131833(v=vs.85).aspx

 

[Heathcliff74]

@Heathcliff74

Having unlock the bootloader can prevent the installation of packages with iutool?
can't sent packages, error HRESULT = 0x8024a110

First of all: be very careful with updates when you have unlocks on your phone!!

If you have only unlocked the bootloader (Root Access not enabled), you should be able to push OS updates.

If you also enabled Root Access, you can get all kinds of errors when you try to run updates. System files are modified. Any differential update on those files will fail. You can first disable Root Access and then try to push the OS updates.

If you try to push OEM firmware updates, then these can also contain updated bootloaders. This is very risky. It's possible that you undo the bootloader unlock. But when only parts of the bootloader are updated, you get a half-patched-bootloader, which probably results in a bricked phone.

 

[Heathcliff74]

Hi guys,

I apologise in advance if this has already been asked. Do you know if the 630, 635, or 535 are supported by this tool?

Thanks

Nscxp2005

Sent from my SM-G928F using Tapatalk

Not supported.

 

[mahmoud.facebook]

Do not work on devices Microsoft

 

[sensboston]

First of all: be very careful with updates when you have unlocks on your phone!!

Summarizing: looks like WPI 1.0 definitely not for the primary, main phone WM10 is very buggy (looks like MS replaced all professional Q&A people to "enthusiast beta-testers") and MS will push updates very frequently (fixing old bugs and adding a new ones). The risk to completely brick your brand new expensive "flagship" handset is too high.

We need (or we are already have one? Sorry I haven't followed the WM10 "interop" news) simpler, bullet- & MS-proof method to achieve interop unlock/root access for the "tasty" things...

 

[Heathcliff74]

Summarizing: looks like WPI 1.0 definitely not for the primary, main phone WM10 is very buggy (looks like MS replaced all professional Q&A people to "enthusiast beta-testers") and MS will push updates very frequently (fixing old bugs and adding a new ones). The risk to completely brick your brand new expensive "flagship" handset is too high.

We need (or we are already have one? Sorry I haven't followed the WM10 "interop" news) simpler, bullet- & MS-proof method to achieve interop unlock/root access for the "tasty" things...

Well, I look at it this way:

My first goal was to completely break open the phone; bootloader AND operating system. "All guards down". This is necessary for a couple of reasons:

- Being able to do proper research on the OS
- Being able to sideload homebrew apps with full privileges
- Being able to apply other tweaks / hacks

In the "Getting started" section I also tell that you might want to consider disabling Root Access afterwards.

So, I encourage finding alternative unlock-mechanisms. The Root Access which is currently implemented in Windows Phone Internals can be used to disable security on the phone, then apply necessary tweaks and unlocks and finally disable the Root Access method of Windows Phone Internals. You could see it as an "Unlock loader".

Back in the WP7 era, I did something similar with WP7 Root Tools. First I created Root Access. Later on, I created a Policy Editor to better control Root Access.

Windows Phone Internals is just the first step. Other hackers / developers need to create more cool stuff which builds on top of Windows Phone Internals unlocks.

Currently I would think twice about using Windows Phone Internals on your daily-use-phones. At least, you should first get familiar with it, probably on a test-phone. Later on, you might use it on other phones. But unlocks have always been and will always be a bit risky, especially with updates. Unlocks will never be fully Microsoft-proof / update-proof, simply because Microsoft can't take all unlock mechanisms into account. In the Custom ROM business it is common that you flash a certain ROM and when you want to update to a newer OS, you flash a new version of that custom ROM. If you are eager to test every new build asap, then custom ROM's are not very suitable for that purpose.

 

[sensboston]

@Heathcliff74, my post wasn't about to "criticising" your work and method, of course not! I'm absolutely sure, it's a great job and perfect basis for the future platform research.
But I tried to look into this from the practical side: it's definitely will be good to have ability to run apps with elevated privileges on WM10 platform - to apply some tweaks, get rid from some cell providers greediness (meaning internet sharing) etc. and so on.

As for the "safe" methods, AFAIR most previously known "interop" hacks are safe and many of 'em survived the OS updates. Your "jailbreak" is a different kind; sorry for these words but it looks like a bridge to the "hell" of the custom ROMs (with huge limitations 'cause we have no sources of the OS and must use buggy MS bits!), bricked phones, crying newbies and so on (I'm kidding so pls take it easy).

Hope, someone will find another "lightweight" hack just for "interop" unlock using your "full jailbreak" for the released WM10 soon!

 

[endera]

Yezz Billy 4.7 support is there ?

 

[MrCego]

Some Lumias only.

 

[rustybob]

Thank you for the fantastic app. Long story short, I bought a Lumia 920 off Craigslist for $40 with a wireless charger. The ad said Glance wasn't working, so I suspected that it was just dirty under the screen by the proximity sensor, which would be an easy fix, and then I could flip the phone for more money. That wasn't the problem, but I still think I got my money's worth out of the deal. The charger is nice to have, and I made a post in the Lumia 920 forum as well. This was the AT&T version of the phone, and while it shared the same part number as the Canadian Rogers version, it did not support AWS HSPA. Nobody ever replied, but I believe I solved the mystery of why it didn't work. I noticed some antenna pins pushed down that weren't on a Rogers version that I had to replace the glass. I lifted them up, booted up the phone, and it immediately connected to the Mobilicity network. Calling and data worked, and the signal was just as strong as my Rogers version of the phone.

Anyways, the problem with the phone ran much deeper than dirt by the proximity sensor. The previous owner had flashed the Rogers version of the firmware on the phone. I suspected the issue was firmware related, but there was no way to flash back to the AT&T version until now. Using the Nokia Care Suite, I put the phone in test mode, and it failed multiple tests, the accelerometer, proximity sensor, front camera, microphone, and a few others. I know that the brightness settings on the phone also couldn't be changed. All of them said the error was due to a missing driver.

WPInternals finally allowed me to flash the original AT&T firmware for this phone. The Windows Device Recovery Tool now works without issue. The AT&T firmware has fixed some things. Auto brightness still doesn't work, but it's not stuck on low, it can go in between the three brightness levels. In Test Mode, it fails five tests still, with the accelerometer, proximity sensor, front camera, and microphone still the big issues. Previously, Glance couldn't be installed, but it does install fine now, it just doesn't work because of the proximity sensor. Trying to update to Windows 10 previously resulted in a soft brick, but works fine now.

Because of the issues on this phone, it's been the perfect candidate to play around with on WPInternals. I think it would be awesome to get it back into fully working condition again, though. Some internet searching hasn't brought up much info about this. One person had the issue disappear after the 8.1 update was pushed to their phone. Another did a hard reset with the SIM inserted. Neither of these worked.

Maybe I'm wrong, but I do have the suspicion that the issues are, in fact, driver related. The camera app worked fine when I bought it, but after doing a reset from the About screen, the camera app never launched again. I suspect that there would be no way to change the drivers through Mass Storage mode on a running phone, since those files should hypothetically be in use. So I'm thinking that making a custom ROM to flash might fix the issue. Would anyone happen to know where in the file system the driver files would be located? I could extract them from a different RM-820 (or perhaps an RM-821) ROM, and see if it worked. I don't care if I fully bricked the phone by doing this, since it's not really a useable phone at the moment, and the charger and the knowledge learned have been worth the $40 I paid already. The fact that some functionality was restored by going back to the original AT&T software, and that Windows 10 is now installable, also gives me some hope that this is a software-related issue.

Also, I just noticed the Build and Capture section in the Getting Started section. It mentions that registry settings survive a hard reset. I think I will attempt a build and capture, and use SDELETE to clean up the image.

It doesn't seem like this is a very common issue. Or, perhaps, people have just assumed that the issue isn't fixable. If it can be fixed through software, I'd love to give that information back to this community. The info on XDA has saved me many times, it would be nice to give something back.