Develop Bugs

USB Host?

I noticed that the Com5+ releases (include WMD/280xx) have several drivers included (some of these used to be provided by OEMs and many exist in desktop windows):
usbd.dll
usb8023.dll
vmini.dll
ne2000.dll
tcpstk.dll
rndismp.dll
netmui.dll
ndis.dll
dhcp.dll
They have their reg settings and are loaded, but I am not sure exactly what they provide?
The first USBD is usually for USB Host functionality.
Some of this may be related to dlna functionality planned for Com5.
Anyone that knows more about these drivers, please chime in..

USB Host?
lol.
If your device is capable of USB Host, it's determined by your chipset. If it supports Host mode, it needs the required drivers (not generic and not from Microsoft as they are chip dependant) to make it to work properly as USB host.
However...
usbd.dll -> USB stacks driver. Needed for USB proprietary drivers to work.
usb8023.dll -> USB-To-LAN for RNDIS
vmini.dll -> Ethernet virtual adapter driver (used for debug sharing procedures)
ne2000.dll -> NE2000 Ethernet driver for NE2000 compliant ethernet chips (useless with newer devices)
tcpstk.dll -> TCP/IPv4 stack
rndismp.dll -> RNDIS driver (for WMDC/Activesync capability)
netmui.dll -> Another support driver for WMDC/Activesync support
ndis.dll -> Support for Ethernet drivers to be written/loaded and to work correctly
dhcp.dll -> Support for DHCP.

To be clear - these are from the Raphael build, I have not looked at builds for other devices.
- It is unusual to see MS add drivers from one COM branch to the next.
- Some dlna functionality and some new bluetooth protocols will be supported in the com5+ branches.

pidsw said:
To be clear - these are from the Raphael build, I have not looked at builds for other devices.
- It is unusual to see MS add drivers from one COM branch to the next.
- Some dlna functionality and some new bluetooth protocols will be supported in the com5+ branches.
Click to expand...
Click to collapse
We need a USB-OTG Specified device to do USB Host stuff.. Else try zenos Usb host drivers + power injecter >.>...a bit of a drag..but works if u can make it

[GUIDE]WINDOWS 8 LIVE USB : install it on a USB KEY - UPDATE 11/01/13 - RTM TOO !!!

Hello to all ...
I have received many requests from some other forum users with whom I collaborate x and I am here today to explain how I solve a problem that does not yet seemed to have a solution ...
I WANTED TO INSTALL WINDOWS 8 ON A USB KEY AND ON THIS
THEN IT RUNS DIRECTLY !!!
I'm not talking about putting the ISO on a USB Key and then install it on your hard disk of a PC but installing it directly on it so it's ready to run on every PC on which we put the key.
NB I would like to remind everyone that the version of Windows 8 used from myself for these experiments is Windows Customer Preview 8 32 BIT, it is freely and can be found on Microsoft's site and downloading is free. This is not the ultimate version 'cause Win 8 is not out yet (due out in late 2012, perhaps) or a pirated copy. Therefore I don't intend to encourage or push someone to piracy. All of following is perfectly legal.
A few simple steps and an afternoon of testing. Here's how I did:
01) download the ISO of Windows 8 Customer Preview from Microsoft's Site (English)
02) note the relative activation KEY (always English)
03) unzip the ISO of windows with WinRAR to any folder on your PC
04) unzip the file /SOURCES/INSTALL.WIM with "UniExtract" (universal extractor) in any folder on your PC
05) have a partition of at least 12 GB free on your USB stick
06) format it, if u want, as NTFS format with Cluster Size = 1.024 bytes or 2.048 bytes
07) from the disk management of windows on that partition, run the "mark partition as active" so that the PC can then use it to boot
08) copy the entire contents of extracted INSTALL.WIM to that partition (except the trash folder, RECYCLE.BIN)
09) open the attachment that I put here in RAR, copy the 2 files on the USB KEY and from the DOS command line ( if not works, run DOS Shell as administrator ):
10) bcdboot.exe X:\windows /s X:
11) bootsect /nt60 X: /force
where X is the letter of the partition used in the USB stick. Reboot and ensure that the PC starts from USB stick. In figure 01 you can see my 8 partitions on the same USB drive where I have Windows 7 32 & 64 BIT, WINDOWS 8 32 & 64 BIT, LINUX Pinguy 32 & 64 BIT, Easeus Todo Backup Recovery with Linux shell.
NB The above guide works with the English version of Win 8 Customer Preview 32 BIT as well as the same 64 BIT only that the second requires a bit' more size (about 3 GB +). My guide is the minimum requirement under the which wraps everything but if u want it running more lean, fast and efficient, then we say that the ideal is 16 GB free for the 32 BIT and 20 GB for the 64 BIT.
The first start will make the whole configuration of the system, will ask for the key to activate the free copy of the system, your name, a password that you
can create, etc. From second boot, windows 8 will start in half a minute on a dual core processor with 2 GB of RAM. I remind you that booting from USB, will never be as fast as if it were installed on the hard disk, unless you have a USB 3.0 and never the same also in this case...
THIS IS A PREVIEW, THIS METHOD IS NOT YET FOUND IN THE WEB. I CREATED IT ONLY YESTERDAY AFTERNOON BEING ABLE TO DO IT WORKS. MY PROBLEM WAS THE COMMAND LINE FROM DOS BUT NOW IT'S PERFECT AND WORKS PERFECTLY ... SHARE THIS HOW TO IF YOU WANT, JUST PLEASE REMEMBER TO WRITE MY NAME ... PYCON IS ALWAYS QUALITY !!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
UPDATE 11/01/2013 => WINDOWS 8 RTM 32 & 64 Bit
Hello everyone ... After a while 'on the run, I remembered having to try again with the release of Windows 8 RTM Build 9200, then finally ... 2 little hours for testing a program of which I already knew the existence ( not new, just some persons often combine this program with wrong DOS command or not right card format ) et voilà ! IN A FEW STEPS, WINDOWS 8 LIVE USB ... RTM VERSION AND PREVIEWS TOO ( I tried with my old Consumer Preview, I assume that it might work with the very old Developer one ). However, if the preview doesn't work, my previous method still works for sure with the previews...
Pre-requisites:
A) have the ISO Microsoft Windows 8 RTM ( remember men... the free trial is 90 days)
B) have a PRIMARY partition at least 12 GB free space on the USB drive formatted in NTFS with the choice between
- Cluster Size = 512 bytes
- Cluster Size = 1024 bytes
- Cluster Size = 2048 bytes
C) have the two little programs WINRAR (including trial version) & GIMAGEX (opensource)
Here's how:
01) open with WINRAR the ISO of Windows 8 RTM ( or the release u want to use )
02) extract the file /SOURCES/INSTALL.WIM to the hard disk ( where you want )
03) open with GIMAGEX ( Image Extractor Tool ) the file INSTALL.WIM... This's a small portable utility, download it, unzip it where you want and open the executable in 32-bit or 64-bit EXE depending on your system:
- go to 2nd tab "APPLY"
- in the 1st field "Source", click once on Browse and select your file INSTALL.WIM
- in the 2nd field "Destination", click once on Browse and select the root of your USB drive (eg X: )
- in the 3rd field "Image" you can check by clicking on Select that it's the NUMBER 1
- "Verify" not flagged
- "Check" not flagged
- click on APPLY and wait ... here it's stolen to me about 20 minutes ... depends on key and system ...
04) from disk management builted in windows, choose the partition of the USB key used and right click to "mark partition as active" so that the PC can then use it to boot
05) open a DOS command line with administrator privileges
06) go to the directory of the key X: \ Windows \ System32 where X: is the partition of the USB key
07) bcdboot.exe X:\windows /s X: /f ALL
FINISHED!
ENJOY IT !!! PYCON RULEZ !!!

wow, that's impressive. thanks for this guide, im gonna try it out very soon

Awesome

I want to try thid method.... but the attached file is unavailable‼

onisto said:
I want to try thid method.... but the attached file is unavailable‼
Click to expand...
Click to collapse
I can download it with no problem...

Left click on "Boot.RAR" --> "404 Page Not Found
The page you requested was not found."

onisto said:
Left click on "Boot.RAR" --> "404 Page Not Found
The page you requested was not found."
Click to expand...
Click to collapse
Incredible, I try to reattach it...

THX, now it's downloadable!

is this also working, when i plug the usb stick in my transformer prime?
that would be awesome!

KingGong said:
is this also working, when i plug the usb stick in my transformer prime? that would be awesome!
Click to expand...
Click to collapse
Ehm... what's transformer prime ?

PYCON said:
Ehm... what's transformer prime ?
Click to expand...
Click to collapse
the best android tablet at the moment! it comes with a docking station with usb 2.0 port that's why i asked

KingGong said:
the best android tablet at the moment! it comes with a docking station with usb 2.0 port that's why i asked
Click to expand...
Click to collapse
I don't know it so... try...

KingGong said:
is this also working, when i plug the usb stick in my transformer prime?
that would be awesome!
Click to expand...
Click to collapse
No, because the proccesor in your prime has an ARM architecture so it wan't boot a 32 bit system. It also doesn't have BIOS to boot from USB.
Sent from my U20i using XDA

how long did it take you to "unzip" the install.wim ?

Somebody have lenovo tablet try them but i dont knw about the chipset

k.janku1 said:
how long did it take you to "unzip" the install.wim ?
Click to expand...
Click to collapse
It depends of performance of your PC.
INSTALL.WIM is 2,5 average size file, so on my I7 the uncompress
got me waiting for about 6 / 7 mins... So try, if u jave a dual core
it's possible u've to wait up to 12 / 15 mins to uncompress it...

