Database Develop

[ROM] [TEST] Miui 10 for Oneplus 6t

I am not responsible for anything that happens to your device.
This is a port of MIUI 10 for the op6/6t
Flash at your own risk and make sure to check what's working. Logcats would be appreciated!
Instructions:
1: Flash OxygenOS 9.0.7 twice, this is very important
2: Extract the download somewhere
3: Run the OnePlus 6t flasher (make sure phone is still in fastboot/bootloader)
4: Reboot to TWRP (fastboot boot it if it dissapeared, if you install TWRP you must install Magisk)
5: Flash or adb sideload NFC fix that is included in the download
6: Reboot and install V4A Magisk module and enable headset and speaker, this fixes audio
7: Enjoy!
Download (v3):
MOD EDIT: LINK REMOVED
What works:
Everything except stuff in what doesn't work
What doesn't work:
NFC
Flashlight toggle (3rd party apps work)
MIUI camera (3rd party apps work)
Fingerprint (top priority - @nima0003 - me)
Audio fix #2:
Credits to @dougie313
Flash viper4android module
Grab root browser
Go to vendor\lib\soundfx folder and rename or delete all files in folder
Source code: https://github.com/OnePlusOSS/android_kernel_oneplus_sdm845
Credits: @nima0003 me @ProtoDeVNan0 for the current build
Dylan Neve
Omar

What is it based on? And will you keep working on it?

dennisbednarz said:
What is it based on? And will you keep working on it?
Click to expand...
Click to collapse
Yeah, it'll be hard to do so because of school but I will. It's based off of mi 8 Dev miui (same soc)

nima0003 said:
Yeah, it'll be hard to do so because of school but I will. It's based off of mi 8 Dev miui (same soc)
Click to expand...
Click to collapse
Ah, so it doesn't use OxygenOS as a base?
I'm personally very interested in a MIUI ROM for the OP6T and seeing that someone is willing to work on it makes me pretty happy.
What about features like the mute switch and in-display fingerprint sensor?

dennisbednarz said:
Ah, so it doesn't use OxygenOS as a base?
I'm personally very interested in a MIUI ROM for the OP6T and seeing that someone is willing to work on it makes me pretty happy.
What about features like the mute switch and in-display fingerprint sensor?
Click to expand...
Click to collapse
It's uses AOSP as the base rom, I'm pretty sure alert slider doesn't work yet, hell I'm not sure it even boots yet. But if someone is able to test and it boots stable I'll get to work on those type of things.

nima0003 said:
It's uses AOSP as the base rom, I'm pretty sure alert slider doesn't work yet, hell I'm not sure it even boots yet. But if someone is able to test and it boots stable I'll get to work on those type of things.
Click to expand...
Click to collapse
My 6T is my daily driver. I may back everything up later and test it out.
Wouldn't it be easier to use OOS as the base for better performance, easier porting of features and so on? Would also make most kernels compatible.

Am I correct in assuming this supports treble? If so, I'm sure it'll make it easier to focus on 6/6t features being added rather than worrying about troubleshooting compatibility ??

champ784 said:
Am I correct in assuming this supports treble? If so, I'm sure it'll make it easier to focus on 6/6t features being added rather than worrying about troubleshooting compatibility ??
Click to expand...
Click to collapse
Yes it is treble based, but I didn't even think of the basic bootable gsi. I'll look more into this, thanks for the idea.

dennisbednarz said:
My 6T is my daily driver. I may back everything up later and test it out.
Wouldn't it be easier to use OOS as the base for better performance, easier portion of features and so on? Would also make most kernels compatible.
Click to expand...
Click to collapse
Yes that's a great idea actually, I was just worried some framework stuff would get in the way but maybe not.

nima0003 said:
Yes it is treble based, but I didn't even think of the basic bootable gsi. I'll look more into this, thanks for the idea.
Click to expand...
Click to collapse
Sure thing! We finally got treble support via lineage os for the Moto Z2 Force, which really helped keeping the device alive. Also makes flashing a TON easier, so maybe it's a good place to start

I'm downloading to test, report back in a bit.

champ784 said:
Sure thing! We finally got treble support via lineage os for the Moto Z2 Force, which really helped keeping the device alive. Also makes flashing a TON easier, so maybe it's a good place to start
Click to expand...
Click to collapse
My dad traded his z2 force for a 6t. Rom support was good but everything was messed up, camera didn't focus, no safteynet...

nima0003 said:
My dad traded his z2 force for a 6t. Rom support was good but everything was messed up, camera didn't focus, no safteynet...
Click to expand...
Click to collapse
There are workarounds, but I think it being one of the earlier devices having A/B partitions and basically being abandoned by Moto made it a task. I still have mine, but I wonder if there's something wrong with my device because I can't really flash anything beside rooted stock Rom, which leads me to think it's just a tedious device and I'd rather focus on my new 6t which is FAR superior in every way!

champ784 said:
There are workarounds, but I think it being one of the earlier devices having A/B partitions and basically being abandoned by Moto made it a task. I still have mine, but I wonder if there's something wrong with my device because I can't really flash anything beside rooted stock Rom, which leads me to think it's just a tedious device and I'd rather focus on my new 6t which is FAR superior in every way!
Click to expand...
Click to collapse
Yeah same thing happened to my Xperia xc, I could only flash stock rom, not even rooted.

Flashing failed, error: invalid zip file format.

Dark Nightmare said:
Flashing failed, error: invalid zip file format.
Click to expand...
Click to collapse
Great, thank you, working on it.

You would be my hero
It is great to see other types of roms, instead of only los type roms. Great to switch between them over time.

nima0003 said:
Yes that's a great idea actually, I was just worried some framework stuff would get in the way but maybe not.
Click to expand...
Click to collapse
Hopefully not. Lot's of people prefer stock-based ROMs specifically for the reason that they're usually more stable, almost always better performant and always better for battery (with the exception of TouchWiz). And the whole feature thing is also useful.
Lot's of people base the ROMs of Lineage as it usually has hardware specific support, but as we don't have official lineage yet and it would still be a lesser experience than a stock ROM, I strongly advocate for the OOS base.
Wish I could help out but I'm not a developer. If you need something designed, contact someone at Xiaomi, OnePlus or Google, or if you need some piece of code some person is sitting on, let me know (on Twitter or Telegram @dennisbednarz as i don't use the forum DM system).

So basically you just ported the OS and want testers? As of now, OP6T is just 3 weeks old and hardly would anyone dare to try something that says 'I highly doubt it'll work' in the OP.

Can Not installed
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app

[EOL][MOD] BlackenedMod v3.1 (Pixel 3 / Pixel 3 XL)

