Related
I got an update to mwd49b this evening. All I could find was some info for the Moto 360. Anyone know of any change logs? Looks like maybe just a security update.
gtriamy said:
I got an update to mwd49b this evening. All I could find was some info for the Moto 360. Anyone know of any change logs? Looks like maybe just a security update.
Click to expand...
Click to collapse
not recieved it but then I am on a custom rom..
quick search statets"This release of Android Wear featuring build version MWD49B, brings important security and stability improvements to the smartwatches."
but you already knew that... But now will stop others asking same question! LOL
gtriamy said:
I got an update to mwd49b this evening. All I could find was some info for the Moto 360. Anyone know of any change logs? Looks like maybe just a security update.
Click to expand...
Click to collapse
Are you have root on your watch?
alex6600 said:
Are you have root on your watch?
Click to expand...
Click to collapse
would be surprised if he is!
lohtse said:
not recieved it but then I am on a custom rom..
Click to expand...
Click to collapse
Before update, try to flash stock recovery.
alex6600 said:
Before update, try to flash stock recovery.
Click to expand...
Click to collapse
lol am rooted so if it follows the same as it does on ANY OTHER android device it would fail.... AM not undoing all your hardwork on you rom and kernel justs for this...
My statement was that if he is rooted I VERY much DOUBT it would have updated so he is most likely on stock recovery and rom plus unrooted..
alex6600 said:
Are you have root on your watch?
Click to expand...
Click to collapse
I'm not rooted.
gtriamy said:
I'm not rooted.
Click to expand...
Click to collapse
If you have access with adb to you watch- give pls output of:
cat /proc/version
OTA download URL MWD49B
OTA URL from reddit:
https://android.googleapis.com/pack.../72d654fa1e24110ad9843690ce967dd7503a0234.zip
size: ~16MB
reddit post with link to install howto:
https://www.reddit.com/r/AndroidWear/comments/4oss2p/android_wear_15_ota_list
@alex6600
There is a boot.img.p inside.
ranf said:
OTA URL on reddit:
https://android.googleapis.com/pack.../72d654fa1e24110ad9843690ce967dd7503a0234.zip
There is a boot.img.p inside.
Click to expand...
Click to collapse
Anyone can post /proc/version?
PS. I try to make update for rooted watch with custom kernel.
alex6600 said:
Anyone can post /proc/version?
PS. I try to make update for rooted watch with custom kernel.
Click to expand...
Click to collapse
Code:
[email protected] $ Android/Sdk/platform-tools/adb shell | tee -a mwd.log
[email protected]:/ $ uname -a
Linux localhost 3.10.17+ #1 SMP PREEMPT Thu Apr 21 20:34:29 CEST 2016 armv7l
[email protected]:/ $ cat /proc/version
Linux version 3.10.17+ ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Thu Apr 21 20:34:29 CEST 2016
[email protected]:/ $ cat /proc/cpuinfo
Processor<----->: ARMv7 Processor rev 4 (v7l)
processor<----->: 0
model name<---->: ARMv7 Processor rev 4 (v7l)
BogoMIPS<------>: 617.25
Features<------>: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt.
CPU implementer>: 0x41
CPU architecture: 7
CPU variant<--->: 0x0
CPU part<------>: 0xc07
CPU revision<-->: 4
processor<----->: 1
model name<---->: ARMv7 Processor rev 4 (v7l)
BogoMIPS<------>: 625.77
Features<------>: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt.
CPU implementer>: 0x41
CPU architecture: 7
CPU variant<--->: 0x0
CPU part<------>: 0xc07
CPU revision<-->: 4
Hardware<------>: Brooks 1.0
Revision<------>: 0000
Serial<><------>: 0000000000000000
[email protected]:/ $ ^D
I've received the update tonight.
Since last 6.0.1 update, I've problems with battery duration(difficulties to end full day) and GPS accuracy (buggy and lot of signal losts...). factory reset, wipe cache, etc... doesn't fix the problems.
With this new update, battery seems to last more time, 10% drain in 4 hours with screen always on, wifi on, etc..
Tonight I'll check If GPS problems where fixed, but sounds very good
I have just updated my SWR50 via Xperia Companion.
- I can confirm that the Reboot option is back.
- Camera bridge application is working again, so if I launch the Xperia Camera on the phone I can take photos with the button on the watch. (it was broken in the first MM release)
- Incoming phone call notification still has a delay but it seems faster than the previous release, however it is not as fast as it was in the last Lollipop. (the contact details of the caller appears after a few rings)
Gps problem fixed: great accuracy on 35 min run
Battery problem fixed: 10% battery use every 4 hours with always on screen.
Reboot option back to menu.
1 May 2016 security patch included.
Well I get we need a dev to repack this so we can flash it over Alex6600's rom or on a rooted watch etc so we can all play
just got the update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
redank said:
just got the update
Click to expand...
Click to collapse
Just got it too in Germany
Just got the update in Singapore. Can't wait to try the GPS fixes.
Sent from my Nexus 6P using Tapatalk
How can I install the OTA manually?
I got the update early yesterday here in Poland. When I got up in the morning the watch already had the notification about the update.
After applying it, the watch feels a little bit smoother and the battery is definitely better. I don't know anything about GPS, I've never used it, it's disabled. Reboot option is back, as was already told.
Sent from my D5803 using XDA-Developers mobile app
Here you will find latest firmware for MTCD_KD units.
Inside each rar file you'll find 3 files (dmcu.img, dupdate.img and info_MTCD_KD_Vx.xx_x.txt)
Please contact me for all the firmwares (newer or older) there's not in the list (Let's build a good bulk download area). I will upload and update ASAP the post with the firmware. Be sure you have both .img files and a plain text file (txt) with all the "Version info" screenshot like the ones below.
MCU version:
MTCD_KD_V1.82_1
Aug 26 2016 09:28:58
Android version:
5.1.1
Kernel version:
3.0.101+
[email protected] #92
Tue Aug 23 20:06:29 CST 2016
Build number:
rk3188-userdebug 25082016.09:47:50
Download (mega) 363.0 MB
MCU version:
MTCD_KD_V1.95b_1
Nov 2 2016 20:26:29
Android version:
5.1.1
Kernel version:
3.0.101+
[email protected] #237
Wed Nov 2 16:18:31 CST 2016
Build number:
rk3188-userdebug 02112016.19:56:40
Download (mega) 378.2 MB (Thanks to pb40!)
MCU version:
MTCD_KD_V2.06_1
Dec 20 2016 18:37:12
Android version:
5.1.1
Kernel version:
3.0.101+
[email protected] #39
Fri Dec 2 15:38:02 CST 2016
Build number:
rk3188-userdebug 19122016.20:49:30
Download (mega) 396.7 MB (Thanks to cupi1234!)
MCU version:
MTCD_KD_V2.06_2
Dec 20 2016 18:37:12
Android version:
5.1.1
Kernel version:
3.0.101+
[email protected] #39
Fri Dec 2 15:38:02 CST 2016
Build number:
rk3188-userdebug 19122016.20:49:30
Download (mega) 396.7 MB (Thanks to pb40!)
MCU version:
MTCD_KD_V2.16_2
Feb 10 2017 14:28:05
Android version:
5.1.1
Kernel version:
3.0.101+
[email protected] #80
Wed Jan 11 19:06:42 CST 2017
Build number:
rk3188-userdebug 09022017.00:46:00
Download (mega) 428.3 MB (Thanks to RazGame!)
MCU version:
MTCD_KD_V2.40_1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mar 16 2017 13:58:09
Android version:
5.1.1
Kernel version:
3.0.101+
[email protected] #207
Fri Apr 7 12:19:26 CST 2017
Build number:
rk3188-userdebug 14042017.02:02:55
Download (mega) 429.9 MB (Thanks to RazGame (mcu V2.40_1) and Kalti94 (Android 14.04.2017)!)
I changed MCU using 1.82_2 version but It is a KGL MCU version; are you sure it is correct file?
Same! It's wrong:
I'll try to search the correct one!
Notice me if you have the correct one
me too
It is a KGL 1.6v MCU version
Yap, I've bricked my unit due to the wrong MCU file, even if I thought it was for KD. I downloaded it from above link. Be sure what you post and be extra sure what you will flash on your unit. It is better to get MCU file directly from supplier.
Hello,
a new firmware for KD version 1.95 :https:...//1fichier.com/?u8w51aayog
and dmcu :https:...//1fichier.com/?9ml29nbddd
Any changelog?
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
On my car, a Peugeot 308 no modification for the moment since the V 1.82 but the apk parameter car works better with the canbus.
pb40 said:
Hello,
a new firmware for KD version 1.95 :https:...//1fichier.com/?u8w51aayog
and dmcu :https:...//1fichier.com/?9ml29nbddd
Click to expand...
Click to collapse
What about AF? In my HU, when I make a long trip, I lose broadcast, it seems like RDS (or AF) doesn't work properly
pb40 said:
On my car, a Peugeot 308 no modification for the moment since the V 1.82 but the apk parameter car works better with the canbus.
Click to expand...
Click to collapse
What do you mean with "the apk parameter car works better with the canbus"
Which parameters?
Thanks
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Looking forward to hearing how this is working. My KD unit is stable using @da_anton slimmed down ROM, so I am going to let you guys test this first. Please post if there are any changes that are noticible.
Since the Joying MCU file was working on the KD units, I wonder if the opposite is true.
Patton
The apk allows an access to the screen of the car on the canbus number 50.( for PSA 308) and I have no more an unexpected reboot on the long trip.
Which apk?
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
In the tray where you see all apps you have one preinstalled all named "control settings" the one with orange icon.
Inside the app you have a page named "control settings" again . In control settings you have soft keys that emulate input from the original RD4 or other stock radio installed by Peugeot. It allows you to access the menus on the EMF screen of the car (see picture attached)
Before that option was made available in the late September update you had no way to access these Peugeot settings. The only way to do something as simple as set EMF date and time was to attach back the original car radio set.
All of this may also apply to any car manufacturer/model where the original radio set have specific keys for accessing settings other than radio related ones.
In my KD HU I have installed JY MCU 1.90 and now installed KD 1.95b (the new one): I hope to improve AF function with this update
Just installed and everything works ok.
Tomorrow i'll test to see if i notice any improvements. Please post if you see anything new.
Main post updated with the .rar file (mega server)
colostro said:
In my KD HU I have installed JY MCU 1.90 and now installed KD 1.95b (the new one): I hope to improve AF function with this update
Click to expand...
Click to collapse
I'll try to install this firmware and will report. So far couldn't find AF working in any way. Radio is just lost and have to search for it again. I'm with Malaysk Octobre firmware, so do you guys think that installing this one can brick the device? I've read somewhere that reverting back to original FW from Malaysk one can brick the device (think on Joying site)... Although mine is not a JY, let's just hope it won't.
So far I've several issues regarding my Peugeot 308 MTCD-KD HU. Here's a brief list of them:
1) on a long trip (longer than 2 hours), the display goes blank and nothing helps to bring the UI back. Steering wheel buttons work, turning volume up or down shows the gauge on the display, but that's all and none of the UI parts are visible. The one and only solution is restarting the HU.
2) the USB devices (both 3G modem and a USB flash) get unmounted at random times. Frustrating when you're listening music from flash drive. SD card never got unmounted tho, so a 16GB full of music seems to be half a solution. I lose the 3G modem tho and it's always at random time, but it always unmounts. Tried to remove the modem and use the USB flash drive only to clear any doubts, but still the flash drive unmounts
3) Sometimes when I press the home button, launcher crashes...
4) (last but not least) sometimes GPS locks in seconds after I run my car and sometimes it takes more than 10-15 mins, sometimes it never locks. It sees many satellites, GPS antenna is on the dash, just behind the windshield, no problem with signal strength. GPS monitors prove the signal strength is high. I've read about Lollipop problems with GPS, so I wonder is it a possible reason and is there a fix, or even is there an Android 4.4 for my unit. If so - I'll gladly flash it.
Sometimes (rarely tho) the HU becomes very laggy, for example when I try to increase volume from steering wheel, it reacts after several seconds
The roms serve for all vehicles or each vehicle it's own rom?
Enviado desde mi SM-N910F mediante Tapatalk
Hello. I've also got KD 1.95b. Is it possible to make root and install Xposed? I want to install MTC-Service app.
karolp1993 said:
Hello. I've also got KD 1.95b. Is it possible to make root and install Xposed? I want to install MTC-Service app.
Click to expand...
Click to collapse
Yes, you can install Xposed.
When I can write a guide, I'll post the tutorial.
Stay tuned
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Inter981 please
They are suitable for all vehicles or you have to change something. I am waiting to receive from the supplier the rom mtcd_mx 1.97a_1 Nov 16.2016 is a Renault megane 3
Enviado desde mi SM-N910F mediante Tapatalk
---------- Post added at 08:52 AM ---------- Previous post was at 08:51 AM ----------
Enviado desde mi SM-N910F mediante Tapatalk
---------- Post added at 08:53 AM ---------- Previous post was at 08:52 AM ----------
Enviado desde mi SM-N910F mediante Tapatalk
Here’s my build of LineageOS 15.1 for Raspberry Pi 3 Model B and Model B+ (bluetooth does not currently work on the new plus model). It is unofficial and unsupported by the LineageOS team. It’s for advanced users only. This build currently uses Google’s SwiftShader software renderer so display performance is probably not what you’d expect. This build is not meant as a daily driver and it’s certainly not suitable for media device use.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://konstakang.com/devices/rpi3/LineageOS15.1/
lineage-15.1-20180706-UNOFFICIAL-KonstaKANG-rpi3.zip
https://www.androidfilehost.com/?fid=5862345805528041370
md5:257ade2f567223cf792023e2d75e5b75
Sources:
lineage-rpi
Thanks:
Google for Android Things platform
peyo-hd and everyone who’s contributed to android-rpi
LineageOS team & everyone who’s been working on LineageOS 15.1
How to install:
Follow the official Raspberry Pi instructions for writing the image to the SD card (Linux, Mac, Windows).
FAQ:
Q: I can’t find developer options, why?
A: Settings -> About phone -> Click ‘Build number’ several times
Q: I have no root, why? What is that hashtag on my status bar?
A: You need enable root access under Settings -> Developer options -> Root access. Root management is now integrated as part of LineageOS’ Privacy Guard and you can manage per app permissions under Settings -> Developer options -> Manage root access. You’ll have a persistent notification in the status bar when you’re running an app that uses root permissions.
Q: Settings -> Storage shows xx GB used by system. There’s unallocated space on my sdcard. What should I do?
A: This is a 4 GB image, remaining space on your sdcard will remain unallocated. Settings app shows unallocated space as used by system which in reality it is not. You can use e.g. GParted and extend /data partition (/dev/block/mmcblk0p4) to cover the unallocated space. Resizing the partition manually will break support for encrypting /data. Format /data in TWRP recovery (Wipe->Format data) after resizing to leave required space for crypto footer.
Q: Raspberry Pi doesn’t have power button, how do I power off/reboot my device?
A: Following keyboard keys work as Android buttons: F1 = Home, F2 = Back, F3 = Multi-tasking, F4 = Menu, F5 = Power, F11 = Volume down, and F12 = Volume up. You can also use one of many third party reboot applications.
Q: How to boot to TWRP recovery?
A: There’s currently no proper way to boot between Android and TWRP, but this can achieved by renaming the ramdisk you want to boot. Execute following commands in ‘adb shell’/serial console/terminal (you can enable built-in terminal app from Settings -> Developer options -> Local terminal) and reboot your device:
Code:
su
rpi3-recovery.sh
If mouse cursor doesn’t appear, try replugging your mouse.
Q: How to boot out of TWRP recovery?
A: You can execute the same script in TWRP terminal (Advanced->Terminal) if you have system partition mounted (Mount->System):
Code:
rpi3-recovery.sh boot
Or you can flash my recovery2boot zip in TWRP.
Q: How to install Google apps?
Download MindTheGapps-8.1.0-arm-XXXXXXXX_XXXXXX.zip and save it to your device’s internal storage or use an external USB drive
Boot to TWRP recovery (see FAQ)
Install MindTheGapps-8.1.0-arm-XXXXXXXX_XXXXXX.zip from your selected storage
Wipe->Factory reset!
Boot out of recovery (see FAQ)
Merged commits not mentioned in the changelog.
6.7. changelog:
update to Linux 4.14.53 kernel
add initial support for Pi 3 Model B+ (bluetooth does not currently work)
include TWRP 3.2.2-0 custom recovery (see FAQ how to boot)
build SwiftShader from source and update to master branch (improves graphics performance)
add support for encrypting the device
13.6. changelog:
update display drivers from Android Things 1.0
add support for USB webcams (UVC) with third party USB webcam apps
default to noop I/O scheduler
update to Linux 4.4.136 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 June 2018 (merged)
7.3. changelog:
update display drivers from Android Things DP 7
update wifi firmware
update to Linux 4.4.120 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 March 2018 (merged)
3.3. changelog:
initial release
Previous builds:
AndroidFileHost
Wow thank you very much. gonna test this on the 3b plus
Does this build support RCA video out. ?
reversegear said:
Does this build support RCA video out. ?
Click to expand...
Click to collapse
Not sure, haven't tried and I don't even have a display with composite video in to test with. I'd say with LineageOS 14.1 and Linux 4.4 it's not supported (https://github.com/anholt/linux/issues/14). LineageOS 15.1 has a much newer kernel (4.14) but it doesn't even use the VC4 driver (Google's SwiftShader software renderer is used instead) so IDK.
You'd likely need to modify config.txt at least if you want to test this. https://www.raspberrypi.org/documentation/configuration/config-txt/video.md
On my 3B I'm not getting any HDMI video output. It just shows a black screen.
__init__ said:
On my 3B I'm not getting any HDMI video output. It just shows a black screen.
Click to expand...
Click to collapse
Some displays might require modifying config.txt. https://www.raspberrypi.org/documentation/configuration/config-txt/video.md
720p is the max resolution this build currently supports.
Pie on Pi! LineageOS 16 booted on Raspberry Pi3.
KonstaT said:
Some displays might require modifying config.txt. https://www.raspberrypi.org/documentation/configuration/config-txt/video.md
720p is the max resolution this build currently supports.
Click to expand...
Click to collapse
alright, so do I have to build myself? I don't have a screen that small
__init__ said:
alright, so do I have to build myself? I don't have a screen that small
Click to expand...
Click to collapse
No, config.txt is in the boot partition (FAT) so even Windows should mount it when you plug in the sdcard. You need to use a proper text editor, though.
KonstaT said:
No, config.txt is in the boot partition (FAT) so even Windows should mount it when you plug in the sdcard. You need to use a proper text editor, though.
Click to expand...
Click to collapse
All three partitions are EXT4 and even when I mount them using Ext2Fsd I don't see config.txt in any of them. (I don't see bootcode.bin or start.elf either.) :/
Edit: I found it - the boot partition wasn't mounted on my PC for some reason :/
---------- Post added at 12:49 AM ---------- Previous post was at 12:09 AM ----------
It's still not working... I changed hdmi_group to 2 and hdmi_mode to 46 (I also tried 48)
__init__ said:
All three partitions are EXT4 and even when I mount them using Ext2Fsd I don't see config.txt in any of them. (I don't see bootcode.bin or start.elf either.) :/
Edit: I found it - the boot partition wasn't mounted on my PC for some reason :/
---------- Post added at 12:49 AM ---------- Previous post was at 12:09 AM ----------
It's still not working... I changed hdmi_group to 2 and hdmi_mode to 46 (I also tried 48)
Click to expand...
Click to collapse
Like said 720p is maximum supported resolution with LineageOS 15.1 build. hdmi_mode 46 and 48 are 1440x900 so that's not going to work of course.
You can try with a different display or try LineageOS 14.1 build.
KonstaT said:
Pie on Pi! LineageOS 16 booted on Raspberry Pi3.
Click to expand...
Click to collapse
Is this just a tease, or are you maybe gonna make available, I hope.?
mrmazak said:
Is this just a tease, or are you maybe gonna make available, I hope.?
Click to expand...
Click to collapse
If/when it's ready and I feel like it otherwise. Audio, bluetooth (on Pi 3 B), ethernet, display, and wifi already working to LineageOS 15.1 standards. It only started week three after the AOSP source drop so everything is still in very early stages. There's no Lineage apps, no Lineage features, no root, etc, and there's still some very basic UI issues.
LineageOS 15.1 Raspberry B+
Thanks for your rom
I dont find script rpi-display.sh for touchscreen like in lineageOS 14.1 Its possible to use this script ?
ericimbert said:
Thanks for your rom
I dont find script rpi-display.sh for touchscreen like in lineageOS 14.1 Its possible to use this script ?
Click to expand...
Click to collapse
I don't have any display hardware so I haven't tested. Some people have reported that LineageOS 15.1 works with the original 7" display but I don't know if they've made any modifications.
LineageOS 14.1 script won't work as is at least. You can try this one instead (https://pastebin.com/A2kfGhrR). Push to /system/bin/, set correct permissions (755) and run. I think you also need to change ro.sf.lcd_density in /system/build.prop to match the resolution change (in LineageOS 14.1 as well) but no one has given any proper feedback on that either.
Can someone do support for bluetooth 4.2 (for Rpi3B+), please ?
This rom is the first non official rom i could boot on my pi 3 B+ !!!!
tkx
go on working on this way
display performance is really really too poor
Version 1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Works with:
- Xiaomi Redmi Note 9
- Xiaomi Redmi 10X 4G
Build Date:
2020/05/13
Android Version:
QP1A.190711.020
Display ID:
AL2522-Merlin-V039-Q-0513
Build Fingerprint:
Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
Security Patch:
2019/12/05
Radio/Modem/Baseband Version:
MOLY.LR12A.R3.MP.V94.3
Kernel Version:
4.14.141-gf3c3c7a
Wed May 13 12:49:46 CST 2020
Download:
https://www.mediafire.com/file/lon7...V039-Q-0513_QP1A.190711.020_by-VD171.zip/file
Password:
Pass is in the attached file: PASSWORD_by_VD171.txt
How to flash it?
Use any scatter file specific for MERLIN.
Radio/Modem/Baseband properties:
Code:
md1_dbginfodsp=DbgInfo_DSP_MT6768_MOLY_LR12A_R3_MP_V94_3_2019_12_31_16_23.xz
md1_dbginfo=DbgInfo_LR12A.R3.MP_HUAQIN_Q0MP1_MT6769_SP_MOLY_LR12A_R3_MP_V94_3_2020_03_26_19_19.xz
md1_mddbmeta=MDDB.META_MT6768_S00_MOLY_LR12A_R3_MP_V94_3.EDB
md1_mddbmetaodb=MDDB.META.ODB_MT6768_S00_MOLY_LR12A_R3_MP_V94_3.XML.GZ
md1_mddb=MDDB_InfoCustomAppSrcP_MT6768_S00_MOLY_LR12A_R3_MP_V94_3.EDB
Prop.default:
Code:
ro.build.version.incremental=258
ro.odm.build.version.incremental=258
ro.vendor.build.version.incremental=258
ro.build.version.security_patch=2019-12-05
ro.vendor.build.security_patch=2019-12-05
ro.build.display.id=AL2522-Merlin-V039-Q-0513
ro.vendor.mediatek.version.release=alps-mp-q0.mp1.tc8sp2-V1.4_huaqin.q0mp1.k69v1.64_P1
ro.build.product=merlin
ro.product.board=merlin
ro.product.odm.device=merlin
ro.product.odm.model=merlin
ro.product.odm.name=merlin
ro.product.product.device=merlin
ro.product.product.model=merlin
ro.product.product.name=merlin
ro.product.system.device=merlin
ro.product.system.model=merlin
ro.product.system.name=merlin
ro.product.vendor.device=merlin
ro.product.vendor.model=merlin
ro.product.vendor.name=merlin
ro.build.flavor=merlin-userdebug
ro.build.description=merlin-userdebug 10 QP1A.190711.020 258 test-keys
ro.board.platform=mt6768
ro.build.id=QP1A.190711.020
ro.odm.build.id=QP1A.190711.020
ro.product.build.id=QP1A.190711.020
ro.system.build.id=QP1A.190711.020
ro.vendor.build.id=QP1A.190711.020
ro.bootimage.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.odm.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.product.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.system.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.vendor.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.build.tags=test-keys
ro.odm.build.tags=test-keys
ro.system.build.tags=test-keys
ro.vendor.build.tags=test-keys
ro.build.type=userdebug
ro.odm.build.type=userdebug
ro.system.build.type=userdebug
ro.vendor.build.type=userdebug
ro.bootimage.build.date=Wed May 13 12:41:51 CST 2020
ro.build.date=Wed May 13 12:41:51 CST 2020
ro.odm.build.date=Wed May 13 12:41:51 CST 2020
ro.product.build.date=Wed May 13 12:41:51 CST 2020
ro.system.build.date=Wed May 13 12:41:51 CST 2020
ro.vendor.build.date=Wed May 13 12:41:51 CST 2020
MD5 hashes:
Code:
APDB_MT6768_S01__W1953 -> 3adfe0c4e41828cd51ed783da774bd08
boot-debug.img -> e9dfb7dde67795157a871bc14b490054
boot.img -> d6e19a30d85a27379d91072665ad43c9
cache.img -> c40c137a18a26980d406d4ef0ccd7e61
cust.img -> e8c4e9f4ee0fe5052cf0dc356aedd8de
DbgInfo_LR12A.R3.MP_HUAQIN_Q0MP1_MT6769_SP_MOLY_LR12A_R3_MP_V94_3_2020_03_26_19_19_1_ulwctg_n -> b5bf654ddaacfd61e78c131f721974af
dtb.img -> ec4b37b164f1bd9ce6f2b1b911ac0872
dtbo-verified.img -> 9b0fa19089a0310325b88eebc8e41ae7
dtbo.img -> 9b0fa19089a0310325b88eebc8e41ae7
efuse.img -> 421f2cead0fbea555680b96136555941
exaid.img -> e8c4e9f4ee0fe5052cf0dc356aedd8de
lk-verified.img -> 0ba475d8c216b2613815b59e3db8da2b
lk.img -> 0ba475d8c216b2613815b59e3db8da2b
logo.bin -> 257508aa9cdeb690e4a4ed038c91ff76
md1arm7.img -> a0453e723dc84255940d7791740d06db
md1img-verified.img -> 27cd78644df092ade4ca03799dc3c2a3
md1img.img -> 27cd78644df092ade4ca03799dc3c2a3
md3img.img -> 9a9c185e3f6234103e5949716b9962d2
MDDB.META.ODB_MT6768_S00_MOLY_LR12A_R3_MP_V94_3_1_ulwctg_n.XML.GZ -> 4e040508c1878706a428c54ef0844e0f
MDDB.META_MT6768_S00_MOLY_LR12A_R3_MP_V94_3_1_ulwctg_n.EDB -> 7c1ecfd4e3d626957b6655f107824649
MDDB_InfoCustomAppSrcP_MT6768_S00_MOLY_LR12A_R3_MP_V94_3_1_ulwctg_n.EDB -> b24757bd125ad435bd2d26575b5c1d75
MT6768_Android_scatter.txt -> 0a8f16b2276ee9c37337a3937f71a7c8
preloader.img -> dbc21da31860042674fab69d07444e95
preloader_emmc.img -> dbc21da31860042674fab69d07444e95
preloader_merlin.bin -> bc7ebc0c2ca06b0d99856d595949e215
preloader_ufs.img -> 29ef0e631a45bf14555fd6b7adb7a7bf
product.img -> 7ec4f1ffd2b49d7c5b4f1bb5d3ba0dc6
ramdisk-debug.img -> b6048055b240d3c9f6933544b86416b5
ramdisk-recovery.img -> 77de275ef543e46bbedfd53b7e36f945
ramdisk.img -> 545ec84cf25662d1e4f4cf7e496fa56e
recovery.img -> 6362f1beb617572680f3fc91640d3767
scp-verified.img -> 2cac6177dc7eec82421cb3f4a2776aff
scp.img -> 2cac6177dc7eec82421cb3f4a2776aff
secro.img -> 096587b863e1252d67b1b8307291db09
spmfw-verified.img -> 40345cc1edec88bcd510fa62eac01739
spmfw.img -> 40345cc1edec88bcd510fa62eac01739
sspm-verified.img -> 0ceaf392e89bf70c9a52a5c91cc75865
sspm.img -> 0ceaf392e89bf70c9a52a5c91cc75865
super.img -> 542873466ecc6603c81758cf6a000390
super_empty.img -> a6d56d7a12d989bf31511d866449291d
system.img -> 27976b65c09bd01e7963a5f3db563fc7
tee-verified.img -> 4f2fdf78d5be3a5de0154c46af69d476
tee.img -> 4f2fdf78d5be3a5de0154c46af69d476
userdata.img -> 802561cd4739f2f0aae7a51890a5866f
vbmeta.img -> 31da88d4a00b99b36081f859f17f808a
vbmeta_system.img -> a6b560b53a42c98fba204f2b69e70fd7
vbmeta_vendor.img -> 86fae46d211bdedcb49bd08e901d4d3f
vendor.img -> 1a15f790bf6c32fb959da9bc4dfce6e4
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/
Can I flash this in MI Flash?
DavitidzeSh said:
Can I flash this in MI Flash?
Click to expand...
Click to collapse
I'm not sure. Maybe yes if your bootloader is unlocked.
You can try to flash this in MiFlashTool and then tell us, please
But, certainly you can flash this in SP Flash Tool.
VD171 said:
I'm not sure. Maybe yes if your bootloader is unlocked.
You can try to flash this in MiFlashTool and then tell us, please
But, certainly you can flash this in SP Flash Tool.
Click to expand...
Click to collapse
Well, the file format looks like Stock firmware fence the assumption. But I guess I'll go with SP flash since I'm a student and i can't afford to hard brick this
DavitidzeSh said:
Well, the file format looks like Stock firmware fence the assumption. But I guess I'll go with SP flash since I'm a student and i can't afford to hard brick this
Click to expand...
Click to collapse
Yes, it has all flashing scripts.
Taken care for NOT flashing the flash_all_lock script or your device will be locked again.
Sorry for the Noob question, but what's Engineering rom? Its a custom rom? And what changes from miui?
Thank you
jvfigueredo said:
Sorry for the Noob question, but what's Engineering rom? Its a custom rom? And what changes from miui?
Thank you
Click to expand...
Click to collapse
It is an OFFICIAL ROM by Xiaomi.
It helps engineers to make updates, bug fixes, new improvements and many other things on the device, because this rom does not have all the security steps and procedures.
In other words, it helps for DEBUGGING and DEVELOPMENT.
DavitidzeSh said:
Well, the file format looks like Stock firmware fence the assumption. But I guess I'll go with SP flash since I'm a student and i can't afford to hard brick this
Click to expand...
Click to collapse
Yes, you can flash with MI Flash. You might need to erase vendor and system.
VD171 said:
It is an OFFICIAL ROM by Xiaomi.
It helps engineers to make updates, bug fixes, new improvements and many other things on the device, because this rom does not have all the security steps and procedures.
In other words, it helps for DEBUGGING and DEVELOPMENT.
Click to expand...
Click to collapse
It is not OFFICIAL, it is not released to public. It has been released by Halabtech. and engineering rom is used as a base to build the stock rom for the device.
Also, please credit @ErdilS, as he provided the firmware originally.
Can
VD171 said:
Yes, it has all flashing scripts.
Taken care for NOT flashing the flash_all_lock script or your device will be locked again.
Click to expand...
Click to collapse
Can anyone tell me what is engineering rom i am tired but not able to find any answer and developer plzz tell me simply about engineering rom
[email protected] said:
Can
Can anyone tell me what is engineering rom i am tired but not able to find any answer and developer plzz tell me simply about engineering rom
Click to expand...
Click to collapse
Engineering rom is base firmware used by the company to test features and build stock rom for the device.
It is not for daily use, just for unbricking device.
Communos said:
It is not OFFICIAL, it is not released to public. It has been released by Halabtech. and engineering rom is used as a base to build the stock rom for the device.
Also, please credit @ErdilS, as he provided the firmware originally.
Click to expand...
Click to collapse
YES, this is leaked but it is OFFICIAL developed and signed by xiaomi.
Only Xiaomi can sign images with xiaomi signature.
Are you insane?
Do you mean halabtech has any developer on its team?
LOL, LOL, LOL.
Halabtech is just a (good) copier.
I've never seen anything developed by halabtech team.
Except some bat files compiled to exe... LOL, LOL, LOL.
( IF ANYBODY NEEDS ANY FILE UPLOAED TO halabtech, JUST TELL ME AND I WILL PROVIDE THIS FILE TO YOU FOR FREE ! )
[email protected] said:
Can
Can anyone tell me what is engineering rom i am tired but not able to find any answer and developer plzz tell me simply about engineering rom
Click to expand...
Click to collapse
Read this: https://forum.xda-developers.com/t/...dmi-note-9-redmi-10x-4g.4227933/post-84441883
I guess merlin can come under miatoll category
Jas Grover said:
I guess merlin can come under miatoll category
Click to expand...
Click to collapse
Unhappy, it can't.
Merlin, does NOT shares the same kernel with Curtana, Joyeuse, Excalibur and Gram.
It shares the same kernel of Redmi 10X 4G, Redmi 9 and Redmi POCO M2.
You can see this here: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/
Hello mod, if i flash this Rom, i may repair imei null for my device?
p233 said:
Hello mod, if i flash this Rom, i may repair imei null for my device?
Click to expand...
Click to collapse
I'm not a mod.
Engineering Firmware does NOT repair your imei.
It just allow you to enter in meta mode and use maui meta.
You need to do everything by yourself.
Talking about changing imei is not allowed on XDA, please don't ask about how to do that.
Good luck
VD171 said:
I'm not a mod.
Engineering Firmware does NOT repair your imei.
It just allow you to enter in meta mode and use maui meta.
You need to do everything by yourself.
Talking about changing imei is not allowed on XDA, please don't ask about how to do that.
Good luck
Click to expand...
Click to collapse
If you can post FRP bypass threads on XDA, You can talk about changing IMEI too.
Still waiting for you to credit @ErdilS, he got this for Redmi Note 9. Remember that you did not find this yourself, we brought it to you. Even the screenshot you posted is mine.
Forum rules clearly state you are supposed to credit the source.
VD171 said:
I'm not a mod.
Engineering Firmware does NOT repair your imei.
It just allow you to enter in meta mode and use maui meta.
You need to do everything by yourself.
Talking about changing imei is not allowed on XDA, please don't ask about how to do that.
Good luck
Click to expand...
Click to collapse
How enable meta mode and use maui meta in ROM 12.0.4 China (Redmi 10x 4G)? Thanks pro.
p233 said:
How enable meta mode and use maui meta in ROM 12.0.4 China (Redmi 10x 4G)? Thanks pro.
Click to expand...
Click to collapse
(Retracted)
Received a Play-systemupdate today (3rd one in past month). Size was 59MB.
The Play-systemupdate date moved from Dec 1, 2021 to Jan 1, 2022.
Also my Google Play store app updated to 29.0.14-21 (not sure if this is somehow related to the Play-systemupdate).
Since other people had already received this Play-systemupdate it is still a mystery to me what exactly the conditions are that trigger these updates.
Changes:
Code:
< com.google.android.ext.services |aml_ext_3111100| (311110010)
> com.google.android.ext.services |aml_ext_3113130| (311313000)
< com.google.android.hotspot2.osulogin | 12-8070528| (31)
> com.google.android.hotspot2.osulogin | 12-7999070| (31)
< com.google.android.modulemetadata | 2021-12-01S+| (311235024)
> com.google.android.modulemetadata | 2022-01-01S+| (311323004)
< com.google.android.networkstack |aml_net_3112130| (311213010)
> com.google.android.networkstack |aml_net_3113130| (311313000)
< com.google.android.networkstack.tethering | 12-8070518| (31)
> com.google.android.networkstack.tethering | 12-7936552| (31)
< com.google.android.permissioncontroller |aml_per_3112110| (311211010)
> com.google.android.permissioncontroller |aml_per_3113110| (311311000)
< com.google.android.providers.media.module | 12-8070517| (31)
> com.google.android.providers.media.module | 12-8012820| (31)
foobar66 said:
Received a Play-systemupdate today (3rd one in past month). Size was 59MB.
The Play-systemupdate date moved from Dec 1, 2021 to Jan 1, 2022.
Also my Google Play store app updated to 29.0.14-21 (not sure if this is somehow related to the Play-systemupdate).
Since other people had already received this Play-systemupdate it is still a mystery to me what exactly the conditions are that trigger these updates.
Changes:
Code:
< com.google.android.ext.services |aml_ext_3111100| (311110010)
> com.google.android.ext.services |aml_ext_3113130| (311313000)
< com.google.android.hotspot2.osulogin | 12-8070528| (31)
> com.google.android.hotspot2.osulogin | 12-7999070| (31)
< com.google.android.modulemetadata | 2021-12-01S+| (311235024)
> com.google.android.modulemetadata | 2022-01-01S+| (311323004)
< com.google.android.networkstack |aml_net_3112130| (311213010)
> com.google.android.networkstack |aml_net_3113130| (311313000)
< com.google.android.networkstack.tethering | 12-8070518| (31)
> com.google.android.networkstack.tethering | 12-7936552| (31)
< com.google.android.permissioncontroller |aml_per_3112110| (311211010)
> com.google.android.permissioncontroller |aml_per_3113110| (311311000)
< com.google.android.providers.media.module | 12-8070517| (31)
> com.google.android.providers.media.module | 12-8012820| (31)
Click to expand...
Click to collapse
Just received my first play update too
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I got this last night as well. Not long after it was installed I had my first random reboot. Hopefully it was just a fluke as it hasn't happened again.
I actually received 2 updates : the first one was just 597KB. Done it but after restarting it still showed December 1, 2021. I did manual check again, and got immediately 59MB. Now the date changed to Jan 1
DVD-XDA said:
I actually received 2 updates : the first one was just 597KB. Done it but after restarting it still showed December 1, 2021. I did manual check again, and got immediately 59MB. Now the date changed to Jan 1
Click to expand...
Click to collapse
This is the second one I just received
What are you guys play services? I havent gotten the latest one 22.02.19 yet or 29.1.0 on Play Store
Doug8796 said:
What are you guys play services? I havent gotten the latest one 22.02.19 yet or 29.1.0 on Play Store
Click to expand...
Click to collapse
22.02.19 (190400-424636017)
Nice. Haven't gotten it yet. I got impatient.. removed play services and tried redownloading the update and now stuck back on 21.48.15 oof.
29.1.10.
I wonder what the difference is between the 29 and the 22 versions.
TheForceUnleashed said:
29.1.10.
I wonder what the difference is between the 29 and the 22 versions.
Click to expand...
Click to collapse
29 is play store and 22 play services
Lycidias said:
29 is play store and 22 play services
Click to expand...
Click to collapse
Ah, thank you.
DVD-XDA said:
I actually received 2 updates : the first one was just 597KB. Done it but after restarting it still showed December 1, 2021. I did manual check again, and got immediately 59MB. Now the date changed to Jan 1
Click to expand...
Click to collapse
I just recieved the first one 597kb one, no sign of next update (even after manually triggering multiple times).
Still on December
Weird, when I check the menu item today, it just asked me to reboot the phone.
Doing a diff before/after, another package was updated:
Code:
< com.google.mainline.telemetry | 2021-11-01S+| (311104004)
> com.google.mainline.telemetry | 2022-01-01S+| (311300004)
foobar66 said:
Weird, when I check the menu item today, it just asked me to reboot the phone.
Click to expand...
Click to collapse
Exact same thing happened to me today.
foobar66 said:
Weird, when I check the menu item today, it just asked me to reboot the phone.
Doing a diff before/after, another package was updated:
Code:
< com.google.mainline.telemetry | 2021-11-01S+| (311104004)
> com.google.mainline.telemetry | 2022-01-01S+| (311300004)
Click to expand...
Click to collapse
Yeah I get that too
And today I finally got a update from January 1st. Why am I more than a month behind? :S
Unlocked as well.
No updates for me, so I sideloaded:
Play store
Play services and
Main components
Now I am on Jan 01 system update level.
Interesting to find out if the phone will automatically update to Feb or not
HtcDesire2 said:
No updates for me, so I sideloaded:
Play store
Play services and
Main components
Now I am on Jan 01 system update level.
Interesting to find out if the phone will automatically update to Feb or not
Click to expand...
Click to collapse
How the hell did you side load? Do you have a guide
Doug8796 said:
How the hell did you side load? Do you have a guide
Click to expand...
Click to collapse
APK mirror is your friend.
Srearch for latest APK for each of them. Get the right one for p6(arm64-v8a).
some APK require SAI (Split APK installer) - get if from play store.
install the apks and viola you are done.
Disclaimer: please use this at your own risk .
Which one did you get for play services? It said it had conflicts