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!
HI Guys , its me again so after a long working night of disabling encryptions and verifications i finaly was able to boot a AOSP Generic System Image on my LG G7 (EUROPEAN VARIANT ONLY) and now im here to show you how to install
How to install ?
Download the GSI from PHH AOSP thread , take a/b ones with ot without gapps as you like
Download my SecuretyOff-Vendor-image and my Permissive boot.img
Reboot to fastboot and unlock your bootloader if you havent done it yet (you can find tutorials online, same method as on g6 and previous)
flash the magisk enabled securetyoff permissive kernel with the command "fastboot flash boot_a pathtoimghere"
Reboot your G7 to LG Stock os and install magisk manager and TerminalEmulator from PlayStore
Now copy the Downloaded Vendor file to your internal sdcard and rename it to vendor.img
Open TerminalEmulator (adb shell works aswell) and type su, hit enter, then type "dd if=/sdcard/vendor.img of=/dev/block/bootdevice/by-name/vendor_a" , hit enter m this will take some time pls be patient
Once youre done with flashing the new vendor reboot to fastboot again and flash the GSI with the following command "fastboot flash system_a pathtoimghere"
One last step before you can enjoy AOSP type "fastboot -w" and then "fastboot reboot"
Whats Working ?
So for me everyting works so far i just noticed 2 small bugs till now
1. the Notification LED wont stop blinking (im on that already)
2.sometimes the display turns black for about 0,5secs
3. if your headphone jack doesn't work open up a root shell and enter "setprop persist.sys.overlay.devinputjack true"
Credits
Me for testing and patching the **** out of that boot.img and vendor.img
AutoPrime for his G7 system Dump
Phhuson for his brilliant work on GSI's
Zefie for recommending me the right tool to repack kernel without bootloops (xD)
SGMarkus for providing ideas and additional Help
reserved
reserved 2
Update , Ressurection Remix Gsi and LineageOS Gsi work too , also i was able to fix the blinking led , but it doesnt work at all anymore (lights hal doesnt load will investiagte tomorrow) but RR or Los doesnt have gapps packed with them so you will need to wait for twrp to be ready (i think i will finish it in next few days)
J0SH1X said:
HI Guys , its me again so after a long working night of disabling encryptions and verifications i finaly was able to boot a AOSP Generic System Image on my LG G7 (EUROPEAN VARIANT ONLY) and now im here to show you how to install
How to install ?
Download the GSI from PHH AOSP thread , take a/b ones with ot without gapps as you like
Download my SecuretyOff-Vendor-image and my Permissive boot.img
Reboot to fastboot and unlock your bootloader if you havent done it yet (you can find tutorials online, same method as on g6 and previous)
flash the magisk enabled securetyoff permissive kernel with the command "fastboot flash boot_a pathtoimghere"
Reboot your G7 to LG Stock os and install magisk manager and TerminalEmulator from PlayStore
Now copy the Downloaded Vendor file to your internal sdcard and rename it to vendor.img
Open TerminalEmulator (adb shell works aswell) and type su, hit enter, then type "dd if=/sdcard/vendor.img of=/dev/block/bootdevice/by-name/vendor_a" , hit enter m this will take some time pls be patient
Once youre done with flashing the new vendor reboot to fastboot again and flash the GSI with the following command "fastboot flash system_a pathtoimghere"
One last step before you can enjoy AOSP type "fastboot -w" and then "fastboot reboot"
Whats Working ?
So for me everyting works so far i just noticed 2 small bugs till now
1. the Notification LED wont stop blinking (im on that already)
2.sometimes the display turns black for about 0,5secs
Credits
Me for testing and patching the **** out of that boot.img and vendor.img
AutoPrime for his G7 system Dump
Phhuson for his brilliant work on GSI's
Zefie for recommending me the right tool to repack kernel without bootloops (xD)
SGMarkus for providing ideas and additional Help
Click to expand...
Click to collapse
Amazing work friend
What about the rom with the DAC? I can change this in the settings of the sound more precise. So not like the lg rom, the preset sound profiles?
Look forward to this! Many thanks +++
what about the dac? sound does not work over jack connection.
Hi.
Does the wide camera work with this rom?
And does the radio fm work?
Where can I find the last release?
Thanks.
Sent from my LM-G710 using Tapatalk
ricxgp said:
Hi.
Does the wide camera work with this rom?
And does the radio fm work?
Where can I find the last release?
Thanks.
Sent from my LM-G710 using Tapatalk
Click to expand...
Click to collapse
wide angle works on aosp rom , fm radio idk but try , you can find the latest release in treble enabled device section of xda
Any word on AOSP 9? As far as I know it requires vndk 8.1 but the g7 launched with Android 8. Do we have to wait for Android 8.1/9 from LG for AOSP 9?
https://highonandroid.com/android-r...oject-treble-unlocked-bootloader-twrp-method/
I saw a video on youtube by max lee i do believe he said you could install this as long as you had twrp recover
I have the sprint verison so i cant try but if anyone with twrp can try and comment
LameMonster82 said:
Any word on AOSP 9? As far as I know it requires vndk 8.1 but the g7 launched with Android 8. Do we have to wait for Android 8.1/9 from LG for AOSP 9?
Click to expand...
Click to collapse
does not work will maybe never work
Guys, can anyone pls do this in adb (or if you have root with terminal app):
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms >/sdcard/kallsyms.txt
UltraM8 said:
Guys, can anyone pls do this in adb (or if you have root with terminal app):
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms >/sdcard/kallsyms.txt
Click to expand...
Click to collapse
With the stock ROM or with aosp?
LameMonster82 said:
With the stock ROM or with aosp?
Click to expand...
Click to collapse
Doesn't really matter
so the headphone jack is now fixed open up a root shell and type setprop persist.sys.overlay.devinputjack true then reboot and it will work
UltraM8 said:
Guys, can anyone pls do this in adb (or if you have root with terminal app):
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms >/sdcard/kallsyms.txt
Click to expand...
Click to collapse
Hello, sorry for being so late but i finaly got the files that youre looking for. "Kptr_restrict" is attached in the post but "kallsyms" is too big so i uploaded it to my google drive. The link is:
https://drive.google.com/file/d/1Mn9jeS7n681dbRWvZqlundCuTAvNF4FJ/view?usp=drivesdk
LameMonster82 said:
Hello, sorry for being so late but i finaly got the files that youre looking for. "Kptr_restrict" is attached in the post but "kallsyms" is too big so i uploaded it to my google drive. The link is:
https://drive.google.com/file/d/1Mn9jeS7n681dbRWvZqlundCuTAvNF4FJ/view?usp=drivesdk
Click to expand...
Click to collapse
thx man!
LameMonster82 said:
Hello, sorry for being so late but i finaly got the files that youre looking for. "Kptr_restrict" is attached in the post but "kallsyms" is too big so i uploaded it to my google drive. The link is:
https://drive.google.com/file/d/1Mn9jeS7n681dbRWvZqlundCuTAvNF4FJ/view?usp=drivesdk
Click to expand...
Click to collapse
I've checked kallsyms, how did you get it? via terminal app, or adb (or even twrp maybe if it's possible on g7)? The prob is that functions addresses are zeros, that's not good.
This overlay APK it's "born" because of the necessity to overcome missing overlays (thanks Huawei, love ya xoxo) under /vendor/overlay .
What it does exactly?
Nothing more than adding AOSP overlay matching our device capabilities and also, inherits Anne power profile.
Do I need it?
Yes.
It will fix Battery stats problems and add compatible features for your ANE over GSI.
This will conisderably enhance your experience on every GSI ROM giving better functionality overall.
Why you did that?
Because I'm sick of inheriting stuff that belongs to /vendor, in system.
Project Treble it's all about separating vendor implementation from system.
So why we should keep adding OEM stuff in that doesn't belong no more in /system
I have XYZ device with ZYX firmware can I use it?
As long as you're on a ANE-*** device (with a non-EMUI firmware), you're good to go.
Otherwise DO NOT USE IT FOR THE LOVE OF MANKIND.
I don't have ANE, but I want it on my Huawei device !
Well, that's fine, join the Telegram group @GSI_HI6250, so that you could help me with stock files grabbing to make an overlay for your device.
Overlay configs (aka "what does dis do, ser tell pl0x"):
Allows all rotations;
Configs autobrightness levels;
Configs autobrightness Lcd values;
Configs BLE;
Sets Doze Component;
Sets Doze After screen off;
Configs autopowermodes (doze related);
Configs power management on:
screen off due to proximity sensor interaction;
decouple on suspend state;
Configs brightness doze value;
Configs Intrusive led;
Configs dual band wifi support (where available);
Configs hotswap (where available);
Configs Color Transform on HWC;
Configs VoLTE available (even tho it needs support on GSI side);
Configs WFC over IMS;
Configs wifi background scanning support.
Installation Instructions
Download the overlay
With root, push the overlay to /vendor/overlay. Create the folder if it doesn't exist.
Run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/dil3mm4-overlay-ANE.apk
XDA:DevDB Information
[Overlay] Dil3mm4's Overlays for Anne Series devices (all variants), Device Specific App for the Huawei P20 Lite
Contributors
Dil3mm4
Version Information
Status: Stable
Created 2018-07-10
Last Updated 2018-07-09
Bettery reporting still not working
AJ said:
Bettery reporting still not working
Click to expand...
Click to collapse
Then you're doing it wrong.
Sorry, but I can't fix you.
Dil3mm4 said:
Then you're doing it wrong.
Sorry, but I can't fix you.
Click to expand...
Click to collapse
Am on aosp treble maybe that's why ,
Plus you don't have the device , how could you be so sure ???
wait i get this :
Code:
chcon: '/vendor/overlay/dil3mm4-overlay-ANE.apk' to u:object_r:vendor_overlay_file:s0: Read-only file system
AJ said:
Am on aosp treble maybe that's why ,
Plus you don't have the device , how could you be so sure ???
wait i get this :
Code:
chcon: '/vendor/overlay/dil3mm4-overlay-ANE.apk' to u:object_r:vendor_overlay_file:s0: Read-only file system
Click to expand...
Click to collapse
1- Who tells that I don't have this device? Are you some CIA agent or what?
2- This has been extensively tested.
3- You're free to don't use it, with this kind of cockiness you're showing, you won't receive any help from me.
Peace.
Dil3mm4 said:
1- Who tells that I don't have this device? Are you some CIA agent or what?
2- This has been extensively tested.
3- You're free to don't use it, with this kind of cockiness you're showing, you won't receive any help from me.
Peace.
Click to expand...
Click to collapse
Ok up to you
Peace too
AJ said:
Am on aosp treble maybe that's why ,
Plus you don't have the device , how could you be so sure ???
wait i get this :
Code:
chcon: '/vendor/overlay/dil3mm4-overlay-ANE.apk' to u:object_r:vendor_overlay_file:s0: Read-only file system
Click to expand...
Click to collapse
Do it in TWRP, you cocky bastard.
crayonicle said:
Do it in TWRP, you cocky bastard.
Click to expand...
Click to collapse
Did it in twrp , still says battery usage unavailable
AJ said:
Did it in twrp , still says battery usage unavailable
Click to expand...
Click to collapse
Well? Did it give any errors? Also, battery usage may take a while for it to finish analyzing all your apps and stuff, so it takes some time.
crayonicle said:
Well? Did it give any errors? Also, battery usage may take a while for it to finish analyzing all your apps and stuff, so it takes some time.
Click to expand...
Click to collapse
No , no errors , i mounted vendor placed the file there and ran the command in twrp terminal .
How can I verify if I did everything correctly and it works? I put the commands with fastboot
thx
UPDATE
-P compatibility
-Improved brightness levels
DOWNLOAD
Does this make GSI rom to support display notch?
I cant execute the command.
It gives me this error
Code:
chcon: '/vendor/overlay' to u:object_r:vendor_overlay_file:s0: Read-only file system
chcon: '/vendor/overlay/dil3mm4-overlay-ANE.apk' to u:object_r:vendor_overlay_file:s0: Read-only file system
How can I fix this?
Remount the vendor partition as RW
mount -o rw,remount /vendor
Sent from my Huawei P20 Lite using XDA Labs
sykomaniac said:
Remount the vendor partition as RW
mount -o rw,remount /vendor
Click to expand...
Click to collapse
Thx, it's working now. But I didn't notice any changes
Zerogoki_00 said:
Thx, it's working now. But I didn't notice any changes
Click to expand...
Click to collapse
You shouldn't really. It just fixes a bunch of vendor specific configuration issues
Sent from my Huawei P20 Lite using XDA Labs
@Dil3mm4
I think what I really need????????????,
Does anyone have BLE working on Pie roms? I can't connect to my Mi Band 3, logcat says something about BLE, but I don't know where to look deeper. BT headphones work ok. Seen somwhere that mi band is LE only device.
I have L21(C10), tried every rom, tried this overlay, every time get the same error.
Update FW as soon as a new FW is released, without waiting for update via OTA
Link download:
9.1.0.123:https://www.mediafire.com/file/2dukfz849883kt2/update_full_base.9.1.0.123.zip/file
9.1.0.129:http://update.dbankcdn.com/TDS/data/files/p3/s15/G4227/g4224/v288229/f1/full//update_full_base.zip
Or https://www.mediafire.com/file/misbmeij6gvkbtb/update_full_base_EVR-AL00-9.1.0.129.zip/file
9.1.0.131: http://update.dbankcdn.com/TDS/data/files/p3/s15/G4227/g4224/v290807/f1/full//update_full_base.zip
9.1.0.135 http://update.dbankcdn.com/TDS/data/files/p3/s15/G4227/g4224/v297953/f1/full//update_full_base.zip
Flash guide:
+ For lock booloader:
- Method 1: Using HStool: https://forum.xda-developers.com/mate-20-pro/how-to/manual-upgrading-mate-20-pro-bl-locked-t3905924
https://forum.xda-developers.com/showpost.php?p=79034230&postcount=70
- Method 2: Using Hisuite: http://www.mediafire.com/file/jx8fcupo0g0343u/HiSuite-9.0.2.301_Patch.rar/file
(Applicable to all Huawei devices using Hisuite for updates (Note: version of FW use to update must be true for your phone)
1. Install patch Hisuite:
- Uninstall all Hisuite related patches and files
- Install the HiSuite-9.0.2.301 version, End dont hit start - After Installation just close it. Make sure it doesn't run before the patching
- Replace the existing files withe file in patch foder:
httpcomponent.dll C:\Program Files (x86)\HiSuite
HiSuiteConfig.xml C:\Users\XXX\AppData\Local\HiSuite\userdata\UpdateDogDev (XXX is your name in your computer)
2. Prepare flash:
- Use winrar the decoding zip to update.app and other files or folders (Etc XYZ).
- Move folder XYZ above to the following folder: C:\Users\XXX\Documents\HiSuite\ROM (XXX is your name in your computer)
3. Flash rom:
- Disable Hisuite check update via internet by Edit the hosts C:/Windows/System32/Drivers/Hosts (Add 127.0.0.1 query.hicloud.com)
- Open Hisuite -> Click on Recovery -> Click continue
- Turn phone off. Connect phone to pc an keep pressing volume down and power until fastboot mode.
- Enable internet via Hosts file by Edit the hosts C:/Windows/System32/Drivers/Hosts (Edit 127.0.0.1 query.hicloud.com to #127.0.0.1 query.hicloud.com)
- Now Click Recover
- Wait until Hisuite Download and decompile from 85% to 95% then you quickly replace all your files in folder XYZ above (in C:\Users\XXX\Documents\HiSuite\ROM\XYZ)
- Hisuite will update your firmware, wait until finished and enjoy
Tip: Here the folder in C:\Users\XXX\Documents\HiSuite\ROM
http://www.mediafire.com/folder/w775spegaqark/ROM_hisuite
For update from 9.1.0.127 FW & up to 9.1.0.135, Every one can download & put to C:\Users\XXX\Documents\HiSuite\ROM . Hisuite Don't need download again (So Quickly update FW)
Video https://youtu.be/YfjxQBVvlV0
+ For unlock booloader: Don't work with 9.1.0.131 (error at 77%)
- Method 1: Root & Using EMUI Flasher: https://forum.xda-developers.com/ma...-mate-20-x-global00ized-2-0-emui-9-1-t3920956
- Method 2: Using nocheck recovery via ADB commands (Need install TWRP): Boot to TWRP recovery, open "ADB and Fastboot" then paste these command:
adb shell twrp decrypt
adb push ZIPS-HERE/update.zip /data/update/HWOTA/update.zip
adb push ZIPS-HERE/nocheck.img /data/update/nocheck.img
adb shell "echo --update_package=/data/update/HWOTA/update.zip > /cache/recovery/command"
adb shell dd if=/data/update/nocheck.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
adb reboot recovery
=======================================================================================================
Changlogs: 9.1.0.135
This update adds the instant projection feature, and support for the smart display series products, for an interactive home viewing experience.
-System:
Adds the instant projection feature, and support for the smart display series products, for an interactive home viewing experience.
-Settings:
Adds the DC dimming mode, preventing screen flickering. Go to Settings > Display > Eye comfort to enable Flicker reduction.
Security"
Integrates Android security patches released in August 2019 for improved system security. For more information on the security of Huawei EMUI system updates, please visit the official Huawei website: https://consumer.huawei.com/en/support/bulletin/2019/8/.
Good Job
This is full rom? Can I extract ramdisk from it and patch with magick?
Thanks
ivanox1972 said:
This is full rom? Can I extract ramdisk from it and patch with magick?
Thanks
Click to expand...
Click to collapse
This is FullOTA-MF rom, you can using tool to extract ramdisk .img file
I am stuck at the uncompressing step. When it reach 90% it gives me error code 7
https://i.imgur.com/8Ff4w3u.jpg
I tried 6 or 7 times, same result
I see FunkyHuawei don't download anything at Appdata/Local/FunkyHuawei/hisuitefiles.zip
So I guess that's the problem.
Any ideas?
[/COLOR]
vuhien said:
New FW EMUI 9.1.0.123 EVR-AL00
Link download:
http://update.hicloud.com:8180/TDS/...7/g4224/v268325/f1/full//update_full_base.zip
Flash guide:
+ For lock booloader:
- Method 1: Using HStool: https://forum.xda-developers.com/mate-20-pro/how-to/manual-upgrading-mate-20-pro-bl-locked-t3905924
https://forum.xda-developers.com/showpost.php?p=79034230&postcount=70
- Method 2: Using Hisuite with a few small tricks (I will update later)
+ For unlock booloader:
- Method 1: Using EMUI Flasher: https://forum.xda-developers.com/ma...-mate-20-x-global00ized-2-0-emui-9-1-t3920956
- Method 2: Using nocheck recovery via ADB commands:
adb shell twrp decrypt
adb push ZIPS-HERE/update.zip /data/update/HWOTA/update.zip
adb push ZIPS-HERE/nocheck.img /data/update/nocheck.img
adb shell "echo --update_package=/data/update/HWOTA/update.zip > /cache/recovery/command"
adb shell dd if=/data/update/nocheck.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
adb reboot recovery
=======================================================================================================
Changle log:
This update adds Moon mode to Camera, enabling you to take dazzling moon photos. Adds the support of Huawei Ark Compiler and EROFS, improving system performance and fluidity.
Master AI automatically identifies the moon and enables Moon mode, selecting suitable Camera parameters.
Adds support for the Huawei Ark Compiler, and improves system performance and fluidity.
Adds the EROFS system function, which improves app speed and fluidity.
Optimizes the front camera picture effects in dark environments, for reduced image noise and more natural colors.
Optimizes Face unlock, fixing the issue where the screen would unlock but not light up.
Fixes the issue where the Search function in Settings would ocassionally crash.
=======
Note: EROFS Files System:
The EROFS file system can increase the random read speed by 20%. When it comes to reading files types such as documents, music or videos, the higher reading speed the higher the response rate. Especially while launching a large app including a game, the startup speed will be faster and takes less time.
======
Click to expand...
Click to collapse
Care to elaborate on how to use HiSuite to get this update?
Flashed 123 success got weird issue if i boot magisk root my cobtact and dialer dont open but if i dont boot magisk root its all fine ...can anyone help me with this issue.. Thanks
If you are rooted do you have contact and dialer issue?
jbaggs said:
[/COLOR]
Care to elaborate on how to use HiSuite to get this update?
Click to expand...
Click to collapse
Need that HiSuite way too..
I'm getting the feeling the L29 version is going to get no new love on updates, we got a security patch at the weekend, wooooooooooo
walkwitmeinhel said:
If you are rooted do you have contact and dialer issue?
Click to expand...
Click to collapse
I've read doing a factory reset fixed this issue on previous updates, give that a try.
Link down
Link down friend.
---------- Post added at 02:50 AM ---------- Previous post was at 02:23 AM ----------
walkwitmeinhel said:
Flashed 123 success got weird issue if i boot magisk root my cobtact and dialer dont open but if i dont boot magisk root its all fine ...can anyone help me with this issue.. Thanks
Click to expand...
Click to collapse
Do you have the file from the link?
ErnestoSV said:
Link down friend.
---------- Post added at 02:50 AM ---------- Previous post was at 02:23 AM ----------
Do you have the file from the link?
Click to expand...
Click to collapse
I uploaded
https://drive.google.com/file/d/1PuOqWJR1N00-qgurnfy-vJzU4yDDEVeD/view?usp=drivesdk
walkwitmeinhel said:
I uploaded
https://drive.google.com/file/d/1PuOqWJR1N00-qgurnfy-vJzU4yDDEVeD/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks, I clicked the link so I think I will need your approval to download it.
ErnestoSV said:
Thanks, I clicked the link so I think I will need your approval to download it.
Click to expand...
Click to collapse
Its open now
walkwitmeinhel said:
Its open now
Click to expand...
Click to collapse
Thanks, downloading...
---------- Post added at 07:52 AM ---------- Previous post was at 07:37 AM ----------
walkwitmeinhel said:
Its open now
Click to expand...
Click to collapse
By the way. If I do the upgrade from 120 to 123, will my data be erased?
ErnestoSV said:
Thanks, downloading...
---------- Post added at 07:52 AM ---------- Previous post was at 07:37 AM ----------
By the way. If I do the upgrade from 120 to 123, will my data be erased?
Click to expand...
Click to collapse
No
walkwitmeinhel said:
No
Click to expand...
Click to collapse
I tried but, HI Suite says that my device is not supported.
ErnestoSV said:
I tried but, HI Suite says that my device is not supported.
Click to expand...
Click to collapse
Are you locked or unlocked?
version: 4.9.4
Last update of the program in the header: 04/06/2020
Developer: kory-vadim
For the program to function, root privileges are required.
Install: flash as Magisk module
Short description:
Unpacking, assembling and converting system (vendor) {. Img} {. New.dat} {. New.dat.br}, mounting raw.images, gluing the system.img broken into parts into a single image (from the firmware for Qfil), unpacking payload.bin, repackaging boot (recovery) .img, extracting file_contexts from boot.img (android <= 8.1), and converting file_contexts.bin on the phone.
Description:
To unpack images, you can use a phone with android 5+.
The system make_ext4fs is used from the phone’s firmware, so on a phone with android 6+ (or better 7), you can collect system.img images from android 5+.
We need root rights, busybox (needed before UKA version: 4.4 inclusive) and enough space for the images themselves and unpacking them in ./data.
Before flashing versions 4.6, 4.7, delete the old version and flash the corresponding archive via twrp.
In the kitchen there is a utility AIK - Android Image Kitchen for repacking boot (recovery) .img.
If, for some reason, you do not want to flash AIK-mobile (or, for example: already installed), then delete the file "AIK.Mobile.Installer.v3.4.zip" from the archive and flash "unpack-android_new_4.6. zip "without this file.
After flashing, install the terminal emulator (if it is not already installed), and check the box for UTF-8 in its settings.
To start the kitchen, in the terminal enter:
su
menu
Go to the item: "Extract file_contexts", and select the subitem: "Install configuration", if this is not done, then the conversion file_contexts.bin -> file_contexts will not work.
You need to run the configuration installation only once.
*In version 4.5 and above it should work without applying this item.
And then enter the numbers corresponding to the desired action.
To extract file_contexts, put boot.img in the folder: /data/local/UnpackerContexts.
To unpack .img images, you need to put system.img or vendor.img in the folder: /data/local/UnpackerSystem, and select the .img file (no more than 5) for unpacking.
When unpacking, the folders will be deleted: "system", or "vendor"; files: * _fs_config and * _pack.sh from the previous unpacking.
To build the image, copy the received file_contexts to the folder: /data/local/UnpackerSystem, if for some reason it will not be in the folder, then the assembly will be performed with file_contexts obtained when unpacking the image.
If files or folders were added to the disassembled image, then before assembling it, you must enter everything added into fs_config, and only then collect it.
If there are spaces in the names of folders or files in the unpacked image, then make_ex4fs will not collect such an image until you rename the files and correct the entries in fs_config.
Therefore, adding folders and files with spaces to the unpacked image is also not possible.
In version 4.6, the write assistant in fs_config is added.
If you just deleted something, then you do not need to edit fs_config.
Also in the collected folder must be present symlinks.
Well, in terms of context, Selinux will also need to be watched, depending on what was added.
To unpack or convert .dat, .br and in other cases, you will be prompted to enter the path to the folder where the image is located (in the same folder should be system (vendor) .transfer.list).
When converting and assembling in .dat, look behind the phone screen, because in some cases you need to enter a number corresponding to the version of the android, the image being collected.
There is a choice of compression ratio for converting * .new.dat to br.
To reduce the conversion time, compression can be selected 3-5 (maximum 7).
To unpack boot (recovery) .img, put the file in the folder: /data/local/AIK-mobile, and select the file in the menu: "unzip boot"
For packaging, use the item: "pack boot".
The collected file will be located in the folder: /data/local/AIK-mobile with the name boot-output.img.
To clean the working folder, also use the corresponding item. Source and output files will not be deleted.
AIK-mobile can be completely removed from the phone directly from the menu.
To mount, use the corresponding menu item, and the raw image must be located in the folder: /data/local/UnpackerSystem.
Do not forget to unmount the image.
To remove the kitchen from the phone, go to the corresponding menu item and confirm the removal,
after confirmation, the phone will be overloaded in twrp, and after working out the script, it will be loaded into the system.
Screenshots(Gdrive): https://drive.google.com/folderview?id=1-5dSaOQKpDH4gy737gcDp-Anp0vAj_VU
Download(Gdrive): https://drive.google.com/file/d/1-nOvictMuUNXbowwn3h1lbdrkJur2jJh/view?usp=drivesdk
MOD EDIT: Link removed
..
chelghouf said:
Hello ??
First thank you for the great work ?
After downloading version 4.9.2 I found it perfect for Android ROMs modification without the need for a computer .. But it needed translation, so work began on that then I decided to add a feature to save and rebuild the ROM currently installed on the device .. This feature is tested on one device " MediaTek treble enabled " .. and on two Android systems 9 And 10 and works perfectly this feature helped me a lot to repack and share the ROM after debugging it or adding new features .. Sorry I don't have other devices to confirm the effectiveness of this feature, but the script is designed to support most versions of Android and many devices when possible .. I'm glad if you accept to add and develop this feature in the next updates .. Thank you.
This is my modded version
https://www.mediafire.com/download/x9doxd3nnd0h2ja
This is the video showing how it works
https://www.mediafire.com/download/qchspnzniikg1gw
https://ibb.co/0QjG7S8
https://ibb.co/XxJ8FPp[/QUOTE
I am having issues in using your modded version.
Please kindly guide me on how to set it up.
Click to expand...
Click to collapse
..
chelghouf said:
What type of issues !
If you followed the video then, try to type menu in place of arkm, else be more specific please.
---------- Post added at 01:10 AM ---------- Previous post was at 12:49 AM ----------
This is a small update a feature removes kitchen binary files from the new build while extracting backup for sar and non sar devices.
I can't post links yet so replace @ with media fire home link
@/download/pq5obfcqhb18hpi
tested and confirmed working on 2 treble mtk devices running android 9 and 10 gsi ROMs and device stock ROM android 8.1
Previous link removed !
This is a small update
4.9.2.3
Added support for some kirin devices
@/download/o1ga3o1v4v13a0c
Click to expand...
Click to collapse
Thank you so much. It works flawlessly. Kudos Bro
chelghouf said:
What type of issues !
If you followed the video then, try to type menu in place of arkm, else be more specific please.
---------- Post added at 01:10 AM ---------- Previous post was at 12:49 AM ----------
This is a small update a feature removes kitchen binary files from the new build while extracting backup for sar and non sar devices.
I can't post links yet so replace @ with media fire home link
@/download/pq5obfcqhb18hpi
tested and confirmed working on 2 treble mtk devices running android 9 and 10 gsi ROMs and device stock ROM android 8.1
Previous link removed !
This is a small update
4.9.2.3
Added support for some kirin devices
@/download/o1ga3o1v4v13a0c
Click to expand...
Click to collapse
Link not working
..
chelghouf said:
@/download/9o1t3hlgh4duied
Replace @ with media fire home link
Click to expand...
Click to collapse
Dev all runs well except option 13 , kitchen not able backup vender . In my device (zuk z2 ) vender is as /factory.
Thanks
..
chelghouf said:
Thanks for feedback , It's fixed i'll give you a link when upload finish
---------- Post added at 09:38 AM ---------- Previous post was at 09:03 AM ----------
@/download/pmzfg8kvdk7to1n
This is a small fix for zuk z2 pro and plus and there is no problem to flash the final rom build.
But if you want your vendor file output name like this "factory.new.dat.br" then you have to wait.
Click to expand...
Click to collapse
All custom roms(z2+) shows "vendor.new.dat.br" in zip, only they unpack in /factory partition .
..
chelghouf said:
Good, i had no idea, i hope it has been fixed.
Click to expand...
Click to collapse
Thanks Dev it starts backing up & converting to zip.
..
chelghouf said:
Hello ??
First thank you for the great work ?
After downloading version 4.9.2 I found it perfect for Android ROMs modification without the need for a computer .. But it needed translation, so work began on that then I decided to add a feature to save and rebuild the ROM currently installed on the device .. This feature is tested on one device " MediaTek treble enabled " .. and on two Android systems 9 And 10 and works perfectly this feature helped me a lot to repack and share the ROM after debugging it or adding new features .. Sorry I don't have other devices to confirm the effectiveness of this feature, but the script is designed to support most versions of Android and many devices when possible .. I'm glad if you accept to add and develop this feature in the next updates .. Thank you.
This is my modded version
https://www.mediafire.com/download/x9doxd3nnd0h2ja
This is the video showing how it works
https://www.mediafire.com/download/qchspnzniikg1gw
https://ibb.co/0QjG7S8
https://ibb.co/XxJ8FPp
Click to expand...
Click to collapse
@chelghouf I keep installing it in magisk but it doesn't show up! Any hint?
..
chelghouf said:
Install from twrp
https://www.mediafire.com/download/q3lq7wz6rsdbfww
Click to expand...
Click to collapse
I installed from TWRP now and it's still the same.
..
chelghouf said:
Type menu and use it from the link I gave you to get all the new features.
Click to expand...
Click to collapse
It's still the original Russian one, should I uninstall the original one? [Thank you for your attention]
Yes, uninstalling the original one fixed it, let's try it out.
..