Related
Guardian Rom by x942Thanks to:
The Guardian Project
Cyanogen Mod
Android Open Source Project
Open-Pdroid Project
Any one else I am missing
Click to expand...
Click to collapse
What is Guardian Rom?
Guardian ROM is a custom android ROM multiple devices. The ROM is completely Open Source and based off of the CM10.1. While this build is stable because it's based on CM10.1 it is a preview so please expect some bugs, & missing features (i.e updater).
What Features does Guardian Rom have?
Kernel is hardened with SecDroid Tweaks.
ROM is patched with and includes OpenPdoird for
permissions management.
Guardian Project apps are pre-installed – These include Orbot (Tor), Gibberbot (Secure IM),
and more.
CSSimple and OStel (https://guardianproject.info/wiki/Ostel) are included as replacements to the
built calling apps. providing encrypted communications.
If encryption is enabled and password is entered wrong 10 times the phone wipes user data.
Click to expand...
Click to collapse
Coming Soon:
Including support for Deniable Encryption (similar to Truecrypt hidden volumes).
Including GRSecurity for exploit mitigation and more secure phone.
Including SQLCipher to ensure all data is encrypted whenever possible
Including a customer “app store” for our repos.
Different lockscreen pin and Pre-Boot authentication password.
Auto-Prompt for encryption setup on first boot.
Click to expand...
Click to collapse
How to use:
Simply flash the flashable zip through your favorite custom recovery. (TWRP is recommended as it supports encrypted devices). Once flashed you should enable Full Disk Encryption by doing the following (may very depending on device):
Code:
Settings --> Security ---> Password [enter a strong 8-16 char password]
Than
Code:
Settings --> Security ---> Encryption --> Enable Encryption
Downloads:Downloads are over here.
Please verify the downloaded file with the attached GPG signature to ensure is is a legit copy.
GAPPS
Google Apps are NOT included and before you flash them you may want to read this article.
UPDATES:
Since this is a preview I have not had a chance to remove or modify the CM Updater. Please do NOT use it as you will be flashing a stock CM10.1 build and not Guardian Rom. This will be fixed shortly.
Reserved.
you could cherrypick some stuff from here
selinuxproject.org/page/SEAndroid
baz77 said:
you could cherrypick some stuff from here
selinuxproject.org/page/SEAndroid
Click to expand...
Click to collapse
I may use SeAndroid. Right now I am focusing on the encryption side of things instead of the exploit mitigation side. That will come later.
Been following your work on sec Droid, this looks like a very very good start! May I know which version of CM that you used for this? Or it is based on the latest repo when you built it.
Thanks!
Flowed from my Nexus⁴
azrash said:
Been following your work on sec Droid, this looks like a very very good start! May I know which version of CM that you used for this? Or it is based on the latest repo when you built it.
Thanks!
Flowed from my Nexus⁴
Click to expand...
Click to collapse
Awesome! Thanks! It's is based off the latest repo. I simple pulled and than modified the sources. I am currently getting some hosting for our own repo and Tor Hidden service for downloading. Stay tuned much more to come.
TimeAndroid said:
Look'in good, might try.
Click to expand...
Click to collapse
The next build will have an AOSP 4.2.2 base with Mobiflage built in. Also Lock screen PIN and Pre-Boot PINs are now separated. So you can use a simple 4 digit pin on the lock screen and a 32 character pin at boot.
Also for more security you have to passwords one for the "outer volume" which you use as you daily usage and one as "hidden volume" which is your hidden os. You use the second for anything sensitive. That way if an attacker tries to force you to give up your password you just give up the outer volume (decoy) password. There is no way to prove the hidden volume exists.
Encryption also uses AES-256-XTS now instead of AES-128-CBC. Better key length and protection against watermarking attacks.
EDIT: If anyone wants early access please PM. The build is not ready for prime time as there is no GUI for encryption but can be used as a daily driver.
SecUpwN said:
No, I'm sure you're right. But since he explicitly stated that he won't build an ('unofficial') AOKP version, I'm looking for a way to get in the favor of the securiry modifications without gaving to switch to another ROM. It's just that AOKP has so many cool simplifications compared to CyanogenMod, I'd like to avoid a switch backwards. Maybe he could create an unsupported AOKP version every month? Possible?
Click to expand...
Click to collapse
Or you could compile your own. Not trying to sound like a d**k but he had already stated numerous times he is only doing Cm base and yet u and others keep saying do this for aokp. There is a reason he is using cm as a base.
Sent from my Nexus 4 using Tapatalk 4 Beta
DontPushButtons said:
I'm guessing the modifications he has been making go a little further beyond a flashable zip. Otherwise he would've done that instead of making a whole rom around privacy.
Could be wrong..
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes. I custom kernel is needed at the very least. Not to mention removal of Google Apps and tweaked UI for encryption (mobiflage). All of these are OS level tweaks and cannot be made into a ZIP.
droidkevlar said:
Or you could compile your own. Not trying to sound like a d**k but he had already stated numerous times he is only doing Cm base and yet u and others keep saying do this for aokp. There is a reason he is using cm as a base.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
This. AOKP will NOT be supported. EVER. If anyone wants a different base download the source code from my github and compile it yourself. Build documentation is on there. Furthermore AOKP and CM10.1 are both great roms, however there are too many variables. Both have a ton of unneeded binaries and settings. We cannot guarantee security are these builds. We choose CM10.1 because it's fully open source and has fewer complications then AOKP. On NEXUS devices we are using AOSP modified with our security tweaks. On non-nexus we use CM10.1 for now for simplicity.
I am hoping with the recent Google Edition devices it will be easier to port/compile AOSP onto those devices.
TL;DR:
WE WILL NEVER OFFICIALLY SUPPORT AOKP.
Thanks for understanding.This message is only meant to stop these requests, not to be rude so please don't take it that way.
Cleaning
This thread is in the DEVELOPMENT section. And is for the "Guardian Rom [Secure] [Privacy] [Preview]".
If you need to report an issue or bug then READ THIS POST ABOUT BUG REPORTS
Keep ALL posts aimed at the ROM development.
This thread is NOT A Q&A thread.
So don't ask why the WiFi won't work, post a LOGCAT of the actual event or it did not happen.
I have cleaned this thread.
If you repeatedly make junk posts, then INFRACTIONS will follow.
~JAB
Hey @x942, where is our Android 4.3 version of this funky ROM?
SecUpwN said:
Hey @x942, where is our Android 4.3 version of this funky ROM?
Click to expand...
Click to collapse
We are working toward this. The issue we are having is that while 4.3 is latest 5.0 may be just around the corner. We don't want invest a ton of effort just to have re-port everything to 5.0 if it's released 2-3 months from now. That's not to say 4.3 won't happen. It's just we are focusing on adding more security. For now stable is 4.2.2.:good:
Am I missing where to find the flashable zip?
Sent from my Nexus 4 using xda app-developers app
Will this ever come to a Samsung Galaxy 3, or are your plans only for Nexus devices?
koz said:
Will this ever come to a Samsung Galaxy 3, or are your plans only for Nexus devices?
Click to expand...
Click to collapse
S3 is underway. We have support for:
S3, HTC One, Nexus 4, Galaxy Nexus, S4, Nexus 7 and soon Moto X, Note 3 and Nexus 5.
Request
Hi,
Please add the new moto g xt1032 to your list of planned devices - it would be a great way to get more people secured as it is a very popular handset
Thanks for all your hard work!
x942 said:
S3 is underway. We have support for:
S3, HTC One, Nexus 4, Galaxy Nexus, S4, Nexus 7 and soon Moto X, Note 3 and Nexus 5.
Click to expand...
Click to collapse
Has this ever been developed for the Galaxy S3? I haven't been able to find a download anywhere...
@X942 gaurdian rom sounds very interesting to me. would also like the att slll i747 to be added on list for consideration for dev.
am not a dev myself.
thank you for your work/time/energy. :thumbup:
err on the side of kindness
good
Sent from my Nexus 4 using XDA Premium 4 mobile app
x942 said:
S3 is underway. We have support for:
S3, HTC One, Nexus 4, Galaxy Nexus, S4, Nexus 7 and soon Moto X, Note 3 and Nexus 5.
Click to expand...
Click to collapse
I cant find a download for the Note 3 ROM. The only thing I read about it is an update on http://shadowdcatconsulting.com/blog/ saying that support will come soon.
ATTENTION! I HAVE MOVED THE SCRIPT OVER TO:
MOD EDIT: REMOVED: Requires registration
ALL CONVERSATIONS AND DEVELOPMENT WILL NOW BE CARRIED OUT THERE!
Do you network security work? Do you hate having to carry around a laptop with you when you do your work? Are you wondering why I'm asking you all these questions?
Well, have I got something for you! Based on Kali NetHunter, I have created an installer script that will give you NetHunter AND be able to multi boot between your stock OS and your Kali OS!
FEATURES:
Install NetHunter and all of its fun features
Gives you the ability to boot between multiple OSs
Lets you choose between Using different ROMs as the base for Kali
And much more!
Supported Devices:
Nexus 5 (Hammerhead)
Nexus 7 2012 Wifi (Grouper)
Nexus 7 2012 Cellular (Tilapia)
Nexus 7 2013 Wifi (Flo)
Nexus 7 2013 LTE (Deb)
Nexus 10 2012 Wifi (Manta)
Planned Features:
Support for more base ROMs for Kali NH
More Automated
Instructions:
ALWAYS RUN THE SCRIPT UPDATER WHEN YOU RUN THE SCRIPT
Download the kfu.zip at the bottom of this post
Unzip the file
Run the extracted kfu.sh (You may have to run "chmod +x kfu.zip")
MAKE SURE TO SELECT THE UPDATE OPTION TO MAKE SURE IT IS UP TO DATE!
Follow the instructions
You now have Kali NetHunter!
Changelog:
v1.4
Added auto-updating capability.
v1.3.4
Added Pac-ROM as a base ROM for Kali
Fixed some bugs
v1.3.3
Slightly more verbose
Fixed some bugs
v.3.2
Added the ability to restore to the stock Google-provided ROM!
v.3.1
Installs MultiROM Manager APK to internal ROM.
v1.3
Added support for the Nexus 10 (Manta)!
v1.2
Installing files with multirom already installed
Ability to install kali to existing ROM without MultiROM
Option to uninstall MultiROM and all secondary ROMs
v1.1.1
Fixed a few small bugs
v1.1
Changing hosting to the file's owner's servers. i.e. Kali Utilities hosted on kali servers
Fixed some bugs.
v1.0
EVERYTHING.
Updated to V3.7
Changes:
Code cleanup
Moved file hosting to Google drive (It's faster!)
Awesome just ordered the hardware. Been meaning to try this out! Thanks.
Sent from my Nexus 7 using Tapatalk
ironmaskusa said:
Awesome just ordered the hardware. Been meaning to try this out! Thanks.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Let me know how well it works! I don't have a 2012 Nexus 7 or a Nexus 5 so all of this is theoretically supposed to work, other people have done it successfully, but I couldn't try for myself.
OK.. Hopefully next week sometime
Sent from my Nexus 7 using Tapatalk
awesome, i gotta do a security presentation for a class and wanted to show off pen testing with my nexus
Now I just need to find my laptop with lynux already installed so I can commence to doing this!
Sent from my Nexus 7 using Tapatalk
Hmmm this is cool
Sent from my Nexus 7 using XDA Free mobile app
Now just waiting for USB otg Y cable.. That may take a week or 2 from what the amazon store said though.. Is there a GUI that puts me into monitor mode and let's me do attacks or is it all terminal shell based?
Sent from my Nexus 7 using Tapatalk
ironmaskusa said:
Now just waiting for USB otg Y cable.. That may take a week or 2 from what the amazon store said though.. Is there a GUI that puts me into monitor mode and let's me do attacks or is it all terminal shell based?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Depends on the attack. It is mostly terminal based, but the utilities have a nice "UI". There are a couple apps that actually have a native Android UI.
Oh, some apps I recommend downloading: dSploit and Network Spoofer. They have some nice native android UIs!
Cool sounds great! I've done penetration tests on Ubuntu setup.. But I think it will be really cool to do this with my Nexus soon! Thanks again, I will return with some feedback after I get my last hardware peripheral to complete the setup.
Sent from my Nexus 7 using Tapatalk
I have gone over my Dropbox bandwidth limit, so I cannot host the files! If anybody knows of a file sharing service that allows direct links, let me know!!
I seem to have found a solution to my hosting issues! I shall push the updated script soon!
I was going to mention Google drive? Please do post your update.. I'm still waiting on the USB otg with the ability to power the WiFi adapter to get this project running. I just wish there was a simpler way, like just flashing it like a regular custom ROM and kernel.
Sent from my Nexus 7 using Tapatalk
ironmaskusa said:
I was going to mention Google drive? Please do post your update.. I'm still waiting on the USB otg with the ability to power the WiFi adapter to get this project running. I just wish there was a simpler way, like just flashing it like a regular custom ROM and kernel.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
There is someone who offered to host the files with a couple TB of bandwidth, so I'm looking into that... If not, I have a backup plan! The backup plan isn't very high speed unfortunately.
EDIT: I have been having issues with Google Drive's direct downloads. I'm not sure if curl doesn't like them or what...
EDIT 2: I am looking into making it into just one big flashable zip. I have a computer that I can have automatically build and update zips, but I need to learn how to combine zips in a script and stuff first...
So this would mean you could flash it like a custom ROM with no need of using a Linux PC? If so, that would be freaking awesome! ?
Maybe one of the devs could help you out?
Sent from my Nexus 7 using Tapatalk
ironmaskusa said:
So this would mean you could flash it like a custom ROM with no need of using a Linux PC? If so, that would be freaking awesome! ?
Maybe one of the devs could help you out?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yup! Like I said though... I need to fix the file hosting, then make the all-in-one zips!
Good luck I'm really anticipated! ?
Sent from my Nexus 7 using Tapatalk
How is the progress going? @photonicgeek
Sent from my Nexus 7 using Tapatalk
am i wrong. it will install multiboot then installs kali and the previous rom ?
I'm not sure.. That is why I would love to see this as a normal ROM to flash inside multirom so I can convert to F2FS as well and just boot into it when I want to use it, yet still use my daily driver.. Although, if this ROM runs fairly smooth and I can use mkernel on it I would just consider it as my daily driver.. I'm still waiting for my OTG USB with power to give this a shot.. It should be here in a few days.
Sent from my Nexus 7 using Tapatalk
Apologies for the links: as I am a new user, I am not allowed to directly link to outside sources. Please replace _ with :// or . (Forum suggestion: use optional pre-publication review for posts from new users that depend strongly on external links.)
INTRODUCTION: My BMW 318 (E46, 2004) had a factory default BMW ULF bluetooth module (early generation) that worked fine with my BB Q10 and all phones up to Android 4.1. From 4.2 onwards, I and many others have been having problems with keeping the Bluetooth connection alive for more than a few seconds. This has been widely reported but never addressed in stock Android. As even the latest OTA upgrade to 4.4.3 didn't solve it, I decided to compile the required Bluetooth kernel module myself.
BACKGROUND: The change from the Bluez to Bluedroid system in Android 4.2 caused the compatibility issues. User 'wulu' at the forums of CyanogenMod reported on how he patched his CM10.2 (and later) to include a patch that solves the issue. I repeated his procedure for stock 4.4.3 for the Nexus 5.
Markus Schmidt's problem description & patch: https_github_com/Root-Box/external_bluetooth_bluedroid/commit/97d2f6346bad56299f60cfcd8c45ad893a0da78c
Wulu's specifics for Nexus 5 & BMW's ULF for CM: http_forum_cyanogenmod_com/topic/77834-bluetooth-connection-drops-car-kit-bmw/
METHODS:
The following procedure is specifically to compiled the Bluetooth kernel module for the Nexus 5 hardware and the 4.4.3_r1.1 (OTA) release. It should therefore only work for this specific combination. If you want to compile the module yourself, please read the linked pages with Google's excellent instructions: http_source_android_com/source/initializing.html
Here are a couple of notes I made that deal with some specifics for my Mac and the Nexus 5:
On Mountain Lion (Mac), I had to use Xcode 5.0.2 to get past a compile error. See instructions here on how to download and use the older 5.0.2 version of Xcode: https_groups_google_com/forum/#!topic/android-building/FPCSo1xKJ4U
Do not download the "master" source using the repo command, but download "android-4.4.3_r1.1". The master source has post-OTA changes that make a compiled module incompatible with the OTA release for the Nexus 5. "android-4.4.3_r1.1" was listed on those pages as specifically the version that was used for the OTA 4.4.3 upgrade for the Nexus 5.
Setup the environment as instructed and add the three proprietary driver sets listed for the Nexus 5 and 4.4.3 (see "Building for devices" on the Google pages).
There is no need to use the full patch. You can make the two small modifications to the bta_ag_sdp.c file using any text editor. Find the file first (find . -name "bta_ag_sdp.c") and commend out the two lines with the minus signs given in wulu's the first post (or Markus Schmidt's patch) by putting a # in front of both lines: #if (p_scb->peer_features == 0), #p_scb->peer_features = p_attr->attr_value.v.u16;.
Select the "aosp_hammerhead-userdebug" (=Nexus 5) option with the lunch command, and compile using the make command. I was able to follow the instructions pretty much to the letter without any problems.
After the compilation I had two version of the file, in four locations. They are easily found using the find command (find . -name "bluetooth.default.so" -exec ls -la {} \. The bigger one (in the symbols subdirectory) is for debugging. The smaller one is the one I used (and which is linked in this message). It was located at "./out/target/product/hammerhead/system/lib/hw/bluetooth.default.so" in my source tree.
After this, it was pretty straightforward. I rooted my Nexus 5, re-installed FX (with paid-for Root add-on, but the free ES File Explorer should also work), uploaded the file via Dropbox and its Save to SD, transferred it to the R/W mounted system directory to replace /system/lib/hw/bluetooth.default.so with it, and restarted my phone. I also modified the config file (/system/etc/bluetooth/auto_pair_devlist.conf) that blacklists BMW components by commenting out most lines, but I am not sure if this is helpful or not.
RESULTS: It seems a little bit less stable than the Bluetooth connection I had with my Blackberry, but it definitely works. I was able to transfer my contacts and to make and receive calls. For anybody with stock KitKat 4.4.3 on the Nexus 5, here is the bluetooth.default.so kernel module: http_s000_tinyupload_com/index.php?file_id=07750725920558658087
DISCUSSION: The compilation procedure can undoubtedly be optimized. I compiled the entire source tree over several hours, just to be sure I didn't miss out on things. Feel free to give tips, but I'm happy that it worked at all.
CONCLUSION: Thanks to wulu's advice in the CM forum thread I was able to compile a patched Bluetooth module for stock Android with KitKat 4.4.3 that works with my BMW 318 (E46, 2004) ULF car kit.
That´s great! :good:
Is it possible for you to provide the same for Nexus 5 - 4.4.4 OTA ?
mnasty said:
That´s great! :good:
Is it possible for you to provide the same for Nexus 5 - 4.4.4 OTA ?
Click to expand...
Click to collapse
Yes, great job!
Nobody have already done this for 4.4.4 ? I'll do this if I have time.
ZeroKcm said:
Yes, great job!
Nobody have already done this for 4.4.4 ? I'll do this if I have time.
Click to expand...
Click to collapse
4.4.4 from 4.4.3 is only security fixes, everything else is the same.
Does 5.0 Lollipop resolve the BMW ULF connection issue?
guys, do you think 5.0 Lollipop would resolve the current BMW ULF connection problem? Have anyone tried the 5.0 yet ?
I'm still in 4.4.3 working great on N5 paring ULF 8th Gen kit, thanks for S1010, wulu and Alpejohn guiding me the entire process.
REV HRD said:
guys, do you think 5.0 Lollipop would resolve the current BMW ULF connection problem? Have anyone tried the 5.0 yet ?
I'm still in 4.4.3 working great on N5 paring ULF 8th Gen kit, thanks for S1010, wulu and Alpejohn guiding me the entire process.
Click to expand...
Click to collapse
I have the same disconnect issue with my Seat, haven't tried the fix cause I was running 4.4.4 and there was no ready module for it, but lollipop didn't fixed it. I tried compilation without success. I followed all the instructions and compiled it successfully, but after replacing it, bluetooth fails to start. In the logcat logs I can see that it complains there is no bluetooth (something like that, don't have the exact logs to check it now), seems the compiled so file is not compatible.
If anyone can give a hand on this
Not sure if Seat using the same implementation as BMW ULF kit provides, my family also has a 06 Audi A4 with stock BT, I don't experience any connection issue from the stock 4.4.3 on N5. I would think Audi / Seat might use the same BT module as they share most of the VW parts.
I experience the same disconnects. I was experiencing it and with the old phone Galaxy Nexus, till one day I updated to cyanogenmod and the problem was gone. Then changed the phone with Nexus5 and again I have the same issues, tried everything with no luck. Changing the kernel, doing some stuff with paid bluetooth apps to manage the phonebook that the car is accessing. So I suspect the problem is the same
(Seems I'm still not able to post links, I just prepared one with the Blutooth device model number and year on it, if it mean anything to someone it is from 03.2007).
Don't work in lollipop, in your free time please compile a new file.
Thks.
S1010 said:
Apologies for the links: as I am a new user, I am not allowed to directly link to outside sources. Please replace _ with :// or . (Forum suggestion: use optional pre-publication review for posts from new users that depend strongly on external links.)
INTRODUCTION: My BMW 318 (E46, 2004) had a factory default BMW ULF bluetooth module (early generation) that worked fine with my BB Q10 and all phones up to Android 4.1. From 4.2 onwards, I and many others have been having problems with keeping the Bluetooth connection alive for more than a few seconds. This has been widely reported but never addressed in stock Android. As even the latest OTA upgrade to 4.4.3 didn't solve it, I decided to compile the required Bluetooth kernel module myself.
BACKGROUND: The change from the Bluez to Bluedroid system in Android 4.2 caused the compatibility issues. User 'wulu' at the forums of CyanogenMod reported on how he patched his CM10.2 (and later) to include a patch that solves the issue. I repeated his procedure for stock 4.4.3 for the Nexus 5.
Markus Schmidt's problem description & patch: https_github_com/Root-Box/external_bluetooth_bluedroid/commit/97d2f6346bad56299f60cfcd8c45ad893a0da78c
Wulu's specifics for Nexus 5 & BMW's ULF for CM: http_forum_cyanogenmod_com/topic/77834-bluetooth-connection-drops-car-kit-bmw/
METHODS:
The following procedure is specifically to compiled the Bluetooth kernel module for the Nexus 5 hardware and the 4.4.3_r1.1 (OTA) release. It should therefore only work for this specific combination. If you want to compile the module yourself, please read the linked pages with Google's excellent instructions: http_source_android_com/source/initializing.html
Here are a couple of notes I made that deal with some specifics for my Mac and the Nexus 5:
On Mountain Lion (Mac), I had to use Xcode 5.0.2 to get past a compile error. See instructions here on how to download and use the older 5.0.2 version of Xcode: https_groups_google_com/forum/#!topic/android-building/FPCSo1xKJ4U
Do not download the "master" source using the repo command, but download "android-4.4.3_r1.1". The master source has post-OTA changes that make a compiled module incompatible with the OTA release for the Nexus 5. "android-4.4.3_r1.1" was listed on those pages as specifically the version that was used for the OTA 4.4.3 upgrade for the Nexus 5.
Setup the environment as instructed and add the three proprietary driver sets listed for the Nexus 5 and 4.4.3 (see "Building for devices" on the Google pages).
There is no need to use the full patch. You can make the two small modifications to the bta_ag_sdp.c file using any text editor. Find the file first (find . -name "bta_ag_sdp.c") and commend out the two lines with the minus signs given in wulu's the first post (or Markus Schmidt's patch) by putting a # in front of both lines: #if (p_scb->peer_features == 0), #p_scb->peer_features = p_attr->attr_value.v.u16;.
Select the "aosp_hammerhead-userdebug" (=Nexus 5) option with the lunch command, and compile using the make command. I was able to follow the instructions pretty much to the letter without any problems.
After the compilation I had two version of the file, in four locations. They are easily found using the find command (find . -name "bluetooth.default.so" -exec ls -la {} \. The bigger one (in the symbols subdirectory) is for debugging. The smaller one is the one I used (and which is linked in this message). It was located at "./out/target/product/hammerhead/system/lib/hw/bluetooth.default.so" in my source tree.
After this, it was pretty straightforward. I rooted my Nexus 5, re-installed FX (with paid-for Root add-on, but the free ES File Explorer should also work), uploaded the file via Dropbox and its Save to SD, transferred it to the R/W mounted system directory to replace /system/lib/hw/bluetooth.default.so with it, and restarted my phone. I also modified the config file (/system/etc/bluetooth/auto_pair_devlist.conf) that blacklists BMW components by commenting out most lines, but I am not sure if this is helpful or not.
RESULTS: It seems a little bit less stable than the Bluetooth connection I had with my Blackberry, but it definitely works. I was able to transfer my contacts and to make and receive calls. For anybody with stock KitKat 4.4.3 on the Nexus 5, here is the bluetooth.default.so kernel module: http_s000_tinyupload_com/index.php?file_id=07750725920558658087
DISCUSSION: The compilation procedure can undoubtedly be optimized. I compiled the entire source tree over several hours, just to be sure I didn't miss out on things. Feel free to give tips, but I'm happy that it worked at all.
CONCLUSION: Thanks to wulu's advice in the CM forum thread I was able to compile a patched Bluetooth module for stock Android with KitKat 4.4.3 that works with my BMW 318 (E46, 2004) ULF car kit.
Click to expand...
Click to collapse
FYI, had similar issue with 2009 E61 5 series. Solution was third party app (Bluetooth Phone book) and a full software update for the car from the dealer. The app cost a few quid, the dealer software update much more!
That said, it works perfectly with stock Lollipop and I consider it money well spent.
---------- Post added at 09:15 PM ---------- Previous post was at 09:13 PM ----------
FYI, it was this app: https://play.google.com/store/apps/details?id=com.android_rsap.irmc
Hi guys, i found android device tree for our device (anzhen4_mrd7), apparently for cm12:
https://github.com/quanganh2627/android_device_intel_baytrail
Anyone wants to try a build or two?
Kryogen said:
Hi guys, i found android device tree for our device (anzhen4_mrd7), apparently for cm12:
https://github.com/quanganh2627/android_device_intel_baytrail
Anyone wants to try a build or two?
Click to expand...
Click to collapse
OMG!
So all developers could release their own version of Android 5 Lollipop for Teclast x98 Air devices!!!!
This is a great news!
Maxximo88 said:
OMG!
So all developers could release their own version of Android 5 Lollipop for Teclast x98 Air devices!!!!
This is a great news!
Click to expand...
Click to collapse
Actually, that's just a repo i found online
IT could be useful, it could be not - we're missing prebuilt binaries and kernel drivers (Though i don't think the tablet uses private kernel drivers, they should already be in there )
Good news is: lenovo youga tablet 2 has similar hardware to our x98, and its full source code is public
Kryogen said:
Actually, that's just a repo i found online
IT could be useful, it could be not - we're missing prebuilt binaries and kernel drivers (Though i don't think the tablet uses private kernel drivers, they should already be in there )
Good news is: lenovo youga tablet 2 has similar hardware to our x98, and its full source code is public
Click to expand...
Click to collapse
Yep, I saw it has 10,1" FHD IPS, Intel Atom Z3745, 1,3GHz, 2GB RAM!
Nice, I hope to see some devs interested in sources...Maybe to see a CyanogenMOD port!
Is it possible to use the Lenovo source code, add some stuff extracted from the stock boot.img and build a asop rom?
I'm not a dev and I want to know a bit more about this...
Gesendet von meinem X98 Air 3G mit Tapatalk
Best kernel for testing
Hi,
I've made some tests 6 months ago, The best kernel was the kernel of the Dell Venue ( just check dell + opensource on google) , Everything was working but deep sleep and charging. The tests were done with grub on a usb key , kernel on usb key and system image on flash.
Now I've got a x98 plus tablet, I hope to have some time to recompile a kernel.
Cheers
Occip
occip said:
Hi,
I've made some tests 6 months ago, The best kernel was the kernel of the Dell Venue ( just check dell + opensource on google) , Everything was working but deep sleep and charging. The tests were done with grub on a usb key , kernel on usb key and system image on flash.
Now I've got a x98 plus tablet, I hope to have some time to recompile a kernel.
Cheers
Occip
Click to expand...
Click to collapse
Nice, so with that kernel we can just change it when it is power off?
This Magisk module adds the required firmware for external wireless adapters to be used with Nethunter.
NOTE: Your kernel still needs to support external network adapters. This module only provides missing firmware, if any.
The list of included firmware is given below. For other devices, create a new issue on GitHub here.
This module should work with any variant of Nethunter, but it was created to work with Nali Kethunter (https://forum.xda-developers.com/an...li-kethunter-modded-kernel-supported-t3770455) - another Magisk module by @LazerL0rd which systemlessly installs Kali Nethunter.
Supported chipsets:
htc_7010 (used by TL-WN722N)
htc_9271
RT2870 (used by AWUS036NEH)
RT3070, RT3071 (used by TE-W322U)
RTL8188EU (used by TL-WN722N-V2)
RTL8192* (CU, EU, DE, SE)
MT7601u
Downloads
Available in Magisk Manager, also flashable zip attachment.
Changelog
Code:
v2.0.3
Added files for bcm43xx (meant for bcm4358)
v2.0.2
Added all Ralink files
Check chipset list above
v2.0.1
Added files for AR7010 and RTL8821
v2.0.0
Migrated to new Magisk Installer template
Added upater-script for zip flashing
v1.0.5
Added files for AR9170
v1.0.4
Added files for RTL8192
v1.0.3
Added files for RTL8188EU
v1.0.2
Added files for RT3070 and RT3071
v1.0.1
Added files for RT2870 and MT7601u
v1.0
Initial release
Source: https://github.com/rithvikvibhu/nh-magisk-wifi-firmware
Issues / Request other firmware: https://github.com/rithvikvibhu/nh-magisk-wifi-firmware/issues
any chance of adding in RT 8187?
thirtythr33 said:
any chance of adding in RT 8187?
Click to expand...
Click to collapse
Hm. I only seem to find drivers for RTL8187. Is that what you're looking for?
rithvikvibhu said:
Hm. I only seem to find drivers for RTL8187. Is that what you're looking for?
Click to expand...
Click to collapse
yes that is it! that would be perfect!
thirtythr33 said:
yes that is it! that would be perfect!
Click to expand...
Click to collapse
From what I can find, this should already be present by default. There are very old drivers which can be installed separately, but I don't have a lot of hope for that. Can you send a dmesg log right after plugging the adapter in? The problem might be something else.
rithvikvibhu said:
From what I can find, this should already be present by default. There are very old drivers which can be installed separately, but I don't have a lot of hope for that. Can you send a dmesg log right after plugging the adapter in? The problem might be something else.
Click to expand...
Click to collapse
yes I will definitely do that. I'm glad you said they may already be present because I am working on getting my kernel patched to enable external adapter support. so it may not even be an issue with the module I just didn't see it listed in the supported chipsets. antsy I'll respond once I get the kernel patched. thank you for responding!
not find for antheros AR9271L or AR9002U chipset
I do not find support about Atheros chipset AR9271L OR Atheros AR9002U in his description whether you can add the driver for wifi adapter card TP-Link tl-wn722n v1.
Please Help me..!!
---------- Post added at 04:47 AM ---------- Previous post was at 04:17 AM ----------
rithvikvibhu said:
From what I can find, this should already be present by default. There are very old drivers which can be installed separately, but I don't have a lot of hope for that. Can you send a dmesg log right after plugging the adapter in? The problem might be something else.
Click to expand...
Click to collapse
can you help me please to add driver for Atheros AR9271L on tl-wn722n v1
Tarra Ista said:
I do not find support about Atheros chipset AR9271L OR Atheros AR9002U in his description whether you can add the driver for wifi adapter card TP-Link tl-wn722n v1.
Please Help me..!!
---------- Post added at 04:47 AM ---------- Previous post was at 04:17 AM ----------
can you help me please to add driver for Atheros AR9271L on tl-wn722n v1
Click to expand...
Click to collapse
Both AR9271L (same as AR9271) and AR9002U are supported right from V1. Must've missed it while updating the README.
Thanks for letting me know, I'll add it to the list. Btw did you try the module? Did it work? If there are any issues, feel free to create a new issue at https://github.com/rithvikvibhu/nh-magisk-wifi-firmware/issues
rithvikvibhu said:
This Magisk module adds the required firmware for external wireless adapters to be used with Nethunter.
Supported chipsets:
htc_7010 (used by TL-WN722N)
Click to expand...
Click to collapse
What about ath9k_htc driver ?
Its better than htc_7010
bezpieka said:
What about ath9k_htc driver ?
Its better than htc_7010
Click to expand...
Click to collapse
I haven't given it much thought really. This has been working for me for years without issues.
Zip flashable thru TWRP?
Sent from my POCOPHONE F1 using Tapatalk
help please
i was searching for the MT7612U driver, can you add it or tell me how i can add by myself plz?
thanks
ellednarb666 said:
Zip flashable thru TWRP?
Sent from my POCOPHONE F1 using Tapatalk
Click to expand...
Click to collapse
Yes. Both via Magisk Manager and TWRP.
SPIKELORD said:
i was searching for the MT7612U driver, can you add it or tell me how i can add by myself plz?
thanks
Click to expand...
Click to collapse
You basically have to find the correct firmware files for that chipset. I'll try to look for it and add it.
I already flashed thru magisk (repo) but still my external adapter is undetected.
My device is Poco F1 and my question is, should I just flash the zip or extract the firmware and place to the right path?
Sent from my POCOPHONE F1 using Tapatalk
ellednarb666 said:
I already flashed thru magisk (repo) but still my external adapter is undetected.
My device is Poco F1 and my question is, should I just flash the zip or extract the firmware and place to the right path?
Sent from my POCOPHONE F1 using Tapatalk
Click to expand...
Click to collapse
Just flash it. No need to extract anything.
Get the latest copy from the GitHub repo. I haven't updated the files on XDA or even GitHub releases in a long time.
Flashing didnt work.
Btw, my phone is Poco and my Ext Wifi is Tenda W311M v2
Sent from my POCOPHONE F1 using Tapatalk
ellednarb666 said:
Flashing didnt work.
Btw, my phone is Poco and my Ext Wifi is Tenda W311M v2
Sent from my POCOPHONE F1 using Tapatalk
Click to expand...
Click to collapse
Check out GitHub issues, feel free to create one with dmesg right after plugging the adapter.
Also, some people miss it:
If it does not work, then make sure you have the correct drivers installed, kernel built with support, etc. This module only adds some firmware files required, systemless-ly.
What that means?
NOTE:*Your kernel still needs to support external network adapters.*
I need custom kernel with rtl8812au drivers inside? So why i need this firmware if i need kernel? Or just kernel with enabled modules?
unknown1818 said:
What that means?
NOTE:*Your kernel still needs to support external network adapters.*
I need custom kernel with rtl8812au drivers inside? So why i need this firmware if i need kernel? Or just kernel with enabled modules?
Click to expand...
Click to collapse
This module only provides firmware files that some devices need (located at /etc/firmware/). It isn't a replacement for kernels with support for the adapters.
Will try it, i found files for rtl8188eu in the kernel source of NetHunter for OnePlus7