[OFFICIAL/UNOFFICIAL] LineageOS 20 for Amlogic GXL/GXM/G12*/SM1 Family Devices

[OFFICIAL/UNOFFICIAL] LineageOS 20 for Amlogic GXL/GXM/G12*/SM1 Family Devices - Google TV General

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Amlogic GXL/GXM/G12*/SM1 Family Devices
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 20 thread for the Amlogic GXL/GXM/G12*/SM1 SoC family of devices.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed:
Official Builds:
deadpool - Google ADT-3
wade - Dynalink TV Box (4K)
Disclaimer: My unofficial builds have full Android TV Google Apps and some other goodies included. OTA's roll roughly once a month. Support not guaranteed or implied.
Unofficial Builds:
deadpool - Google ADT-3
dopinder - Walmart Onn UHD Box
sabrina - Chromecast with Google TV
wade - Dynalink TV Box (4K)
We also support a few development boards, but at least (for now, until we have time to write up instructions), you're on your own to figure out the install process and set things up:
m5 - Banana Pi M5
odroidc4 - Odroid C4
radxa0 - Rock Pi Radxa Zero
EDIT: The development boards don't boot on LineageOS 20 at the moment for some reason, but we know why and are working on it!
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
Recent apps/Multitasking menu doesn't launch.
(sabrina only) The remote firmware sometimes gets hung up, you can reboot to solve this issue.
(dopinder/sabrina) L1 is currently broken, this is what is holding up official builds for these devices.
Notes:
GApps are baked in on Unofficial builds - No, I will not be building without GApps included for this device. These builds are built, packaged, and signed by me, and not affiliated with LineageOS whatsoever.
Firmware is shipped in the ROM package for this device, so you'll end up on the newest version of compatible firmware after install. Please don't touch firmware partitions after install.
On the unofficial OTA is provided the same way officials would have them.
Find any more on an official build? Report them according to this guide.
FAQ:
Does L1 Widevine DRM break when I unlock my bootloader?
Nope, it works fine. L1 certificates, and the mechanism that reports is all still exist and work as expected.
Can I haz Netflix?
Yup! Play Store has it for you. Unless you're on dopinder or sabrina, but that will be fixed soon hopefully.
Is this Android TV or Google TV?
Android TV, with some of the better components of Google TV.
Can I go back to stock and relock the bootloader?
Yeah, grab the factory image for your device and flash it just like you would for a Pixel device, you can find the factory images here. Don't know it I'd relock though, consider that process largely untested on these device. Especially on sabrina, where you can't necessarily re-unlock should you ever want to.
Are these the stock codenames for these devices?
Astute observation, no, they are not. The ADT-3 is actaully `adt3`, but earlier in production is was `deadpool`, which is much cooler. The Dynalink box internally is extremely similar to the ADT-3, so we coined it `wade` after Wade Wilson, AKA deadpool. The Onn box is in the same family, but different enough to coin it `dopinder`, after, well, go watch Deadpool the movie I guess. sabrina is actually the codename given by Google - no clue as to the reason.
Does it pass SafetyNet?
Maybe - the only sure fire way it Magisk, as our boot loader is unlocked and can't be relocked safely.
Does the stock remote work?
Yup, just like it would on stock, in-remote-microphone and all! If it's an IR remote like wade's, it will even work in recovery!
Can we we support higher resolution than 4K, higher FPS, or HDR on non-certified screens?
Nope.
I have a very similar device! Can I install these builds and use them?
No. Please don't do that. You will brick your device, as we include firmware and bootloader images.
If you're a developer looking to help port to a new device, contact me.
Kernel Source (G12*/SM1): https://github.com/LineageOS/android_kernel_amlogic_linux-4.9
Kernel Source {GXL/GXM): https://github.com/LineageOS/android_kernel_amlogic_linux-4.9-pie
Contributors:
npjohnson
bgcngm
stricted
webgeek1234
deadman96385
trautamaki
luca020400
aleasto
chrmhoffmann
highwaystar
mikeioannina

Thx for your time
Thx to ALL in the team

Very excited for this! Kudos to the devteam!

Thanks for the work you’re putting in on this. I’m going to go ahead and wait to hear what other users are thinking of this what’s good and where’s the bugs before flashing. I just don’t feel like re installing magisk and all that right now. But… I do have a 4 day weekend so… I’m probably just in denial I’m sure I’ll end up setting this up. Happy new years everyone. Let the record show we have lineage 20 android 13 on our budget boxes BEFORE 2023. Amazing.

I tried upgrading from official 19 to 20(lineage-20.0-20221220-UNOFFICIAL-wade). Upgrade was successful. But Netflix app errors everytime it runs. Prime video was fine.
My device is wade. Sorry i wouldn't be more verbose since i have downgraded.

ascii79 said:
I tried upgrading from official 19 to 20(lineage-20.0-20221220-UNOFFICIAL-wade). Upgrade was successful. But Netflix app errors everytime it runs. Prime video was fine.
My device is wade. Sorry i wouldn't be more verbose since i have downgraded.
Click to expand...
Click to collapse
I could be wrong, but I believe the reason the build is an unofficial build is with broken widevine L1 . That is a DRM that netflix requires for their app to run correctly. I know this was what held up official builds on 19.1 for some devices.

talksickisil said:
I could be wrong, but I believe the reason the build is an unofficial build is with broken widevine L1 . That is a DRM that netflix requires for their app to run correctly. I know this was what held up official builds on 19.1 for some devices.
Click to expand...
Click to collapse
Nope not on wade - L1 should work fine - I think it's _just_ Netflix because Prime Video works.

npjohnson said:
Nope not on wade - L1 should work fine - I think it's _just_ Netflix because Prime Video works.
Click to expand...
Click to collapse
Interesting. Well I’m a pirate anyways … The only “official” app I use is directv stream with a friends log in from my home state. (Which keeps me able to watch all my home town nfl nba mlb games) anyways…I am going to go ahead and install this today and I’ll report back after installed.

All I have to say is WOW was that quick and easy. I didn’t even need to turn on my laptop. Upgrading is a breeze. I used root toolbox (I think it’s called) to flash the recovery .img without even exiting the android session. Then after rebooting recovery from that same app I verified the date it shows and confirmed it flash successfully. Then I just flashed the .zip from my usb flash drive for EXternal storage attached to OTG. I was going to wipe everything and start fresh. For whatever reason, the recovery decided to reboot after I didn’t hit any buttons for awhile. To my surprise everything migrated from 12 to 13 flawlessly with exception of magisk. I did not even have issues with my INternal storage usb drive. It’s installed but I will need to re-patch the boot img. If I do have any issues I will keep this dirty flash in mind. Thanks as always for your work. I like the file manager you added. Nice touch. Also I notice this build using about 300 mb larger than the average official highly build. Did you include more g apps or something? With this dirty flashed I won’t be able to tell anything I already had installed. Oh and also: the signature verification warning in recovery is no more. That’s excellent also.

Hi. Which GXL devices will be supported?

DiogoSilva48 said:
Hi. Which GXL devices will be supported?
Click to expand...
Click to collapse
beast (ADT-2) is s905x
hertz (devkit) is s922x
More welcome if we get more people interested!

I tried this build on my dopinder box and it went flawlessly. It was much simpler than the 19.1 build.
I see encrypted content still isn't playing. I did some investigation into the problem and I see something that looks like it could be causing the problem.
In logcat, I see the following:
E/OMXNodeInstance: setParameter(0xeaec3e14:amlogic.avc.decoder.awesome2.secure, OMX.google.android.index.storeMetaDataInBuffers(0x7f000002): Input:0 en=0 type=1) ERROR: BadPortIndex(0x8000101b)
That 0x8000101b error is usually caused by a bad codec, which suggests amlogic.avc.decoder.awesome.secure probably isn't compatible with the S905X2 SoC. Was it compiled for the S905Y2 and maybe that build doesn't work with the S905X2 in dopinder/sabrina?
Thanks to everyone that created this build.
Edit: I thought wade had a S905Y2 but it has the S905X2 so I guess it isn't the SoC model causing the error.

