Related
I build the AOSP successfully but in my case the microphone is buggy ... everything else is working. Is there Anyone who build it with a working mic? I've build r30 and r32 with the same result :/
I have not yet. Ordered my XZ1c yesterday. Should be here Monday. Hoping for more developer colaberation. Thank You for working on this!
Because of Treble it should be possible to build Lineage OS without interfering with the fingerprint sensor and T-Mobile VoLTE functionality, no?
Can I ask, how is the camera on the AOSP build? Is it still the ****ty quality/green blob effect camera? I want to desperately have root on my xz1 and I know I can have it with AOSP but I don't want to sacrifice the camera.
N1ghtr08d said:
Can I ask, how is the camera on the AOSP build? Is it still the ****ty quality/green blob effect camera? I want to desperately have root on my xz1 and I know I can have it with AOSP but I don't want to sacrifice the camera.
Click to expand...
Click to collapse
It's still going to be bad. Until we get a proper DRM backup method all custom ROMs will take awful photos.
Issues Flashing Build
Hi there -
If you don't mind me asking, did you run into any issues when flashing the build? I was able to build android-8.0.0_r30 successfully. After flashing android-8.0.0_r30, my phone boots to a screen covered in distorted colors. There is a small message, but most of it is cut off. From what I can tell, it seems that something is corrupt, or so I believe the partial message said.
Did you run into any issues while flashing?
Could you please offer some insight into your process?
Thank you for your time,
Dominic
[Edit]
I am getting the same screen of distorted color after the Sony screen when flashing android-8.1.0_r7.
Before flashing again this time, I went to another machine and used Sony's flashing tool, Emma, to flash a stock Sony ROM back to the device. This allows me to boot to what I assume is Sony's most current build available. The phone boots no problem this way. I decided to try another flash.
My specific steps for flashing post build:
sudo fastboot flash boot boot.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img
sudo fastboot flash oem SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v05_yoshino.img
[Edit]
I am able to successfully use Sony's Flash Tool, Emma, on a separate system to get the phone booting to the stock ROM. Emma shows the following under Software:
Application Software:
1307-7511 47.1.A.8.49
[(Delayed) Edit]
I rebuilt AOSP from source and was able to successfully boot into the OS after flashing the partitions.
Maybe a corrupt image was generated during the build process.
Either way, I am updating this in case anyone else comes across it. Downloading the source and rebuilding it resolved the issue.
Aosip for Motorola Z2 Force
What is this?
AOSiP is a quality custom ROM based purely on GOOGLE AOSP source since 6.0 release. Twisted with the latest features and blended with stability. We strive for perfection and it shows.
Obligatory Warning: This guide and ROM assumes you know the fundamentals of fastboot, flashing TWRP, and running a flash all. Your warranty is voided because of the unlocked bootloader. This is a Third Party ROM. Things may not work as expected compared to stock (for better or for worse).
Warning 2: If you can't do fastboot commands, do a flash all, root your device or flash TWRP/ROM, please do not ask for help here. If you cannot flash all back to stock, please stay stock for everyone's sake.
Warning 3: if you don't flash the firmware so you are on Oreo on both slots, when you boot after flashing, you'll be on Nougat firmware and have a brick. Try a flash all as that's your only hope on recovering your phone.
How to install
1. Download the latest ROM from here.
2. Prepare your phone for AOSP style ROMs. (download one of the firmwares depending on your model)
Flash the firmware with the .bat file. (See links below or on Post #2)
3. Boot to TWRP
4. Flash TWRP to boot image (with the zip from their website.) Reboot to Newly flashed recovery.
5. Erase oem, data, and system
6. Flash rom like you would any aosp rom, in twrp.
7. Reboot to bootloader
8. run the command "fastboot -w" (this will erase EVERYTHING from your phone, even internal SD, but is needed to have these ROMs work)
9. reboot.
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Volte (T-Mobile)
Change quick charge
Fingerprint reader
NFC
Lights
Sound / vibration
Some motomods (soundboost mod doesnt work)
Team Illusion:
Josh Fox (xlxfoxxlx)
Akhil Narang
Sri Harsha (@srisurya95)
Shreesha Murthy
Brett Montague
Known issues
1. WiFi Calling hit and miss
2. Cannot flash Gapps (included temporarily)
3. some Audio recording apps will not have audio recording work (phone functions fine)
4. if you don't fastboot -w, you will not boot.
5. if you don't flash the firmware your bootloader might relock itself and be stuck on Nougat.
6. SElinux is passive (meaning CTS check will always fail until further notice.)
Downloads:
official link(aosiprom.com)
​Thanks to everyone at @aosip @mosimchah @moto999999 and @codeworkx for their amazing work
Android OS version: 8.1.0
Security patch level: April 2018
Build author: @Infect_Ed
Source code: https://github.com/AOSiP-Devices/device_motorola_nash - AOSiP source.
https://github.com/InvictrixRom-devices/kernel_motorola_nash - kernel
https://github.com/TheMuppets/proprietary_vendor_motorola - vendor blobs
Contributors
@Infect_Ed @invisiblek @npjohnson @erfanoabdi @joemossjr @jbats @nathanchance
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.4.x
Phone Firmware Required: 8.0
T-Mobile
Sprint
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2018-03-28
Created 2018-03-28
Last Updated 2018-04-10
Note: I did not build this. If you want to give thanks for this ROM build, thank @Infect_Ed for building AOSiP, I am just maintaining the support thread for XDA.
Firmware files needed!
T-Mobile:27.1
Sprint: Found em!
Sources Post:
https://github.com/AOSiP-Devices/device_motorola_nash - AOSiP source.
https://github.com/InvictrixRom-devices/kernel_motorola_nash - kernel
https://github.com/TheMuppets/proprietary_vendor_motorola - vendor blobs
Bug reports:
If you don't flash the firmware and your other slot is nougat, after flashing the ROM, you'll brick. (Custom ROM with a locked nougat slot.) Your only hope is attempting an official flash all and try again after flashing the firmware zip in the posts above.
Fair warning and off-topic: I am okay with some off topic questions. If you have a question, please use the search function. If I have addressed the question before, I will not answer and advise to find it in the thread. I will report the post for a mod to delete along with my response to keep the thread tidy. It seems some users think this ROM has international support. It doesn't and won't unless someone with another variant or an unlocked T-Mobile/Sprint model tests, confirms and debugs for that international carrier. Please keep in mind of what I said below regarding this. I posted this on page 20 or so and copying here for better visibility.
Your SIM is locked. You are trying to run a phone off it's intended network. Please don't post those problems here. It isn't ROM related. Like the thread states. It works for T-Mobile and Sprint only on their respective models on their locked networks. Any other tom foolery isn't supported and must be kept out of the thread. After this it will be considered off topic.
Edit: if you have Sprint or T-Mobile service and run into issues with using your (albeit, expensive) international roaming plan, I will assist with that if it works on stock but not AOSP. If you don't have a sprint or T-Mobile sim, I cannot help. Almost all devs on this device won't be able to help. "Almost" all of us are on US carriers.
Click to expand...
Click to collapse
Images posted here
@Uzephi is your device on sprint? Data works but LTE does not? Does the Moto Mods support Hot Swapping? This is great progress and can't wait to see more on this phone.
xDABZx said:
@Uzephi is your device on sprint? Data works but LTE does not? Does the Moto Mods support Hot Swapping? This is great progress and can't wait to see more on this phone.
Click to expand...
Click to collapse
Motomods work with kernel in ROM (hot swapping should as well iirc, I don't use the mods that often where my projector is outdated) LTE doesn't work on Sprint, but 3G and 1xTT works fine.
@Uzephi if we were to flash your kernel, we would lose motomods support?
cervantesjc said:
@Uzephi if we were to flash your kernel, we would lose motomods support?
Click to expand...
Click to collapse
For now, yes. Still trying to get it work. Clang is being a PITA on my build box, having to go to Linaro which can't build the Motorola Greybus driver correctly.
Thanks sir, I appreciate what you've done for the community, finally can go back to my moto from a GS8+
I'm sorry if this is a dumb question but...
Ive never had to install different firmware before on a ROM. If I install this, will it change the process of installing a different ROM in the future?
Thank you.
Sprint varient if it matters by the way.
Edit: I'm sorry for this but is there a way to do this without the .bat file? currently working on OSX
wcain89 said:
I'm sorry if this is a dumb question but...
Ive never had to install different firmware before on a ROM. If I install this, will it change the process of installing a different ROM in the future?
Thank you.
Sprint varient if it matters by the way.
Edit: I'm sorry for this but is there a way to do this without the .bat file? currently working on OSX
Click to expand...
Click to collapse
Open the bat file in a text editor and run each of those commands one by one.
This I'd a dual boot device. Your other slot has the older Nougat bootloader. That firmware flashed the current Oreo firmware to both slots. If you don't do that, and you flash one of these ROMs, you'll reboot to your nougat slot, locked and pretty much screwed without a flash all and luck of being able to flash OEM images in oem mode.
Edit: you won't need to flash this any consecutive times until there is another big firmware update like nougat to Oreo was.
Uzephi said:
Open the bat file in a text editor and run each of those commands one by one.
This I'd a dual boot device. Your other slot has the older Nougat bootloader. That firmware flashed the current Oreo firmware to both slots. If you don't do that, and you flash one of these ROMs, you'll reboot to your nougat slot, locked and pretty much screwed without a flash all and luck of being able to flash OEM images in oem mode.
Edit: you won't need to flash this any consecutive times until there is another big firmware update like nougat to Oreo was.
Click to expand...
Click to collapse
Thank you for the quick reply. I've installed the firmware, but now when I boot to TWRP and try to install the ROM, it instantly fails with ERROR:1. Tried redownloading with a different browser but got the same result. I feel like I'm missing something obvious.
wcain89 said:
Thank you for the quick reply. I've installed the firmware, but now when I boot to TWRP and try to install the ROM, it instantly fails with ERROR:1. Tried redownloading with a different browser but got the same result. I feel like I'm missing something obvious.
Click to expand...
Click to collapse
Flash twrp zip to your phone, reboot to your phone's newly flashed twrp recovery and flash the rom. If I remember right,you need to wipe oem and system before flashing the ROM as well. I'll add that shortly.
Up and running! Thank you!! Still looking around but I do see a built in updater. Will this function 100%? By that I mean, when the Sprint LTE issue is resolved and whatever else is coming will be handled by the updater?
Thanks again very excited to play around.
wcain89 said:
Up and running! Thank you!! Still looking around but I do see a built in updater. Will this function 100%? By that I mean, when the Sprint LTE issue is resolved and whatever else is coming will be handled by the updater?
Thanks again very excited to play around.
Click to expand...
Click to collapse
Yes, since it's official, it checks the link in OP for any new updates.
For anyone using the ROM, are you seeing notification dots, I tried to get them to work, but they're not working for me.
cervantesjc said:
For anyone using the ROM, are you seeing notification dots, I tried to get them to work, but they're not working for me.
Click to expand...
Click to collapse
Working fine for me thru Evie Launcher. Soundboost mod is broken though. My SoundBoost is recognized and the notification says the mod is attached, but the volume steps are reduced to on/off and no sound comes out.
Edited to reflect that only the sound boost mod isn't working AFAIK.
wcain89 said:
Working fine for me thru Evie Launcher. Mods are broken though. My SoundBoost is recognized and the notification says the mod is attached, but the volume steps are reduced to on/off and no sound comes out.
Click to expand...
Click to collapse
Oh, @npjohnson and @invisiblek don't have the sound mod, so they can't get it to work. All of us in the development discord are trying to mail one out, they can't guarantee when it would get fixed.
Edit: added disclaimer to OP. We can only guarantee what we have works. Like when I do my kernel, the only mod I have is the free projector, so that's the only mod I can guarantee works when I do get it working.
I have an extra soundboost I could mail to someone.
Hi friends, so there's a lot about installing gsi images on various phones that support project treble but i cannot find anything about how you update them. I installed OmniRom beta3, via fastboot, on my H9L and 3 days later they put out an update. The rom works fine and i set it up to my preference with magisk and it even shows up as Play certified, so all is good. However, with the update I prefer not to go through the whole magisk uninstall/install again. Anyone here knows how you would update an existing gsi images ? If I use fastboot to load the new update wouldn't that erase everything again, as stated on the openkirin.net installation instructions ? or could i jsut fastboot the new beta3.1 over beta3 and just not do a factory reset as recommended ?
Weird everyone writes about installation and no one things about updates ?
thanks.
xzyk said:
Hi friends, so there's a lot about installing gsi images on various phones that support project treble but i cannot find anything about how you update them. I installed OmniRom beta3, via fastboot, on my H9L and 3 days later they put out an update. The rom works fine and i set it up to my preference with magisk and it even shows up as Play certified, so all is good. However, with the update I prefer not to go through the whole magisk uninstall/install again. Anyone here knows how you would update an existing gsi images ? If I use fastboot to load the new update wouldn't that erase everything again, as stated on the openkirin.net installation instructions ? or could i jsut fastboot the new beta3.1 over beta3 and just not do a factory reset as recommended ?
Weird everyone writes about installation and no one things about updates ?
thanks.
Click to expand...
Click to collapse
Good question mate. Since you're on omni I rom do you think it's better than ressuruction remix?
Fredin_ said:
Good question mate. Since you're on omni I rom do you think it's better than ressuruction remix?
Click to expand...
Click to collapse
for me, yes, because one of the most important feature i need is safetynet to pass. Omni was easier to get it to pass safetynet checks (via magisk) then RR. I also like the way Omni implemented the dark theme, obviously all of these are just preferences both roms are good daily drivers.
UPDATE: so i fastbooted the updated img file with stock recovery and did not do any wipes. All was fine including root and certification.
xzyk said:
for me, yes, because one of the most important feature i need is safetynet to pass. Omni was easier to get it to pass safetynet checks (via magisk) then RR. I also like the way Omni implemented the dark theme, obviously all of these are just preferences both roms are good daily drivers.
UPDATE: so i fastbooted the updated img file with stock recovery and did not do any wipes. All was fine including root and certification.
Click to expand...
Click to collapse
Good to hear that you updated successfully. I also love the theme engine in Omni rom but had to switch to stock for the camera
Hi guys, I have an SM-N960F dual sim exynos Note 9 and i have recently discovered this whole other element of ROM flashing known as project treble ROMs. I tried to flash a few different ones and i could only get one to work and the rest all just either bootlooped or stayed on the initial splashscreen. I was wondering if anybody could shed some light on them a bit for me and perhaps knew exactly the best way to flash them, and what firmware is best to start on beforehand etc? I found the whole thing EXTREMELY confusing especially with venfor images and kernel images etc...
Thank you for any input/help!
We can't really use the term Project Treble when talking about Samsung phones. Technically it is implemented, but Samsung being Samsung, it's quite a non-standard implementation and not really compatible with anything else.
oddbehreif said:
We can't really use the term Project Treble when talking about Samsung phones. Technically it is implemented, but Samsung being Samsung, it's quite a non-standard implementation and not really compatible with anything else.
Click to expand...
Click to collapse
Ive flashed a few of them onto my phone but it seems to be a bit of hit and miss as to whether they boot up or not. The ones that do have been good in terms of the size and speed etc, I even flashed a generic copy of OneUI which worked well.
I am on Pie base using the Dr.Ketan rom, so I tried a few GSIs which are supposed to be compatible with Pie base. I took them from here.
The way I flash them is:
1. Factory reset from TWRP
2. Flash the GSI as system image
3. Flash stock kernel otherwise you will be stuck on boot logo or you will get into bootloop. To flash the stock kernel I just use Dr.Ketan's rom, because the UI upon flashing allows you to choose and flash stock kernel and skip everything else.
(They mention that we should flash Permissiver also, but it gives error so I can't flash it)
So those GSIs boot up, but they are barely usable. The "System is finishing update" and "System setup will start soon" are stuck for me and never finish. Also for example in the PixelExperience9 from this collection I was not even able to add my Google account because of the system auto-closing almost all system apps that I try to open.
It might be that these things should be done in a different way, but this is my experience for now. So..... back to Dr.Ketan ROM. I was really hoping to get the MIUI GSI as daily, but it seems impossible to me.
EDIT: Lol I realised we are the same people talking on the other thread also, so you gave me the link to the treble collection.
Ok, got a T380. Device specs show it should be much more snappy and responsive than it is. I want to build an ASOP or lineage build for it. There are no custom ROMs right now for my device. Can any dev point me in the direction of a tutorial for building the device tree and obtaining the proprietary blobs? I have been googling for weeks and most of them tell me to get the blobs from a similar device running LOS. I have some coding, flashing and linux expericence, so I am not going in as a complete noob. Any advice or help would be greatly appreciated. TIA
I started compiling roms in August so I have been through this journey in which you are about to start. I'm not a developer, but this is what I learned so far.
If you have a supported lineageos device, I suggest you build that first following the guides they have written. This will ensure you have the proper toolchain, tools, OS, memory, hard disk space, etc setup properly. Here is an example.
https://wiki.lineageos.org/devices/gtelwifiue/build
For the device tree, I did a search using "github sm-t380" and it came up with
https://github.com/tangalbert919/android_device_samsung_gta2swifi
Once I knew the code name, gta2swifi, then I searched "github gta2swifi" which lead to
https://github.com/lilindian16/android_device_samsung_gta2swifi
which looks like a good start.
In order to build the rom, you need 5 things.
1) device tree
2) kernel source
3) vendor blobs
4) roomservice.xml
5) twrp
For kernel source, the T380 has open source code at
https://opensource.samsung.com/main
Type T380 in search box and download the Pie kernel source code.
For vendor blobs, if the
https://github.com/lilindian16/android_device_samsung_gta2swifi/blob/master/proprietary-files.txt
is correct, there's over 2300 files that you need to copy over.
For roomservice.xml, take an existing one that is close to the T380 and make modifications to it. I built the T350 and you can look at the roomservice.xml file at
https://forum.xda-developers.com/ga...ficial-lineageos-17-1-galaxy-tab-8-0-t4162573
For twrp, use an existing T380 twrp.
Video tutorials that I found useful in building roms.
https://www.youtube.com/c/AlaskaLinuxUserAKLU/videos
Thanks so much for the help. I am pretty much in the same spot. I have rooted and flashed just about every device I have ever owned and feel pretty confident I can build a ROM for this device. I already have rooted and TWRPed my T380 it was the vendor files and proprietary blobs that were totally dumbfounding me. I will check your links and work through it. Again, thanks so much for the links.
Okiera29 said:
it was the vendor files and proprietary blobs that were totally dumbfounding me.
Click to expand...
Click to collapse
If you haven't noticed, the vendor blobs are at
https://github.com/lilindian16/android_vendor_samsung_gta2swifi
One other tip. For your first build, build an eng build so you have adb logcat enabled right away. It took me days to figure that out when the boot animation was stuck or the tablet was boot looping. The magic command is
TARGET_BUILD_TYPE=debug TARGET_BUILD_VARIANT=eng make -j2 bacon
-j2 because my machine is only dual core and I only have 12GB DRAM to build.
It's the only way to see debug and information messages while the tablet is booting.
Thanks man! Still trying to get it set up right. I tried to build a debloated, deknoxed stock rom with Android Kitchen and failed. Luckily, had a TWRP back up so the soft brick wasn't an issue. I am determined to figure this out and get a thin custom ROM built for this sucker. I need to figure out overclocking too. You have been a tremendous help!!!
@Okiera29 Were you able to get a working LineageOS rom for your T380. If you don't mind telling me what you have tried and if you had success that would help me out a lot. I'm a newbie trying to find my way around custom roms
I forgot that I participated in this thread. I don't have the SM-T380, but one of the links I referenced earlier shows activity in the last month for the SM-T380 and as recent as < 48 hours.
Looking through the commit history, @andr01dfr3ak might actually have a running 18.1 because enforcing selinux is usually done last after the build is up and running.
Albert, aka andr01dfr3ak also worked on earlier versions of the SM-T350 with 15.1. Since then, I have helped build SM-T350 16.0 with some people and then built 17.1 and 18.1 basically on my own.
I do not have the SM-T380 either, so I am not sure if what I have right now even works. I just know that I can build LineageOS for this device.
@andr01dfr3ak built this rom for me I posses a SM-T380 but I don't have it rn I got stuff removed... for awhile.... If @retiredtab has the device may I suggest having @andr01dfr3ak give @retiredtab the rom to run?
{Mod edit: Link removed} my Discord Server.
i'm trying to download the rom from @andr01dfr3ak but there aren't any available mirrors on androidhost
Want to chime in here -- I too have a Samsung SM-T380, rooted and have TWRP 3.2.3-1 flashed to recovery. I downloaded an image lineage-18.1-20220114-UNOFFICIAL-gta2swifi.zip from somewhere, which is what I think @andr01dfr3ak has been working on.
I am able to successfully install the image, but when booting, the following message is displayed at initial splash screen: "KERNEL is not seandroid enforcing"
And then the display goes dark.
I'm more than happy to provide logs and/or test images if that would be helpful? Please let me know if there's anything I can do to move this along so we have a stable Lineage 18.1 image for the SM-T380!
I've (somehow) got this tree to boot. Whatever the manifest in the tree was doing, it wasn't working, but reverting to the stock one (and downgrading everything) seemed to do it.
I can't get the camera HAL to detect any cameras, though. I think Bluetooth also has issues, but at least WiFi/sound/earbuds are working so at the very least you can use it as a media consuming tablet. And I also have no idea if it works outside of my own device either.
Am a little uncomfortable uploading something that barely works, though, but if anyone capable of building it wants to find out, I have a tree here:
https://github.com/lifehackerhansol-android/android_device_samsung_gta2swifi
https://github.com/lifehackerhansol-android/android_vendor_samsung_gta2swifi
@lifehackerhansol Mind DM'ing me a link to your build? I'd like to work on this a bit and reviewing your progress would be helpful!
christophershaw said:
@lifehackerhansol Mind DM'ing me a link to your build? I'd like to work on this a bit and reviewing your progress would be helpful!
Click to expand...
Click to collapse
So I no longer have this device, it has been given to a family member and reverted to stock. So I can't really make a build and confirm that it's working. The device tree I left above is exactly as I left it back when it did work, so you can go off that.
Sorry, I lost the existing build since. Had to reinstall Linux on my machine and all.
I now have another SM-T380. (lol)
The camera was a kernel issue. Turns out we were using j4primelte's kernel, and it worked all the way until it tried to initialize cameras, because our device's cameras aren't supported in that kernel. It's a miracle anything else worked... Well that was the first problem. The second one was that the blobs were old and Samsung botched their upgrade to 9.0 so I had to deal with several workarounds for that. Anyway camera fixed.
Currently in the middle of mucking with SELinux. When that looks clean I'll push a build(?)