Database Develop

[ROM][P6800][OnHold]Ubuntu-touch dev preview(18.03.2013)

I have put this project on hold for now. I flashed latest Austrian ICS build to my device and continue using it as my Kindle reader on my travels. IF somone manages to fix the two issues with kernel, send me a message and I'll continue working with the repository. But for now I'm not thinking nor touching the subject before Easter. Thank you for participating for now
I've started porting Ubuntu-touch dev-preview to the Galaxy Tab 7.7 (3g). If you do not understand it already, you flash this at your own risk. There is now also a Ubuntu-touch specific device page here: https://wiki.ubuntu.com/Touch/Devices/p6800. I'll try to keep this thread and the Ubuntu devices page as close to each other as possible.
Big thanks to Daniel_hk for helping with boot.img Now It can be booted, but the screen is still black
Also, without working wifi and display, the preview is basically unusable... Next steps should be these:
1. Get wifi drivers working.
2. Get display drivers working.
Code:
[email protected]:/# uname -a
Linux localhost 3.0.15-CM-g1dc3074 #2 SMP PREEMPT Wed Mar 13 00:43:37 EET 2013 armv7l armv7l armv7l GNU/Linux
Repositories:
Latest release tagged with: "v0.3", not tested!
https://github.com/dun1982/android_device_samsung_p6800
https://github.com/dun1982/android_kernel_samsung_p6800
Download
cm-10.1-20130312-UNOFFICIAL-p6800.zip
Daily Ubuntu image: http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/
Installation
Install CWM 6.0.2.8
Wipe data/factory reset
Wipe cache partition
Flash cm-10.1-20130312-UNOFFICIAL-p6800.zip to device
Flash quantal-preinstalled-phablet-armhf.zip to device
Reboot
Starting to use
Then it gets interesting (Black sreen for now now Run the following commands in your desktop system:
Code:
adb root
adb shell
ubuntu_chroot shell
You should have now root access inside your tabled. Continue with this wiki next
What works
Ubuntu-touch dev-preview is flashable.
It boots!
Known Issues
Kernel is based to the CyanogenMod/android_kernel_samsung_smdk4210, but it is a mess. So forked it, took code here and there (mostly from locerra's JB build).
Kernel is based 3.0.15 and no newer one available (yet).
Most of the drivers in kernel had to be turned off, because build was not succeeding...
bluetooth: Doesn't work
audio: Dock audio doesn't work.
hwcomposer: HDMI dongle doesn't work.
wifi: Doesn't work.
camera: Doesn't work.
.. and lot of kernel level bugs for sure.
Displaydrivers are not working (yet).
Release notes
Version 0.2 (13.03.2013) - Now it boots, see release notes
Version 0.1 (07.03.2013) - Intial release, nothing works
Credits
BIG THANKS to daniel_hk for solving the boot.img problem for me.
Anyone who has worked previously with the device/kernel source.
locerra (for getting CM10.1 to flashable state).

wowww!!! thank you !test now:victory::victory:

Placeholder for future.

Re: [ROM][P6800]Ubuntu-touch dev preview(02.03.2013)
Not 6810 versión?
AUs

el_campi said:
Not 6810 versión?
AUs
Click to expand...
Click to collapse
I cannot test it for anything else. The kernel sources are from CM10.1 that was in use from locerra, so in theory it should work with i815 and with p6810 as well. But I cannot give you any guarantees...
And also before I get this build to even start with my device, I do not think that sharing image would help anyone. But if you are a developer, I would like to talk with you on issues that I might have missed or done wrong. So contact me

Re: [ROM][P6800]Ubuntu-touch dev preview(02.03.2013)
any update?
Sent from my GT-P6800 using xda premium

Not much. The generated image is missing /data/ubuntu completely and that is the reason why the image does not boot. I got also flu and fewer, so I have had not that much time after the weekend to look on the issues on that.
I'm also waiting if I get any answers from Ubuntu touch emailing list regarding the problem and where to look for answers, but my quess is that it has something to do with the devices fstab file...

Good news everyone!
Just got a very good answer the problem I had with the /data/ubuntu-folder missing from the image. There was no image provided for the actual Ubuntu at all by the build-process...
When I get home from work, I'll try to find time to look into the build process if I can include the actual Ubuntu image to the ready made image and then release it after I get my device to boot. But it seems that I got the right nudge forward for this now :highfive:

Hmpf, still not booting. Now the /data/ubuntu logs are unmodified, which would point towards kernel or fstab-issue (ie. /data/ubuntu is never used...).

Re: [ROM][P6800]Ubuntu-touch dev preview(02.03.2013)
Good job :thumbup::thumbup::thumbup::thumbup::thumbup::thumbup:
Sent from my GT-p6800 using xda premium

Doh... still not working... Any ideas anyone?

Ok, new version build from different repositories (thx, danile_hk for tip).
I'll test the new image this evening when I get back to home, and I have my fingers crossed that I can get the device to boot up and even display something useful. After that I can start looking for ubuntu developemnt

New version did not work, but then Daniel_hk gave me working boot.img. So now I need to find out what the heck is wrong with my repository and fix it so that I can get working boot.img from start and also the device configuration has issues. Both repositories are currently out of sync I'm afraid

dun1982 said:
New version did not work, but then Daniel_hk gave me working boot.img. So now I need to find out what the heck is wrong with my repository and fix it so that I can get working boot.img from start and also the device configuration has issues. Both repositories are currently out of sync I'm afraid
Click to expand...
Click to collapse
Also, without working wifi and display, the preview is basically unusable... Next steps should be these:
1. Get wifi drivers working.
2. Get display drivers working.

It seems that I hit the wall (again) with the mentioned big issues.
For now, I keep some sabbatical from Ubuntu Touch things (ie. I flashed ICS Austria to my device) and use it as my Kindle reader again.
If by miracle I get more info regarding how to get the Kernel working with Ubuntu Touch, then by allmeans I continue working with this project. So far it just seems that making a working image, is out of my hands currently.

At least you had a go. Thanks for your efforts, and hope you might have another crack at it later on.
I'm feeling a little bit that way right now too, and put my ICS kernel on the back burner. I think I'm trying to multitask a little too much at times....
Yep, a break is what you need, maybe some clarity will come after you've had a chance to recharge.
Sent from my GT-I9300 using xda premium

It's very nice to see you took up the big responsibility to make this superb device to be usable again! it has great specs, really. KUDOS bro!!

Any update on this development?

ZhenMing said:
Any update on this development?
Click to expand...
Click to collapse
Not much, I have had no interest to spend time with this topic because I have been very busy IRL. After I get my new house renovated fully and get my job tasks done, I wont be spending much time with this project. Feel free to use any sources provided in this thread to further advance the subject.
But this wont go forward that much, if the GT-P6800 wont get official CM10.1 update...

It works?

[REQ]Dump of the preinstalled rom

People are already recieving their units.
Every other wear prior to this one so far has had roms made directly by goog, I dont expect this is any different.
TheManii said:
Android wear runs, well android.
I would like to request that someone that has a wear to dump the rom that is preinstalled on it, and to make note if there it prompts for an ota on first setup.
I don't know how to enable adb on it, but I would expect that it would be available, for the moment merely doing a
Code:
adb pull /system
will be as much as anyone can expect.
In the event it actually supports fastboot, I'd also like to request a
Code:
fastboot get-var all
Click to expand...
Click to collapse
Here's a guide on enabling adb on wear, it's not specific to any one device:
[How-To] Android Wear: Enable Debugging, Take Screenshots, Unlock The Bootloader, And Root The LG G Watch
You won't be able to root it however for the time being, you need a custom recovery specifically for your device.
I don't know if there's an OTA out yet or not, but I would not be surprised if there is/will be one soon.
Please make note of if you got an ota if you upload a dump.

TheManii said:
People are already recieving their units.
Every other wear prior to this one so far has had roms made directly by goog, I dont expect this is any different.
Here's a guide on enabling adb on wear, it's not specific to any one device:
[How-To] Android Wear: Enable Debugging, Take Screenshots, Unlock The Bootloader, And Root The LG G Watch
You won't be able to root it however for the time being, you need a custom recovery specifically for your device.
I don't know if there's an OTA out yet or not, but I would not be surprised if there is/will be one soon.
Please make note of if you got an ota if you upload a dump.
Click to expand...
Click to collapse
Hi ill try and do this later this evening when i get home. I have a lot of meeting so wont be until later so if someone is going to beat me to it go for it!

when i want to pull the system..
command line is giving error: more than one device and emulator..i have managed to link the watch to localhost:4444

doki81 said:
when i want to pull the system..
command line is giving error: more than one device and emulator..i have managed to link the watch to localhost:4444
Click to expand...
Click to collapse
U trying to adb over blue tooth?
im dumping the system now. give me some time to upload
Sent from my GT-I9505 using XDA Premium 4 mobile app
---------- Post added at 06:50 PM ---------- Previous post was at 06:36 PM ----------
system dump
W110_4.4W.2_System_Dump.zip - 206.78 MB

Hawke84 said:
system dump
W110_4.4W.2_System_Dump.zip - 206.78 MB
Click to expand...
Click to collapse
Thanks, did you have any otas before getting this? I assume there is one but I need confirmation.
Also, what is the bootloader version? Most reliable way is to check in fastboot mode.

TheManii said:
Thanks, did you have any otas before getting this? I assume there is one but I need confirmation.
Also, what is the bootloader version? Most reliable way is to check in fastboot mode.
Click to expand...
Click to collapse
yeah had 1 OTA

Hawke84 said:
yeah had 1 OTA
Click to expand...
Click to collapse
Could you check the bootloader version and kernel version?
The kernel version can be found with:
Code:
adb shell cat /proc/version

TheManii said:
Could you check the bootloader version and kernel version?
The kernel version can be found with:
Code:
adb shell cat /proc/version
Click to expand...
Click to collapse
Linux version 3.10.0-g7326b80 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Thu Oct 9 17:43:04 PDT 2014
---------- Post added at 07:19 PM ---------- Previous post was at 07:15 PM ----------
Hawke84 said:
Linux version 3.10.0-g7326b80 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Thu Oct 9 17:43:04 PDT 2014
Click to expand...
Click to collapse
Is it same kernel as original g watch? I'm wondering if we can use the same root exploit
Sent from my GT-I9505 using XDA Premium 4 mobile app

No they're not the same kernel:
android / kernel/msm / android-msm-dory-3.10-kitkat-wear
android / kernel/msm / android-msm-lenok-3.10-kitkat-wear
lenok's kernel is currently newer then sprat's.
I cant tell you what you can do with the differences, I assume it's a matter of waiting for a custom recovery to be ported.
How long ago have you updated your gwar? If it was very recent, could you do an "adb bugreport" and post that?
If it's recent enough it may still have the ota details inside.

TheManii said:
No they're not the same kernel:
android / kernel/msm / android-msm-dory-3.10-kitkat-wear
android / kernel/msm / android-msm-lenok-3.10-kitkat-wear
lenok's kernel is currently newer then sprat's.
I cant tell you what you can do with the differences, I assume it's a matter of waiting for a custom recovery to be ported.
How long ago have you updated your gwar? If it was very recent, could you do an "adb bugreport" and post that?
If it's recent enough it may still have the ota details inside.
Click to expand...
Click to collapse
i was about a week ago, havent read the log yet
http://d-h.st/0hq

Hawke84 said:
i was about a week ago, havent read the log yet
Click to expand...
Click to collapse
Thanks for uploading it, but it's been too long and it's not in there.

Also: android / kernel/msm / android-msm-dory-3.10-kitkat-wear
I had the wrong repo, dory is the gwa and lenok is the gwar.
Sprat is the gear live, the same conclusion is drawn however: lenok is still newer then dory as far as kernels go.

TheManii said:
Also: android / kernel/msm / android-msm-dory-3.10-kitkat-wear
I had the wrong repo, dory is the gwa and lenok is the gwar.
Sprat is the gear live, the same conclusion is drawn however: lenok is still newer then dory as far as kernels go.
Click to expand...
Click to collapse
as far as i can tell (and im not a dev) the toolkit to root the original g watch uses an insecure custom kernel to allow for root access so we need a kernel dev or something good with compiling from source to build for g watch r

Request 4.4W.1 Rom
would be great if someone could manage to pull the original rom the LGWR comes with
the update to 4.4W.2 introduces a nasty bug that no longer updates the time every minute in ambient mode
(someone still running 4.4W.1 and able to confirm the bug isn't there?)
I learned about this too late and immediately updated my watch on arrival

I still need a dump of KIW52H if anyone still has an unupdated gwar

Cool, dev talk. Well here is my progress. I used the pulled boot.img someone posted here amd I made it insecure and I compiled the insecure boot.img. i am calling it a night but will work on it more this week when I have more time. Although it looks promising.
I also have looked at the oroginal lg g watch tweaks made and think i know how to boost the vibration setting on our device.

[Q] Strange Error Compiling Note 5 Kernel - PLEASE HELP!

Hi All,
I have been building permissive kernels for my own use for a while now, but the Note 5 kernel (both the "C" and "I" versions from Samsung open Source) is giving me fits. As you can see from my terminal output, I get through the creation of the image, the modules build fine, but when the firmware install makefile starts, I get an error I've never seen before, even if I have made no changes at all to the source code:
Code:
OBJCOPY arch/arm64/boot/Image
GZIP arch/arm64/boot/Image.gz
Building modules, stage 2.
MODPOST 2 modules
CC net/ipv4/tcp_htcp.mod.o
LD [M] net/ipv4/tcp_htcp.ko
CC net/ipv4/tcp_westwood.mod.o
LD [M] net/ipv4/tcp_westwood.ko
[B]/home/parallels/ANDROID/KERNEL/920c_kernel/scripts/Makefile.fwinst:45: target `/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule[/B].
I have looked at the cited section code, but don't see anything obvious. I have also google searched for this error way too thoroughly and PM'd some who have successfully compiled this kernel, but alas...
I am running Ubuntu 14.04 via Parallels on a Macbook Pro running Yosemite. As noted above, I am compiling from the Samsung OpenvSource files for The 920I and have also tried the 920C version, as well. As for toolchains, I have tried the Android NDK aarch64 4.9 toolchain, linaro aarch64 4.9 and linaro aarch64 5.2, all to no avail. I have tried make clean, make mrproper, deleted .ccache, etc., as well as using/not using -jX.
Here is a link to a repo with the untouched source code: https://github.com/sk806/N5_Kernel.git
ANY HELP IS GREATLY APPRECIATED!!!
Thanks!
Steve

sk806 said:
Hi All,
I have been building permissive kernels for my own use for a while now, but the Note 5 kernel (both the "C" and "I" versions from Samsung open Source) is giving me fits. As you can see from my terminal output, I get through the creation of the image, the modules build fine, but when the firmware install makefile starts, I get an error I've never seen before, even if I have made no changes at all to the source code:
Code:
OBJCOPY arch/arm64/boot/Image
GZIP arch/arm64/boot/Image.gz
Building modules, stage 2.
MODPOST 2 modules
CC net/ipv4/tcp_htcp.mod.o
LD [M] net/ipv4/tcp_htcp.ko
CC net/ipv4/tcp_westwood.mod.o
LD [M] net/ipv4/tcp_westwood.ko
[B]/home/parallels/ANDROID/KERNEL/920c_kernel/scripts/Makefile.fwinst:45: target `/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule[/B].
I have looked at the cited section code, but don't see anything obvious. I have also google searched for this error way too thoroughly and PM'd some who have successfully compiled this kernel, but alas...
I am running Ubuntu 14.04 via Parallels on a Macbook Pro running Yosemite. As noted above, I am compiling from the Samsung OpenvSource files for The 920I and have also tried the 920C version, as well. As for toolchains, I have tried the Android NDK aarch64 4.9 toolchain, linaro aarch64 4.9 and linaro aarch64 5.2, all to no avail. I have tried make clean, make mrproper, deleted .ccache, etc., as well as using/not using -jX.
Here is a link to a repo with the untouched source code: https://github.com/sk806/N5_Kernel.git
ANY HELP IS GREATLY APPRECIATED!!!
Thanks!
Steve
Click to expand...
Click to collapse
That is Samsung for ya. Maybe @g.lewarne could provide some insight

mikeyinid said:
That is Samsung for ya. Maybe @g.lewarne could provide some insight
Click to expand...
Click to collapse
I hope so! Thanks.
It's weird, as i've gotten the same error on both a virtual box and parallels setup. I am going to try boot camping it and then I'm done, unless someone knows what is going on.

sk806 said:
I hope so! Thanks.
It's weird, as i've gotten the same error on both a virtual box and parallels setup. I am going to try boot camping it and then I'm done, unless someone knows what is going on.
Click to expand...
Click to collapse
Have you resolved this issue? I am running into it too trying to compile S6 Kernel for 5.1.1

elesbb said:
Have you resolved this issue? I am running into it too trying to compile S6 Kernel for 5.1.1
Click to expand...
Click to collapse
I haven't. I can get every kernel to compile for my current devices, except this one. Strange.

sk806 said:
I haven't. I can get every kernel to compile for my current devices, except this one. Strange.
Click to expand...
Click to collapse
It is related to modules compiling from what I can gather. If I use Ktoonsez source, I don't get that error. However, I notice it doesn't compile any modules. I still get an Image in my boot directory. Do you? I think the kernel itself is safe to use. You could probably ignore this error.

You guys just need to read what the error exactly refers to and then search for it in your source.
Would have brought you to. ....
https://github.com/UpInTheAir/SM-N920/commit/ad77e0333fbdccf5e0e1485e5a65ae47a062b235
Easy

UpInTheAir said:
You guys just need to read what the error exactly refers to and then search for it in your source.
Would have brought you to. ....
https://github.com/UpInTheAir/SM-N920/commit/ad77e0333fbdccf5e0e1485e5a65ae47a062b235
Easy
Click to expand...
Click to collapse
I don't have anything like that in my makefile.fwinst file. Here is what is at line 45, which is where terminal is telling me the error is at:
$(installed-fw): $(INSTALL_FW_PATH)/%: $(obj)/% | $(INSTALL_FW_PATH)/$$(dir %)
$(call cmd,install)
Here is the actual terminal error message:
/home/seth/S6-Kernel_Parent/Extracted_S6_Source/Kernel.tar/scripts/Makefile.fwinst:45: target `/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule.
So I'm confused.
EDIT: Nevermind I'm an idiot. I found it. Thank you so much!! Finally solved

UpInTheAir said:
You guys just need to read what the error exactly refers to and then search for it in your source.
Would have brought you to. ....
https://github.com/UpInTheAir/SM-N920/commit/ad77e0333fbdccf5e0e1485e5a65ae47a062b235
Easy
Click to expand...
Click to collapse
HA! I googled the error a million times and never saw your repo! I wasn't sure if removing "stm_z1.fw tsp_stm" from the makefile would screw anything up, but apparently it doesn't. Many thanks, sir!
It's odd that others have built with the same sources (920C, mainly, from what I have seen), and have not changed that section of the makefile, but still succeeded in their build. I wonder what it is about my setup that caused this error. Anyway, not an issue now. Thanks again.
Steve

sk806 said:
HA! I googled the error a million times and never saw your repo! I wasn't sure if removing "stm_z1.fw tsp_stm" from the makefile would screw anything up, but apparently it doesn't. Many thanks, sir!
It's odd that others have built with the same sources (920C, mainly, from what I have seen), and have not changed that section of the makefile, but still succeeded in their build. I wonder what it is about my setup that caused this error. Anyway, not an issue now. Thanks again.
Steve
Click to expand...
Click to collapse
There are others I've seen using my commit (no credit) and didn't cherry-pick keeping the history. I believe the Image still flashes with or without though

I am having the same issue can you explain what was the issue ?

UpInTheAir said:
You guys just need to read what the error exactly refers to and then search for it in your source.
Would have brought you to. ....
https://github.com/UpInTheAir/SM-N920/commit/ad77e0333fbdccf5e0e1485e5a65ae47a062b235
Easy
Click to expand...
Click to collapse
I have the same problem as OP with my S6. This link would help me but it is broken. Can you please provide some info about the commit or another link or whatever?

elesbb said:
I don't have anything like that in my makefile.fwinst file. Here is what is at line 45, which is where terminal is telling me the error is at:
$(installed-fw): $(INSTALL_FW_PATH)/%: $(obj)/% | $(INSTALL_FW_PATH)/$$(dir %)
$(call cmd,install)
Here is the actual terminal error message:
/home/seth/S6-Kernel_Parent/Extracted_S6_Source/Kernel.tar/scripts/Makefile.fwinst:45: target `/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule.
So I'm confused.
EDIT: Nevermind I'm an idiot. I found it. Thank you so much!! Finally solved
Click to expand...
Click to collapse
Can you tell me what you did? I have the same error and i cant fix it ????

minealex2244 said:
I have the same problem as OP with my S6. This link would help me but it is broken. Can you please provide some info about the commit or another link or whatever?
Click to expand...
Click to collapse
Did you figure it out?

EncryptedCurse said:
Did you figure it out?
Click to expand...
Click to collapse
Uhm somehow. I used a script which ignored that error as your kernel image is already built and you shouldn't care about modules. But if you still want a fix then see my commit: https://github.com/minealex2244/AldeXus/commit/e89301766b3d251b285649a38ee4dea4f2871b99
This commit shows you what to remove (it may be the perfect fix or just an example of what you should do in your code).
Tell me if it helped.

Broken link
Hey, I'm having the same issue but I can't find your commit, could you please fix the link?. Thanks in advance.

[KERNELS]Permissive_MM - 815/710/715/810 so far

This is for all the Permissive S2 Marshmallow kernels. Further builds of kernels will go in their own threads.
Make sure to thank @ashyx and @jafangie if you use their kernels.
Permissive_Marshmallow_S2_Kernels​
This will work on the 815/710/715/810 MM. So far
You flash this at your own risk. We are not responsible for anything that happens!!! There's the discaimer. ​
Install instructions:
You MUST HAVE ROOT and TWRP installed to flash this!!
This is for Marshmallow only
Flash kernel then wipe cache and dalvic
Reboot and profit!!
Changelog
815 Permissive Kernel - Stock with init.d support
710 Permissive Kernel - Stock with init.d support
715 Permissive Kernel - Stock with init.d support
810 Permissive Kernel - Stock with init.d support
______________________________
Downloads:
815_Permissive_initd_Kernel engine95
710_Permissive_initd_Kernel engine95
715_Permissive_initd_Kernel jafangie Thank here
810_Permissive_initd_Kernel engine95
XDA:DevDB Information
[KERNELS]Permissive_MM - 815/710/715/810 so far, Kernel for the Samsung Galaxy Tab S2
Contributors
engine95, ashyx, jafangie
Source Code: https://github.com/engine95/exynos5433-MM-NNKernel.git
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2016-05-08
Created 2016-05-08
Last Updated 2016-05-26

extra info
In a rooted explorer, you will need to delete /system/app/SecurityLogAgent. Or you will get a nagging warning.

I think whenever I reboot to recovery the permissive will be gone
Is it possible ?
I see the red line says "recovery is not seandroid enforcing" and apps that needs permissive won't work any more
But about shows permissive
weird ha ?
So I flashed kernel again and apps work ok.

papampi said:
I think whenever I reboot to recovery the permissive will be gone
Is it possible ?
I see the red line says "recovery is not seandroid enforcing" and apps that needs permissive won't work any more
But about shows permissive
weird ha ?
So I flashed kernel again and apps work ok.
Click to expand...
Click to collapse
The latest TWRP has fixed that warning. For recovery.
As for the kernel, it will show "Kernel is not seandroid". That's just wording and doesn't affect anything.
Why you would lose permissive can't happen. But your root could be broken if you flashed 2.65 and higher. Some apps still look for root in /system. So check and see if your app still has root. I'm betting that's the cause of it.
Edit. SU will say you have root. But if you actually use root for the app, it'll say no root. Estrong file explorer is a prime example.
Sent from my LGLS990 using XDA-Developers mobile app

engine95 said:
The latest TWRP has fixed that warning. For recovery.
As for the kernel, it will show "Kernel is not seandroid". That's just wording and doesn't affect anything.
Why you would lose permissive can't happen. But your root could be broken if you flashed 2.65 and higher. Some apps still look for root in /system. So check and see if your app still has root. I'm betting that's the cause of it.
Edit. SU will say you have root. But if you actually use root for the app, it'll say no root. Estrong file explorer is a prime example.
Click to expand...
Click to collapse
Dang so the issue I have had with es was broken root all this time I didn't know, I don't have that issue now but, that would have been nice to know a while ago...lol.

Josephigloe said:
Dang so the issue I have had with es was broken root all this time I didn't know, I don't have that issue now but, that would have been nice to know a while ago...lol.
Click to expand...
Click to collapse
The maker of the app needs to stop using hard-coded paths for root detection.
Most have corrected this. If you have an app that doesn't I urge you to contact the author or use a different app.
As said the Seandroid warning is nothing but a flag and wont affect anything in any way.

engine95 said:
The latest TWRP has fixed that warning. For recovery.
As for the kernel, it will show "Kernel is not seandroid". That's just wording and doesn't affect anything.
Why you would lose permissive can't happen. But your root could be broken if you flashed 2.65 and higher. Some apps still look for root in /system. So check and see if your app still has root. I'm betting that's the cause of it.
Edit. SU will say you have root. But if you actually use root for the app, it'll say no root. Estrong file explorer is a prime example.
Sent from my LGLS990 using XDA-Developers mobile app
Click to expand...
Click to collapse
@Engine95, Hi my friend!
You're so lucky, take a look here http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=t710 .
Concerning T715 I asked for sources to Samsung last Saturday... They just reply to me that they are now in the process of reviewing my inquiry.
Jaf

jafangie said:
@Engine95, Hi my friend!
You're so lucky, take a look here http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=t710 .
Concerning T715 I asked for sources to Samsung last Saturday... They just reply to me that they are now in the process of reviewing my inquiry.
Jaf
Click to expand...
Click to collapse
The 815 source came out in 2 days after I requested it. I was in shock.
I requested 710 a week ago, so you made good time.
I have a feeling 710 source will be tied with the 810. So the 810 MM will probably need to release before I get source.
At least you got it and can move forward now. [emoji3]
Major edit: My bad. I just assumed. Wow
Maybe I should request your source. I'm on a roll. Maybe I should bet it all on black. Lol
Edit #2: Too funny. I just now got the notification from Samsung.
Sent from my LGLS990 using XDA-Developers mobile app

To the 815 users of this kernel. I have 2 questions.
1. Is wifi dropping on reboot? Meaning do you have to sign in each time you reboot? If you do, let me know so I can fix it. I'm taking things one step at a time because I don't know how Marshmallow runs yet.
2. Do you have the nagging security notice? If so, you need to delete /system/app/SecurityLogAgent, in a rooted explorer.
710 users, I have a permissive kernel about done. It was built using 815 source. So I'm gonna need this kernel flogged to death to make sure all is right. I just used the 710 MM defconfig.
Edit: This is in the OP now also. 710-MM-Permissive-Kernel

@engine95
will not let me download from link above or in OP -error on android filehost for 710-MM-Permissive -Kernel unexpected response from server?

rumrunner4000 said:
@engine95
will not let me download from link above or in OP -error on android filehost for 710-MM-Permissive -Kernel unexpected response from server?
Click to expand...
Click to collapse
Try a different server. I just dl'd from the Georgia one and it worked fine.
Sent from my LGLS990 using XDA-Developers mobile app

Update download available now.

@engine95, please create kernel for T810:
http://www.sammobile.com/firmwares/download/71178/T810XXU2CPD9_T810DBT2CPD9_DBT/
Model SM-T810
Model name Galaxy Tab S2
Country Germany
Version Android 6.0.1
Changelist 7767647
Build date Mon, 25 Apr 2016 11:01:57 +0000
Product code DBT
PDA T810XXU2CPD9
CSC T810DBT2CPD9

kutaxov said:
@engine95, please create kernel for T810:
http://www.sammobile.com/firmwares/download/71178/T810XXU2CPD9_T810DBT2CPD9_DBT/
ModelSM-T810
Model nameGalaxy Tab S2
CountryGermany
VersionAndroid 6.0.1
Changelist7767647
Build dateMon, 25 Apr 2016 11:01:57 +0000
Product codeDBT
PDAT810XXU2CPD9
CSCT810DBT2CPD9
Click to expand...
Click to collapse
I need to request source. Then wait til Samsung will release it.
But ya, you'll get one.
Sent from my LGLS990 using XDA-Developers mobile app

rumrunner4000 said:
@engine95
will not let me download from link above or in OP -error on android filehost for 710-MM-Permissive -Kernel unexpected response from server?
Click to expand...
Click to collapse
Worked for me.

engine95 said:
I need to request source. Then wait til Samsung will release it.
Click to expand...
Click to collapse
Hi engine95,
I am stil trying to build from T815_MM my T715_MM!
But I have one issue.
What I do :
1) Update Cross-Compiler
$ git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8
2) Edit the base kernel Makefile to set up my cross compiler.
3) Build the kernel
$ export CROSS_COMPILE=/home/ja/android/arm-eabi-4.8/bin/arm-eabi-
$ export ARCH=arm
$ make exynos5433-gts28lte_defconfig
$ make ARCH=arm -j5
No eror, I have my Zimage
4) Make the new image
$ umkbootimg boot.img
$ mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --output boot.img
My boot.img doesn't boot at all... I try your T815_MM it boots and bootloop (I think it is normal way )
What I am missing, is there one step more on MM?
Any idea? It was exactly what I did for T715_LL and everything is going well!
In advance thank a lot.

