[Q] What's needed to build a custom rom for S9+? - Samsung Galaxy S9 Questions & Answers

Hi Im curious what's required to build a custom rom (pie or later) for the Qualcomm China varient? Are there any guides tailored or something towards these devices (basically less of generalized one)?
What I know i need:
A 64bit Linux box i have that: Debian 10 currently.
Custom rom source (I'll decide on it later probably will be Lineage)
Samsung S9 Source Code etc <== Not sure how to get it.
A way to Flash said custom rom once built (TWRP would be easiest since i have it already plus saves me trying to make a flash package for the Linux's varient of Odin)
End of what I know im sure that there's more i will need hence the reason for the thread lol.
Anyway Thanks to anyone for any help they can offer in advance.

darkensx said:
Hi Im curious what's required to build a custom rom (pie or later) for the Qualcomm China varient? Are there any guides tailored or something towards these devices (basically less of generalized one)?
What I know i need:
A 64bit Linux box i have that: Debian 10 currently.
Custom rom source (I'll decide on it later probably will be Lineage)
Samsung S9 Source Code etc <== Not sure how to get it.
A way to Flash said custom rom once built (TWRP would be easiest since i have it already plus saves me trying to make a flash package for the Linux's varient of Odin)
End of what I know im sure that there's more i will need hence the reason for the thread lol.
Anyway Thanks to anyone for any help they can offer in advance.
Click to expand...
Click to collapse
two things. 1: an unlocked bootloader 2: asking your question in the right place just messing with you on the latter, of course.
Id poke around in the Galaxy devices built specifically for non US markets as they have unlocked bootloaders and that level of development is awash in those areas.

Youdoofus said:
two things. 1: an unlocked bootloader 2: asking your question in the right place just messing with you on the latter, of course.
Id poke around in the Galaxy devices built specifically for non US markets as they have unlocked bootloaders and that level of development is awash in those areas.
Click to expand...
Click to collapse
actually i have the unlocked bootloader SM-G9650 (star2qltechn) i forgot to mention that lol my bad..

Related

Koodo Note 2 compatibility?

Hi everyone. So I Just got a note 2 the other day after having been using a nexus 4 for the past six months. I never use stock Roms and haven't since I got my s3 a year or so ago (I seemingly change phones often...). That being said I was looking into how to root this device and which Roms were compatible etc.
It seems all Canadian note 2 devices are the same? Rogers, Bell, koodo/telus etc? Am I correct in assuming this, and if so that any of the Roms found in this forums sub forums for aosp as well as other Roms like PA etc are compatible? (if it's compatible with the att note 2 my koodo note 2 is good to go?)
Also, it seems this devices forums are outdated and dying sadly, so can anyone recommend a recently active Rom, be it aosp or not, that is highly themeable and configurable, and preferably has good s-pen support?
Much appreciated!
Oh, and a link to the correct post for rooting this device and flashing new recovery (twrp or cwm) in its latest compatible version would be awesome too.
Thanks everyone!
There are two Canadian Note 2 models: the I317M (yours) and the T889V (mine).
So long as you don't try flashing a non I317M modem on your device, you can pretty much flash any t0lte/t0lteatt/t0ltetmo a.k.a N7105, I317(M) or T889(V) ROM out there. Along the same lines, do not flash anything meant for the N7100.
For a nice belt and suspenders approach: make backups of your EFS partitions with all known methods: EFS Professional text format, QPST qcn, "Synergy ROM" method recovery script. (I adapted the latter for the T889V and it should work as is for your device.)
Assuming your device already has the stock 4.3 ROM, you will burn the KNOX fuse by flashing anything custom or generally trying to root.
(There may be more steps involved for KNOX, you're on your own for that part: the only thing stock 4.3 I've flashed is the modem.)
To root, get the latest t0lte Odin-flashable TWRP image, apply SuperSU or superuser zip from there as desired.
There's still a fair amount of activity out here, I've been running Omni nightlies for a while now.
It's normal for things to slow down: Bugs get squashed, ROMs on a manual release schedule slow down because they've implemented what they wanted, automatically built ROMs get smaller incremental updates from upstream. There's been an uptick with the stock TouchWiz 4.4 releases in the pipeline (the N7105 Nordic Countries CSC has been pushed, others are incoming) and kernel sources also trigger some action. Another factor for slow down is that early adopter devices are going on two-years and people upgrade.
I hardly use the S-Pen so I can't help you that much with it. There's a couple open source apps that support it and that can be added to your choice of AOSP ROM to enable things like gestures or hand-drawn notes.
Darkshado said:
There are two Canadian Note 2 models: the I317M (yours) and the T889V (mine).
So long as you don't try flashing a non I317M modem on your device, you can pretty much flash any t0lte/t0lteatt/t0ltetmo a.k.a N7105, I317(M) or T889(V) ROM out there. Along the same lines, do not flash anything meant for the N7100.
For a nice belt and suspenders approach: make backups of your EFS partitions with all known methods: EFS Professional text format, QPST qcn, "Synergy ROM" method recovery script. (I adapted the latter for the T889V and it should work as is for your device.)
Assuming your device already has the stock 4.3 ROM, you will burn the KNOX fuse by flashing anything custom or generally trying to root.
(There may be more steps involved for KNOX, you're on your own for that part: the only thing stock 4.3 I've flashed is the modem.)
To root, get the latest t0lte Odin-flashable TWRP image, apply SuperSU or superuser zip from there as desired.
There's still a fair amount of activity out here, I've been running Omni nightlies for a while now.
It's normal for things to slow down: Bugs get squashed, ROMs on a manual release schedule slow down because they've implemented what they wanted, automatically built ROMs get smaller incremental updates from upstream. There's been an uptick with the stock TouchWiz 4.4 releases in the pipeline (the N7105 Nordic Countries CSC has been pushed, others are incoming) and kernel sources also trigger some action. Another factor for slow down is that early adopter devices are going on two-years and people upgrade.
I hardly use the S-Pen so I can't help you that much with it. There's a couple open source apps that support it and that can be added to your choice of AOSP ROM to enable things like gestures or hand-drawn notes.
Click to expand...
Click to collapse
Great Question and great response.
I recently got the Koodo note 2. I finally switched coming from my well aged HTC HD2. Anyway I have a quick question. If i'm using a TW or a AOSP rom I can't connect to my Mac adhoc network. The old roms I used on My HTC had something baked into them that allowed that. Note sure if there's a special file I have to change. Any help would be appreciated.
Thanks
Darkshado said:
There are two Canadian Note 2 models: the I317M (yours) and the T889V (mine).
So long as you don't try flashing a non I317M modem on your device, you can pretty much flash any t0lte/t0lteatt/t0ltetmo a.k.a N7105, I317(M) or T889(V) ROM out there. Along the same lines, do not flash anything meant for the N7100.
Click to expand...
Click to collapse
Thank you Darkshado for all your helpful posts!
1) I'm also considering one if these from Koodo, currently advertised to contain the dreaded 4.3 update. May I restate what your saying is t0lte for N7105, t0lteatt for I317M, and t0ltetmo for t0ltetmo. When I looked previously on the TWRP site I saw the 't' choices but no clear cross reference to device model number.
2) I've read for many many hours about the downgrade path to 4.1.1 to unlock and how this would blow the KNOX fuse. Considering I'd be buying the device new from Koodo, I'm not happy about the prospect of losing an entire 12 month warranty-assuming a broken KNOX.
Catalyst2012 said:
Thank you Darkshado for all your helpful posts!
1) I'm also considering one if these from Koodo, currently advertised to contain the dreaded 4.3 update. May I restate what your saying is t0lte for N7105, t0lteatt for I317M, and t0ltetmo for t0ltetmo. When I looked previously on the TWRP site I saw the 't' choices but no clear cross reference to device model number.
2) I've read for many many hours about the downgrade path to 4.1.1 to unlock and how this would blow the KNOX fuse. Considering I'd be buying the device new from Koodo, I'm not happy about the prospect of losing an entire 12 month warranty-assuming a broken KNOX.
Click to expand...
Click to collapse
This is a Note 3 rom for our Note 2's. I have the same phone as you are asking about. That rom will work for the I317M/I317 variants also.
http://forum.xda-developers.com/showthread.php?t=2504016
Comes with most of the N3 features including Air Command(very handy), and you can use the S5 GUI and some of the S5 apps also.
It's been very stable for me so far. I love it and it's my current daily driver.
Good luck!
Catalyst2012 said:
Thank you Darkshado for all your helpful posts!
1) I'm also considering one if these from Koodo, currently advertised to contain the dreaded 4.3 update. May I restate what your saying is t0lte for N7105, t0lteatt for I317M, and t0ltetmo for t0ltetmo. When I looked previously on the TWRP site I saw the 't' choices but no clear cross reference to device model number.
2) I've read for many many hours about the downgrade path to 4.1.1 to unlock and how this would blow the KNOX fuse. Considering I'd be buying the device new from Koodo, I'm not happy about the prospect of losing an entire 12 month warranty-assuming a broken KNOX.
Click to expand...
Click to collapse
1) Nope, t0lte is just as fine for the I317M. (If anything I'm even surprised the TWRP team still builds three separate recoveries. I'd have to look at the code for any meaningful differences, but I'm short on time to do that. Maybe ask on IRC?)
2) It's unfortunate, but then again there are other options, you could get a code from Koodo or elsewhere online; if you're adamant about keeping KNOX untouched. My understanding is that in Europe, the onus is on companies to prove that the user's root and ROM related activities caused problems with a given device. I'm thinking that the same would hold in many Canadian provinces if someone put up a fight in small claims court.
DelphinusMinor said:
This is a Note 3 rom for our Note 2's. I have the same phone as you are asking about. That rom will work for the I317M/I317 variants also.
http://forum.xda-developers.com/showthread.php?t=2504016
Comes with most of the N3 features including Air Command(very handy), and you can use the S5 GUI and some of the S5 apps also.
It's been very stable for me so far. I love it and it's my current daily driver.
Good luck!
Click to expand...
Click to collapse
Looks fascinating! A brief read indicates its for the N7100 - thanks for clarifying that it works for the i1317M. Does Call Recording work for you?
Catalyst2012 said:
Looks fascinating! A brief read indicates its for the N7100 - thanks for clarifying that it works for the i1317M. Does Call Recording work for you?
Click to expand...
Click to collapse
I haven't tried. I can't test it at the moment either because I need to top my minutes up. D'oh! I should be doing that tomorrow sometime.
It's a great rom. Been using it for several days and no issues.
Darkshado said:
1) Nope, t0lte is just as fine for the I317M. (If anything I'm even surprised the TWRP team still builds three separate recoveries. I'd have to look at the code for any meaningful differences, but I'm short on time to do that. Maybe ask on IRC?)
2) It's unfortunate, but then again there are other options, you could get a code from Koodo or elsewhere online; if you're adamant about keeping KNOX untouched. My understanding is that in Europe, the onus is on companies to prove that the user's root and ROM related activities caused problems with a given device. I'm thinking that the same would hold in many Canadian provinces if someone put up a fight in small claims court.
Click to expand...
Click to collapse
Thanks.
1) No need to check the TWRP code as your response was clear and helpful.
2) A local unlocker business told me: they have a new way that no longer requires downgrading to 4.1.1. With his codes, I could unlock the device without any additional software or PC for C$40. I explicitly asked about KNOX - he wasn't 100% clear but said he did not think it would affect it. He said they buy lists of unlock codes based on IMEI and resell them for a small profit. Koodo requires 90 days on Koodo + the same unlock $ fee. I wasn't planning on staying on Koodo that long. In perhaps the 8 hours by now I've spent reading about this on XDA, its still not certain a device with 4.3 can be customized without blowing the Knox efuse. Towelroot 'might' give me root without tripping it but the risk of losing a full 12 month warranty is not welcome. A used device might be OK if it was still on 4.1.x. If it had been downgraded from 4.3, though unlikely, I probably wouldn't know until after I got home. Otherwise I could root+custom right way and never mess with samsung roms.
Any suggestions are welcome!
DelphinusMinor said:
I haven't tried. I can't test it at the moment either because I need to top my minutes up. D'oh! I should be doing that tomorrow sometime.
It's a great rom. Been using it for several days and no issues.
Click to expand...
Click to collapse
You should be able to test it without using any of your minutes. Just call Koodo customer service from your handset (*611 I think) it should be a free call. When the voice menu begins, start recording. Ask a few questions like "Do you support custom ROMs?" or "Do you know the winning lottery numbers", or whatever, this is just a 2-way voice recording test. I use this trick all the time when testing. Enjoy.

