[ROM] [7.1.2] Mik-el Android for Takee 1

[Mik-el]

Device and Project Presentation
In 2015 the chinese company EStar launches on the market the Takee 1. An octacore smartphone with an astonishing Holographic 3D technology developed by the german Seereal.
Despite the cutting-edge hardware, a low price and the big innovations in the field of 3D and airtouch... the phone does not receive the big success it deserved, Estar closes down and the last official software update dates back to 2015, leaving the whole system stuck to Android 4.2.

But today, 5 year after the last update and the closure of the company, I continue what the far-sighted EStar was doing, studying 3D technologies and releasing a new Android 7 Software Update.
I had to face many difficulties but...
making an Android 7 ROM from just an Android 4.2 base is now possible!
Let's go guys!

Presentation Image

http://imgur.com/Be7YKsg

Other screenshots

http://imgur.com/a/RRyUNL7

Youtube video
*avaible in the next hours*

v1.0
First release that can boot, no need to download it.


v1.1
Usability

• WiFi module - Working
• Phone module - Working
• Audio - Working
• Camera - Working (you have to apply a fix)
• Fm radio - Working
• USB debugging - Working
• Bluetooth - Not working but I'm working on a fix!
• Holographic 3D and AirTouch support - in Development

Theming
Transition from RidonOS to Mik-el Android:

• Removed most of the references to RidonOS and Micromax 311
• Mik-el bootscreen (boots faster)
• Mik-el wallpaper

Apps

• Replaced Ridon launcher with a lighweight Open Source Pixel Launcher
• Removed Old Google apps, size of the rom reduced
• Added F-Droid, Open Source alternative to Google play store
• Added 52kb app to exchange files on wifi between smartphone and PC
• Added OpenCamera, best android camera app (and it's Open Source)
• Added High quality Audio recorder with noise reduction

System and Performance

• Enabled USB Debugging by default
• Adjusted dpi value: screen is more readable and system is more reactive!
• Removed loudsound patch to avoid possible conflicts with the original Cauldron Audio driver added by EStar

Mik-el fixes to extend the life of your device

• system warns you when you reach high temperatures
• system doesn't write on the phone memory over and over again (The original Takee 1 stock rom is based on Android 4.2 and trimming was introduced starting from Android 4.3 only)
• you can install apps directly on external SD card - starting from v. 1.2

Support me:

• Telegram Channel here
• Instagram here
• Youtube here
• Paypal here

XDA:DevDB Information
Mik-el Android 7 for EStar Takee 1

Contributors
Mik-el
ROM OS Version: 7.1.2 Nougat
ROM Kernel: Linux 3.4.67

Version Information
Status: Stable with some bugs

Created 2019-11-02
Last Updated 2020-12-08

 

[Mik-el]

TWRP by Mik-el - Download and Instructions
To flash an Android 7 Rom You must use an updated TWRP custom recovery!
I made a new TWRP for Takee 1 and I released 2 versions

• TWRP 3.1.1. here
• TWRP 3.1.1 with OTG support here

Instructions and Screenshots are include in the previous links.


Rom Download
*coming soon*


Integrity Infos
*Coming soon*


General Advices about Takee 1

• Don't use the original charger, probably you have a good one but it gave problems to most of the users
• Don't try to flash this rom with SP Flash tool, you can't, follow the instruction I'm providing here

Instructions to flash the Rom

1. Backup any important data of your phone;
2. Download and Install the updated TWRP custom recovery made by me if you haven't done it yet:
   • TWRP 3.1.1. here
   • TWRP 3.1.1 with OTG support here
3. Download my rom, the file is a .7z archive that contains the rom in .zip format;
4. Use a software like 7zip to extract the rom .zip file and copy it on your microSD;
5. Once you have installed the recovery you can boot into it;
6. "Wipe" -> "Swipe to Factory Reset";
7. "Install" -> select the .zip file for the rom -> "Swipe to flash"
8. "Reboot" -> "System"

How to solve Camera Bug for ROM version 1.1
Open the "Reboot Manager" app and do a quick/warm reboot, now your cameras work!

Spoiler: Click here for an Alternative Method

Go to Settings

1. Go to developer options
2. Activate "extended reboot menu"

When you want to use the camera:

1. Long press power button and select "reboot" - you will be asked, which type of reboot you want to do
2. Select "warm reboot"
3. Camera is now working!

Definitive solution
Will be solved in the next release.
Help me with testing and support me to get an invincible Rom!


Next updates

• Full 3D and Airtouch Support
• Camera ready at boot without warm reboot
• "Mik-el Rom Updater" to update the system with one touch
• Bluetooth Fix
• whathever you want!

Support me
Leave a 5 stars review and a positive review using the panel on XDA.
Use these links to support me:

• Telegram Channel here
• Instagram here
• Youtube here
• Paypal here

Credits

• Mik-el
• a big hug to io2345 for:
  • helping me with testing and fixes
  • donating 10 euro for the development
  • for exchanging almost 150 mails with me to bring this project to life!
• YuriRM
  • for having collected informations and having made a detailed list of Harware specs from phones similar to the Takee 1
  • for his continuous effort to bring back interest in this device on XDA and Telegram
• kano3d
  • for donating 4 euro for generic 3D development
• other members of the Takee 1 community (giotogo and Talwarmirza)
• two boys that give me an advice on Telegram ()
• an unknown artist for the Mik-el Android wallpaper

 

[Mik-el]

Reserved for future Updates.
P.S. Ignore the very next posts below: intially the community and I were talking about other things (problems faced during development), and NOW that the Rom is ready I updated this same thread, to don't make a new one. Now, Enjoy

 

[YuriRM]

ROM for Holographic 3D smartphone

Thanks! This ROM will bring a fresh air and new lease of life to EStar TAKEE 1, the first ever Holographic 3D smartphone launched in 2015 at an affordable price ($100-150). Nobody will need to buy an extremely expensive RED Hydrogen One at $1200.
The 3D community will rejoice!

The amazing resources of PHEREO are available to all lovers of 3D Stereo Images and Photos.
http://phereo.com/
Select an image and click Wiggle... if you do not have a smartphone with 3D display.

My advice is to install the PhereoRoll3D app too!
https://github.com/JackDesBwa/PhereoRoll3D

NewPipe - to download 3D videos from YouTube
https://github.com/TeamNewPipe/NewPipe/

INVIDIOUS - to download 3D videos from YouTube, VEVO, etc.
https://www.invidio.us/

Plenty of resources for 3D lovers that justify buying a device with 3D display.

 

[giotogo]

interesting. this phone is still good.....

 

[io2345]

Anyone with ViperOS development experience?

 

[Mik-el]

Anyone with ViperOS development experience?

More than ViperOS developers we need someone that has experience with rom porting.
I made more than 7 releases for this ROM and @io2345 tested them all!
We solved the failed installation problem, now we just need to solve the bootloop.
The porting process is OK, the updater-script file is OK, file permissions are OK...
I don't know where the problem could be!

Next time I'll use another porting guide. (there are only 2 guides and one didn't work since now)
Instead of ViperOS I'll also use a LineageOS rom as port rom.
Let's see what I can get.