If you format the USB where W8 is on, then its normally removed?

Marc. said:
If you format the USB where W8 is on, then its normally removed?
Click to expand...
Click to collapse
Yes, but whwn I had it installed on a second partiton of my HDD and then formatted it, I couldn't boot back to windows 7

Marc. said:
If you format the USB where W8 is on, then its normally removed?
Click to expand...
Click to collapse
No man, u can't format the usb key on which u've installed Win 8.
'cause for the system, it's the C: and so the system partition, u
can't format it, resize it, remove it from usb tray icon...

@pycon: I think he meant that he wanted to format it from Windows 7 (or whatever his other OS is), and I think it's safe to do that.
@k.janku1: That's because Windows 8's dual boot screen is shown AFTER Windows 8 actually boots, so before deleting Windows 8 you first have to remove it from the boot list in "msconfig" (just type that in the search), and if you already formatted your HDD partition where Windows 8 is installed, then your only solution is to repare your MBR using a Windows DVD or some other boot tool like SuperGRUB (it can restore Windows MBRs too, not just Linux!)

[HACK] Using complete Windows API in Windows Store app (c++)

As we know, MS prohibits using most of standard Win32 API in Windows Store applications. Obviously there are lots of ways to overcome this limit and to call any API you like, if you are not going to publish your app on Windows Store. And here is one of them.
Idea is really simple and rather old (lots of viruses use it): search for kernel32.dll base in memory, then parse its exports for LoadLibraryA and GetProcAddress, call them - and get profit.
Writing here so this post can be indexed by google.
Partial code:
Code:
void DoThings()
{
char *Tmp=(char*)GetTickCount64;
Tmp=(char*)((~0xFFF)&(DWORD_PTR)Tmp);
while(Tmp)
{
__try
{
if(Tmp[0]=='M' && Tmp[1]=='Z')
break;
} __except(EXCEPTION_EXECUTE_HANDLER)
{
}
Tmp-=0x1000;
}
if(Tmp==0)
return;
LoadLibraryA=(t_LLA*)PeGetProcAddressA(Tmp,"LoadLibraryA");
GetProcAddressA=(t_GPA*)PeGetProcAddressA(Tmp,"GetProcAddress");
CreateProcessA=(t_CPA*)PeGetProcAddressA(Tmp,"CreateProcessA");
HMODULE hUser=LoadLibraryA("user32.dll");
MessageBoxA=(t_MBA*)GetProcAddressA(hUser,"MessageBoxA");
MessageBoxA(0,"A native MessageBox!","Test",MB_OK);
STARTUPINFO si;
memset(&si,0,sizeof(si));
si.cb=sizeof(si);
PROCESS_INFORMATION pi;
CreateProcessA("c:\\Windows\\system32\\cmd.exe",0,0,0,FALSE,0,0,0,&si,&pi);
}
Complete project is attached. It contains sources and compiled appx files for side-loading.
Code compiles fine for x86/x64 and ARM, tested on x86/x64. Can someone test it on ARM? Ability to sideload metro apps is required.
The application should output a MessageBox, then execute cmd.exe.
A note: Windows Store application runs in a sandbox and as a limited account, so most of API returns "access denied". You can check this in a launched CMD - it displays "access denied" even on a "dir" command because normally "modern ui" apps don't have even read access to c:\.
To overcome this - add "all application packages" full control to the directories/objects you like (for example to c:\).

Works perfectly on my Windows 8 x64 Tablet :good:... its not ARM based though ...

Can i use this to run a non-store app?
Here is the catch, I have managed to get the installed (not the installation) file from a kind member here on XDA. But when I paste the folder in:
C:\Program Files\WindowsApps\Microsoft.ZuneMusic_1.0.927.0_x64__8wekyb3d8bbwe
The app isnt seen on the metro UI?
Any way to start a scanner of some sorts so that I can see the app in Metro.../?
THanx a ton!
Plz feel free to laugh a little at my noobish question...im stil learning..

Works perfectly on my surface RT!
but type dir in CMD returns "access denied".

There are no code signature checks from the command prompt that you launch.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <iostream>
void main()
{
std::cout << "Hello RT World!\n";
}
Compiled as an exe with info in http://stackoverflow.com/questions/...op-programs-be-built-using-visual-studio-2012

Open properties of your disk c:, go to the security tab and add "ALL APPLICATION PACKAGES" == full control. In this cage "dir" command would work, and your apps would be able to access whole filesystem.

Sorry if it's unrelated, but does RT check signatures for loaded DLLs too? Can one run regedit and change some system CLSID to point to unsigned library, will it be loaded?

Simplestas said:
Sorry if it's unrelated, but does RT check signatures for loaded DLLs too? Can one run regedit and change some system CLSID to point to unsigned library, will it be loaded?
Click to expand...
Click to collapse
Unless the dll is loading with a restricted security policy (such as through a Metro app) it is checked, yes.

Excellent work on the 'App1' technique of starting a cmd prompt from a modern app, and the fact it can run other unsigned cmd line apps.
Note that the cmd prompt still runs in the modern app container and probably has lots of restrictions
And also it only runs when the modern app is running and effectively freezes when the modern app goes into the background and suspends
Don't seem to be able to run win32 gui apps from the cmd prompt it starts -- they start but immediately terminate, presumably because the full win32 stuff cant initialise in a modern app container.
But can tum gui win32 api's, like the create dialog one, from the App1 modern app
Luckily we can also test, investigate and debug this on an intel Windows 8 system (dual monitor is best) when trying to work out what is going on, and then test on ARM after that.

@Simplestas: LoadLibrary is also blocked, I'm afraid. One fo the first things I tried was creating a DLL compatible with the built-in rundll.exe program and using that. It failed to load the third-party library.
@xsoliman3: Don't forget the debugger. You can't run it on the RT device right now, but there are (official) tools for debugging RT apps remotely. That should allow connecting to the child process and seeing what happens as it starts up.

GoodDayToDie said:
@Simplestas: LoadLibrary is also blocked, I'm afraid. One fo the first things I tried was creating a DLL compatible with the built-in rundll.exe program and using that. It failed to load the third-party library.
@xsoliman3: Don't forget the debugger. You can't run it on the RT device right now, but there are (official) tools for debugging RT apps remotely. That should allow connecting to the child process and seeing what happens as it starts up.
Click to expand...
Click to collapse
Great seeing you again!
Anyways, I determined from some work with the VS Remote Debugger that the integrity checks are enforced in ZwCreateUserProcess. But, I bet LoadLibrary has its integrity checks in user-mode, since it normally doesn't access any functions using a call-gate to the kernel on Windows 7, which would mean we can modify it to allow us to load unsigned DLL's.
However, with this vulnerability, I had a different. What about allowing a native application to open, such as Notepad, and before it reaches the entrypoint, remotely injecting a different application to be ran (this would involve some sort of custom LoadLibrary + CreateRemoteThread pair of functions)? With the VS Debugger, you can already attach to any native process in user-mode and modify running code, data, and even the context (e.g. registers and similar data).

That suggestion is possible, and for trivial operations (i.e. replacing some strings in a program, or causing it to take one branch instead of another) people have already done so. Doing a wholesale replacement would be tricky, but should be possible (perhaps aided with WinDBG scripts or similar).

GoodDayToDie said:
Doing a wholesale replacement would be tricky
Click to expand...
Click to collapse
Not so tricky, I've already made a prototype on desktop Win8. Just make an ARM DLL that implements a PE loader using only 2 WinAPI functions - LoadLibrary (used only to get kernel32 handle) and GetProcAddress. Inject that DLL code and data sections via debugger, fixup relocs (you can minimize their amount in your "loader DLL" by not using global variables, placing all code into one file, not using CRT at all, and so on, ARM makes it easy to create position-independent code), and call your injected code via debugger passing it the address of LoadLibrary and GetProcAddress as parameters. Your code than would do what you wish - load and execute an unsigned DLL that you specify.
With this trick you can load EXE files too, as all ARM EXEs contain relocs by default.
But this way is too inconvenient to the end-user, so should be avoided. I really think that MS left enough holes for us to "unlock" unsigned apps on retail WinRT devices.
I'm already thinking on buying an Asus tablet with 3G (instead of waiting for a better device that I wish), so after NY holidays I'll join your game

Ah, that's a much more clever approach than actually trying to load the full program using the debugger itself... if it works. LoadLibrary triggers the same signature check that CreateProcess does (or rather, the system calls that they do will perform that check; if it was user-mode we could bypass it with the debugger). Your method may work, but since the desktop doesn't have the signature check anyhow, prototyping it there doesn't actually mean it will work on RT. Try it out and let us know how it goes, and if it works, posting your source would be awesome!

GoodDayToDie said:
Ah, that's a much more clever approach than actually trying to load the full program using the debugger itself... if it works. LoadLibrary triggers the same signature check that CreateProcess does (or rather, the system calls that they do will perform that check; if it was user-mode we could bypass it with the debugger). Your method may work, but since the desktop doesn't have the signature check anyhow, prototyping it there doesn't actually mean it will work on RT. Try it out and let us know how it goes, and if it works, posting your source would be awesome!
Click to expand...
Click to collapse
He doesn't mean making a prototype and importing from kernel32.dll. He means manually mapping the PE file, then using either CreateRemoteThread or modifying the context of a thread already launched to run it once it's in the memory address of another process. It's basically DLL injection with our own implementation of LoadLibrary. It would work because LoadLibrary doesn't use any system calls except to map memory (and mapping memory doesn't have integrity checks of any sort, and it shouldn't be design -- e.g. VirtualAlloc).
A bigger problem I thought of is automating this. I took a quick peek with Wireshark at my remote debugging session and saw HTTP with what appeared to be a proprietary protocol. In order to automate this from another computer (or any mobile device for that matter), we would need to reverse engineer the protocol. Or, an alternative would be to hook into Visual Studio once the debugging session is launched (maybe just a nice VS plugin would work?).