I got this up and running on Dopinder. I did have to manually reboot into recovery using the side button, but otherwise the install was easier than my experience with the 19.1 build. Like the previous post, the important apps, like Netflix/Prime, are still broken. Thanks for your continued hard work!

01520717 said:
Edit: I thought wade had a S905Y2 but it has the S905X2 so I guess it isn't the SoC model causing the error.
Click to expand...
Click to collapse
I thought Walmart, Dynalink, ADT-3 all have Y2 but google have D3. The wiki says different so I don't know what's correct.

I wish had some type of criticism but there has not been any new issues for me specifically since updating. So I will just reiterate thank you for bringing this forward. I know it’s not part of the rom or supported but magisk is playing very nicely with either build. And even the stock rom. It’s nice having these options!

ROM works great on wade! One issue I am having is selinux errors for netflix which is triggering a compat error and DRM errors for Hulu, logs are below:
hulu: https://pastebin.com/uX6eTQEK
netflix:
Code:
12-30 16:21:11.340 7302 7302 W DefaultDispatch: type=1400 audit(0.0:78): avc: denied { read } for name="u:object_r:vendor_netflix_prop:s0" dev="tmpfs" ino=3556 scontext=u:r:untrusted_app_30:s0:c103,c256,c512,c768 tcontext=u:object_r:vendor_netflix_prop:s0 tclass=file permissive=0 app=com.netflix.ninja
12-30 16:21:11.148 7302 7302 W DefaultDispatch: type=1400 audit(0.0:77): avc: denied { read } for name="u:object_r:vendor_netflix_prop:s0" dev="tmpfs" ino=3556 scontext=u:r:untrusted_app_30:s0:c103,c256,c512,c768 tcontext=u:object_r:vendor_netflix_prop:s0 tclass=file permissive=0 app=com.netflix.ninja

ji said:
ROM works great on wade! One issue I am having is selinux errors for netflix which is triggering a compat error and DRM errors for Hulu, logs are below:
hulu: https://pastebin.com/uX6eTQEK
netflix:
Code:
12-30 16:21:11.340 7302 7302 W DefaultDispatch: type=1400 audit(0.0:78): avc: denied { read } for name="u:object_r:vendor_netflix_prop:s0" dev="tmpfs" ino=3556 scontext=u:r:untrusted_app_30:s0:c103,c256,c512,c768 tcontext=u:object_r:vendor_netflix_prop:s0 tclass=file permissive=0 app=com.netflix.ninja
12-30 16:21:11.148 7302 7302 W DefaultDispatch: type=1400 audit(0.0:77): avc: denied { read } for name="u:object_r:vendor_netflix_prop:s0" dev="tmpfs" ino=3556 scontext=u:r:untrusted_app_30:s0:c103,c256,c512,c768 tcontext=u:object_r:vendor_netflix_prop:s0 tclass=file permissive=0 app=com.netflix.ninja
Click to expand...
Click to collapse
Thanks for reporting this! Easy fix. Will be in next build.

What is the upgrade procedure for those coming from 19.1 ?
Also, are there still issues with wifi, I am having on 19.1?
1. Wifi disconnecting after long periods of inactivitiy.
2. Wifi config in settings missing static ip setup.

matrix200200 said:
What is the upgrade procedure for those coming from 19.1 ?
Also, are there still issues with wifi, I am having on 19.1?
1. Wifi disconnecting after long periods of inactivitiy.
2. Wifi config in settings missing static ip setup.
Click to expand...
Click to collapse
I'm still having the WiFi weirdness post-upgrade... :-(
I upgraded to these:
lineage-20.0-20221220-UNOFFICIAL-dopinder.zip
lineage-20.0-20221219-recovery-dopinder.img
I followed the wiki, which is written for people coming from a retail device, even though I was upgrading from 19.1. Since the build automagically upgrades the recovery, I'm guessing it would be simpler just to boot into the 19.1 recovery and flash the ...dopinder.zip - I think manually flashing the latest recovery is unnecessary?
I would also appreciate knowing what the correct upgrade procedures are...I often feel like I'm guessing lol

wyldwilly said:
I'm still having the WiFi weirdness post-upgrade... :-(
I upgraded to these:
lineage-20.0-20221220-UNOFFICIAL-dopinder.zip
lineage-20.0-20221219-recovery-dopinder.img
I followed the wiki, which is written for people coming from a retail device, even though I was upgrading from 19.1. Since the build automagically upgrades the recovery, I'm guessing it would be simpler just to boot into the 19.1 recovery and flash the ...dopinder.zip - I think manually flashing the latest recovery is unnecessary?
I would also appreciate knowing what the correct upgrade procedures are...I often feel like I'm guessing lol
Click to expand...
Click to collapse
just flash the 20 zip from recovery - that's all you need to do.

Related

[MASTER THREAD] Fire HD 8 (2017) (7th Generation)

