Related
I can't post to the development section because i'm new here, so feel free to move this thread
I've found some really interesting things around the internet.
I got an mt6573 device half a year ago(Star A920) and ported over some ROM'S.
Now i wan't to get deeper, the problem is the sourcecode from mediatek. Alcatel has released its sources (OT918d, OT991d) which are mt6573 phones. For building the mediatek Android, we need other files, which were not included in their sources.
Now it's getting interesting:
I've found this on the internet:
www.github.com/fanjunwei/mytqe
It seem like this is the development environment for the ALPS MTK builds.
I also found this "How-To" for the environment.
http://wenku.baidu.com/view/86c3bad749649b6648d74748.html
..and the kernelsource for the alcatel 991d.
www.sourceforge.net/projects/alcatel/files/OT_991D_20120725.tar.xz/download
I'm trying to build an android from sources, maybe we are successfull together.
If I'm wrong - correct me, please.
edit: sucessfully build Android 2.3.6 from sources!!! ( ALPS.GB.FDD2.MP.V4.5 , e1101_v73_jbl1ctp_a515, Kernel Version 2.6.35.7 )
Whoa bro !
can u make a guide how to compile from sources ?
Chrizzly92 said:
I can't post to the development section because i'm new here, so feel free to move this thread
I've found some really interesting things around the internet.
I got an mt6573 device half a year ago(Star A920) and ported over some ROM'S.
Now i wan't to get deeper, the problem is the sourcecode from mediatek. Alcatel has released its sources (OT918d, OT991d) which are mt6573 phones. For building the mediatek Android, we need other files, which were not included in their sources.
Now it's getting interesting:
I've found this on the internet:
www.github.com/fanjunwei/mytqe
It seem like this is the development environment for the ALPS MTK builds.
I also found this "How-To" for the environment.
http://wenku.baidu.com/view/86c3bad749649b6648d74748.html
..and the kernelsource for the alcatel 991d.
www.sourceforge.net/projects/alcatel/files/OT_991D_20120725.tar.xz/download
I'm trying to build an android from sources, maybe we are successfull together.
If I'm wrong - correct me, please.
edit: sucessfully build Android 2.3.6 from sources!!! ( ALPS.GB.FDD2.MP.V4.5 , e1101_v73_jbl1ctp_a515, Kernel Version 2.6.35.7 )
Click to expand...
Click to collapse
it's cool!!
can you make a tutorial for comiling android from source?
look at the second link i've posted. there is an complete tutorial. (setting up a virtual machine, for example). you have to use "./makeMtk baoxue r" to build the komplete system with recovery, boot.img etc.
then u need some cust_xxx.c files from the alcatel sources, or the build fails. ( copy them manually to the folders, shown in the error logs of the builds).
I have to get deeper into it, maybe compiling a new kernel for our devices. Sure I will make an Tutorial, but at first i have to know exactly what im dooing. I hope someone else can help me, so we can get the best results out of it.
Chrizzly92 said:
I can't post to the development section because i'm new here, so feel free to move this thread
I've found some really interesting things around the internet.
I got an mt6573 device half a year ago(Star A920) and ported over some ROM'S.
Now i wan't to get deeper, the problem is the sourcecode from mediatek. Alcatel has released its sources (OT918d, OT991d) which are mt6573 phones. For building the mediatek Android, we need other files, which were not included in their sources.
Now it's getting interesting:
I've found this on the internet:
www.github.com/fanjunwei/mytqe
It seem like this is the development environment for the ALPS MTK builds.
I also found this "How-To" for the environment.
http://wenku.baidu.com/view/86c3bad749649b6648d74748.html
..and the kernelsource for the alcatel 991d.
www.sourceforge.net/projects/alcatel/files/OT_991D_20120725.tar.xz/download
I'm trying to build an android from sources, maybe we are successfull together.
If I'm wrong - correct me, please.
edit: sucessfully build Android 2.3.6 from sources!!! ( ALPS.GB.FDD2.MP.V4.5 , e1101_v73_jbl1ctp_a515, Kernel Version 2.6.35.7 )
Click to expand...
Click to collapse
Congratulations buddy, a tut by your experience shall be highly helpful
Xperia Neo V? thas NOT an mt6573 based Phone. maybe you have a chinese fake or something, then u could be right here.
Great work! what is the latest news??
Header is missing
Hi pals,
the Problem is that the repack-MT6577.pl assumes tht the needed Header information is already in the zImage, which is because normally you would pass the zImage which you extractet from a original boot.img to the script. So it will not boot until you append the Header to the zImage,
i extracted the Header with dd and build a zImage with it. Will try that out now
Edit:
the header is the first 512bytes of the original zImage
Edit2:
It boots with my custom kernel Forgot to mention my device: Alcatel OT998 (sold by Base in Germany, almost the same as OT997/OT997D)
Edit3: sorry Wrong Thread, as it is a different MTK-Platform but the info correct for you also i guess
HUELK said:
Hi pals,
the Problem is that the repack-MT6577.pl assumes tht the needed Header information is already in the zImage, which is because normally you would pass the zImage which you extractet from a original boot.img to the script. So it will not boot until you append the Header to the zImage,
i extracted the Header with dd and build a zImage with it. Will try that out now
Edit:
the header is the first 512bytes of the original zImage
Edit2:
It boots with my custom kernel Forgot to mention my device: Alcatel OT998 (sold by Base in Germany, almost the same as OT997/OT997D)
Edit3: sorry Wrong Thread, as it is a different MTK-Platform but the info correct for you also i guess
Click to expand...
Click to collapse
Again nice work!
Can you a somewhat detailed tutorial??
balamu96m said:
Again nice work!
Can you a somewhat detailed tutorial??
Click to expand...
Click to collapse
hi ,
sorry sure i can give detail, well at least i try:
1. Get the zImage from a working boot.img eg with unmkbootimg or split_bootimg.pl
2. The needed header is in the first 512bytes of the zImge extract that:
dd if=<zImgeOrig> of=header bs=512 count=1
3. Append the header to the build zImage
3.1 dd if=header of=zImageMod
2.2 dd if=zImageCustom of=zImageMod seek=512
4. Repack Boot.img with repack-MT65xx.pl as known
5. Flash through CWM:
I flash it to my device over the adb console after putting the Image on the sdcard with adb push:
dd if=/sdcard/<boot.img> of=/dev/bootimg
NOT TESTET: flashing through the cwm update-script with write_raw_image("boot.img", "/dev/bootimg");
Thats the way i got it up to boot, but i have some Problems with the permission of pvrsrvkm.ko know, i building CM10 for my Device if anyone wants to know...
i guess you can easily modify the repack-MT6577.pl to include that for fresh kernels, i will have a look at that in the next days.
Greetz HUELK
<-----THANKS Button
HUELK said:
hi ,
sorry sure i can give detail, well at least i try:
1. Get the zImage from a working boot.img eg with unmkbootimg or split_bootimg.pl
2. The needed header is in the first 512bytes of the zImge extract that:
dd if=<zImgeOrig> of=header bs=512 count=1
3. Append the header to the build zImage
3.1 dd if=header of=zImageMod
2.2 dd if=zImageCustom of=zImageMod seek=512
4. Repack Boot.img with repack-MT65xx.pl as known
5. Flash through CWM:
I flash it to my device over the adb console after putting the Image on the sdcard with adb push:
dd if=/sdcard/<boot.img> of=/dev/bootimg
NOT TESTET: flashing through the cwm update-script with write_raw_image("boot.img", "/dev/bootimg");
Thats the way i got it up to boot, but i have some Problems with the permission of pvrsrvkm.ko know, i building CM10 for my Device if anyone wants to know...
i guess you can easily modify the repack-MT6577.pl to include that for fresh kernels, i will have a look at that in the next days.
Greetz HUELK
<-----THANKS Button
Click to expand...
Click to collapse
Bad that I can't give a double thanks for your highly useful post!
Building CM 10 = awesome!
I would like to know more....cm10 with dual sim support??
Thanks again!
balamu96m said:
Bad that I can't give a double thanks for your highly useful post!
Building CM 10 = awesome!
I would like to know more....cm10 with dual sim support??
Thanks again!
Click to expand...
Click to collapse
Hi,
building cm10 with dual sim support will be complicated as there is no support for it in cm10 , my device has no dual sim but nfc instead. i now almost got it up running, the pvrdrv loads now correctly but there is some problem with some framework files and BOOTCLASSPATH variable. I think i will get it fully up today. Was awake till 6 o'clock on this .
HUELK said:
Hi,
building cm10 with dual sim support will be complicated as there is no support for it in cm10 , my device has no dual sim but nfc instead. i now almost got it up running, the pvrdrv loads now correctly but there is some problem with some framework files and BOOTCLASSPATH variable. I think i will get it fully up today. Was awake till 6 o'clock on this .
Click to expand...
Click to collapse
Great again! Hope you complete it soon!
I would somehow try to port it.....!
Hi thanks for your procedure.
I tried , i can boot but the display is very slowly. I tried with this source code https://github.com/wiko-sources/cink-king
I have a wiko cink king with mt6577.
Have you ever used repack-MT65xx.pl for mt6577?
TY
HUELK said:
hi ,
sorry sure i can give detail, well at least i try:
1. Get the zImage from a working boot.img eg with unmkbootimg or split_bootimg.pl
2. The needed header is in the first 512bytes of the zImge extract that:
dd if=<zImgeOrig> of=header bs=512 count=1
3. Append the header to the build zImage
3.1 dd if=header of=zImageMod
2.2 dd if=zImageCustom of=zImageMod seek=512
4. Repack Boot.img with repack-MT65xx.pl as known
5. Flash through CWM:
I flash it to my device over the adb console after putting the Image on the sdcard with adb push:
dd if=/sdcard/<boot.img> of=/dev/bootimg
NOT TESTET: flashing through the cwm update-script with write_raw_image("boot.img", "/dev/bootimg");
Thats the way i got it up to boot, but i have some Problems with the permission of pvrsrvkm.ko know, i building CM10 for my Device if anyone wants to know...
i guess you can easily modify the repack-MT6577.pl to include that for fresh kernels, i will have a look at that in the next days.
Greetz HUELK
<-----THANKS Button
Click to expand...
Click to collapse
@HUELK
Where you able to boot? I would like to try the process on a mtk6573
Kudos!
myphoneuser said:
@HUELK
Where you able to boot? I would like to try the process on a mtk6573
Kudos!
Click to expand...
Click to collapse
would like to help here too, already working on rom development for mt6573...
HUELK said:
3. Append the header to the build zImage
3.1 dd if=header of=zImageMod
2.2 dd if=zImageCustom of=zImageMod seek=512
Click to expand...
Click to collapse
The zImageMod and zImageCustom is confusing me. Can you differentiate between them??
Thanks.
boots now
Hi,
NEWS: got it up to boot cm10! yes display is slow for me too, but its a start
greetz huelk
---------- Post added at 11:14 PM ---------- Previous post was at 11:12 PM ----------
balamu96m said:
The zImageMod and zImageCustom is confusing me. Can you differentiate between them??
Thanks.
Click to expand...
Click to collapse
hi yes, the zImage Custum is the zImage wich resides in arch/arm/boot/zImage after you build the kernel, the zImage Mod is the Output file which will be inside the boot.img that you will flash
HUELK
---------- Post added at 11:17 PM ---------- Previous post was at 11:14 PM ----------
balamu96m said:
The zImageMod and zImageCustom is confusing me. Can you differentiate between them??
Thanks.
Click to expand...
Click to collapse
As i told you my device is a mt6577 but the changes you need should be the same, can you send me an original boot.img of your device, i will have a look.
HUELK said:
Hi,
NEWS: got it up to boot cm10! yes display is slow for me too, but its a start
greetz huelk
---------- Post added at 11:14 PM ---------- Previous post was at 11:12 PM ----------
hi yes, the zImage Custum is the zImage wich resides in arch/arm/boot/zImage after you build the kernel, the zImage Mod is the Output file which will be inside the boot.img that you will flash
HUELK
---------- Post added at 11:17 PM ---------- Previous post was at 11:14 PM ----------
As i told you my device is a mt6577 but the changes you need should be the same, can you send me an original boot.img of your device, i will have a look.
Click to expand...
Click to collapse
Thanks for clarifying my doubt!
And great to know that CM 10 booted :highfive: !
here is my boot.img : here
btw, how can the slow touch response be solved bro ??
Chrizzly92 said:
would like to help here too, already working on rom development for mt6573...
Click to expand...
Click to collapse
Hey bro,
i'm asking this, because you had cloned the full MT6573 source........Can you upload the following folders from the source's root :
Kernel
Mediatek
I need it to try my hands at the MT6573 kernel!
Thanks in advance!
I am not responsible for any damage that may or may not occur to your device.
If you use my recovery in your project link back to this thread, and give me credit in your thread for my recovery.
This is the Linux version of TWRP tethered recovery and CWM tethered recovery.
TWRP 2.8.6.0 recovery, currently tested on two tablets, venue 3830, iview -1700
screen for 1-700 is 1024x600 landscape
screen for venue 3830 800x1280 portrait
Purpose of this guide is to root intel tablets using Linux computer.
This project includes the work of people perhaps more.
This version includes 4 triggers.
@vampirefo
Linux Fastboot Binary, intel compatible cwm recovery.
http://forum.xda-developers.com/dell-venue/general/dell-venue-8-cwm-unsecure-boot-recovery-t2866925
@Chainfire
super user package update-supersu-vxxx.zip
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
@social-design-concepts
recovery.launcher, recovery.envsetup, recovery.trigger, triggers and for sharing his work.
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
http://forum.xda-developers.com/showthread.php?t=2681783
TeamWin for their great recovery
https://github.com/omnirom/android_bootable_recovery/tree/android-5.1
Download
https://www.androidfilehost.com/?fid=24052804347784850
Download release.zip extract some where, choose which recovery you want to run, rename to recovery.zip, then execute trigger choice. make sure trigger script is executable All four triggers are included in the trigger script.
1. cwm_recovery.zip
2. twrp_3830_recovery.zip
3. twrp_i700_recovery.zip
To use trigger script, open terminal in directory where files have been extracted.
Code:
adb reboot bootloader
choose which trigger you want to use.
Trigger 1
Code:
sudo ./trigger 1
Trigger 2
Code:
sudo ./trigger 2
Trigger 3
Code:
sudo ./trigger 3
Trigger 4
Code:
sudo ./trigger 4
To allow recoveries to work on more devices delete the contents of /etc, the files in /etc are for my device and other devices similar removing the contents of /etc allows @social-design-concepts tools to generate a fstab for your particular device.
Change log 7-31-2015
Twrp has been updated to 2.8.7.0
This version includes @social-design-concepts latest trigger (fbrl.trigger) and launcher (recovery.launcher), Also included is a script for Tesco Hudl 2 users, this device requires addition info to launch fastboot commands.
For Tesco Hudl 2 users use hudl2 script instead of trigger, or you can still manually edit trigger if you want.
If you would like your device added posted required information about your device.
1. Name of Device
2. Screen Size of device
3. Your device portrait or landscape mode in stock recovery?
Sent from my T1 using Tapatalk
can you tell me bug
---------- Post added at 08:28 AM ---------- Previous post was at 07:56 AM ----------
test work on zenfone 2
But flash zip not work
and only mount sdcard
can you Screen Size for zenfone 2 Full HD ?
tks
ps:UI work good
29y6145 said:
can you tell me bug
---------- Post added at 08:28 AM ---------- Previous post was at 07:56 AM ----------
test work on zenfone 2
But flash zip not work
and only mount sdcard
can you Screen Size for zenfone 2 Full HD ?
tks
ps:UI work good
Click to expand...
Click to collapse
@TheSSJ has made a TWRP recovery for your device.
http://forum.xda-developers.com/zenfone2/development/alpha-tethered-twrp-asus-zenfone-2-t3123532
Sent from my Venue 8 3830 using Tapatalk
Works good for Lenovo Yoga Tablet 2 10150F. KitKat 4.4.2 - Trigger 3, CWM only
Thank you!!!
Dell Venue 7370
Works : Trigger 1
Thank you very much for the Linux version! You saved the day for me!
Hey I forgot you... Thank you for your effort! CWM works, twrp does not. No worries.
Confirmation number: 0YV98561UW917140R
workdowg said:
Hey I forgot you... Thank you for your effort! CWM works, twrp does not. No worries.
Confirmation number: 0YV98561UW917140R
Click to expand...
Click to collapse
Did you remove the files from /etc on twrp? Anyway thanks for the donation.
Sent from my NXA8QC116 using Tapatalk
vampirefo said:
Did you remove the files from /etc on twrp? Anyway thanks for the donation.
Sent from my NXA8QC116 using Tapatalk
Click to expand...
Click to collapse
Doh... I guess I should read and reread... I'll try that now. Thanks.
---------- Post added at 12:54 PM ---------- Previous post was at 12:40 PM ----------
workdowg said:
Doh... I guess I should read and reread... I'll try that now. Thanks.
Click to expand...
Click to collapse
Still errors but works now. "FAILED (status read failed (No such device))".
Thanks
workdowg said:
Doh... I guess I should read and reread... I'll try that now. Thanks.
---------- Post added at 12:54 PM ---------- Previous post was at 12:40 PM ----------
Still errors but works now. "FAILED (status read failed (No such device))".
Thanks
Click to expand...
Click to collapse
Thanks,
I will be updating @social-design-concepts binaries in a few days, and updating the twrp recoveries.
Working - Yoga Tablet 2 - 1050F
-- Lollipop - trigger 4
-- KitKat - trigger 3
Recoveries have been updated.
Change log 7-31-2015
Twrp has been updated to 2.8.7.0
This version includes @social-design-concepts latest trigger (fbrl.trigger) and launcher (recovery.launcher), Also included is a script for Tesco Hudl 2 users, this device requires addition info to launch fastboot commands.
For Tesco Hudl 2 users use hudl2 script instead of trigger, or you can still manually edit trigger if you want.
Thanks for the update!
BTW... Links below in OP are dead or wrong...
@social-design-concepts
recovery.launcher, recovery.envsetup, recovery.trigger, triggers and for sharing his work.
http://forum.xda-developers.com/andr...p-cwm-t2975096
http://forum.xda-developers.com/show....php?t=2681783
Click to expand...
Click to collapse
Links have been changed on OP, sometimes xda changes their short links.
hello. Would like to try this on my lenovo yaga tab 3 pro.
Just wanted to know is this dangerous/chance of brick or all very temporary?
joesnose said:
hello. Would like to try this on my lenovo yaga tab 3 pro.
Just wanted to know is this dangerous/chance of brick or all very temporary?
Click to expand...
Click to collapse
No this can't brick your device, once rooted you could brick your device if you delete needed files.
Sent from my BLU ENERGY X PLUS using Tapatalk
removed.
Sent from my Lenovo YT3-X90F using Tapatalk
ONLY FOR WW PHONES WITH 16 GB MEMORY AND 2GB RAM!
Code:
ВНИМАНИЕ!!! Attention! Achtung! Attenzione! Увага! Perhatian!
I am not responsible for broken phones, broken micro USB, pregnant women and children.
By installing this recovery, you take responsibility for yourself.
After modifying system, OTA update will not install.
Before installing, make backups!
| What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
| MY CHANGELOG
Replace the standard interface on a bright, transparent buttons and background.
Corrected display time, the military 24-hour format.
Off to install TWRP App.
Time off screen to 120 seconds.
Vibration when the buttons are pressed: 40; When working with the keyboard: 0; termination: 100.
Mounted sections of the APD and ADF.
Fixed way responsible for the brightness of the screen.
Included in the Assembly modules: FB2PNG and NTFS-3G
As the name backup files using the name of the firmware, not the serial number as the default.
Data section now properly formatted.
Off protection in default.prop: ro.adb.secure=0 ro.secure=0 security.perf_harden=0. Only during recovery. To completely disable it you need to modify boot.img
Off encrypted backups
Backup all sections except the Data, if not removed encryption. To remove the encryption Data section: Wipe > Format Data > yes > Click the check mark.
The result will clear all user apps and settings. After that, the Data section will be mounted.
| How-to install:
| Download SP Flash Tool
SP_Flash_Tool_v5.1728_Win.zip
or
SP_Flash_Tool_exe_Windows_v5.1728.00.000.zip
| Download & Install VCOM/PRELOADER driver
USB-to-Serial_1_0.zip
or
MTK_drivers.rar
| SPFT setting
| For WW (E281L) 2/16 devices based on Android 6
| Base on firmware MRA58K.WW_Phone-13.0.1.58-20170326
DOWNDLOAD TWRP 3.1.1 https://mega.nz/#!uVIjVKgY!5CiCr2h62em5xUUgdWF8i73blURMkdz9XijeHOCVhXo
Scatter https://mega.nz/#!CQpwwSBb!MgeZYr60RvKWy-ydTXZ251BUlejYu7Qase9LHUopc4w
Screenshots https://mega.nz/#F!XEYQ2KDI!czj1ZI1Bkrs9BGFiVsnS9g
| For WW (E281L) 2/16 devices based on Android 7 Nougat
| Base on firmware NRD90M.WW_Phone-14.01.1707.43-20170714
DOWNDLOAD TWRP 3.1.1 https://mega.nz/#!PRhjGarI!hHmXmi46V2jo3Nz8PW2XXhIDRHnTpW3eoIdzJFb65mU
Scatter https://mega.nz/#!ucIEmbqR!MgeZYr60RvKWy-ydTXZ251BUlejYu7Qase9LHUopc4w
Screenshots https://mega.nz/#F!GVAyBDjJ!AxiM_odLDE9DdIxv0EcHFw
| For Pegasus X008 (E280L) 2/16 based on recovery CM_V1.0B23 on firmware CMCC_13.0.0.25
DOWNDLOAD TWRP 3.1.1 https://mega.nz/#!iQJW0CwA!clen84DJgAhNLl8OfmWiFxFDzc4gjvn63RHkD6lIypY
Scatter https://mega.nz/#!3MQwEShR!Kx5qrMC0v-dMwqzPbrwxVEXIXH8FXIGR2-A_MGdSb3U
| HOW TO GET ROOT
UPDATE-SuperSU-v2.82-20170528234214.zip
Before flashing TWRP, to obtain Root, download UPDATE-SuperSU-v2.82-20170528234214.zip and put on external memory card.
After flashing TWRP immediately install UPDATE-SuperSU-v2.82-20170528234214.zip or the recovery will be reset to stock
| Source
TWRP
If you liked my work and you appreciate my work, you can make a donation:
PayPal: https://www.paypal.me/BlackCorsar
QIWI: https://qiwi.me/19a4407f-091f-432f-af0f-81a42b9daec1
Compiled by BlackCorsar (me)
Thanks to all TWRP creators!
How to BackUP/Restore via SPFT
Instruction in pictures:
BackUP: https://mega.nz/#F!icBkWZCJ!WNA-rcXV8MIp_YOD8gMVHA or https://postimg.org/gallery/2itywikay/
Restore: https://mega.nz/#F!HJRwSLwb!WfuVSIJMvx8NZscMW_-o4Q or https://postimg.org/gallery/1pd89j5u2/
Preloader for Asus ZenFon 3 MAX X008D WW (Anroid6/7) preloader_E281L.zip
I do not have a preloader for Pegasus and I can't make twrp for 3/32 phones. I have neither the scatter nor the recovery.img for 3/32 phones.
Hi, Anyone can help me? I need TWRP for Zenfone 3 Max ZC520TL (X008DA) , Naugat ID version, thanks
scatter and preloader of 3/32 device
Hello can you build a recovery from this files?
they were removed from a working 3/32 ZC520TL device update program
thank you
can you help me in my device my chipset is MT6737 not mt6737t please help me
---------- Post added at 02:10 PM ---------- Previous post was at 02:03 PM ----------
Please HELP ME for my device my device is WW 14.10.1708.58 please help me for my scatter file and twrp img please
rictec said:
Hello can you build a recovery from this files?
they were removed from a working 3/32 ZC520TL device update program
thank you
Click to expand...
Click to collapse
I have the same phone and the ID version firmware contains this scatter file which sp flash tools cannot read and even the system.img and userdata.img are not present in the stock firmware.. there is system.new.dat file
---------- Post added at 08:32 PM ---------- Previous post was at 08:29 PM ----------
can you please make a working scatter file from the attachments attached by rictec and find some way how to flash that system.new.dat ???
I've tried this version of TWRP on my X008DC (US ZenFone 3 Max ZC520TL) but the phone won't take it. When attempting to go into recovery the phone just reboots itself back into Android.
I downloaded the WW version for Nougat 7.
i have the scatter file and recovery image and as well as the preloader for Asus X008DA Nougat ID version with 3/32 config.. as i am new on xda i am not allowed to post links.. how can i upload it so that you can port a twrp recovery for this phone ??
---------- Post added at 08:39 PM ---------- Previous post was at 08:38 PM ----------
BlackCorsar said:
Instruction in pictures:
BackUP: https://mega.nz/#F!icBkWZCJ!WNA-rcXV8MIp_YOD8gMVHA or https://postimg.org/gallery/2itywikay/
Restore: https://mega.nz/#F!HJRwSLwb!WfuVSIJMvx8NZscMW_-o4Q or https://postimg.org/gallery/1pd89j5u2/
Preloader for Asus ZenFon 3 MAX X008D WW (Anroid6/7) preloader_E281L.zip
I do not have a preloader for Pegasus and I can't make twrp for 3/32 phones. I have neither the scatter nor the recovery.img for 3/32 phones.
Click to expand...
Click to collapse
i have the scatter file and recovery image and as well as the preloader for Asus X008DA Nougat ID version with 3/32 config.. as i am new on xda i am not allowed to post links.. how can i upload it so that you can port a twrp recovery for this phone ??
Did anybody have the custom recovery for Asus Pegasus 3 X008D_1 (32 Internal Memory/3 GB Ram)? Please do share. I am tired searching around the net..
Can anybody make one for asus ZenFone 3 max ZC520TL CHIPSET MT6737V/W.PLEASE.Thank you.scatter file would be good ,then I could try to make it .SOFTWARE VERSION = US 14.14.1707.47_2017.1724.Need help
Angeloland said:
Can anybody make one for asus ZenFone 3 max ZC520TL CHIPSET MT6737V/W.PLEASE.Thank you.scatter file would be good ,then I could try to make it .SOFTWARE VERSION = US 14.14.1707.47_2017.1724.Need help
Click to expand...
Click to collapse
up for this i need this also... if found please email me [email protected]
Can I help you? ASUS Zenfone 3 Max ZC520TL
obar46 said:
Hi, Anyone can help me? I need TWRP for Zenfone 3 Max ZC520TL (X008DA) , Naugat ID version, thanks
Click to expand...
Click to collapse
I can help you, but I'm new in this forum and my English is base level. Say me how can I help you.
I already flashed my device correctly and works well!
Bye
From Italy... ?
dumper74
Code:
[I]DISCLAIMER[/I]
[COLOR="red"]Do not mirror my builds![/COLOR] Please post a link to this thread instead.
All information and files — both in source and compiled form — are provided on an as is basis.
No guarantees or warranties are given or implied. The user assumes all risks of any damages
that may occur, including but not limited to loss of data, damages to hardware, or loss of
business profits. Please use at your own risk. Note that unless explicitly allowed by the
warranty covering your device, it should be assumed that any warranty accompanying your
device will be voided if you tamper with either the system software or the hardware.
Introduction
This is my unofficial build of LineageOS 16.0 for the ZTE Blade S6 aka P839f30.
This is the first alpha release, so be aware that issues could arise.
I have tested this version with my AS variant device. Other variants have to be tested.
Click to expand...
Click to collapse
Features
working:
phone: calls, sms, data.
wifi
bluetooth
sensors
gps: mostly I have used the energy saving mode
sound
camera: rear with flash and front.
torch
headphone detection
swap back and menu button
light: button backlight, brightness control and adaptive brightness, breath light (notification and/or battery)
not working:
SELinux is permissive.
We have to test to find out.
Click to expand...
Click to collapse
Installation instructions
It is best to have installed the latest stock rom beforehand, so modem and all other vendor stuff is up to date.
If you like you can use this mod to have a unified data partition, please proceed with caution.
You will need TWRP or any other custom recovery.
Reboot into recovery and do a nand backup.
Do a factory format.
Download Rom and put it on your phone or use adb sideload.
Install the rom and then clear cache and dalvik cache.
optional: install su and/or gapps (preferable pico).
Click to expand...
Click to collapse
Changelog:
25.05.2021 - new release:
los security patch level 05.05.2021
revert some kernel changes from the last release
add some cpu governors and cpu hotplug
now with Boeffla WakeLock Blocker and other things
wireguard kernel support
22.12.2019 - 1st beta release:
los security patch level 05.12.
kernel supports EU device variant
add autosmp hotplug
add cpu governors blu_active, darkness, lionfish and relaxed
Revert CwMcu sensor driver from SU6 kernel release
24.10.2019 - 2nd alpha release:
los security patch level 05.10.
CwMcu sensor driver from SU6 kernel release, with wake lock disabled
wifi mac is loaded anyway, remove the loading in the wifi driver
give bluetooth a null mac address, to overcome force close error
kang gps from oppo
04.10.2019 - 1st alpha release:
los security patch level 05.09.
initial release of pie
Click to expand...
Click to collapse
Downloads
new release - 25.05.2021:
Google Drive.
first beta release - 22.12.2019:
Google Drive or here.
second alpha release - 24.10.2019:
Google Drive or here.
first alpha release - 04.10.2019:
Google Drive or here.
If you want root use the lineage addon package found here - download arm version.
Install it after flashing the rom or download your favourite root package and install it.
Click to expand...
Click to collapse
Sources
device
msm8916-common
vendor
kernel
Click to expand...
Click to collapse
FAQ
Here you will find some answers to common question which could arise.
Q: How to give root access to an app or adb?
A: First install the su extra package from Lineage OS or any other su tool you like. Then go into settings and about device, click there multiple times on the build number until you unlocked the developer options. Go to developer options and look for root access.
Q: I thing I found an issue, what to do now?
A: Do a logcat or grab a dmesg while having the issue, otherwise we can't say what is happening. Report as much info as possible. Quote your stock rom your device shipped with or which device variant you possess.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
*aquaris-dev team
*aymende7
*PacMM79
*LineageOS team
*many others
XDA:DevDB Information
Unofficial LineageOS 16.0 [PQ3A.190801.002] P839F30, ROM for the ZTE Blade S6
Contributors
lightwars
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: LineageOS 16.0
Version Information
Status: Beta
Current Beta Version: 20191213
Beta Release Date: 2019-12-22
Created 2019-10-04
Last Updated 2019-12-22
many thanks for the new version, i will tested later :good: :highfive:
Hello, works on my ZTE Blade S6 Plus (p839f50)
but only with a fixed updater-script
from Folder: lineage-16.0-20191002-UNOFFICIAL-p839f30.zip\META-INF\com\google\android
the bold text must delete and than save the file
after the start my phone , i have a error message with bluetooth is deactivated
updater-script - original
https://filehorst.de/d/crqjwnjI
updater-script - fixed
https://filehorst.de/d/cbmctorj
new update is in the op.
just small changes and updated security patch level.
Anybody tested with EU device?
... at the moment no time to test myself (to much effort to keep my other devices up-to-date ), just wanted to ask if anybody already tested on EU device (and forgot to post ).
Gtz
Kurt
Kurt Krummbein said:
... at the moment no time to test myself (to much effort to keep my other devices up-to-date ), just wanted to ask if anybody already tested on EU device (and forgot to post ).
Click to expand...
Click to collapse
Answer my own request, gave it a try, didn't boot, screen stayed black and device went into fastboot-mode ... restored my nandroid-backup of stock-EU-B15 .
Next time, i format system and just install rom without gapps and addon-su.
Gtz
Kurt
Kurt Krummbein said:
Answer my own request, gave it a try, didn't boot, screen stayed black and device went into fastboot-mode ... restored my nandroid-backup of stock-EU-B15 .
Next time, i format system and just install rom without gapps and addon-su.
Gtz
Kurt
Click to expand...
Click to collapse
Hello Kurt,
please, if you find the time to do another test. Download the attached zip extract the boot.img and copy it to your device, flash it with twrp right after installing the lineage zip through twrp. report back if something different happens.
I splited the dtb from the zImage and attached the almost stock eu dtb, so maybe we are lucky. But I have not find any big differences in analyzing the dts of EU vs AS and kernel defconfigs EU vs AS.
I can show this files too, if somebody has a better understanding of this.
lightwars said:
Hello Kurt,
please, if you find the time to do another test. Download the attached zip extract the boot.img and copy it to your device, flash it with twrp right after installing the lineage zip through twrp. report back if something different happens.
I splited the dtb from the zImage and attached the almost stock eu dtb, so maybe we are lucky. But I have not find any big differences in analyzing the dts of EU vs AS and kernel defconfigs EU vs AS.
I can show this files too, if somebody has a better understanding of this.
Click to expand...
Click to collapse
Hi!
Well, i loaded the def's and config's into WinMerge and did a compare ... in the def's there are some different addresses, but i have now clue what the meaning of that all is :angel:. The config files look like beeing from different kernel versions, there are some options which don't exist in both, one is modularised, the other is not ... all in all quite strange.
Ok, i made a try with the boot_eu.img:
- Made a factory reset
- Flashed the LOS.zip
- Wiped caches
- unzipped the boot.img
- copied it to boot partition with dd if=boot_eu.img of=/dev/block/bootdevice/by-name/boot
- reboot
... screen goes black, one buzz .... nothing. One the PC the fastboot device appears and that's it. I was looking for tombstones, but couldn't find any ... they are stored to /data/tombstones, are they? I'm not sure, the kernel i getting up high enough to mount /data.
Cheers
Kurt
P.S.: one thing i forgot to mention ... i coulnd't find the "OEM unlock" swich in the stock system anywhere and the bootloader seems to be quite dumb, many commands from fastboot just end in a "command unknown", perhaps there's something left to do on my side (tweak in build.prop etc ... googleed for it no result ).
Kurt Krummbein said:
Ok, i made a try with the boot_eu.img:
- Made a factory reset
- Flashed the LOS.zip
- Wiped caches
- unzipped the boot.img
- copied it to boot partition with dd if=boot_eu.img of=/dev/block/bootdevice/by-name/boot
- reboot
... screen goes black, one buzz .... nothing. One the PC the fastboot device appears and that's it. I was looking for tombstones, but couldn't find any ... they are stored to /data/tombstones, are they? I'm not sure, the kernel i getting up high enough to mount /data.
Click to expand...
Click to collapse
Thanks for testing. You used the reboot system button of twrp I guess. Have you tried to reboot by pressing the power button?
I can think of two things: There is some flag in the kernel source which is called download_mode. I have seen that some devices have different default values! At the moment the value is 0, devices like the ones from bq with msm8916/msm8939 used this too, but devices from oppo with msm8939 uses a value of 1 as default. We can try this one.
Or there is a mask, which defines the restart reason so to speak says the device which mode to boot to. Here we have some differences in the meaning of the bits, a different bit shifting is used.
I can not really think that one of these causes your device to boot into download mode, because the recovery uses the same kernel on both region variants...
lightwars said:
Thanks for testing. You used the reboot system button of twrp I guess. Have you tried to reboot by pressing the power button?
I'll give that one a try .
Hope my device is not "going over the Wupper" LOL (this one has to come somewhen ...)
Click to expand...
Click to collapse
Ok, tried it ... same result. Then did a (perhaps a bit wired) test, just restored boot from my nandroid-backup. With this, the white ZTE bootscreen comes up and after some seconds it reboots to twrp.
Perhaps the dumb-bootloader refuses to boot with AS keys ... otherwise it wouldn't boot recovery. Strange puzzle.
Cheers
Kurt
Kurt Krummbein said:
Ok, tried it ... same result. Then did a (perhaps a bit wired) test, just restored boot from my nandroid-backup. With this, the white ZTE bootscreen comes up and after some seconds it reboots to twrp.
Perhaps the dumb-bootloader refuses to boot with AS keys ... otherwise it wouldn't boot recovery. Strange puzzle.
Cheers
Kurt
Click to expand...
Click to collapse
It is okay to do some unusual testings. I was doing this sort of things also, back then.
I'm not sure I get you, when you write about AS keys. Do you mean the fingerprint in the build.prop? I think I used the ones from the eu version. Maybe they build in some kind of kernel version check inside the bootloader, but only for the eu and other versions.
The cause is, that android needs an advanced kernel, so we can not use the stock kernel to boot newer android version like nougat, oreo or pie.
Sorry, I can not be of much help here, because I do not have a device with eu or some other region version. But we can try do some changes, if you like to do some more testing and maybe get something like a log, last_kmseg or ramoops. We should look to activate some of them.
Hello @Kurt Krummbein,
if you find the time please post the info you get by issuing this commands in the adb shell or on your phone in a terminal:
Code:
su
cat /sys/zte_board_id/board_id
cat /proc/device-tree/model
cat /proc/device-tree/compatible
Do this on your rom or stock rom you are using a the moment. Thank you.
For reference mine output is this:
Code:
Blade-S6:/ # cat /sys/zte_board_id/board_id
wrbA
Blade-S6:/ # cat /proc/device-tree/model
Qualcomm Technologies, Inc. MSM 8939 MTP
Blade-S6:/ # cat /proc/device-tree/compatible
qcom,msm8939-mtp qcom,msm8939 qcom,mtp
It could be that the eu variant uses another device tree inside the kernel, because the bootloader request that, but we have only this model available.
lightwars said:
Hello @Kurt Krummbein,
if you find the time please post the info you get by issuing this commands in the adb shell or on your phone in a terminal:
Code:
su
cat /sys/zte_board_id/board_id
cat /proc/device-tree/model
cat /proc/device-tree/compatible
Do this on your rom or stock rom you are using a the moment. Thank you.
For reference mine output is this:
Code:
Blade-S6:/ # cat /sys/zte_board_id/board_id
wrbA
Blade-S6:/ # cat /proc/device-tree/model
Qualcomm Technologies, Inc. MSM 8939 MTP
Blade-S6:/ # cat /proc/device-tree/compatible
qcom,msm8939-mtp qcom,msm8939 qcom,mtp
It could be that the eu variant uses another device tree inside the kernel, because the bootloader request that, but we have only this model available.
Click to expand...
Click to collapse
Mine is:
cat /sys/zte_board_id/board_id
wrbA-EUROPE
cat: /proc/device-tree/model: No such file or directory
cat: /proc/device-tree/compatible: No such file or directory
ls /proc/device-tree
/proc/device-tree: No such file or directory
Attached my build.prop ... perhaps this sheds some light .
Thx
Kurt
Kurt Krummbein said:
Mine is:
cat /sys/zte_board_id/board_id
wrbA-EUROPE
cat: /proc/device-tree/model: No such file or directory
cat: /proc/device-tree/compatible: No such file or directory
ls /proc/device-tree
/proc/device-tree: No such file or directory
Attached my build.prop ... perhaps this sheds some light .
Thx
Kurt
Click to expand...
Click to collapse
Sorry for that, I forgot that the stock kernel did not expose the device tree.
But I think I remeber the info about the model is in the logcat after boot up...
Please try this ones in a terminal on the phone or via adb shell, they should work.
Code:
su
Blade-S6:/ # cat /sys/devices/soc0/hw_platform
MTP
Blade-S6:/ # cat /sys/devices/soc0/soc_id
239
lightwars said:
Sorry for that, I forgot that the stock kernel did not expose the device tree.
But I think I remeber the info about the model is in the logcat after boot up...
Please try this ones in a terminal on the phone or via adb shell, they should work.
Code:
su
Blade-S6:/ # cat /sys/devices/soc0/hw_platform
MTP
Blade-S6:/ # cat /sys/devices/soc0/soc_id
239
Click to expand...
Click to collapse
mine is:
cat /sys/devices/soc0/hw_platform
MTP
cat /sys/devices/soc0/soc_id
268
cat /sys/devices/soc0/image_version
10:LRX22G:eng.root.20150808.123811
Gtz
Kurt
Kurt Krummbein said:
mine is:
cat /sys/devices/soc0/hw_platform
MTP
cat /sys/devices/soc0/soc_id
268
cat /sys/devices/soc0/image_version
10:LRX22G:eng.root.20150808.123811
Gtz
Kurt
Click to expand...
Click to collapse
Fantastic! Here we have an explanation. Your device reports 268 as id which equals to msm8929 and I have a device with id 239 which is msm8939. The kernel only holds a device tree blob (dtb) for the id 239. I thought that the variant were very similar, so last time I used a dtb from the eu release but only for id 239. Attached I have added a dtb for id 268. Please test this rom with that boot image.
Again, just unpack the bootASEU.img and copy it to your device, flash it after installing the lineageos zip.
Please make a backup beforehand and report back, when you have time. Happy trying out.
lightwars said:
Fantastic! Here we have an explanation. Your device reports 268 as id which equals to msm8929 and I have a device with id 239 which is msm8939. The kernel only holds a device tree blob (dtb) for the id 239. I thought that the variant were very similar, so last time I used a dtb from the eu release but only for id 239. Attached I have added a dtb for id 268. Please test this rom with that boot image.
Again, just unpack the bootASEU.img and copy it to your device, flash it after installing the lineageos zip.
Please make a backup beforehand and report back, when you have time. Happy trying out.
Click to expand...
Click to collapse
One step ahead ! Phone is booting with the new boot.img ... but ends with a bootloop.
Highest was one boot with start of the setup-wizard, but after setting language to "Deutsch (Deutschland)" (and several "Bluetooth is not working" messages) it went around again. Couldn't get logs yet ... well see :
Cheers
Kurt
Kurt Krummbein said:
One step ahead ! Phone is booting with the new boot.img ... but ends with a bootloop.
Highest was one boot with start of the setup-wizard, but after setting language to "Deutsch (Deutschland)" (and several "Bluetooth is not working" messages) it went around again. Couldn't get logs yet ... well see :
Cheers
Kurt
Click to expand...
Click to collapse
Yeah! Would be best to build the dtb from source, rather than attaching just the right one to the kernel...
The bluetooth message can be made silent, by the way what build you are using? I think the first build has not the fix for the message. The build.prop should contain this line:
Code:
ro.boot.btmacaddr=00:00:00:00:00:00
and the message should not appear.
I hope there are not any preferences with could only be applied to msm8939 and not to msm8929.
@Kurt Krummbein
Here is my latest build or just grab the boot.img from the attachment. Which has a dtb for msm8929 build from source.
Maybe this will boot without any bootloop.
lightwars said:
@Kurt Krummbein
Here is my latest build or just grab the boot.img from the attachment. Which has a dtb for msm8929 build from source.
Maybe this will boot without any bootloop.
Click to expand...
Click to collapse
For which version is your latest build? the eu?
Thanks
BR Slawo
slawoko said:
For which version is your latest build? the eu?
Thanks
BR Slawo
Click to expand...
Click to collapse
AS and hopefully EU.
Ok so heres the full story (It's short):
So my V20 bricked itself for no reason (I was on stock for a few days unrooted no unlock nothing)
and while going through xda I stumbled upon this:https://forum.xda-developers.com/on...eble-lineageos-15-1-treble-oneplus-3-t3830455
Treble on the oneplus 3 and 3t. Why this one you might ask
well it is because our V20 and the Oneplus are similar.
So here is what somebody who is willing to help with a h990ds or H990 (It wont brick your device don't worry)needs to do:
1.First install this modded twrp here is the Link (Made from Pheonix591's twrp): https://drive.google.com/file/d/1pBrjWnKqRFFsQ-By_ElE3pW3LbWsg9sx/view?usp=sharing
2. Boot into the TWRP and go to advanced options then select terminal
Now type Treble and wait for a few seconds (This command is taken from the trebel port for oneplus 3 @simonsh)
Next reboot to whatever rom you are using(If it doesn't boot or bootloops something went wrong retry from step 2)
After it boots successfully go back to twrp and check in wipe and advanced wipe for Vendor
Now here is the problem the partition is only about 100 megabytes which we cant really use for treble it is too small.
So I am pinging a person who might be able to help us :
@runningnak3d I need your help in making the partition larger as it is again only about 100megabytes
Edit: So Runningnak3d has stopped developing for the V20 :crying: and I had just remembered that @x86cpu might be able to help so pinging him, we want as much people as possible.
Uhh so seems like my wifi is not properly working I will upload the twrp
Mysteriouslog6 said:
Ok so heres the full story (It's short):
So my V20 bricked itself for no reason (I was on stock for a few days unrooted no unlock nothing)
and while going through xda I stumbled upon this:https://forum.xda-developers.com/on...eble-lineageos-15-1-treble-oneplus-3-t3830455
Treble on the oneplus 3 and 3t. Why this one you might ask
well it is because our V20 and the Oneplus are similar.
So here is what somebody who is willing to help with a h990ds or H990 (It wont brick your device don't worry)needs to do:
1.First install this modded twrp here is the Link (Made from Pheonix591's twrp):
2. Boot into the TWRP and go to advanced options then select terminal
Now type Treble and wait for a few seconds (This command is taken from the trebel port for oneplus 3 @simonsh)
Next reboot to whatever rom you are using(If it doesn't boot or bootloops something went wrong retry from step 2)
After it boots successfully go back to twrp and check in wipe and advanced wipe for Vendor
Now here is the problem the partition is only about 100 megabytes which we cant really use for treble it is too small.
So I am pinging a person who might be able to help us :
@runningnak3d I need your help in making the partition larger as it is again only about 100megabytes
Click to expand...
Click to collapse
Running naked moved on and stopped developing for the V20 a long time ago.
Sent from my LG-H910 using XDA Labs
cnjax said:
Running naked moved on and stopped developing for the V20 a long time ago.
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
That's really sad I was hoping someone can help me with the partition problem, what about @x86cpu ?
Mysteriouslog6 said:
Ok so heres the full story (It's short):
So my V20 bricked itself for no reason (I was on stock for a few days unrooted no unlock nothing)
and while going through xda I stumbled upon this:https://forum.xda-developers.com/on...eble-lineageos-15-1-treble-oneplus-3-t3830455
Treble on the oneplus 3 and 3t. Why this one you might ask
well it is because our V20 and the Oneplus are similar.
So here is what somebody who is willing to help with a h990ds or H990 (It wont brick your device don't worry)needs to do:
1.First install this modded twrp here is the Link (Made from Pheonix591's twrp): https://drive.google.com/file/d/1pBrjWnKqRFFsQ-By_ElE3pW3LbWsg9sx/view?usp=sharing
2. Boot into the TWRP and go to advanced options then select terminal
Now type Treble and wait for a few seconds (This command is taken from the trebel port for oneplus 3 @simonsh)
Next reboot to whatever rom you are using(If it doesn't boot or bootloops something went wrong retry from step 2)
After it boots successfully go back to twrp and check in wipe and advanced wipe for Vendor
Now here is the problem the partition is only about 100 megabytes which we cant really use for treble it is too small.
So I am pinging a person who might be able to help us :
@runningnak3d I need your help in making the partition larger as it is again only about 100megabytes
Edit: So Runningnak3d has stopped developing for the V20 :crying: and I had just remembered that @x86cpu might be able to help so pinging him, we want as much people as possible.
Click to expand...
Click to collapse
Mind if I help I recently acquired a vs995 for cheap so for know at least im back. I experimented with trebe on the g5 and was able to build a treblized los 15.1 but the problem was no gsi would boot here's what I used to build it.
https://review.lineageos.org/c/LineageOS/android_device_lge_h850/+/222974
https://review.lineageos.org/c/LineageOS/android_device_lge_msm8996-common/+/221553
https://review.lineageos.org/c/LineageOS/android_kernel_lge_msm8996/+/222018
I then added this to BoardConfigCommon.mk:
# Treble
BOARD_PROPERTY_OVERRIDES_SPLIT_ENABLED := true
BOARD_VNDK_RUNTIME_DISABLE := true
BOARD_VNDK_VERSION := current
PRODUCT_FULL_TREBLE_OVERRIDE := true
I would also like to mention that a few years ago @King_lilrowrow said he was working on/achieved treble on the G5 I'd contact him as well for help.
What is 'treble' / 'treblizing'... Curious what it does.
kaluna00 said:
What is 'treble' / 'treblizing'... Curious what it does.
Click to expand...
Click to collapse
The command does this (From @simonsh thread)
Code:
/sbin/sgdisk --typecode=5:8300 /dev/block/sdf
/sbin/sgdisk --change-name=5:vendor /dev/block/sdf
It basically makes the sdf block the vendor partition (Works as nothing has interfered with the working of the phone so the partition is unused but it is too small need help with that)
kaluna00 said:
What is 'treble' / 'treblizing'... Curious what it does.
Click to expand...
Click to collapse
So treble aka project treble is something google implemented with android 8 that splits system/vendor to / system and /vendor basically it gives vendor files which are device-specific code and drivers used to interact with the phone's hardware there own separate partition. Now since /system without vendor is mostly free of device-specific code it means that the phones os can be upgraded with messing with building and modifying the device-specific code, this is were GSIs (generic system images) come in, flashing a gsi essentially means we can modify and upgrade our OS like a custom rom but instead of spending hours working on a custom rom we can just build a system image which is very fast and easy and it can do just as much as a custom rom as far as enhancing the user experience goes.
That's the best I can explain it here is an article explaining it more and as far as trebilizing goes it's just a term used when someone gets treble working on an old device that doesn't support it from the factory.
ROMSG said:
Mind if I help I recently acquired a vs995 for cheap so for know at least im back. I experimented with trebe on the g5 and was able to build a treblized los 15.1 but the problem was no gsi would boot here's what I used to build it.
https://review.lineageos.org/c/LineageOS/android_device_lge_h850/+/222974
https://review.lineageos.org/c/LineageOS/android_device_lge_msm8996-common/+/221553
https://review.lineageos.org/c/LineageOS/android_kernel_lge_msm8996/+/222018
I then added this to BoardConfigCommon.mk:
# Treble
BOARD_PROPERTY_OVERRIDES_SPLIT_ENABLED := true
BOARD_VNDK_RUNTIME_DISABLE := true
BOARD_VNDK_VERSION := current
PRODUCT_FULL_TREBLE_OVERRIDE := true
I would also like to mention that a few years ago @King_lilrowrow said he was working on/achieved treble on the G5 I'd contact him as well for help.
Click to expand...
Click to collapse
Thanks for wanting to help I will send a link for the vs995 with a custom twrp. Also isn't the BoardConfigCommon.MK in the source for lineage os I will try building it with the modifications
Mysteriouslog6 said:
Thanks for wanting to help I will send a link for the vs995 with a custom twrp. Also isn't the BoardConfigCommon.MK in the source for lineage os I will try building it with the modifications
Click to expand...
Click to collapse
Thanks, BoardConfigCommon.mk is a device tree file and specific to any rom. Here this Commit outlines one of the issues @x86cpu had with getting treble working.
@ROMSG
Thanks a bunch for the explanation. I appreciate you breaking it down I like that. I'll do some homework and check out that link after work. Take care!
Mysteriouslog6 said:
Thanks for wanting to help I will send a link for the vs995 with a custom twrp. Also isn't the BoardConfigCommon.MK in the source for lineage os I will try building it with the modifications
Click to expand...
Click to collapse
Any update on the vs995 custom twrp?
ROMSG said:
Any update on the vs995 custom twrp?
Click to expand...
Click to collapse
Sorry for the late reply I will send it tomorrow itself (Will have to somehow see if the TWRP boots or not)
Heres the link:
twrp-treble-vs995.img
drive.google.com
ROMSG said:
Any update on the vs995 custom twrp?
Click to expand...
Click to collapse
I have sent the TWRP just check the latest post
Mysteriouslog6 said:
I have sent the TWRP just check the latest post
Click to expand...
Click to collapse
Just saw it thanks
Mysteriouslog6 said:
Ok so heres the full story (It's short):
So my V20 bricked itself for no reason (I was on stock for a few days unrooted no unlock nothing)
and while going through xda I stumbled upon this:https://forum.xda-developers.com/on...eble-lineageos-15-1-treble-oneplus-3-t3830455
Treble on the oneplus 3 and 3t. Why this one you might ask
well it is because our V20 and the Oneplus are similar.
So here is what somebody who is willing to help with a h990ds or H990 (It wont brick your device don't worry)needs to do:
1.First install this modded twrp here is the Link (Made from Pheonix591's twrp): https://drive.google.com/file/d/1pBrjWnKqRFFsQ-By_ElE3pW3LbWsg9sx/view?usp=sharing
2. Boot into the TWRP and go to advanced options then select terminal
Now type Treble and wait for a few seconds (This command is taken from the trebel port for oneplus 3 @simonsh)
Next reboot to whatever rom you are using(If it doesn't boot or bootloops something went wrong retry from step 2)
After it boots successfully go back to twrp and check in wipe and advanced wipe for Vendor
Now here is the problem the partition is only about 100 megabytes which we cant really use for treble it is too small.
So I am pinging a person who might be able to help us :
@runningnak3d I need your help in making the partition larger as it is again only about 100megabytes
Edit: So Runningnak3d has stopped developing for the V20 :crying: and I had just remembered that @x86cpu might be able to help so pinging him, we want as much people as possible.
Click to expand...
Click to collapse
Hello, since Android 12 beta has released recently, i get to know that we can use the GSI image to update “any” (in terms of project treble supported) device to a newer android version without the need of building the rom per device.
So that i started to explore on a few xda threads trying to get Treble on LG V20. After digging into it, i updated my TWRP to the latest image (official TWRP 3.5.2_9 H990 which is the Official TWRP build commit based on Pheonix591's twrp build), then i saw that the /vendor shows up on mount, but not on either Wipe or Backup, which Phoenix591’s reddit post stated that this means there’s no vendor partition on it.
I followed this thread, since my TWRP is not modded (as the link in your comment does not work) I typed two sgdisk commands which the Treble command does, after a reboot, i saw a Vendor partition in Backup showed 0mb, Vendor partition DOES NOT appears on Wipe.
Next, as what i saw from @x86cpu ’s comment, he said he repartitioned and created the /vendor partition of 512mb by resizing the /system partition, unfortunately i am new to partitioning the Android device, i haven’t figured out how i can do that.
I tried to do sgdisk —print /dev/block/mmcblk0, it showed a single 64gb MBR FAT32 Partition instead of showing the system partition, it seems to be showing the micro sd card instead of the system volume, so i tried to unplug the sd card and reboot, now /dev/block/mmcblk0 is not found. I also tried to list info of /dev/block/sdf which we have wrote the partition name “vendor” to the 5th parnum of /sdf, it shows that the partition is only 4kb.
Since i have a H990N (Hong Kong version of the H990) i used the Dirty Santa patch to get TWRP installed on the device, that means the device’s bootloader is NOT fully unlocked, so the device might have difference between official unlocked device like the VS995.
Is there anything i could try ?
kwankiu said:
Hello, since Android 12 beta has released recently, i get to know that we can use the GSI image to update “any” (in terms of project treble supported) device to a newer android version without the need of building the rom per device.
So that i started to explore on a few xda threads trying to get Treble on LG V20. After digging into it, i updated my TWRP to the latest image (official TWRP 3.5.2_9 H990 which is the Official TWRP build commit based on Pheonix591's twrp build), then i saw that the /vendor shows up on mount, but not on either Wipe or Backup, which Phoenix591’s reddit post stated that this means there’s no vendor partition on it.
I followed this thread, since my TWRP is not modded (as the link in your comment does not work) I typed two sgdisk commands which the Treble command does, after a reboot, i saw a Vendor partition in Backup showed 0mb, Vendor partition DOES NOT appears on Wipe.
Next, as what i saw from @x86cpu ’s comment, he said he repartitioned and created the /vendor partition of 512mb by resizing the /system partition, unfortunately i am new to partitioning the Android device, i haven’t figured out how i can do that.
I tried to do sgdisk —print /dev/block/mmcblk0, it showed a single 64gb MBR FAT32 Partition instead of showing the system partition, it seems to be showing the micro sd card instead of the system volume, so i tried to unplug the sd card and reboot, now /dev/block/mmcblk0 is not found. I also tried to list info of /dev/block/sdf which we have wrote the partition name “vendor” to the 5th parnum of /sdf, it shows that the partition is only 4kb.
Since i have a H990N (Hong Kong version of the H990) i used the Dirty Santa patch to get TWRP installed on the device, that means the device’s bootloader is NOT fully unlocked, so the device might have difference between official unlocked device like the VS995.
Is there anything i could try ?
Click to expand...
Click to collapse
So in regards to partitioning you have to build a ROM with that partiton table in place for it too work and I have gotten treble to work (this was on myt h830) however no gsi will boot. I had to use this tool to add vender in order to flash my treble rom. I used the 800MB option in order for vender to show up.
Here are some 15.1 device tress I made for tbe VS995. I used the changes from x86cpu
GitHub - ROMSG/Treble-android_device_lge_msm8996-common
Contribute to ROMSG/Treble-android_device_lge_msm8996-common development by creating an account on GitHub.
github.com
GitHub - ROMSG/android_device_lge_vs995
Contribute to ROMSG/android_device_lge_vs995 development by creating an account on GitHub.
github.com
GitHub - ROMSG/Treble_android_device_lge_v20-common
Contribute to ROMSG/Treble_android_device_lge_v20-common development by creating an account on GitHub.
github.com
ROMSG said:
So in regards to partitioning you have to build a ROM with that partiton table in place for it too work and I have gotten treble to work (this was on myt h830) however no gsi will boot. I had to use this tool to add vender in order to flash my treble rom. I used the 800MB option in order for vender to show up.
Here are some 15.1 device tress I made for tbe VS995. I used the changes from x86cpu
GitHub - ROMSG/Treble-android_device_lge_msm8996-common
Contribute to ROMSG/Treble-android_device_lge_msm8996-common development by creating an account on GitHub.
github.com
GitHub - ROMSG/android_device_lge_vs995
Contribute to ROMSG/android_device_lge_vs995 development by creating an account on GitHub.
github.com
GitHub - ROMSG/Treble_android_device_lge_v20-common
Contribute to ROMSG/Treble_android_device_lge_v20-common development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Thanks for your reply ! I used the tool in your comment, at first i tried take use /system space to resize a 512mb /vendor partition unfortunately this makes the /system partition only at 5gb which result in Error:7 while flashing new ROMs, so i removed the partition and did it again by adding a 512mb /vendor using space AFTER /data, i checked the partition by fdisk -l /dev/block/sda the /vendor partition is created successfully with 512gb partition size, but no “/vendor” Partition was shown on the Wipe page of TWRP (while the partition was shown in Backup and Mount), not sure whether this affect us on going Treble or not, but wiping /vendor should be possible via terminal commands.
ROMSG said:
So in regards to partitioning you have to build a ROM with that partiton table in place for it too work and I have gotten treble to work (this was on myt h830) however no gsi will boot. I had to use this tool to add vender in order to flash my treble rom. I used the 800MB option in order for vender to show up.
Here are some 15.1 device tress I made for tbe VS995. I used the changes from x86cpu
GitHub - ROMSG/Treble-android_device_lge_msm8996-common
Contribute to ROMSG/Treble-android_device_lge_msm8996-common development by creating an account on GitHub.
github.com
GitHub - ROMSG/android_device_lge_vs995
Contribute to ROMSG/android_device_lge_vs995 development by creating an account on GitHub.
github.com
GitHub - ROMSG/Treble_android_device_lge_v20-common
Contribute to ROMSG/Treble_android_device_lge_v20-common development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
One more thing, I actually misunderstood the partition yesterday that i said it was 0mb, in fact, the backup page shows 0mb is a normal behaviour as the vendor partition is empty, i didnt check how big is the partition size, but I believe it should be 100mb after running the command “Treble”. Anyways, thanks for pointing out the tools which makes it 512mb now !