mamaich said:
Code:
void DoThings()
{
char *Tmp=(char*)GetTickCount64;
Tmp=(char*)((~0xFFF)&(DWORD_PTR)Tmp);
while(Tmp)
{
__try
{
if(Tmp[0]=='M' && Tmp[1]=='Z')
break;
} __except(EXCEPTION_EXECUTE_HANDLER)
{
}
Tmp-=0x1000;
}
if(Tmp==0)
return;
Click to expand...
Click to collapse
I was looking through the provided sample -- wouldn't our own GetModuleHandleA implementation be a better way of doing this? I'm just thinking should the alignment be changed in kernel32.dll it may be better to have something like this:
Code:
522 if (!name)
523 {
524 ret = NtCurrentTeb()->Peb->ImageBaseAddress;
525 }
526 else if (flags & GET_MODULE_HANDLE_EX_FLAG_FROM_ADDRESS)
527 {
528 void *dummy;
529 if (!(ret = RtlPcToFileHeader( (void *)name, &dummy ))) status = STATUS_DLL_NOT_FOUND;
530 }
Source: http://source.winehq.org/source/dlls/kernel32/module.c#L504
Grabbing the Peb (NtCurrentTeb()->Peb) would involve pulling from the FS register at offset 0x30. Implementing this on ARM could be trickier, as I'm not sure of the inline assembly or availability of intrinsics (not to mention, it would be stored somewhere else than the FS register).
Now, for the PC, it appears __readfsdword is available as an intrinsic, so this *should* work on x86 installations of Windows 8.

mamaich said:
Not so tricky, I've already made a prototype on desktop Win8. Just make an ARM DLL that implements a PE loader using only 2 WinAPI functions - LoadLibrary (used only to get kernel32 handle) and GetProcAddress. Inject that DLL code and data sections via debu
Click to expand...
Click to collapse
I think this approach (of injecting own loader as far as understand) has such problem(even if implemented & automated)
Loaded exe can have own dependant dlls(any complicated-usefull proj has) that it cant load because of signing checks (and even more problems if it uses dynamic loading of own dlls and getprocaddress)
Or do i miss somth in your idea?

Will I be able to read/write to a parallel port using this method? Do the limited store apps have sufficient permissions to do that? Writing to a parallel port requires calling
Code:
hndleLPT = CreateFile("LPT1",(GENERIC_READ | GENERIC_WRITE), 0, 0, OPEN_EXISTING, 0, 0);
. Will this succeed?
Will I be able to successfully load this: http://www.highrez.co.uk/Downloads/InpOut32/default.htm ?
---------- Post added at 03:01 PM ---------- Previous post was at 02:11 PM ----------
This looks like an improved method to get the base address:
http://tedwvc.wordpress.com/2013/07/19/finding-the-kernel32-dll-module-handle-in-a-windows-store-app-using-approved-apis/

You should be able to do that using CreateFile2, which is permitted in Store apps already (no need to use the rest of the Win32 API). As for the permissions, I don't know, but it will probably work.
I mean, assuming your computer *has* an LPT port. I haven't seen one of those in a while...

how about the other way round? can a desktop app have access to the full windows 8 api (including those reserved for win store apps only)?

Windows RT 8.1 IR5 Media Builder

Windows RT 8.1 IR5 Media Builder:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​This media builder will download Windows RT 8.1 IR5, download and integrate selected Windows Updates, integrate drivers and generate custom installation media ready for use on the selected device.
Mainstream support for Windows RT 8.1 ended January 9, 2018, and extended support for Windows RT 8.1 will end on January 10, 2023.
The use of this media builder or the media it produces is entirely at your own risk.
User Guide
- Device Support
- Known Issues
- Version History
10/05/2023 - Windows_RT_8.1_IR5_Media_Builder_v2.4j.zip
- Tegra Jailbreak USB updated to v1.6.
- Office 2013 RT Home & Student Plus update lists updated to May 2023.
Download: Open-RT / Archive.org
27/04/2023 - Windows_RT_8.1_IR5_Media_Builder_v2.4i.zip
- Minor fixes.
15/04/2023 - Windows_RT_8.1_IR5_Media_Builder_v2.4h.zip
- Minor correction to Office 2013 RT removal option.
- DISM now uses the Media Builder temporary folder for scratch space where possible.
- Added check to prevent Media Builder from offering any of the drive(s) it is using from being offered as an output destination.
- Added file system check.
- Minor fixes.
19/03/2023 - Windows_RT_8.1_IR5_Media_Builder_v2.4g.zip
- Corrected an issue which caused the output for ASUS VivoTab RT to be unbootable.
- ASUS VivoTab RT driver pack updated.
- Office 2013 RT Home & Student Plus update lists updated to March 2023.
20/02/2023 - Windows_RT_8.1_IR5_Media_Builder_v2.4f.zip
- Possible workaround to the issue of hanging on the UEFI boot logo when attempting to install Windows using Windows Media Builder output on the Surface 2.
15/02/2023 - Windows_RT_8.1_IR5_Media_Builder_v2.4e.zip
- Windows Update lists updated to February 2023.
- Office 2013 RT Home & Student Plus update lists updated to February 2023.
- Nokia Lumia 2520 driver pack updated.
10/01/2023 - Windows_RT_8.1_IR5_Media_Builder_v2.4d.zip
- Windows Update lists updated to January 2023.
- Office 2013 RT Home & Student Plus update lists updated to January 2023.
- Surface RT & 2 Jailbreak USB updated to v1.5b.
- Minor fixes.
29/12/2022 - Windows_RT_8.1_IR5_Media_Builder_v2.4c.zip
- Windows Update lists updated to December 2022.
- Minor fixes.
20/11/2022 - Windows_RT_8.1_IR5_Media_Builder_v2.4b.zip
- Windows Update lists updated to November 2022.
- Office 2013 RT Home & Student Plus update lists updated to November 2022.
13/10/2022 - Windows_RT_8.1_IR5_Media_Builder_v2.4a.zip
- Windows Update lists updated to October 2022.
- Office 2013 RT Home & Student Plus update lists updated to October 2022.
- Surface RT & 2 Jailbreak USB updated to v1.5a.
17/09/2022 - Windows_RT_8.1_IR5_Media_Builder_v2.4.zip
- Added option to create a "Windows To Go" bootable USB drive. ^
- Added option to remove Office 2013 RT. ^^
- Windows Update lists updated to September 2022.
- Office 2013 RT Home & Student Plus update lists updated to September 2022.
- DISM logs are now being saved correctly.
- Minor fixes.
^ This isn't real Windows To Go but it will write a USB with a bootable installation of Windows. The option is disabled by default and has to be enabled from Media Builder Settings if required. If enabled this option will be offered either after creating an image or when writing an existing one. There are no guarantees that this is stable but it might be useful if you want to test something without touching the local installation.
I have only tested this on a Surface 2 and cannot predict how or even if it will work on other devices, in the test I have done the installation was usable when installed to a USB 2 Western Digital 250GB conventional hard drive. If a drive with inadequate performance is used then at best the installation will take an hour or two or in the worst case the installation will fail. For Windows RT 8.1 this option requires a USB drive that reports as "fixed", it will not work on a "removable" device.
^^ Based on Microsoft instructions for manual removal of Office and it might not be perfect.
Click to expand...
Click to collapse
​

Hello,
Could you explain how to use your file?
Thank you

xenis said:
Hello,
Could you explain how to use your file?
Thank you
Click to expand...
Click to collapse
Download and extract the zip file then run Build.cmd as administrator. Once Build opens select your device by typing the number corresponding to your device and pressing enter. After that no interaction will be required for a while, it will download Windows RT 8.1 IR5 and the updates for Windows directly from Microsoft, integrate them, add drivers for your device and then produce a folder ready to be copied to USB for installation on your device. Optionally an ISO can be created for archival purposes, you will be prompted for this towards the end of the run.
On an old test box I've found the process to take around 50 minutes including download time. I've attached some pictures of it running start to finish in first post.

I have an error message
«*this application cannot run on you computer*»
«*To find applications for this pc, open windows store*»
Do you know what’s happen?

xenis said:
I have an error message
«*this application cannot run on you computer*»
«*To find applications for this pc, open windows store*»
Do you know what’s happen?
Click to expand...
Click to collapse
What are you running it on? This is run on a normal x86/x64 PC, the media prepared here can then be used on your RT device. It could be made to work on an RT device but I imagine it would be incredibly slow to produce the updated installation source.
EDIT: I have updated the download, it will show an error if you are running on an unsupported architecture.

Can I grab iso my language different than en-us?

hooddy said:
Can I grab iso my language different than en-us?
Click to expand...
Click to collapse
Yes, you should just need to edit "\Download_Lists\Windows.txt" and replace the link with one of these.
ar-sa: http://vg.dl.ws.microsoft.com/dl/co..._343214DC5C52DBA99F34B9196A6ACBDD0BE53505.esd
bg-bg: http://vg.dl.ws.microsoft.com/dl/co..._307C20D50B8EC7CE3C8A8AE3E087E211A3BED662.esd
cs-cz: http://vg.dl.ws.microsoft.com/dl/co..._8D39E5906B750806CA68802DF1F79A2AF81B9FD5.esd
da-dk: http://vg.dl.ws.microsoft.com/dl/co..._62A6E28F1679CB64726655EF928936BFDF8F9FF4.esd
de-de: http://vg.dl.ws.microsoft.com/dl/co..._AD36CA5F9F8D384187EAB1583C71E7979357B63D.esd
el-gr: http://vg.dl.ws.microsoft.com/dl/co..._6813245AFCC99B8F84CC63B72FA082CCE8CE1AC4.esd
en-gb: http://vg.dl.ws.microsoft.com/dl/co..._410B5AE61DE3EA349F61BB8ACC3F3CB0681B1DCF.esd
es-es: http://vg.dl.ws.microsoft.com/dl/co..._45C90FB10612AF9C4AE7795623129AB9950FE655.esd
et-ee: http://vg.dl.ws.microsoft.com/dl/co..._516956ECB25C4B480489F820E4C780214F9551BE.esd
fi-fi: http://vg.dl.ws.microsoft.com/dl/co..._6CBAF4362316241EF87D5EF9B80CB7F1F37EDBED.esd
fr-fr: http://vg.dl.ws.microsoft.com/dl/co..._1EF69BB926B9A0742A093854DF82ABFF2E995F23.esd
he-il: http://vg.dl.ws.microsoft.com/dl/co..._11CB81D14F847684BD193BEB50BC3C4E408FF34C.esd
hr-hr: http://vg.dl.ws.microsoft.com/dl/co..._48FC1DABE3D0A1B88E0E68FD083381E99A24516E.esd
hu-hu: http://vg.dl.ws.microsoft.com/dl/co..._182ECAEBB0E738B165924C8F99B89A696F4FCADA.esd
it-it: http://vg.dl.ws.microsoft.com/dl/co..._D942BBC8808E629681CC21E1BD77A15E4396AF9C.esd
ja-jp: http://vg.dl.ws.microsoft.com/dl/co..._B788FF2B21517E2E555F8037A806A55ED967D8EB.esd
ko-kr: http://vg.dl.ws.microsoft.com/dl/co..._CB3FE5FBBEEDC1A7C15BC7906853663AFE853B98.esd
lt-lt: http://vg.dl.ws.microsoft.com/dl/co..._CE7A71D3FA5F56F58E2D6ACD9BB645725C04FB0E.esd
lv-lv: http://vg.dl.ws.microsoft.com/dl/co..._21ADAE9C229741CAE4C249125D03060410A864B6.esd
nb-no: http://vg.dl.ws.microsoft.com/dl/co..._7C750ADB12C6AAEA12D4A8D951D6E5386D984181.esd
nl-nl: http://vg.dl.ws.microsoft.com/dl/co..._7A1963FF85610217CA3B0DEF2C35B266BCABAD0D.esd
pl-pl: http://vg.dl.ws.microsoft.com/dl/co..._81EB4062960D6A3461A1564094A8EB00AE9685BF.esd
pt-br: http://vg.dl.ws.microsoft.com/dl/co..._409716869AA521EF41B7D86333B77088EDD73334.esd
pt-pt: http://vg.dl.ws.microsoft.com/dl/co..._3182A88D293A37AAF7418BF896DFDF19F5A4818D.esd
ro-ro: http://vg.dl.ws.microsoft.com/dl/co..._967EB013E8C52BA0B2A7C1F9BE3A474EE2402ECF.esd
ru-ru: http://vg.dl.ws.microsoft.com/dl/co..._FBE42B32AB8B8A8D0F84FEBEB95099EC5DA1EEF8.esd
sk-sk: http://vg.dl.ws.microsoft.com/dl/co..._A0CBCFCD2B80D22AFC1C8403ACDBA62C4E9BA635.esd
sl-si: http://vg.dl.ws.microsoft.com/dl/co..._78571325C1D8395436A6630E31EBC4FE2CFD8C91.esd
sr-latn-rs: http://vg.dl.ws.microsoft.com/dl/co..._18FED3F95C86CB7B1E3BA6A669F73B5218501125.esd
sv-se: http://vg.dl.ws.microsoft.com/dl/co..._2EE5CDE96856C69021B643825BE26C04B59E3331.esd
th-th: http://vg.dl.ws.microsoft.com/dl/co..._76873E5D21F711EEB31239479B215868AC779F78.esd
tr-tr: http://vg.dl.ws.microsoft.com/dl/co..._86C5586E947025AEC939F2D0A7B2B52E0760B744.esd
uk-ua: http://vg.dl.ws.microsoft.com/dl/co..._F4D7A99684BE4B7AA01D37E14377B1786FD24C4E.esd
zh-cn: http://vg.dl.ws.microsoft.com/dl/co..._36BE8400D2BDA3C3BEBE8A51F0859090C1C27C76.esd
zh-hk: http://vg.dl.ws.microsoft.com/dl/co..._89FE5E0F6173EE16806482C4884E32E5535193BB.esd
zh-tw: http://vg.dl.ws.microsoft.com/dl/co..._AA6F117073060E944950AD4081F178C126145C26.esd
Click to expand...
Click to collapse

jwa4 said:
Yes, you should just need to edit "\Download_Lists\Windows.txt" and replace the link with one of these.
Code:
ar-sa: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_ar-sa-IR5_CCSA_WOAFRER_AR-SA_ESD_343214DC5C52DBA99F34B9196A6ACBDD0BE53505.esd
bg-bg: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_bg-bg-IR5_CCSA_WOAFRER_BG-BG_ESD_307C20D50B8EC7CE3C8A8AE3E087E211A3BED662.esd
cs-cz: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_cs-cz-IR5_CCSA_WOAFRER_CS-CZ_ESD_8D39E5906B750806CA68802DF1F79A2AF81B9FD5.esd
da-dk: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_da-dk-IR5_CCSA_WOAFRER_DA-DK_ESD_62A6E28F1679CB64726655EF928936BFDF8F9FF4.esd
de-de: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_de-de-IR5_CCSA_WOAFRER_DE-DE_ESD_AD36CA5F9F8D384187EAB1583C71E7979357B63D.esd
el-gr: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_el-gr-IR5_CCSA_WOAFRER_EL-GR_ESD_6813245AFCC99B8F84CC63B72FA082CCE8CE1AC4.esd
en-gb: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_en-gb-IR5_CCSA_WOAFRER_EN-GB_ESD_410B5AE61DE3EA349F61BB8ACC3F3CB0681B1DCF.esd
es-es: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_es-es-IR5_CCSA_WOAFRER_ES-ES_ESD_45C90FB10612AF9C4AE7795623129AB9950FE655.esd
et-ee: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_et-ee-IR5_CCSA_WOAFRER_ET-EE_ESD_516956ECB25C4B480489F820E4C780214F9551BE.esd
fi-fi: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_fi-fi-IR5_CCSA_WOAFRER_FI-FI_ESD_6CBAF4362316241EF87D5EF9B80CB7F1F37EDBED.esd
fr-fr: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_fr-fr-IR5_CCSA_WOAFRER_FR-FR_ESD_1EF69BB926B9A0742A093854DF82ABFF2E995F23.esd
he-il: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_he-il-IR5_CCSA_WOAFRER_HE-IL_ESD_11CB81D14F847684BD193BEB50BC3C4E408FF34C.esd
hr-hr: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_hr-hr-IR5_CCSA_WOAFRER_HR-HR_ESD_48FC1DABE3D0A1B88E0E68FD083381E99A24516E.esd
hu-hu: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_hu-hu-IR5_CCSA_WOAFRER_HU-HU_ESD_182ECAEBB0E738B165924C8F99B89A696F4FCADA.esd
it-it: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_it-it-IR5_CCSA_WOAFRER_IT-IT_ESD_D942BBC8808E629681CC21E1BD77A15E4396AF9C.esd
ja-jp: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_ja-jp-IR5_CCSA_WOAFRER_JA-JP_ESD_B788FF2B21517E2E555F8037A806A55ED967D8EB.esd
ko-kr: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_ko-kr-IR5_CCSA_WOAFRER_KO-KR_ESD_CB3FE5FBBEEDC1A7C15BC7906853663AFE853B98.esd
lt-lt: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_lt-lt-IR5_CCSA_WOAFRER_LT-LT_ESD_CE7A71D3FA5F56F58E2D6ACD9BB645725C04FB0E.esd
lv-lv: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_lv-lv-IR5_CCSA_WOAFRER_LV-LV_ESD_21ADAE9C229741CAE4C249125D03060410A864B6.esd
nb-no: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_nb-no-IR5_CCSA_WOAFRER_NB-NO_ESD_7C750ADB12C6AAEA12D4A8D951D6E5386D984181.esd
nl-nl: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_nl-nl-IR5_CCSA_WOAFRER_NL-NL_ESD_7A1963FF85610217CA3B0DEF2C35B266BCABAD0D.esd
pl-pl: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_pl-pl-IR5_CCSA_WOAFRER_PL-PL_ESD_81EB4062960D6A3461A1564094A8EB00AE9685BF.esd
pt-br: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_pt-br-IR5_CCSA_WOAFRER_PT-BR_ESD_409716869AA521EF41B7D86333B77088EDD73334.esd
pt-pt: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_pt-pt-IR5_CCSA_WOAFRER_PT-PT_ESD_3182A88D293A37AAF7418BF896DFDF19F5A4818D.esd
ro-ro: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_ro-ro-IR5_CCSA_WOAFRER_RO-RO_ESD_967EB013E8C52BA0B2A7C1F9BE3A474EE2402ECF.esd
ru-ru: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_ru-ru-IR5_CCSA_WOAFRER_RU-RU_ESD_FBE42B32AB8B8A8D0F84FEBEB95099EC5DA1EEF8.esd
sk-sk: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_sk-sk-IR5_CCSA_WOAFRER_SK-SK_ESD_A0CBCFCD2B80D22AFC1C8403ACDBA62C4E9BA635.esd
sl-si: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_sl-si-IR5_CCSA_WOAFRER_SL-SI_ESD_78571325C1D8395436A6630E31EBC4FE2CFD8C91.esd
sr-latn-rs: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_sr-latn-rs-IR5_CCSA_WOAFRER_SR-LATN-RS_ESD_18FED3F95C86CB7B1E3BA6A669F73B5218501125.esd
sv-se: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_sv-se-IR5_CCSA_WOAFRER_SV-SE_ESD_2EE5CDE96856C69021B643825BE26C04B59E3331.esd
th-th: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_th-th-IR5_CCSA_WOAFRER_TH-TH_ESD_76873E5D21F711EEB31239479B215868AC779F78.esd
tr-tr: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_tr-tr-IR5_CCSA_WOAFRER_TR-TR_ESD_86C5586E947025AEC939F2D0A7B2B52E0760B744.esd
uk-ua: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_uk-ua-IR5_CCSA_WOAFRER_UK-UA_ESD_F4D7A99684BE4B7AA01D37E14377B1786FD24C4E.esd
zh-cn: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_zh-cn-IR5_CCSA_WOAFRER_ZH-CN_ESD_36BE8400D2BDA3C3BEBE8A51F0859090C1C27C76.esd
zh-hk: http://vg.dl.ws.microsoft.com/dl/content/c/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_zh-hk-IR5_CCSA_WOAFRER_ZH-HK_ESD_89FE5E0F6173EE16806482C4884E32E5535193BB.esd
zh-tw: http://vg.dl.ws.microsoft.com/dl/content/d/updt/2015/01/9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_zh-tw-IR5_CCSA_WOAFRER_ZH-TW_ESD_AA6F117073060E944950AD4081F178C126145C26.esd
Click to expand...
Click to collapse
Oh thats cool. Btw why did you hide Lumia drivers? I have Lenovo one to add into.

hooddy said:
Oh thats cool. Btw why did you hide Lumia drivers? I have Lenovo one to add into.
Click to expand...
Click to collapse
It's not hidden as such (I haven't added the drivers) but I'm not sure how to safely approach Lumia 2520 yet, I will look into it at the weekend. Once certain updates are applied to Lumia 2520 they can't ever be jailbroken again whereas on Surface we can just format them or remove the jailbreak blocking updates.
I'm also not sure what the jailbreak situation is on other RT devices so I need to try and found out if any of them are in the same boat as the Lumia 2520 before adding driver packs for them all. I suspect its going to end up having two update lists, the full one used in the existing release and a jailbreak friendly one.
I will also try to add language selection to avoid having the manually change it.

