yashsingh1/xdaforums huggingface dataset:
[Android Software Development] io2345:
Mikel, first just to inform you, that there is no order /apps in /system (it's name is /app), as well as there is no file core-o.jar in /framework (it's name is core-oj.jar). I guess those are the ones you meant, right?

I did the deleting/replacing of files as told, zipped all and installed without problems, but the result is the same: "out of space" error when trying to install apps.
[Android Software Development] zdomjus:
Hi, same problem here. Tried to make space deleting some apps using adb, no result.It seems that something is wrong with internal memory addressing or management, the applications' footprint is abnormally reported as few bytes, surely uncorrect. 'Out of space' is shown if I try to install any new apps.
[Android Software Development] Mik-el:
PORTED ROM:

Thank you for the feedback!

I hope you liked everything else anyway! :)

Yes, sorry for my errors, haste... yes it's system/app and core-oj.jar

Basically one of those apk or files that changed from 1.0 to 1.1 is causing the "out of space problem", and we can't figure out how this could be possible since the most important files (fstab file for partition layout and zimage and bootimage files for kernel) are the same !!:mad::mad:

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

COMPILED ROM:

Yes, we're adating both the EQ kernel and the Micromax a311 kernel, since the hardware it's almost identical too and the rom I ported from Micromax works great except for the storage bug!

Mediatek does not supply kernel for each device like snapdragon does, that's why adapting and building a kernel is harder and it requires more testing and debugging.

Usually malware is in the apps, so Android code, not kernel. Anyway the developer that is working with me knows more than me and we'll consider that too.

Many thanks for the files, io2345, as always.
[Android Software Development] Mik-el:
Many thanks to you @zdomjus !!

I'm really happy and satisfied to hear that!! :D:D

io2345 helped me with the twrp too!
[Android Software Development] YuriRM:
luckasfb

Senior Member

Jul 11, 2016 at 9:54 PM

#791

