Related
hi there!
I have a viewsonic n710 tablet ,it's a fake Nexus7,and it's only saled in chinese mainland,I have to say ,it sucks,hardware and software!
about hardware ,I only can do nothing,but the software ,because it's similar with nexus7 ,so I decided to do something on it!
now here comes my question:
I got stuck on unpacking zImage ,I used all the methods that learned from xda here ,but only repack_zImage works,but whatever version I used to unpack the zImage ,the result seems not right,the early version I used can extract some files in the zImage_unpacked folder but it prompted wrong message and quit ,the newest versiion (0.6) I used can also extract some files in that folder but the program keep displaying many increased numbers and never stop unless you pressed "ctrl+c" to quit it forcely ,so I think the files maybe not right either!!!
in the first place ,I think the tools I used to unpack is not compatible with my n710 zImage,so I searched at least 3 different to unpack my kernal,
unpack ,unpack-initramfs,repack_zImage, the former 2 tools even can not extract anything from zImage ,only extract a folder named initramfs_root,only repack_zImage did something but seems not right!!
so I tried such ways to unpack nexus7 zImage for proving ,but it surprised to me that it can not unpack nexus7 either!!
I am confused now,I have been searching solution to solve this problem for two days,but a little achievment I got!!!
the only way I can do now to ask such question at here,I am sure that some people can extract right files from zImage ,(because they even can do an custom kernal for nexus7,:good:I adore them so much,)so will someone tell me how to unpack right files from zImage???or did I miss any important things for unpacking ,I am a green hand on linux system.,so I might make many silly mistakes on operation
!!
thank you very much in advance!!any suggestion and hint also will be appericated!!
Just because it might look/seem like a n7, its not one. Its different so our kernels wont work
Kernels aew very specific so they need to be made for the device because they have different hardware
Sent with from my Asus Nexus Unicorn
markj338 said:
Just because it might look/seem like a n7, its not one. Its different so our kernels wont work
Kernels aew very specific so they need to be made for the device because they have different hardware
Sent with from my Asus Nexus Unicorn
Click to expand...
Click to collapse
sure ,I cann't agree any more with your opinion!thank you for your information!
but if I knew the way to unpack nexus7 zImage ,I could also unpack n710 zImage!you know ,if I could unpack kernel ,I would hack it with my mind!
Viewsonic N710
Hi There
I agree with you, i bought the same Tablet and the prior Incident is that you can not install the Google Playstore. Contacting the "Customer" Support is useless cause you always have a different employee who answers emails or is on the Chat Line. I asked them now for about 6 Times to give me a RMA Number and the Return Adress and it they do not want to understand.
The Tablet itself seems to have a good Hardware, Sygic runs very fast and stable, i also installed some Games and they are very solvent.
Dolphin HD didn't runs for the First Installation but now also runs stable and fast.
There is an Instruction on Tabletrepublic but it didn't work for me. I was able to install the ADB Driver and can also run it from the DOS Box. I was not able to Root the Tablet which is necessary to get Google Playstore to Run.
Does anybody else has rooted this Device and can explain how he did it...?
Thanks
Michael
chinajjb said:
hi there!
I have a viewsonic n710 tablet ,it's a fake Nexus7,and it's only saled in chinese mainland,I have to say ,it sucks,hardware and software!
about hardware ,I only can do nothing,but the software ,because it's similar with nexus7 ,so I decided to do something on it!
now here comes my question:
I got stuck on unpacking zImage ,I used all the methods that learned from xda here ,but only repack_zImage works,but whatever version I used to unpack the zImage ,the result seems not right,the early version I used can extract some files in the zImage_unpacked folder but it prompted wrong message and quit ,the newest versiion (0.6) I used can also extract some files in that folder but the program keep displaying many increased numbers and never stop unless you pressed "ctrl+c" to quit it forcely ,so I think the files maybe not right either!!!
in the first place ,I think the tools I used to unpack is not compatible with my n710 zImage,so I searched at least 3 different to unpack my kernal,
unpack ,unpack-initramfs,repack_zImage, the former 2 tools even can not extract anything from zImage ,only extract a folder named initramfs_root,only repack_zImage did something but seems not right!!
so I tried such ways to unpack nexus7 zImage for proving ,but it surprised to me that it can not unpack nexus7 either!!
I am confused now,I have been searching solution to solve this problem for two days,but a little achievment I got!!!
the only way I can do now to ask such question at here,I am sure that some people can extract right files from zImage ,(because they even can do an custom kernal for nexus7,:good:I adore them so much,)so will someone tell me how to unpack right files from zImage???or did I miss any important things for unpacking ,I am a green hand on linux system.,so I might make many silly mistakes on operation
!!
thank you very much in advance!!any suggestion and hint also will be appericated!!
Click to expand...
Click to collapse
Jiggasonic said:
Hi There
I agree with you, i bought the same Tablet and the prior Incident is that you can not install the Google Playstore. Contacting the "Customer" Support is useless cause you always have a different employee who answers emails or is on the Chat Line. I asked them now for about 6 Times to give me a RMA Number and the Return Adress and it they do not want to understand.
The Tablet itself seems to have a good Hardware, Sygic runs very fast and stable, i also installed some Games and they are very solvent.
Dolphin HD didn't runs for the First Installation but now also runs stable and fast.
There is an Instruction on Tabletrepublic but it didn't work for me. I was able to install the ADB Driver and can also run it from the DOS Box. I was not able to Root the Tablet which is necessary to get Google Playstore to Run.
Does anybody else has rooted this Device and can explain how he did it...?
Thanks
Michael
Click to expand...
Click to collapse
To root N710 is not a big deal any more!you can flash cwm recovery to help you ,I released cwm for N710 at Tabletrepublic,so just download the right version recovery for your tablet ,please aware that 1.01-1.05,1.07,they don't use the same cwm recovery!
after fflash recovery ,run into cwm recovery ,and flash superuser.zip just like nexus 7 does!
of course you can also flash the gapps.zip to get google service serial and what not !
good luck to you if you tackle it!
Introduction
This is a collection of Tools and Resources for Flashing Mi2(s)(c).
MiFlash4Linux
https://github.com/M1cha/aries-image-builder
Core Recovery Package for MiFlash
This is a small package to Recovery MI2 from any bricked state. It has the following advantages over the official ones from Xiaomi:
They don't flash any ROM, just the core system(bootloaders, modem and recovery)
They are small which means both Download and Installation are faster
It directly installs custom Bootloader and TWRP. That means you easily get your device back to a modded status.
Please follow the official MiFlash guidelines for installation with the following differences:
the DLOAD config is called rawprogram_core.xml
the fastboot script is called flash_core.bat(or flash_core.sh for linux)
there's a script called flash_partition_table_and_core which is a alternative to flash_core.bat/sh.
It can be used to change the partition table.
USE THIS WITH THE CUSTOM BOOTLOADER INSTALLED BY ONE OF THE CORE PACKAGES ONLY. Xiaomi's bootloader will format your whole MMC device. THIS WOULD ERASE YOUR EFS AND YOU CAN'T MAKE CALLS ANYMORE
Changing the partition table
There are multiple packages available:
separated: Xiaomi's original layout with a virtual internal sdcard
separated_single: same as separated but without Dualsystem and bigger system partitions
unified: Xiaomi's new layout with /data/media support
unified_single: same as unified but without Dualsystem and bigger system partitions
unified_single_xiaomi: Xiaomi's version of unified_single
SkiFire13 said:
aries_core_unified_single.zip -> only MIUI > 5.4.x or M1cha's CM12.1 or latest AOSP5 works (only they can see Internal Storage, that now is a virtual sd-card in /data/media/0)
aries_separated_single.zip -> other roms
Click to expand...
Click to collapse
Installation:
Backup all your data(including internal sdcard, and EFS just to be safe)
if you don't use the custom Bootloader yet, flash this package using flash_core.bat/sh first. See the big red warning above for more information
flash the package using flash_partition_table_and_core.bat/sh
boot into recovery(which is TWRP now), recreate the filesystems for all partitions(system,data,cache,sdcard to ext4) in the wipe menu and reinstall your ROM.
Version Information
Bootloader: https://github.com/M1cha/mi2_lk/commits/LA.AF.1.1-02810-8064.0
TWRP: v2.8.7.0
core partitions: aries_images_5.7.16_20150626.0000.4_5.0_cn_a63cddccfa.tgz
Download links for Mobile users:
aries_core_unified_single_xiaomi.zip
aries_core_unified_single.zip
aries_core_unified.zip
aries_core_separated_single.zip
aries_core_separated.zip
XDA:DevDB Information
Flashtools, Tool/Utility for the Xiaomi Mi 2
Contributors
m11kkaa
Source Code: https://github.com/M1cha/aries-image-builder
Version Information
Status: Stable
Created 2015-02-21
Last Updated 2015-07-27
First (as always)
Sent from my A0001
the singleboot packages causes the latest version of CM12 to fail booting because of SELinux enforcing. I'll upload a fixed package asap.
everything has been fixed and is up again.
Pls download everything again(especially MiFlash4Linux if u use that).
i think i will wait util the release of GRUB4Android....
acastrocab said:
i think i will wait util the release of GRUB4Android....
Click to expand...
Click to collapse
the purpose of this thread is not G4A
G4A doesn't allow u to change the partition table. I may publish a simple tool for it though.(so u don't need a computer).
m11kkaa said:
the purpose of this thread is not G4A
G4A doesn't allow u to change the partition table. I may publish a simple tool for it though.(so u don't need a computer).
Click to expand...
Click to collapse
Hey m11kkaa, I'm sorry for the noob question, but where can I download the files for windows? And how should I use them? I can't understand from the OP. Thanks in advantage for your help
MyNameIsKappa said:
Hey m11kkaa, I'm sorry for the noob question, but where can I download the files for windows? And how should I use them? I can't understand from the OP. Thanks in advantage for your help
Click to expand...
Click to collapse
On the top of the page just followed by the title, there is a "Download" tab, you could find the miracle at there ;p
MyNameIsKappa said:
Hey m11kkaa, I'm sorry for the noob question, but where can I download the files for windows? And how should I use them? I can't understand from the OP. Thanks in advantage for your help
Click to expand...
Click to collapse
I can't find the links too, but i saw this link in another thread... http://forum.xda-developers.com/devdb/project/?id=8360#downloads
ancics said:
I can't find the links too, but i saw this link in another thread... http://forum.xda-developers.com/devdb/project/?id=8360#downloads
Click to expand...
Click to collapse
You can see this with a computer only.(Tapatalk doesn't work)
http://puu.sh/gamlY/dd7e4904f9.png
Hey M1cha, thank you! Great job!
I have some issues about the procedure:
1. I am not sure if already had a custom bootloader, so first i'll flash the package flash_core.bat :
- turn on mi2s in fastboot mode
- plug usb, device should appear in miflash(the program should be configured as the photo?)
- and click flash
- reboot phone, enter in fastboot mode again and do the same procedure with flash_partition_table_and_core.bat
Is that right?
It's easy to recreate the ext4 filesystem in TWRP? always used CWM....
m11kkaa said:
You can see this with a computer only.(Tapatalk doesn't work)
http://puu.sh/gamlY/dd7e4904f9.png
Click to expand...
Click to collapse
Oh that's why, I'll download it from a computer, thanks!
Sent from my MI 2S using XDA Free mobile app
@m11kkaa: thnx for the linux tools/scripts, it made my migration from CWM to single-system partition + new bootloader + TWRP easier.
BTW, I just wanted to migrate and keep my current CM11 for the time being. I had to fight a bit with restore from backup because I was not aware of the incompatibility between CWM and TWRP, luckily enough it eventually was sufficient to:
reformat system, data and cache in TWRP
flash the old CWM temporarily and restore boot, system and data
flash TWRP again and make new backups.
Proposal:
It would be good if you can change the heading style of "Installation" in the OP to be the same as e.g "Introduction", because now it looks like part of "Singleboot Partition Layout" section only. It is confusing IMHO.
In my case (i.e. flashing both flash_core.sh and then flash_partition_table_and_core.sh), I had to recreate ext4 FS not only on the system partition in TWRP, but also on the data partition (it could not be mounted and TWRP announced 0 MB size) and eventually also on the cache partition. This seems to contradict the info in OP, part "Singleboot Partition Layout", which mentions that data will be preserved.
@cogano thx for your feedback
it's weird that u had to recreate the filesystems because the positions of these partitions still are the same. I resized system1, modem1 and boot1 to 2KB and system, modem and boot to 2*oldsize-2KB. I checked the offsets and they still are the same.
I have another phone and plan to do the same some time in the next week.
I'll try to avoid the trial&error approach and keep notes between the steps.
P. S. I am quite proficient with Linux administration. However I have to admit that upgrading android devices is usually a risky thing: I would have to read lot of guides - often unclear and confusing - or just give it a go and resolve the problems as they appear. The latter one eventually seems to be faster
cogano said:
I have another phone and plan to do the same some time in the next week.
I'll try to avoid the trial&error approach and keep notes between the steps.
P. S. I am quite proficient with Linux administration. However I have to admit that upgrading android devices is usually a risky thing: I would have to read lot of guides - often unclear and confusing - or just give it a go and resolve the problems as they appear. The latter one eventually seems to be faster
Click to expand...
Click to collapse
thx "parted /dev/block/mmcblk0 p" will help to debug these things.
If you don't have a ROM/Recovery with parted you can reboot to dload from the bootloader which will provide ur whole MMC as a usb drive to your computer.
i didn't see the download tab at first, so i downloaded the whole zip from the github and excuted the ./build.sh in Cygwin. Anyway, it works!
m11kkaa said:
you can reboot to dload from the bootloader which will provide ur whole MMC as a usb drive to your computer.
Click to expand...
Click to collapse
What a great feature!
superiyezi said:
i didn't see the download tab at first, so i downloaded the whole zip from the github and excuted the ./build.sh in Cygwin. Anyway, it works!
Click to expand...
Click to collapse
There's a Download "card" on top.
What are the partitions sizes after flashing the singleboot partition layout?
TWRP3.2.30-Universal version uploaded
https://drive.google.com/open?id=16BueY8230PzL-5ngkMiNZGxpIYBoK4EL
TWRP3.2.20-Universal version uploaded
https://drive.google.com/open?id=1Qr35EfIy76c6lkQZaKBzRS_PuBhUfjMX
TWRP3.2.10-Universal version uploaded
Rebased on TWRP3.2.1-0
https://drive.google.com/open?id=1Tcc5pk-7MOz5IRwqgH-zfKj-t7pnSMi5
TWRP3.2.0-0-Universal version uploaded
Changelog:
Backup / Restore every possible partition
Supports both Android 5.x and 6.0+ partitioning schemes
Oreo ready..........
https://drive.google.com/open?id=1uJAc84Qgw4k1NW3W3BjcVtwc37y--xz8
TWRP3.1.1-0-Universal version uploaded
Changelog:
Uses 7.5.11 Android 5.02 kernel
Backup / Restore every possible partition
Supports both Android 5.x and 6.0+ partitioning schemes
https://drive.google.com/open?id=0BwdRTuyj12_yVWZqUnd6MEN0QVk
Note: This version saves to a folder named as the serial number of the device which is different to the previous version. Old backups will not work unless they are copied into the new folder.
TWRP3.0.2-2 has had a makeover also:
Rebased on 7.3.16 Kernel
Removed F2FS support to prevent "mishaps"
Added ability to backup & restore Preloader partition
https://drive.google.com/open?id=0BwdRTuyj12_yU19qQWNra1o3alk
Hi, great work. Can you make twrp 3.0 for our beloved xrmn2? It's has been released: http://www.xda-developers.com/twrp-3-0-0-has-arrived/
If you don't like the extensive partition listings in the original, I have altered the fstab files and repacked so you see only the necessary partitions for each function. Other than that, it is the same.
Now only one version with all the partitions you need and none that will get you into trouble
Thank you for sharing!
jajk said:
TWRP3.0 is here. All credit to Jeminni.
Unpacked, examined and tested to be fully functional and free from malware by me. This is totally unaltered - just mirrored here for convenience.
Click to expand...
Click to collapse
Hi, great work...thanks alot, just keep peaking !
Can we get informed by you what kind of malware plant in this, does it method by flashing any zip using it or by restore/backup process?
Anyway, u're whispering somethin' th
at we cant wait ur MM builds desperately...
@Adam Hui Maybe you misunderstood, I checked that there is no malware in the original by unpacking it and looking at the code. I also tested every function does not break the phone and works correctly. I am assuring other users that maybe cannot examine the contents that it is clean.
My modified version only rationalizes how partitions are presented in Recovery. Try the original and you will understand the need to alter the partitions displayed.
MIUI based on MM is in beta testing for ReNo2 already (I am not one of the beta testers)
Be careful what you wish for as MM brings everyone one step closer to a closed platform like Apple. I would be happy on 5.1.1
jajk said:
[MENTION=4666525]
Be careful what you wish for as MM brings everyone one step closer to a closed platform like Apple. I would be happy on 5.1.1
Click to expand...
Click to collapse
Hey man, pls washout that greyed info.
Do u mean there'll be a locked bootloader in miui MM ?
U should inform us if u knew it at first time !
Hi, Is there a MultiROM / dualboot feature included in this release?
Thank you to jemimi for the dev work and thank you in advance for any reply.
@MiSteven No dualboot in this one and I haven't seen one for our phone (not that I have been looking)
New version 3.0.0-3
jajk said:
New version 3.0.0-3
Click to expand...
Click to collapse
Is this update of jemmini's TWRP_3_ReNo2.zip from 4pda.ru?
@sanceliken2000 No it is original.
jajk said:
@sanceliken2000 No it is original.
Click to expand...
Click to collapse
Thanks for the answer. Could you please tell me if i could flash it directly with twrp 3 jemminis' in order not to do the procedure with fastboot?
@sanceliken2000 Just flash it in your existing TWRP (it is a flashable zip)
Interface look good, old backups need to be re-backup! Thx~
addro said:
Interface look good, old backups need to be re-backup! Thx~
Click to expand...
Click to collapse
If you have backup made by jemmini's TWRP3 it is not necessary to re-back. The new one understands that backup.
@faorekh It surely is. I look for compatible donors since we have no official build for our device.
The only thing that changes from previous TWRP backups is the folder name where it is stored. If needed, rename the old folder to /TWRP/BACKUPS/Redmi_Note_2 and TWRP will see it or just move the old backups into the new folder when it is created on first new backup.
There is the signature "Lenovo/full_aio_otfp/aio_otfp" inside recovery. Is this recovery port from recovery-twrp-3.0.0-3-k3.img of Lenovo K3 Note?
This version works great for my rmn2 prime.
Sent from my 2014817 using Tapatalk
I flashed this recovery yesterday through my twrp 2.8.7.
After updating to TWRP 3.0.0-3 I got messages like this:
Code:
This package is for "hermes" devices; this is a "".
[COLOR="Red"]Updater process ended with ERROR: 7
Error installing zip file '/external_sd/!Flash/twrp287.zip'[/COLOR]
After that I used the fix in this thread to make my old recovery flashable again. Now everything works fine again, but you may want to look into that, so others won't have to get similar headaches as me.
Little note: I spent 3 hours trying to make this work under OSX El Capitan, but it seems like OSX can't create flashable zips. I used a windows partition to zip the files and everything worked fine.
WARNING : I will not responsible for any damage and lost, USE IT AT YOUR OWN RISK.
EDIT : USE V2, V1 have a serious bug in restore.
Functions :
-- Backup specified block to image
-- Restore specified image to block
Principle :
This tool using the exploit of linux kernel (or you can use normal shell superuser, but I didn't test that yet),
and use dd command to dump the block, pull it out, then there have the image of that block.
Limit :
-- You can't backup image that bigger than your phone's free space.
-- This tool is only available for Windows.
How to use :
Download the zip below, then go read Readme.
Credit :
@nlra for possible root method
someone for "su98-memory-kallsyms" binary
Nice job!
It's awesome you made an easy tool for TA backup/restore. There are perhaps millions of devices still locked out there.
I haven't tested the tool since I don't have a windows machine, but this should surely make things a bit simpler to those who arrive now to the XZs party (such as myself).
I already got my TA backup (unlocked BL and relocked) but I'm sticking to stock for now because I can't find a way to have both camera support and stability. Surprisingly, the smoothest rom I found was built for a different device (XZ) lacking only camera support in the kernel.
Can I ask what rom did you end up using?
dinosaur99 said:
Nice job!
It's awesome you made an easy tool for TA backup/restore. There are perhaps millions of devices still locked out there.
I haven't tested the tool since I don't have a windows machine, but this should surely make things a bit simpler to those who arrive now to the XZs party (such as myself).
I already got my TA backup (unlocked BL and relocked) but I'm sticking to stock for now because I can't find a way to have both camera support and stability. Surprisingly, the smoothest rom I found was built for a different device (XZ) lacking only camera support in the kernel.
Can I ask what rom did you end up using?
Click to expand...
Click to collapse
I think there has no a rom which can use as daily for xperia xzs due to its short battery-life.
But if you have time to try different possibles, maybe you can flash android 11 aosp-based rom, maybe that works.
thank you, i have successfully backed up my ta
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