Develop Bugs

[DEV] Nemo Mobile - Alpha

This is non androd, non based on android ROM
This OS based on Meego.
I promised to publish a small guide how to boot Nemo Mobile on your phone instead of the default android. Here is a small guide how to do so. The process it self is quite simple and should be relatively safe as well, as you do not need to flash anything to try it out.
In this guide it is assumed that one has android tools, such as adb and fastboot installed, also Linux is assumed but it should work also on windows with minor modifications.
The phone used was unlocked/rooted before I tried this, so that might also be required for following these instructions.
First thing is to download all the needed files:
Downloads:
rootfs image: - http://sage.kapsi.fi/sagestechblog/gt-i9250/2012-04-26.1/nemo-handset-armv7l-gt-i9250.img.bz2
Kernel: - http://d-h.st/Ffw (also with this kernel you can boot arm linux)
Instruction:
Push the rootfs image to the /sdcard
# Uncompress
adb shell bzip2 -d /sdcard/nemo-handset-armv7l-gt-i9250.img.bz2
adb shell mv /sdcard/nemo-handset-armv7l-gt-i9250.img /sdcard/image.img
2. Download and flash kernel.elf
fastboot flash boot kernel.elf
fastboot reboot
Or with Flash Tools
3. Connect mouse via OTG
After this, the device should boot to the MTF based UX home screen.
What works:
USB OTG
USB Mouse/Keyboard
Display
Backlight
What no works:
Xorg starts with standard fbdev (no 3D acceleration)
Applications do not start as the software flag isn't forwarded properly
No window manager/application switcher (requires 3D)
No 3D acceleration
Touch screen
Sensors (Especially disabled)
No USB networking
No WLAN
No Bluetooth
No Sound
Touch keys
Hardware keys
...
Kernel sources:
https://github.com/XperiaNext/kernel_sony_msm8x60/tree/msm-3.0.67-fb

Changelog:
Alpha
- Added in kernel framebuffer support for booting this OS

Small preview:
Video:
Screenshots:
{
"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"
}

WOW，looks very powerful, but not for daily use.

Wow nice :good: keep going
waiting for better version with working touch . wifi etc....

[8.x / 7] WinPE 32-bit en-US

Might be you need a "32-bit Windows 8.x / 7 Rescue Disk (WinPE)" at some point. If you won't create such a WinPE by yourself, you might use the one I created by means of phantastic WinBuilder - a script engine that will run a project developed by you, which produces a very efficient boot disk . Note, that this WinPE boots in legacy mode and only comes with legacy apps.
{
"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"
}
• Requirements:
1. At least 1 GB RAM; the WinPE completely is copied to RAM and runs from therein.
2. A storage device with at least 1 GB; the WinPE currently is ~225 MB of size.
3. A VESA-compatible display device. Note, that screen resolution will be set to 1024x768 and colordepth to 32-bit.
• Network:
Wireless networking is not supported in WinPE, this WinPE uses TCP/IP and/or NetBIOS over TCP/IP to provide network access and support for standard network drivers. Hence connect the PC to a router using an ethernet cable before booting.
• How To:
» You burn the .ISO on CD/DVD/BD or USB-stick (use 2x speed).
» You direct your Windows 8.x / 7 32-bit computer to boot from the storage device you burnt the .ISO onto.
» You power off the PC.
» You insert the CD/DVD/BD or plugin the USB-stick.
» You restart your Windows 8.x / 7 32-bit computer.
If WinPE has successfully booted, you right click anywhere in the desktop to get the WinPE's MENU shown. You wiil not find a pretty GUI with buttons and nice graphs!
• Disclaimer:
This WinPE only was tested in VMWare Player. It comes with no warranty or official support - I will try to help with any bugs or issues that people report when I get chance but this is not in any way guaranteed. No guarantee of final success or absence of undesirable side effects is being given hereby. Any liability of any kind will be rejected. I cannot be held accountable for any loss of data that occurs as a result of using this WinPE, you use the programs included AT YOUR OWN RISK. Be aware in WinPE environment you are "nt authority/system", which is the highest level on a local system, above Administrator.
TO GET AN IDEA, WHAT A PROGRAM INCLUDED IS FOR, PLEASE VISIT ITS RESPECTIVE WEB-SITE.
This WinPE comes with no programs' documentation! Might be with next version of this WinPE.
• License, Use, Copying, and Distribution:
Because this WinPE compilation only is based on free softwares, it is licensed as Freeware and free to download and for personal and commercial usage.
• Trade-Marks and Proprietary Notices:
Parts of this WinPE contents might be protected by copyrights, trademarks, trade secrets, or other proprietary rights, and if so, these rights are valid and belong to the authors of the softwares injected in the WinPE. "Microsoft Windows PE 5.0" which this WinPE is built on, is copyrighted by Microsoft.
• Credits:
Misty, who provided an excellent basic WinBuilder-project ready to start with
grischka, who developped bbLean, a Windows Shell Replacement that appears spartan and minimalistic compared to a normal Windows interface and is therefore resource saving.
• Version History:
v1 2014-05-01
Download: WinPE-32bit-en-US-v1.iso
MD5 Checksum: 4c7bcc301463dd04b8ed69865aa9b82a