I localized the problem with starting the ROM :) Its **** may be from chineze security servise :(

They include in ROM's "lovelyfonst.apk", "fontshelper.apk" with trojan functions (collect all passw, logins, card number to base and push it to China.

Yesterday I regect to include this APK-s and lib's in ROM, but I din'n know what the functions of this trojans included im mach java-sources of android platform. And this functions "very need" the trojan lib - libFONTS.so :D

I spent about 3 hours for disable all functions for "lovelyfonts" in the sources.

I sent the lib to tester and he include it to ROM for testing. ROM start normally. I start to build second revision of ROM without trojan functions.

I'm worried about users with Zopo ZP998 (where same ROM worked as stock....)

https://xdaforums.com/t/takee-1-ful...with-play-store.3202829/page-40#post-67702646

luckasfb

Senior Member

Oct 19, 2016 at 8:42 PM

#912

So Chinese trojans deleted allready. I promise 3D will be worked fine or partially in my next release of KK 4.4.2 ROM.

https://xdaforums.com/t/takee-1-ful...with-play-store.3202829/page-46#post-69209851

luckasfb

Senior Member

Oct 19, 2016 at 9:52 PM

#914

Unfortunately, to identify the spy code in the full firmware Chinese smartphone is quite difficult. In this case, I have analyzed the text strings of binary files "lovelyfonts" applications, and having a similar smartphone firmware source code removed all strings that was used to call and run this application. Only later in the topic on a similar smartphone firmware I discovered suspicions of other users on the acts of espionage that application.

---------- Post added at 23:52 ---------- Previous post was at 22:58 ----------

I think 3D didn't work, becouse in CM/AOSP not had code, apps and libs for naked eye 3D.

https://xdaforums.com/t/takee-1-ful...with-play-store.3202829/page-46#post-69210073
[Android Software Development] Mik-el:
Mik-el Android 2.0 for Takee 1 just released!

What's new:

➡solved the "out of space" bug, now you can install every app

➡added Bluetooth fix to the Rom (no need to install it separately)

➡added Google Apps 2021. Most lightweight version possible

➡added more permissions to some system apps

➡️removed root. I still have to fully disable it, so you can use new Banking Apps, the OS must pass all the security checks.

➡I hope that the "usb debugging" by default is now off and that "developer options" work again (test it)

Special thanks and a Big News about this Project:

➡Thanks to dimonikod from 4pda.ru (https://4pda.ru/forum/index.php?showtopic=589200&st=3740)! For having liked the Rom and having published a video showing the installation process!

➡Thanks to someone in Asia who downloaded the Rom making it land in China too!

➡Thanks to a new dev for offering my her help to make a new big step forward: making a new and open source kernel for the EStar Takee 1! 😱😃 (It will be a long trip, so if you want to support us... let us know!)

➡Thanks to @io2345 as always

Link for the Rom Download:

It's in the 2nd post of this thread, as always!

(Download is still external since my uploads on xda fail everytime for some reason.)
[Android Software Development] io2345:
Mikel, tried to install it, but hangs on "Searching for updates" after entering WLAN-Information. If you restart, it will again go until "Searching for updates" again before it automatically reboots. Next boot it went one step further before rebooting, next it finally went on until where you can enter google account. Maybe should have done a factory-reset after installing the ROM?

fstrim didn't work initially, as ROM isn't rooted (although when installing the ROM it says "Installing SuperSU"). I installed Magisk without problems and could use fstrim after that. Magisk won't pass Safetynet-Check though, guess there are some remains of SuperSU still present in bootimage. Maybe you can remove that in one of the next versions. Magisk is way better.
[Android Software Development] Mik-el:
I hope that our biggest problem (out of space) was solved! In that case I'm very happy!

Do the new 2021 google apps work well?

This is veeeery strange, can you send me a screenshot?

Before connecting to wifi try to disable ota updates from settings. If the problem persists use Total Commander to delete/uninstall the one time initializer apk in system/priv-app (it's the ridon os first configuration wizard, maybe it runs in background too?)

A factory reset wipes the data and cache partition and keeps the system partition.

Maybe you're facing errors because some things from the old rom persist in the data partition, so I would suggest you to wipe the data partition, cache and dalvik cache before installing a new rom. (I wrote this in the first or second post if I'm not wrong)

Yes, I saw from the rom files that the installation prints that "installing super su" message and the installation does a thing too, but I didn't remove that thing because I didn't want to generate the "out of space problem" again.

I'm removing that thing and I'm adding magisk to the rom. Send me the apk or the .zip file fro magisk so I can include it in the rom. I'm uploading this v2.1 asap, maybe today! :)

So you can directly test 2.1 without losing time anymore on 2.0.

If the "out of space" problem and the un-root problem are solved, I'll finally add the complete support to 3D and airtouch on Android 7, the material is already organized on my hard disk !!
[Android Software Development] io2345:
Out of space-problem is solved, could install apps!

I always wipe Data+System+Cache+Dalvik before installing a new ROM followed by a reboot into recovery.

Will try the installation again for making screenshots (or photos). Let's see if behaviour changes if I completely skip connecting to wifi.

Will also try the latest Magisk before sending it to you - just to be sure
[Android Software Development] io2345:
Situation is ok when not using WLAN-connecting during setup.

They changed Magisk in the latest versions - MagiskManager is now installed as APK and from there you start the installation of Magisk itself. But you have to select a *.img or *.tar file to patch. Didn't know which file to select there. You can also install the APK as ZIP in recovery, just have to rename extension. Tried that as well, but installation fails (see attached screenshot).

I'll send you an older Magisk version (20.4) which installs from recovery without problems.
[Android Software Development] Mik-el:
Ok thanks, let me know if I should remove the OneTimeInitializerApk too (I don't think so)
[Android Software Development] Mik-el:
@io2345

Done!

I hope we got rid of super su even if I don't think so.

But at least magisk should work out of the box now!

Reuploading the whole rom would be a waste of time, so do this:

1)Rename the magisk zip file you sent me to just "magisk.zip"

2)Make a folder in the root of our rom, call this folder "magisk"

3)copy the "magisk.zip" file inside that "magisk" folder

4)replace the updater-script of the rom with the one attached here.

Sorry but I had to put it in a zip just for xda...

The location of the updater script is META-INF\com\google\android as always! ;)

After having tried this, use this flashable zip to remove superSU in case we didn't succeed!
[Android Software Development] io2345:
Mikel, I tried it. Looks good. Magisk installs, which makes fstrim work "out of the box". One-Time-Initializer also works now with Wifi connected.

SuperSU doesn't install, but traces are still there. I tried the "Update-UnSU-signed" script already some time ago, doesn't change anything. Looking in the information of the UnSU-script it says "Note: To completely remove all traces of the systemless roots, you still need to flash a different, unrooted boot.img, likely the default one that came with the ROM".

