Related
mt6572, mt6575, mt6577, mt6589, mt6582, mt6592 and all the other variants up to mt6592, except AndroidOne project.
The version 2.7 is the final version for Jellybean kernels (or older). This is the end of the road for it. Won't be more updates. Instead for newer kernels (kitkat, maybe lollipop) you should check my new version.
DISCLAIMER:
Rooting your phone and using custom Recoveries and ROMS have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledges about phones and phones utilities too.
Make sure that whatever you do, you are doing it at your own responsibility.
It is a CWM based recovery and is compatible with it. In this version I used Napstar-xda's full touch module as base. The navigation it is posible by touching the menu item. In long display menu (as choose zip from sdcard) for scroll page down Swipe Right and for scroll page up Swipe Left. For Go Back also Swipe Left.
If the Swipe doesn't work (usually if your phone is multitouch but has only 2 points of touch), use bottom virtual navigation keys or volume buttons Down for Scroll down, Up for Scroll up, and the back button for Go Back.
Version 2.7 update (11-dec-2014):
- rebuilt from base (cwm 6.0.3.7) and add improvements on top.
- reintegrated bottom virtual navigation keys, to compensate the non-function of swipe in some phones
- better compressed backups integration - pigz support from cm-11
- new "nvram backup/restore" menu functionality: the nvram partition will be backed up in clockworkmod/backup/.nvram/nvram-xxxxx folder as nvram.img. This will help if you lose IMEI and other communication features. It will work only if you have the nvram partition defined in recovery.fstab. If the nvram partition is damaged (as in flashing an oversized recovery) this will not help you, and you need SPFlashTools to reflash with format your phone official firmware, and after that flash this recovery, boot in recovery and restore nvram.
- the recovery has now an increased stability, many issues are solved
- the content of the backup folder will contain only what an usual clockworkmod backup contain, and that will make it easy to restore backups made with older versions.
- new GUI images, very light (the difference between non-touch modded cwm and this one is only 14 Kb, for 720x1280 resolution)
- some other changes.
You can flash in recovery the attached AromaFM_installer.zip, and the aromafm.zip will be placed at its place, so you can use aroma fm menu.
For port follow my new guide from here. If you want to use the automated method, that works only for older versions at my friend yuweng's thread.
Currently there are two lunfile paths in the world of mtk devices. This will make your USB Mass storage to work in recovery or not. Search that path in your device to see what you have.
Lunfile path 1 (old): "/sys/devices/platform/mt_usb/gadget/lun%d/file" - this can be found in many devices mt6572, mt6589, mt6589T, and other old ones.
Lunfile path 2 (new): "/sys/devices/platform/mt_usb/musb-hdrc.0/gadget/lun%d/file" - this is related to new devices mt6582, mt6592...
Find where is your path and download the image to port from correct section.
There are two sections, corresponding to those two lunfile paths, with 15 images each. These 15 images are corresponding to different resolutions. Choose the one that match exactly your phone resolution. If your phone has the resolution 720x1280, then take an image with "720x1280" in name. There are few landscape versions for tablets with landscape format, so don't confuse "720x1280" with "1280x720".
IMPORTANT:[/B]
These are compiled recoveries for porting purposes only. DON'T take any of them and flash it in your phone as it is. It won't work, they include a dummy kernel. You need to port it to your device as I show in my guide, to make it work.[/COLOR]
CREDITS:
- Napstar-xda - for touch module;
- Philz-cwm6 - for get partition size method;
- xiaolu - for the new fonts;
- C3C0 - for initial mtk tweack hint - Unused now;
- Koush and all CWM team for the recovery;
- bgcngm for unpack/repack utils;
- sk8erwitskil for aromafm menu
RULES for posting your ports!
If you manage to port this to your device, add proper credits in your thread, post or article.
If you want that to be posted in a list with working devices, then post here a link to the thread or the post on xda (only on xda). Why not a free hosting link, like google drive, dev-host, mega-coz or other? Because if in the future you will port a new version, you have to replace it in that thread or post and the link from list remain the same.
ATTENTION:
There is a possibility that the touch feature to not work in all phones. It was tested in many phones, and in some of them it doesn't work. There isn't a switch, a toggle or other method to make it to work, it depends on your phone touchscreen capability from recovery. If this doesn't work in your phone, I'm sorry, it happens, and my advice is to try something else.
Few clarifications:
I provided all necessary infos to help you to port it to your devices.
It is ment to be ported to all MTK devices, but this doesn't mean it will work in all.
In some devices with a cheap screen display (usually those with anly one or two points of touch) there is a big chance to not work, or to work only partial.
If the recovery has the screen flipped, you need to use the non-touch version, and to compile it by yourself from source, or to ask a developer from your device to do it, with BOARD_HAS_FLIPPED_SCREEN true flag in device BoardConfig.
This recovery is compiled in CM-10.1 environment (android 4.2.2) and is proved to be working in devices with kernels up to Android 4.3. For kitkat use my new version.
The main purpose for this recovery was to keep it under 6Mb, to fit in that small recovery partition that was used in these MTK phones.
If your phone's kernel is bigger than 4.3Mb and the recovery size is 6Mb, don't botter to try it. It won't work, because it will exceede those 6Mb.
Carliv Touch Recovery, version 2.7, for phones with custpack partition
This is for phones with an extra custpack partition (Alcatel or TCL).
Carliv Touch Recovery, version 2.7, for phones with "ubifs" file system
This is for phones with "ubifs" file system.
CREDITS:
- Christian Troy - for ubifs initial code;
List of compiled or ported recoveries for various devices.
Lenovo S660 (CN version S026)
THL T100S
THL T11
Elephone P7 mini
Bluboo X1 (mt6582)
Doogee Rainbow DG210
Kuphone 1phone 5s (sanstar72_wet_jb3)
ZTE V967S
iNew V3 for fw versions up to 1.0.7 (different kernel)
iNew V3 for fw versions 1.0.8 and above
ONN M7 tablet
Hisense Mira II HS EG980 / Smartfren Andromax Z
Alcatel OT POP C5 5036X/5036D
Polytron W8470 / Gionee GBW192
BLU Life Play L100
BLU Life Play X L102
Micromax A110
Micromax A110 - v2.5
Alcatel One Touch 5020 and variants
Xolo Q700/Q700i
Xolo A500s
Xolo A600
Micromax A120
LAVA-iris458Q * XOLO-Q600 * CROSS A88
Alcatel One Touch S'Pop 4030/A/E/D/Y/X
Landvo L200G
XOLO 8x-1000/8x-1100
Huawei Y320-U10
Lenovo P780 - [4Gb/CN/2013 version]
Alcatel Pop C2/4032A
Acer Liquid E3 / E380 v1
Acer Liquid E3 / E380 v2
Acer Liquid Z5(Z150)
Acer Liquid Z2 (Z120)
Alcatel One Touch Pop C3 4033A/X/D/E
CTR Recovery Ported to Canvas 2 / A110/ Noir Q10/Cynus T2
Master @carliv
Master,
Once Again a Masterpiece of yours is on XDA & So, Once again this disciple of yours has done this first.....
Here is My Thread for
CTR Recovery & CWM Recovery 6.0.4.0 for Micromax A110.
Thanks a ton for this again & again. Don't know how to thank you for all of your work. but I do remember my words and waiting for that to thank you once.
thanks for your efforts!
edit: ported the 720x1280 ver. for my device and it seems to be working all fine but the log info seems to be blocking the navigation button. I guess that's just it, thanks again!
dnle71 said:
thanks for your efforts!
edit: ported the 720x1280 ver. for my device and it seems to be working all fine but the log info seems to be blocking the navigation button. I guess that's just it, thanks again!
Click to expand...
Click to collapse
No. it shouldn't be that way. This has something to do with some values from default_recovery_ui. I put those values arbitrary because I don't have your phones. It's not really blocking, only visual, but the buttons still work. I guess it looks like in the old AmonRa recovery with touch buttons.
I will take that in consideration for future improvements. For other phones with same resolution, may be different.
It will be really helpfull if you post here your phone res and the maxX and maxY values from settings.ini from cotrecovery folder, if you had that installed before.
carliv said:
No. it shouldn't be that way. This has something to do with some values from default_recovery_ui. I put those values arbitrary because I don't have your phones. It's not really blocking, only visual, but the buttons still work. I guess it looks like in the old AmonRa recovery with touch buttons.
I will take that in consideration for future improvements. For other phones with same resolution, may be different.
It will be really helpfull if you post here your phone res and the maxX and maxY values from settings.ini from cotrecovery folder, if you had that installed before.
Click to expand...
Click to collapse
touch is working even if it was somewhat blocked or something but the touch could extend above even if im not actually touching the nav buttons.
cot settings here.
;
; COT Settings INI
;
[Settings]
Theme = hydro ;
SDTheme = 0;
ORSReboot = 0 ;
ORSWipePrompt = 1 ;
BackupPrompt = 1 ;
SignatureCheckEnabled = 0 ;
BackupFormat = 0 ;
maxX = 742 ;
maxY = 1278 ;
touchY = 1067 ;
Language = en ;
dnle71 said:
touch is working even if it was somewhat blocked or something but the touch could extend above even if im not actually touching the nav buttons.
cot settings here.
;
; COT Settings INI
;
[Settings]
Theme = hydro ;
SDTheme = 0;
ORSReboot = 0 ;
ORSWipePrompt = 1 ;
BackupPrompt = 1 ;
SignatureCheckEnabled = 0 ;
BackupFormat = 0 ;
maxX = 742 ;
maxY = 1278 ;
touchY = 1067 ;
Language = en ;
Click to expand...
Click to collapse
Can you download and port again your resolution 720x1280? I changed some settings and it is updated to 6.0.4.0
Tell me if it works to re-compile all res again.
carliv said:
Can you download and port again your resolution 720x1280? I changed some settings and it is updated to 6.0.4.0
Tell me if it works to re-compile all res again.
Click to expand...
Click to collapse
still the same.. also notice my finger, the nav button detects it.
dnle71 said:
still the same.. also notice my finger, the nav button detects it.
Click to expand...
Click to collapse
The Touch is something similar like the Graph (of Mathematics).
Its based on X,Y positions like - X10 & Y 10 but in this there is no negative numbers.
So notice one thing. When ever you will click above any navigation key you will find it clicks the navigation button coming parallel to it.
Its not completely like TWRP or CWM Touch Version. But yes as we know Master @carliv can port the CWM touch version also for CTR Recovery. Then only we can get everything on touch based.
Awesome brother.. hats off.. expecting a full touch recovery soon from you...
Update
Successfully ported the recovery and its cent percent functional..btested every single options.. touch is working fine.. thanks for your suppport brother.. and I'm uploading the file now.. after that I'll update it here brother..
Sent from my Celkon A97i
I forgot to write. I made it this way, to be full screen touch. You can navigate up, down by swipe up/down in button area. For select you have to touch the screen in select button area. What is bothering me is log overlaping the icon menu. In my phone doesn't...
I will study that and maybe I will find an universal solution.
-----------------------
Ok, I figured out. I have to reduce MAX_ROWS.
I will rebuild every res, and the new one will be on 6.0.4.0 base.
carliv said:
I forgat to write. I made it this way, to be full screen touch. You can navigate up, down by swipe up/down in button area. For select you have to touch the screen in select button area. What is bothering me is log overlaping the icon menu. In my phone doesn't...
I will study that and maybe I will find an universal solution.
Click to expand...
Click to collapse
Brother here is the link.. and thanks for your awesome releases..and bro it didn't take even 2 mins to port it.. thanks for your guides..
http://forum.xda-developers.com/showthread.php?p=45347902
Sent from my Celkon A97i
All done. All updated to version 2.2. All recoveries compiled again with new version.
In attachment are ported recoveries for Canvas4 A210, Cubot A890, Star B6000, Star S9500, Star N9500, Zopo ZP820, UMI X2, Blackview JK809, Alcatel One Touch X'Pop 5035D (with custpack).
If you share one of these recoveries on your site, or other sites and forums, please use the name I gave it Carliv Touch Recovery, not Recovery Touch or CWM Touch (which is Koush's touch recovery name) or anything else. After six months of hard work I deserve that, and wasn't an easy job. Thanks!
carliv said:
All done. The source is adapted to 6.0.4.0 version of CWM. All resolutions recoveries compiled again with new version, and I hope the overlaping issue is gone.
In attachment are ported recoveries for Cubot A890 and Star B6000.
Click to expand...
Click to collapse
thanks! it's fixed now. will patiently wait for the updated features of this recovery
carliv said:
All done. The source is adapted to 6.0.4.0 version of CWM. All resolutions recoveries compiled again with new version, and I hope the overlaping issue is gone.
In attachment are ported recoveries for Cubot A890 and Star B6000.
Click to expand...
Click to collapse
Thanks Again Carliv, This Carliv Touch Recovery v.1 do Work!
I've thanked you!
PS: I put the recovery in my thread, as I did with the COT, and I also Quoted you and this 2nd post, okay?
carliv said:
All done. The source is adapted to 6.0.4.0 version of CWM. All resolutions recoveries compiled again with new version, and I hope the overlaping issue is gone.
In attachment are ported recoveries for Cubot A890 and Star B6000.
Click to expand...
Click to collapse
Bro @carliv I've ported this new recovery and its very good.. but a little problem with it is after finished installing the zip updates it never returend to the main menu.. to go out of recovery I'm removing the battery.. even the volume and power buttons also failed to work.. this problem shows up rarely and rest of the time it was good... and brother I'm moving my tjread for celkon here
http://forum.xda-developers.com/showthread.php?t=2473641
Please update it brother. The old thread is discontinued.. and one again a tons of thanks for you recoveries...
Sent from my Celkon A97i
praderj said:
Bro @carliv I've ported this new recovery and its very good.. but a little problem with it is after finished installing the zip updates it never returend to the main menu.. to go out of recovery I'm removing the battery.. even the volume and power buttons also failed to work.. this problem shows up rarely and rest of the time it was good...
Sent from my Celkon A97i
Click to expand...
Click to collapse
That's because the recovery doesn't exit from zip updater-script. Ask who write that script to do it better, with necessary unmount and clean up entries.
carliv said:
That's because the recovery doesn't exit from zip updater-script. Ask who write that script to do it better, with necessary unmount and clean up entries.
Click to expand...
Click to collapse
Brother I myself wrote it and it has correct format as you said.. it unmounts all the mounted partitions and also cleans up the temp files.. when I tried to flash the same recovery again the process went good.. ssometimes it stuck in the flashing screen and never returns.. it occured twice of my 13 tries....
Sent from my Celkon A97i
@chrmhoffmann compiled first ever CyanogenMod for his Wiko Stairway which is a MT6589 device and made it possible for other MT6589 users to taste CM. Since then many are porting it to their MT6589 device and many are requesting to make a port for their device. So, I have made a guide here to make it easier for them to port themselves. You should give proper credits to respected developers and hit thanks before posting on XDA.
NOTE:I have made a list of already ported CM roms in #2 post below , if your device is not listed there download any of the ported CM rom and follow this guide to port it to your device
This is the guide to port CM 10.2/11 for all MT6589 devices.Read carefully and follow each step correctly otherwise CM won't boot
Tools Required:
1) Archive Manger (winrar,winzip,7zip)
2) boot.img Unpack Repack Tools
http://forum.xda-developers.com/showthread.php?t=1587411(For Linux)
http://forum.xda-developers.com/showthread.php?t=2036528(For Windows)
NOTE:
For CM 11 the same proceedure is followed but the stock boot.img must be having kernel with binder.c patched and SELinux enabled (This feature can be bypassed but binder.c patch is must otherwise CM 11 won't boot)
Guide:
1) First get your stock rom and download any ported CM 10.2/11 rom from #2 post below
2) Get boot.img from your phone(stock rom) and boot.img from downloaded CM-ROM.zip
3) Unpack both of them to get ramdisk and kernel of both.
4) Repack CM's ramdisk and stock kernel (your phone's) to get a new boot.img
5) Extract system folder from your phone(stock rom) and system folder from downloaded CM-ROM.zip
6) Copy and replace these files from stock to CM,
=> /lib/modules/ -> all files
=> /framework/ -> CustomProperties.jar
mediatek-common.jar
mediatek-framework.jar
mediatek-op.jar
secondary-framework.jar
=> Also all the files mentioned in the below link ( A great thanks to Kashifmin for providing this )
https://github.com/kashifmin/android_device_micromax_a116/blob/master/proprietary-files.txt
7) Now take the modified CM system folder and the new boot.img and make a zip archive with normal deflate compression ( are default in 7zip)
8) Open the newly created zip archive and downloaded CM-rom.zip .Now drag and drop the META-INF and file_contexts from downloaded CM-rom.zip to newly created zip archive.
9) Now flash the new zip using recovery (CWM/TWRP)
10) Enjoy !!
CREDITS:
@michfood for his Boot unpack/repack utils for WINDOWS.
@bgcngm for his Boot unpack/repack scripts for LINUX.
@kashifmin for his proprietary-files.txt
@kashifminfor guiding me.
@chrmhoffmann For bringing the first ever CM10.2 for an MT6589 device.
@XpLoDWilD
@Dr-Shadow
OmniROM project.
Available CM port builds for MT6589
CM 10.2 builds:
Wiko Stairway / MMX Canvas 4 (A210) -> http://forum.xda-developers.com/showthread.php?t=2467400
MMX Canvas HD (A116) -> http://forum.xda-developers.com/showthread.php?t=2673367
XOLO Q700/Q700i -> http://forum.xda-developers.com/showthread.php?t=2675963
LAVA 458Q / XOLO Q600 / CROSS A88 -> http://forum.xda-developers.com/and...-cross-a88-t2814034/post54103404#post54103404
CUBOT GT99 / Cherry Apollo / XYZ X1 -> http://forum.xda-developers.com/and...cubot-gt99-t2834832/post54542482#post54542482
CM 11 builds:
Wiko Stairway / MMX Canvas 4 (A210) -> http://forum.xda-developers.com/showthread.php?t=2676086
MMX Canvas HD (A116) -> http://forum.xda-developers.com/showthread.php?t=2676896
ACER liquid e2 v370 -> http://forum.xda-developers.com/showthread.php?t=2766290
MMX Canvas Magnus (A117) -> http://forum.xda-developers.com/canvas-magnus/development/rom-cyanogenmod-11-canvas-magnus-a117-t2790957
MMX Canvas 2+ (A110Q) / Fly IQ450 -> http://forum.xda-developers.com/mic...-2-cyanogenmod-11-port-canvas-2-plus-t2750867
MMX Canvas Turbo (A250) -> http://forum.xda-developers.com/canvas-turbo/development/rom-cyanogenmod-11-canvas-turbo-t2780905
If CM for any MT6589 device is missing here , PM me. I will add here.
i try but always stuck on boot splash, no boot up.. pleash help thanks
Uhm.... I guess I can't port cm10.2 over stock jb4.2.1 rom, right?
I ask because I first looked for cm10.1 to port, but to my surprise, I didn't find any cm10.1 builds for any mt6589 on google.
@polfrank you can port CM 10.2 using stock 4.2.1 rom. First you have to download any CM 10.2 Rom from above and follow guide to port. You can even port above CM 11 Roms if you have a working kernel source for your device
Sent from my iris458Q using XDA mobile app
@limam27 boot loop occurs if 1) boot.IMG is badly repacked 2) any file is missing from your device stock rom which has to be copied to CM ROM as mentioned in the guide. Check them first . Also Check whether you are getting errors during unpack and repack of boot.IMG.
Sent from my iris458Q using XDA mobile app
Hmm, I'm stuck on my brand's splash screen too. I don't get to see the boot animation, and as you mention I get errors during both unpacking and repacking. But it said that the file was copied though.... I 'll search for another way to upack and repack on Google and come back.
Edit: pfff, seems like the only way to do it on windows was the one you provided...
Which CM version you are trying to port ?
If have Linux use unpack scripts to unpack/repack boot.img
Windows always gave me errors.
Sent from my iris458Q using XDA mobile app
4shreyas said:
Which CM version you are trying to port ?
If have Linux use unpack scripts to unpack/repack boot.img
Windows always gave me errors.
Sent from my iris458Q using XDA mobile app
Click to expand...
Click to collapse
I chose the CM10.2 from Wiko Stairway.
Yes, I'm now setting a Virtual Machine with Linux 14. And I'll try the unpack scripts from there. Let's see...
UPDATE:
OK, i ended up doing a clean install of ubuntu.
I upacked both images SUCCESS.
I repacked using stock kernel.img and CM ramdisk folder, SUCCESS.
I Install boot.img through CWMrecovery, it now gets past boot logo(Cubot white screen) but I think that before it would enter bootanimation the screen becomes a weird mass of colours, as if the screen was broken. It lasts for 1 second, then it restarts.
ps. I can successfully go to recovery with power+volUP If i like..
Any ideas?
You should get CM boot animation even if you use stock boot.img but won't boot. Did u correctly replace all required files in rom ? Do a clean one. Check if you can get logcat. Send me the logs
Sent from my iris458Q using XDA Premium 4 mobile app
4shreyas said:
You should get CM boot animation even if you use stock boot.img but won't boot. Did u correctly replace all required files in rom ? Do a clean one. Check if you can get logcat. Send me the logs
Sent from my iris458Q using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think I used wrong kernel.img. I repacked, will flash soon and come back to report.
EDIT: Are you sure that I have to use the META-INF folder from the CM rom? It gives me status 7 error.... (I also used the META-INF from a rom for my device, unfortunatelly it uses aroma, but it seems to install properly..)
EDIT2: I think that now I repacked the correct components of boot.img. It seems to get past the Cubot white splash screen, but after this, I get a black screen, but I can see that the screen is on, I can see the backlight. [I will try again with the CM META-INF-->still fails]
ps. Seems like I have to learn how to get a logcat if I wanna make use of your help... I'll be back in some hours.
----------------------------------------------------------------------
To sum up:
I have packed the new boot.img and replaced the needed files in the rom.
1) With the CM's META-INF folder I can't install, status 7 error.
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "stairway || getprop("ro.build.product") == "stairway"
E: Error in /sdcard/experiment/cm102last.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
2) With the stock rom's META-INF it seems to install propperly.
After reboot from recovery it goes to a black screen and stays there. I tried to logcat (adb logcat -v long > port.txt) but it just says:
[email protected]:/home/pol/Documents/sdk/platform-tools# adb logcat -v long > port.txt
- waiting for device -
Click to expand...
Click to collapse
If i write adb devices it says :
[email protected]:/home/pol/Documents/sdk/platform-tools# adb devices
List of devices attached
0123456789ABCDEF offline
Click to expand...
Click to collapse
When I am on recovery I get:
[email protected]:/home/pol/Documents/sdk/platform-tools# adb devices
List of devices attached
CWM-ZTE-V967S recovery
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------------
CONCLUSION: I managed to install the new boot.img and rom but it stops on a black screen, right after it passes from the white logo screen. And now, I need your ideas...
ps. I repeated the porting process from the beginning to make sure that I didn't make any mistakes... again, the same result.
--------------------------------------------------------------------------------------------------------------
NEW UPDATE: IT BOOTED!! but how....? Here it is........
I just replaced the boot.img from the wiko stairway flashable zip with the boot.img I created with repacking my phone's kernel and CM's ramdisk.
SO, I just changed the boot.img !!!! Testing.......
-------------------------------------------------------------------------------------------------------------
Testing results: buggy mobile network and sound not working. I guess this is why all those files are needed to be copied. I think I ll start copying..... But I wonder...what did I do wrong earlier while copying,,,?
You will get status 7 error because it is a security feature which doesn't allow to flash one device's ROM to other. You have to edit using any text editor and remove first line in the update-script found in meta-inf/com/Google/android/
Also don't use other rom's meta-inf as they have different symbolic links which may not boot the device.
Your phone's modules will be different from wiko's. That's why you got buggy audio and network. Replace all the mentioned files.
sent from my iris458Q using XDA mobile app
Okay, after some hours of trial and error I copied all the porting files provided in the op, except 2:
-libjpeg.so - When I port this from stock, Cm boots, but cannot show images, every single image, including the bootanimation is black.
-libmedia.so - When I port this from stock, Cm stays in the bootanimation forever. (No bootloop, just bootanimation forever)
-------------------------------------------------------------------------------------------------------------------------------------
The "extra" bugs that I have are:
1. No sound from the speaker (but yes in the headphone).
2. Weak signal. I don't know if this is normal. It has 1 bar and sometimes it has 0 and says no service. Also, the name of the tile in the QuickSettings is 20201 (weird...). I also get a message when the rom boots and it says: "Restricted Access changed. Data service is blocked." This appears sometimes at random too.
3. USB storage doesn't work through Android.... ( I don't know if this is normal too). When I plug it on PC it just charges. (Note: I now see that other devices have this problem too. I found a partial workaround in the MMX Canvas HD cm10.2 section)
PS. Would logcat help in any of these problems?
--------------------------------------------------------------------------------------------------------------------------------
I moved on, and took some adb logcats.
1. I took the audio.txt as follows: started logcat, pressed play on the apollo widget, pressed pause, stopped logcat
2. I took the signal.txt as follows: started logcat (while on Airplane mode), disable Airplane mode (from quickSettings tiles), enable mobile data, disable mobile data, enable Airplane mode, stop logcat
I'll look at logs meanwhile I never had problem with signal, speaker audio and images. To get USB storage working add these lines to build.prop and reboot
persist.sys.usb.config=mass_storage,adb
persist.sys.usb.config=mtp,adb
For signal issue , did u replace your modem.IMG in CM ROM ?
For image issue try those 2 files from wiko ROM.
Edit:
Try to freshly port CM once again as given in guide with some changes in meta-inf and build.prop as I gave. If you still have problems then report here.
I couldn't debug audio log but in signal log > network is disconnected as data is enabled and even it's saying messaging settings are false. There may be issue with modem.img
sent from my iris458Q using XDA mobile app
Thanks for the USB storage tip. At least the internal SD can be seen now by the computer.
Images are OK now with the lib of CM.
For signal issue I copied modem.IMG from stock into the CM rom, and still having problems.
Btw, I just created a new thread for my device, I hope this is not a problem.
http://forum.xda-developers.com/and...cubot-gt99-t2834832/post54542482#post54542482
Cheers !! I'll add your device in the ported list. As I said previously all necessary files should be replaced in CM to be bug free except major BT,camera,hwcomposer,FM,GPS,2nd Sim bugs.
Also USB storage is buggy now as SD card is unmounted in mass storage mode but not mounted on PC and when disconnected from PC it doesn't get mounted and you have to reboot to get it working on android. Also mtp mode sometimes doesn't work
sent from my iris458Q using XDA mobile app
Nice!
The only file missing is /lib/libmedia.so and I 'm starting to think that this may be the cause of the sound bug. But when I copy it from the stock rom, I get boot problems...
Anyway, thanks for your help, and sorry that I messed up/spammed your thread. I think the most important part of the job is done..! Good job!
EDIT: I think I sort of fixed the mobile network issue. I used a modem.img from another version of stock rom and it seems to work. However I still get the error "Restricted Access changed. Data service is blocked." But I have full signal and 3G! It's something!
Restricted access notification occurs if you enable or disable data and turn on/off airplane mode and phone and it is not a issue I think. It may be cyanogenMod's security message or something.
Also try libmedia.so from other
Stock rom which you said above.
sent from my iris458Q using XDA mobile app
thanks for repley
4shreyas said:
@limam27 boot loop occurs if 1) boot.IMG is badly repacked 2) any file is missing from your device stock rom which has to be copied to CM ROM as mentioned in the guide. Check them first . Also Check whether you are getting errors during unpack and repack of boot.IMG.
Sent from my iris458Q using XDA mobile app
Click to expand...
Click to collapse
I want to port my device MT6589T JB 4.2 to cm11 kitkat but I do not know how to activate the binder c in the boot.img.
I've tried without a binder c install process always aborted status 7
please help thank you
Hello @limam27
@Iimam27 said:
I want to port my device MT6589T JB 4.2 to cm11 kitkat but I do not know how to activate the binder c in the boot.img.
I've tried without a binder c install process always aborted status 7
please help thank you
Click to expand...
Click to collapse
You can't patch binder.c from boot.IMG. You must be having kernel source for your device and you must patch binder.c in kernel. If you don't have kernel source then its almost impossible to get KitKat. See if your device clones have kernel source for their device. Else look for almost similar specs device with same processor. My device has mt6589m but no source from vendor. I used similar mt6589m device's source to build kernel. Now CM 11 is booting but no display due to different GPU config. So it's really hard if you don't have source. Try with CM 10.2 first .
EDIT- Previously I have told why you get status 7 error. So read whole thread before posting here. Good luck
Sent from my iris458Q using XDA Premium 4 mobile app
Infocus M810/T/U thread. (Also wth interesting things for m812 holders.)
Infocus m810 thread on facebook
Note:
All roms on this page are remade to use with Infocus m810 so don't flash on m812. MULTILANGUAGE
Bootloader unlock (m812/m812):
Custom recovery (m810/m812):
SUT flashable images (SUT Factory tool 3.0.8):
SUT 3.1.4 cracked.
Video tutorial SUT flashing on Android 6
ROMS M812(A/I) VN2/PHX:
Android 5.0.2 m812 OFFICAL sut. (Suitable for m810 too) to be used with SUT
cm13 for m812(a) http://forum.xda-developers.com/showpost.php?p=68355126&postcount=1110
ROMS M810(T/I/U):VNA
25/07/16 CM13 beta 2 (release) http://forum.xda-developers.com/showpost.php?p=67901403&postcount=1074
20/03/16 Android 6 custom ROM (ported from m812 ver 617A firmware)
23/02/16 Android 6 custom ROM (ported from m812 ver 6130 firmware)
27/12/15 Android 5.1.1 (internal version 511C(D updated)) (port from m812 ver 511C firmware)
Official Android Kitkat 4.4.2 (VNA-1640-0-00WW-A02)
Older roms
Older ROMs are designed for recovery installation and need some knowledge:
Before the installing of thiose ROMs you must be common with Adb/fastboot driver and installation. working fastboot.exe and adb.exe here
Im the author of this work. So feel free to ask and report.
All you install from here is on your responsibility.
m810.ROM Android 5.0.2: (October 2015) MULTILANGUAGE.
This ROM is full upgrade, so its able to install over Android 4.4.2 ROMS.
How tot install: Russian installation site
1. Put the zip file to sdcard.
2. Connect phone by USB cable. Press and hold volume down+power buttons
(10s), when phone restarts, release power button after vibrating and keep
holding volume down button until FASTBOOT message appear on screen.
3. Download boot recovery https://yadi.sk/d/v_LrtBVdk8pAj and place in fastboot/adb
folder
4. Run in cmd: fastboot boot tw101_recovery_repack_by_titovich.img
5. When recovery booted, Choose firmware UPDATE502_M810_v1.zip and
install.
In the end you should get this error: apply parsed perms lsetfilecon from
/cache to u_object_r:cache_file:s0 failed operation not supported on transport
endpoint set_metadta: some changes failed.
Ignore it. Its issue of recovery.
6 Besides, ROOT and Xposed for 5.0.X framework preinstall can be copied to
sdacard and installed same time after rom installed from boot recovery.
7. Hold power button 10 sec and reboot.
Enjoy.
5.0.2 DOWNLOAD
m810.ROM Android 5.1.1A 08/10/15 The beta version of Lollipop
5.1.1A
ROM from official 511A m812.
Same install instructions as above
Main changes
-Wifi reception better;
-GPS;
-Added buttons config, e-compass, g-sensor calibrations to display menu .
5.1.1 DOWNLOAD.
XPOSED for 5.1.1 . ROOT
Note Xposed from version 5.0 and 5.1 are different!
To flash via SUT:
ODEXED ROM Android 5.1.1B 11/15 The beta version of Lollipop
5.1.1B from official m812 511B update ROM. |For SUT installer. With
unbricking feature.
- ROM designed for odexed files so it contains resized partition for system
(by titovich). means one you install the partition table will remain - 2.5gb for
system. original system parttion is less 2gb. You will be able to install all
m810 roms but I noticed you.
-not for XPLOSED framework. The ROM is full odexed. So don't try Xposed it
will fail;
-minor changes from my side diff to previous ROM;
-fixes from Infocus to battery life.
bugs: haptics not working for hard buttons (to be fixed)
To be installed via SUT utility SUT 3.0.8: DOWNLOAD
-install SUT (drivers will be installed with SUT);
-download zip with nb0 image. Unzip.
-open nb0 image file in SUT.
-Check "Normal Download" and "Erase data".
-Download ignore warning messages.
-Flash will complete in less than 1 min.
5.1.1B for SUT DOWNLOAD LINK2
EOL
Tweaks and enchantments :
M810 service manual
http://forum.xda-developers.com/showpost.php?p=68520451&postcount=1123
Edit boot logo m81X
http://forum.xda-developers.com/showpost.php?p=68956713&postcount=1163
Other party hears the noise durine the phone call
build.prop file
persist.audio.fluence.voicecall=false
Secret codes:
*#*#4636#*#*, *#*#653837#*#*, *#*#76278#*#* Settings.
Note, never tap "USA Band", otherwise you will need to reflash modem part or firmware to make phone back to work.
*#*#873#*#* Upload service
*#*#225#*#* Calendar
*#*#2324636#*#* , *#*#232#*#*, *#*#23273#*#* ,*#*#233#*#*, *#*#231#*#*, *#*#2324678#*#* CDA
*#*#278#*#* CPUDaemon
*#*#324#*#* DebugCfg
*#*#368#*#* Device manager
*#*#3721#*#*, *#*#6721#*#*, *#*#372#*#*, *#*#672#*#*, *#*#4867#*#* High Temperature Monitor
*#*#744#*#*, *#*#628#*#* Mobile Assistant
*#*#787#*#* PackageUsageTool
*#*#227#*#* Pandora Box
*#*#272#*#* Permission Control
*#*#33546#*#* Permission Detection
*#*#793#*#*, *#*#795795#*#* Power Detective
*#*#795#*#* power Monitor
*#*#277#*#*, *#*#3277#*#* Stability Monitor
*#*#28274663#*#* TeleService
Themes pack for 511B/C:
http://forum.xda-developers.com/showpost.php?p=64725810&postcount=429
Disable buttons backlight. (pale blue led shine instead). ROOT needed.
Replace system\lib\hw\lights.msm8974.so to get rid of buttons backlight. Instead, PALE blue led will be on.
Don't forget to backup the original file.
Advanced users can control that API /sys/devices/virtual/input/touch/light_led (with echo 0,1)
There is no any other control to disable or enable it.
XPOSED framework can't do anything too
Noise fix. When party on other side is claiming on noise above your voice.
This is typical issue of dual mic QUALCOMM devices on 5+ Androids. Edit built.prop
persist.audio.fluence.voicecall=true change to false
Enable DIAG port for QXDM (QPST). Rooted.
adb shell
su
setprop persist.sys.usb.config diag,serial,mass_storage,adb
Increase speaker volume
http://forum.xda-developers.com/showpost.php?p=64566136&postcount=330
Sound volume mod working on m810
https://www.youtube.com/watch?feature=player_embedded&v=DOo7sT_JIs8
IMEI, Serial number, MEID, MAC, BT changer. Service tool (m810/m812) DANGEROUS!!!
https://drive.google.com/open?id=0B3Wy4Ok3qGszcmZlMDFCbGdwUjQ
I was trying to follow up this conversation on 4pda but i don't speak russian and google translate does a terrible job.
So a couple of questions:
Is this a multilanguage rom?
Does 2g-3g-4g work?
What about wifi?
Thanks.
will Infocus m810 get android 5.1???
there is an ota update for m812 to android 5.1 but i am unable to find the file.
My phone its on the way.Im interesting this thread
sknipas said:
I was trying to follow up this conversation on 4pda but i don't speak russian and google translate does a terrible job.
So a couple of questions:
Is this a multilanguage rom?
Does 2g-3g-4g work?
What about wifi?
Thanks.
Click to expand...
Click to collapse
Yes, its Multilanguage.
2g-3g-4g work
sknipas said:
there is an ota update for m812 to android 5.1 but i am unable to find the file.
Click to expand...
Click to collapse
If you find it, pls share, it can be used for further development.
@ heineken78
Thanks for coming here at XDA
I am daily following your good works at 4PDA and I am actually with Titovich's 5.02 rooted and i feel more than satisfied.
I take the opportunity to send you my grateful Thanks.
I will install the new update and let comment as well. I hope and wish the system repartitioning will not give any issue ( I don't like playing with root partition!!).
Question: Was not possible to make the system file as lean as possible , eg removing apk that are unnecessary or available at Playstore for everybody choice in order to avoid this modification.
Regards
good work bro. looking for rom based on 5.1 . following this thread
lolo9393 said:
@ heineken78
Question: Was not possible to make the system file as lean as possible , eg removing apk that are unnecessary or available at Playstore for everybody choice in order to avoid this modification.
Regards
Click to expand...
Click to collapse
Stock reserved place in m810 for system partition is ~1,6 gb. Making firmware less, won't bring any changes, unless repartitioning it to lets say 1,1 gb. This operation needs lot of system knowledge from people who will install it.. And profit of changes will be only 500 mb? is nothing.
m812 has partition of 3 gb, that's huge, but suitable for oxdexed roms.
repartition means- you need to change start sectors of emmc in order to set sizes of system, cache. Everything before those partitions remain the same.
Ok, tweak as promised
http://forum.xda-developers.com/showpost.php?p=63576292&postcount=2
Wow,wonderful news... i will test it,downloading...
Hi Guys!
I would like to ask that ROM by titovich, which languages contains?
Thanks
@ heineken78
I've just finished the new Rom install. I followed instructions and had no issue . Rebooted via recovery and installed my stuffs.
-Wifi reception is the same as before and always weaker than my other phones. (minus 8 db)
-GPS IS NOT GETTING ANY FIX. 25 SAT in view and no one fixed.
-New Rom is a HUGE bit of improvement and feel more pleasant and very fast.
-DISPLAY is vibrant and very well set. Automatic mode is perfect also at night reading. good
- Battery leak in stand by is impressively low. less 1% full night. very good
THANKS TO THE TEAM BUILDING FOR THIS REALIZATION.
Can we suggest next challenge to make unlock the 3G 900Mhz Euro Band N°8 in a practical way?
I care less about the 4G...
---------- Post added at 03:52 AM ---------- Previous post was at 03:40 AM ----------
[email protected] said:
Hi Guys!
I would like to ask that ROM by titovich, which languages contains?
Thanks
Click to expand...
Click to collapse
Indonesian/Deutch/ENGLISH/Espanol/Filipino/FRENCH/Portugues/VIET/Russian/chinese/ and 2 symbolic i can't know ....sorry may be Hebreu,
lolo9393 said:
Can we suggest next challenge to make unlock the 3G 900Mhz Euro Band N°8 in a practical way?
I care less about the 4G...
---------- Post added at 03:52 AM ---------- Previous post was at 03:40 AM ----------
Click to expand...
Click to collapse
Yes Im trying that.
But for now, "adb reboot ftm" to reboot in ftm mode and enable qualcomm diag driver.
Then change nv's as written here and here. Uz mztool to calculate right entry's.
@heineken78
Thanks dude!
Its an official or unofficial translated ROM?
Im just ask the reason of hope, maybe put into some more languages too.
Im get this phone yesterday, it looks really great, but enter the recovery and fastboot mode its terrible.
Do you know TWRP or CWM recovery for this phone?
ilhi, i tried to disable backlight with .rar file you attached and it does work but i
heineken78 said:
TWEAKS:
1. Disable buttons backlight. (pale blue led shine instead). ROOT needed.
Replace system\lib\hw\lights.msm8974.so to get rid of buttons backlight. Instead, PALE blue led will be on.
Don't forget to backup the original file.
Advanced users can control that API /sys/devices/virtual/input/touch/light_led (with echo 0,1)
There is no any other control to disable or enable it.
XPOSED framework can't do anything too
Click to expand...
Click to collapse
ilhi, i tried to disable backlight with .rar file you attached and it does work but i can't adjust screen brightness in settings. Now its full bright and can't switch it low or automatic
a1dahiya said:
ilhi, i tried to disable backlight with .rar file you attached and it does work but i can't adjust screen brightness in settings. Now its full bright and can't switch it low or automatic
Click to expand...
Click to collapse
Dude, this is patched driver the from the build on first page. Drivers are different on stock502(titovich) so you may have an issue.
what should i do please help me
heineken78 said:
Dude, this is patched driver the from the build on first page. Drivers are different on stock502(titovich) so you may have an issue.
Click to expand...
Click to collapse
What should I do, please help me out
---------- Post added at 08:46 AM ---------- Previous post was at 08:38 AM ----------
a1dahiya said:
What should I do, please help me out
Click to expand...
Click to collapse
What drivers to change or any other change of value .....?
I'm on stock lollipop 5.0.2 rooted
I also tried to replace the patched file with original which I copied before replacing but nothing helped
The intention behind this thread is to share some experience of a little project where I try to migrate the Sony Xperia Shinano devices (based on Qualcomm MSM8974 chipset with a Broadcom BCM4339 wifi/bluetooth chip) from the old bcmdhd wifi driver to a close-to-mainline brcmfmac driver. I want to share the progress and status here, and maybe get some hints. It is work in progress, and for sure it still contains some mistakes - I haven't done something like this before and am still learning.
Why?
The Shinano devices are still maintained by the LineageOS, and some devices are currently on the official LineageOS 17.1 stream.
The kernel however is terribly outdated, based on msm-3.4
There are some wifi issues with all LineageOS-based ROMs since years, like weak 5GHz connections and non-working wifi in some countries. There are some hacks around that, but they work (afaik) by practically disabling the kernel-level regulatory system by e.g. setting a static country code like "DE".
I am curious if we can improve that by updating the kernel drivers and network/wifi components, and maybe also the firmware (to the latest release available from Broadcom, 6.37.34.43 ?) . I got the ideas from Sonyxperiadev/Loire (+ related platform config), the Linux Backport Project and other MSM8974 based devices.
Working so far:
Did a few tests only so far, STA with WPA2 and p2p (hotspot) seem to work
Wifi connection is stable on 2,4GHz on 00 world regulatory domain (tested on a Z3 and a Z3c)
5GHz manually setting a country code (could only test DE)
Switching countries / setting new regulatory domains is now working, too
Download speed looks OK to me, in my case at least better than before Download >60MBit, Upload >30 Mbit on some initial tests.
Not working yet:
WifiHAL (qcom-caf) does not work correctly. This may create multiple issues, tbd.
Connection bandwidth seems to be not reported correctly
I don't know if wowlan works (interrupts working?)
Stability: After 1-2 days without reboot wifi sometimes crashes but immediately reconnects. Reason not yet understood.
Patches & Picks
Kernel:
backported and configured brcmfmac, cfg800211 wireless configuration API and wireless network stack from linux-stable v5.8 by adopting the compatibility patches from the linux backporting project.
updated Shinano device tree, updated Z3, Z3c and Z2 (Z2 test needed!) defconfigs (unset bcmdhd and enabled brcmfmac) and removed board-sony_shinano-wifi.o in the arch-msm makefile
Note: the backported drivers and compatibility-patches are located in a separate backports/ subdirectory
Sorry, this is work in progress and contains some hacks, to be cleaned up later
--> https://github.com/LineageOS/androi...1...Tom1000:lineage-17.1-driver-backport-v5.8
Vendor blobs / device z3(c): removed proprietary firmware and replaced that by publicly available firmware for bcm4339 on linux-firmware.git
z3c --> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
z3 --> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
Shinano-common: Use qcwcn instead of bcmdhd WLAN device, serve wpa_supplicant_overlay.conf
--> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
msm8974-common: raise wpa_supplicant version (unknown if we need that) and update sysfs node for MAC address
--> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
As a follow up, the driver seems to work quite stable already. I still have issues with nl80211 private commands, as a mainline brcmfmac does not seem to accept command strings passed via a libnl control socket like this:
qcwcn/wpa_supplicant_8_lib/driver_cmd_nl80211.c
@vknecht : I've seen your backporting work for the Xperia X. How does this work for Loire with SODP? Does e.g. a "set country code request" work for you, and if so, can you give me a hint?
I need some feedback from people with a Z3/Z3c/Z3Dual to see if the new builds work in affected countries, where 5GHz wifi is not working on current custom ROMs like e.g. LineageOS 17.1. I would appreciate if you test one of the builds below and send me a full log.
WARNING: The following builds are for debugging purpose only. Do not use them as a daily driver, as they have SELinux disabled and create excessive log entries. This ROM is not stable, some features are not yet implemented.
Xperia Z3 (D6603):
lineage-17.1-20201227-UNOFFICIAL-z3.zip
drive.google.com
Xperia Z3c (D5803):
lineage-17.1-20201227-UNOFFICIAL-z3c.zip
drive.google.com
Xperia Z3Dual (D6633) Update 10Jan2021:
lineage-17.1-20210110-UNOFFICIAL-z3dual.zip
drive.google.com
Z3Dual build has SELinux enabled already
If possible, please follow these steps:
Install ROM with TWRP for Android 10 or Lineage Recovery for 17.1
If possible, factory reset the device. Be sure to get rid of all former Magisk modules which try to set country codes etc. (if applicable).
Make sure a a local SIM card is inserted.
Boot the device. Enable mobile data and enable wifi. Connect to a 5GHz capable access point or router.
Optional: Increase log buffer size. This may be required as the kernel is set to verbose logging, creating large logfiles. You can do this via settings/developer options or via adb:
adb logcat -G 8M
Get close to the access point or router, so that the device would prefer 5GHz over 2.4GHz.
Reboot the device and let wifi connect. Check if device uses a 5Ghz connection. (Ignore bandwith / speed for now.)
Create a logfile, e.g. with this command via adb:
adb shell logcat -d -b all > mylog.log
The logfile may contain private information, so I recommend not to post them public. Together with the ligfile I would like to know
a) Wifi 5GHz working?
b) The country in which you have tested this.
nice work bro.
i live in iran and in this build my Z3 Dual detects wifi networks while the sim card is also connected.
but in 10 Jan 2021 update my phone can't detect my router's wifi unfortunately while the previous build could do it without problems.
hotspot turns on on both 2.4GHz and 5GHz.
in this new build cellular network and data are working.
Thanks @TheShadowOfAGhost20 !
Can you please run a root shell (E.g. by connecting via ADB, run adb root, then adb shell) and then
$> iw wlan0 scan → scan for networks
and then look if your access point is found?
Furthermore, can you please check which WiFi channel this particular router ist set to, and if possible the bandwidth?
Mr.Tom_Tom said:
Thanks @TheShadowOfAGhost20 !
Can you connect via ADB, run adb shell and then
$> iw wlan0 scan → scan for networks
and then look if your access point is found?
Furthermore, can you please check which WiFi channel this particular router ist set to, and if possible the bandwidth?
Click to expand...
Click to collapse
i did that but got this error: "/system/bin/sh: iw: inaccessible or not found"
but i found the cause: my wifi channel was set to 12. i changed it and then got detected!
TheShadowOfAGhost20 said:
i did that but got this error: "/system/bin/sh: iw: inaccessible or not found"
Click to expand...
Click to collapse
Sorry I forgot to write that you have to do this as root, I edited the post accordingly.
TheShadowOfAGhost20 said:
i found the cause: my wifi channel was set to 12. i changed it and then got detected!
Click to expand...
Click to collapse
Tha sounds reasonable. However, Channel 12 should be usable in IR.
Mr.Tom_Tom said:
Sorry I forgot to write that you have to do this as root, I edited the post accordingly.
Tha sounds reasonable. However, Channel 12 should be usable in IR.
Click to expand...
Click to collapse
channel 13 has detection problem too. the others are OK
.sorry erroneous post
New buildsFeedbacks have been positive so far, so here are some updated builds.
Lineage Sources* as of 20 March 2021
Kernel sources* based on Linux 3.4.113 with backported wifi from 5.8.18 plus cherry-pick of the following changes:
bluetooth: fixed #ifdef'ed PM callbacks ("BTLowPower" wakelock) 50f16d16b32871c5ce97b029e68692008c848bb2
SELinux enforcing
Build as userdebug, normal loglevels
* For links to sources see 1st post. Z3Dual does not have official Lineage17.1 sources yet, bringup is in progress.
Xperia Z3 (D6603):
HiDrive
hidrive.ionos.com
md5: d7aaf1fea120df3e2aad10b3a2d32226
Xperia Z3c (D5803):
HiDrive
hidrive.ionos.com
md5: 456ff87441c3a63e8dc8c7a8d03bdf39
Xperia Z3Dual (D6633):
HiDrive
hidrive.ionos.com
md5: 1848681c82d608f3212f1ace621327cb
As always, feedback is welcome.
Has anyone found a bug/installed this latest build yet? lineage-17.1-20210320-UNOFFICIAL-z3dual
Finding this super stable.. The only thing that does not work for me is the advanced boot recovery that goes back into system, But that's a known issue.
Mr.Tom_Tom said:
New buildsFeedbacks have been positive so far, so here are some updated builds.
Lineage Sources* as of 20 March 2021
Kernel sources* based on Linux 3.4.113 with backported wifi from 5.8.18 plus cherry-pick of the following changes:
bluetooth: fixed #ifdef'ed PM callbacks ("BTLowPower" wakelock) 50f16d16b32871c5ce97b029e68692008c848bb2
SELinux enforcing
Build as userdebug, normal loglevels
* For links to sources see 1st post. Z3Dual does not have official Lineage17.1 sources yet, bringup is in progress.
Xperia Z3 (D6603):
HiDrive
hidrive.ionos.com
md5: d7aaf1fea120df3e2aad10b3a2d32226
Xperia Z3c (D5803):
HiDrive
hidrive.ionos.com
md5: 456ff87441c3a63e8dc8c7a8d03bdf39
Xperia Z3Dual (D6633):
HiDrive
hidrive.ionos.com
md5: 1848681c82d608f3212f1ace621327cb
As always, feedback is welcome.
Click to expand...
Click to collapse
hi mr.tom. it's perfect as always, found no bug except wifi signal power, it's weak compared to stock roms but there was no difference in speeds. maybe it's because of wifi icon that shows little weaker signal.
and about overheating: i didn't test this build for long but while working with it i have noticed that my device is cooler than previous builds, maybe it's because of this new kernel.
i have recorded 4k for about 7 minutes then my phone rebooted i think that was because of too much heat, then i've reinstalled stock rom, however, stock rom's camera won't let me record much and the app shuts down because of heat, so i can't find out if stock rom can record 4k at least without rebooting.
i need to test this build for more time i hope the heating is now gone
and one question: can you port cyberian camera mod for these roms? or is that possible?
netwave said:
Has anyone found a bug/installed this latest build yet? lineage-17.1-20210320-UNOFFICIAL-z3dual
Finding this super stable.. The only thing that does not work for me is the advanced boot recovery that goes back into system, But that's a known issue.
Click to expand...
Click to collapse
lineage os recoveries have these problems yet, there's no fix for that, only the developer can fix it. currently the twrp works if you flash it to FOTAKernel partition but i think the twrp is useless because it doesn't install these builds.
Surely better to do: fastboot boot recovery-20201012-TESTING-z3dual.img rather than a "flash" recovery. What would be the point in flashing a recovery if its not working.
Hey
Thanks @Mr.Tom_Tom for new build and @TheShadowOfAGhost20 for testing dev builds!
today i installed the new release
but i have some problems with recovery and boot
after installing Lineage i cannot boot to recovery again
i tried adb, android advanced boot options and "fastboot boot image.img"
none of them taken me to recovery mode
so i needed to install Magisk , OpenGApps , and rom itself with adb sideload and reboot to system because i can't boot to recovery again
i'm now installing my apps for daily usage testing - i need about one or two week to test and use and see if anything is wrong or not
for now WiFi problem is gone , i have full wifi access and both sims antenna
again , thanks to everyone puts effort on this project (and sorry for bad English)
i will update this post if i found anything
navidmafi said:
today i installed the new release
but i have some problems with recovery and boot
after installing Lineage i cannot boot to recovery again
i tried adb, android advanced boot options and "fastboot boot image.img"
none of them taken me to recovery mode
Click to expand...
Click to collapse
If your going to settings\system\developer options\advanced restart\power\restart recovery , Forget it! this method doesn't work for now, & will only boot you back into Lineage. It's an issue that hopefully get's fixed in the future.
But here's a better way of entering recovery without having to flash it...
Check all your drivers are installed correctly & make sure you have the correct recovery to hand.
Here's what I Command:
adb devices
adb reboot bootloader
fastboot devices
fastboot boot recovery-20201012-TESTING-z3dual.img
Good luck!
Hey again
Thanks to @netwave i can now boot to recovery without problems by going to fastboot from adb , and booting image directly by "fastboot boot"
while using devices after installing new release , i have a problem with WiFi connectivity
when i lock the screen by power button , the wifi disconnects
for example i use whatsapp a lot and when screen is locked wifi is not connected
i checked power settings - and even set the battery profile to "Quick" (and battery saver is off) but it did not help
is this a bug or a feature?
navidmafi said:
Hey again
Thanks to @netwave i can now boot to recovery without problems by going to fastboot from adb , and booting image directly by "fastboot boot"
while using devices after installing new release , i have a problem with WiFi connectivity
when i lock the screen by power button , the wifi disconnects
for example i use whatsapp a lot and when screen is locked wifi is not connected
i checked power settings - and even set the battery profile to "Quick" (and battery saver is off) but it did not help
is this a bug or a feature?
Click to expand...
Click to collapse
Have you tried without Magisk installed? Don't use v22.0 what ever you do as it disables WiFi
Ow
I'm using Magisk and it is version 22.0
and even root not works
should i reflash ?
Edit : Ok i'm flashing again now
navidmafi said:
Ow
I'm using Magisk and it is version 22.0
and even root not works
should i reflash ?
Click to expand...
Click to collapse
Install the Magisk uninstall.zip from recovery
when your back in Lineage your still have a disabled WiFi as Magisk does not uninstall correctly.
So Install the original boot extracted from the Lineage.zip to get things working again.
- adb devices
- adb reboot bootloader
- fastboot devices
- fastboot flash boot boot.img
- fastboot reboot
Then your be sorted.
I have prepared hybrid ROM 1.04 / 1.05 (Android 9) -> its suitable for T1P2, T1P3, T1P4 version of Teclast T30
Its based on official global ROM 1.04 and chinesse 1.05 ROM.
In the folder with firmware 1.05, I replaced the scatter file and system.img from firmware 1.04.
The result is:
Version 1.0: firmware 1.04 with Google Play store and 60 Hz screen frequency, MUCH better touch response, containing all languages.
Version 1.1: same as version 1.0 + Magisk (ROOT) pre-installed
Version 1.2a: same as version 1.0 + TWRP 3.3.1 pre-installed
The big advantage of this procedure is the standard easy installation of the firmware via Flashtool.
Download:
look to attachments
Installation 1.0:
- Unpack FlashTools, and Click on Flash_tool.exe
- Select "scatter-Loading" and search MT6771_Android_scatter.txt in ROM
- Wait file to be added into Flash Tool
- Select "Firmware upgrade"
- Turn off your tablet.
- Press “Download” button to start
- Connect your tablet into the computer via USB data cable.
- The process will start and a red progress bar will appear after color purple, yellow.
- And green circles display
- Finish !
- Reboot System
Installation1.1:
- Unpack FlashTools, and Click on Flash_tool.exe
- Select "scatter-Loading" and search MT6771_Android_scatter.txt in ROM
- Wait file to be added into Flash Tool
- Select "Firmware upgrade"
- Turn off your tablet.
- Press “Download” button to start
- Connect your tablet into the computer via USB data cable.
- The process will start and a red progress bar will appear after color purple, yellow.
- And green circles display
- Finish !
- Reboot System
- Install Magisk Manager v7.5.1 or Magisk Manager v8.0.3
Installation 1.2a:
- Unpack FlashTools, and Click on Flash_tool.exe
- Select "scatter-Loading" and search MT6771_Android_scatter.txt in ROM
- Wait file to be added into Flash Tool
- Select "Download only"
- Turn off your tablet.
- Press “Download” button to start
- Connect your tablet into the computer via USB data cable.
- The process will start and a red progress bar will appear after color purple, yellow.
- And green circles display
- Finish
- - Wait aprox. 20 seconds
- Do not start tablet by normal way!!!
- To go to TWRP start the tablet by pressing and holding the Power and Vol+ buttons simultaneously, until text menu on tablet will appears
- On the tablet screen, use Vol+ to select "Recovery Mode", confirm the selection with the Vol-
- To control the TWRP connect the mouse to the tablet, because touch do not work in TWRP
- Click Cancel when prompted for a password
- Click on Wipe / Format Data / Swipe to confirm
- On question enter "yes"
- Click Back (3 times) and click to Reboot / Recovery!!!
- Install "DisableForceEncryption_Treble.zip"
- Install Magisk 21.1
- Click Reboot System
- Install Magisk Manager v8.0.3
- To easy access to TWRP instal Recovery reboot application
Note. Unfortunately, the touch does not work in TWRP, so a mouse and USB adapter must be used
If someone has a problem with Flashtool, fails to burn ROM to tablet, try install drivers " MTK_USB_All_v1.0.8.zip"
- unzip archive
- run file "MTK_USB_All_v1.0.8.exe"
- it will create desktop folder "MTK Usb Driver v1.0.8"
- run file \MTK_Driver_ ext\DriverInstaller.exe
- it will install drivers
- restart PC
- done
Edit 8. january 2021
Because XDA Admid removed my external download links I had to upload all files to attachments.
As a backup, all files are stored here also
to all T30 owners out there that suffer from touch-screen lag: rtb07 did a phenomenal job in creating this hybrid rom that fixes the issue. Installation is easy to do, just follow the above instructions.
I fixed my T1P2 EEA T30 using the 1.2a hybrid rom and could not be happier with the result. It is working like a charm now.
THX to rtb07!!!!
Welcome. Thank goodness I managed to correct that annoying touch mistake.
I would love to do installation 1.0 on my T1P2 but all the download links have been removed :/
Vandal4125 said:
I would love to do installation 1.0 on my T1P2 but all the download links have been removed :/
Click to expand...
Click to collapse
Because the XDA administrator deleted my external links to the files, I had to upload everything to the first post.
So now is all OK.
Thanks for this. I preordered this tab at launch in late 2019 and hated the touch response and just overall laggy feel, so it's been sitting in a drawer for over a year. This firmware actually makes it nice and smooth, also extremely simple to flash.
Yes, in my ROM version the touch finally works fine. It is tragic that Teclast only fixed this in the Chinese version 1.05 ROM and did not release a corrected version of the EEA / Global ROM. When I wanted to work normally with the tablet, I had to make a corrected version of Global ROM 1.04.
It is a pity that the manufacturer does not release new updates.
rbt07 said:
It is a pity that the manufacturer does not release new updates.
Click to expand...
Click to collapse
I bought 3 Chinese tablets from different company’s & not one of them have been updated by the makers, but my 2 years old Samsung S9 South Korean phone still getting updates.
Its really is poor customer service when they can easy fix the problems, thankfully there people like you around to do there job for them!
Hi!
First of all, thanks for your great work. I have ghost touch in my Teclast T30 and I've been looking for a solution for weeks. Some days ago I found this post and installed the 1.0 version, that should fix my touch-screen issue. The installation was succesful, but still having the same problem. Ghost touch in the bottom side. ¿What can I do to fix this? I have the T1P2 version.
Thanks!
Hi, I don't know if anyone else is reporting a problem with a ghost touch on our tablet. I have not encountered this problem. They all reported only a problem with low touch sensitivity, which was solved by this hybrid ROM.
Maybe you could try peeling off the protective film. But I don't guarantee it will help.
Does physical keyboard work with hybrid rom?
Yes!
This hybrid ROM saved my T30. What a fantastic work Sir rbt07! The screen response is now super fast. After installing the version 1.0 I spent over a hour scrolling up and down just trying to believe in what I was seeing. It became a much better tablet now. Btw I got stucked in the 0% format during the flashing process and had to install the MTK drivers on my laptop. I only installed the last driver "we had three folders there" and then I could complete the installation. You should invoice Teclast to pay you for your work. Thanks a lot mate!
jagoooodka said:
Does physical keyboard work with hybrid rom?
Click to expand...
Click to collapse
Yes it does work with the physical keyboard, I tested it myself
I'd like to thank you OP, this made my tablet actually able to play rhythm games to an acceptable degree. I didn't like to flash other ROMs because they all have a common issue: bluetooth connection. This ROM works flawlessly on my T1P3 by using it for 3 days.
Hybrid ROM is just a mix of two original ROMs, so it doesn't have many bugs.
Hi, do I need to unlock or do anything to my device before I can follow these instructions?
fieldmar said:
Hi, do I need to unlock or do anything to my device before I can follow these instructions?
Click to expand...
Click to collapse
It is not necessary to do nothing more, just follow instructions.
Hello @rbt07 ,
Thanks for the awesome rom
Works like a charm