jwa4 said:
It's not hidden as such (I haven't added the drivers) but I'm not sure how to safely approach Lumia 2520 yet, I will look into it at the weekend. Once certain updates are applied to Lumia 2520 they can't ever be jailbroken again whereas on Surface we can just format them or remove the jailbreak blocking updates.
I'm also not sure what the jailbreak situation is on other RT devices so I need to try and found out if any of them are in the same boat as the Lumia 2520 before adding driver packs for them all. I suspect its going to end up having two update lists, the full one used in the existing release and a jailbreak friendly one.
I will also try to add language selection to avoid having the manually change it.
Click to expand...
Click to collapse
Lenovo is easily jailbreaked like Surface.
It is good to have multilang.

hooddy said:
Lenovo is easily jailbreaked like Surface.
Click to expand...
Click to collapse
Yea, I had a quick look and as I understand it all the Tegra devices can't be permanently blocked from being Jailbroken. It's just all the Qualcomm devices like the 2520 that are out of luck, these devices might get an alternative safe update list.
hooddy said:
It is good to have multilang.
Click to expand...
Click to collapse
I've got to do a quick test wim build tonight but the language selection is done, picture attached.

hooddy said:
It is good to have multilang.
Click to expand...
Click to collapse
I've updated the link, v1.3 will hopefully let you pick a language without editing anything. I have only tested this with Chinese, Dutch, English & French IR5 sources.
The optional Appx pack remains unchanged.