Now, which boot.img can that be in our case? One of stock-Takee, or has it to be an A311-boot-image?
[Android Software Development] Mik-el:
Great!

No you can't use a boot.img from a different rom (yes you could use 1.0 and so on, but it would be the same).

You should patch the boot.img of the last ROM.

Just saw that superR kitchen should allow to unroot a ROM.

Let me know :)
[Android Software Development] zdomjus:
@Mik-el @io2345 Kudos to you for your efforts. The latest rom is an absolute masterpiece. Fast, efficient, beautiful. If it has got any minor problem, who cares? My old takee is reborn as new, I have scotch taped an old, but still working, Li-ion battery from a dead LG Optimus One and my Takee runs for( at least) 4-5 hours. Thank you, the estinct dinosaur Takee community must hold you in its hearts forever.
[Android Software Development] YuriRM:
@Mik-el @io2345 albeit slow you have done a magnificent job. Magisk is a wonderful refinement for the ROM. However, a bug-free 3D version and a new battery replacement proposal are of paramount importance to ressurect the extinct Takee community.

It may be feasible to buy 50-100 units of brand new batteries, made-to-order, if we join efforts worldwide with Takee communities at XDA/4PDA/China.
[Android Software Development] Mik-el:
WOW! Many thanks zdomjus!!

I'm very happy that you you find the Rom so powerful :D and "this isn't even my final form" ( :ROFLMAO: ), I still have to add the air touch and holographic 3D on Android 7!

I hope that you liked the YT video too!

Thanks again for your message, it made my day!
[Android Software Development] Mik-el:
OK so @io2345 and I tried to fully unroot the rom with SuperR kitchen and a flashable zip but it didn't work.

These are other ways to fully unroot that you io2345 can use:

On rooted android

open SuperSU app and click on "full unroot"

use Universal Unroot App (I don't know if It can work with magisk)

use total commander to delete the superuseruser.apk (can have a different name and can be installed in "system/app" or "system/priv/app") then delete "system/bin/busybox" and "system/bin/su", if they're not present delete "system/xbin/busybox" and "system/xbin/su"

Since the previous methods doesn't edit the bootimg I think, On linux:

I remember there was an option on dsixda kitchen too, but I could be wrong
[Android Software Development] io2345:
I guess the ROM itself and thus the boot.img isn't pre-rooted, but the SuperSU-part was only flashed at the end of the ROM-installation.

I could now successfully patch an older boot.img (it was part of one of the June 2020 versions) with Magisk 22.0. Installation of this Magisk-Version (it is the latest one) still fails with "unknown image format" error. I asked for help in the Magisk-Support thread, let's wait for a solution. If this version works, we could finally activate "Magisk Hide", which should allow the use of even the critical banking apps.

I have already prepared ROM version 2.0.1 containing all fixes on problems found on 2.0 version. Just waiting to get this Magisk-version implemented.
[Android Software Development] YuriRM:
The principles of privacy that have been a guidance for the development of this custom ROM are enshrined in the teachings of Rob Braxman Tech... the Internet Privacy Guy. They are remarkably efficient!

Rob Braxman Tech

I'm the Internet Privacy Guy. I'm a public interest hacker and technologist. I use my extensive knowledge of cybersecurity and tech to serve the public good. There are enough tech people focused on ...

lbry.tv
[Android Software Development] YuriRM:
Are both cameras working properly?

@Mik-el is an egyptologist!

He discovered the mummy of Lava Iris X8 and to surprise us has glorified it by christening EStar Takee 1 reborn.
[Android Software Development] io2345:
@YuriRM "Are both cameras working properly?"

Basically they do work. As kernel is still the same, they suffer the same problem than the latest Android 6 ROMs: After a full reboot the first start of camera will give you "communication error". You'll have to wait some minutes (let's say 10 minutes) until the selfie-cam is working. As soon as it does, you can do a "warm reboot", then both cameras are working.

Easiest way to do a warm reboot is going to "Developer options" and activate "Advanced restart". If now you press the power button and select "restart" you have several options, one of them is "warm reboot".
[Android Software Development] YuriRM:
@io2345 Thanks for the info on cameras! Are you ready to solve the Magisk bug or is that a task for @Mik-el in a brand new kernel?
[Android Software Development] io2345:
For Magisk things look good. The error seems to have re-occured on an issue that had been already resolved in earlier versions. Hope devs will fix that in new versions again. Moreover, Magisk already does give root-access at the current point. It's just that MagiskHide cannot be activated so far.