Galaxy Tab 3 7.0 SM-T211 SNIFFERS

Hello,
I done everything. Installed BUSYBOX Pro . Tried DSPLOIT, ZANTI, WI.CAP. Any sniffers do not work on my device .
It is ROOTED 4.4.2 kitkat flashed wtih werewolf custom rom.
Can anyone help me to run apps like this?
Gradz,
Head16
Head16 said:
Hello,
I done everything. Installed BUSYBOX Pro . Tried DSPLOIT, ZANTI, WI.CAP. Any sniffers do not work on my device .
It is ROOTED 4.4.2 kitkat flashed wtih werewolf custom rom.
Can anyone help me to run apps like this?
Gradz,
Head16
Click to expand...
Click to collapse
Dude, seriously? If you don't see what's wrong with your question then you shouldn't be playing
with those things. Lot's of reading and learning must you do, hmmm?
Yoda
okay, slightly dickish answer sorry.
you need certain abilities enabled at the kernel/driver level for some of the things you want
to do. which maybe be as relatively simple as patching kernel source and rebuilding or may require
rev-eng'ing proprietary drivers/binaries additionally.
you may be better served to researched a device more naturally endowed with these capabilities,
alternately a device with usb-otg support so you can use a dongle device proven to be
capable of these tasks.
ommmm
So because i used custom rom, this apps does not working?
Head16 said:
So because i used custom rom, this apps does not working?
Click to expand...
Click to collapse
sort of yes/no because the custom rom contains the software and the kernel is a custom build
it does not necessarily mean that your hardware is capable [meaning the device's capability, the kernel
having the necessary code and if there are proprietary/prebuilt source code unavailable/ binaries and firmware
support files which need to be hacked/engineered.
find out the device id of your wifi hardware and search it's id/name along with the function you are trying to perform.
for example
bcm4334 monitor mode
use the search engine that works for you, read carefully and fully and get yourself trained to follow trails of related/seemingly related
information, no matter how obscure.
good luck, may the schwartz be with you ! :silly:
m

Xperia L1 open source archive

In case anyone wants to develop a ROM. It is hard to believe there is no development for this phone yet.
https://developer.sonymobile.com/do...archives/open-source-archive-for-43-0-a-4-46/
I have the phone, but I have 0 experience to make custom kernel and recovery, but I found an interesting guide and I am working on it. Hopefully I will make the very first kernel and TWRP based on 43.0.A
https://forum.xda-developers.com/crossdevice-dev/sony/root-root-stock-firmware-modern-sony-t3558904
Wish me success
mingkee said:
I have the phone, but I have 0 experience to make custom kernel and recovery, but I found an interesting guide and I am working on it. Hopefully I will make the very first kernel and TWRP based on 43.0.A
https://forum.xda-developers.com/crossdevice-dev/sony/root-root-stock-firmware-modern-sony-t3558904
Wish me success
Click to expand...
Click to collapse
This guide does not work for MediaTek devices.
The L1 uses a Mediatek SoC...so yes, I wish you luck, but it won't do you any good.
Maybe this is more helpful for you ( us )
https://forum.xda-developers.com/showthread.php?t=2701283
Any custom roms?
Have any custom roms been made available for this phone? I have the G3113 model. I managed to successfully unlock the bootloader and install TWRP recovery, but I'm not able to find any custom roms for this phone in particular. I know it might have something to do with the MediaTek SoC, but was hoping someone would've gotten around that at this point.
Any update on this

Possible to install custom ROMs on K425 (AT&T K10)?

I've had a lot of trouble finding information on this specific model, so I'm wondering if it's possible to install a custom ROM like Cyanogenmod, for instance? I'm willing to answer questions and help out if more info is needed.
Possible maybe, available right now - no.
I don't see any development (at least here) on that model so bad news for you.
Professor Woland said:
Possible maybe, available right now - no.
I don't see any development (at least here) on that model so bad news for you.
Click to expand...
Click to collapse
I am in the process of device bring up for MS428. No ETA for Custom ROM though.

Multiboot multiple OS on Note 8 after January update that changes bootloader

Max Weinbach posted on https://www.xda-developers.com/samsung-galaxy-s8-note8-bootloader-odin/ that Samsung 8/8+/Note 8 January update come with a new bootloader that
1) can not downgrade your phone after installing this
2) block Prince Comsy’s modded Odin.
Max wrote one consequence is: "Note8 owners with the carrier Note8 devices cannot flash the US unlocked firmware. If you try to flash the carrier unlocked firmware on carrier phone, it will hard brick your phone". But later make this correction as an EDIT: After being tested by XDA Senior member me2151, it turns out cross region flashing does work. Prince Comsy Odin is working, but we can not test if the factory binary flashing will hard brick your phone. So flashing US unlocked onto a US carrier device should work.
I will like to buy a Note 8 and what I want to do is have 2 (or more) ROM (OS) and be able to multi boot. I have 4 questions regarding this. With the January update can I use multi boot ROM (MultiROM, DualBootPatcher, or any other) on:
1) The Unlock International Version (install the T-mobile ROM and other ROMs)?
2) The Unlock US Version (install the T-mobile ROM and other ROMs)?
3) The T-Mobile (Snapdragon) version (Install US unlock version ROM and other ROMs)? As far said here: https://www.androidauthority.com/samsung-galaxy-note-8-update-805328/ the T-mobile Janaury update is not out yet for T-Mobile, so a T-Moile Note 8 is not supposed to be affected by it.
The 4th questions is: Lets said I have T-Mobile Note 8, Im succesfull installing a multi boot, I have 3 ROMs simulstaniously. ROM 1 is the T-Mobile ROM that came with the phone, ROM 2 is Unlock US Note 8 ROM and ROM 3 FireFox OS. Everything work fine. Then After that, came out the “January” update for T-Mobile and I installed (because I need to be protected by the vulnerabities if fix). But the update change the bootloader. The question is> Will I be able to multi boot the 3 ROMs, like was doing before instaling the update? Or the 2 non carrier ROMs will be affected by the boot loader change made by the update, and the T-mobile phone will only able to boot to the original T-Mobile ROM that came with the phone? Or when the update change the boot loader will mess (probably brick) the whoe phone not letting me to boot what ever ROM it have (the T-Mobile and and the other 2 ROMs)

			
				