jwa4 said:
I've updated the link, v1.3 will hopefully let you pick a language without editing anything. I have only tested this with Chinese, Dutch, English & French IR5 sources.
The optional Appx pack remains unchanged.
Click to expand...
Click to collapse
I will check it. Btw I do not get what to do with appx pack... Unpack it into appx folder?

It is seems working. Add lenovo drivers please. I can share it if any.

hooddy said:
I will check it. Btw I do not get what to do with appx pack... Unpack it into appx folder?
Click to expand...
Click to collapse
Yep, extract to Appx folder so it looks like the attached image and once the pack is present Build.cmd will ask if you want to update the Appx or not.
hooddy said:
It is seems working. Add lenovo drivers please. I can share it if any.
Click to expand...
Click to collapse
I will try to take a look tonight. Do you have an RT 8.1 recovery image for the device? I wonder how close they are to the Surface RT ones.

hooddy said:
It is seems working. Add lenovo drivers please. I can share it if any.
Click to expand...
Click to collapse
This one contains the Lenovo drivers, just a test for now because I don't have a Yoga 11 to test it on. Assuming this works please check device manager,check all drivers are present and let me know the result.
Download: EDIT: Main link updated to v1.4
Thanks to lgibson02 for the drivers and testing!

28/11/2020 - Windows_RT_8.1_IR5_Update_Kit_v1.5.zip
- Added UNTESTED support for ASUS VivoTab RT, Dell XPS 10, Nokia Lumia 2520 & Samsung Ativ Tab.
- Added Update List selection, choice of update lists - All Updates for Windows (Including "Jailbreak Killers"), Longhorn Jailbreak Safe & Myriachan Jailbreak Safe.

17/12/2020 - Windows_RT_8.1_IR5_Update_Kit_v1.6.zip
17/12/2020 - Windows_RT_8.1_IR5_Update_Kit_v1.6_Appx.zip
- Added three additional update modes (None, Service Stack Only & Service Stack and Update 3 Only).
- Added warning for languages that do not currently support App updates.
- Added warning if an unmodified IR5 image is going to be created.
- Removed Start Menu Update Discoverability notification if Update 3 is installed and Start Menu is enabled by default.
During testing I found that trying to update provisioned apps in Windows RT 8.1 IR5 for Saudi Arabia, Bulgaria, Germany, Croatia, Hungary, Russia and Slovakia results in the following error:
App packages (.appx) cannot be serviced on an offline image after a user has logged into the image.
Click to expand...
Click to collapse
I will try to find what causes this but for the moment these will be excluded from attempting app updates.
At this time I don't think there is going to be a solution for adding updates for Office 2013 RT offline.

hi I have installed all the windows update, everything perfect
I would like to know how to install the jailbreak and if you have to compile from the surface directly or from another pc.
thanks

ivanothai said:
hi I have installed all the windows update, everything perfect
I would like to know how to install the jailbreak and if you have to compile from the surface directly or from another pc.
thanks
Click to expand...
Click to collapse
Another thread might be best suited for jailbreak discussion but there are a few options. There are methods from Myriachan, Never_Released / black_bob and imbushuo.

Does myriachan jailbreak automatically with this program? What does it consist of? Should it be done? Can I put a newer browser? Thank you

[DEV][ROM][UNOFFICIAL] LineageOS 18.1 (Android 11) for Raspberry Pi 4 B

Here’s my build of LineageOS 18.1 for Raspberry Pi 4 Model B, Pi 400, and Compute Module 4. It is unofficial and unsupported by the LineageOS team. It’s for advanced users only. Pi 4 model with at least 2GB of RAM is required to run this build.
Important! This image includes parts that are licensed under non-commercial license (Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International). You may use this build freely in personal/educational/etc use. Commercial use is not allowed with this build! You can contact me by email to discuss creating customized Android builds for commercial purposes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 18.1 (Android 11)
for Raspberry Pi 4
konstakang.com
There is also Android TV version available.
LineageOS 18.1 Android TV (Android 11)
for Raspberry Pi 4
konstakang.com
Working:
Audio (HDMI, 3.5mm jack, USB microphones, bluetooth speakers/headphones, etc)
Audio DAC (using GPIO DACs e.g. Hifiberry DAC+)
Bluetooth (and bluetooth tethering)
Camera (using official Pi camera modules & UVC USB webcams)
GPIO
GPS (using external USB modules e.g. U-Blox 7)
Ethernet
Hardware accelerated graphics (V3D, OpenGL & Vulkan)
HDMI display (and HDMI-CEC)
I2C
IR remotes (using external GPIO IR modules e.g. TSOP4838)
RTC (using external GPIO I2C modules e.g. DS3231)
Sensors (using external GPIO I2C modules e.g. MPU6050, LSM6DS3, LSM303DLHC, BME280/BMP280, and APDS9930 accelerometer, gyroscope, magnetometer, temperature, pressure, humidity, ambient light, and proximity)
Serial console (using external GPIO serial console adapters e.g. PL2303)
SPI
Touchscreen/multi-touch (USB touchscreens, Waveshare SPI touchscreens)
USB (mouse, keyboard, storage, etc)
USB-C (ADB, MTP, PTP, USB tethering)
Wifi (and wifi tethering)
Not working:
Hardware video decoding & encoding (software decoding & encoding works)
Issues:
Stock camera app is not working - many third party camera apps seem to work
SELinux is in permissive mode
and more…
Sources:
kernel
Thanks:
Peter Yoon and android-rpi project
Roman Stratiienko and GloDroid project
AOSP reference board developers (dragonboard, hikey, yukawa)
E. Anholt for V3D graphics driver
Maxime Ripard for Pi 4 KMS driver
Android-x86 project
LineageOS team and everyone who has contributed to LineageOS 18.1

