These are the steps that worked for me to achieve root on the SM-X110 in the EU My original post on XDA: https://xdaforums.com/t/samsung-galaxy-tab-a9-8-7-sm-x110-sm-x115-etc-basic-root-guide.4672259/
CPU and Chipse is Mediatek Helio G99 (6nm) Octa-core (2x2.2 GHz Cortex-A76 & 6x2.0 GHz Cortex-A55)
PREP:

• Update Tablet as far as it will go
• Update Windows 10/11 software and drivers

PART 1 - TABLET

1. Boot tablet and go to settings -> about tablet -> software information -> tap on "build number" 5 times to enable developer options
2. Go back to settings and scroll down to new "developer settings" option at the very bottom.
3. Enable OEM unlocking and enable ADB debugging
4. Turn off tablet
5. When tablet is off, hold volume UP + DOWN whilst inserting the charging cable connected to your PC
6. Long press Volume up to enable device unlock
7. Device will reboot
8. Set up device again
9. Download and install Magisk onto tablet - https://github.com/topjohnwu/Magisk

PART 2 - WINDOWS PC

1. On a windows PC download the samsung USB drivers - https://developer.samsung.com/android-usb-driver
2. Ensure your PC can detect and mount the tablet
3. Download Patched Odin 1.13.1B Patched and install - https://xdaforums.com/t/patched-odin-3-13-1.3762572/
4. Download 7zip and install - https://7-zip.org/
5. Download LZ4 https://github.com/lz4/lz4/releases and extract to a folder named appropriately
6. Download firmware for your phone, I could only find the EUX firmware using BiFrost - https://github.com/zacharee/SamloaderKotlin - It will require you to input the Serial/IMEI number of your device to verify. This is a security feature implemented by Samsung in late 2023 I believe.
7. Extract the firmware file (using 7zip) resulting in 4 x files (AP, BL, CSC, HOME)
8. Click the AP file file and extract that (using 7zip)
9. From the newly extract files, copy and paste boot.img.lz4 and Vbmeta.img.lz4 into the folder you you extracted the LZ4 software to.
10. Drag and drop the boot.lz4 file into to the lz4.exe icon, it will create a boot.img file.
11. Copy and paste the boot.img.and Vbmeta.img file onto your Tablet (download folder usually)

PART 3 - BACK TO TABLET

1. Open Magisk App
2. Click install at the top
3. Navigate to the boot.img and Vbmeta.img file and select the boot.img file
4. Wait for the process to complete and a new patched .img file inside the same folder you opened the boot.img file from.
5. Copy and Paste the new patched file and Vbmeta back to Windows PC

PART 4 - BACK TO WINDOWS PC

1. Open 7zip and drag/drop the patched .img file in
2. Create a .tar archive usin the .img file using 7zip
3. After you get a new boot.tar, Drag the Vbmeta. img into boot.tar.
4. Since we can't use TWRP, we have to use Odin to flash the patched boot.tar
5. Launch Odin
6. On tablet hold Volume UP+DOWN and instert cable connected to PC
7. Odin should display "ADDED!". If not, re-install Samsung Drivers / Reboot PC.
8. In the AP section, select your patched boot.tar
9. If you are using the WiFI only mode, skip mounting the CP. If you have the 4G model, mount the CP from the originally extracted firmware download
10. Mount the BL and CSC from the originally extracted firmware download
11. Under "Options" in Odin, de-select "Auto Reboot"
12. Click "Start"

PART 5 - BACK TO TABLET

1. Press the Volume DOWN + Power button to exit Download
2. Immediately Press the Volume UP + Volume DOWN + Power buttons as soon as the screen goes off. This boots into recovery mode
3. Go to Wipe Data/Factory Reset and Select Yes to wipe data
4. Reboot phone
5. Magisk should now displayed that it's installed and you can now install modules.

Thanks, hope this helps!
suppressbotwarnings