Hi,
This is a list (incomplete) of all the ROMs, mods, hacks, guides, etc. available for the Fire HD 8 (2017).
This was a root progress discussion thread, and I think there's too much valuable information here to just let it get buried. So, following @Rortiz2's suggestion this thread was transformed to a master thread with the aim of providing a complete guide for anyone wanting to mod their tablet.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Device Codename: douglas
Specifications:
SoC: Mediatek MT8163
CPU: Cortex-A53 (Quad Core 4x1.3Ghz)
GPU: Mali 720
RAM: 1.5GB
Android: 5.1 (FireOS 5.x.x.x)
Storage: 16/32GB
Includes a MicroSD slot
Battery: 3210mAh
Display: 8"
Front Camera: 2MP
Rear Camera: 2MP
The italicized text below are my comments/clarifications.
The root method was patched in 5.6.4.0 (some versions of 5.6.4.0 still work so you could try) It is advisable to disable OTA updates or unlock the bootloader immediately. It is still possible to unlock by a different method, check the bootloader unlocking thread.
Bootloader Unlock and TWRP:
[UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 8 2017 (douglas)
This is an excellent and complete guide which has everything you need for this. Requires Linux, so you'll have to either install it as dual-boot or use a live system if you are not using it already. You don't need to downgrade if you are on 5.6.4.0.
Rooting:
You can flash Magisk using TWRP after bootloader unlock. Using Magisk is recommended because SuperSU is no longer supported, and Magisk has modules, Magisk Hide, and the root prompt is working (In SuperSU it's not working so you have to always grant root permissions which is a major security loophole)
Rapid Temporary Root for HD 8 & HD 10
This is the first software root method discovered for this tablet and is a really easy and quick method of getting a root shell, and the link has a complete guide on it. Refer here for installing SuperSU for permanent root, and here for an automated script for Windows.
[ROOT] Hardmod Root Your Amazon Fire HD 8 (7th Gen)
This is first root method ever discovered for this tablet and is a hardware root. This link has a complete step-by-step guide, assuming you have some soldering experience.
ROMs:
[ROM][unlocked]Lineage-12.1 for Amazon Fire HD8 2017 (douglas)
The first (and currently only) ROM for this device and it works great!
Miscellaneous:
Amazon Fire Toolbox, I have never tried this but it looks awesome!
Without root:
Removing accounts and viewing Usage Access settings which are hidden.
Debloating guide without root
With root:
A debloating guide made for HD 10, but works fine on the HD 8.
You can install apps as system apps just as on any other device, and you can use the app Link2SD for converting user apps to system apps. Refer to this StackExchange post for a guide on how to install apps as system.
Flashing GApps works well with TWRP, but the 16GB version doesn't have enough space in the system for even the pico version. Probably using pm uninstall on some system apps would work.
General Tips:
To return to stock or recover from a soft brick:
(Don't use this if you have already unlocked your bootloader: if you want just stock FireOS flash it through TWRP, and if complete stock follow the guide in the unlock thread)
(This assumes that you have ADB installed, I would not advise you on how here, there are numerous guides waiting for a Google search. This will erase your data.)
Download your current FireOS or a later firmware version. You can find the latest over at Amazon's website.
Boot to the recovery mode of your tablet, and use the volume and power buttons to select "Apply Update via ADB".
Now connect the tablet to a PC with a USB cabke, open a command prompt or shell on the directory where you downloaded the firmware BIN, enter the command adb sideload X.bin (replace X with the name of the BIN) and wait until finished (DON'T disconnect your device from the PC)
Now select "Wipe Data/Factory Reset" and "Yes" to wipe data (you can skip doing this if you want your data, but note that the tablet may bootloop or complain about corrupted data)
Select "Reboot system now"
The firmware BINs are just renamed ZIP files: you can rename it from .bin to .zip and treat it as such.
Amazon employs an anti-rollback mechanism which could permanently brick your device if you flash an older version through adb sideload. If you really want an older FireOS, you can rename .bin to .zip and flash them through TWRP after unlocking.
The stock launcher AppID is com.amazon.firelauncher, the stock keyboard is com.amazon.redstone, and the OTA update apps are com.amazon.device.software.ota and com.amazon.kindle.otter.oobe.forced.ota.
Again, this list is incomplete, so please suggest any additions in the comments! (don't hesitate to suggest your own work-the target of this thread to be a comprehensive and complete guide on everything about this tablet)
Good luck modding this tablet!

Thread before changing to a master thread (for historical purposes )
NOW WE HAVE AN UNLOCKING METHOD WITH TWRP! THE CONTENT BELOW IS OUTDATED.
Hi,
Now, I'm sick of Amazon's bloat slowing my tablet, and the frustration of not being able to use root apps. Fire HD 10 got rooted, but HD 8 and HD 7 are still in dark. HD 7 users can at least downgrade their devices and hope for a root exploit, but HD 8 users can't. If anyone else wanting to root this tablet and make it super fast, get rid of Fire Launcher, use Xposed, remove bloat, etc., let's collaborate with this!
LATEST RELEASE - Fire OS 5.3.6.4/Fire OS 5.6.3.4
SECURITY PATCH - ???
KERNEL VERSION - 3.18.19
List of possible software root methods:
1.) eMMC overwriting
Thanks to the hardware root method, we have a full eMMC dump so using the loophole in the flash unlock process which causes overwriting partitions next to it, we could overwrite on all the way, flashing original things, to the system partition and then flash a modified system partition.
Additions to the list are welcome!
List of possible exploits
Additions to list are welcome!
1.)CVE-2017-8890
Status: Confirmed possible.
Description: As I think, this is the most exploitable currently. Running the PoC results in 'somewhat unnatural' Use-After-Free s but the PoC fails to orient them to escalate privileges.
Cons: This exploit is based on obsolete IPv4 sockets, unlike it's cousin CVE-2017-9077, which is based on IPv6, but rather the same exploitation as this. That 'may' make this harder to exploit, but of course there's no evidence.
I, really only added this to cons because you should have a con.
2.)CVE-2017-15868
Status: Unsure
Description: NP Hardass said that this vulnerability is present on the source,I haven't explored it yet.
Cons: ¯\_(ツ)_/¯
If you tried these exploits, please notify me in below and I'll update the status. UPDATE: No point on keeping on trying these kernel exploits as no one (please correct me) who knows to write exploits in C comes here anymore. If someone wants to try though I will start maintaining this list again. Come on, let's collaborate on this!!! :laugh:
Thanks!
Download the eMMC dump from here: https://www.androidfilehost.com/?w=files&flid=282721
PS: You can download original kernel sources from Amazon, just search for it.
Original Thread:
Hi,
Now, I'm sick of Amazon's bloat slowing my tablet, and the frustration of not being able to use root apps. Fire HD 10 got rooted, but HD 8 and HD 7 are still in dark. HD 7 users can at least downgrade their devices and hope for a root exploit, but HD 8 users can't. If anyone else wanting to root this tablet and make it super fast, get rid of Fire Launcher, use Xposed, remove bloat, etc., let's collaborate with this!
LATEST RELEASE - Fire OS 5.6.0.1
SECURITY PATCH - 2017/08/01
KERNEL VERSION - 3.18.19*
*a quite old release it is.
List of possible exploits
Additions to list are welcome!
1.)CVE-2017-12762
Status: Unsure
Description: A super likely-to-work great exploit. If you want you can go look at the kernel source (link included below the thread) 3.18.19 for proof, it starts in line 2640. Looks like a stack buffer overflow.
Cons: ASLR may be an absolute game killer in this case. And some skill is required to exploit, very less-known around the internet. And Amazon may have removed the ISDN support up from the roots of kernel, because it's VERY deprecated.
2.)CVE-2017-16939
Status: Unsure
Description: A nice attack vector. A PoC is available in SecuriTeam blogs, which triggers use-after-free. I tried contacting them for some help, but they almost instantly replied that they don't provide support for their reported vulnerabilities. Sad.
Cons: ¯\_(ツ)_/¯
3.)CVE-2017-15868
Status: Unsure
4.)CVE-2017-10661
Status: Unsure
5.)CVE-2017-7541
Status: Unsure
6.)CVE-2017-6074
Status: Unsure
If you tried these exploits, please notify me in below and I'll update the status. Come on, let's collaborate on this!!! :laugh:
Thanks!

I added the link to the vulnerable code, in case anyone was wondering.

I'm glad to see this thread. Since recently rediscovering the potential of an old Fire 6 and rooting it, removing the bloat and Googlizing it, I wanted to get something a little bigger. I just got my 7th gen HD 8 in the mail yesterday and was devastated to see it was 5.4.0.1. I've blocked OTA, deleted the update it had downloaded, installed Google Play et al., and used NoRoot Data Firewall to block all Amazon apps. Unfortunately, I do not have the expertise to contribute much toward an effort to root this device but would like to help in any way. I appreciate seeing others are out there working on it.

if i knew how to develop the exploits i would honestly try these

Thank you so much for making this thread but I hope I never have to come back here and help, but if i get some extra time in the future I do plan on running all my binaries + servers on the tablet as well. Not to mention just looking at that version number made me want to vomit.

[/COLOR]What steps should I take to increase performance on the hd 8 while we wait for root?

rawfullz said:
[/COLOR]What steps should I take to increase performance on the hd 8 while we wait for root?
Click to expand...
Click to collapse
Hello rawfullz!
Try Greenify. You can use a workaround to grant it Usage Access.
1) Download Activity Launcher and Greenify from Play Store.
2) Launch Activity Launcher.
3) Notice the "Recent" text in the task-bar, press it, and select "All" from the drop-down list.
4) Scroll all the way below until you find "Settings", and press it.
5) Again, scroll below until you find "Apps with usage access", and press it.
6) The hidden "Apps with usage access" menu will pop up.
7) Grant Greenify usage access there. (You can turn off usage access for all Amazon apps if you want, to increase performance but it's recommended to leave out "Storage Management" intact, just in case.)
8) Launch Greenify, and continue with the setup.
9) :laugh::laugh::laugh::laugh:
If you ever want to grant any other app Usage Access, do this procedure, but, remember that "Activity Launcher" is kind of dangerous, if you just launch random activities. I learned that the hard way.

REMOVED

Thank you for making this thread, im looking forward to this become real.

What I dont get is you can download the firmware.bin as well as the source code from amazon, Whats the problem devs should be able to root ?

derwoodbones said:
What I dont get is you can download the firmware.bin as well as the source code from amazon, Whats the problem devs should be able to root ?
Click to expand...
Click to collapse
Hello!
Yes, we definitely can get the firmware. But there are some troubles,
1. Amazon devices are not very well known among the community.
2. Devs don't want to spend their time on our devices, even if we root this thing, no custom ROMs because of the locked bootloader.
3. Amazon didn't leave any loopholes on their OS, they are too clever.
And, I don't think that Amazon will open source their firmware until they checked throughly for any exploits.
We'll have to find exploits the rough way. :crying:

Hey, what about the Janus vulnerability? If some dev is reading this, please help us, because it doesn't require the device.

Supersonic27543 said:
Hello!
Yes, we definitely can get the firmware. But there are some troubles,
1. Amazon devices are not very well known among the community.
2. Devs don't want to spend their time on our devices, even if we root this thing, no custom ROMs because of the locked bootloader.
3. Amazon didn't leave any loopholes on their OS, they are too clever.
And, I don't think that Amazon will open source their firmware until they checked throughly for any exploits.
We'll have to find exploits the rough way. :crying:
Click to expand...
Click to collapse
You don't need an unlocked bootloader to flash a ROM.

