yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco F1 Questions & Answers] stinka318:
Flashed no gravity kernel and my problem went away as well I believe it has something to do with how Google receives information about the bootloader in the kernel.......
[Xiaomi Poco F1 Questions & Answers] SnOOpeRa:
It was working ok for me till today. I had the problem with cts profile : false, then it clears from itself (google change something or revert the changes) , but now I checked randomly in magisk manager and this time I got both cts profile false and basic integrity false , so think google change the things again and even more restrictive than previous time , anyone else can confirm ?
[G2 Q&A, Help & Troubleshooting] Ka-B00M:
I was trying to get some data off of a T-Mobile LG G2. Unfortunately, the phone tried to fight with me, so I decided to root it to get around the bull**** because electronics that fight with me always get taught a lesson. The phone has been rebooted several times since then, but on one particular reboot, the phone decided to strike back at me and not actually boot up, and it has never booted up since. I get stuck on the LG logo with the smoothly transitioning green/blue LED. And this is where I'm stuck, but I won't let a phone defeat me. It would be nice if I could get the phone working, but I don't care about the phone itself that much because the phone has already been replaced. I only need some of the data from it. (It was not backed up because it is my mom's old phone, not mine, and my mom is an idiot.) I can think of several ways to proceed.

1. Try to fix it with recovery mode. Unfortunately, the built in recovery mode only offers a factory reset, so I would have to install TWRP with download mode first. Except from my research it seems like I can only flash the main OS with download mode, overriding the data in the process, and I'd have to use a Windows machine to do it.

2. Somehow get access to ADB and use that to do anything that has to be done. USB debugging is enabled, but as far as I can tell, ADB only runs when Android is fully booted. Which obviously doesn't happen anymore.

3. Boot into fastboot mode and do stuff from there to get it back up. It seems like in order to make it do that, the phone has to be unable to pass execution to whatever boot mode I try to boot it into (whether that's Android, download mode, or LG's ****ty excuse for "recovery" mode). If that's right, it means that the phone is not broken enough and I need to somehow break it more.

What should I proceed with, and how should I go about it? If none of these are good ideas, what should I do instead?
[Advantage X7500, MDA Ameo ROM Development] fards:
sounds great, why .net 2.0 and not 3.5?

which SPL is the image for?
[Advantage X7500, MDA Ameo ROM Development] xtep:
Very good iniciative.

I've been testing some of the ROMs posted in this forum in order to use one of them as base for my own personalized ROM.

I think that in order to release a kitchen I think that is better to keep all the .dsm and .rgu files, so the people can choose what packages to keep or remove. Is there any tool that merge all the rgu/dsm in one before cooking? This would be the best option.
[Advantage X7500, MDA Ameo ROM Development] Palmchen:
sounds really good,

a software-combination from the new devices combined in Athena (Ameo).

If the operating system is english or not is not the biggest iisue for me; but I couldn't use a german keyboard with an english keyboard driver...

Is there planned in any way to chance leastwise the keyboard in another language.

AND - if I find that the new version is not so good for me, could I go back to the original Version (t-mobile german WM6) ?

btw: do you support with this rom ms voice command too ?
[Advantage X7500, MDA Ameo ROM Development] mgozamy:
Great

Seems intereting and promising...just want to know, if you would be able to avail this rom for both spl's 1.2 & 3.5.