Introduction:
Hello everyone!
The idea to this 'project' did blossom after having an conversation with @pkgnex in the past about the general idea of creating something else that follows what he started with his PK's Tuning Script for Pixel 2 (XL) but with a twist, mainly as a complement to his own thread that you can find here, but also with a completely different vision and focus on what the script itself should achieve (and deliver) for kind of results for myself and for all of you personally, of course, that wants to try it out and use it as a "daily driver".
Shortly explained.
These scripts is created with the goal of improving both battery life and performance on our Pixel 3 (XL) devices, and after a whole range of configurations and various set-ups, I've come up with something that, in my eyes, is worth sharing with all of you so that you can try it out yourself and judge on your own, with constructive feedback on what can be improved or added in future releases - if desired. My philosophy is, and will always be, this:
If something can be improved or altered in a positive way so the average user can feel and see a difference, then go for it. Non stop.
The latest release can be found here.
Disclaimer:
This is presented as "what if". If this modification screws up or breaks anything for you, I am not the one to be held responsible. It's a free will to try out this kind of changes/modifications/addons/tweaks, just don't blame the inventors for eventual bad results and/or screw-ups.
Note: These scripts is not recommended to be modified or customized by the user.
Features:
Reduced battery consumption
Device specific enhancements for best possible balance between battery life & performance
Enabled, and fully configured, Boeffla generic kernel wakelock blocker
Disabled a lot of useless stuff at kernel level (Improves battery life as well as performance)
CPUSet improvements & optimizations
Power efficiency enhancements
Wide IO block tuning (Reduces the possibility of hiccups, lags and overhead)
Possibly other miscellaneous things I've forgotten to write down here, both big and small.
Requirements/what you need for getting these scripts fully working:
An unlocked bootloader
Your own specific choice of kernel
Latest possible version of Magisk
Busybox for Android NDK Magisk Module by @osm0sis
Patience
Installation/How-To use & abuse:
1) Download the attached ZIP
2) Extract the scripts
3) Move the scripts to the following location;
/data/adb/service.d and give it the following & needed file permissions (0775)
4) Reboot your phone, let Android boot to the launcher and let Magisk boot service do its crucial magic (takes a few seconds before the scripts is fully up and running around behind the scenes)
5) Enjoy!
Note: If you still are unsure how to do for making my kernel configuration / modification work & be up and running behind the scenes, then please read @Phalanx7621 phenomenal guide here or check out @Phalanx7621 in-depth video here. The installation method is the same for all generations of released Pixels!
Credits:
@franciscofranco for all the information on which kernel wakelocks that is safe to block
@Phalanx7621 for his phenomenal how-to guide
@Lord Boeffla for his awesome generic kernel wakelock blocker
@pkgnex for inspiring me walking into this partially unknown territory.
@flar2 for his excellent EXKM application and ElementalX Kernel
@osm0sis for his Magisk Busybox module
Everyone that I've forgotten to mention here
Telegram:
If you want to try out betas / previews of my script before they are officially released, or just hangout and chat a little, then join the official Telegram group here
To-Do list:
Optimize and properly tune things even further for best possible balance between battery life, system responsivness and performance
Contributors:
@xFirefly93
Created: 2019-01-06
Last updated: 2019-10-25

Note: The changelogs have been strictly moved to the release posts.

Thank you for this, I will give it a try. I was hoping someone would come up with a script that we can use to automate whatever we want at the kernel level. I feel like this could make the stock kernel much better as far as battery life and performance. I know you said use whatever kernel, but Do you recommend using the stock kernel for this?

freebee269 said:
Thank you for this, I will give it a try. I was hoping someone would come up with a script that we can use to automate whatever we want at the kernel level. I feel like this could make the stock kernel much better as far as battery life and performance. I know you said use whatever kernel, but Do you recommend using the stock kernel for this?
Click to expand...
Click to collapse
Of course. BlackenedMod is universal across the whole Pixel 3 (XL) line-up, so it will work more than perfect with stock kernel, if that is what you are using!
:highfive:

On 2xl there was a file wich showed that mod works. How about 3 xl?

I remember on the pixel 2 XL there would be a file formed internal storage that showed that the script was working. That doesn't seem to happen on this device?

xFirefly93 said:
Of course. BlackenedMod is universal across the whole Pixel 3 (XL) line-up, so it will work more than perfect with stock kernel, if that is what you are using!
:highfive:
Click to expand...
Click to collapse
i was using proton kernel. so i went back to stock kernel through fastboot. upon booting the white google splash screen popped for about 1 sec then my phone rebooted and i got the your device is corrupt screen. i then rebooted to bootloader and loaded twrp img file. i then rooted the stock kernel with magisk. after that i still got the your device is corrupt message but i was able to continue after that and it booted up fine. so looks like you dont want to do this on stock kernel that is not rooted. heh.
it looks like my phone keeps saying my device is corrupted. i've restarted 2 times and both times it says that and you cant get past that screen unless you hit continue. any ideas how to get this to work without the phone doing that?

blaze9090 said:
On 2xl there was a file wich showed that mod works. How about 3 xl?
Click to expand...
Click to collapse
Gordietm said:
I remember on the pixel 2 XL there would be a file formed internal storage that showed that the script was working. That doesn't seem to happen on this device?
Click to expand...
Click to collapse
For now, you have to manually create a folder in your internal storage named "logs" (without quotes) because of some security kind of thing that Google have addee which prevents "automatically" created folders to even be made at all.
Otherwise the specific output log, that tells you if the script could execute or not, won't be generated because of a non-existing path / folder.
I will though look around for a possible workaround and see if it can be added directly within the BlackenedMod script for maximal flexibility directly on-the-fly.

freebee269 said:
i was using proton kernel. so i went back to stock kernel through fastboot. upon booting the white google splash screen popped for about 1 sec then my phone rebooted and i got the your device is corrupt screen. i then rebooted to bootloader and loaded twrp img file. i then rooted the stock kernel with magisk. after that i still got the your device is corrupt message but i was able to continue after that and it booted up fine. so looks like you dont want to do this on stock kernel that is not rooted. heh.
Click to expand...
Click to collapse
You need Magisk (=root) and the Busybox Magisk module for even being able to use BlackenedMod.

Installed in Pixel 3 with Botleggers and Proton V10, at the moment everything is perfect, thanks for the work! I will report results!
Enviado desde mi Pixel 3 mediante Tapatalk

gaseoso said:
Installed in Pixel 3 with Botleggers and Proton V10, at the moment everything is perfect, thanks for the work! I will report results!
Enviado desde mi Pixel 3 mediante Tapatalk
Click to expand...
Click to collapse
Enjoy!

xFirefly93 said:
You need Magisk (=root) and the Busybox Magisk module for even being able to use BlackenedMod.
Click to expand...
Click to collapse
it looks like my phone keeps saying my device is corrupted. i've restarted 2 times and both times it says that and you cant get past that screen unless you hit continue. any ideas how to get this to work without the phone doing that?

freebee269 said:
it looks like my phone keeps saying my device is corrupted. i've restarted 2 times and both times it says that and you cant get past that screen unless you hit continue. any ideas how to get this to work without the phone doing that?
Click to expand...
Click to collapse
Try with clean flashing stock firmware.

*Deleted*

xFirefly93 said:
Try with clean flashing stock firmware.
Click to expand...
Click to collapse
that worked. i backed up my current system image and data in twrp. then did the flash-all.bat without -w. then went back into twrp and rooted the stock kernel. then went back into twrp and restored my backup. thanks a lot. will report back on how its gone after a couple days.

Telegram:
Not for going off-topic far too much now but..
If you want to hang out a little, try previews / betas of BlackenedMod for Pixel 3 (XL) before they are officially released or just want to meet a lot of awesome people from every possible corner of the woeld - then join the official Telegram group, fully dedicated to the P3(XL) line-up here.
:highfive:

Will you eventually have different versions for different kernels or are you keeping the mod universal for the pixel 3 XL?

