Disclaimer: I am not responsible for any damage (including, but not limited to, loss of data, non-functional device etc.) which may occur to your device from following the directions (or from any failure to follow the directions) found on this post. Use (and flash) at your own risk.
Credits go to genokolar for actually porting the U8860 2.3.6 firmware to the U8800Pro. This builds upon his port.
You may find his port announcement here, and you can download it from here. Thanks to user Skyline111 for the mirror.
Thanks also go to birdyi, who ported the U8860 2.3.6 firmware to the U8860. His port contained some brilliant things such as CarrierIQ framework removal.
--
This is a 2.3.6 ROM for the U8800Pro based on the U8860 B866 ROM. 2.3.6, naturally, brings a slightly newer version of Gingerbread compared to our 2.3.5 with B540. While I know it's all about CM9 (ICS), MIUI and so on these days, I'm a fan of stock (in the Huawei sense of the term) Gingerbread.
Features (or limitations depending on what you think of some of the following entries) of this ROM:
Rooted (adb also runs as root, too)
(Huawei) DLNA
(Huawei) A task manager that shows open applications with pictures (launching it when pressing Home has disabled in this modification because I found the Recent menu saves more time)
(Huawei) Security Guard, a way of hiding text messages, I think
(Huawei) Traffic Manager – a data counter
(Huawei) Wi-Fi WPS support
(Genokolar) FPS unlocked by default (configurable in enhanced.conf)
(Genokolar) ZRAM (Compcache) enabled
(Genokolar) Changed the autorun.iso path to the image partition so that formatting /data from CWM does not leave you with an empty CD-ROM drive when you plug the phone into a computer
bugreports service turned off entirely so that pressing the volume up button quickly after you've pressed volume down does not leave you with a few seconds' delay and a bugreports folder on your memory card
BusyBox from CM7
Android’s toolbox (poor coreutils replacement; more barebones than BusyBox) has its full set of links installed in /system/bin, so you use Android’s native chmod etc. tools. Why? To match the stock B512 firmware and to ensure developers testing on the U8800Pro correctly hardcode “busybox” in their root programs if needed
Optional lazy CPUfreq governor
Default language and region changed from Chinese – China to English – United Kingdom
Added in boombuler’s AppWidgetPicker
CM7’s Pacman added in to remind you to install Google Apps after adding an account with the Setup Wizard (make sure GApps is installed!)
VoiceDialler.apk added in from B512 firmware (although, to be honest, the microphone quality on my phone is awful…)
Bash shell, fix_permissions script, iwmulticall, MMS.apk, tcpdump and gdbserver and additional ringtones etc. from CyanogenMod (20120107-cm-7.1.0-u8800pro-Geno-en.zip) added in
Phone model changed to Desire HD, so Gameloft games can be bought. This may cause licensing problems with bought Market applications so be careful. (Although, I must admit that giving money to a company that doesn't support our phone seems counter-intuitive.)
Shutdown vibration reduced from 500ms to 100ms because I hate it (especially at night) but understand its usefulness in determining the answer to the question “Has the phone gone off yet?”
Huawei’s god-awful Low Battery notification replaced with a nicer one from CyanogenMod
Widgets actually restore themselves after a reboot! This was fixed by me replacing 2.3.6's PackageManager service with Huawei's 2.3.5 one.
MyCalendar widget from birdyi's port and MyEmail from B512 added in
Fixed proximity sensor dying if the light sensor was on, too.
Stripped down enhanced.conf - only swappiness, VSync and ZRAM settings available. I don't like /system/log.txt being created every time my phone boots and I think using a tool in Android like, say, No-frills CPU Control is the better place to set the frequency. SetXperia has support for setting the phone's CPU voltage.
More languages selectable from the Setup Wizard than just English (US) and Chinese.
Flash Player removed for copyright reasons. You can install it from the Market
Notepad and Richpad removed
Droid Sans Fallback supports more character ranges
Toolbox correctly has "Wi-Fi" instead of "WLAN"
Misc. kernel modules, like in B512, included
But I like the BusyBox tools and want to use them without having to prefix BusyBox everytime!
Just run the bash shell; BusyBox versions of cat, chmod, chown, df, insmod, ln, lsmod, mkdir, mount, mv, rm, rmdir, rmmod, umount, sleep, kill, and ifconfig will become the default while you’re using the bash shell (also nicer, BTW: you get tab-completion, for one) thanks to the CyanogenMod team.
Attempts to remove Carrier IQ. Huawei *do* include Carrier IQ in their firmware.
I’ve done the following to attempt to remove it the best I can:
Edited boot.img to not start Carrier IQ services
Removed Carrier IQ libraries from /system/lib and CiQ binaries from /system/bin
Added lines to build.prop to disable CarrierIQ, taken from the framework.jar file itself.
birdyi has also modified framework.jar to stop the CarrierIQ objects from being instantiated.
Ideally the best way to be Huawei-free is to use CyanogenMod.
I've removed the Cloud+ apps because of this. I've left some Huawei apps in, but I strongly recommend you install PDroid (the patcher works fine with this ROM) and block the more concerning permissions of Huawei system apps.
Kernel changes
Since the kernel genokolar provided with his port had a problem when a program used the light and proximity sensor at the same time – the proximity sensor would die out until the next restart – I took it upon myself to rebuild the kernel available from his github repository with the config from his latest kernel. After comparing his kernel to the source Huawei put out, I could see no code changes that would cause the proximity sensor to die out. Since I was rebuilding the kernel, I thought I’d make a few changes:
Add in the Lazy CPU governor by Ezekeel
Update a patch by stockwell to disable keypad lights (echo 1 > /sys/module/leds_msm_pmic/parameters/disable_button_leds) - use ButtonLock to control
Reverse genokolar’s decision to always allow NV logging – this can be turned on and off from the service menu on a stock ROM anyway…
Set minimum backlight level to 15, from Franco’s kernel. Warning: I haven’t tried setting it to 15 so I don’t know if that value renders the display practically useless, and I don’t know if Android lets you set it to 15 from its settings!
ButtonLock
Not as revolutionary as I'd like it to be, but useful nevertheless. I've written a quick widget, which looks like the Power Saving one, that turns off the button backlight. Useful for when you're reading books through FBReader.
You need to be using my kernel as it has the disable_button_leds patch. The advantage the disable_button_leds patch has over the chmod 444 method is that it doesn't introduce noticable lag. The widget's source is in the same folder.
When pressing the widget's button for the first time, there is a delay as the Superuser allow/deny dialog box takes its time to come up. After accepting, future launches are instantaneous.
If you need something that this ROM doesn’t provide compared to other stock ROMs, I recommend:
Not using it; or
Using a combination of diff, abootimg, Winmerge (or Beyond Compare) and apktool to compare this with genokolar’s original release, and with birdyi's ROM, and add what you want back in
Installation
Note: You must be running firmware version B522 on your device! If you have B540, you need to downgrade. If you have a firmware version lower than B522 (Froyo?), you must upgrade to B522 first. If you're already running a custom ROM, ignore this.
Take out the SIM card if you want the setup wizard to use Wi-Fi during setup.
Install genokolar’s recovery: http://forum.xda-developers.com/showthread.php?t=1343276
Place u8800pro-2.3.6-geno-v1-modified.zip on the internal memory card or an external one (I recommend the internal one to ensure you don’t run into U8800Pro CWM bugs with the external).
Get gapps for Gingerbread and place on your memory card. Find the link using every Android user’s favourite search engine.
I highly recommend using PDroid, but it’s up to you whether you want to use it. If you would like to use it, get the patcher from http://forum.xda-developers.com/showthread.php?t=1357056 and point it to u8800pro-2.3.6-geno-v1-modified.zip. Place the PDroid-v1.27-u8800pro-2.3.6-geno-v1-modified.zip file onto your memory card.
Boot into recovery (make sure that fast boot is turned off in Settings->Applications and hold power and volume up while turning the phone on)
Do a data/factory reset.
Install the ZIPs, starting with u8800pro-2.3.6-geno-v1-modified.zip (obviously).
Reboot!
Install the Google apps (those ones not included in CM's gapps ZIP like YouTube) if desired when prompted – but note that the Market will probably close as you’re doing this as it will automatically update itself.
Downloads
ROM: http://www.mediafire.com/?k0g17z1kraw7b67
SHA512: 4988B123488B8B24732401420DE849E8D8E5632C075A4520F176AA1D64DA0ECF946FF4D4E6CEC4D257EE4C4C999200A93C2CB309FD7B5FE50234A1C5700DEB2D
Modified kernel source (I suck at Git - I really need to read that VCS by Example book I have ): http://www.mediafire.com/download.php?a0022t73q2v7r7d
ButtonLock source (Apache licensed, though I must admit I'm more of a GPL person...): attached.
--
Extras:
genokolar's 5.0.27 recovery for the U8800Pro with the charging animations from https://github.com/Victor-android/android_device_huawei_u8800pro/tree/master/recovery/res/images:
attached.
Anyone tried it?
ill try it this evening I hope it fixes missed calls....
I have B512 official gingerbread, am I good to go?
Too times was a situation, when phone lost connection with wi-fi spot, he see the network, but can't connect. Help reboot.. else working so far without problems, testing..
...
turned off the wi-fi and got the main bug - does not work 3g/2g data transfer, hmm....
bobsido said:
with wi-fi spot, he see the network, but can't connect. Help reboot.. else working so far without problems, testing..
Click to expand...
Click to collapse
Interesting. I've had no problems reconnecting to a network that uses WPA2-PSK and another that uses 802.11x authentication.
turned off the wi-fi and got the main bug - does not work 3g/2g data transfer, hmm....
Click to expand...
Click to collapse
Are your APNs set correctly? In my case 2G works and I've had HSDPA working because when testing the Weather Clock widget (from B522, when I had it in) it would connect using it - I could see the icon in the status bar - and I had the pleasure of having my balance run down each time - I'm not a rich man
Edit: In build.prop, you can try playing with ro.config.hw_fast_dormancy=3 - genokolar had it set to 2, but I changed it back to 3 from the U8800Pro original ROM because I wouldn't be able to connect to my network otherwise.
Hopefully, it's not the case but it could be hardware differences. genokolar, who's work this is based on, being from China, probably has a Unicom U8800Pro, just like I do...
@Zaic
B512? This is for the U8800Pro. I'd advise you not to flash it. I'd recommend using birdyi's ROM. If you're after a certain improvement from this ROM, tell me and I'll try and isolate it for you (as long as it doesn't involve kernel stuff - I don't know how to build U8800 kernels) so that you can use with birdyi's ROM
I have u8800 pro - 100%
My ROM is original unrooted 2.3.5 B512 its one before the latest release which is B540
My ROM still has access to pink screen, otherwise its the same as B540 I guess
SO what should I do first to install this ROM? roll back to 2.2.2 or was it 2.2.3?
Ah, if you're running 2.3.5 already and in the pink screen mode you see a folder called image when connecting your phone to the computer you're ready to go
Hi!
My compliments for the porting of Android 2.3.6 to U8800Pro!
I am using your rom since yesterday and still now I am not having any kind of problems.
Anyway I notice the same bug of the B512 and B540 roms: put your smartphone on screenoff, then wait about 1 minute and fastly unlock the screen and try to pinch to zoom on the home. Sometimes the multitouch doesn't work on every position of your fingers, it only works correctly if your fingers are in the position of principal axes.
Please try to reproduce this bug.
I am using LauncherPro but this bug is indipendent by the launcher (for example I tried also Zeam Launcher, Go Launcher EX, etc etc).
I hope you can solve this bug, maybe kernel-related.
Regards,
kalo86
Hi,
kalo86 said:
My compliments for the porting of Android 2.3.6 to U8800Pro!
Click to expand...
Click to collapse
The honor is genokolar's
I am using your rom since yesterday and still now I am not having any kind of problems.
Click to expand...
Click to collapse
Thanks; it's nice to know that it's working OK on somebody else's device other than mine.
Anyway I notice the same bug of the B512 and B540 roms: put your smartphone on screenoff, then wait about 1 minute and fastly unlock the screen and try to pinch to zoom on the home. Sometimes the multitouch doesn't work on every position of your fingers, it only works correctly if your fingers are in the position of principal axes.
Click to expand...
Click to collapse
Sorry for asking, but how do you pinch to zoom on the home screen? I'm using Go Launcher Ex and I know that that has the swipe up gesture but I can activate that with one finger, anyway.
In any case, have you applied the Synaptics touchscreen update? For me it has increased the touchscreen performance greatly. I had one problem that when after unlocking, the touchscreen wouldn't respond unless I turned the screen off and tried again. The update solved that.
If you want to try it, open the service menu (*#*#2846579#*#*), go to ProjectMenu->Upgrade->Touch screen version query and see if it says "synaptics". If so, put the original Huawei recovery.img back on and put the synaptics.img file in a folder called update on your SD card. Use the recovery's "touchscreen firmware update" update option and it will automatically reboot when it's done.
Best regards,
qwerty12
Oh, really thank you for this "news" about the synaptics touchscreen update!
I have a synaptics too, then I am going to update the firmware.
Another bug, still present in B512, B540, Cyanogen and U8860 port: unplug your battery from the smartphone, insert it again, power on, then open your file manager and try to read the sdcard content. At 99% my sdcard is not read, then I have to reboot my U8800Pro and magically the sdcard is read.
Thanks to You and Genokolar for our development!
Regards,
kalo86
UPDATE: I updated the synaptics touchpanel but I have always the bug of multitouch. It is reproducible when you unlock the screen after a pause of 1 minute (about), then you open the stock browser and try to zoom with the multitouch. It works only if your fingers are on the principal axes and not in other positions. I have this bug on 4 different U8800 Pro! It cannot be a singular problem.
So, I have tried a lot of roms, based on B512, B540, U8860, CyanogenMod 7.1, I am sure I will try this bug on the next release because it's mabe a kernel bug due to the multitouch field.
Video demonstration
This is a video which I just uploaded on YouTube with the real multitouch bug.
This bug is in 4 different U8800 Pro.
http://www.youtube.com/watch?v=avSdW2V8TLg
kalo86 said:
Another bug, still present in B512, B540, Cyanogen and U8860 port: unplug your battery from the smartphone, insert it again, power on, then open your file manager and try to read the sdcard content. At 99% my sdcard is not read, then I have to reboot my U8800Pro and magically the sdcard is read.
Click to expand...
Click to collapse
I really can't reproduce this. I pulled out the battery while it was on, put it back in and started File manager (the one included with Huawei ROMs) and the internal SD card along with my external one were seen fine.
UPDATE: I updated the synaptics touchpanel but I have always the bug of multitouch. It is reproducible when you unlock the screen after a pause of 1 minute (about), then you open the stock browser and try to zoom with the multitouch. It works only if your fingers are on the principal axes and not in other positions. I have this bug on 4 different U8800 Pro! It cannot be a singular problem.
So, I have tried a lot of roms, based on B512, B540, U8860, CyanogenMod 7.1, I am sure I will try this bug on the next release because it's mabe a kernel bug due to the multitouch field.
Click to expand...
Click to collapse
Thanks for the video! Unfortunately I don't know how this can be fixed - I'm not a developer! It was only yesterday I tried looking in the driver to see how I can enable more than two finger recognition but I'm not seeing it...
Best regards,
qwerty12
Sorry for disturbing you, but I have a question: do you have the same bug of the multitouch after the lock-screen?
This is a second video about the same problem:
http://youtu.be/64NvbFJD3rs
qwerty12 said:
I really can't reproduce this. I pulled out the battery while it was on, put it back in and started File manager (the one included with Huawei ROMs) and the internal SD card along with my external one were seen fine.
Click to expand...
Click to collapse
The same here with sd,full power off device, power on then sd card is not mounted and cpu load is almost 100%. after restart or reinserting sd, problem just dissapear. on every rom i tried. i flashed official V100R001C00B512G001Gb (2.3.5) and then tried CM7; u8800+v100r001c00b540g001gb-rooted_geno-v4.
Is FM Radio working in this ROM?
Yes, Radio is working fine
qwerty12 said:
Are your APNs set correctly?
Click to expand...
Click to collapse
i fix APN settings and 3g/2g start work, thanks.. after reflashing wi-fi start work without problem. but after first reflash don`t work home button. they have response, but nothing happen. i secondary reflash phone, without wipe data/cash and home button start to work correct.. now tests are continuing
kalo86 said:
Sorry for disturbing you, but I have a question: do you have the same bug of the multitouch after the lock-screen?
This is a second video about the same problem:
http://youtu.be/64NvbFJD3rs
Click to expand...
Click to collapse
A little bit - after unlocking, I can do the multitouch gesture and phone will respond like it's supposed to but I have seen twice that it has not responded to me; I have to do it twice more...
Barracuda72 said:
Is FM Radio working in this ROM?
Click to expand...
Click to collapse
Like kalo86 said, it is indeed
bobsido said:
i fix APN settings and 3g/2g start work, thanks.. after reflashing wi-fi start work without problem. but after first reflash don`t work home button. they have response, but nothing happen. i secondary reflash phone, without wipe data/cash and home button start to work correct.. now tests are continuing
Click to expand...
Click to collapse
Please do let me know if you come across more problems
Zaic said:
Anyone tried it?
ill try it this evening I hope it fixes missed calls....
I have B512 official gingerbread, am I good to go?
Click to expand...
Click to collapse
So, any missed calls?
If someone wants to help the Community to understand the sdcard mount bug, please have a look here: http://forum.xda-developers.com/showthread.php?t=1483519
This is a poll, please vote!
Best regards,
kalo86
Zyzas said:
So, any missed calls?
Click to expand...
Click to collapse
Haven't had time to install this ROM yet.... but ill report as soon as I know
---
---
---
---
---
For owners of Xiaomi Air 12 or 13 that are facing static sound in Audio cause of Windows 10 please update your Realtek driver from their own website and not use windows update or general update. You need to download the latest 64bit driver dated ' 14-Jun-17 - 6.0.1.8186 '
@Wootever, sorry for my unrelated question. But, I have a Xiaomi Air 13 2016 and I've set a supervisor password when I changed to Linux. I then removed the password when I changed back to Windows 10, but it's still asking me for one...
Do you happen to know a way on how to remove the BIOS password on this laptop? I've extracted the executable from Insyde H20 A06 updater and changed the platform.ini, so it does a force flash of the password area (Password=1), however, it's still asking for one.. Any help would be greatly appreciated! Thanks in advance
@r00tPT
Try to set the password again and then set it to blank.
Wootever said:
@r00tPT
Try to set the password again and then set it to blank.
Click to expand...
Click to collapse
Thanks, but I cannot set the a new password, as when I try to access the BIOS, it asks me for a password..
I wanted to reset this password altogether, so I can access my BIOS and set a new one =/
@r00tPT
You can try to flash this default BIOS A06 Package, it will overwrite all device specific data (Serial, Windows Key, NVstore).
All settings should be set to default (including the password), but i haven't tested this (no guarantee and at your own risk).
Edit:
Don't forget to create a backup using the Backup.cmd file, it should be possible to restore the Serial number on the "empty" default BIOS.
Wootever said:
@r00tPT
You can try to flash this default BIOS A06 Package, it will overwrite all device specific data (Serial, Windows Key, NVstore).
All settings should be set to default (including the password), but i haven't tested this (no guarantee and at your own risk).
Edit:
Don't forget to create a backup using the Backup.cmd file, it should be possible to restore the Serial number on the "empty" default BIOS.
Click to expand...
Click to collapse
Thank you, Wootever! I think it's worth a try.
Would it make sense to create the backup, flash the default package, confirm if there's no password and then flash back the original Xiaomi BIOS to restore the Serial number?
Sorry, as I have near to none experience related to bios. thanks once again
@r00tPT
The backup includes all current settings (including the password), restoring it would also re-enable the password protection.
I made a little script to restore the device serial from the backup.bin file.
This is necessary because the Windows Activation seems linked with the device serial number.
Edit:
Updated the script.
Wootever said:
@r00tPT
The backup includes all current settings (including the password), restoring it would also re-enable the password protection.
I made a little script to restore the device serial from the backup.bin file.
This is necessary because the Windows Activation seems linked with the device serial number.
Edit:
Updated the script.
Click to expand...
Click to collapse
Wouldn't it be best to make a backup of the current bios with a flash programmer? I still haven't done this, as I'm trying to figure out what password I put.. (I basically set a supervisor password when I disabled secure boot, but then when I tried to set a new blank password it didn't change it back)
I have a friend who has the exact same laptop. Would it be fine if I made a backup of his bios and restore it into mine?
Could there be an issue or some missing information? Probably only the device serial number, which I could write again using your script? Would that be feasible?
By the way, sorry for asking these questions here/to you, but it's hard to find some guidance regarding this topic. Thanks once again
@Wootever, it worked!! You're the greatest man! I'm now able to access my BIOS again!
Is there any way to re-enable the flash protected range register again, just in case?
Wootever said:
I just got my hands on a Xiaomi Air 13 (2016 version) and wanted to share my findings.
The BIOS version of this device is A07, which is not yet made available by Xiaomi and originally, BIOS updates can only be flashed with the Insyde tools.
However, those require a valid certificate to correctly sign the binary file, thus a provided backup of version A07 won't be applicable as a update.
Intel Flash Programming tool is another alternative which allows to flash unsigned/customized versions, but in practice FPT can't access the BIOS region due to the protected range register which prohibits write access.
Code:
Error 316: Protected Range Registers are currently set by BIOS, preventing flash access.
Please contact the target system BIOS vendor for an option to disable Protected Range Registers.
Fortunately there is an undocumented variable switch that i found by coincidence which deactivates the flash protected range register.
For this i made a little tool which automatically patches the variable to allow BIOS update via FPT.
Note: modifying your BIOS is at your own discretion, i am not responsible for any damage caused by this procedure.
Download my variable patcher, extract it and execute Patcher.cmd
Reboot your device.
Download BIOS A07 for the Xiaomi Air 13 (2016)
Execute Backup.cmd to create a backup of your current BIOS.
Then execute Update.cmd to install version A07.
Use Serial.cmd to restore the device serial number from the backup BIOS.
Reboot your device.
I also made a few changes for this BIOS:
Updated microcode to 0xBA
Increased PWM frequency to 5000 Hz
Click to expand...
Click to collapse
I tried but I have this problem with patcher, any suggestion?
@Wootever
1) after upgrading the bios, how do i re-activate the flash protected range register?
2) do you have the default clean A07 bios (without the microcode and PWM changes)?
thank you!
May I ask if there is an easy way to unlock BIOS totally on Xiaomi Air 13? Because previously I opened a topic about it in biosmods.com , someone reached to me and told that due to write protection it needs quoting from him: "Bios mod can be flashed using SPI-programmer+SOIC8 clip only". That requires opening laptop up and connecting clip on chip physically. I love to tinker things in my laptop but that is a bit scary for me. So is there another way to do it, anyone knows??
THANK YOU!! This is pure gold! By the way, does the flag you found also unlock the ME region?
Update: nevermind. The answer is no unfortunately
bigorbi said:
May I ask if there is an easy way to unlock BIOS totally on Xiaomi Air 13? Because previously I opened a topic about it in biosmods.com , someone reached to me and told that due to write protection it needs quoting from him: "Bios mod can be flashed using SPI-programmer+SOIC8 clip only". That requires opening laptop up and connecting clip on chip physically. I love to tinker things in my laptop but that is a bit scary for me. So is there another way to do it, anyone knows??
Click to expand...
Click to collapse
No, you can flash any bios mod with the flag found by @Wootever. However, you may want to get a programmer (Altera USB blaster has cheap Chinese clones supported by flashrom) and a SOIC8 clip anyway just in case. They're dirt cheap and allow for recovery when things go wrong.
As a bonus, an external programmer enables you to get rid of the management engine.
CARLiCiOUS said:
THANK YOU!! This is pure gold! By the way, does the flag you found also unlock the ME region?
Update: nevermind. The answer is no unfortunately
Click to expand...
Click to collapse
It might be possible if the variable for ME Image Re-Flash is set:
Code:
Me FW Image Re-Flash, Variable: 0xD08
Disabled, Value: 0x0 (default)
Enabled, Value: 0x1
Variable to unlock protected range register:
Code:
BIOS SPI Lock:, Variable: 0x258
Enabled, Value: 0x1 (default)
Disabled, Value: 0x0
Edit:
Here is another variable patcher that also enables the ME Re-Flash variable.
(Note: not tested, use with caution)
Projectivy Launcher (formerly ProjecTivy Tools) now has its own dedicated thread located here.
Intro
There's so much information here that a new user could probably feel lost without the courage to read everything. So let's keep things simple : as the thread's title says, the primary aimed devices are projectors produced by Xiaomi related brands (xiaomi/fengmi/wemax), though it could probably be useful to other Android Tv models and other brands, so you might want to keep reading until the end of the introduction.
What you can find here :
Full tutorial to Googlize your chinese device with my custom made Google Apps package dedicated to Android Tv 6 (only tested on MiUi Tv, root required)
General FAQ related to these devices [post #2]
Information on how to root xiaomi/wemax/fengmi/vava projectors (and custom made TWRP for many chinese models) [post #2]
Full firmware and OTA for many models [post #2]
Google Apps / Services instructions
Here's a full tutorial to root and install Google services on your Android 6 MiUi device (ie: chinese xiaomi/fengmi/wemax).
This has been tested successfully on all devices where a custom TWRP is available below. If anything goes wrong for you, try to factory reset / clean flash
Except for "AndroidMediaShell" (Google Cast server), most (all?) features are working fine including :
Tv settings
Google Play (to let it install/update apps, please enable the Accessibility Service)
ATV remote service : if you install Google ATV remote on your smartphone, everything (including speech recognition) will work
Google Assistant : with the Accessibility Service enabled, a short press on the mic button on your stock remote control will launch Google Assistant. Then, when it's listening, press and hold the mic button while speaking and release it when done. According you've used More Locale to change to your mother tongue, this will even work in your language.
Installation steps:
root your device (see post #2) (you don't need to flash any firmware)
if not already done, install the latest version of ProjecTivy Launcher and launch it
execute Applications / install 3rd party apps, then install :
Aptoide Tv Store
ATV launcher [optional] (alternative launcher)
Youtube [optional]
MoreLocale [optional] (in case your mother tongue is not english, it will let you choose more than what's listed in Android settings)
Google Apps/services (don't forget it )
execute Applications / Freeze Stock launcher (to disable your stock home screen)
execute Applications / Freeze Stock apps (to disable most Xiaomi apps and services)
execute System / Custom Props override (to pass safetynet checks, enable more stock behavior and fix black screen with non-stock launcher)
execute System / Accessibility Service, enable the service in accessibility settings (to fix "Google Play" ability to install/update apps and to link the stock remote control "Voice recognition" button to Google Assistant as well as many other features)
[Optional] Install magisk module "Nexus Media" to change the stock bootanimation (go to Shortcuts / Magisk Manager to execute it, and then in the left menu, "Downloads" section, just install "Nexus Media")
Reboot and complete the Welcome app to setup your Google account (first and second boot will be longer than usual)
Note that an Android accessibility setting might get enabled after the first reboot when Google Apps have been installed. It'll cause green borders around buttons. Just go to settings / accessibility and disable "talkback".
Launch Google Play to update Google apps and let the update finish before exiting Google Play (if the app's accessibility service is running as it should, it will display a message when launching/exiting Google Play)
[Optional] start MoreLocale to change your language
Disable the "smart update" in the projector settings so that it doesn't try to download and install OTAs (which would just display an "error" message after each boot, when it fails to install it)
Enjoy your Google Tv device !
Important :
Once installed, don't change the device resolution in the Android Tv settings. This is not supported by the video drivers that will then only display a checkerboard. The only known solution as of now is to factory reset and start again.
Engineering Menu App Translation
Here you'll find information about xiaomi's engineering menu app.
After a bit of google translate and reverse engineering, here's a translation of the different menus, along with my own values (1st one is for "rainman", second one for "batman")
Projector information
- Brightness [1541][1610]
- DLP vendor name [APPO][APPO]
- Production Week [1812][1921]
- Contrast ratio [3828][3370]
- Brightness Uniformity [940][856]
- Serial Number
- Color coordinates [r:860 g:860 b:860 x:283 y:302][r:860 g:860 b:860 x:2720 y:2790]
Solid color (android) -> displays a solid color (using android system)
Solid color (projector) -> displays a solid color (native)
Other image test (android) -> displays a gradient (using android system)
Other image test (projector) -> displays a gradient (native)
Color wheel delay -> when incorrectly set, this can lead to posterization issues (gradients become unnatural and tend to display large uniform areas) [490][420]
Save color wheel delay to Android
Image mode: change the screen light intensity
- Standard
- Highlight
- Energy saving
Temperature monitoring
- ambient temperature [31][43]
- color wheel [52][63]
- Laser temperature channel 1 [60][74]
- Laser temperature channel 2 [61][74]
- DMD temperature [-][0]
Model name [MiProjA1][MiProjLAS2]
Human body induction -> enables/disables IR sensor that disable image when coming close to the laser
Save information to projector
DLP version [major:1, minor:2, patch:5][major:7, minor:3, patch:7]
3D (when modified, need to restart to take effect) -> enable/disable 3d support
Devices list
For reference, here's a list of devices where ProjecTivy (and several of its special features) has been tested working fine.
Only models using Android 6 can be rooted yet.
1080p Laser Projectors:
Xiaomi Mi Laser UST Projector 150" (chinese) / MiProjA1 / model: MJJGYY01FM / codename: rainman
Wemax One 7000 / MiProjA1 / model: FMWS01C / codename: rainman (thanks rockpaperscissors)
Wemax One Pro / MiProjA1 / model: FMWS02C / codename: rainman
Xiaomi Mi laser UST Projector 150" (international) / MiProjA1 / model: MJJGYY02FM / codename: anglee (thanks Nathan0121) (no root supported yet)
Xiaomi Mijia ALPD 3.0 (rear throw laser) / model: L185JCN / codename: franky (no feedback concerning twrp yet, try rainman and report if it works)
4k Laser Projectors:
Xiaomi Mi Laser UST Projector 150" 4k (chinese) / MiProjLas2 / model: MJJGTYDS01FM / codename: batman
Xiaomi Mijia 1S 4k (chinese) / MiProjLas2 / model: MJJGTYDS04FM/ codename: batman
Wemax A300 / MiProjLas2 / model: L1668FCF / codename: batman
Fengmi 4K cinema laser / MiProjLas2 / model: L176FCN / codename: batman
probably not released yet / MiProjLas2 / model: L246 / codename: batman
Fengmi 4K cinema pro laser / FMProjA2 / model: L176FCNPro / codename: jerry (no root supported yet)
Fengmi 4K C2 (cinema 2) / ? / model: L166FCN / codename: jerry (no root supported yet)
Fengmi 4k Max / model: L406FCN / codename: jerry (no root supported yet)
Xiaomi Mi 4K laser UST Projector 150" (international) / model: XMJGTYDS01FM / codename: angleeUHD (no root supported yet)
Led projectors:
Xiaomi Mi Home Projector Lite / Mijia DLP Projector Youth edition / MiProjLED1 / model: MJJGTYDS02FM / codename: conan (root using rainman twrp below)
Mi Smart Compact Projector (international) / Mijia DLP Projector Youth Global edition / model: M055MGN / MiProjM05 / SJL4014GL / codename: ?
Fengmi M055FCN / model: M055FCN / MiProjLED1 / codename: doraemon (root using rainman twrp below)
Xiaomi Mijia Mi / ZMiProj / model: TYY01ZM / codename: zodiac
Tvs:
Xiaomi Mi TV 3s / codename: mission impossible
Xiaomi Mi TV 4 / codename: pulpfiction
Xiaomi Mi TV 4a/4c/4s/4x / codename: matrix/xmen
to be completed
More in post #2 below
FAQ and more resources related to these devices
Differences between projector devices
Wemax One / Chinese Xiaomi Mi Laser:
They are (almost ?) the same.
Software-wise :
They are exactly the same (exaclty same codename, firmware, etc...)
Hardware-wise :
Wemax is black, Xiaomi Mi is white
Wemax is described to be 7000 lumens (1688 ansi lumens), Xiaomi mi 5000 lumens (1600 ansi lumens) (not sure if hardware is different or it's only a software parameter that changes its laser power)
Chinese Xiaomi Mi Laser/ International Xiaomi Mi Laser:
Software-wise :
Chinese one comes with android 6.0.1 and MiUI Tv (a Xiaomi UI dedicated to chinese users), International one comes with android 8.1 (more details below)
Hardware-wise :
Chinese one is equipped with DDR3 ram, International version DDR4
Chinese one has Amlogic T968 with onboard Mali T830 gpu, International one has Amlogic T962 with onboard Mali 450 gpu (somewhat less powerful, not sure it has any real world impact)
Also note than more often than not, International version will probably come with a warranty. It might be important, as few people complaining about dead white pixels seem to have a hard time getting their chinese projector repaired.
Pros/Cons of 8.1 international device / firmware (as of 10/10/2018)
This might help people choose between 02 international version and 01/wemax devices. Most of the information below come from this test. This is however subject to change as I believe Xiaomi will probably enhance their drivers in the coming monthes.
Pros
Complete software translations (no more chinese ressources)
Better user interface
Google Play Store availability
Better support of media apps that hardly work on 6.01 (Netflix, Prime Video...)
Better default colorimetry (but less configurable)
Less input lag (75,6 ms vs 126,6 ms) fixed on 1218+ firmwares
Cons
No 3d support
Less options related to display settings (missing RGB levels)
Worse image quality as noise reduction and sharpness seem to be less effective than on the 01 version
Judder and image tearing during media playback
Can devices international firmware be flashed on chinese models
No :
- devices hardware is not exactly the same
- partition layout is different (android 8.x requires a vendor partition)
- we don't have access to any international firmware
Supported video modes
EDID data here for "rainman" (1080p version) : View attachment edid-rainman-report.txt
EDID data here for "batman" (2160p version) : View attachment edid-batman-report.txt
EDID data here for "jerry" (2160p version) : View attachment edid-jerry-report.txt
EDID data extracted with HDMI 2.0 enabled from /sys/devices/hdmirx.28/hdmirx/hdmirx0/edid and analyzed with Advantiv EDID Editor 1.01.0268
Is my 4K device really displaying in 2160p ? Why does YouTube refuse to stream 4k ?
- Yes.
- Blame it on Google. Or AmLogic.
More details here.
Note : more recent devices such as Fengmi Cinema 4k pro (codename Jerry) based on Amlogic T972 soc don't have this limitation (they support VP9 hardware accelerated decoding)(but seem to lack 3D support)
ALR Screens
Interesting post from @servo386 regarding Ambient Light Rejection screens dedicated to UST devices.
Rainbow effect
I see many questions regarding rainbow effect (due to the DLP technology used). What I can say is that I never saw anybody complaining about it on the Mi laser projectors. A previous projector I owned (an Optoma) was also using DLP technology and I could see this rainbow effect from time to time. In the case of rainman/batman, I've never been able to see it.
Input lag
The Mi laser projectors have relatively high input lag (150/175 ms). Firmware updates sometimes help. As of september 2019, the lowest input lag can be obtained on "Monitor" or "Game" mode (approximately 100ms on batman, 75ms on rainman). If your device is rooted and you're using the ProjecTivy Tools, you can also use the "User" mode, and long press the "back" button to get down to the same input lag as "Monitor" mode, with the benefits of keeping your calibration settings.
Dead/black/white pixels
One owner of the chinese version here (french) who had a dead pixel managed to fix it by increasing RGB custom settings above 1500 for some time (don't know how long). When reverting to previous values, the white pixel had disappeared. Didn't work out for another user, but it might be worth a try.
This might change in the future (in this case, please keep me informed), but trying to manually repair by changing the chip is a dead end. It's not the usual Texas Instrument DLP4710FQL, but the DLP4711FQL (source), which is not compatible(source) and can't be bought online.
Display issues with MJJGTYDS01FM (Xiaomi branded 4k model)
Many display issues can affect this device : taking time (minutes) to start displaying something, displaying only half image or white lines/bands... Most issues appear when the device is cold and get fixed when it has heat up.
Seems like a hardware design issue that can be fixed by removing a few screws. More information here. After this, like your projector, you won't be screwed anymore
More details can be found here as well.
HDMI input ports don't work anymore in International devices after upgrade
Install the tools, launch engineering menu and select "HDCP key reset" (thanks @xthing)
Cross platform Remote Control
I also developped a simple web based remote control for MiUI TV (Xiaomi with chinese interface) based android devices (such as projectors, boxes, TVs).
No need to install anything special on your controlled device, this website/webapp communicates with the MiUI TV internal web server to send events to your device.
It should be compatible with anything running a web browser (provided it's quite up to date): Android, iPhone/iPad, PC/Mac computers...
Just head to http://mireco.hopto.org, configure your device local IP address and you're good to go.
More details on GitHub.
Other Tools
MiiInfo from 4PDA user Loly, shows various details concerning your projector.
Firmware updates after rooting and/or installing Google Apps
Firmware updates won't install if files on your system or kernel partition are modified. Using the ProjecTivy Tools and installing the Google apps won't modify existing system files, but rooting with magisk will modify the kernel. So before any update, you have to restore your kernel (aka "boot") partition using TWRP, and then reapply Magisk once update is done.
Google Apps Issues / not yet working
Amazon Prime video : it's been reported that Amazon purposefully blocks the app on projectors. The app loads, but refuses to stream videos. Some previous versions (requiring mouse for some features) work fine though. You can install the most recent compatible one using the ProjecTivy Tools.
Netflix : No recent Tv version seems to work. Some previous versions (requiring mouse for some features) work fine though. You can install the most recent compatible one using the ProjecTivy Tools. Anyway, due to missing full widevine support, full hd / 4k will probably never work.
Chromecast framework (Google Cast Server, aka AndroidMediaShell) isn't supported (devices need to be approved by Google to be supported)
Recovery
To go into recovery, turn off your projector, unplug it, hold down OK and BACK buttons simultaneously (OK and HOME for anglee) on your remote and plug back your projector while still holding them down.
Warning : don't "hot-unplug" it, turn it off before, or it won't work.
If you're looking for TWRP, have a look a few points below
Unroot
Start the Magisk Manager app and select uninstall
OR
Boot Twrp and reflash the Boot (kernel) backup you made just before installing Magisk
Factory Reset
Reflash the full stock firmware available below in this post. This doesn't require any intervention on your part so it should work even if you can't see the display
OR
Boot the stock recovery and select the "reset device" (not sure of the exact terms) option
Root
Note : both methods below work for rainman as well as batman (4k) devices.
Easy Method:
This method doesn't require any special hardware, only the TWRP I made (3.2.2.0, based on stock recovery files), along with another config file.
Thanks to @cr4zyw3ld3r who made a video tutorial based on the following instructions.
For french people, here you can find a tutorial made by Pierre. Thanks to him.
Extract this file View attachment batman_twrp_3.2.2.0b.zip (for "batman" 4k), this file View attachment zodiac_twrp_3.2.2.0.zip (for "zodiac"), or this file View attachment rainman_twrp_3.2.2.0.zip (for "rainman" 1080p and most other devices such as conan) at the root of your (FAT32 formatted) USB drive, where you also place the latest magisk version (magisk 20+ version support has been added on tools v3.5+), and plug it into your projector (I used the right USB port)
I also built (but not tested) a twrp for Vava projectors here : View attachment vava_twrp_3.2.2.0b.zip (please report if it works).
Download ADB for your computer (check here)
Start command line (terminal)
Enable USB debugging in Android settings / developer options (you can access them from the projectivy tools)
Type "adb connect IP_OF_YOUR_DEVICE:5555" to connect through the network
Type "adb reboot update" (This will restart your device and make it boot the TWRP on the USB drive.)
Once in TWRP a mouse will be required. Make backups if you wish (at least "boot" partition that you'll need to restore before applying any OTA update), and then mount SYSTEM, and install magisk in order to root the device (it will be in "/udisk" and will be called Magisk-......zip)
Note : to thank the donors, I also developed an application that installs on your Android smartphone, which automates steps 1 to 6. There is no need for computer or custom command lines in this case. Once the app is connected to your projector, you're only one button click away from TWRP.
Note : if it still boots to stock recovery and not twrp, make sure you extracted the zip and not only copied it to your usb drive. If it's extracted correctly but still doesn't work, try another usb drive, a few people reported that this fixed their issue (some users had to try 3 or 4 usb devices before finding one the works).
Old Method:
With the correct hardware, you can root your device, following this tutorial from @servo386
To simplifiy the rooting process described in the link above :
Extract this file View attachment twrp-files.zip at the root of your USB drive, where you also place the latest magisk version (as of now 19.3), and plug it into your projector
Follow the steps described in the tutorial, up to the point where you have a root console access in recovery
Then, according you've plugged your USB drive before starting your device, just type ". /udisk/twrp.sh" in the root console. This will copy the necessary files and automatically run twrp, reducing the number of steps (and potential mistakes) to root your device.
Once in TWRP, make backups if you wish, and then mount SYSTEM, and install magisk in order to root the device (it will be in "/udisk" and will be called Magisk-.....zip)
Roms / Dumps
Due to issues on the new XDA 2021 website (preventing edition of long posts containing many links), full firmwares and OTA have been (temporarily ?) moved to post #4.
You'll have to scroll down by yourself, I can't even add a link to it
Spocky great work this looks fantastic,
you highlighted that you're not yet rooted and I've tried a few things so far that haven't worked however a few days ago one of the guys on the XDA forums has managed to access command line probably using the jtag points on the board. It's quite likely but this is a good way to get a ADB and then root access, and therefore if uses nandroid type tools he should be able to complete a full dump of the ROM.
I have a Chinese projector with same firmware as your own, but I'm hoping we can load the Android TV launcher interface as in the international version.
Let me know if you need anything specific tested.
Roms / Dumps
Warning: Full roms below can help you recover your device if you're stuck with a non functional projector. However, if your device shipped with a more recent firmware than the one you're trying to flash and has a more recent hardware revision, you might have display issues. So before flashing a full firmware, please try to boot to recovery and use the "wipe all data" option. On MiTv devices, this will basically do the same thing (this will automatically flash the device with the stock shipped firmware, which is present on the /backup partition).
MJJGYY01FM / FMWS01C / FMWS02C (Chinese Xiaomi Mi Projector / Wemax One) [rainman]
Full rom 1.3.63 (6.0.1.935) (thanks to @servo386 and rockpaperscissors)
OTA [user] from 6.0.1.935 to 6.0.1.1074 (1.3.63 to 1.3.74)
OTA [user] from 6.0.1.935 to 6.0.1.1218 (1.3.63 to 1.3.97)
OTA [user] from 6.0.1.935 to 6.0.1.1289 (1.3.63 to 1.3.105)
OTA [user] from 6.0.1.1074 to 6.0.1.1218 (1.3.74 to 1.3.97)
OTA [user] from 6.0.1.1218 to 6.0.1.1289 (1.3.97 to 1.3.105)
OTA [user] from 6.0.1.1289 to 6.0.1.1425 (1.3.105 to 1.3.105)
OTA [user] from 6.0.1.1289 to 6.0.1.1453 (1.3.105 to 1.3.105) (Latest Stable)
MJJGTYDS01FM / L1668FCF / L176FCN / L246 (4k Chinese Xiaomi/Mijia Mi Projector / Wemax A300 / Fengmi Cinema 4k) [batman]
Full rom 1.3.97 (6.0.1.312) ONLY FOR MIJIA
Full rom 1.3.105 (6.0.1.494) Owners of recent fengmi devices, use the rom below
Full rom 1.3.105 (6.0.1.669) Should be working on most recent Fengmi Cinema 4k, with hardware version l176_1. If yours is fm_10, it probably won't work (I still need a /dev/block/backup image of fm_10 hardware version)
Full rom 1.3.105 (6.0.1.724) Extracted from a recent Mijia 1S. Should probably work on most batman devices (people with fengmi 4k fm_10 stuck on a black screen, give it a try)
OTA [user] from 6.0.1.312 to 6.0.1.494 (1.3.97 to 1.3.105)
OTA [user] from 6.0.1.494 to 6.0.1.624 (1.3.105 to 1.3.105) (ONLY FOR MIJIA)
OTA [user] from 6.0.1.494 to 6.0.1.793 (1.3.105 to 1.3.105) (Latest Stable)
MJJGYY02FM (International Xiaomi Mi Projector) [anglee]
Full rom 8.1.0.1317 (OPM8.190205.001.1317)
Full rom 9.0.0.1911 (PQ3B.190705.003.1911)
L176FCNPro / L166FCN / L406FCN (Fengmi 4K cinema pro, 4k Max, C2) [jerry]
Full rom 1.2.1.1689 (only for Cinema Pro, more recent device should use the next one)
Full rom 1.4.6.2378 (use this one for Fengmi C2 and Max 4k. Cinema Pro should work fine too)
MJJGTYDS02FM (Mijia Projector Youth edition) [conan]
Full rom 1.3.97 (6.0.1.304)
Full rom 1.3.123 (6.0.1.519) (Prefer this version as it's probably compatible with most recent devices too)
TYY01ZM (Xiaomi Mijia Mi) [zodiac]
Full rom 1.3.67 (6.0.1.391)
M055FCN (Fengmi M055FCN) [doraemon]
Full rom 1.3.123 (6.0.1.309)
L206FCN-X2 (Fengmi Formovie T1) [nemo]
OTA [user] from 2.0.0.2289 to 3.0.0.3049 (Not final, but stable)
How to flash :
[OTA only] be sure your current firmware version is the same as the "from" version specified above.
Download and extract the zip file to the root of a USB thumb device and follow the procedure to boot into recovery mode. The full firmware or OTA update will be automatically installed (approximately 5 minutes will be necessary). You shouldn't lose any data (well, unless there's a power cut during the update process ). Even after flashing the full firmware, I still had my apps installed. I suppose you need to factory reset if you want a clean install.
Those willing to reinstall from scratch will need to use the "wipe all data" from the recovery menu. If you can't acces it somehow, you can try flashing a full rom (935 for rainman, 312 for batman *mijia* or 494 for batman *fengmi/wemax*), and then flash to the latest available OTA (you might need to chain flash if no direct OTA is available from you stock full rom to the rom you're targeting).
Please note that for a few users, the OTA won't install (it will stop during the update process with a chinese message). It's due to the fact that during installation, a check on the system files and kernel is made and at least one could not pass. This will be the case if you have rooted your device (only kernel is modified then). In that case, if you want to apply the update, you'll need to revert to an unmodified kernel/system. If you didn't modify system partition, restoring kernel partition (boot.img) should be enough (or uninstall Magisk from magisk manager app). If not, try restoring system.img also. If nothing works, reinstall from scratch (see just above)
wemax 7000
Great job !
I will try it tomorrow on my wemax 7000.
Let me know how I can help.
Should I also make a dump of my Chinese rom ?
How did you dump yours ?
I also badly hope to get the android tv rom working with the play store.
Thanks a lot !
Getting a wemax dump would be great indeed !
I did it with adb, connected wirelessly to my computer.
To do the same :
- download adb for your system
- connect wirelessly by using "adb connect IP.OF.YOUR.WEMAX"
- create a folder for the dump on your computer : "mkdir dump"
- go in it : "cd dump"
- pull system files : "adb pull /system"
Then every file that doesn't require root access will be downloaded to your computer. Just make a zip of it and upload it somewhere.
If it feels too complex for you, wait for a few days, I'll probably upload a tool to make an archive and automatically upload it somewhere. I just need to fix a few things before.
Hello, I'm the one who got root via the HDMI->UART diagnostic bridge. All credit goes to @loly though on 4PDA, who is the person who actually figured out this process on his Xiaomi Mi TV 4A, which has a similar chip to this projector so I took a guess that it would work too.
The posts I made on AVSforum are pretty long and lots of pictures and formatting so for now im just gonna link it but hopefully I can easily copy over the posts and make them here too.
https://www.avforums.com/threads/xi...aser-projector.2142037/page-101#post-26580089
Hi,
I installed the app and got a Chinese popup telling me that what I was doing was forbidden to users.
The menu is in Chinese too and I tried translating it with google translate but It's very tedious and I'm not very confident going through the menus.
Thanks a lot for the procedure for the backup.
I will cleanup all the installed apps and maybe reset it completely so that i can share the backup online.
If you're going to prepare a tool to do so, I will wait so I can test it as well.
Let me know if I can help you by sending you more infos.
Cheers
Jerome
Xiaomi Mi Laser Root Procedure
This is a long one. Also it was originally written for an audience who may have not been as familiar with Android/Linux commands so it has lots of explanation that might feel out of place on XDA.
So first and foremost ALL CREDIT BELONGS TO @loly ON THE 4PDA.RU FORUM WHO ACTUALLY DISCOVERED THIS PROCESS
https://4pda.ru/forum/index.php?showtopic=810785&st=3260#entry75802829
I definitely am just a copy cat who guessed that his process would also work on this device since their both Xiaomi TV devices with Amlogic T96* boards.
So if you read his post (which you definitely should in addition to this post in order to get the full picture of how this is done), you'll see that this is quite complicated and a kind of high level hack. I hope I'll be able to explain it enough and walk through it enough for it be fairly accessible for less technically inclined people who want to root their Xiaomi projectors.
What is required:
1. HDMI cable you can chop up or an HDMI breakout cable like this one: https://www.amazon.com/Adapter-signals-Terminal-Breakout-Connector/dp/B01CU9SHOO/
2. UART to USB adapter cable/board like this one: https://www.amazon.com/Adapter-Serial-Converter-Development-Projects/dp/B075N82CDL though there are cheaper options available
3. Cables/wires to connect both things. The USB UART package above comes with some, though you'll have to strip the ends to screw them into the terminals of the HDMI breakout board.
4. A spare USB drive
5. A computer to use the USB to UART adapter and a terminal program, i am using Putty.
So the basic idea behind this is that one of the HDMI ports (HDMI 1 in this case, the one closest to the edge) also serves as a diagnostic/UART port via 3 of the 19 pins of the HDMI. When this HDMI port is properly wired to the UART adapter, and you have a terminal open observing said port, upon boot the machine reads out all its startup stuff and when booting into recovery, gives you a completely liberated UNIX terminal that accepts input from the UART terminal, with full root privileges and busybox! As @loly says in his post, here we thank the people at Xiaomi for not bothering to secure this section and giving us full diagnostic root access with busybox. This is almost surely the way the developers of this machine would interact with this machine and developed for it. So let me try to explain how this works and how we get to TWRP and root.
Steps:
1. We need to properly connect the correct pins on the HDMI cable to the correct pins on the UART.
Here I am going to re-post some of @loly's images from the original thread, so all credit goes to him.
Here we see the pins we need. Pin 14 is our VCC, which in this 5v (the UART adapter im using has a switch for 3.3v or 5v, this switch needs to be set to 5v!) Pin 15 is the receive pin and Pin 16 is the transmit pin
The fourth lead we need is the GND (ground), which in the case of an HDMI cable is usually an un-shielded wire that connects to the the case of the connector itself.
I'm going to stop here for a sec and say this is why it's alot easier to use the HDMI breakout board over trying strip an HDMI cable and finding which wire corresponds to which pin (you need a multi-meter to do that)
its a small investment but it makes everything ALOT easier. On the HDMI breakout board, the ground terminal is pin 20.
the corresponding pins on the UART are pretty straightforward. VCC goes to VCC on the UART, pretty straightforward, on the other hand the RX pin of the HDMI (pin 15) goes on the TX OF THE UART makes sense right? the receiever of the HDMI should be listening to the transmitter of the UART and vice versa, so the TX pin of the HDMI goes on the RX pin of the UART. The GND pin (pin 20 on breakout board) goes to the GND on the UART.
Here's my setup. Sorry for the not very great picture. The terminal blocks on the HDMI breakout board work basically like you were connecting speakers to an amp, you unscrew the terminal till you see a little metal hole and you stick the stripped tip of the cable into the hole and screw the terminal back up till its snuggly holding onto the cable. You can use a multi-meter if you have one to make sure the wire is making contact with the terminal and even test the exact pin with the cable to make sure the connection goes all the way. If you're cable is making contact with the metal of the terminal, it is almost certainly correctly making contact with the actual HDMI pin, barring maybe a badly manufactured breakout board. I used spare MALE end pin connector cables to strip the ends and stick in the terminals, and connected them to the FEMALE connectors that came with the UART adapter. You don't necessarily have to do it this way, you can directly strip one of the female ends of the cable and connect the other female end to the pins on the UART, but you'll have a pretty short cable from HDMI to USB and you'll probably need a USB extension to comfortably use it with a computer.
So now you have you're HDMI diagnostic cable!
2. Setup your computer for UART and Putty.
Connect your UART to USB adapter to your computer. In Windows 10, it should automatically install drivers, but if it doesn't, your device should come with a link or something to download the drivers. I'm not going to get into the specific of how to install drivers on Windows computers but needless to say, you need to get the computer to recognize the device and properly utilize it via the drivers. Once you have it properly installed on the machine, it should show up in your device manager under Ports (COM & LPT) or something similar.
this is important because we need to 1. determine what COM port you're device is on and 2. change the baud setting.
So in the photo you see that it tells you what COM port is, which we need for later.
Now you need to go into the settings of the device and go into Port Settings tab
WE NEED TO SET THE BITS PER SECOND TO 115200!
Very important!
Setting up putty:
Basically open up putty and put the button on Serial, set the speed to 115200 and in the SERIAL LINE put the correct COM port number (COM1, COM2, COM3, ect)
Pressing enter on this should open a big blank black terminal with no activity. Thats good because its working. If it wasn't, you'd get an error about not reaching COM port or something.
3. Testing out our diagnostic cable with UART and Putty
Unplug your projector. Plug your HDMI into HDMI port 1 and connect your USB to computer. Open up a Putty terminal session as outlined above. If you get a big black screen with no errors upon launching the terminal, youre in a good spot.
Plug in the Projector. If you've done everything right you should get a big long readout of text scrolling by as it boots. If you get this, congratulations, you've accessed the diagnostic correctly!
The final step for actually accessing the usable terminal is doing the same but while booting into recovery.
4. Booting into recovery
Turn off your projector. Unplug it. Take your remote and hold down THE OK BUTTON and the BACK BUTTON at the same time. While still holding this, plug in the projector. It should start booting up. You're terminal Putty should be going crazy with text readout like last time. After a few seconds, let go of the buttons. Your projector should eventually end up on the Recovery menu, which is just some big buttons in english and chinese with a black background.
image courtesy of jaberwocky on AVS
After the readout in the terminal has stopped, press enter. It should skip to a new line with
Code:
~#
Tada, root! You're officially in a fully privileged root terminal in the underlying unix system of the projector.
This is the hard part of all this. If you've successfully reached this part, you've won the battle. Everything from here on out is just a couple of commands and some files being downloaded and transferred.
Launching TWRP, making a Nand dump, flashing Magisk, getting Root
So if you indeed have reached the point where, from recovery, you can enter commands into the terminal session, now the question what to with it. The answer is basically anything you want, but let's launch TWRP and go from there.
So here is where you need to download this zip file, also courtesy of @loly from the original russian thread. He went to the trouble of (I'm assuming) compiling his own TWRP for Xiaomi Mi TV 4A which, which as I've mentioned before it's chip (Amlogic T962) is the in the same family as the chip in our projector (Amlogic T968) so it works. That said I would say right now this is not a full TWRP specially made for our projectors, so we aren't going to flash it. We are going to launch it from the terminal (as per @loly's instructions) and use it, but not flash it to our recovery partition. This is for the best right now because a. it's not for our device and b. stock recovery allows us to install OTA updates if they come in the future
View attachment TWRP.zip
my attached version has only the twrp folders, no recovery image, no magisk included.
https://yadi.sk/d/uTUrwdAl3ZyUcN <---- original zip
Download that zip file and unzip its contents right into your USB drive, so that the folder `twrp` (lowercase) is in the root of your drive . This will make it easier to type the commands exactly as they appear later. Ignore the recovery.img, we're not flashing this onto this device.
The magisk included in the TWRP.zip is old by this point. I flashed Magisk 17.1 flashable zip, the latest stable as of this writing. Get it here https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip and put it on the flash drive.
A quick primer, this terminal instance has Busybox installed. Busybox is a "swiss army knife" of unix command like binaries because it packages all the standard linux commands into one single binary, so instead of calling
Code:
ls
to see the contents of the directory you instead would type
Code:
busybox ls
and it would work.
One last thing before I continue: while doing terminal stuff, I quickly learned that occasionally the terminal would throw up all kinds of gibberish which, as far as I can tell, had no rhyme or reason to it and more important had no discernible effect on what i was doing. Its a weird bug that maybe only ill experience because of my setup, I don't know. It would take two forms, one where it would throw up a bunch of lines of technical sounding text which included references to errors and such, but would ever actually affect anything. the other is when it would randomly spit out something like "hotplug_9" and again, id just press enter to get to the new line and nothing would have been affected. Don't be alarmed.
1. Insert USB drive into projector
Take your USB and plug it in. On your terminal, you should a small flurry of activity and references to a new device located at
Code:
/dev/block/sda1
or
Code:
/dev/block/sda2
take note of this, because this is the physical address of your USB drive thats going to have to be mounted. sda1 is the typical one, in my experience.
2. Mount USB and copy over files
This is just a series of commands, type them in precisely as I have them here, assuming you've maintained the same file structure on your USB stick as I did, unzipped the TWRP.zip straight onto the root of the USB.
Code:
busybox mount /dev/block/sda1 /sdcard
This mounts your USB device to the folder `/sdcard' if you're usb is at a different device location, change it appropriately.
Code:
busybox ls /sdcard
Just do a quick readout of the contents of `/sdcard` to make sure it properly mounted. you should see the contents of your USB drive listed here
Code:
busybox cp -r /sdcard/twrp/twres /
Copy the folder `twres` from the USB to the root of your projector
Code:
busybox cp -r /sdcard/twrp/license /
Copy the folder `license` to the root of your projector
Code:
busybox cp -rf /sdcard/twrp/etc/* /etc
Copy the contents of the folder `etc` to the etc directory on your projector
Code:
busybox cp -rf /sdcard/twrp/sbin/* /sbin
Copy the contents of the folder `sbin` to the sbin directory on your projector
Code:
busybox chmod -R 0750 /sbin
Change the permissions of the sbin folder to its all executable
So thats all the copying, now the moment of truth
3. Launch TWRP
YOU NEED A MOUSE PLUGGED INTO THE PROJECTOR TO NAVIGATE TWRP!
Code:
/sbin/run.sh
after hitting enter on this command, TWRP should boot up on your screen (and a bit of readout in your terminal
IF TWRP DOESN'T LAUNCH, YOU'VE DONE SOMETHING WRONG. GO BACK AND CHECK EVERYTHING.
I hope if you're doing this you're somewhat familiar with TWRP, but I will try to walk through the 2 most important things to do
4. Rom backup
One of the big buttons is BACKUP, go there and you'll see a series of check boxes for each of your partitions (boot, bootloader, recovery, system, ect). Select the ones you want (I selected all but I know for a fact this is unnecessary but I did't want to overlook anything and I didn't want to guess which I could ignore). It should ask you where to save the backup, select either the USB drive or internal memory and pick a folder. Slide over the thing to begin backup. It'll take a bit but eventually it should finish. Tada, you have a backup of your entire device.
5. Flash Magisk (ie get root)
This is the big kahuna, the one that unlocks everything OS-wide. Before trying to flash Magisk, we need to mount the system partition. This was big headache for me cause I didn't know why all the commands in the install scripts for failing and it was because /system/bin contains all the commands/binaries that Magisk installer script uses to do its stuff, so thats why we need to mount it first before trying anything. Go to the big MOUNT button and you should see checks next to USB and INTERNAL MEMORY or something to that effect, i can't remember off the top of my head. Almost certainly SYSTEM does not have a check next to it, meaning its not mounted. Click the check mark next to SYSTEM and that should be it, it is now mounted.
There is a quick way to check this, which is to go to ADVANCED>TERMINAL and in the terminal type
Code:
mount
if you get any sort of read out of device partitions, you're good, that means the mount command is working meaning the /system/bin is being made available to TWRP to execute commands.
With that done, go over to the INSTALL button on the home screen and navigate over to your USB stick and find the Magisk 17.1.zip. Select it. Check the check mark to reboot after install. Slide over the slider to begin the install. Moment of truth, you'll likely get to errors in big red text something like MOUNT -O BIND /SDCARD FAILED or something, thats fine, ignore it. It should go onto to say
Code:
|----Magisk Installer Script 17.1----|
or something like that, that means its doing its thing. Everything should go well and it should ask to reboot.
6. Verify root
Once you boot into the Xiaomi home screen after flashing Magisk, you should get some kind of thing asking to confirm that you want to install the application. That application is the Magisk Manager, which means you did it, Magisk installed successfully!
Go ahead and install some app that you know asks for superuser and it should prompt you for superuser access, grant it. You did it, you're root!
View attachment 4617430
jhordies said:
Hi,
I installed the app and got a Chinese popup telling me that what I was doing was forbidden to users.
The menu is in Chinese too and I tried translating it with google translate but It's very tedious and I'm not very confident going through the menus.
Thanks a lot for the procedure for the backup.
I will cleanup all the installed apps and maybe reset it completely so that i can share the backup online.
If you're going to prepare a tool to do so, I will wait so I can test it as well.
Let me know if I can help you by sending you more infos.
Cheers
Jerome
Click to expand...
Click to collapse
There's really not much this app can break (and not much to change neither). Most interesting thing would be the information page, along with the temperature page.
Concerning the dump, no need to cleanup anything as user data is stored :
- in /sdcard (internal memory) mount
- in app folder which can't be accessed without root
Dumping /system won't access any of them, this will basically only copy files that where part of the last firmware installed on your device.
As for my app, not sure I'll have time to finish it before next week.
servo386 said:
This is a long one. Also it was originally written for an audience who may have not been as familiar with Android/Linux commands so it has lots of explanation that might feel out of place on XDA.
So first and foremost ALL CREDIT BELONGS TO @loly ON THE 4PDA.RU FORUM WHO ACTUALLY DISCOVERED THIS PROCESS
https://4pda.ru/forum/index.php?showtopic=810785&st=3260#entry75802829
I definitely am just a copy cat who guessed that his process would also work on this device since their both Xiaomi TV devices with Amlogic T96* boards.
So if you read his post (which you definitely should in addition to this post in order to get the full picture of how this is done), you'll see that this is quite complicated and a kind of high level hack. I hope I'll be able to explain it enough and walk through it enough for it be fairly accessible for less technically inclined people who want to root their Xiaomi projectors.
What is required:
1. HDMI cable you can chop up or an HDMI breakout cable like this one: https://www.amazon.com/Adapter-signals-Terminal-Breakout-Connector/dp/B01CU9SHOO/
2. UART to USB adapter cable/board like this one: https://www.amazon.com/Adapter-Serial-Converter-Development-Projects/dp/B075N82CDL though there are cheaper options available
3. Cables/wires to connect both things. The USB UART package above comes with some, though you'll have to strip the ends to screw them into the terminals of the HDMI breakout board.
4. A spare USB drive
5. A computer to use the USB to UART adapter and a terminal program, i am using Putty.
So the basic idea behind this is that one of the HDMI ports (HDMI 1 in this case, the one closest to the edge) also serves as a diagnostic/UART port via 3 of the 19 pins of the HDMI. When this HDMI port is properly wired to the UART adapter, and you have a terminal open observing said port, upon boot the machine reads out all its startup stuff and when booting into recovery, gives you a completely liberated UNIX terminal that accepts input from the UART terminal, with full root privileges and busybox! As @loly says in his post, here we thank the people at Xiaomi for not bothering to secure this section and giving us full diagnostic root access with busybox. This is almost surely the way the developers of this machine would interact with this machine and developed for it. So let me try to explain how this works and how we get to TWRP and root.
Steps:
1. We need to properly connect the correct pins on the HDMI cable to the correct pins on the UART.
Here I am going to re-post some of @loly's images from the original thread, so all credit goes to him.
View attachment 4617376
Here we see the pins we need. Pin 14 is our VCC, which in this 5v (the UART adapter im using has a switch for 3.3v or 5v, this switch needs to be set to 5v!) Pin 15 is the receive pin and Pin 16 is the transmit pin
The fourth lead we need is the GND (ground), which in the case of an HDMI cable is usually an un-shielded wire that connects to the the case of the connector itself.
I'm going to stop here for a sec and say this is why it's alot easier to use the HDMI breakout board over trying strip an HDMI cable and finding which wire corresponds to which pin (you need a multi-meter to do that)
its a small investment but it makes everything ALOT easier. On the HDMI breakout board, the ground terminal is pin 20.
the corresponding pins on the UART are pretty straightforward. VCC goes to VCC on the UART, pretty straightforward, on the other hand the RX pin of the HDMI (pin 15) goes on the TX OF THE UART makes sense right? the receiever of the HDMI should be listening to the transmitter of the UART and vice versa, so the TX pin of the HDMI goes on the RX pin of the UART. The GND pin (pin 20 on breakout board) goes to the GND on the UART.
View attachment 4617377
Here's my setup. Sorry for the not very great picture. The terminal blocks on the HDMI breakout board work basically like you were connecting speakers to an amp, you unscrew the terminal till you see a little metal hole and you stick the stripped tip of the cable into the hole and screw the terminal back up till its snuggly holding onto the cable. You can use a multi-meter if you have one to make sure the wire is making contact with the terminal and even test the exact pin with the cable to make sure the connection goes all the way. If you're cable is making contact with the metal of the terminal, it is almost certainly correctly making contact with the actual HDMI pin, barring maybe a badly manufactured breakout board. I used spare MALE end pin connector cables to strip the ends and stick in the terminals, and connected them to the FEMALE connectors that came with the UART adapter. You don't necessarily have to do it this way, you can directly strip one of the female ends of the cable and connect the other female end to the pins on the UART, but you'll have a pretty short cable from HDMI to USB and you'll probably need a USB extension to comfortably use it with a computer.
So now you have you're HDMI diagnostic cable!
2. Setup your computer for UART and Putty.
Connect your UART to USB adapter to your computer. In Windows 10, it should automatically install drivers, but if it doesn't, your device should come with a link or something to download the drivers. I'm not going to get into the specific of how to install drivers on Windows computers but needless to say, you need to get the computer to recognize the device and properly utilize it via the drivers. Once you have it properly installed on the machine, it should show up in your device manager under Ports (COM & LPT) or something similar.
View attachment 4617379
this is important because we need to 1. determine what COM port you're device is on and 2. change the baud setting.
So in the photo you see that it tells you what COM port is, which we need for later.
Now you need to go into the settings of the device and go into Port Settings tab
View attachment 4617381
WE NEED TO SET THE BITS PER SECOND TO 115200!
Very important!
Setting up putty:
View attachment 4617383
Basically open up putty and put the button on Serial, set the speed to 115200 and in the SERIAL LINE put the correct COM port number (COM1, COM2, COM3, ect)
Pressing enter on this should open a big blank black terminal with no activity. Thats good because its working. If it wasn't, you'd get an error about not reaching COM port or something.
3. Testing out our diagnostic cable with UART and Putty
Unplug your projector. Plug your HDMI into HDMI port 1 and connect your USB to computer. Open up a Putty terminal session as outlined above. If you get a big black screen with no errors upon launching the terminal, youre in a good spot.
Plug in the Projector. If you've done everything right you should get a big long readout of text scrolling by as it boots. If you get this, congratulations, you've accessed the diagnostic correctly!
View attachment 4617385
The final step for actually accessing the usable terminal is doing the same but while booting into recovery.
4. Booting into recovery
Turn off your projector. Unplug it. Take your remote and hold down THE OK BUTTON and the BACK BUTTON at the same time. While still holding this, plug in the projector. It should start booting up. You're terminal Putty should be going crazy with text readout like last time. After a few seconds, let go of the buttons. Your projector should eventually end up on the Recovery menu, which is just some big buttons in english and chinese with a black background.
View attachment 4617401
image courtesy of jaberwocky on AVS
After the readout in the terminal has stopped, press enter. It should skip to a new line with
Code:
~#
Tada, root! You're officially in a fully privileged root terminal in the underlying unix system of the projector.
This is the hard part of all this. If you've successfully reached this part, you've won the battle. Everything from here on out is just a couple of commands and some files being downloaded and transferred.
Launching TWRP, making a Nand dump, flashing Magisk, getting Root
So if you indeed have reached the point where, from recovery, you can enter commands into the terminal session, now the question what to with it. The answer is basically anything you want, but let's launch TWRP and go from there.
So here is where you need to download this zip file, also courtesy of @loly from the original russian thread. He went to the trouble of (I'm assuming) compiling his own TWRP for Xiaomi Mi TV 4A which, which as I've mentioned before it's chip (Amlogic T962) is the in the same family as the chip in our projector (Amlogic T968) so it works. That said I would say right now this is not a full TWRP specially made for our projectors, so we aren't going to flash it. We are going to launch it from the terminal (as per @loly's instructions) and use it, but not flash it to our recovery partition. This is for the best right now because a. it's not for our device and b. stock recovery allows us to install OTA updates if they come in the future
View attachment 4617409
my attached version has only the twrp folders, no recovery image, no magisk included.
https://yadi.sk/d/uTUrwdAl3ZyUcN TERMINAL and in the terminal type
Code:
mount
if you get any sort of read out of device partitions, you're good, that means the mount command is working meaning the /system/bin is being made available to TWRP to execute commands.
With that done, go over to the INSTALL button on the home screen and navigate over to your USB stick and find the Magisk 17.1.zip. Select it. Check the check mark to reboot after install. Slide over the slider to begin the install. Moment of truth, you'll likely get to errors in big red text something like MOUNT -O BIND /SDCARD FAILED or something, thats fine, ignore it. It should go onto to say
Code:
|----Magisk Installer Script 17.1----|
or something like that, that means its doing its thing. Everything should go well and it should ask to reboot.
6. Verify root
Once you boot into the Xiaomi home screen after flashing Magisk, you should get some kind of thing asking to confirm that you want to install the application. That application is the Magisk Manager, which means you did it, Magisk installed successfully!
Go ahead and install some app that you know asks for superuser and it should prompt you for superuser access, grant it. You did it, you're root!
View attachment 4617430
Click to expand...
Click to collapse
Thank you for your time adding this post here and for the tests you've made to root this device. That's really cool !
If you have time, don't hesitate to post a full dump of your rom, we might learn a bit more than with mine.
Also I have not read your post from my computer so it might just be a bug, but Tapatalk reports your twrp.zip file as being 5 bytes only.
Edit: nevermind, your twrp is fine
I've ripped the "backup" archive that is a flashable update image of the stock image, used by the machine when you do "system restore" in recovery.
Basically here is the stock rom for the model 01 "rainmain" at last.
https://mega.nz/#!jY40SCQR!2gPjpPxzoDg3c1--pxGBR7qfKHxSyzWqU3eZGUz7kb0
#1 and #2 posts edited, adding many details, roms links...
Hi,
Thanks again guys for the effort you put on this.
I bought the hdmi breakout and a usb ttl and followed the instructions (very clear, thanks again for this) and backed up everything as you did but didn't root the device yet.
Are my .win backup files usefull to anyone (Wemax 7000) or do you need me to root the device to make the dump as spocky12 suggested?
I don't know how interesting my Chinese rom would be to others though...
Anyway it's good to know that we could flash the device with the android 8.1 rom when it will be available.
If you know anyone having the english rom, I would be willing to send him my cable to make a backup of his.
Cheers
jhordies said:
Hi,
Thanks again guys for the effort you put on this.
I bought the hdmi breakout and a usb ttl and followed the instructions (very clear, thanks again for this) and backed up everything as you did but didn't root the device yet.
Are my .win backup files usefull to anyone (Wemax 7000) or do you need me to root the device to make the dump as spocky12 suggested?
I don't know how interesting my Chinese rom would be to others though...
Anyway it's good to know that we could flash the device with the android 8.1 rom when it will be available.
If you know anyone having the english rom, I would be willing to send him my cable to make a backup of his.
Cheers
Click to expand...
Click to collapse
Thank you for your message. Glad you managed to follow @servo386's intructions. If you don't mind, I'd be interested in your .win files, to validate a few assumptions I have.
Concerning the international model, unfortunately, as of now, no owner seems to be willing to take the plunge. Hopefully it'll change soon enough.
For hackers out there, I found a tool that might prove helpful to build customs roms or repack roms using international model paritions (once somebody will dump it).
It's AMLogic Tools 5.5.0 that can be found here. I haven't had time to read the full thread yet. There might be valuable information there.
You can use it with the stock rom (935) from @servo386 that I specifically extracted and repacked with latest (1074) recovery (stock "backup" rom does not ship with recovery, which is needed by AmLogic Tools).
You can use the "customization tool" to easily extract/repack a rom that can be flashed in recovery or with special Amlogic USB flash tool.
There is also a tool that can "convert" a classic recovery to TWRP recovery (but supposedly only works with S905/S912. Might be interesting to check what is needed to make it work on our chip)
Unfortunately, I'm not an expert at building custom roms in Android (the latest custom rom I built was for Windows Mobile 6.1) (Great. I'm feeling old now ). I'm not quite sure what is allowed to be flashed with our bootloader. I haven't tried to flash anything yet, as if I brick the projector, my wife will probably kill me . But I suppose that if the custom built firmware doesn't embed bootloader/recovery, most errors will be recoverable by flashing the stock rom again.
If you want to test, don't forget to call the built rom "update-rainman.zip" and to put it in the root folder of an USB device along with this file.
Hey, it's me again
Some of you might be interested in an update to a more recent (but beta) version for wemax/chinese Mi projector.
I added a link to OTA from 1074 (1.3.74, built on May 4th) to 1189 (1.3.95d, built on Oct 12th) in the second post (yes, it's still Android 6.0.1)
To install it, just extract the zip file to the root of a USB thumb device and follow the procedure to boot into recovery mode. The update will be automatically installed (approximately 5 minutes will be necessary). You won't lose any data (well, unless there's a power cut during the update process ).
I haven't tested much, but here are the changes I've seen :
- most menus (settings) are in english now
- new settings options (the only one still in chinese) : automatic power off after 10 minutes of inactivity (doesn't seem to work, though)
- new volume UI
- Karaoke app added
- new animations during recovery installation
- wmv3 video format support added
As a side note, I've found a reference to an upcoming Xiaomi Laser projector in code, that wasn't there before : MiProjLAS2, codename batman.
spocky12 said:
...
I added a link to OTA from 1074 (1.3.74, built on May 4th) to 1189 (1.3.95d, built on Oct 12th) in the second post (yes, it's still Android 6.0.1)
...
Click to expand...
Click to collapse
Thank you so much for your work.
The file to update to the current beta is only 55Byte in size. Nothing happens when plugging in the USB stick.
===============================
I had two xiaomi laser projectors so far.
Projector 1 had dead pixels after 3 weeks of use. Here are the key figures from the engineering menu.
Here projector number 331 from 2018 calendar week 3:
It had a great contrast: 5382:1
The one complained to gearbest and got an exchange(Projector 2).
Here projector number 1196 from 2018 calendar week 13:
Contrast: 2441:1
Projector 2 unfortunately has too little contrast and is very blurred at the edges. Currently exchange projector 3 is on its way.
.bismarck
Thanks for your message. Comparing data from different projectors is really interesting.
Concerning the link, my bad, I've updated it to the right file, you can download it again if you wish.
Thanks spocky12, just loading the beta
When Projektor3 has arrived, I put the values from the menu here.
Edit: I copied the unzipped archive into the root of the USB stick. But nothing happens when inserting the stick.
.bismarck
You have to follow the procedure to boot into recovery. Either use :
- "ADB reboot recovery" if you have ADB
or
- unplug your projector, keep your remote "ok" and "back" pressed and plug your projector back in. It will boot into recovery and automatically start the update process.
(Your usb thumb drive should be formatted in fat32 and both files placed in its root folder).