So I'm trying to get halium working for tab 2 (we can get ubuntu touch and maybe even plasma mobile with help of it) and I get this error
Code:
arch/arm/boot/compressed/atags_to_fdt.o: In function `merge_fdt_bootargs':
atags_to_fdt.c:(.text+0x20c): undefined reference to `__stack_chk_fail'
atags_to_fdt.c:(.text+0x210): undefined reference to `__stack_chk_guard'
It seems to be a toolchain error any help?
"It would appear that the -mstack-protector-guard option is only for backwards compatibility with how the stack protector worked in the past. In the past the canary was in a global variable. Later it was switched to TLS. It would appear that the operating system / libc you use either removed or never had support for the global variable canary, so only TLS works.
Don't touch the -mstack-protector-guard option and everything should work. The default should be fine when you use -fstack-protector-all."
"Provide __stack_chk_guard with a random value in c file, avoid using regular values like all zero's or FF's because the stack can easily get these values during any memory operation. Wiki on providing magic number implementation. This __stack_chk_guard will be placed at the top and bottom of the stack, which will be checked during every stack access. Any change in the value implies a corrupted stack and returns with error providing the stack protection.
unsigned long __stack_chk_guard;
void __stack_chk_guard_setup(void)
{
__stack_chk_guard = 0xBAAAAAAD;//provide some magic numbers
}
void __stack_chk_fail(void)
{
/* Error message */
}// will be called when guard variable is corrupted "
"There are two ways to remove this error: 1. From the compiler option disable(comment out) the "stack guard".
Define __stack_chk_guard in you c file.
When you define __stack_chk_guard make sure you provide random value to it. For providing random value you need to pass as an argument to the random function.
For any further detail you can refer to the compiler manual."
"For those that get this error in bare metal software development with a custom linker script, make sure to pass the option -nostdlib option:
gcc -nostdlib
since Ubuntu 16.04 for example enables the stack protection by default on the compiler. man gcc says:
NOTE: In Ubuntu 14.10 and later versions, -fstack-protector-strong is enabled by default for C, C++, ObjC, ObjC++, if none of -fno-stack-protector, -nostdlib, nor -ffreestanding are found.
-fno-stack-protector also solved it for me, but you should likely tell your poor compiler that you are doing baremetal stuff to prevent other such problems.
I'm guessing this is because the feature relies on symbols which are normally defined if a linker script is not given? But TODO I found no mention of those symbols by dumping the default linker script with:
aarch64-linux-gnu-gcc -Wl,-verbose main.c
so I'm not sure.
I grepped GCC 6.4.0 source code and it suggests that the symbol comes from libgcc2.c at gcc/doc/tm.texi:
The default version of this hook creates a variable called @samp{__stack_chk_guard}, which is normally defined in @file{libgcc2.c}."
Click to expand...
Click to collapse
source: https://stackoverflow.com/questions/27290086/gcc-canaries-undefined-reference-to-stack-chk-guard
i cant wait to use this and your other project (sailfishos)!
wizzer48 said:
i cant wait to use this and your other project (sailfishos)!
Click to expand...
Click to collapse
Yes even I can't wait for both as there is no latest development for our tab !!!
Arc android said:
Yes even I can't wait for both as there is no latest development for our tab !!!
Click to expand...
Click to collapse
Halium doesnt seem to work i tried but to no avail
Mithil17 said:
Halium doesnt seem to work i tried but to no avail
Click to expand...
Click to collapse
Its OK at least you tried to build it !!
Hey I have a great idea Mithil17, can you try to build MIUI 7 for galaxy tab 2? There was an attempt to build it earlier but it wasn't successful.
Arc android said:
Hey I have a great idea Mithil17, can you try to build MIUI 7 for galaxy tab 2? There was an attempt to build it earlier but it wasn't successful.
Click to expand...
Click to collapse
MIUI ??? Why do you wanna china bloadware sooo badly?? what's wrong with LOS or any other bloadware free ROMs?
Plus it's gonna be laggy as h3ll... done and forgotten.
drnightshadow said:
MIUI ??? Why do you wanna china bloadware sooo badly?? what's wrong with LOS or any other bloadware free ROMs?
Plus it's gonna be laggy as h3ll... done and forgotten.
Click to expand...
Click to collapse
Yeah I know it's Chinese but it looks beautiful. You'll know it if you have tried mini 5 for tab 2.
Arc android said:
Yeah I know it's Chinese but it looks beautiful. You'll know it if you have tried mini 5 for tab 2.haha
Click to expand...
Click to collapse
Haha, no thank you! I'm happy with LOS and RR ROMS. I own redmi note 5 pro but never used MIUI [email protected], I unlocked bootloader and installed LOS asap. I like to have privacy in my hand and I hate when OS wanna rape my privacy. My privacy isn't on sale.
drnightshadow said:
Haha, no thank you! I'm happy with LOS and RR ROMS. I own redmi note 5 pro but never used MIUI [email protected], I unlocked bootloader and installed LOS asap. I like to have privacy in my hand and I hate when OS wanna rape my privacy. My privacy isn't on sale.
Click to expand...
Click to collapse
If you actually want this much privacy, here's something for you : https://androidfilehost.com/?fid=17248734326145705104
An unofficial /e/os build for your device. Just trying to help you in case you didn't know this. That's all !
Arc android said:
If you actually want this much privacy, here's something for you : https://androidfilehost.com/?fid=17248734326145705104
An unofficial /e/os build for your device. Just trying to help you in case you didn't know this. That's all !
Click to expand...
Click to collapse
whyred = Redmi Note 5. Not SGT2
Are you sure? It can brick device
levider said:
whyred = Redmi Note 5. Not SGT2Are you sure? It can brick device
Click to expand...
Click to collapse
Note 5/pro = whyred that's what Google says.
Also in the above link, it is made for redmi note 5 pro
Official /e/ forum link : https://www.google.com/url?sa=t&sou...FjACegQIBBAC&usg=AOvVaw1iyAyl2Ur__Xid-tw1cRCz
I hope I am not doing anything wrong
Arc android said:
Note 5/pro = whyred that's what Google says.
Also in the above link, it is made for redmi note 5 pro
Click to expand...
Click to collapse
Dude, this is not Redmi Note 5 thread.
Update: It boots now, Sources are in https://github.com/Halium/projectmanagement/issues/238 no ui still
Mithil17 said:
Update: It boots now, Sources are in https://github.com/Halium/projectmanagement/issues/238 no ui still
Click to expand...
Click to collapse
So we can install it now ???? !!!!!
Arc android said:
So we can install it now ???? !!!!!
Click to expand...
Click to collapse
Well you can just install it, it just boots, no ui/display
Mithil17 said:
Well you can just install it, it just boots, no ui/display
Click to expand...
Click to collapse
So it means even if I install it, it can't be operated. Why some things are way too difficult for tab 2 ?? I mean miui7, sfos, treble, Oreo and now haloum are ported to other devices too that are mostly similar to ours but running them on tab 2 is a bit more difficult.
Related
Hello I'm trying to compile cyanogenmod 7 with subskyper tass device to try to mantain this project update in line with the original philosophy: keep it 100% cyanogenmod without any tweaks
When I compile I face two errors that broke my compilation:
1-
device/samsung/tass/overlay/frameworks/base/core/res/res/values/config.xml:95: error: Resource at swap_volume_keys_orientation appears in overlay but not in the base package; use <add-resource> to add.
make: *** [out/target/common/obj/APPS/framework-res_intermediates/package-export.apk] Errore 1
make: *** Eliminazione del file "out/target/common/obj/APPS/framework-res_intermediates/package-export.apk"
make: *** Attesa per i processi non terminati....
This one I commented out the line reguarding swap_volume_keys_orientation in file
device/samsung/tass/overlay/frameworks/base/core/res/res/values/config.xml
but when i continue...
2-
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/tass/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates/AndroidRuntime.o: in function android::gRegJNI:AndroidRuntime.cpp(.data.rel.ro+0x148): error: undefined reference to 'register_android_hardware_fm_fmradio(_JNIEnv*)'
collect2: ld returned 1 exit status
make: *** [out/target/product/tass/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates/LINKED/libandroid_runtime.so] Errore 1
make: *** Attesa per i processi non terminati..
Someone faced same problems?
Any ideas?
thanks a lot
Send PM With The Error To Subpsyke
t-r-e said:
Send PM With The Error To Subpsyke
Click to expand...
Click to collapse
done. I hope he will answer me cause I'm able to sync repos in a couple of hours, so it will be easy to mantain pure cyanogenmod 7 for our sgm.
mebitek said:
done. I hope he will answer me cause I'm able to sync repos in a couple of hours, so it will be easy to mantain pure cyanogenmod 7 for our sgm.
Click to expand...
Click to collapse
Best Luck Buddy Don't Give Up Early , We Look Forward To See Your Work As We Need To Keep Subpsyke Project Alive
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld:
Click to expand...
Click to collapse
Are you using 32-bit linux system ?
If yes, then I guess 64-bit is necessary to get things compiled properly without errors.
NB: Just sharing info.
coolsandie said:
Are you using 32-bit linux system ?
If yes, then I guess 64-bit is necessary to get things compiled properly without errors.
NB: Just sharing info.
Click to expand...
Click to collapse
Thanks for the reply but I think that this kind of error is a missing reference for the function register_android_hardware_fm_fmradio that is called from AndroidRuntime.cpp
32 or 64 bit it is no differnce in compile result. just speed....
However I've checked tass configuration and I see that fm radio is set to BCM2049 chip.
I checkd into frameworks/base/core/jni/ cm source tree directory and I found only fm hardware reference for :
bcm4325
si4708
si4709
wl1271
now I'm trying to compile again setting radio to bcm4325 just to see if something appens...
P.S. should be nice to have some tecnical ideas about the code error not only if the host system is well configured
P.P.S. changed values to bcm4325 let me not face errors no more. Now I'm compiling!!!!
I have checked some github projects and I see that a lot of device as sgm with bcm2049 fm chipset set it to bcm4325. I see that just subskype change that value to bcm2049. Should be nice to have some tip and tricks from him to understand well the point of the situation
Now I have a signed zip to flash into my sgm.
It contains subskype cm7.2 tass device configuration and latest cm 7.2 sources update at 31-01-2012.
to check changes:
http://review.cyanogenmod.com/#q,status:open,n,z
It works!!! finally compiled and booting successfully.
Now I'm trying to study the best way to mantain this kind of project (it's first time for me in android dev and I just have an android device by november).
first at all I was thinking to add V6 supercharge by default. what do you think?
mebitek said:
It works!!! finally compiled and booting successfully.
Now I'm trying to study the best way to mantain this kind of project (it's first time for me in android dev and I just have an android device by november).
first at all I was thinking to add V6 supercharge by default. what do you think?
Click to expand...
Click to collapse
Great news. Glückwunsch (don't know the english word at the moment).
Supercharger would be possibly good. Subpsyke said something to it but i don't rember clearly.
Keep up your work.
Sent from my GT-S5570 using xda premium
mebitek said:
It works!!! finally compiled and booting successfully.
Now I'm trying to study the best way to mantain this kind of project (it's first time for me in android dev and I just have an android device by november).
first at all I was thinking to add V6 supercharge by default. what do you think?
Click to expand...
Click to collapse
No not add anything. It s better. Completely clean
Inviato dal mio GT-S5570 usando Tapatalk
mebitek said:
Thanks for the reply but I think that this kind of error is a missing reference for the function register_android_hardware_fm_fmradio that is called from AndroidRuntime.cpp
32 or 64 bit it is no differnce in compile result. just speed....
However I've checked tass configuration and I see that fm radio is set to BCM2049 chip.
I checkd into frameworks/base/core/jni/ cm source tree directory and I found only fm hardware reference for :
bcm4325
si4708
si4709
wl1271
now I'm trying to compile again setting radio to bcm4325 just to see if something appens...
P.S. should be nice to have some tecnical ideas about the code error not only if the host system is well configured
P.P.S. changed values to bcm4325 let me not face errors no more. Now I'm compiling!!!!
I have checked some github projects and I see that a lot of device as sgm with bcm2049 fm chipset set it to bcm4325. I see that just subskype change that value to bcm2049. Should be nice to have some tip and tricks from him to understand well the point of the situation
Click to expand...
Click to collapse
For the radio, I used my patch to add support for the bcm2xxx devices with proper seeking. It's on gerrit here: http://review.cyanogenmod.com/#change,10358
mebitek said:
It works!!! finally compiled and booting successfully.
Now I'm trying to study the best way to mantain this kind of project (it's first time for me in android dev and I just have an android device by november).
first at all I was thinking to add V6 supercharge by default. what do you think?
Click to expand...
Click to collapse
no no...no v6.
Just vanilla cm7...and thanks for the initiative and ABT!
dont add scripts..but maybe something from cm gerrit if u wish..but then it'll not be vanilla.
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.
Hello there, it's time to get this rolling somewhere.
This is a Development-Thread. Please don't post if you aren't a developer.
What this IS
This is a Development thread, a platform for developers to discuss the development of CyanogenMod for the G925F. It's made so that we can get this working, fix up the problems - because there will be severe ones - and achieve a working official Rom at some point.
At the moment it's @OldDroid and me with help, but it would be awesome if interested devs would join in so that we can make this a team effort.
In short, it's a Dev-Thread in a dev section.
Right now it doesn't work and I'm not sure that it will work.
What this IS NOT
This is NOT a working Rom. Not even close. I can only link you to the kernel repo and soon to device and vendor, as they are almost completed for a first try.
And yes, there is no download link for the Rom. Because there isn't anything you could download yet.
This is also NOT intended as a Q&A thread. Please don't ask if your variant will be supported, I will respond by trolling. Firstand only priority is to get this running, then we'll talk about variants.
And ETA is an evil word with no meaning here. I work slowly, deal with it
Where are we currently?
Much further than a day ago
Thanks to @OldDroid, we've teamed up
All the links you want (minus the download link :angel
device: (soon, almost complete)
https://gitlab.com/mythos234/device_samsung_zeroltexx
vendor:
https://gitlab.com/mythos234/vendor_samsung_zerolte
kernel:
https://gitlab.com/mythos234/zerolte-kernel-CM
Once available, buggy alpha builds will be posted here
///
vendor and device will soon be pushed to my github
Reserved
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
vendor is setup
OldDroid said:
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
Click to expand...
Click to collapse
Welcome aboard then
vendor is finally setup and good to go!
https://github.com/mythos234/vendor_samsung_zerolte
It's apparently not without some minor casualties, but we got it. Huge thanks to @RaymanFX, he's helping me, since I'm not that much into CM building yet and I'm also basing this project on his CM for the N910C, which's 5433 is darn similar to our 7420, so we got a pretty good base to begin with.
add me as participant to the repos ^^
https://github.com/OldDroid
OldDroid said:
add me as participant to the repos ^^
https://github.com/OldDroid
Click to expand...
Click to collapse
Done for all the 3 of them
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
mythos234 said:
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
Click to expand...
Click to collapse
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
nasko_spasko said:
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
Click to expand...
Click to collapse
I'm currently building the Rom with completely removed Bluetooth support
First Build is compiled and ready for a test.. But I can't install the zip. This would be hillarious if it wasn't so annoying
mythos234 said:
Besides I said it can't be installed Hard to test something you can't even install
Click to expand...
Click to collapse
I think that there was a mistake in the partition sizes.. /system was declared as 4.1GB, but it's only 3.6GB. Recompiling with a new value, should be able to flash it then
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Aircondition said:
Good luck develop without documentation for exynos chipset.
Click to expand...
Click to collapse
The lack of drivers makes this a fun exercise almost Where's be the challenge if everything was easy...?
Aircondition said:
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Click to expand...
Click to collapse
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
mythos234 said:
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
Click to expand...
Click to collapse
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
lch920619x said:
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
As a base to know how to do it, obviously we can't just use drivers for a different chipset
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
mythos234 said:
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
Click to expand...
Click to collapse
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
-Mr. X- said:
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
Click to expand...
Click to collapse
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
mythos234 said:
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
Click to expand...
Click to collapse
I would personally flash an Engineering boot loader while doing this, to ensure version checking is not the issue.
https://github.com/ShqipLewis/Xiaomi_Kernel_OpenSource/tree/andromeda-p-oss
https://github.com/ShqipLewis/device_xiaomi_andromeda
https://github.com/ShqipLewis/vendor_xiaomi_andromeda
https://github.com/Inkypen79/device_xiaomi_andromeda
If anyone wants to build a custom rom possibly lineage i have found the trees hopefully this does help, lineage is the easiest so yeah
Current lead Dev is @Inkypen, if anyone else has any idea or wants to contribute here is the group chat
https://t.me/mimix3_5G
How I can help with this?
ZigmaInvader said:
How I can help with this?
Click to expand...
Click to collapse
honestly edit the respitory because so far they dont work i have made few files but keep in mind i literally borrowed them all from the perseus device tree since our device is pretty much identical apart from battery, if you do wanna make changes please know what your doing because i have no clue lol , and hopefully we can get this to boot ONLY edit files in the lineage path because the other paths need to be untouched okay thank you
Quantumkk123 said:
honestly edit the respitory because so far they dont work i have made few files but keep in mind i literally borrowed them all from the perseus device tree since our device is pretty much identical apart from battery, if you do wanna make changes please know what your doing because i have no clue lol , and hopefully we can get this to boot ONLY edit files in the lineage path because the other paths need to be untouched okay thank you
Click to expand...
Click to collapse
there also another difference is processor
Sorry guys I can't lie I think it's a complete mess I will be building a device tree for this device I just need A LOT of time and then I will try building some ROMs for this device reason why it will take so long is because I am learning myself and this will be the first time I am doing it hope it goes successfully for me
Hi guys! I've being making ROMs for the original Mi Mix and decided to take the plunge and get a Mix 3 5G. I've built up these skeleton trees and made LineageOS, but I haven't received my new device yet so I can't test it. It's horribly unoptimised and still has a lot of bloat from unnecessary drivers (hence the 1gb size) and I have no idea if this will even boot but here is the initial build if anyone is brave enough to install it. https://drive.google.com/open?id=1WOsXzgpdA8qTP6QWHi1gNW131dqgdDIC
This is an engineering build to help track down bugs so ADB debugging is enabled as standard. Any logs would be appreciated.
Inkypen said:
Hi guys! I've being making ROMs for the original Mi Mix and decided to take the plunge and get a Mix 3 5G. I've built up these skeleton trees and made LineageOS, but I haven't received my new device yet so I can't test it. It's horribly unoptimised and still has a lot of bloat from unnecessary drivers (hence the 1gb size) and I have no idea if this will even boot but here is the initial build if anyone is brave enough to install it. https://drive.google.com/open?id=1WOsXzgpdA8qTP6QWHi1gNW131dqgdDIC
This is an engineering build to help track down bugs so ADB debugging is enabled as standard. Any logs would be appreciated.
Click to expand...
Click to collapse
Ok I will try it aha can you send me these please because it will save me time from building another lineage device tree lol, my email is [email protected] please accept as I have ubuntu running on my pc now and I will try to fix a few things if that's okay?
Quantumkk123 said:
Ok I will try it aha can you send me these please because it will save me time from building another lineage device tree lol, my email is [email protected] please accept as I have ubuntu running on my pc now and I will try to fix a few things if that's okay?
Click to expand...
Click to collapse
I didn't realise that I didn't have link sharing on, should be ok to download now. I haven't uploaded my tree to GitHub yet, but once I do it will be available at https://github.com/Inkypen79/device_xiaomi_andromeda
Inkypen said:
I didn't realise that I didn't have link sharing on, should be ok to download now. I haven't uploaded my tree to GitHub yet, but once I do it will be available at https://github.com/Inkypen79/device_xiaomi_andromeda
Click to expand...
Click to collapse
Oh aha that's fine man , didn't realise this was android 10 good job man
Quantumkk123 said:
Oh aha that's fine man , didn't realise this was android 10 good job man
Click to expand...
Click to collapse
Don't get too excited yet lol. This LineageOS build is pie, once I know that's stable then I can move to ten. I brought up the original Mi Mix to ten so I have an idea of what's required.
Inkypen said:
Don't get too excited yet lol. This LineageOS build is pie, once I know that's stable then I can move to ten. I brought up the original Mi Mix to ten so I have an idea of what's required.
Click to expand...
Click to collapse
Lmao I realized when it said 16.0 aha that's fine tho still a lot more progress than me
I keep getting this error when trying to flash...the suggestion was to update twrp but 3.3.1-0 is the only one we have available ....
E: String resource 'zip_compatible_err' not found.
Using default value
Zip Treble compatibility error!
Invalid zip file format!
Any suggestions?
i think its my fault lemme just factory reset my phone install stock and see what happens. Yep our twrp is broken as after install it bricks whole device , and I know this isn't from the ROM because basically twrp bricked my phone from reloading to fastboot, it's very broken , but no one has been able to test that out because there hasn't been much to flash recently. Therefore @Inkypen will build some twrps for me to try and flash and see if his builds do work , fingers crossed they will
Quantumkk123 said:
i think its my fault lemme just factory reset my phone install stock and see what happens. Yep our twrp is broken as after install it bricks whole device , and I know this isn't from the ROM because basically twrp bricked my phone from reloading to fastboot, it's very broken , but no one has been able to test that out because there hasn't been much to flash recently. Therefore @Inkypen will build some twrps for me to try and flash and see if his builds do work , fingers crossed they will
Click to expand...
Click to collapse
Seems interesting. I have got mi mix 3 5g, just waiting on unlocking and will sure help it
ptlsajan said:
Seems interesting. I have got mi mix 3 5g, just waiting on unlocking and will sure help it
Click to expand...
Click to collapse
Sure there's a group chat where more info is posted there...updates etc https://t.me/mimix3_5G
I also have a mi mix 3 5g on the way, will be happy to test once i get it, thx alot for you work!
So far I have built a working version of Orange Fox recovery. Still waiting for my device to arrive, then some real work can start
https://www.androidfilehost.com/?fid=4349826312261670861
I should be getting my Mix 3 5G this week, the parcel is allegedly with my local post office already. I'd love to help out to get LineageOS working on it. I have minimum experience having flashed custom ROMs onto my current phone (Mi Max helium) as well as that of my Mrs (Mi 6 sagit), but I'd love to get more involved if possible. I don't need it to be my daily driver immediately, so I just need enough confidence in what we'll be doing here so as not to turn it into an expensive, cute brick The chassis being ceramic, it's already half way there right off the bat, but let's not get any closer please
Please generate LineageOS android 10 from Mi Mix Andromeda
ZigmaInvader said:
Please generate LineageOS android 10 from Mi Mix Andromeda
Click to expand...
Click to collapse
Join the telegram chat if you want any requests
It finally happened the source code is released
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/spes-r-oss
Leaving this also as a place for first discussions. So, go for it.
NeoPreacher said:
It finally happened the source code is released
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/spes-r-oss
Leaving this also as a place for first discussions. So, go for it.
Click to expand...
Click to collapse
Finally!!!
Let's gooooooooooo!!!!!!!!!
It only took them a year and three months to release it.
Oh god...
NeoSDAP said:
It only took them a year and three months to release it.
Oh god...
Click to expand...
Click to collapse
lmao
Snapdragon_Mid_2020.SPF.1.0.1R_r00024.0
lol it makes even more sad.
Does the Kernel being for Android 11 mean its useless for us? Can Android 12/13 roms not be made with it? I really just wanted working doubletap2wake, would the Android 11 Kernel make that happen? Thank you!
Zylam Marex said:
Does the Kernel being for Android 11 mean its useless for us? Can Android 12/13 roms not be made with it? I really just wanted working doubletap2wake, would the Android 11 Kernel make that happen? Thank you!
Click to expand...
Click to collapse
No; sure; works already flawless in PA, but sure why not. There are others problems eg. missing drivers in source and missing devs in group. Fyi: many people using a13 custom rom with a11 stock kernel actually on rn11
nice. they can now close 1k issues regarding spes kernel. hahaha
pulsar said:
nice. they can now close 1k issues regarding spes kernel. hahaha
Click to expand...
Click to collapse
There are some people fixing the issues with source already!
NeoPreacher said:
No; sure; works already flawless in PA, but sure why not. There are others problems eg. missing drivers in source and missing devs in group. Fyi: many people using a13 custom rom with a11 stock kernel actually on rn11
Click to expand...
Click to collapse
Oh wow really, tape2wake works great in PA? I have tried almost all roms but PA. Thank you for letting me know, a shame the Kernel is missing drivers and such. I wonder why Xiaomi is trying to make sure the Note 11 is never developed for, it's such a good phone with a custom rom.
BerserkSlayer said:
There are some people fixing the issues with source already!
Click to expand...
Click to collapse
Haha I think Pulsar was referring to Xiaomi's github page where there would be like 10 posts a day asking for Spes kernel
tap2wake also works on PixelExperience, FWIW.
EDIT: board_id.h is present in the same directory, not in include/. \
I've tried compiling the kernel from Xiaomi's sources and stumbled across an error about a missing header file:
Code:
drivers/misc/st21nfc.c:43:22: fatal error: board_id.h: No such file or directory
#include <board_id.h>
^
compilation terminated.
make[2]: *** [scripts/Makefile.build:338: drivers/misc/st21nfc.o] Error 1
make[1]: *** [scripts/Makefile.build:642: drivers/misc] Error 2
This file board_id.h does not exist in the include/ folder. Perhaps Xiaomi uploaded incomplete sources?
aureljared said:
tap2wake also works on PixelExperience, FWIW.
EDIT: board_id.h is present in the same directory, not in include/. \
I've tried compiling the kernel from Xiaomi's sources and stumbled across an error about a missing header file:
Code:
drivers/misc/st21nfc.c:43:22: fatal error: board_id.h: No such file or directory
#include <board_id.h>
^
compilation terminated.
make[2]: *** [scripts/Makefile.build:338: drivers/misc/st21nfc.o] Error 1
make[1]: *** [scripts/Makefile.build:642: drivers/misc] Error 2
This file board_id.h does not exist in the include/ folder. Perhaps Xiaomi uploaded incomplete sources?
Click to expand...
Click to collapse
yes
Much easier to compile this kernel using Clang rather than GCC. Still getting used to it, it's been a good while since my last kernel compile, haha.
Does anyone know how to build a new boot image by hand? I have a working boot.img for PixelExperience and I'd like to replace the kernel with one that I built for testing, but I'm not sure if I should still use mkbootimg like with older Android devices as this is the first time I'll be dealing with a device that uses dtb/dtbo files. Any insights would be welcome.
aureljared said:
EDIT: board_id.h is present in the same directory, not in include/.
Click to expand...
Click to collapse
Not an expert here. What exactly are the benefits of this? What does it mean for custom ROM development?
SAM209 said:
Not an expert here. What exactly are the benefits of this? What does it mean for custom ROM development?
Click to expand...
Click to collapse
For one, it is theoretically easier to keep the device up to date without having to wait for Xiaomi's updates. Some changes that come with Android's monthly security patches are made to the kernel, for example, and having the kernel source code means we can apply those patches faster than if we were to wait for updated kernel builds from Xiaomi.
Some ROMs like LineageOS also require kernels to be built from source (i.e., not prebuilt) for a device to be granted official status.
Hello,
Can someone guide me on how to install that kernel on redmi note 11 (Pixel Experience custom os)
Already installed twrp 3.7.0 but gives me some errors all the time like Invalid zip file format!.
I download it as zip from github and put it in twrp folder and install it from there.
Thanks in advance
jasmin811 said:
Hello,
Can someone guide me on how to install that kernel on redmi note 11 (Pixel Experience custom os)
Already installed twrp 3.7.0 but gives me some errors all the time like Invalid zip file format!.
I download it as zip from github and put it in twrp folder and install it from there.
Thanks in advance
Click to expand...
Click to collapse
There's nothing to flash here. Only the link to the kernel source. There's still some work to do for a flashable kernel (compiling eg). Also there are drivers missing in the source it seems. What you tried was flashing the uncompiled kernel source package i guess and that.. doesn't work
Oh ok,I though it was finished already.