Cheers
[Advantage X7500, MDA Ameo ROM Development] irus:
sogarth, dude you did a GREAT JOB with this rom it is awsome I fu*king love it. its not the fastest rom but its stable and most important i got the data connection working under spl 1.2 :D..... just an awsome job i am going to do a little more testing and with sogarth's permission i will release it for spl 1.2 the only thing i will add is uc compliant and the rest will be untouched.
[Advantage X7500, MDA Ameo ROM Development] xtep:
Answering myself: Yes, there are tools to merge all the packages in a ROM (I suppose that is was a stupid question, sorry, but I'm learning to cook ROMs).

For example, buildos+packagetools4.2b3 from ervius can do it automatically.

I have been using this tool to learn how to cook ROMs. Attached to this post

is .bat files that allow you to use buildos+packagetools4.2b3 to extract/build ROMS from/for the Athena.
[Advantage X7500, MDA Ameo ROM Development] Montecristo:
Only for SPL 1.2???
[Advantage X7500, MDA Ameo ROM Development] xtep:
One question about SPL versions: As far as I understand (as I said before I,m quite new on cooking), the diference between a ROM for SPL 1.2 or SPL 3.5 is in the XIP used. The ROMs for SPL 3.5 are based on AP4/AP5 (or takes the XIP from them), while ROMs for SPL 1.2 are based on old WM6 oficial ROMs. Is that right? Is there no problem for using a XIP form WM6 and a SYS from WM6.1?

thanks in advance
[Advantage X7500, MDA Ameo ROM Development] mgozamy:
What was stated above that the XIP is the XIP from AP 5.0 beta, does this mean that this rom is for spl 3.5? Can some one help me answering this question.
[Advantage X7500, MDA Ameo ROM Development] retroqwe:
unable to send a text or email message

Hello

Just trying the new rom and found that i am unable to send an email or text message. If I press "menu" and then "new" nothing happens.

Also the contacts details page is coming up blank. I can confirm that this can be fixed by implementing the SJ Fix_Summary_Contact.cab file found in various places.

cheers

Alex
[Advantage X7500, MDA Ameo ROM Development] mgozamy:
Alex,

What spl is this rom for?

Cheers
[Advantage X7500, MDA Ameo ROM Development] Brau0303:
I would be interested in a version that can be used with SPL 3.50, and the ability to start with a base (yet complete) WM6.1 is what I have been really looking for (while the Manilla stuff looks really cool it was not intended for the Athena hence the stability issues, I could live without it). This project looks very interesting.

Cheers

BR
[Advantage X7500, MDA Ameo ROM Development] irus:
for spl 1.2 i have the same problem with text messages and emails but the contacts problem i do not have any thoughts sogarth?
[Advantage X7500, MDA Ameo ROM Development] retroqwe:
The contact problem is only at 128 and 96 DPI, this is an old problem seen and fixed in other 6.1 roms. The text /email is new.

I am using SPL 3.5

cheers

alex
[Advantage X7500, MDA Ameo ROM Development] irus:
thats good to know as i am using spl 1.2 and im having the same text/email problem not sure why?

edit: can you recieve text msg
[Advantage X7500, MDA Ameo ROM Development] retroqwe:
Hi Irus, sorry had to flash back to taxist rom as I needed to be able to send emails [work and all that :-( ] . so unaable to test if I can recieve text's

alex
[Advantage X7500, MDA Ameo ROM Development] retroqwe:
Mirco Drive oddness

Hello

The microdrive mounted as MicroDrive2 , [another folder is prescent called microdrive with a my documents folder with default "stuff". Not sure if this is just me.. can anyone else check this please..

This is not a a porblem just a feature :-)

alex
[Advantage X7500, MDA Ameo ROM Development] Sogarth:
Running through responses (I posted this just before I went to sleep, and I've just managed to sit down at my desk long enough to type a response at work):

.NET 2.0 and not .NET 3.5 because .NET 2.0 is what ships as part of the Windows Mobile 6.1 SYS. It's not that hard to roll a .NET 3.5 OEM package; I'm sure you'd be able to find one without too much difficulty.

There is a tool that merges all the .dsm files into one and deletes the .rgu files post-registry generation while generating the ROM (Bepe made one). That's what I'm using. In the kitchen itself, there are all of the different SYS and OEM folders you'd expect. But it looks like you found that on your own too.

The operating system is WWE at the moment. If you have access to all of the German folders (I know WWE is 0409; I don't know what German is), it would be pretty easy to go through and replace the folders. Replacing the keyboard itself might be possible; I don't know for sure. If nothing else, the advantage of a kitchen is that you'd be able to try it yourself. :)

This is an SPL 3.5 ROM at the moment, so the only way you'd be able to go back to the T-Mobile German WM6 ROM would be by downgrading back to SPL 1.2 first. It's possible, although I understand a bit involved.

Any ROM should be able to run MS Voice Command. I actually have an OEM package sitting around so that MS Voice Command can be built into a ROM; if I were to release that OEM package, though, it would have certain files missing that users would need to re-add themselves, as it's a commercial product.

Well, I wasn't aiming for fastest, as I said. That gets to be the experimentation later. ;)

Feel free to release an SPL 1.2 version if you want, although if everything works out, I'll be releasing a kitchen that would be able to generate either, depending on the OS.nb it's built with.

As far as I know, that's correct. Ideally, you'd have have an XIP that matches your SYS (down to the build level), but there isn't a huge difference between WM6 and WM6.1, so that would be fine. Even better would be if you could port an XIP, but I've been having a few problems with that.

Hmm... for the first, that's odd. I'll have to look into that, since I'm not sure what could be causing that.

For the second, I thought I'd gotten that working, but I guess I hadn't. *sigh* I'll take care of that, although I'd like to know why that's happening, too, since I'm using WM 6.1 96- and 128-dpi resource files. Unless it's something other than that? :confused:

Hmm... I'd suggest deleting MicroDrive and doing a soft reset, which should fix it. I would have freaked if that happened to me every time with this ROM.

I'll admit that as part of setup, the ROM does copy stuff to your microdrive (demo files for HTC Album, which the HTC Diamond ROM seems to like to do). It's pretty easy to disable, but I figured I would leave it in for the base ROM (since to be honest, I personally hate it when kitchen developers "tweak" packages, since I want to know that what I'm working with is relatively untouched).
[Advantage X7500, MDA Ameo ROM Development] irus:
i can confirm that i can recieve text messages but i can't view them except for when it first pops up in the bubble. there is a dll file missing i think
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] duskwind:
After installing Lineage OS on my HDX 7 I have problems with some apps. I wasn't able to download Netflix from Play Store for example. I solved that by using an apk from Fire OS.

I cannot install Kindle Reader either, but since Kindle is part of the Fire system the Netflix solution does not work.

Is there a way to install Kindle Reader on a Fire with Lineage OS? Is there an apk that works?
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Official Android Kindle app is available in the Play Store. Serviceable, but less full featured than FireOS version that will not run on custom ROMs. Amazon saves the best for their own devices/os.

Compatible Netflix app can be downloaded from numerous sources including official Netflix support pages. Issue here is Play Store device certification as newer Netflix app builds can download content. You'll either have to live with limitations of older builds or view content is a browser window.

Twiddling with device fingerprints can yield limited benefits but it is a cat and mouse game at best. I rarely use HDX devices for streaming content; the high resolution panel is better suited to textual content consumption.

Good luck.
[Redmi Note 8 Questions & Answers] Sykin:
There is no fingerprint option after fixing system has been destroyed. How do i fix this? Please help :crying:
[Redmi Note 8 Questions & Answers] the_weird_aquarian:
flash full fastboot rom with mi flash and then see if issue persists or not.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] evdenis:
How to build the kernel locally on your PC

This instructions assumes you are using Linux. Install mkbootimg (AIK tool) from osm0sis, heimdall (if you want to flash the kernel automatically).

Next:

# Install prerequisites
# If you use ubuntu or ubuntu based distro then you need to install these tools:
$ sudo apt-get install build-essential libncurses-dev libtinfo5 bc bison flex libssl-dev libelf-dev
# If you use Fedora:
$ sudo dnf group install "Development Tools"
$ sudo dnf install ncurses-devel ncurses-compat-libs bc bison flex elfutils-libelf-devel openssl-devel

# Install mkbootimg
$ wget https://github.com/osm0sis/mkbootimg/archive/master.zip
$ unzip master.zip
$ cd mkbootimg-master
$ sed -i -e 's/-Werror//g' Makefile
$ make
$ sudo mv mkbootimg /usr/local/bin/mkbootimg

# Get the sources
$ git clone https://github.com/CruelKernel/samsung-exynos9820
$ cd samsung-exynos9820
# List available branches
$ git branch -a | grep remotes | grep cruel | cut -d '/' -f 3
# Switch to the branch you need
$ git checkout cruel-v3
# Install compilers
$ git submodule update --init --recursive
# Compile
$ ./build mkimg name=CustomCruel model=G973F +magisk+canary +wireguard +ttl +cifs +nohardening
# You will find your kernel in boot.img file after compilation.
$ ls -lah ./boot.img

# You can automatically flash the kernel with heimdall
# if you connect your phone to the PC and execute:
$ ./build :flash

# Or in a single command (compilation with flashing)
# ./build flash name=CustomCruel model=G973F +magisk+canary +wireguard +ttl +cifs +nohardening
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] evdenis:
Pin problem

The problem is not in sources. It's due to os_patch_level mismatch with you current kernel (and/or twrp). CruelKernel uses common security patch date to be in sync with the official twrp and samsung firmwares. You can check the default os_patch_level in build.mkbootimg.* files. However, this date can be lower than other kernels use. When you flash a kernel with an earlier patch date on top of the previous one with a higher date, android activates rollback protection mechanism and you face the pin problem. It's impossible to use a "universal" os_patch_level because different users use different custom kernels and different firmwares. CruelKernel uses the common date by default in order to suite most of users.

How can you solve the problem? 5 ways:

You can restore your previous kernel and the pin problem will gone

You can check the os_patch_level date of your previous kernel here https://cruelkernel.org/tools/bootimg/ and patch cruel kernel image to the same date. If your previous kernel is nemesis, patch cruel to 2099-12 date.

You can reboot to TWRP, navigate to data/system and delete 3 files those names starts with 'lock'. Reboot. Login, set a new pin. To fix samsung account login, reinstall the app

You can rebuild cruel kernel with os_patch_level that suites you. To do it, you need to add the line os_patch_level="<your date>" to the main.yml cruel configuration. See the next section if you want to rebuild the kernel.

You can do the full wipe during cruel kernel flashing
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] starbucks2010:
Good job!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Valentino911:
Thanks Dev! Does this kernel work also with LineageOS and AOSP roms?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hanspampel:
Did you checked it if it works for you? For me the oneliner didnt work in main.yml. I must edit the build.mkbootimg.G975F file and rebuild. Then i got no pin problems cause the OPL was now changed.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] evdenis:
Yes, I checked that it works. Here you did't use os_patch_level setting and the date is 2020-02. Next, you updated os_patch_level and you can see the date changed if you unfold "Show information about build" section in build log. In the third commit you removed the os_patch_level and cancelled the build, so the date reverted to default one 2020-02. And in finial commit the date was changed in build.mkbootimg.G975F file. If you doubt the date changed, you can check the build settings either in "Show information about build" section in build log or in "Kernel Configuration Info" file next to the kernel image in "Artifacts". Thanks!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] evdenis:
As for now, it compatible only with Samsung based firmwares. Works on native samsung firmwares, BeyondROM, on Ambasadii it's better to use Nemesis kernel (you will face pin problem if you try to install cruel). The kernel doesn't work on LOS.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Ali.M7mmoud:
Anybody want gcam for exynos.. u can see tgis video it for android Q one ui 2.0 for s10plus exynos