(Stay tuned subscribing to this thread and collaborating with us, cheers)

 

[YuriRM]

Greek & Indian ROM ports by Jpower7 (A310 kernel) and blacklisted.rock (A311 kernel)

My suggestion is to try other 3.4.67 ports for EStar Takee 1.

ROM ports by Jpower73 (A310 kernel) - Greece
He maintains working links for his ROMs. Therefore, you can also ask his help.

(Android Ice Cold Project) for Coolpad F1/MmxA310-Α311/Himax Polymer Octa by Jpower73
https://forum.xda-developers.com/a310/development/android-ice-cold-project-coolpad-f1-t3802656

HTC SENSE 10 for Coolpad F1-A310-Himax Polymer Octa by Jpower73
https://forum.xda-developers.com/a310/development/htc-sense-10-coolpad-f1-a310-canvas-t3952369

Poly Os for Coolpad F1/Micromax Canvas Nitro A310/Himax Polymer Octa by Jpower73
https://forum.xda-developers.com/a310/development/poly-os-coolpad-f1-micromax-canvas-t3801223


ROM ports by blacklisted.rock (A311 kernel) - India
The developer does not use his device anymore. His phone is over 5 years old and the battery is malfunctioning.

[BUGLESS][7.1.2]Ridon OS for A310/A311/Coolpad F1/Himax Polymer by blacklisted.rock
https://forum.xda-developers.com/a310/development/bugless-ridon-os-a310-a311-coolpad-f1-t3779279

[ROM][FINAL]Resurrection Remix OS 5.8.5 V4.0 for A311/A310/Coolpad F1/Himax Polymer by blacklisted.rock
https://forum.xda-developers.com/a310/development/rom-resurrection-remix-os-5-8-5-v4-0-t3786640

But you can look for other ROMs here
https://forum.xda-developers.com/a310/development


List of TAKEE 1 clones for parts by YuriRM
https://forum.xda-developers.com/showpost.php?p=74386084&postcount=1199

