yashsingh1/xdaforums huggingface dataset:
[Android Software Development] YuriRM:
Recruitment of testers for Alpha version

Congratulations to all members of the development team of Android 7.1.2 (Ridon ROM) and TWRP 3.1.1.0 recovery for EStar Takee 1.

This is a landmark in the history of this remarkable Holographic 3D smartphone!

Recruitment of testers for this Alpha version is of paramount importance.

[MENTION=7386826]giotogo[/MENTION], [MENTION=7185693]snapss[/MENTION], [MENTION=8807728]Talwarmirza[/MENTION] are you ready to take action and give feedback to our development team, please?

Bugs need to be fixed before announcement at main threads of EStar Takee 1 at XDA and 4PDA.

One must ensure that this ROM and recovery do not descend into oblivion, for lack of awareness by owners of this device.

In order to sustain the valiant effort of [MENTION=5128870]Mik-el[/MENTION], a strategy for reaching all owners of EStar Takee 1 is needed.

My suggestion is to update regularly the TWRP recovery and include it in the Official TWRP App, available at the Google Play Store.

1- Let's bring our version to the latest TWRP 3.4.0-0 (24th June 2020)

2- Let's comply with requirements for inclusion in the official distribution of TWRP

3- TWRP Maintainer should be [MENTION=5128870]Mik-el[/MENTION], at this moment in time

4- A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM"

TeamWin - TWRP

https://twrp.me/

Any more suggestions are welcome.

NOTE - I will give a reward of 20 euro to [MENTION=5128870]Mik-el[/MENTION], after receiving bug reports by alpha testers.
[Android Software Development] Mik-el:
[MENTION=7147494]YuriRM[/MENTION] many thanks for your reward!

I sent the custom ROM to [MENTION=6026343]io2345[/MENTION] , he's already helping me finding bugs and troubleshooting everything.

The ROM is not an Alpha, it's already a Beta!!

Maybe even better: it's already good for daily use!

According to io2345 the rom is fanstastic! It's fast, stable and the battery life is very good.

The only 2 bugs found are:

1) Bluetooth bugged (but I'm going to fix it)

2) Frontal camera and main camera work! They require a warm reboot to be "unlocked" but I think I just got an idea to solve this bug too.

Obliviously io2345's reviews are very accurate (as you know), he'll post more when I'll release the rom.

As you can see my Rom is just born and at this stage is already suitable for daily use! Did you remember when you suggested me to port Android 6 first? I'm glad I went to straight to the next release... now we have Android 7.1.2 and it works better than Vladjocker's ROM!

I won't post the Rom download these days: I want to keep fixing some things and remove any dependency that remind to other Chinese devices. I asked our friend io2345 to keep helping me testing betas without sharing them.

But don't worry, when the first good release is ready to the internet I'll post everything here and the whole takee 1 community will be informed with a tag or a quote on xda. (you'll get a notification from my telegram channel too).

Regards,

Mik-el
[Android Software Development] giotogo:
hi, i am here and my takee is alive. :D were i can download the rom to test?

i downloaded TWRP, but, can not unzip.

https://ibb.co/mb9fK8k
[Android Software Development] io2345:
Tried to redownload and unpack, works for me. You'll have to rename parts to <any_name>.001 and <any_name>.002 (as already stated above) and open it in 7-zip.

Giotogo, do you have an upload space? Then I can send you the latest TWRP-Version (has some improvements, e.g. USB-OTG support).

As for the ROM: You'll have to wait for Mikel's official release. He is still working on it, but has to complete university exams these days, which - of course - is of higher priority.
[Android Software Development] giotogo:
The same problem, can not extract. error and 99%... send if you can. ok, i will wait. :o
[Android Software Development] io2345:
Here is the latest TWRP-version in WinRAR-Format.

Update: Files deleted, see Mikels Upload further down here
[Android Software Development] giotogo:
thank you, installed. :)
[Android Software Development] Mik-el:
Guys sorry for my absence. I didn't even read the new replies under this thread.

I had to pause development to concentrate on my exams. (the best news is that they went good!!), anyway I'm back.

These days I'll upload screenshots, files and news.
[Android Software Development] giotogo:
Congratulations on completing the exams and good luck... :):):):)
[Android Software Development] Mik-el:
Ok I had to spent 2 days fixing my takee.