Take a look at the BT stack with BlueBorne.
Sent from my iPhone using Tapatalk

Supersonic27543 said:
Now, I'm sick of Amazon's bloat slowing my tablet
Click to expand...
Click to collapse
You forgot to add: "and I wanna to fill my tablet by the Google's bloatware (2 times slower than Amazon's), and also add some rootkits and spyware masked as "super-duper tools for young hackars"

Great to see this thread. Hope some devs collaborate and find a way. Can't wait.
Meanwhile, do you guys have any cool mod to try in the tab.
I have installed playstore and adfree iytb YouTube and bunch of usual apps.

Hello!
DragonFire1024 said:
You don't need an unlocked bootloader to flash a ROM.
Click to expand...
Click to collapse
Yes, you don't need an unlocked bootloader to flash a ROM, theoretically, if the ROM is signed by Amazon. But considering custom ROMs, Lineage, Resurrection Remix, Stock Android, is it possible to compile and flash them without an unlocked bootloader? I thought that you need a custom recovery = unlocked bootloader. Thanks!
sensboston said:
You forgot to add: "and I wanna to fill my tablet by the Google's bloatware (2 times slower than Amazon's), and also add some rootkits and spyware masked as "super-duper tools for young hackars"
Click to expand...
Click to collapse
Hah. :laugh::laugh::laugh:
Robius said:
Take a look at the BT stack with BlueBorne.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Great idea, gotta try this! Thanks!
EDIT: Not very confident though. Anyway, likely to work because the security patch of HD 8 is in August.
http://www.androidpolice.com/2017/0...atch-fixes-blueborne-bluetooth-vulnerability/

Someone got a bluetooth adapter handy?

Supersonic27543 said:
Hello!
Yes, you don't need an unlocked bootloader to flash a ROM, theoretically, if the ROM is signed by Amazon. But considering custom ROMs, Lineage, Resurrection Remix, Stock Android, is it possible to compile and flash them without an unlocked bootloader? I thought that you need a custom recovery = unlocked bootloader. Thanks!
Hah. :laugh::laugh::laugh:
Great idea, gotta try this! Thanks!
EDIT: Not very confident though. Anyway, likely to work because the security patch of HD 8 is in August.
http://www.androidpolice.com/2017/0...atch-fixes-blueborne-bluetooth-vulnerability/
Click to expand...
Click to collapse
Ask @ggow how he does it. But you don't need a unlocked bootloader. With root, FlashFire helps to get by the bootloader.

[ROM][UNOFFICIAL][10] LineageOS 17.0 for K-touch i9 mini-phone (Anica i9) (MT6739)

Introduction
This is the LineageOS 17.0 (non-GSI) port for K-touch i9 a.k.a Anica i9. Due to the lack of kernel source code, this port comes with a prebuilt kernel image, but the ramdisk has been updated to support a proper System-as-Root system partition as is required by Android 10.
This is ONLY compatible with the MT6739 variant of this phone.
About the phone
The K-touch i9 is an ultra-mini phone produced by K-touch (Ktouch / Anica) based on the MT6739 SoC. I got the phone purely due to its interesting size (similar to the Palm phone) and the desire to port real custom ROMs to it to see if they can work well. I mainly use it as a backup phone, so this port might not be thoroughly tested enough for daily drive.
Known Issues
- Some particular animation / gifs will skip frames or repeat incorrectly
Images
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flashing instructions
1. Unlock the phone (reboot to bootloader by holding volume up on boot, run `fastboot flashing unlock` and confirm)
2. Flash TWRP image from here
3. Reboot to recovery (hold volume up and choose Recovery accordingly)
4. Backup all stock partitions whatever way you like (especially boot / vendor)
5. Flash this LOS 17 port image and format data
6. Reboot and enjoy
Please note that after flashing this LOS 17 image, you have to restore the stock boot.img before being able to install A-only Android 10 GSIs again. Although you MIGHT be able to boot phh A/B GSI 10 on the boot.img of this LOS 17 port, please note that this is not tested and you still need to shrink the image size before phh GSIs can work -- the same as the A-only situation.
Why not GSI
There is no reason why not to use a phh GSI on this phone, given that phh GSIs work pretty well and I have actually fixed a few bugs for it too and I absolutely love it. However we can't play with some certain things, for example, transitioning to System-as-Root, in a GSI, and that's why I started this port just for fun. Also this device has such a small system partition that GSIs won't work out-of-the-box and require some manual adjustments just for the device, which kind of defeats the purpose. Nevertheless, I will contribute my fixes to GSIs so that things will work as well on GSIs as on my device-specific ROM ports.
Downloads
20191025: https://www.androidfilehost.com/?fid=4349826312261605900
Alternatively, you may check the latest updates to both the TWRP and the LOS 17 port on my GitHub
Source code
https://github.com/PeterCxy/android_device_ktouch_i9
There is no kernel source code available for this device, unfortunately.
Credits
all the people that have worked on MTK devices before me.

twrp link does not work

theleftykid said:
twrp link does not work
Click to expand...
Click to collapse
It works here. It links to a GitHub release page where you can download recovery.img for TWRP

Hi,
I bought this phone, but with different CPU- MT6580, 5MP camera at the back, would this ROM be compatible with it well?
I've tried to flash the TWRP recovery, but it failed - "FAILED (remote: size too large)" so it mean the recovery image not compatible with my phone?
This device is really nice, but huge let down by the operation sys. The battery drain really fast, always "phone idle" take place at the top of battery consuming chart.
Thank you!

hi, i have tried to flash the twp from your github site. i get an error that flashing was FAILED, file is too large. my unit is Ktouch/anica i9s with October 2019 update.
is there any chance you can upload the original recovery.img as well pls.. thank you.

theleftykid said:
hi, i have tried to flash the twp from your github site. i get an error that flashing was FAILED, file is too large. my unit is Ktouch/anica i9s with October 2019 update.
is there any chance you can upload the original recovery.img as well pls.. thank you.
Click to expand...
Click to collapse
Based on the previous comment before you, you seem to have the MT6580 version of the phone. This means you have a different and smaller gpt than the one from the OP that uses MT6739. You can't flash this ROM or any recovery from the MT6739 since they have different hardware and different partition layout. If you flash something, it will end with a nice brick
Cheers!

Rortiz2 said:
Based on the previous comment before you, you seem to have the MT6580 version of the phone. This means you have a different and smaller gpt than the one from the OP that uses MT6739. You can't flash this ROM or any recovery from the MT6739 since they have different hardware and different partition layout. If you flash something, it will end with a nice brick
Cheers!
Click to expand...
Click to collapse
Well, I’m sending myne back to get the mt3739 so I could mount 128gb sd card and to try this buil. It look promissing.

theleftykid said:
hi, i have tried to flash the twp from your github site. i get an error that flashing was FAILED, file is too large. my unit is Ktouch/anica i9s with October 2019 update.
is there any chance you can upload the original recovery.img as well pls.. thank you.
Click to expand...
Click to collapse
You boot into the original OS and the recovery will be back.

Thank you for this ROM.
I used it on my K-touch i10. Its the same as the i9 but the shape is slightly different.
I have the 3gb - 64gb version and it seems OK.
I had to use BiTGApps-Q for Playstore to appear.
I also had to go into the USB developer options to set up file transfer from a PC.
And no wallpaper app from holding on home screen.
I hope you keep this up to date else I might have to try and work out how to apply security patches.
Thanks again
EDIT. Oh so are you saying I could just try and install the GSI?
Edit. OK so Wellbeing and problems with Gapps is to do with Android 10 and gapps.

I also found twrp hard to control. The swipe action and pressing near the edge was difficult.
I don't have face recognition to unlock, not sure if that's because lineage os doesn't have it or the i9 doesn't, but certainly possible on my i10.
The swipe action in lineage is also difficult.
Thanks again. Just want to let you know.
Edit. Also a problem for me is when it's charging, touch screen gives the odd ghost press when used.
Ive found forcedoze useful with this phone.