EStar Takee 1 - list of components
http://deviceinfohw.ru/devices/inde...=cpu0&brand=brand0&filter=takee&submit=Search

HIMAX POLYMER - 10 shared components with EStar Takee 1
Back CAMERA and Front CAMERA (sunny_imx135_mipi_raw and ov5648_mipi_raw), LENS, ALSPS, one part in two of CHARGER (fan5405), PMIC, WIFI and two parts in four of OTHERS (kd_camera_hw and dummy_eeprom) and RAM.
http://deviceinfohw.ru/devices/item.php?item=1083

Micromax A311 \ A315 \ A316 - just 1 shared component with EStar Takee 1
Back CAMERA
http://deviceinfohw.ru/devices/item.php?item=4999 (A315)
http://deviceinfohw.ru/devices/item.php?item=3526 (A316)

There is no data for Micromax A311 and A310
http://deviceinfohw.ru/devices/inde...m0&brand=brand0&filter=Micromax&submit=Search

I have requested to upload the list of components of Micromax A311 and A310 to the Device Info HW database

 

[YuriRM]

Android 4.4.2 KitKat kernel - BQ Aquaris E5 FHD

Official source code for BQ Aquaris E5 FHD
https://github.com/bq/aquaris-E5FHD

Have you acquired knowledge enough for including specific drivers of EStar Takee 1 into this Android 4.4.2 KitKat kernel of BQ Aquaris E5 FHD?

You will get a much better kernel (3.4.67) than luckasfb.

Instructions

Building custom kernels for Android devices
https://source.android.com/setup/build/building-kernels

SavageMessiahZine - Russian forum of Android kernels and assembly instructions

Development of kernels and firmware for devices on the MTK platform � | Self-compiled kernel from source � | Instructions for building ANDROID from sources. � | Theme on assembling the source code MTK on china-iphone | Build TWRP for Qualcomm platform �
https://www.savagemessiahzine.com/forum/index.php?showtopic=583114

Guidance from LordArcadius (GitHub and Telegram) and nathanchance (XDA)

Compiling Android Kernel for your own device #67
https://github.com/ILUGD/talks/issues/67

XDA Reference guide:- https://forum.xda-developers.com/an...erence-how-to-compile-android-kernel-t3627297
Help and support Telegram group:- http://t.me/LinuxKernelChat
Upstreaming guide:- https://forum.xda-developers.com/an...rence-how-to-upstream-android-kernel-t3626913
Toolchain:-
GCC 4.9 for 64 bit:- https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/
GCC 4.9 for 32 bit:- https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/

My Telegram username:- @LordArcadius

 

[YuriRM]

GPIO pin numbers in the Circuit Board of EStar Takee 1

I hope there is a solution for camera bugs introduced by luckasfb in his latest kernel of EStar Takee 1.
Some KitKat kernels share both cameras (Sony imx135_mipi_raw and OmniVision ov5645_mipi_yuv) with EStar Takee 1.
However, it may be down to GPIO pin numbers in the Circuit Board. That is why I want to know the Circuit Board ID number, the physical address number of each component and GPIO pin numbers of camera sensors of those devices.
That info is included in the kernel source code of BQ Aquaris E5 FHD.

@giotogo can you find this information inside your EStar Takee 1 device, please?
Circuit Board ID number
GPIO pin numbers of camera sensors in the Circuit Board
Take detailed photos of internal components
Take detailed photos of internal numbers printed in the motherboard.

This information may help find other devices that share an identical Circuit Board ID number. This list of most compatible devices is useful. Hopefully, It will enable to choose the easiest Android 7.1.2 Nougat ROM to port into EStar Takee 1.

It also provides crucial information for changing the GPIO pin numbers of both cameras in the KitKat kernel source code of EStar Takee 1.

Bug in power for cameras GPIO pins in codegen - EStar Takee 1
https://forum.xda-developers.com/showpost.php?p=79024675&postcount=1361

The video below shows how to open a device and find the Circuit Board ID number.

However, my guess is that it boils down to the physical address number of each component and GPIO pin numbers in the motherboard. This enables to direct each camera driver (front and back cameras) to a specific address in the Circuit Board (GPIO pin number). This is the info that luckasfb tried so hard to find, trying by hand hundreds of combinations for GPIO pins. He did not open the case of his EStar Takee 1 device.

How to Find and download Firmware file for chinese tablets
https://www.youtube.com/watch?v=XZqLoxpbUSA

 

[YuriRM]

How to fix a bootloop after installing a Custom ROM like Viper OS

Anyone with ViperOS development experience?

