Stuck on boot loop on Mobvoi TicWatch (1) - Other SmartWatches

I have unlocked the bootloader, installed TWRP, and my last objective was to install the custom ROM from the official Kali Linux website. After flashing the custom rom via fastboot, the watch goes into a boot loop. "TicWatch" shows up on watch screen for a time of roughly 10 seconds then restarts. I am still able to reach the bootloader and enter recovery mode/TWRP.
Can anyone help resolve my issue I am having? I tried flashing to what I believe were stock ROMs but I couldn't find any official ROMs from Android or the TicWatch wear OS' manufacture, Mobvoi. No such luck.
Any help in pointing me in the right direction would be very much appreciated.
Thank you for your time and effort in helping me,
x_____________
***UPDATE***
ADB fastboot no longer recognizes my TicWatch when device is plugged into PC and in the bootloader menu.

hey! sorry for your bummer
in the thread
[ROM+KERNEL+TWRP][Ticwatch Pro(Catfish)(Catshark-4G)]+[Ticwatch C2(Skipjack)[9Aug20]
-[Ticwatch Pro 4G/LTE (EU) (Catshark)-PWDD.190617.059]-[30-5-2020] - [Ticwatch Pro 2020 (Catfish-Ext)-PMP2.191203.001]-[22-6-2020] - [Ticwatch Pro (Catfish)-PWDD.190617.074]-[09-8-2020] ############################# - [Ticwatch Pro 4G/LTE (USA)...
forum.xda-developers.com
there's a mega folder link (watch for the decryption key hidden in there iZbWXMs8vabDW1szJz1hgg)
MEGA
MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now
mega.nz
inside if you navigate to TicWatch-XDA>TicWatch-Pro(Catfish)>Stock-Rom
There will be what i believe to be a stock rom, while myself haven't done it myself (i have a version not yet supported - so i was lurking to try see something myself)
If you want to give another try (maybe missed a point or it didn't worked right) there's the exactly files in there which are described in the steps from Nethunter official page. (those said files are on TicWatch-XDA>TicWatch-Pro(Catfish)>Custom-Rom>Rom>2020>09-August note that there's kernels in there too) i would give it another try if it was me
IF it works the link to the stock rom is this:
7.15 GB folder on MEGA
66 files and 66 subfolders
mega.nz
hope it helps
i haven't done it myself

NUMAflex said:
hey! sorry for your bummer
in the thread
[ROM+KERNEL+TWRP][Ticwatch Pro(Catfish)(Catshark-4G)]+[Ticwatch C2(Skipjack)[9Aug20]
-[Ticwatch Pro 4G/LTE (EU) (Catshark)-PWDD.190617.059]-[30-5-2020] - [Ticwatch Pro 2020 (Catfish-Ext)-PMP2.191203.001]-[22-6-2020] - [Ticwatch Pro (Catfish)-PWDD.190617.074]-[09-8-2020] ############################# - [Ticwatch Pro 4G/LTE (USA)...
forum.xda-developers.com
there's a mega folder link (watch for the decryption key hidden in there iZbWXMs8vabDW1szJz1hgg)
MEGA
MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now
mega.nz
inside if you navigate to TicWatch-XDA>TicWatch-Pro(Catfish)>Stock-Rom
There will be what i believe to be a stock rom, while myself haven't done it myself (i have a version not yet supported - so i was lurking to try see something myself)
If you want to give another try (maybe missed a point or it didn't worked right) there's the exactly files in there which are described in the steps from Nethunter official page. (those said files are on TicWatch-XDA>TicWatch-Pro(Catfish)>Custom-Rom>Rom>2020>09-August note that there's kernels in there too) i would give it another try if it was me
IF it works the link to the stock rom is this:
7.15 GB folder on MEGA
66 files and 66 subfolders
mega.nz
hope it helps
i haven't done it myself
Click to expand...
Click to collapse
Thank you for responding and for your help. I will give you an update on if this works or doesn't work for me.
I appreciate the time into helping me solve my problem.
-a

Related

[Q] Lenovo Lepad S1 Y1011 - leaked rom

Hello,
my borther brougt me this tablet from china for chrismas: Lenovo Lepad y1011 (sry can't send a link becaus i'm a new user...)
But Lenovo has changed everything on android and they call it OS 2.0 (= Android 2.2 )
Maybe someone found a solution to update the OS to honeycomb or to install CWM?
I have read so mutch chinese forms but the googletranslator didn't find something usefull for me.
I hope someone of you may help me.
thx MiracelVip
_____________________________________________________
Here is a mirror for the roms:
3G001_0100.3010_user_mode(1).rar h**p://ul.to/mmv76osx
WiFi001_0100.3010_user_mode.rar h**p://ul.to/26utcnuo
hi, the thinkpad tablet never came with anything lower than 3.1, also that isn't a valid model number for this tablet.
I think you must have something other than a thinkpad tablet
Cheers
Tom
Check here, shows the instructions for that model.
TS
Yes i know this thread! But its just about rooting and installing google maps and the market... but the market in this thread isn't working anymore! i think the version is to old...
but i hate the lenove OS, i would like it to install another one or maybe develop my own one if CWM would work
it's this one: h**p://appserver.lenovo.com.cn/shop/shop_Detail.aspx?gdsid=A2100014142
Unfortunately, it's said that Lenovo has no any upgrade plan for this pad. LePad S1(Y1011) is the first mode of pad from Lenovo. the product, particularly its deep customized OS, is in very low maturity. short after its released to the market, it's ended production and replaced by A1 series pad. that's the situation, so disappointed, and angry. and finally, its ROM leaked.
i searched some Chinese forum and got the following leaked ROM:
* LePad S1 Ver_Wifi ROM here
* LePad S1 Ver_3G ROM here
* resource pack here
hope it helpful to you guys who may interested look into the code
Thanks for this informations! Does someone know what we can do with this files?
________________________________________________________________________
This files are working! While I tried to install Gapps i bricked my Y1011 and i was able to reflash everything by using fastboot and LePad S1 Ver_3G ROM.
thx again for the files
hi i have the same tablet and really heavy problems. i look at all chinese forums with google translation and it is horrible to find anything about a working custom firmware.
if you instal the upper firmware it will be nice to tell us something about the changes. when i want to download i didnt work download allways stopp. the name is the same like the orriginal number.
im loking for a stable full android version. im read that there is a chinese caled chita he costum firmware for the lephone and the lephone works normal withe leos like the lepad.
so if anybody knew news about the lepad y1011 it wil be nice to write it here.
mfg
thorwald
yes i was able to install the firmeware above but ther are no changes! its just a leaked original version
at the moment i'm uploading the firmewares to uploaded.to
watch the 1. post
Thanks for your post. So i wont install the leaked rom if it isnt a full android. Do you know anything about Chitas Roms.
I worked with Costum Rom for my Archos Tablet and for HTC sensation xl but i m not god enough to custom a own one.
But i got Market place working without Gaaps. I have some mistakes with 492 but only by a few apps.
Thanks for upp the Files if I break it its easy to unbrick it. I will download it.
If some from China will inform us it will be very nice.
you have been able to install the market?! could you give me tutorial how you have done this? and thefiles you installed?
everytime i've tried it i bricked my device
(gerne auch auf deutsch )
At First German is on this forum not allowed. Forum rules (mir wärs auch lieber)
I have got market work with some mistakes on some files got mistake 492 if you find the APK on other Place the most will work but not with autoupdate.
Some Games will not work bcause the OS2.0.0 The Hardware is god enough
So here are how to do it
Install LeTools on Windows 7 PC. it is assumed that LenovoStore on your Lepad is already connected usin wifi.
Connect USB cable with Windows 7 PC
unzip attached file to your PC.
1. Copy all attached files to your LePad using LeTools in any known directory.
2. Use LePad filemanager and click on z4root.apk and install it. Its icon will appear on last Desktop
3. Use LePad file manager and click on Root_Explorer.apk and install it. Its icon will appear on last Desktop
4. Click on Z4root icon to run it. select temporary root permission
5. Click on Root_Explorer icon. It may say that it needs a restart to gain root access. so re run.
6. Now little hardwork. Find the folder where you copied the files. You have to copy following files to the folder /system/app
a. Vending.apk
b. Network location.apk
c. Market updater.apk
d. talk.apk
e. googleServicesFramework.apk
f. googlePartnerSetup.apk
7. Touch the file name and hold for a second, menu will appear. Select copy and go on top of listed files where .. is there for going to previous directory. keep going back till you reach the root folder.
8. Go to folder /system/app and touch the copy button at bottom of LePad screen.
9. Repeat the process for all above files.
10. Change the permissions on each copied file by touching the file name and holding for a second, from menu selecting permissions.
Select permissions as follows
User - Read and write
Group - Read
Others - Read
11. Now shutdown the LePad and then Power On.
12. Use file Manager and go to folder where you initially copied the files. Touch the Vending.apk to install it.
13. Now you should have Google market icon on Last Desktop.
14. All the best. You are needed to have a gmail account to use Google market.
I will look were i can Upload the files. If you start and stop the market it will automatik update to the 4.3.3
h**p://dl.dropbox.com/u/56215670/rootet.rar
Hope i could you Help
MFG
Thorwald
Any chance that there will be an Custom Rom For the S1 with android v2.3 or v4?
New LEOS vers. in China
Ther is a new leos version upcomming in china vers Nr WiFi001_C_S_1.0100.3014.rar
Hopefully i will update it in a Few days after Test
MFG
Thorwald

[Q] Getting ZTE Open to 1.1

I recently got a ZTE Open via ebay UK.
First thing to do is upgrade to 1.1 to get fastboot functionality, unfortunately only one of the two downloads on ztedevices.com for the zte open seems to download to my computer correctly, and that is 2014012010220351.zip which from what i've read is for taking a 1.1 to 1.1 with fastboot enabled.
The other download 2014012010205829.zip which is the one that I think I need takes hours rather than minutes to download, and once downloaded nothing on my PC thinks it is a valid zip archive.
Questions
Has anyone successfully downloaded and used contents of 2014012010205829.zip ? -
link is titled: OPEN(European Standard) SD card upgrading instruction & software package(ebay)-2376270OPEN_EU_DEV_FFOS_V1.1.0B02(for V1.0)
Thanks in advance
r1b2718 said:
I recently got a ZTE Open via ebay UK.
First thing to do is upgrade to 1.1 to get fastboot functionality, unfortunately only one of the two downloads on ztedevices.com for the zte open seems to download to my computer correctly, and that is 2014012010220351.zip which from what i've read is for taking a 1.1 to 1.1 with fastboot enabled.
The other download 2014012010205829.zip which is the one that I think I need takes hours rather than minutes to download, and once downloaded nothing on my PC thinks it is a valid zip archive.
Questions
Has anyone successfully downloaded and used contents of 2014012010205829.zip ? -
link is titled: OPEN(European Standard) SD card upgrading instruction & software package(ebay)-2376270OPEN_EU_DEV_FFOS_V1.1.0B02(for V1.0)
Thanks in advance
Click to expand...
Click to collapse
For me the downloads are dodgy in the sense that sometimes they download within minutes and sometimes they begin downloading with an estimated time of minutes and then indefinitely increase in time. The only fix I've found is trying to download the files again at a later time. I hope this helps, if not, ask someone with knowledge of uploading files to the internet to help you out by downloading and uploading it to somewhere for you

A comprehensive guide to the Lenovo Yoga Tab 3 Pro (YT3-X90*) and a Cooked ROM

THESE COOKED ROMS ASSUME YOU HAVE ALREADY AN UNLOCKED BOOTLOADER AND TWRP AS RECOVERY SYSTEM. You can flash them using TWRP, after wiping ART, cache, data, boot and system partitions.
FINAL RELEASE: Well... this is the final release from me and it is specifically for the WiFi model. I hope it is worth it for you. It is more stable and somewhat updated, anyway, if you use a X90F (wifi model) you will probably like it. The other versions are still up for whatever reason. Here's the link. Follow this guide by @Quardah if you are coming from a factory ROM. Go to post 46 if you can't get past the setup wizard. A barely tested (by @Nuihc88) version for the 3G (X90L) model can be found here.
NOTICE: If you find this work useful, mirror it. I won't be hosting it for free forever and it is becoming a burden to my Nextcloud installation. One would say this is a pretty much forgotten thread, but I'm seeing almost daily download activity. I'm putting the ROM files offline now and getting away from XDA for a while. Please don't DM me for the files. If you are looking for them, ask others in this thread. Good bye.
||||||||||||||||||| FROM HERE IS JUST INFORMATION YOU PROBABLY DON'T NEED |||||||||||||||||||
Spoiler: NEWS THAT ARE NOT ANYMORE.
APRIL 9, 2021: You can find in these links a new version of the cooked ROM.
The link for the updated cooked ROM is: https://centsoarer.ddns.net/s/Y8o3eoBK4Ryx5RP. This is a version with GAPPS updated: https://centsoarer.ddns.net/s/FPKjgQcmW3CHZCw. Feel free to mirror, unless you are afraid of Lenovo's lawyers, but don't forget to share the link.
My personal version... even more debloated (if you don't need chinese, japanese, korean, or russian input support/apps) and with CPU tweaks for my own usage: https://centsoarer.ddns.net/s/jcCDAgNedryGRjo
KNOWN ISSUES AND SOLUTIONS:
1) One random reboot after the first boot will happen and it is normal.
2) I'd reccommend to stay with Magisk 21.4 for a while, Magisk Manager >21.4 won't manage your extensions.
3) If you can't get past the initial Setup Wizard check post 46. Basically you have to boot into bootloader, erase the config partition and format it again.
4) Needs confirmation, but versions with signature spoofing patches seem to break Lenovo's SmartSide Bar.
JUNE 12: Fast update on the Cooked ROM and TWRP and KERNEL. They are not as universal as I implied before. Proceed carefully since they may not work four your device/firmware. Make a Nandroid backup and only flash with testing purposes.
JUNE 5: So, I know this is not what everybody who owns this tablet wants to have (that is Android 9 or 10 of course) but, in recent weeks Lenovo updated the firmware of this tablets. It still is a Marshmallow one and it still sucks big time but I took it as a base and cooked it to deliver a newer TWRP recovery with compression, a flashable modified kernel and a cooked flashable stock ROM to free the owners of this tablets from the treacherous path of making this hardware to work properly. If you want a better overall experience and are in stock firmware you just need to Unlock your bootloader, flash TWRP, Format data partition (not only wipe), Wipe Cache, Dalvik/ART, System and DATA and flash the Cooked ROM to put this tablet in a sweeter spot. For details go to post #2!
JUNE 3: Been trying to get to know some of the source code available for Cherry Trail devices and I am fairly lost at building TWRP from source. Anyway, I ported a newer TWRP recovery IMG file for the YT3-X90F (maybe L, X, Y and Z) from the TWRP image for the Chuwi Hi10 Pro tablet from here, using AIK-Linux. The result is in the second post labeled as beta, since I only tested in the YT3-X90F model, running lollipop firmware. So far, it works fine flashing ZIP archives, backing up and restoring backups. Advantages? Well, backups are way lighter if you enable compression (like half the size), higher resolution, twrp turns off the screen with a timeout and whatever made them bump from version 2 to 3. While I could port a newer TWRP version, I just wanted to have lighter backups with compression... so maybe it is what it is .
ORIGINAL POST STARTS HERE. This is general information that I collected for geeks or desperate users that bricked their tablets. When I started this post it wasn't intended to produce a cooked ROM that would include most of these hacks. You don't need this if your tablet boots to Android or TWRP. You also don't need this if you are ready to flash the cooked ROM.
(This is a lenghty post. I suggest you to navigate by section header and find the one you might need.)
There are several Lenovo Yoga 3 tablet models out there and, while some of them enjoy of prime community support as the Yoga Tab 3 Plus, this Intel Atom powered tablet is pretty much forgotten and, at the same time, users were recently buying this tablet, which is a great piece of hardware but has the most terrible support by Lenovo.
Spoiler: WHAT LENOVO TABLET(S) IS THIS GUIDE FOR?
Basically, this is that Lenovo tablet with an attached projector and an Intel Atom Cherry Trail x5 Z8500. There are several models, though, to my knowledge they vary in their code names in the last letter, the two most basic ones (2GB RAM, 32 GB ROM) are the YT3-X90F and the YT3-X90L, the former connects to the internet by WiFi and the latter being the one with LTE/Phone capabilities. There are other models, though, and they vary on the amount of RAM and internal storage. Apparently, the YT3-X90[YX] models (the 4/64 GB refresh) have some use for these firmwares we describe, but in a very specific way, if you own a Y or X model, keep reading, especially the next section.
Spoiler: EXPLAINING HOW TO FIND THE RIGHT STOCK FIRMWARE
Lenovo support has been terrible (there are no words to describe it, really), so they launched this tablet with Android 5.1 Lollipop and they maintained it for a while but were very slow to deliver Android 6.0 Marshmallow. In fact, there was already Android Nougat, when they sent the Marshmallow update. Nevertheless, the update was bad. Performance issues were always a thing and some functionality went lost in the update (less intuitive multiple windows, a crippled recents activity/screen, and a laggy overall experience). Bottom line, they launched a curated Android Lollipop 5.1 firmware with security updates until March 2016 (striked because the last lollipop update f*cks up my sensors, except the light one) and a half-assed Android Marshmallow 6.0.1 firmware.
Of course, at the time, I'm guessing most of us upgraded to Android Marshmallow 6.0.1, hoping the upgrade would fix the issues in Lollipop or with security patches in mind. The reality was that Android 6.0.1 wasn't nearly as maintained as 5.1 and security ambitions went nowhere. So, we got the upgrade all right, but at this point, both Android versions can be considered inherently insecure and we really shouldn't be using it for sensitive work.
OK, there are several Android 5.1 and 6.0 firmwares, you can recognize them because they are all over the internet typically in a compressed format. For example, this firmware hosted in androidhost.ru named:
YT3-X90F_ENG_S100265_1601281130_WW24_ROW
Is a firmware for the Lenovo Yoga Tab 3 (YT3) Pro (X90) Wifi Version (F). The ENG part is an indication of the build type, ENG is an engineer build while USR is probably a firmware for the end user (this is common now that I know a bit more about AOSP source code), it is a Lollipop firmware (S1, Marshmallow would be a S2) with update version (00265), date of compilation and a good estimate of its security patch (1601281130), the WW24 is the weekly release version of the Android kernel for Intel devices (the latest, in May 2020, being WW31 which is exactly the same as WW28 and not updated since 2016), the final part means it is the global ROM version (ROW, opossed to the Chinese version CN). This is the latest Lollipop firmware I am aware of, so, as an example, an imaginary Android Marshmallow Chinese firmware for the LTE version of the Yoga Tab 3 would look like:
YT3-X90L_USR_S200013_1610141535_WW24_CN
As an additional note the Chinese ROMS, I presume, are not trusty but they are also Google-free for what it's worth. On the other hand, they ship with a "Lenovo Services Framework" that should be as intrusive as the Google Play Services. Oh, also, baidu and yandex, and, really, any less traditional search engine can help you find a fitting firmware.
Spoiler: EXPLAINING HOW TO FLASH A STOCK FIRMWARE (DOWNGRADE TO LOLLIPOP AND UNBRICK)
I did test several firmwares, chinese and global, lollipop and marshmallow and the safest and easiest way to flash them is by using the Intel Platform Flash Tool Lite . I can't say I trust in this site, but it hosts a handy tutorial on how to use it, though, is pretty intuitive. The software exists for Mac, Windows and Linux, be sure you are in, at least, the 5.8.x version, this is important to avoid the need to install some special drivers separately as a pre-requisite. Grossly, Intel Flash Tool Lite works like this:
0) Turn off your tablet if it is on.
1) Launch Intel Platform Flash Tool Lite.
2) If your downloaded firmware is in zip format load it with the blue "Browse..." button.
2 bis) OR, if your firmware is in other compressed formats, uncompress it first. After this use the "Browse..." button to load the "flash.json" file.
3) In Configuration option select "blank" if it isn't set already. Optionally, un-tick the "On-demand flash" option to have more control of this process. Also, maybe you can use the "erase" configuration here.
4) Start your tablet in DNX mode. To do this, press Vol- and hold it, then Vol+ and keep holding both, then press the Power button until it turns on and you see the Lenovo logo and some text indicating you are in said mode.
5) Connect your Yoga Tablet with a USB cable and your Intel Platform Flash Tool Lite windows should show it as detected. Now you can proceed using the blue "Start to flash" button.
6) Keep an eye on your tablet, since some firmwares will prompt to set some more options. Unless you know what you are doing, answer "Yes" to any question.
7) Reboot and wait.
If a couple hours have passed and the tablet hasn't booted, maybe you should try another firmware.
IMPORTANT NOTE AND INSTRUCTIONS FOR YT3-X90Y AND POTENTIALLY YT3-X90X USERS: I don't know the rules in xda about linking to other forums but in certain forum there is an answered question about the Y model (the 4/64 GB WiFi only refresh) on how to flash a firmware. Instructions are the same as I gave in this section, except, apparently, you need to do it twice, first with the ENG version and the second time with the USR version except you are not using the flash.json file, this time you'll browse for the flash_factory_1st_stage.json one and the factory1st configuration in fastboot. It is not clear what are the consequences of not doing it this way or what if you combine different firmware versions (it would be interesting to have a tester here). Notice please, these firmwares are marked for the YT3-X90F model. So, clarifying:
1) Follow the instructions above to flash the YT3-X90F_ENG firmware.
2) Power off your tablet.
3) Boot into bootloader (not in DNX, you need to boot into bootloader by powering on while holding Vol+).
4) From the YT3-X90F_USR firmware folder use Intel Platform Flashing Tool Lite to load the flash_factory_1st_stage.json and select the factory1st configuration.
5) After flashing the USR firmware, reboot and you should be good to go.
METANOTE: This wasn't tested by me, please do this only when you are hopeless with your hardware. This is just an educated guess but I bet it works the same with the YT3-X90L (the LTE version 2/32 GB Yoga Tab 3 Pro) and the YT3-X90X (the 4/64 GB refresh).
ALTERNATIVE WAY TO FLASH A STOCK FIRMWARE (ADVANCED USERS, requires fastboot)
Well, there is no need, really, to use that Intel tool. In my search for a lollipop firmware (I wanted to downgrade from Marshmallow) I found the firmware YT3-X90F_USR_S100195_1512052308_WW24_ROW in www.firmware247.com or www.androidfilehost.com (IMPORTANT: please read the note on downgrading to Android 5.1 Lollipop in the note at the end of this section). This firmware was special since, if you are in Windows and have fastboot executable ready and in place, you can run a script (run_me.bat) in the Windows terminal (CMD) or Powershell to flash the firmware semi-automatically. I think this firmware was modified, though, since I found differences in the boot.img when compared with stock firmwares. This script is credited to XDA members @ionioni and @joesnose and you can replicate its steps if you:
0) Turn off your tablet if it is on.
1) Start your tablet in DNX mode. To do this, press Vol- and hold it, then Vol+ and keep holding both, then press the Power button until it turns on and you see the Lenovo logo and some text indicating you are in said mode.
2) Connect your tablet to your fastboot enabled PC using a USB cable.
3) Input "fastboot flash osloader loader.efi"
4) Wait 5 seconds to be sure the loader flash finishes.
5) Reboot into Bootloader. If you don't know how, one way is to hold Vol+ and Power on your tablet.
6) Input "fastboot oem unlock" and confirm using Vol keys to select the right option and the Power button to enter it.
7) Input "fastboot flash system system.img"
8) Input "fastboot flash boot boot.img"
9) Input "fastboot flash recovery recovery.img"
10) Input "fastboot flash bootloader bootloader.img"
Follow your instincts, since I don't know if these IMG files are always named the same. You can get these IMG files from downloaded sources or dump them yourself using dd command.
NOTE ON DOWNGRADING TO ANDROID LOLLIPOP 5.1: So, one of my main concerns has been to go back to Android Lollipop. There is a last version of Lollipop from where you can upgrade to Marshmallow with a security patch from March 2016. Nevertheless, you MAY end up loosing other sensors except the light one. If this happens, you need to use a complete firmware flash using Intel Platform Flash Tool Lite. In my experience, some boot images are not compatible with other weird partitions like country or misc.
Spoiler: TWEAKS ALREADY IN THE COOKED ROM
The first boot takes some time even amounting for the time of the setup itself. By the time you are in the launcher tapping on app's icons you think there's nothing wrong with our device, but after some apps are in memory, you notice some lag. You think "OK, it is updating, but soon it'll settle", but it does not. So, you reboot again after updates and fire up a terminal emulator and connect to your tablet using a USB cable with USB debugging turned on and issue a free command to find something like this:
Code:
total used free shared buffers
Mem: 1950372 1820964 129408 0 7756
Swap: 524284 10740 513544
Total: 2474656 1831704 642952
Which means you have a total of ~2.5 GB (this is the 2 GB model). So, did I download that extra half GB of RAM or Lenovo was feeling generous? Well, no. The issue here is Lenovo built the kernel with zRAM support which is a technology included in Linux that reserves space in RAM to quickly compress and uncompress pages of data exceeding our physical amount of RAM installed (2 GB). This is not Virtual Memory as in a swap file/partition or Windows' Page File inside storage media. zRAM literally reserves a fixed amount of physical RAM space (blocks) to expand it by compressing data. The consequence is you loose "fast RAM" (THE RAM) and gain some "slow RAM" (the zRAM). You also sacrifice some CPU power to compress/decompress data and, with this, some battery juice is also lost.
That does not sound like a terrible trade-off for a RAM-limited device, one would think. Another interesting thing would be WHEN to send this piling data in "fast RAM" to the compressed space and WHEN to get it back. Two parameters control the WHENS, one is called "swappiness" (when to send it to the compressed space, the "slow RAM") and the other may be the "vfs_cache_pressure" (when to uncompress it and send it back to the "fast RAM"). And this is where the main problem is, really, because the kernel, Linux, is pressing the RAM constantly to send some less prioritary data to "slow RAM" and, at the same time, is trying constantly to send compressed data back to the "fast RAM". Summarizing, this kernel behavior is practically minimizing the fast RAM amount and usage while maximizing the "slow RAM" usage. This is nuts, by default a swappiness and a vfs_cache_pressure of 100 are not even default for servers, these parameters extremely prioritize that processes can get done no matter how slow they get, and they are even more nuts when Android is designed to work without swap space.
What that free command is telling us is the tablet is using the "slow RAM" even when we only just turned it on. Fortunately there are two ways to fix this problem: one is to completely disable zRAM, the other one is to use ZRAM a whole lot less by tweaking the swappiness and vfs_cache_pressure parameters. This can be easily done with the following sentences in a rooted tablet:
Code:
# echo 5 > /proc/sys/vm/swappiness
# echo 50 > echo 5 > /proc/sys/vm/vfs_cache_pressure
Or, to regain the whole fast RAM:
Code:
# swapoff /dev/block/zram*
One caveat of the first method, reducing swappiness, is there is still a lot of RAM (one quarter of the whole RAM in a 2 GB device) reserved as "slow RAM".
SOME ROMS DID NOT ENABLE KERNEL SAMEPAGE MERGING, UNFORTUNATELY
Additional to the sorry implementation of zRAM, some firmwares support a fabulous Linux tool to reduce RAM usage called Kernel Samepage Merging (KSM) but they don't use it by default. This software runs at kernel level, so, it really is CPU-wise inexpensive and, opposite to zRAM it can actually recover some RAM usage by reducing the amount of data flagged as redundant in physical RAM by merging it. KSM is good for you and you should have it always enabled by issuing the following command as root:
Code:
# echo 1 > /sys/kernel/mm/ksm/run
STOP WRITING AND FIX MY RAM! PLEASE!
Well... are there any people interested on this? With the above information you can write a script to execute at boot. Something like this should work in any version of the firmware:
Code:
#!/system/bin/sh
# Mount system as rw
busybox mount -o remount,rw -t auto /system
# Tweaking swappiness in zram
echo "5" > /proc/sys/vm/swappiness
echo "50" > /proc/sys/vm/vfs_cache_pressure
# Activating Kernel Samepage Merging
echo 1 > /sys/kernel/mm/ksm/run
# Remount system as ro. noatime option for faster and volatile system
# busybox mount -o ro,remount,noatime /system
busybox mount -o ro,remount /system
exit 1
Or, you can unpack the boot.img and modify the init.cht_ffd.rc (lollipop) or the init.r2_cht_ffd.rc (marshmallow) files to write these values as default... or, if there is interest for something easier, I can produce this boot.img files for you to flash using fastboot.
ROOTING THE LENOVO YOGA TAB 3 PRO (YT3-X90[FL])
Here I am not gonna write a lot. Instructions were given in this thread. I'd only recommend to put vm.targetutilization at 0.8 top 0.85 in system/build.prop
After rooting, debloat your firmware. I use the app "/system/app mover" from Fdroid to convert to user apps and uninstall them. Also, if rooting is not your cup of tea, you can install AppOps software to freeze all those apps that you don't use regularly. Also, I couldn't patch my services.jar for Signature Spoofing with Nanodroid patcher in the most recent lollipop firmware, but it did work in Marshmallow... anyway I'll do it manually.
ARE YT3-X90F AND YT3-X90L FIRMWARES INTERCHANGEABLE?
I own a WiFi only device (YT3-X90F) so I can't assert they are interchangeable. If I owned the LTE version and use a WiFi firmware I would expect to loose LTE functionality. Now, on the other direction is more interesting because I've been using a LTE firmware version for weeks (as a matter of fact, the one joesnose linked in his How-To debrick this tablet, flashed with the instructions I posted for advanced users it even updated to recent 2020 firmwares). The only tweak you need for this to work well is to add "ro.ril.disable=1" in the build.prop file. So, yes, firmware for the LTE version work in the WiFi version but kind of not vice versa.
Spoiler: YT3-X90(FL) UN-DEVELOPMENT
No news here. All capable people interested on developing for this device are all done with Lenovo and their attitude against Open Source. Don't expect your situation to change.
I'm happy to know there are still a couple of developers interested on this device. I won't cite them by linking their names but they are OOEvil and alquez, the first guy is trying to make a Generic System Image (GSI) ROM compatible with our tablet, I don't know the details so I wouldn't go further. Alquez has been active in this thread and, while he is trying to figure out how to build a kernel, he believes the best way to start having some alternative to official Lenovo firmware is by using a firmware kernel (a prebuilt kernel) to, first, build a more up-to-date TWRP recovery.img and from there try to build CyanogenMod 13, which was based on Android Marshmallow 6.0.1. My guess is newer Android versions wouldn't work if we can't build the kernel from source.
PHOTO ALBUM OF YT3/X90Y BIOS
This photo album documenting every screen option in the BIOS of the Yoga Tab 3 Pro may or may not help someone, but it contains a lot of useful hardware information and guidance for those attempting to boot something else than the original Android 5 or 6 firmware. Using this options, that are accessible through F2 at boot with an attached USB keyboard, you could try Linux distributions on the tablet or even attempt to run Windows, @alquez informs it works fine with a recent distro but the mainline kernel is lacking touchscreen and battery support. This is absolutely his work and he asked me to share it. I hope it serves someone. It is hosted in a rather obscure website but it was the only reasonable placeholder I could find for the 321 photos.
Hope this helps someone, I just didn't want to keep it to myself. Have a nice day!
Just remember, if your tablet is 3G capable I strongly suggest that you modify the line "ro.lenovo.tablet=wifi" to "ro.lenovo.tablet=3gdata" and remove the line "ro.radio.noril=true" to your build.prop file in /system. To do this you can use the section Build.prop Editor of the Kernel Adiutor app or you can do it manually if you have already a method to modify system files. If you do not use mobile data at all, you may leave the build.prop as it is, you'll save a lot of battery by using only wifi.
Spoiler: Some old info here, but maybe useful
ONLY FOR TESTING: Cooked ROM, newer TWRP and tweaked kernel
ONLY TRY THESE FOR TESTING PURPOSES, THE TWEAKS ARE ALL SAFE TO USE BUT ONLY FLASH FOR TESTING PURPOSES, PLEASE. FIRST, TRY TO USE FASTBOOT TO BOOT THE boot.img FILE WITHOUT FLASHING: IF IT BOOTS GO AHEAD AND TRY THE OTHER FILES (fastboot boot boot.img). THE TWRP IS NOT AS STABLE AS THE OTHER ONE HERE AT XDA BUT ALLOWS TO USE ZIP COMPRESSION IN BACKUPS. I AM NOT GONNA BE AROUND. IF YOU TRY SOMETHING MAKE A BACKUP FIRST. THIS DEVICE IS MESSY AS F*CK.
Spoiler: Some old info here, but maybe useful
I wrote a very detailed guide about these files I uploaded to my Nextcloud that include the newer TWRP-3.0.2, a TWRP flashable Cooked ROM and a separate kernel (boot.img) in case your system is already setup, but the post went to some XDA void and didn't upload. These are based on the YT3-X90L latest firmware, but they work on the X90F model too. The TWRP should work with Lollipop and Marshmallow firmwares.
I can't write everything again, so, the kernel contains better management of RAM and emmc (internal) memory, a 256 MB zRAM space instead of 512 and a more conservative approach to LowMemoryKiller.
The cooked ROM includes the described kernel and debloated apps, it's already rooted with Magisk (you can unroot with Magisk Uninstaller), an updated Busybox build, su.d support (I plan to use it with AFWall+), zipaligned apps, etc. It is for the X90L but possibly works for the other Yoga Tab 3 Pro models. It works for the X90F but it will reboot once after the first boot because the RIL configuration times out. To install the cooked ROM you need to:
0) Know that by doing this you will loose pretty much everything in your tablet. You start from scratch if everything goes smooth, if not you could possibly end up with a system without an OS. The usual stuff when you are customizing your system.
1) Boot into TWRP and make a Nandroid backup. IT IS IMPORTANT because @joesnose had problems with a "random reboot" and lost Bluetooth/WiFi after it. I am trying to look into this. The only difference is his tablet has 4 GB RAM and probably a different firmware.
2) Wipe cache, Dalvik/ART, System and Data in TWRP - Wipe, Advanced Wipe menu. If your tablet is encrypted, or in factory firmware you also need to explicitly use the button "Format Data partition" and confirm writing "yes" in the format procedure prompt. You will loose any configuration made to your tablet.
3) Install the superr_stockMM.zip wich is flashable by selecting the file from your Internal tablet memory, using the Install button in the main TWRP interface.
FOUR IMPORTANT NOTES TO COMMON ISSUES:
If you come from a stock firmware your data partition is encrypted. You need to pass a blank password in TWRP to continue to use the custom recovery. You also need to format data partition before flashing the cooked ROM.
If your tablet is WiFi-only I strongly suggest that you modify the line "ro.lenovo.tablet=3gdata" to "ro.lenovo.tablet=wifi" and add the line "ro.radio.noril=true" to your build.prop file in /system. To do this you can use the section Build.prop Editor of the Kernel Adiutor app or you can do it manually if you have already a method to modify system files. In Lollipop firmware you use "ro.ril.disable=1" instead of "ro.radio.noril=true" to get the same effect: sort of a conversion to WIFI-only tablet from LTE models. I'd argue this is useful to do if you are gonna be without LTE connection/service for long periods of time and I can think a couple of other uses.
Do not use stock Lenovo launcher unless you uninstall Magisk... they are incompatible for reasons I don't care to know and the Launcher will constantly FC (it is a pain in the arse).
If you are still expecting better performance I am sure there are some tweaks left in RAM management but it wont go too much further in 2 GB devices. Instead, you may consider to lower your display resolution and pixel density to something reasonable as 1400x2240 or even 1200x1920 maintaining the same aspect ratio. To do this you do not need to have root but you need to interact with the tablet using ADB. First change the size of your display:
Code:
adb shell wm size 1400x2240
Then adjust your density:
Code:
adb shell wm density 260
If still is not enough you can go even further with 1200x1920 and 224, use the same method to go back to stock with 1600x2560 and 300 to 302. This won't need a reboot but will probably cause an inconsistent UI that will lead to FCs and random reboot. You can just reboot after applying these tweaks. Unless you are really sight-gifted you won't notice a lot has changed but you will be dealing with 2.x Mpixels instead of 4.x Mpixels and that will help with your overall performance as well as your battery life sacrificing a pixel count that most of the people wouldn't even notice. If you did this correctly, in the next boot sequences you'll notice an offset on the Lenovo orange logo.
It is important to say that your display supports 1600x2560 pixels physically, but I'm assuming the GPU has no dedicated RAM and uses the device's, so, by reducing the quantity of pixels the GPU needs to deal with, the pressure on the device's RAM is also reduced.
EXTRA TIP: If boot annoys you just delete /system/media/boot.wav, bootanimation.zip and shutdownanimation.zip and you'll get a silent boot and the generic android boot animation.
Hope you enjoy your tablet!
TWRP-3.0.2.0- BETA: Again, this is not a flashable zip. Uncompress first and test the recovery system using "fastboot boot twrp_yt3-x90f_beta.img". If everything works for you, you may want to flash it permanently rebooting to bootloader and flashing with "fastboot flash recovery twrp_yt3-x90f_beta.img". Remember I did not test this in Marshmallow yet.
FEATURES:
- Fixed RAM issues (swapiness 10, vfs_cache_size 50 and disabled dynamic low memory killer tweaks and minfree values).
- Reduced zRAM size to only 256 MB.
- Tweaked interactive CPU scheduler to use other than min and max frequencies (but still responsive). The tweaks are based on the Advanced Interactive Governor Tweaks Guide. This may save battery life.
- Max frequency capped to 2.08 GHz (this is not great if you are a gamer). This tablet throttles when using max frequency for a long time, so, to save battery and keep it cooler I tweaked the CPU to run slower.
- Tweaked I/O schedulers to use deadline governor and read ahead cache to 640 kb (used benchmarks to get to this value).
- Force encryption disabled (to avoid applying ionioni script after flashing). Still needs to format data partition. You can encrypt your data partition later through Configuration -> Security user interface.
- Implemented native init.d support (not su.d anymore and no need to root the main OS).
- Busybox updated.
- Rooted with Magisk by default ( you can use Magisk uninstaller to unroot).
- Debloated apps. I also deleted Lenovo User Experience Program which was asking for root privileges even when you don't opt in to the Lenovo UE Program at setup wizard. I find this behavior shady.
-Multi-window mode is available in Developer Options and needs to be activated by you. In this mode if an app is compatible with multi-window mode you can double-tap on its title bar to enable Window mode. This function was more transparent in Lollipop firmware but it is still there in Marshmallow firmware if you change the build type to userdebug instead of user in build.prop (that's how I enabled it in the Cooked ROM).
- There are also other tweaks in VM and KSM.
And that's it, I'm not trying to change a lot, only the fundamental issues. But I suggest some other tweaks up there.
Such a shame. I love my Yoga Tab 3 Pro. Great hardware. But the software. Thanx anyway for your work.
Very nice write up. Thanks.
joesnose said:
Very nice write up. Thanks.
Click to expand...
Click to collapse
You're welcome. Thanks to you, while learning about this hardware your username pops everywhere.
jahfaby said:
Such a shame. I love my Yoga Tab 3 Pro. Great hardware. But the software. Thanx anyway for your work.
Click to expand...
Click to collapse
It really, really sucks. Let's hope something interesting happens after these strange and recent updates.
CENTSOARER said:
V1: The zip name boot_mod_mm.zip is based on the latest boot IMG provided by Lenovo. You need to first uncompress and flash it using fastboot (this is not a TWRP flshable zip). If you are uncomfortable flashing, you can test it only by issuing "fastboot boot boot_mm_march20_mod.img" once uncompressed, or, if you feel fine using it you can flash it permanently by using the command "fastboot flash boot boot_mm_march20_mod.img". This boot IMG will only work with Marshmallow firmwares in both YT3-X90(FL).
FEATURES:
- Fixed RAM issues (swapiness, vfs_cache_size and low memory killer tweaks).
- Reduced zRAM size to only 128 MB.
- Tweaked interactive CPU scheduler to use other than min and max frequencies (but still responsive). This saves battery life.
- Max frequency capped to 2.08 GHz (this is not great if you are a gamer). This tablet throttles when using max frequency for a long time, so, to save battery and keep it cooler I tweaked the CPU to run slower.
- Tweaked I/O schedulers to use deadline governor.
- Force encryption disabled (it's unnecesary to apply ionioni script now). Still needs to format data partition. You can encrypt your data partition later through Configuration->Security user interface.
Click to expand...
Click to collapse
Thanks for this. Going to take it for a spin.
joesnose said:
Thanks for this. Going to take it for a spin.
Click to expand...
Click to collapse
Please, please provide feedback and don't forget to wipe caches.
alquez said:
"No news here. All capable people interested on developing for this device are all done with Lenovo and their attitude against Open Source. Don't expect your situation to change."
https://github.com/intel/ProductionKernelQuilts this repository containts patches necessary to create base 3.14.55 and 3.14.64 uefi/cht-m1stable kernel tree. The same tree that was butchered by Lenovo in their OPEN_SOURCE "release".
Check this file https://github.com/intel/ProductionKernelQuilts/blob/master/uefi/cht-m1stable/ChangeReport.md and the WW24 part in the "YT3-X90F_ENG_S100265_1601281130_WW24_ROW" will become more clear
Quilt manual: https://elinux.org/images/7/74/Maintaining_Multiple_Android_Linux_Kernels_at_Intel.pdf
If someone would be looking for a good piece to start: the best would be to recreate 3.14.55 or 3.14.64 from the quilts, use the x86_64 defconfig and build a kernel which can be booted. In order to test this, the best solution is to repack TWRP with the new kernel and do "fastboot boot" without flashing, until it boots and the touch screen is working. There's no other way i'm afraid.
I have prepared complete photo documentation of UEFI Bios, i can share, currently moving to different google photos account. Its over 300 photos.
Please, set up a Discord channel if you want to proceed. The first month will be quite boring and daunting because it's going to be build -> repack -> boot -> rant
Click to expand...
Click to collapse
In my defense, when I wrote that sentence was after taking a peek on your github profile, I figured you were just done with the Yoga Tab 3 Pro. I am really, really glad you're still trying and I recognize you are very capable of changing things for this device. I appreciate the sources you link but I am afraid I am useless as a developer, partly because of a lack of time and partly because of a lack of adequate training. I will try to help as much as I can, though. Thanks for the post.
alquez said:
No worries, however if anyone is interested how to actually crunch this one: we have a working prebuild kernel which can be pulled of boot image, and we have a working TWRP, however it looks like TWRP wasn't actually built from source, but cooked using android kitchen so we're still missing a device tree, which in my opinion is a good place to start, because you can use prebuilt kernel to build recovery and lineageos/aosp (it's deprecated but we're talking about android 6 aka cm-13.0/lineage 13.0). If I can create a most basic device tree which is capable of building recovery from scratch useing binary kernel and modules, i'd say were' good, because the next part would be adding more binary blobs from the official software, and we can skip the kernel source part for now until we have lineageos build 13 working). I started experimenting on xiaomi latte tree because it wasnt split like Z00A. It's not gonna be a proper port but it should work from now (i think)
@joesnose did you cook or compile TWRP? It's important
Ok, I'm at the stage i have two folders. The one is unpacked working TWRP, the other one is unpacked compilation i'm building, which means im able to build TWRP from source with binary kernel, but it's not working yet. The goal is make the left one look like the right one by adjusting various parts in BoardConfig.mk and copying files.. If someone has right partition sizes for BoardConfig.mk that would be really helpful, the values i calculated suck and don'y boot yet
Click to expand...
Click to collapse
Uhmmm, I've been there and took some notes with some "GNU shell Fu". What sizes are you using right now?
And regarding the WW part of the name I've noticed the recent updates are marked as WW17 opposed to WW28 which was the latest stable with any changes. Any idea why Lenovo used WW17 to update the Yoga Tab 3 Pro recently?
alquez said:
update, ive managed to boot vanilla android-x86 x64 6.0.1 build without touching the kernel yet and different TWRP (3.1.1.0) with kernel swap
Click to expand...
Click to collapse
Geez, I was excited because I read Ubuntu booted on this hardware but then I realized it was the Yoga 3 tablet but not the Yoga Tab 3, goddamnit. Keep up the good work!
alquez said:
Um Ubuntu 20.04 boots with working accelerometer so the screen rotation works + wifi, and probably audio i forgot to play youtube video, the stuff missing is battery, touchscreen and projector.
To test it you need to connect a usb hub using usb otg, put ubuntu and a keyboard in the hub, boot, and press f2 really fast if you haven't enabled slow boot yet. You can even boot
Xubuntu to ram and remove flash drive. It's a pc architecture after all and most of the processor related stuff is in the linux mainline since 4.11
Recently i was checking why the Windows 10 installer crashes on ACPI Error.
Click to expand...
Click to collapse
Oh, I will have fun doing this kind of stuff at the end of the year. It must run swiftly with i3, provided you won't get touchscreen support.
alquez said:
Geting TS and a battery running is a mandatory, the next is the projector. The rest is pretty much working. I'm building generic celadon x86 atm and the beast is huge it's like 18% now after two hours on -j8 on i7. Maybe we can give this old monster a new life
edit:
And i need to add 480gb drive ;/
Code:
/dev/sdc1 229G 210G 6,7G 97% /home/android
Click to expand...
Click to collapse
I am afraid those are the peripherals that will keep you in 3.14.55/64 Linux, at least for a while , unless you know something more (wouldn't be surprised).
Are those GB for source code or for cache? Both? Jesus... the thing is huge but reading the unpacked boot.img makes much more sense now.
It was ionioni who made the twrp for the device. I dont have the foggiest how he did it.
---------- Post added at 01:23 AM ---------- Previous post was at 01:18 AM ----------
Wow! I missed lot, looks like you have made some serious progress here. very well done.
alquez said:
I contacted my friend and he told me to compare these two folders:
https://github.com/alquez/lenovo_yt...l/cht/arch/x86/platform/intel-mid/device_libs
https://github.com/torvalds/linux/tree/master/arch/x86/platform/intel-mid/device_libs
the new files in "lenovo tree" are the modules we're after, mostly and it's a place to start
I need to ask inioni about twrp.
Click to expand...
Click to collapse
I will guess it was ported from the Yoga Tab 2. I will edit this post soon.
alquez said:
Nice! There's big chance the modules are reused somewhere. We can compare these. I think the two folders in
https://github.com/alquez/lenovo_yt3_x90_osc/tree/master/kernel/cht/drivers/input/touchscreen
which are missing from vanilla tree are two separate drivers and one is for "any pen" driver. Can you ask someone porting modules recently
to help us refresh my memory
[edit]
I've got in touch with TeamBliss of BlissRoms , they are working on cherrytrail tree
Click to expand...
Click to collapse
Nah, I couldn't confirm it was ported. A lot of posts were removed when XDA enforced the GPL measures to its developers.
About BlissRoms, it just makes sense they are working on Cherry trail. I hope you and those guys can achieve something soon. I mean, it's a 2 GB RAM device but the display, projector and dolby audio system are worth for a better fate than Lenovo's plans.
alquez said:
4GB of ram 4 cpu cores, Hardware virtualization support, fast gpu and fast emmc memory. It's a beast, way ahead of it's time.
Click to expand...
Click to collapse
Well, I have the 2 GB RAM model, so my expectations are conservative. Anyway, don't believe I'm a hardcore user, so it's plenty enough for me, considering I won't even flash Google apps. I am now settled with Lollipop, since I need apps not getting killed by damn Doze. It is a shame how OEMs can limit a device like this one. Crond, init.d, bad zRAM, shell, even busybox... frequently the OS is crippled. I read somewhere Doze can be disabled in build.prop or something but one thing I just hate is the recents screen in Marshmallow firmware (my God, is terrible!) and can't be easily changed for something like OmniSwitch. I mean, for a mobile device you have an unusual architecture, why limit it further? Damn, I wish BlissRoms come up with a working build.
Hey, @alquez, have you tried Linux 5.7 on the tablet? I saw this article and seems like the touchscreen may work with the next mainline kernel release. I mean, right now is on RC7, should be stable enough to compile and try (I'd try it, but can't get to my workstations thanks to the virus).
EDIT: Ah... I was looking into my device and it comes with a HiDeep touchscreen (cat /dev/input/event3), the linked news is for the Goodix driver / devices. At least, I guess, it will attract others to this platform... anyway, I was wondering and also confused, shouldn't touch screen work with the hideep driver using this config already?
Thanks for the new feel.
This is great, glad to see a developer picking up this tablet. It's a fine machine with an unfortunately small user base and has never really seen any development apart from ionioni s efforts and he didn't even own one, lol.
Edit: *Thank for the new twrp * auto correct!
I love this device! For me it's the perfect device for vacation just because of the projector!
I am so happy that you guys are working on it again. the ram and display tweak works like a charme for me. Had to reset my background screen though
thx for all your help. As soon as you guys have light rom, i'll install it on my 2GB device.
hello how to flash your twrp please ?
can someone upload adb drivers for the yt3-x90f please ? because i try to flash in dnx fastboot mode but commands don't work, even "fastboot devices" don't show me the yoga tab 3 pro

S999 Smart Watch MTK-6761: Stock Firmware, Unlock Booloader, Root, GSI Roms...

Hello guys, i open this thread as an open discussion about the S999 Smart Watch device which is working great !!
S999 (MTK-6761) maybe branded as:
- Lokmat APPLP Max
- JingTider S999
- BEESCLOVER S999
-...
I was able to get latest SP fLash Tools Firmware from Lokmat Support (V9-regular S999 for all devices) that can also fix imei/device ID...
Here is the link:
4G_H19_S999_EN_V0.9_P_user_20220611
I was able to one-click unlock bootloader using mtk-client (only works for me under Linux, but Windows Version available):
MTK-Client
Also, i played with some GSI ROMS flashed with SP Flash Tools, a lot of them works! But also a lot of them get both of the internal microphone/bluetooth headset activated so this results to an horrible "echo" of my voice during calls. Please someone can fix this?! or give a workaround?
The only rom i found that 100% works (no echo in bluetooth mode, but need to use Firefox for browser video playing) is Corvus OS A12 Official (i'm not an android dev so maybe you guys can found what makes bluetooth headset working with no echo in this rom and not in the others). I don't want to use A12 Rom i would prefer A10 or A11 but with bluetooth working!!!:
GSI ROMS List
Also i tried to port recovery to TWRP with no success, again, maybe you guys can port the recovery to custom one for this device?!
Here is the stock recovery extracted from stock rom above:
S999 Stock Recovery
The Corvus OS Rom is working great on this device, altought you need to pull off the sim card ("OK" button for sim code cannot be reached) on first boot to change DPI size (around 400).
Also after some charge/discharge cycles battery drain seems to be ok (maybe better than stock), but i'm also looking for a good "overlay" file/script to get this device working as best as possible, can someone do that?! (if you need something from stock rom .zip or SP Flash Read Back partitions/files i can provide it...
Hi, i ve also been playing with the same device. Currently running android 10 via crdrom rom. Works pretty okay although i havent tried out sim card functionality.
However i do have an issue, which im thinking could be hardware or MTK decided to do it, so i wanted to ask you of that also happens to you. So basically on all the roms i have tried out including the stock one, auto rotation doesnt work. Although i see accelerometer values using a sensor test app, but there is a orientation sensor from mtk which is always showing 0 and my autorotation just doesn’t work.
Did you experience the same? Also did you manage to find a trick to use heart rate sensor running custom rom?
Little tip: if you want to have the stock watch faces, you can extract these from the stock rom or in the worst case i can send them to you and then install them on your custom rom. They are essentially just live walpapers.
My setup:
-Crdrom android 10
-Using autogyro to manually change rotation to horizontal
-Microsoft launcher for app drawer, looks great in horizontal mode also
-Installed stock watch faces and set lock mode to none so i get the same functionality as on stock
laarSn said:
Hello guys, i open this thread as an open discussion about the S999 Smart Watch device which is working great !!
S999 (MTK-6761) maybe branded as:
- Lokmat APPLP Max
- JingTider S999
- BEESCLOVER S999
-...
I was able to get latest SP fLash Tools Firmware from Lokmat Support (V9-regular S999 for all devices) that can also fix imei/device ID...
Here is the link:
4G_H19_S999_EN_V0.9_P_user_20220611
I was able to one-click unlock bootloader using mtk-client (only works for me under Linux, but Windows Version available):
MTK-Client
Also, i played with some GSI ROMS flashed with SP Flash Tools, a lot of them works! But also a lot of them get both of the internal microphone/bluetooth headset activated so this results to an horrible "echo" of my voice during calls. Please someone can fix this?! or give a workaround?
The only rom i found that 100% works (no echo in bluetooth mode, but need to use Firefox for browser video playing) is Corvus OS A12 Official (i'm not an android dev so maybe you guys can found what makes bluetooth headset working with no echo in this rom and not in the others). I don't want to use A12 Rom i would prefer A10 or A11 but with bluetooth working!!!:
GSI ROMS List
Also i tried to port recovery to TWRP with no success, again, maybe you guys can port the recovery to custom one for this device?!
Here is the stock recovery extracted from stock rom above:
S999 Stock Recovery
The Corvus OS Rom is working great on this device, altought you need to pull off the sim card ("OK" button for sim code cannot be reached) on first boot to change DPI size (around 400).
Also after some charge/discharge cycles battery drain seems to be ok (maybe better than stock), but i'm also looking for a good "overlay" file/script to get this device working as best as possible, can someone do that?! (if you need something from stock rom .zip or SP Flash Read Back partitions/files i can provide it...
Click to expand...
Click to collapse
Hello, are there instructions on how to do this? I just got this watch and would like to see what it can really do. Thanks!
EDIT: Just a quick update...I've installed the MTK-Client for Windows. I now only need to understand how to use it to load an image to the smart watch.
Thanks much!
TheMixNation said:
Hello, are there instructions on how to do this? I just got this watch and would like to see what it can really do. Thanks!
EDIT: Just a quick update...I've installed the MTK-Client for Windows. I now only need to understand how to use it to load an image to the smart watch.
Thanks much!
Click to expand...
Click to collapse
Another update...I have the USB driver, Python, SP Flash Tool and MTK Client all operational now. I just cannot figure out how to get the watch into BROM mode to be able to connect. Android Development Studio actually does recognize when the device is plugged in but none of the apps seem to be able to read the device. Any suggestions?
You can Power Off the Device and start the Application (mtk client or whatever..) and let the Application wait for the Device.
Your Watch must be powered off AND DISCONNECTED FROM PC!!!!
While your Application is waiting for the Device please connect the POWERED OFF Watch to the PC.
This is the same procedure as you are flashing with SP-Flashtool, i asume so.
A Step for Step guide would be very nice and helpfull for "HOW TO UNLOCK THE BOOTLOADER" with MTK-Client.
I do not have one!
Actrapit said:
You can Power Off the Device and start the Application (mtk client or whatever..) and let the Application wait for the Device.
Your Watch must be powered off AND DISCONNECTED FROM PC!!!!
While your Application is waiting for the Device please connect the POWERED OFF Watch to the PC.
This is the same procedure as you are flashing with SP-Flashtool, i asume so.
A Step for Step guide would be very nice and helpfull for "HOW TO UNLOCK THE BOOTLOADER" with MTK-Client.
I do not have one!
Click to expand...
Click to collapse
Thanks much!
I did get it to connect using the method you described and SP-Flashtool. Too uncertain of what to do next to make any changes. It still doesn't connect to MKT-Client.
Hmm,
the owner of this Thred might help!
He did it successfully.
I did it with a different Method long time ago....
It´s CM2MT2 and the Dongle for it.
Yes, i payed for, but i love it because it is just working perfect and very simple too.
A simple description in the attachment, but i don´t know if it will help you!?
On what maschine you are working, Windows or Linux?
If Win you like to check the Drivers for the Watch in the Devicemanager of Windows there don´t has to be anywhere a yellow triangle.
If so a Driver is not correct installed. Until the yellow trinagle persists you have to troubleshoot and solve this first!
Actrapit said:
Hmm,
the owner of this Thred might help!
He did it successfully.
I did it with a different Method long time ago....
It´s CM2MT2 and the Dongle for it.
Yes, i payed for, but i love it because it is just working perfect and very simple too.
A simple description in the attachment, but i don´t know if it will help you!?
On what maschine you are working, Windows or Linux?
If Win you like to check the Drivers for the Watch in the Devicemanager of Windows there don´t has to be anywhere a yellow triangle.
If so a Driver is not correct installed. Until the yellow trinagle persists you have to troubleshoot and solve this first!
Click to expand...
Click to collapse
I'm on Windows...Yeah, already ran into a bit of troubleshooting with getting the Python modules properly installed before I was able to get the to MTK GUI. I am fairly technical and just haven't done this particular thing before; so, am starting from the beginning. My world is mostly PHP/CSS/SQL with some minor dabbling in other aspects. I've loaded images into ROMs before but on routers and such.
Any help is certainly appreciated...I appreciate the information!
kudicini said:
Hi, i ve also been playing with the same device. Currently running android 10 via crdrom rom. Works pretty okay although i havent tried out sim card functionality.
However i do have an issue, which im thinking could be hardware or MTK decided to do it, so i wanted to ask you of that also happens to you. So basically on all the roms i have tried out including the stock one, auto rotation doesnt work. Although i see accelerometer values using a sensor test app, but there is a orientation sensor from mtk which is always showing 0 and my autorotation just doesn’t work.
Did you experience the same? Also did you manage to find a trick to use heart rate sensor running custom rom?
Little tip: if you want to have the stock watch faces, you can extract these from the stock rom or in the worst case i can send them to you and then install them on your custom rom. They are essentially just live walpapers.
My setup:
-Crdrom android 10
-Using autogyro to manually change rotation to horizontal
-Microsoft launcher for app drawer, looks great in horizontal mode also
-Installed stock watch faces and set lock mode to none so i get the same functionality as on stock
Click to expand...
Click to collapse
Hi, yes same!
Simply use: Rotation apk
TheMixNation said:
Hello, are there instructions on how to do this? I just got this watch and would like to see what it can really do. Thanks!
EDIT: Just a quick update...I've installed the MTK-Client for Windows. I now only need to understand how to use it to load an image to the smart watch.
Thanks much!
Click to expand...
Click to collapse
Maybe you should learn more... there is no "image" to "load" via MTK-client...This tool is only to unlock bootloader. Also please try harder to learn by yourself = every commands and instructions are on the github page of mtk-client.
To flash new rom:
- Unlock Bootloader
- Enable USB Debugging in developper options
- Download and install adb/fastboot drivers and program for windows
- In windows terminal type:
adb reboot bootloader
- Then your device will reboot in fastboot mode
- Type:
fastboot erase system
fastboot flash system nameofyourrom.img
fastboot -w
fastboot reboot
TheMixNation said:
Thanks much!
I did get it to connect using the method you described and SP-Flashtool. Too uncertain of what to do next to make any changes. It still doesn't connect to MKT-Client.
Click to expand...
Click to collapse
If you can try with a live usb linux (ubuntu or something else)
Device powered off i only type:
python mtk e metadata,userdata,md_udc (errors allowed)
and
python mtk da seccfg unlock
then connected my device...= Instant unlocking
I also experiment trouble to get this device up under windows, go Linux
Actrapit said:
You can Power Off the Device and start the Application (mtk client or whatever..) and let the Application wait for the Device.
Your Watch must be powered off AND DISCONNECTED FROM PC!!!!
While your Application is waiting for the Device please connect the POWERED OFF Watch to the PC.
This is the same procedure as you are flashing with SP-Flashtool, i asume so.
A Step for Step guide would be very nice and helpfull for "HOW TO UNLOCK THE BOOTLOADER" with MTK-Client.
I do not have one!
Click to expand...
Click to collapse
Working on it dude! since hovatek community for this device including Russian guys seems dead ill post it here!
But if you read carrefully the Github page to the end, there is all the step by step guide to get this done!
laarSn said:
Working on it dude! since hovatek community for this device including Russian guys seems dead ill post it here!
But if you read carrefully the Github page to the end, there is all the step by step guide to get this done!
Click to expand...
Click to collapse
Hmm it was @TheMixNation who asked something, not me!
Did you realized this?
laarSn said:
Maybe you should learn more... there is no "image" to "load" via MTK-client...This tool is only to unlock bootloader. Also please try harder to learn by yourself = every commands and instructions are on the github page of mtk-client.
To flash new rom:
- Unlock Bootloader
- Enable USB Debugging in developper options
- Download and install adb/fastboot drivers and program for windows
- In windows terminal type:
adb reboot bootloader
- Then your device will reboot in fastboot mode
- Type:
fastboot erase system
fastboot flash system nameofyourrom.img
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
laarSn said:
Maybe you should learn more... there is no "image" to "load" via MTK-client...This tool is only to unlock bootloader. Also please try harder to learn by yourself = every commands and instructions are on the github page of mtk-client.
To flash new rom:
- Unlock Bootloader
- Enable USB Debugging in developper options
- Download and install adb/fastboot drivers and program for windows
- In windows terminal type:
adb reboot bootloader
- Then your device will reboot in fastboot mode
- Type:
fastboot erase system
fastboot flash system nameofyourrom.img
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
Thank you for so kindly steering me in the right direction.
I clearly need to learn more - hence the questions and statements indicating that I had not done this particular thing before.
That said, I have spent many hours thus far learning and managing to get the Python install to work on Windows without throwing module not found errors.
I had not indicated that I thought the image was to be installed via one app or the other, just that I had the programs set up and was looking for the correct order to do things in.
While they may not need to be "loaded" via the MTK client, the ROMs are still system "images" that get up"loaded"/written into the device's memory.
{
"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"
}
laarSn said:
Hello guys, i open this thread as an open discussion about the S999 Smart Watch device which is working great !!
S999 (MTK-6761) maybe branded as:
- Lokmat APPLP Max
- JingTider S999
- BEESCLOVER S999
-...
I was able to get latest SP fLash Tools Firmware from Lokmat Support (V9-regular S999 for all devices) that can also fix imei/device ID...
Here is the link:
4G_H19_S999_EN_V0.9_P_user_20220611
I was able to one-click unlock bootloader using mtk-client (only works for me under Linux, but Windows Version available):
MTK-Client
Also, i played with some GSI ROMS flashed with SP Flash Tools, a lot of them works! But also a lot of them get both of the internal microphone/bluetooth headset activated so this results to an horrible "echo" of my voice during calls. Please someone can fix this?! or give a workaround?
The only rom i found that 100% works (no echo in bluetooth mode, but need to use Firefox for browser video playing) is Corvus OS A12 Official (i'm not an android dev so maybe you guys can found what makes bluetooth headset working with no echo in this rom and not in the others). I don't want to use A12 Rom i would prefer A10 or A11 but with bluetooth working!!!:
GSI ROMS List
Also i tried to port recovery to TWRP with no success, again, maybe you guys can port the recovery to custom one for this device?!
Here is the stock recovery extracted from stock rom above:
S999 Stock Recovery
The Corvus OS Rom is working great on this device, altought you need to pull off the sim card ("OK" button for sim code cannot be reached) on first boot to change DPI size (around 400).
Also after some charge/discharge cycles battery drain seems to be ok (maybe better than stock), but i'm also looking for a good "overlay" file/script to get this device working as best as possible, can someone do that?! (if you need something from stock rom .zip or SP Flash Read Back partitions/files i can provide it...
Click to expand...
Click to collapse
Thank you for opening this thread. Can you please share some screenshots of the home screen of the smartwatch S999 with Corvus OS A12 Official (which you mentioned) ?
@laarSn @kudicini l know you guys are busy, but can you please post a screenshot of the S999 watch's homescreen or maybe sum more fotos how it looks ? Thanks in advance
Freemaurer said:
@laarSn @kudicini l know you guys are busy, but can you please post a screenshot of the S999 watch's homescreen or maybe sum more fotos how it looks ? Thanks in advance
Click to expand...
Click to collapse
View attachment 5828415View attachment 5828417Hi These are some of the screenshots,I actually didnt do any modifications, didnt really have time to play that much with it, initially i ve bought it to use while on work, for teams, but still havent used it, it was actually turned off for the last month or so haha
Anyway, I m using Microsoft Launcher, I find it really great since I can use it in horizontal mode, which is the only natural way of using this device since the width is too small and you re anyway gonna be using it while on wrist (for most stuff). I ve set no lock screen and instead use button to lock/unlock which makes it more similar to smartwatch. The big clock you can see is actually one of the clocks from the original image, since I ve figured out the original clock images on the original image are just live wallpapers, so you can actually use it on your custom rom also, however the multi functional clocks work partially, depending on what you click and also any clock image using heart rate monitor will fail.
If you want heart rate monitor I ve also found one app that actually works on this device, but personally I dont really use it. For the above mentioned problem of horizontal rotation, i am using autogyro app which works pretty well.
laarSn said:
I was able to get latest SP fLash Tools Firmware from Lokmat Support (V9-regular S999 for all devices) that can also fix imei/device ID...
Here is the link:
4G_H19_S999_EN_V0.9_P_user_20220611
Click to expand...
Click to collapse
I'm dying to try this out, but I am unable to download this file. Do I need to request access somehow?
Thanks for this awesome work! I thought my S999 was destined for the junk pile until now.
Try this:
S999 Bootloader unlock - Page 9
(05-12-2022, 02:51 PM)maxpayne Wrote: (03-12-2022, 08:58 AM)laarSnn Wrote: Hello guys, i have some good news for you i was able to get latest SP fLash Tools Firmware from Lokmat Support (V9-regular S9
www.hovatek.com
Newfred said:
I'm dying to try this out, but I am unable to download this file. Do I need to request access somehow?
Thanks for this awesome work! I thought my S999 was destined for the junk pile until now.
Click to expand...
Click to collapse
Try again it should works: https://drive.google.com/file/d/1K6J7WBVaHP96lk41ZDn2FVAC7WarRABt/view?usp=sharing

ONE UI 4.1 ANDROID 12 FOR SAMSUNG GALAXY A10

Hi, i created a version of one ui 4.1 for samsung galaxy a10,
INSTRUCTIONS:
1. BOOT UP YOUR PHONE TO RECOVERY
2. FLASH System_Repartitioner_4000MB, be careful, do it with an sd card otherwise all the files will disappear, it will go back to recovery on its own as soon as it's done.
3. FLASH Vendor_Repartitioner_680MB, AS IN THE FIRST IT WILL RETURN TO RECOVERY BY ITSELF.
4. AS THE LAST FILE YOU MUST FLASH OneUI_4.1_Galaxy_A10_Arm64_Apks WHICH IS THE ROM. JUST IT'S FINISHED DO WIPE CACHE AND REBOOT NOW, IT WILL TAKE 5-10 MINUTES TO REBOOT, GOOD LUCK!
camera and face recognition dosen't work very well...
FILES ARE THERE
Download one ui (I put the link for one ui because it's too heavy, the other files are below):
OneUI_4.1_Galaxy_A10_Arm64_Apks
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Hi can i ask you for a favor, i am using galaxy m20, i am finding for 2 months for a zip to resize my system into 4GB and vendor into 500MB (mine system is 3346MB and vendor is 404MB right now) i only find 1 way that's called "parted" but i am scared of it cause i am not a developer like you and others, is there any possibility to use your system and vendor repartitionar and is it gonna work on my device somehow? please help me, if its easy for you then please made one for galaxy m20 if you can,Thanks in advanced
Tahir Jamil said:
Hi can i ask you for a favor, i am using galaxy m20, i am finding for 2 months for a zip to resize my system into 4GB and vendor into 500MB (mine system is 3346MB and vendor is 404MB right now) i only find 1 way that's called "parted" but i am scared of it cause i am not a developer like you and others, is there any possibility to use your system and vendor repartitionar and is it gonna work on my device somehow? please help me, if its easy for you then please made one for galaxy m20 if you can,Thanks in advanced
Click to expand...
Click to collapse
Hi, you can try but I can't assure you anything. Try and let me know, bye
marcogalaaaaaaaaaaa said:
Hi, you can try but I can't assure you anything. Try and let me know, bye
Click to expand...
Click to collapse
It doesn't work saying wrong device, please fix it
Thanks for the ROM it works beautifully
One small issue though
The sound on some apps is broken ( Spotify and Chrome )
I hope you could fix it as soon as possible
Thanks again
Works like a charm!!!!!
One issue though.....the location seems to not work.....maybe there's a fix?!?!?!

Categories

Resources