How to install:
Follow the official Raspberry Pi instructions for writing the image to the SD card.
If you’re running a recent build (20220121 or newer) you can also update to newer builds using TWRP flashable OTA packages. OTA updates pushed through the built-in Updater app are stored at /data/lineageos_updates/.
Download lineage-18.1-xxxxxxxx-UNOFFICIAL-KonstaKANG-rpi4-ota.zip and save it to your device’s internal storage or use an external USB drive
Boot to TWRP recovery (see FAQ)
Install lineage-18.1-xxxxxxxx-UNOFFICIAL-KonstaKANG-rpi4-ota.zip from your selected storage
(Flash Magisk/other add-ons you had previously installed)
Boot out of recovery (see FAQ)
Changes that are backed up and restored flashing OTAs:
Device specific settings changed using Settings -> System -> Raspberry Pi settings
Manual changes to /boot/resolution.txt and /boot/rc_keymap.txt
USB boot configuration in /boot/config.txt
GApps
Changes that are not backed up and restored flashing OTAs:
Manual changes to /boot/config.txt (and any other manual changes to /boot partition)
Magisk
FAQ:
FAQ is getting quite long and difficult to maintain in several different places. You can find the always up-to-date FAQs here:
https://konstakang.com/devices/rpi4/LineageOS18/
https://konstakang.com/devices/rpi4/LineageOS18-ATV/

