I have a rooted Snapdragon S8 (done by this method) and I want to install LineageOS (or any other non-samsung android build) onto it.
I have searched far and wide on this form an the internet and I have not been able to find a single custom ROM for the Snapdragon S8. Does anyone know of any of these ROMs that exist?
If they do not exist, would it be possible for me to make one? Is there a tutorial or resource to help me with this? I have a decent amount of experience with rather technical programming on the PC (writing Linux kernel code, etc.) so I would not be walking in completely blind to the topic, however, I have never really messed with android before (besides rooting this phone and a couple of Nexus devices).
I apologize if this is a repeated question, like I said, I couldn't find anything.
Thank you in advance for any and all help!
sckzor said:
I have a rooted Snapdragon S8 (done by this method) and I want to install LineageOS (or any other non-samsung android build) onto it.
I have searched far and wide on this form an the internet and I have not been able to find a single custom ROM for the Snapdragon S8. Does anyone know of any of these ROMs that exist?
If they do not exist, would it be possible for me to make one? Is there a tutorial or resource to help me with this? I have a decent amount of experience with rather technical programming on the PC (writing Linux kernel code, etc.) so I would not be walking in completely blind to the topic, however, I have never really messed with android before (besides rooting this phone and a couple of Nexus devices).
I apologize if this is a repeated question, like I said, I couldn't find anything.
Thank you in advance for any and all help!
Click to expand...
Click to collapse
I also have mine with root I have tried with a lineage rom from an s4 but it installs but does not start. Look at the forum, maybe they will help you to achieve one.
ROOT_8_SERIES_AND_OLDER
You can view and join @S8_N8_ROOT right away.
t.me
Related
Hey,
I've just recently started Android development and I'm keen to learn as much as I can about the whole system, not just about SDK app development. As such I'm interested in attempting to build my own ROM completely from scratch. I've downloaded the Android Source (and Galaxy S source) and would like to try my luck.
First I've been mucking around creating custom ROMs with the emulator, moving apps from the Galaxy S ROM I dumped from my device onto the stock emulator ROM and testing things out.
Anyway I'm at the point where I'm wondering if it's possible to flash the stock emulator ROM onto a Galaxy S phone? I know the Galaxy S source includes a lot of device specific stuff however I'm not interested in getting the camera, bluetooth or anything hardware specific working just yet.
If I flash a ROM with a stock kernel, drivers etc. onto my phone will it work? Has anyone done this? Will it just brick my phone?
Any help would be appreciated.
Cheers,
Ben
Anyone?
Also, I know people have flashed AOSP ROMs on other phones, does anyone know if they required modifications or whether they are in fact stock ROMs?
nje, can't work. why?
1) different bootloaders
2) different partition layout
3) different (kernel)drivers
4) different vendor setup
etc.
it is possible to flash the emulator image onto a dev device (dream/sapphire) but even then a lot will not work properly!
if you want to learn about the android architecture you should start with building a kernel (there is already a thread about that here) and playing around with stuff like the (file)system and utilities...
Thanks jodue.
Yeah my long term intentions were definitely to build the Galaxy S kernel and any necessary libraries and drivers specifically necessary for the apps I decide to include in a custom ROM.
I was hoping that I'd be able to start out by tweaking a minimalistic/generic ROM (the AOSP default ROM) on my Galaxy S. However, as you've pointed out I'll have to start out with the kernel and all the device specific stuff first.
I've got quite a bit of information on building an Android/linux kernel both from the thread you mentioned and also the official AOSP page. However information on putting together a complete working ROM seems a bit sparse. Does anyone know where I can find some information on the topic?
I'm also curious to learn about the list of things jodue mentioned i.e. Android bootloaders, partition layouts and drivers (generic and Galaxy S specific). I assume detailed information about particular devices and drivers probably isn't available but if anyone even knows where I can learn detailed information about default AOSP ROMs I'd be extremely interested know.
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.
Please... I recently updated to marshmallow and it's buggy and a bit slow and I'm completely infuriated about the fact that I couldn't find ROMs for my model (I know it's not popular but I thought someone might already have done it). I'm learning how to program but I'm still not advanced enough to be able to modify a ROM. It should be relatively easy though bc SM-A700FD & SM-A700H share the same processer! They only differ that the first supports LTE while the second 3G (they both have two sim slots). Thanks for anyone who will help me! I own the 2015 A7 btw. If you can help me find a ROM for my device I'll be grateful! Doesn't have to be resurrection I just want a stable stock build with useful features.
Hello guys,
this is my first post. Since today I´m a proud owner of a Galaxy Tab A (SM-T510 with 64 GB ROM and 3GB RAM, newest stock android build T510XXU2ASK5, never connected to internet yet).
I want to install Nethunter OS or Kali Linux (if possible) on this and read many hours in the internet but there are some questions:
Has anyone flashed the SM-T510 with Nethunter OS? (if this isn´t possible, a way to just use the kali apps is fine too but not my first choice)
Is it possible to flash directly to the ROM instead to a SD Card?
Which type of processor has the tablet? I think it is amd64 not arm, right? Maybe I could try to flash a Nethunter Image for Galaxy Tab S4 but I´m sure this doesn´t work cause the processor is not exact the same... (https://www.offensive-security.com/kali-linux-nethunter-download/)
I found this thread about Kali Linux installation but I would find a direct installation better https://forum.xda-developers.com/hardware-hacking/hardware/devices-kali-linux-installation-t3414523 (If I can´t install directly, can I use this guide for my device after I rooted it?)
A few years ago I flashed Android on a SD-Card for my HTC Kaiser 130 (still working fine), so I have a little experience about flashing and so on but flashing this tablet looks a little bit more difficult to me, so I want as much information as possible cause I have only one try (in the baddest scenario)
I hope you can help me.
Thanks for reading! (I´m from germany, so I´m sorry for my bad english)
Edit: I have found UserLAnd and will try it now, if someone has a better suggestion, feel free to post it
Where'd you get the idea that this was an AMD64 tablet? All Samsung Galaxy Tab As are ARM, The T510 has an Exynos 7904 or 7885 SoC. And I've never heard of anyone porting a Linux distro to one.
lewmur said:
Where'd you get the idea that this was an AMD64 tablet? All Samsung Galaxy Tab As are ARM, The T510 has an Exynos 7904 or 7885 SoC. And I've never heard of anyone porting a Linux distro to one.
Click to expand...
Click to collapse
Thanks for your answer lewmur, I just read it is a 64bit proc and thought it is amd64, my last tablet is some years old and I just thinked the technical development is quicker... ^^
Hmm... sounds like bad news, I just googled yesterday and it is a Exynos 7904, yes you´re right. That means it is closed source, damn.
In this thread (https://forum.xda-developers.com/galaxy-m30/help/hope-custom-rom-development-m30-exynos-t3910256) I found someone who maybe has kernel source, I will write him. Maybe where is a way to build a Nethunter image by myself. I have tested UserLAnd on the tab and I don´t really like it, it´s not smooth.
On monday I will go to the shop where I buyed the tab and try to give it back, maybe they have goodwill, then I will buy online a nexus tablet, looks much more easier.
Thank you anyway, maybe someone has some more good tipps for me.
I have downloaded this
nethunter-2021.3-generic-armhf-kalifs-full.zip
and flashed it with TWRP on my Rooted Device and it works on SM-T510 Android 11 StockROM
I just bought an S5E, and having owned two previous Samsung devices, I expected a fair amount of bloat, but not nearly the amount I discovered. It makes my previous two Samsungs look downright slender. Particularly loathsome, in my view, is the way SS has hijacked Find My Mobile and Google Messages, the latter of which, as a Google Fi customer, I have to use for SMS.
Hence, I am going to root, and cleanse this otherwise delightful device with the fire of 1000 suns. I have rooted Android devices before, but it's been a while, and my memory hasn't improved with age, so I have several questions, some about rooting in general, and some specific to this device. I should add that, while I am not opposed to performance gains and newer versions of Android and suchlike, my only pressing concern is to de-Samsungize the bejeebers out of this thing. Other than that, something like a stock version of Android and an otherwise low-maintenance tablet will make me very happy. So, here goes:
I have the PewPewk method bookmarked, and believe I have one or two others using various combinations of ADB and Magisk and suchlike bookmarked. I imagine I can handle them, but they look complicated. Are any of the apparently simpler approaches found here effective, sufficient to achieve my goals, and unlikely to brick me?
What are the advantages of Custom Android Recoveries relative to the stock Android, and if they add much in the way of complications, can I live without them?
Do I need a custom ROM, and more specifically, do I need one to give me non-Samsungized versions of Find My Mobile and Google Messages? At a minimum, I need the garden-variety version of Google Messages so I can text like a normal person, not a Samsung zombie.
Again, I don't really need tweaks for performance or new versions of Android, but I do need to get bug fixes and security patches with a minimum of fuss. How do I find that minimal sweet spot?
If the answers to one or more of these question are that yes, I need a custom recovery and/or ROM - I suspect this will be the case - then can anyone recommend good candidates that will get me the outcomes I'm looking for without perplexing me too greatly and making me want to cuss?
Can anyone identify the questions which I should be asking, but which didn't occur to me, and then pose them and answer them?
I'm confident that I'm in the right forum to get the answers I need, so all advice will be greatly appreciated.
smilejack1 said:
I just bought an S5E, and having owned two previous Samsung devices, I expected a fair amount of bloat, but not nearly the amount I discovered. It makes my previous two Samsungs look downright slender. Particularly loathsome, in my view, is the way SS has hijacked Find My Mobile and Google Messages, the latter of which, as a Google Fi customer, I have to use for SMS.
Hence, I am going to root, and cleanse this otherwise delightful device with the fire of 1000 suns. I have rooted Android devices before, but it's been a while, and my memory hasn't improved with age, so I have several questions, some about rooting in general, and some specific to this device. I should add that, while I am not opposed to performance gains and newer versions of Android and suchlike, my only pressing concern is to de-Samsungize the bejeebers out of this thing. Other than that, something like a stock version of Android and an otherwise low-maintenance tablet will make me very happy. So, here goes:
I have the PewPewk method bookmarked, and believe I have one or two others using various combinations of ADB and Magisk and suchlike bookmarked. I imagine I can handle them, but they look complicated. Are any of the apparently simpler approaches found here effective, sufficient to achieve my goals, and unlikely to brick me?
What are the advantages of Custom Android Recoveries relative to the stock Android, and if they add much in the way of complications, can I live without them?
Do I need a custom ROM, and more specifically, do I need one to give me non-Samsungized versions of Find My Mobile and Google Messages? At a minimum, I need the garden-variety version of Google Messages so I can text like a normal person, not a Samsung zombie.
Again, I don't really need tweaks for performance or new versions of Android, but I do need to get bug fixes and security patches with a minimum of fuss. How do I find that minimal sweet spot?
If the answers to one or more of these question are that yes, I need a custom recovery and/or ROM - I suspect this will be the case - then can anyone recommend good candidates that will get me the outcomes I'm looking for without perplexing me too greatly and making me want to cuss?
Can anyone identify the questions which I should be asking, but which didn't occur to me, and then pose them and answer them?
I'm confident that I'm in the right forum to get the answers I need, so all advice will be greatly appreciated.
Click to expand...
Click to collapse
Hello there
Your questions are really deep, maybe that is why no answers so far
I'm not an expert at all, so I can't give you comprehensive answers. But I rooted Tab S5e successfully (on stock ROM) and I've read a lot about modifying it, so I can share just few hints.
I wouldn't bother of any other rooting method than Magisk. However, this tab isn't as easy to root as most of the other devices... By far the best and comprehensive guide to root the stock ROM is here:
Galaxy Tab S5e (SM-T720) - Root Instructions (Release 1.0) | XDA Developers Forums (xda-developers.com)
If you follow it closely, you shouldn't have problems. I did it and can confirm it's working fine.
I haven't used custom ROM on this device, but there are some available, especially LineageOS from the recognized developer and one of the LineageOS team member. You can take a look on those threads:
[ROM][OFFICIAL][gts4lvwifi][10] LineageOS 17.1 | XDA Developers Forums (xda-developers.com)
[ROM][UNOFFICIAL][gts4lvwifi][11] LineageOS 18.1 | XDA Developers Forums (xda-developers.com)
In order to flash custom ROM you need custom recovery. There is TWRP available:
Samsung Galaxy Tab S5e WiFi (twrp.me)
Again, I did not try to flash it, I've heard it's tricky, so you need to dig dipper inside those threads and articles.
Alternatively, there is a method to debloat stock ROM without root. It is described in this thread:
[Guide] Samsung Galaxy Tab S5e Debloat Without Root-Info | XDA Developers Forums (xda-developers.com)
Hope it helps!
Thank you for your input. By the time you offered it, I had plunged ahead with the rooting method you suggested. Overall, it went well, but I'm having a few issues with the tablet since getting Lineage 17.1 installed.
I have made a new post requesting help with those issues, which can be found here. If you can offer any advice thereupon, I would be greatly appreciative, and if not, thank you for your efforts above.