Gordietm said:
Will you eventually have different versions for different kernels or are you keeping the mod universal for the pixel 3 XL?
Click to expand...
Click to collapse
I am keeping it universal with everything good / great / greater than greatest from every kernel organized in the same package and place.

so i followed instructions, got it all done, rebooted, i'm good to go? don't need to do anything just set it up and go right?

Is there a way to tell if this is working?

[UNOFFICIAL][EXPERIMENT] TWRP for Galaxy Tab S7 Wifi

This is my first thread of this kind, so bear with me if I'm not formatting it quite right.
I've run a test build of TWRP 3 for the Galaxy Tab S7 Wifi (T870) against a customized version of the kernel that shipped with the T870OXM2BUC6 firmware. At this point, this is completely untested, as I do not currently have my tablet in a state where I can test it (I'm working on this).
Here is a link to the recovery image on my Google Drive:
twrp-gts7lwifi_BUC6.img
drive.google.com
I will post it to somewhere better once it has been verified as working.
My work was based on what Ian Macdonald did here:
TWRP for the Samsung Galaxy Tab S7+ 5G (T976B)
I'm stuck in TWRP loop with the new T970XXU1ATK3 firmware won't boot to system after the update. Is there anyway to fix this issue?
forum.xda-developers.com
My source code is available here:
TWRP Source
Kernel source
Device tree
I'm finishing a write-up of what I did to create this image now. I'll post a link to that on this thread later today.

Here is my write-up on how I did this.
tales_of_hackery/building_twrp.md at master · bxlentpartyon/tales_of_hackery
Contribute to bxlentpartyon/tales_of_hackery development by creating an account on GitHub.
github.com
I tried to make it as complete as possible, but quite a bit of work went into this, so I'm sure I've left out some details. If you attempt this yourself, please let me know if/where you run into issues and I'll update the document accordingly.

Note that, once I have confirmation that my build process is sound, I'll be happy to try and perform builds for other devices in this family as well, as long as kernel sources are available.
I've submitted a request to Samsung for the sources for the latest kernel for my device (T870XXU2BUF5). I'm not expecting a response until after the weekend, but I _think_ that they're obligated to provide the sources upon request.

bxlentpartyon said:
Note that, once I have confirmation that my build process is sound, I'll be happy to try and perform builds for other devices in this family as well, as long as kernel sources are available.
I've submitted a request to Samsung for the sources for the latest kernel for my device (T870XXU2BUF5). I'm not expecting a response until after the weekend, but I _think_ that they're obligated to provide the sources upon request.
Click to expand...
Click to collapse
when I requested the sources for my T970 it took over a month and I requested it 3 times.

bxlentpartyon said:
This is my first thread of this kind, so bear with me if I'm not formatting it quite right.
I've run a test build of TWRP 3 for the Galaxy Tab S7 Wifi (T870) against a customized version of the kernel that shipped with the T870OXM2BUC6 firmware. At this point, this is completely untested, as I do not currently have my tablet in a state where I can test it (I'm working on this).
Here is a link to the recovery image on my Google Drive:
twrp-gts7lwifi_BUC6.img
drive.google.com
I will post it to somewhere better once it has been verified as working.
My work was based on what Ian Macdonald did here:
TWRP for the Samsung Galaxy Tab S7+ 5G (T976B)
I'm stuck in TWRP loop with the new T970XXU1ATK3 firmware won't boot to system after the update. Is there anyway to fix this issue?
forum.xda-developers.com
My source code is available here:
TWRP Source
Kernel source
Device tree
I'm finishing a write-up of what I did to create this image now. I'll post a link to that on this thread later today.
Click to expand...
Click to collapse
I doubt that it'll work, I tried it a while ago (I didn't test it myself) with added firmware files, updated kernel and device tree stuff and I used a very custom upstreamed samsung sm8250 common kernel which I had good experience with but it had the same issue, your commits are mostly updates for the twrp a11 source and new kernel source, so the differrences from my build and yours are that I have a more custom and upstreamed kernel with firmware but you used the a11 twrp source (which manifest wasn't available for me when I made it).

Appreciate the effort, we do need devs here. But whats the actual point of twrp, when we have ZERO roms to flash.

Bushcat said:
I used a very custom upstreamed samsung sm8250 common kernel which I had good experience with but it had the same issue
Click to expand...
Click to collapse
Not sure what issue you're talking about here. The guy whose process I copied didn't seem to have problems, or at least not many significant ones.
If you did this same thing with a "very custom" kernel and were not successful, my instinct would be that the kernel was "too custom." The whole idea behind my method of customizing my kernel was to minimize the differences between what I built, and the kernel that Samsung shipped, which is known to be functional.

bs3pro said:
Appreciate the effort, we do need devs here. But whats the actual point of twrp, when we have ZERO roms to flash.
Click to expand...
Click to collapse
I did this partially as a learning exercise, to familiarize myself with the Android build process. I'm still obviously fairly new to the Android scene, but the biggest piece of TWRP that I hoped to utilize was the backup/restore functionality.
Eventually I'm planning to try and install openSuSE on my tablet natively, and I wanted to be sure that I have solid backups, for when I eventually screw up and trash my device. I've learned through talking with jhill a bit that I'll probably get by just fine with just the stock firmware available to re-flash, but I wasn't entirely positive about that when I started working on this, and I figured I'd already burned the time building the kernel, so I might as well finish the job

bxlentpartyon said:
I did this partially as a learning exercise, to familiarize myself with the Android build process. I'm still obviously fairly new to the Android scene, but the biggest piece of TWRP that I hoped to utilize was the backup/restore functionality.
Eventually I'm planning to try and install openSuSE on my tablet natively, and I wanted to be sure that I have solid backups, for when I eventually screw up and trash my device. I've learned through talking with jhill a bit that I'll probably get by just fine with just the stock firmware available to re-flash, but I wasn't entirely positive about that when I started working on this, and I figured I'd already burned the time building the kernel, so I might as well finish the job
Click to expand...
Click to collapse
Keep up the good work! Not complaining, just wish we had a couple devs making aosp. Thanks

bxlentpartyon said:
Not sure what issue you're talking about here. The guy whose process I copied didn't seem to have problems, or at least not many significant ones.
If you did this same thing with a "very custom" kernel and were not successful, my instinct would be that the kernel was "too custom." The whole idea behind my method of customizing my kernel was to minimize the differences between what I built, and the kernel that Samsung shipped, which is known to be functional.
Click to expand...
Click to collapse
There have been many people testing ianmacds build and trying to build twrp for the tab s7 but everybody had this blue screen issue which made the twrp screen unusable but you can use twrp from usb.
Ianmacd and other users tried it with a slightly modified kernel from samsungs source, I wanted to try a differrent kernel because samsungs kernel source can be ****ty sometimes so I tried an upstreamed lineageos samsung sm8250 common kernel (which I'm also using for my galaxy tab s7+ TWRP and PBRP builds and it's working well there) but it had the same issue. The Tab S7+ also has a small display issue in twrp but it's still usable, when hitting some ubttons in twrp you can sometimes see a small flickering stripe at the top. In twrp it's hard to notice but in PBRP this issue was very annoying because it happenned much mnore often and longer, it got very bad when you turn off and on the display in recovery, I was able to lower the glitches with some screen values like timeout but I wasn't able to fix this issue.
{
"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"
}

bxlentpartyon said:
I did this partially as a learning exercise, to familiarize myself with the Android build process. I'm still obviously fairly new to the Android scene, but the biggest piece of TWRP that I hoped to utilize was the backup/restore functionality.
Eventually I'm planning to try and install openSuSE on my tablet natively, and I wanted to be sure that I have solid backups, for when I eventually screw up and trash my device. I've learned through talking with jhill a bit that I'll probably get by just fine with just the stock firmware available to re-flash, but I wasn't entirely positive about that when I started working on this, and I figured I'd already burned the time building the kernel, so I might as well finish the job
Click to expand...
Click to collapse
Welcome to the tab s7/+ dev community, I'm searching for more devs and custom stuff for our devices but sadly we aren't many, I've started trying to make Lineageos for the tab s7+ a while ago (my first from the ground up tree but I maintain ResurrectionRemix official for the OnePlus 6T since january) and I got further in small steps but since I'm stuck at this kernel issue since a month (I don't have much time atm but I'll try harder soon), the kernel doesn't want to load the fstab, I tried los17 and 18, asked many devs about this issue (jimbok77 mentioned a los18 init issue for the galaxy 20 series), this is my first device with dynamic partitions and my last samsung device was a samsung galaxy s5 mini exynos G800F, you can find more about my progress here Interest thread s7+ Lineage os and in the tab s7/+ development telegram chat, and you can find testers at telegram chat by ianmacd.
My plans are to make a working lineageos and then postmarket os, ubuntu touch and jing os.
Mod Edit: TG links removed as per XDA Telegram Chat Rules.

Bushcat said:
There have been many people testing ianmacds build and trying to build twrp for the tab s7 but everybody had this blue screen issue which made the twrp screen unusable but you can use twrp from usb.
Ianmacd and other users tried it with a slightly modified kernel from samsungs source
Click to expand...
Click to collapse
Thanks for the explanation. From what I understood, nobody had really attempted a build for the T870 yet. I was unaware that it has been tried, but nobody has gotten it working. Judging from the fact that the TWRP source has been shown to be functional on the S7+, I'd assume that this is still a kernel issue, but knowing that certainly doesn't help anybody find what the actual issue is, haha.
Bushcat said:
Welcome to the tab s7/+ dev community, I'm searching for more devs and custom stuff for our devices but sadly we aren't many, I've started trying to make Lineageos for the tab s7+ a while ago (my first from the ground up tree but I maintain ResurrectionRemix official for the OnePlus 6T since january) and I got further in small steps but since I'm stuck at this kernel issue since a month (I don't have much time atm but I'll try harder soon), the kernel doesn't want to load the fstab, I tried los17 and 18, asked many devs about this issue (jimbok77 mentioned a los18 init issue for the galaxy 20 series), this is my first device with dynamic partitions and my last samsung device was a samsung galaxy s5 mini exynos G800F, you can find more about my progress here Interest thread s7+ Lineage os and in the tab s7/+ development telegram chat, and you can find testers at telegram chat by ianmacd.
My plans are to make a working lineageos and then postmarket os, ubuntu touch and jing os.
Click to expand...
Click to collapse
The "custom ROMs" side of things is something I don't really have any knowledge about. To be honest, I don't have a ton of interest in going down that road, at least at the moment, as I don't really understand what benefits I would get from a custom ROM. From my point of view, I'm much more interested in getting "plain old Linux" running on the device, as that makes it far more powerful and useful, IMO.
A big part of what I want to do with my device is to run gaming console emulators, and the whole added layer of complexity of needing to write a Java wrapper around an already-functional C program just to get it to run doesn't really appeal to me. Again, this could all be ignorance of the real possibilities on my part, but I'm just trying to give you an idea of where I'm coming from.
Thanks again for the explanation of the current state of TWRP, and the introduction to some of the rest of what's going on out there!

Bushcat said:
I doubt that it'll work, I tried it a while ago (I didn't test it myself) with added firmware files, updated kernel and device tree stuff and I used a very custom upstreamed samsung sm8250 common kernel which I had good experience with but it had the same issue
Click to expand...
Click to collapse
Arrrgh, you were right. I finally spent the time to fully root my tablet and get my TWRP build installed, but the end result was exactly like the screen pic you posted. You can see the top of the screen, but everything else is just blue. Being new to TWRP, I didn't know how to pull the log at the time to see if there were any obvious errors in it, and I've already flashed back to stock recovery at this point.
I'll give this another go sometime later this week, or over the weekend, and see if I can learn anything else.
If anyone has some basic TWRP debugging tips that would be helpful. From what I've seen the number one option is:
abd pull /tmp/recovery.log
But I'm not sure if that is still valid, or if there are other things that can be done.

