When you found a bug when porting a ROM, you can try to fix using
this methods!
Just replace it from Stock ROM to your Custom ROMs.
Bootloop when porting:
/system/lib/libandroid_runtime.so
/system/lib/libandroid_servers.so
/system/lib/libmedia_jni.so
*Repack boot.image
Showing black screen after logo:
\system/lib/libMali.so
Sensors :
/system/bin/akmd*
/system/lib/libsensors.so
/system/lib/libms3c_yamaha.so
/system/etc/firmware(folder)
/system/bin/servicemanager
Bluetooth :
/system/bin/bd_prov
/system/bin/uim*
/system/bin/hcid
/system/bin/bluetooth*
/system/bin/hciattach
/system/bin/sdptool
/system/xbin/hciconfig
/system/bin/brcm_patchram_plus
Wifi :
/system/bin/netcfg
/system/bin/dhcpcd
/system/bin/ifconfig
/system/bin/hostap
/system/bin/hostapd
/system/bin/hostapd_bin
/system/bin/pcscd
/system/bin/wlan*
/system/bin/wpa*
/system/bin/netd-> Fix wifi hotspot
/system/lib/libhardwarelegacy.so-> Fix wifi
/system/etc/wifi (folder)
/system/etc/firmware (folder)
Camera :
system/lib/libfeatureio.so-cameranotworking
/system/etc/media_profiles.xml
/system/lib/libcamera.so
/system/lib/liboemcamera.so
\system\lib\hw\camera.default.so
\system\lib\libcamera_client.so
\system\lib\libcameracustom.so
\system\lib\libcameraprofile.so
\system\lib\libcameraservice.so
\system\lib\libmhal.so
\system\lib\libmhalcontent.so
\system\lib\libmhaldrv.so
\system\lib\libmhalmdp.so
\system\lib\libmhalpipe.so
\system\lib\libmhalscenario.so
\system\lib\libmhalutility.so
\system\etc\permission\android.hardware.camera.front.xml
\system\lib\libOmx*.so-fixcamcoder
\system\lib\libfeatureo.so-fixcamfocus
#camera not working or force close or any other problem
copy all libs starting with /libcam*.so
#Camera showing wrong model in pic property?
Change model in build.prop
Still not working? Replace following file from STOCK to PORT
system/lib/libexif.so
SD card/Memory:
/system/bin/vold
\system\etc\vold.fstab->edit file for swap internal and external
\system\etc\vold.fstab.nand
*Note:If not present leave this. from kitkat4.4.x this file has been moved into boot.img
Storage not mounting:
Decompile framework-res.apk using apk tool or apk multitool and
replace following file from STOCK framework-res.apk to PORT
framework-res.apk
/res/xml/storage_list.xml
GPS:
\system\xbin\libmnlp
/system/etc/gps.conf
Touch Screen (Haptic):
/system/usr
/system/usr\keylayout\Generic.kl->fixHomeKey
Sim1/2 (RIL):
\system\etc\firmware\modem.img
\system\etc\permission(RIL)
/system/bin/stmd
/system/bin/rild*
/system/etc/rril
Audio/Sound:
\system\lib\libaudio*.so
Ads:
/system/etc/hosts->replace with new files or use tweak.
Resolution problem:
open build.prop and add following line
ro.sf.lcd_density=240
[ex:240 but your dpi may be different]
Pixalation in video:
Replace following file from STOCK to PORT
system/lib/libvcodecdrv.so
Flipped touch screen:
Replace following files from STOCK to PORT
system/lib/libinput.so
LED not working:
Replace following files from STOCK to PORT
system/lib/libfeatureio.so
Fix Network / 3G Network:
/system / etc/agps_profiles_conf
/system / etc/APNs-conf
/system / etc/epo-conf
/system / etc/spn-conf
/system / etc/virtual-spn-conf-by-efspn
/system / etc/virtual-spn-conf-by-IMSI
#Most of it works.
Need some guides
[email protected]!C said:
When you found a bug when porting a ROM, you can try to fix using
this methods!
Just replace it from Stock ROM to your Custom ROMs.
Bootloop when porting:
/system/lib/libandroid_runtime.so
/system/lib/libandroid_servers.so
/system/lib/libmedia_jni.so
*Repack boot.image
Showing black screen after logo:
\system/lib/libMali.so
Sensors :
/system/bin/akmd*
/system/lib/libsensors.so
/system/lib/libms3c_yamaha.so
/system/etc/firmware(folder)
/system/bin/servicemanager
Bluetooth :
/system/bin/bd_prov
/system/bin/uim*
/system/bin/hcid
/system/bin/bluetooth*
/system/bin/hciattach
/system/bin/sdptool
/system/xbin/hciconfig
/system/bin/brcm_patchram_plus
Wifi :
/system/bin/netcfg
/system/bin/dhcpcd
/system/bin/ifconfig
/system/bin/hostap
/system/bin/hostapd
/system/bin/hostapd_bin
/system/bin/pcscd
/system/bin/wlan*
/system/bin/wpa*
/system/bin/netd-> Fix wifi hotspot
/system/lib/libhardwarelegacy.so-> Fix wifi
/system/etc/wifi (folder)
/system/etc/firmware (folder)
Camera :
system/lib/libfeatureio.so-cameranotworking
/system/etc/media_profiles.xml
/system/lib/libcamera.so
/system/lib/liboemcamera.so
\system\lib\hw\camera.default.so
\system\lib\libcamera_client.so
\system\lib\libcameracustom.so
\system\lib\libcameraprofile.so
\system\lib\libcameraservice.so
\system\lib\libmhal.so
\system\lib\libmhalcontent.so
\system\lib\libmhaldrv.so
\system\lib\libmhalmdp.so
\system\lib\libmhalpipe.so
\system\lib\libmhalscenario.so
\system\lib\libmhalutility.so
\system\etc\permission\android.hardware.camera.front.xml
\system\lib\libOmx*.so-fixcamcoder
\system\lib\libfeatureo.so-fixcamfocus
#camera not working or force close or any other problem
copy all libs starting with /libcam*.so
#Camera showing wrong model in pic property?
Change model in build.prop
Still not working? Replace following file from STOCK to PORT
system/lib/libexif.so
SD card/Memory:
/system/bin/vold
\system\etc\vold.fstab->edit file for swap internal and external
\system\etc\vold.fstab.nand
*Note:If not present leave this. from kitkat4.4.x this file has been moved into boot.img
Storage not mounting:
Decompile framework-res.apk using apk tool or apk multitool and
replace following file from STOCK framework-res.apk to PORT
framework-res.apk
/res/xml/storage_list.xml
GPS:
\system\xbin\libmnlp
/system/etc/gps.conf
Touch Screen (Haptic):
/system/usr
/system/usr\keylayout\Generic.kl->fixHomeKey
Sim1/2 (RIL):
\system\etc\firmware\modem.img
\system\etc\permission(RIL)
/system/bin/stmd
/system/bin/rild*
/system/etc/rril
Audio/Sound:
\system\lib\libaudio*.so
Ads:
/system/etc/hosts->replace with new files or use tweak.
Resolution problem:
open build.prop and add following line
ro.sf.lcd_density=240
[ex:240 but your dpi may be different]
Pixalation in video:
Replace following file from STOCK to PORT
system/lib/libvcodecdrv.so
Flipped touch screen:
Replace following files from STOCK to PORT
system/lib/libinput.so
LED not working:
Replace following files from STOCK to PORT
system/lib/libfeatureio.so
Fix Network / 3G Network:
/system / etc/agps_profiles_conf
/system / etc/APNs-conf
/system / etc/epo-conf
/system / etc/spn-conf
/system / etc/virtual-spn-conf-by-efspn
/system / etc/virtual-spn-conf-by-IMSI
#Most of it works.
Click to expand...
Click to collapse
Why don't you post some Rom Porting Guides.. I Know That There Are Lots Of Them Available Here On XDA But I Tried Them (Result : Stuck on bootanimation or bootloops).:silly:. i mean none of them worked.. if you are having experience with porting Please Put up some porting guides also..:good:
Yeah
mohit sethi said:
Why don't you post some Rom Porting Guides.. I Know That There Are Lots Of Them Available Here On XDA But I Tried Them (Result : Stuck on bootanimation or bootloops).:silly:. i mean none of them worked.. if you are having experience with porting Please Put up some porting guides also..:good:
Click to expand...
Click to collapse
First things first. Don't quote whole OP.
And the guide I use is this one http://forum.xda-developers.com/showthread.php?t=1908008
[email protected]!C said:
First things first. Don't quote whole OP.
And the guide I use is this one http://forum.xda-developers.com/showthread.php?t=1908008
Click to expand...
Click to collapse
oops sorry for that !
and thanx for guide
Error Loading
matrixex said:
Buddy let's try with some ROMs and this info is very useful I think I will try this with Stock ROM vs liquid smooth lollipop
And here is guide for porting ROM from another device by Rishab Raj
http://forum.xda-developers.com/showthread.php?t=1908008
Oops Someone is already posted this link no prob.
Click to expand...
Click to collapse
Liquid smooth is lollipop based rom......for porting CM13 rom to our jellybean we will need source codes + CM13 device tree and further compiling in ubuntu will give us CM 13 Rom....This method is insane :silly:
Try porting 4.4.x based or 4.1.2 based roms using this guide :good:
mohit sethi said:
Liquid smooth is lollipop based rom......for porting CM13 rom to our jellybean we will need source codes + CM13 device tree and further compiling in ubuntu will give us CM 13 Rom....This method is insane :silly:
Try porting 4.4.x based or 4.1.2 based roms using this guide :good:
Click to expand...
Click to collapse
END
matrixex said:
We already have liquid smooth lollipop by Ahmad hardy just try it.
Click to expand...
Click to collapse
it is the most buggy rom for X/XL
[email protected]!C said:
First things first. Don't quote whole OP.
And the guide I use is this one http://forum.xda-developers.com/showthread.php?t=1908008
Click to expand...
Click to collapse
First thanks for Tips, Let me add this, it'll be very helpful in porting
Nokia X Vendor Files https://github.com/NormandyLP/android_vendor_nokia_normandy
Nokia XL Vendor Files https://github.com/Nokia-xl-legacy/vendor_xl
Is their any way to test the ported rom other than flashing on device
Sent from my Nokia_XL using XDA Free mobile app
There is hissing noise that comes out of the speaker after playing media.
I replaced all audio libs, libcustom_nvram.so
How can i fix it?
zenowaren said:
There is hissing noise that comes out of the speaker after playing media.
I replaced all audio libs, libcustom_nvram.so
How can i fix it?
Click to expand...
Click to collapse
Well, i unpacked stock system.img and flashed via cwm without modifying any files, there is the same problem again. It is not related to port
Related
dsixda's Android Kitchen - Now for Samsung Galaxy S
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy S custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of version 0.178, you can now create your own Galaxy S ROMs with the kitchen.
I'd like to thank Perka for testing and providing feedback, and also for giving me some ideas through his tutorial in his Ultimate ROM Cooking Guide.
[MAIN PAGE] [RELEASE NOTES] [FAQ - page 1] [FAQ - page 2]
PROCEDURE
This guide may be a bit basic right now but I will update it later if required.
First, you need a rooted Samsung Galaxy S with a ClockworkMod custom recovery. The kitchen supports the GT-I9000, but should also support most of its variants, such as the Captivate, Fascinate, Vibrant and Epic.
Visit the Android Kitchen thread to download the kitchen. Then, follow the link to the FAQ which will show you how to install it on Windows, Linux or Mac OS X. Ensure you read the FAQ carefully.
IMPORTANT (DO NOT IGNORE THIS STEP): To verify your variant of the Galaxy S works in the kitchen, read this post.
Put your base ROM(s) under the original_update folder. For the Samsung Galaxy S, there is support for the following formats which can be placed in that folder (you can place multiple ROMs there):
Stock firmware:
factoryfs.rfs (and optionally: cache.rfs, zImage)
PDA.tar.md5 (and optionally: CSC.tar.md5, PHONE.tar.md5)
PDA.tar (and optionally: CSC.tar, PHONE.tar)
TAR/ZIP file containing factoryfs.rfs (optional: cache.rfs, zImage, modem.bin)
TAR/ZIP file containing PDA.tar and others
TAR/ZIP file containing PDA.tar.md5 and others
Custom ROM:
ZIP file originally created by the kitchen from the stock firmware (NOTE: The kitchen does NOT support custom ROMs created through other methods, due to potential file structure incompatibility issues)
Nandroid backup from ClockworkMod recovery
system.img and boot.img
Here are some basic steps to creating your first ROM after you have your base of files under original_update (more options are available in the kitchen):
Start the kitchen with: ./menu
Create a working folder (by choosing your base ROM)
If you used a factoryfs.rfs but then didn't include the cache.rfs, then you have the option to add a cache.rfs later using the Extract CSC script in the Advanced menu's 'Plugins' section.
Optional: Add a rooted kernel (zImage) to the base of your working folder
You can create a ROM without a zImage and thus keep the existing kernel on your device, although keep in mind that a newer ROM may not work with a kernel meant for older ROMs!
If you use the stock kernel (zImage), you can always replace it later with the CF-Root kernel or any other custom/rooted kernel. Just replace the stock zImage anytime before you build the ROM.
Optional: Add a modem.bin to the base of your working folder, or remove the existing modem.bin if you don't want it. You can flash the ROM with or without a modem.bin.
Root your ROM
Add Busybox
In the Advanced options menu: De-odex your ROM
Build ROM
The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin.
Some notes:
Just select the defaults whenever you are asked about something in the kitchen and are unsure whether to type 'y' or 'n'.
There are lots of questions answered in the FAQ in Posts 3 and 4 of the main Android Kitchen thread. So please go through that first if you have any issues.
For the benefit of other readers, and to prevent confusion, please only discuss Samsung Galaxy S in this thread!
Most of all, have patience, take your time and enjoy!!
thanks for info mate exactly wat im looking for
cheers
Thx for this. Working very well.
Very nice guide
Just what i was looking for great
Sent from my GT-I9000 using xda premium
Thanks works very well! *5 stalls *
So i made my first selfmade rom for samsung s5660 Gio but i am getting errors trying to flash in cwm. First error i managed to solve as in the updater-script there were # missing at the mount and unmount options.
Now im having "assert failed: write_raw_image("/tmp/boot.img","boot")" error. Reading up on XDA i saw u mentioned that it has to do with wrong update-binary and someone solved it by adding "edify_def" but i have no clue what that might be.
Any help would be much apreciated.
Also u mention there are 3 update-binary. Any link to all 3 and can i just try with each one of them first?
Edit: adding the updater-script and update-binary
Gvdn said:
So i made my first selfmade rom for samsung s5660 Gio but i am getting errors trying to flash in cwm. First error i managed to solve as in the updater-script there were # missing at the mount and unmount options.
Now im having "assert failed: write_raw_image("/tmp/boot.img","boot")" error. Reading up on XDA i saw u mentioned that it has to do with wrong update-binary and someone solved it by adding "edify_def" but i have no clue what that might be.
Any help would be much apreciated.
Also u mention there are 3 update-binary. Any link to all 3 and can i just try with each one of them first?
Edit: adding the updater-script and update-binary
Click to expand...
Click to collapse
The Gio is not a Galaxy S device. This is where your problem lies. I am not sure how a ROM is constructed for that device.
dsixda said:
The Gio is not a Galaxy S device. This is where your problem lies. I am not sure how a ROM is constructed for that device.
Click to expand...
Click to collapse
So no matter what i try it wont work with kitchen? Damn too bad i was starting to know my way around it now
Kitchen made the whole rom without a problem tho. Using the boot.img option and following Perka guide. Just seems its not generating the Meta file correct.
Do u have any idea to what i asked earlier? If there is only 3 different update-binaries , can i get all 3 and test em out and 1 will work for sure or it wont work no matter what?
I don't know anything about your device, dude. Just copy one from an existing ROM that someone made for your device. Anyways you're asking about a non-Galaxy S phone so you'll probably find more help in the Chef section of the forum or in your device's subforum.
dsixda said:
I don't know anything about your device, dude. Just copy one from an existing ROM that someone made for your device. Anyways you're asking about a non-Galaxy S phone so you'll probably find more help in the Chef section of the forum or in your device's subforum.
Click to expand...
Click to collapse
Ok thx alot. Sadly no subforum for Gio
CWM issue
I'm having a big problem using the kitchen with regards to entering recovery in any custom ROM I make using the kitchen.
Once I flash the ROM everything is fine and dandy in the OS itself, works 100% and all customizations work flawlessly, but once I try to reboot into CWM whether via 3Button or extended power menu/adb, CWM gives a ton of errors saying it cannot mount volumes and basically recovery is useless. The errors are numerous, I'll see if I can post a pic if needed. The important one I'm thinking is "E:/unknown volume for path /sdcard" repeated for /data, /system, /cache, everything.
I tried eliminating sources of error by basically just inserting a JVS rom and pasting in a kernel (Semaphore JVS) without any customizations, and the error still occurs.
Any help?
krazykipa said:
I'm having a big problem using the kitchen with regards to entering recovery in any custom ROM I make using the kitchen.
Once I flash the ROM everything is fine and dandy in the OS itself, works 100% and all customizations work flawlessly, but once I try to reboot into CWM whether via 3Button or extended power menu/adb, CWM gives a ton of errors saying it cannot mount volumes and basically recovery is useless. The errors are numerous, I'll see if I can post a pic if needed. The important one I'm thinking is "E:/unknown volume for path /sdcard" repeated for /data, /system, /cache, everything.
I tried eliminating sources of error by basically just inserting a JVS rom and pasting in a kernel (Semaphore JVS) without any customizations, and the error still occurs.
Any help?
Click to expand...
Click to collapse
I'm having the same problem here with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS, I tried to move to DarkCore_4.0_JVS and the device get into reboots (just after activating lagfix).
its 2 days now that im working on stock rom and trying only to root and deOdex... help?
Will this work for galaxy s 4g? If not, is there any way I can help to add support for it?
bhundven said:
Will this work for galaxy s 4g? If not, is there any way I can help to add support for it?
Click to expand...
Click to collapse
Sorry for the late reply. Check your build.prop's ro.product.device value. If the name doesn't exist under the kitchen's tools/samsung_files/sgs_variants folder then just create a file there with same name.
Unfortunately I don't have the Galaxy S so I cannot test on my own.
dsixda said:
Sorry for the late reply. Check your build.prop's ro.product.device value. If the name doesn't exist under the kitchen's tools/samsung_files/sgs_variants folder then just create a file there with same name.
Unfortunately I don't have the Galaxy S so I cannot test on my own.
Click to expand...
Click to collapse
Looks like the SGH-T959V file exists. Thanks for helping me figure that out!
I am having an issue with wi-fi not be able to connect after i have flashed my build.. and thats about it. I'm not sure whats causing it any ideas?
EDIT:
Was the updater-script, i swapped it out with another and all is well.
There are problem with kernels. I can't change?
is this supported by the sidekick since it has similiar specs to the samsung vibrant?
xtrem88 said:
is this supported by the sidekick since it has similiar specs to the samsung vibrant?
Click to expand...
Click to collapse
If it's basically the same device then it should support it. Just make sure you have an entry in the kitchen for the ro.product.device value. See the note in the 2nd step in Post #1.
This is the discussion and bug report thread about arco68's [ROM][KK][4.4.2][KOT49H] CyanogenMod 11.0 (20140101-UNOFFICIAL)
Downloads and Changelogs:
2014-03-11: CM-11.0 20140311-UNOFFICIAL [DOWNLOAD]
MD5SUM: 4fe488467dfbf33a95e8363bb758871b
Updated Adreno blobs
Synced with CM
Kernel 3.4.82
2014-01-22: CM-11.0 20140122-UNOFFICIAL [DOWNLOAD]
MD5SUM: 65a6dcf31f0cd8917f0447b7bdb761e8
Disabled Low Power Audio (LPA)
New workaround for text glitch (using classic webview)
Fix zoom in camera preview (credits Dorregaray)
2014-01-17: CM-11.0 20140117-UNOFFICIAL [DOWNLOAD]
MD5SUM: 546d101784cbd493607558273459ac6b
Enabled Low Power Audio (LPA)
Fixed VOIP audio
Fixed Netflix playback
USB OTG and zRAM fixes (credits Christopher83)
Kernel 3.4.77
2014-01-10: CM-11.0 20140109-UNOFFICIAL [DOWNLOAD]
MD5SUM: 5688ddd7efccbfdf3d485804543fe8b3
Enable TARGET_USE_QCOM_BIONIC_OPTIMIZATION
Possible workaround for the graphic glitch
Updated media profiles
Increased minimum CPU frequency to 368 MHz
Lowered zRAM size to half of what it was
Kernel 3.4.76
2014-01-06: CM-11.0 20140106-UNOFFICIAL [DOWNLOAD]
MD5SUM: 588e8977250194cb3bd8bedfc6e29c8c
Fixed storage swapping
2014-01-05: CM-11.0 20140105-UNOFFICIAL [DOWNLOAD]
MD5SUM: c577b62973aac5099bdea60b20e3073d
Fixed bluetooth tethering
Implemented storage switching
Increased zRAM allocation and changed setup according to KK specs (old method is removed from CM11)
2014-01-01: CM-11.0 20140101-UNOFFICIAL [DOWNLOAD]
MD5SUM: 57e225a2955e15236c37abb00072ee9d
Switched back to updated camera app (fixed issue with preview)
Allocated more memory for PMEM (should fix issues like switching to video mode in camera app after taking pictures)
2013-12-31: CM-11.0 20131231-UNOFFICIAL [DOWNLOAD]
MD5SUM: 26910b9933dce0ff01137f278c6b49d7
Fixed activity indicators for mobile data
Fixed preview in camera after taking a picture
Enabled ZRAM by default
2013-12-28: CM-11.0 20131228-UNOFFICIAL [DOWNLOAD]
MD5SUM: 9f2c2aae9fa3143c69537e7f67b51ac1
Initial release
GAPPS:
gapps version 20131208 (Not ART compatible)
MD5SUM: a387243442413f0a9153ab1bad149199
Please verify the md5sum to be sure you got the right one.
Note: CM for Galaxy W is provided with no warranty. You are installing this software at your own risk. You may be violating your warranty.
Installation Steps:
Use CWM6.
Warning: Only use this recovery to flash CM-11.0. Otherwise, you risk bricking your phone, or you might experience boot and stability issues!
Wipe data and cache.
Flash update*.zip.
Flash gapps*.zip. You must flash gapps after every upgrade to CM11.0 since /system is formatted, wiping your previous add-ons.
Reboot phone.
After you setup your Google account, reinstall the three apps from Market in order to restore most of your apps, call log and SMS history.
Warning: Do not restore backup data of system apps!
Bugs:
CM-11.0 20140311
-Movie Studio is unstable and can crash or freeze phone
CM-11.0 20140122
-Movie Studio is unstable and can crash or freeze phone
CM-11.0 20140117
-Movie Studio is unstable and can crash or freeze phone
CM-11.0 20140109
-Movie Studio is unstable and can crash or freeze phone
-Storage swapping is not yet implemented in CM11.
CM-11.0 20140106
-Movie Studio is unstable and can crash or freeze phone
-Storage swapping is not yet implemented in CM11.
CM-11.0 20140105
-Movie Studio is unstable and can crash or freeze phone
-Storage swapping is not yet implemented in CM11.
CM-11.0 20140101
-Movie Studio is unstable and can crash or freeze phone
-Storage swapping is not yet implemented in CM11.
Q&A:
-Q:How to enable transparent status bar?
A:Edit build.prop line
Code:
ro.config.low_ram=true
Change "true" to "false"
-Q:How to enable USB Mass Storage?
A:Edit build.prop line
Code:
Persist.sys.usb.config=mtp
Change 'mtp' to 'mass_storage'
How to post a bug:
Please copy the following code in your post and fill in the information:
Version: (For example 20131231)
Bug title: Write the title
Probability of occurrence: Write here "LOW/MEDIUM/HIGH" (depending on how often the bug occurs)
Description: Write how the bug appears and how you solve the bug
Log: Add a logcat if you can
Screenshoot: Make a screenshot
ATTENTION! Posts about bugs caused by custom Kernels or MODs will be ignored! Post them in the specific Kernel / MOD Thread but not here.
thanks for making this discussion thread man
okay let me start my first post here. i guess the feature we're missing atm is sdcard swap.
theoretically this should be done on ramdisk because we can't find vold.fstab anymore. i haven't got time to test this but i think swapping through ramdisk modification should be working
reference here
Can I use the recovery 6.0.44 version ?
The link you provided is not available.
freinet
freinet said:
Can I use the recovery 6.0.44 version ?
The link you provided is not available.
freinet
Click to expand...
Click to collapse
the googledrive link is working
Hhmmmhh, it gives me this : cm_ancora-ota-build1.zip
This is not the recovery I think
freinet
weihan1102 said:
the googledrive link is working
Click to expand...
Click to collapse
when I download recovery from google drive the extension file is .bin? why not .img? so how to flash it?
freinet said:
Hhmmmhh, it gives me this : cm_ancora-ota-build1.zip
This is not the recovery I think
freinet
Click to expand...
Click to collapse
sorry , it is my mistake...i put the right link now.
Racun said:
when I download recovery from google drive the extension file is .bin? why not .img? so how to flash it?
Click to expand...
Click to collapse
it should be .img
weihan1102 said:
it should be .img
Click to expand...
Click to collapse
yes I think is corrupt file because I have bad connection.
after I download again from google drive file extension is .img
Thanks and see u soon I will flash this rom and report again if I found bugs.
Img file is new for me, how to flash?
Til now I have only flashed with recovery and sometimes with odin?
What recovery version is this?
Thanks for help.
freinet
freinet said:
Img file is new for me, how to flash?
Til now I have only flashed with recovery and sometimes with odin?
What recovery version is this?
Thanks for help.
freinet
Click to expand...
Click to collapse
put the recovery file in sdcard then type this in terminal emulator
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
freinet said:
Img file is new for me, how to flash?
Til now I have only flashed with recovery and sometimes with odin?
What recovery version is this?
Thanks for help.
freinet
Click to expand...
Click to collapse
You can use adb shell like above.
Or the easiest way is using http://forum.xda-developers.com/showthread.php?t=2401988 by hornet and educk
There is "Flash RECOVERY" function on "Tools" tab.
hadidjapri said:
thanks for making this discussion thread man
okay let me start my first post here. i guess the feature we're missing atm is sdcard swap.
theoretically this should be done on ramdisk because we can't find vold.fstab anymore. i haven't got time to test this but i think swapping through ramdisk modification should be working
reference here
Click to expand...
Click to collapse
So it depends on kernel?!!
I think when cm finished and released first nightly, there will be more features and SD swap with!
Sent from my GT-I8150 using XDA Premium 4 mobile app
weihan1102 said:
it should be .img
Click to expand...
Click to collapse
Im trying download the recovery from drive, bit only have bin files...
Sent from my GT-I8150 using xda app-developers app
Recovery
I flash this very nice rom with Cmw 6.0.4.4 and not seen any problem...
What should happen?
hadidjapri said:
thanks for making this discussion thread man
okay let me start my first post here. i guess the feature we're missing atm is sdcard swap.
theoretically this should be done on ramdisk because we can't find vold.fstab anymore. i haven't got time to test this but i think swapping through ramdisk modification should be working
reference here
Click to expand...
Click to collapse
yes I confirm your theory in a 4.4 galasxy s rom i read this:
Kernel for switching internal & external SD
Because vold.fstab is no longer used and has been integrated in fstab.aries (which can only be changed before compiling the kernel, as it ends up in the ramdisk), I made a special kernel version with switched SD cards:
he make two kernel, one normal and one with swap SD
skylender96 said:
I flash this very nice rom with Cmw 6.0.4.4 and not seen any problem...
What should happen?
Click to expand...
Click to collapse
it will no any problem i think.
Spirit FM is tested and working fine
it is a good news for people who needs FM radio
PS: you need to set Method qdsp5v2 Altern to get the sound (if your phone freeze after change the Method,just long press power button , after restart Spirit FM will works fine)
i know is a stupid question, u can make the status bar trasparent on the lockscreen like cm11 by penguin
Finitore said:
i know is a stupid question, u can make the status bar trasparent on the lockscreen like cm11 by penguin
Click to expand...
Click to collapse
actually statue bar doesn't transparent is because low_ram is enabled
you can simply turn off it by change the
ro.config.low_ram=true
Click to expand...
Click to collapse
to
ro.config.low_ram=false
Click to expand...
Click to collapse
in build.prop to get the transparent status bar
I ported a ROM for my Tab S [SM-T800] but does not boot to system.
Boot animation comes and stucks at boot animation.
I used PACROM for SM-T800 as a base and Europhia OS for SM-T700.
Please help
Who knows? No good without logs, dmesg, last_kmsg, logcat
ashyx said:
Who knows? No good without logs, dmesg, last_kmsg, logcat
Click to expand...
Click to collapse
@TimurAlaskara_TR probably knows
Nandr0idC0nsumer said:
@TimurAlaskara_TR probably knows
Click to expand...
Click to collapse
What are you saying he's clairvoyant?
Logs are needed to have an idea of the issue. It's impossible to just guess, it could be any number of things
ashyx said:
What are you saying he's clairvoyant?
Logs are needed to have an idea of the issue. It's impossible to just guess, it could be any number of things
Click to expand...
Click to collapse
he just seems to have some magic that I don't
porting a Rom from a Tab s model to another is a pritty simple process
just Need to open boot.img with any boot Image unpacker and copy Zimage from stock to port, repack and done
also some changes in build.prop are recommended to make, it doesnt look cool if you have a t700 and System says t800
if you are porting a wifi Rom to a lte device you will need to use the boot.img of cm
also Need to change/add some libs in System/lib and 2 files in System/bin
System/Bin:
- Rild
- charon
System/Libs:
- Libc.so
- Libcec.so
- Libcharon.so
- Libcsc.so
- Libril.so
- Librilutils.so
- Libsecril.so
some of them may be irrelevant or only be in touchwiz roms, but this is the list a friend gave me some months ago
i think GPS related libs are missing there also :/
TimurAlaskara_TR said:
porting a Rom from a Tab s model to another is a pritty simple process
just Need to open boot.img with any boot Image unpacker and copy Zimage from stock to port, repack and done
also some changes in build.prop are recommended to make, it doesnt look cool if you have a t700 and System says t800
if you are porting a wifi Rom to a lte device you will need to use the boot.img of cm
also Need to change/add some libs in System/lib and 2 files in System/bin
System/Bin:
- Rild
- charon
System/Libs:
- Libc.so
- Libcec.so
- Libcharon.so
- Libcsc.so
- Libril.so
- Librilutils.so
- Libsecril.so
some of them may be irrelevant or only be in touchwiz roms, but this is the list a friend gave me some months ago
i think GPS related libs are missing there also :/
Click to expand...
Click to collapse
Oh really thanks Greetins from Turkey.
Sent from my Asus ZenFone 2 Laser (ZE550KL) using XDA Labs
This guide will explain to users on how to port from the HTC One M8, HTC One E8 and HTC Butterfly 2 roms to our beloved Desire EYE. The porting between these devices take little to no knowledge at all to do, if you know how to logcat and read kernel last_kmsg.
In this guide i will explain how I've ported InsertCoin M8 to Desire EYE.. Should apply to all htc msm8974 devices.
Requirements :
- Developers Permission for the rom your porting if you plan to release
- Android Image Kitchen
- Basic knowledge on understanding my method of porting
InsertCoin ( Port )
Desire EYE Rom ( Base )
Step 1 : Fixing Camera
Each HTC MSM8974 devices have different camera modules thus need fixing
So take these similar libs from stock roms and place them into the rom your porting.
1. All /system/lib/libtuning** lib files from stock and place them in port in /system/lib/
2. All /system/vendor/lib/libchromatic** lib files from stock and place them in port in /system/vendor/lib/
3. 2. All /system/vendor/lib/libmmcamera** lib files from stock and place them in port in /system/vendor/lib/
4. Take /system/etc/res_ctrl** files from stock and place them in port in /system/etc/ ( fix camera resolution )
Step 2 : Fixing NFC
EYE, E8, and B2 all have same NFC driver. So this method will explain when porting from M8
Files to Delete from Port
Code:
- /system/app/Nfc
- /system/etc/nfcee_access.xml
- /system/lib/hw/nfc.qcom.so
- /system/lib/libnfc.so
- /system/lib/libnfc_jni.so
- /system/libnfc_ndef.so
- /system/vendor/firmware/libpn544_fw.so
Now add these from stock to port
Code:
- /system/app/NfcNciNxp/
- /system/etc/libnfc-brcm.conf
- /system/etc/libnfc-nxp.conf
- /system/etc/nfcee_access.xml
- /system/lib/hw/nfc_nci_pn547.defualt.so
- /system/lib/libnfc-nci-nxp.so
- /system/lib/libnfc_nci_nxp_jni.so
- /system/lib/libnfc_ndef.so
- /system/vendor/firmware/libpn547_fw.so
Kernel Side for NFC : Will edit later with indep fixing
Step 3 : Having Correct Kernel
Will post stock kernel ports soon with NFC ramdisk fixes.
Thank you, but is this tutorial complete ?
CelesteBlue said:
Thank you, but is this tutorial complete ?
Click to expand...
Click to collapse
Yes, it's complete, it will work.
EDIT: The kernel part is left.
? ok thank you, personally, I have a Samsung Galaxy S4 Advance (msm8974, S800 2.3GHz), and I'm porting a Galaxy S5 ROM (msm8974pro, S800 2.5GHz). The rom works, except HDR in camera, and NFC... Could you help me please (PM if you want). Credits will go to you.
CelesteBlue said:
? ok thank you, personally, I have a Samsung Galaxy S4 Advance (msm8974, S800 2.3GHz), and I'm porting a Galaxy S5 ROM (msm8974pro, S800 2.5GHz). The rom works, except HDR in camera, and NFC... Could you help me please (PM if you want). Credits will go to you.
Click to expand...
Click to collapse
Try the camera fixing and NFC fixing method in the post above..that should work.
So we can port any MSM8974 device ROM to ours ?
Like
Samsung S5
Sony Xperia Z3
Arun.Gunupudi said:
So we can port any MSM8974 device ROM to ours ?
Like
Samsung S5
Sony Xperia Z3
Click to expand...
Click to collapse
no the port will only work between msm8974 htc devices..
Okay....
So can we directly port CM ROM of Htc-one-m8 to our eye, without having cm repo & need of SSD? @xXminiWHOOPERxX
I wish you are posting this because you want someone to share the work with you to make more ROMs, not because you're abandoning us
Our device is not a developer magnet due to the small community of users + actually nearly no one donates.. :/
Please don't ever abandon us because without you we are hopeless :'(
I wanted a similar guide to start porting from M8, and I will help you increase the base of our ROMs for our beloved EYE.
I want to ask you this guide only works for Sense ROMs? GPE and AOSP based ROMs support this guide? Thanks..
Arun.Gunupudi said:
Okay....
So can we directly port CM ROM of Htc-one-m8 to our eye, without having cm repo & need of SSD? @xXminiWHOOPERxX
Click to expand...
Click to collapse
If you have a working CM kernel, it should work.
modaifallah said:
I wish you are posting this because you want someone to share the work with you to make more ROMs, not because you're abandoning us
Our device is not a developer magnet due to the small community of users + actually nearly no one donates.. :/
Please don't ever abandon us because without you we are hopeless :'(
I wanted a similar guide to start porting from M8, and I will help you increase the base of our ROMs for our beloved EYE.
I want to ask you this guide only works for Sense ROMs? GPE and AOSP based ROMs support this guide? Thanks..
Click to expand...
Click to collapse
It will work for Sense and GPE ROMs, but AOSP, I have a doubt, there could be some kernel issues.
xXminiWHOOPERxX said:
no the port will only work between msm8974 htc devices..
Click to expand...
Click to collapse
Msm8974 is the motherboard, but you must be considering the differences : camera, ram, storage, and the peripherals...
So porting will be more hard, more different hardware you have...
This guide is only to port a HTC XXX ROM (Sense, AOSP) to another phone HTC YYY.
HTC XXX must be MSM8974.
HTC YYY must be MSM8974.
Hit Thanks if you think this post useful.
Oh!!I've been wait for this for a long time!
how about others file?just keep them original?
CelesteBlue said:
? ok thank you, personally, I have a Samsung Galaxy S4 Advance (msm8974, S800 2.3GHz), and I'm porting a Galaxy S5 ROM (msm8974pro, S800 2.5GHz). The rom works, except HDR in camera, and NFC... Could you help me please (PM if you want). Credits will go to you.
Click to expand...
Click to collapse
Message me.
Sent from my HTC6525LVW using Tapatalk
Regarding the kernel, we can simply use your latest Mini's kernel right?
xXminiWHOOPERxX said:
This guide will explain to users on how to port from the HTC One M8, HTC One E8 and HTC Butterfly 2 roms to our beloved Desire EYE. The porting between these devices take little to no knowledge at all to do, if you know how to logcat and read kernel last_kmsg.
In this guide i will explain how I've ported InsertCoin M8 to Desire EYE.. Should apply to all htc msm8974 devices.
Requirements :
- Developers Permission for the rom your porting if you plan to release
- Android Image Kitchen
- Basic knowledge on understanding my method of porting
InsertCoin ( Port )
Desire EYE Rom ( Base )
Step 1 : Fixing Camera
Each HTC MSM8974 devices have different camera modules thus need fixing
So take these similar libs from stock roms and place them into the rom your porting.
1. All /system/lib/libtuning** lib files from stock and place them in port in /system/lib/
2. All /system/vendor/lib/libchromatic** lib files from stock and place them in port in /system/vendor/lib/
3. 2. All /system/vendor/lib/libmmcamera** lib files from stock and place them in port in /system/vendor/lib/
4. Take /system/etc/res_ctrl** files from stock and place them in port in /system/etc/ ( fix camera resolution )
Step 2 : Fixing NFC
EYE, E8, and B2 all have same NFC driver. So this method will explain when porting from M8
Files to Delete from Port
Code:
- /system/app/Nfc
- /system/etc/nfcee_access.xml
- /system/lib/hw/nfc.qcom.so
- /system/lib/libnfc.so
- /system/lib/libnfc_jni.so
- /system/libnfc_ndef.so
- /system/vendor/firmware/libpn544_fw.so
Now add these from stock to port
Code:
- /system/app/NfcNciNxp/
- /system/etc/libnfc-brcm.conf
- /system/etc/libnfc-nxp.conf
- /system/etc/nfcee_access.xml
- /system/lib/hw/nfc_nci_pn547.defualt.so
- /system/lib/libnfc-nci-nxp.so
- /system/lib/libnfc_nci_nxp_jni.so
- /system/lib/libnfc_ndef.so
- /system/vendor/firmware/libpn547_fw.so
Kernel Side for NFC : Will edit later with indep fixing
Step 3 : Having Correct Kernel
Will post stock kernel ports soon with NFC ramdisk fixes.
Click to expand...
Click to collapse
Can You Be more Specific In How to use Android Kitchen? As I tried porting resurrection remix and was unable as it had .data file instead of system files etc after extracting.
deveshgupta69 said:
Can You Be more Specific In How to use Android Kitchen? As I tried porting resurrection remix and was unable as it had .data file instead of system files etc after extracting.
Click to expand...
Click to collapse
Before I can assist you what HTC msm8974 device are you using? 2 this guide is for sense and gpe rom porting... any aosp roms may vary on porting, sorry I don't know.
Sent from my HTC6525LVW using Tapatalk
xXminiWHOOPERxX said:
Before I can assist you what HTC msm8974 device are you using? 2 this guide is for sense and gpe rom porting... any aosp roms may vary on porting, sorry I don't know.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I'm using the HTC Desire EYE ULCA, Even if AOSP porting won't work, I would like to know how to use your porting steps in android Kitchen. I'm using Android Kitchen on cygwin.
Sent from my HTC Desire EYE using XDA-Developers mobile app
deveshgupta69 said:
I'm using the HTC Desire EYE ULCA, Even if AOSP porting won't work, I would like to know how to use your porting steps in android Kitchen. I'm using Android Kitchen on cygwin.
Sent from my HTC Desire EYE using XDA-Developers mobile app
Click to expand...
Click to collapse
Those porting steps do not require anything special tool, just replace the files and then the boot.img part, you require Android Image Kitchen, that is to replace the zimage, dtb and make ramdisk nfc fix.
aj20010319 said:
Those porting steps do not require anything special tool, just replace the files and then the boot.img part, you require Android Image Kitchen, that is to replace the zimage, dtb and make ramdisk nfc fix.
Click to expand...
Click to collapse
what exactly do to port kernal from one m8 ?
fetto0o said:
what exactly do to port kernal from one m8 ?
Click to expand...
Click to collapse
To port kernel, first download official kernel sources of both eye and m8, then add the board files from eye's source to m8's source, then compile it. Last step, fix things if they are broken.
Hi friend!
The Ultimate ROM any Android device should have is here for mipad1.
As all know Remix OS is one of the best rom available for Android device
but it's limited to few devices.
Remix OS give you full pc experience on your Android devices.
i was using Remix OS 1.0 which was awesome.
so i have decided to get Remix OS 2.0 on mipad 1.
Luckily i found a zip file of remixos on xda shared by @majinvegeta3886
here !
https://forum.xda-developers.com/remix/remix-ultratablet/remix-2-0-305-flashable-zip-t3426112
which is base on Android 5.1.1 .
so i need a rom that is running on mipad1 with Android Version 5.1.1
which is already builded by most respected developer for mipad1 @highwaystar_ru .
so i used these 2 roms and a day of my life and made Remix OS 2.0 bootable
on mipad1.
ROM is very smooth even with bugs
#############
Download Link ..
#############
Remix OS => https://drive.google.com/file/d/1-SqdWZXyx_YVnvcANyJ4JSGn4OgLR5zy/view?usp=drivesdk
Repartition => http://en.miui.com/thread-118294-1-1.html
Twrp Multirom = > https://rahulthevirus.github.io/multirom_mocha/multirom/twrp-multirom-20170311-UNOFFICIAL-mocha.img
###########
How to flash
###########
* You must have Stock blobs.
if you are using smoke rom base on shield blob so first return to stock blob base rom.
* You must have repartition if not then get my zip And flash threw twrp 3x
* You must have multirom twrp recovery .
* Be ready with these things..
return to stock blob (if not already ) , flash twrp , wipe everything ( /delvik- cache /cache /system /data )
wiping internal is not nessesrery just delete folder name "Android" from internal memory.
* After this reboot into twrp and flash rom in intarnal ( × Not in multirom)
* When completed flash superuser zip
* Remember Do not flash gapps (core gapps already builtin) otherwise you may get errors.
* you can install Gapps simply like an apk or from playstore.
* Now reboot and wait for welcome screen. (Sometimes this can take ~15 min.)
* Follow Setup screen and enjoy ..
#######
Working
#######
* Touch panel
* Hardware keys
* Navigation Keys
* Sound
* Wifi
* Internal Sdcard
* & All basic stuffs to run a device
###########
Known Bugs
##########
* All bugs available in CM 12.1
* Camera not working
* Bluetooth not working
* Mic not working
* Headphone s not working
* Ex Sdcard not working
* default cm init (managed threw multirom init )
Updated changelogs!
drakonizer said:
RemixOS update:
I have taken the build by Rahul and fixed the following bugs:
* Camera
* Headphone Jack detection
* SD Card
The current bugs are now only:
* Bluetooth
* Microphone
Click to expand...
Click to collapse
##########
Source :-
#########
Remix OS for Remix Ultratablet :- https://forum.xda-developers.com/remix/remix-ultratablet/remix-2-0-305-flashable-zip-t3426112
CM 12 .1 for mocha :- https://forum.xda-developers.com/mi-pad/development/cyanogenmod-12-1-mipad-mocha-t3535640
kernel source :- https://github.com/RahulTheVirus/nethunter-mocha.git
########
Credit :-
#######
All major credit goes to Jide to transforming Android
and to @highwaystar_ru for cm 12.1
& @majinvegeta3886 For sharing Remix OS zip.
And Special thanks to @drakonizer for bugfix.
##############################
Want contribute or need any assistance
##############################
Mi Pad 1 Group on Telegram
https://t.me/MiPad1
________________________________________________
If anyone help to bugs fix that highly appreciated.
Thanks !
=============================
Download Latest here!
==============================
RemixOS build 3 => [email protected]
Currently some issue with rom updated by darkonizer
i have temporary solution..
flash my beta 3 build. setup everything and once you are in remixOS just copy 2 files from darkonizer's build
framework-res.apk
framework.jar
and replace your system files from /system/framework
reboot.
reboot into recovery and flash this fix zip
RemixOS-2.0.305-framework-fix.zip
this will fix your issue but camera still broken.
Almost stable build
RemixOS-2.0.305-mocha.zip
=================================
Some Screenshots
Pradyumna26 said:
Some Screenshots
Click to expand...
Click to collapse
Thanks
Thanks for your post.. Im getting the attached error.. Any suggestion?
Ardhendu said:
Thanks for your post.. Im getting the attached error.. Any suggestion?
Click to expand...
Click to collapse
If i am not wrong then you have formated data and without reboot you flashed rom.
So advice to reboot into recovery then flash rom.
Also make sure you have already merged both system partitions into single .
I mean repartition to 1.2GB.
RahulTheVirus said:
If i am not wrong then you have formated data and without reboot you flashed rom.
So advice to reboot into recovery then flash rom.
Also make sure you have already merged both system partitions into single .
I mean repartition to 1.2GB.
Click to expand...
Click to collapse
Rebooting again into recovery before flashing the rom worked. It transformed mipad into a laptop like device. Negligible lag.
Can you please make me clear if it works with multi rom? Because i want keep los14 along with it...
Ardhendu said:
Rebooting again into recovery before flashing the rom worked. It transformed mipad into a laptop like device. Negligible lag.
Can you please make me clear if it works with multi rom? Because i want keep los14 along with it...
Click to expand...
Click to collapse
Yes it will work:good:
But recommanding to use los14 as secondry if using twrp given in thread.
Because multirom have 2 versions and same has twrp.
So choose acordingly ..
Any issue feel free to connect me :good:
RemixOS update:
I have taken the build by Rahul and fixed the following bugs:
* Camera
* Headphone Jack detection
* SD Card
The current bugs are now only:
* Bluetooth
* Microphone
DOWNLOAD:
https://www.androidfilehost.com/?fid=673791459329072079
drakonizer said:
RemixOS update:
I have taken the build by Rahul and fixed the following bugs:
* Camera
* Headphone Jack detection
* SD Card
The current bugs are now only:
* Bluetooth
* Microphone
DOWNLOAD:
https://www.androidfilehost.com/?fid=673791459329072079
Click to expand...
Click to collapse
Flashed the rom provided by you, but it is not booting getting stuck at this screen at the time of first boot.
ASK-Rambo said:
Flashed the rom provided by you, but it is not booting getting stuck at this screen at the time of first boot.
Click to expand...
Click to collapse
Same here... ?
ASK-Rambo said:
Flashed the rom provided by you, but it is not booting getting stuck at this screen at the time of first boot.
Click to expand...
Click to collapse
Ardhendu said:
Same here...
Click to expand...
Click to collapse
Sorry friends i have flashed rom and found same issue .
we 'll fix rom as soon as possible.
we both are very busy right now.
i have updated my thread with solution please check .
RahulTheVirus said:
Hi friend!
Currently some issue with rom updated by darkonizer
i have temporary solution..
flash my beta 3 build. setup everything and once you are in remixOS just copy 2 files from darkonizer's build
framework-res.apk
framework.jar
and replace your system files from /system/framework
reboot.
this will fix your issue but camera still broken.
=================================
Click to expand...
Click to collapse
Resulted bootloop.... :crying:
Ardhendu said:
Resulted bootloop.... :crying:
Click to expand...
Click to collapse
Not possible , i am using this right now .
RahulTheVirus said:
Not possible , i am using this right now .
Click to expand...
Click to collapse
Same here...i also got bootloop after replacing those two files. If possible can you provide flashable zip for those files or a working build that you are using on your mipad after replacing files.
ASK-Rambo said:
Same here...i also got bootloop after replacing those two files. If possible can you provide flashable zip for those files or a working build that you are using on your mipad after replacing files.
Click to expand...
Click to collapse
I will upload a fixed build this weekend. I *think* you should be fine if you flash the first build, set it up, and then dirty flash my build. You can test and see.
drakonizer said:
I will upload a fixed build this weekend. I *think* you should be fine if you flash the first build, set it up, and then dirty flash my build. You can test and see.
Click to expand...
Click to collapse
Headphone jack not working is the major bug for me as i use my mipad mostly for the media. Hence the first build is not usable for me as of now. So
Waiting for the new build.
Ps:- take your time bro. You guys are doing great work for our beloved device. Peace.
ASK-Rambo said:
Same here...i also got bootloop after replacing those two files. If possible can you provide flashable zip for those files or a working build that you are using on your mipad after replacing files.
Click to expand...
Click to collapse
ok i'll share flashable zip soon .
ASK-Rambo said:
Same here...i also got bootloop after replacing those two files. If possible can you provide flashable zip for those files or a working build that you are using on your mipad after replacing files.
Click to expand...
Click to collapse
Ardhendu said:
Resulted bootloop.... :crying:
Click to expand...
Click to collapse
Hi
Ardhendu & ASK-Rambo .
Thanks for feedback.
post is updated with recovery flashable zip.
I think now all your issue will solve for now .
RahulTheVirus said:
Hi
Ardhendu & ASK-Rambo .
Thanks for feedback.
post is updated with recovery flashable zip.
I think now all your issue will solve for now .
Click to expand...
Click to collapse
A big thanks again for the the ROM again......
I'm seeing this post late :silly:
I just replaced the firmware files in your old ZIP and flashed it and worked for me....:victory:
Now it is looking like a complete ROM... I don't use camera in MIPAD anyway....
Recently facing a bug while device in auto rotate and screen is rotated, the systemUI is restarting...... I was not facing this for 2 weeks.. It appeared recently... Any one faced this issue?