Database Info

[ROM] I337UCUAMF3 Unadulterated [8-19-13]

Notice (4/16/14): I'm no longer here. I've said "goodbye" to AT&T and their locked bootloader schemes. I'm voting with my wallet - I've sold my I337 and switched to T-Mobile. My apologies to the community, but you're now on your own here.
"I337UCUAMF3 Unadulterated"
This rom is a 100% pure, untouched copy of the System and Kernel that came with the MF3 OTA update. The first question that many will have is, "Why did you release this - why wouldn't I just use <insert name here>'s stock rom?" It's simple: every other rom in this forum (at this time) has been modified from the original stock rom - whether they've added root, de-odexed it, debloated it, or otherwise. Because the Unadulterated rom is 100% stock (with stock kernel), it is possible for other developers to flash this rom and use it as a platform for attempting to find a root method for the MF3 users out there already. Plus, I like to make my own modifications from a stock base.
UPDATE (8-1-13): a root method has been found for MF3. See thread here. This ROM's purpose has been fulfilled, but your are still welcome to use it, of course!
UPDATE: The MF3 Odin files have been uploaded by @Shockndrop over in his thread here. Remember that the Odin files will flash your bootloader to MF3 (if you allow them), so be careful out there.
Rest assured, this rom will not update your bootloaders, it will not break your custom recovery, and it won't flash your modems. Like most roms, it will simply replace your /system and flash a Kernel. It's also scripted to wipe cache and dalvik for you. It will not wipe your /data partition - you might want to do so if you run into problems, especially when coming from other roms.
Next, you might ask, "How can you say this is 100% stock? How did you construct it?" I'll hide nothing from you - you can build it yourself if you'd like. Here's how I did it:
Rooted with motochopper
Installed TWRP 2.6.0.0
Wiped data & cache
Odin to MDL stock
Allow one full reboot:
Boot script runs (installs CSC - this is REQUIRED for the MF3 update to patch correctly)
Clears up any SysScope flags, etc. that may have persisted from previous rom or root.
"Temporary Root" using motochopper:
Code:
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
adb shell rm /data/local/tmp/pwn
NOTE: Possible outcomes of temporary root:
Failure
Success, motochopper exploit hangs, device spontaneously reboots
Success, immediate return to prompt, but adb shell is still not root (indicated by $ prompt)
Success, immediate return to prompt, adb shell is root (indicated by # prompt)
Repeat as needed (usually only twice or so?)
NOTE: Don't both trying to run su. It isn't installed. We're just relying on motochopper to give us a temporary adb root shell.
From adb root shell, installed TWRP recovery:
Code:
dd if=/sdcard/openrecovery-twrp-2.6.0.0-jflteatt.img of=/dev/block/mmcblk0p21
Rebooted, checked to be sure system status is still Official. Note that at this point, we've got a 100% stock MDL rom, without root, but with a custom recovery. Woot.
Rebooted into TWRP, installed custom-neutered OTA update (mf3-sys-only.zip), which only does the following:
Verifies all system files
Removes "unneeded" files (as determined by AT&T, not me)
Patches files
Copies new files
Sets permissions
Patches build.prop
Wiped data & cache for good measure
Booted phone, verified ROM works okay, system status = official. Rebooted, checked Odin Mode:
Code:
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
Booted back to TWRP to begin pulling dumps
... Now, on to the good stuff!
ROM Install Instructions:
Download mf3-stock-rom.zip and place it on your internal sdcard.
Make a nandroid backup of your existing system, data, cache, and anything else you deem important (everything!).
Flash/install the zip using your favorite custom recovery. This part should take several minutes - the file is huge!
Optionally, flash any additional Add-ons that you want (e.g. SuperSU for root)
Optionally, flash a custom kernel (use instructions from the kernel's author!). Note that some custom kernels will need you to flash Loki-Doki. The included kernel does not require Loki patching! It is 100% stock, and your system will accept it as-is.
Optionally, wipe /data. You can skip this, but if you get a ton of force-closes or extreme problems, this would be one of the first troubleshooting steps.
Reboot, and enjoy!
Click to expand...
Click to collapse
Important Recommendation:
You are advised to disable the OTA update applications! If AT&T/Samsung release a new OTA update (beyond MF3), it is theoretically possible to download and install it while using this rom! Accepting such an update could do just as much damage as the original MF3 update did. You can easily disable OTA updates from a root ADB shell using the following commands:
Code:
pm disable com.wssyncmldm
pm disable com.LocalFota
pm disable com.sec.android.fwupgrade
You could also use Titanium Backup Pro to accomplish the same thing. I will later look into the possibility of disabling these using a flashable Add-on zip that otherwise keeps your system as stock as possible.
Known Bugs:
If you do not flash a custom kernel, you will lose WiFi. The WiFi in the MF3 Kernel is expecting the MF3 bootloaders, which we aren't flashing. Therefore it breaks.
If you happen to have the MF3 modem/baseband installed, your WiFi might work, but your sound may stop working completely. This is also a result of not having MF3 bootloaders. A custom Kernel should fix this too.
If you use the "remove-SysScope" Add-on, be careful of any other mods that may poke around with SecSettings.apk - these are rare, but there's some risk of conflict here.
With the custom kernel I installed, I frequently received the "The device has detected an application attempting..." message. This can be pinpointed to the KNOX agent, and can be fixed a different ways (your choice!):
I found this post to be very helpful.
You can also try using the command pm disable com.sec.knox.seandroid from a root ADB shell. This just freezes the app. Personally, I used this method.
@jeboo also mentioned that the KNOXAgent.apk can be patched using smali/baksmali. Check out his post about it.
Also with the kernel I installed, there was a bug regarding updating the camera firmware. I was forced to restore the stock kernel temporarily, open the camera app to update the camera firmware, and then re-flash the custom kernel. The original MF3 kernel is included in the Add-ons.
Any other bugs are likely straight from AT&T/Samsung, otherwise they could be from your custom kernel, if you flashed one.
Be sure to make good backups of everything, and be prepared to use Odin back to stock. One member has reported that after flashing away from this rom to any other rom/kernel, their SIM card would not work until they used Odin to return to stock. After Odin, it worked fine.
It seems most custom kernels are expecting you to have an MDL baseband. Some people are reporting strange issues (such as problems with video streaming) when using MF3 modems and their choice of custom kernels. Check out File #11 for various modems, NON-HLOS modems, and kernels.
Custom Kernels:
Here's a list of custom kernels that are known-working with this rom. Please feel free to test and report other working kernels, and I will gladly add them to the list!
@jeboo's Kernel - built for @shoman94's SHOstock rom. Available in post #3 of their thread.
@Jamison904's Bioshock Kernel - available on the Infamous Development Website. This kernel is working great for me - no issues to report at this time. It also includes BusyBox v1.19.3, which was particularly useful for me. It appears that the kernels in their thread require Loki-Doki to be flashed after flashing the kernels. However, the one that I downloaded came from here: http://d-h.st/WVs and it was pre-patched for the I337.
@Jamison904's Infamous Kernel works really well, it seems. It also has BusyBox v1.19.3. I'm currently using v4.0, but there are newer versions available on his Dev-Host folder. These are for the M919, so flash Loki-Doki afterwards if you're on I337!
Downloads:
I've provided the rom in several different formats. When I last tested the odin-flashable tarballs, they did not work for me (due to signatures, etc). However, I'm still providing these for a few XDA members who will be testing them out on their semi-bricked devices. Additionally, someone might be able to get these signed somehow, and I'll leave this hanging out there as an invitation.
File #1 - mf3-stock-rom.zip - CWM/TWRP-Flashable ROM .zip file - created by hand (you are welcome to dissect it if you'd like - take a look inside the updater-script)
Files #2-#7 (individual image files and odin-flashables):
File #2 - system.img.ext4 - EXT4 format copy of the System partition - pulled using make_ext4fs in TWRP:
Used fdisk to obtain partition size:
Code:
# fdisk -l /dev/block/mmcblk0p16
Disk /dev/block/mmcblk0p16: 2894 MB, 2894069760 bytes
4 heads, 16 sectors/track, 88320 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p16 doesn't contain a valid partition table
Dumped the partition:
Code:
# make_ext4fs -s -l 2894069760 -a system /sdcard/system.img.ext4 /system
Creating filesystem with parameters:
Size: 2894069760
Block size: 4096
Blocks per group: 32768
Inodes per group: 8032
Inode size: 256
Journal blocks: 11040
Label:
Blocks: 706560
Block groups: 22
Reserved block group size: 175
Created filesystem with 3192/176704 inodes and 584765/706560 blocks
File #3 - system.img - Binary copy of the System Partition - pulled using dd:
This was much easier to create:
Code:
# dd if=/dev/block/mmcblk0p16 of=/sdcard/system.img bs=4096
File #4 - boot.img - Kernel - pulled from the OTA update file
File #5 - mf3-sys-boot.tar.md5 - "Odin-flashable" tarball - created without any modification:
Using a Linux PC or Cygwin, executed the following:
Code:
$ tar -H ustar -c system.img.ext4 boot.img > mf3-sys-boot.tar
$ md5sum -t mf3-sys-boot.tar >> mf3-sys-boot.tar
$ mv mf3-sys-boot.tar mf3-sys-boot.tar.md5
File #6 - mf3-sys-boot-sgs4ext4fs.tar.md5 - "Odin-flashable" tarball - "bloated" with Chainfire's sgs4ext4fs
Using a Linux PC (I used Ubuntu 13.04 64bit - couldn't get the win32 version to process the file entirely):
Code:
$ mv ./sgs4ext4fs.linux.amd64 ./sgs4ext4fs
$ sudo chmod 755 ./sgs4ext4fs
$ mv system.img.ext4 system.img.ext4.orig
$ ./sgs4ext4fs --bloat system.img.ext4.orig system.img.ext4
Optionally, you can use the "--list" option to view the file before and after the bloating. Once complete, pack it up in a tarball again.
File #7 - mf3-factoryfs.tar.md5 - "Odin-flashable" tarball - created using the system.img instead:
Using a Linux PC or Cygwin, executed the following:
Code:
$ mv system.img factoryfs.img
$ tar -H ustar -c factoryfs.img boot.img > mf3-factoryfs.tar
$ md5sum -t mf3-factoryfs.tar >> mf3-factoryfs.tar
$ mv mf3-factoryfs.tar mf3-factoryfs.tar.md5
Files #8-#11 (Add-ons!):
File #8 - UPDATE-SuperSU-v1.41.zip - ROOT! Flash this to root your new MF3 rom!
Original is found on Chainfire's website.
File #9 - remove-SysScope.zip - Want to stay "Official", even though you rooted? Flash this! It will remove SysScope and customize your SecSettings.apk to not check for SysScope anymore. Must be flashed before first boot, otherwise you'll just be stuck with a "custom" status until you remove it by some other means.
File #10 - mf3-kernel-only.zip - Want to quickly flash back to the MF3 stock Kernel again? Flash this. No need to use Loki-Doki after flashing this - the I337 will accept this just fine and boot.
File #11 - all-kernel-modem-apnhlos.zip - My personal collection of flashable .zip's of all available versions of the stock kernel, stock modem, and stock NON-HLOS modem for the I337 - including MDB, MDL, MF3. Unzip this file first, and flash individual partitions/versions in whatever combination you want.
Disclaimers, etc.:
I have only tested this with my AT&T Galaxy S4 (I337). While you are welcome to try this with other devices, I can't guarantee anything!
You are free to use this ROM, whole or in part, as a base for any other rom, mod, or otherwise. I do not gain profit from this, and the original rom was of course made by AT&T and Samsung. All I'm providing is a way to install it safely and easily. If you do use this rom as a base, please mention my name in your credits/thanks (thank you!).
I cannot be held liable for any damage you do to your own devices due to not following instructions or cataclysmic events beyond my control. Like any other rom, you assume all risks by flashing it to your device.
If you appreciate my work, please use the THANKS button below to let me know!

reserved...

First .. ..... Hey guess u got ur phone up and running huh ?

Nice post man! I still have hope for your recovery process
Here's another way to remove that annoying message without killing the entire APK:
http://forum.xda-developers.com/showthread.php?p=41794748#post41794748

as expected...
Aou said:
"I337UCUAMF3 Unadulterated"
This rom is a 100% pure, untouched copy of the System and Kernel that came with the MF3 OTA update. The first question that many will have
.......
[*]I have only tested this with my AT&T Galaxy S4 (I337). While you are welcome to try this with other device, I can't guarantee anything!
[*]You are free to use this ROM, whole or in part, as a base for any other rom, mod, or otherwise. I do not gain profit from this, and the original rom was of course made by AT&T and Samsung. All I'm providing is a way to install it safely and easily. If you do use this rom as a base, please mention my name in your credits/thanks (thank you!).
[*]I cannot be held liable for any damage you do to your own devices due to not following instructions or cataclysmic events beyond my control. Like any other rom, you assume all risks by flashing it to your device.[/list]
If you appreciate my work, please use the THANKS button below to let me know!
Click to expand...
Click to collapse
The result was what was expected.
Keeping my fingers crossed for other solutions...

iB4STiD said:
First .. ..... Hey guess u got ur phone up and running huh ?
Click to expand...
Click to collapse
Nope! Ended up needing to replace it, unfortunately. The original is a 100% hard brick. It won't even take the MF3 firmware via JTAG.
jeboo said:
Nice post man! I still have hope for your recovery process
Here's another way to remove that annoying message without killing the entire APK:
http://forum.xda-developers.com/showthread.php?p=41794748#post41794748
Click to expand...
Click to collapse
Awesome - thanks! I'll add that to the list of options. Also, thanks again for your awesome Kernel. v1.4 is exactly what I need for my phone.
SaltyFoam said:
The result was what was expected.
Keeping my fingers crossed for other solutions...
Click to expand...
Click to collapse
This is really unfortunate, but somewhat expected (as you've said). Have you tried the Odin-flooding again (even with the MDL or MF3 Recovery) yet? That was a very interesting accidental discovery you made. I'm going to have to try that myself too! It might have been a fluke, but still worth investigating.
As an update: The last file (mf3-factoryfs.tar.md5) has finished uploading, so I'm adding the link to the OP now.

FINALLY, someone else that respects untouched firmware. Glad to see this.

The odin flooding is not working at this point.
apparently one of the features of the new odin mode (aboot?) is that once it gets the 'failed auth' it stops responding to further pushes. It does not even allow the connection to be setup until a power down and restart.
As you can see in the other thread I submitted a warranty claim and they are replacing the device: as I have no backup device and a family that needs to get in touch with me (i.e. my wife and mother scolding me for not having a phone) I ran out of time...
I still have a few days with the old device before the replacement arrives...
I any case I am off to work.

If anyone wants to help create a flashable-zip that would disable the OTA updates without touching /system, I'm working on it here:
http://forum.xda-developers.com/showthread.php?t=2379517
I just need someone to write something up in a bash script that will make modifications to a file in /data. Should work without rooting the system.

Jah0n said:
FINALLY, someone else that respects untouched firmware. Glad to see this.
Click to expand...
Click to collapse
One thing I've seen in many "stock" roms is: "Completely stock, except for this.... and this.... and this mod I made here.... and this...."
-_-

I was curious - wanted to see what a true stock would feel like after all this time I have been rooted and using custom roms - anyway -I flashed this - everything seemed to work ok - but after restoring a nandroid - I lost data completely - I tried flashing a new rom and I got an error when trying to set it up saying that I needed to install my SIM - I tried to go into settings to add my APN and that error about the SIM came up again and would not let me add APN.
I could not get data to work on any nandroid or new flash and I ended up using odin to flash back to stock and then re-rooted.
I don't know if it was related to this rom -but it seems to be the only thing that could have caused it - unless you have an idea?

We should really team up on something sometime. I just created a hybrid stock UCUAMF3 kernel with the international (i9505) newest XXUBMGA image ROM. I removed the bloat but kept everything that is needed for all the settings to function. It runs so smooth, I'm not sure I want to go back to Google Edition... To release, or not to release. Okay, I'm done rambling. Great work so far from what I see here. Keep em clean!

mocsab said:
I was curious - wanted to see what a true stock would feel like after all this time I have been rooted and using custom roms - anyway -I flashed this - everything seemed to work ok - but after restoring a nandroid - I lost data completely - I tried flashing a new rom and I got an error when trying to set it up saying that I needed to install my SIM - I tried to go into settings to add my APN and that error about the SIM came up again and would not let me add APN.
I could not get data to work on any nandroid or new flash and I ended up using odin to flash back to stock and then re-rooted.
I don't know if it was related to this rom -but it seems to be the only thing that could have caused it - unless you have an idea?
Click to expand...
Click to collapse
It sounds like the other rom you flashed did not have a kernel. Easiest way to check is to open the zip file and check for a "boot.img" - that's the kernel (not the bootloader).
That's strange that your nandroid would not backup Data - did you check that option when you made the backup?

Jah0n said:
We should really team up on something sometime. I just created a hybrid stock UCUAMF3 kernel with the international (i9505) newest XXUBMGA image ROM. I removed the bloat but kept everything that is needed for all the settings to function. It runs so smooth, I'm not sure I want to go back to Google Edition... To release, or not to release. Okay, I'm done rambling. Great work so far from what I see here. Keep em clean!
Click to expand...
Click to collapse
Awesome! If the kernel turns out alright, we could add it to the list in the OP.

Aou said:
It sounds like the other rom you flashed did not have a kernel. Easiest way to check is to open the zip file and check for a "boot.img" - that's the kernel (not the bootloader).
That's strange that your nandroid would not backup Data - did you check that option when you made the backup?
Click to expand...
Click to collapse
The other rom had a kernel, but it doesn't matter because I flashed a different kernel with the other rom - the kernel was not the problem. If it didn't have a kernel, the rom never would have booted in the first place.
The problem is that mobile data did not work - at all. PLUS When I tried to add manually add an APN - it told me that I needed to add my SIM CARD. My SIm Card was fine - I never uninstalled it -
I have flashed and restored hundreds of roms and never had this happen before.
Something happened when I flashed your rom - that wiped out something related to my sim card.
I don't know what that would be - but as a result of flashing this rom - it happened. Just to verify, I redownloaded the rom - flashed it - and the same thing happened the 2nd time.
The phone booted fine and started the setup process - wifi worked fine - but the data bars showed NO DATA. I tried to manually add an APN and I got the same SIM CARD ERROR -so - when I tried to restore a nandroid - I got the same SIM CARD ERROR- I tried flashing a new rom - and got the same error - - the ONLY way I could fix it was to use ODIN and return to stock.
SO - Not sure why I seem to be the only one this has happened to - luck of the draw or something -

mocsab said:
The other rom had a kernel, but it doesn't matter because I flashed a different kernel with the other rom - the kernel was not the problem. If it didn't have a kernel, the rom never would have booted in the first place.
The problem is that mobile data did not work - at all. PLUS When I tried to add manually add an APN - it told me that I needed to add my SIM CARD. My SIm Card was fine - I never uninstalled it -
I have flashed and restored hundreds of roms and never had this happen before.
Something happened when I flashed your rom - that wiped out something related to my sim card.
I don't know what that would be - but as a result of flashing this rom - it happened. Just to verify, I redownloaded the rom - flashed it - and the same thing happened the 2nd time.
The phone booted fine and started the setup process - wifi worked fine - but the data bars showed NO DATA. I tried to manually add an APN and I got the same SIM CARD ERROR -so - when I tried to restore a nandroid - I got the same SIM CARD ERROR- I tried flashing a new rom - and got the same error - - the ONLY way I could fix it was to use ODIN and return to stock.
SO - Not sure why I seem to be the only one this has happened to - luck of the draw or something -
Click to expand...
Click to collapse
Makes a lot more sense now - thought you meant your data partition. >_<
And by another rom not having a kernel, it's still possible for roms to not include a kernel and work - the kernel lies in a separate partition and would remain untouched if the new rom didn't flash this.
I'll add this situation to the bugs list - thank you for the report!

Aou said:
Makes a lot more sense now - thought you meant your data partition. >_<
And by another rom not having a kernel, it's still possible for roms to not include a kernel and work - the kernel lies in a separate partition and would remain untouched if the new rom didn't flash this.
I'll add this situation to the bugs list - thank you for the report!
Click to expand...
Click to collapse
The kernel lies in a separate partition but twrp wipes it away by default so you'd have to unmount the boot partition
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Is boot.img a compressed file?

jortex said:
Is boot.img a compressed file?
Click to expand...
Click to collapse
I did not compress it at all. However it is not a full 10MB either. It's the exact file that came from the MF3 update package. The way that the OTA update .zip installs it is by doing this:
Code:
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
If you need a full 10MB partition dump (i.e. using dd or a nandroid), I can upload those if you need them for any reason.
UPDATE: I just did a binary comparison of the boot.img that came from the OTA .zip (the one I uploaded), and a nandroid backup I made. It was 100% identical, except the nandroid was padded with zeros at the end (a couple megabytes of zeros...)

Added another kernel to the list:
@Jamison904's Bioshock Kernel - available on the Infamous Development Website. This kernel is working great for me - no issues to report at this time. It also includes BusyBox v1.19.3, which was particularly useful for me.

[Q] I can't compile recovery

Hi all I'm translating cwm recovery. I downloaded cm source. But when i enter this command :
make -j4 recoveryimage
i get too many errors and compilation fails :
Code:
[email protected]:~/android$ make -j4 recoveryimage
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4.2
CM_VERSION=
TARGET_PRODUCT=full
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
TARGET_CPU_VARIANT=generic
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.8.0-19-generic-x86_64-with-Ubuntu-13.04-raring
HOST_BUILD_TYPE=release
BUILD_ID=KOT49H
OUT_DIR=/home/jale/android/out
============================================
/home/jale/android/out/target/product/generic/obj/APPS/SignatureTest_intermediates
find: “src”: No file or directory
grep: /build/target/board/generic/recovery.fstab: No file or directory
No private recovery resources for TARGET_DEVICE generic
build/core/tasks/kernel.mk:91: **********************************************************
build/core/tasks/kernel.mk:92: * Kernel source found, but no configuration was defined *
build/core/tasks/kernel.mk:93: * Please add the TARGET_KERNEL_CONFIG variable to your *
build/core/tasks/kernel.mk:94: * BoardConfig.mk file *
build/core/tasks/kernel.mk:95: **********************************************************
prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7/bin/arm-linux-androideabi-ld: error: /home/jale/android/out/target/product/generic/obj/lib/crtbrand.o: file is empty
make: *** [/home/jale/android/out/target/product/generic/obj/lib/crtbegin_static.o] Hata 1
make: *** Waiting for unfinished operations....
target thumb C++: libc <= bionic/libc/bionic/pthread_debug.cpp
target thumb C++: libc <= bionic/libc/bionic/libc_init_dynamic.cpp
cc1plus: warning: command line option '-std=gnu99' is valid for C/ObjC but not for C++ [enabled by default]
cc1plus: warning: command line option '-std=gnu99' is valid for C/ObjC but not for C++ [enabled by default]
bionic/libc/bionic/libc_init_dynamic.cpp:95:17: warning: unused parameter 'onexit' [-Wunused-parameter]
bionic/libc/bionic/pthread_debug.cpp:545:13: warning: 'void hashmap_removeEntry(HashTable*, HashEntry*)' defined but not used [-Wunused-function]
[email protected]:~/android$
Thanks.

I have the same problem. Have you been able to fix this?

Harmc0re said:
I have the same problem. Have you been able to fix this?
Click to expand...
Click to collapse
i already fixed this.
Sent from my Nexus 5 using Tapatalk.

yashade2001 said:
i already fixed this.
Click to expand...
Click to collapse
May I ask how ?

jdegreef said:
May I ask how ?
Click to expand...
Click to collapse
There was a problem with kernel tree.

yashade2001 said:
There was a problem with kernel tree.
Click to expand...
Click to collapse
Can you give details ? I have the same message. (no recovery resource...) The recovery finish building but doesn't boot.

jdegreef said:
Can you give details ? I have the same message. (no recovery resource...) The recovery finish building but doesn't boot.
Click to expand...
Click to collapse
Are u buildin for maguro?

yashade2001 said:
Are u buildin for maguro?
Click to expand...
Click to collapse
No, I'm building for trebon (gt-s7500) using omnirom sources. The rom is booting but not the recovery. I've also tried with CM11 TheWhisp trebon sources but with both I get this "No private recovery resources for TARGET_DEVICE trebon". I'm only interrested in the recovery.img as my goal is to port Philz CWM to trebon. But for this I first need to have the stock recovery working.

jdegreef said:
No, I'm building for trebon (gt-s7500) using omnirom sources. The rom is booting but not the recovery. I've also tried with CM11 TheWhisp trebon sources but with both I get this "No private recovery resources for TARGET_DEVICE trebon". I'm only interrested in the recovery.img as my goal is to port Philz CWM to trebon. But for this I first need to have the stock recovery working.
Click to expand...
Click to collapse
Make sure u have working device-vendor-kernel tree.

yashade2001 said:
Make sure u have working device-vendor-kernel tree.
Click to expand...
Click to collapse
Well, I assume it is correct as the rom compiles, is flashable and boot.
I have the feeling that recovery is broken in Omnirom.
Yesterday I build CM11 (nightly sources) for Galaxy Tab 2 (gt-p5100) and I get the same "No private recovery resources for TARGET_DEVICE p5100" message. BUT the rom is working AND the recovery too !
The fact that the recovery from Omnirom is not booting as therefore nothing to do with this message.
I'll keep on searching and, more important, learn
One month ago I didn't know anything about building a rom but I had some knowledge about compiling the Linux kernel.
Anyway thank you for your help.

jdegreef said:
Well, I assume it is correct as the rom compiles, is flashable and boot.
I have the feeling that recovery is broken in Omnirom.
Yesterday I build CM11 (nightly sources) for Galaxy Tab 2 (gt-p5100) and I get the same "No private recovery resources for TARGET_DEVICE p5100" message. BUT the rom is working AND the recovery too !
The fact that the recovery from Omnirom is not booting as therefore nothing to do with this message.
I'll keep on searching and, more important, learn
One month ago I didn't know anything about building a rom but I had some knowledge about compiling the Linux kernel.
Anyway thank you for your help.
Click to expand...
Click to collapse
Recovery from omni is twrp and buildin twrp is a little different

yashade2001 said:
Recovery from omni is twrp and buildin twrp is a little different
Click to expand...
Click to collapse
Yes, I notice that.
I've made progresses and been able to compile both cwm and twrp. Compilation goes without error, recovery.fstab, twrp.fstab and BoardConfig.mk seem correct and recovery is flashed on the right partition but the recovery doesn't boot. It either get stucked at the first Samsung logo, either bootlooping at that logo. I have no idea what could be the cause and, worst, I have no idea how to debug that...
Even the method with the extracted boot.img gives the same results.
Sent from my GT-P5100 using Tapatalk

P6000 General Thread - Bug fixes, FAQ, general info.

Elephone P6000
Phone reviews by @s7yler
Stock ROM (SPFlash):
from elephone servers
from needrom.com
Custom Recovery --- Touch RecoveryCourtesy of @bigrammy, @carliv and @Santhosh M​Various
Latin Paradise(拉丁乐园)(Elephone) on Baidu
P6000 Folder
OTA Updates - direct from elephone
--- both are 404 now ---
12282014 to 31012015
01092015 to 31012015
Other threads and useful sites:
http://forum.xda-developers.com/android/general/elephone-p6000-mtk6732-64-bit-4g-5-2g-t2957425
SP Flash Thread - P6000
4pda thread - translated top post is fairly concise
Check your Mobile Network/Carrier
Please use the other threads/Q&A and the thanks button - to minimise duplicate posts reporting the same issues.
I'd like this thread to be used mainly for bug fixes, tips and tricks. If someone reports a similar problem/fix/bug click the thanks button if you'd like to agree.

Bugs
Android 5.0 'Official' Release
Update Official (V3.3)
Some modifications: #186
Android 5.0 Beta
12-02-15 ROM available on needrom.com
Hardware buttons don't work
Battery doesn't draw charge
Ril related memory leak
No ADB​
Android 4.4.4 (V8.4)
Notification light - not breathing when charging
OTG only works with self-powered devices
Battery seems to jump from 100% to ~90% Soon after removing from charger
Screen jumps several pixels (30) on slow scrolling. ​Android 4.4.4 (V8.3) bugs not present in V8.4Data encryption results in a stalled boot/softbrick​
FAQ/Fixes
1. Notification light is not working in V8.4 as it was in V8.3
Try Light Manager from the play store or gravity box (xposed module)
2. Does OTG work?
It seems to work only with a powered USB hub - I've only been able to check a powered external hard-drive which wouldn't connect
3. How do you fix the screen jump issue?
There are several options here:
From @the1024 / zOrgent we have two options 1. Using a chinese tool - and 2. Using a .bat
From elephone we have TpUpgrade.apk (appears to only work with V8.4)
From lidmiloff we have P6000 Bugfixer.apk​
4. How do you restore a Stock ROM?
Download a SPFlash ROM from #1; you will need to install MediaTek USB VCOM drivers (if they aren't automatically installed); On the download page select the scatter from the ROM folder; and the page should populate with the various .img's and .bins; if it doesn't then double click on the entry and locate it manually (also useful if you wan to change boot/recovery with SPFlash). Hit download; remove the battery from the phone and connect it to the PC (you can connect the battery again). The connection will be fairly instantaneous (there may be a driver install the first time it's connected); if it doesn't connect then unplug/replug.
More details from @bigrammy found here
5. Battery jump from 100% to 90%.
Haven't really noticed this too much - download an app like Battery Monitor Widget, add widget (Battery monitor widget gauge => Content => Central value => Battery => Battery Current (mA)) which will show you the battery drain/draw and charge until the draw is close to; if not +0mA
6. Is there any touch recovery?
As of now (pre-5.0) there is no touch recovery. The recovery thread on #1 contains various recoveries - most of which boot but none have touch - this seems to be a kernel issue.
Touch recoveries can be found here. These are built for KK.
7. What about Custom ROMs?
Potential Port devices (MT6732/MT6752) and their ROMS
As there are no official sources released; for MT6732 or P6000 then custom ROMs are a no-go for now. Porting ROMs from other devices running on MT6732 (and MT6752); i.e. Ulefone Be Pro for example is theoretically possible but there doesn't appear to be any custom ROMs on these chips that offer anything different than the stock/AOSP(almost) that we have already. As other devices get released possibly running MIUI or ColorOS then Custom ROMs may be possible.
FlymeOS
8. How do you take a screenshot?
Natively pressing Volume down and power together for 1 second will take a screenshot - it may take a while to get used to - if volume mixer appears then they were too slow and need to wait for it to disappear. Over adb/terminal you can make use of screencap and screen record
9. How do you back up EVERYTHING(except preloader)?
In SPFlash Tools => readback from 0x00 to 0x3a3e000000
This is a fairly quick way to make sure you have a copy of all the partitions on the device; it will create a 14GB+ file containing all the partitions. You will need to break this block up (manually for the moment) into it's constituent parts if you want to use it to restore - using a Hex-editor (HxD for example) and a copy of the matching /proc/partinfo file and/or scatter.txt
The essential partitions to backup for a fully running device are - boot, (recovery), system, (cache) and data which can all be backed up using a custom recovery. The one other partition needed is nvram - this can be backed up with SPFlash (look at /proc/partinfo) or with dd commands. The nvram partition will only be needed to be restored if you Format All with SPFlash. If you don't have a backup you can restore/recreate the IMEI files that it contains.
10. How do you backup/restore IMEI?
Several options here:
1. MTKDroid
2. Backup NVFLASH partition via readback in SPFlash Tools (look at the scatter.txt) to restore you need to modify the scatter.txt to give the nvflash a file_name: and change it from is_Download: false to is_Download: true
3. From elephone there's a IMEI coding tool
4. Keep a copy of the /data/nvram folder
5. Create new imei files to add to nvram folder/partition with imei.exe
6. Chamelephon app from the play store
7. MTK Engineering Mode
11. Adb access with 5.0 Beta ROMs
1. Use KingoRoot
2. Add the Mediatek subsystem id (0x0e8d) to adb_usb.ini
12. Any Stock Camera fixes?
For KK-4.4.4 from @z0rgent at 4pda

FAQ/Fixes Continued
Android 5.0 V1; V1.1; V2.2 (V3.2); V3.3 #125 #186These versions seem to have gapps preinstalled and are prerooted - for everything else have a look at the 5.0 Betas section below
5.0 Modifications #186​Android 5.0 Beta1 Beta2 Beta3
To gain adb access
Linux/Windows - need to add the Mediatek subsystem id (0x0e8d) to adb_usb.ini
Linux: ~/.android/adb_usb.ini
Windows: C:/Users/${Username}/.android/adb_usb.ini​KingoRoot It won't root the device however - I believe this is due to it installing a 32bit su binary rather than a 64bit one.
Root
For root install SuperSU v2.11+
Confirmation
Custom Recovery
Recovery from @carliv - from #1; modded to boot on L (basically just the cmdline changed / initrd.gz from stock L recovery replaced with carliv's built CWM).
Carliv Port by hanuma50 on 4pda (hopefully all his work and not partially stolen to take credit)
This recovery seems to only work when the Lollipop Beta ROM is installed.
Gapps
64-bit gapps made for the Nexus 9.
My phone seems to be running a little hot after installing the gapps - but that might just all the cores kicking in.
Mirrored copy of the version I'm using.
(OP's thread has updated them and removed the previous version)
Busybox
64-bit busybox installation
Removing encrypted data (temporarily)
In recovery while in an adb shell: /sbin/make_ext4fs /dev/block/mmcblk0p19
This will allow you to restore backed up data - but it will get re-encrypted on first boot, I'll take a look at removing encryption when I get the chance - should be either secro partition or something in the boot.img​
Android 5.0 Beta Breakdown
Screenshots to come later.
Entering LKVOL UP and POWER (this no longer enters recovery)
From lk menu: entering fastboot mode and normal boot works.
Entering recovery (stock) doesn't work and I can't tell if the other normal boot options do anything different​Charging batteryFlashing a custom recovery should allow you some way to charge the battery​I haven't yet been able to install/boot any recovery. Flashing lk and boot from 4.4.4 (I took them from the 48MB OTA) seems to let you charge when powered off. Confirmed​RIL Memory leakThere seems to be a RIL/Sim related memory leak leading to random reboots - for testing purposes disable the sim card(s) or enter airplane mode
I could be wrong about the RIL and the ROM just needed time to settle; all I can say is I had reboots until I switched to airplane mode​IMEIIMEI was lost but that would be due to formatted flash memory (wiped nvflash partition) - it's a good idea to keep a backup regardless.​Antutu Scores64-bit Antutu Scores are around 28000
32-bit Scores are around 27000
Data-encrypted 4.4.4 Antutu scores are also around 28000​SensorsBacklight, sound ... can't be changed
Brightness can be fixed in MTK Engineering Mode #5​ROM is not rooted; does not have gapps installed and data is encrypted.
TL;DR The issues with the 5.0 Beta ROM, are primarily not ROM related but kernel related, they have bumped the kernel version up to 3.10.61+, and the issues that need correcting are the various kernel modules (power,sensors).
Android L kernel config

Annotated /system/build.prop
Stripped top of build.prop (build properties) due to size
# begin mediatek build properties
ro.mediatek.version.release=ALPS.KK2.MP13.V1.27
ro.mediatek.platform=MT6752
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=KK2.MP13
ro.mediatek.version.sdk=3
# end mediatek build properties
#
# from out/target/product/k01q_e/obj/CUSTGEN/config/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
#
wifi.tethering.interface=ap0
#
ro.opengles.version=196608
wifi.direct.interface=p2p0
# dalvik.vm.heapgrowthlimit=256m
# dalvik.vm.heapsize=512m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
# Switching Menu of Mass storage and MTP
ro.sys.usb.storage.type=mtp #### adding ,massstorage to this gives an additional USB option but it apears to still mount as a media device (MTP) adding ,mass_storage will let you mount the microsd card
# USB BICR function
ro.sys.usb.bicr=no #### changing to yes will allow you to mount /system/mobile_toolkit/iAmCdRom.iso to PC via USB ####
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=0
ro.gemini.sim_switch_policy=1
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.btstack=blueangel
ro.sf.hwrotation=0
ril.current.share_modem=2
curlockscreen=1
ro.mediatek.gemini_support=true
persist.radio.fd.counter=15
persist.radio.fd.off.counter=5
persist.radio.fd.r8.counter=15
persist.radio.fd.off.r8.counter=5
persist.radio.fd.on.only.r8.network=0
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=0
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
persist.mtk.anr.mechanism=1
mediatek.wlan.chip=CONSYS_MT6752
mediatek.wlan.module.postfix=_consys_mt6752
ril.radiooff.poweroffMD=0
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.config.ringtone=Backroad.ogg
persist.mtk.wcn.combo.chipid=-1
ter.service.enable=0
mediatek.extmd.usbport=0
ro.lte.dc.support=0
ril.active.md=0
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.4.4
ro.com.google.clientidbase=alps-k01q_e-{country}
ro.com.google.clientidbase.ms=alps-k01q_e-{country}
ro.com.google.clientidbase.yt=alps-k01q_e-{country}
ro.com.google.clientidbase.am=alps-k01q_e-{country}
ro.com.google.clientidbase.gmm=alps-k01q_e-{country}
wfd.dummy.enable=1
persist.sys.dalvik.vm.lib=libdvm.so #### Charnging this to libart.so appears to have no effect ####
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
# begin fota properties
ro.fota.platform=MTK6732_KK
ro.fota.type=phone
ro.fota.oem=new-bund6732_KK
ro.fota.device=k01q_e
ro.fota.version=eng.jenkins.1422677980
# end fota properties
ro.sf.lcd_density=190
#### Stock value I believe is 320; changing to >190 switches the device to phablet mode; this spoofs the screen size to be 7.73 inches (CPU-Z) enabling tablet apps in the apps store after clearing play store app data ####
qemu.hw.mainkeys=0
#### This enables softkeys ####
Annotated /custom/customprop/custom.prop
ro.product.model=Elephone P6000
ro.product.name=Elephone P6000
ro.product.brand=elephone
ro.product.manufacturer=elephone
ro.bt.name=P6000
ro.wifi.name=P6000
ro.notification.breath=yes #### This seems to not be working with V8.4 ####
ro.build.display.id=ALPS.KK2.MP13.V1.27
ro.internal.build.version=K01Q-E.ELEPHONE.vR83.E4.150109
ro.custom.build.version=Elephone_P6000_V8.4_20150109
ro.fota.device=Elephone_P6000
ro.fota.version=Elephone_P6000_V8.4_20150109202612

MTK Engineering Mode
*#*#3646633#*#* (*#*#ENGMODE#*#*)
What can be done in engineering mode
General non-specific guide
Backlight
Hardware ===> LCM ===> LCM Cycle ===> add a value between 5 and 55 ===> Hit Set.
(On L at least this value will jump to value in the millions/billions; unsure if this has any implications)
Audio
http://forum.xda-developers.com/showthread.php?t=2746861
http://forum.xda-developers.com/showthread.php?t=2248396
GPS
http://www.cnx-software.com/2013/11...ps-lock-on-mediatek-mt65xx-based-smartphones/
Orientation / GSensor
Hardware Testing ===> Sensor ===> Sensor Calibration ===> GSensor Calibration ===> Do Calibration (20% tolerance)
IMEI Restore
Command should be AT +...
Xposed Installer (or WSM Tools)
I've had no problems with any xposed modules.
You will get a warning regarding AliyunOS -
this issue is reported due to the presence of /system/framework/*.jar.jex files.
You can ignore/move/remove these *.jar.jex files without it causing any (noticable) issue.
I haven't decompiled any apps so I don't know if. jex files are used elsewhere within the ROM (in place of .jar),
so can't comment on whether the stock ROM is indeed an Aliyun OS.
I would advise backing them up so that any future OTA can complete 100%.
Any issues identified with xposed modules will be reported here.​

Very Helpful and concise
Nice one bro :good:
Subscribed

Ludmiloff's Screen fix apk version 1.2 final now works with 8.3 also. Just wanted to give you a quick update so you edit your post HypoTurtle

greekfragma said:
Ludmiloff's Screen fix apk version 1.2 final now works with 8.3 also. Just wanted to give you a quick update so you edit your post HypoTurtle
Click to expand...
Click to collapse
Still doesn't work for me on 8.3.

Nice one, i get my phone in a couple of weeks.

Hello
and Thanks for all your work ! :victory:
Can you add how save and restore imei ?

xenonism said:
Still doesn't work for me on 8.3.
Click to expand...
Click to collapse
Sorry to hear that man. Can you give more details? Are the driver version letters shown normal or "?"

greekfragma said:
Sorry to hear that man. Can you give more details? Are the driver version letters shown normal or "?"
Click to expand...
Click to collapse
Well, I tried the first methods which came out and they wouldn't work. Then I upgraded to V8.4, at the same time the Elephone APK came out, so I used it and it set the thresholds to 3 and 4. Then I decided to go back to V8.3 and since then, no method managed to make a persistent change to the values (I tried ludmiloff's works, Elephone's APK modified by me, which worked for others, and the old Russian method). At best, I get the new vaules in the "init config" portion of the configuration, never in the "real config" portion, and they are always gone after a reboot. File permissions of /proc/gt9xx_config are 660, owned by root. The config version letter is currently F and ludmiloff's app reads it correctly.
I guess that's all the info I can share.

xenonism said:
Well, I tried the first methods which came out and they wouldn't work. Then I upgraded to V8.4, at the same time the Elephone APK came out, so I used it and it set the thresholds to 3 and 4. Then I decided to go back to V8.3 and since then, no method managed to make a persistent change to the values (I tried ludmiloff's works, Elephone's APK modified by me, which worked for others, and the old Russian method). At best, I get the new vaules in the "init config" portion of the configuration, never in the "real config" portion, and they are always gone after a reboot. File permissions of /proc/gt9xx_config are 660, owned by root. The config version letter is currently F and ludmiloff's app reads it correctly.
I guess that's all the info I can share.
Click to expand...
Click to collapse
Well, time to get in here, I guess...
@xenonism, the best I could tell you is to start over with clean ROM, preferably the one listed at 4pda.ru thread about elephone P6000 (in the head section) and try again. There must be something messed up in your device. I really believe the config is independent of ROM. The secret is very simple, you must start with new version letter and at offset 184 set correct checksum. How to calculate checksum:
//cal checksum
byte checksum;
for(i=0; i<chip_cfg_len; i++) {
checksum += file_config;
}
file_config[chip_cfg_len] = (~checksum) + 1;
Where chip_cfg_len = 184
Then write the checksum and write 0x01 at offset 185.
I believe you already know where are the theshsold values - at offset 16 and 17.
If you wish, I could send you my hand crafted config, which I was an inspiration for my apk.
Good luck

Err... it looks like I am unable to install a clean ROM, or even to update the existing one. I guess I'll have to sort this issue out before I join back the discusssion.
I have a fully functionalV8.3_20141228 ROM running and carliv's CWM from the 7th of February installed. The phone offers me the OTA update and it downloads a ~23 MB update. When I agree to install it, the phone reboots to CWM and the update fails with the following messages:
E:Invalid command argument
Finding update package...
E:unknown volume for path [/storage/sdcard0/adupsfota/update.zip]
E:Can't mount /storage/sdcard0/adupsfota/update.zip
Installation aborted.
Click to expand...
Click to collapse
If I try to install the same update with ROM Manager, it also fails in CWM with the following message:
-- Installing: [FILENAME SHOWS HERE]
Finding update package...
Opening update package...
Installing update...
Installation aborted.
Click to expand...
Click to collapse
But when I reboot the phone, I get the "Android is upgrading...] Screen, saying it's optimizing 124 apps. I believe no actual update takes place, though.
And here's what I'd consider the relevant portion of the recovery.log file:
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/platform/mtk-msdc.0/by-name/userdata on /data failed: Device or resource busy
mount: mounting /dev/block/platform/mtk-msdc.0/by-name/cache on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
about to run program [/sbin/chmod] with 3 args
about to run program [/tmp/recovery/11-rommanager.sh] with 2 args
mount: mounting /dev/block/platform/mtk-msdc.0/by-name/system on /system failed: Device or resource busy
about to run program [/sbin/umount] with 2 args
Click to expand...
Click to collapse
If I try to install the full 20150109 ROM with ROM Manager, it also fails in CWM, without displaying any meaningful messages in recovery. I also get the "Android is upgrading screen here".
The errors in recovery.log are the same as above.
I guess I could install the full ROM via SP Flash Tool, right?
Also... I have a couple of questions to ask, can I feel free to do it in this thread? Some might be trivial for most.

ludmiloff said:
Well, time to get in here, I guess...
@xenonism, the best I could tell you is to start over with clean ROM, preferably the one listed at 4pda.ru thread about elephone P6000 (in the head section) and try again.
Click to expand...
Click to collapse
@ludmiloff does your app require busybox to be installed?
Downloading from 4pda.ru is a bit hit and miss for me, any chance someone can post the CWMLollipop.img...
Is there any difference in the 4pda.ru ROMs and the ones on needrom.com?
Also found a fix for the backlight in Android L - in engineering mode - not sure if it will do anything useful in 4.4.4 (lower the minimum brightness?).
MTK Engineering Mode => Hardware => LCM => LCM Cycle => value between 5 and 55.
xenonism said:
Err... it looks like I am unable to install a clean ROM, or even to update the existing one. I guess I'll have to sort this issue out before I join back the discusssion.
Click to expand...
Click to collapse
Feel free to elaborate. Edit your previous post with your current setup / what you've tried - so we can turn it into a troubleshooting post.

HypoTurtle said:
Feel free to elaborate. Edit your previous post with your current setup / what you've tried - so we can turn it into a troubleshooting post.
Click to expand...
Click to collapse
Ok, thanks a lot. I will edit my post right now. The thing is... I haven't used an Android phone in 4 years and I did a lot of my tinkering on my P6000 while working or late at night so.. things got a bit messy.

@HypoTurtle,
My app does not require busybox. It simply run some commands in the shell, though.
In fact It is my first experience with android programming and I just followed some examples found here and there. I also wanted to make a Kotlin based app, but then I decided to continue with plain old java. The app might not a perfect one. Hope it worked for many of elephone owners
---------- Post added at 08:05 AM ---------- Previous post was at 07:41 AM ----------
@xenonism, you should try a clean ROM with sp flash tool. It is a bit tricky, I have tried one from needrom and as the author suggested, I did not check the preloader mark. Then my phone ended totally bricked. The ROM from 4pda worked for me. Today I'm going to reflash it again and investigate why my app does not work on it.

@ludmiloff, I ended up installing 20150109 via SP Flash Tool and then updating via OTA to the latest version. Sure enough, your app worked then. And permissions for gt9xx_config are now 666.
I am not particularly happy with the gravitybox solution for the notification issue, so I'm trying to look into it, but I am not really hopeful to achieve something.

xenonism said:
@ludmiloff, I ended up installing 20150109 via SP Flash Tool and then updating via OTA to the latest version. Sure enough, your app worked then. And permissions for gt9xx_config are now 666.
I am not particularly happy with the gravitybox solution for the notification issue, so I'm trying to look into it, but I am not really hopeful to achieve something.
Click to expand...
Click to collapse
Same I did just few minutes ago. Won't install updates and will try to make my app working on this ROM.
BTW. Russian method write a very different format to file /process/gmnodexxxxxxx where xxxxxxx is build date. I'm pretty sure if I could change the file with correct checksum and version letter it should work too.
Anyway, my intent was to fix the scroll after I applied the elephone apk. For sure the Russian method with correct version letter and checksum would work too and it is still the best flow now for phones with very stock ROM. I already explained how to calculate the checksum.

HypoTurtle said:
@ludmiloff does your app require busybox to be installed?
Downloading from 4pda.ru is a bit hit and miss for me, any chance someone can post the CWMLollipop.img..
Click to expand...
Click to collapse
I cant see any CWMLollipop.img there
They only list two recoverys my P6000CWM3.img with no links or credits of course
and carliv's CWM_Modd_2.img again no links or credits
I will be working on the lollipop soon
I am getting another phone very soon to use for daily life so I can use the P6000 for dev only purposes.

[ROM] Unofficial LineageOS 16.0 PQ3A.190801.002] for ZTE Blade S6 (P839F30)

Code:
[I]DISCLAIMER[/I]
[COLOR="red"]Do not mirror my builds![/COLOR] Please post a link to this thread instead.
All information and files — both in source and compiled form — are provided on an as is basis.
No guarantees or warranties are given or implied. The user assumes all risks of any damages
that may occur, including but not limited to loss of data, damages to hardware, or loss of
business profits. Please use at your own risk. Note that unless explicitly allowed by the
warranty covering your device, it should be assumed that any warranty accompanying your
device will be voided if you tamper with either the system software or the hardware.
Introduction
This is my unofficial build of LineageOS 16.0 for the ZTE Blade S6 aka P839f30.
This is the first alpha release, so be aware that issues could arise.
I have tested this version with my AS variant device. Other variants have to be tested.
Click to expand...
Click to collapse
Features
working:
phone: calls, sms, data.
wifi
bluetooth
sensors
gps: mostly I have used the energy saving mode
sound
camera: rear with flash and front.
torch
headphone detection
swap back and menu button
light: button backlight, brightness control and adaptive brightness, breath light (notification and/or battery)
not working:
SELinux is permissive.
We have to test to find out.
Click to expand...
Click to collapse
Installation instructions
It is best to have installed the latest stock rom beforehand, so modem and all other vendor stuff is up to date.
If you like you can use this mod to have a unified data partition, please proceed with caution.
You will need TWRP or any other custom recovery.
Reboot into recovery and do a nand backup.
Do a factory format.
Download Rom and put it on your phone or use adb sideload.
Install the rom and then clear cache and dalvik cache.
optional: install su and/or gapps (preferable pico).
Click to expand...
Click to collapse
Changelog:
25.05.2021 - new release:
los security patch level 05.05.2021
revert some kernel changes from the last release
add some cpu governors and cpu hotplug
now with Boeffla WakeLock Blocker and other things
wireguard kernel support
22.12.2019 - 1st beta release:
los security patch level 05.12.
kernel supports EU device variant
add autosmp hotplug
add cpu governors blu_active, darkness, lionfish and relaxed
Revert CwMcu sensor driver from SU6 kernel release
24.10.2019 - 2nd alpha release:
los security patch level 05.10.
CwMcu sensor driver from SU6 kernel release, with wake lock disabled
wifi mac is loaded anyway, remove the loading in the wifi driver
give bluetooth a null mac address, to overcome force close error
kang gps from oppo
04.10.2019 - 1st alpha release:
los security patch level 05.09.
initial release of pie
Click to expand...
Click to collapse
Downloads
new release - 25.05.2021:
Google Drive.
first beta release - 22.12.2019:
Google Drive or here.
second alpha release - 24.10.2019:
Google Drive or here.
first alpha release - 04.10.2019:
Google Drive or here.
If you want root use the lineage addon package found here - download arm version.
Install it after flashing the rom or download your favourite root package and install it.
Click to expand...
Click to collapse
Sources
device
msm8916-common
vendor
kernel
Click to expand...
Click to collapse
FAQ
Here you will find some answers to common question which could arise.
Q: How to give root access to an app or adb?
A: First install the su extra package from Lineage OS or any other su tool you like. Then go into settings and about device, click there multiple times on the build number until you unlocked the developer options. Go to developer options and look for root access.
Q: I thing I found an issue, what to do now?
A: Do a logcat or grab a dmesg while having the issue, otherwise we can't say what is happening. Report as much info as possible. Quote your stock rom your device shipped with or which device variant you possess.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
*aquaris-dev team
*aymende7
*PacMM79
*LineageOS team
*many others
XDA:DevDB Information
Unofficial LineageOS 16.0 [PQ3A.190801.002] P839F30, ROM for the ZTE Blade S6
Contributors
lightwars
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: LineageOS 16.0
Version Information
Status: Beta
Current Beta Version: 20191213
Beta Release Date: 2019-12-22
Created 2019-10-04
Last Updated 2019-12-22

many thanks for the new version, i will tested later :good: :highfive:
Hello, works on my ZTE Blade S6 Plus (p839f50)
but only with a fixed updater-script
from Folder: lineage-16.0-20191002-UNOFFICIAL-p839f30.zip\META-INF\com\google\android
the bold text must delete and than save the file
after the start my phone , i have a error message with bluetooth is deactivated
updater-script - original
https://filehorst.de/d/crqjwnjI
updater-script - fixed
https://filehorst.de/d/cbmctorj

new update is in the op.
just small changes and updated security patch level.

Anybody tested with EU device?
... at the moment no time to test myself (to much effort to keep my other devices up-to-date ), just wanted to ask if anybody already tested on EU device (and forgot to post ).
Gtz
Kurt

Kurt Krummbein said:
... at the moment no time to test myself (to much effort to keep my other devices up-to-date ), just wanted to ask if anybody already tested on EU device (and forgot to post ).
Click to expand...
Click to collapse
Answer my own request, gave it a try, didn't boot, screen stayed black and device went into fastboot-mode ... restored my nandroid-backup of stock-EU-B15 .
Next time, i format system and just install rom without gapps and addon-su.
Gtz
Kurt

Kurt Krummbein said:
Answer my own request, gave it a try, didn't boot, screen stayed black and device went into fastboot-mode ... restored my nandroid-backup of stock-EU-B15 .
Next time, i format system and just install rom without gapps and addon-su.
Gtz
Kurt
Click to expand...
Click to collapse
Hello Kurt,
please, if you find the time to do another test. Download the attached zip extract the boot.img and copy it to your device, flash it with twrp right after installing the lineage zip through twrp. report back if something different happens.
I splited the dtb from the zImage and attached the almost stock eu dtb, so maybe we are lucky. But I have not find any big differences in analyzing the dts of EU vs AS and kernel defconfigs EU vs AS.
I can show this files too, if somebody has a better understanding of this.

lightwars said:
Hello Kurt,
please, if you find the time to do another test. Download the attached zip extract the boot.img and copy it to your device, flash it with twrp right after installing the lineage zip through twrp. report back if something different happens.
I splited the dtb from the zImage and attached the almost stock eu dtb, so maybe we are lucky. But I have not find any big differences in analyzing the dts of EU vs AS and kernel defconfigs EU vs AS.
I can show this files too, if somebody has a better understanding of this.
Click to expand...
Click to collapse
Hi!
Well, i loaded the def's and config's into WinMerge and did a compare ... in the def's there are some different addresses, but i have now clue what the meaning of that all is :angel:. The config files look like beeing from different kernel versions, there are some options which don't exist in both, one is modularised, the other is not ... all in all quite strange.
Ok, i made a try with the boot_eu.img:
- Made a factory reset
- Flashed the LOS.zip
- Wiped caches
- unzipped the boot.img
- copied it to boot partition with dd if=boot_eu.img of=/dev/block/bootdevice/by-name/boot
- reboot
... screen goes black, one buzz .... nothing. One the PC the fastboot device appears and that's it. I was looking for tombstones, but couldn't find any ... they are stored to /data/tombstones, are they? I'm not sure, the kernel i getting up high enough to mount /data.
Cheers
Kurt
P.S.: one thing i forgot to mention ... i coulnd't find the "OEM unlock" swich in the stock system anywhere and the bootloader seems to be quite dumb, many commands from fastboot just end in a "command unknown", perhaps there's something left to do on my side (tweak in build.prop etc ... googleed for it no result ).

Kurt Krummbein said:
Ok, i made a try with the boot_eu.img:
- Made a factory reset
- Flashed the LOS.zip
- Wiped caches
- unzipped the boot.img
- copied it to boot partition with dd if=boot_eu.img of=/dev/block/bootdevice/by-name/boot
- reboot
... screen goes black, one buzz .... nothing. One the PC the fastboot device appears and that's it. I was looking for tombstones, but couldn't find any ... they are stored to /data/tombstones, are they? I'm not sure, the kernel i getting up high enough to mount /data.
Click to expand...
Click to collapse
Thanks for testing. You used the reboot system button of twrp I guess. Have you tried to reboot by pressing the power button?
I can think of two things: There is some flag in the kernel source which is called download_mode. I have seen that some devices have different default values! At the moment the value is 0, devices like the ones from bq with msm8916/msm8939 used this too, but devices from oppo with msm8939 uses a value of 1 as default. We can try this one.
Or there is a mask, which defines the restart reason so to speak says the device which mode to boot to. Here we have some differences in the meaning of the bits, a different bit shifting is used.
I can not really think that one of these causes your device to boot into download mode, because the recovery uses the same kernel on both region variants...

lightwars said:
Thanks for testing. You used the reboot system button of twrp I guess. Have you tried to reboot by pressing the power button?
I'll give that one a try .
Hope my device is not "going over the Wupper" LOL (this one has to come somewhen ...)
Click to expand...
Click to collapse
Ok, tried it ... same result. Then did a (perhaps a bit wired) test, just restored boot from my nandroid-backup. With this, the white ZTE bootscreen comes up and after some seconds it reboots to twrp.
Perhaps the dumb-bootloader refuses to boot with AS keys ... otherwise it wouldn't boot recovery. Strange puzzle.
Cheers
Kurt

Kurt Krummbein said:
Ok, tried it ... same result. Then did a (perhaps a bit wired) test, just restored boot from my nandroid-backup. With this, the white ZTE bootscreen comes up and after some seconds it reboots to twrp.
Perhaps the dumb-bootloader refuses to boot with AS keys ... otherwise it wouldn't boot recovery. Strange puzzle.
Cheers
Kurt
Click to expand...
Click to collapse
It is okay to do some unusual testings. I was doing this sort of things also, back then.
I'm not sure I get you, when you write about AS keys. Do you mean the fingerprint in the build.prop? I think I used the ones from the eu version. Maybe they build in some kind of kernel version check inside the bootloader, but only for the eu and other versions.
The cause is, that android needs an advanced kernel, so we can not use the stock kernel to boot newer android version like nougat, oreo or pie.
Sorry, I can not be of much help here, because I do not have a device with eu or some other region version. But we can try do some changes, if you like to do some more testing and maybe get something like a log, last_kmseg or ramoops. We should look to activate some of them.

Hello @Kurt Krummbein,
if you find the time please post the info you get by issuing this commands in the adb shell or on your phone in a terminal:
Code:
su
cat /sys/zte_board_id/board_id
cat /proc/device-tree/model
cat /proc/device-tree/compatible
Do this on your rom or stock rom you are using a the moment. Thank you.
For reference mine output is this:
Code:
Blade-S6:/ # cat /sys/zte_board_id/board_id
wrbA
Blade-S6:/ # cat /proc/device-tree/model
Qualcomm Technologies, Inc. MSM 8939 MTP
Blade-S6:/ # cat /proc/device-tree/compatible
qcom,msm8939-mtp qcom,msm8939 qcom,mtp
It could be that the eu variant uses another device tree inside the kernel, because the bootloader request that, but we have only this model available.

lightwars said:
Hello @Kurt Krummbein,
if you find the time please post the info you get by issuing this commands in the adb shell or on your phone in a terminal:
Code:
su
cat /sys/zte_board_id/board_id
cat /proc/device-tree/model
cat /proc/device-tree/compatible
Do this on your rom or stock rom you are using a the moment. Thank you.
For reference mine output is this:
Code:
Blade-S6:/ # cat /sys/zte_board_id/board_id
wrbA
Blade-S6:/ # cat /proc/device-tree/model
Qualcomm Technologies, Inc. MSM 8939 MTP
Blade-S6:/ # cat /proc/device-tree/compatible
qcom,msm8939-mtp qcom,msm8939 qcom,mtp
It could be that the eu variant uses another device tree inside the kernel, because the bootloader request that, but we have only this model available.
Click to expand...
Click to collapse
Mine is:
cat /sys/zte_board_id/board_id
wrbA-EUROPE
cat: /proc/device-tree/model: No such file or directory
cat: /proc/device-tree/compatible: No such file or directory
ls /proc/device-tree
/proc/device-tree: No such file or directory
Attached my build.prop ... perhaps this sheds some light .
Thx
Kurt

Kurt Krummbein said:
Mine is:
cat /sys/zte_board_id/board_id
wrbA-EUROPE
cat: /proc/device-tree/model: No such file or directory
cat: /proc/device-tree/compatible: No such file or directory
ls /proc/device-tree
/proc/device-tree: No such file or directory
Attached my build.prop ... perhaps this sheds some light .
Thx
Kurt
Click to expand...
Click to collapse
Sorry for that, I forgot that the stock kernel did not expose the device tree.
But I think I remeber the info about the model is in the logcat after boot up...
Please try this ones in a terminal on the phone or via adb shell, they should work.
Code:
su
Blade-S6:/ # cat /sys/devices/soc0/hw_platform
MTP
Blade-S6:/ # cat /sys/devices/soc0/soc_id
239

lightwars said:
Sorry for that, I forgot that the stock kernel did not expose the device tree.
But I think I remeber the info about the model is in the logcat after boot up...
Please try this ones in a terminal on the phone or via adb shell, they should work.
Code:
su
Blade-S6:/ # cat /sys/devices/soc0/hw_platform
MTP
Blade-S6:/ # cat /sys/devices/soc0/soc_id
239
Click to expand...
Click to collapse
mine is:
cat /sys/devices/soc0/hw_platform
MTP
cat /sys/devices/soc0/soc_id
268
cat /sys/devices/soc0/image_version
10:LRX22G:eng.root.20150808.123811
Gtz
Kurt

Kurt Krummbein said:
mine is:
cat /sys/devices/soc0/hw_platform
MTP
cat /sys/devices/soc0/soc_id
268
cat /sys/devices/soc0/image_version
10:LRX22G:eng.root.20150808.123811
Gtz
Kurt
Click to expand...
Click to collapse
Fantastic! Here we have an explanation. Your device reports 268 as id which equals to msm8929 and I have a device with id 239 which is msm8939. The kernel only holds a device tree blob (dtb) for the id 239. I thought that the variant were very similar, so last time I used a dtb from the eu release but only for id 239. Attached I have added a dtb for id 268. Please test this rom with that boot image.
Again, just unpack the bootASEU.img and copy it to your device, flash it after installing the lineageos zip.
Please make a backup beforehand and report back, when you have time. Happy trying out.

lightwars said:
Fantastic! Here we have an explanation. Your device reports 268 as id which equals to msm8929 and I have a device with id 239 which is msm8939. The kernel only holds a device tree blob (dtb) for the id 239. I thought that the variant were very similar, so last time I used a dtb from the eu release but only for id 239. Attached I have added a dtb for id 268. Please test this rom with that boot image.
Again, just unpack the bootASEU.img and copy it to your device, flash it after installing the lineageos zip.
Please make a backup beforehand and report back, when you have time. Happy trying out.
Click to expand...
Click to collapse
One step ahead ! Phone is booting with the new boot.img ... but ends with a bootloop.
Highest was one boot with start of the setup-wizard, but after setting language to "Deutsch (Deutschland)" (and several "Bluetooth is not working" messages) it went around again. Couldn't get logs yet ... well see :
Cheers
Kurt

Kurt Krummbein said:
One step ahead ! Phone is booting with the new boot.img ... but ends with a bootloop.
Highest was one boot with start of the setup-wizard, but after setting language to "Deutsch (Deutschland)" (and several "Bluetooth is not working" messages) it went around again. Couldn't get logs yet ... well see :
Cheers
Kurt
Click to expand...
Click to collapse
Yeah! Would be best to build the dtb from source, rather than attaching just the right one to the kernel...
The bluetooth message can be made silent, by the way what build you are using? I think the first build has not the fix for the message. The build.prop should contain this line:
Code:
ro.boot.btmacaddr=00:00:00:00:00:00
and the message should not appear.
I hope there are not any preferences with could only be applied to msm8939 and not to msm8929.

@Kurt Krummbein
Here is my latest build or just grab the boot.img from the attachment. Which has a dtb for msm8929 build from source.
Maybe this will boot without any bootloop.

lightwars said:
@Kurt Krummbein
Here is my latest build or just grab the boot.img from the attachment. Which has a dtb for msm8929 build from source.
Maybe this will boot without any bootloop.
Click to expand...
Click to collapse
For which version is your latest build? the eu?
Thanks
BR Slawo

slawoko said:
For which version is your latest build? the eu?
Thanks
BR Slawo
Click to expand...
Click to collapse
AS and hopefully EU.

Development boot.img for SM-A127F and SM-A125F with the touch and MTP fixed

Here is a few boot.img files (tarred for Odin and zipped) intended to be used together with GSI systems (e.g. LineageOS) which suffer from the non-functional touchscreen after the wake-up and the non-functional MTP (USB file transfer). The boot.img files contain the recompiled stock kernel taken from Samsung Open Source with only a couple of the most necessary fixes. 99.9% unaltered, 100% open-source
All credits for the touchscreen fix go to manteiga25, he's done an amazing job on figuring this all out, still from his solution which includes additional performance tweaks I've taken the absolute bare minimum so that the problem is no longer present. Also huge thanks to Osvaldo Costa for the wonderful bootimgtool.
NOTE: If you did not yet flash any non-stock boot.img or recovery.img you may get the bootloop after flashing of any of these files (except for the orig's). That bootloop is caused by bootloader refusing to boot the VB-unsigned kernel together with the rest of the VB-signed components. The only solution (unfortunately) is the full factory reset, so you'll have to lose your user data; everything else, including the GSI will remain intact, but you'll have to set it up from scratch.
UPDATE 01/09/23: added the version based on A127FXXU7CVL2 (Android 13) version of the kernel.
UPDATE 01/11/23: added the fixed kernels for SM-A125F.
UPDATE 03/16/23: added the version based on A127FXXU5BVF3 (Android 12) version of the kernel.
Files for SM-A127F:
boot_sm-a127f-u4_fixed.zip: A127FXXU4AUK1-based kernel, Ilitek ili9881x fix, MTP fix
boot_sm-a127f-u5_fixed.zip: A127FXXU5BVF3-based (Android 12) kernel, Ilitek ili9881x fix, MTP fix
boot_sm-a127f-u7_fixed.zip: A127FXXU7CVL2-based (Android 13) kernel, Ilitek ili9881x fix, MTP fix
orig_boot_sm-a127-u4.zip: the original unaltered A127FXXU4AUK1 boot.img for undo
orig_boot_sm-a127-u5.zip: the original unaltered A127FXXU5BVF3 boot.img for undo
orig_boot_sm-a127-u7.zip: the original unaltered A127FXXU7CVL2 boot.img for undo
src_sm-a127f_fix.zip: all the altered source files
Files for SM-A125F:
boot_sm-a125f-u2_fixed_v1.zip: A125FXXU2BVB4-based kernel, Ilitek ili9881x fix, MTP fix
boot_sm-a125f-u2_fixed_v2.zip: A125FXXU2BVB4-based kernel, Ilitek ili9881x fix, Novatek nt36525 fix, MTP fix
orig_boot_sm-a125-u2.zip: the original unaltered A125FXXU2BVB3 boot.img for undo
src_sm-a127f-fix_v2.zip: all the altered source files
v1 should be easy on battery, but v2 will probably eat more because it basically disables the power saving features of the touchscreen chip (unfortunately that's the only solution at the kernel side).
If you don't trust me or if you're in desperate need of a more recent kernel, here are the steps how to rebuild it all yourself (for SM-A127F on Debian 11):
Download the kernel source from Samsung Open Source (A127FXXU3AUJ5)
Unpack SM-A127F_RR_Opensource.zip and Kernel.tar.gz inside
Unpack SM-A127F_RR_Opensource_A127FXXU4AUK1.zip into the same dir (overwriting the files)
Unpack the attached source.tar.gz, it contains only the changed files and build.sh facilitating compilation
From root: apt install clang-9 gcc-9-aarch64-linux-gnu
Remove any other versions of clang. Then cd /usr/bin; ln -s clang clang-9; ln -s clang++ clang++-9; ln -s clang-cpp clang-cpp-9
Back in the Kernel dir, run build.sh and wait for the kernel to compile
Download bootimgtool and compile it (just "make")
Download the stock firmware
Extract boot.img from AP_A127FXX[...].tar.md5 (unpack using tar, ignore the .md5) to the root dir of your Kernel
bootimgtool disassemble boot.img
cp Kernel/arch/arm64/boot/Image kernel
bootimgtool create -o boot.img
Flash boot.img as is using Heimdall or pack into .tar and flash using Odin
For SM-A125F you'll need to use the Google's patched Clang and GCC instead, and there is no way around that except for lots and lots of additional include paths for the Mediatek drivers (and even that does not guarentee that it will be compiled successfully).

uluruman said:
Here is the boot.img (tarred for Odin) intended to be used together with GSI systems (e.g. LineageOS). It contains the recompiled stock U4 kernel taken from Samsung Open Source with only a couple of the most necessary fixes, namely the freezing touchscreen and the non-functional MTP. 99.9% unaltered, 100% open-source.
All credits for the touchscreen fix go to manteiga25, he's done an amazing job on figuring this all out, still from his solution which includes additional performance tweaks I've taken the absolute bare minimum so that the problem is no longer present. Also huge thanks to Osvaldo Costa for the wonderful bootimgtool.
If you don't trust me here are the steps how to rebuild it all yourself (on Debian 11):
Download the kernel source from Samsung Open Source (A127FXXU3AUJ5)
Unpack SM-A127F_RR_Opensource.zip and Kernel.tar.gz inside
Unpack SM-A127F_RR_Opensource_A127FXXU4AUK1.zip into the same dir (overwriting the files)
Unpack the attached source.tar.gz, it contains only the changed files and build.sh facilitating compilation
From root: apt install clang-9 gcc-9-aarch64-linux-gnu
Remove any other versions of clang. Then cd /usr/bin; ln -s clang clang-9; ln -s clang++ clang++-9; ln -s clang-cpp clang-cpp-9
Back in the Kernel dir, run build.sh and wait for the kernel to compile
Download bootimgtool and compile it (just "make")
Download the stock firmware
Extract boot.img from AP_A127FXX[...].tar.md5 (unpack using tar, ignore the .md5) to the root dir of your Kernel
bootimgtool disassemble boot.img
cp Kernel/arch/arm64/boot/Image kernel
bootimgtool create -o boot.img
Flash boot.img as is using Heimdall or pack into .tar and flash using Odin
Click to expand...
Click to collapse
Amazing work. Love to see developers still working on this device. Does it work with SM-A125F?

Allehandro said:
Amazing work. Love to see developers still working on this device. Does it work with SM-A125F?
Click to expand...
Click to collapse
You can try, it may work, but most likely will bootloop. SM-A125F is based on a Mediatek SoC, SM-A127F is based on Exynos, which has a different kernel config.

uluruman said:
You can try, it may work, but most likely will bootloop. SM-A125F is based on a Mediatek SoC, SM-A127F is based on Exynos, which has a different kernel config.
Click to expand...
Click to collapse
I don't want to risk it as it is my main device and don't want to have to restore the device later on. Thanks though.

I've finally managed to compile the SM-A125F kernel (A125FXXU2BVB4 - SM-A125F_EUR_RR): somehow it turned out to be MUCH harder than that for SM-A127F, as nearly everything there is designed for only one specific toolchain, plus the non-Samsung s_mtp driver did not compile, so I had to take it from A127F's source. Anyway, I've ported the same fixes and here is the experimental boot.img. As I don't have SM-A125F I cannot test it, so I need someone to test it. Also attached is the original U2 boot.img: in case it does not work you just flash the original.

Amazing bro! Mad respect!!!!
I will soon put this baby to the test and see what's made of!!!
I can flash this using ODIN (PDA) directly over the current LOS GSI right?
Also, do you plan to include this kernel in your gsi building script so that the boot img of the gsi will be this one?
One other issue that I seemed to also have in my phone was the proximity sensor was not working e.g. when I was in call the screen would remain on....

axy_david said:
Amazing bro! Mad respect!!!!
I will soon put this baby to the test and see what's made of!!!
I can flash this using ODIN (PDA) directly over the current LOS GSI right?
Also, do you plan to include this kernel in your gsi building script so that the boot img of the gsi will be this one?
One other issue that I seemed to also have in my phone was the proximity sensor was not working e.g. when I was in call the screen would remain on....
Click to expand...
Click to collapse
Yes, flash using Odin. GSI should not be affected in any way. If anything does wrong I've also attached the original A127FXXU4AUK1 boot.img, so that you could revert the changes.
Currently I'm struggling to make the same fixed boot.img for my second phone, which is SM-A325F, and I cannot: even if I just unpack and repack back the same boot.img using any tool, including the Google's official mkbootimg, it causes the bootloop. So all of this is currently experimental.

uluruman said:
Currently I'm struggling to make the same fixed boot.img for my second phone, which is SM-A325F, and I cannot: even if I just unpack and repack back the same boot.img using any tool, including the Google's official mkbootimg, it causes the bootloop. So all of this is currently experimental.
Click to expand...
Click to collapse
This issue is sorted out: one cannot flash a custom boot.img over the signed stock one and don't do the full factory reset afterwards. Only after the factory reset the system boots with the unsigned boot partition. Interestingly enough, Download allows flashing such an image without any warnings (in contrast to flashing up_param.bin) but the system just refuses to boot.

uluruman said:
This issue is sorted out: one cannot flash a custom boot.img over the signed stock one and don't do the full factory reset afterwards. Only after the factory reset the system boots with the unsigned boot partition. Interestingly enough, Download allows flashing such an image without any warnings (in contrast to flashing up_param.bin) but the system just refuses to boot.
Click to expand...
Click to collapse
is it possible to fix the proximity sensor?

axy_david said:
is it possible to fix the proximity sensor?
Click to expand...
Click to collapse
There is no physical proximity sensor in this phone, but with the latest firmware you can normally use the Phone app. Now it normally reacts on touching the top part of the screen with your ear and blanks the screen. The screen does not blank on approaching the screen but only on touching it.

uluruman said:
Here is the boot.img (tarred for Odin) intended to be used together with GSI systems (e.g. LineageOS). It contains the recompiled stock U4 kernel taken from Samsung Open Source with only a couple of the most necessary fixes, namely the freezing touchscreen and the non-functional MTP. 99.9% unaltered, 100% open-source.
If the fixed boot.img does not work for you for some reason, I've also attached the original U4 boot (taken from the SM-A127F_NPB_A127FXXU4AUK1 firmware) so you could revert the changes.
All credits for the touchscreen fix go to manteiga25, he's done an amazing job on figuring this all out, still from his solution which includes additional performance tweaks I've taken the absolute bare minimum so that the problem is no longer present. Also huge thanks to Osvaldo Costa for the wonderful bootimgtool.
If you don't trust me or if you're in desperate need of a more recent kernel, here are the steps how to rebuild it all yourself (on Debian 11):
Download the kernel source from Samsung Open Source (A127FXXU3AUJ5)
Unpack SM-A127F_RR_Opensource.zip and Kernel.tar.gz inside
Unpack SM-A127F_RR_Opensource_A127FXXU4AUK1.zip into the same dir (overwriting the files)
Unpack the attached source.tar.gz, it contains only the changed files and build.sh facilitating compilation
From root: apt install clang-9 gcc-9-aarch64-linux-gnu
Remove any other versions of clang. Then cd /usr/bin; ln -s clang clang-9; ln -s clang++ clang++-9; ln -s clang-cpp clang-cpp-9
Back in the Kernel dir, run build.sh and wait for the kernel to compile
Download bootimgtool and compile it (just "make")
Download the stock firmware
Extract boot.img from AP_A127FXX[...].tar.md5 (unpack using tar, ignore the .md5) to the root dir of your Kernel
bootimgtool disassemble boot.img
cp Kernel/arch/arm64/boot/Image kernel
bootimgtool create -o boot.img
Flash boot.img as is using Heimdall or pack into .tar and flash using Odin
P.S.: the U5 kernel sources are suspicously segregated between RR (rest of the world), EUR, CIS and CIS-SER (Russia). It's quite interesting what are the differences?
Click to expand...
Click to collapse
Can you make one for A127F/DSN U7? (I don't have linux)

just tested on my phone latest U7 or s7???? nevertheless it bootloops

axy_david said:
just tested on my phone latest U7 or s7???? nevertheless it bootloops
Click to expand...
Click to collapse
it only works for u4 currently.

TheWorldYT said:
Can you make one for A127F/DSN U7? (I don't have linux)
Click to expand...
Click to collapse
I will, hold on.

just tested on my phone latest U7 or s7???? nevertheless it bootloops
TheWorldYT said:
it only works for u4 currently.
Click to expand...
Click to collapse
damn, and I can't downgrade, im using A127FXXS7BVK1 the latest update for europe really

axy_david said:
just tested on my phone latest U7 or s7???? nevertheless it bootloops
damn, and I can't downgrade, im using A127FXXS7BVK1
Click to expand...
Click to collapse
same thing.
also:
uluruman said:
I will, hold on.
Click to expand...
Click to collapse
axy_david said:
just tested on my phone latest U7 or s7???? nevertheless it bootloops
damn, and I can't downgrade, im using A127FXXS7BVK1 the latest update for europe really
Click to expand...
Click to collapse
uluruman said he will create one.

axy_david said:
just tested on my phone latest U7 or s7???? nevertheless it bootloops
damn, and I can't downgrade, im using A127FXXS7BVK1 the latest update for europe really
Click to expand...
Click to collapse
Done! ) See the update in the first post.
I've used the A127FXXU7CVL2 version source but it should work anyway because it's also U7-based (anyway there is no alternative - Samsung provides only that U7-based kernel). The only thing that theoretically can be needed is the factory reset: at least with my SM-A325F that was the case of the weird boot loop - the Verified Boot protection being voided (the warranty void bit being set) caused the bootloader to refuse loading the kernel.

uluruman said:
Done! ) See the update in the first post.
I've used the A127FXXU7CVL2 version source but it should work anyway because it's also U7-based (anyway there is no alternative - Samsung provides only that U7-based kernel). The only thing that theoretically can be needed is the factory reset: at least with my SM-A325F that was the case of the weird boot loop - the Verified Boot protection being voided (the warranty void bit being set) caused the bootloader to refuse loading the kernel.
Click to expand...
Click to collapse
Thank you!

uluruman said:
I've finally managed to compile the SM-A125F kernel (A125FXXU2BVB4 - SM-A125F_EUR_RR): somehow it turned out to be MUCH harder than that for SM-A127F, as nearly everything there is designed for only one specific toolchain, plus the non-Samsung s_mtp driver did not compile, so I had to take it from A127F's source. Anyway, I've ported the same fixes and here is the experimental boot.img. As I don't have SM-A125F I cannot test it, so I need someone to test it. Also attached is the original U2 boot.img: in case it does not work you just flash the original.
Click to expand...
Click to collapse
Can u make flashable zip for fix touch and mtp for a125f cause i think it dndt work after flashing only boot.img in twrp,still i found out that the baseband version is still bv5 instead of bv4 i hope you fix that bro because i want to install gsi

uluruman said:
Here is the boot.img (tarred for Odin) intended to be used together with GSI systems (e.g. LineageOS). It contains the recompiled stock U4 kernel taken from Samsung Open Source with only a couple of the most necessary fixes, namely the freezing touchscreen and the non-functional MTP. 99.9% unaltered, 100% open-source.
If the fixed boot.img does not work for you for some reason, I've also attached the original U4 boot (taken from the SM-A127F_NPB_A127FXXU4AUK1 firmware) so you could revert the changes.
All credits for the touchscreen fix go to manteiga25, he's done an amazing job on figuring this all out, still from his solution which includes additional performance tweaks I've taken the absolute bare minimum so that the problem is no longer present. Also huge thanks to Osvaldo Costa for the wonderful bootimgtool.
UPDATE 01/09/23: added the version based on A127FXXU7CVL2 (Android 13) version of the kernel.
If you don't trust me or if you're in desperate need of a more recent kernel, here are the steps how to rebuild it all yourself (on Debian 11):
Download the kernel source from Samsung Open Source (A127FXXU3AUJ5)
Unpack SM-A127F_RR_Opensource.zip and Kernel.tar.gz inside
Unpack SM-A127F_RR_Opensource_A127FXXU4AUK1.zip into the same dir (overwriting the files)
Unpack the attached source.tar.gz, it contains only the changed files and build.sh facilitating compilation
From root: apt install clang-9 gcc-9-aarch64-linux-gnu
Remove any other versions of clang. Then cd /usr/bin; ln -s clang clang-9; ln -s clang++ clang++-9; ln -s clang-cpp clang-cpp-9
Back in the Kernel dir, run build.sh and wait for the kernel to compile
Download bootimgtool and compile it (just "make")
Download the stock firmware
Extract boot.img from AP_A127FXX[...].tar.md5 (unpack using tar, ignore the .md5) to the root dir of your Kernel
bootimgtool disassemble boot.img
cp Kernel/arch/arm64/boot/Image kernel
bootimgtool create -o boot.img
Flash boot.img as is using Heimdall or pack into .tar and flash using Odin
P.S.: the U5 kernel sources are suspicously segregated between RR (rest of the world), EUR, CIS and CIS-SER (Russia). It's quite interesting what are the differences?
Click to expand...
Click to collapse
Please create working flashable zip file for twrp for a125f cause i dont have pc i cant use odin,thank you