{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This script is still in development state.
Hi.
My name is Rafal. I'm from Poland.
Here is a page about my script for porting ROMs.
This script will not make You a developer.
If You will public that port on xda or somewhere, please write author of this script,
and remember that uploading ROMs on xda need update sometimes.
Please don't post that number of port that You can't handle to update.
Main goal:
- full automatic script that port ROMs from other devices.
- support block and non-block based ROMs
ROMs based on lollipop and marshmallow mostly are based on block build but not all
Second goal:
- Support all devices
For DEVs
If You know BASH language and want help me, Send me private mess.
I'm open to any cooperation.
Request:
- linux
- zip
- python 3.x
- exec permission for ALL files
Usage:
Port is ROM that You want to port.
Base is ROM that You want as base for that port. (have to work with Your device!)
- Rename port ROM to port.zip and paste to port folder.
- Rename base ROM to base.zip and paste to base folder.
- Run script with ./run.sh
Remember that all files (expect ROMs) need exec permission.
Without that permission You will get only problems.
- Pick up done.zip from done folder
- Rename it in installer.
At META-INF/com/google/android/updater-script and find ROM name in ui_print(" ");
- If You will public port at xda or somewhere, please write author of this script, thanks!
Actual changelog:
https://bitbucket.org/wisniew99/auto-port/commits/all
Source / Download
https://bitbucket.org/wisniew99/auto-port
I will upload releases on other server than bitbucket because bitbucket don't support releases like github.
Q&A
Q: I need to know something about programming or development?
A: No, script is fully automatic. But remember: that script will not make You a dev.
Q: What roms support this script?
A: Block and non-block builds. In normal language: all packed in zip that have recovery support.
Q: What ROM are You prefering to use as base?
A: ROM that is stable as rock.
Q: This is inpossible!
A: If someone said that something is inpossible, so that is impossible for him/her not for You.
Reserved
No one interested?
I am interested. But I do not want to try.
If there is any problem, I do not know how to solve it.
And worry about break my device.
I could try. I have elementary OS PL live sd-card, but persistent image is only 4 gb. Are 4gb enough for porting roms? I want to use AOSP haxynox as a base and port candysix rom from n710p
Weicheng_Gao said:
I am interested. But I do not want to try.
If there is any problem, I do not know how to solve it.
And worry about break my device.
Click to expand...
Click to collapse
So You don't need to worry about any problems or something.
If problem automaticly quit and print what goes bad.
And Roms will not break Your phone.
aciupapa said:
I could try. I have elementary OS PL live sd-card, but persistent image is only 4 gb. Are 4gb enough for porting roms? I want to use AOSP haxynox as a base and port candysix rom from n710p
Click to expand...
Click to collapse
All linux is linux so elementary is ok too. 4GB is enough because one ROM based on AOSP and CM have less then 500MB, script don't use any of space because removing file from one rom and paste from second. If You will port stock like sony (~1.5GB) or samsung (~2GB) maybe You will not have enough.
Maybe today will be first version with block block script. but other will be easller then block block.
If ROMs don't use block block, script will automaticly quit and inform what rom don't have block structure.
Thank dev...will test it.
=====
Give report...
1. This support .tar.md5 stock sammy have ?
2. failed when clone
unable to access 'https://bitbucket.org...
3. success be download and extrat it be folder wisniew99-auto-port-9623255937fd
see all exec permittion...
but no any folder port, base and done...
make it manual folder alone becouse when be ./run.sh need that folder and insert file base.zip and port.zip
3. This just for 5.x up rom ? not clearly in op look like in there just discription abaout l and m blok and unblock
4. speculation for first time Im try 4.4.4 from one device my shv port as port and my i9305 port as based all deodek
And the result is just only extrat zip rom each above in base and port folder
No any done.zip .. althoung i have give done folder before manually.
Or im wrong ?
Thankyou
Sent from my GT-I9500 using XDA Free mobile app
zuziemanis said:
Thank dev...will test it.
=====
Give report...
1. This support .tar.md5 stock sammy have ?
2. failed when clone
unable to access 'https://bitbucket.org...
3. success be download and extrat it be folder wisniew99-auto-port-9623255937fd
see all exec permittion...
but no any folder port, base and done...
make it manual folder alone becouse when be ./run.sh need that folder and insert file base.zip and port.zip
3. This just for 5.x up rom ? not clearly in op look like in there just discription abaout l and m blok and unblock
4. speculation for first time Im try 4.4.4 from one device my shv port as port and my i9305 port as based all deodek
And the result is just only extrat zip rom each above in base and port folder
No any done.zip .. althoung i have give done folder before manually.
Or im wrong ?
Thankyou
Click to expand...
Click to collapse
Script is in pauze status.
Too much work at once.
Now script not work correctly without some fixes.
When I will get oneplus3 then I make that tool from zero.
Block is mostly used in Loli+ roms.
That script will not support raw porting, so any OEM roms (Samsung, sony) propobly will not work.
Will this work on other Samsung phones like the a series or j series? Because there's no ROM for the a series so the only only ROM available is the stock 5.1.1 and stock Europe 6.0
This script isn't very useful as S3 is based on Exynos 4412 which is only used by S3 3G/4G, Note 2 3G/LTE and certain Lenovo phone unless we are talking about S3 3G to S3 4G ports, this might be useful then
Wysłane z mojego LG-H815 przy użyciu Tapatalka
conanDO98 said:
Will this work on other Samsung phones like the a series or j series? Because there's no ROM for the a series so the only only ROM available is the stock 5.1.1 and stock Europe 6.0
Click to expand...
Click to collapse
As I said, script will not support OEM roms like samsung sony, htc and other.
Script will support all phones and all aosp roms.
(Maybe will support OEM roms but I will not support that roms officialy at begin)
Minto107 said:
This script isn't very useful as S3 is based on Exynos 4412 which is only used by S3 3G/4G, Note 2 3G/LTE and certain Lenovo phone unless we are talking about S3 3G to S3 4G ports, this might be useful then
Wysłane z mojego LG-H815 przy użyciu Tapatalka
Click to expand...
Click to collapse
This is for all phones.
I posted this on s3 forum because I testing this on s3 at the moment.
Why on i9300 this isn't useful?
Porting aosp roms don't stack You to port roms from the same platform.
rafciowis1999 said:
As I said, script will not support OEM roms like samsung sony, htc and other.
Script will support all phones and all aosp roms.
(Maybe will support OEM roms but I will not support that roms officialy at begin)
This is for all phones.
I posted this on s3 forum because I testing this on s3 at the moment.
Why on i9300 this isn't useful?
Porting aosp roms don't stack You to port roms from the same platform.
Click to expand...
Click to collapse
About the last one you're wrong. You can't port S4 i9505(for example) CM13 to I9300, both devices uses different platforms. It's just not that easy
Wysłane z mojego LG-H815 przy użyciu Tapatalka
Minto107 said:
About the last one you're wrong. You can't port S4 i9505(for example) CM13 to I9300, both devices uses different platforms. It's just not that easy
Wysłane z mojego LG-H815 przy użyciu Tapatalka
Click to expand...
Click to collapse
No comment...
rafciowis1999 said:
No comment...
Click to expand...
Click to collapse
Patients dev...
Good bless you
Sent from my GT-I9300 using XDA Free mobile app
rafciowis1999 said:
No comment...
Click to expand...
Click to collapse
You have certainly no idea what you're talking about... Hope you're not calling yourself a dev. You can't port Exynos to Snapdragon and vice versa... To show me I'm wrong, use ur 'magic' tool to port i9505 AOSP+OMS rom to i9300. Sure you can port it but you CAN'T boot it...
Wysłane z mojego LG-H815 przy użyciu Tapatalka
Related
Hello XDA members, in this guide, i'll give you the easiest way to porting rom for your device, i've broken my porting record by ported 5 roms in less than 1 hour using this method, have enjoy and hope it'll works for you too
What you need ?
- Rom base (CM or AOSP)
- Rom port (any roms that you like to port)
- Apktool (for compiling .apk and .jar files)
- Note++ (for editing .txt and .xml files)
- Winrar or 7zip (for extracting and repacking rom)
- dsixda's Android Kitchen, you really need this to Port MIUI, PAC, and Slimrom
- Open mind and never give up to trying
Rules
1. Find the rom port with similar CPU like your device, clock speed doesn't matter here, the important is the number of CPU Cores, if your device is single core, find the single core rom, dual-core with dual-core, etc
2. Forget about screen sizes(4, 5, or 7 inci), the important is screen DPI(pixels destiny) you can port rom from tablet or devices that have bigger/smaller screen sizes
example
> LDPI & LDPI
> MDPI & MDPI
> HDPI & HDPI
> xHDPI & xHDPI
> etc
3. Same Android SDK version(Check in build.prop)
Example, you can port Android 4.4.3 using Android 4.4.2
4. GSM and GSM, CDMA and CDMA
Step by step
Extract booth of the roms(rom base and rom port)
> In rom port folder <
1. Delete all files and folders except "system" folder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Delete these folders and files in system
> tts
> usr
> vendor
> build.prop
3. Delete these folders in system/etc
> Bluetooth
> Firmware (if exist)
> Wifi
4. Delete these folders in system/lib
> hw
> modules
5. Go to system/framework
> Open framework-res.apk
> Go to res/xml
> Replace storage-list.xml with your rom base
> In rom base folder <
1. Copy all files and folders except "system" to rom port folder
2. Copy these folders and files in system folder to rom port system folder
> tts
> usr
> vendor
> build.prop
3. Copy these folders in system/etc to rom port system/etc
> Bluetooth
> Firmware (if exist)
> Wifi
4. Copy these folders in system/lib to rom port system/lib
> hw
> modules
Repack the rom then flash it in the recovery
Now the rom port should booted(to menu) now, not stuck on bootanimation anymore
if you still stuck on bootanimation, check bootclasspath in boot.img, unpack it, and check in "init.environ.rc", use note++ to edit it, there's must be something miss there
If the rom doesn't boot to menu or stuck on manufacturer logo(LG, Sony, Samsung, etc), find the same rom port from other devices. I've this experience while porting Liquid Smooth, then i used other devices and it's booted
Notes :
If you successful ported the rom, please do these before your releasing your ROM
> Ask the permission from the developers of the rom base and rom port
> Give credit for them
> And give credit for me too if you using this guide
> And don't forget to hit THANKS button
For porting MIUI Kitkat, you need to unpack boot.img from both roms, then do these
- Copy paste init.miui.rc from rom port to rom base ramdisk folder
- Open init.rc from both roms, then compare it, there's some line you need to be edited...
Troubleshooting
Now, to fix some issues in rom port, do these...
1. Information about rom
Open build.prop from booth of the rom then edit information just like the rom port
You can edit these lines in build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.display.id=
ro.build.date=
ro.build.user=
ro.build.host=
ro.product.name=
ro.product.locale.language=
ro.product.locale.region=
ro.cm.device=
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.sys.root_access=
ro.modversion= > replace with rom port
ro.cm.version= > you can delete this
ro.config.ringtone=
ro.config.notification_sound=
ro.config.alarm_alert=
ro.sf.lcd_density=
and the other lines relating information about rom
2. RIL
Replace these files in rom port with your rom base files
system/bin/rild
system/lib/libreference-ril.so
system/lib/libril.so
system/lib/librilutils.so
system/lib/libsec-ril.so
system/lib/libsecril-client.so
And add any files with "ril" in the name of file
3. Sensor
Replace these files in rom port with your rom base files
system/bin/sensord
system/bin/sensorservice
system/lib/libsensorservice.so
system/lib/libhardware.so
system/lib/libhardware_legacy.so
4. WiFi
Replace these files in rom port with your rom base files
system/bin/wifimac
system/bin/wpa_cli
system/bin/wpa_supplicant
system/lib/libwpa_client.so
5. Missing files
You have to copy the rest of files in base rom to port rom to make rom better, but don't replace it if the files/folders was exist
6. Files can be replace in your ported rom using files from base rom
Bin
>adb
>dalvikvm
>debuggerd
>dhcpcd
>dnsmasq
>drmserver
>gdbserver
>glgps
>hostapd
>hostapd_cli
>ime
>ip
>ip6tables
>iptables
>logcat
>logwrapper
>media
>mediaserver
>mtpd
>ndc
>netcfg
>netd
>ntfs-3g
>ping
>ping6
>pppd
>radiooptions
>rild
>screenshot
>sdcard
>sensord
>sensorservice
>service
>servicemanager
>toolbox
>vdc
>vold
>wifimac
>wpa_cli
>wpa_supplicant
Lib
>lge-ril.so (for LG devices)
>libbluetooth_jni.so
>libbt-hci.so
>libbt-utils.so
>libhardware.so
>libhardware_legacy.so
>liblgehdmi.so
>libnfc.so
>libnfc_jni.so
>libnfc_ndef.so
>libreference-ril.so
>libril.so
>librilutils.so
>libsensorservice.so
>libwpa_client.so
>
>
7. Video streaming
> libstagefright.so
and all libs with "libstagefright" of the lib's name
Rom that can be ported
What roms can be ported using this guide ?
This guide should can port any costum roms base on AOSP or CM, not manufacturer roms, not yet...
My experience, I've ported these roms
Mokee Open Source Project
Carbon Rom
Paranoid Android
Xperience
SDK NX v1
AOKP
Hellfire
Codename Lungo
AOSB Project
OMNI Rom
SlimKat
PAC man
SOKP
AICP
MIUI V5 Kitkat
Rom ported by XDA Members using this guide
- Liquid Smooth
Bonus :
Need Aroma Installer on your rom ?
please go to this thread
If this guide helping you, please do these
> Donate to me
> Hit my THANKS button
> Rate the thread
> Poll the thread
> Hit "Tip us" ? to make this thread on portal, so many people will know it the easiest way to porting any costum rom
> Mention me (@Nasheich Xfiles) at your rom thread
> Keep this thread at first page with your posting
> Like this thread at Facebook, Google+ and Twitter
Best Regards
Nasheich
Credits
> Nasheich Xfiles : it's me
>ZduneX25
Very nice bro :good::good::good:
Thanks for this Awesome Guide
Will Try and let u know
Great guide.. is there a way we can get Tmobile Z1S stock rom (with wifi calling) to Z ultra? I am ready to do it myself with some guidance.
Great guide, ported a hellkat rom with it
Thanks for the guide but it's more interesting to port KitKat (4.4.x) to Jelly Bean (4.3.x), like Xperia ZR 4.4 ROM to Xperia SP with only 4.3 available. It's Qualcomm, many things possible with it. Any ideas?
D-SHEL said:
Thanks for the guide but it's more interesting to port KitKat (4.4.x) to Jelly Bean (4.3.x), like Xperia ZR 4.4 ROM to Xperia SP with only 4.3 available. It's Qualcomm, many things possible with it. Any ideas?
Click to expand...
Click to collapse
No You can't
Try using AOSP binaries (4.4) to port ZR 4.4 Rom
Sent from a Beast :')
---------- Post added at 04:57 AM ---------- Previous post was at 04:54 AM ----------
Rules
1. Find the rom port with similar CPU like your device, clock speed doesn't matter here, the important is the number of CPU Cores, if your device is single core, find the single core rom, dual-core with dual-core, etc
2. Forget about screen sizes(4, 5, or 7 inci), the important is screen DPI(pixels destiny) you can port rom from tablet or devices that have bigger/smaller screen sizes
example
> LDPI & LDPI
> MDPI & MDPI
> HDPI & HDPI
> xHDPI & xHDPI
> etc
In fact you can PORT Custom Roms from an HDPI Device to MDPI Device if they shares the same CPU core
Sent from a Beast :')
Can I port 4.4.2 lg optimus l9 ii using 4.4.3 pure aosp.
Sent from my Xperia S using xda premium
Is it possible to port XperiaOverlay ROM for Arc S (LT18i) to any build of CM11 LX ROM for Arc S with this guide?!?!
XperiaOverlay ROM is AOSP based but I think that XeperiaOverlay will running better if it is merged to CM11 LX...
Thanks in advance for all suggestions! :good:
pepitoff said:
Is it possible to port XperiaOverlay ROM for Arc S (LT18i) to any build of CM11 LX ROM for Arc S with this guide?!?!
XperiaOverlay ROM is AOSP based but I think that XeperiaOverlay will running better if it is merged to CM11 LX...
Thanks in advance for all suggestions! :good:
Click to expand...
Click to collapse
Haish, AOSP is smoother than CM11 because it's not modified (Pure android).
Btw, you can't get anything diffirent if you rebased overlay to CM11
MT27i said:
Haish, AOSP is smoother than CM11 because it's not modified (Pure android).
Btw, you can't get anything diffirent if you rebased overlay to CM11
Click to expand...
Click to collapse
OK. But is it possible to port XperiaOverlay to CM11 LX with this guide?
pepitoff said:
Is it possible to port XperiaOverlay ROM for Arc S (LT18i) to any build of CM11 LX ROM for Arc S with this guide?!?!
XperiaOverlay ROM is AOSP based but I think that XeperiaOverlay will running better if it is merged to CM11 LX...
Thanks in advance for all suggestions! :good:
Click to expand...
Click to collapse
It's Kinda Possible !!
But Chances are 40-45%
Since XO uses AOSP binaries
Sangeet007 said:
Thanks for this Awesome Guide
Will Try and let u know
Click to expand...
Click to collapse
Yes, let me know, I'll do my best to help you
royalva said:
Great guide.. is there a way we can get Tmobile Z1S stock rom (with wifi calling) to Z ultra? I am ready to do it myself with some guidance.
Click to expand...
Click to collapse
just try it, and let me kbow
Aaskereija said:
Great guide, ported a hellkat rom with it
Click to expand...
Click to collapse
Nice
D-SHEL said:
Thanks for the guide but it's more interesting to port KitKat (4.4.x) to Jelly Bean (4.3.x), like Xperia ZR 4.4 ROM to Xperia SP with only 4.3 available. It's Qualcomm, many things possible with it. Any ideas?
Click to expand...
Click to collapse
no, you can't, different files system between JB and KK
Black_Eyes said:
In fact you can PORT Custom Roms from an HDPI Device to MDPI Device if they shares the same CPU core
Sent from a Beast :')
Click to expand...
Click to collapse
Yes, you can port lower LCD destiny and Lower CPU too, i just make a simple explanation
nisu4717 said:
Can I port 4.4.2 lg optimus l9 ii using 4.4.3 pure aosp.
Sent from my Xperia S using xda premium
Click to expand...
Click to collapse
yes, you can, I've ported many rom base on AOSP, and you can ported 4.4.2 using 4.4.3, cause it has same Android SDK version (check on build.prop)
pepitoff said:
Is it possible to port XperiaOverlay ROM for Arc S (LT18i) to any build of CM11 LX ROM for Arc S with this guide?!?!
XperiaOverlay ROM is AOSP based but I think that XeperiaOverlay will running better if it is merged to CM11 LX...
Thanks in advance for all suggestions! :good:
Click to expand...
Click to collapse
Yes, there's always possibility to port any rom, cause the fact is 80% of Android files is same ..
Sorry if this sounds idiotic, but can I port SOKP from nexus 5 to xperia z1 using this method since they share the same chipset?
allinkiran said:
Sorry if this sounds idiotic, but can I port SOKP from nexus 5 to xperia z1 using this method since they share the same chipset?
Click to expand...
Click to collapse
yes, you can, if the specification of the hardware just like what I've wrote, not just the same chipset, but RAM too
Thank you. Would try tomorrow since nexus has son many roms that I want to try on my z1
Hi All,
This Guide is For Lenovo K3 Note Other devices can use it but some files may vary.
Here is a quick guide for getting the basics of the rom working.
Display, sound ,GSM (3g) and Wifi .
I used this for CyanogenMOD based ROMS and MIUI and it worked for me.
If anyone finds additional items or wants to complete this guide please feel free to add it in here.
Please remember, i am posting this so that people will try things and usually when they do, they end up finding something better and awesome than not trying.
I use this from stock and make it a zip file so it makes easy porting by just dragging the system folder with stock files to the rom to be ported and replace.
NOTE: ALWAYS REMOVE RECOVERY-FROM-BOOT.P before you do anything else.
FOR CROSS PORT
SO THE FILES NEEDED TO REPLACE FROM STOCK TO PORT:
BIN FOLDER:
Code:
afm_server
akmd09911
applysig
audiocmdservice_atci
climax
custom_sn
encfs
factory
factory_reset.sh
fusermount
gzip_static
ipod
kpoc_charger
mtkbt
nvram_proximity
seeder
updater
vold
IF YOU THINK SOME FILES ARE ABSENT, DONT WORRY JUST SKIP THEM
NOW MODEM FILES:
Code:
take the whole [COLOR="Red"]firmware[/COLOR] folder from system/etc/
take the whole [COLOR="Red"]mddb[/COLOR] folder from system/etc/
NOW THE MAIN THING OF K3 Note (Audio)
Code:
take the whole folder [COLOR="Red"]tfa98xx[/COLOR] from system/etc/
NOW LIBS Folder:
Code:
lib3a.so
libacdk.so
libbluetoothdrv.so
libbluetooth_mtk.so
libbypass.so
libcam.camadapter.so
libcam.camnode.so
libcam.camshot.so
libcam.client.so
libcam.device1.so
libcam.device3.so
libcam.exif.so
libcam.exif.v3.so
libcam.hal3a.v3.so
libcam.halsensor.so
libcam.iopipe.so
libcam.jni.lomohaljni.so
libcam.metadataprovider.so
libcam.paramsmgr.so
libcam.sdkclient.so
libcam.utils.so
libcam3_app.so
libcam3_hwnode.so
libcam3_hwpipeline.so
libcam3_pipeline.so
libcam3_utils.so
libcamalgo.so
libcamdrv.so
libcameracustom.so
libcamera_client_mtk.so
libcam_hwutils.so
libcam_platform.so
libcustom_nvram.so
libdpframework.so
libfeatureio.so
libfeatureiodrv.so
libhardware_legacy.so
libimageio.so
libimageio_plat_drv.so
libipod.so
libJpgDecPipe.so
libJpgEncPipe.so
liblocSDK5c.so
liblocSDK_2_5OEM.so
libm4u.so
libMA3-wavesfx-Coretex_A9.so
libmhalImageCodec.so
libMiraVision_jni.so
libmtkjpeg.so
libmtk_drvb.so
libnetworklocation.so
libnvram.so
libnvramagentclient.so
libnvram_platform.so
libnvram_sec.so
libshowlogo.so
libtfa9897_interface.so
libvc1dec_sa.ca7.so
libvcodecdrv.so
libvcodec_oal.so
libvcodec_utility.so
libweibosdkcore.so
mtk-ril.so [COLOR="Red"]<= IF U GET BOOT LOOP TRY WITHOUT REPLACING THIS FILE[/COLOR]
mtk-rilmd2.so [COLOR="Red"]<= IF U GET BOOT LOOP TRY WITHOUT REPLACING THIS FILE[/COLOR]
And this subfolder with these libs:
Code:
drm\libfwdlockengine.so
egl\egl.cfg
egl\libGLES_mali.so
hw\audio.primary.mt6752.so
hw\audio_policy.default.so
hw\bluetooth.default.so
hw\camera.mt6752.so
hw\gps.default.so
hw\gralloc.mt6752.so
hw\hwcomposer.mt6752.so
hw\lenovopower.default.so
hw\lights.default.so
hw\sensors.mt6752.so
soundfx\libdownmix.so
soundfx\libmaxxeffect-cembedded.so
NOW LIB64 Folder:
Code:
lib3a.so
libacdk.so
libbluetoothdrv.so
libbluetooth_mtk.so
libcam.camadapter.so
libcam.camnode.so
libcam.camshot.so
libcam.client.so
libcam.device1.so
libcam.device3.so
libcam.exif.so
libcam.exif.v3.so
libcam.hal3a.v3.so
libcam.halsensor.so
libcam.iopipe.so
libcam.jni.lomohaljni.so
libcam.metadata.so
libcam.metadataprovider.so
libcam.paramsmgr.so
libcam.sdkclient.so
libcam.utils.sensorlistener.so
libcam.utils.so
libcam1_utils.so
libcam3_app.so
libcam3_hwnode.so
libcam3_hwpipeline.so
libcam3_pipeline.so
libcam3_utils.so
libcamalgo.so
libcamdrv.so
libcameracustom.so
libcamera_client_mtk.so
libcamera_metadata.so
libcam_hwutils.so
libcam_mmp.so
libcam_platform.so
libcam_utils.so
libcustom_nvram.so
libdpframework.so
libfeatureio.so
libfeatureiodrv.so
libhardware_legacy.so
libimageio.so
libimageio_plat_drv.so
libJpgDecPipe.so
libJpgEncPipe.so
libm4u.so
libmhalImageCodec.so
libMiraVision_jni.so
libmtkjpeg.so
libmtk_drvb.so
libnvram.so
libnvramagentclient.so
libnvram_platform.so
libnvram_sec.so
libtfa9897_interface.so
libvcodecdrv.so
libvcodec_utility.so
And this subfolder with these libs:
Code:
drm\libfwdlockengine.so
egl\libGLES_mali.so
hw\audio.primary.mt6752.so
hw\audio_policy.default.so
hw\camera.mt6752.so
hw\gps.default.so
hw\gralloc.mt6752.so
hw\hwcomposer.mt6752.so
hw\lenovopower.default.so
hw\lights.default.so
hw\mmsdk.default.so
hw\sensors.mt6752.so
soundfx\libdownmix.so
NOW VENDOR FOLDER:
Code:
system\vendor\etc\audio_effects.conf
system\vendor\etc\default.mps
FOR DIFFERENT CHIPSET (i.e. 6795 to 6752)
Proceed as above THEN
open build.prop
EDIT THESE LINES
Code:
ro.mediatek.platform=[COLOR="Red"]MT6795[/COLOR] to [COLOR="Red"]MT6752[/COLOR]
mediatek.wlan.chip=[COLOR="Red"]MT6630[/COLOR]to [COLOR="Red"]CONSYS_MT6752[/COLOR]
mediatek.wlan.module.postfix=[COLOR="Red"]_mt6630[/COLOR]to [COLOR="Red"]_consys_mt6752[/COLOR]
And Now Boot.img
Unpack both stock and port boots from CarlivImageKitchen Tool
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now
In port boot.img
replace the boot.img-kernel
and in ramdisk folder add these files:
fstab.mt6752
init.mt6752.rc
init.mt6752.usb.rc
AND DELETE THOSE with mt6795 and mt6595 words.
REPACK THE KERNEL
MAKE THE FLASHABLE ZIP
AND FLASH THE ROM
If u get WIFI AND BLUETOOTH NOT SWITCHING ON OR BATTERY PERCENTAGE WRONG THEN REPLACE init.project.rc
FOR SAME CHIPSET PORTING
Just replace
Code:
etc/firmware
etc/mddb
and from lib and lib64 hw folder replace all libs named like this camera.mt6752.so
and replace audio_policy.default.so from both hw folder
from lib and lib64
replace
Code:
libcameracustom.so
libaudiocomponentengine.so
libaudiocustparam.so
libnvram.so
libnvramagentclient.so
libnvram_platform.so
libnvram_sec.so
libcustom_nvram.so
UPDATE :
TIP:To BOOT a rom with minimal replacements
Replace the boot.img files as usual
in system:
ETC FOLDER
etc/firmware
etc/mddb (not needed tho)
etc/tfa**(if your device uses)
LIB & LIB64
lib/libjni_pq.so
lib/libmtk_drvb.so
lib/libtfa****.so
lib64/libjni_pq.so
lib64/libmtk_drvb.so
lib64/libtfa****.so
HW folder
All the 67xx files if crossporting
VIOLA UR A PORTER
Can you add some image :3
Syaoran Lord said:
Can you add some image :3
Click to expand...
Click to collapse
i can add but image of what should i add
Porting to Ulefone be touch 2
Hi! Nice tutorial. Will this method work with Ulefone be touch 2? I want to port Aerom v5 from elephone p7000 to Ulefone be touch 2. My kernel version is 3.10.61 and port rom kernel is 3.10.91 so I have to port kernel? Thanks in advance
Ufoner said:
Hi! Nice tutorial. Will this method work with Ulefone be touch 2? I want to port Aerom v5 from elephone p7000 to Ulefone be touch 2. My kernel version is 3.10.61 and port rom kernel is 3.10.91 so I have to port kernel? Thanks in advance
Click to expand...
Click to collapse
yes it will work
no need to do anything about kernel u just proceed as the guide says
Thank you so much! And one more question please. Some guy try to port CM12.1 for BT2 and volume down button stopped working and screen is laggy. Installing stock ROM not solve that problem. Can happend this when i port android 5.0 or 5.1? Sorry for my bad English. Thanks in Advance.
Ufoner said:
Thank you so much! And one more question please. Some guy try to port CM12.1 for BT2 and volume down button stopped working and screen is laggy. Installing stock ROM not solve that problem. Can happend this when i port android 5.0 or 5.1? Sorry for my bad English. Thanks in Advance.
Click to expand...
Click to collapse
try taking logcat while pressing the vol down key
Hello, I don't undestand that : ALWAYS REMOVE RECOVERY-FROM-BOOT.P before you do anything else. please someone could explain for me ?
jordandroid64 said:
Hello, I don't undestand that : ALWAYS REMOVE RECOVERY-FROM-BOOT.P before you do anything else. please someone could explain for me ?
Click to expand...
Click to collapse
You need to delete file "recovery-from-boot.p" from system folder of your stock ROM and of port :good:
---------- Post added at 07:55 PM ---------- Previous post was at 07:53 PM ----------
I ended again with black screen when porting cm12.1 from redmi note 2 Is it caused by another size of ram Because my device has 3gb ram and redmi note 2 has 2gb.
thanks but it's an img on my port rom and I don't find this file... and same on my stcok rom (androium) but there are files name recovery i need to delete all of them ?
jordandroid64 said:
thanks but it's an img on my port rom and I don't find this file... and same on my stcok rom (androium) but there are files name recovery i need to delete all of them ?
Click to expand...
Click to collapse
You need to extract system.img with ext4unpacker and then make it folder with ext2explore. You dont need recovery so delete it
I have already extract the img but with ext2explore only that will be good also?
thanks for your answer
edit: edit : on the port rom at the last when i search recovery that whow me that :
http://www.hostingpics.net/viewer.php?id=839697recovery.jpg
Help me with bootloop please
Hi sandeep.sethi!
Today i port your aicp 5.1.1 from k3 note to be touch 2(stock rom is android 5.0.1) and i got bootloop . I edited mount points and replaced all files as your guide says.
Do i need to port kernel or anything else when my device has 3gb ram and k3 note has 2gb ram All specs are same except the ram size.
Stock rom is 5.0.1, but alex1112 port cm12.1(5.1.1) to be touch 2, so do i need to port kernel from alex1112 cm12.1 or from my stock rom to AICP?
Is this guide for same android version ex. 50.1 to 5.0.1?
Thanks in advance and have a good day
Ufoner said:
Hi sandeep.sethi!
Today i port your aicp 5.1.1 from k3 note to be touch 2(stock rom is android 5.0.1) and i got bootloop . I edited mount points and replaced all files as your guide says.
Do i need to port kernel or anything else when my device has 3gb ram and k3 note has 2gb ram All specs are same except the ram size.
Stock rom is 5.0.1, but alex1112 port cm12.1(5.1.1) to be touch 2, so do i need to port kernel from alex1112 cm12.1 or from my stock rom to AICP?
Is this guide for same android version ex. 50.1 to 5.0.1?
Thanks in advance and have a good day
Click to expand...
Click to collapse
then try using his kernel in the boot.img with my roms' ramdisk
Thanks but i have problem
sandeep.sethi said:
then try using his kernel in the boot.img with my roms' ramdisk
Click to expand...
Click to collapse
Thank you it worked, but when device start after bootanimation it show aicp is upgrading optimizing app starting apps ..... and then it restart and then again starting apps... and reboot. Please help. Thank you so much for your support.
Ufoner said:
Thank you it worked, but when device start after bootanimation it show aicp is upgrading optimizing app starting apps ..... and then it restart and then again starting apps... and reboot. Please help. Thank you so much for your support.
Click to expand...
Click to collapse
what files did u replace from lib/hw and lib64/hw
or try taking cm12 of ur phone as base
Sent from my Lenovo K3 Note using Tapatalk
sandeep.sethi said:
what files did u replace from lib/hw and lib64/hw
or try taking cm12 of ur phone as base
Sent from my Lenovo K3 Note using Tapatalk
Click to expand...
Click to collapse
I replaced all files except in lib and lib64 lenovopower.default.so and in drm i don´t replaced drm\libfwdlockengine.so because my stock rom don´t have these files. I tried this method to fix stuck in starting apps... http://www.mtkroms.com/2016/01/bugless-lollipop-exodus-for-mt6592.html and it not worked I searched that some people say the problem is in system apps and i need to replace them, is it true? Thanks, today i will try to port rom again with cm12.1 files If you help me and rom will boot i will donate to you bro :good:
Help with porting
Hello! Thanks for this awesome tutorial!
But now i need some help with porting a ROM
I am porting your BlissPOP rom from Lenovo K3 Note to my Elephone P7000 device!
when i install it with TWRP i get stuck in a bootloop
Can you please help me with this problem, i have followed the tutorial exactly as i should!¨
What should i do?
please help!
//AnStu00
AnStu00 said:
Hello! Thanks for this awesome tutorial!
But now i need some help with porting a ROM
I am porting your BlissPOP rom from Lenovo K3 Note to my Elephone P7000 device!
when i install it with TWRP i get stuck in a bootloop
Can you please help me with this problem, i have followed the tutorial exactly as i should!¨
What should i do?
please help!
//AnStu00
Click to expand...
Click to collapse
I got bootloop too and sandeep.sethi told me how to fix it!
1. You need to change mount points in updater-script
2.Extract blisspop´s rom boot.img and extract boot.img from Elephone CM12.1 http://www.needrom.com/download/elephone-p7000-cyanogenmod-12-1/ and then copy blisspop rom ramdisk and copy it to cm12.1 boot.img and then repack it
Ufoner said:
I replaced all files except in lib and lib64 lenovopower.default.so and in drm i don´t replaced drm\libfwdlockengine.so because my stock rom don´t have these files. I tried this method to fix stuck in starting apps... http://www.mtkroms.com/2016/01/bugless-lollipop-exodus-for-mt6592.html and it not worked I searched that some people say the problem is in system apps and i need to replace them, is it true? Thanks, today i will try to port rom again with cm12.1 files If you help me and rom will boot i will donate to you bro :good:
Click to expand...
Click to collapse
okay try porting again and this tym in ramdisk replace factory rc files
Sent from my Lenovo K3 Note using Tapatalk
Hey guys! Guess what? I'm currently busy on porting the Android N Developer Preview 2 ROM from the Xperia Z3 to Z2! Hope this turns out stable!
Here is the Download link to the ROM below:
Mediafire: http://www.mediafire.com/folder/hp8fnbbxkbb4f/Android N Xperia Z2
IMPORTANT NOTICE!!!
For anyone or everyone saying that I'm, or that this OP is a troll, please stop. This is a WIP, and the ROM did indeed work (when I still had my PC.) I did follow a ROM port guide the first time when it was successful, but now I don't know which one it is. I have contacted some ROM porters for help so I guess that I should wait for an answer to let them help me port it. And for this ROM, it's NOT for stable use yet. This is just for people wanting to test and see if it works at all. If you have your PC at the moment then please and try to fix it yourself. (I'll add you to credits.) Anyway, sorry about the inconvenience, but please don't call me a troll becuase I'm not! �� Cheers.
BUT BEFORE DOWNLOAD, READ THE STEPS BELOW. I'M NOT RESPONSIBLE FOR ANY DEVICE BRICKS ETC. THIS ROM IS FOR UNLOCKED BOOTLOADER PHONES ONLY HAVING MODEL NUMBER OF D6503.
Better safe then sorry. Create a ROM backup of your device in TWRP before installing the ROM in Recovery! Download ZipMe from the Play Store to backup some of your important data!
1: Download all of the files that you want to flash from the link given above and place them in the Root of your sdcard.
3: Download the updater-script FOR ROM FIX file and rename the file to updater-script.
4: Extract the ROM and replace the updater-script from the one you downloaded earlier with the one in the ROM (META-INF/google/com/android folder I think.). REZIP the ROM.
5: Reboot into recovery. Click on Wipe then "Adcanced Wipe." Wipe Dalvik Cache, Cach, System, Data, and Internal Storage.
6: Go back after finished. Flash the Android N ROM, then the Optional files. (Root, Media Apps, & And Smoother Boot Animation, backed up data etc.)
7: Flash the custom Kernel. (Link: http://forum.xda-developers.com/xperia-z2/development/kernel-advanced-stock-kernel-t3347413)
8: Reboot and Enjoy!!!
If anything isn't working or your stuck in a bootloop, try and flash the bootloop fix file from here: https://mega.nz/#!AJcwERiQ!FUmk6eS5aoVsFSZ1f4WZIELIt7sckPCj11n0AIdCNzU
If your still stuck in a bootloop, then the ROM may not be compatible with your device. Use Flashtool to flash back to Lollipop/Marshmallow and wait for a ROM that's compatible with your Phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THANKS!!!
BTW this ROM is different from the one i installed. i have managed and tried to fix some issues like the camera, but if anything isn't working then just please report it. Thanks.!
Below Are Some Problems That You May Encounter.
-The Multi-Window is EXTREMELY laggy.
-Some apps don't work such as the Beta Program App Settings. (But then again, it's expected from a port. XD)
-Recovery (TWRP) may no longer work. You can try and install a Kernel and Recovery your self, but be sure to make a Backup before risking your phone into a Bootloop.
-My Bootloader is unlocked, so I HIGHLY recommend only flashing this ROM if you have a Unlocked Bootloader. If not, wait for a Locked Bootloader version!
-No more Sony Media Apps (Walkman Music, Album, Video etc.) after flashing ROM, so flash the Sony Media Apps zip after ROM to restore the Media Apps.
-The Boot Animation is EXTREMLY slow and laggy, (5-8fps) so please flash the Smoother Boot Animation zip after ROM flashed to ensure a smoother, 30fps Boot Animation.
I haven't encountered any other problems as of now, but I will update the list if I find a bug! And once I receive a problem or bug, I will try to patch it and upload it as a Flashable zip file to fix the bug. A Screenshot of Home Screen from Z2 Android N ROM is attached below...
Once the link is given and doesn't work on your device, just tell me the problem that it's going through, give me your device details, (LB or UB device, Model number, IMEI etc.) and I'll double check the ROM and will try to make supported for your device!
As you can see in the screenshot attachment down below, i have changed some of my icons (like the app icons and status bar icons) back to stock Xperia. I wasn't a BIG fan of all of the AOSP icons.
Upcoming ROM Information.
Contributers
Brandon Nel
Thiagomesa
pollonamid
hiredantispammer
ROM OS Version: N
ROM Kernel: Z2 Marshmallow 6.0.1 Kernel
ROM Firmware Required: At least 23.5.A.0.486
Based On: Android N DP2
Version Information
Status: BETA
Current Stable Version: N/A
Current Beta Version: 2016/04/27
Stable ROM Release Date: May 3 2016
waiting you.:good:
carlito-lt26i said:
waiting you.:good:
Click to expand...
Click to collapse
Guess what? i'm already busy zipping all the files together ready for upload. The upload link will be available around 3 May 2016 since i can't upload now due to TERRIBLE Upload speed. next week will have access to much faster upload speeds and I will upload the download link then. Thanks for comment!
Will it work on LB also?
Brandon Nel said:
Guess what? i'm already busy zipping all the files together ready for upload. The upload link will be available around 3 May 2016 since i can't upload now due to TERRIBLE Upload speed. next week will have access to much faster upload speeds and I will upload the download link then. Thanks for comment!
Click to expand...
Click to collapse
Bro, once you got the zip ready and uploaded, I can help uploading it to other sites like mega or drive as well. Just hit me up or allow me. My internet is fast AF. The work you're doing here is outstanding.
vikash1994b said:
Will it work on LB also?
Click to expand...
Click to collapse
No sorry. You can try but do a backup first! Link is coming 3 may 2016.
hiredantispammer said:
Bro, once you got the zip ready and uploaded, I can help uploading it to other sites like megaupload or drive as well. Just hit me up or allow me. My internet is fast AF. The work you're doing here is outstanding.
Click to expand...
Click to collapse
thanks but I have no clue on how to share a file to upload without uploading it to begin with. I will be happy to share it but i don't know how it works. Please help! :0
Brandon Nel said:
No sorry. You can try but do a backup first! Link is coming 3 may 2016.
Click to expand...
Click to collapse
Hmm well thnkx for ur work
Btw hw is the rom and bugs?
vikash1994b said:
Hmm well thnkx for ur work
Btw hw is the rom and bugs?
Click to expand...
Click to collapse
The ROM is working pretty good so far. It isn't 100% fast and stable but it works pretty well. For the bugs, the camera is most of the time unresponsive (Probably because I forgot to change the camera settings and stuff before installing it.) The camera also sometimes force closes. As for the Multi-Window, it's almost totally unusable but I think this is because of the CPU and not the ROM. And some apps also don't work at all, such as the Beta Program App Settings, The Notification bar glitching too small etc. Hopefully i will fix these bugs before final upload! Fingers crossed. X0
Brandon Nel said:
thanks but I have no clue on how to share a file to upload without uploading it to begin with. I will be happy to share it but i don't know how it works. Please help! :0
Click to expand...
Click to collapse
Yeah, you'll have to at least upload it to Google Drive or Mega first.
hiredantispammer said:
Yeah, you'll have to at least upload it to Google Drive or Mega first.
Click to expand...
Click to collapse
Sorry then. I'll upload it on 2 or 3 May. Just be patient!
hiredantispammer said:
Yeah, you'll have to at least upload it to Google Drive or Mega first.
Click to expand...
Click to collapse
When I upload it to Dropbox or Drive first, then I will share the link for you to mirror to other sites such as Mega.
wow. great work!
Wow i don't receive the marshmallow update via OTA and you are working in android N.
that's very nice Thanks for all your dedication to have update the Xperia Z2. :good:
zierra05 said:
Wow i don't receive the marshmallow update via OTA and you are working in android N.
that's very nice Thanks for all your dedication to have update the Xperia Z2. :good:
Click to expand...
Click to collapse
Download the FTF via Xperifirm. MM's version number ends in .570.
Then flash using Flashtool. You can choose to wipe or not to wipe data if you're coming from stock lollipop. Just uncheck 'wipe data'. If you follow the steps properly, you should have a smooth upgrade to MM!
Also - could you release a version without the edited status bar icons etc?
Multiwindow maybe working when edit buildprop debug to userdebug ?
This is crazy, only few weeks after the official mm ROM we be gettin Android N. I'm hella shocked right now. We own it to my bruh Brandon
---------- Post added at 11:50 AM ---------- Previous post was at 11:46 AM ----------
http://forum.xda-developers.com/showthread.php?t=2772879
Ur ROM might work wit this recovery
good job！！！
Hi. First thank you for doing this.
You could provide us some information what you did with the N Z3 build to make it work on Z2 so we can reproduce it. I guess you used the Z3 system image and replaced the kernel with a Z2 one. What else was needed to make it work?
Thank you very much.
Viper OS 7.1.2 cross ported for MT6580
Lollipop 5.1.1 devices using stock Kernel 3.10.72+
Now with SP Flash Tool files for direct flashing
BETA version note:
This release is not in a stable state yet, however has most functions available.
Releasing to allow others to port to their devices. I recommend using Vysor during intial set up.
Increase font size and screen size (in screen settings) to MAX.
Bundled with Magisk v17.1, root checker, and Universal Launcher
Working:
Ril (Calls, Data, SMS)
Wifi
Lots more
Not working:
Bluetooth (working on this)
So far...
Info:
Rom Name: Viper OS
Rom Version: v3.1.1 Coral
Base: LineageOS
Rom OS Version: Android Nougat v7.1.2
Stock Info:
Stock Device: Finow X5 AIR / LEMFO LEM 5 Pro
Stock OS Version: Android Lollipop v5.1.1
Chipset: MediaTek - MT6580
Kernel: Linux 3.10.72+
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to Install:
*PLEASE MAKE SURE YOU HAVE A FULL BACKUP
BEFORE PROCEEDING...*
TWRP
-DOWNLOAD LINK
-Boot into recovery mode [ adb reboot recovery ]
-Wipe : Data, Cache, Dalvik, System
-Install ViperOSBetav2.zip
-After completed install Gapps
-Wipe Dalvik/Art and Cache
-Reboot system
SP Flash Tool
-Find a good tutorial for setting up SPFT - there is too much for me to rewrite here and get it right
-Load Scatter file from download -----> LINK
-Make sure only download is selected in SPFT
-Hit download and connect watch whilst powered OFF
-Wait for Success
-Reboot system
Please allow some time for initial boot. The spinning logo will be onscreen for 5+ minutes.
If flashing by SP Flash Tool, this will allocate 13Gb to System storage and 1Gb to user storage.
You will also need to register you device with Google Play so follow an online proceedure for
pulling your device ID and authorizing it.
I try and release a storage fix patch for ther SPFL version.
As this ROM was compiled by another team, please see their release credits below:
Credits:
Lineage OS Team
Viper OS Team
Tanvir Ahmed
Vgdn1942
Tribetman
Pedro P DarkKiller
Samiul Islam Shawon
Android GSM BD
And Many More
Hello,
Can I also take the Rom for my LEMFO LEM x?
Thank you
*
Cool ! I just saw your thread !! Why the he'll didn't I know about this earlier (lol) .
It should work in lemfo y3 (mtk6580) , will test it soon and report , may I modify it ?
jesvi said:
Cool ! I just saw your thread !! Why the he'll didn't I know about this earlier (lol) .
It should work in lemfo y3 (mtk6580) , will test it soon and report , may I modify it ?
Click to expand...
Click to collapse
Of course feel free to mod it to get it working on more devices. Just if you post it up please copy the credits so the work by the teams involved is recognized (just look at the end of my post for their details)
I would suggest you try the 5.1 custom ROM I uploaded as this is much more stable and my daily driver. Battery life is off the scale compared to stock OS, and everything except the sensors work. Who really needs to know their fake heart rate anyway...
I also have a EMUI ROM available if you want it, but the dpi is messed up and as such you need to drive the icon size way down to get the screen to look usable - which in turn makes it unusable. However you might have better luck on a different watch.
Keep us updated and share if successful.
Hi,
I have tried the ROM on my LEM5 (not Pro) without enabling the pre-loader. At first everything works fine when going through the initial setup, but right after getting to the home screen it hangs and gets into a boot loop unfortunately. So had to revert back to my previous ROM, do you think it would possible to create a non-Pro version as well?
Thanks.
Braas000
braas000 said:
Hi,
I have tried the ROM on my LEM5 (not Pro) without enabling the pre-loader. At first everything works fine when going through the initial setup, but right after getting to the home screen it hangs and gets into a boot loop unfortunately. So had to revert back to my previous ROM, do you think it would possible to create a non-Pro version as well?
Thanks.
Braas000
Click to expand...
Click to collapse
Unfortunately I only own an X5 Air so wouldn't be able to test anything I ported for other devices. I don't want to take up peoples time asking them to test things out that have a high chance of not working. Its just 10 fold easier having the device at hand to debug it.
I personally found this build too buggy for my liking, and I experienced the occasional reboot / kernel panic.
Have you tried the Resurrection Rom (5.1)? - its far more stable.
I just done this to see if nougat could run on the older kernel.
Thanks for your response, I will give the Resurrection Rom a try.
X-Bo V5 handset with MT6580 and 3.10.72 kernel SPFT
Hi,
I have an X-Bo V5 handset with an MT6580 chipset and 3.10.72 kernel. Do you know where I can get an custom rom based on Lineage OS for this, NOT using TWRP (must be SP Flash Tool).
I thought your rom was it, but I realise it's for a smart watch! The download process completed with a success tick, but it bricked my phone lol. Luckily I was able to restore the stock rom.
Any ideas where I can get a Lineage OS based rom for X-Bo V5 handset with MT6580 chipset and 3.10.72 kernel? Must have scatter file for installation using SP Flash Tool, twrp cannot work on this device.
Peter
pmckinley said:
Hi,
I have an X-Bo V5 handset with an MT6580 chipset and 3.10.72 kernel. Do you know where I can get an custom rom based on Lineage OS for this, NOT using TWRP (must be SP Flash Tool).
I thought your rom was it, but I realise it's for a smart watch! The download process completed with a success tick, but it bricked my phone lol. Luckily I was able to restore the stock rom.
Any ideas where I can get a Lineage OS based rom for X-Bo V5 handset with MT6580 chipset and 3.10.72 kernel? Must have scatter file for installation using SP Flash Tool, twrp cannot work on this device.
Peter
Click to expand...
Click to collapse
There only appears to be official firmware for the X-Bo that I've came across anyway. If TWRP is unavailable for the device then this would probably attribute to the lack of custom firmware available. Your best bet would be finding a generic MT6580 rom and porting it into your existing SP files.
You only really need system.img and boot.img however will than more likely - unless you are very lucky with file sizes - need to create a fresh scatter file. Ive used WR_MTK_v2.30 a few times and the scatter function works well. There are some excellent guides here on xda.
Good luck.
Thanks CerebralFlex!
Can you recommend a no-frills generic MT6580 rom I could try? I’ve clicked on so many dead links lol
Peter
Hi, Im a little confused with this custom rom thing. Ive got a Phillips S358 phone with the processor and kernel specified on the op, will it work or is it only for some specific devices?
pmckinley said:
Thanks CerebralFlex!
Can you recommend a no-frills generic MT6580 rom I could try? I’ve clicked on so many dead links lol
Peter
Click to expand...
Click to collapse
Sorry for the delay mate; its hard to suggest a generic rom cause peoples idea of generic differs a fair bit, but if I was too suggest anything, it would be Lineage OS. See if you can find a MT6580 port, or better yet, try and find a phone similar in hardware to your X-Bo and see if there is one for that.
By this I mean, I'm using the Finow X5 smartwatch, and this shares very similar hardware to say the Infinix X510 (Hot 2) so I can near enough get any rom for the X510 booting on the smartwatch.
Just keep an eye on your kernel level and and your good to go if your current kernel matches.
So say: https://forum.xda-developers.com/hot-2/orig-development/rom-t3596838
If your X-Bo is running Marshmallow and 3.18.x then this has a good chance at working.
Vlurr said:
Hi, Im a little confused with this custom rom thing. Ive got a Phillips S358 phone with the processor and kernel specified on the op, will it work or is it only for some specific devices?
Click to expand...
Click to collapse
Hi
There is a good chance it will work yes, but you will need to port it using your stock resources. Pretty much as long as the ROM matches your processor and kernel level then it will be possible to get it to boot up. Its just a matter of if any specific hardware (native to Phillips) is used, you will need to adapt the drivers in the ROM to utilize it. So things like the camera for example is a pain to get working and even some of the most experienced chefs out there cant get it to work properly.
All part of the fun and games learning to port software.
But in short, no, this ROM as downloaded, is for the Finow X5 smartwatch. But nothing stopping you importing your kernel to the boot.img and giving it a bash.
CerebralFlex said:
There only appears to be official firmware for the X-Bo that I've came across anyway. If TWRP is unavailable for the device then this would probably attribute to the lack of custom firmware available. Your best bet would be finding a generic MT6580 rom and porting it into your existing SP files.
You only really need system.img and boot.img however will than more likely - unless you are very lucky with file sizes - need to create a fresh scatter file. Ive used WR_MTK_v2.30 a few times and the scatter function works well. There are some excellent guides here on xda.
Good luck.
Click to expand...
Click to collapse
Hi can you help with creating the fresh scatter file, what are the steps??
Peter
Can i port it for a mobile phone
I use the x5 air and when I get into this rom, the finow logo has been flashing, unable to access the boot logo. So how can I fix this error, thanks. Sorry for my bad english
Reflash stock ROM using SP Flash Tool
I'm not sure why it wont boot for you, I suggest using TWRP to flash the Lineage or RR ROM I posted a while back. These both work better than Viper.
I downloaded all 3 of your Roms and none worked , I use TWRP 303 by jemmini
CerebralFlex said:
Viper OS 7.1.2 cross ported for MT6580
Lollipop 5.1.1 devices using stock Kernel 3.10.72+
Now with SP Flash Tool files for direct flashing
Stock Info:
Stock Device: Finow X5 AIR / LEMFO LEM 5 Pro
Stock OS Version: Android Lollipop v5.1.1
Chipset: MediaTek - MT6580
Kernel: Linux 3.10.72+
Click to expand...
Click to collapse
Can you share the rom link again? I want to port it for my device
Hello, Please someone who has the rom that can upload it again, we would be very grateful since the link is broken
I writing this post to give you some tools to boot GS'i
This post will be get updates in the past of the days/weeks/months
Always used XPerience 13 as vendor
How to install MIUI:
Download MIUI from: https://mirrors.lolinet.com/firmware/gsi/
Install permissiver_v4.zip
Install Fix boot in MIUI GSI:
Basketbuild Download
SourceForge Download
MD5sum: 2c8095915f7e71268fe1875b3908aa79
Google apps fix (install as normal apk , reboot and configure) Credits to PriQue77
Download link: https://drive.google.com/file/d/1KX8WLYxGqfIkerFFRl21VMeQHDGSjTu4/view?usp=drivesdk
Restart and wait
Enjoy!!
Screenshots: MIUI
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bugs:
Camera
NFC
Adb due it need to have mi account and that apps is crashing xD but im not ported the GSI so i can't do much.
OOS PIE from OP7:
How to install MIUI: in progress
Download MIUI from: https://mirrors.lolinet.com/firmware/gsi/
Install permissiver_v4.zip
Download our temporally fixes:
Download from basketbuild
Download from SourceForge
Google apps fix (install as normal apk , reboot and configure) Credits to PriQue77
Download link: https://drive.google.com/file/d/1KX8WLYxGqfIkerFFRl21VMeQHDGSjTu4/view?usp=drivesdk
Screenshots:
Bugs:
NFC
Donate:
http://paypal.me/TheXPerienceProject
Reserved
You use xpe 13 as vendor ? If you get working HAL3 it will be milestone !!! . NFC maybe can be enabled/stabilised by magisk module .
sebx_g1 said:
You use xpe 13 as vendor ? If you get working HAL3 it will be milestone !!! . NFC maybe can be enabled/stabilised by magisk module .
Click to expand...
Click to collapse
XPerience 13 as vendor at this moment i cant enable adb in miui so other bug added in the list about NFC with magisk HELL NO!, i will fix it
TeamMex said:
XPerience 13 as vendor at this moment i cant enable adb in miui so other bug added in the list about NFC with magisk HELL NO!, i will fix it
Click to expand...
Click to collapse
With xpe 12.1 as vendor magisk fix for nfc worked well. But of course it is better to have it working out of the box. MIUI was one gsi which always don't boot - only very old port I booted once . OOS is easier - even latest Erfan's builds boots ok .
You OC our poor 625 to 2.75 ghz in miui ???
sebx_g1 said:
With xpe 12.1 as vendor magisk fix for nfc worked well. But of course it is better to have it working out of the box. MIUI was one gsi which always don't boot - only very old port I booted once . OOS is easier - even latest Erfan's builds boots ok .
You OC our poor 625 to 2.75 ghz in miui ???
Click to expand...
Click to collapse
Camera Fixed In OOS and miui in newer builds of XPerience you will not need the fixes (well only in miui cuz it need a proprietary xml)
TeamMex said:
Camera Fixed In OOS and miui in newer builds of XPerience you will not need the fixes (well only in miui cuz it need a proprietary xml)
Click to expand...
Click to collapse
Is something missing in post yet - additional fix file ? Man - 3h of work and you fixed that ? Will camera work also on not Erfan's ported Gsi - eg. Havoc 2.6 ?
Camera working = gcam - yes ?
sebx_g1 said:
Is something missing in post yet - additional fix file ? Man - 3h of work and you fixed that ? Will camera work also on not Erfan's ported Gsi - eg. Havoc 2.6 ?
Camera working = gcam - yes ?
Click to expand...
Click to collapse
I only tested in those both for the camera fix you need to flash the OP7 gsi fixes
OP updated
TeamMex said:
I only tested in those both for the camera fix you need to flash the OP7 gsi fixes
OP updated
Click to expand...
Click to collapse
So you merged patch for MIUI with OOS together and add camera fix for both ? Busy night full of flashing is comming - I like it
sebx_g1 said:
So you merged patch for MIUI with OOS together and add camera fix for both ? Busy night full of flashing is comming - I like it
Click to expand...
Click to collapse
you need to flash both xD in miui the miui and OOS fixes
MIUI GSI is - hardcore opponent :/ It don't see my storage also brightness need fix . I have patch which partialy helps with brightness but - no visible storage is a problem .
Now I am looking at gsi Havoc 2.6 - camera still don't work [emoji58] but Bluetooth, NFC, lte+ data and maybe wifi works - no its not work can't be switched on [emoji58]. Very fast rom. When I return to home I do logs, maybe @TeamMex you could be able look at them and try to fix camera Hal3.
sebx_g1 said:
MIUI GSI is - hardcore opponent :/ It don't see my storage also brightness need fix . I have patch which partialy helps with brightness but - no visible storage is a problem .
Now I am looking at gsi Havoc 2.6 - camera still don't work [emoji58] but Bluetooth, NFC, lte+ data and maybe wifi works - no its not work can't be switched on [emoji58]. Very fast rom. When I return to home I do logs, maybe @TeamMex you could be able look at them and try to fix camera Hal3.
Click to expand...
Click to collapse
idk if miui support adopted storage i mean XD maybe is broken(?) idk if mi mix2s support sdcard
I need to check the brightness issue you have the briightnes fix?
TeamMex said:
idk if miui support adopted storage i mean XD maybe is broken(?) idk if mi mix2s support sdcard
I need to check the brightness issue you have the briightnes fix?
Click to expand...
Click to collapse
Yes look at that patches - they are not tuned for MZP to bright screen is setup without patch it is to dark [emoji2957].
https://mega.nz/#!A0YHHQzZ!MaobUtQVto8MpNJtaPTk0GNb_VqgzxSTDm-sY9V37V0
I didn't tested that
https://mega.nz/#!J8RHWSSY!3rO4NywLqnNAS2wDNWjBvJy4XG1JwNXYrSvJ-pRG1m0
Wysłane z mojego XT1635-02 przy użyciu Tapatalka
sebx_g1 said:
Yes look at that patches - they are not tuned for MZP to bright screen is setup without patch it is to dark [emoji2957].
https://mega.nz/#!A0YHHQzZ!MaobUtQVto8MpNJtaPTk0GNb_VqgzxSTDm-sY9V37V0
I didn't tested that
https://mega.nz/#!J8RHWSSY!3rO4NywLqnNAS2wDNWjBvJy4XG1JwNXYrSvJ-pRG1m0
Wysłane z mojego XT1635-02 przy użyciu Tapatalka
Click to expand...
Click to collapse
I'll check thanks
I suppose that miui and OOS supports adopted storage even they normally not use it. I think it is broken only on connection vendor-gsi because gsi see storage config properly but only can't access it.
Wysłane z mojego XT1635-02 przy użyciu Tapatalka
thank you!
@TeamMex
I am now temporary on xpe 13 build 13/06 + gsi Havoc 2.6 official.
Data lte works, NFC too, no wifi and any camera I have logs for it. To test Bluetooth.
Plus crash log from gcam :
https://del.dog/ayoxedahot
Wysłane z mojego XT1635-02 przy użyciu Tapatalka
sebx_g1 said:
@TeamMex
I am now temporary on xpe 13 build 13/06 + gsi Havoc 2.6 official.
Data lte works, NFC too, no wifi and any camera I have logs for it. To test Bluetooth.
Plus crash log from gcam :
https://del.dog/ayoxedahot
Wysłane z mojego XT1635-02 przy użyciu Tapatalka
Click to expand...
Click to collapse
your log is 06-15 13:36:17.719 F/linker ( 1880): CANNOT LINK EXECUTABLE "/vendor/bin/hw/wpa_supplicant": library "<email omitted>" not found telling XD a library with @ is a email i cant see what library is "missing"
I moving libbinder and libutils to vndk seems needed in AOSP
can you share XD other log ? but with no email omission you can edit them manually to remove your email if needed.
Edit:
Please test
https://basketbuild.com/filedl/devs...xperience-13.0.0-20190616-NIGHTLY-addison.zip
Dont expect wifi fix until I get new logs
TeamMex said:
your log is 06-15 13:36:17.719 F/linker ( 1880): CANNOT LINK EXECUTABLE "/vendor/bin/hw/wpa_supplicant": library "" not found telling XD a library with @ is a email i cant see what library is "missing"
I moving libbinder and libutils to vndk seems needed in AOSP
can you share XD other log ? but with no email omission you can edit them manually to remove your email if needed.
Edit:
Please test
https://basketbuild.com/filedl/devs...xperience-13.0.0-20190616-NIGHTLY-addison.zip
Dont expect wifi fix until I get new logs
Click to expand...
Click to collapse
Maybe today in 10h I made new logs as I understand in name of missing library is @ and name Was deleted in log yes?
In that location in xpe13 system/hw sits file:
[email protected]
and in system many others files with @ in its name - that is crazy to add @ in file names, Google that is crazy!!! [emoji23]
Anyway on screenshot are wifi related files some of them.
Wysłane z mojego XT1635-02 przy użyciu Tapatalka
sebx_g1 said:
Maybe today in 10h I made new logs as I understand in name of missing library is @ and name Was deleted in log yes?
In that location in xpe13 system/hw sits file:
[email protected]
and in system many others files with @ in its name - that is crazy to add @ in file names, Google that is crazy!!! [emoji23]
Anyway on screenshot are wifi related files some of them.
Wysłane z mojego XT1635-02 przy użyciu Tapatalka
Click to expand...
Click to collapse
I want to help you guys but meanwhile I can't flash my phone as I need it to be on all-time. Once I get free I will help you with testing.