[youtube]Xcexl2R5eCI[/youtube]
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] elchinemil:
I have a question . The hadest rum was established, respectively the hadest kernel. I install the cruel kernel, but after the reboot the kernel of the hadest returns. Why? The first time I encounter this phenomenon, How to solve the problem?

Before rebooting the cruel core, the necessary functions work. After a reboot, the hades kernel returns.:(
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hanspampel:
[MENTION=10496119]evdenis[/MENTION]

I got problems with your latest sources (3.0 and 3.1). It doesnt boot to recovery with an app. This works for a few commits earlier(last week or so). Now its not working. And the OSPL in main.yml doesnt work for me too. Doesnt pass the restart pin. But thats not a problem, changed it in the other side.

Cant test your compiled versions, pin problem, i was on nemesis kernel, so i have to compile it myself.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hanspampel:
Another problem ive saw, the device doesnt shut down. It only reboots. Compiled with 3.0 and 3.1 sources. With the older source a week ago, it works.

Edit: So tried your released v3.1 and changed the OSPL manually for PIN Fix, seems to work(recovery and shutdown). Maybe something went wrong on my side till compiling. Have no clue atm.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] evdenis:
This could be due to enabling non-default configuration presets, like +nodebug or +nohardening2.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] evdenis:
Hades rom uses very good kernel. Technically, I don't see any reason to change it on hades rom, unless you really want to experiment with, for example, +1000hz or +bfq scheduler.

