Rm-1104 Firmware

[Siiri]

Aswe reported earlier, Microsoft released a new firmware update for Lumia 950 and Lumia 950 XL devices. Now Microsoft has published the list of Lumia 950 and Lumia 950 XL variants which are getting new firmware updates.

I want to assure you that this is very hard to brake the phone. Even if you destroy the phone partition this is restorable with Windows Device Recovery Tool which is official Nokia/Microsoft tool for service centers. This tool will download a latest firmware from support servers (still operate) and flash your phone even with broken partitions (just need to do it twice). There are other ways to flash FFU, e.g. from WPInternals.

We need to unlock the phone to manipulate with GPT. This is done by WPInternals tool which is well crafted .NET application that supports all Lumia phones line up to first Lumia 800. NOTE: Unlocking bootloader will block official Windows Update channel, so before gold install you need to update Windows 10 Mobile a little bit.

The phone can be in one of 4 modes: 1) Normal mode (when you pluggin the phone with default drivers in host OS); 2) Flash mode (for unlocking and locking the bootloader, needed for our experiments); 3) Mass-storage mode (for manipulating with direct access to GPT); 4) Label-mode (we don't need it). There are only following name and root key hashes combinations (Lumia AA64 models). The code for determining the model could be found in Deployer.Lumia.NetFx namespace. This information is needed to know which drivers should be applied to Windows folder from WIM image.

So the second step is to unlock your phone with WPInternals tool. During this step WPInternals will force you to download freshly updated firmare to your disk as FFU file, so later you can WPInternals to flash too. Also this is a way how FFU files are being distributed over internet among enthusiasts.

EFI is a a new BIOS. Three years ago I made two notes about EFI: LUA.EFI and State of EFI in 2016. I love hacking EFI. So we basically need to setup three EFI applications and one UEFI.elf: 1) BootShim.efi for booting Windows 10 Pro (); 2) developermenu.efi for developer menu inside NTOSLDR with diagnostic routines and Mass-storage mode enabler; 3) WinLoad.efi for bootin Windows 10 Mobile; 4) UEFI.elf. These file should be placed at following locations:

For each partition x perform nessesary flags and after that list all your partitions you want to include into NTOSLDR boot menu. It may include all EFI modules you may found running or developed by yourself!

DISM is the tool for managing WIM images, apply them to partitions, patch drivers and service packages. WIM is new ISO-9660 from Microsoft created especially for Windows provisioning. E: drive here contains regular ISO image of Windows 10 for ARM64.