Last time I flashed a working ROM on this device I used the stock ROM exported by s7yler (I didn't know it was bugged at the time).

That ROM probably corrupted my recovery and is probably causing problems when charging the device too.

So I've spent these 2 days doing a lot of research and trying to flash the recovery:

---with spflashtool

(error 4001, USB connection interrupts when flashing or doing a readback, the problem could come from my 2 USB cables since they're not perfect but maybe no, since the same cable allowed me to do a full and big backup with mtkdroidtools).

Anyway Unsuccessful.

---with the official twrp app

(no error displayed in app and nothing changed).

Unsuccessfull.

---from fastboot ("partition recovery does not support flashing" error)...

Unsuccessful.

But at the end of the day I resulted to flash a working recovery with Mobile Uncle Tools App!! :victory:

New updates tomorrow!
[Android Software Development] giotogo:
In my case, I had a broken USB. I wanted to go back to the original program and mix things up. Then I unplugged the phone, restored the two disconnected USB information contacts, and while recording only this version of SP_Flash_Tool_v5.1352 worked and recorded the program. In all other cases it indicated a USB cable problem
[Android Software Development] Mik-el:
Thank you for the info.

I'm using the last version of sp flash tool v5.1924, I'll try this old version :good:

What do you mean with "restored the two disconnected USB information contacts"?

I have 2 Takees, I bought a new battery since the old ones were unusable, but then I discovered that one Takee has damaged usb port for sure.

The other has working usb port I get error 4001 on sp flash tool (lost usb connection).

The 2 usb cables I have here (xiaomi) work good, but sometimes disconnect, anyway if you put attention they don't disconnect.

(I had a perfect Dell cable but probably someone stole it to me).

****************************

Anyway the Takee with working port has a strange behavior too:

1) In general I don't know why when I plug in the cable the phone wait a few seconds, then it always shows the image with the thunder on the battery (like when is fully discharged) and after a second shows the correct battery percentage. :confused:

Maybe I get error 4001 because the phone is not fast enough to start charging and spflash tool does not detect it...

2) If turned ON and connected to the pc everything is ok, but

3) If turned OFF and plugged to the pc the red led doesn't turn on and it seems it does not recharge. :confused:

Then if I disconnect and reconnect the battery in this state the red led turns on and it starts charging normally. :confused:
[Android Software Development] giotogo:
What do you mean with "restored the two disconnected USB information contacts"? ------> I replaced the USB port and it was charging alone after that. There was no reaction when connected to the computer.

Mine was no longer charging, so I added this little charger board from which I got the + contact and plugged it directly into the battery contact https://photos.app.goo.gl/4yR688RusRsd2BYt6

In short, the phone is hemorrhoids ---- :D:D:D:D:D:D:D:D
[Android Software Development] Mik-el:
OK, I want to reupload the TWRP as a single files using the official Download section.

I don't have limitations for the file size, moreover some of you had problems repacking the 2 splitted parts premiered by my friend and tester [MENTION=6026343]io2345[/MENTION]

Anyway I'm very happy, it seems that 34 users has already downloaded the splitted twrp, but... where are you?? (maybe you are not subscribed to xda)

Anyway when I try to upload

anything

in the Download section I get this error (both on Opera and Chrome!)

there was an error processing the file on the server: filesystem error

I'll try tomorrow... if it keeps to doesn't work I'll contact the forum admin.
[Android Software Development] io2345:
OMG. Sometimes you just can't believe what you see :eek: you are even worse than me, mate . :highfive:

:cowboy:
[Android Software Development] Mik-el:
TWRP 3.1.1-0 for Takee 1 + Download

Here we go guys!

Here's to you the download for the new TWRP 3.1.1-0 for Takee 1 !

With my updated TWRP recovery is now possible to install Android 7 and above on Takee 1 !

The last recovery we got was developed in 2016 ( by @luckasfb) and it was not enough anymore for our needs, we could just install Android 6 ROMs or older...:crying: but with my new recovery a new era of updated custom ROMs awaits to be tested on Takee1!... Starting from the amazing Mik-el Android 7 ROM !!!

Stay tuned! :D

Advantages:

The previous downloads provided by @io2345 are splitted in 2 parts and are not recommended anymore

I have access to Developer Tools so I uploaded the file in the official Downloads section of this thread (not possible at the moment since XDA is switching to new technologies. will be solved after the switch)

I added SHA-1 and MD5 keys so you can check the integrity of the file before flashing it (you can use an easy software like this, really easy)

Downloads:

In this post! Scroll down.

Integrity Infos:

Name: TWRP_3110_Takee_by_Mik-el
Date: 10/08/2020
Size: 9 MB (10,211,328 bytes)
--------
SHA-1: 8d2f012da8500efe68d17d57b7118af68e12a748
MD5: cd4f0a512fdfab834937bd93cec28fbb
CRC32: 7256ec74

Installation Instructions:

You can flash this custom recovery in 4 ways (choose one):

using the official TWRP app (requires root)

using Mobile Uncle Tools app (requires root)

flashing it from the old twrp in case you previously flashed it

flashing it from SP flash tool on Windows (for advanced users)

To boot into recovery:

turn off your phone

connect the charger to the phone

long press Power Button + Volume Up button until the Takee 1 logo on screen moves a millimeter

(this is the only way to do that!)

New version:

New recovery version will include otg support too and will be uploaded tomorrow.

Credits:

Mik-el

a special thanks to @io2345 for testing and for applying my instructions :highfive: ;)

@Augustoandro for his twrp porting guide

@teja.k for his twrp used as base
[Android Software Development] mozzafar alali:
Thank you ?
[Android Software Development] Mik-el:
Updated Twrp 3.1.1-0 with OTG support

This is a new update for the TWRP recovery I worked on!

Do you know that I made a new TWRP recovery for Takee 1? Read my previous post if you didn't.

This time I added OTG support! This brings new advantages to the 3.1.1-0 recovery!

New Features:

you can flash files, save and restore your backups on USB pendrives using an OTG cable. Useful for devices with damaged micro-sd reader.

you can use a usb keyboard or even a usb mouse through OTG. Useful for devices with broken screen.

the size of the recovery remains unaltered: (9 MB)

Downloads:

It's in this post! Scroll down

Integrity Infos:

Name: TWRP_3110_Takee_otg_by_Mik-el.img
Date: 29/07/2020
Size: 9 MB (10,211,328 bytes)
--------
SHA-1: 684ed1a411fd67d2e1cebc7d64632bbcd6d5018f
MD5: b69d3cae06ba5bbc0c17da250423a306
CRC32: ae6ab0b3

Installation Instructions:

You can flash this custom recovery in 4 ways (choose one):

using the official TWRP app (requires root)

using Mobile Uncle Tools app (requires root)

flashing it from the old twrp in case you previously flashed it

flashing it from SP flash tool on Windows (for advanced users)

To boot into recovery:

turn off your phone

connect the charger to the phone

long press Power Button + Volume Up button until the Takee 1 logo on screen moves a millimeter

(this is the only way to do that!)

Credits:

Mik-el

a special thanks to @io2345 for testing and for applying my instructions :highfive: ;)

@Augustoandro for his twrp porting guide

@teja.k for his twrp used as base

Little preview: in the next days I'll post new material about Mik-el Android 7 for Takee 1!!!
[Android Software Development] giotogo:
You are doing resuscitation, artificial respiration, adrenaline on this phone :D :D :D

---------- Post added at 01:36 PM ---------- Previous post was at 01:34 PM ----------

What do we do when you have no other choice, I have to improvise :D:D:D:D:D:D:D
[Android Software Development] Mik-el:
Development process slowed down again for the battery... On 4pda forum a user said that probably the batteries sold on AliExpress come from a defective or old... that guy has a problem like mine (phone discharges heavily). Unfortunately that seller is the only one that still sells batteries for Takee 1!

If needed I'll buy a Zopo battery and I'll ladapt it for my takee (another Italian user has done this).

Anyway the improvements of these ROMs in these days were:

---boot time reduced and smoother experience

---some new apps

---removed text from Micromax and RidonOS

---now I'm facing problem when customizing framework-res.apk, I made a new version that is ready and I'll test it when the phone would allow me to do it.

I'm trying to involve Russian users from 4pda but the Takee 1 thread has been closed for lack of activity (last posts were just some of mine XD). Now I can leave a reply but I need to contact a moderator, but I don't find the option... If you're Russian or you speak it you can help me
[Android Software Development] seraser:
[MENTION=5128870]Mik-el[/MENTION], Im trying to Port for coolpad 9976A Nougat, twrp 3.4.0-0 ported fine, cant get speaker sound(two) porting from Lenovo s939, please, link for porting guide is gone, can you post instructions of this guide?

Thank you.
[Android Software Development] Mik-el:
Rom Updates

ROM Updates:

Last week [MENTION=6026343]io2345[/MENTION] applied some instructions I gave him to allow the customisation of the rom.

