hi so i bought OP3T to have nethunter on it. but now i am totally confused how to install nethunter on my device properly, there needs to be an updated guide about it that i couldn't find in xda forums.
first about my phone:
it's OP3T on nougat, OOS 4.1.7 . currently i'm using latest official LOS 14.1 rom.
with Encryption enabled, on LOS stock kernel.
What i tried is this thread,
https://forum.xda-developers.com/oneplus-3t/development/kernel-kali-nethunter-oneplus-3t-t3507816
and i downloaded
nethunter-generic-arm64-kalifs-full-rolling-3.20-20170903-2143.zip
kernel-nethunter-oneplus3T-cm-nougat-3.20-20170903-2143.zip
by following above guide i went into TWRP recovery i flashed kernel which also flashed supersu with it, and then flashed kali nethunter,
everything went perfect, no problems, but i can't use kali nethunter, its terminal does not open,
on above thread @uaiclout pointed to following thread to use that build,
https://forum.xda-developers.com/oneplus-3/development/kernel-boeffla-kernel-linaro-uber-t3455888/
but when i went to that thread that is a kernel and not a rom, and not a nethunter build,
i don't understand what do i have to do to make NetHunter work properly? and there is no specific thread / guide on it. i don't wanna brick my phone so taking my steps carefully, as i am new in OP3T and coming from Samsung devices there are some new strange abbreviations being used in OP3T forums which i don't know what they mean.
like bootloader thing is not being mentioned in OP3T forums but firmwares (i am confused what they are?) and like kernels are using some strange terms,
so it will be very thankfull for someone who uses NetHunter on OP3T successfully to create a guide or atleast tell others how you made it work on nougat LOS or other non-stock based custom roms? and kernels + wifi devices to be detected on phone like TL-WN722N ?
thanks in advance.
Hello Mate,
Welcome to the OnePlus fam!
So as I've understood, your Kali Terminal is not working. I've had the exact issue, and I fixed it by reinstalling the Terminal apk ;(https://github.com/offensive-securi...thunter-installer/update/data/app/Term-nh.apk)
If you're getting a chroot error, uninstall the chroot, and re-download it from Chroot Manager.
To correct your misunderstandings, Firmware is the base software of the phone, which has Modem information, etc etc. Firmware is released by OnePlus, and it has minor changes and tweaks with every new version. Developers can choose any Firmware version to build their ROM over it. So if you're installing a new ROM, make sure to check the Firmware version. If your current firmware version is below the required version for the ROM, TWRP will give you a "Error=7" when flashing the ROM.
Kali Nethunter is a Kernel for OP3/3T, not a ROM. Make sure you've flashed the correct Zip file, as there are many versions, one for OOS stock, another for LOS, and so on and on.
Also for using Kali for Wi-Fi related purposes, I must warn you that it is not legal, but if you must, then there is a specific Wi-Fi adapter to be used with the 3/3T. I will update you on what the exact model is, and it is quite inexpensive on eBay.
I advise you to use Kali on OOS, rather than LOS, as it is more stable on OOS.
Cheers!
thes3usa said:
Hello Mate,
Welcome to the OnePlus fam!
So as I've understood, your Kali Terminal is not working. I've had the exact issue, and I fixed it by reinstalling the Terminal apk ;(https://github.com/offensive-securi...thunter-installer/update/data/app/Term-nh.apk)
If you're getting a chroot error, uninstall the chroot, and re-download it from Chroot Manager.
To correct your misunderstandings, Firmware is the base software of the phone, which has Modem information, etc etc. Firmware is released by OnePlus, and it has minor changes and tweaks with every new version. Developers can choose any Firmware version to build their ROM over it. So if you're installing a new ROM, make sure to check the Firmware version. If your current firmware version is below the required version for the ROM, TWRP will give you a "Error=7" when flashing the ROM.
Kali Nethunter is a Kernel for OP3/3T, not a ROM. Make sure you've flashed the correct Zip file, as there are many versions, one for OOS stock, another for LOS, and so on and on.
Also for using Kali for Wi-Fi related purposes, I must warn you that it is not legal, but if you must, then there is a specific Wi-Fi adapter to be used with the 3/3T. I will update you on what the exact model is, and it is quite inexpensive on eBay.
I advise you to use Kali on OOS, rather than LOS, as it is more stable on OOS.
Cheers!
Click to expand...
Click to collapse
now i am on latest PA official rom, i'm gonna try again. i like non-stock based roms because they allow device encryption with root (which stock roms don't allow) and i always keep my device encrypted as a security and ethical hacking student . i try to secure my devices from every new hack i learn. but i heard when you install NetHunter on Android, its security is compromised already, anyways,
as i mentioned the zips i downloaded from NetHunter builds, do you see any wrong zip? i downloaded kernel for CM based roms and also generic NetHunter,
which exactly Rom+Kernel combinations you have if you are using NetHunter? my device was on OOS 4.1.7 before i installed LineageOS 14.1 official on it. so suggest me the better OOS? and i will have to download anyway coz i lost my original backup of stock OOS 4.1.7 .
about wifi devices, i have 3 devices.
1. TP-LINK TL-WN722N
2. ALFA AWUS036H
3. ALFA AWUS036NH
none of them was detected by NetHunter app info screen, i heard on kali nethunter thread that TP Link TL-WN722N works, but it was not detected. but i can buy new device if needed, thats not a big issue, though it would be better if i can make one of above device to work with it. and there is a discussion on it that i will check if my NetHunter works properly first.
about the firmwares, i still don't get it, correct me if i'm wrong,
let say my phone was on OOS 4.1.7 when i bought it, then i rooted and installed TWRP on it, then i installed LineageOS 14.1 on it. so technically i am still on firmware 4.1.7 ? is that what you mean?
so if i want to install CM 13 on my device i will have to check what firmware is CM 13 build upon and flash that firmware before i flash CM 13 ? is that right?
so there is no trouble of bootloaders in OP3T as it was in samsung ? like in note 5 i upgraded to nougat and then i wanted to go back to lollypop but i couldn't because newer bootloader didn't allow me to go back, and i had to do some exercise to downgrade bootloader to lollypop before i could install any lollypop rom. so in OP3T firmware is to be flashed before installing certain roms is same like bootloaders was in samsung?
is it safe always to go back and forth in firmware flashings? if i wanna install lollypop rom i just flash that firmware which that rom is built upon and i am good to go? and then if i want to come back to nougat rom i just flash specific firmware and i'm good to go? (i know i am totally confused in this system, but i think i got it right now?). please confirm if all i said about firmwares is right or wrong so i can understand :fingers-crossed:
thanks
It sounds like the issue is that you are using PA. Their source is usually not CM/LOS based. I don't know about the newest versions though or if NetHunter has a PA compatible version.
Sent from my OnePlus 3T using XDA Labs
MrMeeseeks said:
It sounds like the issue is that you are using PA. Their source is usually not CM/LOS based. I don't know about the newest versions though or if NetHunter has a PA compatible version.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
no no, i am now on PA, but i tried NetHunter in LOS official 14.1
Related
Hi everyone, so some mistakes have been made today. While playing around with substratum theme engine on my mix running lineage-os 14.1, i had uninstalled one of the themes and then decided to uninstall the app entirely, however after uninstall it didnt reset the theme, so i rebooted. While attempting to reboot it got stuck in a boot loop. At this point I plugged my phone into my pc and booted into twrp so i could access my files and get them off, however when attempting to boot into twrp i could not use the touch screen which is preventing me from re-flashing my rom. and so after troubleshooting for an hour or soi had all my files off of my device, so i decided to format the system partition. so now i have no rom flashed and a twrp that i cannot use due to lack of touchscreen, its temporarily bricked i guess. So my questions are; A. can i use an otg cable and a mouse to control twrp? B. Is there some way to directly flash a rom from adb or from the connected pc. Then I should also state that I have tried older/newer versions of twrp to try to get the touchscreen working, to no avail (currently running 3.1.1-0 lithium). Ive read that it may be touchscreen drivers or something that are mis-matched from the rom. the onlyt issue is that there is no rom, also ive heard that the touchscreen is at a kernel level so i may need to flash a new kernel to get it working. TBH im not going to do anything else so that i dont completely brick my phone. Thank you all in advance for helping out!
Please try this (older) TWRP by MrRaines: https://www.androidfilehost.com/?fid=673368273298927160
It's TWRP 3.0.2-0 based but has different kernel/driver that is more compatible with a varous bunch of ROMs.
You're a god, this is exactly what I needed, thanks!!!
raupe said:
Please try this (older) TWRP by MrRaines: https://www.androidfilehost.com/?fid=673368273298927160
It's TWRP 3.0.2-0 based but has different kernel/driver that is more compatible with a varous bunch of ROMs.
Click to expand...
Click to collapse
I LOVE you, spent hours trying to get recovery working. This was the only fix!
Thank you so much brother.
kanej2006 said:
I LOVE you, spent hours trying to get recovery working. This was the only fix!
Thank you so much brother.
Click to expand...
Click to collapse
Ok glad to read that it works.
Please keep in mind: the TWRP of MrRaines is an older one and is heavily modified.
ATM i'm trying to investigate what's the specific reason other TWRP versions are conflicting with touchscreen drivers on every new release of an stable or dev rom but MrRaines TWRP is still working ^^
The TWRP compatibility case has become even worse with the release of some Android 7.x / Nougat based ROMs - without an official kernel source release for Android 7 by Xiaomi (Android 6 kernel sources should have been released some weeks ago).
Could take a couple of days to find a reason and some more to find a solution...
... any help, tips and confidential information is very welcome @MrRaines @jcadduono
raupe said:
Ok glad to read that it works.
Please keep in mind: the TWRP of MrRaines is an older one and is heavily modified.
ATM i'm trying to investigate what's the specific reason other TWRP versions are conflicting with touchscreen drivers on every new release of an stable or dev rom but MrRaines TWRP is still working ^^
The TWRP compatibility case has become even worse with the release of some Android 7.x / Nougat based ROMs - without an official kernel source release for Android 7 by Xiaomi (Android 6 kernel sources should have been released some weeks ago).
Could take a couple of days to find a reason and some more to find a solution...
... any help, tips and confidential information is very welcome @MrRaines @jcadduono
Click to expand...
Click to collapse
Just see the kernel img, ramdisk and boot files/blobs
raupe said:
Ok glad to read that it works.
Please keep in mind: the TWRP of MrRaines is an older one and is heavily modified.
ATM i'm trying to investigate what's the specific reason other TWRP versions are conflicting with touchscreen drivers on every new release of an stable or dev rom but MrRaines TWRP is still working ^^
The TWRP compatibility case has become even worse with the release of some Android 7.x / Nougat based ROMs - without an official kernel source release for Android 7 by Xiaomi (Android 6 kernel sources should have been released some weeks ago).
Could take a couple of days to find a reason and some more to find a solution...
... any help, tips and confidential information is very welcome @MrRaines @jcadduono
Click to expand...
Click to collapse
Hmmm. I did try two or even three other versions of TWRP. The first two would not even flash giving me an error. The third worked but touch screen would not work. Final attempt was the one from MrRaines which worked perfect!
so i bought note 5 SM-N920T which was already on android 7 latest firmware according to sammobile website.
and there are only handful of custom roms (not stocked based but those which occur in original android development).
and all of them have serious issues,
like lineageOs 14.1 has no audio in call, battery drain issues, flash light issue, doesn't take images in dark somehow flash work when you take image but the end image is dark. etc.
and others also have similiar issues.
My requrements for a rom are following.
1. no matter stock based or not, it should have root and MUST SUPPORT ENCRYPTION after root (no matter if i have to flash any kernel or do any gymnastics, i am willing to do it to get to this requirement.
2. it should be fully stable, atleast all basic features should be stable like phone calling, sms, bluetooth, wifi, and others which are necessary for a daily life smart phone.
well that is all because i have xposed in my requirement but xposed is not available for 7 yet so leave it out.
now let see.
stock based custom roms (those i checked) does not support encryption after you root them, and if you encrypt them before rooting, then because their encryption method is such that TWRP don't mount data, so root is impossible after encryption, even i tried that magisk trick of cache workaround, it does not work. after i flash magisk to an encrypted rom, when i get to the point of entering password for encryption, rom says there has been some integrity issues with encryption and you can no longer decrypt, you have to reset the device to factory.
and if i root a stocked based rom before encrypting then they don't encrypt at all.
then there are custom roms like lineageOS. they support encryption with root and their encryption method is also supported in TWRP.
BUT
they are not stable to use as a daily driver.
so can anyone please tell me how can i achieve my requirement on note 5 SM-N920T ? any rom? any kernel / rom combinations ? anything?
or should i sell my note 5 and buy a better device?
thank you for your answers in advance.
Actually PurifyOS has an unofficial Xposed port that works just fine for the 920T, I've been using it for a month. When I flashed Lineage the flashlight and in-call audio worked just fine. Battery drain wasn't very noticeable, but every time the screen turned off while I listening to music my viper and Dolby apps stopped processing.
There's a very stable rom that has very close to stock battery drain, it's the Khongloi S8+ rom in this forum.
buy a better,newer device
Metabolic12 said:
Actually PurifyOS has an unofficial Xposed port that works just fine for the 920T, I've been using it for a month.
Click to expand...
Click to collapse
i can't find PurifyOS somehow, tried search in forum and also google, PurifyOS website is down.
is it a ROM or just xposed to flash in any ROM ? i will really apreciate if you can tell me about it? and if you can also share a link of PurifyOS for note 5 SM-N920T ?
Metabolic12 said:
When I flashed Lineage the flashlight and in-call audio worked just fine. Battery drain wasn't very noticeable, but every time the screen turned off while I listening to music my viper and Dolby apps stopped processing.
Click to expand...
Click to collapse
i don't know how is that possible that i have many issues and you don't have them, i am on latest firmware / bootloader QG3 on my SM-N920T. and i flashed cleanly LineageOS 14.1 on it with or without root and without any kernel. still i have all the issues with flashlite, music app, camera dark images, mic not working in calls initiated by me and also on internet calls, and very high battery drain with only one app that is Conversations.
can you tell me which lineageOS version are you using? i am using 14.1 from following link.
https://forum.xda-developers.com/note5/orig-development/rom-lineageos-14-1-t3572047
Metabolic12 said:
There's a very stable rom that has very close to stock battery drain, it's the Khongloi S8+ rom in this forum.
Click to expand...
Click to collapse
have you tried it? does device encryption work with having a root?
https://forum.xda-developers.com/xposed/xposed-android-nougat-sdk-25-arm64-t3639221
There's the thread for xposed. If you have the latest firmware release from T-Mobile, I'm pretty sure Lineage won't flash over that bootloader. I had to roll back my bootloader to flash it, but Rayman fizzled the problems you were explaining in his second release for the 920T.
As for re-encrypting a device with root I have no never done it. I enjoy flashing roms and custom kernels so once I break encryption and DM-Verity on my devices I leave them that way. I'm pretty sure, don't quote me though, that with supersu you cannot restore encryption while you're rooted. I don't Magisk so you may want to look into that. Hope this helps bro.
Metabolic12 said:
https://forum.xda-developers.com/xposed/xposed-android-nougat-sdk-25-arm64-t3639221
There's the thread for xposed. If you have the latest firmware release from T-Mobile, I'm pretty sure Lineage won't flash over that bootloader. I had to roll back my bootloader to flash it, but Rayman fizzled the problems you were explaining in his second release for the 920T.
Click to expand...
Click to collapse
thank you for the link.
i am already on latest lineageOS 14.1 and it is flashable on latest bootloader. which second release are you talking about that has fixed those issues.?
I used Smartswitch to upgrade my Tab A to 7.1.1 and decided to give rooting a try. I flashed CF Autoroot (CF-Auto-Root-gt58wifi-gt58wifixx-smt350) with ODIN which was successful in installing SU and giving me root. Confirmed using Titanium Backup and FolderMount.
Have you found something to change the lock screen clock design? I hate the hours & minutes arranged vertically.
Sent from my ONEPLUS A5000 using Tapatalk
SM-T550 Still waiting grrrrrr
trying to build custom ROM for it (using either Superr Kitchen or ASSAYYED KITCHEN) , but does not look like working, it bootloops, I know there's custom ROM done for 7.0 (@luattic ), but not sure why it does not works for 7.1.1., haven't check with @ashyx for his feedback
funny thing is that you can flash offical firmware of SM-T350 7.1.1, and then flash @ashyx TWRP 3.1.0-1, and then flash latest super su, it all good...it just when build custom ROM for 7.1.1 does not works...i wonder if these ROM kitchen does not include latest superSU or maybe something else
jazzespresso said:
trying to build custom ROM for it (using either Superr Kitchen or ASSAYYED KITCHEN) , but does not look like working, it bootloops, I know there's custom ROM done for 7.0 (@luattic ), but not sure why it does not works for 7.1.1., haven't check with @ashyx for his feedback
funny thing is that you can flash offical firmware of SM-T350 7.1.1, and then flash @ashyx TWRP 3.1.0-1, and then flash latest super su, it all good...it just when build custom ROM for 7.1.1 does not works...i wonder if these ROM kitchen does not include latest superSU or maybe something else
Click to expand...
Click to collapse
Haven't even started on the custom rom I was going to make, updating at the moment, but can you help me out? Haven't been learning about Android Development yet and still trying to learn Java and Kotlin (don't know any at the moment too). Thanks if you reply back.
Confirmed worked for me to even though chainfire site says for marshmallow
I wasn't able to root my sm-t350 until I upgraded to 7.1.1 it was a brand new device as of yesterday. I tried just about any method I could find, was about to give up then I took it from 6.x.x to 7.1.1 and then the method you mentioned above and boooooyah....
jazzespresso said:
trying to build custom ROM for it (using either Superr Kitchen or ASSAYYED KITCHEN) , but does not look like working, it bootloops, I know there's custom ROM done for 7.0 (@luattic ), but not sure why it does not works for 7.1.1., haven't check with @ashyx for his feedback
funny thing is that you can flash offical firmware of SM-T350 7.1.1, and then flash @ashyx TWRP 3.1.0-1, and then flash latest super su, it all good...it just when build custom ROM for 7.1.1 does not works...i wonder if these ROM kitchen does not include latest superSU or maybe something else
Click to expand...
Click to collapse
7.1 changed a lot of the filesystem and policy layout. That is probably why the custom rom kitchens aren't quite working all the way then. I do believe you do need to use at least SuperSU 2.8 on Nougat builds of android, 2.82 is a super decent build to run on Nougat 7.0 and 7.1.1
Does anyone have a no pc method? My computer is slow af.
Is smartswitch the built in updater? That modal that pops up saying there is an update available?
DeepWideBellWonder said:
Does anyone have a no pc method? My computer is slow af.
Click to expand...
Click to collapse
What difference does that make, you're only downloading it?
Have you found a TWRP package which is compatible with the SM-T350 running Nougat 7.1.1?
Have you done it with Galaxy Tab A 8.0 2017?
---------- Post added at 11:02 AM ---------- Previous post was at 10:57 AM ----------
rgp1236 said:
I used Smartswitch to upgrade my Tab A to 7.1.1 and decided to give rooting a try. I flashed CF Autoroot (CF-Auto-Root-gt58wifi-gt58wifixx-smt350) with ODIN which was successful in installing SU and giving me root. Confirmed using Titanium Backup and FolderMount.
Click to expand...
Click to collapse
Have you used the Galaxy Tab A 8.0 2017 version? If not, will it work with it? It runs 7.1.1 too.
Bricked my last tablet just bought a sm-t350 with 7.1.1
I have a sm-t350 running 7.1.1. I’ve searched everywhere for step by step instructions on how to root my tab. If somebody could please point me in the right direction that would be very helpful. Very interested in what android has to offer. Doing as much research as I can but nervous since I hard bricked my last device thanks
Cbr100091 said:
I have a sm-t350 running 7.1.1. I’ve searched everywhere for step by step instructions on how to root my tab. If somebody could please point me in the right direction that would be very helpful. Very interested in what android has to offer. Doing as much research as I can but nervous since I hard bricked my last device thanks
Click to expand...
Click to collapse
Referring to @jazzespresso above...
I am waiting to hear back from @ashyx on the latest TWRP build for the T350. From there, it's a simple matter to flash via Odin and then zip install SuperSU 2.82 via TWRP.
Edit:
TWRP v3.1.0-1 is available for DL to T350. From there, just follow instructions above to root.
Help
Download link to TWRP?
there where
Edit:
TWRP v3.1.0-1 is available for DL to T350. From there, just follow instructions above to root.
gr1mr34p3r said:
Have you found a TWRP package which is compatible with the SM-T350 running Nougat 7.1.1?
Click to expand...
Click to collapse
i need to know this also,..
This did root my device, but resulted in some strange behavior. When I restart the tablet, some apps are randomly deleted on startup. Any ideas?
Hello, I cannot give root access to my device Samsung Tab A SM T350. My device now has version 7.1.1. How do I root the device?
Hello,
my friend has a Samsung galaxy note 8 with the model SM-N950F and he was thinking about giving me his phone to install a custom ROM for him, the phone is running stock ROM.
my question is what is the most stable android 12/13 Rom ( AOSP ) that doesn't require rooting and has banking apps and the pen working fine, also what is the latest stable TWARP and Odin that works for that model ( because I had SM-G530h and some Odin versions didn't work with it ).
one more question is it available to go back to Stock ROM once again using Odin like with old Samsung phones and where can I find a trusted source as Sammobile doesn't seem to work for me for some reason?
thanks in advance for your help.
KingDark2010 said:
Hello,
my friend has a Samsung galaxy note 8 with the model SM-N950F and he was thinking about giving me his phone to install a custom ROM for him, the phone is running stock ROM.
my question is what is the most stable android 12/13 Rom ( AOSP ) that doesn't require rooting and has banking apps and the pen working fine, also what is the latest stable TWARP and Odin that works for that model ( because I had SM-G530h and some Odin versions didn't work with it ).
one more question is it available to go back to Stock ROM once again using Odin like with old Samsung phones and where can I find a trusted source as Sammobile doesn't seem to work for me for some reason?
thanks in advance for your help.
Click to expand...
Click to collapse
Your question is a contradiction. You're asking whether you can use a custom ROM without root but still pass Play Integrity and other checks? This is not possible. Simply having an unlocked bootloader makes your device fail. To pass Play Integrity and be able to use banking apps, the Universal SafetyNet Fix module is required for use with Magisk. Further, AOSP does not include any of the "frills" that Samsung preloads into their firmware, meaning that not all features may work, including the S Pen. If you want to try AOSP anyway, you can follow my guide here to install an AOSP GSI.
As for returning your device to stock using Odin, yes. Sammobile is a good source, but if it doesn't work for you, you can try Frija or Samfirm.js to download the firmware directly from Samsung's servers.
V0latyle said:
Your question is a contradiction. You're asking whether you can use a custom ROM without root but still pass Play Integrity and other checks? This is not possible. Simply having an unlocked bootloader makes your device fail. To pass Play Integrity and be able to use banking apps, the Universal SafetyNet Fix module is required for use with Magisk. Further, AOSP does not include any of the "frills" that Samsung preloads into their firmware, meaning that not all features may work, including the S Pen. If you want to try AOSP anyway, you can follow my guide here to install an AOSP GSI.
As for returning your device to stock using Odin, yes. Sammobile is a good source, but if it doesn't work for you, you can try Frija or Samfirm.js to download the firmware directly from Samsung's servers.
Click to expand...
Click to collapse
Frija is faster and I recommend it. SAMMobile forces users to register to their website and limit your DL-speed.
It's not strictly required to use Magisk. Some Custom ROMs by default spoof SafetyNet Attestation to BASIC and don't need Magisk.
But in the case of Custom ROMs like LineageOS (which doesn't spoof/hide the Unlocked Bootloader on purpose!), or Stock OneUI ROM, you do need to use Magisk + "MagiskHide Props Config" Magisk Module and set the fingerprint to Note8. If Note8 isnt available as a fingerprint, use SafetyNet-Fix Module.
Also, I don't use my Note 8 anymore, but we have Custom ROMs for Note8. I see we have LineageOS 20.0. Why use GSIs? They are much more unstable and buggy.
cyanGalaxy said:
Frija is faster and I recommend it. SAMMobile forces users to register to their website and limit your DL-speed.
It's not strictly required to use Magisk. Some Custom ROMs by default spoof SafetyNet Attestation to BASIC and don't need Magisk.
But in the case of Custom ROMs like LineageOS (which doesn't spoof/hide the Unlocked Bootloader on purpose!), or Stock OneUI ROM, you do need to use Magisk + "MagiskHide Props Config" Magisk Module and set the fingerprint to Note8. If Note8 isnt available as a fingerprint, use SafetyNet-Fix Module.
Also, I don't use my Note 8 anymore, but we have Custom ROMs for Note8. I see we have LineageOS 20.0. Why use GSIs? They are much more unstable and buggy.
Click to expand...
Click to collapse
LineageOS is largely developed as a GSI. Yes, in many cases, it is bundled with a device specific kernel as a complete ROM, but for Project Treble compliant devices, a Generic System Image is just that - a single generic system image that does not have any device specific functions and can be used with any kernel on any device. In that regard, the official AOSP GSIs are very stable, and any issues are usually involved with the kernel, not the system image.
KingDark2010 said:
Hello,
my friend has a Samsung galaxy note 8 with the model SM-N950F and he was thinking about giving me his phone to install a custom ROM for him, the phone is running stock ROM.
my question is what is the most stable android 12/13 Rom ( AOSP ) that doesn't require rooting and has banking apps and the pen working fine, also what is the latest stable TWARP and Odin that works for that model ( because I had SM-G530h and some Odin versions didn't work with it ).
one more question is it available to go back to Stock ROM once again using Odin like with old Samsung phones and where can I find a trusted source as Sammobile doesn't seem to work for me for some reason?
thanks in advance for your help.
Click to expand...
Click to collapse
To be able to use Banking Apps, the following practices are good.
Passing SafetyNet (you can check this with YASNAC from Play Store).
If you don't pass SafetyNet, use Magisk with one of the 2 modules mentioned above.
You may also need to enable Zygisk, Enforce DenyList, and add your Banking Apps to Magisk DenyList.
I use a Xiaomi Poco F3 with ArrowOS Custom ROM, it already contains patches to force SafetyNet to BASIC, and so I dont need any modules, but only Zygisk, Force DenyList, and add my Banking Apps to the DenyList and reboot ^^
V0latyle said:
LineageOS is largely developed as a GSI. Yes, in many cases, it is bundled with a device specific kernel as a complete ROM, but for Project Treble compliant devices, a Generic System Image means the system image can be used with the OEM kernel on any device, because everything specific to that device is contained within the kernel. In that regard, the official AOSP GSIs are very stable, and any issues are usually involved with the kernel, not the system image.
Click to expand...
Click to collapse
My Xiaomi Poco F3 (2021) supports Treble and GSI's are not at all usable/daily-drivable. Scratchy Sound, Missing Vibration etc..
cyanGalaxy said:
My Xiaomi Poco F3 (2021) supports Treble and GSI's are not at all usable/daily-drivable. Scratchy Sound, Missing Vibration etc..
Click to expand...
Click to collapse
What GSIs have you tried? I suspect that the device kernel is not fully Treble compliant.
V0latyle said:
What GSIs have you tried? I suspect that the device kernel is not fully Treble compliant.
Click to expand...
Click to collapse
V0latyle said:
What GSIs have you tried? I suspect that the device kernel is not fully Treble compliant.
Click to expand...
Click to collapse
Generic System Image releases | Platform | Android Developers
developer.android.com
The official Googley ones. Tho I don't mind, since I use an AOSP Custom ROM anyway (on my Xiaomi phone). My Note 8 is kept on OneUI 1.0... i miss the "Samsung Experience" dayz.. Yknow, the OS that came after TouchWiz. It had a rather professional-looking boxy design. Don't like the Huge padding and Rounded Corners of OneUI. The modern OneUI versions are also eh. Due to Samsung stuffing additional apps like TikTok and other rubbish as pre-installed apps.
cyanGalaxy said:
Generic System Image releases | Platform | Android Developers
developer.android.com
The official Googley ones. Tho I don't mind, since I use an AOSP Custom ROM anyway (on my Xiaomi phone). My Note 8 is kept on OneUI 1.0... i miss the "Samsung Experience" dayz.. Yknow, the OS that came after TouchWiz. It had a rather professional-looking boxy design. Don't like the Huge padding and Rounded Corners of OneUI. The modern OneUI versions are also eh. Due to Samsung stuffing additional apps like TikTok and other rubbish as pre-installed apps.
Click to expand...
Click to collapse
Huh. I've used both the "pure" GSIs from Android CI, as well as the Android Developer GSIs on my Tab A 8.0 with the CUK4 kernel. Everything works like it should. Make sure you're using the correct architecture and bitness for your device - most are arm64 - but in the off case that your Xiaomi isn't ARM, there will likely be a lot of issues.
Remember that while a Treble kernel should run any GSI, you still have to wipe data. You can't go from OEM firmware to GSI or vice versa without a data wipe; that cause a a lot of stability issues.
thanks for the replays and information guys regarding official releases of AOSP ROMs I haven't seen one that is higher than android 9 ( which is mainly the reason why we want to install a higher version due to compatibility issues with the company portal apps ) so any idea what is the most stable ROM for that model running android 10 or above
I want to install Kali Nethunter on my rooted OP3T. How ever the download page says "OnePlus 3/3T (Ten)," Should this work on LineageOS 18.1 despite it being 11? I don't really want to have to wipe and flash a different ROM just to install it, especially since stock ROM only goes to Pie. If so, can anyone give me a fairly up-to-date tutorial on how to install it? I'm currently watching this David Bombal video on how to install it on a 7T, and I am hoping the install instructions would be the same. (yes, I did post this on another OP3T forum, but realised it was the wrong one and am awaiting it to be removed)
Do you have any updates on it? Asking cuz I couldn't find any available LineageOS based on Android 10 to download.
lemongrass1717 said:
Do you have any updates on it? Asking cuz I couldn't find any LineageOS based on Android 10 to download.
Click to expand...
Click to collapse
Nah, I've sorta given up on the project. Maybe try and find a LOS 14.1 download? Apparently this uses Ten and works with NetHunter
I discovered 17.1 uses 10 Android, not sure if NetHunter supports it. But few years ago I tried to run NetHunter on not officially supported device, it kinda worked but required LineageOS + generic NetHunter + custom kernel. Maybe it'll work for 3T.