jafangie said:
Hi engine95,
I am stil trying to build from T815_MM my T715_MM!
But I have one issue.
What I do :
1) Update Cross-Compiler
$ git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8
2) Edit the base kernel Makefile to set up my cross compiler.
3) Build the kernel
$ export CROSS_COMPILE=/home/ja/android/arm-eabi-4.8/bin/arm-eabi-
$ export ARCH=arm
$ make exynos5433-gts28lte_defconfig
$ make ARCH=arm -j5
No eror, I have my Zimage
4) Make the new image
$ umkbootimg boot.img
$ mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --output boot.img
My boot.img doesn't boot at all... I try your T815_MM it boots and bootloop (I think it is normal way )
What I am missing, is there one step more on MM?
Any idea? It was exactly what I did for T715_LL and everything is going well!
In advance thank a lot.
Click to expand...
Click to collapse
It could be a few things. And I'm guessing you're building a "Permissive" kernel.
Just in case, my git is here. https://github.com/engine95/exynos5433-MM-NNKernel.git It uses 815 source.
I didn't see that you did: "make menuconfig" when building your zimage.
Edit: Just save it. You don't need to make any changes there.
As for the ramdisk, use it from the 715 MM kernel.
In "default.prop" add this line. "ro.securestorage.support=false".
Above "# BOOTIMAGE_BUILD_PROPERTIES" I think we have to have this in now, not just for WIFI" I think I needed this to get it to boot. But I'm not positive.
Another problem could be the "defconfig". I tried "L" and it didn't work. I needed to wait for source so I could get it for "M". But this could have been my problem when I first built. Trying to figure things out.
SU might be another issue. I think I used a clean boot.img from the .tar. Don't root it.
Thing is, my ROM has SU built in /system, instead of systemless root. So I'm not sure what that's going to do to you.
When I build 710 or 810 using same source, the zImage does build differently. So they aren’t interchangeable. That was probably the bootloop when you tried that with 815 on 715.
Let me know how it goes. We'll get it figured out.