Developer Menu Application - For WPInternals unlocked phones ONLY

Some people may have never heard of developermenu.efi, it's an efi application Microsoft mostly uses on test devices which allows you to do many things, here are the main highlights:
Note: if some people have a problem with getting this efi to display something, please use this one: https://forum.xda-developers.com/windows-10-mobile/exe-binaries-binaries-w10m-oem-kit-t3476453
Enter Mass Storage mode directly on the phone without the need of a computer.
Delete and dump the UEFI variable storage from the phone (be careful with this you can easily cause problems).
Tickle the battery to 0% (useful for re-calibration).
This EFI application is test signed, this means you must run it on an unlocked device.
{
"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"
}
It's also the latest available (from 15254.158).
You can create a new entry in BCD for a new bootapplication and reference it in the place you did put the efi. You also must make sure you turn on nointegritychecks on it because it's test signed.
For reference here's what Microsoft actually does to BCD when installing it (aside from nointegritychecks):
You must place the files attached in EFIESP\windows\system32\boot\
Provided are also the latest bmpx files which enables graphical status when you're in mass storage (also works when switched using WPInternals).

L630DS work fine but I don't see anythynk, just black screen.
PS: tried use different devmenu efi(from this post) and it work and display.

the_R4K_ said:
L630DS work fine but I don't see anythynk, just black screen.
PS: tried use different devmenu efi(from this post) and it work and display.
Click to expand...
Click to collapse
What doesn't display? The menu or when you enter the mass storage section? That efi should defintely work except maybe on rs2+, didn't check everything but I vaguely remember MS breaking feature manifest policies with rs2.

gus33000 said:
What doesn't display? The menu or when you enter the mass storage section? That efi should defintely work except maybe on rs2+, didn't check everything but I vaguely remember MS breaking feature manifest policies with rs2.
Click to expand...
Click to collapse
menu.
I can't say my build because my phone...
I have this configs:
w10m 15254.1(one big part)
winRt(small part in end of drive)
efiesp(maybe different version than system likely wp8...)
But intresting that another file work fine.

How about tutorial?

augustinionut said:
How about tutorial?
Click to expand...
Click to collapse
I can't actually make a tutorial now because each people have their own way of loading entries from bootmgr, but I have planned making a whole post about bootmgr and bcd entries and how to have multiple of them on a lumia device in the future, afterwards sure.

Please make tutorial using bcdedit

I have BSOD on 950
UPD: My fault, i had efi file on wrong partition

So I do have a question on this, it is the 'Reset your phone' inside "About" that we use to open this, right? (running 10586 on a htc one m8, trying to follow your guide on unlocking the bootloader)
update: nevermind, its a hard reset and not a factory reset

[GUIDE] VMOS on GSI ROMs

Hi all,
I found that VMOS also works on GSI Roms [A10] , [A11], maybe it will be interesting for someone...
VMOS is an APP software based on Virtual Machine (VM). VMOS can be installed in the form of a normal APP to Linux or Android system through VM technology. That is to run another complete Android system through an application Moreover, VMOS is not controlled by the host system. (Android on the phone).
VMOS Features:
- Create a Fake Phone Environment: Use VMOS to create a full virtual Android environment with a working Play store and network connectivity. This virtual Android machine will run Android 7.1 and appears as a native OS with full touch control just like you would use on your primary Android system. The Android VM is complete with an app drawer, Google services, and some standard apps like a file manager and internet browser. You can sign in with your gmail account and access the full Play store and download new apps as well.
- Root Support: The virtual machine that you create in VMOS can be rooted without affecting the primary system. This is a good solution for anyone looking to run root apps but don’t have the ability to root their actual phone. This is also an essential feature for developers testing apps. Root access is often required for specific functions of different applications. Now developers can run them without risking corrupting the primary system.
- Multiple Accounts and Apps: With the ability to run two Android systems on one phone, you can use the virtual space to run duplicated apps with different accounts. The VM is a good way to keep your personal apps and accounts separate from your work. Sign in with your personal email, snapchat, twitter ect. on your main system, then put all of your work related accounts on the VM. You can run VMOS in a floating window, making it easy to switch between systems quickly, giving you faster access to duplicated apps.
Official website:
https://www.vmos.com/
Apk for [A10] - LOSQ-17.1 etc.:
Download
Apk for [A11] - Lir-18.1, CAOS etc. (pre-rooted with SuperUser):
Download
Screenshots - Lir-18.1
{
"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"
}