Scratch some of what I said above. I determined that:
/cache/recovery/last_kernel.log
Contains the log buffer from TWRP booting my custom kernel, and:
/cache/recovery/last_kmsg*
Contain log buffers from regular kernel boots. I'm combing through these looking for any interesting differences now, but there's obviously a lot to comb through, and it takes some effort to determine what is expected to be different due to config differences, and what might actually be important.
At least I've got something interesting to stare at for a little while.

bxlentpartyon said:
Scratch some of what I said above. I determined that:
/cache/recovery/last_kernel.log
Contains the log buffer from TWRP booting my custom kernel, and:
/cache/recovery/last_kmsg*
Contain log buffers from regular kernel boots. I'm combing through these looking for any interesting differences now, but there's obviously a lot to comb through, and it takes some effort to determine what is expected to be different due to config differences, and what might actually be important.
At least I've got something interesting to stare at for a little while.
Click to expand...
Click to collapse
Anything you need help with? Unfortunately I'm only a web developer so I don't think my Pyhton, CSS, or HTML knowledge would help much in the development of custom recovery but if there's anything we can do I'm happy to contribute.

bxlentpartyon said:
I'd assume that this is still a kernel issue, but knowing that certainly doesn't help anybody find what the actual issue is, haha.
Click to expand...
Click to collapse
I put a lot of effort and tried hard to find out the issue source. Mixed and compiled many different dtbos but every attempt gave me exactly the same result. I used almost stock sammy kernel and my highly modified Amnesty build.
Click to expand...
Click to collapse

Btw I am currently using Linux Deploy with Sparkle overlay for graphics acceleration.
Kinda convenient choice if u do not mind chroot environment.

Jerry12798 said:
Anything you need help with? Unfortunately I'm only a web developer so I don't think my Pyhton, CSS, or HTML knowledge would help much in the development of custom recovery but if there's anything we can do I'm happy to contribute.
Click to expand...
Click to collapse
Unfortunately I barely know enough about Android/TWRP to even know what to ask for help with, haha. If you want to pitch in, I'd encourage you to get your feet wet and try to run a TWRP build and see if you can reach the same point that others have gotten to (i.e. blue screen). You can use the guide I posted above to attempt that. I'll be glad to help with any questions you have along the way.
From there, it seems like it's basically anybody's game at this point. Apply whatever knowledge you have to see if you can make progress on the current issue!