The reason the previous kernel restores back could be again due to patch level mismatch.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] evdenis:
I will update installation method in the next version to dynamically repack kernel during installation procedure. Hope, this will solve os_patch_level problem (pin issue) once and for all.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] tin2404:
nice kernel
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] thehacker911:
Thanks for this wonderful kernel! It is an honour for me to be able to participate in this!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hamidru:
G975N

Working in 975N or not
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Abaddon:
If it works om F/FD devices. It will work on N devices
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] lupin57:
If it's an exynos device ... no reason to this :D
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hanspampel:
But not for

N

975! Only S-devices =

G

97x!!!!!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] jelbo:
I haven't used a custom kernel in several years. Does this kernel do anything to /system? I'm using Magisk and want to keep it untouched.

/edit: so this one doesn't.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] doclucas:
I am currently on stock Android 11, N975FXXS6EUA1_N975FOXM6ETLL firmware

I tried to compile v3.10 (+magisk), which works when I am running my N975F with stock Android 10 (TH7 base), but doesn't boot when I am flashing it on Android 11.

Is this kernel only for Android 10 bases? Or can it be compiled for Android 11 as well?

EDIT: Nevermind. Found it.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] mikehorizon:
Feature request:

Boost volume for Bluetooth headphones also, not just wired headphones.

