THIS is a thread for discussion about the Samsung Galaxy Core Plus or Samsung Galaxy Trend 3 (but only the ones with Qualcomm chipsets). All Questions like "Is there a [Insert any Software Name here] for this phone?" or "I did ... and now my phone doesn't boot!" go HERE.
I created this thread to avoid users creating new threads for any new question, which just clutters up our forum.
Thanks!
Just a conclusion I wrote about the "original" SM-G350, the Qualcomm versions of the SM-G350 and Qualcomm Secure Boot (QSB):
TimSchumi said:
The original SM-G350 (also called "Samsung Galaxy Core Plus") already has CM11, CM12.1 (unreleased), CM13 (public WIP) and multiple TWRP versions.
And the Qualcomm version of the SM-G350 (also called "Samsung Galaxy Core Plus" when it's a Dual SIM Phone or "Samsung Galaxy Trend 3" when it's a Single SIM Phone (correct me if I'm wrong)) does not have the ability to run Custom ROMs or Custom Recoveries (due to QSB)
But I will explain further below:
The original G350 (I have one) has a completely different board and chipset, so using the QCom ROM on it won't work in any case. We tried it the other way round, so someone tried to boot the "original" CM11 on the Qualcomm Version. And it did not boot. So I offered to TRY to make the ROM running on the other Phones although I don't own any of the Qualcomm Versions. At that point no one knew that the phones do have completely different chipsets. It makes developing extremely hard when you don't have the phone the ROM should run on.
I know that it is hard to go along with Samsung's Stock ROM,and I do feel really sorry that I can't help, but there is no known way to bypass Qualcomm Secure Boot on those phones.
Someone theorized that QSB could be bypassed by a special crafted boot.img because of a software design flaw (namely loading the boot.img before the signature is checked, but then aborting due to the missing signature) so that QSB is overwritten at every boot before it can check the signature.
But it's even harder to do this WITHOUT the phone.
TL,DR; I guess there is no way to install anything Custom on this phone until someone with this phone sits down and investigates the problem
EDIT: Here is a PDF file on how the mechanism could be bypassed. Feel free to try to craft a boot.img which supasses QSB:
https://firmwaresecurity.com/2017/06/08/breaking-samsung-galaxy-secure-boot-through-download-mode/
Click to expand...
Click to collapse
TimSchumi said:
Just a conclusion I wrote about the "original" SM-G350, the Qualcomm versions of the SM-G350 and Qualcomm Secure Boot (QSB):
Click to expand...
Click to collapse
If I find my SM-G350L which is a Latin American Snapdragon model, I will give it a hand again at porting TWRP. I have a better computer now that can compile in less time.
Been reading the paper and apparently relies on an Odin exploit that causes it to read data directly from the boot image at verification time and we could just load the entrypoint of the kernel into memory. I think it's the same exploit used for AT&T Galaxy S4 and we could Loki it into executing our custom recovery. Lemme find it and I will make TWRP soon, if i find it of course. It's lost somewhere in a deep corner of my house
Related
HI! I need your help. My samsung s5 clone doesn't open anymore. When i tried to open it, it'll just stay on black screen but when i press the power button it'll vibrate. Please help me. I think restoring will fix this but i don't know how.
MT6572
SM-G9008
Quad-core (but i'm not sure if it's true)
2Gig ram(i'm not sure with this too.)
Manufacturers of clone devices almost never release their factory ROM's, or even their kernel source which breaks the GN GPLv2 license. Therefore you won't be able to find the stock ROM for your phone.
In addition to that we don't usually support cloned devices on XDA in terms of custom ROM's because the developers of custom ROM's buy the real phones, not clones.
Thread closed.
Im surprised to see no ones brought this up in the S5 forum or over at Ubuntu. Isnt there anyone working on multiboot rom or way to dual-boot linux from sd card on the S5? If not, why?
jross3030 said:
Im surprised to see no ones brought this up in the S5 forum or over at Ubuntu. Isnt there anyone working on multiboot rom or way to dual-boot linux from sd card on the S5? If not, why?
Click to expand...
Click to collapse
Didn't search the forum before posting?
There are any number of variations on multi boot from Hashcode's Safestrap here to Tasssadar's multiboot for Nexus. And related proprietary modes that resemble user profiles e.g. Samsung's kids mode.
Google had also announced that full multi-user profiles would be supported from 4.2 /4.3 forward. But they subsequently restricted the feature to tablets and haven't done much with it since.
But you are probably thinking more about booting into something like Kali linux There have been a few threads about that. And it has been done for the S4, Note, Nexus, etc. A bit soon to expect it on the S5 as it has only been released for a couple of months. And it's a new processor too. Do you want to develop it for is?
.
fffft said:
Didn't search the forum before posting?
There are any number of variations on multi boot from Hashcode's Safestrap here to Tasssadar's multiboot for Nexus. And related proprietary modes that resemble user profiles e.g. Samsung's kids mode.
Google had also announced that full multi-user profiles would be supported from 4.2 /4.3 forward. But they subsequently restricted the feature to tablets and haven't done much with it since.
But you are probably thinking more about booting into something like Kali linux There have been a few threads about that. And it has been done for the S4, Note, Nexus, etc. A bit soon to expect it on the S5 as it has only been released for a couple of months. And it's a new processor too. Do you want to develop it for is?
.
Click to expand...
Click to collapse
Thanks for the reply. I did search "Ubuntu" and "Linux" within the S5 forum but nothing but a firmware dump or porting popped up. I'm new to Android and a bit wary of risking device trying to piece together methods from other devices. I don't care about Kali, just Linux OS i can boot into, not needing to vnc into a virtual environment.
Hello guys, i just have a (few) question(s)
So, last week i installed Google Edition Andriod Kitkat 4.4.4 on my galaxy S4 I9505.
This rom is till now, still amazing, fast and better than touchwiz in any way. But i can't seem to find on the internet how and which version of xposed framework i need to install, since it is per model (i think?) which model do i choose?
since i have a Galay S4 but my rom is not from a galaxy S4, i get confused which one i have to install.
Some links to downloads would be great!
Thanks in advance
Dylan
dylanbos1996 said:
Hello guys, i just have a (few) question(s)
So, last week i installed Google Edition Andriod Kitkat 4.4.4 on my galaxy S4 I9505.
This rom is till now, still amazing, fast and better than touchwiz in any way. But i can't seem to find on the internet how and which version of xposed framework i need to install, since it is per model (i think?) which model do i choose?
since i have a Galay S4 but my rom is not from a galaxy S4, i get confused which one i have to install.
Some links to downloads would be great!
Thanks in advance
Dylan
Click to expand...
Click to collapse
Hi mate
Basically it works in any android 4.0 + base rom device see from one of his threads
For which devices/ROMs does it work?
I develop the Xposed framework based on the AOSP sources. I'm personally using CM10.2 on an I9100 (Samsung Galaxy S2, bought in Germany). Basically, it should work on any phone which with a ROM based on Android 4.0 or later and an ARM or x86 processor (this is the processor architecture, almost all smart phones and tablets have either of those). Exceptions might be ROMs which are different from the original Android code in some very internal, central code parts (which don't need to be touched for most theming and enhancement modifications). But this is related to the ROM, not the phone itself.
The modules target higher-level code, so they are more likely to be incompatible with your ROM. Basically, the question is whether the methods and resources which the module modifies are similar on your ROM and on the developer's ROM. Let's say a module needs to modify the result of a certain method call. For this, it needs to specify the exact name and parameters that identify that method. If the in your ROM, an additional parameter has been added, the module can't find the method anymore and won't work. If the method can still be found, it will probably work (unless the rest of the app/ROM has changed too much).
There is not definite answer whether it will work. Just try it (of course, making a nandroid backup before is never a bad idea). If it doesn't work, just disable the module. You might want to inform the module developer (not me!) about this fact and provide details (e.g. a logcat and/or the content of /data/data/de.robv.android.xposed.installer/log/debug.log).
Try with latest 2.6.1
http://forum.xda-developers.com/xposed/xposed-faq-issues-t2735540
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Thank You!
MAX 404 said:
Hi mate
Basically it works in any android 4.0 + base rom device see from one of his threads
For which devices/ROMs does it work?
I develop the Xposed framework based on the AOSP sources. I'm personally using CM10.2 on an I9100 (Samsung Galaxy S2, bought in Germany). Basically, it should work on any phone which with a ROM based on Android 4.0 or later and an ARM or x86 processor (this is the processor architecture, almost all smart phones and tablets have either of those). Exceptions might be ROMs which are different from the original Android code in some very internal, central code parts (which don't need to be touched for most theming and enhancement modifications). But this is related to the ROM, not the phone itself.
The modules target higher-level code, so they are more likely to be incompatible with your ROM. Basically, the question is whether the methods and resources which the module modifies are similar on your ROM and on the developer's ROM. Let's say a module needs to modify the result of a certain method call. For this, it needs to specify the exact name and parameters that identify that method. If the in your ROM, an additional parameter has been added, the module can't find the method anymore and won't work. If the method can still be found, it will probably work (unless the rest of the app/ROM has changed too much).
There is not definite answer whether it will work. Just try it (of course, making a nandroid backup before is never a bad idea). If it doesn't work, just disable the module. You might want to inform the module developer (not me!) about this fact and provide details (e.g. a logcat and/or the content of /data/data/de.robv.android.xposed.installer/log/debug.log).
Try with latest 2.6.1
http://forum.xda-developers.com/xposed/xposed-faq-issues-t2735540
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Click to expand...
Click to collapse
Thank you so much for your help. I think it is pretty clear for me now.
Dylan
dylanbos1996 said:
Thank you so much for your help. I think it is pretty clear for me now.
Dylan
Click to expand...
Click to collapse
Any time mate.
Hi ,
I have Samsung Galaxy S7 edge (model SM-G935FD - G935FXXU1BPLB) model device with me.
Downloaded G935FXXU1BPLB - SM-G935F_MM_Opensource.zip , from opensource.samsung.com
I have taken boot.img from the phone and disassembled using unpackbootimge tool.
Compiled the Downloaded kernel as mentioned in the "README_Kernel.txt". Then overwritten boot.img-zImage file with compiled Kernel/arch/arm64/boot/Image.
Created boot.img (used mkbootimg tool) with the modified kernel boot image , then flashed the new boot.img with
dd if=boot.img of=/dev/block/sda5 bs=2048
After restarting the phone, i am stuck with " Kernel is not seadroid enforcing " even though the compiled kernel is downloaded from the samsung official site.
Please help me to fix it.
The message is not the reason that your phone is not booting up (as it seems).
Despite you built a kernel based on Samsung sources it is one you made and it is not signed by Samsung. However, this message is informational only (and should disappear once you flash a kernel built and released by Samsung).
Why your system is not booting up is a different question and based on your information impossible to tell.
andiling said:
The message is not the reason that your phone is not booting up (as it seems).
Despite you built a kernel based on Samsung sources it is one you made and it is not signed by Samsung. However, this message is informational only (and should disappear once you flash a kernel built and released by Samsung).
Why your system is not booting up is a different question and based on your information impossible to tell.
Click to expand...
Click to collapse
thank you for the reply.
I followed the same method for samsung galaxy s6 , it is working fine, i.e, am able to flash the kernel downloaded from samsung official site.
where as with samsung galaxy s7 edge, Compiled the kerenel from the official site, After that i am seeing the "Kernel is not Seandroid enforcing error".
I don't know the reason why it is not booting. But i need samsung galaxy s7 edge which will be working with compiled kernel source.
Please help to debug the issue, let me know if you need any further information ?
Hello XDA community,
After months of struggling im in desperate need of your help.
What is my goal?
To compile our own kernel so we can mess around with Qualcomm's trustzone.
Where did it all start?
It all started a few months ago back in November 2021 when me and a friend read a blog about a Trustzone exploit in Qualcomm's MSM8974 processor. (link to the blog)
Big noobs as we where, we where getting hyped an bought ourselves a Samsung Galaxy Note 3 with a MSM8974 processor. After messing around with the device we learned more and more about android and the workings of the software. We first started to root the phone and play around with ADB. After that we found that we can use Frida aswell. But all of it didn't lead to the result we wanted. So we started to dig deeper in to the write-up of the blog. We soon came to the conclusion that we where not even close to doing the right thing.
What happend next?
After we came to the conclusion that ADB and Frida is not enough we understood we need to build our own kernel for this exploit to work. So we do what we always do and that was start googling and watch YouTube. By doing that we found 2 different kernels:
Lineage 18.1
SM-N9005_EUR_LL_Opensource
We where over the moon because inside the folders we found the the files that need to be replaced for the exploit to work. So we replaced the files and try to compile the kernel by using this YouTube tutorial. Everything seemed to go well, we made the
Code:
make msm8974_sec_defconfig
and we run
Code:
make menuconfig
so far so good. the last and final step should be to run
Code:
make
to compile the kernel. And that is where it went wrong an ran in to a error.
Then what?
Then we started to compare the original files with the modified files and we found out that it wasn't just a few modifications in the code but the code was different. So we did what we always do, go back to the source. So back at the blog we thought maybe its because they modified a Nexus 5 at android 4.4.4.
Now what?
Now im trying to find the source of a android 4.4.4 kernel of msm8974 so we can compare those files to the modified files. So if anyone has useful info or knows where to find a kernel for android 4.4.4 for a Samsung Galaxy Note 3 (SM-N9005).
TLDR;
Im looking for a source of android 4.4.4. for a Samsung Galaxy Note 3 (SM-N9005) (hlte)
Well, unfortunately today almost no one uses android 4.4.4. even that have the exact same device, I am using Android 11 on my phone.
I recommend not wasting your time on a kernel for Android 4.4.4. And if you really want to make a kernel for this device I need one for Android 10 and above.
Also I think making a kernel for AOSPs like LineageOS or HavocOS or crDroid ETC is much easier.
A.M.2.K.M said:
Well, unfortunately today almost no one uses android 4.4.4. even that have the exact same device, I am using Android 11 on my phone.
I recommend not wasting your time on a kernel for Android 4.4.4. And if you really want to make a kernel for this device I need one for Android 10 and above.
Also I think making a kernel for AOSPs like LineageOS or HavocOS or crDroid ETC is much easier.
Click to expand...
Click to collapse
Thanks for your response I will look in to it. not sure if it will be easier because the files that needed to be changed are:
arch/arm/mach-msm/scm.c
arch/arm/mach-msm/include/mach/scm.h
drivers/misc/qseecom.c
SwAgLaNdeR said:
Thanks for your response I will look in to it. not sure if it will be easier because the files that needed to be changed are:
arch/arm/mach-msm/scm.c
arch/arm/mach-msm/include/mach/scm.h
drivers/misc/qseecom.c
Click to expand...
Click to collapse
Well, I don't know much about kernels.
I said it's easier because I thought it's a pure and raw operating system. But now according to your post it turns out it's not easier.
Plus almost no developers left for this now very old model .