bxlentpartyon said:
Unfortunately I barely know enough about Android/TWRP to even know what to ask for help with, haha. If you want to pitch in, I'd encourage you to get your feet wet and try to run a TWRP build and see if you can reach the same point that others have gotten to (i.e. blue screen). You can use the guide I posted above to attempt that. I'll be glad to help with any questions you have along the way.
From there, it seems like it's basically anybody's game at this point. Apply whatever knowledge you have to see if you can make progress on the current issue!
Click to expand...
Click to collapse
Yea I've tried it but blue screened too. I know a few different devices I've messed around with before has had weird screen issues (flickering, off colors, etc) in TWRP.. I don't know if they had the sames issue we are or not but it seems probable.

I put a lot of effort and tried hard to find out the issue source. Mixed and compiled many different dtbos but every attempt gave me exactly the same result. I used almost stock sammy kernel and my highly modified Amnesty build.
Click to expand...
Click to collapse
At this point, I really want to think that the issue has something to do with how we're setting up/driving the display. I'm leaning away from it being an outright problem with the kernel (and definitely don't think it's the device tree), but I do wonder if the information in the kernel logs might help us find the problem.
In comparing logs from stock recovery (where video obviously works) with logs from TWRP, I can see some notably different values getting used for initial backlight/brightness settings, as well as some other differences related to the display.
Now, I don't know that the differences I've spotted actually matter, but the display in the T870 is obviously a different model than the larger one in the T976, where TWRP is functional, so it's certainly something to check at least. For now that's all I've really got, but I'll be digging into this more soon.

Question LineageOS for A33

Has anyone created a lineage rom for the A33? Can't find it.
To be clear, for me this forum is like a maze, i was previously searching for a rom for the galaxy S7 and could not find it anywhere but then a forum member sent me a link to an unofficial build which i installed and it works perfectly, so i really dont care about unofficial builds, i will take anything over the preinstalled google spyware, if you know where to find a lineageos build for the A33 please share it!!

I'm not even sure if there's a custom recovery for A33 yet, let alone a Lineage build. You could maybe attempt to patch stock recovery to allow fastbootd and use to to try and flash Lineage GSI as system.img
It's the only way I see it may work

ShaDisNX255 said:
I'm not even sure if there's a custom recovery for A33 yet, let alone a Lineage build. You could maybe attempt to patch stock recovery to allow fastbootd and use to to try and flash Lineage GSI as system.img
It's the only way I see it may work
Click to expand...
Click to collapse
I did not expect lineageos to be available for a very new phone, this is the only phone i can get for free from my provider that's why i asked.
As recovery i could use TWRP, or not?
Sorry i don't know what you mean by lineage GSI, could you please explain? What does GSI stand for and where can i get it?
Edit: just noticed you made a rom (RayOS) or atleast ported it for the A52, that's interesting!
I never heared about RayOS, is it similar to lineageos? Is there a official website?

For starters, let me know if you have a U.S. phone because if you do this whole conversation is moot.
Librem5OS said:
As recovery i could use TWRP, or not?
Click to expand...
Click to collapse
Well I don't see TWRP in this forum so, I'm guessing it's still not available. I've seen a few people patch their stock recovery to allow fastboot commands so, maybe that'll work.
Librem5OS said:
Sorry i don't know what you mean by lineage GSI, could you please explain? What does GSI stand for and where can i get it?
Click to expand...
Click to collapse
GSI is a Generic System Image. It can count as a "ROM" but it's not for a specific device. Without going too much into detail, ever since Google released Oreo they changed the way of how it works. Project Treble (you can look it up for more details) now separates the system and where the system takes its hw libs (called vendor). Because of this, it has opened the gate for GSI to act as ROMs. Developers can build a generic Lineage (or Lineage-like) system and it can pretty much work on most devices that have Project Treble (this is mandatory for devices released with Oreo and onwards). So, you can look up Lineage GSI on google and you'll be able to find it. The only downside to this as opposed to actual ROMs for devices is that since it's generic, some features may work for some brands and some features are broken on other brands. Unfortunately, every OEM has taken it upon themselves to implement Project Treble as they please and there are a few differences here and there, therefore GSI won't work the same for all brands.
Sorry to dump all this information to you, I hope you're still with me here lol. From what I've seen, GSI that are based on phhusson (a developer who is also known as phh) work pretty well on Samsung devices, so if you're interested you can look for GSI that say that they're based on his work.
Librem5OS said:
Edit: just noticed you made a rom (RayOS) or atleast ported it for the A52, that's interesting!
I never heared about RayOS, is it similar to lineageos? Is there a official website?
Click to expand...
Click to collapse
RayOS is OneUI based. I just took S21FE system (which has built in flagship features) and flashed them over to A-series phones which don't have most of those flagship features. Because this is Samsung to Samsung and they implement Project Treble pretty much the same across all their devices, be it mid-end or high-end, this was real easy to achieve and implement with a few fixes here and there. It's just my little personal project, I don't have a website for it.

ShaDisNX255 said:
For starters, let me know if you have a U.S. phone because if you do this whole conversation is moot.
Well I don't see TWRP in this forum so, I'm guessing it's still not available. I've seen a few people patch their stock recovery to allow fastboot commands so, maybe that'll work.
GSI is a Generic System Image. It can count as a "ROM" but it's not for a specific device. Without going too much into detail, ever since Google released Oreo they changed the way of how it works. Project Treble (you can look it up for more details) now separates the system and where the system takes its hw libs (called vendor). Because of this, it has opened the gate for GSI to act as ROMs. Developers can build a generic Lineage (or Lineage-like) system and it can pretty much work on most devices that have Project Treble (this is mandatory for devices released with Oreo and onwards). So, you can look up Lineage GSI on google and you'll be able to find it. The only downside to this as opposed to actual ROMs for devices is that since it's generic, some features may work for some brands and some features are broken on other brands. Unfortunately, every OEM has taken it upon themselves to implement Project Treble as they please and there are a few differences here and there, therefore GSI won't work the same for all brands.
Sorry to dump all this information to you, I hope you're still with me here lol. From what I've seen, GSI that are based on phhusson (a developer who is also known as phh) work pretty well on Samsung devices, so if you're interested you can look for GSI that say that they're based on his work.
RayOS is OneUI based. I just took S21FE system (which has built in flagship features) and flashed them over to A-series phones which don't have most of those flagship features. Because this is Samsung to Samsung and they implement Project Treble pretty much the same across all their devices, be it mid-end or high-end, this was real easy to achieve and implement with a few fixes here and there. It's just my little personal project, I don't have a website for it.
Click to expand...
Click to collapse
I am from the EU so i dont have a US phone.
Im not an expert so this whole information is a little more detailed than what i usualy deal with, had to read it twice lol. How is GSI different from the default google OS? Does it have google services injected or not?
From your description it sounds like the general stock rom for android.
I will check phhusson, however if GSI has google in it im not interested, i want privacy so no google.
I also never heared about OneUI, does it or does RayOS (your work) have google services in it or is it google free? I don't necessarly need lineage as my os, anything without google spyware will do the job.
-Thank you for the reply.

Librem5OS said:
How is GSI different from the default google OS? Does it have google services injected or not?
From your description it sounds like the general stock rom for android.
I will check phhusson, however if GSI has google in it im not interested, i want privacy so no google.
Click to expand...
Click to collapse
I think the best way to answer this question is by stating that most GSI's offer both a vanilla and gapps version. Vanilla meaning no Google services on them.
Librem5OS said:
I also never heared about OneUI
Click to expand...
Click to collapse
OneUI is the current OS name for all Samsung phones... That's what they name their version of Android
Librem5OS said:
does RayOS (your work) have google services in it or is it google free?
Click to expand...
Click to collapse
I leave the Google apps on, I use them so I don't remove them.
Librem5OS said:
I don't necessarly need lineage as my os, anything without google spyware will do the job.
Click to expand...
Click to collapse
Well then when you look for GSI, search for the term vanilla.

