Related
Hello,
I'm trying to develop a little app for my Win6.5Pro PDA (brand new, entreprise edition).
So I've made my own certificate (using tools from the SDK) and it runs smoothly on the emulator.
But when I want to transfer it to my PDA, it says: The file X cannot be opened. Either it is not signed with a trusted certificate, or one of its components.....
I installed the certificate on my PDA, but nothing changed.
I tried with a .cab instead of an .exe, but nothing changed.
I tried to run the .exe in another WinMo, and it run smoothly.
I tried to install other apps, but nothing except the Marketplace's apps were allowed.
After a few hours on Google and MSDN, I think it is because the security level is set to "Locked" (cf. http://msdn.microsoft.com/en-us/library/bb416350.aspx ).
Is there a way to change the security level, or to bypass it?
(it's for personnal dev, and I'm not part of Mobile2Market Program so I don't have a trusted certificate)
Not sure if WM5 version will work with WM6.5, but there's a tool for this:
http://www.microsoft.com/downloads/...8C-D587-47E0-908B-09FEE6EA517A&displaylang=en
Here's a short tutorial:
http://www.riverpast.com/en/support/tutorials/view/?id=4
Thanks stepw.
The Security Configuration Manager tool is also include in the WinMo 6 SDK, so it should work fine.
But I've already tried, and the phone can't connect to anything but ActiveSync
So, after a cople of hours, I've somehow managed to find a solution.
I don't know if it will help somebody but I will write it here.
It's probably not the best solution, but it work fine with me.
First, I've copied the following configuration file into the PDA:
C:\Program Files\Windows Mobile 6 SDK\Tools\PocketPC\Security\SecurityOff.cpf
C:\Program Files\Windows Mobile 6 SDK\Tools\PocketPC\Security\RapiSecurityRapiAllowed.cpf
And I've executed them several times: it seems that something happened (the screen got black for half a second) but at this stage I still wasn't able to launch my app.
I've try to hard reset the device and still nothing changed.
But when I deleted the ActiveSync connection on my desktop and re-connected the PDA, a pop-up appeared saying that the device should restart so new changes will take effect.
And when the PDA restarted, everything was fine
Ok, so we haven't had quite as much luck yet as we would have liked, but I think as we continue to try out different approaches we will have some luck. I think it might be beneficial for us to have a an overview of what has been tried and what has been attempted thus far. So here is a list of things people have tried (please feel free to add anything that I may have left out or accidentally overlooked).
Registry Edit to access Zune storage
I believe this was the first approach that people took to gaining access to the KIN, and this link provides a great walkthrough.
Bitpim
This is a pretty good overview of what has been attempted through Bitpim. Recently some have even tried using some other software, namely CDMA Workshop, (Look at the last post of the page.) I would suggest that we also try a couple more:
RevSkills
UniCDMA
Nvidia Tegra Flash
I forgot this when I first posted.
OpenZDK
This was another potential since much of the hardware, namely the processor is the same on both the kin and zune.
Looking for clues in the log files
To put it simply in the hidden menu there is an option to have system log s emailed to you. I tried reading through some and noticed some of the events and files that the KIN uses, but have not had any luck yet.
FTP
This link is the same as the link for the Log Files above.
Export/Import in hidden Menu
Once again, the linked used here is the same one for Log Files and FTP.
Please add anything that I may have left out, either different approaches or links to helpful information. I haven't had a chance to tinker with RevSkills too much yet, but it looks real promising.
Ah, we mods like these threads. Keep it up. Stickied.
The hidden import feature becomes active if you create a contact while using
qpst. It imports but I don't know where it put that info.
Interesting to note is that None of my phone entered contacts show up in qpst.
It is like that directory is mapped to some other place.
I was able to create directories and added txt files using qpst that remain even after power cycling the phone. I haven't found any of this using the phone yet.
I am getting the same results as you when I use the EFS manager and service programming. I can create files and make changes and they last after reboot.
I find it odd that when I export contacts from the hidden menu the file is visible in windows explorer if I have edited the registry as noted in the first post. I find this odd because everything else that is visible on the device using this method is related to the Zune, i.e. photos, music, and videos.
I have started looking back at some of the log files that I had the phone email me through the hidden menu and I have found some AT commands for the phone along with some other information. Here is a little bit of one file that I just started sorting through. The formatting isn't perfect because the log files have a lot of unreadable characters, but I have bolded files and commands. I also left everything in the case (upper and lower) as I found it in the file. The name of this file is:
MICROSOFT-PMX-DEBUGSTRINGPROVIDER-CHANNEL.02.clg
MPM_MainsSmThread
MPM_BB_STATE_NORMAL_ON_PRE_UPDATE
MPM_BB_USB_DRIVER_LOAD_UPDATE_EVENT, dwWaitTime: -1
MPM_Util:USB Client 1 has been Loaded
MPM_Util:USB Client 2 has been !UnLoaded!
CDMA Radio Updeate: Text stored version : v0.4.727
CDMA Radio Update:Registry Key version: v0.4.727
CDMA Radio Update: Current Modem version: v0.4.727
MPM_MainsSmThread
MPM_BB_STATE_NORMAL_ON_PRE_UPDATE
MPM_MainsSmThread
MPM_BB_UPDATE_REQ_EVENT - No modem update is needed
MPM_MainsSmThread
MPM_BB_STATE_NORMAL_ON_POST_UPDATE
MPM_END_RSTISR_REQ_EVENT, dwWaitTime: -1
MPM_MainsSmThread
MPM_BB_STATE_NORMAL_ON_POST_UPDATE
MPM_END_RSTISR_REQ_EVENT MODEM RESET ISR Init Completed.
MPM_MainsSmThread
MPM_BB_STATE_NORMAL_ON_POST_UPDATE
MPM_POWER_ON_REQ_EVENT, dwWaitTime: -1
RILNDIS: GetPacketInterface Initialize = c117d634
Shutdown = c117c4e4
RILDrv : i : Accumulated response (1) : <cr><lf>
IOPTMODE: 6 <cr><lf>
RILDrv : i : Sending cmd: ATV0E0X3 <cr>
RILDrv : t : LoadEriData : Opening file
\RoamingIndicator\eri.bin
RILDrv : i : Accumulated response (1) : ATV0E0X3 <cr> 0 <cr>
RILDrv : t : LoadEriData:
\RoamingIndicator\eri.bin not exist. Err 0x00000002
RILDrv : i : Sending cmd:
AT+cstt=0, 1, 75, 85, 95, 100 <cr>
RILDrv : t : LoadEriData: Opening file
\Windows\eri.bin
RILDrv : i : Accumulated response (1) : 0 <cr>
RILDrv : i : Sending cmd :
AT+CSTT=1,1,18,22,26,30 <cr>
PMIC Boot cookie: rb7262h
RILDrv : i : Accumulated response (1) : 0 <cr>
RILDrv : i : Sending cmd :
AT+CSQT=1<cr>
RILDrv : i : Accumulated response (1) : 0 <cr>
RILDrv:i: Sending cmd:
AT+GMI; +GMM; +GMR; +CKEYPAD?25<cr>
RILDrv:i: Accumulated response: +CKEYPAD:25
RILDrv:i: Accumulated response (2): equesting :
IUSBON, USBST, New PLMST, timestamp, 10, 2,2944 <cr><lf>
RILDrv:i:Accumulated response(1): +IQMIREADY <cr><lf>
+IUSBON<cr><lf>+IECHO: Requesting:IUSBON, USBST,
New PLMST, timestamp, 10, 2, 2944 <cr><lf>
RILDrv:i: ParseNotificationOEM: +IQMIREADY: SetEvent for QMI Init
RILDrv:i: Accumulated response(1): +IUSBON<cr><lf> +IECHO:
Requesting: IUSBON, USBST, New PLMST, timestamp, 10, 2, 2944<cr><lf>
RILDrv:i: Accumulated response(1): +IECHO:
Requesting: IUSBON, USBST, New PLMST, timestamp, 10, 2, 2944<cr><lf>
RilDrv:arseGetEquipmentInfo Modem Version: 727
I found out one more thing, if you use the s+l+power comination when the phone is powered off and connected to the computer another USB device is found. I just found this thanks to conflipper's early work We will have to come up with some sort of driver for this now.
Here is the name of the device and the hardware IDs
Microsoft Pink Bootstrap
USB\VID_045E&PID_2345&REV_0000
USB\VID_045E&PID_2345
I also just found this hardware id when having the computer turned off and plugged into the pc. When I hold down u+s+b+power Windows finds another device with the following name and hardware IDs (According to what I have found online this VID is Nvidia.) So this might be where we can use the tegra chipset stuff.
APX
USB\VID_0955&PID_7416&REV_0103
USB\VID_0955&PID_7416
Thought I would also add that my phone is currently unusable, but on the positive side, I wouldn't found those other two usb hardware IDs if this hadn't happened. Sidenote, I was using QPST Configuration program, and I right clicked on the my phone in the active phones tab. I then clicked on "Configure service to port mapping..." and added one property (unforturnately, I can no longer go back to the window because the program doesn't recognize my phone now). At this point, my phone rebooted and is now stuck trying to boot up.
I don't think it is completely bricked, but I fear that until we pull a rom it is probably useless because it is stuck in a constant cycle trying to reboot. The only way to stop this is to remove the battery. I have since tried using the various key combinations provided by conflipper and have found that the bootstrapper combination (s+l+power) would probably work if we had a rom. I then tried the hard reset combination (c+b+power) which initially looks like it might work but then it gets stuck in the cycle of rebooting.
I am going to continue working on it, hoping that somehow now that I might have some extra sort of access to hardware, but I am afraid my contributions may be limited until we are able to pull a rom.
Sorry to hear that. There has to be a way of getting it out of the loop.
RevSkills Hardware Log.
Diag Port Supported Command List.
7E - TRS FRM MSG supported.
5A - CHECK AKEY supported.
59 - EFS CMD supported.
58 - GET IS95B supported.
57 - SET MAX SUP CH supported.
56 - SUP WALSH CODES supported.
55 - FER INFO supported.
51 - GET FEATURES supported.
49 - READ PRL supported.
47 - UNKNOWN unknown response:
45 - GET CDMA RSSI unknown response:
44 - CHANGE SERIAL MODE unknown response:
43 - GET PARAMETER unknown response:
42 - UNKNOWN unknown response:
40 - SET PILOTS unknown response:
3F - GET STATE unknown response:
3E - UNKNOWN unknown response:
3D - CONF SLEEP unknown response:
3C - GET PACKET SEQNO unknown response:
22 - DISPLAY EMU supported.
04 - PEEK DWORD supported.
03 - PEEK WORD supported.
02 - PEEK BYTE supported.
01 - Show ESN supported.
00 - Version Info supported.
Click to expand...
Click to collapse
(the phone rebooted many times while doing this test, hence the unknown responses).
I tested more of the options provided by the free version of Revskills and it was kind of funny to see how the keyboard emulator worked, but only for numbers.
After all the reboots and so, i got some hex descriptions for errors in a new folder, called Err. Uploaded a new screenshot from that folder contents.
Easy CDMA just lets you browse the filesystem we already know.... not so much fun.
Little update.
You seem to be able to enter the recovery mode holding the U S B + power option but, as i tried right now, also using "Volume -" + power as stated for other tegra devices. Can't check if that loads ok on the computer, as i dont have the usb cable here right now.
OOPS I made a mistake. I am not seeing anything using windows 7 using u+S+B and power up. Should I disable zune, change registry for zune back to normal etc??
You shouldn't have to because the device has a different hardware id, so the drivers installed for the zune portion aren't applicable. Try turning your phone off, plugging in the usb cable and then using the key combinations. If the new hardware message box doesn't appear, you should still see an unkown device in device manager.
Also you have to hold the u+s+b+power for a few seconds before it will be recognized. When I have done this the screen stays blank on my phone and the only way I know it is working is through Windows.
Using Windows 7 OS. I had to uninstall the zune driver located in portable devices in the device manager then it found new APX device and i was able to point to the NVIDIA driver. Tried ruining the phone (Flashing android to it) as in another thread but it also got stuck on the flashing prompt. Restarted phone normally and the windows found another device and loaded the zune drivers back.
Incidently, holding the volume down and power on does the same as the U+S+B+Power and is easier on the fingers.
Thanks and keep up the great work.
I again may have spoken to soon. I cannot duplicate the above scenario anymore.
I also can no longer transfer pictures taken with my phone on to my pc. I can add pictures to the phone from pc and back but not the ones taken with the camera. Originally I could with zune software. The folders for uploaded pictures are different then the ones taken with the phone. I really think that I screwed something in the phone up by playing with qpst and others.
I'm not sure about what you did there, but in my testing & curiosity purposes trials, i wasnt able to alter the device (do a write to memory), so i doubt that qpst or the others did it for you.
Also, according to coinflipper notes, the kin has several layers, including the SBL that is the one operating with the os directly (the "Ms Pink bootstrap" device), not the recovery mode, which basically put us handling a modem....
I'm trying some things, but no results yet... gonna take some time....
I have changed the USB password and added contacts (somewhere) while writing to the device using qpst. I changed the password to 000001. Is this a different part of memory I am fooling with?
Thanks
I am not sure. I have no previous experience with any phone deving nor Qualcomm tools. Just pointed what coinflipper said.
I said "basically a modem", cause you got diag(nostics) mode within a com port, and some users (in other posts) showed logs with AT commands.
I'm working with some tools to connect to the device, but using the driver we all got (zune software). Not promising anything, just peeking around some tests.
@mcdietz
Here I pasted a public output of the linux command "lsusb -vv" (ultraverbose) where Kin (factory default settings) values are.
http://pastebin.com/rZscb9wz
Is useful for usb access to the kin. Use at will.
I have been testing usb connections to the kin devices (the ones we used in this forum) and i checked this:
Kin mode (normal Zune mode):
- Using MTP protocol:
-- You can browse files/folders/track related to Zune values using the lib-mtp tools in the system you like.
-- You can format the device (zune related folders) & delete zune files using the lib-mtp tools.
-- You can't download files from the device using the lib-mtp tools (kin doesn't allow you to)
-- You can't upload files to the device using the lib-mtp tools (kin doesn't allow you to)
- Using raw USB:
-- You can Write & Read values to the device (Kin VID 0x045e, PID 0x0641). Protocol allowed: MTP
Click to expand...
Click to collapse
Of course, Zune software does use this mode and is allowed to write to the filesystem. But that's because before doing so, it uses MTP protocol values to send and receive crypto values based on JANUS from Microsoft (Microsoft DRM for Mobile Devices) and after crypto relationships, the usb commands enable the "Connected" window at the Kin.
Capturing and replaying this values over usb does not work (ever) and does not work for the kin (had to try), so no go-go from here. Also, we cannot know if it would be able (dreaming after bypassing the DRM) to go outside the pictures/music/etc folders.
On the other hand, MTP tools reports that our little friend is able to reproduce the following files:
Firmware file
MediaCard
Abstract Playlist file
Abstract Album file
JPEG file
Microsoft Windows Media Video
MPEG-4 Part 14 Container Format (Audio+Video Emphasis)
Advanced Audio Coding (AAC)/MPEG-2 Part 7/MPEG-4 Part 3
MPEG-4 Part 14 Container Format (Audio Emphasis)
Microsoft Advanced Systems Format
Microsoft Windows Media Audio
ISO MPEG-1 Audio Layer 3
Click to expand...
Click to collapse
Where firmware is strange and good but the question is... how to upload the firmwares files (you can get zune firmwares from the net) to the zune software on the device (and run them)?.
It's more interesting when you notice that firmwares contain "Zboot.bin" which is "Tegra device bootloader" but, sadly, doesnt work with nvflash because of what I said below. Those updates are WinCE updates too...
APX mode (nvidia "flashing" mode), with or without Nvidia driver.
- Using nvflash
-- You can't start flashing due to writing to usb error
-- Following attemps block the nvflash and device access.
- Using raw USB:
-- You can't Write or Read values to the device (APX VID 0x0955, PID 0x7416). Protocol allowed: None
Click to expand...
Click to collapse
This matches the post where coinflipper told us that you cannot dump the rom image.
Microsoft Pink Bootstrap (No driver):
- Using raw USB:
-- You can Write & Read values to the device (Kin VID 0x045e, PID 0x2345). Protocol allowed: Unknown
-- Phone answers "01" to all the write requests i did (from "00" to "FF").
Click to expand...
Click to collapse
markspace. com/kin/
Here's some software that was developed for it, but I'm guessing it is only client end?
I'm not allowed to link, so assemble the spaces yourself please
The link for the download (direct) , being for Mac(only) is:
http://www.markspace.com/kin/download.php
But you must register to get an activation code from the main page (posted by shlhu). It will need internet access to activate the software during installation and reboot after it.
Requires Itunes (for audio sync), Iphoto (for image, also have started it once), and Quicktime (for video).
I tested it with a fresh installed Snow Leopard and i can say that it works. I dunno how it does (without zune installed), but it works.
Unfortunately, i wasnt able to analyze the usb transmission there, so i cant compare with the windows one. If it can skip the JANUS drm, then we may have a chance. If it is the same process as windows... we are done... lol.
This is my first modern Windows Mobile (I used Windows Mobile 11 years a go) and it seems Microsoft was crippled the operating system.
Model: Bush Eluma, Windows 10 native (rebranded Archos 50 Cesium)
Specification:
Snapdragon 210
Adreno 304
1 GB RAM
16GB ROM
MicroSD support up to 128GB
5" 720x1280 IPS screen
4G LTE
WIFI/Bluetooth/GPS
8MP rear/2MP front with flash
2100mAh battery
Spec. Sheet: archos [dot] com/corporate/press/press_releases/EN_ARCHOS_50Cesium_50eHelium.pdf
What I'm trying to do: Interop-unlock
What I've managed to do: Deploy apps, such as Root Tool and vcREG
Where I'm stuck: Setting the value for my model of phone - I have no idea where to look
I hope I've provided information in a clear format. I'd very much appreciate some help or feedback in order to interop-unlock this model
System\Platform\DeviceTargetingInfo
PhoneManufacturer
Value = "True" (I think this used to just say "ARCHOS")
Thank you for reading.
Was there any progress made with this? Looking to interop unlock phone too so any help would be great
you tried this?
https://forum.xda-developers.com/windows-10-mobile/acer-liquid-jade-primo-upgrade-to-au-cu-t3589156
Worked a treat! Thanks a lot.
user154 said:
Sorry to kinda hijack this thread, but I have this device and struggling to find any other owners. My understanding is that the archos 50 cesium is the windows version of the 50e helium. I have an emmc dump of the 50e helium, if you cant already tell where im going with this, I want to flash this dump to my eluma b2 but cant get qfil or thor2 to do this. Can anyone help? or even know if this is possible?
Click to expand...
Click to collapse
I say just enjoy the W10 phone while you can, or if you really want Android, go buy that model online some where.
It is not as simple as it sounds. You would need at least a flash programmer for the SoC in that phone which usually the manufacturers never release. Depending on the format of the dump you might need other flashers or files to understand how the Archos 50 eMMC is structured or to utilize them in the flashing process. You would also want to be able to put the phone into EDL mode. If you can manage to even boot the flash programmer and initialize a flash of the phone there is also high risk of bricking it. Because you would be flashing partitions that were not signed for that phone/SoC. So I am not sure if you would also need to unlock the boot loader on it or not...sounds like you would. IMO it would be best to unlock the bootloader so you can backup the current layout of the phone. This as far as I know is not possible, so I would just stop there.
I know there are some threads in other forums where they are trying to do this with the IDOL 4s, and maybe a couple devices in the past have worked out to be able to do this. However it pretty much hinges on unlocking the boot loader. Also from what I know once you flash it like that and even if device survives (it boots, the IMEI is in tact, etc.) you cannot revert it back or it is pretty much impossible to go back without bricking it.
user154 said:
It doesnt really matter if the device is rendered unusable, it is quite a long way down the list of backup devices I have, it was more for the fun of trying to do it. The device is the exact same as its android counterpart (hardware wise) this is what made me think it should theoretically be possible. The dump I have was made with infinitybox, I have managed to create the required rawprogram.xml and patch.xml from the gpt binary contained within the dump. I have also found a couple of flash programmers for the soc (prog_emmc_firehose_8909.mbn, and a couple of manufacturer specific ones, pretty sure iv got the filename slightly wrong there). I have been able to boot the device to EDL mode using a cable, however sahara fails to load the flash programmer to the device. I didnt think the bootloader would need to be unlocked to flash the device seeing as the device is in EDL mode and what Im trying to flash is signed as is just the dump from the android counterpart. Maybe this is where im going wrong. Also Im working on the assumption the IMEI will be wiped as I plan to flash persist.img from dump too, I thought trying to keep the partition where it is stored in windows 10 and repartition the rest of the emmc to the same as the android counterpart might make things more complicated than they already are. Also IMEI can sometimes be quite simple to repair on certain devices (A lot more simple than what Im trying to acheieve here anyway). Can you point me in the right direction as to where I can find instructions to unlock the bootloader of this device? for some reason it doesnt get recognised by wpinternals (In any mode, EDL, standard flash mode, no idea what thats called on windows haha, or booted normally)
Click to expand...
Click to collapse
Sounds like you're on the right path. I'm not 100% sure you need to unlock the boot loader, however it would definitely make things easier as you could dump partitions from the phone as it is and even possibly enable mass storage mode. I am unsure where you would look to unlock that phones boot loader other than here. The flash programmers you have may not be built for the Windows Phone eMMC and why they are not booting.
Hi, this is quite interesting for me as I am struggling with 2 Cesium 40 devices stuck in Qualcomm download mode. I thought I managed to extract msimage.mbn and hex binary file from ffu, converted the hex file to hex.hex and added first and last-but-one lines. Although there was no way to escape from Qualcomm mode. Thor recognizes the Qualcomm deveices, but tells me to stop QFIL operations, even if there is no QFIL. Any ideas?
JoachimP said:
Hi, this is quite interesting for me as I am struggling with 2 Cesium 40 devices stuck in Qualcomm download mode. I thought I managed to extract msimage.mbn and hex binary file from ffu, converted the hex file to hex.hex and added first and last-but-one lines. Although there was no way to escape from Qualcomm mode. Thor recognizes the Qualcomm deveices, but tells me to stop QFIL operations, even if there is no QFIL. Any ideas?
Click to expand...
Click to collapse
If you have qpst/qfil installed on your PC, and have used them recently. The services might still be running. Just hunt for them in task manager and kill them and run thor2 again. See if that helps.
Worked a treat! Much obliged.
@nate0
Hi, thanks for your reply. I am nearly sure, I uninstalled QFIL and shutdown my pc after use, but I will check on it.
So I uninstalled QFIL and rebooted. This is the result:
C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode list_connections
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode list_connections
Process started Wed Nov 14 08:48:16 2018
Logging to file C:\Users\me\AppData\Local\Temp\thor2_win_20181114084816_ThreadId-4796.log
Debugging enabled for listconnections
WinUSB in use.
Connection list START
0.1A07:0004:0004 {71de994d-8b7c-43db-a27e-2ae7cd579a0c} Emergency mode connected
Connection list END
Exited with success
C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode emergency -hexfile cesium\hex.hex -mbnfile cesium\prog_emmc_firehose_8x10.mbn -ffufile cesium\flash_retail.ffu
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode emergency -hexfile cesium\hex.hex -mbnfile cesium\prog_emmc_firehose_8x10.mbn -ffufile cesium\flash_retail.ffu
Process started Wed Nov 14 08:48:52 2018
Logging to file C:\Users\me\AppData\Local\Temp\thor2_win_20181114084852_ThreadId-7500.log
Debugging enabled for emergency
Initiating emergency download
Using default emergency protocol
ALPHA EMERGENCY FLASH START
Emergency Programmer V1 version 2014.10.31.001
Hex download selected
Check if device in Dload
Message send failed with error code -1
Waiting connection to DLOAD: 2 of 2
Check if device in Dload
Message send failed with error code -1
Failed to connect to DLOAD mode
Make sure that the COM port is free. Close QPST.
ALPHA EMERGENCY FLASH END
Emergency messaging closed successfully
Operation took about 8.00 seconds.
THOR2_EMERGENCYFLASHV1_ERROR_PROGRAMMER_SEND_FAILED
THOR2 1.8.2.18 exited with error code 85030 (0x14C26)
Any suggestions?
Seems that there's a way to enable reset protection feature on non-american devices.
IT COULD BRICK YOUR PHONE POSSIBLY! DO IT AT YOUR OWN RISK!
I do not bear any responsibility for what may happen to your phone.
It works only on devices with WP 8.1 GDR2 and later firmware! It's, for example, Lumia 640. You can check firmware version using WDRT or lumiafirmware.com.
Actually, trick is only for Lumia 640, Lumia 550, Lumia 650, Lumia 950 and, possibly, Lumia 735.
Do not turn on reset protection and phone encryption at the same time. There's a bug in Windows, which can give you Bitlocker recovery screen after that.
One more warning: reset protection writes some stuff to UEFI. That can't be undone or changed neither by Windows Device Recovery Tool nor by the other flashers. So, it's most likely, that you won't be able to "delete" reset protection. But if can be turned off on supported phones just in Settings.
1) Download and install the program.
2) Download the necessary CAB file from Microsoft Update Catalog. Type in search, for example, 000-RU, then choose your build and click 'Download'.
Press Ctrl + F, type ‘reset’. 2 files will be found. You need file with the ‘CBS’ signature (not ‘CBSU’). Download it.
Here's a link to 14393.693 file.
3) Connect your phone to the PC.
4) Press Win + X and run Command Prompt (Admin).
5) Depending on your OS type, paste and run one of these commands.
32-bit: CD C:\Program Files\Windows Kits\10\Tools\Bin\i386
64-bit: CD C:\Program Files (x86)\Windows Kits\10\Tools\Bin\i386
6) Don’t close Command Prompt window.
7) Copy the address of the folder where downloaded CAB file is located. Important note: file must be in the separate
folder without any other files. The name of this folder mustn’t contain non-English characters or spaces.
8) Go back to the command line and paste the next command (without square brackets):
iutool -v -p [address of the folder with CAB file]
9) Your phone will restart and begin to install updates. It will take about 10 minutes. Do not disconnect the phone
from the PC during this operation.
After that you'll have reset protection button in 'Find my phone' settings.
Please, write here, if the operation will finish successfully for you.
I'll be thankful to anyone who will try make hard reset after that and reply, if reset protection is working for him.
To delete.
DilanChd said:
Work, but it must be send a OS update (just cbs cabs of device's packages), not just send this cab. @gus33000
Click to expand...
Click to collapse
IUTool installs this CAB.
To delete.
DilanChd said:
I know that. I means that you must also download and install all cbs cabs (of 10.0.14393.693 in your example) that corresponding to the packages installed on the device (GetDULogs).
Click to expand...
Click to collapse
We installed only selected CABs, when made Continuum or LED work. Why now we should install all the CABs?
To delete.
DilanChd said:
No idea, it's @gus33000 that said it, to enable reset protection.
Click to expand...
Click to collapse
Interesting. Let's wait for him.
working fine on my 950XL
To delete.
DilanChd said:
He told me that maybe for that the cab be in the same version as the OS. So, if that's it, if it's 14393.693 that is installed, install effectively only the ms_rs_protection 14393.693 cbs cab.
Click to expand...
Click to collapse
We do it in this way. We install only ms_rs_protection CBS CAB for 14393.693. No other CABs. Or you mean something else?
To delete.
DilanChd said:
Yes, that's what I mean.
Click to expand...
Click to collapse
So, no problem with that?
To delete.
Successfuly acivated Reset Protection for both my Xiaomi MI4 w10m for russian region. Got an email wich confirms this action. Also see the proove on my devices page.
Havent tried to reset it yet cause ive just spent alot of time to set my phones up perfectly)
#UP
what is the difference between CBS cab and CBSU cab? What happen if CBSU cab is flashed? Someone activate the Reset Protection from Settings, then he reboots the phone, then he got BitLocker Blue screen. I am wondering if he flashed CBSU cab?
HTC_FUZE said:
what is the difference between CBS cab and CBSU cab? What happen if CBSU cab is flashed? Someone activate the Reset Protection from Settings, then he reboots the phone, then he got BitLocker Blue screen. I am wondering if he flashed CBSU cab?
Click to expand...
Click to collapse
I think, it looks so, that CBSU is Update file which includes only changes, CBS is full package. microsoft.ms_reset_protection.mainos.cbs - 43 KB
microsoft.ms_reset_protection.mainos.cbsu - 28KB
So incomplete installation (of CBSU file) may take unpredictable effect
Can I do it on my l535 DS ?
The_Andro-geek said:
Can I do it on my l535 DS ?
Click to expand...
Click to collapse
yes
to all W10M devices with current build (not insider)
dxdy said:
(not insider)
Click to expand...
Click to collapse
it will work even for "Release preview" insider branch when it have the same build with Release. Have tested on my second MI4.
BTW
I've just tried to reset phone with "reset protection" enabled. so, how does It work (for me)
- reset of the phone by menu (settings - about - reset) require an account password
- after entering the password phone will be shown with "Reset protection" option turned to OFF (was obvious)
- during initial settings (right after setting up network) phone have checked reset protection state
- also "Reset protection" option is available (and turned ON by default) on quick parameters settings page
While the Nokia Lumia 530 isn’t officially supported, it’s still possible to get Windows 10 mobile running on it. At the time of writing, it has become a bit tricky to get it to work, since most official Microsoft tools are discontinued and will therefore not work. I will be linking the files which I’ve used. The credits to the people who made or shared the tools and guides I used will be at the bottom of this guide.
Note that I am not responsible for any damage made. Proceed at your own risk!
Prerequisites:
- A Nokia Lumia 530 running the Windows 8.1 Denim Update (will be referred to as "device")
- A stable Windows 7 system or VM, with .NET Framework 4.5.x or 4.6.x (on Windows 10, the IUTool will fail to synchronize, hence this requirement)
- An internet connection that can handle a download of approximately 2GB data on the computer and about the same on the phone
- A good USB cable (a flimsy one with a loose fit could brick the device while it’s updating)
- The programs linked below
First part of the installation:
1. Make sure the device is fully charged. If it’s not fully charged the device could get (soft-)bricked.
2. Factory reset the device, so you have as much storage as possible available on the device. After the reset is done, leave it at the language selection screen, because it doesn’t do anything there.
3. Extract HCTSW_WXMSOUP_V5.3beta6.update.lzma2.7z with 7zip or whatever you prefer.
4. Download the Visual C++ libraries from here: https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/ and run the install script.
5. The next thing you are going to do is download the updates, push them to the device and install them. This will take some time, but it depends on your internet connection for the most part. The files will be downloaded from the official Microsoft servers. Now here’s what to do: open run_en.cmd and follow the steps. These are pretty clear, so I don’t think I need to point all of them out here. It will open a webpage where you can download WDRT, you will need to install that for the tool to work.
6. Now you can move on to the second part.
Second part of the installation:
In this part of the installation, you will be updating the device from version 1511 to the latest available build, which should have a working Microsoft store.
1. The setup of the device. The version that just got installed doesn’t have a lot of options yet, including language packs. If you have a device that’s not English United States, the keyboard will bug out on setup, because it’s trying to access a language pack that doesn’t exist. Therefore, the first step, setting the language should be English (United States), so the OS itself won’t bug out. Once you’ve set the language (it will prompt to reboot, do that), you can go through the rest of the setup. Don’t log it into your Wi-Fi, don’t log it into your Microsoft account and don’t turn on automatic app updates. It’ll say it needs to set up apps, that takes some time but eventually you’ll get to the home screen. Now is when you need a few tools, which brings us to step 2.
Now is a good moment for me to point out that, if you have a non-English-US device, the keyboard for another language is still "installed". It can be removed by holding it in settings -> time and language -> keyboard and choosing “Delete”.
2. Installing Interop Tools. In order to get updates, you’ll need to modify your device a bit. This won’t be very hard, but it involves some registry modifications so you’ll have to pay close attention.
Go to settings -> update and security -> for developers and enable developer mode, so you can sideload the Interop Tools (Linked below). Copy the contents of the Interop Tools zip to the device first. Then, go to the file manager on the phone and go to the directory where you put the files. INSTALL THE DEPENDENCIES IN THE \ARM FOLDER FIRST, THEN THE INTEROP TOOLS FILE ITSELF! Check if the Interop Tools installed on the “all apps screen” and get ready to open it.
3. Modifying the registry. Open Interop Tools and tap the “This Device” button. This will bring up a menu.
3.1. Tap the menu button on the top left corner, then select “Modify Registry”. In the “Registry Key Path”, put SYSTEM\Platform\DeviceTargetingInfo. Then, put PhoneManufacturerModelName in the “Registry Value Name” box and tap the “Read” button at the bottom. You’ll see some text appear in a box. This will need to be edited to the following value: RM-1089_1048. After you did that, tap the “Write” button.
3.2. Now put PhoneModelName in the the “Registry Value Name” box and tap “Read” again. Now change the value to Lumia 535 and tap “Write”.
3.3. Exit out of Interop Tools and go to the next step.
4. Logging in to the Wi-Fi and checking for updates.
4.1. Logging it in to the Wi-Fi. Go to settings -> network & wireless -> Wi-Fi and choose your network. Easy peasy probably.
4.2. Checking for updates. This is the part that always went wrong with me, because of storage limits (gotta love that 4GB eMMC). But if I’ve explained this well enough, you might not have to do a lot of weird stuff. Oh well, to the instruction we go. Go to settings -> update and security -> windows update and check for updates. This will take a while! Keep it on wall power because updating can only be done at 40% or more at this point. I got two updates: from 1511 to early 1607 and from that to late 1607. Maybe you can get a newer version with WDRT or OTC but I doubt that to be honest.
Hooray! Now you should have a fully functional Nokia Lumia 530 with Windows 10 mobile!
Credits:
nemesis from Realmtech (for the registry changes) (https://www.realmtech.net/user/1)
@hikari_calyx (for the semi-offline update tool)
@STALKER18 (for the tips on how to clear storage)
@gus33000 (for the Interop Tools)
My dad (for the device)
Everyone who encouraged me to do this mod
Files:
Interop Tools: https://forum.xda-developers.com/attachments/interoptools_rc2_1-9-400-0_arm-zip.3995811/
And it's dependencies: https://forum.xda-developers.com/attachments/dependencies_arm-zip.3995814/
Windows 10 mobile semi-offline updater: https://forum.xda-developers.com/attachments/hctsw_wxmsoup_v5-3beta6-update-lzma2-7z.4955261/
PS: If you brick the device, the WDRT can restore it. If it just puts it in flashing mode, you can use Windows Phone Internals to download and flash a ROM. That tool can be found here: https://www.wpinternals.net/index.php/downloads/doc_download/46-wpinternals-2-8-zip
[ADDITION] Updating from build 1607 to 1709.
I said it wouldn’t be possible and it would break stuff, but I tried it and it doesn’t break anything some people say it might break. Yeah, it might impact on battery life a bit, but nothing has broken for me (yet), it has only improved.
I’ve learned that the update from 1607 to 1703 is the hardest one yet, but you should be able to get it going. This is because the preinstalled Store in 1607 can connect to the app update servers, but it can’t view the app. This is a difficult situation because many apps will become very large when they get updated. You need to figure out for yourself what gets you the space you need, but I found that uninstalling all the apps that can be uninstalled and deleting system apps through MTP (which can be done by bootloader unlocking, rooting and booting into mass storage mode with Windows Phone Internals (I recommend that you only delete OneNote, SkyDrive (as it’s being referred to in /data/program files/windowsapps) and the Xbox app).
Step 0: you might want to factory reset first
Let’s get to the updating though…
1. Modifying the registry. Open Interop Tools and tap the “This Device” button. This will bring up a menu.
1.1. Tap the menu button on the top left corner, then select “Modify Registry”. In the “Registry Key Path”, put SYSTEM\Platform\DeviceTargetingInfo. Now do the exact same as you did before, except use these “registry value names” and put the corresponding information into the box below that. Don’t forget to tap write!
Values you should use:
PhoneHardwareVariantRM-1104PhoneManufacturerMicrosoftMDGPhoneManufacturerModelNameRM-1104_11210PhoneModelNameLumia 950
1.2. Exit out of Interop Tools and go to the next step.
2. Logging in to the Wi-Fi and checking for updates.
2.1. Logging it in to the Wi-Fi. Go to settings -> network & wireless -> Wi-Fi and choose your network. Easy peasy probably.
2.2. Checking for updates. Go to settings -> update and security -> Windows Update and check for updates. This will take a while! Keep it on wall power because updating can only be done at 40% or more at this point. I got 3 updates, one from 1607 to 1703, one from 1703 to 1709 and another one from old 1709 to last 1709.
Credit to @demon2112 for the registry values
Can you backup your efiesp.bin partition and share?
augustinionut said:
Can you backup your efiesp.bin partition and share?
Click to expand...
Click to collapse
Did you break it?
Edit: WPInternals refuses to put the phone in mass storage mode so uh... Yeah...
I managed to get them off with Interop Tools
How?
augustinionut said:
How?
Click to expand...
Click to collapse
In the Interop Unlock menu, there's a mount entire storage option. Copied the EFIESP from there and compiled it into a bin. For WPI the Windows on the phone is too new :/
Thats why didnt worked
I wanted dumped partition with, WPInternals.
augustinionut said:
Thats why didnt worked
I wanted dumped partition with, WPInternals.
Click to expand...
Click to collapse
Yeah that doesn't work. Rename the .bin to .zip, extract, mount the phone in mass storage mode and copy the files to the EFIESP folder/symlink. If you can't do that, WDRT can probably unbreak it
Please anounce me when you can upload the dumped partition.
Is resulting that efiesp.bin , data.bin and mainos.bin are related, so i cant upgrade my phone to windows 10 mobile without them.
augustinionut said:
Is resulting that efiesp.bin , data.bin and mainos.bin are related, so i cant upgrade my phone to windows 10 mobile without them.
Click to expand...
Click to collapse
Just flash the original FFU. Literally all I did is in the guide and I never had to flash something from another device
Thanks, but: my phone was reflashed with reset protection active. Guess what?
augustinionut said:
Thanks, but: my phone was reflashed with reset protection active. Guess what?
Click to expand...
Click to collapse
Something that might work (according to a friend. Again, I am not responsible for a phone that gets rendered useless)
Mount as mass storage, diskpart clean the thing, hold power button for ~10 seconds, flash a bootloader with WDRT (may fail 2-3 times), flash FFU
_Yep, erase clean DPP partition )) buhahahaha
How do you get to the Denim update? I'm getting the error that I am running a build older than 8.10.14219.341 and need to update first.
EirikrHinnRauthi said:
How do you get to the Denim update? I'm getting the error that I am running a build older than 8.10.14219.341 and need to update first.
Click to expand...
Click to collapse
You can download and flash it in WPInternals (will delete all data so back that up first) or WDRT (not sure if that erases userdata)
BennoMP said:
You can download and flash it in WPInternals (will delete all data so back that up first) or WDRT (not sure if that erases userdata)
Click to expand...
Click to collapse
WDRT already says I'm at the latest version of Windows for my device, so that sucks. I shall try WPInternals! Thanks!
Would you please transfer a video of the process?
BennoMP said:
While the Nokia Lumia 530 isn’t officially supported, it’s still possible to get Windows 10 mobile running on it. At the time of writing, it has become a bit tricky to get it to work, since most official Microsoft tools are discontinued and will therefore not work. I will be linking the files which I’ve used. The credits to the people who made or shared the tools and guides I used will be at the bottom of this guide.
Note that I am not responsible for any damage made. Proceed at your own risk!
Prerequisites:
- A Nokia Lumia 530 running the Windows 8.1 Denim Update (will be referred to as "device")
- A stable Windows 7 system or VM, with .NET Framework 4.5.x or 4.6.x (on Windows 10, the IUTool will fail to synchronize, hence this requirement)
- An internet connection that can handle a download of approximately 2GB data on the computer and about the same on the phone
- A good USB cable (a flimsy one with a loose fit could brick the device while it’s updating)
- The programs linked below
First part of the installation:
1. Make sure the device is fully charged. If it’s not fully charged the device could get (soft-)bricked.
2. Factory reset the device, so you have as much storage as possible available on the device. After the reset is done, leave it at the language selection screen, because it doesn’t do anything there.
3. Extract HCTSW_WXMSOUP_V5.3beta6.update.lzma2.7z with 7zip or whatever you prefer.
4. Download the Visual C++ libraries from here: https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/ and run the install script.
5. The next thing you are going to do is download the updates, push them to the device and install them. This will take some time, but it depends on your internet connection for the most part. The files will be downloaded from the official Microsoft servers. Now here’s what to do: open run_en.cmd and follow the steps. These are pretty clear, so I don’t think I need to point all of them out here. It will open a webpage where you can download WDRT, you will need to install that for the tool to work.
6. Now you can move on to the second part.
Second part of the installation:
In this part of the installation, you will be updating the device from version 1511 to the latest available build, which should have a working Microsoft store.
1. The setup of the device. The version that just got installed doesn’t have a lot of options yet, including language packs. If you have a device that’s not English United States, the keyboard will bug out on setup, because it’s trying to access a language pack that doesn’t exist. Therefore, the first step, setting the language should be English (United States), so the OS itself won’t bug out. Once you’ve set the language (it will prompt to reboot, do that), you can go through the rest of the setup. Don’t log it into your Wi-Fi, don’t log it into your Microsoft account and don’t turn on automatic app updates. It’ll say it needs to set up apps, that takes some time but eventually you’ll get to the home screen. Now is when you need a few tools, which brings us to step 2.
Now is a good moment for me to point out that, if you have a non-English-US device, the keyboard for another language is still "installed". It can be removed by holding it in settings -> time and language -> keyboard and choosing “Delete”.
2. Installing Interop Tools. In order to get updates, you’ll need to modify your device a bit. This won’t be very hard, but it involves some registry modifications so you’ll have to pay close attention.
Go to settings -> update and security -> for developers and enable developer mode, so you can sideload the Interop Tools (Linked below). Copy the contents of the Interop Tools zip to the device first. Then, go to the file manager on the phone and go to the directory where you put the files. INSTALL THE DEPENDENCIES IN THE \ARM FOLDER FIRST, THEN THE INTEROP TOOLS FILE ITSELF! Check if the Interop Tools installed on the “all apps screen” and get ready to open it.
3. Modifying the registry. Open Interop Tools and tap the “This Device” button. This will bring up a menu.
3.1. Tap the menu button on the top left corner, then select “Modify Registry”. In the “Registry Key Path”, put SYSTEM\Platform\DeviceTargetingInfo. Then, put PhoneManufacturerModelName in the “Registry Value Name” box and tap the “Read” button at the bottom. You’ll see some text appear in a box. This will need to be edited to the following value: RM-1089_1048. After you did that, tap the “Write” button.
3.2. Now put PhoneModelName in the the “Registry Value Name” box and tap “Read” again. Now change the value to Lumia 535 and tap “Write”.
3.3. Exit out of Interop Tools and go to the next step.
4. Logging in to the Wi-Fi and checking for updates.
4.1. Logging it in to the Wi-Fi. Go to settings -> network & wireless -> Wi-Fi and choose your network. Easy peasy probably.
4.2. Checking for updates. This is the part that always went wrong with me, because of storage limits (gotta love that 4GB eMMC). But if I’ve explained this well enough, you might not have to do a lot of weird stuff. Oh well, to the instruction we go. Go to settings -> update and security -> windows update and check for updates. This will take a while! Keep it on wall power because updating can only be done at 40% or more at this point. I got two updates: from 1511 to early 1607 and from that to late 1607. Maybe you can get a newer version with WDRT or OTC but I doubt that to be honest.
Hooray! Now you should have a fully functional Nokia Lumia 530 with Windows 10 mobile!
Credits:
nemesis from Realmtech (for the registry changes) (https://www.realmtech.net/user/1)
@hikari_calyx (for the semi-offline update tool)
@STALKER18 (for the tips on how to clear storage)
@gus33000 (for the Interop Tools)
My dad (for the device)
Everyone who encouraged me to do this mod
Files:
Interop Tools: https://forum.xda-developers.com/attachments/interoptools_rc2_1-9-400-0_arm-zip.3995811/
And it's dependencies: https://forum.xda-developers.com/attachments/dependencies_arm-zip.3995814/
Windows 10 mobile semi-offline updater: https://forum.xda-developers.com/attachments/hctsw_wxmsoup_v5-3beta6-update-lzma2-7z.4955261/
PS: If you brick the device, the WDRT can restore it. If it just puts it in flashing mode, you can use Windows Phone Internals to download and flash a ROM. That tool can be found here: https://www.wpinternals.net/index.php/downloads/doc_download/46-wpinternals-2-8-zip
Click to expand...
Click to collapse
Hello! I followed your step with editing values and after checking updates, there was an update which is Windows 10 Mobile (10.0.14393.1066) as of now, May 2022.
my question is what is the size of this update? and will I able to install this with my Lumia 530?
any other way to install this offline? i really need this update because I need working Microsoft Store.
Thanks...