Hi all,
So I heard around the internets that LoD may not be coming to the Note 10s and that it may have been canceled all together. With that said on my free time I've been poking around the decompiled apk to see how it works. I have found the checks and recompiled (also want to say there's a thread in the S8 forum that was trying the same thing and I got to the same position as them).
The kernel source shows that "CONFIG_LOD_SEC=y" so that's good
It still didn't work. Eventually, since I have an S10+ and a Note 10+, I decompiled then recompiled without modification and tried to run on my S10+ and got the error "Update your software Linux on DeX requires your device to have the latest software to support some features."
Clean Binary
... I LxD_i : getDeviceName: model: SM-G975U, device: beyond2q
... I LxD_o : isSupportedBinary: binary version: 5, required version: 4
Clean Binary with recompile
... I LxD_i : getDeviceName: model: SM-G975U, device: beyond2q
... I LxD_o : isSupportedBinary: binary version: 1, required version: 4
I believe Note 10+ has everything needed to run LoD but the code below is whats stopping it from running. If someone has a rooted Note 10(+) and can change the device name to "beyond2q" and device model to "SM-G975U" then sideload the Samsung signed apk I'm hoping it will work. If this is the case then the non-samsung signed apk is whats stopping LoD from running.
Code:
private static String a(String str) {
String str2 = c;
Log.d(str2, "getDeviceNameByDevice: " + str);
if (TextUtils.isEmpty(str)) {
return null;
}
if (str.startsWith("crown")) {
return "CROWN";
}
if (str.startsWith("gts4")) {
return "TABS4";
}
if (str.startsWith("gts5")) {
return "TABS5";
}
if (str.startsWith("star")) {
return "STAR";
}
if (str.startsWith("beyond")) {
return "BEYOND";
}
if (str.startsWith("winner")) {
return "WINNER";
}
if (str.startsWith("great")) {
return "GREAT";
}
return null;
}
Any help is appreciated.
Thanks,
BlueKalel
BlueKalel said:
Hi all,
So I heard around the internets that LoD may not be coming to the Note 10s and that it may have been canceled all together. With that said on my free time I've been poking around the decompiled apk to see how it works. I have found the checks and recompiled (also want to say there's a thread in the S8 forum that was trying the same thing and I got to the same position as them).
The kernel source shows that "CONFIG_LOD_SEC=y" so that's good
It still didn't work. Eventually, since I have an S10+ and a Note 10+, I decompiled then recompiled without modification and tried to run on my S10+ and got the error "Update your software Linux on DeX requires your device to have the latest software to support some features."
Clean Binary
... I LxD_i : getDeviceName: model: SM-G975U, device: beyond2q
... I LxD_o : isSupportedBinary: binary version: 5, required version: 4
Clean Binary with recompile
... I LxD_i : getDeviceName: model: SM-G975U, device: beyond2q
... I LxD_o : isSupportedBinary: binary version: 1, required version: 4
I believe Note 10+ has everything needed to run LoD but the code below is whats stopping it from running. If someone has a rooted Note 10(+) and can change the device name to "beyond2q" and device model to "SM-G975U" then sideload the Samsung signed apk I'm hoping it will work. If this is the case then the non-samsung signed apk is whats stopping LoD from running.
Code:
private static String a(String str) {
String str2 = c;
Log.d(str2, "getDeviceNameByDevice: " + str);
if (TextUtils.isEmpty(str)) {
return null;
}
if (str.startsWith("crown")) {
return "CROWN";
}
if (str.startsWith("gts4")) {
return "TABS4";
}
if (str.startsWith("gts5")) {
return "TABS5";
}
if (str.startsWith("star")) {
return "STAR";
}
if (str.startsWith("beyond")) {
return "BEYOND";
}
if (str.startsWith("winner")) {
return "WINNER";
}
if (str.startsWith("great")) {
return "GREAT";
}
return null;
}
Any help is appreciated.
Thanks,
BlueKalel
Click to expand...
Click to collapse
I have had a poke around on this myself, It checks for the Validation of the Apk itself, an if its not signed by Samsung then it fails to launch the environment.
I give up at this point, Couldn't locate the validation check to see if it was possible to remove it.
Might be possible for someone to edit the App after its been installed with Root privileges, But this is the first device i have not needed to root and i am unsure if i will root this one.
not sure if this helps, maybe someone cld try to debug it in vmos app?
Sent from my SM-N975F using Tapatalk
someone found a solution. install Version: 1.0.43 (104301200) from apkmirror
Sent from my SM-N975F using Tapatalk
jemfalor said:
someone found a solution. install Version: 1.0.43 (104301200) from apkmirror
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
I just tried this and the information is correct. 1.0.43 does indeed seem to operate. Well, I downloaded the Ubuntu image and then tried to use terminal mode. It doesn't work for me. But, it let me get as far as installing it.
EDIT: I tried DeX too and that also fails. It seems that the older version can set up the image but something is likely missing in the Note 10 firmware in order to fully support this. Now, that's boneheadedly stupid. The phone is basically a Note 9 with the processor and GPU from an S10, both of which are fully supported. I'm going to have to guess that our good buddies Microsoft are behind this garbage.
Collin80 said:
I just tried this and the information is correct. 1.0.43 does indeed seem to operate. Well, I downloaded the Ubuntu image and then tried to use terminal mode. It doesn't work for me. But, it let me get as far as installing it.
EDIT: I tried DeX too and that also fails. It seems that the older version can set up the image but something is likely missing in the Note 10 firmware in order to fully support this. Now, that's boneheadedly stupid. The phone is basically a Note 9 with the processor and GPU from an S10, both of which are fully supported. I'm going to have to guess that our good buddies Microsoft are behind this garbage.
Click to expand...
Click to collapse
yes. good guess. someone needs to resolve this issue
any time there's a feature problem, some capitalist is banking on it.
Sent from my SM-N975F using Tapatalk
I've looked into this version as well. The newest version crashes because of the device name on the Note 10. When we modify the apk and resign it with apksigner it becomes different than the original, obviously. There's a function in the code called SemSystemProperties that I can't find anything about, but I think it has to do with the signing of the app and the secure folder creation and what not. With the old app I was able to get all the way to creating the image but once ran it crashed. The error in logcat for the crash delt with the Device Model. I changed the model in the code and recompiled but this time I get You have to upgrade the binary message, never getting to the image stage. Again all points to the SemSystemProperties and the signing of the apk.
-Code thats an issue:
private static String d() {
Log.d(c, "getDeviceNameByDevice: ");
if (Build.DEVICE.startsWith("crown")) {
return "CROWN";
}
if (Build.DEVICE.startsWith("gts4")) {
return "TABS4";
}
if (Build.DEVICE.startsWith("star2")) {
return "STAR2";
}
if (Build.DEVICE.startsWith("beyond")) {
return "BEYOND";
}
if (Build.DEVICE.startsWith("winner")) {
return "WINNER";
}
return null;
}
and
public static int getNstVersion() {
return SemSystemProperties.getInt("linux_on_dex_version", 1);
-From the logs without modification
I LxD_g : getDeviceName: model: SM-N975U, device: d2q
E LxD_LxDUncaughtExceptionHandler: uncaughtException: classs = class com.samsung.android.lxd.processor.LxdException, uncaughtException = com.samsung.android.lxd.processor.LxdException: undefined model: SM-N975U, d2q
-From the logs after modification
I LxD_j : isSupportedBinary: binary version: 1, required version: 4
If anyone knows what SemSystemProperties is and its function I'm all ears.
Thanks,
BlueKalel
It looks to me that SemSystemProperties is a java class (exposed by the android system) that can be used to query system properties. You can see in that line "return SemSystemProperties.getInt("linux_on_dex_version", 1);" that it seems to be uses a default value of 1 if it can't read the property. So, perhaps just try changing the 1 to a 5 which is what it seems to have been looking for. Then you're effectively hard coding the value it wanted anyway and maybe it will work. But, I fear they've intentionally left out bits and pieces required. I suppose the only way to find out is to try it.
theres also an init file.. appears the version number is a simple prop value you should be able to set easily..
ps.. ill try n get it running on my n976v andvreport back.. maybe using the old version, setting the properties then using an activity manager to launch it.. maybe can bypass initial loading of the app where it errors?
couldnt post an init rc file so uploaded to gdrive.. its from my g975u.. located at /system/etc/init
https://drive.google.com/file/d/1-o6PpFBNFt-DfJro6yEGaybLXIuxgJZI/view?usp=drivesdk
The rc file is what I believe it uses in starting and stopping the container which also is protected. The only way I think this will work is if you have a rooted device and can change the device's model name. Because once you modify the apk it no longer works. Now not sure if rooting messes up the Knox stuff which if it does then I believe it will still not work. The issue comes down to signing and Knox security. It seems if the apk is signed by Samsung it allows execution of the container. If someone who is rooted will try changing its name and installing the apk it would be helpful with this hypothesis.
Thanks,
BlueKalel
Someone please keep this thread alive
Samsung just emailed me:
End of Linux on DeX Beta
Thank you for supporting Linux on DeX Beta. The development of Linux on DeX was all thanks to customer interest and valuable feedback. Unfortunately, we are announcing the end of our beta program, and will no longer provide support on future OS and device releases.
NOTE — Linux on DeX will not be supported on Android 10 Beta. Once you update your device to Android OS 10, you will not be able to perform a version rollback to Android Pie. If you decide to update your device to Android 10 Beta, we recommend backing up data before updating.
Thank you,
The Linux on DeX Team
Trying this on my note 10 today was able to install it fine
jutley said:
Trying this on my note 10 today was able to install it fine
Click to expand...
Click to collapse
u got it fully working? more info plz and some screens if u can.. wat firm are u on?
elliwigy said:
u got it fully working? more info plz and some screens if u can.. wat firm are u on?
Click to expand...
Click to collapse
sorry i couldn't mount the linux partition it just would not start
jutley said:
sorry i couldn't mount the linux partition it just would not start
Click to expand...
Click to collapse
o ok lol. same as wats already been reported then
elliwigy said:
u got it fully working? more info plz and some screens if u can.. wat firm are u on?
Click to expand...
Click to collapse
It works with this version 1.0.38. But if I press RUN button, it will start with "Please wait..." message, and black screen. Nothing to do....
I'm sure somebody can mod the app to work with Android 10 I tried it but I was not successful
Related
I hope HTC provides an update real soon:
http://www.theregister.co.uk/2009/08/14/critical_linux_bug/
I think there is very little real world danger of this being a problem for Android based phones, primarily because most applications run using the Dalvik VM and therefore do not run native code and couldn't exploit this directly. Of course, there is the possibility that an app could use the NDK to run code natively, but bear in mind this "vulnerability" has existed in versions of the Linux kernel since 2001 and hasn't been a problem thus far.
Regards,
Dave
Thx for the reply!
actually the kernel code already apply the patch as I can see:
Code:
static ssize_t sock_sendpage(struct file *file, struct page *page,
int offset, size_t size, loff_t *ppos, int more)
{
struct socket *sock;
int flags;
sock = file->private_data;
flags = !(file->f_flags & O_NONBLOCK) ? 0 : MSG_DONTWAIT;
if (more)
flags |= MSG_MORE;
return kernel_sendpage(sock, page, offset, size, flags);
}
Make sock_sendpage() use kernel_sendpage()
kernel_sendpage() does the proper default case handling for when the
socket doesn't have a native sendpage implementation.
Now, arguably this might be something that we could instead solve by
just specifying that all protocols should do it themselves at the
protocol level, but we really only care about the common protocols.
Does anybody really care about sendpage on something like Appletalk? Not
likely.
Its a problem
[QUOTE ....but bear in mind this "vulnerability" has existed in versions of the Linux kernel since 2001 and hasn't been a problem thus far.
Regards,
Dave[/QUOTE]
Hi Dave It hasn't been a problem because nobody knew about it until now.
The good news is that if it is not "fixed" in android right now, we have another way to get root on almost any android phone.
texasaggie1 said:
The good news is that if it is not "fixed" in android right now, we have another way to get root on almost any android phone.
Click to expand...
Click to collapse
haha - that's the way to THINK!!
texasaggie1 said:
The good news is that if it is not "fixed" in android right now, we have another way to get root on almost any android phone.
Click to expand...
Click to collapse
Precisely
That's exactly what I thought when I read the thread title. A kernel exploit doesn't worry me...
I think the fake OTA method will work for now though on current devices that get upgraded to 2.1.
This is an old exploit. And I hope you guys know the original kernel sources for android uses ksplice. That bug is already patched some time ago.
Ok guys, quick and sweet. Pure aosp build with insecure boot, root, busybox, and my CDMATools app. Radios are 100%. SMS/MMS send/receive win. Everything wins afaik.
Other than that have fun. Oh feel free to mirror, tweak, theme, fix, mod, do whatever. If you start a thread with it, gimme a holla.
Note: Once we get our repo right, i'll push the theme engine source. I need some more eyeballs on ActivityThread as the theme change is not applying to running processes.
Version 3 Change Log:
Tmobile Theme Engine! REQUIRES REBOOT FOR THEME TO FULLY APPLY. THAT'S JUST HOW IT IS FOR NOW!
3 way reboot menu in Global Actions
Panel Tile Mods from my buddy kevdliu
His thread is here and his git is here
Google insists December does not exist and i agree for now
Maybe next build December will exist again.
Version 2 Change Log:
Added all the "experimental" 4.2 AOSP binaries. Not sure if there's any real difference in feel.
Excluded SprintExtension.apk as it was fc'ing on boot.
Added Google Location fix credit to Craig Gomez and mmuzzy for shooting it over here.
Cleaned up build props and keep 4.1.1 fingerprint for app and service compatibility.
I think that's it. This will likely conclude my participation here. The Eos project should be up and running soon. Peace.
My personal gapps. Photosphere, swipe kbd, facelock, videochat, I can't find anything that don't work. Built from slim_gapps and misc other sources.
BRD 4.2 Gapps
VERSION 3 Theme Engine AOSP Toroplus
VERSION 2 AOSP 4.2 Toroplus
Download AOSP 4.2 toroplus
Patches and Misc.
Stock AOSP kernel
Version 2 Tether Fix (use old SecPhone)
How to fix radios for 4.2 Toroplus
Ok guys. The root of the problem is libsec-ril_lte.so. This library was compiled against either 4.1.1 or 4.1.2. Even the library on AOSP for 4.2 was compiled against 4.1.1 or 4.1.2. I found the problem when running a radio log at boot. Turns out the system library linker could not load the library as it was missing a linked symbol. That missing symbol was actually a ScreenshotClient call to SurfaceComposerClient. So I diffed the 4.2 version against the 4.1.2 version. Low and behold, one of the constructors was removed in 4.2. So, we just add the missing constructor back!
Code:
frameworks/native/libs/gui/SurfaceComposerClient.cpp
at about line 591 or so, right under the
Code:
ScreenshotClient::ScreenshotClient()
: mWidth(0), mHeight(0), mFormat(PIXEL_FORMAT_NONE) {
}
class declaration, add this method...
Code:
status_t ScreenshotClient::update() {
sp<ISurfaceComposer> s(ComposerService::getComposerService());
if (s == NULL) return NO_INIT;
mHeap = 0;
return s->captureScreen(0, &mHeap,
&mWidth, &mHeight, &mFormat, 0, 0,
0, -1UL);
}
Also, we have to declare the method in the header as well...
We move to
Code:
frameworks/native/include/gui/SurfaceComposerClient.h
At about line 166 under the class declaration
Code:
class ScreenshotClient
{
sp<IMemoryHeap> mHeap;
uint32_t mWidth;
uint32_t mHeight;
PixelFormat mFormat;
public:
ScreenshotClient();
// frees the previous screenshot and capture a new one
include the following method
Code:
status_t update();
Now run a fresh build. Your libsec-ril_lte.so will load up and your radio will light up like a Christmas Tree. I think the real question here is, "Why is a radio library require linking to the screenshot call?" I don't know, but I know that is what the problem was.
Thanks as always :good:
Great job BRD!
Sent from my Galaxy Nexus using Tapatalk 2
OK. Good job man. Giving it a whirl
Sent from my Galaxy Nexus using xda premium
YES Finally i can stop scratching my arm like pookie .......Ahhhhhh relief .....lol
I'll wait until someone reports back. So please post your results!
Sent from my Galaxy Nexus using XDA Premium HD app
Win!
I need to go try this once I get home!
flash flash flash!! data works!
edit/ only issue ive ran into is it seems gps is not working correctly. Google now says "location service is off" even though it is on. im thinking its a google now issue because maps gets a lock on location.
edit2/ my issues have been resolved with version 2. thank you.
Just double checking, included GApps or no?
Sent from my Galaxy Nexus using Tapatalk 2
Mirror
Mirror if anyone needs: http://www.multiup.org/fichiers/download/d6a7d19e86f44fbde7c4c276f582a16e_full_toroplus-ota-eng.bigrushdog.zip
Hopefully it downloads faster than it uploads.
backup up now so I can flash...Will this have the gapps included?
nacho945 said:
backup up now so I can flash...Will this have the gapps included?
Click to expand...
Click to collapse
Doesn't look like it.
THIS IS WHY I BOUGHT A NEXUS!!!
Hell to the yes!!
Already on the 3rd upgrade
jesusice said:
Doesn't look like it.
Click to expand...
Click to collapse
Where can I find a set of Gapps that should work with this rom?
nacho945 said:
Where can I find a set of Gapps that should work with this rom?
Click to expand...
Click to collapse
I haven't got a chance to flash this yet but I found these which are supposed to be for 4.2. http://d-h.st/wBX
EDIT: Icebluemale30 says they suck, go down a couple more posts and try the other link.
nacho945 said:
backup up now so I can flash...Will this have the gapps included?
Click to expand...
Click to collapse
GApps not included. Just flashed and found that out lol. Ah well.
Super Duper!!! I'll give them a shot, In the process of flashing the rom right now.
jesusice said:
I haven't got a chance to flash this yet but I found these which are supposed to be for 4.2. http://d-h.st/wBX
Click to expand...
Click to collapse
I used the ones in this link, simply because this is what the Team SyEnce build had linked to: http://d-h.st/SrU
Disclaimer: Im not responsible for any damage done to your device if you flash this kernel.
Nexus 9 5.0.1 Stock Kernel with 2Amp charging modification
http://www38.zippyshare.com/v/52487126/file.html
compiled from source. edited the current limits based on FIK kernel. thanks to USBHost.
https://github.com/USBhost/FIK/commit/62aa76b7e1c6e68abdcc723e7a2aabfd398cf9e4
I'm still trying to figure out how to change the kernel version name. But this is a working kernel. I'm using it on my device. The highest charging current i have achieved is 1.9amps and charges my N9 from 5% to 100% in 3.5 hours using an Apple Charger.
Feedback is appreciated.
heres a screenshot of 3c toolbox battery status
Will this be good for LTE model or just wifi
I'm not sure if the kernel for lte is the same. I only have the non lte nexus9
Seems to work just fine on my LTE version. Verified the data connection still comes up and works for me.
jonahmt21 said:
I'm still trying to figure out how to change the kernel version name.
Click to expand...
Click to collapse
You will need to edit your defconfig for that
make "your defconfig"
make menuconfig
select the first option
select the second option :: if I remember correctly
Then type what you want
Then exit and save
Can you make this as flashasble zip please
How flash this kernel? On fastboot or can use flashify?
I used flashify and it worked great. No need for a flashable zip.
fastboot install using the nexus root toolkit.
I should of known... If you removed encryption, install this kernel, your device will encrypt itself... Dag nab it..
USBhost said:
You will need to edit your defconfig for that
make "your defconfig"
make menuconfig
select the first option
select the second option :: if I remember correctly
Then type what you want
Then exit and save
Click to expand...
Click to collapse
Actually, isn't that easier to just open the Makefile at the kernel dir? "kernel/htc/flounder/Makefile"
Code:
VERSION = 3
PATCHLEVEL = 10
SUBLEVEL = 40
EXTRAVERSION = [COLOR=Green][I]ENTER HERE FREE SPACE[/I][/COLOR]
NAME = [COLOR=DarkRed]TOSSUG Baby Fish [COLOR=Green]<--Or just change the given name here[/COLOR][/COLOR]
The first blank space option prob better.
I know I am a million years late here but I don't know how many old old threads I've had to read to get stuff. So good deal. I'm still trying to get the Camera working on DirtyUnicorns on flounder. haha
I think I must have a problem with my setup cuz I am getting weird compile errors when I try to build the kernel, inline or not....Like the stupid -mlittle_endian crap. MAN! gcc or PATH issues? hmm
wantowan2 said:
Actually, isn't that easier to just open the Makefile at the kernel dir? "kernel/htc/flounder/Makefile"
Code:
VERSION = 3
PATCHLEVEL = 10
SUBLEVEL = 40
EXTRAVERSION = [COLOR=Green][I]ENTER HERE FREE SPACE[/I][/COLOR]
NAME = [COLOR=DarkRed]TOSSUG Baby Fish [COLOR=Green]<--Or just change the given name here[/COLOR][/COLOR]
The first blank space option prob better.
I know I am a million years late here but I don't know how many old old threads I've had to read to get stuff. So good deal. I'm still trying to get the Camera working on DirtyUnicorns on flounder. haha
I think I must have a problem with my setup cuz I am getting weird compile errors when I try to build the kernel, inline or not....Like the stupid -mlittle_endian crap. MAN! gcc or PATH issues? hmm
Click to expand...
Click to collapse
True you can use EXTRAVERSION one
but the other one NAME it wont show in the kernel version
Could someone compile a version of this kernel with encryption disabled?
siraltus said:
Could someone compile a version of this kernel with encryption disabled?
Click to expand...
Click to collapse
You just need to edit the ramdisk
No need to recompile
All links are dead
Sent from my SM-N920C using XDA-Developers mobile app
Apologize for possible OT, but I can't find an always working (and stable) SSH daemon app for the Zenfone2's Lollipop
This is what I tried, any of them PAID apps:
QuickSSHd - too old, not even starts
SSHDroid Pro - sometime starts, only first time after reboot, but only without root and higher ports (>1024)
RRooted SSH/SFTP Daemon - always refusing connections
Ssh Server Pro (olive tree) - seems promising, but very poor of binaries
The Dropbear service hanging issue seems the root of this problem
Thanks for any hint
I can't even find a proper ssh binary. I just tried sshd from an x86 cyanogen port (RAZRi, I think). Got this after loading appropriate library in lib (same as client)
1|[email protected]:/ # sshd
CANNOT LINK EXECUTABLE: could not load library "libssh.so" needed by "sshd"; caused by cannot locate symbol "EVP_ripemd160" referenced by "libssh.so"...
Good luck sir
Blades said:
I can't even find a proper ssh binary. I just tried sshd from an x86 cyanogen port (RAZRi, I think). Got this after loading appropriate library in lib (same as client)
1|[email protected]:/ # sshd
CANNOT LINK EXECUTABLE: could not load library "libssh.so" needed by "sshd"; caused by cannot locate symbol "EVP_ripemd160" referenced by "libssh.so"...
Good luck sir
Click to expand...
Click to collapse
Hi,
I followed the following guide which you can get from googling "Compiling-Dropbear-for-a-Nexus-7-tablet". Sorry, I can't post any links yet as my post counts are still below 10
The difference with the info from the website above is that we don't need to cross compile if you're compiling in a Linux x86-64 system. Just need to make a static binary.
Let me know if you have any questions and I'll try to help out.
Cheers.
wolfdude said:
The difference with the info from the website above is that we don't need to cross compile if you're compiling in a Linux x86-64 system. Just need to make a static binary.
Let me know if you have any questions and I'll try to help out.
Click to expand...
Click to collapse
Thanks for your answer.
Sorry but I can't get the exact entry-point, bypassing all the NDK / X-compiling stuff, as we're on a x86_64 architecture
Referring to the "simplified" version of your link (here: https://nerdoftheherd.com/articles/cross-compiling-dropbear-rsync-android/ ),
how should I compile the Dropbear source ?
Something like this ?
Code:
./configure \
--disable-zlib --disable-largefile --disable-loginfunc --disable-shadow --disable-utmp --disable-utmpx --disable-wtmp \
--disable-wtmpx --disable-pututline --disable-pututxline --disable-lastlog \
CFLAGS='-Os -W -Wall -fPIE' LDFLAGS='[COLOR="Red"]-static[/COLOR] -fPIE -pie'
... right before make-ing ?
Thanks for any further hint in the right direction
Hi,
I didn't refer to that site you have posted BUT that site does have a link at the bottom to the site where I followed.
From that site, what I did was :-
1) Download dropbear v58 (dropbear-2013.58.tar.bz2). I know this is older but the patch available is based on this version.
2) Download patch (dropbear-patch2) from that site.
3) Apply patch to the original dropbear (v58) source.
4) Run configure :-
./configure --disable-zlib --disable-largefile --disable-loginfunc \
--disable-shadow --disable-utmp --disable-utmpx --disable-wtmp \
--disable-wtmpx --disable-pututline --disable-pututxline --disable-lastlog
5) Run make :-
STATIC=1 MULTI=1 SCPPROGRESS=0 PROGRAMS="dropbear dropbearkey scp dbclient" make strip
6) You should end up with "dropbearmulti" which is a static binary that you can then copy over the the phone & go on from there.
There are some issues with that version of the code (v58+patch). Namely the "scp" doesn't work (but I have found the offending code in scp.c and found a workaround).
Let me know if you need more details. If I have some time, I might look at getting the latest dropbear version & working out a patch for it to get it to work on android x86.
Cheers.
wolfdude said:
Hi,
I didn't refer to that site you have posted BUT that site does have a link at the bottom to the site where I followed.
[...]
There are some issues with that version of the code (v58+patch). Namely the "scp" doesn't work (but I have found the offending code in scp.c and found a workaround).
Let me know if you need more details. If I have some time, I might look at getting the latest dropbear version & working out a patch for it to get it to work on android x86.
Cheers.
Click to expand...
Click to collapse
Yes of course. The main link you weren't able to post is:
http://blog.xulforum.org/index.php?post/2013/12/19/Compiling-Dropbear-for-a-Nexus-7-tablet
Actually that procedure seemed too complex as mostly dealing with the cross-compiling issue, which didn't apply to x86 case.
So I named the derivative one
Thanks for pointing out the static compiling is done within MAKE and not CONFIGURE phase... I'm quite newbie in those flags so I do appreciate any of your words
About issues, what about using the latest v67 for Dropbear sources ? (see here)
If the patch doesn't work for such different version, I guessed commenting out the interactive password line would be enough
I'm trying to compile it this way and - for instance - replace the binaries in one of the SSHD packages I named in the OP...
Thank you again for your time
Val3r10 said:
About issues, what about using the latest v67 for Dropbear sources ? (see here)
If the patch doesn't work for such different version, I guessed commenting out the interactive password line would be enough
I'm trying to compile it this way and - for instance - replace the binaries in one of the SSHD packages I named in the OP...
Thank you again for your time
Click to expand...
Click to collapse
Hi,
Yes, the patch for v58 does not work for v67. I think one just have to go through the patch and "adjust" it slightly for the newer v67. Hopefully there isn't much changes from v58 to v67. There may be more than just commenting out the password prompt as there are certain functions that don't work in Android as in *NIX. When I have some time, I will attempt to patch v67 meanwhile, I'm running v58 fine on my ZE550ML so no complains there.
Cheers.
Hi,
I've created a guide on compiling the latest dropbear (2015.67) :-
http://forum.xda-developers.com/zenfone2/general/compiling-dropbear-2015-67-zenfone-2-t3142222
Hope it helps.
Cheers.
wolfdude said:
I've created a guide on compiling the latest dropbear (2015.67)
Click to expand...
Click to collapse
Thanks a lot.
Do you think the same process (STATIC build, of course, not patching) could be likely used for other small binaries too ?
Val3r10 said:
Thanks a lot.
Do you think the same process (STATIC build, of course, not patching) could be likely used for other small binaries too ?
Click to expand...
Click to collapse
Of course. I've managed to compile tcpdump, iperf, gdbserver, etc... successfully and working fine on the Zenfone 2.
Cheers.
I found that "Servers Ultimate" SSH/SFTP modules work on the Zenfone2 once properly configured. Its not working 100% but its already more then most solutions out there.
I'm posting this now and hope in doing so some new input can be reached. Due to recent new and old exploits we need this, I have hardened the kernel some, from CopperheadOS, and put in place full "Harden usercopy", updated it to 3.10.108, and before I go any further in breaking the kernel i release this WIP. I refer to this post ( https://forum.xda-developers.com/showpost.php?p=80265757&postcount=50 ) for the current state of mobile calls etc.
Fastboot images:
190919: https://drive.google.com/open?id=1OAzYc_D_FHbbmIyFiSVtGLolB2EfiE40
290819: https://drive.google.com/open?id=1d8FNiFlMN6Bey6xD606pBomqBgSiZ-MO
Features:
OS Version: 8.1.0 Oreo
Kernel: Linux 3.10.108
Important informations:
You should be familiar with general installation of custom roms.
Required for installation: fastboot
This ROM needs a clean install, old /data may cause problems!
Working:
WIFI
Bluetooth
OTG-USB
NFC
These things are NOT working.
Camera; is not included due to inconsistency in the build currently. But failed to connect to the camera last time it did.
GSM; this will require reworking some android code, making some progress i think.
Code:
Abort message: 'CANNOT LINK EXECUTABLE "/system/bin/netmgrd": cannot locate symbol "_ZN6google8protobuf8internal20RepeatedPtrFieldBase4SwapEPS2_" referenced by "/system/vendor/lib64/libcneapiclient.so"...'
FM-Radio (not included)
GPS
Bugs:
Installing apps freeze the phone for a while.
Basically, this release needs help.
Source:
https://github.com/threader/local_manifests
https://github.com/threader/kernel
https://github.com/threader/android_device_sony_sumire
https://github.com/threader/android_device_sony_kitakami-common
Patch for external/protobuf attached to this thread.
Modified libcneapiclient.so attached.
Credits:
Everyone involved with the Sony-msm8994 project ( https://github.com/sony-msm8994/android_device_sony_kitakami-common/commits/lineage-15.1 )
Mr. Open devices "jerpelea", for actually answering some of my stupid questions I should have realized myself.
Berni-0815 for trying to do this for the z5c and leaving useful resources.
And everyone posting and following the Guide to port to Lineage-16.0 thread by algui91 (https://forum.xda-developers.com/xperia-z5/general/guide-to-port-to-lineage-16-0-t3931428) and willing to participate, this is a community effort after all.
Please don't quote this thread, I will edit it as I release new builds and make progress.
I was unsuccessful in building a flashable zip image first time I tried some moons ago, I don't know if this was due to the need of a TWRP update or just my half arsed attempt, I would appreciate if someone could direct me to correctly doing so.
Cheers
How can i help including the fact that i am nearly noob in Linux / Unix and havent built any custom ROM at the moment?
DP
threader said:
BuzzerHead.
Click to expand...
Click to collapse
let me think on that, but there are two things that's needed, a libcneapiclient.so that is msm8996 perhaps and for Android 8.x, maybe we can decompile and figure out the differences. And a Qualcomm trust zone from from maybe 8996 to hack and plug the holes. I'm still reading up.on this though but if you Google "chipsec Qualcomm trust zone" or indeed just the first results for " Qualcomm trust zone" you certainly see the problem ( https://blog.quarkslab.com/introduction-to-trusted-execution-environment-arms-trustzone.html , https://www.blackhat.com/docs/us-14/materials/us-14-Rosenberg-Reflections-on-Trusting-TrustZone.pdf )
I'm re-working the external/protobuf modifications just now as I think that is why the bug i listes occurred.
Edit:
Right, great, after unhacking the hacks and returning the protobuf API to its original state I'm stuck an error before the quite impossible error i had earlier, so this is not going as quickly as i thought, either.
Code:
Abort message: 'CANNOT LINK EXECUTABLE "/system/bin/netmgrd": cannot locate symbol "_ZN6google8protobuf2io17CodedOutputStream13WriteVarint32Ej" referenced by "/system/vendor/lib64/libcneapiclient.so"..
This is a clearly defined symbol already but perhaps not behaving as intended and an error my previous attempt somehow worked around.
The following might be the reason it hangs during package install though;
Code:
09-16 18:46:55.875 865 956 W SchedPolicy: add_tid_to_cgroup failed to write '1947' (Permission denied); fd=3
09-16 18:46:38.393 865 1126 W NativeCrashListener: Couldn't find ProcessRecord for pid 2958
Any news?
Is this project dead? Seeing a newer version of LOS on this device would be nice.
Sent from my SM-T580 using XDA Labs
TALUAtXDA said:
Is this project dead? Seeing a newer version of LOS on this device would be nice.
Sent from my SM-T580 using XDA Labs
Click to expand...
Click to collapse
It's resting... My life up ended and screwed my peace and tranquility, I simply have not had the time to look at it, I'm having a look now as long as the peace lasts.
I see there is a 10.0 now, with some collaboration maybe we can get this all working, I argued a lot with the vendor libs, i just need to get a grip on what's going on there with the other project. As far as i can tell quickly looking at it I can merge some of those changes to the unified kernel 3.10.108 I'm using and see how things go, It will take a some time to get going again. As far as the kernel goes I ought get it up to 3.12, there are some pagetable ioslation patches that are required for safe operation etc, but I paused kernel work until i could get Android in shape, then life happened....