yashsingh1/xdaforums huggingface dataset:
[Google Home] octathorp:
I'm not aware about how device management and FRP works on assistant devices, but maybe there is something still linked with the Google account you have set on device previously, and the process trying to read credentials is crashing due to the open bootloader or unlocked AVB.

Try to factory reset device from recovery (the "No command" screen), but if its something effectively related to FRP nothing will change.

Maybe, as a last resort option you could restore the mtkclient backup and then make a factory reset from Settings menu on the Assistant interface. That will for sure wipe FRP or any related partition. Then install the LOS system again.

But if you had not a linked Google account on the device prior to this process, I am running out of ideas...
[Google Home] Ierlanfdan:
Try to factory reset device from recovery (the "No command" screen), but if its something effectively related to FRP nothing will change. Worked.

Now I am trying to setup it up as a smart clock (Google Assitant/Google Home like stock but with the option to develop. It's just a launcher so shouldn't be a big problem.
[Google Home] gabrl12345678900:
Hi

I have a problem, when i try to connect my smart clock to Mtkclient it reads all the information about the device and then this appears:

DAXFlash - Reconnecting to stage2 with higher speed

and after this, it crashes...

what should i do?
[Google Home] theubusu:
I had the same issue as you. I used Linux instead of windows and it worked fine, so try doing it on Linux.
[Google Home] gabrl12345678900:
Oh ok

I hate my life :cry:
[Google Home] gabrl12345678900:
hey, i have another problem

When i try to flash on fastboot mode my PC doesn't see the device, it sees the device as an unknown android

what should i do?

Problem solved using Linux
[Google Home] SjorsMaster:
Tried it myself, if you run into issues with windows it seems like the android driver isn't set up properly in device manager (marked with a tiny ⚠️)

I tried running Gapps but it looks like 1gb of ram really isn't going to cut it, do we possibly have a way to flash a lighter weight version of android? (ran Gapps through magisk)

A bit of feedback on the guide, the section where it's stated you have to tap mute and + a couple of times on the no command screen, all you really need to do is hold mute and tap + to cycle through the screens. this makes it way less frustrating and a lot more reliable

thanks

edit: attempting to install microG instead to see how it handles that instead
[Google Home] octathorp:
I will modify the guide with your suggestion about buttons on recovery, thank you!

I have tried to install GApps even on lower Android versions (10, 11), but at the end the result is a extremely slow and laggy device. RAM is not enough to run the memory-hungry Google services, so it's simply something I accepted as is.

You could try with microG, as tricky as the installation process is, but if you only need Play Store, maybe you could try Aurora Store (I have not tested it on this, but I use it on other devices).

I have a similar device to this (Alcatel 5033D, similar MTK processor, same 1GB RAM) with Google Apps and it's not usable at all, but removing them makes the device run a lot smoother, so with this experience I have no hope on this device neither.
[Google Home] nguyenbangdoshome:
I Just need to convert My Xiaomi Smart Clock Chines Version(lx04) into Global version (x04g). Can you show me the way. And can I use google assitant after convert it to global version?
[Google Home] alpha002:
please help me, the mtk client cant detect my mi smart clock, i am on kali linux x64, MTKClient - Version 2.0,am I doing something wrong ?; this is what i do:

─$ python mtk_gui

press the (+) button on the smart clock

the connect it to the laptop

where is the issue why it don't recognize it ?

please help me i really want to install android on it,
[Google Home] edepalos:
Hi!

Actually You need to press the + and - buttons simultaneously! I had this issue also...

Did you manage to solve this issue? I have the same problem and no sound at all....
[Google Home] alpha002:
it says "Aucune commande" wich means somthing like no commande, what i am supposed to do now ?
[Google Home] edepalos:
You have probably pressed the MUTE button too... only +&- needs to be pressed and held down...
[Google Home] alpha002:
no i only press the + and - buttons and it says "Aucune commande", i dont think i have a LX04
[Google Home] alpha002:
i've red somewhere that i need to patch my kernel or somthing like that, is that necessery ? will this fix it ? or it has nothing to do with it, and if it does how to patch my kali linux kernel ?
[Google Home] alpha002:
so i did as you said and it show : "Aucune commande" but then if i press the mute button and volume up, it goes to Android Recovery mode

Xiaomi/micro_x04g/micro_x04g

soo is this good ? is it a step forward ?
[Google Home] Longshinsjohnson:
This is awesome! Massive props to @octathorp - after posting the original thread and checking in occasionally, and not finding any progress, I just thought this device would be stuck as-is forever... I randomly searched for it again this week and boom, here we are!

I've successfully flashed your LineageOS image and yep, works great. It's made me wonder though, would it be possible to take the stock image and just tweak it? I don't actually need much more from this little clock - it'd be neat to cast video to it, or to install a launcher and a couple of apps on it for when you might want something more, but 90% of my use case is covered by stock and I'm looking at a mountain of effort to get back to where I started with a custom ROM underpinning it. So, how easy would it be to inject USB debugging for ADB access, for instance? Like, that is really all I think I need from the little guy 😁
[Google Home] Longshinsjohnson:
You'll want to check your USB cable I think -- before trying any custom stuff, just plug your regular USB cable in to the clock and your computer and see if the device shows up as a phone on your desktop. I'm on Xubuntu and it appears, unmounted, as a phone.

If it doesn't appear, in the terminal type lsusb to list out all your USB connected devices. There will be at least one entry for everything USB connected on your system -- you're looking for an entry that starts "MediaTek Inc.".

If you try both of these and you see nothing, use a different USB cable, you might have one that is charge only and doesn't have the data lines terminated.
[Google Home] Longshinsjohnson:
Not being super experienced with custom roms, i tried injecting the latest android system webview APK (in case the disabled downloading is something to do with the specific build that's on the stock rom) as well as a simple keyboard apk in the system apps... Unfortunately both apks just crash, I'm missing something obvious I expect!
[Google Home] markomiki:
Can tou help me install it
[Google Home] XiChar:
@octathorp how did you remap the mute button to act as a power button? Is it possible to revert this? I'd like to use the button for activating tasker tasks, but the usual remapping apps can't remap the power button and I couldn't get Xposed to work.
[Google Home] octathorp:
You need to edit Generic.kl file under /vendor/usr/keylayout folder to set a different function for power button.
[Google Home] XiChar:
Thank you, that worked perfectly.
[Google Home] theubusu:
There's a guide linked in the main post. https://github.com/octathorp/x04g_tools/blob/master/howtos/FlashCustomImages.md
[Google Home] markomiki:
Thanks
[Google Home] kipjr:
Hi, thanks for the great guide however I'm stuck at the following... how can this be fixed?

python mtk da seccfg unlock

.....Preloader - CPU: MT8167/MT8516/MT8362()
Preloader - HW version: 0x0
Preloader - WDT: 0x10007000
Preloader - Uart: 0x11005000
Preloader - Brom payload addr: 0x100a00
Preloader - DA payload addr: 0x201000
Preloader - CQ_DMA addr: 0x10212c00
Preloader - Var1: 0xcc
Preloader - Disabling Watchdog...
Preloader - HW code: 0x8167
Preloader - Target config: 0xe5
Preloader - SBC enabled: True
Preloader - SLA enabled: False
Preloader - DAA enabled: True
Preloader - SWJTAG enabled: True
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: True
Preloader - Mem write auth: True
Preloader - Cmd 0xC8 blocked: True
Preloader - Get Target info
Preloader - BROM mode detected.
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xcb00
Preloader - SW Ver: 0x1
Preloader - ME_ID: XXXXXXXXXXXXXXXXXXXXXXXXXXXX
Preloader - SOC_ID: 0000000000000000000000000000000000000000000000000000000000000000
Preloader - Jumping to 0x200000
Preloader - Jumping to 0x200000: ok.
DeviceClass - [Errno 19] No such device (it may have been disconnected)
sej - HACC init
sej
sej - [LIB]: SEJ Legacy Hardware seems not to be configured correctly. Results may be wrong.
sej - HACC run
sej
sej - [LIB]: SEJ Hardware seems not to be configured correctly. Results may be wrong.
sej
sej - [LIB]: SEJ Hardware seems not to be configured correctly. Results may be wrong.
sej - HACC terminate
sej - HACC init
sej
sej - [LIB]: SEJ Hardware seems not to be configured correctly. Results may be wrong.
sej
sej - [LIB]: SEJ Hardware seems not to be configured correctly. Results may be wrong.
sej
sej - [LIB]: SEJ Hardware seems not to be configured correctly. Results may be wrong.
sej - HACC run
sej
sej - [LIB]: SEJ Hardware seems not to be configured correctly. Results may be wrong.
sej
sej - [LIB]: SEJ Hardware seems not to be configured correctly. Results may be wrong.
sej - HACC terminate
None
[Google Home] AfonsoOnXDA:
Having the same issue.
[Google Home] OctoNezd:
Did anyone try other firmwares, like previous versions of lineageos? Boot for me is slow as all hell on LOS20 from post, pinned super.img gets stuck on whitebox on screen for a very long time, with nothing in adb. Cant get adb shell or adb logcat to display anything when its on screen.
[Google Home] OctoNezd:
Looking at logs there are a few OOMs before that, and a lot of this:

01-06 21:14:25.408 852 858 E IMGSRV : PVRSRVAllocSparseDeviceMemMIW2:405: PVRSRVMapToDevice fail (82)
[Google Home] kr1v:
Hi guys! I've recently also managed to find the send feedback thing, and I've managed to log in to my google account on the default os (no custom firmware shenanigans) by copying the @ from YouTubes comments and manually copying and pasting every letter, and inputted my case sensitive password somehow in the same way in the email box, and then using cut to copy and remove it and then paste into the password box (this was a hell)

This way I was able to watch YouTube at a decent refresh rate and quality, with my personal recommendations. This also revealed the devices name, that being X04G. I was able to see this trough the email I got from Google saying blah blah new login blah blah

With that out of the way I wanted to say that you can use your search history to go to links, and even have the alphabet or something in your search history so you can just "type" normally

I wanted to try stuff like this because I couldn't sleep, but also because I knew it was a backbone android because when using Spotify just normally it randomly crashes, and when this happens multiple time an error shows up indicating that it's an android. I have yet to do more of this but I'm very exited by what you all have done to this thing!

One last question. Will this coldboot into the custom environment or will I have to do something like a browser exploit to get into cfw? Oh and howmuch storage capacity does this thing have?

Edit: sorry for talking so much lol

Right thread this time. Alright so I've just poked around in the play store and I went to the kids section and there was a big yellow button saying install. I tapped it and the browser didn't immediately crash but instead prompted me to install it on another one of my devices... I'm assuming this rules out any play store stuff?
[Google Home] _raydroid:
How is the Helio A22 chipset on this Xiaomi Smart Clock compared to the Snapdragon 624 SoC used in other Lenovo devices? Trying to make a decision between the two.

Looks like development on this one is slightly better as there is a newer version of Android running on this one, but there are a lot less people talking about the Xiaomi Smart Clock.
[Google Home] mcdull:
I have a LX04, how to convert it to XG04?
[Google Home] Rainygortex3:
If someone would be so kind as to release an MTKClient backup of the X04G, that'd be great.
[Google Home] Rainygortex3:
NOTICE to LX04 USERS:

I have attached a guide to convert LX04 into X04G.

[GUIDE] XIAOMI SMART CLOCK - Guide to convert LX04 (China edition) to X04G (Global edition) and vice versa

I have attached a guide for conversion below, from my successful experience: It is translated to English (for XDA), Chinese (for coolapk 酷安), Russian (for 4pda.to) and German.

xdaforums.com

The result you will get is something like this:
[Google Home] Rainygortex3:
--noreconnect option in MTKClient
[Google Home] Rainygortex3:
Thx for the firmware!

It was a bit of a curved path ,but I live in Guangzhou so I could only get the LX04. (They don't sell it in China.)

So Ungeskriptet uploaded a firmware for X04G, which I flashed (but then accidentally bricked the preloader)

So now my Device is converted to X04G,

And now it's running Lineage!
[Google Home] yunoaorio:
Hello to all have you encounter this problem
[Google Home] Rainygortex3:
If you are currently experience this issue on the Chinese firmware there have been issues reported on Chinese firmware with this issue on version 2.6.8 for Newer models of Xiao Ai Speaker, I don't know if this is the issue if you're working with global edition

Quote https://tiebac.baidu.com/p/7727027938?lp=home_main_thread_pb&mo_device=1

"2020年后及2021年年出厂小爱触屏音箱刷2.6.8一定会花屏，原因在于更换了屏幕，驱动不一致，部分小爱音箱花屏后可以通过连接手机升级或通过喊小爱同学系统升级来回复，但2021年小爱花屏后会彻底变砖。

解决办法

下载SP5.5小爱专改刷机工具，下载小爱触屏-LX04_2.99.99-官改刷机包。"

"Xiao Ai speakers produced after 2020 and 2021 flashed with version 2.6.8 will experience the issue of screens with lines. The issue lies in the fact that Xiaomi changed the screen model and thus the drivers are changed too. Some models of Xiao Ai may have this issue fixed via upgrade by phone or voice commands to Xiao Ai to upgrade the system. However, if your Xiao Ai is produced after 2021 you may not be able to fix the issue using the above methods.

Solution:

Download Xiao Ai flashing tool SP5.5, and Download the LX04_2.99.99 firmware."
[Google Home] Rainygortex3:
You may download different firmware versions below (China Firmware):

小爱音箱资源站

xiaoai.qgmzmy.me
[Google Home] ARCL01:
Great work has been done here.

I have one question, I have managed to make an super.img from the factory installation following one of your guides. Right now I am stuck as I don't know how to make the boot image from the original installation. Can someone guide me through or can I just use the boot.img from the lineageOS?
[Google Home] arnoldtan327:
I don't know what i have done and now every command i send to the smart clock i can this errror message. anyone can help.
[Google Home] Rainygortex3:
Seems like your GPT's broken. Is this converting LX04 to X04G or GSI flashing?
[Google Home] arnoldtan327:
Trying convert lx04 to xg04
[Google Home] arnoldtan327:
Yes converting lx04 to x04g
[Google Home] arnoldtan327:
now got new error
[Google Home] Rainygortex3:
@arnoldtan327

"python mtk wf gpt.bin --noreconnect"
[Google Home] arnoldtan327:
i got this error when i run mtk wl --preloader x04g_files/preloader_mico_x04g.bin --noreconnect x04g_files. pls help my screen now is black
[Google Home] Rainygortex3:
Run "python mtk wf gpt.bin --noreconnect" first then it will work
[Google Home] arnoldtan327:
i already run the command but still the same
[Google Home] arnoldtan327:
DA_handler - [LIB]: ←[31mError: Couldn't detect partition: gpt_backup

, skipping←[0m

DA_handler

DA_handler - [LIB]: ←[31mError: Couldn't detect partition: preloader_mico_x04g

, skipping←[0m

how to resolve this
[Google Home] Rainygortex3:
try "python mtk printgpt --noreconnect"
[Google Home] arnoldtan327:
printgpt got this
[Google Home] Rainygortex3:
USB 5 means Wire is loose
[Google Home] arnoldtan327:
Today try printgpt get this
[Google Home] arnoldtan327:
I manage to get the screen back using splash but screen stuck as attach and how can I proceed from here
[Google Home] Whyle:
same problem i got, because it cant found device id. I have temporary found a solution to resolve.

adb shell did_write ”123/|123”
# or
adb shell setprop ”123/|123”
[Google Home] Rainygortex3:
LX04 convert X04G? Or just X04G?
[Google Home] dueruem:
Is the mute button gonna be on/off or is it just useless?
[Google Home] Rainygortex3:
On/off
[Google Home] CryptoScient:
I got the global version just to stream my kids room camera on this ****ty clock and i am very disappointed since it streams like we are in 90s or something. So my humble question is;

1- Can i install Mi home app after flashing this new OS on my clock?

2- Also can we use the mute button as "Mute" function after flashing? like mapping it back to mute?

3- Can I map the mute button to open the "Mi Home" app?

Thank you for this work. You really saved my money as it is non-returnable **** haha
[Google Home] CryptoScient:
How do i setup this driver properly on windows please help
[Google Home] CryptoScient:
Stuck there too. now i need to install a whole new operating system just for this man this sucks
[Google Home] CryptoScient:
anyone willing to help me a bit on flashing this using windows please? I'm tired and out of options :/
[Google Home] CryptoScient:
please respond someone :/ How do i do this on windows 11? I did every step correctly.
[Google Home] theubusu:
You should try using linux for the flashing. You don’t have to replace your windows install, you can use a live usb instead. I used the mtkclient live usb which has all the tools already installed and ready to use. Hope that helps
[Google Home] Lucavon:
How did you mod that LineageOS GSI to run on the clock? I tried you unpacking-repacking script, but the content of the LineageOS GSI is too large to fit into the partition.
[Google Home] Rainygortex3:
For me it works, which model of clock do you have?
[Google Home] Lucavon:
I got the X04G. What I did is this:

1) Download and unpack Andy's unofficial LOS21

2) Run the unpacker script on my super image

3) cp -r to copy all from LOS21 into the mounted directories from the unpack script

4) Error: ran out of space

What do I need to do differently?
[Google Home] CryptoScient:
well i guess I am too dumb n old to do that. created live usb but it won't boot up. Apparently there're too many things to do before i can even boot up that usb lol. When i restart my pc to boot up it just shows black screen. And i am too worried to mess up my already installed OS so might as well give up. If anyone managed to flash this crap on windows 11 please let me know.
[Google Home] Rainygortex3:
Maybe its your disk space insufficient
[Google Home] Lucavon:
I still have a few hundred GB. I think the problem is that the images are mounted and the filesystem in there has a specific size, and that filesystem might not have enough space. I'll try expanding it later. Thanks!
[Google Home] laavu:
In case someone else runs to this, had an error when writing vbmeta.img from LineageOS20_X04G.zip with fastboot:

Writing 'vbmeta' FAILED (remote: 'No such file or directory')

The solution was to go back to mtkclient, rename the vbmeta.img to vbmeta.dat and write it with mtkclient. I used the GUI, rename might not be needed if writing from commandline. After that, LineageOS booted just fine.
[Google Home] XDARKZ909:
I know this is an old thread, but maybe someone can help me. I never tried to unlock the device, but for some reason, the red state appeared, and the device is now stuck in a boot loop. I don't know how to fix it. If anyone can help, I would greatly appreciate it.
[Google Pixel 7] Gothsome:
Hello!

I have bought Klipsch BT headphones and i wanted to use an equalizer, but somehow nothing wants to funtion:

The headphones arent supported by the Manufacturer App

so i tried an App i used on my old Pixel, but just for Aux devices: eq+ and it shows an error - so not supported it seems.

I searched the web and tried the audio enhance functions of the phone itself:

In the the audio enhancer appi choosesmartphone-media and it crashes - tried it a few times and then my phoe told me the app ist crashing ann the time -bugreport ...

Tried settinig in dev options the absolute volumesettings on and off with reboot.

i just want to give the max volume and bass a little gain with the bluetooth device

I have Android14 Beta without root and the headphones are the T5 Neckband

Now im a litte clueless and happy about your suggestions

Thank you!
[Google Pixel 7] SkylinesHD:
Use wavelet (Non-rooted) or V4A_RE (rooted)
[Google Pixel 7] Lughnasadh:
Or Rootless JamesDSP
[Google Pixel 7] Gothsome:
I use tidal and they arent supported and i wont touch root until the warranty is more expired.

Thank you!
[Google Pixel 7] Gothsome:
The setup is first a little confusing, but it really does the job!

Thank you very much - you made my evening!
[Google Pixel 7] SkylinesHD:
Warranty does not expire, when you root a Pixel.
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] pooklim:
Hi , don't know if I've come to the right place but I'm trying to get information on upgrading an old Galaxy pro 12.2 from Android 5.0.2 to 5.1 . There are ROM s available for the american firmware , AT&T and Verizon both offered OTA updates ,but I don't see anything for the UK version. The firmware on the tablet is P900XXS0BPL2 CSC is P900BTU0B0L1 . There is a thread on here that uses american firmware , can I switch? I realize that people use Lineage to put later android versions on , but I heard they didn't include the stylus functionalty. I am very much a newbie in this , any simple pointers to my way forward if I want a more advanced Android (Sky Mobile is available on 5.1 is the reason behind all this) , one that will work with the stylus , and the least chance of bricking my tablet?
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] Oswald Boelcke:
Hello and good afternoon, @pooklim Welcome to XDA! I hope you'll always get the support you require.

However, prior to your next posting please read besides the XDA Forum Rules all the guidances that are stuck on top of every forum like

Note: Questions go in Q&A Forum

If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...

xdaforums.com

and the others. I've moved your thread to

https://xdaforums.com/f/galaxy-tab-pro-12-2-10-1-8-4-q-a-help-trouble.2780/

Regards

Oswald Boelcke

Senior Moderator
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] bmwdroid:
Might it not be better for him to have the thread to be moved to here?

https://xdaforums.com/f/galaxy-note-pro-12-2-android-development.2789/
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] bmwdroid:
There may be a 5.1 for these (afaik) provider locked devices but for my P900 DBT I didn't ever find anything higher than 5.0.2.

That's why mine is on LOS 14,1 Nougat.

Of course with restricted s-pen options but I can mark, read and write with it.

Bricking may be possible but on all my owned/flashed Samsungs (I9195, I9300, G900, G910F, G800, P605,P900, T325, T810 , T825) I never had that (yet?).

Odin always helped to get back to stock.