Works with K-Touch M16?
Theoretically speaking this Rom should work in the K-Touch M16 as it has the exact same specs, processors, etc. Being the only difference is that it has a fingerprint sensor.
So I was wondering does anyone know if this custom ROM and TWRP works on the K-Touch M16.?

how do i download this rom. there are no active links available!

PeterCxy said:
Downloads
20191025: https://www.androidfilehost.com/?fid=4349826312261605900
Alternatively, you may check the latest updates to both the TWRP and the LOS 17 port on my GitHub
Source code
https://github.com/PeterCxy/android_device_ktouch_i9
There is no kernel source code available for this device, unfortunately.
.
Click to expand...
Click to collapse
From the first post

m16 tried
I have tried this with my M16, which is very similar to i9, same cpu same spec, got fingerprint though... no luck, unable to boot into recovery, anyone successfully done?

It worked with my K-touch i10.
I guess you should start looking at TWRP. If you have the same processor you should be able to get TWRP going.
Sorry no help here, maybe try a TWRP forum or something.

chinese bootloader
hi, i just got the phone so i wanted to flash this rom. but my bootloader is in chinese and i don't speak/read chinese.
can anyone here please help me get trough the bootloader so i do all the steps correctly.
i attached the picture from bootloader and also what google translate offers for translation.
does volume up and down works correctly on your devices? on my it just jumps one step down and up on ether up key or down key when i press and hold the key ti gradually turns volume up on ether up or down key.

I have an i10 and am no expert.
When I reboot and hold up-volune I get 3 options. Recovery, Fastboot and Normal in that order.
Are you sure your phone is the mt3769. As I had an i10 which was was MT6580 and I got those options. I did have Fastboot though. Sorry don't still have it for reference.

I just found out on youtube this menu should pop up when you press volume down + power on. But on my phone it also boots to this menu when i press volume up + power on. Guess i received defective volume buttons on my phone. Too bad as it is such a nice little phone.

Are you able to use the volume keys to move up and down the menu you took a picture of? Moving in this menu and selecting should be the up and down volume keys. Guess then you could see for sure if you have a key problem.
I did manage to take my phone apart as when I dropped it I managed to disconnect the screen cable inside but was lucky to be able to fix it.
---------- Post added at 12:23 PM ---------- Previous post was at 11:44 AM ----------
PeterCxy said:
...you still need to shrink the image size before phh GSIs can work...
...
Also, this device has such a small system partition that GSIs won't work out-of-the-box and require some manual adjustments just for the device, which kind of defeats the purpose. Nevertheless, I will contribute my fixes to GSIs so that things will work as well on GSIs as on my device-specific ROM ports.
Click to expand...
Click to collapse
Hello I'd like to update this for myself. I thought I'd use the GSI image but you say it needs resizing before use. Can you give me any pointers as to how you do this?

free30 said:
Are you able to use the volume keys to move up and down the menu you took a picture of? Moving in this menu and selecting should be the up and down volume keys. Guess then you could see for sure if you have a key problem.
I did manage to take my phone apart as when I dropped it I managed to disconnect the screen cable inside but was lucky to be able to fix it.
Click to expand...
Click to collapse
i am unable to enter the correct bootloader that gives you three options you mentioned before. i already contacted the seller to see what we can do cause i just received the phone. on this chinese menu i can navigate only down (pressing volume up or down moves the selection down) and i can select the item via power button.

[OFFICIAL/UNOFFICIAL] LineageOS 19.1 for Amlogic G12*/SM1 Family Devices

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Amlogic G12*/SM1 Family Devices
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Amlogic G12*/SM1 SoC family of devices.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed:
Official Builds:
deadpool - Google ADT-3
wade - Dynalink TV Box (4K)
Disclaimer: My unofficial builds have full Android TV Google Apps and some other goodies included. OTA's roll roughly once a month. Support not guaranteed or implied.
Unofficial Builds:
deadpool - Google ADT-3
dopinder - Walmart Onn UHD Box
sabrina - Chromecast with Google TV
wade - Dynalink TV Box (4K)
We also support a few development boards, but at least (for now, until we have time to write up instructions), you're on your own to figure out the install process and set things up:
m5 - Banana Pi M5
odroidc4 - Odroid C4
radxa0 - Rock Pi Radxa Zero
EDIT: The development boards don't boot on LineageOS 19.1 at the moment for some reason, we're looking into it.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
Recent apps/Multitasking menu doesn't launch.
(sabrina only) The remote firmware sometimes gets hung up, you can reboot to solve this issue.
(dopinder/sabrina) L1 is currently broken, this is what is holding up official builds for these devices.
Notes:
GApps are baked in on Unofficial builds - No, I will not be building without GApps included for this device. These builds are built, packaged, and signed by me, and not affiliated with LineageOS whatsoever.
Firmware is shipped in the ROM package for this device, so you'll end up on the newest version of compatible firmware after install. Please don't touch firmware partitions after install.
On the unofficial OTA is provided the same way officials would have them.
Find any more on an official build? Report them according to this guide.
FAQ:
Does L1 Widevine DRM break when I unlock my bootloader?
Nope, it works fine. L1 certificates, and the mechanism that reports is all still exist and work as expected.
Can I haz Netflix?
Yup! Play Store has it for you. Unless you're on dopinder or sabrina, but that will be fixed soon hopefully.
Is this Android TV or Google TV?
Android TV, with some of the better components of Google TV.
Can I go back to stock and relock the bootloader?
Yeah, grab the factory image for your device and flash it just like you would for a Pixel device, you can find the factory images here. Don't know it I'd relock though, consider that process largely untested on these device. Especially on sabrina, where you can't necessarily re-unlock should you ever want to.
Are these the stock codenames for these devices?
Astute observation, no, they are not. The ADT-3 is actaully `adt3`, but earlier in production is was `deadpool`, which is much cooler. The Dynalink box internally is extremely similar to the ADT-3, so we coined it `wade` after Wade Wilson, AKA deadpool. The Onn box is in the same family, but different enough to coin it `dopinder`, after, well, go watch Deadpool the movie I guess. sabrina is actually the codename given by Google - no clue as to the reason.
Does it pass SafetyNet?
Maybe - the only sure fire way it Magisk, as our boot loader is unlocked and can't be relocked safely.
Does the stock remote work?
Yup, just like it would on stock, in-remote-microphone and all! If it's an IR remote like wade's, it will even work in recovery!
Can we we support higher resolution than 4K, higher FPS, or HDR on non-certified screens?
Nope.
I have a very similar device! Can I install these builds and use them?
No. Please don't do that. You will brick your device, as we include firmware and bootloader images.
If you're a developer looking to help port to a new device, contact me.
Kernel Source: https://github.com/LineageOS/android_kernel_amlogic_linux-4.9
Contributors:
npjohnson
bgcngm
stricted
webgeek1234
deadman96385
trautamaki
luca020400
aleasto

i probably will write up install instructions for the `BananaPi-M5` and `Odroid C4` Soon™
its a bit more complicated than just booting into recovery and flashing it unfortunately

I managed to install this on the onn 4k tv box (I used a usb keyboard and flash drive in the recovery) and everything went fine while installing but now I'm just stuck at the boot animation. I've left it on for at least 30 minutes and it never goes anywhere. Here's the serial log: https://paste.ee/p/7PAxS
It pretty much just stops there except for the occasional healthd battery message.

Do these builds support Signature Spoofing to replace GApps with MicroG?

Big Dumb Object said:
Do these builds support Signature Spoofing to replace GApps with MicroG?
Click to expand...
Click to collapse
No, as MicroG doesn't emulate what Android TV needs. Different GMSCore.

lmore377 said:
I managed to install this on the onn 4k tv box (I used a usb keyboard and flash drive in the recovery) and everything went fine while installing but now I'm just stuck at the boot animation. I've left it on for at least 30 minutes and it never goes anywhere. Here's the serial log: https://paste.ee/p/7PAxS
It pretty much just stops there except for the occasional healthd battery message.
Click to expand...
Click to collapse
yeah, aware of the issue, it's video firmware not loading, building new builds now.
But for what it's worth, you don't need a keyboard or drive - you can adb sideload it over usb - easiest method, just like the wiki describes.

