Hi all,
I want to port cm13 to our device (at least I'll give it a try) but i don't know if i can use cm12.1 files to port cm13. And can i compress .ext4 files to
.dat in Windows?
Anyway the rom i wt to use is Redmi 1s cm13
Redmi 1s have the same chipset as s3 neo http://forum.xda-developers.com/redmi-1s/orig-development/cyanogenmod-13-0-t3265044
ziad311 said:
Anyway the rom i wt to use is Redmi 1s cm13
Redmi 1s have the same chipset as s3 neo http://forum.xda-developers.com/redmi-1s/orig-development/cyanogenmod-13-0-t3265044
Click to expand...
Click to collapse
It would be better to use source as it's give with the rom; you could copy some from cm12.1 (of s3 neo) and some from cm13 (of redmi 1s). It's very difficult that poting works (none of mine booted ), expecially with different versions. To have sucess you will have to replace a lot of files and it can still not work. Sorry but I don't think it will work; anyway good luck!
For extracting lollipop files.
If you search there's a guide that explain how to use dat2img.exe but then you need to mount it as a loopback device and windows can't do that. I succesfully extracted it with sdat2img.exe with this syntax: sdat2img system.transfer.list system.new.dat system.img and then accessed system.img with and then ext2explore and ext4 unpack; however then you haven't got any way to recompress it.
It'll not work. You need to build rom from source, becouse M have many changes in kernel (Selinux is good example) and LP kernel won't boot M.
Device and Project Presentation
In 2015 the Chinese company EStar launches on the market the Takee 1. An octa-core 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 years 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
https://imgur.com/Be7YKsg
Other screenshots
https://imgur.com/a/RRyUNL7
Youtube video
The last ROM is v. 3.0
Everything works except the Cameras. 3D partially works.
Changelog (click to show history of working/not working components)
v2.0
Magisk improvements
v1.2
Bluetooth Now Working
Full Holographic 3D and AirTouch support - in Development
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!
v1.0
First release that can boot, no need to download it.
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 an Open Source alternative to Youtube
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!
First step to port the Bit Cauldron 3D Audio Technology included in the Takee stock Rom: Removed loudsound patch to avoid possible future conflicts
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 2021-10-16
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 included in the previous links.
Rom Download
Free Download, Virus Free (just use "slow download")
v 1.1-------------> here
v 1.2-------------> here
v 2.0-------------> here (10th March 2021)
v 2.0.1 Bundle*---> here (9th April 2021)
v 3.0 (3D) and Bundle*--->here (16th October 2021)
* = Bundle includes= ROM + Optional Stuff among: Google Apps, SuperSU root and Magisk!
Google Apps
Google Apps 2021. Most lightweight version possible. We love privacy, so they're optional.
I made a flashable .zip to install them from TWRP recovery but it seems not working for me, you can test it and let me know.
Magisk or Root? What do you want?
I want Magisk = Rom 2.0.1 is pre-patched for Magisk (boot.img). After booting the ROM just install the Magisk Canary apk. (Apk included in the 2.0.1 bundle you have just downloaded).
I want Root =before installing the 2.0.1 ROM, take the "boot_unrooted.img" file inside the 2.0.1 Bundle you just downloaded. rename this file in "boot.img" and replace it inside the .zip file of the ROM. Now you can flash the ROM and then flash SuperSU through recovery
Rom Integrity Infos
Code:
Name: Mik-el_Android_for_Takee_v1.1.zip
Date: 27/12/2020
Size: 602 MB (631,352,946 bytes)
--------
SHA-1: 260999abe54d3ae473272a4002cc9cef2ea93e60
MD5: c2fb20469f11a2f6c16c0479a8c157f6
CRC32: 8436c496
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:
Backup 3D calibration files or you'll lose the 3D effect forever. Internal and External storage -> "Android" folder -> "HolographyProfile" file and "matrix" file. To know more about 3D calibration, read this! Also, backup your important data, as always;
Boot your Stock Rom and check if you still have these (or other) Air Touch games in your phone storage.
Fruit Ninja (it looks like this)
Sector Strike (it looks like this)
This game (it looks like this)
This other game (it looks like this)
Shadow Snake (it looks like this)
Tunnel Trouble (it looks like this)
If the answer is YES, go to step 3. Otherwise, go to step 4.
Spoiler: YES, I still have Air Touch Games
These Air Touch games can't be downloaded anymore! The Takee 1 3D store is offline! Now you can help the Takee community preserving these games for the future. You just need 1 minute. Download the ApkExtractor app (2.4 MB), save the games on your external SD card and upload them somewhere on the web! Then, you can flash the new Rom.
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
Download my Rom, it's a .zip file;
Copy the Rom file on your MicroSD;
Once you have installed the recovery you can boot into it;
"Wipe" -> "Swipe to Factory Reset";
"Install" -> select the .zip file for the Rom -> "Swipe to flash"
"Reboot" -> "System"
A tip to Improve Rom Performance
Use the Rom for a few minutes and see how it performs. After that, open the fstrim app included in the Rom and use it to trim the internal storage of you device. This will be the first trim you'll phone has received in 6 years, since 2015 ! It took me 3 trims in a row to fully trim my /data partition. Now see how much more responsive the phone has become!
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
Go to developer options
Activate "extended reboot menu"
When you want to use the camera:
Long press power button and select "reboot" - you will be asked, which type of reboot you want to do
Select "warm reboot"
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
whatever 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 euros for the development
for exchanging almost 150 mails with me to bring this project to life!
@YuriRM
for having collected information and having made a detailed list of Hardware 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 euros for generic 3D development
other members of the Takee 1 community (@giotogo, @Talwarmirza, @snapss , @Hunter_07)
an unknown artist for the Mik-el Android wallpaper
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
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.
interesting. this phone is still good.....
Anyone with ViperOS development experience?
io2345 said:
Anyone with ViperOS development experience?
Click to expand...
Click to collapse
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)
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
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
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
How to fix a bootloop after installing a Custom ROM like Viper OS
io2345 said:
Anyone with ViperOS development experience?
Click to expand...
Click to collapse
@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
YuriRM said:
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
Click to expand...
Click to collapse
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
YuriRM said:
@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.
Click to expand...
Click to collapse
Found the time today and tried the method via fastboot. Sadly to say, it doesn't change anything. Phone keeps bootlooping.
@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
@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
{Mod edit: Quoted post has been deleted}
why you need this damned phone?
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!
June 2020 Updates: Rom ported! Now we need a recovery!
June 2020 Updates: Rom ported! Now we need a recovery!
Guys, I've really faced a lot of problems when trying to port this rom:
1) I had to wait 5 months to receive a working battery from China, thank you Corona Virus...
2) university... XD
3) porting guides on the web suck, I had to contact many people and study many articles and video guides... until I had to make my own porting guide...
4) some tools to extract boot.img files extract .img files, but with a wrong structure!! (and I discovered this just recently!)
5) I had to change the port rom, now I'm not using a ViperOS rom, but a RidonOS rom from a Micromax device much more similar to Takee 1 (more than 90%of the hardware is identical)
6) I want to thank you @io2345 for helping me to test over 10 roms!! We had to exchange almost 100 mails to bring you a new and updated Rom!!
Anyway after all this FREE effort I think that I finally got a working Rom !! (correctly ported!!)
But we dhave another problem now...
We discovered that the custom recovery we use on Takee 1 (twrp 2.8.0.0. developed by @luckasfb ) is too old to support Android 7! We need a new custom recovery, probably a twrp 3.0 or above.
I've already researched new material and guides on the web. I found a guide that seems to clearly explain how to port a custom recovery to any device.
The process is simple, it consist in the extraction of the recovery from an Android kitchen in Linux, the rest is about replacing files.
Is this the end, or not?
Anyway the process is long and boring...
I'm quite busy with exams, life a few other projects...
I don't know if continuing this project is convenient for me at this point...
If someone wants to help me and @io2345 please leave a message hereunder, I'll leave you links and infos about the recovery porting.
Cheers!
A reward of 20 euro is awaiting your delivery of a fully working Android 7 ROM + custom recovery.
I expect @io2345 to reward you as well:
Regarding TWRP-3.1 custom recoveries for EStar Takee 1, I did some porting attemps from 5-19 November 2017.
https://forum.xda-developers.com/showpost.php?p=74410087&postcount=1201
https://forum.xda-developers.com/showpost.php?p=74434705&postcount=1202
https://forum.xda-developers.com/showpost.php?p=74482513&postcount=1203
https://forum.xda-developers.com/showpost.php?p=74488944&postcount=1205
https://forum.xda-developers.com/showpost.php?p=74540282&postcount=1206
https://forum.xda-developers.com/showpost.php?p=74564282&postcount=1207
TWRP for BQ Aquaris E5FHD
https://twrp.me/bq/bqaquarise5fhd.html
Current version
twrp-3.4.0-0-vegetafhd.img
Hello every1,
Need some info on building latest(Android 11) AOSP rom for my phone.
First, how do i know if my phone is A or A/B partition type(and isn't that dtbo) ?
Second, where do i find my boardconfig?
Last, my phone's manufacturer (Mi Redmi 4A - codename rolex) has put the kernel source on github how do i make aosp rom with that?
chraso said:
Hello every1,
Need some info on building latest(Android 11) AOSP rom for my phone.
First, how do i know if my phone is A or A/B partition type(and isn't that dtbo) ?
Second, where do i find my boardconfig?
Last, my phone's manufacturer (Mi Redmi 4A - codename rolex) has put the kernel source on github how do i make aosp rom with that?
Click to expand...
Click to collapse
Well, kernel source is not even nearly all needed. You have to create more files including the BoardConfig. For A or AB please google