I added the fix to the rom, unfortunately the test is not immediate since the last rom I tested gave me bootloop (can't boot to recovery) and I STILL get error 4001 from SP flash tool on Windows.

I'm using the Takee with working usb port and I finally found again my PERFECT usb dell cable I tought I lost, so it's not my fault. The 4001 error seems to come from the preloader driver, I completely unistalled any driver with "usbdeview" and then reinstalled them from many sources, both automatically (.exe) and manually (.inf). I also disabled the driver signature protection obliviously. Windows 8.1 seems much more unsupported in terms of drivers and it has the same annoying driver signature protection of Win10. My idea is to reinstall Windows 7 instead of 8.1 to see if I the preloader driver works better allowing me to use SP falsh tool without error 4001.

If the new rom with the customisation fix doesn't cause bootloop I'll upload it.

Meanwhile I could upload some screenshots form the old, non-customized version in case you don't believe in the existence of the rom :D

P.S. Yes I could use my second Takee to flash the new rom right now, but I decided to let that phone untouched, it currently has the unrooted september2015 firmware with perfect 3D and I want to have it super-ready to use, to test and debug 3D apps correctly before adding them to the new custom rom.

I'll let you know if I fix the 4001 eror on Windows 7 guys, regards!

I'm glad to help you. Let's try to keep this thread Takee 1 focused, you can contact me on Telegram or any other platform for now :)
[Android Software Development] Mik-el:
Has anyone here ever faced a 5054 error in SP flash tool?

Has anyone here ever faced a 5054 error in SP flash tool?

After days of work me and [MENTION=6026343]io2345[/MENTION] discovered that my computer and my Takee does not have connection problem (error 4001), insted I tried an older SP flash tool version and I saw that the actual error seems 5054.

At least now I know my drivers are set perfectly.

Do you know how to solve error 5054 quickly?
[Android Software Development] giotogo:
Did you tried SP flash tool old versions?
[Android Software Development] Mik-el:
Users, do you have a working preloader?

Yes as I said I get

---error 4001 with new sp flash tool v5.1924

---error 5054 with old sp flash tool v5.1436, I resulted to flash sempteber stock rom in "format all+ download" mode without preloader but now the phone seems dead and I keep getting those errors.

Has anyone here ever flashed preloader on their Takee 1?

Do you have a preloader I can trust? Stock Rom backups does not include preloaders unfortunately...
[Android Software Development] giotogo:
older versions, try v5.1352 versions. this worked for me. i returned to stock rom.
[Android Software Development] Mik-el:
Thanks giotogo, some questions for you:

1)which is the last rom you flashed with sp flash tool on your takee?

2)which rom is currently installed?

3)do you know how to do a full readback on sp flash tool and then use the "prepare block feature" of MTK droid tools? I have my own old backup but the powerful SP flash tool v3 refuses to load my "preloader_and_dsp.bin" file, maybe you can get a "preloader.bin" file.

Before starting let me know if you want to collaborate, since I should give some other little tricks to ensure everything is right.
[Android Software Development] giotogo:
I upload it to Yanedx Cloud. Here is a link https://yadi.sk/d/YWDoPZGW4jXObg

For now, I gave my Takee to my nephew temporarily.

"prepare block feature ---> I have no idea what you are talking about :D
[Android Software Development] Mik-el:
Thank you giotogo, I haven't download it, but from the name it seems the rom we already have (a backup made by Pogodancer). Unfortunately this rom doesn't not include "preloader.bin" and "dsp.bin", that's why I was asking for a new backup
[Android Software Development] giotogo:
here is official rom https://www.needrom.com/download/estar-takee-1/comment-page-2/ but it needs premium account. maybe someone has?
[Android Software Development] Mik-el:
Takee 1 Fixed!

I finally fixed my Takee 1 ! :D

That hardbrick was terrible but it didn't stop us!

Soon, nice news!

And here's the first screenshot.
[Android Software Development] giotogo:
sorry, my Takee touch screen is dead. :( my nephew killed it
[Android Software Development] YuriRM:
Are you going to repair your Takee 1?

You are an amazing DIY person!
[Android Software Development] Mockingbird83:
Hey guys a quick question about the battery, my battery died and finding a new one is really difficult is there a battery from another phone that will fit Takee1?

I find the new battery only on Aliexpress but it takes forever to arrive if it will arrive so I am asking if anyone has an idea if the phone is compatible with other batteries

Thanks :)
[Android Software Development] YuriRM:
[MENTION=1956074]F1_Freak[/MENTION] wrote this on 28th January 2016