npjohnson said:
No, as MicroG doesn't emulate what Android TV needs. Different GMSCore.
Click to expand...
Click to collapse
Sad. I vaguely recalled something about that, but couldn't find any concrete proof when asked.
Please consider releasing the full Android as it was with Shield TV. I believe it will be in demand, given the negative attitude of a lot of power users towards Android TV.

Big Dumb Object said:
Sad. I vaguely recalled something about that, but couldn't find any concrete proof when asked.
Please consider releasing the full Android as it was with Shield TV. I believe it will be in demand, given the negative attitude of a lot of power users towards Android TV.
Click to expand...
Click to collapse
Eh, maybe once we're in a more functional state (eg. Hardware OMX gets fixed).

npjohnson said:
yeah, aware of the issue, it's video firmware not loading, building new builds now.
But for what it's worth, you don't need a keyboard or drive - you can adb sideload it over usb - easiest method, just like the wiki describes.
Click to expand...
Click to collapse
I couldn't figure out how to navigate the recovery menu. I tried the button on the side like in the stock recovery but pressing it did nothing and holding it would change the highlight color to green but it didn't actually run the option that was highlighted. It was detecting the button presses (there were keyevents in the serial log) so it isn't just a broken button. I tried doing adb sideload without selecting the option but I just got `adb: sideload connection failed: closed`

lmore377 said:
I couldn't figure out how to navigate the recovery menu. I tried the button on the side like in the stock recovery but pressing it did nothing and holding it would change the highlight color to green but it didn't actually run the option that was highlighted. It was detecting the button presses (there were keyevents in the serial log) so it isn't just a broken button. I tried doing adb sideload without selecting the option but I just got `adb: sideload connection failed: closed`
Click to expand...
Click to collapse
okay, figured it out, you need to hand flash DTB before booting recovery, will update instructions

npjohnson said:
okay, figured it out, you need to hand flash DTB before booting recovery, will update instructions
Click to expand...
Click to collapse
Sounds good. One more question, is this build using a 64-bit kernel? I'd like to use the app for my drone on a big screen and this box would've been perfect if the stock kernel wasn't 32-bit.

lmore377 said:
Sounds good. One more question, is this build using a 64-bit kernel? I'd like to use the app for my drone on a big screen and this box would've been perfect if the stock kernel wasn't 32-bit.
Click to expand...
Click to collapse
64-bit kernel, 32-bit userspace - aiming to do 64 bit userspace someday.

Do you have an ETA for when the next builds will be done?

lmore377 said:
Do you have an ETA for when the next builds will be done?
Click to expand...
Click to collapse
they're uploaded now - sorry, got caught up putting out fires at work all day today lol

npjohnson said:
they're uploaded now - sorry, got caught up putting out fires at work all day today lol
Click to expand...
Click to collapse
I'll try it and flashing dtb for the button in recovery in a bit

lmore377 said:
I'll try it and flashing dtb for the button in recovery in a bit
Click to expand...
Click to collapse
DTBO/DTB - they need to be in sync.

npjohnson said:
DTBO/DTB - they need to be in sync.
Click to expand...
Click to collapse
I flashed the two (I got them from here) and now the button and usb otg don't work at all. I tried to flash back to stock but the box got stuck on the can't load android system screen and it was ignoring all my attempts at interacting with it (it was even ignoring Ctrl+C in uboot), but luckily I managed to boot into the lineage os recovery by putting it on a flash drive and holding down the button then wiping /misc thru the serial console.

lmore377 said:
I flashed the two (I got them from here) and now the button and usb otg don't work at all. I tried to flash back to stock but the box got stuck on the can't load android system screen and it was ignoring all my attempts at interacting with it (it was even ignoring Ctrl+C in uboot), but luckily I managed to boot into the lineage os recovery by putting it on a flash drive and holding down the button then wiping /misc thru the serial console.
Click to expand...
Click to collapse
I'll look into this... Can you try flashing the newest build through lineage recovery and wipe data?

npjohnson said:
I'll look into this... Can you try flashing the newest build through lineage recovery and wipe data?
Click to expand...
Click to collapse
Is there any way to activate sideload mode through adb shell or the serial console? Again, since the button isn't working (still works in uboot so it isn't a hardware issue) with the new dtb I can't navigate through the recovery menu.

lmore377 said:
Is there any way to activate sideload mode through adb shell or the serial console? Again, since the button isn't working (still works in uboot so it isn't a hardware issue) with the new dtb I can't navigate through the recovery menu.
Click to expand...
Click to collapse
Adb reboot sideload works, maybe just reboot sideload?
I'll go grab an Onn box at Walmart tmrw afternoon.
I know it works as 3 of our developers have and use it.
Just a matter of install process it seems...

General [Kernel] StarKissed B2Q [Raccoon City]

Current Kernel Improvements
Boeffla Wakelock Blocker v1.1.0
Wireguard v1.0.20210606
Patched SafetyNet commandline
Magisk process detection patch
Disable watermark boosting
Multicolor LED / PlayStation / Nintendo HID
Tuxera ExFAT / NTFS modules
Umbrella Core / Raccoon City [WIP]
Optimization from Kirisakura / StarKissed
raccoon_city (originally written for the Shield Tablet) is a new take on "interactive" by using a combination of low latency timers and the kernel scheduler to scale more aggressively (or less, if configured that way) based on workload, in addition to capping the max inactive frequency. The purpose is to provide a balance between good battery life and performance without handicapping the device.
umbrella_core (originally written for the Note 4 and ported to hundreds of other devices) takes raccoon_city a step further with automation. In addition to the full array of user settings, this governor features a smart mode that will adjust the base values within a set range to further optimize battery and performance.
The difference between these governors and the batterysaver implementation (also available) is the lack of arbitrary caps on max values during normal use. By controlling the workload, this allows better control over when the next frequency is reached, instead of whether it is available at all.
The default configuration idles at a max of about 800 mHz, but can be configured for each cluster, much like most settings.
The original source is provided through the public Samsung source under SM-F711B
Samsung Open Source
opensource.samsung.com
Building / Compiling Custom Kernels
starkissed-kernel-b2q/build at main · StarKissed/starkissed-kernel-b2q
Contribute to StarKissed/starkissed-kernel-b2q development by creating an account on GitHub.
github.com

I haven't finished setting up my phone to back it up, wipe it, and start over with an unlocked bootloader yet. If anyone is feeling really brave and wants to test the builds, though, you are welcome to contact me. Remember that I have absolutely no idea if they will even boot, though.

Temporarily delayed. See below.

I really want to try this but for the life of me I can't get any fastboot commands to work (waiting for any device) flashed every known usb/fastboot driver out there, changed ports/cables etc but no luck, ADB works fine. Is there a way to make it flashable through Magisk or Odin?

beanbean50 said:
I really want to try this but for the life of me I can't get any fastboot commands to work (waiting for any device) flashed every known usb/fastboot driver out there, changed ports/cables etc but no luck, ADB works fine. Is there a way to make it flashable through Magisk or Odin?
Click to expand...
Click to collapse
I've been looking for how to convert it. I missed a couple changes, so I'm trying to wrap those up first.

I have a feeling it will be much like the last few devices where you need to use FKM, EX, etc until such time as custom recoveries exist. I don't see any instances where anyone has converted a modern kernel to Odin (tar) format, which means I doubt there was much success.

@twistedumbrella Probably silly question. I've always wondered if video-out is a hardware or software limitation on this device, since it lack DeX and I can't get any other video signal via USB-c.
Q: In your Kernel, does it allow any video signal from "force desktop mode" or similar via the USB-c or do you think this is total no-go due to hardware limitation?
EDIT: oh wait sorry, I think you actually answered my question in a another thread, although I did not really understood if it was confirmed to be a hardware limitation or not.