Hi, I just received my Y700 2023 tablet CN version from AliExpress. Somehow, the seal was already broken when I opened it and the current software version is ZUI 15.0.654 (Stable version). I have not done any updating yet but the next version available is 15.0.774.
From reading XDA and other posts from forums such as Reddit, it seems the RSA instruction from the popular GigglehHD blog is slowly getting outdated due to updates and improvements of the RSA app or releases of new versions. For instance, some claim there is no need to unlock the bootloader and just proceed directly with RSA or cases where they followed the GiggleHD instruction but unable to relocked bootloader or unfortunately bricked their device.
TL;DR: So, has anyone recently succesfully flashed the official global ROM from ZUI 15.0.654 CN version through RSA, preferably as recent as late April or just this May? Kindly provide us your latest installation steps in the comments below. Thank you!
UPDATE: nvm, proceeded to install official global rom via RSA using broswer-translated GiggleHD instruction. Steps exactly the same and there is no need to prep anything beforehand such as tapping software version 7 times or unlocking bootloader as I read in other forums/blogs/comments.
This is how I did, so it may or may also work for you:
1) I downloaded RSA app on my Windows laptop using the link in GiggleHD blog. Downloading was quite slow and there might be a prompt to update afterwards to the latest version of RSA. Proceed to update and download the new RSA version.
2) Made sure I have the original CN software version and have not done any firmware update yet. You can see this in the settings > About tablet (just click exit if it is requesting permission to access the network to update firmware)
3) In addition, I deleted the majority of the CN apps first before turning off the wifi and turning off the device (just long press).
4) Back to RSA app, created an account then follow GiggleHD blog steps until the part to Continue with Software Update>OK>OK (until nothing to OK left and it's just waiting to plug the device in)
5) I used my data/charging cable (65W) with Type A to Type C ports for the next step. While pressing the volume up button, I plugged in the Type C port to the long-side port of the tablet (the extra port of Y700). Then I plugged the USB A of the cable into the laptop. Immediately after, there's a vibration which I then release the volume up button.
6) In the RSA app, the downloading progress is shown. It will take sometime to reach 100% while the tablet remains black/off.
7) Once it is 100% completed, there are some prompt sounds but I continue to do nothing and wait until the tablet reboots. The reboot page is basically Lenovo logo followed by choosing system language, wifi connecting and other Google installation stuff.
8) At this stage, I have decided to unplug the tablet from the laptop and then in the RSA app, proceeded to auto-delete downloaded firmware which it will then go back to the RSA Rescue page.
Yea that's all. Very easy. I have managed to download apps from Google Playstore and played a Prime Video movie. The only con so far is that there is more Google bloatware in this official global version than the CN version.