ShaDisNX255 said:
I think the best way to answer this question is by stating that most GSI's offer both a vanilla and gapps version. Vanilla meaning no Google services on them.
OneUI is the current OS name for all Samsung phones... That's what they name their version of Android
I leave the Google apps on, I use them so I don't remove them.
Well then when you look for GSI, search for the term vanilla.
Click to expand...
Click to collapse
Thank you now i know what ill have to look for!
[GSI][12] LineageOS 19.x GSI (A64B/64B)
Background: This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and...
forum.xda-developers.com
This seems to be the generic build you where talking about?
I was just a little confused if i should visit phhs github or xda.
After all his XDA thread says: You are STRONGLY ADVISED to try PHH's AOSP of equivalent version FIRST
So i did that and this is where it takes me https://github.com/phhusson/treble_experimentations/releases/tag/v414
However all the files extensions are .xz i have no idea what that means.
When i flashed lineage it said img.tar if i remember correctly.

{
"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"
}
Whats the difference between the two red marked? one says secure img the other only img?
As they say vanilla these must be the ones without google?
Or should i download these instead? If yes which one? I have no clue what the names stand for. Noticed one says ARM and the other doesnt. However what is the difference between those and what is the difference between all arm versions and all non arm versions?

Librem5OS said:
However all the files extensions are .xz i have no idea what that means.
Click to expand...
Click to collapse
The .xz extension is just an .img file compressed. You need to use something like 7zip to unzip the .img file inside.
Librem5OS said:
I was just a little confused if i should visit phhs github or xda.
Click to expand...
Click to collapse
Well as I mentioned before, many people base their work of phh. I guess this developer wants you to check phh's work first so that if it doesn't boot, you won't bother installing his work at all.
Librem5OS said:
When i flashed lineage it said img.tar if i remember correctly.
Click to expand...
Click to collapse
Tar is usually made for flashing with Odin. Looks like someone did the work of packing everything to make it easier for Samsung users to flash to their phones.

ShaDisNX255 said:
The .xz extension is just an .img file compressed. You need to use something like 7zip to unzip the .img file inside.
Well as I mentioned before, many people base their work of phh. I guess this developer wants you to check phh's work first so that if it doesn't boot, you won't bother installing his work at all.
Tar is usually made for flashing with Odin. Looks like someone did the work of packing everything to make it easier for Samsung users to flash to their phones.
Click to expand...
Click to collapse
Thanks for the help.
So as the title of his post says:
[GSI][12] LineageOS 19.x GSI (A64B/64B)​That does not mention any specific device, so i asume it should be compatible with any android device.
So if i have a huawai phone with android on it, i should be able to flash this GSI on it, correct?
If yes excuse me if that sounds stupid but huawai is known to be chinese spyware, what do you think about privacy on a huawai with lineage on it? Could it be that the chinese has some shady things so deep in the phone perhaps even hardware so that even flashing a custom rom wont guarantee privacy?
Also i checked on youtube how to install GSI and the person said, flashing GSI system img only installs the system but not a boot img so i wont be able to boot, im not sure what im supposed to think about this?
For beginngers what do i need? a recovery like twrp?
A boot img?
A system img?
Is the GSI all in one or are further steps required?
Also im not sure if sourceforge is a trustworthy download option.

Librem5OS said:
[GSI][12] LineageOS 19.x GSI (A64B/64B)​That does not mention any specific device, so i asume it should be compatible with any android device.
Click to expand...
Click to collapse
Well, also have to make sure you're using the correct system. As far as I know, there are arm builds, a64 builds and arm64 builds. That A64B/64B in the title makes me thin they're only offering a64 and arm64 builds, download the one according to your device. I don't know in which category A33 falls so I can't help you there. My first guess is always arm64.
Librem5OS said:
So if i have a huawai phone with android on it, i should be able to flash this GSI on it, correct?
If yes excuse me if that sounds stupid but huawai is known to be chinese spyware, what do you think about privacy on a huawai with lineage on it? Could it be that the chinese has some shady things so deep in the phone perhaps even hardware so that even flashing a custom rom wont guarantee privacy?
Click to expand...
Click to collapse
I've never owned a Huawei phone so I can't really comment if they can flash GSI flawlessly and/or if that helps with any privacy issues they may or may not have.
Librem5OS said:
Also i checked on youtube how to install GSI and the person said, flashing GSI system img only installs the system but not a boot img so i wont be able to boot, im not sure what im supposed to think about this?
Click to expand...
Click to collapse
The boot.img is the kernel, your phone already has a stock boot.img in it, no need to worry about it for now. If you dedice to use a GSI, a common bug in Samsung phones is that you won't be able to use MTP when connecting to a PC. This is usually fixed in custom kernels specifically made for AOSP ROMs and GSIs. It's a result of Samsung like doing things their own way.
Librem5OS said:
For beginngers what do i need? a recovery like twrp?
A boot img?
A system img?
Click to expand...
Click to collapse
Yes, you need a recovery capable of flashing custom system.img. It can be TWRP, OrangeFox or maybe just patching your stock recovery to be able to use fastboot commands.
Boot img is optional, as I mentioned above your phone already has one so no need to worry about it
System img is obvious, yes it's the GSI itself.
Librem5OS said:
Is the GSI all in one or are further steps required?
Click to expand...
Click to collapse
Usually GSI have all the same steps. Flashing the system and wiping data

ShaDisNX255 said:
Well, also have to make sure you're using the correct system. As far as I know, there are arm builds, a64 builds and arm64 builds. That A64B/64B in the title makes me thin they're only offering a64 and arm64 builds, download the one according to your device. I don't know in which category A33 falls so I can't help you there. My first guess is always arm64.
I've never owned a Huawei phone so I can't really comment if they can flash GSI flawlessly and/or if that helps with any privacy issues they may or may not have.
The boot.img is the kernel, your phone already has a stock boot.img in it, no need to worry about it for now. If you dedice to use a GSI, a common bug in Samsung phones is that you won't be able to use MTP when connecting to a PC. This is usually fixed in custom kernels specifically made for AOSP ROMs and GSIs. It's a result of Samsung like doing things their own way.
Yes, you need a recovery capable of flashing custom system.img. It can be TWRP, OrangeFox or maybe just patching your stock recovery to be able to use fastboot commands.
Boot img is optional, as I mentioned above your phone already has one so no need to worry about it
System img is obvious, yes it's the GSI itself.
Usually GSI have all the same steps. Flashing the system and wiping data
Click to expand...
Click to collapse
My bet was also arm64, i tend to just try it. If i want to be 100% sure propably wikipedia or the manufactuers tech specs should have info on that? a64b and 64b are entirely new to me.
TWRP is capable of flashing custom roms so if twrp is released for a33 nothing stops me from downloading and flashing the arm64 gsi onto the a33 right? I think twrp has been released for the a33 after looking here https://twrp.me/Devices/Samsung/
Just a question, if it wasn't released are there people on xda pushing their own version of twrp or similar recoverys in order to allow people to flash gsi or custom lineageos builds?