I accidently updated my phone and now it's running Android 12.
Anyone know if a workaround to get vmos running on A12?

HobbesG6 said:
I accidently updated my phone and now it's running Android 12.
Anyone know if a workaround to get vmos running on A12?
Click to expand...
Click to collapse
Ask here

Hi there, with installed
VMOS can Huawei stock camera work on Treble ROMs? For example, version EMUI 5? (Android 7).

Fjord1 said:
Hi there, with installed
VMOS can Huawei stock camera work on Treble ROMs? For example, version EMUI 5? (Android 7).
Click to expand...
Click to collapse
It would be great, but unfortunately no.

Is there any way to make magisk work on vmos?

Tan22 said:
Is there any way to make magisk work on vmos?
Click to expand...
Click to collapse
VMOS didn't support Magisk yet.

Just downloaded workex for certain time and screen stop responding any fix

Themes / Apps / Mods [ROOT] Virtual Machine with KVM acceleration for Tensor Chips

Hi all,
On Android 13, Google enabled KVM support for Tensor Chips model(Pixel 6 / 6pro / 6a). So we can run a Virtual machine at full speed, but there is no APP to utilize this feature.
I modified the Limbo Emulator (QEMU), so it can enable the KVM on Pixel 6 Phones. Due to the limitation of the kernel, the APP needs ROOT permission to access the KVM service(/dev/kvm)
Currently, only VNC is working on this APP, and you can only boot directly using the Linux kernel. UEFI did not work on KVM.
Network functions worked, but you may need to set the DNS inside the Guest OS.
Arch Linux for arm64 runs pretty well on Limbo. It runs even faster than Raspi 4. You can download it from ArchLinuxARM-aarch64-latest.tar.gz
Other Linux can also run on the Limbo, but you may need to recompile the kernel to enable virto-related functions.
Download link:
Releases · wasdwasd0105/limbo_tensor
Limbo for Tensor is a QEMU-based Hypervisor for Tensor-based Google Pixel devices such as Pixel 6 & 7 series. - wasdwasd0105/limbo_tensor
github.com
{
"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"
}

Interesting concept. If I get some time I'll give it a whirl.
Thanks for this

Gives me a "package appears to be invalid" when trying to install. Assuming this could be a signature issue? not sure....

im having same issue
edit: you need to install the debug apk with adb
Code:
adb install -t <name-of-apk>
it would be awesome if this app had a terminal emulator function so you dont have to exclusively use the vnc viewer.

Can confirm this^ works. Would love to install w11 with this. Looks good

Is anyone else having issues with being able to bring CPUs online since the v0.2.1 update? It seems that each boot a random amount of allocated CPUs will online (it seems to mostly be just one), and attempting to online the ones that failed results in:

ryaniskira said:
Is anyone else having issues with being able to bring CPUs online since the v0.2.1 update? It seems that each boot a random amount of allocated CPUs will online (it seems to mostly be just one), and attempting to online the ones that failed results in:
View attachment 5741675
Click to expand...
Click to collapse
Try 0.22

Unfortunately the issue still exists.
I've attached a log on Pastebin though I can't see anything obviously wrong other than Java not being able to find a file.

ryaniskira said:
Unfortunately the issue still exists.
View attachment 5743195
I've attached a log on Pastebin though I can't see anything obviously wrong other than Java not being able to find a file.
Click to expand...
Click to collapse
can you try using uefi mode？

uefi mode results in nothing.

UEFI + Debian works just fine. One issue i have is that ssh port forwarding just doesn't work, but telnet does (but it forgets i set it every time i launch the app).
Is there a telegram group for this project?

Can you please share how you created the EFI pflash image, specifically the part where the memory write issue is resolved. I have an idea on how to fix Windows, but I've not ever seen the memory write issue.