Develop Bugs

Linux kernel on i780.

I was able to partialy boot Linux kernel on Samsung i780. It wouldn't be possible without help from tmzt. You can find him, and other helpful people on #htc-linux IRC channel on freenode network.
Here are files (kernel, kernel config, default.txt) http://netbsd.pl/~lama/i780/
{
"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"
}

How have i to use these files (.config,linux+default ecc)?
And what means "partially boot"?The i780 doesn t start?

Partially boot means the video is corrupt and the kernel panics because it can't find the root filesystem, the sd card is not implemented yet and ll4m4 did not use an initramfs.
This kernel is not specific to i780, it's just the first step in linux/android on i780.

Nice!
Now that's cool!! I'll be watching...

isn't the i780 hardware similar to the omnia?

It s a start point, but now we only know the i780 can run haret, we don t have a specific zImage or a specific default.txt...

I think we can modify the "omnia's linux" to get it working on i780.I tried to run those files without any modification but the phone vibrates a lot during boot and there is also a screen issue.

ilMessia said:
I think we can modify the "omnia's linux" to get it working on i780.I tried to run those files without any modification but the phone vibrates a lot during boot and there is also a screen issue.
Click to expand...
Click to collapse
Looking forward to test this !!!
Keep the good work

I've manage to make some "progress"...
rev 1
Build kernel based on linux-2.6.29-rc4 sources with arm-2008q3 cross-compiler (config attached )
+fixed res problems, keys reacting (not mapped right), kernel is chill-out
-no connection with device
Cross-compiled busybox-1.13.2 and made initfs (I'm not sure is it working)
It's not big step but step at all
UPDATE 14.02
rev 2
+fixed key mapping, most letters are correct
+kernel is more stable, compressed and it don't spill errors,
+you can actually do something besides writing, there is busybox but don't have all symlinks. all commands are available by "busybox command" // usage example "busybox touch new_file"
- initrd still sucks a lot, it was created in 5min for sake of kernel. but this is just first day of develop...
Besides this I'm planning to move news and files to MelPlace2 website...
UPDATE 24.02
rev 3
+further key fixes
Vol up/down = up/down arrows
Green/red keys = page up/down (usefull to scroll console SHIFT+PGUP)
Rest of keys = explore
+framebuffer corrected - no cut letters near margins
+initrd with little kick, it show that working on this device can be enjoyable
+many devices appear in dmesg...
but
-initrd is still not enough - working on MMC and Ethernet
-randomly kernel boots with white area on right part of screen - reset your device as fast as possible or it will leave strange mark on screen for few minutes, even in WM (!!)
Please test latest revision and send some constructive feedback
I've created kernel git repository on GitHub HERE.
So if you want to help check it out (do not trash this thread with messages about git- it's separately thing).
I've just started (1 patch) so everybody should know what is going on.
Updated download link: i780Linux.zip (2,4 MB)

melgurth said:
I've manage to make some "progress"...
Build kernel based on linux-2.6.29-rc4 sources with arm-2008q3 cross-compiler (config attached )
+fixed res problems, keys reacting (not mapped right), kernel is chill-out
-no connection with device
Cross-compiled busybox-1.13.2 and made initfs (I'm not sure is it working)
It's not big step but step at all
Download link: i780Linux.zip (2,3 MB)
Click to expand...
Click to collapse
Great work man!!!

I just baught my i780 couple of weeks ago. My original plan was, to buy an Android phone. But there was just the HTC Dream available and its price was doubled - compared to the i780.
Now I am glad to hear, that you are working on getting Linux running. I am a Linuxer since 1997. I will try the kernel.
If I can help somehow, let me know.
Cheers
Holger

linuxholgi said:
....
If I can help somehow, let me know.
Cheers
Holger
Click to expand...
Click to collapse
...help is always needed.
Right now I'm in need of good initrd. If You willing to help You can try to make something.
I'll brake work on this weekend due to my birthday (social life) but I'm gonna resume kernel dev in monday. Could be useful to have good initrd with busybox and rootfs.

Ok, is there a ready-to-use toolchain I can use?
Holger

linuxholgi said:
Ok, is there a ready-to-use toolchain I can use?
Holger
Click to expand...
Click to collapse
yes it is. it's magical and working like charm
http://www.codesourcery.com/sgpp/lite/arm/portal/release644
Advanced Packages:
IA32 GNU/Linux TAR
unpack to (location) and make changes in makefile of compiling source
Code:
ARCH ?= arm
CROSS_COMPILE ?= /(location)/arm-2008q3/bin/arm-none-linux-gnueabi-

OK I am prepared now, but take some time to get a good working initr.d. Quite busy these days but do my best!
Holger

Anyone has anynews?

check out this link guys:
http://forum.xda-developers.com/showthread.php?t=484228
which links to video on http://exabyte.es/omnia/2009/02/video-con-linux-corriendo-en-omnia/
which contains video of the omnia AND the i780! (starting from around 2min30s)
They even seem to have enabled all of the functions like camera as well, so why not try contacting those people instead of reinventing the wheel?
Greetz

bazzix said:
check out this link guys:
http://forum.xda-developers.com/showthread.php?t=484228
which links to video on http://exabyte.es/omnia/2009/02/video-con-linux-corriendo-en-omnia/
which contains video of the omnia AND the i780! (starting from around 2min30s)
They even seem to have enabled all of the functions like camera as well, so why not try contacting those people instead of reinventing the wheel?
Greetz
Click to expand...
Click to collapse
It would be great, but i don't think samsung will tell you how to run LiMo

Awesome work!
Is there some news?
anyway, keep it on!!! *Thumps Up*

Linux seems to be running fine on the phone. Anyone trying android?
SD card isn't working is the only blocker for me.

[DEV] [APP] [01/04/2012] Multi Boot Manager 1.22 final for Bravo

{
"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"
}
Code:
Author
=======
Binoy Babu ([email protected])
Thanks to
=========
Quarx2k for valuable advise and ICS
m11kkaa for multiboot and advise
Epsylon3 for ICS
adamo3957 for testing
XDA forum
Reqirements
===========
1) Rooted Motorola Defy/Defy+/Bravo with 2nd init bootmenu installed
2) Multiboot feature by m11kkaa 0.51
Features
========
* Supports any number of ROMs
* Full support for multiboot 0.51
* Support multiple fsimages
* Create, recycle and format virtual systems.
* Delete, rename and edit description of each entry.
* Shows size of the VFS.
* Much more..
What is this?
=============
A manager for Virtual File Systems (fsimages) in your sdcard.
How to use this?
================
1) First of all a custom ROM should be installed as base. Preferably the latest CM9/CM7 nightly to get the latest 2nd-init bootmenu.
2) Then flash defy_multiboot_v0.5.1.zip by m11kkaa. You can get it from [URL="http://forum.xda-developers.com/attachment.php?attachmentid=973410"]here[/URL].
3) Install [URL="http://forum.xda-developers.com/attachment.php?attachmentid=985618&d=1333683822"] MultiBootManagerFree_v1.28_royale1223.apk[/URL]
4) Now open Mult Boot Manager from app drawer. Create new VFS from options. You can see now the new VFS listed. You just created your first VFS.
5) If you need MBM to detect your already existing VFS folders. You have to move them to /mnt/sdcard/multiboot.
6) Instructions for using multiboot 0.51 [URL="http://forum.xda-developers.com/showpost.php?p=24237176&postcount=524"]here[/URL], thanks joydeep1985.
7) If you have coming from leodfs multiboot, you have to restart from step 1. I hope you have enough knowledge to figure out which steps to skip.
8) Rest of the options in MultiBootManager are pretty self explanatory. Please make use of the context menu(long click menu).
9) Please report bugs and any features you want. I'm bit busy now but I'll fix/implement them later.
10) This app now works in virtual system also.
11) This app will work on all GB and ICS ROMs with 2nd init.
.
How to use this??
1) First of all a custom ROM should be installed as base. Preferably the latest CM9/CM7 nightly to get the latest 2nd-init bootmenu.
2) Then flash defy_multiboot_v0.5.1.zip by m11kkaa. You can get it from here.
3) Install MultiBootManagerFree_v1.22_final_royale1223.apk
4) Now open Mult Boot Manager from app drawer. Create new VFS from options. You can see now the new VFS listed. You just created your first VFS.
5) If you need MBM to detect your already existing VFS folders. You have to move them to /mnt/sdcard/multiboot.
6) Instructions for using multiboot 0.51 here, thanks joydeep1985.
7) If you have coming from leodfs multiboot, you have to restart from step 1. I hope you have enough knowledge to figure out which steps to skip.
8) Rest of the options in MultiBootManager are pretty self explanatory. Please make use of the context men(long click menu).
9) Please report bugs and any features you want. I'm bit busy now but I'll fix/implement them later.
10) This app now works in virtual system also.
11) This app will work on all GB and ICS ROMs with 2nd init.
Notes :
1) Always download the latest version of MBM, that would be MultiBootManagerFree_v1.28_royale1223.apk
3) My version of MBM and leodfs' MultiBoot are not compatible with each other. You can't use the two at the same time. Running leodfs version will break the functionality of my app. To restore it you will need to flash mk41aa's MultiBoot 0.41 again.
Change log version 1.28
Prevent an error during rename/edit
You can now set name of a new vfs while creating
Translation support strings.xml uploaded
New look for set icon dialog
Updated instructions
Add git versioning, it's getting very hard to keep track of the code
Code optimization.
Click to expand...
Click to collapse
Change log version 1.22
Many Bug-fixes
Support for multiboot 0.51
The name displayed is folder name, to rename a vfs, just use edit option
Set a default removed (no more relevant)
Improved UI
Works in both real and virtual
Detects if real/virtual
System info button
Many more, I dont remember everything.
Click to expand...
Click to collapse
Todo :
Translations(working on externalising all strings. It's a mess)
Other Devices support(I will try and port to moto devices first, then others, one at a time)
Install zip feature(pro).
Resize feature(pro).
Click to expand...
Click to collapse
Orginal thread : http://forum.xda-developers.com/showthread.php?t=1522329

Great you created a thread for it.
Im arriving home now, its 5.00 am here in my country, I was working
I'll try it when my phone is charged!
-----------------------------------------------------------------------
EDIT:
Worked perfect I dont like to use multiboot, but having now more than 2 multiboot roms is great.
I can confirm it is working perfectly!

Off topic Corner > All off topic chat here only

I created this thread to avoid chatting into other threads keeping them clean..
Please if you have questions about anything post them here, and keep an order.
Use quoting of maximum 3-4 lines, use
or use @ to mention someone without quoting.
Thanks! :good: :highfive:

hi @corsicanu
i have samsung i9070 s advance
cwm and root install method: flash directly through stock recovery
and it does not increase binary counter
and you know that to flash something through stock recovery,
package must be signed with original signature
now, why not it be for fame and for other packages like roms or themes
do you have any idea about signing with an original signature
regards

Naney said:
hi @corsicanu
i have samsung i9070 s advance
cwm and root install method: flash directly through stock recovery
and it does not increase binary counter
and you know that to flash something through stock recovery,
package must be signed with original signature
now, why not it be for fame and for other packages like roms or themes
do you have any idea about signing with an original signature
regards
Click to expand...
Click to collapse
i have no idea how to sign them but i think i have a solution to flash cwm without increasing custom bin.. from what i`ve seen vroot works good for Galaxy Fame without increasing the counter.. And if you succed rooting you can use Flashify to flash img of cwm directly from phone, getting rid of odin.. I didn`t tested this but i assume it works.. will search to see if it`s any chance to sign zip`s with original and also i`ll try the above method to root and install cwm without increasing counter..

Hi @corsicanu
I think, like you, the better idea for optimize our FAME is a new Kernel... I don´t know how to make a new one, but if you can recommend me some literature about it, maybe I can help you in any task.
Thanks for your work.

corsicanu said:
i have no idea how to sign them but i think i have a solution to flash cwm without increasing custom bin.. from what i`ve seen vroot works good for Galaxy Fame without increasing the counter.. And if you succed rooting you can use Flashify to flash img of cwm directly from phone, getting rid of odin.. I didn`t tested this but i assume it works.. will search to see if it`s any chance to sign zip`s with original and also i`ll try the above method to root and install cwm without increasing counter..
Click to expand...
Click to collapse
hey this method is fully working 101% working........as i flash recovery every time with this method on my S6812 !!!!!
it does not effect phone working, binary counter, and it is 100% safe !!!!!!!
cheers !!!!!!!!!!

Vkas Raj said:
hey this method is fully working.. as i flash recovery every time with this method on my S6812 !
it does not effect phone working, binary counter, and it is 100% safe !
Click to expand...
Click to collapse
Not so sure about it.. I need to test it on a fresh device because i have a feeling that the counter will get to 1 automatically when it will detect custom binary flashed.

Hakets said:
I think, like you, the better idea for optimize our FAME is a new Kernel... I don´t know how to make a new one, but if you can recommend me some literature about it, maybe I can help you in any task.
Click to expand...
Click to collapse
First of all you will need a linux distro installed and configured. I followed this tutorial to make it happend. The only toolchain working for our kernel will be 4.6 as the source code needs an update for compiling with newer toolchains without errors. The source code for our devices is here. Download the proper pack for your device/region and unzip it. Inside will be 'how to' file. Looks like this:
Code:
################################################################################
1. How to Build
- get Toolchain
From android git server , codesourcery and etc ..
- arm-eabi-4.6
- edit Makefile
edit target architecture.
- ARCH ?= arm
edit "CROSS_COMPILE" to right toolchain path(You downloaded).
EX) CROSS_COMPILE= $(android platform directory you download)/android/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin/arm-eabi-
Ex) CROSS_COMPILE=/usr/local/toolchain/arm-eabi-4.6/bin/arm-eabi- // check the location of toolchain
$ make bcm21654_rhea_ss_nevisp_rev00_defconfig
$ make
2. Output files
- Kernel : arch/arm/boot/zImage
- module : drivers/*/*.ko
3. How to Clean
$ make clean
################################################################################
Long story short:
Code:
mkdir ~/Desktop/kernel
cd ~/Desktop/kernel
mkdir nevis
mkdir toolchains
#Unzip source code for kernel into 'nevis' folder
#and toolchains into their folder.
cd ~/Desktop/kernel
export ARCH=arm
export CROSS_COMPILE=~/Desktop/kernel/toolchains/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-
make bcm21654_rhea_ss_nevisp_rev00_defconfig
make -j16
The outputed file after succesfully compiling will be zImage. Using boot image tools, pack your new kernel with the new zImage and ramdisk.gz from old kernel. Congrats! Now you have a new kernel..
For changing govs, schedulers, freq`s and others see this and make changes in the source. After changing the source use 'make clean' before starting a new build of kernel. Hope i covered all.. Cheers!

Wow, nice answer, thanks so much.
Enviado desde mi GT-S6810 mediante Tapatalk

@corsicanu
buddy
i have problem with apktool
it does not work
i decompile package and even with no changes i can not recompile it
different faults each time
do you know anything about it
i have been using it for months, but i did not faced such a thing before
i updated sdk but no solution
very funny!
i searched xda but found nothing
i used it with no problem yesterday
and suddenly it created problems today
did not understand anything?
{
"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"
}

install framework.apk and tw-framework.apk and set api level to 16 for 4.1.x roms.. and after that it should work.. i'm not at home and i can't give more instructions..

corsicanu said:
install framework.apk and tw-framework.apk and set api level to 16 for 4.1.x roms.. and after that it should work.. i'm not at home and i can't give more instructions..
Click to expand...
Click to collapse
buddy
i told, i have been using it for months
i already installed frameworks and worked on lots of apps
i know how to use it
but interesting, it suddenly gives errors!
regards

Naney said:
buddy
i told, i have been using it for months
i already installed frameworks and worked on lots of apps
i know how to use it
but interesting, it suddenly gives errors!
regards
Click to expand...
Click to collapse
sorry my bad.. i've read in rush.. try with a new working folder and re-setup apk tool.. i had those errors from second print when was a wrong api.. are you using the latest apktool? or try with other apk.. maybe its SecSettings guilty.. cheers!

corsicanu said:
sorry my bad.. i've read in rush.. try with a new working folder and re-setup apk tool.. i had those errors from second print when was a wrong api.. are you using the latest apktool? or try with other apk.. maybe its SecSettings guilty.. cheers!
Click to expand...
Click to collapse
it is not from tool version or working folder or apk.
i deleted apktool folder in personal folder and now it is ok again.
it contains 1 framework file at the moment.
what do you think, why is it?

Naney said:
it is not from tool version or working folder or apk.
i deleted apktool folder in personal folder and now it is ok again.
it contains 1 framework file at the moment.
what do you think, why is it?
Click to expand...
Click to collapse
dont know what to say.. when i decompiled i installed first framework-res and second was tw-framework.. and in personal were two zips.. 1.apk and 2.apk.. and from what i read in cmd from apktool output 1 was for framework and 2 was for tw-framework.. this method of setting up apktool i found it here on xda and was working for me.. but who knows.. if it's working i don't see any problem with that single zip.. btw test the outputted apk because it may compile without errors and could not work if there is anything wrong..

[UNOFFICIAL][RECOVERY] TWRP 3.5.1 for Galaxy J7 PRO

{
"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"
}
TWRP is an open source, community project. A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like LineageOS or OmniROM.
Disclaimer
I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Rooting your phone may void warranty so don't root your device unless you know what you are doing.
Downloads
MEGA : TWRP_3.5.1
Flashing
Recovery : Download Recovery.img file from link and flash it through your current recovery in recovery Partiton
ODIN : else pack recovery img in .tar and flash it through ODIN in AP.
Changelog
Fixes
Build compilation in 7.1 tree - CaptainThrowback
SAR: Don't follow symbolic links for block devices - bigbiff
SAR Update script name for clarity - CaptainThrowback
Wrappedkey support running only on FBE devices - CaptainThrowback
TWRP App log information reduced - epicX67
Refresh details after system wipe and adb sideload - AdrianDC
Chinese translation updates - betaxb
Support keymaster 2 - PeterCxy
add tzdata to TWRP for timezones - CaptainThrowback
ParitionManager: support delayed adopted storage mount - PeterCxy
Support to start terminal from file manager directory - AndroiableDroid
Nano support - nebrassy
Add nano support to open files from file manager - CaptainThrowback
Include new magisk apk support to be installed by TWRP - ianmacd
Add support to change directory name where TWRP stores backups - epicX67
Add bash support - not the default shell - DarthJabba9
ORS support to format data - AdrianDC
Add support to flash both slots when flashing an image - epicX67
NL translation updates - ianmacd
Cleanup
Installation cleanup - remove dupe PackageExtractFn - klabit87
Remove logd-reinit service - CaptainThrowback
Fixes
Restore system root context - bigbiff
Only include keymaster 2 if tree supports it - CaptainThrowback
Strip lines containing '--' in language_helper.py - ianmacd
Unlocalized string fix - ianmacd
Credits
all goes to @Astrako for his hard work with all exynos7870 device trees without him this would not be possible
Device trees : https://github.com/samsungexynos7870
7870 Group : https://t.me/samsungexynos7870
PrishSupport : https://t.me/prishsupport
PrishChannel : https://t.me/prishupdates
TWRP : https://twrp.me/site/update/2021/03/17/twrp-3.5.1-released.html
Note : Test it and if you found any issue do let me know by PMing me on telegram @neel0210 .

Thanks my friend
Install ok
Boot ok
No detect bugs

Repporting
Twrp 351 install magisk apk natively
Twrp 351 install New apk

Between TWRP and Orange Fox which one is better ?

paperbird said:
Between TWRP and Orange Fox which one is better ?
Click to expand...
Click to collapse
I like twrp simple and better

AdAway 550...
[APP][ROOT/NONROOT][OFFICIAL] AdAway v6.1.0
AdAway AdAway is an open source ad blocker for Android using the hosts file. Google Play Store notice According the Google Play Developer Policy, especially the "Device and Network Abuse" section, ad blocker like AdAway violates the "Apps that...
forum.xda-developers.com

root the device j730g security u11 please help twrp all fail reports

O que acontece se der errado a instalação do twrp?
Translation: What happens if the twrp installation fails?

link dead?

I flashed some twrp image in my samsug j7 max via odin , but instead of AP in odin , I selected BL i guess, Now after flashing my device wont even turn on. It isn't responding to any commands, not even download mode. I need some serious help as it is my only device. can anyone help me solve my problem?

Stone336522 said:
I flashed some twrp image in my samsug j7 max via odin , but instead of AP in odin , I selected BL i guess, Now after flashing my device wont even turn on. It isn't responding to any commands, not even download mode. I need some serious help as it is my only device. can anyone help me solve my problem?
Click to expand...
Click to collapse
You messed up bro, thats why in each and every post everything is clearly mentioned you should pay attention to the details...
Mtk devices are not meant for this things my last phone also got bricked accidentally by my own hands

Pradeep1998 said:
You messed up bro, thats why in each and every post everything is clearly mentioned you should pay attention to the details...
Mtk devices are not meant for this things my last phone also got bricked accidentally by my own hands
Click to expand...
Click to collapse
Ya ,it was the moment i knew i got fkd up , is there anything i can do with my phone?

very good

works on J730F/DS?

Does it work on SM-J730F/DS?

Link dead

nedium said:
link dead?
Click to expand...
Click to collapse
Kutsuya said:
Link dead
Click to expand...
Click to collapse
If you still need it
Mirror Link here.

THX!!!!

[KERNEL][A11/A12][EA][STOCK]"STABLE" Kernel

This Kernel is for EA Android Q version. If you're using TM or ATT, please cross flash to EA.
This Kernel Does not Support for L51A(JP version[DOCOMO])
(I have committed the TM20k change in rebase but not merge in EA version)
NOTE:
1. Your Phone must be unlocked bootloader and have magisk root
2. Your Phone's ANDROID VERSION must be 11/12
KERNEL FEATURE:
01. Merge CAF version into LA.UM.9.12.r1-14000-SMxx50.0
02. Merge DTS version into LA.UM.9.12.r1-14000-SMxx50.0
03. Update Kernel version to 4.19.225
04. Move to PELT
05. Use Sultan Kernel Toast's CPU/Devfreq input boost
06. Use SIMPLE LMK (Sultan Kernel Toast's)
06. GPU overclock to 855Mhz (I've broke the TM varient while oc to 870MHZ)
07. KCAL support
08. Import Juhyung Park arter97's exfat to support LGE's texfat
09. Use Proton Clang 13 for kernel compiling
10. Disable blocking touch while reboot to recovery (TESTING) -> author: SGCMARKUS
HOW TO FLASH:
1. The flashable zip is support Magisk, Flash it just like flashing a module.
DOWNLOADLINK:
MEGA LINK
KERNELSOURCE:
GITHUB LINK
Special Thanks:
* SGCMarkus
* Sultan (kernel toast)
* Arter97
* Ayrton990
* TingyiChen
* LibXZR
* EmanuelCN
* spakkkk
AND Many Other Great Developers!
Final: Sorry about my English
SCREENSHOTS:
{
"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"
}

ChangeLog
Android 12:
V6:
1. Merge ACK (Kernel version: 4.19.267)
2. Update exfat source from namjaejeon
3. Merge latest f2fs-stable
4. Fix LGE wifi private command error
V5:
1. Merge ACK (Kernel version: 4.19.261)
2. Update exfat source from namjaejeon
V4:
1. Merge ACK (Kernel version: 4.19.255)
2. Merge caf tag to LA.UM.9.12.r1-14700-SMxx50.0
3. Merge latest f2fs-stable
4. Update crypto.
Android 11:
V13 (Reupload):
WALT only:
1. Merge ACK (Kernel version: 4.19.255)
2. Merge caf tag to LA.UM.9.12.r1-14500-SMxx50.0
3. Merge latest f2fs-stable
4. Tweak little cpu freq to reduce animation lags
5. Clang 16 support
6. Use LRNG random
V12:
WALT only:
1. Merge ACK (Kernel version: 4.19.251)
2. Merge caf tag to LA.UM.9.12.r1-14300-SMxx50.0
3. Android 12 support And FIX com.android.phone crashed
4. Android 11 final (no longer update)
V11:
WALT/PELT:
1. Merge ACK (Kernel version: 4.19.240)
2. MPTCP update to 0.95.2
3. ZRAM update to 5.15 (Arter97)
BUG:
1. HIGHER CPU JITTER DURATION AND I CAN'T SOLVE IT ANYMORE
2. DON'T KNOW ABOUT WIFI ISSUE

Really fast kernel. It works fine on my V600Ea

If im on the att 60 A10, can i still crossdflash?

FC06 said:
If im on the att 60 A10, can i still crossdflash?
Click to expand...
Click to collapse
It's necessary, but i don't have a guide to crossflash to EA ver

staljin said:
Really fast kernel. It works fine on my V600Ea
Click to expand...
Click to collapse
The v2 version has been rebuilt, details are on the changelog.

Is there a way to use this on tm without crossflash? Crossflash kills volte and TMobile enforces it

crimsonrommer said:
Is there a way to use this on tm without crossflash? Crossflash kills volte and TMobile enforces it
Click to expand...
Click to collapse
I came to ask this question for the exact same reason.

crimsonrommer said:
Is there a way to use this on tm without crossflash? Crossflash kills volte and TMobile enforces it
Click to expand...
Click to collapse
mnt/product/op -> the configs of volte are in this folder

ErickG233 said:
mnt/product/op -> the configs of volte are in this folder
Click to expand...
Click to collapse
Right and what do I do with that info lol?

crimsonrommer said:
Right and what do I do with that info lol?
Click to expand...
Click to collapse
back up your preset folder, and backup your ftm(dev/block/bootdevice/by-name/ftm) block, refurbish to ea 20j, then use hex to open ftm binary file, search "FFF" with asicII(not hex), then change the end number(ea is 11), flash it,then replace all the files in /mnt/product/OP/OPEN_EU/etc and /mnt/product/OP/OPEN_EU/cust.prop then reboot.
maybe one day i will post a thread about OP mod....

ErickG233 said:
back up your preset folder, and backup your ftm(dev/block/bootdevice/by-name/ftm) block, refurbish to ea 20j, then use hex to open ftm binary file, search "FFF" with asicII(not hex), then change the end number(ea is 11), flash it,then replace all the files in /mnt/product/OP/OPEN_EU/etc and /mnt/product/OP/OPEN_EU/cust.prop then reboot.
maybe one day i will post a thread about OP mod....
Click to expand...
Click to collapse
To replace the files in the OPEN_EU folder, where do I get the new files from?
I believe a thread on changing the OP is much needed and appreciated since there are a lot att devices crossflashed to EU FW.

Working well so far on my V600TM Cross flashed V600EA.
Any plans for a suture release or an update?

MrHomebrew said:
Working well so far on my V600TM Cross flashed V600EA.
Any plans for a suture release or an update?
Click to expand...
Click to collapse
Hi, I live in Europe and I have v600tm, I like to put my company's software, i looked everywhere on this site to understand how to cross flash, can you please link me a place to understand how cross flash works, thanks and sorry for my English

MrHomebrew said:
Working well so far on my V600TM Cross flashed V600EA.
Any plans for a suture release or an update?
Click to expand...
Click to collapse
V6 has been released.

Any plans in releasing a kernel that doesn't require crossflash?

crimsonrommer said:
Any plans in releasing a kernel that doesn't require crossflash?
Click to expand...
Click to collapse
Well you can flash anyway, it can boot but not sure NO BUG.
Bootable variant (A11): TM ver.

MrHomebrew said:
Working well so far on my V600TM Cross flashed V600EA.
Any plans for a suture release or an update?
Click to expand...
Click to collapse
How did u crossflashed your V600TM to EA firmware?

Hi, just wanna ask which EA firm should i crossflash? Tried on mine Crossflashed but i got kernel panic

Kratos574 said:
Hi, just wanna ask which EA firm should i crossflash? Tried on mine Crossflashed but i got kernel panic
Click to expand...
Click to collapse
you need to recover the abl from kdzs NOT the factory ABL