Related
No more free rides
Donor is Port Rom?
Black_Eyes said:
Donor is Port Rom?
Click to expand...
Click to collapse
Yes
Tqr said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
Runs on Windows & Linux with WINE
MiPatcher is designed to append MIUI to any CM base that shares the same 'Build.id'. This can be found in build.prop.
At the same time this will also serve as a technical guide for folks just starting out with porting MIUI in the 4.4 era, those doing this by hand or others who are just returning to the game.
MiPatcher is not a substitute for PatchROM and is not the same in function by any means although it can use Patch components on the most basic level.
This is geared more toward people who are trying to build a functional MIUI for neglected devices and also for people testing various bases who may not yet be configured to build from source to accommodate some of MIUIs functionality.
MiPatcher is as of right now very straight-forward; you pick the resolution for the device you are porting for and it will adjust the Donor MIUI to 'look right' on your device.
Requirements
- Autohotkey (Only if you intend to run the source for this)
- CyanogenMod 11
*Disabled SELinux
*Boot.img edits (for full functionality if not using PatchROM)
*Modified seapp_contexts (At Kernel level for use with PatchROM, at source level for manual porting/using this tool)
**Stock CM with init.d support may also be used; although it will be sloppy.
- MIUI donor firmware with the same 'Build.id' found in /system/build.prop
- PatchROM resources (If your Donor is a different resolution, you do not 'need' them unless things look terrible)
*Or get PatchROM resources here if you intend to grab for every resolution; it's half the size of the one on Github better compression
- WinRAR or 7zip
Features
- Automatically append MIUI to any same code-base firmware.
- Append init.d on supported devices to force boot without changes to the kernel
Prep-work
Only three files must be edited for test-ports, which I'll cover now.
Framework-res.apk
Open your Base and donor Framework-res.apk, navigate to res/xml and import the following XMLs:
Code:
Storage List
Power Profile
Build.prop
Code:
ro.build.version.incremental=x.xx.xx
persist.sys.root_access=0
ro.config.notification_sound=xxx.ogg
ro.config.alarm_alert=xxx.ogg
ro.config.ringtone=xxx.ogg
ro.skia.use_data_fonts=1
ro.miui.ui.version.code=3
ro.miui.ui.version.name=V5
qemu.hw.mainkeys=0 **[U] If you have no physical HW keys.[/U]
Updater-Script
Code:
set_perm(0, 0, 06755, "/system/xbin/lbesec"); ***If LBEsec exists in your donor
set_perm(0, 1000, 06750, "/system/xbin/shelld");
set_perm(0, 0, 06755, "/system/xbin/su");
With these most basic edits, MIUI will boot but with the need to install MIUI Lite to fix themes partially; as native ThemeManager, updater and backup will FC continuously.
Planning to use PatchROM? If you have an unlocked BL device or a device that will accept an unsigned kernel you can split your boot.img's ramdisk and add the following entries to 'seapp_contexts' immediately under user=shell, like this :
user=shell domain=shell type=shell_data_file
Code:
user=theme seinfo=platform domain=platform_app type=platform_app_data_file
user=backup seinfo=platform domain=platform_app type=platform_app_data_file
user=updater seinfo=platform domain=platform_app type=platform_app_data_file
And above anything else that may follow user=shell.
If you are not planning on using PatchROM, you will have to disable SELinux fully and edit your 'seapp_contexts' in source. In CyanogenMod11 source it is located in the following directory:
Code:
external/sepolicy/seapp_contexts
Now it's time to kill SELinux, navigate to your Kernels config folder in source; generally found at:
Code:
kernel/brand name/kernelname-common/arch/arm/configs
and find 'kernelname_defconfig' or 'kernelname_selinux_defconfig', change the following value to 'n':
Code:
CONFIG_SECURITY_SELINUX=[B]n[/B]
This will yield a functional CyanogenMod11 that can be used with PatchROM without issue, and can also be used to just fork firmware which is useful in the case of unified device builds, which Patch does not really like so much.
Now that you've built your base the following edits must be made to the kernel's Ramdisk:
Init.rc
Add this line at the very end of init.rc
Code:
import /init.miui.rc
init.miui.rc
Create this file in the root of your ramdisk and place the following inside:
Code:
#service for shelld
service shelld /system/xbin/shelld
class main
#service for su
service su_daemon /system/xbin/su --daemon
class main
oneshot
service lbesec /system/xbin/lbesec
class main
oneshot
init.superuser.rc
Code:
Delete this file
init.cm.rc
Add a '#' to the following line to disable the calling of init.superuser.rc
Code:
[B]#[/B]import /init.superuser.rc
Default.prop
Change the following values:
Code:
ro.adb.secure=[B]0[/B]
ro.secure=[B]0[/B]
ro.allow.mock.location=[B]1[/B]
Once these edits have been made your base can now be adapted to MIUI.
MiPatcher Instructions
1. Extract the contents of baserom.zip to 'base'
2. Extract the contents of miuidonor.zip to 'donor'
3. Inside of the PatchROM resources zip, extract 'HDPI' 'xHDPI' and 'xxHDPI' into the 'PatchROM' folder
4. Run MiPatcher, select your resolution and if you haven't made any kernel editing or done special source building, use soft-mods.
5. Zip the contents of 'Base' and flash it.
6. If this yields a non-booting build your codebase is too distant from your donor, find another same Build.ID release and try again if not proficient with ADB.
Current version:0.01
0.01: First release, Basic functionality and enough to produce one-shot ports when the base is properly prepared.
0.01: x64 x86 stand-alone .exe
Next Version:0.02
0.02: Clean up redundant/inefficient code.
0.02: Add options for boot.img, build.prop, meta-inf backup and loading.
*to avoid having to edit or manually move these with each attempt on base.
Download
9/28/2014: MiPatcher x86&x64
This is stand-alone and requires nothing to run, PatchROM parts are optional but suggested nonetheless.
Source
To use this source as an executable 'program' you must download and install Autohotkey, after right-click on your desktop to create a new '.ahk' file, paste the contents of this inside of it and save.
Create the following folders in the same folder as your .ahk file, the folder structure should mimic the following in terms of layout with extracting things:
-base
*META-INF
*System
*Boot.img
-donor
*META-INF
*System
*Boot.img
-mod create two notepad++ files with no extension, name them the following and place the respective content inside:
*00lbesec
Code:
#!/system/bin/sh
/system/xbin/lbesec &
*00shelld
Code:
#!/system/bin/sh
/system/xbin/shelld &
-patchrom
*HDPI
*xHDPI
*xxHDPI
AHK source:
http://paste.ee/p/balNM
FAQ
Q: My ROM isn't booting!
A: Try another MIUI that uses the same Build ID as yours, or use ADB to debug your build as it will be really close either way.
Q: Is there any difference between using a .ahk file and a .exe?
A: Yes. It's easier to update by pasting new code into a .ahk text file than to download packed .exe files in the longrun; however when using a .exe you don't need to install Autohotkey.
I will make standalone .exe for this at some point soon today.
Q: Theme/Updater/Backup is FCing!
A: It's a SELinux related error, sounds like you may be using PatchROM or a unified build; in this case build from source with the Seapp_context, and with SELinux turned off.
Q: Storage isn't mounting!/File Explorer is closing!
A: Import CyanogenMod11's 'StorageList' located in Framework-res.apk/res/xml into MIUI's along with the 'PowerProfile' to resolve unreadable storage
Q: [Insert name] App is crashing...
A: Debug using ADB or find another donor if you're feeling lazy, most of the time this yields perfect results but some things will maybe need a little polish depending on how far the codebase from the Donor and your Base firmware are.
Big TY to:
Code:
* Sijav
* Chevelle
* Yun
* All the Russian firmware developers, ahead of everyone else by a bit..
XDA:DevDB Information
MiPatcher: A MIUI forking utility, Tool/Utility for all devices (see above for details)
Contributors
Tqr
Version Information
Status: Testing
Stable Release Date: 2014-10-04
Beta Release Date: 2014-09-30
Created 2014-09-28
Last Updated 2014-09-28
Click to expand...
Click to collapse
What's the "MIUI donor firmware" ? Doest it work on Ubuntu with Wine ?
h2o64 said:
What's the "MIUI donor firmware" ? Doest it work on Ubuntu with Wine ?
Click to expand...
Click to collapse
Any MIUI firmware as long as it has the same build.id as your base
Edit: Yes this tool works in ubuntu with WINE, but only as a .exe, it can't run as a .ahk file I believe.. I mean I've never tried running raw .ahk files in Linux
Tqr said:
Any MIUI firmware as long as it has the same build.id as your base
Edit: Yes this tool works in ubuntu with WINE, but only as a .exe, it can't run as a .ahk file I believe.. I mean I've never tried running raw .ahk files in Linux
Click to expand...
Click to collapse
Okok.. I'll use CM 11 of my Moto G with the Nexus 5 build.
Can I post here if I've trouble with the software?
h2o64 said:
Okok.. I'll use CM 11 of my Moto G with the Nexus 5 build.
Can I post here if I've trouble with the software?
Click to expand...
Click to collapse
Sure, I don't mind Q&A
h2o64 said:
Okok.. I'll use CM 11 of my Moto G with the Nexus 5 build.
Can I post here if I've trouble with the software?
Click to expand...
Click to collapse
Nexus 5 won't be Good
what about a little wait and We will Port from Moto x ? @h2o64
Black_Eyes said:
Nexus 5 won't be Good
what about a little wait and We will Port from Moto x ? @h2o64
Click to expand...
Click to collapse
I'll try from one plus one (4.4.4)
If we need to wait. I prefer waiting for Redmi 1S which have a configuration very near to Moto G's one.
---------- Post added at 04:53 PM ---------- Previous post was at 04:22 PM ----------
Tqr said:
Sure, I don't mind Q&A
Click to expand...
Click to collapse
Works perfectly fine on Ubuntu 14.04 64 bits (I've used x64 one).
I'll flash the zip file. Keep you updated.
Black_Eyes said:
Nexus 5 won't be Good
what about a little wait and We will Port from Moto x ? @h2o64
Click to expand...
Click to collapse
I just made a post for the Moto X, sorry about that lol
Tqr said:
I just made a post for the Moto X, sorry about that lol
Click to expand...
Click to collapse
Which base did You use?
Help us to Boot it on Moto g
Black_Eyes said:
Which base did You use?
Help us to Boot it on Moto g
Click to expand...
Click to collapse
ok, I'll have to build you guys CyanogenMod from my code-base.. give me a few hours and I'll get it built by the end of today
Edit: I'm going to automate this in a very strong way; by the time this tool reaches 'stable' I will have ideally automated everything so that people with a totally unsupported device can have everything done for them from building to having MIUI applied without having to manually do anything.
It will not be as recent as a PatchROM build but it will be a 'sure bet' for anyone looking to use a pretty recent internal version of MIUI; I'm not trying to make a platform to replace PatchROM It's essential but I am trying to make a platform to enable people to just use MIUI without having to pull teeth over it
Tqr said:
ok, I'll have to build you guys CyanogenMod from my code-base.. give me a few hours and I'll get it built by the end of today
Click to expand...
Click to collapse
Ok Thanks i will be waiting
---------- Post added at 08:06 PM ---------- Previous post was at 08:02 PM ----------
Tqr said:
ok, I'll have to build you guys CyanogenMod from my code-base.. give me a few hours and I'll get it built by the end of today
Edit: I'm going to automate this in a very strong way; by the time this tool reaches 'stable' I will have ideally automated everything so that people with a totally unsupported device can have everything done for them from building to having MIUI applied without having to manually do anything.
It will not be as recent as a PatchROM build but it will be a 'sure bet' for anyone looking to use a pretty recent internal version of MIUI; I'm not trying to make a platform to replace PatchROM It's essential but I am trying to make a platform to enable people to just use MIUI without having to pull teeth over it
Click to expand...
Click to collapse
That will be Great :good:
Tqr said:
ok, I'll have to build you guys CyanogenMod from my code-base.. give me a few hours and I'll get it built by the end of today
Edit: I'm going to automate this in a very strong way; by the time this tool reaches 'stable' I will have ideally automated everything so that people with a totally unsupported device can have everything done for them from building to having MIUI applied without having to manually do anything.
It will not be as recent as a PatchROM build but it will be a 'sure bet' for anyone looking to use a pretty recent internal version of MIUI; I'm not trying to make a platform to replace PatchROM It's essential but I am trying to make a platform to enable people to just use MIUI without having to pull teeth over it
Click to expand...
Click to collapse
Amazing ...
Is the source code available ?
@Tqr the tutorial stays a bit un-clear :
Why using patchrom after porting ? Can we use it during porting ?
All the stuff about patchROM is a bit complicated.
We need to re-build an entire CM11 without Selinux ?
h2o64 said:
Amazing ...
Is the source code available ?
@Tqr the tutorial stays a bit un-clear :
Why using patchrom after porting ? Can we use it during porting ?
All the stuff about patchROM is a bit complicated.
We need to re-build an entire CM11 without Selinux ?
Click to expand...
Click to collapse
He will Build for Us
Black_Eyes said:
He will Build for Us
Click to expand...
Click to collapse
I'm a dev. I want to try it myself and to learn how to do.
I've work a lot on it :'( :'( :'(
h2o64 said:
Amazing ...
Is the source code available ?
@Tqr the tutorial stays a bit un-clear :
Why using patchrom after porting ? Can we use it during porting ?
All the stuff about patchROM is a bit complicated.
We need to re-build an entire CM11 without Selinux ?
Click to expand...
Click to collapse
When using PatchROM you can leave SELinux intact, when porting manually/using this tool you must fully disable SELinux or use a base that does not have it to begin with.
You don't even need to touch PatchROM to use this, or Linux honestly.. even the PatchROM Resources aren't required unless you're coming from a device with a different resolution sometimes.. but not always
Edit: Otherwise make the following edits I've outlined to CyanogenMod in source, I feel I was pretty clear on what to change
Tqr said:
When using PatchROM you can leave SELinux intact, when porting manually/using this tool you must fully disable SELinux or use a base that does not have it to begin with.
You don't even need to touch PatchROM to use this, or Linux honestly.. even the PatchROM Resources aren't required unless you're coming from a device with a different resolution sometimes.. but not always
Edit: Otherwise make the following edits I've outlined to CyanogenMod in source, I feel I was pretty clear on what to change
Click to expand...
Click to collapse
You just have to say the two first line of this post because they are perfectly understable and help me a lot .
Can I just re-built the kernel without Selinux ?
h2o64 said:
You just have to say the two first line of this post because they are perfectly understable and help me a lot .
Can I just re-built the kernel without Selinux ?
Click to expand...
Click to collapse
@h2o64 Yes
and i think that's why Rom doesn't boot with manually Porting
---------- Post added at 08:37 PM ---------- Previous post was at 08:33 PM ----------
How can i disable SELinux without Building the Kernel ?
h2o64 said:
You just have to say the two first line of this post because they are perfectly understable and help me a lot .
Can I just re-built the kernel without Selinux ?
Click to expand...
Click to collapse
No; you will still have Fingerprint errors
All developments are carried out thanks to donations on Purchase of these or other devices
thank
Please do not copy files to other file shares
the project is under constant development and refinement
Project name [ROM] Moto X L!te FW LPA23.12-15.5.EU.ML
Tagline Faster Lighter Economical
for XT1052/1053/1058 - 2G/3G/LTE
and only GSM XT1049/1050/1056/1060/ - 2G/3G/LTE (for CDMA use menu *#*#4636#*#*)
SYSTEM Firmware LPA23.12-15.5.EU.ML Multilingual
- firmware Deodex - allowing resources using modifiers such GravityBox apply all when firmware odex, it sometimes limited customization or going awry
- Launcher -4*5, no searche bar
- tzdata 2015f
- icudt53l last
- return "the gesture of the Jedi" (after installing the firmware of the old sensor /*** it does not threaten the phone)
- delete more apps FaceLock, MotoServices, Google Drive & Docs, Permissions and etc
- replaced by sound WirelessChargingStarted
- uppdate apps LatinIME, Migrate, Calendar, AudioMonitor, Moto, MotCamera, MotGallery
- Stagefright Fix
- removed a lot of the background services collect and send data on the type of phone DropBox, MotoCare, MotoConntect, Drive, FaceLock ... etc.
- add apps VendorApp ESFileManager, CCleaner
- added Russian, Ukrainian language
for Unloked Device
Install for Custom Recovery
Root not PreInstalled
Download there https://yadi.sk/d/jp8ykQqFindY8/MotoX/5.1.0
for Loked Device
5.1.0 for locked phones ready to be sewn LONG !!! 5.1.0 1.5 GB used by all, no matter what the new system weighs only 900MB ... the old system to be erased
Install for QDLoad9008
Root, BusyBox is PreInstalled
- Root SuperSU v2.46
- BusyBox v1.32.2
DISCLAIMER
Author is not responsible for totally bricked devices, broken arms, legs, plane crashes and your wife's cheating.
All actions taken is your own risk.
Instructions to install
You:
- shouldn't be afraid of Qualcomm HS-USB QDLoader 9008;
- do not change any files, pathes;
- can install drivers manually;
- need to install python-2.7.9 and pyserial-2.7.win32;
- unzipp _Rus_5_1_0_LPA23_12.XX.7_BL_V30.BE.rar to Cython27;
Method is dangerous, however gives results.
you must have firmware SU6-7 receiving is not in the form of an update (OTA) and stitched through the RSD Lite.
00 Flash *******_5.1.0-LPA23.12-XX.7_CFC.xml firmware
01 Unzipp everything to Cython27.
02 Run BLBROKE.bat.
03 After you got Qualcomm HS-USB QDLoader 9008, install drivers manually
04 Run RUN_Rus_Part**.bat. Parts 250 of system.
*** You can also run a file if you are sure that your phone can work 6-7 hours with the screen RUN_Rus_***_Full.bat
then repeat this step X times (the number of times equal to 6)
while (found next part) do
***
>> fastboot to hold 10 minutes that would have been charged a little phone
>> Run BLBROKE.bat.
>> Run RUN_Rus_***_Part**.bat. Parts 250 of system.
***
end
99 Turn device on. Now you have SU DEODEX PreRooted
Drivers, Soft there -> https://yadi.sk/d/p458Cy0XineRC
Scripts, ROM there -> https://yadi.sk/d/kxbxpTnziSg35/Moto X/5.1.0
Please do not copy files to other file shares
the project is under constant development and refinement
XDA:DevDB Information
[ROM] Moto X L!te FW LPA23.12-15.5.EU.ML, ROM for the Moto X
Contributors
CrashXXL
ROM OS Version: 5.1.x Lollipop
ROM Firmware Required: Android 5.1.0 LPA23.12-15.5
Version Information
Status: Stable
Current Stable Version: 1.00
Stable Release Date: 2015-10-19
Current Beta Version: 0.01
Beta Release Date: 2015-09-28
Created 2015-10-12
Last Updated 2015-10-21
So can I assume this is a stock based rom that has been debloated, optimized, and such but is fully functional as a stock Rom? I've been waiting to update the wife's X on account of all the reported troubles with the official lollipop update.
This firmware is the most clean and fast
It based on the stock, and includes all updates and patches
Hi!
First of all, thank you very much for your rom, the "jedi" gesture is back!
I checked the stagefright detector and it seems to be vulnereble to the "CVE-2015-6602" I asume is a new vulnerability and motorola haven´t patched yet.
I have installed the rom an hour ago and everything works as expected, so nothing else to report, if I find anything strange i will tell you.
Thanks again!
Iktor said:
Hi!
First of all, thank you very much for your rom, the "jedi" gesture is back!
I checked the stagefright detector and it seems to be vulnereble to the "CVE-2015-6602" I asume is a new vulnerability and motorola haven´t patched yet.
I have installed the rom an hour ago and everything works as expected, so nothing else to report, if I find anything strange i will tell you.
Thanks again!
Click to expand...
Click to collapse
stagefright was fixed in last update, so I would certainly expect this ROM to have that patch. also, I believe that this thread should be moved to the Development section, not in general. you may need a mod to help out.
"and only GSM XT1049/1050/1056/1060/ - 2G/3G/LTE (for CDMA use menu *#*#4636#*#*)"
So this could work on the Sprint network with a 1056?
please link to another server
Enviado desde mi Moto X mediante Tapatalk
May I know how often will you update?
What about the very serious glitch-bug on YouTube ? Is it fixed ?
Sent from my XT1052 using Tapatalk
the project will be updated as long as I have moto phone x1
applications such as YouTube, Chrome, and others I can not fix, maybe, I do not have the source code of the product
YES 1056 will work
Xposed?
wildblade64 said:
Xposed?
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed
CrashXXL said:
the project will be updated as long as I have moto phone x1
applications such as YouTube, Chrome, and others I can not fix, maybe, I do not have the source code of the product
Click to expand...
Click to collapse
Thank you for reply.
jco23 said:
stagefright was fixed in last update, so I would certainly expect this ROM to have that patch. also, I believe that this thread should be moved to the Development section, not in general. you may need a mod to help out.
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/ota-xt1052-firmware-update-5-1-10-10-t3221898
Above thread has screenshots of XT1052 with update and shows that the above vulnerability is not fixed yet. It's the only one thats not fixed.
---------- Post added at 07:05 PM ---------- Previous post was at 07:02 PM ----------
CrashXXL said:
the project will be updated as long as I have moto phone x1
applications such as YouTube, Chrome, and others I can not fix, maybe, I do not have the source code of the product
Click to expand...
Click to collapse
I'm sorry... I dont understand... Do these apps not work right now???
I want to try this ROM to get back to stock... I do not have a system to flash the stock files...
Please help me understand.
XT1049 on C Spire?
Do you think this ROM will work on XT1049 from C Spire? I also would like to use a stock based ROM.
I do not change third-party applications, such as YouTube, Chrome, and other Google search, wait for the update application from the developers (Google)
Sorry, I meant to say if this rom will have xposed built in. Thank you so much crash by the way, I'm assuming this will eventually work for xt1058 with locked bootloaders?
what is that?
the gesture of the Jedi
what is that?
On kitkat you could have your hand in front of the screen and it would display moto display, since the lolipop update, you have to hold your hand directly over the light sensor for a few seconds.
Hi guys,
Cloud_Commander is a universal gsm software.
The software was targeted towards phone technicians and users for free.
Current latest version : ver 1.7(Pirates edition) .
All bugs should be reported to [I][email protected][/I]
NB: THE SOURCES OF THIS SOFTWARE IS ALSO FOR SALE INCLUDING ALL RIGHTS (OWN THIS SOFTWARE AS YOUR OWN), CONTACT ME FOR MORE DETAILS !
NB: PLEASE DON'T SEND COMMANDS THAT ARE NOT TESTED PERSONALLY!
Just make sure you have the necessary drivers installed and don't forget to runas administrator.
Added latest adb support.
Improved layout and increased window size.
Added f2search user panel.
Added LG file download by imei and flashtool launchers.
Improved lumia unbrick tool(works still in progress).
Added powerfull windows driver manager.
Fixed huawei calc layout bug.
Added advanced phone hardware pinouts for hardware help.
Added f2search username in settings(New files will be added on release).
We'll fix commands arrangement to follow a specific order(also on release).
Only tool that can remove techno n5s frp.
Only tool with free pinouts. All models will soon be added by users, anyone can add pinouts.
Only tool that can download lg flashfile by imei.
Only tool where users can add commands without need to re-download software.
[DOWNLOAD VER 1.7 HERE]
USE THIS VERSION
DOWNLOAD VER 1 . 7 1 Bug fix HERE<<<LATEST
XDA:DevDB Information
Cloud_Commander Ver1.7 (Pirates edition) [BETA], Tool/Utility for all devices (see above for details)
Contributors
kenkitt
Version Information
Status: Testing
Current Beta Version: 1.7
Beta Release Date: 2016-11-18
Created 2016-11-18
Last Updated 2016-11-18
need mediafire or google drive link
kenkitt said:
Hi guys,
Cloud_Commander is a universal gsm software.
The software was targeted towards phone technicians and users for free.
Current latest version : ver 1.7(Pirates edition) .
All bugs should be reported to [I][email protected][/I]
NB: THE SOURCES OF THIS SOFTWARE IS ALSO FOR SALE INCLUDING ALL RIGHTS (OWN THIS SOFTWARE AS YOUR OWN), CONTACT ME FOR MORE DETAILS !
NB: PLEASE DON'T SEND COMMANDS THAT ARE NOT TESTED PERSONALLY!
Just make sure you have the necessary drivers installed and don't forget to runas administrator.
Added latest adb support.
Improved layout and increased window size.
Added f2search user panel.
Added LG file download by imei and flashtool launchers.
Improved lumia unbrick tool(works still in progress).
Added powerfull windows driver manager.
Fixed huawei calc layout bug.
Added advanced phone hardware pinouts for hardware help.
Added f2search username in settings(New files will be added on release).
We'll fix commands arrangement to follow a specific order(also on release).
Only tool that can remove techno n5s frp.
Only tool with free pinouts. All models will soon be added by users, anyone can add pinouts.
Only tool that can download lg flashfile by imei.
Only tool where users can add commands without need to re-download software.
[DOWNLOAD VER 1.7 HERE]
XDA:DevDB Information
Cloud_Commander Ver1.7 (Pirates edition) [BETA], Tool/Utility for all devices (see above for details)
Contributors
kenkitt
Version Information
Status: Testing
Current Beta Version: 1.7
Beta Release Date: 2016-11-18
Created 2016-11-18
Last Updated 2016-11-18
Click to expand...
Click to collapse
how to use it bro..............................
alo sk said:
need mediafire or google drive link
Click to expand...
Click to collapse
That is a mediafire link, generated by our site automatically.
You should be able to skip the add (adfly).
other link please...
please how can i run this file? the extension is arc file
use this my friend :
http://freearc.org/Download.aspx
http://www.mediafire.com/file/hb1zld94st1jij3/Cloud_Commander_ver1.7(Pirates+edition)release.arc
File: Cloud_Commander1.71 bug fix(Pirates edition)release.arc
MD5: 085e4077fc5901a542775a0da668356b
asadnow2k said:
http://www.mediafire.com/file/hb1zld94st1jij3/Cloud_Commander_ver1.7(Pirates+edition)release.arc
Click to expand...
Click to collapse
Please don't post direct links, we earn money through adfly, direct links will bypass adfly.
The tool is free for everyone.
K
Sent from my iPhone using Tapatalk
edit
links does not work
The link is has been updated
I am working the new version which will have alot of features. It has alot of work, we are getting rid of that userinterface for 3d using ogre3d. The new version will allow you to choose which interface you preffer, but I'll concentrate on the 3d version. It will also include mtk flashing where you will just choose like say infinix 551 (remove frp) or readbackup format etc, devs will have access to a new mtk flashing system to add new phones support.
FOLLOW MY PROGRESS WITH THE RE-ANIMATION EDITION ON TRELLO
The new cloud_commander will function with a service.
https://trello.com/b/wALk1Gp0
and
https://trello.com/b/eKSi6iX0
https://www.patreon.com/cloud_commander
kenkitt said:
https://www.patreon.com/cloud_commander
Click to expand...
Click to collapse
I can't run the software, Can you please help me ?
Javaron said:
I can't run the software, Can you please help me ?
Click to expand...
Click to collapse
Hi, this tool is very old, what did you want to use it for ?
We have another tool maybe it might be ablee to help you.
kenkitt said:
Hi, this tool is very old, what did you want to use it for ?
We have another tool maybe it might be ablee to help you.
Click to expand...
Click to collapse
I want to unbrick My Lumia 730
I tried many processes to make it alive, but I can't.
Can you please give me a solution ?
Author Nickname: Deelie
Applicable models: Lenovo ZUK Z2
Based on version: ZUI 3.1.117
Android version: 7.0
Team Support: LR.Team
Posted: 2017.11.29
Sina Weibo: Deelie
Updated this week
Follow up ZUI 3.1.117 stable version
Join the bottom of Android 7.0
Add root privileges
Streamline the official built-in APP promotion software
Precautions
Bootloader needs to be unlocked before brushing into this package (ignore if BL has been unlocked)
Unlock Bootloader Address :
http://developer.zuk.com/bootloader
Copy the code
Be sure to brush third party recovery after unlocking
One-touch brush into TWRP:
https://pan.baidu.com/s/1c2rHZqg
Copy the code
Sync official update
New design style, make your ZUI like a smart windmill
A new negative screen, the key information and quick payment one screen mastered
New lock screen and desktop wallpaper synchronization push function
Find new mobile phone features, go to Settings -> cloud services open
Added QQ article reading and chat back and forth switching function
Add list search function, management application more convenient and quick
Added yellow calendar, solar terms, grab votes calendar
Added Import birthday from contact
Add credit card repayment reminder
Added calendar backup and recovery
Optimize meeting schedule management
Added memo cloud sync feature
Optimized notes editing
Added spring rain doctor health advisory function
source: https://club.lenovo.com.cn/thread-4259973-1-1.html
Is this rom Chinese only or CHV/ENG?
plz share the download link..
Instead flash gizrom 3.0 based on 3.1.117st.
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