Hi,
Can anyone here upload the "camera.qcom.so" file from the system/lib/hw folder of any Oneplus - 2 Nougat ROM ???
As it is a SD 810 device and I want the SO file to use in Xperia Z5 series .
Instruction on the xda:
https://www.xda-developers.com/enab...kers-nexus-5x-nexus-6p-oneplus-3-xiaomi-mi-5/
other:
My solution :
It works on my Xperia XZ Premium In build.prop I change Android version from 8.0 to 8.1 but maybe working to on 8.0 I don't try I use everytime 8.1 on my XZ Premium and I have Pixel 2 XL model name and etc. I use pixelify magisk but I change after flash in magisk file system.prop in folder root > magisk > pixelify-4rk4n with this line from screenshot
FLASHTOOL - FLASHING ROM - XPERIA XA1 PLUS AND ULTRA
Flashtool at this moment don't support any wariants of xperia XA1 ultra and plus , in flashtool you can flash only normal XA1 .
If you want to flash you xperia xa1 ultra or plus you need to patch the flashtool , but if don't patch the flashtool you can't flash variants plus and ultra.
What you need to patch and flash xa1 plus and ultra :
1. Installed last version of flashtool.
2. Installed/updated drivers from flashtool (the same folder what is flashtool)
3. Than you start flashing and start flashtool make a patch . Patch is HERE .
4. Patch your flashtool now.
5. Start flashtool
6. Click on xperi firm
7. Download rom via flashtool
8. After download (if you correct patch flashtool) close xperi firm
9. Flashtool start ,,pack'' rom to ftf file
10. Click on ,,thunder'' and check rom and start flash your device
IMPORTANT:
This guide is only for xperia XA1 ULTRA and XA1 PLUS with all wariants !!
If flashtool ask about add .fsc script to ftf - CLICK YES . Fsc script must to be inside ftf file for correct flash , if flash device use fsc !!
If this guide is helpfull click thanks
FLASHTOOL - FLASHOWANIE ROMU - XPERIA XA1 PLUS AND ULTRA
Flashtool na ten moment nie wspiera żadnego wariantu xperii xa1 ultra jak i plus , w flashtoolu można jedynie sflashować rom od normalnej xperii xa1 .
Jeżeli chcesz sflashować xperie xa1 ultra lub plus potrzebujesz spatchować flashtoola , gdyż jak pisałem wyżej niema oficjalnego patcha dla tych dwóch pozostałych wariantów . W przypadku nie spatchowanego flashtoola nie można flashować wariantu plus i ultra .
Co potrzebujesz do patchowania i flashowania xperii xa1 plus i ultra :
1. Zainstalowanego najnowszego flashtoola.
2. Zainstalowanych/zaktualizowanych sterowników flashtoola (ten sam folder co flashtool).
3. Nim zaczniesz flashowanie i zrób patcha flashtoola !! Patch jest tutaj .
4. Zrób patch flashtoola .
5. Uruchom flashtool.
6. Uruchom przez flashtool xperi firm.
7. Pobierz rom przez flashtool.
8. Po pobraniu (jeżeli poprawnie spatchowałeś flashtoola) zamknij xperi firm.
9. Flashtool zacznie pakować rom do pliku ftf.
10. Kliknij na piorunek , wybierz rom i zacznij flashować swoją xperię smile.gif
Ważne:
Faq jest tylko dla xperii xa1 plus i ultra w każdym wariancie !!
Jeżeli flashtool zapyta o dodanie fsc script kliknij yes . Fsc script jest wymagany w pliku ftf do poprawnego sflahowania telefonu . Jeżeli flashtool zapyta o użycie fsc script do flashowania również klikamy yes .
Jeżeli temat był pomocny kliknij mi thanks
Temat ten został przez mnie utworzony na XDA i jestem jego właścicielem !!
Tłumaczenie tego tematu na język angielski nie było łatwe , więc jeżeli widzisz jakieś błędy napisz mi o tym proszę na pm na xda . Dziękuję
Flashed nougat with flashtool, not patched just fine
Here's the guide to convert an Oreo trebled DSSI(OEM ROM) into an sGSI.
Before starting, I have to claim these points below:
1.This thread aims to converting ,not generalizing.This means they are the basic steps of porting a DSSI, I can lead you to boot, but bug fixes are up to you.
2.Some of the devices with official / unofficial treble support isn't compatible with sGSI(at least my definition) e.g. mido
3.Only supports Oreo porting.VNDK version of DSSI and your vendor needs to be the same.If you want to support a different vndk,you should investigate the way to add another vndk support by yourself.
First - unpack and deploy the original rom to your device.
This means that you don't need to use a kitchen,as it will cause problems.
Unpack the rom and get raw system.img.
-use brotli tool to covert system.new.dat.br to .dat
-use sdat2img to convert dat to raw img
Mount it to your device's /system
-copy it to your sdcard.
-goto twrp-advanced-terminal
Enter:
losetup /dev/block/loop0 /sdcard/system.img
mount /dev/block/loop0 /system
Debloat it by using filemanager
-Goto twrp file manager,
-goto /system
-delete only apps that you are sure it's safe to remove(e.g. Downloadable GApps)
Create a twrp backup of the target
-Just use twrp to backup /system using normal method.
Write /system to your real partition.
-twrp mount menu - uncheck /system
-restore your backup created.
Then you've flashed the rom's system to your device.
Second - SELinux Fix
This is the most important step to avoid fastboot kick.
-Download an Oreo GSI and unpack using whatever methods you like.
-extract /system/etc/selinux/mapping from the GSI.
-adb push <your extracted folder>/system/etc/selinux/mapping/. /system/etc/selinux/mapping
To test it:
Flash permissiver.zip from semiGSI thread.
Reboot.
If your device isn't kicked into fastboot mode, then it's possible to port this DSSI.
Third - ramdisk fixes.
Get boot patcher from any sGSI thread.
Unpack target rom's boot.img
Put necessary files into boot patcher zip.
Mainly:
/init.rc
/init.environ*
/init.zygote*
/init.($oem name / rom name).*
Exclude:
/init
/init.usb*
is possible take my rom of huawei mate 9 , emui 8.0 and create a GSI for install in others phones ????
Fourth - Vendor patch fixes.
Download vendor patch from my MIUI sGSI thread.
Extract your DSSI's vendor.img using the same way as system.img.
In the patcher from my thread you will see some files under /vendor.They are the files necessary for ports of Oreo Qualcomm DSSIs.
-get the "necessary" files from vendor.img and put them to the patcher.
-If there are vendor implementations the one I described in my P Preview porting thread , add them too.
There will be some files that is rom-specific and you need to find out later by logs.
Fifth - build.prop editing.
-copy and add contents from target rom's /vendor/*.prop to /system/build.prop
(Mainly PMS configs)
Sixth - Test
Modify /system/etc/prop.default to disable adb secure.
Wipe /data
Reboot and adb logcat
is possible take my rom of huawei mate 9 , emui 8.0 and create a GSI for install in others phones ????
aureliomilitao said:
is possible take my rom of huawei mate 9 , emui 8.0 and create a GSI for install in others phones ????
Click to expand...
Click to collapse
Other EMUI8.0 phones.
fxsheep said:
Other EMUI8.0 phones.
Click to expand...
Click to collapse
so, no possible take the gsi and create a rom for install in others, mido, example...custom rom ?
aureliomilitao said:
so, no possible take the gsi and create a rom for install in others, mido, example...custom rom ?
Click to expand...
Click to collapse
Yes it's possible but without RIL GPS and Sensors .maybe HWC too.
BTW mido doesn't support sGSI.
Can we use this guide to port Oyxgen os (P) to Asus Zenfone max pro m1?
Would it be possible to port z17 rom to z17s? The z17 has 8.1. The z17s does not but it can boot GSI.
devast8ndiscodave said:
Would it be possible to port z17 rom to z17s? The z17 has 8.1. The z17s does not but it can boot GSI.
Click to expand...
Click to collapse
yes
Pretty much thank you for the guide. Ill try to convert the Redmi 6 Pro ROM into sGSI and try to get it stable for mido(Mido can boot sGSI btw like your MIUI10 sGSI).
Just a question @fxsheep . How can i get away with force encryption? Ive tried many methods on my old MIUI Oreo port but all of them failed.
Στάλθηκε από το Redmi Note 4 μου χρησιμοποιώντας Tapatalk
Tisenoiazei100 said:
Pretty much thank you for the guide. Ill try to convert the Redmi 6 Pro ROM into sGSI and try to get it stable for mido(Mido can boot sGSI btw like your MIUI10 sGSI).
Just a question @fxsheep . How can i get away with force encryption? Ive tried many methods on my old MIUI Oreo port but all of them failed.
Στάλθηκε από το Redmi Note 4 μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
forcecrypt -> encryptable in fstab.qcom
so would u recommend going with android P Releases or Oreo ?
cause i wanted to port funtouch os 4.0 8.1 from vivo x9 which has the same chip as my phone (rn4x) and i saw you ported the P Version which did not boot
omarilzz said:
so would u recommend going with android P Releases or Oreo ?
cause i wanted to port funtouch os 4.0 8.1 from vivo x9 which has the same chip as my phone (rn4x) and i saw you ported the P Version which did not boot
Click to expand...
Click to collapse
Then Oreo.But imo it has nothing to do with Android version.MIUI also have many bugs on it(which is from the same chipset too).That's because of the poor vendor support of your device.
@fxsheep Just a tip:
Include the need to add libcameraservice.so from stock lib & lib64 to port as phones like mido bootloop without it.
Στάλθηκε από το Redmi Note 4 μου χρησιμοποιώντας Tapatalk
I want to ask can the sony z3 d6603 [LB] 23.5.A.1.291 install Magisk Manager please give me the information i love the Z3 and all of you thks