Search results

Your phone is not bricked, because you can still flash a stock FFU to the phone to recover. But it's weird. WPI did not find a flashing profile for your phone. Normally that should never happen. You could try to unlock using a different profile FFU for RM-1104.

Always use the latest version of WPinternals. Have you tried to relock the phone?

Wow, wow, wow! Hold it right there! The tool is full of warnings. And when you started the tool for the first time, you agreed to the Disclaimer. This text is a part of the Disclaimer-text of the Windows Phone Internals tool: It is not my software who caused problems. You took the risk and...

WPI is capable of flashing any partition. But to be able to do that it needs at least an FFU with a header which is accepted by the phone. So, there you have the chicken and the egg.

Try again with WPI version 2.4 and let me know the results.

The UEFI partition can be replaced on Lumia's with bootlaoder Spec A. Not on Lumia's with bootloader Spec B! This is because SecureBoot Hack v2 works entirely different. You can add custom efi's though. Quite a few people already experimenting with this. For example...

"Restore bootloader" functionality is also improved in version 2.4. You may want to try this version to restore the bootloader.

Profiling data is indeed saved. For Lumia 640 you may want to redownload the emergency file using WPI 2.4. Because emergency files are mixed up by Microsoft and WPI 2.4 tries to download the correct files (different names).

Download version 2.4. On command-line type: WPinternals.exe /FindFlashingProfileExperimental Let me know the results. René

Fixed in version 2.4. Try again.

--

Correct. That is not possible. The SecureBoot Hack for bootloaders of Spec B Lumia's is too complex to be applied on mounted images. Version 2.4 has a proper warning for it. Instead you'll have to unlock the phone and then use the "Build and capture" technique to create a custom ROM from it...

Disconnect phone. In WPI go to manual mode. It will say "Waiting for connection". There is a link "Interrupt boot". Click that. Connect phone. The phone will go into flash mode. There it will charge.

Fixed in version 2.4. Try again!

On command-line type: WPinternals.exe /FindFlashingProfileExperimental Let me know the results. René

Lol. No! Windows Phone Internals uses highly specialized flashing techniques to accomplish the unlocks. Thor2 can only flash regular emergency images and ffu's. My tool can flash unsigned data to any location of the phone. I use combination of many, many hacks to make this all possible. So it...

Try again with WPI 2.4.

This can happen if you run other processes that access the phone at the same time. Like WDRT. This can mess up communications with the phone.

On command-line type: WPinternals.exe /FindFlashingProfileExperimental Let me know the results. René

Thanks for reporting. Will look into it.

You've got mail.

Correct. They do not need to be signed at all.

You should NOT update the phone while it is unlocked!!

Did you perhaps delete or move the FFU's you used before? If so, redownload the necessary FFU's and leave them there. Windows Phone Internals needs them.

Thanks a lot for this. This seems to be either a problem in the compiler or in the obfuscator. I will look into this and I think this can be solved.

It seems that if you once had Reset Protection enabled, it can come back for you after a reflash of an older FFU. This does not seem to be a problem of Windows Phone Internals, but rather a generic problem of reflashing these phones. It may also have to do with having bitlocker enabled at the...

Doesn't matter. Just download an FFU of RM-1085 and select that as "supported FFU". That will work.

I see a lot of people who have a 950 or 950 XL who don't get it working. I already have some logs. I will look into this. I don't have these problems on my 950 XL, but I will try to reproduce it.

Thanks for the log. I will look into this.

Afaik a bitlockered phone should just be visible normally in mass storage mode.

Then how did you get that message on your phone? If you boot the phone to normal mode and connect it with USB to PC, and you browse the phone with Windows Explorer on the PC, you will see a file called "Non-Production Errors.txt". That file will tell you why it shows that message.

Restore Bootloader

Oh wow. I have not taken that possibility into account. Thanks for reporting!

There is a logfile here: C:\ProgramData\WPinternals\WPinternals.log. Copy the relevant part of logging and send it to me in PM. I will try to see what happened.

Windows Phone Internals 2.3 is released! Version 2.3 is released: https://www.wpinternals.net/index.php/129-wpi23released Heathcliff74

My tool does help with that. But only with my last modifications. Because, it was possible to dump a ROM from the phone. But after a restore it was not possible to update anymore. With my latest modifications (the reason for the delay), you can relock the phone and update again. Heathcliff

Hahaha! No, I'm still alive and kicking. I released that intro video 2 weeks ago, because at that time i was sure i was able to release the tool within a few days. I still haven't released the tool yet, so I owe a little explanation. Two weeks ago I was just wrapping up some final pieces of...

WPI only works on supported OS versions. Version 15254.1 and 15254.12 are both supported. HTC One M8, HP Elite X3 and Alcatel Idol 4S are not supported. It would take me a lot of time to research. I have to see which hacks are compatible. And where I would need to find new hacks. I don't think...

Nope. And I don't think they will be supported. I got neither of these phones to test with. Research would also take a lot of time to see if some of the hacks can be ported to these phones and maybe they also need new hacks. I don't think I would have time to create support for these phones...

Sure is!

Hi all! Windows Phone Internals 2.4 is ready to download. It beats the modern SecureBoot implementation. And furthermore, it brings custom ROM's, Mass Storage Mode, Root access and many more hacks to all Windows Phone 8 and Windows 10 Mobile-based Lumia-models. There is also a new...

First I gotta ask.. if you want an Android phone, why didnt you buy an Android phone?? About flashing Android on the Idol 4S: - All hardware may be the same, the hash of the certificates in the QFuses are different. I checked it for you. The Android version of the phone has proper...

Nice! :) I will. It is hard to keep track of all documentation. Thanks for the heads up. Your second scenario will work too.

What happens if you flash a ROM? You get an error-code/message? Others with AT&T phones have reported that my tool works properly with their phones.

With WPI 1.2 you can indeed keep your data when you relock the bootloader. Your procedure is correct. Note: checks ACL's of the message-file you copy to your phone (ACL = file-properties -> security-tab). It must have proper access to allow Whatsapp to access the file. After disabling Root...

I don't mind that you edited the post. The point was that I already answered your question. And with the info you added to the post, you showed that you still didn't read my instructions. You can access the files using PSexec and a third-party file-browser. Read the "Getting started" section of...

I think you don't understand the concept of rooting Windows Phone. If you read the "Getting started" section of my tool, you will see that you CAN access everything. But the ACL's are an important aspect of the operating system. So you shouldn't mess that up. It's like I give you the key to a...

My "Root Access" hacks are a combination of several hacks: - Disable all ACL-checks, privilege-checks and capability-checks (this provides full access to resources like Registry, FileSystem, RPC-endpoints, etc) - Full Jailbreak (this supersedes Interop unlock and capability unlock and allows to...

You edited your post. But I think you still didnt read the "Getting started" section. You should NOT edit the permissions!!! That will kill the OS and the phone won't boot anymore. Instead download a 3rd party file-browser and run it with SYSTEM-privileges using PsExec. Then you can browse all...

Read the "getting started" section.