Merged commits not mentioned in the changelog.
12.5. changelog:
also available as OTA package
add support for Compute Module 4
fix DAC audio device selection on CM4 & Pi 400 that don’t have 3.5mm audio jack
fix USB storage (Pi 400 as well?)
add support for the RTC on the I/O board
use OTG mode for USB to support ADB, MTP, PTP, USB tethering on the micro-USB port on the I/O board
update boot firmware for newer Pi 4 hardware revisions
various drm_hwcomposer updates e.g. support for headless mode (thanks to Roman Stratiienko)
automatically set density based on display resolution
add support for APDS9930 ambient light/proximity sensor
update to TWRP 3.6.1_11-1-KonstaKANG
update to Mesa 21.3.8
update to Linux 5.4.191 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 May 2022 (merged)
21.1. 2022 changelog:
fix reboots related to Hotspot 2.0 networks/ANQP requests (see issue #6)
Vulkan 1.1 (thanks to people at Igalia for Vulkan 1.1 conformance and Roman Stratiienko for latest Mesa fixes)
add new options to Raspberry Pi settings (force rotation & CPU governor)
prepare for OTAs
update to TWRP 3.6.0_11-1-KonstaKANG
update to Mesa 21.3.4
update to Linux 5.4.173 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 January 2022 (merged)
23.11. changelog:
add support for BME280/BMP280 temperature/pressure/humidity sensors
add option to select HDMI-CEC device
add option to show virtual volume down, volume up, and power keys on navigation bar
add option for old TCP-based ADB over network
show IP address and port for ADB/SSH/VNC options
fix resizing data partition that broke with previous build
update to TWRP 3.6.0_11-0-KonstaKANG
update to Mesa 21.3.0
update to Linux 5.4.161 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 November 2021 (merged)
26.10. changelog:
switch to 64-bit kernel & userspace
switch to minigbm gbm_mesa and [email protected] API (thanks to Roman Stratiienko)
update to Mesa 21.2.4
update to Linux 5.4.155 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
11.10. changelog:
add support for Vulkan
rework bluetooth (thanks to android-rpi)
update to Mesa 21.1.8
update to Linux 5.4.152 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 1 October 2021 (merged)
20.7. changelog:
switch to using HDMI-CEC HAL
update to Mesa 21.1.5
update to Linux 5.4.132 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 July 2021 (merged)
11.4. changelog:
add initial support for HDMI-CEC
add built-in VNC server
update to Mesa 21.0.2
update to Linux 5.4.111 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 April 2021 (merged)
14.2. changelog:
add support for LSM303DLHC accelerometer & magnetometer sensor
add separate TWRP flashable su add-on (see FAQ)
allow switching display off with power button
add support for USB-C (ADB, MTP, PTP, USB-tethering)
enable bluetooth tethering
add settings option for mouse back button feature
update to TWRP 3.5.0_9-0-KonstaKANG
update to Mesa 20.3.4
update to Linux 5.4.98 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 February 2021 (merged)
4.1. changelog:
initial LineageOS 18.1 build
add support for sensors (LSM6DS3 & MPU6050 accelerometer & gyroscope on I2C)
add support for more serial USB GPS devices
drop support for SwiftShader software renderer which also means dropping support for the official 7” touchscreen for now
update to Mesa 20.3.2
add option to switch between gbm and minigbm gralloc
update to TWRP 3.4.0-2
update to Linux 5.4.86 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 December 2020 (merged)
Previous builds:
AndroidFileHost

Will you share an atv variation 18.1?
Thanks for your hard work.

onukomer said:
Will you share an atv variation 18.1?
Thanks for your hard work.
Click to expand...
Click to collapse
What does Android TV 11 offer that is not already available in the latest Android TV builds for the Pi 4 (https://konstakang.com/devices/rpi4/LineageOS17.1-ATV/)? Yeah, I know - big version number, much WOW! But besides that, what's the point?
From user perspective I highly doubt you're going have the slightest clue whether you're running Android TV based on Android 8, 9, 10, or 11 unless you go specifically into the about device settings. Android TV builds are also pretty much useless without installing Google Apps. There's currently hardly any working Android 11 gapps packages available and there's certainly no Android TV gapps for Android 11.
From technical perspective I'm currently not aware of any reason why Android TV 11 builds wouldn't work just as much as before but there's just not going to be much reason for it in a long long time.

KonstaT said:
Here’s my build of LineageOS 18.1 for Raspberry Pi 4 Model B, Pi 400, and Compute Module 4. It is unofficial and unsupported by the LineageOS team. It’s for advanced users only. Pi 4 model with at least 2GB of RAM is required to run this build.
Important! This image includes parts that are licensed under non-commercial license (Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International). You may use this build freely in personal/educational/etc use. Commercial use is not allowed with this build!
https://konstakang.com/devices/rpi4/LineageOS18/
lineage-18.1-20210104-UNOFFICIAL-KonstaKANG-rpi4.zip
https://www.androidfilehost.com/?fid=17248734326145708986
md5:4775eb4b2a89859ebf4d16dbf306cea2
Working:
Audio (HDMI, 3.5mm jack, USB microphones, bluetooth speakers/headsets, etc)
Audio DAC (using GPIO DACs e.g. Hifiberry DAC+)
Bluetooth
Camera (using official Pi camera modules & UVC USB webcams)
GPIO
GPS (using external USB modules e.g. U-Blox 7)
Ethernet
Hardware accelerated graphics (V3D)
HDMI display
I2C
IR remotes (using external GPIO IR modules e.g. TSOP4838)
RTC (using external GPIO I2C modules e.g. DS3231)
Sensors (using external GPIO I2C modules e.g. LSM6DS3 & MPU6050 accelerometer & gyroscope)
Serial console (using external GPIO serial console adapters e.g. PL2303)
SPI
Touchscreen/multi-touch (USB touchscreens, Waveshare SPI touchscreens)
USB (mouse, keyboard, storage, etc)
Wifi
Wifi tethering
Not working:
Hardware video decoding & encoding (software decoding & encoding works)
Issues:
Stock camera app is not working - many third party camera apps seem to work
SELinux is in permissive mode
and more…
Sources:
kernel
Thanks:
Peter Yoon and everyone who has contributed to android-rpi
Roman Stratiienko and GloDroid project for graphics fixes
brobwind for bluetooth fixes
Eric Anholt for V3D graphics driver
Maxime Ripard for Pi 4 KMS driver
Android-x86 project
LineageOS team & everyone who has contributed to LineageOS 18.1
Click to expand...
Click to collapse
BITGAPPS ARM Android 11
BiTGApps-arm-11.0.0-R19_signed.zip
drive.google.com
Its portability is incredible, everything works fine, but the only problem I'm having is that version 17 and 18 doesn't work with the mouse in the GeForceNow application, the right button just doesn't work. I tested the OMNI Android 11 version and it works perfectly, however it is full of bugs and poorly optimized. Can you fix this for us? Having a Raspberry PI 4 that works GeForce Now is incredibly awesome!
Another suggestion is how to disable the physical keyboard shortcut keys like F1-F5, because when we try to play on GeForce Now they simply close the application, at least give a function to remap the buttons.

dhtm15 said:
Its portability is incredible, everything works fine, but the only problem I'm having is that version 17 and 18 doesn't work with the mouse in the GeForceNow application, the right button just doesn't work. I tested the OMNI Android 11 version and it works perfectly, however it is full of bugs and poorly optimized. Can you fix this for us? Having a Raspberry PI 4 that works GeForce Now is incredibly awesome!
Another suggestion is how to disable the physical keyboard shortcut keys like F1-F5, because when we try to play on GeForce Now they simply close the application, at least give a function to remap the buttons.
Click to expand...
Click to collapse
If it helps md5sum for BiTGApps-arm-11.0.0-R19_signed.zip I've used to test is 299182a2d72b977a04360439ed06db8a. It's of course entirely your decision if you trust a download source you can find. You can find more mirrors e.g. in the BiTGApps XDA thread (https://forum.xda-developers.com/t/custom-gapps-bitgapps-for-android.4012165/).
My recent builds map right mouse button to back key. Are you saying that there's Android apps that actually make a difference between left/right mouse clicks? I could add a setting option for that feature in future releases (that's actually already been on my endless list of TODOs).
You can revert to the default keyboard mappings by removing /vendor/usr/keylayout/Generic.kl (or edit that file to change the keymappings to whatever you want).

KonstaT said:
If it helps md5sum for BiTGApps-arm-11.0.0-R19_signed.zip I've used to test is 299182a2d72b977a04360439ed06db8a. It's of course entirely your decision if you trust a download source you can find. You can find more mirrors e.g. in the BiTGApps XDA thread (https://forum.xda-developers.com/t/custom-gapps-bitgapps-for-android.4012165/).
My recent builds map right mouse button to back key. Are you saying that there's Android apps that actually make a difference between left/right mouse clicks? I could add a setting option for that feature in future releases (that's actually already been on my endless list of TODOs).
You can revert to the default keyboard mappings by removing /vendor/usr/keylayout/Generic.kl (or edit that file to change the keymappings to whatever you want).
Click to expand...
Click to collapse
I think I saw something related to this, that the function of the right mouse button when programmed to return can affect applications that use the right button, this is the case with GeForce Now, which does not recognize the right mouse button in any way, all other buttons are functional. I also tried to see how to remap the keyboard buttons and tried to change these files by adding another one, but it didn't solve the problem, I opened it to edit and I didn't find the F1 function until F5, can you show me where exactly i can edit to remove this?
I found this GApps on the 4PDA forum, I think it's safe because it was a topic dedicated to that.
edit: Correction, I had entered the / root / system / usr / keylayout folder so I hadn't seen the changes.

dhtm15 said:
I think I saw something related to this, that the function of the right mouse button when programmed to return can affect applications that use the right button, this is the case with GeForce Now, which does not recognize the right mouse button in any way, all other buttons are functional. I also tried to see how to remap the keyboard buttons and tried to change these files by adding another one, but it didn't solve the problem, I opened it to edit and I didn't find the F1 function until F5, can you show me where exactly i can edit to remove this?
I found this GApps on the 4PDA forum, I think it's safe because it was a topic dedicated to that.
edit: Correction, I had entered the / root / system / usr / keylayout folder so I hadn't seen the changes.
Click to expand...
Click to collapse
Yeah, I checked the md5sum and it's the same what I have for the file I downloaded about a month ago.
I uploaded a TWRP flashable patch that will restore the default mouse button behavior and adds an option to Settings -> System -> Advanced settings to enable back key on right mouse click.
Edit. removed, not needed with latest builds anymore.
Deleting custom Generic.kl from vendor partition will use the default unmodified one from system partition. These are the changes that have been made https://github.com/lineage-rpi/andr...001-rpi3-modify-generic-keyboard-layout.patch

Hello, I try to use this great rom (and others) since 3 days with my PI4 , and "Location" (with waze and maps) never works instead of version 17.
Someone knows why ?
Thank you

Enable root access, was a switch under developer options in 17.1 nowhere to be found in 18.1. Tried flashing a SU from TWRP, nothing shows up. Am I missing something here?

myspac said:
Hello, I try to use this great rom (and others) since 3 days with my PI4 , and "Location" (with waze and maps) never works instead of version 17.
Someone knows why ?
Thank you
Click to expand...
Click to collapse
You would need to be a bit more specific. Are you using actual GPS hardware or do mean e.g. Google network location (which depends on gapps being installed)?
williamparker said:
Enable root access, was a switch under developer options in 17.1 nowhere to be found in 18.1. Tried flashing a SU from TWRP, nothing shows up. Am I missing something here?
Click to expand...
Click to collapse
Please read the FAQ on how to have root access. It's still under consideration if I'm going to bring back built-in su because there's no specific need for it anymore.

Thank you for your answers !
KonstaT said:
You would need to be a bit more specific. Are you using actual GPS hardware or do mean e.g. Google network location (which depends on gapps being installed)?
Click to expand...
Click to collapse
Oh.. yes, I mean Google network location; so , the problem is on gapps: Ok, thank you. I use : open_gapps-arm-11.0-nano-20210104-UNOFFICIAL_TEST.zip, it was ok with open_gapps-arm-10.0-pico-20201223.zip and your "17 version". I m trying other rom (OMNI) with other gapps and I had the same specific problem: that's why I think it was a "18 rom" 's problem...
KonstaT said:
Please read the FAQ on how to have root access. It's still under consideration if I'm going to bring back built-in su because there's no specific need for it anymore.
Click to expand...
Click to collapse
I have and need root access, but it was ok with the FAQ.

Hello,
In Linphone, Bria, ... I can't use my USB microphone (no recorded sound), but it works well in a voice recorder application.
It is also not possible to choose a ringtone.
Do you have an idea about the microphone problem?
Thank you for your work

KonstaT said:
You would need to be a bit more specific. Are you using actual GPS hardware or do mean e.g. Google network location (which depends on gapps being installed)?
Please read the FAQ on how to have root access. It's still under consideration if I'm going to bring back built-in su because there's no specific need for it anymore.
Click to expand...
Click to collapse
Ok, this is my last tests, all without gapps:
- I take your last rom
- connect an hardware gps by bluetooth
- install by adb the app "GPS Bluetooth" to mock the location
- install waze (by adb)
- install maps (by adb)
After:
- MAPs works
- WAZE: my location is ok but the map is not displayed: I didn't know why (if works with your rom 17).
I took an old waze version: and after re set all permission in the app setting AND by Privacy menu (not same permission when I cick on All permission of waze!!!! ???) => it was Ok too, location and map.
I re take last Waze version, but I never success to display map.
In data/wifi usage of the waze app: 0 ko !!!!
I don't understand why some applications (Android Auto too) can't access to network and why permissions are not the same by app's info and by Privacy setting menu. (It was ok with version 17 of your rom).

KonstaT said:
Here’s my build of LineageOS 18.1 for Raspberry Pi 4 Model B, ageOS team & everyone who has contributed to LineageOS 18.1
Click to expand...
Click to collapse
awesome work! i was reading your work and i have a question if you or anyone can chirp in too for ideas.
whats the benefit besides privacy using your build of lineage over raspberrys os?
if it were used offline as storage, but wake on lan when needing access using nextcloud or people recommend nextcloud alternative? also emails nextcloud isnt e2ee, but Tutanota is but i dont think its capable running on nextcloud.
some personal some work so transfering to devices its main purpose is security. maybe running a work chat system e2ee which will also be safer than online apps out there.
TLR: dont want to pay for storage cloud, messaging services online for work when we can do it ourselves and overall safer from uninvited guests

Thanks for this ROM! I understand a lot of stuff here is still experimental, but I look forward to trying this out. I will be getting a 5-inch touch screen next week sometime so I also plan to test performance with it (it's only 800x480, so not driving millions of pixels with the Pi either.) If I had to estimate, the Pi 4 is about as fast as a Galaxy S5 or S6 was, slightly slower than a snapdragon 820. So it's not midrange or high-end, but I think it is more in the upper parts of the low range in terms of raw performance. You can safely boost the clock to 2.2 gHZ, which works well provided you have the thermal cooling to do it without a throttle. I also use a Pi 400. The Pi 400 runs a lot cooler even at the default 1.8, and I have safely pushed it to 2.2. It makes it slightly faster but not a major boost in Android by any means.
If others have had experience getting the USB Type C working on this rom, let me know. I understand it's commented in config.txt, so I plan to uncomment it there and look in /vendor/etc/init/hw/init.rpi4.rc to change it also with my Ubuntu machine. I'm fully blind, so using ADB on this to get talkback working is essential. So far I have used the network boot to do this, installed both an APK for Google TTS and Talkback, got it working just fine after adding values to securesettings. Great news. At least for now, new users wanting ADB access should connect their Pi through ethernet and then connect to ADB over the network, I think this is easiest. I have a USB type C hub here which is powered so I'm able to hook the Pi directly to my computer and do it that way a bit easier than fiddling around in the router for this stuff, and maybe more secure as it is only over USB. But the network way is probably easier for more folks to get going as well. Ups and downs, just as everything to life, right?
I also am wondering if we can get USB ADB over TWRP. This would be a huge win but I will test this and report back on this thread. Again, my only choice is to use openrecovery scripts, not really to find a sighted pair of eyes and ask them to help out reading the TWRP screens. I actually don't have that help available at the moment as my partner and I are both blind. So everything I get to do I have to do in a commandline or speaking way. But I think even despite those odds, this is doable and the disabled need to push ahead in this space anyway if they too want to be tinkerers as it is.
Thanks for working on this and making Lineage accessible to many. It's been yours and other Pi community hardware enthusiasts' effort which got this up and running. I was actually able to get one of the Pi3 builds you posted running with Talkback but at the time I just didn't find the Pi 3 that good for running Android. Certainly not with 1 gig of ram, something the Pi 4 gives us a lot of choice with at least.

Micka41 said:
Hello,
In Linphone, Bria, ... I can't use my USB microphone (no recorded sound), but it works well in a voice recorder application.
It is also not possible to choose a ringtone.
Do you have an idea about the microphone problem?
Thank you for your work
Click to expand...
Click to collapse
It's still very early days for Android 11. Many apps have not yet been updated to support new features it brings. There still could be issues with integration in upstream LineageOS as well (builds are not yet rolling out for officially supported devices so I'm not sure it can be considered feature ready). Gapps are really not ready for Android 11 yet.
There are options that are more feature ready and more thoroughly tested if you're not only after the Android version number.
myspac said:
Ok, this is my last tests, all without gapps:
- I take your last rom
- connect an hardware gps by bluetooth
- install by adb the app "GPS Bluetooth" to mock the location
- install waze (by adb)
- install maps (by adb)
After:
- MAPs works
- WAZE: my location is ok but the map is not displayed: I didn't know why (if works with your rom 17).
I took an old waze version: and after re set all permission in the app setting AND by Privacy menu (not same permission when I cick on All permission of waze!!!! ???) => it was Ok too, location and map.
I re take last Waze version, but I never success to display map.
In data/wifi usage of the waze app: 0 ko !!!!
I don't understand why some applications (Android Auto too) can't access to network and why permissions are not the same by app's info and by Privacy setting menu. (It was ok with version 17 of your rom).
Click to expand...
Click to collapse
It's still very early days for Android 11. Many apps have not yet been updated to support new features it brings. There still could be issues with integration in upstream LineageOS as well (builds are not yet rolling out for officially supported devices so I'm not sure it can be considered feature ready). Gapps are really not ready for Android 11 yet.
There are options that are more feature ready and more thoroughly tested if you're not only after the Android version number.
entwicklun said:
awesome work! i was reading your work and i have a question if you or anyone can chirp in too for ideas.
whats the benefit besides privacy using your build of lineage over raspberrys os?
Click to expand...
Click to collapse
I guess the main benefit is that it's a completely different operating system. It's Android - it runs Android applications.
htc_Tomi said:
Thanks for this ROM! I understand a lot of stuff here is still experimental, but I look forward to trying this out. I will be getting a 5-inch touch screen next week sometime so I also plan to test performance with it (it's only 800x480, so not driving millions of pixels with the Pi either.) If I had to estimate, the Pi 4 is about as fast as a Galaxy S5 or S6 was, slightly slower than a snapdragon 820. So it's not midrange or high-end, but I think it is more in the upper parts of the low range in terms of raw performance. You can safely boost the clock to 2.2 gHZ, which works well provided you have the thermal cooling to do it without a throttle. I also use a Pi 400. The Pi 400 runs a lot cooler even at the default 1.8, and I have safely pushed it to 2.2. It makes it slightly faster but not a major boost in Android by any means.
If others have had experience getting the USB Type C working on this rom, let me know. I understand it's commented in config.txt, so I plan to uncomment it there and look in /vendor/etc/init/hw/init.rpi4.rc to change it also with my Ubuntu machine. I'm fully blind, so using ADB on this to get talkback working is essential. So far I have used the network boot to do this, installed both an APK for Google TTS and Talkback, got it working just fine after adding values to securesettings. Great news. At least for now, new users wanting ADB access should connect their Pi through ethernet and then connect to ADB over the network, I think this is easiest. I have a USB type C hub here which is powered so I'm able to hook the Pi directly to my computer and do it that way a bit easier than fiddling around in the router for this stuff, and maybe more secure as it is only over USB. But the network way is probably easier for more folks to get going as well. Ups and downs, just as everything to life, right?
I also am wondering if we can get USB ADB over TWRP. This would be a huge win but I will test this and report back on this thread. Again, my only choice is to use openrecovery scripts, not really to find a sighted pair of eyes and ask them to help out reading the TWRP screens. I actually don't have that help available at the moment as my partner and I are both blind. So everything I get to do I have to do in a commandline or speaking way. But I think even despite those odds, this is doable and the disabled need to push ahead in this space anyway if they too want to be tinkerers as it is.
Thanks for working on this and making Lineage accessible to many. It's been yours and other Pi community hardware enthusiasts' effort which got this up and running. I was actually able to get one of the Pi3 builds you posted running with Talkback but at the time I just didn't find the Pi 3 that good for running Android. Certainly not with 1 gig of ram, something the Pi 4 gives us a lot of choice with at least.
Click to expand...
Click to collapse
If you/anyone wants to test ADB over USB-C there's two lines you need to uncomment for testing (both LineageOS 17 & 18 should be OK for this).
One line /boot/config.txt under 'USB-C' section:
dtoverlay=dwc2,dr_mode=peripheral
Another one in /vendor/etc/init/hw/init.rpi4.rc:
import /vendor/etc/init/hw/init.rpi4.usb.rc
I don't have any hardware that would provide enough power for the Pi to test this myself. If anyone has recommendations on powered USB-C hubs that are known to work on the Pi 4 for this purpose I'd appreciate that.
My TWRP builds don't support ADB. This is because TWRP has no network support (wifi/ethernet) and I can't test the USB-C for the above reason.

KonstaT said:
If you/anyone wants to test ADB over USB-C there's two lines you need to uncomment for testing (both LineageOS 17 & 18 should be OK for this).
One line /boot/config.txt under 'USB-C' section:
dtoverlay=dwc2,dr_mode=peripheral
Another one in /vendor/etc/init/hw/init.rpi4.rc:
import /vendor/etc/init/hw/init.rpi4.usb.rc
I don't have any hardware that would provide enough power for the Pi to test this myself. If anyone has recommendations on powered USB-C hubs that are known to work on the Pi 4 for this purpose I'd appreciate that.
My TWRP builds don't support ADB. This is because TWRP has no network support (wifi/ethernet) and I can't test the USB-C for the above reason.
Click to expand...
Click to collapse
I can definitely say that uncommenting those lines did get me ADB over the USB type C port. So it does work in this mode successfully. I could then do adb root and at least have some access similar to TWRP minus the flashing and back-ups.
I think the problem with some powered hubs could be the power delivery. I'm not sure if you have a type-C port already on your machine, but it may provide the full 10 GBPS/3A requirement if it's a direct type C port. The 3.0/3.1 gen1 hubs only provide 1.5A of power and 5 GBps, so while the Pi could run on it, you couldn't power any attached devices and would get the reduced lightningbolt symbol performance as well. The powered hubs have dedicated charging ports, but these wire directly to the hub and not the machine, so while providing more power at a cost.
I also tried installing Gapps (BitGapps) for Android 11 but it failed once I signed in with a Google account. Oh well. 32-bit Gapps are also harder to come by anyway. For now I can always sideload apk files which don't rely on the play stuff and use Chrome for browsing. That's a good start.
The reason I need Android 11 is mostly for accessibility. Unlike for sighted folks where lower Android versions don't make an impact on how and what you can use, for the blind, each Android version introduces changes to the accessibility API. This is important as these changes can allow for things like brand new touch gestures (completely different gestures/ swipes and touches in Android 11 with Talkback ) to actual improvements on what the screen reader "sees" in the UI. So no, I'm not doing this to just have the version number myself, but to benefit from the latest changes to Android's accessibility API. I hope this makes sense.

htc_Tomi said:
I can definitely say that uncommenting those lines did get me ADB over the USB type C port. So it does work in this mode successfully. I could then do adb root and at least have some access similar to TWRP minus the flashing and back-ups.
I think the problem with some powered hubs could be the power delivery. I'm not sure if you have a type-C port already on your machine, but it may provide the full 10 GBPS/3A requirement if it's a direct type C port. The 3.0/3.1 gen1 hubs only provide 1.5A of power and 5 GBps, so while the Pi could run on it, you couldn't power any attached devices and would get the reduced lightningbolt symbol performance as well. The powered hubs have dedicated charging ports, but these wire directly to the hub and not the machine, so while providing more power at a cost.
I also tried installing Gapps (BitGapps) for Android 11 but it failed once I signed in with a Google account. Oh well. 32-bit Gapps are also harder to come by anyway. For now I can always sideload apk files which don't rely on the play stuff and use Chrome for browsing. That's a good start.
The reason I need Android 11 is mostly for accessibility. Unlike for sighted folks where lower Android versions don't make an impact on how and what you can use, for the blind, each Android version introduces changes to the accessibility API. This is important as these changes can allow for things like brand new touch gestures (completely different gestures/ swipes and touches in Android 11 with Talkback ) to actual improvements on what the screen reader "sees" in the UI. So no, I'm not doing this to just have the version number myself, but to benefit from the latest changes to Android's accessibility API. I hope this makes sense.
Click to expand...
Click to collapse
Thanks for confirming that ADB over USB-C is working. This might be something that will be enabled by default in future builds.
Latest BiTGapps (BiTGApps-arm-11.0.0-R19_signed.zip) should work just fine. I haven't received any other reports with issues.
Yes, I totally understand that new Android versions bring improvements, that's the whole point. But IMO simply having a bigger version number shouldn't be any reason for doing releases if it's not otherwise feature ready or some things are broken. This is a bit of problem in this "scene" where early utterly broken stuff is being endorsed just because of the version number.