Sad thing is, that even when it's fixed, it will probably not allow us to use critical banking-apps. Even the latest ROM-version, that comes unrooted, doesn't get those apps working and it's not because of root (I think), nor because of recovery and I also cannot find critical apps running (like busybox, screenreaders etc.). The Ridon-system-ROM or the kernel must have been tampered with in some way, but I don't know how.

Already asked in the original thread Ridon for A311 ROM-thread, but until now I didn't receive an answer. So, not much sunshine on that side. I'm afraid that can't be fixed until we have an alternative kernel that doesn't depend on any pre-created ROM of other models. But, maybe I'm wrong and it's no big deal. I'm not a developer, just a user like you (probably)
[Android Software Development] YuriRM:
Do banking apps and critical apps (like busybox, screenreaders etc.) run or did run in the Android 6 ROM of VladJocker and the latest Android 4.4 ROM of @luckasfb?

If they did run in the past or still run in the present then the kernel is not the culprit.

Modern day banking apps require Android 6 at least.
[Android Software Development] io2345:
Not as far as I remember. They all were rooted. Would have to change that before installing.
[Android Software Development] io2345:
@YuriRM : Just tried it: 4.4. is pre-rooted, I uninstalled SuperSU and rebooted, installed banking app, but won't run.

Android 6 isn't even prerooted, but nevertheless banking apps deny to start.
[Android Software Development] YuriRM:
Banking apps are an extreme scenario!

What about critical apps (like busybox, screenreaders etc.)? Do they run?

NOTE - luckasfb trimmed the code and disabled some mechanisms to avoid theft of credit card information, usernames and passwords by Trojans, etc.

He may have done something in the kernel too.
[Android Software Development] io2345:
Do you mean "are they running" and thus cause the problems, or do you want to know, if they can be used?
[Android Software Development] YuriRM:
Can they be used?

Better isolate each test. Test one critical app then remove it before moving to the next one.
[Android Software Development] io2345:
BusyBox and Talkback install and run without problems (rooted version)
[Android Software Development] YuriRM:
Great! Now test a banking app that runs on Android 4.4... I found this one:

Caderneta - Apps on Google Play

Your up-to-date Booklet is wherever you are. It's from the Box, you can trust.

play.google.com
[Android Software Development] io2345:
I already have tested 4.4 with s-pushtan (if I remember correctly)
[Android Software Development] YuriRM:
The app from a portuguese bank requires Android 4.4 or above.

Please test it on luckasfb ROM and Mik-el ROM to clear all doubts... if it is not inconvenient to you.

Anyway, the test of critical apps BusyBox and Talkback has shown that the custom kernel of luckasfb is not the culprit. The problem is in the ported ROM of Mik-el.
[Android Software Development] io2345:
I don't agree with you and can't even follow your thoughts. If LuckasFB, VladJocker and Mi-Kel-Rom use the same LuckAs-Kernel, it is very probable that this is the source of the problem.

Did another test with Stock-ROM (just to be sure): Found a banking-app that runs on 4.2 (Apo Tan+). It does open on Takee-Stock-ROM, but not on Android6 version. Installed Caderneta-app there too (just for being curious). It is not that critical, shows some message in portuguese that modifications have been detected, but starts at least. Feel free to test yourself, if it's fully functional.

Same for Mi-kel ROM: Apo Tan+ doesn't start, Caderneta does with warnings.
[Android Software Development] YuriRM:
Can you bring this to our Holographic 3D phone EStar Takee 1 ?

UBports GSI brings Ubuntu Touch to any Project Treble-supported Android device.

UBports GSI brings Ubuntu Touch to any Project Treble-supported Android device

XDA‌ Recognized Developer erfanoabdi has compiled an Ubuntu Touch GSI that can be installed on any Project Treble compliant device.

www.xda-developers.com
[Android Software Development] io2345:
You'll have to ask Mi-kel. But it doesn't sound too promising: Designed for Android 9... "might work on older Android 8.0 and 8.1-based vendor images as well"
[Android Software Development] YuriRM:
Developer Brings Full Project Treble Compatibility to the Xiaomi Redmi Note 4