I'm sorry not meaning to sound rude but I almost fell asleep midway through reading your post... 1st of all from what I gathered your buying a international note 8? And then want to flash multiboot which I personally only used when running touchwiz Rom and say a ASOP Rom if you will... but you need to keep in mind that your not gonna find too many roms over here on the snapdragon devices. I will tell you if you want to utilize multiboot then don't buy a Samsung. I used multiboot on my LGv20 having stock rooted as my daily and Lineage as my 2nd.
SICKMADE said:
I'm sorry not meaning to sound rude but I almost fell asleep midway through reading your post... 1st of all from what I gathered your buying a international note 8? And then want to flash multiboot which I personally only used when running touchwiz Rom and say a ASOP Rom if you will... but you need to keep in mind that your not gonna find too many roms over here on the snapdragon devices. I will tell you if you want to utilize multiboot then don't buy a Samsung. I used multiboot on my LGv20 having stock rooted as my daily and Lineage as my 2nd.
Click to expand...
Click to collapse
I was told that Snapdragon Note 8 (US unlock and US carrier) does not have unlocked boot loader, therefore is impossible to multiboot.
The question is if the Exynos model could be used to multiboot?
The #1 reason I decided against the international model was issues with Carrier Aggregation I even asked the question in this forum and the international forum about if any fix had been found...I just wasn't willing to shell out that kind of money and not have the phone work properly switching between towers. I went with a US unlocked version...should be here Thursday.
in regards to multi-boot...I believe that would be processor dependent (someone please correct me if I am wrong.) and thus you would need to inquire in the international forum if there is a multi-boot for the exynos chipsets.

Categories

Resources