By Following this guide, you will lose your warranty so keep that in mind before you begin. (Although you have probably already lost your warranty by unlocking the bootloader)
This guide will help you to flash any GSI (Project Treble) ROM onto your Redmi Note 10S, and since TWRP, or any custom recovery for that matter, is not yet available, we have to manually install the GSI roms using fastboot (and fastbootd because of the dynamic partition). The process is lengthy but not that difficult.
It should go without saying that you should backup everything and be prepared to lose your data and potentially soft-brick your phone and the experience with GSI roms is not always known to be stable (although I have not seen any such problems yet aside from a few easy-to-fix bugs) so do all of this at your own risk.
Important to note is that if at anytime you mess stuff up or delete partitions you weren't supposed to (whatever the guides may say, don't erase the product partition, it won't help, you're gonna end up in a bootloop) and soft-brick your phone, as long as you can access fastboot you can easily fix the problem by using the MiFlash tool which will help you get back to square one (you won't have to wait to unlock the bootloader again so don't worry about that)
Now, for the disclaimer:
DISCLAIMER: I'm an amateur in terms of tinkering with android stuff and phones in general. The process mentioned below has worked on my phone but I would still recommend waiting for someone more....experienced to weigh in his/her opinions. If you end up bricking your phone or if things go south, I'm not responsible, that's on you.
NOTE: When I mention fastboot I'm referring to the standard "normal" fastboot and when I mention fastbootd, I'm referring to the dynamic/userspace fastboot which is different (which wiil be indicated by the fastboot screens during either of the modes)
I should mention that using this method I have been able to flash DotOS, Android 12 Beta 5, CorvusOS (my current daily driver) and in my daily driver (Corvus OS), It's passing SafetyNet and the WideVine certification is still at L1 even after rooting, however I have tested neither Google Pay nor Netflix, because I don't use either of them so your mileage may vary, however I did find Netflix in the play store so that is a bit encouraging ig.
Alright, with the appetizers out of the way, let's crack on to the main course:
PART 0: Requirements:-
Please ensure that the following requirements are met:
A Redmi Note 10S with an unlocked bootloader
OEM Fastboot driver and Fastbootd driver is installed
A preferred GSI rom (the file extension should be .img)
Being prepared to lose your data
Obtain android platform-tools along with knowledge about how to use it
Acceptance that the newly flashed GSI rom may/may not be completely stable.
Fastboot rom from here
If you have all that, you can move on to the next step
PART 1: Get Straight to Flashin':
This guide is rather straightforward because there really isn't much to it.
To begin with, extract the vbmeta.img from the Fastboot rom. Once you have done that, reboot your phone to fastboot mode.
Once the phone is in fastboot mode, on your computer, run the following command:
Code:
fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img
to disable what is the android equivalent of window's secure boot
Once that is done, issue the following command:
Code:
fastboot.exe reboot fastboot
(No, there is no typo here, this is what needs to be done to enter the fastbootd mode, which is where the real fun begins)
Ensure that you are in fastbootd mode. The blue coloured "fastboot" text at the bottom will be replaced by a yellow coloured "fastbootd"
Okay, now for the most important command, type:
Code:
fastboot.exe -u flash system your_gsi_rom_of_choice.img
Done!
After this, don't forget to factory reset your device by:
Code:
fastboot.exe -w
Note: If you forget to do the factory reset, you're gonna end up with a frankenstein combination of your new and some configs of your previous rom, in this case reboot to bootloader (using power and volume down) and issue the factory reset command (fastboot -w)
And then for the toppings:
Code:
fastboot.exe reboot
That's.....about it. You should boot into your chosen rom. For the first time, the boot animation may stick around for a long time (5 minutes or more). However, if, even after an absurd amount of time (15-20), the rom doesn't boot up, try using MiFlash tool to get back to square one and try the whole process again.
Once it boots up, continue with the setup process and you will (hopefully) be at the home screen of your new rom.
PART 2: Le Bugs
Of course, no software is perfect and considering the especially ambitious nature of Project Treble, it is no surprise that you will encounter some bugs. 2 bugs in particular are the disabled headphone jack and the wonky brightness slider.
Here's how I fixed them in CorvusOS (most probably applies in other ROMs as well)
1. Disabled Headphone Jack:
Once you boot up the rom, you'll notice that the headphone jack will not work; the audio will only play on the speaker. To fix this one, you unfortunately need to root your phone (although that's not necessary, try looking into the Device Specific customisations of your rom).
Through your computer, issue the following commands (one-by-one, don't copy-paste them):
Code:
adb shell
su
setprop persist.sys.overlay.devinputjack true
reboot
Your phone will now reboot and once it does, you will see that the headphone jack is functioning normally again.
2. Brightness Slider Fix:
This one does not require any root. However, this does require that you can access the device specific customisations,
So, in my case, I had to go into {Device Name} Settings > Misc features and then tick the Force alternative backlight scale . Once you have done that, reboot and your brightness slider will be working properly again. Also, if you noticed sudden fluctuations after booting or when device goes to sleep earlier, that should all be fixed as well.
Conclusion:
At this point, you should be ready to rock the world along with your phone. Depending upon the rom you have chosen (DotOS for example), your widevine certification and safetynet may be compromised, even after trying out several fixes (which is what happened in my case). So if that happens to you, I suggest that you either change your rom, hunt around for some solutions or just, you know, live with it.
In my case, (As I mentioned before) I'm using CorvusOS where the widevine rating and safetynet are unaffected, with the latter requiring some special fixes.
Hope that helped. I look forward to hearing from you people about any recommendations or discussion. If you have any problem with the process or think that something may be wrong, post it in the replies and I'll be happy to get back to you (depending upon the time, of course)
How much extra battery life are you experiencing compared to stock? kernel tweaks? Any other minor bugs or issues while using it as your daily driver?
Can you please fill the listing for our rosemary device on GSI wiki @ github?
Xiaomi Redmi Note 10S
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
miravision said:
How much extra battery life are you experiencing compared to stock? kernel tweaks? Any other minor bugs or issues while using it as your daily driver?
Can you please fill the listing for our rosemary device on GSI wiki @ github?
Xiaomi Redmi Note 10S
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Better than stock, using gpu to render UI and powersave governor.
Xiaomi Redmi Note 10S
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Pre-flash info:
Device name: Xiaomi Redmi Note 10S (rosemary)
Earlier rom: MIUI 12.5.7 (India)
Rooted?: No
Tested images:
Corvus OS
Android 12 Beta 5
DotOS
Steps to installRefer to the guide here: https://forum.xda-developers.com/t/flashing-gsi-roms-on-redmi-note-10s-and-then-fixing-some-issues-all-without-any-custom-recovery.4337099/
Hardware Support post flashing
ComponentCommentCameraWorks but Gcam is a little unstableSpeaker/MicWorks, headphone jack requires a tiny tweakBluetoothNot tested but I'm sure it worksWi-FiWorksSIM/Mobile Data/ VoiceNot testedVoLTENot testedFingerprintWorksNFCNot testedOffline ChargingWorksDisplay Refresh rate60hz (same as before)Screen BrightnessWorks like before after a small tweakVolume scaleWorks fine5GN/ASafetyNet post root?
{
"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"
}
(requires modification)WideVine certification post flash and rootL1 (requires modification)
Personal Notes:
Battery life seems to have reduced a bit
Phone (extremely rarely) reboots out of nowhere.
Raven Launcher (Launcher that comes with Corvus OS) crashes from time to time, taking me back to the lock screen
I personally feel that the speakers are not as loud as they could be but I did not test it before flash so I can't tell precisely.
Tested by: randomaccessvemuri (@Tanmay-V22315)
miravision said:
Xiaomi Redmi Note 10S
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Pre-flash info:
Device name: Xiaomi Redmi Note 10S (rosemary)
Earlier rom: MIUI 12.5.7 (India)
Rooted?: No
Tested images:
Corvus OS
Android 12 Beta 5
DotOS
Steps to installRefer to the guide here: https://forum.xda-developers.com/t/flashing-gsi-roms-on-redmi-note-10s-and-then-fixing-some-issues-all-without-any-custom-recovery.4337099/
Hardware Support post flashing
ComponentCommentCameraWorks but Gcam is a little unstableSpeaker/MicWorks, headphone jack requires a tiny tweakBluetoothNot tested but I'm sure it worksWi-FiWorksSIM/Mobile Data/ VoiceNot testedVoLTENot testedFingerprintWorksNFCNot testedOffline ChargingWorksDisplay Refresh rate60hz (same as before)Screen BrightnessWorks like before after a small tweakVolume scaleWorks fine5GN/ASafetyNet post root?
(requires modification)WideVine certification post flash and rootL1 (requires modification)
Personal Notes:
Battery life seems to have reduced a bit
Phone (extremely rarely) reboots out of nowhere.
Raven Launcher (Launcher that comes with Corvus OS) crashes from time to time, taking me back to the lock screen
I personally feel that the speakers are not as loud as they could be but I did not test it before flash so I can't tell precisely.
Tested by: randomaccessvemuri (@Tanmay-V22315)
Click to expand...
Click to collapse
nope, for me it increased.
Personal Notes:
Battery life seems to have reduced a bit
Phone (extremely rarely) reboots out of nowhere.
Raven Launcher (Launcher that comes with Corvus OS) crashes from time to time, taking me back to the lock screen
I personally feel that the speakers are not as loud as they could be but I did not test it before flash so I can't tell precisely.
Click to expand...
Click to collapse
Has anyone faced these issues or any other issues and how did you fix them/ are they unresolved like random reboots or speaker loudness or mic loudness or noise cancellation or bluetooth HD codec support or bt calls or GCam crashes or instability ...
J6idot said:
nope, for me it increased.
Click to expand...
Click to collapse
Can we please see screenshots of battery drain from 100% to 1% with your app usage statistics in hours?
miravision said:
Has anyone faced these issues or any other issues and how did you fix them/ are they unresolved like random reboots or speaker loudness or mic loudness or noise cancellation or bluetooth HD codec support or bt calls or GCam crashes or instability ...
Can we please see screenshots of battery drain from 100% to 1% with your app usage statistics in hours?
Click to expand...
Click to collapse
Thanks for posting the screenshot. I see that you use AMOLED dark mode to save on battery. Any CPU underclock?
Do you happen to face overnight drain issue which is why for 2 nights battery graph shows 2 blank OFF durations?
With regards to the UX with powersave governor for the GPU can you please clarify the following on GSI ROM:
Can you please attach a short 30s - 1 min screen record session by randomly scrolling through stuff while playing some non copyright NCS audio to see if the g95 SOC is powerful enough to render, a full hd screen with scrolling content, smoothly enough with the least battery draining GPU frequencies?
Can you please clarify by means of some random media playing in the background that internal media sounds are recorded properly? Hence game sounds can be captured with/ without the microphone. Thanks
miravision said:
Thanks for posting the screenshot. I see that you use AMOLED dark mode to save on battery. Any CPU underclock?
Do you happen to face overnight drain issue which is why for 2 nights battery graph shows 2 blank OFF durations?
With regards to the UX with powersave governor for the GPU can you please clarify the following on GSI ROM:
Can you please attach a short 30s - 1 min screen record session by randomly scrolling through stuff while playing some non copyright NCS audio to see if the g95 SOC is powerful enough to render, a full hd screen with scrolling content, smoothly enough with the least battery draining GPU frequencies?
Can you please clarify by means of some random media playing in the background that internal media sounds are recorded properly? Hence game sounds can be captured with/ without the microphone. Thanks
Click to expand...
Click to collapse
Alright so, first of all, powersave governor underclocks to 500mhz -774 mhz. Some of the apps don't use the fully black amoled theme. And i keep my phone off overnight.
About the GPU? governor, same stock one because there is no way to change it/downclock it.
When scrolling, seems smooth to me, it might lag a little but i don't care.
And no, microphone doesn't lag.
Everything with CPU rendering (not GPU)
Hey OP, i would like to also add that few sGSI might completely soft brick the phone.
If you install an sGSI, reboot, and then it bootloops after like 5 seconds, the phone will not boot.
I tried one sGSI, got this problem, reflashed DotOS and it still wouldn't boot, as it would be stuck at the boot animation.
I tried:
Reflashing DotOS
Reflashing the boot image
Reflashing vendor/product
Formatting and wiping continuosly the userdata partition. Nothing.
The only way to fix this is by flashing stock.
Also, if your phone reboots after like 10 seconds or more, then bootloops, reflashing the rom you were using will probably work fine.
How well does the latest Android 12 GSI final release, available since a few days ago, work on the 10s?
Please post detailed review with bug fixes and patches required for various issues on the main rosemary treble GSI rom Github repository to help everybody track the progress on the final release of Android 12 on the 10s.
google gsi? idk, never tried.
Someone built it with phh patches and works fine, except you can't turn off the phone with the Power button, you need to do it from the status bar.
Hi, I installed DotOs 5.2 Android R with Gapps version;
Seems to be smoother than MIUI, and comes without so much bloatware, also, play store works better that in MIUI; I will test for a week, and then I will upload battery usage, and gaming performance in emulators like dolphin, citra, (also the bugs that I will encounter, for now, I encountered only 2 bugs, and the OP already solved them).
PD: There is another bug with bluetooth, you just need to go to settings-->PhhTrebleSettings-->Misc--> mark "Force-disable A2DP offload"
Have you stayed on DotOS or moved to a different GSI? Please post battery usage along with other points you mentioned that have gotten better or worse
seyren00 said:
Hi, I installed DotOs 5.2 Android R with Gapps version;
Seems to be smoother than MIUI, and comes without so much bloatware, also, play store works better that in MIUI; I will test for a week, and then I will upload battery usage, and gaming performance in emulators like dolphin, citra, (also the bugs that I will encounter, for now, I encountered only 2 bugs, and the OP already solved them).
PD: There is another bug with bluetooth, you just need to go to settings-->PhhTrebleSettings-->Misc--> mark "Force-disable A2DP offload"
Click to expand...
Click to collapse
if i want to try DotOS which version should i download? theres a64 and arm64, i haven't installed a custom rom on my phone for a long time.
ono123 said:
if i want to try DotOS which version should i download? theres a64 and arm64, i haven't installed a custom rom on my phone for a long time.
Click to expand...
Click to collapse
arm64 a/b
Is it possible to update using this method using this method? Would it just be this?
Code:
fastboot reboot fastboot
fastboot flash updated_image.img
RandomAccessVemuri said:
PART 2: Le Bugs
Of course, no software is perfect and considering the especially ambitious nature of Project Treble, it is no surprise that you will encounter some bugs. 2 bugs in particular are the disabled headphone jack and the wonky brightness slider.
Here's how I fixed them in CorvusOS (most probably applies in other ROMs as well)
1. Disabled Headphone Jack:
Once you boot up the rom, you'll notice that the headphone jack will not work; the audio will only play on the speaker. To fix this one, you unfortunately need to root your phone (although that's not necessary, try looking into the Device Specific customisations of your rom).
Through your computer, issue the following commands (one-by-one, don't copy-paste them):
Code:
adb shell
su
setprop persist.sys.overlay.devinputjack true
reboot
Click to expand...
Click to collapse
I have successfully installed the DotOS ROM after waiting for a week to unlock the bootloader. I want to inform that NFC can work well on DotOS. but I have a question regarding the headphone jack bug, how do I root this phone after installing the GSI ROM, the things you describe are not clear enough for me. can anyone explain further?
Can installing a different rom help with the video playback oversharpening, etc.? I mean all the miravision related issues. And what happends with HDR playback?
ono123 said:
I have successfully installed the DotOS ROM after waiting for a week to unlock the bootloader. I want to inform that NFC can work well on DotOS. but I have a question regarding the headphone jack bug, how do I root this phone after installing the GSI ROM, the things you describe are not clear enough for me. can anyone explain further?
Click to expand...
Click to collapse
Hi,
You can root the phone using the general procedure (or as shown here) But TL;DR:
Get the boot.img from the fastboot ROM (here)
Install the Magisk Manager APK (from official sources only)
Patch the boot.img with the magisk manager
Flash the boot.img by fastboot flash boot patched_boot.img
Reboot and open Magisk manager
It will prompt you to do some stuff after which your phone should be rooted (it should actually be rooted once you flash the boot.img and boot up the phone but Magisk Manager lets you manage superuser related stuff)
At this point your phone should be rooted and you can proceed with the above instructions. However I'm more than confident that you could fix the headphone jack by looking into the Device specific settings. That's how I fixed it in a later install, anyways.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About this Q&A thread for LineageOS
Use this area to ask anything you want related to LineageOS,
but try not to spam everyone, always search for an answer before.
LineageOS 14.1 for Sony Xperia Blue
Xperia T (Mint) : http://forum.xda-developers.com/-/-/-t3529554
Xperia TX (Hayabusa) : http://forum.xda-developers.com/-/-/-t3529555
Xperia V (Tsubasa) : http://forum.xda-developers.com/-/-/-t3529556
General Questions & Answers
Is root access included into LineageOS ?
No longer included by default to improve user security.
An addon is shared to add SuperUser features : https://download.lineageos.org/extras.
It will survive to updates the same way GApps do.
Go into Settings, About Phone. Tap "Build number" 7 times.
Go back, open Developer options. Change "Root access" option.
Do not use SuperSU unless you are sure, creates booting issues.
Read more about it : Here.
Is the ROM suited for daily usage ? Google Apps compatible too ?
Yes but work in progress. OpenGApps recommended.
Can I flash LineageOS on official and development builds, or even on CM without wipes ?
Migrations from unofficial to official, and from CM builds, are allowed with an experimental migration.
Read more about it here : http://lineageos.org/Update-and-Build-Prep/
Always remember to do backups before doing such changes.
Is the device encryption supported ?
State unknown. If you're coming from an older ROM
please read the details here : a07afb9660a86f702066003b8e81ab63789d1660
When USB connected to a computer, I can't access the storage ?
The phone is in charge-only mode by default on Nougat,
due to a stronger security logic regarding unauthorised data access.
Swipe down the notifications and change the USB mode.
I can't access the ROM's recovery with Volume-
You can either flash the boot.img from the newer Releases with "fastboot flash boot boot.img" or FlashTool,
or follow the instructions of the TWRP Recovery installation to update from TWRP.
Due to an unknown issue in data, the partition still looks like a 2GB
Although very unlikely, it may be possible that your data had an error
that could not be fixed automatically by the time you did the UserData Unification.
Read the ROM instructions and check downloads links on the device's LineageOS Wiki page.
Export the resize_userdata.zip from the unify_userdata zip (from UserData Unification),
and flash it from your recovery. If it works, problem solved.
Against advice, I upgraded without GApps and now it crashes. Any way without factory reset ?
Yes there is, but nothing assures you'll manage to do it fully & preserve all your data...
Once booted, keep saying Ok to all "Unfortunately, ... has stopped",
pull-down the notifications panel, press the Settings icon,
go in Apps, menu, Show System, scroll to Setup Wizard (green Android logo),
Permissions, and activate Contacts + Telephone.
Later, some Play Store apps may need reinstalling.
If not working, then I advise a clean factory-reset reinstallation...
About the battery failure on the Xperia T
If you experience battery issues, please read this : https://forum.xda-developers.com/showpost.php?p=70640214&postcount=8
The AOSP Keyboard does not support swipe gestures ?
Unfortunately the sources for swipe gestures are not available
and Google still requires their prebuilt library to be there for AOSP Keyboard.
Download the following libjni_latinimegoogle.so API 23 from OpenGApps
and push it to /system/lib/libjni_latinimegoogle.so using root access,
or use my one-time install zips : https://mega.nz/#F!ThEAkCRa!byhSwuoTbf6lnC1JxgKrig.
@Adrian DC will the ROM already Support OTA?
@ all
btw. this nice [MOD][SOUND][CM,AOSP][6.0+]SonySoundEnhancement&ViperAudio works with this first Build (Screenshots)
Sina Pack said:
Hello everyone
Which on better?!?!
CM13.snapshat or this ROM
Click to expand...
Click to collapse
Depends what is important for you :silly:
Both working Flawless. :good:
If you want to run MODs like Xposed you have to run Android 6.x (CM13) because the most MODs have no integration for Android 7 until now
If you want the new feautres of Android 7.x you shoud run LinageOS
First of all, a HUGE thank you for your work! Your ROM builds for the Xperia T brought my phone back to life, better than before. Now, I have installed the latest version of LineageOS 14.1, but I am experiencing a small problem. The ROM flashes TWRP 2.8.5 if I recall correctly, but that version does not have an F2FS option for file system. Can you please upgrade the TWRP to the newest version or skip flashing of recovery partition? Also, the TWRP in the AOSP build seems to play better with the device recognizing that Unified UserSpace thing Sony did to the Xperia T. My other problem is, that when I flash the LineageOS ROM, even though I formatted the /system and /cache partitions to F2FS with TWRP 3.0.2.0 after flashing the ROM, the /system partition reverts back to Ext4. Can you convert the ROM to have full F2FS support, maybe even including /data partition?
Also, does anyone have a problem, where you can make and receive calls, use Data connection but can not import contacts from SIM card? The contacts app and various SIM managers find 0 contacts on SIM card.
Your ROM is so awesome, thanks for this. But I see that Root Access options in my Developer Options include only "Disabled" and "ADB only", "App and ADB" option is missing. Can I ask you that this missing option is missing because of your setup ? And can I use your BootBridge to flash SuperSU for this ROM ?
First off thanks Adrian DC for keeping the Xperia T relevant! When I first hear that CM was going offline I immediately started looking for another phone, but I was elated to find out you had decided to work on Lineage OS. I flashed the latest ROM 2 nights ago and I can say that this update is much more quicker and stable for me at least than the last CM 14.1 that I was running from the Christmas night upload. I did notice the Root issue and am not concerned about that right now. The one thing I am concerned with is that I seem to be running through some battery. Is anyone else seeing this issue, my battery life is terrible right now. Thanks again for the great work!!
About battery failures and instant power-offs
Here's a small report about the Xperia T battery failure that I also experienced :
As a few of you reported already, it is quite known that the Xperia T
has a battery that does not survive nicely to years of heavy usage.
Released and sold in 2012, the Xperia T has an inbuilt battery that is not meant to be replaced,
the model is a 3.7V 1780mAh 6.6Wh battery with integrated controller and 3 pins clip plug.
The issues seen when the battery is about to die are random battery drops during reboots
(20+% disappear randomly, reappear later sometimes), below 15% the device goes off fast,
and recharging the device with a wall charger goes high quite (too) fast.
When the battery is truly dead, the device powers off randomly under heavy usage,
for example while taking a picture and the autofocus starts moving or using an USB drive.
Random power-offs also occur while using the device a lot like charging + GPS and such.
The biggest issue is that under a very low level of battery depletion, the device won't power on anymore
even if plugged to offline charge it, only 3 red lights will flash and the device will never boot again.
A solution I found to work multiple times with that situation is to open the device's back (really easy on the T),
unplug the battery plug, connect the USB cable from a wall charger, wait 1-2 seconds,
then directly replug the battery in place to see the device boot in offline charger.
Then leave the phone charge to 100% without interaction.
Small unsure side-effect, after 2 weeks of these mentioned issues, I stopped reviving it,
and ordered a new battery, but the MicroSD was fried. Likely related to the failure but no proof.
About replacing the battery on the Xperia T :
I ordered a "brand" new battery for the Xperia T, the goal is to absolutely avoid fake copies
and try to find a battery identical and original from Sony, otherwise results are unknown.
I bought my battery for 9€ therefore it stays a decent revival of a device that runs properly.
Replacing the battery involves removing the main motherboard flex that goes over the battery,
slightly bend it away from the battery without harming the triple flex plugs on the base of the battery.
Then removing the battery with a bank card takes some work but goes fine with patience.
Harming the flex at the base has to be avoided at all costs, battery can be removed slowly
with an angle to avoid unplugging the flex or touching it in any way.
Boot the battery with my technique and let it charge to 100%.
Then rebuild the device, it should be back to normal usable status.
Posted this as small hints for those experiencing the Xperia T battery issues.
Hi, think my problem fits better in here than in the XT-LineageOS-thread:
Since upgrading to LineageOS14.1 (29.1.17) I can't access the external SD-Card; Lineage-FileManager tells me to try it with root-rights (yea...)
Pretty sure it must be one little "Switch" to trigger, but I have no idea... Thanks for any hints
----------
As for the Battery-Issue:
I had that one several times, but no need to replace it:
First time I encountered it, I installed PacmanROM (think based on Android 5; nothing to loose when the battery is dying, right?) - battery worked well again, for another year - then showed the same "drop to 20% and gone"-symptoms; to revive, I installed CM12 - solved the problem; again one year later (last summer), again the battery... Installed CM13 (thanks Adrian - solved the problem again.
(...thinking about it, maybe I installed CM14.1 too early? ) Everytime, the XT had its old "run-time" (of about 4 days) back it had when first activating it in 2012; before upgrading, the battery hardly lasted one day...
I always made a clean-install including TWRP-upgrades... Maybe a change to a higher version triggers a setting in/for the battery? (eg. "planned obsolency")
---------
Edit:
took a shortcut with the SD-Card; as I could access it via USB I copied all data from it, inserted it back to the XT and initialized it (as external). With the newly possible access, I copied the files back. Seems to be working...
Have a problem with Wi-Fi on Xperia T (mint)
Status bar and settings say "connected, no internet", PlayStore "Check your connection an try again", so I can't install an application.
But Browser is working fine, searching for updates in "About Phone" too, means I have internet.
Have official Lineage Nightly 31st january.
I have already installed it for three times and tried another Wi-Fi, but doesn't work.
ArmW said:
Have a problem with Wi-Fi on Xperia T (mint)
Status bar and settings say "connected, no internet", PlayStore "Check your connection an try again", so I can't install an application.
But Browser is working fine, searching for updates in "About Phone" too, means I have internet.
Have official Lineage Nightly 31st january.
I have already installed it for three times and tried another Wi-Fi, but doesn't work.
Click to expand...
Click to collapse
Seems like your phone can't connect to the preferred DNS server at the moment.
try changing that.
Camera touch focus not working
I recently installed latest build of Lineage OS for xperia Tx. Touch focus for default lineage camera is not working. I am not sure if it is my phone or the lineage os?
farooq666 said:
I recently installed latest build of Lineage OS for xperia Tx. Touch focus for default lineage camera is not working. I am not sure if it is my phone or the lineage os?
Click to expand...
Click to collapse
It was missing for me too, reverting back to the lineage-14.1-20161231-UNOFFICIAL-mint build fixed it, but it did not fix my issue with the SIM contacts Did you try the builds from the official Lineage OS website?
What about battery life in TX? I'm planning switch back to Xperia T or TX cuz by now I'm using a Moto E 2nd Gen LTE and it doesn't work with the 3G/4G band of my carrier and Moto E's cameras sucks
Btw I saw that in Amazon (See attachment)
As far I'm concerned change the battery of T is a pain in the ass, So is better try again with a TX, isn't it?
farooq666 said:
I recently installed latest build of Lineage OS for xperia Tx. Touch focus for default lineage camera is not working. I am not sure if it is my phone or the lineage os?
Click to expand...
Click to collapse
jkristof94 said:
It was missing for me too, reverting back to the lineage-14.1-20161231-UNOFFICIAL-mint build fixed it, but it did not fix my issue with the SIM contacts Did you try the builds from the official Lineage OS website?
Click to expand...
Click to collapse
It's works in '20170214' build
Hi,
I am experiencing recently SoDs again.
I am using a Xperia V (tsubasa) just as a music player.
So only pure LinOS 14.1 without GApps.
It happens always during the night and if it is not charged.
Last night the battery was below 20% when it happened. The other times before I did not pay attention to the battery.
Battery was chenged in 10/2017 and was a new one.
Also I must say the RAM usage is very high. The Android system alone consumes 325MB. But I am not sure if it is related to the SoD.
AdrianDC,
Is there a way to extract the cast feature from the ROM and install it on other devices? Cast in Lineage OS is awesome and works flawlessly, and Samsucks screen mirroring doesn't even work on my same brand TV from my tablet, but Cast works every time.
Gallery shows images twice
After upgrading to lineage-14.1-20170310 (Xperia V), every Gallery-App (Stock, Gallery from F-droid) or Apps with access to images are showing every image twice. Properties of the "gemini-images" will show different paths,
i.e.
/sdcard/Pictures
/storage/emulated/0/Pictures
or
/sdcard/Download
/storage/emulated/0/Download
Has anyone else encountered this issue, too?
unifying the user data trouble guide
I wrote this in the hope this will soon be obsolete. I never succeeded installing lineageOS the official way. I had reproducible errors unifying the user data. I also hard bricked a Xperia V. I wrote a workaround step by step guide which will hopefully work not just for me. I know it sounds a bit crazy but as I did it quiet often and always succeeded by miracle, I wanted to find a reliable way. Everybody interested in the trouble which happens sometimes see attached recovery logs. This guides logs are in the folder UnifySucess. To find the interesting part search for mmcblk0p14. Perhaps it's also useful for diagnostics.
this is made on XPERIA V, if you want to follow this guide for another model you have to replace the files with tsubasa in its name.
EDIT: this is obsolete now
files used:
twrp-3.0.3-20170224-boot-tsubasa.img
recovery-13.0-20161221-SNAPSHOT-ZNH5YAO3Y8-tsubasa.img
lineage-14.1-20170303-nightly-tsubasa-signed.zip
unify_userdata-20170128.zip
restore_sdcard-20170128.zip
cleaner-fota-tsubasa.zip
coming from stock
fastboot flash boot twrp-3.0.3-20170224-boot-tsubasa.img
fastboot reboot
in TWRP
wipe System, Cache, Data, Legacy SD
flash unify_userdata-20170128.zip twice
if there is a failure ignore & flash lineage-14.1-20170303-nightly-tsubasa-signed.zip , gapps (optional)
reboot system ( not sure if necessary )
look into settings if storage is OK, you are done if not reboot bootloader
fastboot flash boot twrp-3.0.3-20170224-boot-tsubasa.img
fastboot reboot
in TWRP
flash restore_sdcard-20170128.zip twice
reboot to bootloader
fastboot flash boot recovery-13.0-20161221-SNAPSHOT-ZNH5YAO3Y8-tsubasa.img
fastboot reboot
in CWM
full factory reset
flash unify_userdata-20170128.zip twice
reboot to bootloader
fastboot flash boot twrp-3.0.3-20170224-boot-tsubasa.img
fastboot reboot
in TWRP
Internal Storage should now be bigger than 2GB, if so
flash lineage-14.1-20170303-nightly-tsubasa-signed.zip , twrp-3.0.3-20170224-fota-tsubasa.zip, gapps (optional)
If you are stuck and already installed the twrp-fota-tsubasa.zip there is a tool from AdrianDC to remove TWRP called cleaner-fota-tsubasa.zip
this is written in the hope to be useful, I'm not responsible for any failures.
guide update
I tried once with TWRP 3.1.0-0 and it did the trick - not initial but instead of CWM.
I am happily hoping not to need the recovery-13.0-20161221 and the cleaner-fota anymore.
@xperanto: I took a short look into the gallery after a clean install and there were no doubles
DISCLAIMER:
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
INTRODUCTION
This thread is mainly intended for devs (pro devs don't really belong here because they're pro and this thread is useless), for someone who need help to continue the work for Nova and fix the bugs on Pie (not many left). I'll help as long as you can speak English xD (no google translate because it can cause misunderstandings). However, don't expect me to spend the same time into this as i''ve did when i've had the phone. Yes, i no longer have the phone (it's still dead) and if you're not up to date with that, then you can read the announcement here and i've mentioned that i've got a new phone here. On top of this, i can't build anymore because i can't sign up on Google Cloud Platform anymore. I've wrote about this here at the hidden content (below as a side note).
Users can also help with doing researches, testing things and logs.
I don't know if i'll consider to continue working on it myself alone without the phone. I'd need at least to be able to build and then i'd need people to test new builds / flashable zips. At some point i might consider that because i'm missing this phone and the community xD.
SOURCES
Device: https://github.com/skinzor/android_device_huawei_hwcan/tree/lineage-16.0-last
Vendor: https://github.com/skinzor/proprietary_vendor_huawei/tree/lineage-16.0-last
Kernel: https://github.com/skinzor/android_kernel_huawei_msm8953-1/tree/lineage-16.0-last
Click to expand...
Click to collapse
There's two branches:
1) lineage-16.0: those ones were used when i've booted Pie the first time. Remember that i've wrote about it here? Those ones were updated from mido's ones.
2) lineage-16.0-last. those ones are the last ones and updated, which i've used in my last build. Those ones were continued from previous branch and updated from tissot ones which were / are updated by another dev (not the same dev as on mido). I recommend to continue with this branch, but it's up to you. You might not be able to get a successful or bootable build anymore with lineage-16.0 branch anyway because lineage's sources were updated since then.
I've used mido's trees as reference for lineage 14 and 15 trees too. You can figure that yourself if you check mido's trees and then Nova's ones, as i've cherry-picked the commits. Why did i use mido's trees? Because:
1) It has the same qcom chipset as Nova.
2) It is a popular phone.
3) A good dev was working on it.
4) It has official lineage support.
Now you might ask why i haven't did myself everything from scratch. Well, as a newbie dev, it would've been much harder and would've took much more time. Also, i'd say that there's no point at all to do something from scratch when it was already done unless you want to go the "hard" way, assuming you have time and want to learn more. I've still learnt a lot since i've started.
There are "universal" commits which are about fixes / improvements that can be related to e.g. the android version or the qcom chipset and those commits are usually found in many device trees, so you just cherry-pick them. A good example would be this commit: hwcan: Use mke2fs to create ext4 images.
FIXING THE BUGS OF LINEAGE 16 / PIE
I assume that you've used lineage-16.0-last branch as i've recommended. I no longer remember what bugs had my last build, but i think that the bluetooth was working, while it wasn't working in the build made from old lineage-16.0 branch. However, i remember that it had a new bug and as far as i remember, it was the RIL, but the baseband was showing up. I think i've tried to fix it and i've got it working (i remember that it was about the blobs), but i don't remember how. As of typing now, i've looked into the logcat which i still have and i've seen this:
Code:
F linker : CANNOT LINK EXECUTABLE "/vendor/bin/tftp_server": library "liboemaids_vendor.so" not found
That kind of error is self explanatory: the blob / lib is missing. After i've seen this, i've remembered that it's a new blob which got added in the original commit and which i've cherry-picked here. I didn't include that blob for a reason, but i don't remember that reason lol (it's not that i've forgot it, but i've skipped it for a reason). I remember that back then i've added the blob manually after i've seen the error, but i don't remember if that's what fixed the RIL, so you can try that and let me know.
As i've said already, i don't remember what bugs had that build besides the RIL, so you can try it and let me know.
At the introduction i've mentioned that i can help. I'll help only here on XDA in this thread because it may help other people too if they're having the same error / problem and after all, it's nice to have a thread like this in my opinion.
You can attach the log or paste it to gist github, pastebin, del.dog or any pasting website, but don't paste it in the XDA post because it just sucks.
Click to expand...
Click to collapse
DOWNLOADS
MEDIAFIRE | ANDROIDFILEHOST
As i've recommended to use lineage-16.0-last branch to build / continue the development, i also recommend to flash that build.
The build from lineage-16.0 branch folder doesn't boot. Back then, when i've seen that it doesn't boot and took a look at the logcat, i've tried the graphic blobs from the tree of zenfone 3 and that one was using them from nokia 7 plus (based on the commit). I had two zips in my PC and i've uploaded both. The first one created is graphic_pie_blobs_zenfone3_nokia_7_plus.zip and the second one sdm_blobs_zenfone3_nokia7_plus.zip, so you flash them in that order. As i've mentioned in that post in which i've said that i've booted Pie, there is some lag / glitches while scrolling, due the display / graphic blobs.
ENDING
As i've promised, i've pushed the tree sources and uploaded my first and last build. The reason i'm willing to help in fixing the bugs is because i'm missing this phone and this community here on XDA (as i've expected xD). It was fun and thanks to this phone and y`all for your support and kind words, i've learnt so many things in this journey. That's simply unforgettable for me.
Hopefully someone will jump on and continue the development further. I'll be here to help.
XDA:DevDB Information
[DEV][9.0] LineageOS 16, ROM for the Huawei Nova/Nova Plus
Contributors
#Henkate
Source Code: https://github.com/skinzor/android_kernel_huawei_msm8953-1/tree/lineage-16.0-last
ROM OS Version: 9.x Pie
ROM Firmware Required: Unlocked bootloader, TWRP
Version Information
Status: Testing
Created 2019-01-02
Last Updated 2019-01-05
Reserved
Reserved
Thank you for all the hard work you put into this. I would try to follow the leads, but for me this phone is dead now. I had hoped it would be something, but naw, just a hunk of something. Maybe someone can pick it up and go with it, encouraged everyone to try. If you are thinking about it Robert @#Henkate will help you. Great person, and this phone got me to know him so boom, good phone.
Maybe this should be in off topic thread, but I will post here.
Thank you for the great work that you have done. You gave us nougat, oreo, almost a pie. LineageOS 15.1 is the best firmware I have ever used. EmUi far behind. Thanks again a lot. Pie is full of bugs (I have already tried), counted a huge list of 10 items, but I think it's time to relax. You gave nova a second life and for that I am grateful to you. I found out that you are switching to another phone. Good luck in developing it, you are a good developer, the main thing is to believe in yourself!
Hi enkate... does wifi calling work on 16 ?
thanks
virusdunil said:
Hi enkate... does wifi calling work on 16 ?
thanks
Click to expand...
Click to collapse
He has no way to check. Maybe someone who has flashed it could test.
wow！thx a lot，I will try it now！
Hey Henkate !, Yesterday I installed LOS16, the last build that you compiled, botched and everything, but at the moment of continuing with the initial configuration, the screen does not give an image, the touch works, but it runs out of image: /
Alee.se said:
Hey Henkate !, Yesterday I installed LOS16, the last build that you compiled, botched and everything, but at the moment of continuing with the initial configuration, the screen does not give an image, the touch works, but it runs out of image: /
Click to expand...
Click to collapse
With the first build go two files, except for the firmware, responsible for the display. Flash them after flash lineage 16 last build and everything will work
Logcats
Hey there!
Finally tried it. I flashed just the latest build and there is what I got:
After flashing only ROM, it booted, but nothing was drawn at the display. Ok, that was expect
Then I wiped system and data again, flashed the build and both of the other zips (from the first build folder)
It booted fine, RIL was working at start, wifi ok. Many other things couldn't be tested, because randomly (one time taking photos, other when scrolling settings, other when trying to test bluetooth) screen went black the blue led got lit up.
I took a logcat only with errors and it seems there is a lot to fix. Still today (just a lot later today, I have to work) I'm gonna fetch los 16 trees, but I still have no idea how to solve any of the bugs. I'll do a lot of search though.
Here is the gist I made with the logcat I took. Any help would be appreciated.
EDIT
just forgot to mention that besides RIL working, I couldn't make a call (display went black and blue led). When rebooted it, I had no signal reception at all
Vinnom said:
Hey there!
Finally tried it. I flashed just the latest build and there is what I got:
After flashing only ROM, it booted, but nothing was drawn at the display. Ok, that was expect
Then I wiped system and data again, flashed the build and both of the other zips (from the first build folder)
It booted fine, RIL was working at start, wifi ok. Many other things couldn't be tested, because randomly (one time taking photos, other when scrolling settings, other when trying to test bluetooth) screen went black the blue led got lit up.
I took a logcat only with errors and it seems there is a lot to fix. Still today (just a lot later today, I have to work) I'm gonna fetch los 16 trees, but I still have no idea how to solve any of the bugs. I'll do a lot of search though.
Here is the gist I made with the logcat I took. Any help would be appreciated.
EDIT
just forgot to mention that besides RIL working, I couldn't make a call (display went black and blue led). When rebooted it, I had no signal reception at all
Click to expand...
Click to collapse
Also to the list of bugs: personally, my phone did not work with a SIM card, constant crash of applications. The YouTube crash, the camera does not take a photo (camera stock), after restarting, the fingerprint disappears (it is not deleted from memory, but it can only be unlocked if you make a new fingerprint) Any heavy application will crash after a while
Thx for u work, I have a reboots after few mins the system starts
nova canL11, cant reply link to adb bugreport logs x_x
penk3 said:
Thx for u work, I have a reboots after few mins the system starts
nova canL11, cant reply link to adb bugreport logs x_x
Click to expand...
Click to collapse
Disable out sim card
AssasinAkindinov said:
Disable out sim card
Click to expand...
Click to collapse
ye, phone in airmode workrd normally,
AssasinAkindinov said:
Also to the list of bugs: personally, my phone did not work with a SIM card, constant crash of applications. The YouTube crash, the camera does not take a photo (camera stock), after restarting, the fingerprint disappears (it is not deleted from memory, but it can only be unlocked if you make a new fingerprint) Any heavy application will crash after a while
Click to expand...
Click to collapse
penk3 said:
Thx for u work, I have a reboots after few mins the system starts
nova canL11, cant reply link to adb bugreport logs x_x
Click to expand...
Click to collapse
Sorry guys, no mean to be rude here, but this thread is for development purposes. My point in posting was to give a logcat and receive help to try and fix the bugs I found. I know that when possible, #Henkate gonna take a look and give some directions, so work can be done. So, if you wanna test and see if the rom works for you, that's fine, but provide logs, please. It's good to have other logs and be able to compare if the bugs are the same and I think it can help development a lot (no need to flood with logs either, be reasonable).
Unbrick no screen.
To repair the phone (when there is more image) it must start in fastboot mode and then flash boot image) wait for the phone to go off or remove the battery. When it is off plug the usb cable c on your huawei nova and the phone will show that the phone is charging. Now you can reflash another rom but not lineage os 16. Sorry i use google translation
Android 9 with jdi screen
Android 9 with jdi screen
Amazing near.
As it is known, custom firmware was not friends with the jdi screens.
And here came LOS16 on Android 9. Read reviews that it is now not usable even on smartphones with "normal" screens, what can we say about JDI
But from the realization that he had bought a new phone and having a lot of time, the thought crept in to try to put a fresh custom for total disappointment in his smartphone and quiet use of the new.
However, not everything is so simple. After the first launch, the screen began to flicker well, I thought everything had arrived, now it will get dark and the sensor will fail. Cured with just one reboot. more of this did not happen.
Sim cards did not pull out (I have 2 of them), some wrote that because of them there were some problems crashing and rebooting the system (I don’t have that)
After a night out, the interface began to respond with a delay of 0.5 seconds. (It was cured by a complete reboot) ..
Quickstep launcher is often closed with an error
The camera does not remove the drain, installed from the playlist of the market works without comments.
The navigation bar disappeared after a telephone conversation, when the interlocutor first completed the call (It was decided to reboot)
Vkontakte application crashes, but I use Kate Mobile, it flies with a bang.
YouTube crashes
The sound from the conversational dynamics is quiet, I think you can fix it in the mixer_paths but this is not exactly
Waiting for the moment until the screen fails.
All right, testing 9 android is over!
Discharged the battery to 0, the phone turned off, when turned on, the painfully familiar symptom with the diagnosis "JDI", no image, the screen backlight is on.
Hope no more. I return the phone to the stock and sell it, turn to Meizu pro 7. Thank you all!
R0mi4 said:
All right, testing 9 android is over!
Discharged the battery to 0, the phone turned off, when turned on, the painfully familiar symptom with the diagnosis "JDI", no image, the screen backlight is on.
Hope no more. I return the phone to the stock and sell it, turn to Meizu pro 7. Thank you all!
Click to expand...
Click to collapse
Ты все посты будешь переводить и сюда кидать?) (It is joke)
Dear, Since I only support Arabic, I will present the necessary files with the pictures
This Files Only For: Lenovo Z6 Pro L78051
Settings > About phone > Technical details > Model > Lenovo L78051
You Can use | Tool All In One | to Force your Device go to Edl
{
"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"
}
Files:
Lenovo Z6 Pro L78051 ROM ZUI 11.0.483
Note:
No Need > Unlock the bootloader
https://www.zui.com/iunlock
Thanks. global rom ??
this is the chinese version with no google play but fixed bugs and real benchmark scores close to the top , for me it was easy to remove the bloatwares and install playstore and my apps
i ve already put negative review on the aliexpress seller who provided a hybrid rom claiming this to be a global release....
Guide for Lenovo Z6 Pro CH/ENG ROM flash (BIG PERFORMANCE BOOST COMPARED TO GLOBAL RO
First of all, some info
Okay guys, I’ve been struggling with this a few hours myself. I am by no means a professional. I think it’s safe to say I’m an amateur who had messed around with Android phones in the past.
As all of you may have noticed; the graphical performance and actually the general performance of the global ROM is really horrible for the Lenovo Z6 Pro. I couldn’t live with the fact that my benchmarks sucked and I felt like my phone wasn’t providing its full potential. After opening an official Lenovo forum some amazing people from the community pointed me in the right direction. Thanks Chaina and PcM_2019 for your amazing input!
The reason for this bad performance has to do with the Global ROM itself. It’s simply poorly optimized right now and receives barely any updates. I expect that in the future it will receive updates accordingly but as of right now it’s better to move over to the Chinese / English ROM.
Keep in mind there will be some Chinese apps and no Google Play in this ROM. You can add Google Play and delete most of the apps in case you’d like it better that way.
Time for the tutorial
MAKE SURE TO BACKUP ALL YOUR DATA, THIS IS A TUTORIAL FOR FLASHING DIFFERENT FIRMWARE FOR YOUR DEVICE AND IT WILL RESULT IN LOSING ALL YOUR DATA. Backup all data you wish to keep. Of course I cannot be held responsible for the loss of your data.
You will need a windows computer and a USB-C data cable.
1) Get all the required software for flashing your device to the preferred ROM.
a. First of all, the ROM itself. Because URL’s are not allowed, look on mirrors.lolinet under firmware for Lenovo L78051. It’s about a 3GB file.
b. Secondly; Qualcomm HS-USB driver.exe Boycracked has in his portfolio a a link to the Qualcomm usb driver. Google for it.
c. Lastly; the Qualcomm Flash Image Loader (QFil)
i. Androidbrick lists the latest Qualcomm flasher qfil gpst 2.7.460. Download this one!
2) We start off with the ROM. It’s a ZIP file, get 7zip or other archiving software to extract it.
3) Install the HS-USB driver – keep pressing next, don’t change anything.
4) Exctract and Install QFil. After the installation you can find the program in start by searching for “QFil”.
5) Place the extracted ROM folder in the following installation path of QFil for avoiding potential issues in the flashing process. The path should be: C:\Program Files (x86)\Qualcomm\QPST\bin. Just drop the entire folder in the bin.
6) You’re now ready for the real deal. Time to flash your device! Open QFil (search QFil in start) and follow these steps.
a. Open the configuration tab, click Firehose configuration and change device type from eMMC to UFS. Also “turn Reset After Download” on. Now press “OK”.
b. Now click “load content” Navigate to the path where you placed the new firmware, the path should be: C:\Program Files (x86)\Qualcomm\QPST\bin\L78051_CN_SECURE_USER_Q00745.01_P_ZUI_11.0.483_ST_190511_qpst and open the XML document “contents”. After this the Programmer path should be automatically filled in.
c. Now open developer options on your phone and turn on USB debugging and OEM unlocking. Change default USB configuration to File Transfer.
d. After this you can turn off your phone. When the phone is turned down completely we will now boot it into flash mode. Hold down the two volume buttons together and plug-in your USB-C data cable which is connected to your PC. QFil should now recognize your device as a COM port. The port should be automatically selected. If that’s not the case, then select port manually. You can now press the blue “Download Content” button.
e. That’s it. Your phone should now be flashed with your selected firmware.
Troubleshooting
If you were to run into problems, don’t worry you can always boot your phone normally again by holding down the power button for 10 seconds after having entered the flash mode. No damage will be done.
If QFIL gives Sahara error, go to device manager and update your COMM port drivers. Let Windows select the correct drivers automatically. Enter flash mode again and try the procedure again.
If it turns out the Sahara error is not fixed after a few attempts you could save a lot of time by using another computer, install everything on there again by following this tutorial and try it again.
If something is unclear, or you keep running into problems, let me know and I’ll try to help you to the best of my ability.
Special credits to Chaina
Additional sources that helped me put this tutorial together:
Boycracked
Mirrors.lolinet
Androidbrick
Has anyone figured out, how to fix google assistant issue in chinese rom? (default assist app is switchnig to none after deepsleep or kill process button) Turning off battery optimization or giving more permissions for google home or google services did not help.
China Official
opened a dispute with seller on aliexpress claiming the sale version as global and here is their joke answer here is no actual comparability between the evaluation software and the actual use. It is subject to actual usage. and The global version refers to language packs and channels. if i win i will take back 30usd as this amount i asked back open up all of you the same dispute , we must not tolerate this attitude and lies....
hello to all , how about twrp for this z6 pro ???
i need it bad .
thanks
help please .
i have unlocked bootloader and the global rom provided by phone seller has crashed , i have installed cn rom but no google play and my job depends on playstore apk's.
so please help with global rom for qfill or twrp and a backup of the global rom
here is the latest , i think
L78051_CN_SECURE_USER_Q00745.01_P_ZUI_11.0.542_ST_190610_qpst
https://drive.google.com/open?id=1r2oqL0jrFWO9MDMGMA6J0D-Jxd5rWryx
Background Services Off
Hi all
Firstly thanks for your efforts above! Tut was good and info too.
Since upgrading I received 2x ZUI updates and am now on the newest version.
I'm having so many problems now, my phone is a borderline frisbee!
Managed to install Google apps via Aptoide easy enough and now have everything installed.
Problem I'm having is: when closing apps; they don't run in background which means, WhatsApp's emails, etc. don't come through unless you go into the app. Secondly the settings do not save, so as mentioned above, setting the assistant also changing keyboard etc.
Does anyone know a fix? Is it worth reverting back/updating to the newest global ROM?
Please help!
Thanks
dnick88 said:
Hi all
Firstly thanks for your efforts above! Tut was good and info too.
Since upgrading I received 2x ZUI updates and am now on the newest version.
I'm having so many problems now, my phone is a borderline frisbee!
Managed to install Google apps via Aptoide easy enough and now have everything installed.
Problem I'm having is: when closing apps; they don't run in background which means, WhatsApp's emails, etc. don't come through unless you go into the app. Secondly the settings do not save, so as mentioned above, setting the assistant also changing keyboard etc.
Does anyone know a fix? Is it worth reverting back/updating to the newest global ROM?
Please help!
Thanks
Click to expand...
Click to collapse
You Need to Lock the app
Multitask button box / Lock the app
nakarmkir69 said:
help please .
i have unlocked bootloader and the global rom provided by phone seller has crashed , i have installed cn rom but no google play and my job depends on playstore apk's.
so please help with global rom for qfill or twrp and a backup of the global rom
Click to expand...
Click to collapse
Lock The boot then use this rom or another one
XQ55 said:
Lock The boot then use this rom or another one
Click to expand...
Click to collapse
Thanks for the idea, i have allready installed the latest(the one that i have posted the gdrive link above) without locking the bootloader, all the commands to lock the bootloader do not work.
The phone is working but no google play that is mandatory to install apk's from store
nakarmkir69 said:
Thanks for the idea, i have allready installed the latest(the one that i have posted the gdrive link above) without locking the bootloader, all the commands to lock the bootloader do not work.
The phone is working but no google play that is mandatory to install apk's from store
Click to expand...
Click to collapse
https://mega.nz/#F!WnIASagK!_EZg03ccDdH_BJz0EbvdbQ
XQ55 said:
https://mega.nz/#F!WnIASagK!_EZg03ccDdH_BJz0EbvdbQ
Click to expand...
Click to collapse
Thanks a lot , got all done .
Please help me to get rid of the China default apk's.
Those that are system apk's and maybe how to lock the bootloader.
On Chinese ROM, does everyone experience battery drain? Think I've gone from 35 hours to 12 now
dnick88 said:
On Chinese ROM, does everyone experience battery drain? Think I've gone from 35 hours to 12 now
Click to expand...
Click to collapse
No drain with zui i am looking for global rom "the fake one" as some people call him
Same, I went from global version 11.0.054 ST to the newest CN version 11.0.575 ST and am having so many issues:
No push notifications, unless apps left open
No location on most apps including Google maps
Battery drain
Settings do not save
On the up side, camera quality and performance is now what I paid for!
I'm hoping I can track down a global ROM newer than .054 but seems impossible at the moment..
XQ55 said:
https://mega.nz/#F!WnIASagK!_EZg03ccDdH_BJz0EbvdbQ
Click to expand...
Click to collapse
I have found some problems on zui :
Whatsapp does not notify with sound , only with popup
System default phone apk does not initiate call when touch call from recents or contacts , just increase the number of calls made.if i insert the number manually it make the call just perfect
---------- Post added at 11:01 AM ---------- Previous post was at 10:56 AM ----------
dnick88 said:
Same, I went from global version 11.0.054 ST to the newest CN version 11.0.575 ST and am having so many issues:
No push notifications, unless apps left open
No location on most apps including Google maps
Battery drain
Settings do not save
On the up side, camera quality and performance is now what I paid for!
I'm hoping I can track down a global ROM newer than .054 but seems impossible at the moment..
Click to expand...
Click to collapse
New phone new problems , i just hope that twrp and lineage or mokee will appear soon, for me is the best way allso was the stock global rom that the phone had installed when arrive but it seems that nobody have it.
Maybe someone will have it and posted here
Hello
I have the RMX1931 with the bootloader unlocked and the twrp recovery [3.3.1-13] installed
I want reset my phone because have random reboots.
Download RMX1931EX_11.A.10 for twrp
First wipe this partition
Cache
Dalvik
Data
Click to expand...
Click to collapse
Then flash
Ozip RMX1931EX_11.A.10 for twrp
Vbmeta
Magisk
Click to expand...
Click to collapse
But dont boot in system
first boot not see realme logo and reboot in twrp
i try restored old backup twrp clear device but same results.
only work backup twrp with data partition full, that I did before starting this experiment.
I believe it is the given partition that makes the device boot. With this clean partition it goes into bootloop
please help me
Flash ozip
Flash vbmeta
Flash magisk
Format data
Reboot
perisman said:
Flash ozip
Flash vbmeta
Flash magisk
Format data
Reboot
Click to expand...
Click to collapse
Tonight i try.
Thank you
perisman said:
Flash ozip
Flash vbmeta
Flash magisk
Format data
Reboot
Click to expand...
Click to collapse
you are a genius.
IT WORKS.
Now I have installed the A10 system and restored the app backup via swiftbackup.
everything seems to work, I hope it will not restart.
if you can give me more advice.
thank you very much.
EDIT :
The phone continues to restart.
I'm thinking it can be Magisk root.
Without applications installed
I went crazy with this problem
You can try with last update C25. I flashed from twrp, and now t'he device works fast and smooth. I have magisk, viper4android installed. T'he only problem us FP, because unlocked BL. You can try with a custom ROM, I have tried phh treble and aosip 10, and works very well, and FP works also. You cqn revert to color os 6.x allways flashing A10 ozip. If with other ROMs hsppens t'he random reboots, then is a hardware problem.
it is a real dilemma because with the clean system, however, the phone has restarted for no obvious reason.
I can't understand what makes the phone restart.
only Magisk could be the cause.
I installed Magic which recommends Jerry. but even with the standard version the problem was always the same
Now I send you a screen so it's better evident.
{
"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"
}
Try Another rom, clean system one day to see what It happens
Yes I try In These Days.
Thank you so much for your support
perisman said:
Try Another rom, clean system one day to see what It happens
Click to expand...
Click to collapse
I am now testing the LINEAGE it happened to me this I removed the SIM card and I installed the costum Rom, I made the various customizations and the phone never locked OR restarted.
I inserted the SIM card in the phone worked perfectly, then having messed up with luckypatcher I had to reinstall the Rom.
So I performed the same procedure with the SIM card inserted in the phone and already at the first start it was unstable with reboots.
Currently I have applied for a change of sim card.
As soon as it arrives I will try to remove the sim card Install from scratch The system is to insert the new SIM card only so I can have the mathematical certainty that it is the SIM card
I hope my experience can help someone
perisman said:
You can try with last update C25. I flashed from twrp, and now t'he device works fast and smooth. I have magisk, viper4android installed. T'he only problem us FP, because unlocked BL. You can try with a custom ROM, I have tried phh treble and aosip 10, and works very well, and FP works also. You cqn revert to color os 6.x allways flashing A10 ozip. If with other ROMs hsppens t'he random reboots, then is a hardware problem.
Click to expand...
Click to collapse
i try lienage os, but now i want return colorOS.
i try flashing A10 colorOS.ozip but color OS Boot Loop (Stuck in Realme Logo)
you have solution? for now flash lineageOS and work well but i want colorOS.
please help me
-First, change twrp. Install orangefox or skyhawk twrp (I am using skyhawk and I can revert from C10 trebled rom to
C26 backup, firsr install C26 ozip, and after first boot, reinstall twrp from fastboot and restore full backup)
-Reboot to twrp
-Flash full Ozip , I recommend C26. Works very well, antutu 501.850, no lags, with viper4android installed. With
lineage 371.056 in antutu
-flash vbmeta
-flash magisk
-format data
-reboot
-Once system boots to system, reboot to fastboot to reinstall twrp (with ozip install, you have stock recovery,
check this booting it, depends of twrp you are using. Orangefox saves twrp, skyhawk no)
I hope it helps
I should follow these steps
1 - flash recovery skyhawk twrp
2 - Reboot to twrp
3 - Flash full Ozip (i prefered pie have Fingerprint work)
4 - flash vbmeta
5 - flash magisk
6 - format data
7 - reboot
I have already done these steps with the (ozip A10 FOR TWRP) but color OS Boot Loop (Stuck in Realme Logo).
do you think that recovery creates this problem?
i now have lineageOS work but want return colorOS
thanks for the support
EDIT:
I have run your advice but unfortunately this device perhaps has a hardware problem.
Whenever it manages to boot, just 30 seconds and restart.
I noticed artifacts when starting the sistama.
I'm really desperate.
what do you advise me to do?
thanks
westenlive said:
I am now testing the LINEAGE it happened to me this I removed the SIM card and I installed the costum Rom, I made the various customizations and the phone never locked OR restarted.
I inserted the SIM card in the phone worked perfectly, then having messed up with luckypatcher I had to reinstall the Rom.
So I performed the same procedure with the SIM card inserted in the phone and already at the first start it was unstable with reboots.
Currently I have applied for a change of sim card.
As soon as it arrives I will try to remove the sim card Install from scratch The system is to insert the new SIM card only so I can have the mathematical certainty that it is the SIM card
I hope my experience can help someone
Click to expand...
Click to collapse
Hi, I also have rebooting issues does your X2 pro still reboots? Did changing sim cards solved your reboot problem Im getting desperate.
JKD23 said:
Hi, I also have rebooting issues does your X2 pro still reboots? Did changing sim cards solved your reboot problem Im getting desperate.
Click to expand...
Click to collapse
sorry to tell you but unfortunately this phone has an underlying problem ie the modem hardware is of poor quality.
I have done 1000 tests I have tried everything and more but unfortunately it keeps restarting the user interface when a call comes in or when you try to make a call.
especially when you keep the modem busy for other chores such as navigation with Google Maps or other and you receive a call the phone suffers a stress and this causes a restart.
I have given myself this explanation because it is truly inconceivable that a top-of-the-range phone has these problems.
if you find a solution Let me know.
Thanks so much
westenlive said:
sorry to tell you but unfortunately this phone has an underlying problem ie the modem hardware is of poor quality.
I have done 1000 tests I have tried everything and more but unfortunately it keeps restarting the user interface when a call comes in or when you try to make a call.
especially when you keep the modem busy for other chores such as navigation with Google Maps or other and you receive a call the phone suffers a stress and this causes a restart.
I have given myself this explanation because it is truly inconceivable that a top-of-the-range phone has these problems.
if you find a solution Let me know.
Thanks so much
Click to expand...
Click to collapse
Sorry to hear that ? I'm also suspecting that I have hardware problem it only reboots when connecting to LTE mobile data. I already tried using flash tool for a clean flash didnt work though.
I'm still hoping it's a software issue because I can still get LTE signal I just can't use mobile data. I kinda regretted buying this phone. I'm so unlucky I got a defective device. ?
If I find a solution I'll let you know.
JKD23 said:
Sorry to hear that [emoji853] I'm also suspecting that I have hardware problem it only reboots when connecting to LTE mobile data. I already tried using flash tool for a clean flash didnt work though.
I'm still hoping it's a software issue because I can still get LTE signal I just can't use mobile data. I kinda regretted buying this phone. I'm so unlucky I got a defective device. [emoji24]
If I find a solution I'll let you know.
Click to expand...
Click to collapse
Basically these have mounted a modem on this phone which in my opinion is not fully compatible with the Snapdragon.
In fact, the price is really very low if you consider that this is a top-of-the-range Smartphone with a 90 Hertz screen and latest generation processor.
They are practically giving it away now on the official website it costs € 350.
westenlive said:
Basically these have mounted a modem on this phone which in my opinion is not fully compatible with the Snapdragon.
In fact, the price is really very low if you consider that this is a top-of-the-range Smartphone with a 90 Hertz screen and latest generation processor.
They are practically giving it away now on the official website it costs € 350.
Click to expand...
Click to collapse
Realme should acknowledge these problems and improve the quality of their units. Let's hope Realme Dev team would release updates that could fix our units. (fingers crossed)
JKD23 said:
Realme should acknowledge these problems and improve the quality of their units. Let's hope Realme Dev team would release updates that could fix our units. (fingers crossed)
Click to expand...
Click to collapse
Dear
since you texted me I have been looking for the problem once again.
I have ILIAD as an operator.
I had self-configuring SMS sent for APNs.
With the new APN the problem seems to have disappeared.
try it too and let me know
hello [emoji1309]
westenlive said:
Dear
since you texted me I have been looking for the problem once again.
I have ILIAD as an operator.
I had self-configuring SMS sent for APNs.
With the new APN the problem seems to have disappeared.
try it too and let me know
hello [emoji1309]
Click to expand...
Click to collapse
That's good to hear, I tried your suggestion using self configuring apns through sms, my other operator doesn't send me any sms while the other one was not self configuring. Doesn't seems to work for me Ill try again rechecking the APNs. I also pulled an ADB bug report and sent it to Realme Devs through email they haven't replied yet. When I opened it I saw a few errors like but I couldn't understand it since im not a dev but a run some hardware and sensor diagnostics app and all sensors seems to be working fine. I hope the devs would reply sooner.
JKD23 said:
That's good to hear, I tried your suggestion using self configuring apns through sms, my other operator doesn't send me any sms while the other one was not self configuring. Doesn't seems to work for me Ill try again rechecking the APNs. I also pulled an ADB bug report and sent it to Realme Devs through email they haven't replied yet. When I opened it I saw a few errors like but I couldn't understand it since im not a dev but a run some hardware and sensor diagnostics app and all sensors seems to be working fine. I hope the devs would reply sooner.
Click to expand...
Click to collapse
Hi dear
have you tried to update to Version: RMX1931EX_11.C.32.
From the log it would seem that they have solved the problems that happen to us.
I have the phone too full and rooted and I would not like to update to android 10 so I am still stuck on android 9.
Have you updated?
How to Bootloader Unlock (Part 1 of 2):
1. You will need a USB A to USB A cable (Example here)
2. You will need fastboot drivers on your PC
3. Unplug your clock
4. Plug the USB A to A cable into your computer and clock
5. Hold the volume + button and plug in the power cord
6. Keep holding volume + for about 20-30 seconds (It is slow to boot to fastboot)
7. On your computer in a terminal run, fastboot flashing unlock
Part 1 of unlocking is now done
AVB/DM-Verity Unlock (Part 2 of 2)
Unlocking the bootloader really does not give a lot to us because all the partitions are still being verified and the device will not boot if they don't match. Normally doing this on an Android Things device is not possible due to their Private key unlock system. But due to a leak, the private key for the Lenovo Smart Clock is available. Word of warning doing this causes the stock android things not to boot only the factory firmware located on Slot A will boot. Consistently if you don't AVB unlock the factory firmware on Slot A doesn't boot If you have already set up your device once the factory firmware is deleted and currently there is not a way to get it back (Hopefully will change soon).
If you are coming from part 1 you can start right away, if not you need to reboot to fastboot again.
1. Extract the downloaded AVB Unlock zip
2. Run this command in terminal
Code:
at_auth_unlock.exe cube_unlock_credentials_v2.zip
3. Wait till it finishes
4. Keep in mind the stock system does not boot properly with AVB off (It is weird some UI elements work but the boot animation never goes away)
5. To relock AVB in the future run the following command:
Code:
fastboot oem at-lock-vboot!
Downloads:
Stock Shipping fastboot firmware:
Here
AVB Unlock tool:
Here
Factory partition changer (Locale changer):
Here
Google released kernel source:
https://github.com/deadman96385/android_kernel_lenovo_mt8167s
Dump of stock partitions for easy viewing:
https://github.com/deadman96385/things_mt8167s_som_dump
Credit to @deletescape for the leak of the AVB Unlock Key, Stock firmware, region changer
Screenshots of the stock android things on Slot A if you don't setup the device :
{
"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"
}
TWRP (Coming Soon)
Excited to see what you manage to do with this!
This is great! I have one of these and it felt way too restrictive, looking forward to seeing what comes out of this.
You can also unlock the boot loader simply with what's below... device does boot with this btw
fastboot flashing unlock
Although I've been messing with the device quite a bit. Plug in a usb keyboard, and you can get a web browser to recognize it and go to websites and such using the touch screen as a cursor, but you can't download APK files and install them and such. I've NEVER had the device recognized by ADB, so I can't pass commands from there either.
KaptinBoxxi said:
You can also unlock the boot loader simply with what's below... device does boot with this btw
fastboot flashing unlock
Although I've been messing with the device quite a bit. Plug in a usb keyboard, and you can get a web browser to recognize it and go to websites and such using the touch screen as a cursor, but you can't download APK files and install them and such. I've NEVER had the device recognized by ADB, so I can't pass commands from there either.
Click to expand...
Click to collapse
Just doing step one does not actually get you anything because if you flash something that isn't stock on the verified partitions it will not boot until you flash back the stock one. I have gotten adb to show up but not properly so it is offline. Still hacking away at it trying to get it to go so i can more easily debug TWRP and make edits to the system.
deadman96385 said:
Just doing step one does not actually get you anything because if you flash something that isn't stock on the verified partitions it will not boot until you flash back the stock one. I have gotten adb to show up but not properly so it is offline. Still hacking away at it trying to get it to go so i can more easily debug TWRP and make edits to the system.
Click to expand...
Click to collapse
Ahhhhh got it. I couldn't find anything when I was messing with it like you've found with those commands. I'm kinda new to all this myself at something with nearly zero support, although I have a ton of experience with phones. Had to find my own exploit with my HTC One M7 because the version of android on the phone was the final supported update when I got it, and everyone said "nothing is possible with this android version" as far as rooting... so I figured out my own way lol
I'll continue trying myself though for sure
I also own one of these clocks, so if anyone has anything that I could test out, please share!
I think I'm bit late to party. Anyone who has a backup for those lenovo products, maybe it's a good idea to torrent them.
Honami754 said:
I think I'm bit late to party. Anyone who has a backup for those lenovo products, maybe it's a good idea to torrent them.
Click to expand...
Click to collapse
I don't have the time to test this stuff out for at least a few weeks, but if when I get to it, I'll try to upload my Backups somewhere before I tinker with the system. I'll update this comment when I do.
[/COLOR]
CiriousJoker said:
I don't have the time to test this stuff out for at least a few weeks, but if when I get to it, I'll try to upload my Backups somewhere before I tinker with the system. I'll update this comment when I do.
Click to expand...
Click to collapse
That's not really what I mean... I was referring to some interesting documents from lenovo. Have a few of those hardware but unfortunately didn't grab those files. Anyone also interested in these can PM me maybe we can do something about it.
when will twrp be avable
Interesting as there has a been a few of these turn up to auction of late .
I have gone with the 10' for main room and 8' for bedroom.. love them..
Got the oldies the little 7'
Great for streaming too..
The one I wish it did was announce the time by voice when the internet was down and we said "Hey Google". I am blind without my glasses and often when I am in bed, the internet is down in my area for maintenance period. The clock becomes useless when the internet goes down.
How are people getting the web browser to appear? I'm able to unlock the bootloader but can not boot with the AVB unlocked (well...technically it boots but still shows the spinning circle even though it will let you go to settings). I tried flashing the stock fastboot img and booting with avb unlocked and still get spinning circle. Not trying to get too fancy with this...just want to be able to point to a status page that I can leave it on.
Does anyone try to build a new firmware image and install this instead of stock?
Maybe compiling Android Things from source is possible, but looks like Google has stopped the development. The Lenovo Smart Frame seems to have the same MT8167S and runs on Android 10. Maybe it's possible to compile a LineageOS version?
lenovo.com/us/en/coming-soon/Lenovo-CD-3L501/p/ZZISZSDCD04
Another option might be fuchsia that contains a mt8167s board ref.
fuchsia.googlesource.com/fuchsia/+/master/boards/mt8167s_ref.gni
Googles Coral announced a Dev Board Mini based on MT8167s, maybe they port the Debian-based Mendel Linux to it.
coral.ai/products/dev-board-mini
hugo987 said:
Does anyone try to build a new firmware image and install this instead of stock?
Maybe compiling Android Things from source is possible, but looks like Google has stopped the development. The Lenovo Smart Frame seems to have the same MT8167S and runs on Android 10. Maybe it's possible to compile a LineageOS version?
lenovo.com/us/en/coming-soon/Lenovo-CD-3L501/p/ZZISZSDCD04
Another option might be fuchsia that contains a mt8167s board ref.
fuchsia.googlesource.com/fuchsia/+/master/boards/mt8167s_ref.gni
Googles Coral announced a Dev Board Mini based on MT8167s, maybe they port the Debian-based Mendel Linux to it.
coral.ai/products/dev-board-mini
Click to expand...
Click to collapse
I suppose the smart frame is running android things as well. Compiling android things does make much sense except to prove the drivers are sort of working, this is not designed to let users have fun (ie installing apps).
Google *really* loves mt8167s for some reason. I'd say there's a good chance of we having full android on it but everyone's busy.
They are throwing these things at our head now. 35/40 USD during black fridays.
I don't think you can order the components for that price
Anybody still working on it ? Lenovo claims it's still working on the sound bug - hxxps :// forums.lenovo.com/t5/Lenovo-Smart-Display-Lenovo-Smart-Clock-with-Google-Assistant/Smart-clock-alarm-volume-too-loud-at-first/m-p/5040962?page=4 (latest reply 2020-13-11 from Lenovo) and they did some unanounced pretty good updates in september 2020 - hxxps :// 9to5google.com/2020/09/21/lenovo-smart-clock-night-light/
They also claim the source is on their website hxxps :// smartsupport.lenovo.com/us/en/products/smart/smart-home/smart-clock/za4r/downloads/ds539701
So is this dead ?
deadman96385 said:
How to Bootloader Unlock (Part 1 of 2):
1. You will need a USB A to USB A cable (Example here)
2. You will need fastboot drivers on your PC
3. Unplug your clock
4. Plug the USB A to A cable into your computer and clock
5. Hold the volume + button and plug in the power cord
6. Keep holding volume + for about 20-30 seconds (It is slow to boot to fastboot)
7. On your computer in a terminal run, fastboot flashing unlock
Part 1 of unlocking is now done
AVB/DM-Verity Unlock (Part 2 of 2)
Unlocking the bootloader really does not give a lot to us because all the partitions are still being verified and the device will not boot if they don't match. Normally doing this on an Android Things device is not possible due to their Private key unlock system. But due to a leak, the private key for the Lenovo Smart Clock is available. Word of warning doing this causes the stock android things not to boot only the factory firmware located on Slot A will boot. Consistently if you don't AVB unlock the factory firmware on Slot A doesn't boot If you have already set up your device once the factory firmware is deleted and currently there is not a way to get it back (Hopefully will change soon).
If you are coming from part 1 you can start right away, if not you need to reboot to fastboot again.
1. Extract the downloaded AVB Unlock zip
2. Run this command in terminal
Code:
at_auth_unlock.exe cube_unlock_credentials_v2.zip
3. Wait till it finishes
4. Keep in mind the stock system does not boot properly with AVB off (It is weird some UI elements work but the boot animation never goes away)
5. To relock AVB in the future run the following command:
Code:
fastboot oem at-lock-vboot!
Locale changer instructions:
Coming soon (Need to figure it out)
Downloads:
Stock Shipping fastboot firmware:
Here
AVB Unlock tool:
Here
Factory partition changer (Locale changer):
Here
Google released kernel source:
https://github.com/deadman96385/android_kernel_lenovo_mt8167s
Dump of stock partitions for easy viewing:
https://github.com/deadman96385/things_mt8167s_som_dump
Credit to @deletescape for the leak of the AVB Unlock Key, Stock firmware, region changer
Click to expand...
Click to collapse
how about smart display ,the same way?
jasonzhang1987 said:
how about smart display ,the same way?
Click to expand...
Click to collapse
We do not have the AVB unlock files for the smart displays sadly.