In keeping with our weekly update schedule, Remix OS for PC version 3.0.103 update is now available OTA.
Please use the 'System update' app found in your app drawer to initiate the update.
Release notes:
Remix OS for PC version: 3.0.103
Release date: August 9, 2016
Setup wizard now skips Wi-Fi connection step if LAN is connected
File Launcher now aligns icons to grid
GMS can now be activated during the setup wizard
Key-mapping tool now enabled by default
Fixed more Wi-Fi issues
Fixed App drawer crashing when ‘Search’ nets no results
Fixed wallpaper distortion
Important note:
If you have key-mapping tool and/or GMS disabled in version 3.0.102, updating to version 3.0.103 will cause problems if you want to activate these apps in 3.0.103.
If you plan to use these apps, we advise you first activate these apps while still running 3.0.102 before updating to version 3.0.103.
If you have no plans to use either of these apps, you don't need to do anything.
Thanks for the update. Please in next update, fix Video playback issues.
hi , nice job ..
i want to esposing two problems
i have an wacom graphic tablet , everithing work , also push sensitivity of the pen... it work perfectly on classic launchers but on remixos launcher doesnt work double tap and the trag and grab of the icons ... expecially on the app launcher and the file manager
another problem is with the logitech wireless keyboard, the extra key's (volume up and down, music player , mail etc..) doesnt't work ... on the remixos 2.x it work perfectly
thanks for the nice wok
I see it.. but when trying to install:
Start updating..
SRC=/android-2016-08-03
ui_printWaning: No file_contexts
script aborted: system partition has unexspected contents
ui_print system partition has unexspected contents
ui_print
error in data/media/0/autoupdater/otapackage.zip (status 7)
update failed
---
any otherway to update?
-I did noticed the the actual update zip is not called Otapackage.zip
My RemixOS 32bit is installed on sda2/ext4/30gb (using INSTALL=1 with Nvidiacard modeset )
Cheers
Wi-Fi doesn't connect reliable
I am working with version 3.0.103 32bit on a Lenovo T400. Remix OS has been installed on a partition of the hard drive (boot option INSTALL=1). After starting Remix OS in most cases the Wi-Fi is not connected automatically, as long as the "Wi-Fi" pop-up window is not opened yet. After opening the Wi-Fi pop-up window Wi-Fi is connected automatically a few seconds later. So it's not a big problem, just not comfortable.
mitchell4you said:
I see it.. but when trying to install:
Start updating..
SRC=/android-2016-08-03
ui_printWaning: No file_contexts
script aborted: system partition has unexspected contents
ui_print system partition has unexspected contents
ui_print
error in data/media/0/autoupdater/otapackage.zip (status 7)
update failed
---
any otherway to update?
-I did noticed the the actual update zip is not called Otapackage.zip
My RemixOS 32bit is installed on sda2/ext4/30gb (using INSTALL=1 with Nvidiacard modeset )
Cheers
Click to expand...
Click to collapse
Got the same error. Unfortunately torrent from the site is 3.0.103 so can't update the normal way.
mitchell4you said:
I see it.. but when trying to install:
Start updating..
SRC=/android-2016-08-03
ui_printWaning: No file_contexts
script aborted: system partition has unexspected contents
ui_print system partition has unexspected contents
ui_print
error in data/media/0/autoupdater/otapackage.zip (status 7)
update failed
---
any otherway to update?
-I did noticed the the actual update zip is not called Otapackage.zip
My RemixOS 32bit is installed on sda2/ext4/30gb (using INSTALL=1 with Nvidiacard modeset )
Cheers
Click to expand...
Click to collapse
The update of an "INSTALL=1" installation is described here .
In order to perform the update you need to start a Linux operating system using a pendrive (e.g. PartedMagic), in order to rename the basic directory from /android-2016-08-03/ to /android-2016-08-08/ and in order to delete all directories within the basic directory other than /android-08-08/data.
After this step you can perform a normal installation (INSTALL=1), but you must not format your partition sda2 because you want to keep your data.
Ahh... i still cant boot / install on Chuwi Vi10 Pro. I stuck here again:
{
"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"
}
Thanks the update went flawlessly.
For some reason, I got again the error with the Playstore and the communication problems with the google service. Did I do anything wron, during the install process? I did a clean install and chose to go with the GSM in the wizard.
hundsboog said:
For some reason, I got again the error with the Playstore and the communication problems with the google service. Did I do anything wron, during the install process? I did a clean install and chose to go with the GSM in the wizard.
Click to expand...
Click to collapse
Did you remember immediately to reboot after using the GSM wizard? If you try to use the Playstore without rebooting first then it won't work.
lollyjay said:
Did you remember immediately to reboot after using the GSM wizard? If you try to use the Playstore without rebooting first then it won't work.
Click to expand...
Click to collapse
Yes Sir, I waited till the wizard was done and did a reboot immediately without touching anything.
remixtester said:
The update of an "INSTALL=1" installation is described here .
In order to perform the update you need to start a Linux operating system using a pendrive (e.g. PartedMagic), in order to rename the basic directory from /android-2016-08-03/ to /android-2016-08-08/ and in order to delete all directories within the basic directory other than /android-08-08/data.
After this step you can perform a normal installation (INSTALL=1), but you must not format your partition sda2 because you want to keep your data.
Click to expand...
Click to collapse
Hmm..
Then I'm giving-up.. ( till this gets resolved )
First I installed the 27jul build.. that hat no update... then I installed aug3 build with updater..
An now it seems.. the updater doesnt work...
This downloading the full ISO every week.. is not for me..
i did a ''pm disable com.jide.autoupdate' to stop it nagging
-- Bah.. if you disable the updater.. the taskbar no longer works ( thumz down )
Cheers
Thanks Devs.
Updated without a hitch
Wireless not connecting automatically on boot is fixed on my aspire V5-122p
Standby still broken but I can live with that.
Thanks your work! I try many version after, even 3.0.103 but can't make it work with Clover Bootloader, when add entry Remix OS into Clover boot by path: EFI\Boot\grubx64.efi but nothing happen, just dark screen.
Only with this version i can make it work with Clover boot loader.
Would you fix it, please sir?
NO I upgrade , I have version 3.0.102 I open the app to update and give closes click download and not download anything.
Good
I updated new version remix os is ok ^^ ! No problem, can only hope the next version will support HDMI out TV : Good:
hundsboog said:
Yes Sir, I waited till the wizard was done and did a reboot immediately without touching anything.
Click to expand...
Click to collapse
same here. error to communicating with google server. any advise?
please get touch screen working for surface 3
Game Toolkit is still not showing up for me. I came straight from 3.0.102 even then it didn't show even when enabled.
Related
{
"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"
}
picture related, sorry for bad potato quality, using twitter camera instead of the default camera.
after updating the OTA to the newest build, it seems that after opening the app that has a "forced full screen". it might crashes and reboot it and now, the taskbar has disappear.
I've been recreating the problem twice, along with reinstalling Remix OS. I can confirm the main problem is in fact due to the full screen apps (some are forced) will crashed and reboot. the taskbar won't appear.
as for work-a-rounds, honestly, no idea. I already reported the bug to Remix Staff already, I feel confident that it going to be fixed quickly.
specs:
Computer/Laptop: Toshiba Satelite C55Dt-A
Disk Drives: Toshiba MQ01ABF050 Hard Drive (dual-boot)
Graphics Card: AMD Radeno HD8400 / R3 Series
CPU: AMD A6-5200 APU
BOOT: Legacy
OS: Remix OS Build 2.0.201
AL2009man said:
picture related, sorry for bad potato quality, using twitter camera instead of the default camera.
after updating the OTA to the newest build, it seems that after opening the app that has a "forced full screen". it might crashes and reboot it and now, the taskbar has disappear.
I've been recreating the problem twice, along with reinstalling Remix OS. I can confirm the main problem is in fact due to the full screen apps (some are forced) will crashed and reboot. the taskbar won't appear.
as for work-a-rounds, honestly, no idea. I already reported the bug to Remix Staff already, I feel confident that it going to be fixed quickly.
specs:
Computer/Laptop: Toshiba Satelite C55Dt-A
Disk Drives: Toshiba MQ01ABF050 Hard Drive (dual-boot)
Graphics Card: AMD Radeno HD8400 / R3 Series
CPU: AMD A6-5200 APU
BOOT: Legacy
OS: Remix OS Build 2.0.201
Click to expand...
Click to collapse
Can you bring up the menu by pressing the Windows key?
Ameris Cyning said:
Can you bring up the menu by pressing the Windows key?
Click to expand...
Click to collapse
tried, didn't work.
Remix os new ota update removed line ro.remixos.no_wallpaper=true in build.prop, use remix tool to extract then add that line in system/build.prop and repack back system.img and problem will resolve hope that help
And there isn't any simpler solution like anything with the root terminal?
Alias X said:
And there isn't any simpler solution like anything with the root terminal?
Click to expand...
Click to collapse
#echo ro.remixos.no_wallpaper=true >> /system/build.prop
If you have system rw
But first check Settings ==> Experimental features ==> zoom level
arts821 said:
Remix os new ota update removed line ro.remixos.no_wallpaper=true in build.prop, use remix tool to extract then add that line in system/build.prop and repack back system.img and problem will resolve hope that help
Click to expand...
Click to collapse
How can I use the tool to do this? You are speaking about the Remix OS installation tool?
Alias X said:
How can I use the tool to do this? You are speaking about the Remix OS installation tool?
Click to expand...
Click to collapse
not remix os installation tool, but rmxtool v1.5 from imadlatch, ty for great software:good:
and remove all ffmpeg line from build.prop cause its cause blinking for some system
arts821 said:
not remix os installation tool, but rmxtool v1.5 from imadlatch, ty for great software:good:
and remove all ffmpeg line from build.prop cause its cause blinking for some system
Click to expand...
Click to collapse
I know the blinking too. ^^ Where can I download it?
Alias X said:
I know the blinking too. ^^ Where can I download it?
Click to expand...
Click to collapse
u can search in Remix os for pc XDA forum for Rmxtools
I'm
HypoTurtle said:
#echo ro.remixos.no_wallpaper=true >> /system/build.prop
If you have system rw
But first check Settings ==> Experimental features ==> zoom level
Click to expand...
Click to collapse
I tried that option, it didn't work for me. I'm not sure if I'm doing something wrong.
EDIT: I GOT It WORKING.
Apparently, I suppose to drop it in the right location, none of the people here didn't specify which line should I put. I'd had to dig in the older build file in order to find the right location.
Message me 4 solution
Private message me
Have uploaded edited build.prop to dropbox
Also usefull apk's i used to fix
JoeyTheRev
I'm Having the same issue... once or twice the taskbar appeared correctly, but for the most times, is completly absent, and with that problem remix OS is useless.
I'm kinda new to this (Remix OS, rooting android, etc), but remix OS is a excellent option for those old notebooks and netbooks that suffer with Windows 8 and up, so i dont want to give up that easy.
I have a HP Mini with this hardware:
CPU: AMD A4-1200 APU with Radeon Graphics 1.00 Ghz
RAM 2.0 GB
Graphics: AMD A4-1200 APU with Radeon Graphics 1.00 Ghz
HDD: Harddrive with dual boot with windows 8.
Any clue of how to solve this? have you heard if there going to be an update that fix this anytime soon?
thanks in advance!
arts821 said:
Remix os new ota update removed line ro.remixos.no_wallpaper=true in build.prop, use remix tool to extract then add that line in system/build.prop and repack back system.img and problem will resolve hope that help
Click to expand...
Click to collapse
How to repack back system.img? ^^
So, how did you get it working?
AL2009man said:
picture related, sorry for bad potato quality, using twitter camera instead of the default camera.
after updating the OTA to the newest build, it seems that after opening the app that has a "forced full screen". it might crashes and reboot it and now, the taskbar has disappear.
I've been recreating the problem twice, along with reinstalling Remix OS. I can confirm the main problem is in fact due to the full screen apps (some are forced) will crashed and reboot. the taskbar won't appear.
as for work-a-rounds, honestly, no idea. I already reported the bug to Remix Staff already, I feel confident that it going to be fixed quickly.
specs:
Computer/Laptop: Toshiba Satelite C55Dt-A
Disk Drives: Toshiba MQ01ABF050 Hard Drive (dual-boot)
Graphics Card: AMD Radeno HD8400 / R3 Series
CPU: AMD A6-5200 APU
BOOT: Legacy
OS: Remix OS Build 2.0.201
Click to expand...
Click to collapse
Looks like 2.0.402 Build has solved that problem.
Sadly, I cannot confirm it myself due to my broken laptop (typing it from my Phone as of this post)
"Taskbar has magically disappear [sic] in the newest Remix OS build"
"... has disappeared ..."
AL2009man said:
I'm
I tried that option, it didn't work for me. I'm not sure if I'm doing something wrong.
EDIT: I GOT It WORKING.
Apparently, I suppose to drop it in the right location, none of the people here didn't specify which line should I put. I'd had to dig in the older build file in order to find the right location.
Click to expand...
Click to collapse
which line please....
Hello,
I've been trying to install RemixOS on old Acer Aspire One zg5 as standalone os.
I created a boot drive from official image with official utility.
I booted it, selected 'Resident' hit TAB and added INSTALL=1 flag.
In CLI installer I formatted the drive to ext4 skipped both 'install grub' and 'install grub2' promts, said 'yes' to writable /system.
In the end of the installer script I selected 'run androidx86' and the system booted just fine.
BUT,
when I removed the thumbdrive and tried to boot the system again I got 'GRUB' with blinking underscore.
I tried different file systems (fat, ntfs) and I tried installing grub/grub2.
The results are the same - 'GRUB' with blinking underscore.
What am I doing wrong? How to fix this?
I just installed Remix on an HP Pavillion.
My steps were:
1. Burn the iso image from the official remix zip onto a dvd (it's already a bootable img)
2. Boot from the dvd drive
3. Press Tab to edit Resident Mode commands
4. Type "INSTALL=1 DEBUG=" press Enter
5. Select "create/modify partitions"
6. Delete any and all partitions
7. Create a new partition at maximum allocation
8. Select new partition to install and select ext4
9. Install grub, skip efi grub, do not allow read/write
10. Wait for it to install system files
11. Reboot
I found that with my device, typically first boot will not recognize my WiFi hardware, so I reboot again. I now have Remix with a 300gb storage space and no other operating system.
Imperius22 said:
I just installed Remix on an HP Pavillion.
My steps were:
1. Burn the iso image from the official remix zip onto a dvd (it's already a bootable img)
2. Boot from the dvd drive
3. Press Tab to edit Resident Mode commands
4. Type "INSTALL=1 DEBUG=" press Enter
5. Select "create/modify partitions"
6. Delete any and all partitions
7. Create a new partition at maximum allocation
8. Select new partition to install and select ext4
9. Install grub, skip efi grub, do not allow read/write
10. Wait for it to install system files
11. Reboot
I found that with my device, typically first boot will not recognize my WiFi hardware, so I reboot again. I now have Remix with a 300gb storage space and no other operating system.
Click to expand...
Click to collapse
Thanks I will try this.
Sent from my on Z00A using XDA Labs
Hi it didn't work.
At the menu to select Resident Mode it would not let me use Tab. Only e to edit which I did
I added add INSTALL=1 DEBUG=1? (Did you delete any lines?)
Had to press Ctrl-x to start at that point
From there did exactly as per your directions.
When asked whether to reboot or run I selected run.
Finished and booted RemixOS
When I rebooted I received the message Operating System not found :crying:
Sent from my Nexus 7 using XDA Labs
I installed a linux distro first(lubuntu 15.10) then installed remix. just stuck on boot screen. help here too. same netbook model.
elphamale said:
Hello,
I've been trying to install RemixOS on old Acer Aspire One zg5 as standalone os.
I created a boot drive from official image with official utility.
I booted it, selected 'Resident' hit TAB and added INSTALL=1 flag.
In CLI installer I formatted the drive to ext4 skipped both 'install grub' and 'install grub2' promts, said 'yes' to writable /system.
In the end of the installer script I selected 'run androidx86' and the system booted just fine.
BUT,
when I removed the thumbdrive and tried to boot the system again I got 'GRUB' with blinking underscore.
I tried different file systems (fat, ntfs) and I tried installing grub/grub2.
The results are the same - 'GRUB' with blinking underscore.
What am I doing wrong? How to fix this?
Click to expand...
Click to collapse
I have not had any luck with this either. The only thing I could do is a regular dual-boot install and then disable Windows boot in Grub. That's a "dirty" method I know, but I had to have something to keep Windows out of the picture. I hope that an upcoming version of Remix allows installation as sole OS.
I was having a similar issue. Attempting to boot from the flash drive the second time tab didn't work but e did I placed INSTALL=1 DEBUG= (don't put anything after the DEBUG=) at the end of the second from last line and then hit ctrl + X (hitting esc undoes your changes)
bomblord said:
I was having a similar issue. Attempting to boot from the flash drive the second time tab didn't work but e did I placed INSTALL=1 DEBUG= (don't put anything after the DEBUG=) at the end of the second from last line and then hit ctrl + X (hitting esc undoes your changes)
Click to expand...
Click to collapse
Yes I tried that without success. The entire process proceeds and then I can even login to Remix OS. But, when I reboot I get the message "No operating system"
I have disabled Secure Boot.
lollyjay said:
Yes I tried that without success. The entire process proceeds and then I can even login to Remix OS. But, when I reboot I get the message "No operating system"
I have disabled Secure Boot.
Click to expand...
Click to collapse
Hi you shouldn't be getting the normal boot screen with the INSTALL=1 DEBUG=
You should be getting something that looks like this
{
"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"
}
bomblord said:
Hi you shouldn't be getting the normal boot screen with the INSTALL=1 DEBUG=
You should be getting something that looks like this
Click to expand...
Click to collapse
Yes, that is what I did. I get to the end where it asks if I want to enter Remix or reboot. When I select reboot, that is where I get "No operating system"
lollyjay said:
Yes, that is what I did. I get to the end where it asks if I want to enter Remix or reboot. When I select reboot, that is where I get "No operating system"
Click to expand...
Click to collapse
When you install it you may have to install GRUB as a boot manager (watch out as it could mess with an existing windows install) and also install it as read/write
lollyjay said:
Yes, that is what I did. I get to the end where it asks if I want to enter Remix or reboot. When I select reboot, that is where I get "No operating system"
Click to expand...
Click to collapse
Can you try and format sda1 to vfat (fat32) and install to sda2 and see if that makes a difference and install efi grub; bypass grub install
why even bother with a standalone install if you already have ubuntu installed
http://forum.xda-developers.com/remix/remix-os/remix-os-installation-rooting-t3293769
~RemixOS_x64- UEFI or Legacy -Xposed-SuperSU-Gapps~
Based on version 3.0.207
UEFI Install
1- Download and extract the package I made
2- Run the installer and select the ISO file
3- Reboot and select: Remix OS option
4- Once in RemixOS open the play store and UPDATE SuperSU
5- Open SuperSU and update the binary. It should say success!!
6- Install XposedInstaller_3.0_alpha4.apk or XposedInstaller_3.1.1.apk (i installed 3.0 alpha4 but doesnt matter which)
7- Reboot and enjoy your RemixOS with newest SuperSU, working Xposed and Gapps
Legacy Install
1- Download and extract the package I made
2- Run the installer and select the ISO file
3- Reboot and select: Remix OS option
4- Once in RemixOS open the play store and UPDATE SuperSU
5- Open SuperSU and update the binary. It should say success!!
6- Install XposedInstaller_3.0_alpha4.apk or XposedInstaller_3.1.1.apk (i installed 3.0 alpha4 but doesnt matter which)
7- Reboot and enjoy your RemixOS with newest SuperSU, working Xposed and Gapps
~RemixOS_x64- UEFI or Legacy -Xposed-SuperSU-Gapps~: https://drive.google.com/open?id=0B_NCp06S3NUmWmVIVUN2ZXRzVDA
Xposed Installer 3.0 Alpha 4: https://drive.google.com/open?id=0B_NCp06S3NUmdG1XSWJGS3dBVUk
Xposed Installer 3.1.1: https://drive.google.com/open?id=0B_NCp06S3NUmU21iY3hCdUJtSFE
Credits go to all involved in creating the software in the first place. Please let me know if it works for you
PizzaG Windows 10 EFI Partition Helper: https://drive.google.com/open?id=0B_NCp06S3NUmUVpNR2RheHpOTlk
Run as Admin
The download link doesn't work, gives 404
@crazygamer64
Hopefully links are fixed. That's really odd, the links were working yesterday. But anyways, should be good again.
PizzaG said:
@crazygamer64
Hopefully links are fixed. That's really odd, the links were working yesterday. But anyways, should be good again.
Click to expand...
Click to collapse
worked now thanks!
@crazygamer64
How did the install go? I'm trying to get some feedback vs ROC version which is the same concept just put together a little different. Trying to narrow down some booting issues on various pc setups vs stock working. Thanks
PizzaG said:
@crazygamer64
How did the install go? I'm trying to get some feedback vs ROC version which is the same concept just put together a little different. Trying to narrow down some booting issues on various pc setups vs stock working. Thanks
Click to expand...
Click to collapse
Well, everything worked out great except for that termux command which gave me : can't open flash-script.sh
crazygamer64 said:
Well, everything worked out great except for that termux command which gave me : can't open flash-script.sh
Click to expand...
Click to collapse
UEFI or Legacy install? If UEFI, maybe try the steps from legacy. cd /system.xposed
then run sh flash-script.sh
PizzaG said:
UEFI or Legacy install? If UEFI, maybe try the steps from legacy. cd /system.xposed
then run sh flash-script.sh
Click to expand...
Click to collapse
Well if I try that then it gives me: no such file or directory edit: now it worked, u typed an . Instead of an /
Termux now gave me: can't create '/system/Xposed.prop': file already exists
Also I am using UEFI
Giving this a shot now. Will update.
Are you planning on maintaining this with OTA updates?
Edit: Awesome. I have Remix OS x64 with R/W and Xposed. Worked great, PizzaG. Many thanks!
Time to AdBlock the crap out of everything.
bobdamnit said:
Giving this a shot now. Will update.
Are you planning on maintaining this with OTA updates?
Edit: Awesome. I have Remix OS x64 with R/W and Xposed. Worked great, PizzaG. Many thanks!
Time to AdBlock the crap out of everything.
Click to expand...
Click to collapse
Glad it worked out for you. Yes, I'll do my best to maintain it as OTA updates come out
PizzaG said:
Glad it worked out for you. Yes, I'll do my best to maintain it as OTA updates come out
Click to expand...
Click to collapse
Awesome. One thing to note, I could not get SuperSu to open at all while in DEBUG mode. I ended up booting normal Remix OS and enabling the debug console and doing it this way. Just a heads up!
Sweet sweet proof:
{
"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"
}
Also, like I previously stated... If you also have another operating system installed (I have Windows 10 Pro x64) you can modify a few things about the new bootup process. Wherever you installed Remix OS (I've installed it to a seperate partition, so for me it is E:/), go there.
- Open the Remix OS folder
- Find "menu.lst" and open it with Notepad++
- Delete the entry for Remix OS DEBUG. Delete the whole entry
- Change "timeout" from '10' to '0'
- Save the file
It will look very similar to this:
Code:
default 0
timeout 0
title Resident mode - RW enabled
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_x64 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
What this will do is remove the entry for Remix OS DEBUG -- INSTALL XPOSED, force standard rooted/xposed Remix OS to boot automatically, and remove the 10 second timeout before the Remix OS selection allowing Remix to boot automatically after selecting it in the Windows bootloader. For advanced users, this can be accomplised in the Remix OS/Remix OS DEBUG selection screen also, by pressing Escape to enter the selection screen, "e" to edit lists, and following the on-screen instructions for deleting selections and saving.
Hope this helps!
Worked perfectly, thanks my friend.
After downloading, the RAR won't extract, says that the file is incomplete, any idea?
jor3l said:
After downloading, the RAR won't extract, says that the file is incomplete, any idea?
Click to expand...
Click to collapse
Your download may be corrupted, try downloading again.
Grindher said:
Your download may be corrupted, try downloading again.
Click to expand...
Click to collapse
Already tried 3 times, same result on my mac, just to confirm this is the MD5 of the file:
MD5 (RemixOS_x64- Xposed-SuperSU-Gapps[v2].rar) = 44ba6fcc6330ad98f1ac375d29b54c5f
---------- Post added at 03:15 AM ---------- Previous post was at 02:57 AM ----------
Worked using WinRar, seems like an issue with The Unarchiver (mac), now testing..
howdy,
successful x64 efi install, bootup, xposed (no flash-script, XposedInstaller_3.0_alpha4.apk works, 3.1.1 doesn't).
apparently everything is nominal. xposed youtube adaway seems to be working. (!)
(i do have a remix problem with my fav game five card draw - grunging $ and win/loss amounts, but that's a remix problem not your adaption)
HP Pavilion x2 12-b020nr 12" Detachable Laptop (Intel Core M3, 4 GB RAM, 128GB SSD) with Windows 10
32gb ntfs partition for remix, use grub2win to boot into remix
good work!
Thanks your work, but seem it not working with Ext4 File system of partition, how can i explan data partition Remix OS from 4Gb to 32Gb?
http://support.jide.com/hc/en-us/articles/218463867-How-to-increase-the-memory-size-
daWyrd1 said:
http://support.jide.com/hc/en-us/articles/218463867-How-to-increase-the-memory-size-
Click to expand...
Click to collapse
thanks you! but i wonderwhy which type format of partition is support for that? maybe only NTFS or include Ext4, bro?
Thanks, it work for me
daWyrd1 said:
howdy,
successful x64 efi install, bootup, xposed (no flash-script, XposedInstaller_3.0_alpha4.apk works, 3.1.1 doesn't).
apparently everything is nominal. xposed youtube adaway seems to be working. (!)
(i do have a remix problem with my fav game five card draw - grunging $ and win/loss amounts, but that's a remix problem not your adaption)
HP Pavilion x2 12-b020nr 12" Detachable Laptop (Intel Core M3, 4 GB RAM, 128GB SSD) with Windows 10
32gb ntfs partition for remix, use grub2win to boot into remix
good work!
Click to expand...
Click to collapse
I try but not work,still error like this
Any idea with my problem,bro?
Gá»i từ Redmi Note 3 của tôi bằng cách sá» dụng Tapatalk
First of all thanks to @ab123321 for porting Android Wear 2.0 to LG Watch G.
Note: I am not responsible for bricked devices, dead SD cards, or any problems that may arise from flashing this ROM.
Virtual Home Button for Android Wear 2.0
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"
}
Description:
Today I have created a system app called Home Button which help us to simulate physical Home Button by tapping a virtual button.So we can use this virtual button to open a wear's default launcher and to complete the wear tutorial (After Reset / Fresh installation.No more paper clips). Also you can use this button on 3rd party app to simulate Home Button if its required.
Features:
Single Press to open android launcher.
Long Press to open Google Assistant.
Auto Start at Boot.
Screen position can be configured .
Transparency can be configured.
Installation:
System Image - App packed inside. This image is created using @ab123321's script. So same as ported rom with App packed inside.
Flash the system image provided below using fastboot.
Code:
fastboot flash system dory.img
Manual installation of APK: (Not necessary if you flashed system image using above method)
1. Create a folder called "HomeButton" under /system/app/
2. Copy the apk into the folder
3. Set permission to 644
4. Restart.
Download:
Version 3:
Note: If you are in version 2 and Google Assistant is working fine for you means you don't need this version. Only updated Google App to 8.20.13.25 and HomeButton to 3.0.0 in this version.
System Image: https://oload.win/f/9D-exXddqkQ/dory_v3.img
APK: https://oload.win/f/SbiakGiQaC8/HomeButton_v3.apk
http://www.mediafire.com/file/unhxocqbt6jbdhs/HomeButton_v3.apk/file
http://www.mediafire.com/file/2ccexhw8jdwr6c5/dory_v3.img/file
Version 2:
System Image: https://oload.win/f/2dvx9cn1Nyc/dory_v2.img
APK: https://oload.win/f/o2x4ZzBoK1Y/HomeButton_v2.apk
Mirrors:
http://www.mediafire.com/file/unhxocqbt6jbdhs/HomeButton_v3.apk/file
http://www.mediafire.com/file/2ccexhw8jdwr6c5/dory_v3.img/file
http://www.mediafire.com/file/35a6775f77d4y27/dory_v2.img
http://www.mediafire.com/file/3r8pz8z9xy2en24/HomeButton_v2.apk
Hash:
dory_v3.img
SHA1: 2FE8B8C23752F990DB1A83122014F92CC15C4E1F
HomeButton_v3.apk
SHA1: 50E3A6DACDD5B0DD7DE18CDE53718E16C5426C60
dory_v2.img
MD5: 84193D0600A5EA1A7C8BE0BE6D31F48C
SHA-1: B69062BF6B21160E42E687F6870DAE8F82F417B8
HomeButton_v2.apk
MD5: 039F379BF5E75000048E77FD5F6CFBB4
SHA-1: 1E6D15271F2551DAFB69E4755945C8C6F038B311
Oh! That's GREAT!
I flashed your system image, and it is working fantastically. Thank you. One word of warning for other users the first boot after flashing took around 10 minutes so don't panic just let it do it's thing.
Has anybody notice if they hold 2 fingers on the screen to turn it off it actualy triggers a command to open the app drawer. Maybe we could expand this built in feature.
---------- Post added at 10:20 PM ---------- Previous post was at 10:11 PM ----------
can anybody help my pc wont pick up my watch in fastboot mode after the wear 2.0 update
---------- Post added at 10:31 PM ---------- Previous post was at 10:20 PM ----------
finally got abd to work and fastboot devices lists my watch now but the home button img will not install it comes up uknown error data transfer failed? please help.
Finally fixed all the errors and it has installed correctly now but the ROM is very unstable, constantly crashing,freezing and jamming up and the button is often non responsive. The other port for this without home button runs flawlessly so maybe collaborate on the project and intergrate each other works into one project.
brostar2017 said:
Finally fixed all the errors and it has installed correctly now but the ROM is very unstable, constantly crashing,freezing and jamming up and the button is often non responsive. The other port for this without home button runs flawlessly so maybe collaborate on the project and intergrate each other works into one project.
Click to expand...
Click to collapse
Are you sure? Anyone else facing this issue?
I'm using this rom from last 7 days. I'm not facing any issue or any lagging.
FYI,I'm using this boot image. https://forum.xda-developers.com/showpost.php?p=73743155&postcount=511
Using the same image and the watch is barely usable with this image across multiple g watches. The other one without but is smooth and instant responds.
Updated.
Changelog:
New system image. (Unpacked @ab123321's latest system image and packed with apk)
Long press to open Google Assistant
brostar2017 said:
Using the same image and the watch is barely usable with this image across multiple g watches. The other one without but is smooth and instant responds.
Click to expand...
Click to collapse
Can you try new system image? Because this image is created by unpacking ab123321's original image and packed with apk.
install manual
How i install manual this program? i guess with minimal adb. i don't want to flash that file on my watch again. can someone do a tutorial? please!
the new system image is amazing, super fast and responsive now and it opens when you push on it and long press now works.
working. tnq
svprm said:
Can you try new system image? Because this image is created by unpacking ab123321's original image and packed with apk.
Click to expand...
Click to collapse
Same problem here. "adb install" yields:
Failed to install ...: Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE: Package couldn't be installed in /data/app/cyb.satheesh.homebutton-1: Package cyb.satheesh.homebutton has no signatures that match those in shared user android.uid.system; ignoring!]
adb push ...\HomeButton_v2.apk /system/app
adb: error: failed to copy '...\HomeButton_v2.apk' to '/system/app/HomeButton_v2.apk': couldn't create file: Read-only file system
(sorry for the newbie questions)
jreschke said:
Same problem here. "adb install" yields:
Failed to install ...: Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE: Package couldn't be installed in /data/app/cyb.satheesh.homebutton-1: Package cyb.satheesh.homebutton has no signatures that match those in shared user android.uid.system; ignoring!]
adb push ...\HomeButton_v2.apk /system/app
adb: error: failed to copy '...\HomeButton_v2.apk' to '/system/app/HomeButton_v2.apk': couldn't create file: Read-only file system
(sorry for the newbie questions)
Click to expand...
Click to collapse
Looks like you don't have permission to install it on /system.So you have to use system.img.
diabolik99 said:
How i install manual this program? i guess with minimal adb. i don't want to flash that file on my watch again. can someone do a tutorial? please!
Click to expand...
Click to collapse
If your watch is rooted and system can be mounted as RW, then you can follow the manual installation. But as of now, our AW 2.0 rom is using Squash filesystem. We can't mount system as RW in squash filesystem. So you have to flash this system.img over AW 2.0 rom to get this work.
svprm said:
If your watch is rooted and system can be mounted as RW, then you can follow the manual installation. But as of now, our AW 2.0 rom is using Squash filesystem. We can't mount system as RW in squash filesystem. So you have to flash this system.img over AW 2.0 rom to get this work.
Click to expand...
Click to collapse
Thanks for the explanation. I now installed just the new system image (without erasing anything), and rebooted (which only took little time). Home button is now there, thanks alot!
Flashed the img and it has been working great for over a week.
I experienced the same bootloop as the original aw 2.0 port, which was solved by following this guide: https://forum.xda-developers.com/g-watch/general/tutorial-avoid-bootloop-porting-wear-2-0-t3656825
So thought I would join in on this seeing as this community is all but dead, I have installed and this is the best thing ever to happen to this device. AW2 runs just fine on this device and adding this home button makes it a lot easier to bring up Google Assistant and the app drawer. This device is still perfect for reading off notifications or getting a quick weather update.
I really hope this community stays alive seeing as Android Oreo will be making its way to AW soon.
Thanks for the virtual home button, it's a must have.
Will the Dev continue to support this watch for wear Oreo?
brostar2017 said:
Will the Dev continue to support this watch for wear Oreo?
Click to expand...
Click to collapse
I don't know if there will be wear based on Oreo.
Hopefully I'm wrong.
The lenok2dory was port of Android Wear 2 for the G watch R, and it isn't getting Oreo.
Hi,my first post on this forum, already with a problem of booting Win11 image from partition created on Mi 8 (NTFS partition).
I was guided by those three sources :
1) Original project Renage installation guide:
Renegade Project
Renegade Project
renegade-project.org
BTW Xiaomi Mi 8 is on supported decives list: https://renegade-project.org/#/en/windows/state-frame.html
2) this yt wideo about installing Win 11 on Mi 8 (unfortunately, in Russian and the youtuber is showing some tips too fast, so I had to slow it down to 0.25 in some parts)
3) yt tutorial about installing Win 11 on OnePlus 6T
So, I have manage to remove and create userdata partition, I have eacreated smaller userdata partion with 30 GB instead of 100-ish something GB,
I have created also \pe partition for WinPE boot (works from UEFI boot), \win (formatted in NTFS) with about 70-something GB, and ESP partition in FAT32.
The UEFI Boot for Mi 8 (device code: dipper) is not installed on the device, I am booting it by flashing it via fastboot (single time, the normal boot image on the device is still genuine boot.img from Xiaomi).
So, just like in the beforementioned guides / tutorials, I am able to boot WinPe (part English, part Chinese), able to start DISM+, able to open prepared Win11 disk (tried either on whole image or n single .wim file) and then:
1) I am asked for choosing a disk to install Win11;
2) I choose \win parttion in NTFS
3) I see window titled 'Bootmgr Repair-UEFI' with a message: 'Boot Partition: None Click more to specify it manually
4) If I choose NTFS partition, I see windwos titled "Tips" with message "If you boot with UEFI, it needs a FAT16/ FAT32 partition
5) I choose ESP Partition https://www.diskpart.com/articles/efi-system-partition-4348.html, install it, then install drivers; enabling Enable Test-Signing mode and reboot device with shutdown -s -t 0
After installation I reboot application -> no UEFI boot so i go to fastboot mode (by combinatin of buttons) from my PC i flash uefi dipper img i choose pption with Windws Bootloader from UEFI boot option, I am waiting and after a lot of time i see that there was a problem with installation of Windows.
What I am doing wrong here? Any thoughts?
{
"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 know I'm late but I got past this point by running DISM++ on a computer instead of the device itself using mass storage mode described on https://wiki.renegade-project.cn/en/install. It was enabled for dipper in one of the RC of the uefi boot image.
I am however stuck at a blue screen where it just says my device ran into a problem and need to restart
@h9419 hi, sorry for being late, but I've manage to go further steps with help on the Renegade Forum:
Open config '\simpleinit.static.uefi.cfg' failed. Not found. Config: load failed. device: Mi 8 dipper
Hi folks, I have installed win10 on my Mi 8 with drivers, but when I try to boot I see only K letter in a blue circle logo and message: main:initialize simple imp Open config ‘simpleinit.static.uefi.cfg’ failed. Not found Config: load failed and I’m going back to boot menu Besides of that I...
forum.renegade-project.tech
However, I have stuck now with blue screen and error:
"Your PC/Device needs to be repaired
The operating system couldn t be loaded because the digital signature of a file or of its dependencies couldn’t be verified
File:
\Windows\System32\DriverStore\FileRepository\qcpil850.inf_arm64_51d4efc7c44baa30\qcpil.850.sys
Error code 0xc0000428
Press the Windows key for UEFI Firmware Settings"
I've received there some advice:"
If you flashed devcfg properly, you won’t get DRIVER_PNP_WATCHDOG anymore
If you successfully disabled testsigning and nointegritychecks using bcdedit, you won’t get 0xc0000428
Don’t use drivers from sdm845-drivers. They won’t work."
So I have checked testsigning and nointegritychecks using bcdedit:
Even after flashing fastboot flash devcfg_ab devcfg-dipper_FixTS.img
I still see “Open config ‘\simpleinit.static.uefi.cfg’ failed. Not found. Config: load failed”
DisableIntegrityChecks is set to True
and AllowPrereleaseSignatures also to True, but under BcdStore\Loaders\WindowsSetup
under {bootmgr} it’s only DisableIntegrityChecks, but without AllowPrereleaseSignatures
I’m a rookie regarding bcedit so I used Visual BCD Editor, should I add something in {bootmgr} or {bootloadersettings}? to the {bootloadersettings} I have no access from Visual BCD
obraz1035×475 149 KB
I see structure of this partition like this:
BTW via Mass Storage mode I have access to the esp partition stored here via Windows64 as I:\ and with Visual BCD editor I have an option to ‘repair bcd’ but I don’t know what this can done, so I don’t touch it
obraz851×486 71.3 KB
I am not sure if windows disk and BCD are connected here
obraz850×484 113 KB
@Vistulack I got it to work a few months ago after joining the telegram channel. My process is about as follows:
1. Dism++ clean install
2. Dism++ driver injection (I used dipper driver 1.1.1)
3. Dism++ disable
testsigning and nointegritychecks
4. Boot into fastboot to flash devcfg (re-flash it after every install, before trying to boot)
5. Flash boot image 1.1.1 (same version as driver) to recovery
6. Boot to recovery to boot windows, reboot to get android
Others have success with 2.0rc2 but I'm happy with 1.1.1. USB, cellular, wifi, Bluetooth screen brightness and touch screen works. Built in audio and accelerometer doesn't. USB C to 3.5mm DAC makes audio work and CH340 driver for Arduino knockoffs works.
Update:
thanks to @h9419 i have managed to succesfully install Win 11 on Mi 8
To sum up:
This time I have install drivers in ver. 1.1.1 https://github.com/edk2-porting/WOA-Drivers/releases/tag/v1.1.1
and after installation of dism I have used not only:
bcdedit /store Y:\efi\microsoft\boot\bcd /set {Default} testsigning on
bcdedit /store Y:\efi\microsoft\boot\bcd /set {Default} nointegritychecks on
but also :
bcdedit /store Y:\efi\microsoft\boot\bcd /set {Default} recoveryenabled no
Also I wouldn't recommend using Windows 10 home, as screen keyboard wasn't working there; I came across error:
C:\Windows\system32\osk.exe
A referal was returned from the server
This error wasn't seen on Windows 11 Pro
During install, I had also a problem with WiFi connections, but after putting mobile in the near of router I was able to connect (this issue camu up only during setting account)
Anyways, now I have other problem.
If I press turn off while charging, either from Windows or bootloader level, I end up back in bootloader menu, without knowing what is the battery level is (in Windows is still shows 0%, which is odd, because phone is still running).
Now I need to check how to enable turning phone off when charging (or put it into charging mode, with only battery level shown).
EDIT: ok, it looks like the best mode to charge the phone is setting it to recovery mode.
If anyone was interested with installing some old apps build on Net Framework 2.0 or 3.5, it looks like it will not work on arm64 architectue.
After installing one of such apps, I saw and error
The following feature couldn't be installed:
.NET Framework 3.5 (includes .NET 2.0 and 3.0)
The changes couldn't be completed. Please reboot your computer and try again.
Error code: 0x80240023
I have tried to fix it using advices from this video
and managed to formally 'install' Net 3.5 by script in PowerShell from sxs folder copied into TEMP folder but now the app is showing message:
"An error occurred:
System.NullReferenceException: Object not set to an instance of an object."
So it looks like it won't work (or maybe on some Virtual Machine build on arm64 for i.e Win Xp or Win7, but it maybe an overkill...)