"genuine" battery replacement is also impossible to get hold of, but if anyone needs instructions on how to bodge a Nexus 5 battery into it, with better lifespan, give me a shout)

https://xdaforums.com/showpost.php?p=65032789&postcount=656

Check also posts on 4PDA because they made several attempts at fitting new batteries on Takee 1.

[MENTION=7386826]giotogo[/MENTION] has some clever tricks up his sleeve for solving battery problems too.
[Android Software Development] giotogo:
how? i can not find touch screen or LCD. even not on aliexpress. :(:(:(
[Android Software Development] io2345:
Last logon for F1_Freak was more than three years ago. Nevertheless I sent him a private message. Let's see.

My battery is still working fine, but if you have a rotten battery, don't throw it away, keep at least the upper bar with the contacts. I guess it's just a question of unpacking the cell itself and connecting it to the bar. Did that before with other electronics, there's no "magic" necessary to do it. Charging circuits are usually integrated in phone's hardware, at max. there might a circuit for protection against wrong polarity, over-temperature and/or over-current.

Original battery has this sizes:

height 83mm

width 60mm

thickness 4,4mm

3,8V 2500mAh

For Nexus 5 I found this on the net: 59 x 54 x 5 mm. Same voltage, smaller and just a little thicker than the original battery.

I also found a battery for ZTE Blade L3 with size 78 x 54 x 4 mm, 3,8V 2100mAh. (In fact, all Li-Ion or Li-Polymer 3,8V batterys with a size equal or smaller than the original one will probably fit)
[Android Software Development] io2345:
What about these:

https://de.aliexpress.com/item/3259...earchweb0_0,searchweb201602_,searchweb201603_

https://de.aliexpress.com/item/3283...earchweb0_0,searchweb201602_,searchweb201603_

Or even complete assy (less work for you):

https://de.aliexpress.com/item/1005...earchweb0_0,searchweb201602_,searchweb201603_
[Android Software Development] giotogo:
---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------

[/COLOR]

thank you... But expensive for me for this phone. :(:(:(:(:(:(:(:(:(:( The dollar exchange rate is 1: 3 in Georgia
[Android Software Development] io2345:
Any screenshots of the new ROM available yet?

EDIT: Found it in Post #56 of this thread
[Android Software Development] Mik-el:
@YuriRM @Talwarmirza It seems that the XDA mail didn't reach you. Did you test the ROM? @io2345 has already tested it ! 😁

io2345, you told me by mail that you faced some bugs, can you copy the message here, so I can give information to other users too? Thank you
[Android Software Development] io2345:
Here we go:

Until now I didn't manage to do a satisfying install - might be my fault, not too sure. Here's what I did so far, maybe you have any idea:

(1) Started off with dirty flash of 1.1 over 1.0 (wiping only cache, dalvik and system). Camera not working, not even after half an hour. Wondered about size of "System" in "Storage". Is 25,17GB normal? Couldn't install App "Osmand+" from F-Droid-Store, gave me an error. Good responsiveness of system, though.

(2) Next followed a fresh install of 1.1, directly after I manually formatted Cache, Dalvik, System and Data. No developer options available. Hitting 7 times build number didn't do the trick. When using App shortcut "Developer Options" I get "Not available for this user". Couldn't get to home screen with middle "button". Vibrates, but display doesn't change. Phone doesn't lock, not even when pressing Power.

(3) Went back to Version 1.0, everything worked fine like before. System-size in "Storage" is here the same: 25,17 GB

(4) Next a normal "factory reset" and then installed Mik-el Android 1.1 together with Open Gapps 7.1 Nano. No wipe Dalvik afterwards. After reboot error message "Music terminated". Google setup assistant terminated as well, using option "restart app" gave me a working assistant. Assistant stays showing "searching for updates" after entering connection data for WiFi. Terminated after 20 minutes or so, did a restart. Same as before, "searching for updates, in a few minutes everything will be ready". Rebooted again after a couple of minutes, went to TWRP and wiped Dalvik + Cache, rebooted. Assistant starts, connects, searches for updates and stays there for about ten minutes, then phone reboots automatically. Factory reset, reboot. Same as before. Reboots after 10 minutes or so.

(5) Wiped Dalvik, Cache, Data, System, rebooted to Recovery, reinstalled Mik-el Android 1.1 without GApps. No wipe afterwards, going directly to "Reboot system". Same as in (2).

In all versions Bluetooth isn't working (we know that), so you'll get a permanent pop-up about that until you click on "don't inform me until next reboot"