Database Users

WileyFox Swift 2 Plus observations

The WileyFox Swift 2 Plus is not a bad looking phone, the case feels good in my hand. It is almost small and light enough to fit into my shirt pocket should I need to.
It runs CyanogenOS which is an improvement on the standard bloated Google Android and is to be applauded.
3Gb for the System and 32Gb Storage, 2.4GHz WiFi, Dual Sim, External SDCard, NFC, Android Pay, Android Beam , FingerPrint recognition, 4G, 16Mp/8Mp cameras, 5" screen - great stuff especially for the price. It is however, designed as a city phone not an everywhere phone that much is apparent.
There are a number of downsides :crying:
The second SIM slot doubles up as the Ext SDRam slot - one or the other not both - what an epic fail !!!
Can't actually use the SDcard for backups or data or media - bit of a waste of space really. You need to root the phone and install SD Fix or similar.
It only works with 2.4GHz WiFi which is a disgrace given my ancient Xperia T covers 5GHz as well.
There is no real GPS only A-GPS which needs an internet connection to work - no good if you have a poor or zero mobile signal. This is really such a waste of time even implementing this instead of the real thing.
Only the Google versions of photo album and media player (which don't find local files), mail(gmail) , calendar, calculator etc are installed. If you like having to use a data connection and Google knowing everything you do then fine. I don't which means I have to install apps covering those functions. Shame I can't just install those I used on my Sony Xperia. If you already have favourites its not a big deal. If you don't then you have to start loading and trying out Apps to find the one you like.
Having set up the phone to your liking it would be nice to be able to save it that way. Which you can't without Rooting the phone.
To make the best of it you need to Root the phone - this is to be able to install effective anti-virus, firewall and anti-theft software. To be able to install Titanium Backup in order to actually backup the current state of the phone including apps and data to the SDcard as well as the cloud.
And remove the Apps that you don't use or don't care to have installed.
Would you use a PC without that type of software ? I suspect not - So why make a phone that you can't install the protective software on to ?
It is very simple to unlock the Bootloader and then Root the phone using SuperSU just using the phones developer options. No need to install ADB on the PC or install TWRP on the phone if you don't want to use a custom ROM. Unfortunately it invalidates the manufacturers warranties. :crying::crying::crying:
This could have so easily been a perfect phone, unfortunately a couple of poor cost cutting decisions have more or less ruined it.
Me ? I have already given away this phone after just 3 days, much to my disappointment.

Isn't A-GPS built on top of GPS and purely there for lock startup speed?

You're right, this "review" is full of nonsenses
1. The SD card slot is shared with second SIM slot, it is right. But SD card can be use to backup data or to extend the internal storage space (marsmallow feature)! You don't really need root and SD fix...
2. A-GPS is used to improve startup speed, which is really impressive (snapdragon!)
3. Photo album and media player, mail, ...? You could install whatever you want, there is a google play store
4. Root. No phones come with builtin root, but if you really need it, it is possible and easy to install.
I believe that there will be a community CaynogenMod ROM in the future - just like for the original Wileyfox Swift 1...
I'm very satisfied with this phone. Yeah there are some drawbacks - it has only 720p display (instead of full HD), it can be a bit smaller (just like the previous Swift) and the CyanogenOS has some bugs (for example the theme provider is time to time crashing...), but I hope it will be fixed in the future...

Even better
You can delete easily what you want with titanium backup. And whitout lag (not like a Miui rom).
The bootloader is probably one of the most easier than I've done in my life (not like a xiaomi one).
The SD cart can be use to save your backup, even my 128gb is working.
The screen it's just the perfect size & definition is the perfect combo for not to drain the battery.
Waiting the LineagOS for the marmite :fingers-crossed:

Just managed to pick up one of these practically brand new for only £100 for a friend.
Really nice build quality and look of the phone and packaging. CM13.1 looks nice and any bloat can be quickly disabled or even uninstalled. 3GB Ram is great as sitting here now, this phone has 2GB just sat there free. (Unlike the Nexus 9 for example!) If I was nit picking, the screen could be better and the fingerprint reader isn't as fast as my One Plus 3, (Not to be expected given the price.)
If I had this in front of me, a P9 Lite, and the standard Moto G4 for the same cash, I'd pick the P9 Lite due to its better screen. I'd pick this second due to the extra RAM and fingerprint reader, and the Moto last. If I had to pick a phone to last 2 years, I'd pick this over the P9 as CM13 is better than the strange Huawei stuff.
If Wileyfox could drop the price to £160, I think they'd be onto a real winner.

bahjesaispas said:
You can delete easily what you want with titanium backup. And whitout lag (not like a Miui rom).
The bootloader is probably one of the most easier than I've done in my life (not like a xiaomi one).
The SD cart can be use to save your backup, even my 128gb is working.
The screen it's just the perfect size & definition is the perfect combo for not to drain the battery.
Waiting the LineagOS for the marmite :fingers-crossed:
Click to expand...
Click to collapse
Just bought today can you give run down how to unlock bootloader:good:

stevegtrlmk said:
Just bought today can you give run down how to unlock bootloader:good:
Click to expand...
Click to collapse
On the Nougat ROM:
Enabled developer options (tap build number several times)
Go to developer options
Enable the "OEM unlocking" option
Not so sure about the rest:
reboot into fastboot (adb reboot bootloader)
fastboot oem unlock
It seems like unlocking will wipe your phone... (At the fastboot step... I only recently got mine, haven't tried this yet)

Demostrike said:
Isn't A-GPS built on top of GPS and purely there for lock startup speed?
Click to expand...
Click to collapse
Nope A-GPS is a cheap replacement for real GPS.
http://www.diffen.com/difference/A-GPS_vs_GPS
If you are running a WileyFox Swift with Cyanogen you will find that any of the GPS test apps will say there is no GPS.
A-GPS does NOT work without an internet connection.
Some phone use A-GPS to speed up their lock within built up areas.
Having said that the Swift running the Android v7.1.1 Nougat package the GPS has been enabled and the GPS Test tools now work.
Go figure why it wasn't enabled in the first place.

rivierakid said:
You're right, this "review" is full of nonsenses
1. The SD card slot is shared with second SIM slot, it is right. But SD card can be use to backup data or to extend the internal storage space (marsmallow feature)! You don't really need root and SD fix...
Depends what you want to use the SD card for, maybe something like saving your Titatium backups which can be removed from the phone if it is dead. And if you want dual SIM you can't use the SD card. And you need to root the phone to use the Marchmallow SD card unlock.
If you let the phone use the SD card as extended memory it is encrypted and you can't read it without that phone - thanks Google.
2. A-GPS is used to improve startup speed, which is really impressive (snapdragon!)
Nope SOME phones use A-GPS to speed up lock within built up areas but it is really a cheap replacement for real GPS.
http://www.diffen.com/difference/A-GPS_vs_GPS
check your facts.
3. Photo album and media player, mail, ...? You could install whatever you want, there is a google play store
And if you don't like the pre-installed versions you need something like Titanium to remove them.
4. Root. No phones come with builtin root, but if you really need it, it is possible and easy to install.
And the UPDATES stop the moment you unlock the BootLoader let alone Root the phone.
Anti-Theft, Anti-Virus, Anti-Malware, Titanium Backup, Nandroid Backup all need ROOT.
The Cyanogen Anti-Theft stopped working when the website closed.
The point I was making is why should you have to 'break' your phone to protect your investment?"
I believe that there will be a community CaynogenMod ROM in the future - just like for the original Wileyfox Swift 1...
LOL - no Cyanogen is no more , although there is a movement to Lineage which may grow into a Cyanogen replacement
I'm very satisfied with this phone. Yeah there are some drawbacks - it has only 720p display (instead of full HD), it can be a bit smaller (just like the previous Swift) and the CyanogenOS has some bugs (for example the theme provider is time to time crashing...), but I hope it will be fixed in the future...
Click to expand...
Click to collapse
Yes I also like the phone and its even better running v7.1.1 Nougat - even though the Zen app is not needed.

SMessy said:
Yes I also like the phone and its even better running v7.1.1 Nougat - even though the Zen app is not needed.
Click to expand...
Click to collapse
Get your facts right, just about all phones use aGPS. And all phones lose updates when rooted. You make generic points and a tribute them to a particular device. Sad.
Sent from my Lenovo P2a42 using Tapatalk

MoHaG said:
On the Nougat ROM:
Enabled developer options (tap build number several times)
Go to developer options
Enable the "OEM unlocking" option
Not so sure about the rest:
reboot into fastboot (adb reboot bootloader)
fastboot oem unlock
It seems like unlocking will wipe your phone... (At the fastboot step... I only recently got mine, haven't tried this yet)
Click to expand...
Click to collapse
Reboot into fast boot is that within the phone or when your connected to computer :good:

stevegtrlmk said:
Reboot into fast boot is that within the phone or when your connected to computer :good:
Click to expand...
Click to collapse
If you use the adb command, on the computer...
(I can reboot into bootloader from the advanced reboot menu on the phone as well)

MoHaG said:
If you use the adb command, on the computer...
(I can reboot into bootloader from the advanced reboot menu on the phone as well)
Click to expand...
Click to collapse
Hey thanks unlocked boot but can't get twrp to flash. Download the newest marmite version put in adb folder tried to flash but nothing

stevegtrlmk said:
Hey thanks unlocked boot but can't get twrp to flash. Download the newest marmite version put in adb folder tried to flash but nothing
Click to expand...
Click to collapse
Hi,
I choose to unlock my swift 2 bootloader and flash TWRP using fastboot commands. If you have unlocked bootloader then using minimal ADB and fastboot command use: fastboot flash recovery recovery.img replacing recovery.img with the one you downloaded. So mine was fastboot flash recovery twrp-3.1.1-0-marmite.img as I am on the current official build.

image45 said:
Hi,
I choose to unlock my swift 2 bootloader and flash TWRP using fastboot commands. If you have unlocked bootloader then using minimal ADB and fastboot command use: fastboot flash recovery recovery.img replacing recovery.img with the one you downloaded. So mine was fastboot flash recovery twrp-3.1.1-0-marmite.img as I am on the current official build.
Click to expand...
Click to collapse
Thanks for that I have not tried yet but will do soon much appreciated:good:

image45 said:
Hi,
I choose to unlock my swift 2 bootloader and flash TWRP using fastboot commands. If you have unlocked bootloader then using minimal ADB and fastboot command use: fastboot flash recovery recovery.img replacing recovery.img with the one you downloaded. So mine was fastboot flash recovery twrp-3.1.1-0-marmite.img as I am on the current official build.
Click to expand...
Click to collapse
Do you have to have the file on root of device or in the adb folder as I am just getting error cannot flash twrp

stevegtrlmk said:
Do you have to have the file on root of device or in the adb folder as I am just getting error cannot flash twrp
Click to expand...
Click to collapse
Minimal ADB and Fastboot is a PC based program. I have provided link below for you.
https://freeandroidroot.com/download-minimal-adb-and-fastboot-all-versions/
Once installed you place the file to be flashed in the program folder with the other installed core program files in directory.
If you run the program you get the command prompt window as displayed in post. This is where you run the Fastboot common I advised you about in earlier post.
So in the command window type and execute:
fastboot flash recovery twrp-3.1.1-0-marmite.img
You might wish to read this thread too on XDA
https://forum.xda-developers.com/showthread.php?t=2317790
Hope this helps Robert.

Remote Access

anyone know of any apps or anyway to remote access shield from. another android device, i normally use teamviewer for all my devices but on shield i can only view not controll it

I got it working with Quick Support app of teamviewer (old version) and AOSP addon but the ID changes everytime you close and open the app which is expected for the QS app.
After that i went and installed the TV Host app but im stuck where it asks for a password, haven't played with it again but i will do so soon.
Anyway if you're ok with Quick Support for now then here are the apps i use:
Teamviewer Quick Support v10.0.3724:
https://drive.google.com/file/d/0B3XeIVyUffMKb2c0WUZIR0o4TFk/view?usp=drivesdk
Teamviewer AOSP addon:
https://drive.google.com/file/d/0B3XeIVyUffMKazZSZzNnTnZOS0U/view?usp=drivesdk
PS: Let me know if it works for you on Android TV as i have installed Full Android Nougat custom ROM and it works fine there.
Enviado desde mi Moto X via Tapatalk!

only allows me to view not control, hodid you install full nougat and is there advantages to that

paulsavo said:
only allows me to view not control, hodid you install full nougat and is there advantages to that
Click to expand...
Click to collapse
Oh you'll see the difference, advantages off course, everything android can provide a.k.a no limitations.
Everything Nvidia related works. Its a fusion between Android TV and full Android and it is also why there are 2 settings apps.
Anyway you can test, is safe to flash as you just flash system.img and vendor.img just read instructions and watch my video (working on english version) to see the whole process. I also provide all the required tools in the description of the video.
You can go back to stock easily by flashing the OTA via TWRP recovery, I've already done it.
http://www.videomap.it/forum/viewtopic.php?f=25&t=1646
https://youtu.be/_mllRt93Ook
Enviado desde mi Moto X via Tapatalk!

thats brilliant, can you answer does it change any performance of shield and also does plex still work as a server

paulsavo said:
thats brilliant, can you answer does it change any performance of shield and also does plex still work as a server
Click to expand...
Click to collapse
Performance is exactly the same. Yes Plex Server works just like in stock, same thing for other nvidia apps and even android tv apps work with the exception of leanback launcher and probably few others.
I've tested spotify, youtube, updated chromecast receiver and netflix apps made for android tv (downloaded from apkmirror.com) without issues.
Enviado desde mi Moto X via Tapatalk!

nice 1 i will maybe give it a go

looks great mate if you could please provide an English video i will definitely follow it... you say leanback dosent work but can you install other launchers

When the dev release the modified boot.img for dual boot you could then also test the custom firmware in an external memory.
Yes you can install any other launcher available in the play store.
Im working on an english version of the same video. I'll also post it here when done.
Enviado desde mi Moto X via Tapatalk!

also i see in video you are using a mouse but will the stock remote work also

paulsavo said:
also i see in video you are using a mouse but will the stock remote work also
Click to expand...
Click to collapse
Yes, i use gamepad, a logitech k400 and droidmote server/client for touchscreen games and other apps that need touch. With droidmote you can have a mouse whenever you need it with a simple button click in the gamepad and it's not limited to certain apps like in Android TV. Im kind of used to use the logitech k400 more but remote and gamepad no matter if they are 2015 or 2017 model work fine, including mic and headphone jack
Enviado desde mi Moto X via Tapatalk!

thanks look forward to english video.. do i need root as well and if so do i root 1st?

paulsavo said:
thanks look forward to english video.. do i need root as well and if so do i root 1st?
Click to expand...
Click to collapse
NO need to root in stock to flash custom firmware, you root after having flashed custom firmware.
If you have new 2017 model root is mandatory, as it removes all warnings and verifications Nvidia has placed and also let the box boot normally, otherwise your shield may be stuck in a black screen with a warning and not boot to full android nougat.
BTW i got teamviewer host working and i could remote control my shield tv from my android smartphone just fine.
Enviado desde mi Moto X via Tapatalk!

yes i have 2017 16gb, is it possible you cud do me a step by step guide as would like to do this asap
greatly appreciate your help

paulsavo said:
yes i have 2017 16gb, is it possible you cud do me a step by step guide as would like to do this asap
greatly appreciate your help
Click to expand...
Click to collapse
In the description of the video there are 3 links, download the tools, MegaDownloader and the firmware (with megadownloader)
1. Uncompress the tools package (adb, fastboot,etc) in C:\ so it looks like C:\ADB once done.
Note: copy supersu zip package to an external usb flash drive just in case, keep reading
2. Make sure you have a good quality usb 3.0 type A male to male cable, a 1080p TV or Monitor (because 4k UHD TVs can cot display image while in TWRP and maybe also fastboot mode).
In case of tower or all-in-one pc use the usb ports of the back and make sure your pc if Windows is in good condition, stable without virus that can make your pc to not respond.
3. Backup everything you can from internal storage including adopted storage if any. If you dont care about it then ignore this step.
4. It is recomended that you do a factory data reset from Storage & reset setting and re-do the initial setup.
5. Enable Developer mode and then usb debugging, disable CEC in Display & Sound > Power Control Setting and power off your ShieldTV.
Plug the USB cable one side to pc and the other to shieldtv.
6. Boot into fastboot or bootloader mode using the controller method or HW method:
http://nv-tegra.nvidia.com/gitweb/?...;f=README_NEW_SHIELD;hb=rel-24-uda-r1-partner
OR https://youtu.be/2AzHF-uNiY8
7. Install Shield Fastboot drivers in Windows from device manager
8. Run the commands:
fastboot oem unlock
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot -w
(if 500gb pro model takes 2 hours to wipe, to avoid this you can wipe data and cache from TWRP)
fastboot boot recovery.img
(this can be tricky, you may need to disconnect usb cable right after you hit enter in order to boot properly to twrp)
9. Once booted up in TWRP mode sideload supersu or install from external usb drive (you will need a usb hub because you'll use 3 usb ports for usb type A cable, mouse and usb flash drive)
10. Reboot system. Done!
Enviado desde mi Moto X via Tapatalk!

ok thats great, in relation to rooting then as im on 2017 model do i just root after all this or do i root prior to this procedure?

paulsavo said:
ok thats great, in relation to rooting then as im on 2017 model do i just root after all this or do i root prior to this procedure?
Click to expand...
Click to collapse
After.
Root is systemless if you wipe data or do a factory reset, root for apps is gone but again remeber i mentioned supersu also modifies boot.
Enviado desde mi Moto X via Tapatalk!

thanks for everything can you just finally answer 2 questions
1. would this be best procedure to follow re root?
http://nvidiashieldzone.com/shield-...rial-root-shield-android-tv-2017-16gb-nougat/
2. more of an android question rather than shield but is there a way that you know of to write/save to external storage on android? i keep getting this error on all my devices " make sure selected folder is writeable and that the new folder name is valid"
thanks again for everything totally appreciated

paulsavo said:
thanks for everything can you just finally answer 2 questions
1. would this be best procedure to follow re root?
http://nvidiashieldzone.com/shield-...rial-root-shield-android-tv-2017-16gb-nougat/
2. more of an android question rather than shield but is there a way that you know of to write/save to external storage on android? i keep getting this error on all my devices " make sure selected folder is writeable and that the new folder name is valid"
thanks again for everything totally appreciated
Click to expand...
Click to collapse
1. Whatever works best for you. I gave punctual resumed instructions. If you're a noob then use those larger instructions.
Also the tools package i provide has shield drivers, adb, fastboot, twrp and supersu already. You can use the hacked twrp for darcy a.k.a 2017 model instead if you want.
I have the 2015 16GB model and the twrp in the package worked just fine and it is also meant to work on 2017 model.
2. Hmm well i have written to my external usb 3.0 flash drive and micro sd like normal. Just yesterday i downloaded some torrents to my flash drive using tTorrent app.
The only issue I've had is with apps that can't write to my mounted SMB NAS so for now i just use ES File Explorer v3.2 5.5 to copy stuff to it via LAN.
Enviado desde mi Moto X via Tapatalk!

ok so following your step by step guide above, what exactly is required after that just to root

Bosion BX-411 (Allwinner T3 QuadCore) Custom ROM [4.4.2] with Root

T3_P1 Custom Rom
FAC_Config: https://mega.nz/#!NkZxhA6Y!2dD0OHU1bxLSpWBZ5cixmGxSjIwXW6is7yUSeRY8FY4
MCU.bin: https://mega.nz/#!ZlhDxBRY!wH6LUPS0GHcNAv0EJs1nRhtjjfjcd9LPrlCfF2ntewI
T3_P1.img https://mega.nz/#!wkYxgRCD!Fo1jJ_auSpllPFjNcOy7_hky_B7CKHMG-qgzWEc0NwM
Root.zip https://mega.nz/#!V14QmLxa!FMw8MULUFS-kdHP_l3-pg6e_yCXf99JKyVcrtov9zBI
Changelog:
- Removed/Moved Bloatware to /system/BLOATWARE
-- ATV.apk (Analog TV => Who the **** watches TV in a car?)
-- AuxIn.apk (Analog Input => Input via Red-White-Cable? LOL)
-- BodaBluetooth.apk (BT-Streaming/Phone => Autostart, I hate it!)
-- BodaMusic.apk (Music Player => Autostart and doesn't play music from hidden SD Card!)
-- CanBusAirInfo.apk (WHAT?)
-- CanBusCarInfo.apk (WHAT?)
-- Chrome.apk (Webbrowser => I hate Chrome, Opera FTW)
-- Disc.apk (DVD Player? => I don't own a DVD Drive)
-- DTV.apk (Digital TV => Ha ha ha ha ...)
-- EasyConnected.apk (MirrorLink => Never worked!)
-- FileExplore.apk (FileManager => Worst FM ever!)
-- PreCamera.apk (Camera/ReverseCamera => Not connected... useless)
-- Radio.apk (Radio => I hate listening to unwanted songs!)
-- SWC.apk (SteeringWheelControl => Don't have a remote in my car to configure)
-- Torque_Pro.apk (OBD2 App => Piracy...)
-- VideoPlayer.apk (VideoPlayer => Who watch a video while driving?)
- Added Apps in /system/preinstall
-- BusyBoxV49.apk (Busybox installer/manager => Root App will love it!)
-- DabPlayer.apk (Digital Radio => Sounds cool?)
-- Easy_DPI_ChangerV3.1.9.apk (DPI Changer => Make your screen looks bigger/smaller)
-- GravityBoxKKV3.6.1.apk (GravityBox Xposed Modul => **** up your Head Unit like a real custom ROM!)
-- MX_PlayerV1.8.11.apk (Video Player => Better than the old one...)
-- MX_Player_Codec_ARMv7V1.8.12.apk (MX Player Codec)
-- MX_Player_Codec_ARMv7_NEONV1.8.12.apk (MX Player Codec)
-- Opera_MiniV21.0.2254.111920.apk (Webbrowser => Also removes Ads and useless Stuff)
-- RebootV2.0.5.apk (Reboot => To Recovery for Update, Shutdown, ...)
-- root.zip (Because I can... contains root for flashing)
-- SHOUTcastV1.apk (WebRadio => Best Radio app, used by Winamp!)
-- SuperBeamV4.1.3.apk (FileSharing => Share/Receive Files over Wifi! Because BT is slow...)
-- WazeV4.21.0.0.apk (Navigation => Better than iGO... but need Internet!)
-- XposedV2.6.1.apk (ROM ****ing App for everything!)
-- X_ploreV3.92.13.apk (FileManager => Better then FileExplore.apk with access to root!)
-- And the best part: You can uninstall some of these useless apps if you want =)
- Changed Boot Animation and Sound
- Recovery 'hacked', so you can use the touchscreen to control it
- You can install SuperSU (old Superuser.apk have to be deactived if SuperSU tries to uninstall it)
Bugs:
- MCU not deactived!
-- Every Android ROM wont be able to act/work freely due the MCU!
The problem is, if you look at the plan of the Allwinner T3 aka R40, you'll notice that many functions are connected to the MCU.
According to XDA-Developer, Android act here blind to things like Bluetooth or else, which means that if you need or want, you have to flash a hacked MCU.
But unfortunately, there aren't any for our MCU, it looks like BOSION have their own MCU.
So far, Bluetooth will only react to A2DP or devices with 'OBD' in their Name. There are some Modules for Xposed which CAN bypass or enhance some limitation,
but I don't know whether they really works with every MCU!
Also, the MCU does some usefull thing like dimming the light or giving you individual Volumne (Input Gain)
- Noise until you don't start any MCU-App (Radio, AuxIn, ...)
- Recovery still reboots after couple seconds or a minute, the boot.img obviously treis to prevent it (Boot.img swapped out once => Bootloop!)
- Sometimes the Buzzer activates itself?! (Probably due a Bug with Recovery/Boot.img? Happens randomly)
- ???
Installation Guide:
Video with bad quality and very stupid, oh my god and I never realized that...: https://www.youtube.com/watch?v=MEXaTXl2uIc
1. Burn T3_P1.img with PhoenixCard into a micro SD card(Windows 7 for best results, Windows 8+ cause random errors)
2. Copy root.zip into the micro SD card (smart would be to use another micro SD card or use the same micro sd card but please, format it first!)
3. Remove any micro SD cards from the head unit, also the hidden one behind the screen (just remove the 2 screws per side)
4. Insert the micro SD card into the from slot aka GPS-Slot and power on the head unit.
5. After flashing, remove the micro SD card and restart the head unit (Reset or power off/on)
6. Wait a bit, the system will reboot by itself to recovery.
7. If the head unit boot into recovery, quickly insert the micro SD card with 'root.zip' and install it from extsd/usbhost.
8. Due some restrictions in Boot.img, the system will try to boot the system, but then realizes that the recovery was flashing a zip and will stay in recovery!
9. Flash 'root.zip' again and if done, just reboot the system
10. Victory Sound, you have root!
FAQ? Yeah please but write me a personal message and I'll answer + add it here

I will flash my unit with your rom this weekend or before.
After reading your FAQ, watched the video and knowing that I'm reverting from Android 6, it's recommended to the install mcu.bin that you provided? HZBHDAndroidConfig.img is required to be installed?
Thank you!

Kazadorng said:
I will flash my unit with your rom this weekend or before.
After reading your FAQ, watched the video and knowing that I'm reverting from Android 6, it's recommended to the install mcu.bin that you provided? HZBHDAndroidConfig.img is required to be installed?
Thank you!
Click to expand...
Click to collapse
MCU.bin and FAC_Config were provided with this ROM, I can't modify something there so the best what you can do is use them.
Also it's better to flash them since you are reverting back to 4.4.2 and maybe something wont work well.

DrTrax said:
MCU.bin and FAC_Config were provided with this ROM, I can't modify something there so the best what you can do is use them.
Also it's better to flash them since you are reverting back to 4.4.2 and maybe something wont work well.
Click to expand...
Click to collapse
Can be flashed the root.zip file directly into the stock rom?

antonio2k said:
Can be flashed the root.zip file directly into the stock rom?
Click to expand...
Click to collapse
6. Wait a bit, the system will reboot by itself to recovery.
7. If the head unit boot into recovery, quickly insert the micro SD card with 'root.zip' and install it from extsd/usbhost.
8. Due some restrictions in Boot.img, the system will try to boot the system, but then realizes that the recovery was flashing a zip and will stay in recovery!
9. Flash 'root.zip' again and if done, just reboot the system
10. Victory Sound, you have root!

I am trying to enter recovery mode but I can not.
What steps do you follow?

antonio2k said:
I am trying to enter recovery mode but I can not.
What steps do you follow?
Click to expand...
Click to collapse
Just flash the firmware and wait until the preinstallation is done, the system will reboot itself ONLY ONE TIME to recovery (also only one time to prevent any bootloops or if someone don't want having root)
If you missed the recovery part, then you have to flash again or you could take a "little" bit of patience and try gain root with 360root.
Sry

DrTrax said:
Just flash the firmware and wait until the preinstallation is done, the system will reboot itself ONLY ONE TIME to recovery (also only one time to prevent any bootloops or if someone don't want having root)
If you missed the recovery part, then you have to flash again or you could take a "little" bit of patience and try gain root with 360root.
Sry
Click to expand...
Click to collapse
Can not be accessed with a buttons combination?
Something like that:
1. Hold RST button and POWER at the same time.
2. Wait 5 seconds.
3. Release RST button and wait 5 seconds.
4. Release POWER.

antonio2k said:
Can not be accessed with a buttons combination?
Something like that:
1. Hold RST button and POWER at the same time.
2. Wait 5 seconds.
3. Release RST button and wait 5 seconds.
4. Release POWER.
Click to expand...
Click to collapse
Not sure, you can try but I think that recovery were disable in that way, that bosion disabled the touchscreen in the boot.img

I will try!!! In the meantime maybe you can help me...in my bx411 there is not the logo select apk...is there any solution?

davidebeatrice said:
I will try!!! In the meantime maybe you can help me...in my bx411 there is not the logo select apk...is there any solution?
Click to expand...
Click to collapse
Check in the image folder. U will find the logo images, open the image you want and check in its options, you will see use as startup image.
You are welcome

kasafex2000 said:
Check in the image folder. U will find the logo images, open the image you want and check in its options, you will see use as startup image.
You are welcome
Click to expand...
Click to collapse
Thanks mate! thats what i was searching for!!

Great work DrTrax. Is this method also compatible with Bosion BX-412? I think it is the same devices are only that 412 has a CD slot.
Greetings Alex

I was hoping if someone on the blog can get me the Full .apk for
Bosion BX-411 T2. There is lots of people on this blog with this Stereo. Use Root Browser and grab the folder or all folders.
Kernel Version
Linux 3.4.39 - Sat May 28 14:13:57 CST 2016
OS Version
Android v4.4 - BSP 1.15 - 20160531
APP Version
APP 1.15

Is the rom in english or can I change the language after installing?

Bluetooth
Hi first thank you very much for the share you save my day (sorry my english im portuguese) i cant find where to conect the bluetooth can you help me?

Help...my HU BX411 ? I was update to firmware 20170408 (Bosion - GOC Bluetooth)everything its ok but stil reboot when turn on car engine...I have tried to install 20170715 (MCU) it turns to bad sound ... then I install back again to mcu 20170408 (Bosion - GOC Bluetooth) but my head unit suddenly totally dead... No black screen like shutdown but can't turn on... If this can be fixed?.. What should be doing master?? thank very much

7. If the head unit boot into recovery, quickly insert the micro SD card with 'root.zip' and install it from extsd/usbhost.
# At which Point shall I insert the card? In the step before i´ve power cycled the device, is it possible to insert the Card before power on? What is visible on the Display at the Point you are expecting to insert?
8. Due some restrictions in Boot.img, the system will try to boot the system, but then realizes that the recovery was flashing a zip and will stay in recovery!
# I´ve got the recovery dialog and tryed to select "...extsd" but nothing happend.
(I´ve formated SD as FAT32. Is this correct or shall i do it also with PhoenixCard as the Image file?)
9. Flash 'root.zip' again and if done, just reboot the system
Do you mean that I shall do it a 2nd time via the recovery dialouge?
Tnx 4 Help
Joe

Alfistagt said:
Is the rom in english or can I change the language after installing?
Click to expand...
Click to collapse
Yes, its possible in Language-Settings

Hi all, I own same device- quadcore bosion. And or course i have some problems with it. after just maybe some days of use, some of the built in apps stopped working. The icons still exist but nothing happens when I touch them. For example radio, equalizer, music player, auxin, BT music- in fact I cant use Bluetooth at all, it just doesnt search for the devices. And the top two buttons stopped working on the left side- power and back. volume works ok. After contacting the seller he sent me some "updates" from which is nothing better, just the same.
But still, I can download apps for everything, that stopped working, but still I would like to have bluetooth at least.
So I tried with this ROM but it is still the same, buttons, bluetooth and some apps that were left on ROM. So is problem software or maybe some hardware issue? I have to say that it happened the same once but it just went to normal the next day. But now nothing.
So what do you guys think of this? if there is no software to fix it I am just gonna use it as it is.
And thanks for all the work here and help.

YT9213AJ 2gb/16gb rooting/recovery

Do not blindly flash this device without knowing what you are doing. While the device is hard to brick in general, it is very easy for someone new to brick it by flashing the wrong partitions.
I will write a generalized tutorial that will cover the basics and hopefully make everyone feel better about flashing the device. At first I was skeptical but after understanding everything, I have to say it really isn't that bad, and I am here doing all the leg work for these fake 2gb (its really 1gb ram) and 16gb hdd
OK I am goin gto try and put all of this information in one place because these units say android 10 or 10.1 but in reality cpu-z they are android 9 with api of 27 (will double check to be sure. This unit says it is 2gb ram but it is indeed 1024 MB (q GB). I am not sure if the other custom firmwares dumps from 1gb yt9213aj models will work without problems on these yt9213aj units that say 2gb.
In order to try anything you need to first make a scatter file for your unit. I messaged the manufacture of my unit for a firmware and they sent it. I unzipped it and looked at the scatter file and it is of a different formatting than one that comes from mtk droid tool.
So, mtk droid tool doesn't work with OS versions 9 or higher. It is the problem of adb. But we can follow this guide https://forum.xda-developers.com/t/...not-revealed-error-in-mtkdroid-tools.3582571/ and get it to work.
Once you have your device connected and recognized in droid tools you should first create the scatter file, as this is the most important step to do a full readback in SP flash tools.
Once you have a backup, you are in the clear for the most part. I am still trying to figure out how to backup preloader and etc if possible.
Now you will also need to connect some kind of wire or some small buttons taken from something disassembled. Just something that you can use as a mock button because there is no hardware button on the device for up/down and OK and you cannot use the touch buttons. So you need to short these traces while in recovery in order to get further/
The main point of this thread is to update the existing ones and to add tools and stuff nmeeded in one location because it has taken me over 5 days to search for all fo this, and I am still not done, so lets make it a little easier on the new comers because the last thing we want to do is brick each others devices by using old outdated guides that don't fully work.
Flow chart of process: install mtk droid tools and sp flash tools ->enable oem debugging and oem unlock on device -> follow guide to get mtk droid tools to work -> get scatter file using mtk droid tools -> make a full readback in sp flash tools -> solder wires/buttons onto test points -> boot to fastboot and unlock bootloader -> fastboot flash recovery <image name> -> boot into recovery and install root and/or custom firmware.
Anyone more skilled knows any better?
This post is a WIP and will be updated periodically as I source information. The main idea behind this post is to bring all resources for yt9213aj in one spot. There is plenty of information, its just very hard to navigate especially for someone new to flashing these devices, and even worse to someone who has never flashed any device

OK after trying what seems like 300 twrp's I finally found one that does work with this device. I thin kthe main difference here is that the board is a new revision and some arch changes caused older version that were ported to not work. This one booted right into it but was in russian, which is easily fixable within the twrp gui.
I will add all of these files to the op when I have collected everything.
I do not think that this version board I have has hifi? Maybe I am mistaken? I have an audio glitch at 19-20 when playing music, the sound will get louder and sound good for a fraction of a second then return to sounding ****ty. So I will look into this more. What sucks is that there are so many of the same **** that doesn't work for this model so its like... I would rather garggle gasoline than have to sift through forums that were translated on the fly
Anyway here is the twrp for this particular device - https://www.dropbox.com/s/vogg7854a7ln2zu/twrp-9213aj.img?dl=0
EDIT: also you can boot to fastboot (adb reboot bootloader) and use fastboot getvar all to get factory partition sizes that's needed to create scatter file (you will need to use a hex calculator to create it, or wait for me to upload my scatter file once I have it done). You need to be making dumps in sp flash tool way before you are ever writing anything. Make plenty of readbacks and get to know how to read it before you write anything. Blindly flashing is not what you really want to do lol
Mtk drivers for pc
to install, you will need to disable signature verification and I had to turn on test signing as well

I have successfully rooted this thing. I did encounter something kind of strange though. When I patched the boot.img I had from the device and the one I got in ota update and patched with magisk. When I booted and checked the root with magisk it said there was an unsupported root using su already. It did this for both boot.imgs.
Anyone ever heard of this on stock firmwares? I am able to grant root permissions to busybox and etc so it seems to be working OK. Maybe the root that is there is the chinese root for backdoor tracking and surveillance xD
Wonder how to see what unsupported su commands are being sent?
EDIT: i also took a lot of pictures of the board. It is yt9213aj v1.2 board. I will update the original post in the few days with everything needed for this model including testpoints etc. The test points are a little different but its pretty much the same. The only two you need in the end are the two bigger ones (for unlocking bootloader) then your set. You could drill some holes and run wire down to the trace and put some hardware buttons for the mcu to use to select things in fastboot and official recovery.
There is also another port/connector on this thing above the touch sensor board. I think we could buy a ribbon cable to connect here and run it to another board with hardware button. Actually I think the connector is for hardware buttons specifically but I don't know for sure. Must do more research

These things have are rooted from the factory. When I try to use magisk it says there is another unsupported su. The Unsu.zip floating around cures that. Then you can install magisk.
Also another thing about these things being prerooted... I think you can dump and flash without any extra sp flash tools or mtkdroid. I was dumping the partitions using adb pull function. Adb pull /dev/block/platform/soc/11230000.mmc/by-name/<insert partition name here>"
And
"/dev/block/mmcblk0pxx" where xx is the specific partition to read/write to.
I had got a scatter.txt in the ota update I obtained from the manufacturer which had all the partition layouts. I used this and a log from a failed supersu.zip install to create a scatter.txt for this particular device. The supersu log can be obtained by trying to flash the supersu zip in recovery, then in adg just pull the log file adb shell cat /tmp/recovery.log. Once you have this, you will have to use brain.exe to make your own scatter for sp flash tools.
All in all its pretty easy to actually root the device, and they are actually rooted from the factory, most likely for some functions within the os to work (like surveillance and spying xD) but that can easily be removed with the unsu.zip then install magisk.
I will be writing up a guide for this specific model in a few more days. If you read this thanks for listening to the rumbling of a mad man

Just discovered another problem. When I try to edit anything in /system it says its read only. Mounting is or remounting it shows as successful with no errors, but something is blocking it from mounting as system. I am trying to rename this audio_effects.conf and it willnt let me. I think it might be some proprietary code in the kernel designed to block mounting or remounting of certain or all partitions.
I think that a lot of them are software locked, like the fader and balance and volume level. Notice how some of these have glitches when turning the volume up and down. I think that there is some code that disables some functions of higher end units, depending on the model. If you buy a cheaper 100 dollar head unit, maybe it is indeed just software locked down.
I know for fact the amp chip in my head unit, YD7388, sec sheet says 4 channel. But my device is only 2 channel, no fader. Also the spec sheet says it needs no output capacitor but mine has one I think (there is a huge capacitor soldered next to the chip. I have some pics of the board and test points and chip markers etc. Once I have everythign ready I will make a nice guide

Wow I think I found the reason this thing outputs as 2 channel on 4 speakers. I need someone with a real 4 channel version to message me so I can get a few files for comparison. If this is the case, a simple magisk module would fix the fixed 2 channel problem we have. In the audio_policy_configuration.xml they have all output set as
XML:
<devicePort tagName="FM Tuner Out" type="AUDIO_DEVICE_OUT_FM" role="sink">
<profile name="" format="AUDIO_FORMAT_PCM_16_BIT"
samplingRates="44100" channelMasks="AUDIO_CHANNEL_OUT_STEREO"/>
</devicePort>
I wonder if you set AUDIO_CHANNEL_OUT_STEREO to multichannel or maybe like "AUDIO_CHANNEL_OUT_QUAD " as described in the official android docs say, I wonder if that would enable true 4 channel (or 5.1)?
If someone who has a 4 real 4 channel stereo and it is around the model of yt9213aj, then send me a message so we can collaborate. If you are not rooted do not worry I will help you

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