Tracking down a couple modules that still need to be made inline. I thought I had converted all of them. Once that's done, we should be good to start releasing builds.
jacobsson said:
@twistedumbrella Probably silly question. I've always wondered if video-out is a hardware or software limitation on this device, since it lack DeX and I can't get any other video signal via USB-c.
Q: In your Kernel, does it allow any video signal from "force desktop mode" or similar via the USB-c or do you think this is total no-go due to hardware limitation?
EDIT: oh wait sorry, I think you actually answered my question in a another thread, although I did not really understood if it was confirmed to be a hardware limitation or not.
Click to expand...
Click to collapse
There is a lengthy discussion on reddit where they found the same results and came to the same conclusions. If no signal is possible, wired video out appears to be missing altogether.
Interesting enough there ARE disabled drivers for it. The only thing I don't know is if they would work. I guess the only real way to find out would be to enable them and find some lucky victi... I mean tester to see if they enable it.

This is going to be interesting...
I have a US unlocked model and rumors are surfacing that this means I cannot unlock the bootloader. It has been stated that this has been the case for many years. This contradicts my experience with the Note 20 Ultra, which was also a US unlocked model with OEM unlock available.
That said, until I can confirm that the bootloader can be unlocked, I am unable to test builds on my own device. I am, however, able to test very similar builds with the same changes on a device with similar hardware.
Assuming Samsung lives up to their history of releasing kernel source that builds out of the box, this should allow building working kernels with only those changes that have been tested on the other device. Please note that the base source is for the European device.
I highly recommend having all data backed up and am Odin restore ready until such time as the kernel has a few confirmations.

Here goes nothing...
starkissed-b2q-b5cf738.zip | by twistedumbrella for Galaxy Z Flip3 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com

Thanks for this, it looks very good but how do we flash it (whilst waiting for twrp) I've tried FKM, EX, Flashify, Magisk and Odin but all of them failed

beanbean50 said:
Thanks for this, it looks very good but how do we flash it (whilst waiting for twrp) I've tried FKM, EX, Flashify, Magisk and Odin but all of them failed
Click to expand...
Click to collapse
I guess this isn't a slot device like most of the newer ones. It would make sense not being one, but I didn't want to break anything being wrong. Assuming it had the slots when it didn't only fails. Assuming it didn't have the slots if it did could have caused a bad write. It was better to try with before trying without, since there is no fastboot to flat out check the device directly.
Here is a version without slots. Fingers crossed.
starkissed-b2q-17c6dd2a1e87.zip | by twistedumbrella for Galaxy Z Flip3 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com

No luck here, FKM said something about 'Magisk detected no need to ...' but I missed the rest of the log as it rebooted within 2 seconds of flashing. However, it got stuck on the Samsung logo upon rebooting, thankfully and eventually I got into download mode and re-flashed the stock rom and all's well again.

beanbean50 said:
No luck here, FKM said something about 'Magisk detected no need to ...' but I missed the rest of the log as it rebooted within 2 seconds of flashing. However, it got stuck on the Samsung logo upon rebooting, thankfully and eventually I got into download mode and re-flashed the stock rom and all's well again.
Click to expand...
Click to collapse
It should have been telling you magisk was detected, so there was no need to install again. I'll have to look back over everything. The hardest part is not being able to test it locally.

Here's the install log if it's any help ...

beanbean50 said:
Here's the install log if it's any help ...
Click to expand...
Click to collapse
Thanks. I think the issue is a few drivers that didn't inline. They hid them all over and Samsung added fuel to the fire by making individual configuration files for each platform (despite being identical).

ok the kernel is being in testing (or experimental), but who has tested it, noticed improvements in battery life? Thank you

iaio72 said:
ok the kernel is being in testing (or experimental), but who has tested it, noticed improvements in battery life? Thank you
Click to expand...
Click to collapse
we still can't flash it (see the post above your one) but the good news is that we should soon have twrp and a custom rom

Even if the kernel didn't fully boot, the good news is that it froze on the Samsung logo and didn't simply reboot. What that means is that, most likely, it really is as simple as tracking down why these drivers are building as modules and making them inline. I imagine, even with things how they are, that the kernel might boot given enough time. Nobody wants to wait that long, though.

[UMX U696CL- RELEASE THREAD]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Proudly Presents
Another Exclusive Release
Supported Model
UMX U696CL
Recoveries
TWRP_11 Recovery
Roms
GSI Roms - Arm32 Binder64 Required
AssuranceRom Custom Stock * WIP *
-AIO ToolKit Prerequisites-
1- Linux: Linux Mint Cinnamon Suggested
2- Python 3
Rom Notes/Disclaimer/Warning
* WIP *
Contributors
@gregeerg / BVK - for using his device as a ginuea pig to make this happen
@AndyYan - for his GSI knowledge and wisdom
@deadman96385 - for uploading dumped files to github
@Jet! - for flashing twrp and dumping stock super image
Big Thanks To The Folks In My A-Team Telegram Group
Big Thanks To The Folks Who Have Come To The A-Team Telegram Group To Help Test
Device Downloads
UMX U696CL Downloads
Recovery Device Trees
Device Source
A-Team Website
A-Team Supported Devices
TeleGram Live Support
A-Team Digital Solutions

-Updates-
5-18-2022- Initial AIO ToolKit v0.01 Release

I don't have telegram, is there anywhere else I can download some of this stuff from?
Thanks..

karl615 said:
I don't have telegram, is there anywhere else I can download some of this stuff from?
Thanks..
Click to expand...
Click to collapse
No sir, I don't put out untested stuff. I've gotten 0 feedback on the toolkit

How do we get feedback if no one can download here? we are not forcing anyone to install tiktok whatsapp instagram facebook telegram or any other crappy pipapo, keep development on xda-developers. Think about it

aIecxs said:
How do we get feedback if no one can download here? we are not forcing anyone to install tiktok whatsapp instagram facebook telegram or any other crappy pipapo, keep development on xda-developers. Think about it
Click to expand...
Click to collapse
I left a download link, unsure what you mean. If XDA would allow me to upload a 1.7gb 7zip file I would but that's not reality. I need stuff tested and chat to be fluid and prompt. That's not possible on a forum. In reality, If I had the device, I could test in 1 day what it would take a week to do on Telegram or 3 months to do on XDA forum. So for getting things done in a timely fashion, Telegram is my go to. I've been a member of XDA since 2012, I've done my time. If people don't want the toolkit or if joining telegram is too much, that's fine, not the people I want to help me test my software then anyways. The people who just want to grab a download and go can wait for the rest of the backend process. Again, I don't even have this device. So why am I even doing this is what i'm now wondering. I guess next time someone comes to me with a untouched device I won't help and use my resources to get something going....
it's alright though, you can consider this project shelved as I have a different hands on device I've already moved on to. Enjoy the twrp I built for you guys!.....

PizzaG said:
I left a download link, unsure what you mean. If XDA would allow me to upload a 1.7gb 7zip file I would but that's not reality. I need stuff tested and chat to be fluid and prompt. That's not possible on a forum. In reality, If I had the device, I could test in 1 day what it would take a week to do on Telegram or 3 months to do on XDA forum. So for getting things done in a timely fashion, Telegram is my go to. I've been a member of XDA since 2012, I've done my time. If people don't want the toolkit or if joining telegram is too much, that's fine, not the people I want to help me test my software then anyways. The people who just want to grab a download and go can wait for the rest of the backend process. Again, I don't even have this device. So why am I even doing this is what i'm now wondering. I guess next time someone comes to me with a untouched device I won't help and use my resources to get something going....
it's alright though, you can consider this project shelved as I have a different hands on device I've already moved on to. Enjoy the twrp I built for you guys!.....
Click to expand...
Click to collapse
Appreciated..
Update: flashed the recovery using 'fastboot flash recovery /path-to-.img' and the recovery works fine as far as I can tell, but the system is gone. Or something is up anyway, I can't get it to boot normally.. only to recovery. What did I do wrong?

Sorry Pizza i havent had the time to give feedback on it but i have the same issues booting. please dont let one person ruin it for everyone. i will hyu on telegram later today

PsYk0n4uT said:
Sorry Pizza i havent had the time to give feedback on it but i have the same issues booting. please dont let one person ruin it for everyone. i will hyu on telegram later today
Click to expand...
Click to collapse
Actually i havent had the time to get my linux machine setup correctly because of a memory leak issue that kept crashing my system but i finally got it running stable. i tried using relive on virtualbox but couldnt get it working properly due to driver issues in the host OS on this windows machine and for some reason i had more than one python version installed causing me conflicts. i ended up just using adb to flash the images and the phone no longer boots. i want to test it on a native linux os first