Please, T810 ?

cedric3 said:
Please, T810 ?
Click to expand...
Click to collapse
Request Opensource Samsung for T810 6.0.1 kernel source, more demand will mean faster source code, which results in a permissive kernel (root )

cedric3 said:
Please, T810 ?
Click to expand...
Click to collapse
I'm cleaning a huge mess I had, from when MM first popped up. I had files scattered across 7 OS's. Testing some different Linux distro's for myself.
Besides that, I've been trying to get a ROM figured out. I either get an unmountable system, or I break wifi and ext SD. 710 isn't a problem because I have that.
Samsung still hasn't posted source for the MM 810. I was waiting for it so I can pull the 810 defconfig.
I'll get you one shortly.
Edit: I've requested 810 source already. Almost a week ago.
Funny, but I'm having an easier time building kernels than Roms now that MM is out.
Sent from my LGLS990 using XDA-Developers mobile app

Question Any dev working on TWRP?

If not, anyone can make a bount?

matheus_sc said:
If not, anyone can make a bount?
Click to expand...
Click to collapse
Surely they are already working on it. But it just takes some time. At the moment everything is working optimally despite fastboot. Even root is possible.

pittrich said:
Surely they are already working on it. But it just takes some time. At the moment everything is working optimally despite fastboot. Even root is possible.
Click to expand...
Click to collapse
I know i use xiaomi eu already. Only update is pain to ass