Librem5OS said:
My bet was also arm64, i tend to just try it. If i want to be 100% sure propably wikipedia or the manufactuers tech specs should have info on that? a64b and 64b are entirely new to me.
Click to expand...
Click to collapse
This is something I can't comment on. I know there are some apps on Playstore that tell you what type of system you can run but I don't know which can tell you accurate information (I personally don't use GSI). I wouldn't use any outside sources like Wikipedia or Google for that matter because of one small detail: Samsung's been known to put 64bit chips on their phones but force them to run in 32bits, even more on their lower end phones. A page may tell you that you have a 64bit chip but I don't think they know if it's even running in 64bits or not. Sorry, I can't be much help here.
Librem5OS said:
TWRP is capable of flashing custom roms so if twrp is released for a33 nothing stops me from downloading and flashing the arm64 gsi onto the a33 right?
Click to expand...
Click to collapse
This is correct
Librem5OS said:
I think twrp has been released for the a33 after looking here https://twrp.me/Devices/Samsung/
Click to expand...
Click to collapse
I think the TWRP available in the page you provided is not for the Galaxy A33 5G. It's actually for the Galaxy A3 (2015) whose model is A300H and for some weird reason Samsung gave it the device code-name 'a33g'. Yeah Samsung's very weird when it comes to their naming.
Librem5OS said:
Just a question, if it wasn't released are there people on xda pushing their own version of twrp or similar recoverys in order to allow people to flash gsi or custom lineageos builds?
Click to expand...
Click to collapse
Well, XDA usually has a set of requirements if you want to post something like a custom recovery. A custom recovery may already exist but it may not comply with XDA's requirements and could be a reason why it may not be posted yet. In my personal opinion, I'd download Telegram and search in public A33 Telegram groups any to see if maybe there's something in the works and/or something that could at least let you flash GSI.

ShaDisNX255 said:
This is something I can't comment on. I know there are some apps on Playstore that tell you what type of system you can run but I don't know which can tell you accurate information (I personally don't use GSI). I wouldn't use any outside sources like Wikipedia or Google for that matter because of one small detail: Samsung's been known to put 64bit chips on their phones but force them to run in 32bits, even more on their lower end phones. A page may tell you that you have a 64bit chip but I don't think they know if it's even running in 64bits or not. Sorry, I can't be much help here.
This is correct
I think the TWRP available in the page you provided is not for the Galaxy A33 5G. It's actually for the Galaxy A3 (2015) whose model is A300H and for some weird reason Samsung gave it the device code-name 'a33g'. Yeah Samsung's very weird when it comes to their naming.
Well, XDA usually has a set of requirements if you want to post something like a custom recovery. A custom recovery may already exist but it may not comply with XDA's requirements and could be a reason why it may not be posted yet. In my personal opinion, I'd download Telegram and search in public A33 Telegram groups any to see if maybe there's something in the works and/or something that could at least let you flash GSI.
Click to expand...
Click to collapse
My bad you are right the twrp for the "arr" shows the first release back in 2017 so that cant be the new 5g version...
If you say samsung uses 64 chipset but forces their phones to run on 32bit (idk how that makes sense) why cant i find a arm32 anywhere? I mean could be this question is out of topic too..
I just woonder if there is even a single person who currently owns the A33 and managed to flash lineageos / gsi onto the device and if so how did they do it, either everyone with that phone is using the stock rom unless they are an expert, or there are already custom recoverys and roms available for the public.
Either way in theory the GSI for android version 12 should/could be compatible with the A33 since it is as you said a generic build, but even if that would work i obviously need a custom recovery in order to flash the system on the device, kinda surprised me you mentioned telegram, i never used it as im not really into social media. I tought if there is a custom recovery my best bet would be XDA forums.
If there is no custom recovery i guess ill have to wait for a official twrp release, or an unofficial one on XDA.

Librem5OS said:
If you say samsung uses 64 chipset but forces their phones to run on 32bit (idk how that makes sense) why cant i find a arm32 anywhere? I mean could be this question is out of topic too..
Click to expand...
Click to collapse
I only said they've been known to on some lower end phones, not all. That's why I don't trust any website with that specific information. The reason why you aren't finding arm32 anywhere is because it's usually just referred to as arm in GSI builds.
Librem5OS said:
I just woonder if there is even a single person who currently owns the A33 and managed to flash lineageos / gsi onto the device and if so how did they do it, either everyone with that phone is using the stock rom unless they are an expert, or there are already custom recoverys and roms available for the public.
Click to expand...
Click to collapse
Well, can't really answer that. Maybe someone will post a way on XDA soon or maybe not.
Librem5OS said:
i obviously need a custom recovery in order to flash the system on the device
Click to expand...
Click to collapse
Correct
Librem5OS said:
kinda surprised me you mentioned telegram, i never used it as im not really into social media.
Click to expand...
Click to collapse
Personally I've seen a lot of developers share their work on Telegram first before publishing in XDA. As I mentioned before XDA has a set of requirements before being able to post something like a custom recovery . I also share my work there first so I can get people to test and report any bugs they may find before publishing a final build on XDA. Telegram is great because you don't need your phone to be on (you can use the PC client) as opposed to something like WhatsApp that is mandatory your phone be on.
Librem5OS said:
I tought if there is a custom recovery my best bet would be XDA forums.
Click to expand...
Click to collapse
That's what we all say of course lol

ShaDisNX255 said:
I only said they've been known to on some lower end phones, not all. That's why I don't trust any website with that specific information. The reason why you aren't finding arm32 anywhere is because it's usually just referred to as arm in GSI builds.
Well, can't really answer that. Maybe someone will post a way on XDA soon or maybe not.
Correct
Personally I've seen a lot of developers share their work on Telegram first before publishing in XDA. As I mentioned before XDA has a set of requirements before being able to post something like a custom recovery . I also share my work there first so I can get people to test and report any bugs they may find before publishing a final build on XDA. Telegram is great because you don't need your phone to be on (you can use the PC client) as opposed to something like WhatsApp that is mandatory your phone be on.
That's what we all say of course lol
Click to expand...
Click to collapse
Im having a problem with my old Huawai SCL-L01, this phone is slow and bad (only 1gb ram).
Atleast even when the devices is trash i wanted to install linage on it to atleast have privacy, as long as it's still working why not use it?
So the problem is i have usb debugging and oem unlock both activated, i installed adb fastboot / platformtools on my pc (which i downloaded here https://developer.android.com/studio/releases/platform-tools), i connected the phone to the pc and allowed data transfer over usb debugging by confirming the request which appears on the phone, i entered adb reboot bootloader into cmd.exe on the pc and the phone rebooted into bootloader, i then typed adb flash lineageos_rom.img
As a result instead of flashing the img, the cmd output "waiting for any device".
I dont know what is going wrong, what am i doing false in the process?
I was following the instructions here https://forum.xda-developers.com/t/index-list-of-roms-for-y6-2018.3854167/

Librem5OS said:
then typed adb flash lineageos_rom.img
Click to expand...
Click to collapse
Because you're using a adb instead of fastboot command. They're 2 different things
It's fastboot flash, not adb flash

ShaDisNX255 said:
Because you're using a adb instead of fastboot command. They're 2 different things
It's fastboot flash, not adb flash
Click to expand...
Click to collapse
I used: fastboot flash system recovery.img

Librem5OS said:
Thanks for the help.
So as the title of his post says:
[GSI][12] LineageOS 19.x GSI (A64B/64B)​That does not mention any specific device, so i asume it should be compatible with any android device.
So if i have a huawai phone with android on it, i should be able to flash this GSI on it, correct?
If yes excuse me if that sounds stupid but huawai is known to be chinese spyware, what do you think about privacy on a huawai with lineage on it? Could it be that the chinese has some shady things so deep in the phone perhaps even hardware so that even flashing a custom rom wont guarantee privacy?
Also i checked on youtube how to install GSI and the person said, flashing GSI system img only installs the system but not a boot img so i wont be able to boot, im not sure what im supposed to think about this?
For beginngers what do i need? a recovery like twrp?
A boot img?
A system img?
Is the GSI all in one or are further steps required?
Also im not sure if sourceforge is a trustworthy download option.
View attachment 5678691
Click to expand...
Click to collapse
Great to meet someone who also uses pagexray.fouanalytics.com
Yeah sourceforge is not trustworthy at all...
I always get confused by sourceforge.net and curseforge.com
One of them is owned by twitch or overwolf which are owned by amazon = bigtech.
Anyways, looking at forum.xda-developers.com makes me worry...

I believe you can use any LineageOS GSI, but you'd need to flash it in a custom recovery such as TWRP while retaining the stock kernel in /boot.

Question GSI Anyone? (maybe some dev interest?)

Opening up this thread in hopes some interest can be made.
Since the beta version of Android 13 dropped, I decided to boot into GSI roms to achieve root. To my surprise, not only did the GSI rom boot, but I was able to go through the google setup like a champ. Every now and again, I load different GSI roms to test and I am currently using Google QPR2. As it stands the following works:
What Works
Opening and closing the device actually works and renders content in open and closed state
Cellular/wifi radio works
Touchscreen works but there's issues (see below)
Camera works (albeit not as well as the pixel camera ports)
Notifications fully work
Android Auto works
SMS works
There is a very big problem with using the GSI - the device detects inputs from both screens whether opened or closed. So here's a list of what doesn't work:
Not working
Touch input (as previously described)
Phone features (phone vibrates but dialer never displays)
Battery isn't optimized (given)
If you want to test it and provide some feedback, I am using this GSI rom:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
As always to install GSI roms, bootloader must be unlocked. To install, use DSU Loader. It's a rather painless process

domineus said:
Opening up this thread in hopes some interest can be made.
Since the beta version of Android 13 dropped, I decided to boot into GSI roms to achieve root. To my surprise, not only did the GSI rom boot, but I was able to go through the google setup like a champ. Every now and again, I load different GSI roms to test and I am currently using Google QPR2. As it stands the following works:
What Works
Opening and closing the device actually works and renders content in open and closed state
Cellular/wifi radio works
Touchscreen works but there's issues (see below)
Camera works (albeit not as well as the pixel camera ports)
Notifications fully work
Android Auto works
SMS works
There is a very big problem with using the GSI - the device detects inputs from both screens whether opened or closed. So here's a list of what doesn't work:
Not working
Touch input (as previously described)
Phone features (phone vibrates but dialer never displays)
Battery isn't optimized (given)
If you want to test it and provide some feedback, I am using this GSI rom:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
As always to install GSI roms, bootloader must be unlocked. To install, use DSU Loader. It's a rather painless process
Click to expand...
Click to collapse
hello and thank you very much for this feedback. after having watched this forum for a very long time, it is time for me to buy this magnificent smartphone because I have always used gsi pixel experience roms. but I would still like to have your opinion on the sound quality of this beast because on no comment and test nobody talks about it

Bwhite... said:
hello and thank you very much for this feedback. after having watched this forum for a very long time, it is time for me to buy this magnificent smartphone because I have always used gsi pixel experience roms. but I would still like to have your opinion on the sound quality of this beast because on no comment and test nobody talks about it
Click to expand...
Click to collapse
GSI depends solely on a bootloader unlock. Unless you get an older device that hasn't been updated, I wouldn't purchase the device with the assumption that root is easy...

domineus said:
GSI depends solely on a bootloader unlock. Unless you get an older device that hasn't been updated, I wouldn't purchase the device with the assumption that root is easy...
Click to expand...
Click to collapse
Yes indeed I understand that. but I read on the forum that unlocking the bootloader was back on a september update. but the question I ask myself more is the sound quality of the dual speakers. anyway thank you very much for your answer.

Bwhite... said:
Yes indeed I understand that. but I read on the forum that unlocking the bootloader was back on a september update. but the question I ask myself more is the sound quality of the dual speakers. anyway thank you very much for your answer.
Click to expand...
Click to collapse
I'm not sure. THere are some who tried who weren't able to bootloader unlock for the September update or afterward.
Sound quality is subjective but I had zero complaints from the speakers

domineus said:
I'm not sure. THere are some who tried who weren't able to bootloader unlock for the September update or afterward.
Sound quality is subjective but I had zero complaints from the speakers
Click to expand...
Click to collapse
ok thank you for all this useful information.

Sorry for the stupid question, but what is GSI? is this a custom rom?

NeoGoku123 said:
Sorry for the stupid question, but what is GSI? is this a custom rom?
Click to expand...
Click to collapse
Generic System Images (GSIs) | Platform | Android Developers
developer.android.com

domineus said:
Opening up this thread in hopes some interest can be made.
Since the beta version of Android 13 dropped, I decided to boot into GSI roms to achieve root. To my surprise, not only did the GSI rom boot, but I was able to go through the google setup like a champ. Every now and again, I load different GSI roms to test and I am currently using Google QPR2. As it stands the following works:
What Works
Opening and closing the device actually works and renders content in open and closed state
Cellular/wifi radio works
Touchscreen works but there's issues (see below)
Camera works (albeit not as well as the pixel camera ports)
Notifications fully work
Android Auto works
SMS works
There is a very big problem with using the GSI - the device detects inputs from both screens whether opened or closed. So here's a list of what doesn't work:
Not working
Touch input (as previously described)
Phone features (phone vibrates but dialer never displays)
Battery isn't optimized (given)
If you want to test it and provide some feedback, I am using this GSI rom:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
As always to install GSI roms, bootloader must be unlocked. To install, use DSU Loader. It's a rather painless process
Click to expand...
Click to collapse
Considering this for a x fold plus.
Were you able to fix the issues and if not, to what to extent are the effects. For example, with the battery not optimized how does it last and with the dialer not displaying are you able to answer the call? Touch input I assume is mostly an issue when using the larger screen (i.e. you accidentally input from the front screen).

NikG25 said:
Considering this for a x fold plus.
Were you able to fix the issues and if not, to what to extent are the effects. For example, with the battery not optimized how does it last and with the dialer not displaying are you able to answer the call? Touch input I assume is mostly an issue when using the larger screen (i.e. you accidentally input from the front screen).
Click to expand...
Click to collapse
I wasn't able to fix them but I didn't try. I don't have the dev machine to try and fix the issues and rebuild a LoS GSI to get it working. Which is a shame :/
But given that I have had a really good time with it otherwise because I like the potential of it