Well, folks...I'm about to give this a go....I still have a BLU View 3 to root today. Much gracias for all the effort

Cinephile 74 said:
Well, folks...I'm about to give this a go....I still have a BLU View 3 to root today. Much gracias for all the effort
Click to expand...
Click to collapse
Well I seem to have faux pas along the way.... bootloader unlocked easy-peasey. But I can't get fastboot to flash TWRP no matter what directory I use....RELP!

Is this the ROM or the bootable zip?

I'm back and about to try this again with an actual thumb drive with the ReLiveDVD on a thumb drive now that I have one

I downloaded A-Team-UMX_U696CL_AIO_ToolKit-v0.01.7z from the tg group and here's my feedback. I don't mean to sound ungrateful but:
Root does not work. I opened Main_Menu.sh and the root option literally does nothing. The lines are commented out and the image it was supposed to flash doesn't exist. Bootloader unlocking works (seems to literally be a single fastboot command i.e. "fastboot flashing unlock", seems like the new "oem unlock") and TWRP does work, but only once. If I flash it in fastboot and immediately reboot to recovery from there, I can get in. If I try to go to recovery after restarting, I get the dead android with the red ! triangle saying "no command". TWRP won't mount data (I think it said it couldn't decrypt, but I don't even have a lock code on it) so you need a micro sd to store the boot.img in order to patch it in Magisk. It would've been nice if you included it, though it seems you intended to but haven't gotten around to it since it's only v0.01. Still, it's not much of an all-in-one if it can't do the primary thing most people will want from it. I do fortunately have micro sd cards so I was able to save (manually in TWRP terminal using dd, annoying as hell on a touchscreen, can't even type "=" without going through 2 keyboard menus) and patch it in Magisk and now do have root working.
I don't understand why this requires Linux. The AIO doesn't do anything you can't do in Windows. The Python file is just an ASCII logo that makes you wait 10 seconds for no reason. It would have more user friendly as just a bunch of separate partition IMG uploads and instructions. I wish I had actually looked at the shell scripts beforehand instead of downloading a Linux distro and booting it as a live cd. If you make a new version, consider just including a portable adb/fastboot with it and skipping Linux/Python since it's not necessary.
After googling the "no command" screen, I held down power and pressed volume up and got into the regular Android recovery. So despite the bootloader being unlocked, it appears TWRP got overwritten by the default recovery. I flashed TWRP at least 3 times, immediately entering TWRP each time afterward, but it never stuck.
I'm attaching my Magisk'd boot.img in case anyone else gets stuck at that part. If anyone chooses to use it, MAKE YOUR OWN BACKUP FIRST, obviously. I'm not responsible for anything that happens using that file.

Eric janaika said:
TWRP does work, but only once.
Click to expand...
Click to collapse
proof that TWRP works for you, anything beyond is usage problem.

aIecxs said:
proof that TWRP works for you, anything beyond is usage problem.
Click to expand...
Click to collapse
I got twrp to stick but could not do anything with it since I didn't have an SD card before I misplaced the phone. Yes the scripts unfinished but as stated above somewhere, the dev did not have a device to test on.
If you wanna help, and it's probably the only way anyone else who isnt so knowledgable as many visiting xda seeking a way to root their device is gonna get this finished as well, please consider joining the telegram chat and contribute to this forum whatever you learn. Maybe Pizza will still be interested in helping. I tried but somehow misplaced the phone in the middle of filling in my huge gaps of knowledge on the subject.
I could not mount or wipe /data in twrp and even flashing the super.imgwould not allow me to boot because I was unable to do anything with the data partition. Had to flash the stock recovery to get it to boot period.
Maybe twrp will get you root if you patch your boot image with Magisk and flash it in twrp.
I'm not sure what else could be done. And not even sure that would work without being able to mount /data.
It's really hard for anyone working on a device they don't have to finish the work without some feedback from people who have enough knowledge to give them useful feedback.

The unlock bootloader option and the flash twrp recovery options work.
Script could be finished but I doubt there's much motivation for them since th3y don't own the device.
But the script is there. Most of the work on that part is done.
would only take some contributions by interested people.
PsYk0n4uT said:
I got twrp to stick but could not do anything with it since I didn't have an SD card before I misplaced the phone. Yes the scripts unfinished but as stated above somewhere, the dev did not have a device to test on.
If you wanna help, and it's probably the only way anyone else who isnt so knowledgable as many visiting xda seeking a way to root their device is gonna get this finished as well, please consider joining the telegram chat and contribute to this forum whatever you learn. Maybe Pizza will still be interested in helping. I tried but somehow misplaced the phone in the middle of filling in my huge gaps of knowledge on the subject.
I could not mount or wipe /data in twrp and even flashing the super.imgwould not allow me to boot because I was unable to do anything with the data partition. Had to flash the stock recovery to get it to boot period.
Maybe twrp will get you root if you patch your boot image with Magisk and flash it in twrp.
I'm not sure what else could be done. And not even sure that would work without being able to mount /data.
It's really hard for anyone working on a device they don't have to finish the work without some feedback from people who have enough knowledge to give them useful feedback.
Click to expand...
Click to collapse

what do you need a script for? read any random TWRP install guide steps are more or less same
- unlock bootloader
- patch avb/dm-verity/vbmeta
- install TWRP
- makesysrw super.img (optional)
- disable encryption (optional)

PsYk0n4uT said:
The unlock bootloader option and the flash twrp recovery options work.
Script could be finished but I doubt there's much motivation for them since th3y don't own the device.
But the script is there. Most of the work on that part is done.
would only take some contributions by interested people.
Click to expand...
Click to collapse
Agreed. PizzaG has done a bang up job with his UMX U696CL offerings, and his knowledge is extensive regarding custom ROMs and recoveries.

Eric janaika said:
I downloaded A-Team-UMX_U696CL_AIO_ToolKit-v0.01.7z from the tg group and here's my feedback. I don't mean to sound ungrateful but:
Root does not work. I opened Main_Menu.sh and the root option literally does nothing. The lines are commented out and the image it was supposed to flash doesn't exist. Bootloader unlocking works (seems to literally be a single fastboot command i.e. "fastboot flashing unlock", seems like the new "oem unlock") and TWRP does work, but only once. If I flash it in fastboot and immediately reboot to recovery from there, I can get in. If I try to go to recovery after restarting, I get the dead android with the red ! triangle saying "no command". TWRP won't mount data (I think it said it couldn't decrypt, but I don't even have a lock code on it) so you need a micro sd to store the boot.img in order to patch it in Magisk. It would've been nice if you included it, though it seems you intended to but haven't gotten around to it since it's only v0.01. Still, it's not much of an all-in-one if it can't do the primary thing most people will want from it. I do fortunately have micro sd cards so I was able to save (manually in TWRP terminal using dd, annoying as hell on a touchscreen, can't even type "=" without going through 2 keyboard menus) and patch it in Magisk and now do have root working.
I don't understand why this requires Linux. The AIO doesn't do anything you can't do in Windows. The Python file is just an ASCII logo that makes you wait 10 seconds for no reason. It would have more user friendly as just a bunch of separate partition IMG uploads and instructions. I wish I had actually looked at the shell scripts beforehand instead of downloading a Linux distro and booting it as a live cd. If you make a new version, consider just including a portable adb/fastboot with it and skipping Linux/Python since it's not necessary.
After googling the "no command" screen, I held down power and pressed volume up and got into the regular Android recovery. So despite the bootloader being unlocked, it appears TWRP got overwritten by the default recovery. I flashed TWRP at least 3 times, immediately entering TWRP each time afterward, but it never stuck.
I'm attaching my Magisk'd boot.img in case anyone else gets stuck at that part. If anyone chooses to use it, MAKE YOUR OWN BACKUP FIRST, obviously. I'm not responsible for anything that happens using that file.
Click to expand...
Click to collapse
Did you flash this from fastboot or from twrp?

Database Info

welcome