wait for it

Rumour has it some chinese dev is working on it

Any news?

matheus_sc said:
Any news?
Click to expand...
Click to collapse
Still no sign.... Orangefox also quiet...
The guy who made lots of xiaomi TWRP recoveries stopped developing.

... are kernel (or device/vendor) repos released for it?
This would help.
Do we have TWRP and/or released kernel sources from other Qualcom 888 based devices out there?

raupe said:
... are kernel (or device/vendor) repos released for it?
This would help.
Do we have TWRP and/or released kernel sources from other Qualcom 888 based devices out there?
Click to expand...
Click to collapse
This?
Xiaomi Mi 11 kernel source code is out, the device is codenamed "venus" - Gizmochina
Yesterday, Xiaomi announced Mi 11 as the world’s first smartphone powered by Qualcomm Snapdragon 888. The handset already went for pre-order soon after the launch and is set to go on sale for the first time on January 1. Ahead of its sale, the company has even released this device’s kernel...
www.gizmochina.com

I read on Xiaomi.eu somewhere that there are issues with how the partitions are made and TWRP is very difficult to make for this. They said it's gonna take either a very long time before a recovery is made, or maybe not even at all.

Danacy said:
I read on Xiaomi.eu somewhere that there are issues with how the partitions are made and TWRP is very difficult to make for this. They said it's gonna take either a very long time before a recovery is made, or maybe not even at all.
Click to expand...
Click to collapse
Yeah they changed everything over to GKI 1.0 and no one seems to be supporting it, although they found somewhere on a Chinese site a recovery that works (TWRP) if you boot it (don't flash it) and unencrypts the data. It's in the XDA forums now.

[TWRP] [venus] TWRP Recovery for Mi 11
REMOVED! Use this instead : https://forum.xda-developers.com/t/recovery-11-official-teamwin-recovery-project.4374109/
forum.xda-developers.com

mslezak said:
[TWRP] [venus] TWRP Recovery for Mi 11
REMOVED! Use this instead : https://forum.xda-developers.com/t/recovery-11-official-teamwin-recovery-project.4374109/
forum.xda-developers.com
Click to expand...
Click to collapse

*justintime* said:
Still no sign.... Orangefox also quiet...
The guy who made lots of xiaomi TWRP recoveries stopped developing.
Click to expand...
Click to collapse
Yeah Mauronofrio is out, too much work for no return. He was pretty much the last standing open-source TWRP dev out there for tons of devices. The ones from China never get source released... Which would mean that someone would have to pickup the TWRP project and re-engineer it to fit the new GKI 1.0 then 2.0 platforms that run off that ACK. That's a lot of work. I'm talking about keeping the TWRP project open-source. It would very nice if Google stepped in since they are experts on the new format, but no such luck.

mslezak said:
Yeah they changed everything over to GKI 1.0 and no one seems to be supporting it, although they found somewhere on a Chinese site a recovery that works (TWRP) if you boot it (don't flash it) and unencrypts the data. It's in the XDA forums now.
Click to expand...
Click to collapse
Interesting, that would explain also the lack of custom ROMs? But I read that the source code is released, even before the device was launched. Isn't there GKI-support to be found in there?

Danacy said:
Interesting, that would explain also the lack of custom ROMs? But I read that the source code is released, even before the device was launched. Isn't there GKI-support to be found in there?
Click to expand...
Click to collapse
Yes they released source there are just no instructions anywhere on how to build the kernel #1 and the GKI modules #2 and combine into a build.

The new Xiaomi.eu weekly includes TWRP for Venus (Mi11) as well as Star (Mi 11 Lite 5G, Mi 11 Pro, Mi 11 Ultra, MIX FOLD) (it's a bootable TWRP, but persists after installation). Seems last week's has added Alioth (Mi 10S, Redmi K40). So I would expect a TWRP for Haydn to show up soon in the weekly Xiaomi.eu releases. Seems they forgot the haydn doesn't have TWRP yet so you can't actually install it! Tried the updater app no go, it can't boot to recovery because they don't have one yet, even though on Xiaomi.eu they say it's available, can't find it anywhere.
BTW the only TWRPs I can actually find are for Venus and Star.
haydn TWRP is not working: https://androidfilehost.com/?fid=14943124697586336730 remember: fastboot boot twrp-3.5.1-haydn.img ... although I tried everything, this TWRP just doesn't work - you boot right into the system after the fastboot boot step. Tried everything I can think of, always boots to system. Guess it's still a waiting game...

mslezak said:
Yes they released source there are just no instructions anywhere on how to build the kernel #1 and the GKI modules #2 and combine into a build.
Click to expand...
Click to collapse
Just one more question since this has been bothering me; what would be needed from Xiaomi? Instructions on how to build the kernel? Have they ever done this before about something like this? Like, is it a reasonable thing to ask them to release instructions? I know some people working there, I could forward the request.

Well I've run this by many many devs.
The issue with the GKI 1.0 and ACK is that you must download the entire AOSP build environment and make sure it works with the separate ACK (Android Common Kernel) and then properly loads the GKI modules from a separate build step. Together they make 1 kernel. This ACK per Linux Version and across vendors should be AOSP and identical. Therefore, a single build should work across all Linux 5.4 based kernels.
But... most devs are just skipping AOSP and inlining the GKI modules so they can have 1 build step. Not exactly what Google intended, but way less storage, and you can use Clang or GCC or whatever you want.
I think what OEMs are posting is merely the entire combined source code, no 2 step build process. Only a single file for the QGKI config portion. Which won't build your GKI modules as it comes. A build script for this (Q)GKI portion would be extremely beneficial.
If any OEM walks through the build steps 1) how to create only the QGKI modules and 2) how to assemble them into 1 kernel with the ACK, that would be great for devs. It just hasn't happened. So we get hacked kernels for the 888 running Linux 5.4.
The Generic Kernel Image (GKI) project | Android Open Source Project
source.android.com

mslezak said:
Well I've run this by many many devs.
The issue with the GKI 1.0 and ACK is that you must download the entire AOSP build environment and make sure it works with the separate ACK (Android Common Kernel) and then properly loads the GKI modules from a separate build step. Together they make 1 kernel. This ACK per Linux Version and across vendors should be AOSP and identical. Therefore, a single build should work across all Linux 5.4 based kernels.
But... most devs are just skipping AOSP and inlining the GKI modules so they can have 1 build step. Not exactly what Google intended, but way less storage, and you can use Clang or GCC or whatever you want.
I think what OEMs are posting is merely the entire combined source code, no 2 step build process. Only a single file for the QGKI config portion. Which won't build your GKI modules as it comes. A build script for this (Q)GKI portion would be extremely beneficial.
If any OEM walks through the build steps 1) how to create only the QGKI modules and 2) how to assemble them into 1 kernel with the ACK, that would be great for devs. It just hasn't happened. So we get hacked kernels for the 888 running Linux 5.4.
The Generic Kernel Image (GKI) project | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
OK, I see. Thank you for your reply. I am going to see how far I can get this. Tnx again!