Related
This thread is for everyone who compile's Cyanogenmod Kang build's from source and would like to post/share with everyone. If you want your build included in this post just pm me and I will update this post asap.
Warning these are unofficial CM7 build's (with myself cherry-picking comments from CM's Gerrit for testing) which may have unfinished mods and/or broken code that is continually changing, ONLY THOSE WHO KNOW WHAT THEY ARE DOING SHOULD FLASH THEM. Don't file bug reports on the Cyanogenmod issue tracker from any of these build's. Please don't bother cyanogen or #teamdouche as you have been warned these build's are unofficial and come with no support except on this thread. If you have any question's try searching as your question might have been already asked and answered. Note: I, nor is anyone else is/are responsible for any bricks or problems you may encounter.
I no longer have a G2 as I gave it to my mom, but will update this periodically. Sorry for the delay I have been super busy with the move, my new job and fixing this house I am now living in.
All credit goes to cyanogen & #teamdouche, thank them not me as all I do is compile
Items from CM's Gerrit that I cherry-picked:
* Give me time
Last Commit repo synced before building-
* Enable access to Audio Effects Settings
I understand that this build is unofficial and I take no responsibility if you brick your phone- Will be update in about an hour and half as I plan on running it when I get home
Please visit @cmsrc, CM's Gerrit or Nightly Device Changelog for a complete list of changes or commits.
Also those who don't know a Kang is an unofficial nightly that someone builds from CM's github.
I will update this post as often as needed to stay current or change as necessary.
Hey everyone, here are the kangs and cherry picks that i will be providing. I want to thanks plasmadragon007 for allowing me to post here.
Everything in the above post applies to here. We will most likely be making these at a different time of day with possible different commits. I do not own a g2 but i do have a couple of decent guys willing to test each kang before posting. If they are not available, i will let you know that the build has not been tested. I do this because i enjoy it and want to. I hope you enjoy it also.
All credit goes to cyanogen & #teamdouche.
Items from CM's Gerrit that I cherry-picked:
Lockscreen background http://goo.gl/5p5Np
you can find my builds on Euroskank http://goo.gl/U7xx6
Hey Guys,
I figured i would share this.
All credit goes to cyanogenmod team. and cyanogen for being a killer coder
All Builds + recoveries can be found here. I have included a date + md5sum
http://xdafiles.net/rhcp/
More Builds/Gapps can be found here:
gridlock32404 - cm7rc0 built by gridlock will be http://www.crackflashers.com/ cause of dropbox excessive traffic, will build new ones tonight if new commits
I uploaded it just now.
You will need to flash CWRecovery 3.0+. Which can be found at
http://xdafiles.net/rhcp/
This has been all built from source.
You need to put your phone in fastboot.
1) fastboot flash recovery recovery.img
2) reboot into recovery
3) backup your current rom
4) adb push the zip
5) flash the zip
As for gapps I can not post any gapps here. (Hint Paul obrians dump of the nexus S)
Notes: I am not responsible for any bricks or problems you may encounter I am just sharing this. If you follow the step you will have 2.3.1 on your phone.
Please help the devs who put this togther for us. fix some bugs. If you know how.
so far, It seems the video has been fixed up a bit. and the wifi works. So, Far the only thing not working video cam. (which is under works so i hear)
Also. Protected apps do not show since this is 2.3.1 (You can fix this by modding your build.prop or wait for google to add 2.3.1)
Thanks and I hope you enjoy this. Please someone mirror the build. I dont think mediafire will keep it up.
If you want to see protected apps. You need to edit your build.prop in system with the following:
Code:
ro.build.description=soju-user 2.3 GRH55 79397 release-keys
ro.build.fingerprint=google/soju/crespo:2.3/GRH55/79397:user/release-keys
This is built from current src as of 30 mins ago.
So, there is a few video fixes and others.
You can read the updates at: http://r.cyanogenmod.com/#q,status:merged,n,z
I appreciate it man. I just moved and I don't have an internet connection yet. It's hard to repo sync on a 1mbps Android tether.
Is there any difference between this one and the other one?
Sent from my HTC Vision using XDA App
smjfosho said:
Is there any difference between this one and the other one?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
This one is more recent, with the newest commits.
Is your link supposed to point to recovery.img?
bivio said:
Is your link supposed to point to recovery.img?
Click to expand...
Click to collapse
Thanks. I mistyped fixed now.
Camcorder still borked?
rhcp0112345 said:
Hey Guys,
I figured i would share this.
All credit goes to cyanogenmod team. and cyanogen for being a killer coder
The rom can be found at: http://www.mediafire.com/?15l284rnq1zjt1h
I uploaded it just now.
You will need to flash this with CWR 3.0. Which can be found at
http://mrcellphoneunlocker.com/recovery.img
This has been all buit from source.
You need to put your phone in fastboot.
1) fastboot flash recovery recovery.img
2) reboot into recovery
3) backup your current rom
4) adb push the zip
5) flash the zip
As for gapps I can not post any gapps here. (Hint Paul obrians dump of the nexus S)
Notes: I am not responsible for any bricks or problems you may encounter I am just sharing this. If you follow the step you will have 2.3.1 on your phone.
Please help the devs who put this togther for us. fix some bugs. If you know how.
so far, It seems the video has been fixed up a bit. and the wifi works. So, Far the only thing not working video cam. (which is under works so i hear)
Also. Protected apps do not show since this is 2.3.1 (You can fix this by modding your build.prop or wait for google to add 2.3.1)
Thanks and I hope you enjoy this. Please someone mirror the build. I dont think mediafire will keep it up.
Click to expand...
Click to collapse
the link to the recovery img is broken because it says reovery not recovery
Im in no rush. Im just going to wait for the cyanogenmod team to fully finish it & wait for RC1.
Vandale said:
Im in no rush. Im just going to wait for the cyanogenmod team to fully finish it & wait for RC1.
Click to expand...
Click to collapse
Sure your not Thats why your watching these threads like everyone else, including me!!
Downloading now, Thanks for the build!
Been waiting for this all day. Thank you!
[ROM]cm7 gingerbread flavor
[Recovery]clockwork 3.0.0
Glad everyone likes.
My pleasure
Sent from my HTC Vision using XDA App
do you know if usb issue was addressed in this build
Have not tested it. Nor do I see any commits. So I assume same issue.I don't mount usb so doesn't bother me. I use adb
Sent from my HTC Vision using XDA App
is the "unknown" thing still showing up in phone number? its the only thing keeping me from sticking with Gingerbread @[email protected] silly, i know.
having problem flashing the img help
I get an assert failed error trying to flash the ROM, too bad I was really looking forward to trying CM7 .
cough..... cough http://forum.xda-developers.com/showpost.php?p=10083640&postcount=151 cough..... cough... man I'm really sick
i read something in the net while i was surfing yesterday, you can look here: http://www.androidcentral.com/motorola-atrix-hd-gets-official-cyanogenmod-support
and then reading these lines made me surprised(maybe getting official cyanogenmod support for ancora is impossible after this moment but who kowns?)
If an Android device has enough of a following, and there are developer(s) willing to commit (no pun intended) to maintaining the device in the official CyanogenMod source tree, this device becomes officially supported -- and receives official builds of the CyanogenMod ROM.
if someone be maintainer for our device can we get official support from CyanogenMod?
is this really possible?
ı mean our device source code are available in github(kernel source device source and vendor files)
maybe forking our device source into CyanogenMod source tree can make this possible or am ı wrong??
maybe this is a bulsh*it after this moment but just wondering
for example galaxy s is getting official support from Cyanogenmod still if im not mistaken mr. pawit is their maintainer and developer
ım waiting your answers brothers what do you think about that? @arco68 @arsradu @LeroViten @honeyx and all ancora devs
with my best regards :good:
The SGW was for more than 3 years without official CM support and we didn´t miss anything, so I don´t think this is that much important for the rest of it´s counted days.
honeyx said:
The SGW was for more than 3 years without official CM support and we didn´t miss anything, so I don´t think this is that much important for the rest of it´s counted days.
Click to expand...
Click to collapse
ı understood bro but is there any hope for galaxy w? return of ancora :good: and also ı understood that from your comment : technically this is possible,galaxy w can get official support from CM Team but this is unnecessary for this dead device isnt it?
I simply don´t think this will happen because you have to look from their point of view.
1. this device is a low activity device in Amercian terms. 2. So never was that popular to get their attention. 3. is already old and not up to date. 4. It´s hype time is almost over and many earlier SGW users are going to replace it. 5. CM is going a different route now and will be focusing on their "device" they are going to launch soon. And finally 6. Why should they change this now after already 3 years?
So if I were CM I would look for the future not looking back to the past with it´s outdated devices and not even waste a single tought about devices like the SGW.
Is this bad for the SGW owners? As long we are having Devs like Radu who are porting the latest ROMs to this device it really doesn´t matter CM is supporting it officially or not supporting it.
So what do you expect from being supported by CM? You only would be able to install the latest nightlys launched by the CM team with all the bugs in the CM code included and maybe some day fixed. A Dev who is porting their CM sources of course has to fight with these bugs too, but also cares to fix the most important ones.
I asked arco68 a while ago, and he said it's because of legacy camera drivers that we are unsupported.
Sent from my Nexus 5 using Tapatalk
SGWUser said:
I asked arco68 a while ago, and he said it's because of legacy camera drivers that we are unsupported.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
auhh thats true sir arne is right as always anyway thanx man for informing us
regards :good:
I don't think so...anyway, we already have the stable n smooth ROM so far. Without Officail, it's does not matter at all.
Hello sir @arco68
First of all huge thanx for your great work on our Wonders
And secondly i wonder something
We are using s5k4ecgx sensor for back camera
And if we add the following patches and if we use v4l2 for camera driver, Can we use CAF based qcom cameraHAL?
-http://www.spinics.net/lists/linux-media/msg50380.html
And probably if we use new qcom cameraHAL, then we wont need legacy stuff the CM doesnt like(MemoryHeapBase,Overlay)
Then maybe we can get cm nightlies
Maybe porting new camera Hal to our phone can be hard but we must not give up. We are so close to official CM after ION i think. We can do it and we can success :good:
Thanx
Regards
hack4er said:
Hello sir @arco68
First of all huge thanx for your great work on our Wonders
And secondly i wonder something
We are using s5k4ecgx sensor for back camera
And if we add the following patches and if we use v4l2 for camera driver, Can we use CAF based qcom cameraHAL?
-http://www.spinics.net/lists/linux-media/msg50380.html
And probably if we use new qcom cameraHAL, then we wont need legacy stuff the CM doesnt like(MemoryHeapBase,Overlay)
Then maybe we can get cm nightlies
Maybe porting new camera Hal to our phone can be hard but we must not give up. We are so close to official CM after ION i think. We can do it and we can success :good:
Thanx
Regards
Click to expand...
Click to collapse
That would be so f... Awesome *-*
Please we need someone who knows how to do this
Code:
*** Disclaimer***
No legal responsibility taken for anything.
use at own risk.
I am not a Developer . Just sharing the RR project with updates and mergers faster for users
Install with full knowledge that this might make your phone 100% unusable and will void your device warranty .
Briefing
This is my own personal RR N build, based on 14.1. i will build the ROM ASAP once crpalmer merges any new codes .
I will upload the ROM if it Boots fine in my personal device
i am not offending anybody's build especially the Official RR thread . i just keep this thread updated daily .
please dont complain anything about the BUGS as all bugs in CM14.1 are present in my build too
Feel free to contribute, recommendations and (new) bug reports are always very welcome.
I am a newbee here if any mistakes please let me know
Click to expand...
Click to collapse
Features & Details
FULL Substratum theme engine support with Masquerade and OMS
Compatible fully with both firmware (MM and N)
SELinux ENFORCING
Build USING Ubuntu 16.04 in Windows using VM
Click to expand...
Click to collapse
INSTRUCTIONS
Download the Rom & and ARM64 7.1 GAPPS .
Reboot to TWRP recovery .
Flash ROM and then GAPPS
Flash Custom Kernel ( Personal recomendation i am using V7.0.2-Beta Android N )
If running Nougat firmware (2.0+) you will need to flash fingerprint patch to use the home button
Click to expand...
Click to collapse
BUGS
Same as CM 14.1 ... i am not listing the bugs
ChangeLog
Add headphones backend (fixes headphones)
WIFI fix ( may be check it out yourself)
Developer settings fixed
USB tethering fixed ( working for me)
Night mode working
Bug fixes
VOIP application issue fixed when it comes for audio
Added Aptx Bluetooth Support
[*] Touch Screen Gestures added
Note :- please dont ask for BUG fixes FYI i am not a developer ... solutions and recommendations are welcome
Downloads
RR-N-v5.8.2-20170319-pme-Nightly.zip
Finally an OMS build .... No help got from any of the devs out here in XDA ... Finally managed to get the OMS in my build.
Thanks a lot to my best mate who helped me in guiding on github and gerrits ++ thanks @ mihran
GAPPS:-
Optional
substratum theme engine
XDAevDB Information
Resurrection Remix ROM N UNOFFICIAL for the HTC 10
Contributors crpalmer
Version Information
Status: Beta
Created 26.12.2016
Source Code Rom
https://github.com/vysakhraju/platform_manifest
Original Rom thread by @Eliminater
=[url]http://forum.xda-developers.com/htc-10/development/rom-resurrection-remix-m-t3440977[/URL]
Thanks alot!
Where is FP patch?
ali nz said:
Thanks alot!
Where is FP patch?
Click to expand...
Click to collapse
As i have not got the permission to use the finger print patch please use the one from CM14.1 thread by @ibrokemypie
@ibrokemypie :- Can i use your finger print patch for my ROM ?
Dec 26th Build with OMS updated in OP
OP I'm on your last build of RR unofficial from 12.22 from the other thread.
do you require or recommend a clean flash for this or can it flash dirty? thank you!
VR32 said:
OP I'm on your last build of RR unofficial from 12.22 from the other thread.
do you require or recommend a clean flash for this or can it flash dirty? thank you!
Click to expand...
Click to collapse
I did dirty flash and is wokring fine
thanks man I'll give it a go
Hi All
Need your support to add OMS support to this ROM
. I have does somebody know how to Clone / fetch the megers to my build ...
If someone know please comment so I can release the build tomorrow
ffs what is with the //word for word// copying now
one thing to build a rom using open source code, another entirely to copy an entire thread and change some words just enough to get past your teacher's plagiarism check.
ibrokemypie said:
ffs what is with the //word for word// copying now
one thing to build a rom using open source code, another entirely to copy an entire thread and change some words just enough to get past your teacher's plagiarism check.
Click to expand...
Click to collapse
As per the request and comments on RR thread i created a seperate thread for my build... To be frank yes copying was easy and i thougt of doing ..I have not spend much time in that lol.. Anyways I have not copied your build or work mate !!!
blackpanther0582 said:
As per the request and comments on RR thread i created a seperate thread for my build... To be frank yes copying was easy and i thougt of doing ..I have not spend much time in that lol.. Anyways I have not copied your build or work mate !!!
Click to expand...
Click to collapse
just to be clear, I never said nor insinuated that you copied my build, very difficult to do that anyway as being all open source, no one is copying anyone, simply building the same source code. Just frustrating to have ones words taken and repeated without permission, attribution or even a simple acknowledgement, and its suddenly something that has happened a lot in the past few days.
Really sorry mate ...yes I have not asked permission from you I apologizing for that ... I don't know how to create a thread while looking at your thread it was really a promising one just to start with .
I was at my work time though so just spend only few mjns for that ..
Sorry once again...
If you insist I will change the entire thread
thanks for building RR I'll keep an eye on this as it develops
Working like a dream for me. Really appreciate this.
(/w Nebula 7.0.2)
Tried to add full OMS support to my yesterdays build ... But I think I am missing some steps..
Without some devs support I think I might not be able to fix it
Finally an OMS included RR nightly has been uploaded... See the main thread for download Link...
Night mode / Live display works
RR-N-v5.8.0-20161228-pme-Nightly.zip
@blackpanther0582 could you compile this kernel?
https://github.com/CyanogenMod/android_kernel_htc_msm8996/commits/cm-14.1-caf
OMS(meaning substrarum) I installed from the Play Store on the 12/24 build seems to work fine. Wifi cuts out at random is that the bug everyone talks about? It just puts am X in it and says connected but no internet.
Sent from my HTC 10 using XDA-Developers mobile app
Nosferatu. said:
OMS(meaning substrarum) I installed from the Play Store on the 12/24 build seems to work fine. Wifi cuts out at random is that the bug everyone talks about? It just puts am X in it and says connected but no internet.
Sent from my HTC 10 using XDA-Developers mobile app
Click to expand...
Click to collapse
Same here on both counts. Gonna install the 28th build to check it the wifi's fixed. That's literally the only bug i need fixed to be 100% daily driver. So awesome how fast CM/RR came all the sudden.
holofractal said:
@blackpanther0582 could you compile this kernel?
https://github.com/CyanogenMod/android_kernel_htc_msm8996/commits/cm-14.1-caf
Click to expand...
Click to collapse
Will sure try
OmniROM
[#KITKAT]
for Samsung Galaxy Nexus (Unified)
[#WHATSOMNI]
[#WARRANTY]
Downloads:
[#DLGITHUBIO]
[#INFOOMNI]
Specials added on top of Official OmniRom Source
All in One Animation Control
Battery Saver mode
On-The-Go mode
Implement App circle sidebar
follow dark 4.4 UI
Those features have never been ready for official Omni, but people spend a lot of time writing those features and i really like those.
I am trying to release an security update monthly after google publish android security bulletins.
Support development
[#DONATETOME]
XDA:DevDB Information
[unified][4.4.4] OmniROM, ROM for the Samsung Galaxy Nexus
Contributors
Android-Andi, Ziyan
Source Code: https://github.com/omni-security
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Current Stable Version: Final Build availabl
Created 2017-08-12
Last Updated 2017-08-18
Hello everyone, first of all, great work @Android-Andi thank you to take the time to support our old device !
And then sorry for my noob questions but :
- I didn't quite understand the difference between device specific and unified builds and I don't want to make a mistake flashing the wrong one.
- What is the main difference between Omni 4.4, Omni 6.0 or Slim 6.0? I want to use one of those but I don't know which one I think Omni 4.4 is the closest from what I had with the official Jelly Bean ROM and the 2 others are optimized version of Marshmallow. And is Slim 6.0 faster than Omni 6.0?
Thank you again
Radder124 said:
I didn't quite understand the difference between device specific and unified builds and I don't want to make a mistake flashing the wrong one.
Click to expand...
Click to collapse
Unified builts are for all types of tuna: Maguro, Toro, Toro+. When booting only the needed (device specific) drivers are loaded, but the drivers fir all supported devices are on board...
Unified works on all tuna variants: maguro, toro and toroplus at same time. It detects your variant on first boot and places needed files. That's the one I'll compile in future too.
Which rom is the best? Use the power of your TWRP and try it out. Test one, check if it fits your needs. If not, make a backup and try a different rom.
Android-Andi said:
Which rom is the best? Use the power of your TWRP and try it out. Test one, check if it fits your needs. If not, make a backup and try a different rom.
Click to expand...
Click to collapse
I can ask you a different question With all the new ROMs, I don't know which ROM you would like to receive bug reports from. Crash logs, etc. I know there is no point giving you CM12.1 crash logs. Which ROM would you like us testing and reporting bugs from?
Thank you for providing this ROM! I finally found a ROM with a working camera for the Gnex with security patches (from 2017-07).
...anyone gotten Xposed Framework installed/working with this? Halp
JLsoft said:
...anyone gotten Xposed Framework installed/working with this? Halp
Click to expand...
Click to collapse
There's somewhere an updated version flying around on XDA, maybe you'll find it (i don't have it anymore)
JLsoft said:
...anyone gotten Xposed Framework installed/working with this? Halp
Click to expand...
Click to collapse
try this
@Android-Andi is it possible to use this ROM with F2FS file system? Which DDK version is included in this ROM? Thank you for your contribution.
Those who are on 4.4:
AOSP Browser was removed for security reasons. Most lightweight Browser use KitKats webview which isn't up to date any more and there's ATM no proper way to update it.
You should use a browser which has its own webview implementation like Chrome, Firefox or Chromium.
From what I have tested Chromium seems to be a good solution. Here's my self compiled Chromium:
https://github.com/andi34/prebuilt_chromium/raw/master/ChromePublic.apk
(It's only missing h264 encoder for legal reasons...H.264 is not a free codec and I don't have the license for distributing)
For Android 5+
https://github.com/andi34/prebuilt_chromium/raw/master/ChromeModernPublic.apk
For Android 7+
https://github.com/andi34/prebuilt_chromium/raw/master/MonochromePublic.apk
New builds are up.
Switched to default libion, thx to @Ziyan and @amaces !
Note: don't flash any custom kernel on this build (also AnyKernel isn't compatible ATM)!
I've been away from the scene for a while so please catch me up. Does this rom bypass carrier limitations when using usb tether?
madspeed said:
I've been away from the scene for a while so please catch me up. Does this rom bypass carrier limitations when using usb tether?
Click to expand...
Click to collapse
Yep, these custom ROMs have nothing to do with carriers
March update is online. Enjoy!
Dear developer,
firstable many thanks for your Rom
I was using OMNI 4.4.4 dated 2015 but I was living issue with GMAIL, HANGOUT and GDRIVE
Today I discovered your product and Installed it on my MAGURO with a clean installation
Unfortunately after few hours I am suffering reboot
The system boots well but after few seconds it reboots itself ... continuosly ...
I am using omni_tuna-4.4.4-20180311-1556
I used GAPPS open_gapps-arm-4.4-pico-20180427
I rooted with SUperSU 2.82 R5
I tried to wipe cache, dalvik-cache, system and reinstall the rom and the gapps wo success
I tried to remove root wo success
HAve you some idea to help me ?
Thanks
Paolo
[EDIT]
I wiped all (clean installation) and installed the older version of rom (omni_tuna-4.4.4-20180128-0005)
[I noted that this version is bigger than the newer of around 30MB ...)
Same GAPPS af above
Same root of above
It runs well now ... cross the fingers and stay tuned
People having issues on latest build could try https://forum.xda-developers.com/showpost.php?p=76429699&postcount=188
The request from root was one of my suspect
Do you suggest to flash new kernel after last updated ROM, gapps and root and so before the first boot ?
Do you confirm that this workaround is not necessary with the previous version ?
Are you able to identify which version needs and which didn't ?
For instance I am using the January version .... Did I need to flash new kernel ?
Inviato dal mio Galaxy Nexus utilizzando Tapatalk
It could be it's needed on all KK roms since end of last year. But only works for latest builds using default libion.
Android-Andi said:
It could be it's needed on all KK roms since end of last year. But only works for latest builds using default libion.
Click to expand...
Click to collapse
Excuse my noob ... What does it mean default libion ?
Inviato dal mio Galaxy Nexus utilizzando Tapatalk
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...