Related
**I AM NOT RESPONSIBLE FOR ANY NEGATIVE OUTCOMES CAUSED BY ANY FILE HERE OR ANY INSTRUCTIONS**
Stock CM12 kernel, but without forced encryption.
ZIP and IMG available!
Download Directories: (Direct downloads in first post)
Root download directory: https://www.androidfilehost.com/?w=files&flid=26041
ZIPs): https://www.androidfilehost.com/?w=files&flid=26073
IMGs: https://www.androidfilehost.com/?w=files&flid=26074
Install instructions:
I will create a new modified boot.img every time the kernel is updated!
Flash latest cm12 nightly in recovery and then flash boot.img zip in recovery before reboot!
If you are already encrypted you will also have to wipe data which means you will lose everything!
IMG:
Flash the latest cm12 nightly. Wipe data if the device is already encrypted, then boot into fastboot and use "fastboot flash boot boot.img"
**YOU MUST DO THIS EVERY TIME YOU FLASH CM12**
Remember to hit :good: thanks!
XDA:DevDB Information
Nexus 9 Stock CM12 Kernel Without Forced Encryption, Kernel for the Nexus 9
Contributors
sp99
Kernel Special Features: No forced encryption
Version Information
Status: Beta
Created 2015-02-09
Last Updated 2015-02-11
Download Links:
Download Directories:
Root download directory: https://www.androidfilehost.com/?w=files&flid=26041
ZIPs: https://www.androidfilehost.com/?w=files&flid=26073
IMGs: https://www.androidfilehost.com/?w=files&flid=26074
Direct downloads:
20150209:
IMG:https://www.androidfilehost.com/?fid=95916177934526641
ZIP:https://www.androidfilehost.com/?fid=95916177934526727
Reserved
Thank you for providing this. Huge speed increase when copying files. Forced encryption the Nexus 9 is so slow, especially when comparing it to my encrypted Nexus 6 and 5.
I know, the forced encryption thing is stupid
Remember to flash the latest boot.img I have with each update, I'll make it a flashable zip later and do the latest nightly
Sent from my A0001 using XDA Free mobile app
sp99 said:
I know, the forced encryption thing is stupid
Remember to flash the latest boot.img I have with each update, I'll make it a flashable zip later and do the latest nightly
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
This is great, ill link it in my OP
The flashable part isn't hard if you want i can help you with it( i had to do it a few times for when we were trying to get the kernel to build)
Also i don't think it will be necessary to rebuild this everyday as nothing in the flounder kernel should really ever change.
EDIT: my bad, looks like you already have the flashables built
And linked to your thread, you rock
zawata said:
This is great, ill link it in my OP
The flashable part isn't hard if you want i can help you with it( i had to do it a few times for when we were trying to get the kernel to build)
Also i don't think it will be necessary to rebuild this everyday as nothing in the flounder kernel should really ever change.
EDIT: my bad, looks like you already have the flashables built
And linked to your thread, you rock
Click to expand...
Click to collapse
Thanks!
If anyone can test the flashable zip that'd be great as I'm letting my n9 charge to 100% after I got a bootloop (not from this don't worry ) and I thought I turned it off... but I obviously didn't so it completely ran out of battery
So much so that its hidden LED lit up! (I didn't think it even had one)
But yeah, if someone could test it that'd be great! :angel:
EDIT: Doesn't matter
zawata said:
This is great, ill link it in my OP
The flashable part isn't hard if you want i can help you with it( i had to do it a few times for when we were trying to get the kernel to build)
Also i don't think it will be necessary to rebuild this everyday as nothing in the flounder kernel should really ever change.
EDIT: my bad, looks like you already have the flashables built
And linked to your thread, you rock
Click to expand...
Click to collapse
I'm having some problems making the zip work :/ I've tried the cm12 update binary and signed using a testsign program but it comes up with errors
EDIT: Fixed
I have the official CM now.. with encrypted on is still good.
How do we know if the system was encrypted in off with this? and what are the benefits? other than some say it is a bit faster.
@sp99
you dont have to make a zip for every build.
you can look here to see if changes happen :highfive:
Max128 said:
I have the official CM now.. with encrypted on is still good.
How do we know if the system was encrypted in off with this? and what are the benefits? other than some say it is a bit faster.
Click to expand...
Click to collapse
It say if it is encrypts in security, but without encryption it seems a lot faster!
USBhost said:
@sp99
you dont have to make a zip for every build.
you can look here to see if changes happen :highfive:
Click to expand...
Click to collapse
Thanks!
sp99 said:
It say if it is encrypts in security, but without encryption it seems a lot faster!
Click to expand...
Click to collapse
I flashed the latest CM12 nightly (from today) and flashed this kernel (9-2), and did an data/factory reset, but it still says Encrypted under Settings -> Security.
I'm using the latest TWRP.
Any suggestion?
edgarf28 said:
I flashed the latest CM12 nightly (from today) and flashed this kernel (9-2), and did an data/factory reset, but it still says Encrypted under Settings -> Security.
I'm using the latest TWRP.
Any suggestion?
Click to expand...
Click to collapse
So did you download cm zip and kernel to computrer, boot to twrp, wipe data, system, cache, dalvik and factory reset. adb push the files and flash cm then the kernel?
I thought he had a new file each build? the build today is working with the file 09, the file is the same?
Max128 said:
I thought he had a new file each build? the build today is working with the file 09, the file is the same?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=58769046&postcount=11
Is working for me now.
Hi,
I want to know if you could do a similar script for the nexus 9? it'd be great!
http://forum.xda-developers.com/nexus-6/development/mod-disable-force-encryption-rom-kernel-t3000788
This is the nexus 9... ?
Sent from my A0001 using XDA Free mobile app
AOSP MASTER BRANCH FOR MANTA DEVICE
Hello everyone, you can download on XDA many good ROMS but each of them are based on "stable" android releases. That's why I chose to share something else.
I am offering a master branch build
Why use master branch ?
clang 3.8 | daily updates | java 1.8
instructions :
reboot to twrp recovery ( you can use mine if you want to use f2fs or having issues flashing my packages)
flasy my package
reset factory and IF YOU COME FROM ANOTHER DISTRIBUTION delete /sdcard/Android/data folder
flash gapps package ( I recommend opengapps)
reboot
I recommend people to factory reset time o time because of the master branch, it can be required to remove some bugs
What is not working/bugging for now
ROOT: latest supersu are patching the boot image and this doesn't work currently with my master branch releases. You need to use SuperSU v2.56
MXPlayer: for some reasons mxplayer doesn't find libcutils.so while it does exists. So for now, you gotta to use some alternatives: vlc, or what ever
Download link
Sources
How to use AdwAway
In oder to get AdAway working you need to do the following:
1/ Set a file at
Code:
su/su.d
with the following content
Code:
mount -o bind /su/etc/hosts /system/etc/hosts;
2/ Make an empty host file at
Code:
/su/etc/hosts
I think you can find a working flashable package doing this on the unoffical adaway thred
XDA:DevDB Information
AOSP Master Branch for Manta, ROM for the Google Nexus 10
Contributors
Khaon
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Beta
Stable Release Date: 2016-04-22
Created 2016-01-27
Last Updated 2016-04-21
Can I confirm this is 100% AOSP, untouched?
Are you doing automated nightly builds?
Thanks!
PainToad said:
Can I confirm this is 100% AOSP, untouched?
Are you doing automated nightly builds?
Thanks!
Click to expand...
Click to collapse
This is not 100% PURE aosp.
The base is aosp master branch. I have included some several extra such :
bootanimation
long press recent switches to latest app
led
...
Well nothing much.
The only critical thing I have touched is android permission : I override user's permission for google play service for the location permission access: otherwise it crashes.
I have uploaded a new build.
Too much changes to display here the changelog.
If you want extra tracking you should head here
To me, the main change, is clang prebult updated!
OP updated, root is now working.
I'm not being thick here (sure of that) but despite flashing SU 2.56 , I can't get root permissions at all. Am I missing something?
ace9988 said:
I'm not being thick here (sure of that) but despite flashing SU 2.56 , I can't get root permissions at all. Am I missing something?
Click to expand...
Click to collapse
Hello,
hm this is kinda unexpected, I got supersu permission with this build.
Did you install anything else ?
Khaon said:
Hello,
hm this is kinda unexpected, I got supersu permission with this build.
Did you install anything else ?
Click to expand...
Click to collapse
Nope. I tried flashing superSU on the ROM + open gapps .....the ROM on it's own without the gapps too. Flashed the 2.56 beta build from the link you provided and although supersu appears in the app drawer, the "Enable Superuser" option appears to be greyed out and none of the apps even request root permission.
ace9988 said:
Nope. I tried flashing superSU on the ROM + open gapps .....the ROM on it's own without the gapps too. Flashed the 2.56 beta build from the link you provided and although supersu appears in the app drawer, the "Enable Superuser" option appears to be greyed out and none of the apps even request root permission.
Click to expand...
Click to collapse
HmHm it is kinda late for me ( european timezone) but I have no issues using app requesting SU rights. I will take a look however at it tmr.
Cant install openGapps. It says Error code 25.Your ROM has no buid.prop or default.prop it says
Katamave18 said:
Cant install openGapps. It says Error code 25.Your ROM has no buid.prop or default.prop it says
Click to expand...
Click to collapse
what opengapps version did you isntall ?
I am using pico, and I have no issue flashing it.
ace9988 said:
Nope. I tried flashing superSU on the ROM + open gapps .....the ROM on it's own without the gapps too. Flashed the 2.56 beta build from the link you provided and although supersu appears in the app drawer, the "Enable Superuser" option appears to be greyed out and none of the apps even request root permission.
Click to expand...
Click to collapse
How is your supersu status ?
I have no issue with su.
------------------------------------------------------------------------------------------------------------------------------------------------------------------
I was reported an issue when formating to f2fs rebooting to the rom would format the userdata partition.
I investigated the AOSP code source and some commit format the partition if it fails mounting. Ofc trying to mount a f2fs partition with ext4 is considered as a fail...
Flashing my standalone kernel permit to pass that issue : my stand alone kernel will transform ext4 entries to f2fs(and vice versa) depending on the actual underlying fs.
The current release I am using features fixes for this, however, something broke the libsensors, so I need to find out what.
Katamave18 said:
Cant install openGapps. It says Error code 25.Your ROM has no buid.prop or default.prop it says
Click to expand...
Click to collapse
Ewww, it should work ! Any other informations ? such logs ?
-----------------------------------------------------------------------------------------------------------------------------------------------------------
I am uploading a new build, I had issues for days with the builds.
Please tell me if you got bootloop on reboot. From what I saw bootloops do not longer exist.
I uploaded a new build.
It features master branch 02/21 with my latest kernel.
You just need latest opengapps for marshamallow and supersu 2.56.
Have fun.
All I see is one dated 2/5?
Sent from my Nexus 10 using XDA Free mobile app
"Play Service stopped" after installing Gapps (Install without errors)
I try OpenGapps Pico and Nano.
Der_Graf said:
"Play Service stopped" after installing Gapps (Install without errors)
I try OpenGapps Pico and Nano.
Click to expand...
Click to collapse
Grant play service the location permission and it will be fixed.
Katamave18 said:
Cant install openGapps. It says Error code 25.Your ROM has no buid.prop or default.prop it says
Click to expand...
Click to collapse
I had this issue sometimes when installing the Rom and gapps in the same queue.. Installing the gapps seperatly afterwards worked then.. Try this out
Can´t give permissions because of looped warnings.
ROM only works fine.
I think i will wait for Khaons Kernel with DT2W Patch and use CM13.
Der_Graf said:
Can´t give permissions because of looped warnings.
ROM only works fine.
I think i will wait for Khaons Kernel with DT2W Patch and use CM13.
Click to expand...
Click to collapse
@Der_Graf
Hehe sorry for you this issue happens, the real culprit is Google. Since MM, the dev got to ask permission if not given. Google Play Frameworks/Service doesn't ask for this. So that's why you got FC. You should try after a Factory Rest- you need to that anyway when coming from another ROM- not installing Gapps in order to not have the first setup screen where you will get stuck because of the fc's spam.
Then Install gapps, and, since you will boot on the Home Screen, you should be able, with some pain, to get access to the app menu to get Location permission for Google Play Services.
Then, for any upgrade install, you won't have issues as the permission is already granted.
I know this sucks, but I tried to force give the permisison and it doesnt work :angry:
Ewwwww.
I wanted to share my latest build, as of the 25th feb, but NFC is broken and makes continuous FC'S, this appears also on my friend nexus 6's device, which is still supported by Google. So this is the bad news I've got to understand why this happens, well until Google fixes it or I find the culprit.
However, the good news is, that this friend, maintains more extra features then I do, so the next releases will feature more extra features
Hi all,
Seems there is a CM14.1 nightly now available for find7s on the official CM site, link here: hxxps://download.cyanogenmod.org/?type=nightly&device=find7s
Was just wondering if anyones given it a go yet, and if so knows whether or not it supports LVM and how stable the rom is?
Haven't found any info that states one way or the other, hoping someone knows.
Thanks in advance.
About the storage support:
Stock -> YES
LVM - NO
Coldbird - Not tested
Chinese - YES
New display:
Cant test it because i havent the new display
At the moment no theme engine
Is stable for daily driver FROM MY POINT OF VIEW
Its a little bit weird that there is not available yet on the page https://www.cmxlog.com/14.1/
Hope it will appear here soon as well as it is already here:
(Find 7a) https://download.cyanogenmod.org/?device=find7
and
(Find 7) https://download.cyanogenmod.org/?device=find7s
Dirty flashed cm-14.1-20161205-NIGHTLY over cm-14.1-20161201-UNOFFICIAL via menu CyanogenMod updates. Everything seems to be OK. One remark: boot time when update is completed is quite long, so be patient. Of course in order to not see "SD corrupted" it is necessary to flash cm-13.0-find7-unified-storage-patch.zip
EDIT: Just for your information: boot animation CM face is gone. Now there is word "android" in plain white.
great news
Finally there we are changes logs:
https://www.cmxlog.com/14.1/find7/
https://www.cmxlog.com/14.1/find7s/
Android 7.1.1 in the next nightly
CyanogenMod will never support LVM.
This is 7.1 right? Or is it 7.0? I downloaded the 7.1 GAPPS, which should be correct for this build...
I updated it, and it runs smooth without any force crashes and nonsense. (Besides the time I tried to open an app not built for nougat, =P. If you're hesistant about updating, don't think, just do it.
Injected said:
About the storage support:
Stock -> YES
LVM - NO
Coldbird - Not tested
Chinese - YES
New display:
Cant test it because i havent the new display
At the moment no theme engine
Is stable for daily driver FROM MY POINT OF VIEW
Click to expand...
Click to collapse
i want to upgrade from an existing cm 13 installation, it is alredy unified with the chinese method, did you made a clean installation? what about the need of flashing Wuxianlin's patch after every upgrade? thanks in advice
-lorenzo- said:
i want to upgrade from an existing cm 13 installation, it is alredy unified with the chinese method, did you made a clean installation? what about the need of flashing Wuxianlin's patch after every upgrade? thanks in advice
Click to expand...
Click to collapse
Yup u can do that. After flashing cm14.1 official, u might wanted to flash cm13 patch by wuxianlin, then flash the gapps and lastly wipe the cache and dalvik
-lorenzo- said:
i want to upgrade from an existing cm 13 installation, it is alredy unified with the chinese method, did you made a clean installation? what about the need of flashing Wuxianlin's patch after every upgrade? thanks in advice
Click to expand...
Click to collapse
And yes you need to flash Wuxianlin's patch after every upgrade just for aesthetic purpose, that is to fix the SDcard damage info bug, unless CM find7 maintainer will fix that, and when it happen you will no longer need to flash the Wuxianlin's CM13 patch.
I am on crdroid right now (LVM) and i really want to try this. Please tell me in short how to revert back to stock partition and then flash this.
Yashraj Chawla said:
I am on crdroid right now (LVM) and i really want to try this. Please tell me in short how to revert back to stock partition and then flash this.
Click to expand...
Click to collapse
1. If you are on LVM you need to back to stock partition layout. Just google for "Find 7 unbrick tool" for procedure. "Sahara" tool is available for download here: http://d3bzg7dsosz4ht.cloudfront.net/OTA/Find7/FIND7WX_12_A.09_140810.tgz
2. Setup Chinese partition layout: http://forum.xda-developers.com/showpost.php?p=64149659&postcount=3
3. Flash wuxianlin's version of TWRP: link available under point 10. on http://community.oppo.com/en/thread-47844-1-1.html
4. Flash cm-14.1 last official nightly build: https://www.cmxlog.com/14.1/find7/
5. Flash nano open gaaps
6. Flash SU
7. Flash cm-13.0-find7-unified-storage-patch
8. Enjoy newest, very stable and fast Android 7.1.1.
Yashraj Chawla said:
I am on crdroid right now (LVM) and i really want to try this. Please tell me in short how to revert back to stock partition and then flash this.
Click to expand...
Click to collapse
rafal.polska.b said:
1. If you are on LVM you need to back to stock partition layout. Just google for "Find 7 unbrick tool" for procedure. "Sahara" tool is available for download here: http://d3bzg7dsosz4ht.cloudfront.net/OTA/Find7/FIND7WX_12_A.09_140810.tgz
2. Setup Chinese partition layout: http://forum.xda-developers.com/showpost.php?p=64149659&postcount=3
3. Flash wuxianlin's version of TWRP: link available under point 10. on http://community.oppo.com/en/thread-47844-1-1.html
4. Flash cm-14.1 last official nightly build: https://www.cmxlog.com/14.1/find7/
5. Flash nano open gaaps
6. Flash SU
7. Flash cm-13.0-find7-unified-storage-patch
8. Enjoy newest, very stable and fast Android 7.1.1.
Click to expand...
Click to collapse
OMG! No! Just need to flash "unlvm" script to revert to stock layout, that is supported by this ROM. Then flash ROM, gapps and SuperSU.
Anyway, to configure chinese storage, if desired, step 1 is unnecesary: just step 2 is enough.
And, of course, don't forget to make a backup in external SD because any choosen method (unbrick tool, setup chinese storage or revert LVM) erases both data and internal card.
Edit:
Here you can find the removelvm_find7_FULL_WIPE script needed to revert to stock layout; flashing it from TWRP is the only you need. When in stock again, you can proceed as usual flashing ROM, gapps and everything you want.
DELETE
Thanks everyone for the info, might hold off as I have LVM, here's hoping that namelessrom put out an official nougat rom in the not too distant future.
New Display is not supported
Injected said:
About the storage support:
Stock -> YES
LVM - NO
Coldbird - Not tested
Chinese - YES
New display:
Cant test it because i havent the new display
At the moment no theme engine
Is stable for daily driver FROM MY POINT OF VIEW
Click to expand...
Click to collapse
New Display is not supported. Colors, ghosting, and bleeding will still be running wild just like all older CM.
The only Custom ROM on the planet that fully supports new display is OmniROM and it seems that they could use some help. Please support their effort: omnirom.org
javier.pc said:
OMG! No! Just need to flash "unlvm" script to revert to stock layout, that is supported by this ROM. Then flash ROM, gapps and SuperSU.
Anyway, to configure chinese storage, if desired, step 1 is unnecesary: just step 2 is enough.
And, of course, don't forget to make a backup in external SD because any choosen method (unbrick tool, setup chinese storage or revert LVM) erases both data and internal card.
Edit:
Here you can find the removelvm_find7_FULL_WIPE script needed to revert to stock layout; flashing it from TWRP is the only you need. When in stock again, you can proceed as usual flashing ROM, gapps and everything you want.
Click to expand...
Click to collapse
Thank you guys i just did that and i must say CM - 14.1 is Lovely :good:
Yashraj Chawla said:
Thank you guys i just did that and i must say CM - 14.1 is Lovely :good:
Click to expand...
Click to collapse
It is. But omnirom support substratum theme.
StormTrooper89 said:
It is. But omnirom support substratum theme.
Click to expand...
Click to collapse
I think you can install substratum theme in CM14.1 (but only substratum themes that support Android 7.1.1), since there no theme engine inside CM14.1
LINEAGE OS
This is an Alpha build of lineageos15.1
Working:
-RIL
-Bluetooth
-Camera (at least 1 of them)
Not Working:
-Probably selinux (did not try enforcing kernel yet)
-Probably encryption (logcat says it works...)
-Wlan (maybe bcs some files from vendor/vendor_system in /system are missing)
-2nd camera (fix could be to use micamera app)
-Probably more
Instructions:
-Download V9.6.11.0.ODLMIFF_8.1 original rom
-go to V9.6.11.0.ODLMIFF/images
-Replace boot.img, with boot.img
-Replace system.img and system_other.img with system.img
-use the flash_all script. THIS WILL WIPE ALL YOUR DATA, EVERYTHING! if you want to go back now (or later) just put the original images back again and use flash_all_except_storage
-Directly after the device reboots by itself, press vol up + power (u might have to hold it until device reboots again) to enter los recovery
-"factory reset--> wipe data"
-If you want TWRP "advanced-->reboot bootloader" and flash TWRP accordingly to thread, then u can flash gapps/mods.
-reboot
-give it time to boot
Source:
ROM
Device branch "los15"
msm8953-device
Kernel
To finish, I WON'T CONTINUE THIS ROM the trees are working, P vendor is there, an adaption to los16 should be possible based on that. Also, i prefer OMNIROM (which i will try to build next).
Thanks goes to:
-Google for the search engine as well as for the source code
-Cozzmi13 for taking some time to show me the basics.
-Lineageos
-Github
-ada12 for offering his help
thankssss
im wait until wlan fix, but thanks for your effort
CreateYourDream said:
im wait until wlan fix, but thanks for your effort
Click to expand...
Click to collapse
I NEED TESTERS
I am building omni now, so cant go back to los and test but if someone can test i might be able to fix it.
TEST:
-download attached zip
-open on pc or device
-copy the files to the corresponding folder (the folder they are in) in "/system" with a root file manager or adb. CAREFUL do not overwrite files already existing. PLEASE only copy the things in etc (especially etc/firmware/wlan/prima/WCNSS_cfg.dat) first, reboot, check if working, if doesnt work, copy other things.
-set permissions accordingly to other files in same folder
-reboot and check if wifi works
It would be nice to have logs, then I could help.
If you ever need help with your omnirom build i would love to help out with everything that i can. Daisy really needs more support to be a very good device.
hi!
anyone know, is this build of LOS 15.1 support correct notch area?
and what about Onmi build?
i want give possible help if need)
Thanks for your work, I hope soon More roms for this great device
ok, installed)
not work:
sound jack (and fm-radio because headset not detected);
notch not apply;
charger led;
wi-fi
bug: sometimes after tapping screen blink with red border
other thing worked in first try. quick and stable but it's very outdated)
.
wertus33333 said:
I NEED TESTERS
I am building omni now, so cant go back to los and test but if someone can test i might be able to fix it.
TEST:
-download attached zip
-open on pc or device
-copy the files to the corresponding folder (the folder they are in) in "/system" with a root file manager or adb. CAREFUL do not overwrite files already existing. PLEASE only copy the things in etc (especially etc/firmware/wlan/prima/WCNSS_cfg.dat) first, reboot, check if working, if doesnt work, copy other things.
-set permissions accordingly to other files in same folder
-reboot and check if wifi works
Click to expand...
Click to collapse
not worked
and usb-tethering too
eremitein said:
sometimes after tapping screen blink with red border
Click to expand...
Click to collapse
I understood why this is happening
I saw the same behavior in the AEX build, which
used the build type "eng"
you also
Can anyone give me the logs for the bugs?
Is this Rom abandoned?
ghanipradita said:
Is this Rom abandoned?
Click to expand...
Click to collapse
Yup. This phone is abandoned in general, which is a shame
eremitein said:
ok, installed)
not work:
sound jack (and fm-radio because headset not detected);
notch not apply;
charger led;
wi-fi
bug: sometimes after tapping screen blink with red border
other thing worked in first try. quick and stable but it's very outdated)
.
Click to expand...
Click to collapse
Thanks for testing. saksham is working on a new build (with updated vendor, etc), will let you know if we need testers.
Nice to know: The blinking red borders show layout updates, they flash in all eng (=developer) builds. If changing the build variant to userdebug (debuging enabled) or user (oem/production builds with few debuging enabled) they vanish.
ghanipradita said:
Is this Rom abandoned?
Click to expand...
Click to collapse
kftX said:
Yup. This phone is abandoned in general, which is a shame
Click to expand...
Click to collapse
Nope, it is not abandoned but we are very few people working on it and none of us has great android experience. Also, all of us do this in our spare time and therefore it can take time. If you want to speed up the build, supply logs (clean install rom, install adb on pc, execute
Code:
adb bugreport > bugreportDATE.txt
or
Code:
adb logcat > logcatDATE.txt
, share the reports), error descriptions (like @eremitein) and/or read on how to build a rom for a device yourself.
eremitein said:
I understood why this is happening
I saw the same behavior in the AEX build, which
used the build type "eng"
you also
Click to expand...
Click to collapse
oh, you already saw this xD
wertus33333 said:
Nope, it is not abandoned but we are very few people working on it and none of us has great android experience.
Click to expand...
Click to collapse
Editing this out of respect even though none was shown.
Also, I would love to help but with the lack of a proper working TWRP (encryption, restore backup issues) I really can't give it the time needed with all the stuff I'd have to reinstall every time, since I need my phone up and working nearly 100% of the time. If a decent version TWRP is released, I'll gladly help.
Glad you're still working on this though, just don't act like we should've known that you still where when the thread was dead for months. Good luck.
wertus33333 said:
Thanks for testing. saksham is working on a new build (with updated vendor, etc), will let you know if we need testers.
Click to expand...
Click to collapse
successful build, always happy to help
is there any reason you build los 15.1 instead of 16?
skyline91 said:
is there any reason you build los 15.1 instead of 16?
Click to expand...
Click to collapse
At the time i built the rom only 8.1 vendor (8.1 official rom) was avaiable. as i'm not really experienced with android it was easier to build 8.1 rom instead of trying to port vendor to 9.0 (while 9.0 vendor would have defenitely be officially out in a month or 2 ) and build los16. porting the device tree from 15.1 to 16.0 should be easy. Also, i don't like los, i want omni .
Can anyone add our device to the supported devices list ? This would be very helpful, especially since we have a large internal space, for testing out new ROMs...
Here is how to add support to any device :
https://forum.xda-developers.com/android/development/guide-dualboot-patcher-unsupported-t3647056
I wanted to try it, but I am using my phone on a daily basis and don't have an alternate VoLTE phone... Also I am a bit inexperienced in development... :crying:
Tried given steps..
1st latest version not worked when clicked on ROM, failed.
I tried bit old version say 9.3 build 179.. Clicking rom worked.
Then followed all steps but not seen X01BD device while patching zip.
This much i did.. Will check other ways.
Note: we need to check other or older version of dbp
sachinm said:
Tried given steps..
1st latest version not worked when clicked on ROM, failed.
I tried bit old version say 9.3 build 179.. Clicking rom worked.
Then followed all steps but not seen X01BD device while patching zip.
This much i did.. Will check other ways.
Note: we need to check other or older version of dbp
Click to expand...
Click to collapse
Thanks for trying
Did you follow the official method ? Which recovery are you using ? TWRP or PBRP ?
Yes
I have tried it finally... Both unofficial method as well as official..
1) Unofficial method does not seem to work, because the app crashes when we click on the ROMs section... This happens for all snapshots from 9.3.0.r340 onwards... I tried the snapshot before this one i.e. 9.3.0.r327 and there were no crashes. I continued with the unofficial method, flashed PATCH.zip, gave root permissions etc but this method did not work...
2) I tried the official method. I forked the project on Github, made the neccessary changes to the asus.yml file and created a pull request.
Here : https://github.com/chenxiaolong/DualBootPatcher/pull/1380
Now we wait for the changes to be merged with the main repo ... Then test the new release...
I didn't have enough bandwidth, otherwise would have built the apk from source myself... Still there is time ... I'll try to see if I can build the apk ....
Hey guys ... Can anyone please help in building this apk ?
Here is my repository which I forked from the official :
https://github.com/Tyakrish/DualBootPatcher
Just fork from my link and build the apk using the steps described here :
https://github.com/chenxiaolong/DualBootPatcher/wiki/Building-DualBootPatcher-from-source
And here :
https://github.com/chenxiaolong/DualBootPatcher/wiki/Building-DualBootPatcher-using-docker-images
Any update on DBP
sachinm said:
Any update on DBP
Click to expand...
Click to collapse
Unfortunately no... @chenxiaolong has not yet merged the commits with the main repo
There are a lot of commits still waiting...
You can check the status of the commit here:
https://github.com/chenxiaolong/DualBootPatcher/pull/1380
I dont currently have a build environment set up... Otherwise I would have built an unofficial version to test on our device...