Thank you,
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] coey0814:
Wow, it was updated to v4.0 few hours ago. Can you tell us what has changed?

Always thank you for your hard work.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] bininga59:
I think if he changes the start-post and makes the kernel available for download, he will also write a changelog.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Zeroleak:
Hello,I currently have a G975F, and just patched into magisk after unlocking the bootloader

however whenever I reboot my phone my root disappears,i have to always boot into recovery i noticed

how do i install TWRP and then flash this kernel? I don't mind resetting or wiping my phone

any help would be appreciated thanks
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] jelbo:
The instructions are there, but I'll help you.

Have TWRP, vanilla or Magisk patched, doesn't matter.

Flash multidisabler and follow the instructions that come with it, it requires a data wipe.

Flash this kernel.

Voila, boot with Magisk root every time.

Easier for you may be to boot your phone with the Power+Bixby+Volume Up combination (and often anything USB other than charging only attached), let go in time and boot Magisk patched Android. This works with Magisk patched stock recovery or Magisk patched TWRP. Both don't require multidisabler.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] jelbo:
It's a long time ago, but did you ever find a way to fix this?

I don't know how to 'reinstall the app', because it is part of the system?

/edit: I managed to fix it by clearing the data for the Samsung Account app, I used App Manager. Prior to that, I flashed backtothefuture with the default year/date of 2099-12. I'm not entirely sure if that was needed though.

/edti2: Android keystore was messed up anyway, I had to do a factory reset to get it working well again. No idea what caused it, because CurelKernel patches itself with the os_patch_level it finds of the stock kernel.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] enebro77:
@evdenis sir,

Any plans for developing a Note 20 ultra Kernel ?

Many thanks in advance
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] dzik75:
How is cruelkernel-4.0-25hz different from cruelkernel-4.0-50hz?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] scriiptSQD:
I'm not really a geeky person, but as I understood it, this frequency represents the frequency of how often does the CPU check for the interruptions, so the least the value is, the more performance you might get, but the more your power consumption will be. Potentially, it can also bring some stutters with simple tasks, as harder and more important ones will always overshadow easier and interrupt the CPU