Related
This will be for the SM-G935D/SC-02H Japanese variant of the s7 edge.
Stock ODIN firmware: https://www.androidfilehost.com/?fid=457095661767130814 (Marshmallow)
TWRP 3.0.3-0: https://www.androidfilehost.com/?fid=817550096634747128
Rooted Rom: https://www.androidfilehost.com/?fid=385035244224413763
HKernel for hero2qltedcm:https://www.androidfilehost.com/?fid=745425885120706416
Kernel includes:
CVE updated
Permissive
F2FS support
Ramdisk changes the same as hero2qltechn variant. (All changes are the same)
Kernel Change-log:
https://github.com/travismills82/android_kernel_samsung_msm8996/commits/tw-6.0
TWRP Unofficial:
F2FS Support
More partitions supported for backup and restore compared to official version
How to root this device: https://forum.xda-developers.com/s7-edge/how-to/guide-sm-g9350-s7-edge-qualcomm-sd820-t3410969
Reserved
travis82 said:
This will be for the Japanese variant of the s7 edge this is an unlocked model also.
Stock ODIN firmware: https://www.androidfilehost.com/?fid=457095661767130814 (SC02HOMU1APL2)
TWRP: Coming soon
Debloated Rom: Coming soon
Kernel: Coming soon
Click to expand...
Click to collapse
Can this be used for sm g9350 hongkong?
Sent from my SM-G9350 using Tapatalk
Please use common sense and read ITS FOR THE JAPANESE VARIANT.. READ THE MODEL #. Good gosh stop posting stupid questions dude.
Thanks I'll try this when I get to work.
I can't seem to unlock my bootloader, I'm unable to flash TWRP and enter the recovery. It just says Recovery mode -> Warranty bit set: Recovery and enters into a normal boot after trying it a few times.
Edit:
used the official TWRP and recovery now works. Now trying to install the rom
Edit2:
When trying to install it keeps giving me the following error:
This package is for "SC-02h,hero2qledcm" devices; this is a "hero2qltedcm"
Update process ended with ERROR: 7
Error installing zip file '/sdcard/TWRP/SC-02H_Debloated.zip'
Edit3:
I edited the update-script and removed the assert.
However I don't notice any changes in the rom itself. It still has some bloatware (docomo stuff)
ahh ok i thought it would use sco2h not dcm I can fix that sorry, and I assume twrp is doing the same. I will use a dcm kernel in twrp, let me know if that kernel boots please I dont have the device in hand so I am relying on you all to let me know.
USE crom.apk to unlock bootloader you should find it in galaxy apps store. I'm pretty sure others have unlocked their bootloader doing the same thing. I also used to have someone install my hkroms and kernels on the jap variant so I know you can unlock the bootloader.
CROM: https://www.androidfilehost.com/?fid=385035244224394932
can you unlock the bootloader with that, its a link to what we used to unlock ours.
I need you to unlock your bootloader first please. Sounds like that is the issue.
If I run that app it just exits with Crom Service has stopped working.
Your rom works fine, it has root which is what I needed the most.
Just wish there was a way to remove the sim lock from the device without having to beg Docomo.
I bet I have my asserts all messed up here man I'm sorry. I see SC-02H than hero2qltedcm, than SM-G935D soo I need to get this in the correct order. Would you mind shooting me a pm so I can hangouts you so we can knocks this out quickly?
updated op with twrp recovery and kernel.
This works, root and most of the bloated software is gone
Off topic question (need some insight)
You have started to make a working TWRP for the Docomo variant - thank you for your work (hopefully people in JP using the Docomo version find success).
I know this is off topic but I thought you could provide me with a better understanding.
I am currently using the au KDDI variant (SCV33-Snapdragon) and have successfully installed TWRP (3.0.2-0) with ability to mount /data following xda, youtube, and a Vietnamese forum using google translate; BUT I am unable to keep TWRP ability to mount /data after flashing re-engineered boot file via odin to apply root (Snapdragon Variant Root). TWRP can still be used to go into recovery, mount /ext sdcard, and reboot. I've tried many different styles of rooting after and before installing TWRP, in addition to flashing in different ways - but I still failed. It's either have full working TWRP that can mount /data but without root; or, have root but TWRP that can't mount /data (basically useless as it cannot install anything nor, make backups).
I apologize for such long response, any insight or somewhere you can point me to where I can do more research, as this is how far I have come so far, but still fail to acquire both (Yes I have watched numerous YT vids and read countless post stating devs have not yet found a way on the US-Snapdragon variants, which I understand this may apply to the JP variant too) . Thank you.
With the development of ROMs for the Exynos variants (SG935F/FD) moving along apace... I'm wondering if it is feasible to use one of those ROMs with this kernel.
I did something similar to get a custom ROM made for an AT&T S4 onto my DoCoMo S4 (SC-04E) without issues.
Is that a stupid question?
SCV33 looks exactly the same as SC-02H. What's the difference? single sim dual sim? Can you use sc-02h roms for it? I need more information unless you guys want to start donating me devices.
bu06034 said:
With the development of ROMs for the Exynos variants (SG935F/FD) moving along apace... I'm wondering if it is feasible to use one of those ROMs with this kernel.
I did something similar to get a custom ROM made for an AT&T S4 onto my DoCoMo S4 (SC-04E) without issues.
Is that a stupid question?
Click to expand...
Click to collapse
You guys should never flash an engineering kernel anymore. There is no need since you have a custom kernel and ramdisk and twrp now since I made them. Also those are exynos not qualcomm you can port it but it will be a major task to do.
travis82 said:
You guys should never flash an engineering kernel anymore. There is no need since you have a custom kernel and ramdisk and twrp now since I made them. Also those are exynos not qualcomm you can port it but it will be a major task to do.
Click to expand...
Click to collapse
First, I really apprecate the work you have put in on bringing ROOT and TWRP to users in Japan. If I can help by doing some testing for you with my DoCoMo model, I'd be happy to do so!
Regarding my original question, I was not talking about an engineering kernel. I was thinking that if I flashed a custom ROM for the SG-935F Hong Kong (Exynos) model, and then flashed your kernel over it, would it work?
As I understand it, the kernel is the interface between the OS and the hardware. Maybe that is ignorant? The reason I ask is because this process was quite common for Japanese S4 users to employ custom ROMs for US S4s; i.e. Flash the US custom ROM (e.g. Mokee or Albee95) and then flash the Japanese S4 kernel onto it.
I understand the question might seem silly to you, but I don't have the hundreds of hours required to reach your level of expertise. I have invested sufficient time to understand much of the jargon; and the tools and methods employed to get root and flash ROMs. More than that, I rely on asking the experts, like you. :good:
you would have to port firmware framework and a bit of other things, secondly hong kong does not self exynos versions here. It's all Qualcomm.
SCV33 waiting for someone to flash this kernel on it to let me know if its compatible or not.
Anyways updated main thread with BETA 2.
Enjoy,
Travis82
SCV33 test 1
travis82 said:
SCV33 waiting for someone to flash this kernel on it to let me know if its compatible or not.
Anyways updated main thread with BETA 2.
Enjoy,
Travis82
Click to expand...
Click to collapse
Travis,
TESTED (Semi-working)
I've done some testing on my SCV33 variant using what you've made for the SC-02H.
[Kernel]
I flashed the HKernal Beta 2, using the SC-02H FW, and TWRP Unofficial you've provided onto my SCV33 Galaxy S7e and it is really snappy and fast. Very nice kernel. Any DoCoMo users out there should flash this - though still beta it does the job. I had no problems flashing this in TWRP.
[TWRP Unofficial]
I was able to mount all partitions - works. I had no problem flashing this using Odin.
[Problems I've Encountered]
* After rebooting into TWRP Unofficial many times. My log reads "Unable to mount /steady." I have no idea what this is or what partition it belongs too; but, TWRP is still able to do everything else such as mount /data, wipe /system, etc. - I don't think its a big issue to be honest. Just wanted to let you know.
* After installing everything and everything working fine. I do not/cannot communicate with networks (cannot connect to wifi, cannot call, and no data). I had check SIM status = not available, IMEI = Unknown, SN = Unknown. I had made an EFS back up of my KDDI rom with working network communication and restored with with TWRP Unofficial. Installation via TWRP log has stated successful, but upon reboot problem has not been fixed. Any ideas I should try? I also believe the software from the SC-02H OS handles how im about to connect to data towers and catch frequencies. Putting in my own APN does not work.
* Crom Service.apk you've provided at an earlier comment to unlock bootloader, which I've installed, does not work. All it does is FC when trying to open the app - installation is fine. I had also tried getting one from the internet, and looking for it at the Samsung Galaxy App Store - the internet one does the same, FC. Samsung Galaxy App Store does not have Crom Service available. I am assuming SCV33 wont ever be able to unlock bootloader.
* Debloated Rom Zip does not work, after doing a clean install to Stock Odin, installing TWRP Unofficial, system ext4 format, wiping /system /data /internal storage /dalvikArt /cache, and flashing Debloated Rom Zip with TWRP - states installed successful and boots up. Though upon booting I still have all the bloat there. In addition, many FCs from many different apps, even after reboot (e.g. tap and play, google play store, google services). The rom still functions after a couple more reboots after a /dalvikART cache wipe, but it just doesn't seem as fast as the stock one though. I believe this maybe a conflict due to my device, and myself as well.
----
Oh BTW the SCV33 is:
*SM-G935J
*OS 6.0.1
*Single SIM only
I will try my best do to other methods on trying to get this to fully work, but the Network Communication thing always halts my progress. I really dig this kernel man.
Again, thank you for your hard work and dedication to the Snapdragon Variant its very much appreciated :highfive:. Looking at the Exynos sub-forum I get so jelly at times.
OK is yours has a different modem then the rest. Also your partitions might be a bit different, I really need that device in my hands to look at the partition layout. If you can find SCV33 kernel source I will be more than happy to make a kernel for this variant also. I call my kernels beta because it's just how I do it.
Ok found your source for the kernel I'll check out the configs and maybe make a kernel later on this week.
SM-G935J (SCV33)
Here is a test kernel: https://www.androidfilehost.com/?fid=529152257862698452
Rooted rom: https://www.androidfilehost.com/?fid=529152257862698453
Let me know if there is any issues.
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.
EDIT: I posted this in the S10+ forum but then realized this forum is probably better
Hey all, for some development work I am required to build a custom kernel with some non-standard features on the Samsung S10 SM-G973F Exynos model. Could anyone point me to the best way to get this done? I have a feeling I have way over-thought this issue... I was trying to just build the code from the Samsung open source resource center, but haven't really had any luck.
I have tried many different kernel configs. Getting the kernel built for my phone's ROM version is not the issue, it's actually getting it to boot. I've disabled a lot of the security features (not all) and either the phone goes into a boot loop, or Heimdall/ODIN cannot finish the boot flash because I get that "You can only run samsung images" error message (paraphrased), which ends up with the "OEM unlocking" developer option going missing until I factory reset and screw around with the phone's date. Also noticed topjohnwu of Magisk posted some details about this as a challenge that had to be overcome for S10 support.
Anyway Im just wondering if maybe I am missing anything really obvious: like can I do this somehow with Magisk (replace the kernel magisk uses? i know magisk does some kind of kernel patching, but not sure if its different for the S10.) or, maybe someone else has gotten a custom kernel going via different means? Any tips would be welcome and much appreciated!
Thanks in advance!
mikecc said:
EDIT: I posted this in the S10+ forum but then realized this forum is probably better
Hey all, for some development work I am required to build a custom kernel with some non-standard features on the Samsung S10 SM-G973F Exynos model. Could anyone point me to the best way to get this done? I have a feeling I have way over-thought this issue... I was trying to just build the code from the Samsung open source resource center, but haven't really had any luck.
I have tried many different kernel configs. Getting the kernel built for my phone's ROM version is not the issue, it's actually getting it to boot. I've disabled a lot of the security features (not all) and either the phone goes into a boot loop, or Heimdall/ODIN cannot finish the boot flash because I get that "You can only run samsung images" error message (paraphrased), which ends up with the "OEM unlocking" developer option going missing until I factory reset and screw around with the phone's date. Also noticed topjohnwu of Magisk posted some details about this as a challenge that had to be overcome for S10 support.
Anyway Im just wondering if maybe I am missing anything really obvious: like can I do this somehow with Magisk (replace the kernel magisk uses? i know magisk does some kind of kernel patching, but not sure if its different for the S10.) or, maybe someone else has gotten a custom kernel going via different means? Any tips would be welcome and much appreciated!
Thanks in advance!
Click to expand...
Click to collapse
If you have your kernel image,try to patch it with magisk.Look at the kernel :HeliosPie Kernel 3.1 for J5 2017.You will see it replaces and deletes some libraries in the phone. Try to do that manually or copy the code from META-INF.
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(?)
Follow the following at your own risk! I am not responsible for any mishaps with your devices. This will NOT obviously work for Verizon, AT&T, and Cricket phones.
Okay, So I've been asking questions, playing, unpacking, and repacking, trying tools, etc. And I got a very experimental port of TWRP happening. VERY EXPERIMENTAL.
THINGS TO KNOW AFTER THE EXCITEMENT DIES DOWN:
For starters, yes THIS DOES BOOT TO TWRP! I'm quite proud about that. This is my first ever port of anything like this. I mostly just fiddle with making bootable stock roms, and not too much since Android 9 and this new nuts file system. Anyway, I set out to try and get a TWRP together for this phone and that happened, so I'm proud of myself I didn't get discouraged.
Having said that, it has ZERO touchscreen functionality. From my research this was also an initial problem for the peeps over at the Moto One 5G Plus variant (Nairo) before they worked out the bugs. Hopefully they will take mercy on us and come give some feedback.
Also, this is a port. I used @Hovatek's Qualcomm tool to accomplish this since unpacking, repacking, copying and pasting a port from Nairo in the Carliv Image Kitchen or Android Image Kitchen just soft bricked my phone. It also doesn't help the traditional porting methods prior to Android 9 don't work anymore. They came up with a great tool, Gawd Bless Em'.
Should you try this for hoots and giggles just know you will have to hard reset. Android will force a factory reset because of the vbmeta flashing, and your phone will be factory brand spanking new. Backup your contacts, pics, messages, and anything else you want to keep just in case.
I'm not going to put detailed instructions on this just yet since it's experimental - this is really for folks that know what they're doing with their phone.
Notes:
You must have the bootloader unlocked and be rooted with Magisk for this to fly. Can't say how this would work on locked bootloaders without root so proceed cautiously on that.
1. Flash VBmeta first. The VBMeta is a blank file and that's to make sure DM-Verity isn't acting up (which as of now I'm 50% certain it is and that's why I had to go ahead and factory reset). The commands to disbale dm-verity didn't work for me. If anybody knows how to get that shut off please add to the discussion.
2. I didn't replace my original recovery. I just did fastboot boot recovery image to see if it would load. I wouldn't advise flashing it to replace the current recovery as it might seriously bootloop.
If anybody wants to try and work on this with me (or take over since I'm a hobbyist at best) then by all means share. But at least now we're getting somewhere, slowly but surely.
Today was a good day in hacking Android 10 on this phone.
Articul8Madness said:
Follow the following at your own risk! I am not responsible for any mishaps with your devices. This will NOT obviously work for Verizon, AT&T, and Cricket phones.
Okay, So I've been asking questions, playing, unpacking, and repacking, trying tools, etc. And I got a very experimental port of TWRP happening. VERY EXPERIMENTAL.
THINGS TO KNOW AFTER THE EXCITEMENT DIES DOWN:
For starters, yes THIS DOES BOOT TO TWRP! I'm quite proud about that. This is my first ever port of anything like this. I mostly just fiddle with making bootable stock roms, and not too much since Android 9 and this new nuts file system. Anyway, I set out to try and get a TWRP together for this phone and that happened, so I'm proud of myself I didn't get discouraged.
Having said that, it has ZERO touchscreen functionality. From my research this was also an initial problem for the peeps over at the Moto One 5G Plus variant (Nairo) before they worked out the bugs. Hopefully they will take mercy on us and come give some feedback.
Also, this is a port. I used @Hovatek's Qualcomm tool to accomplish this since unpacking, repacking, copying and pasting a port from Nairo in the Carliv Image Kitchen or Android Image Kitchen just soft bricked my phone. It also doesn't help the traditional porting methods prior to Android 9 don't work anymore. They came up with a great tool, Gawd Bless Em'.
Should you try this for hoots and giggles just know you will have to hard reset. Android will force a factory reset because of the vbmeta flashing, and your phone will be factory brand spanking new. Backup your contacts, pics, messages, and anything else you want to keep just in case.
I'm not going to put detailed instructions on this just yet since it's experimental - this is really for folks that know what they're doing with their phone.
Notes:
You must have the bootloader unlocked and be rooted with Magisk for this to fly. Can't say how this would work on locked bootloaders without root so proceed cautiously on that.
1. Flash VBmeta first. The VBMeta is a blank file and that's to make sure DM-Verity isn't acting up (which as of now I'm 50% certain it is and that's why I had to go ahead and factory reset). The commands to disbale dm-verity didn't work for me. If anybody knows how to get that shut off please add to the discussion.
2. I didn't replace my original recovery. I just did fastboot boot recovery image to see if it would load. I wouldn't advise flashing it to replace the current recovery as it might seriously bootloop.
If anybody wants to try and work on this with me (or take over since I'm a hobbyist at best) then by all means share. But at least now we're getting somewhere, slowly but surely.
Today was a good day in hacking Android 10 on this phone.
Click to expand...
Click to collapse
Hi. I appreciate a lot your efforts. I know the feeling when you progress with stuff like this. I'm sorry I have no time in these months to assist. Anyway, I hope you'll manage to go forward with this. Keep up with the good work.
useless789 said:
Hi. I appreciate a lot your efforts. I know the feeling when you progress with stuff like this. I'm sorry I have no time in these months to assist. Anyway, I hope you'll manage to go forward with this. Keep up with the good work.
Click to expand...
Click to collapse
CAn you at least tell me how to port a TWRP on Android 10? Can't find any useful information with the new filetypes.
Articul8Madness said:
CAn you at least tell me how to port a TWRP on Android 10? Can't find any useful information with the new filetypes.
Click to expand...
Click to collapse
I'm not sure what you mean by filetypes. Do you mean the A/B partitions (and the fact that there's no separate recovery partition) or something else?
Articul8Madness said:
Follow the following at your own risk! I am not responsible for any mishaps with your devices. This will NOT obviously work for Verizon, AT&T, and Cricket phones.
Okay, So I've been asking questions, playing, unpacking, and repacking, trying tools, etc. And I got a very experimental port of TWRP happening. VERY EXPERIMENTAL.
THINGS TO KNOW AFTER THE EXCITEMENT DIES DOWN:
For starters, yes THIS DOES BOOT TO TWRP! I'm quite proud about that. This is my first ever port of anything like this. I mostly just fiddle with making bootable stock roms, and not too much since Android 9 and this new nuts file system. Anyway, I set out to try and get a TWRP together for this phone and that happened, so I'm proud of myself I didn't get discouraged.
Having said that, it has ZERO touchscreen functionality. From my research this was also an initial problem for the peeps over at the Moto One 5G Plus variant (Nairo) before they worked out the bugs. Hopefully they will take mercy on us and come give some feedback.
Also, this is a port. I used @Hovatek's Qualcomm tool to accomplish this since unpacking, repacking, copying and pasting a port from Nairo in the Carliv Image Kitchen or Android Image Kitchen just soft bricked my phone. It also doesn't help the traditional porting methods prior to Android 9 don't work anymore. They came up with a great tool, Gawd Bless Em'.
Should you try this for hoots and giggles just know you will have to hard reset. Android will force a factory reset because of the vbmeta flashing, and your phone will be factory brand spanking new. Backup your contacts, pics, messages, and anything else you want to keep just in case.
I'm not going to put detailed instructions on this just yet since it's experimental - this is really for folks that know what they're doing with their phone.
Notes:
You must have the bootloader unlocked and be rooted with Magisk for this to fly. Can't say how this would work on locked bootloaders without root so proceed cautiously on that.
1. Flash VBmeta first. The VBMeta is a blank file and that's to make sure DM-Verity isn't acting up (which as of now I'm 50% certain it is and that's why I had to go ahead and factory reset). The commands to disbale dm-verity didn't work for me. If anybody knows how to get that shut off please add to the discussion.
2. I didn't replace my original recovery. I just did fastboot boot recovery image to see if it would load. I wouldn't advise flashing it to replace the current recovery as it might seriously bootloop.
If anybody wants to try and work on this with me (or take over since I'm a hobbyist at best) then by all means share. But at least now we're getting somewhere, slowly but surely.
Today was a good day in hacking Android 10 on this phone.
Click to expand...
Click to collapse
This is tremendously amazing work. TWRP would be a killer feature with the 5G Ace. Couple that with Lenovo having released the source code, and this forum may get popping again!
useless789 said:
I'm not sure what you mean by filetypes. Do you mean the A/B partitions (and the fact that there's no separate recovery partition) or something else?
Click to expand...
Click to collapse
I was referring to the super_sparsechunk type files that when you look at their "filetype" it has 0 image by its name if its super_sparsechunk.0, 1 if its super_sparsechunk.1 and the like. This is different than the old basic img files that read .img. This is where the learning curve for me kicks in.
Articul8Madness said:
I was referring to the super_sparsechunk type files that when you look at their "filetype" it has 0 image by its name if its super_sparsechunk.0, 1 if its super_sparsechunk.1 and the like. This is different than the old basic img files that read .img. This is where the learning curve for me kicks in.
Click to expand...
Click to collapse
I see. Thanks for the explanation. I'm not sure if this could help, but a quick search on google led me to this (a bit old) video:
I'm really busy until the end of the month so I can't really dedicate my time to this stuff though I would love to.
useless789 said:
I see. Thanks for the explanation. I'm not sure if this could help, but a quick search on google led me to this (a bit old) video:
I'm really busy until the end of the month so I can't really dedicate my time to this stuff though I would love to.
Click to expand...
Click to collapse
I see you already tried this here: Post in thread '[Tool] SparseConverter v1.0.1' https://forum.xda-developers.com/t/tool-sparseconverter-v1-0-1.2749797/post-84767377
If I manage I'll take a look at this asap.
useless789 said:
I see you already tried this here: Post in thread '[Tool] SparseConverter v1.0.1' https://forum.xda-developers.com/t/tool-sparseconverter-v1-0-1.2749797/post-84767377
If I manage I'll take a look at this asap.
Click to expand...
Click to collapse
Any and all contributing help is appreciated!
@Articul8Madness I managed to combine the sparse chunk files into a raw image file. I also managed to mount the image, but only in read-only mode. I'll post with updates as I get passed this obstacle.
Seems the US version of this phone isn't popular enough for dev support...oh well I have R/W access so I was able to delete system app bloatware and I have xposed installed. Stock Reteu firmware is working perfectly on Metro...good luck everybody.. I'm looking for a new 5G phone..
Unfortunately, there are no developers here.
All we can produce is a ported twrp where the touchscreen does not work.
The touchscreen does not work due to problems with the porting tool and the smartphone.
I heard that if you build it from source yourself, it will work.
But I can't find any tutorials for android 10+ and I don't even know what files I need.
PEACH-PIT said:
Unfortunately, there are no developers here.
All we can produce is a ported twrp where the touchscreen does not work.
The touchscreen does not work due to problems with the porting tool and the smartphone.
I heard that if you build it from source yourself, it will work.
But I can't find any tutorials for android 10+ and I don't even know what files I need.
Click to expand...
Click to collapse
I posted the source code. The guys over on the Moto One 5G know what tools you need. I was using Carliv's kitchen to build but I've never built before - they had the same problem as us with the touchscreen and had to make modules. That counts me out because that's above my paygrade, lol.
Articul8Madness said:
I posted the source code. The guys over on the Moto One 5G know what tools you need. I was using Carliv's kitchen to build but I've never built before - they had the same problem as us with the touchscreen and had to make modules. That counts me out because that's above my paygrade, lol.
Click to expand...
Click to collapse
Not entirely sure what you mean. If your doing some kind of frankenstein recovery, I'm sure you just failed to copy some module or firmware, obviously the ts works in the official software.
1.) Find out what touchscreen chipset your device uses (you can use kernel log or system info apps or whatever)
2.) Determine which kernel module supports it (all modules built will be in your kernel config)
3.) modprobe that module from adb in your recovery. If it doesn't just work, you will receive some error on the command line or dmesg that you can use to fix it. Could need a configuration file or something, idk. It's likely an opensource module that you can read through and I bet you can find specific info online since your not the first to hit this issue.
If your wondering how to build the kernel, I can help a little, but it's incomplete:
Kernel source:
GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
github.com
Build instructions:
readme/MMI-QPN30.33-40.txt at master · MotorolaMobilityLLC/readme
Readme's for motorola builds. Contribute to MotorolaMobilityLLC/readme development by creating an account on GitHub.
github.com
Snapdragon LLVM Toolchain:
snapdragon-llvm-8.0.6-linux64.tar.gz
drive.google.com
Retail config is on your device:
/proc/config.gz
The instructions don't cover the qcom toolchain, you just take the files here:
snapdragon-llvm-8.0.6-linux64.tar.gz/toolchains/llvm-Snapdragon_LLVM_for_Android_8.0/prebuilt/linux-x86_64/*
and place them here:
$my_top_dir/vendor/qcom/proprietary/llvm-arm-toolchain-ship/8.0/
When building, skip the cat command, and place your config manually to $kernel_out_dir/.config
The step I haven't done is build a device tree. It's not that it's too difficult, I just haven't put in the time required to do it. It's not strictly necessary to achieve for my goals since I only wanted modules and know how to patch the kernel to be able to use them.
https://github.com/moto-sm7250/android_device_motorola_kiev/tree/android-10
Will this not work?
I do not know how to build it.
fddm said:
Not entirely sure what you mean. If your doing some kind of frankenstein recovery, I'm sure you just failed to copy some module or firmware, obviously the ts works in the official software.
1.) Find out what touchscreen chipset your device uses (you can use kernel log or system info apps or whatever)
2.) Determine which kernel module supports it (all modules built will be in your kernel config)
3.) modprobe that module from adb in your recovery. If it doesn't just work, you will receive some error on the command line or dmesg that you can use to fix it. Could need a configuration file or something, idk. It's likely an opensource module that you can read through and I bet you can find specific info online since your not the first to hit this issue.
If your wondering how to build the kernel, I can help a little, but it's incomplete:
Kernel source:
GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
github.com
Build instructions:
readme/MMI-QPN30.33-40.txt at master · MotorolaMobilityLLC/readme
Readme's for motorola builds. Contribute to MotorolaMobilityLLC/readme development by creating an account on GitHub.
github.com
Snapdragon LLVM Toolchain:
snapdragon-llvm-8.0.6-linux64.tar.gz
drive.google.com
Retail config is on your device:
/proc/config.gz
The instructions don't cover the qcom toolchain, you just take the files here:
snapdragon-llvm-8.0.6-linux64.tar.gz/toolchains/llvm-Snapdragon_LLVM_for_Android_8.0/prebuilt/linux-x86_64/*
and place them here:
$my_top_dir/vendor/qcom/proprietary/llvm-arm-toolchain-ship/8.0/
When building, skip the cat command, and place your config manually to $kernel_out_dir/.config
The step I haven't done is build a device tree. It's not that it's too difficult, I just haven't put in the time required to do it. It's not strictly necessary to achieve for my goals since I only wanted modules and know how to patch the kernel to be able to use them.
Click to expand...
Click to collapse
This recovery I built in this thread I used Hovatek's tool to do. I have never built a recovery and I was hoping if someone got the ball rolling we could get a dev to jump in. That hasn't happened.
The guys with the other variant of this phone said they had to create modules. Go to the Moto One 5G forums and see the thread. They had the same problems too, but they had more dev support than we do.
I have never built a TWRP, let alone from source, so half of what you sent I have no idea what it is or how to decompile it (yet).
I have posted the entire Kernel Motorola released its in the other thread. The Device Tree is official and out on github.
Guys, I'm a developer, just that I'm still really busy. I'm following your posts and have looked into some of the stuff, just I'm proceeding slowly due to lack of time. I'll post as soon as I have something working.
useless789 said:
Guys, I'm a developer, just that I'm still really busy. I'm following your posts and have looked into some of the stuff, just I'm proceeding slowly due to lack of time. I'll post as soon as I have something working.
Click to expand...
Click to collapse
Is this the correct twrp for this phone?
Root Motorola One 5G Ace XT2113 and Install TWRP Recovery 3.5.0
Easy tutorial to Root Motorola One 5G Ace XT2113-2, XT2113-3, XT2113-5 easily. For rooting, you have to flash TWRP Recovery 3.5.0 on Android 10 through guide.
www.androidweblog.com
Later guys, keep up the good work
Tomspector said:
Is this the correct twrp for this phone?
Root Motorola One 5G Ace XT2113 and Install TWRP Recovery 3.5.0
Easy tutorial to Root Motorola One 5G Ace XT2113-2, XT2113-3, XT2113-5 easily. For rooting, you have to flash TWRP Recovery 3.5.0 on Android 10 through guide.
www.androidweblog.com
Later guys, keep up the good work
Click to expand...
Click to collapse
This is a fake. It's non-functional garbage.
There is no harm in trying it, unless you flash it, but there is no need to try it.
useless789 said:
Guys, I'm a developer, just that I'm still really busy. I'm following your posts and have looked into some of the stuff, just I'm proceeding slowly due to lack of time. I'll post as soon as I have something working.
Click to expand...
Click to collapse
I have a request to the developers.
GitHub - moto-sm7250/android_device_motorola_kiev at android-10
DT for Moto G 5G / One 5G Ace. Contribute to moto-sm7250/android_device_motorola_kiev development by creating an account on GitHub.
github.com
Can you please build this twrp?
I'm trying to build it.
But I don't know how to solve the error.
I don't think I can build it.