The context of this post is you flashed away your recovery and your system partitions. You're on Linux, like me, or you're on a version of Windows that has the drivers already installed. TWRP is currently not compatible with new firmware or anything beyond android 10 (please correct me if I'm wrong). Given that TWRP is out of date and hasn't been updated since 2022, we'll have to use adb and fastboot only. (If there are other tools from oneplus that make this easier please let me know).
Though I did write these, I did use chatgpt to write this with bullet points and fix any typos I had in my original instructions.

Steps to Successfully Install LineageOS on OnePlus 6T (Fajita)

Here is the detailed step-by-step process to install LineageOS on the OnePlus 6T, including all the commands you ran, in the order you did them. I'll also include notes about potential risks of bricking your phone.

Prerequisites

1. Ensure your phone's bootloader is unlocked.
2. Download the necessary files from the LineageOS website for OnePlus 6T (example):
   • lineage-21.0-20240514-nightly-fajita-signed.zip
   • boot.img
   • vbmeta.img
   • dtbo.img

Steps

1. Reboot into Fastboot Mode:
   • Turn off your phone.
   • Hold the Volume Up and Power buttons until the Fastboot screen appears (or get usb debugging and in the terminal type "adb reboot bootloader").
2. Flash vbmeta Image:
   • This step ensures that the verification of boot and recovery images is disabled, which is essential for custom ROMs.
   • fastboot flash vbmeta vbmeta.img
3. Flash dtbo Image:
   • Flashing the DTBO image updates the device tree overlays, which is necessary for hardware configuration.
   • fastboot flash dtbo dtbo.img
4. Flash the Boot Image to All Slots:
   • This installs the LineageOS recovery, replacing any existing recovery or boot image.fastboot flash --slot=all boot boot.img
5. Reboot into LineageOS Recovery from the fastboot menu or by typing fastboot reboot recovery:
   • After flashing the boot image, reboot into the new recovery mode.
   • fastboot reboot recovery
6. Sideload the LineageOS ROM:

• In the LineageOS recovery, select the option to sideload the ROM.
• On your computer, run the following command:
  adb sideload lineage-21.0-20240514-nightly-fajita-signed.zip
  

Don't worry about this error:

 serving: 'lineage-21.0-20240514-nightly-fajita-signed.zip' (~47%) adb: failed to read command: Success 

Note: The error adb: failed to read command: Success might appear, but if the percentage reaches near 47%, it typically means the process was successful.adb sideload lineage-21.0-20240514-nightly-fajita-signed.zip
Consider this a draft. If I learn more, I'll update this here, unless a mod removes this post for some reason, I'll just post this on another sub or make my own oneplus 6t sub.
edit:
Errors I was getting before. (This will help people who are searching for a solution)
Related, I used adb instead of fastboot for the image because of this error (might not be the exact error. This is reconstructed):

 fastboot flash system < waiting for any device > Sending sparse 'system_a' 1/4 (766924 KB) OKAY [ 19.030s] Writing 'system_a' OKAY [ 0.001s] Sending sparse 'system_a' 2/4 (786417 KB) FAILED (remote: 'Error: Last flash failed : Volume Full') fastboot: error: Command failedlineage-21.0-20240514-nightly-fajita-signed.zip 

For some unkown reason fastboot was giving me a Volume Full error, which wasn't an issue with adb sideload lineage-21.0-20240514-nightly-fajita-signed.zip
Also, here's what TWRP will give you if you're on any Android after 10:

 fastboot boot twrp-3.7.0_9-0-fajita.img Sending 'boot.img' (33116 KB) OKAY [ 1.010s] Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error') fastboot: error: Command failed 

So if you're getting this, you'll have to use the method at the start of this post.

For what it's worth, she's running Windows 11. I've upgraded the firmware and downloaded Brother software, and it has connected to her wifi setup.
I am quite certain that there's no jam, but just in case I re-seated the tray and the paper within the tray, and adjusted the sliders for the paper.
I also re-seated the toner, but the thing is it doesn't really feel 'secure', so I feel like that may be the issue. I found a video intended to show how to insert the toner, but it's for both my model and another model, and naturally they use the other model for the example, so I don't have a video of someone properly inserting toner into my specific model of this specific printer. Likewise, the manual and other documentation is for both my model and another model, and it always uses images of the other model.
Still, I am fairly sure that the toner is probably in the right position because when I remove the toner entirely, or place it less properly, the message switches to saying that there's no toner.
Any ideas?

I want to talk to you about something pretty cool called the General Loader within CE-4K (the user interface on the Legends 4KP). The General Loader allows running your own applications or those created by the community on the 4KP. These apps are made specifically for the 4KP and can do all sorts of things, like freeware/commercial games, tools, and more. As with any downloaded software, make sure that you install them from trusted sources, be aware of the potential for bad stuff, etc. I will not address specific use-cases or applications. I will only provide a few examples along with details on how to build/deploy them to the 4KP.
I've been working closely with the AtGames team to understand how all of this works as a community resource. About a month ago, I started documenting the basic steps involved. It's been quite the journey, but almost there! To make your own apps, you'll need a PC running Ubuntu. I created a guide a few months back showing how to install Ubuntu on your Windows PC in preparation for this project. You can check it out here: https://wagnerstechtalk.com/vms . It will be needed for this upcoming project!
As a little experiment, I used AI (thanks, ChatGPT!) to create a simple sample app. that bounces a ball on the main playfield display. This example will be provided in the upcoming General Loader guide. In addition, there is a more advanced example that was shared with me - a snake game that allows you to use the dPad or Arcade Control Panel to navigate a snake on the playfield. If you're curious what they look like at present, here is an unlisted video as a brief demonstration: https://youtu.be/IQ-_4WGoMhI
I'm hoping to have everything ready to share with you next week, but in the meantime, I'd love to hear what you think! Are you excited about diving into the world of the General Loader? Let me know your thoughts in the comments below!

I downloaded the Arch ISO onto a usb drive to do a bootable install, and successfully got arch on the second nvme drive following the steps on the wiki.
However when I went to install a bootloader, I ran into the problem where installing bootctl only saw my windows 10 installation and bios firmware options. I went through the steps again using the USB boot drive and installed GRUB, only for GRUB to recognize the Arch linux install and the firmware option and not the windows 10 installation.
I since went back to using bootctl since I still need my windows 10 environment and am not sure how to get the situation working correctly. This is on my primary/only computer, so responding to questions about what the results of things are might be untimely.
It doesn't matter to me whether I use GRUB or bootctl, but I would prefer to get a working situation out of this.

First off I am a NOOB and I have decided that I have no idea what I'm doing.
I have a Logitech X-56 that I want to use with MSFS. I have it setup to the default settings and everything seems to work except I get a lot of drift when stick is in the neutral position. I would also like to change the sensitivity.
I read many articles and post and youtube videos on the subject (most were over 2 years old) and not I'm completly confused.
Some say I need to download software from Logitech. I cannot find that anywhere.
Some said I need to calibrate it through Windows (I'm using Windown 11). I can see the controlers in Device Manager and it seems to be ok. On the Logitech site it says to use the HUD software to calibrate and I cannot find that software anywhere. https://support.logi.com/hc/en-us/articles/360023176974-Recalibrate-the-X56-H-O-T-A-S-Axes-Firmware
So now I'm loss. I understand it's me and I have no intention of giving up but it's not a good interduction to Flight Sims. Can someone please put me back on track. Please treat me like a beginer.

This is slightly embarrassing to ask as I work in technology helpdesk but I'm running out of ideas at this point.
I noticed this issue with my T470s where it's not displaying on a secondary monitor. I've tested with a Dell docking station, Anker 6-in-1 dongle and recently a Belkin adapter (USB-C/HDMI charging compatible dongle). Even the intergrated HDMI port isn't displaying. It's unknown if it worked before as I only recently starting attempting to use an external screen with this laptop. Type-C port is able to charge the device, read external storage, and peripherals.
Note this is a refurbished T470s I bought last summer.
I've done the following:

1. Downloaded Lenovo System Update
2. Manually installed Generic DisplayLink Driver
3. Ran Windows update
4. Uninstalled the display driver
5. Installed TB Software setup and TB firmware update
6. Made sure Thunderbolt 3 was enabled in BIOS.

These are the steps that worked for me to achieve root on the SM-X110 in the EU My original post on XDA: https://xdaforums.com/t/samsung-galaxy-tab-a9-8-7-sm-x110-sm-x115-etc-basic-root-guide.4672259/
PREP: - Update Tablet as far as it will go - Update Windows 10/11 software and drivers
PART 1 - TABLET 1. Boot tablet and go to settings -> about tablet -> software information -> tap on "build number" 5 times to enable developer options 2. Go back to settings and scroll down to new "developer settings" option at the very bottom. 3. Enable OEM unlocking and enable ADB debugging 4. Turn off tablet 5. When tablet is off, hold volume UP + DOWN whilst inserting the charging cable connected to your PC 6. Long press Volume up to enable device unlock 7. Device will reboot 8. Set up device again 9. Download and install Magisk onto tablet - https://github.com/topjohnwu/Magisk
PART 2 - WINDOWS PC 1. On a windows PC download the samsung USB drivers - https://developer.samsung.com/android-usb-driver 2. Ensure your PC can detect and mount the tablet 3. Download Patched Odin 1.13.1B Patched and install - https://xdaforums.com/t/patched-odin-3-13-1.3762572/ 4. Download 7zip and install - https://7-zip.org/ 5. Download LZ4 https://github.com/lz4/lz4/releases and extract to a folder named appropriately 6. Download firmware for your phone, I could only find the EUX firmware using BiFrost - https://github.com/zacharee/SamloaderKotlin - It will require you to input the Serial/IMEI number of your device to verify. This is a security feature implemented by Samsung in late 2023 I believe. 7. Extract the firmware file (using 7zip) resulting in 4 x files (AP, BL, CSC, HOME) 8. Click the AP file file and extract that (using 7zip) 9. From the newly extract files, copy and paste boot.img.lz4 and Vbmeta.img.lz4 into the folder you you extracted the LZ4 software to. 10. Drag and drop the boot.lz4 file into to the lz4.exe icon, it will create a boot.img file. 11. Copy and paste the boot.img.and Vbmeta.img file onto your Tablet (download folder usually)
PART 3 - BACK TO TABLET 1. Open Magisk App 2. Click install at the top 3. Navigate to the boot.img and Vbmeta.img file and select the boot.img file 4. Wait for the process to complete and a new patched .img file inside the same folder you opened the boot.img file from. 5. Copy and Paste the new patched file and Vbmeta back to Windows PC
PART 4 - BACK TO WINDOWS PC 1. Open 7zip and drag/drop the patched .img file in 2. Create a .tar archive usin the .img file using 7zip 3. After you get a new boot.tar, Drag the Vbmeta. img into boot.tar. 4. Since we can't use TWRP, we have to use Odin to flash the patched boot.tar 5. Launch Odin 6. On tablet hold Volume UP+DOWN and instert cable connected to PC 7. Odin should display "ADDED!". If not, re-install Samsung Drivers / Reboot PC. 8. In the AP section, select your patched boot.tar 9. If you are using the WiFI only mode, skip mounting the CP. If you have the 4G model, mount the CP from the originally extracted firmware download 10. Mount the BL and CSC from the originally extracted firmware download 11. Under "Options" in Odin, de-select "Auto Reboot" 12. Click "Start"
PART 5 - BACK TO TABLET 1. Press the Volume DOWN + Power button to exit Download 2. Immediately Press the Volume UP + Volume DOWN + Power buttons as soon as the screen goes off. This boots into recovery mode 3. Go to Wipe Data/Factory Reset and Select Yes to wipe data 4. Reboot phone 5. Magisk should now displayed that it's installed and you can now install modules.
Thanks, hope this helps!

Hey all,
I just bought a Maxwell (PS version) for my PC but can't seem to be able to get any sound from my pc to the headphones. I have already downloaded Audeze HQ and updated the drivers on both usb dongle and headset.
My issue is that when connecting directly with the USB connection or using the dongle, Audeze HQ shows that the headphones are connected but no new output audio peripheral appears anywhere on Windows. I can actually control the sound level using the Volume wheel, whatever audio peripheral is selected, so Windows definitely detects this, but apparently not as an audio peripheral and I get no sound.
It works when connected using the AUX connection but I'd like to get it working with the dongle.
Anyone got ideas on potential fixes or things to try?
EDIT: So turns out I found "Chat - Audeze Maxwell" and "Game - Audeze Maxwell" in Device Manager, but they appear in "Other Peripherals" and show up as unknown peripherals with no driver installed, but Audeze HQ confirms that the latest firmware is installed. Help!

Well some of us have ordered the overpriced D-R35 plus, me included. The right decision would be to cancel orders, but some of us are too curious and want to hack the device, making homebrew and custom firmwares possible.
Nihon777 had some success in the comments of https://www.youtube.com/watch?v=nsBpHsMNG2Q
There is a init file in the retro folder, which is a simple shell script. When something is inserted after the "modprobe joydev" line, it gets executed, simple.
And it vaguely revealed the CPU and the amount of memory:
Single Core Cortexc-A7 + 64MB
processor : 0
model name : ARMv7 Processor rev 5 (v7l)
BogoMIPS : 2.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 5
Hardware : GPA7XXXA Device Tree
Revision : 0000
Serial : 0000000000000000
MemTotal: 43120 kB
MemFree: 24232 kB
MemAvailable: 23988 kB
Buffers: 124 kB
Cached: 9540 kB
GPA7740A? ARM Cortex-A7 660MHz w/ NEON, FPU, L1: 32KB/32KB L2: 128KB, 470KB internal RAM, DDR2 64MB, 3D GPU OpenGL ES2.0, OpenVG 1.1

Cross-compiled binary as main replacement did not work, but in folder retro there is the "init" file, you can insert a few lines after "modprobe joydev" and the rest. E.g. "cat /proc/cpuinfo > /usretro/info.txt" will write the cpuinfo into the retro folder after next start. "cat /proc/meminfo > /usretro/info2.txt" etc. I am using notepad++ which leaves the line endings intact (different between linux and windows). And don't forget to make an image from the original card, just in case.
Very minimal linux, just busybox. What a pity, could be a great device with second core and more than 64mb ram. It has half as much ram as SF2000 and the cpu is just on par. Dunno if it is the GeneralPlus 660 Mhz one overclocked to 800 mhz (no clock info) or maybe V.R.T. used the GeneralPlus Cortex-A7 and 2D accelerator stuff on their VT-569 which is assumed to have legacy V.R.T. famiclone technology. The linux seems to use direct framebuffer output, at least during startup. GPA7XXXA Device Tree is is used accordin g to cpuinfo and there only is GPA7740A out. BTW, there is an SDK for that chip that can be downloaded.
Question is if it really is the GeneralPlus. There is info under /proc/device-tree, eg /proc/device-tree/model, returns GeneralPlus EMU Board or something like that. Also somewhere under /proc/device-tree there is a gpu. So yes, you are right, it should be the GeneralPlus one with GPU. There is a datasheet for the GPA7740A stating 3D GPU OpenGL ES 2.0, OpenVG 1.1, 22 Mtriangle/s, 112Mpixel/s. Wonder if the GPDLAv2 "deep learning accelerator" is also onboard. I think yes, probably that is just some kind of dsp or something like that, could accelerate some stuff. Programmable system PLL frequency from 216 Mhz to 1188 Mhz. Who knows, maybe they just clock the chip very high for PSX? Lots of 2D acceleration features too. Yoshis Island running very nicely, Kirby 3 not starting.
There is a newebetter one I think not listed yet on their homepage, but that one seems to be available only in BGA format and not QFP. The [V.R.Technology](javascript:void(0);) VT-569 is rumoured to be compatible with VT03/VT369 and those are famiclone chip compatible (nes on a chip). A single link on the web, nothing more.
I have the cpu clock: cat /sys/devices/system/cpu/cpu0/of_node/clock-frequency > /usretro/info1.txt hexedit of info1.txt shows: 27B25A80, convert to decimal: 666,000,000 = 666 Mhz, so it really seems to be the GeneralPlus chip where we know we can set the cpu clock from 216 Mhz up to 1188 Mhz. It has 1 core less than the Miyoo Mini, 64MB versus 128MB Ram but a 2.5 D graphics accelerator (comparable or better than the Sigmastar 2D accelerator the Miyoo Mini has) AND a 3D GPU. Also GeneralPlus has tech demos on youtube, they seem to be able to make a lot of things happen with minimum cpu clock.
GPU is not visible from within linux, you have to load the kernel modules like in /gpu_[env.sh](javascript:void(0);). It is a Vivante, possibly GC Nano + GC320. I suspect there might be an additional Cortex-M, would show up ad remoteproc, but I do not know how to setup. Next steps would be getting a remote terminal via getty on ttyUSB with a crossover usb nullmodem cable.

I suspected it would be similar to those "Gamestick Lite 4K" devices, because the sdcard layout is very similar what I have seen.
If, big IF, the prices would go down to SF2000 levels, it would be a nice device, I like the controls and the haptic is not too shabby.

Hello everyone,
Two years ago, I bricked my laptop BIOS because of force-removing the battery and AC adapter during BIOS update, then I bought the CH341A SPI programmer to reflash it myself, using the correct firmware for the laptop model downloaded from the official ASUS website, and the laptop went back to life. Because I had no plan to hackintosh the laptop at that time, I didn’t aware of how important the Intel Management Engine Interface is. Now, I have plan to hackintosh it, and in order to make the QE/CI hardware acceleration work, I have to bring back the Intel ME. But, when I checked it through the Windows Device Manager, the Intel ME was missing.
Few days later, I planned to clear the ME region of the firmware before flashing it using the same chip programming device, and the ME also finally brought back yesterday. But the onboard ethernet adapter had a little bit malfunction. It’s detected in Device Manager, like there’s no problem at all, but it won’t recognize the LAN cable at all. Reflashed again with the previous firmware without Intel ME, the ethernet LAN cable worked again.
So, the most important thing is: I want to make both Intel ME and the Ethernet fully working like before the brick that happened two years ago. Anyone has the solution?
Note: I also don't forget to clear the CMOS every after reflashing.
Motherboard and BIOS details: Asus X450C Laptop Intel Core i3-3217u AMIBIOS Aptio version: earlier than V Chip: Winbond 25Q64FVSIG ME version: 8.1.2.1318
The original downloaded firmware (without clearing the Intel ME)
The firmware with Intel ME cleared (but the Ethernet has problem)

After a few frustrating weeks of trying to upgrade my Creative Zen Micro to 128gb, I finally succeeded on upgrading it. Here is a step by step.

With a Virtual Machine

Given that the software part can get very frustrating, I suggest that you first focus on creating a working environment based on your stock mp3 player. This will limit the number of things that can go wrong.
This was tested on a Windows 11 machine (called Host from now on).
Download Virtualbox. Use your own Windows XP SP2 image or find one (google: archive + WinXPProSP2ENG). Download the Windows Media Player 10 updater from here Download the Creative Zen Micro drivers and upgraders from here
Install Virtualbox. Install Windows XP on Virtualbox - this can be a big step if you don't have much experience in this field, but there are plenty of tutorials on how to do it - check the references below.
Now that you have your Windows XP VM (called Guest from now on) up and running, go to the Devices tab on the top of your screen and click on "Insert guest additions CD...". This will insert a virtual CD containing some Virtualbox drivers and you'll get a pop up on your Guest machine. Install them and reboot your machine.
Turn off your Guest machine.
Connect the Zen Micro to your Host machine. Your Host machine should recognize the player with no trouble.
In Virtualbox, click on your VM machine and go to settings > USB > USB2.0 > click on the 'plus' sign and add your device there. The name should be "Creative...".
Now, in the same settings menu, go to the tab "shared folders" and click on "add". Now, choose the folder you want to share between the Host and the Guest machines. Give it a name and a mount point. I picked "sharewithxp" for all the fields, including the name of the directory on Host. Check 'auto-mount' and 'make permanent' (if it exists).
On your Host machine, copy the files MP10Setup.exe, ZenMicroPDE_PCFW_LB_1_11_01.exe and JB3MV2_PCWDRV_US_2_01_00.EXE to the shared directory you just created. Also copy MP10Setup.exe.
Turn on your Guest machine and go to "My Computer". You should see your shared folder in there. Copy all the files from there to your Guest's desktop.
Install MP10Setup.exe - this upgrades the Windows Media Player from 9 to 10. By experience, Windows Media Player 11 was problematic and apparently 9 isn't ok either. Stick to WMP 10. This was key for me. It really didn't work without WMP10.
Install JB3MV2_PCWDRV_US_2_01_00.EXE - these are the drivers for the Zen Micro.
Disconnect your Zen Micro from your computer. Connect it again. Go to devices > usb on the top menu and make sure your device is selected.
Execute ZenMicroPDE_PCFW_LB_1_11_01.exe If everything went according to plan you should now see an "Upgrade" button. If you see said button - congratulations because this was the most painful part of the process. I realized that when the device is correctly loaded, the executable won't open right away - It takes a few seconds. If the device wasn't fully recognized, you'll see a message saying "Your player is not connected, please connect your player".
(If you got the dreadful second message and no "upgrade" button, try to reboot your Guest machine. Disconnect and connect your player again. Make sure it appears on the devices menu.)
Now that you have a working environment, let's move to the fun part.
Format your micro sd card (fat32 if I'm not mistaken) - I used a Sandisk Extreme 128gb (the golden ones) and it worked fine. Insert the micro sd on your CF-to-SD adapter. I got the the only adapter I could find (red one).
Disassemble your Zen Micro - there are tutorials and videos around that show you how to do it better than I possible could - check the references below.
Remove the CF card from the mp3 player and insert the adapter. Pay attention to the position of the old CF card. CF cards don’t have a big distinguishable difference on one side like sd cards do. It's really easy to get mistaken and connect it on the wrong side. The only differences are the slots/openings on both sides of the CF card/adapter - one is larger than the other. When the adapter is connected and in place, its label should be visible (pointing upwards). Take a picture of the original CF card if needed or check the video in the references below.
Assemble everything back but do not insert the battery right away.
Toggle the power button to the left and hold it that position. Insert the battery. You should now be in recovery mode. Navigate to "format all" and click ok. Navigate to "reboot" and click ok.
Connect your player to the computer and, in the Guest machine, make sure it is selected on the devices > usb menu.
Open ZenMicroPDE_PCFW_LB_1_11_01.exe If everything went according to plan, the upgrade button should now be visible. Click. Wait. Enjoy.
[I also tried upgrading to ZenMicroP4S_PCFW_L16_2_21_02.exe and it worked just fine. However, I realized the player needs to reboot 2-3 times and when it did, it lost connection with the machine, so I had to disconnect the cable and connect it back again and it was picked up. If it doesn't, check if it is still selected on the devices>usb menu and try again.]
PS: Inside the Creative Zen Micro link, there are also 2 older drivers in there - I didn't test them.
References: https://www.reddit.com/ipod/comments/18e1698/creative_zen_micro_upgraded_from_5gb_hdd_to_a/ https://www.instructables.com/Upgrade-the-Zen-Micro-5gb-to-8gb-on-the-Cheap/ www.youtube.com/watch?v=VERkcCTJFyI https://www.intowindows.com/how-to-boot-and-install-from-iso-in-virtualbox/

Without a VM (native Windows XP running on a modern computer)

^Soon.

I know this is an iPod subreddit, but it's the most active subreddit dedicated to mp3 players (I think). I know there are some fans of these players around here but let me know if you want this gone though.
After a few frustrating weeks of trying to upgrade my Creative Zen Micro to 128gb, I finally succeeded on upgrading it. Here is a step by step.

With a Virtual Machine

Given that the software part can get very frustrating, I suggest that you first focus on creating a working environment based on your stock mp3 player. This will limit the number of things that can go wrong.
This was tested on a Windows 11 machine (called Host from now on).
Download Virtualbox. Use your own Windows XP SP2 image or find one (google: archive + WinXPProSP2ENG). Download the Windows Media Player 10 updater from here Download the Creative Zen Micro drivers and upgraders from here
Install Virtualbox. Install Windows XP on Virtualbox - this can be a big step if you don't have much experience in this field, but there are plenty of tutorials on how to do it - check the references below.
Now that you have your Windows XP VM (called Guest from now on) up and running, go to the Devices tab on the top of your screen and click on "Insert guest additions CD...". This will insert a virtual CD containing some Virtualbox drivers and you'll get a pop up on your Guest machine. Install them and reboot your machine.
Turn off your Guest machine.
Connect the Zen Micro to your Host machine. Your Host machine should recognize the player with no trouble.
In Virtualbox, click on your VM machine and go to settings > USB > USB2.0 > click on the 'plus' sign and add your device there. The name should be "Creative...".
Now, in the same settings menu, go to the tab "shared folders" and click on "add". Now, choose the folder you want to share between the Host and the Guest machines. Give it a name and a mount point. I picked "sharewithxp" for all the fields, including the name of the directory on Host. Check 'auto-mount' and 'make permanent' (if it exists).
On your Host machine, copy the files MP10Setup.exe, ZenMicroPDE_PCFW_LB_1_11_01.exe and JB3MV2_PCWDRV_US_2_01_00.EXE to the shared directory you just created. Also copy MP10Setup.exe.
Turn on your Guest machine and go to "My Computer". You should see your shared folder in there. Copy all the files from there to your Guest's desktop.
Install MP10Setup.exe - this upgrades the Windows Media Player from 9 to 10. By experience, Windows Media Player 11 was problematic and apparently 9 isn't ok either. Stick to WMP 10. This was key for me. It really didn't work without WMP10.
Install JB3MV2_PCWDRV_US_2_01_00.EXE - these are the drivers for the Zen Micro.
Disconnect your Zen Micro from your computer. Connect it again. Go to devices > usb on the top menu and make sure your device is selected.
Execute ZenMicroPDE_PCFW_LB_1_11_01.exe If everything went according to plan you should now see an "Upgrade" button. If you see said button - congratulations because this was the most painful part of the process. I realized that when the device is correctly loaded, the executable won't open right away - It takes a few seconds. If the device wasn't fully recognized, you'll see a message saying "Your player is not connected, please connect your player".
(If you got the dreadful second message and no "upgrade" button, try to reboot your Guest machine. Disconnect and connect your player again. Make sure it appears on the devices menu.)
Now that you have a working environment, let's move to the fun part.
Format your micro sd card (fat32 if I'm not mistaken) - I used a Sandisk Extreme 128gb (the golden ones) and it worked fine. Insert the micro sd on your CF-to-SD adapter. I got the the only adapter I could find (red one).
Disassemble your Zen Micro - there are tutorials and videos around that show you how to do it better than I possible could - check the references below.
Remove the CF card from the mp3 player and insert the adapter. Pay attention to the position of the old CF card. CF cards don’t have a big distinguishable difference on one side like sd cards do. It's really easy to get mistaken and connect it on the wrong side. The only differences are the slots/openings on both sides of the CF card/adapter - one is larger than the other. When the adapter is connected and in place, its label should be visible (pointing upwards). Take a picture of the original CF card if needed or check the video in the references below.
Assemble everything back but do not insert the battery right away.
Toggle the power button to the left and hold it that position. Insert the battery. You should now be in recovery mode. Navigate to "format all" and click ok. Navigate to "reboot" and click ok.
Connect your player to the computer and, in the Guest machine, make sure it is selected on the devices > usb menu.
Open ZenMicroPDE_PCFW_LB_1_11_01.exe If everything went according to plan, the upgrade button should now be visible. Click. Wait. Enjoy.
[I also tried upgrading to ZenMicroP4S_PCFW_L16_2_21_02.exe and it worked just fine. However, I realized the player needs to reboot 2-3 times and when it did, it lost connection with the machine, so I had to disconnect the cable and connect it back again and it was picked up. If it doesn't, check if it is still selected on the devices>usb menu and try again.]
PS: Inside the Creative Zen Micro link, there are also 2 older drivers in there - I didn't test them.
References: https://www.reddit.com/ipod/comments/18e1698/creative_zen_micro_upgraded_from_5gb_hdd_to_a/ https://www.instructables.com/Upgrade-the-Zen-Micro-5gb-to-8gb-on-the-Cheap/ www.youtube.com/watch?v=VERkcCTJFyI https://www.intowindows.com/how-to-boot-and-install-from-iso-in-virtualbox/

Without a VM (native Windows XP running on a modern computer)

^Soon.

Has anybody experienced with this problem? I downloaded F03 firmware and attempted to install it after using the supplied USB upstream cable, but the program doesn't discover the monitor no matter what.
I tried switching to another upstream cable laying around the house (probably for a printer or scanner), but still a no-go.
Also, should Windows makes a notification sound when you connect USB cable to PC? When I connected the system just stays silent. Almost like the port doesn't work.

I have a drunkdeer g65 that I got at the beginning of the year, and it's been amazing so far, but recently when I got a PC from Gumtree (similar to Facebook marketplace) my keyboard has been rendomly pressing the "u" key, this didn't start happening until today, so id already had had the PC for a few days, problem free! I've tried older firmware, I've tried the newest firmware, ive tried updating my computer, and btw the PC was a fresh install of windows 11, no setup had been completed so that rules out viruses or malware, I've also tried numerous different USB ports, nothing changed, but then when I switched the keyboard over to my laptop it worked again, oh and i havnt modded the keyboard at all or downloaded 3rd party drivers, nothing of the sort, any ideas?

Hi,
I have a problem with the scroll of the mouse HyperX Haste 2 (wired, less than a month of use). I notice small jumps while scrolling, but only in some situations, like at the end of a web page, windows terminal, or randomly when I start scrolling a web page. The scroll don't jump when I'm the middle of the page, never, long or short. The easier way to reproduce is using the scroll on the tab bar of Notepad++ when I have lots of tabs open. I keep the mouse pointer over the tab bar and keep scrolling, I see the tab bar going left and right randomly. Also, testing the mouse with another PC, menu of Call of Duty MW3 (2023) jumps non stop while I scroll down. I fixed my problem downgrading the firmware from 1.1.0.8 to 1.1.0.6, downloaded from official website. Then I tried to set my DPI settings and led color, but the software updated the firmware again to 1.1.0.8. Tested again, the scroll issue was there, I downgraded again to 1.1.0.6 and left the dpi at defaults, scroll issue gone, no more problems.