WOA brand means Windows on ARM64. Everything starting from GPT step could be done automatically by WOA Deployer tool written by Jos Manuel Nieto Snchez who helped to make this post clean, who enlightened essential parts and clarified the nessesary sequences to complete the setup. This manual is slightly based on his pre-WOA document, also at the end here is historical video of first runs. Find the latests release builds or build WOA Deployer yourself (it's under MIT license):

I'm using a prologix GPIB to USB converter rev 6.4.1

-6.0.pdf

I've linked the manuals for both devices.

I'm doing this all through a windows 10 Device. I have tried to connect through the VISA interactive application but I consistently get the "Visa ErrorCode: 0xBFFF0015 (-1073807339)" error or "VISA: (Hex 0xBFFF0015) Timeout expired before operation completed.". I have looked through the troubleshooting guide for that error code but I am confused and don't really know what I'm doing. Firstly I've looked through the manuals I've listed to find some information on baud rate, termination characters but I can't find this information.

I've tried going through the keysight IO manger and it gives me the same issues. I believe I have installed the correct drivers to my adapter and successfully updated the firmware on the devices as the website recommends. I also believe I have the correct drivers eg NI-VISA and the NI-488 Driver. I'm not sure if I have my particular devices drivers since when I go to this link the drivers are not for windows 10

-detail/driver/vxiplugplay-driver-for-836xx-blseries-swep...

Any help is greatly appreciated.

Also I have gotten a USB connection (non GPIB) to work with a SIGLENT SDS 1104X-E and was able to successfully control that using python if that means anything for this GPIB case.

I fixed it! I believe it had to do with the address of the device and I needed to write some code to configure the adapter. I can't remember where I downloaded the GPIB Configurator from but this is what the icon I used looks like. and I'm pretty sure the website was this.

No idea. I had a Harmony meltdown last night when I tried to replace remotes. Had to find a Win 10 laptop to clear all the pairings. It wasn't fun. I wouldn't doubt a firmware update took place, but a few factory resets for sure. I used it as a chance to upgrade the Logitech code to use components, so this is the first time on the new version.

The 4 Home control buttons. They stopped working this past week.

I'm using them to control lights in my home.

Yes, I remember some workaround with SmartThings.

Can you please point me to the new workaround?

Thanks for an awesome driver.

I just got a projector lift that work with RF, I have a broadlink RM4 Pro, if I add it to hubitat, can I assign the lift buttons to the harmony hub and use it in scenes?

trying to minimize the number of remotes (Harmony, phone, etc etc)

thanks again,

Thanks, I will give that a try once I get the Broadlink to learn my RF codes.

what I want to do is basically create a scene that has a step to lower the projector lift and to raise it when I press off.

my guess is that the device will be in Hubitat and broadlink but I don't know how to make it appear in the harmony hub.

I own a couple of tvboxes bought in a private exchange market by a seller claiming they were not working(stuck on ANDROID logo = for sure bad firmware inside) Since the price was really low i bougth some and discovered that mainly the inner processor is rk 3229 from rockchip. A quick search about the possibility to install linux on those tvboxes lead me to the very first approach on theme:

_core

Well, I thought If already someone did it , I can do it too; that was the beginning of one of worst nightmares of my life

Those boards are totally different even when they look similar: some have nand storage, some have emmc, some have ddr2 ram, some ddr3, some have ddr 330 mhz , some other 300, some have GPT partitioning some other have a system called rk_parameter , some control led in a manner some others in other manner.

The first approach was a complete disaster, not even booting or, when booting , missing pieces of hardware or/and nand storage drivers. Then luckly I met two persons that helped me a lot: first thanks go to the man that owns this github:

Mr. Justin Swartz

and then thanks also Mr. Willerson from another forum that discovered where was the neck bottle that prevent booting the boards and let them work smoothless ( before boards stopped to work after 29.59 minutes as you can read on Justin Swartz github)

I am not a coder , I am a good technician in soldering and I had many boards to experiment on , the joint venture coders/tester was successfull , so finally I/We can say there is a good method to boot the mayority of those bords and have a complete linux system aboard.

DISCLAIMER

this method still has a problem : NO HARDWARE acceleration from GPU by missing/lacking libraries that "couple" kernel drivers ( MALI 400 ) with userspace libraries : the decoding of video is made by CPU so AT THE ACTUAL STATE no 4k and even youtube on chromium isn't working at the top performances

So if someone is looking to replace android for better video performances, well go back on android !!!!!

SECOND DISCLAIMER

I will not release any binary or/and pre compiled stuff: not because I want to hold and hide the discoveries for my self, but because I DON'T want any responsability on bricking, destroying, hidden malwares, security holes in firmware.

You have to do by yourself following those instruction or use the original things shipped with original firmware adapted to your needings

WHAT is necessary:

1) AndroidTool_Release_v2.67.zip

2) a pc running UBUNTU/Debian distro for cross compiling

3) rockchip official toolchain, kernel version is 4.4.189 -linux/kernel

4) gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf.tar.xz

6) original/official firmware of you actual tvbox ( there are pleeeentyyyy.. kingbox, leelbox, stock android) before doing ANYTHING be sure you can go back (Fortunately those boards are very UNBRICKABLE since they have a inner,but inner, but inner bootrom not accessible by user so, unless you do a PHISYCAL DAMAGE you will alway able to re-life the board)

5) having a serial connection ttl/usb could save many hours blaming and avoid headaches I strongly reccomend having a serial debug

We will use the method described here :

and here -REPLACEMENT.md

all credits go to the OWNER of that github JUstin Swartz

START

1) git clone -linux/kernel As previously said we will obtain kernel 4.4.189

2) search on the net for gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf.tar.xz ( assuming your pc is 64bit)and put somewhere. Untar it

3) go into directory kernel-develop-4.4-189 and do : make ARCH=arm linux_defconfig you will obtain a basic .config for the compilation

here is it one config modded to enable rknand support, you can open and edit as per you needing YOU MUST RENAME from .config-linux to .config (there is a dot)

3a8082e126