... originally Android 6.0 (Marshmallow), upgradable to 7.0 (Nougat), MIUI 11

Developer Brings Full Project Treble Compatibility to the Xiaomi Redmi Note 4

A developer on our forum has managed to bring full Project Treble compatibility to the Xiaomi Redmi Note 4, and he's proved it by booting a generic Android 8.1 Oreo. This opens up the door for much easier future custom ROM development, and will be hugely beneficial once Android P comes around.

www.xda-developers.com

Project Treble on the Xiaomi Redmi Note 4

How did he do it? He used the “cust” partition on the device for his make-shift vendor partition. The cust partition normally holds a lot of device-specific stuff from MIUI, so it’s essentially wasted space on an AOSP build. Using the approximately 830MB unused partition, he moved the vendor HALs from system into cust without needing to repartition.

Why can't @Mik-el do the same?
[Android Software Development] YuriRM:
luckasfb ROM

BusyBox and Talkback install and run without problems (rooted version)

Caderneta bankIng app installs and starts

Mik-el ROM

BusyBox and Talkback do not run (rooted version)

Caderneta bankIng app installs and starts

Namespace is a feature missing in @luckasfb kernel.

However, it does not affect the test of BusyBox, Talkback and Caderneta bankIng app.

The test of critical apps BusyBox and Talkback has shown that the custom kernel of luckasfb is not the culprit. The problem is in the ported ROM of Mik-el.

Is this the warning message of Caderneta bankIng app that io2345 talks about?
[Android Software Development] io2345:
@YuriRM : You misunderstood what I tried to point out. In Mik-el ROM (rooted version) BusyBox and Talkback install and run without problems.

Critical banking apps do not run or at least show a warning. This is true for all three ROMs using LuckasFB's Kernel.

The message from Caderneta is:
[Android Software Development] YuriRM:
There are changes to your device's operating system that can compromise the normal functioning of the Caderneta App.

Is there something like a signature on stock kernels? Do all custom kernels trigger this kind of warning or denial of service? Is there something fishy on luckasfb kernel like username and password theft?
[Android Software Development] io2345:
If you mean "Do all custom kernels trigger..." in general: No, they don't. I have an old Samsung running on LineageOS. Banking apps can be used there. With MagiskHide you can even have Root and BankingApp.

Who knows which functions are stripped or implemented in LuckAs's Kernel. Only the creator can tell us.
[Android Software Development] YuriRM:
Is our Takee 1 God approachable?
[Android Software Development] Mik-el:
Mik-el Android 2.0.1 for Takee 1 released!

What's new for this release:

➡️ROM comes unrooted

➡️root and superSU installation are now optional

➡️Magisk 22 installation is now optional

➡️"Magisk hide" doesn't support 3.4.67 kernels so home banking apps will still detect root, as long I don't make a patched kernel

➡️Google apps 2021 (most lightweight version possible) installation is now optional

This will be the last version of the ROM that comes without 3D and AirTouch support. As I already said, I can't guarantee anything for the 3D porting of the next release since if the 3D software is incompatible with Android 7 there's not much one can do...

anyway for the next update, I hope to show you 3D running on Android 7! 😊

Download: in the 2nd post of this thread as always
[Android Software Development] YuriRM:
Congratulations! Show us the features of the new ROM on a video, please.

Some owners may be waiting for the 3D version to flash Mik-el's ROM.
[Android Software Development] sandr2010:
and not on another exchanger (google , mega .......) - 41 days will be downloaded!
[Android Software Development] io2345:
For me it took two hours to download. Not perfect, but acceptable.

The ROM-Installation comes without Gapps and Root. Both is included in the archive that you have downloaded. If you want to have Google-Apps, flash Gapps-Zip immediately after ROM-installation (before rebooting). If want to have SuperSU, flash it afterwards (it is included in the archive as well). For Magisk just boot the ROM and install the MagiskCanary-APK included in the archive - it installs Magisk to give you Root-access as well. The Canary is a late Magisk-22 version.

Note that you should use Magisk or SuperSU for root access, but not both.

The ROM isn't really unrooted, just the Root-Tools are not preinstalled. If you want to have the ROM completely unrooted, flash the unrooted boot.img from within TWRP: Go to "Install", select "Install Image", select the boot_unrooted.img that I supply here and select Partition "Boot" as destination.