@io2345 how are you doing? It has been a long time since we last talked.
I may have found a solution for the bootloop of the Viper ROM ported by @Mik-el.
Can you test this method, please?

Have you watched this video by the clever german guy, Christoph Zahradnik ?
His Viper ROM is used in this explanation... Viper SC2_5.2.1.zip ?

How to fix a bootloop after installing a Custom ROM like Viper OS (07/03/2015)
By Christoph Zahradnik
https://www.youtube.com/watch?v=cgYXy2XC1SM

Below find what happened on the previous day.

HTC Sensation (Snapdragon S3) and Viper ROM - installing a Custom ROM and entering a bootloop (06/03/2015)
By Christoph Zahradnik
https://www.youtube.com/watch?v=-Snab4bsnzQ

 

[giotogo]

I hope there is a solution for camera bugs introduced by luckasfb in his latest kernel of EStar Takee 1.
Some KitKat kernels share both cameras (Sony imx135_mipi_raw and OmniVision ov5645_mipi_yuv) with EStar Takee 1.
However, it may be down to GPIO pin numbers in the Circuit Board. That is why I want to know the Circuit Board ID number, the physical address number of each component and GPIO pin numbers of camera sensors of those devices.
That info is included in the kernel source code of BQ Aquaris E5 FHD.

@giotogo can you find this information inside your EStar Takee 1 device, please?
Circuit Board ID number
GPIO pin numbers of camera sensors in the Circuit Board
Take detailed photos of internal components
Take detailed photos of internal numbers printed in the motherboard.

This information may help find other devices that share an identical Circuit Board ID number. This list of most compatible devices is useful. Hopefully, It will enable to choose the easiest Android 7.1.2 Nougat ROM to port into EStar Takee 1.

It also provides crucial information for changing the GPIO pin numbers of both cameras in the KitKat kernel source code of EStar Takee 1.

Bug in power for cameras GPIO pins in codegen - EStar Takee 1
https://forum.xda-developers.com/showpost.php?p=79024675&postcount=1361

The video below shows how to open a device and find the Circuit Board ID number.

However, my guess is that it boils down to the physical address number of each component and GPIO pin numbers in the motherboard. This enables to direct each camera driver (front and back cameras) to a specific address in the Circuit Board (GPIO pin number). This is the info that luckasfb tried so hard to find, trying by hand hundreds of combinations for GPIO pins. He did not open the case of his EStar Takee 1 device.

How to Find and download Firmware file for chinese tablets
https://www.youtube.com/watch?v=XZqLoxpbUSA

Here is photos. i hope, you find what you want

https://ibb.co/3Nc72LG
https://ibb.co/NZpGbPm
https://ibb.co/Sf2bnL6
https://ibb.co/ygg1jWq
https://ibb.co/0sRmXKy
https://ibb.co/vqRcg8P

 

[io2345]

@io2345 how are you doing? It has been a long time since we last talked.
I may have found a solution for the bootloop of the Viper ROM ported by @Mik-el.
Can you test this method, please?

Yurim, I'll try my best to get it done the next weeks. Currently time is a rare factor...
As far as I know, the device of Mik-el is working now (more or less). So it might be a good idea to let him try this method himself.

 

[io2345]

Found the time today and tried the method via fastboot. Sadly to say, it doesn't change anything. Phone keeps bootlooping.

 

[Mik-el]

@io2345 @giotogo
I'm chatting with @blacklisted.rock on telegram. He said he'll send me a better porting guide.
Me and @YuriRM have already chosen a new and better rom to use as port rom.
The failed installation/ updater-binary errors were already solved in my last viperOS port.
Hopefully this time we'll get a booting Android 7 rom.
Regards

 

[Mik-el]

@io2345 @giotogo
I'm chatting with @blacklisted.rock on telegram. He said he'll send me a better porting guide.
Me and @YuriRM have already chosen a new and better rom to use as port rom.
The failed installation/ updater-binary errors were already solved in my last viperOS port.
Hopefully this time we'll get a booting Android 7 rom.
Regards

 

[Hunter_07]

If you still have takee 1....am ready to buy

 

[giotogo]

If you still have takee 1....am ready to buy

why you need this damned phone?

 

[Hunter_07]

Coz i am collecting all the phones which i used frm my childhood and no other logical reason to search for this damned phone

 

[snapss]

Hi everyone, I am also the owner of takee1.
I haven't used it for a long time, but when I saw that someone was doing something to bring it back to life, it gave me hope.
I would be interested in updating it with a more current rom, since 4.2 is no longer compatible with anything!
I hope it will be possible soon.
These Chinese continually churn out new models, but never firmware updates!....shamefull!