Develop Bugs

developing kernel

Hi guys,
First of all I don't know where thi thread should be. so, mods please spare me.
I have been compiling (Developing) kernel for a week now and I compiled 2 kernels from cm11 source and also from cm10.2 source using NDK toolchain4.6 (as 4.8 gives me some errors) .
I got zImage and also modules.I thought I will make a flashable zip but I don't have any other files and also I don't have source for any rom.so i pulled out boot.img from the AICP release 5.0 RC and packed my zImage in to a boot.img (renamed zImage to boot.img-kernel) and tried to put that boot.img and modules in to AICP zip folder and flash but everytime it gets stuck in LG logo.there could be many reasons for this as i am using a very crude method to put boot.img and modules files in to a rom zip and also it could be the kernel itself.I can't flash it in fastboot mode as my device won't stay in fastboot.
SO if anyone wants to try if this kernel works or not,please flash the provided boot.img in your device fastboot and let me know.If it works then i can go on making changes and adding OC ,governors and all.
BTW you know that normal XDA slogan so i won't repeat.
boot.img

Wat steps did u take as in making the image
Am making a kernel for stock KitKat sphinx

1. Unpacked boot.img (i pulled it from AICP release 5 RC.zip) using the script
2. Unpacked ramdisk.gz in to ramdisk folder
3. deleted boot.img-kernel file and renamed zImage to boot.img-kernel
4. repacked using the script
I used this script

I started looking at some videos to try and make a kernel also can you share a guide

sure.this is the best one i found,
[Tutorial] Building Your First Kernel
before this you need to install some things and you can follow this guide for that
How to Compile AOSPA from Source
follow this guide till installing android SDK then download android ndk and then follow the guide I provided above "building your first kernel" .
one more thing i wasn't able to install oracle jdk6 according to that guide so google it,you will find the installation procedure.

sukesh1090 said:
sure.this is the best one i found,
[Tutorial] Building Your First Kernel
before this you need to install some things and you can follow this guide for that
How to Compile AOSPA from Source
follow this guide till installing android SDK then download android ndk and then follow the guide I provided above "building your first kernel" .
one more thing i wasn't able to install oracle jdk6 according to that guide so google it,you will find the installation procedure.
Click to expand...
Click to collapse
Thanks we need some attention on this device, its still an invincible device, if it was on more carriers it would have gotten the attention of many

I want to prest my respect and thanks for youres work, both. The g pro still are a great device, I don't understand why aren't some quality and quantity of stock Base room's and kernel's! So, I hope we seen some of that from yours!
I don't have skills to help, only I can say... Good luck and keep on!

bountyman334 said:
Wat steps did u take as in making the image
Am making a kernel for stock KitKat sphinx
Click to expand...
Click to collapse
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images

Is it necessary to lokify the boot.img before flashing or will freegee will do it for us??
I don't understand why the stock unmodified CM 10.2 kernel get stuck in LG logo.I don't get any errors while compiling but still it won't boot.

sukesh1090 said:
Is it necessary to lokify the boot.img before flashing or will freegee will do it for us??
I don't understand why the stock unmodified CM 10.2 kernel get stuck in LG logo.I don't get any errors while compiling but still it won't boot.
Click to expand...
Click to collapse
What Recovery you use?

I believe the recoveries provided through FreeGee are already lokified.
Sent from my LG-E980 using XDA Free mobile app

I am using TWRP provided in freegee OG pro. I remember sometimes seeing the log while flashing it says lokifying.... .I think it does the job for us but then why the hell my kernel is not booting.
Atleast If fastboot was working it would have made my life much easier,I didn't have to flash then if it won't work then flash some other kernel,its pain in ........
guys is fastboot working for you??

sukesh1090 said:
I am using TWRP provided in freegee OG pro. I remember sometimes seeing the log while flashing it says lokifying.... .I think it does the job for us but then why the hell my kernel is not booting.
Atleast If fastboot was working it would have made my life much easier,I didn't have to flash then if it won't work then flash some other kernel,its pain in ........
guys is fastboot working for you??
Click to expand...
Click to collapse
Try CWM 6.0.4.4 [emoji15]

Mervingio said:
Try CWM 6.0.4.4 [emoji15]
Click to expand...
Click to collapse
Thought i would share this fount a twrp recovery 2.6.3.0 loki-fied and i made a simple swap and it works for all my flashing (am On Spihnx 1.6) <-- Flash this daily becuz am testing g3 & g flex apps and i dont have to switch over to cwm....
but Note when u wipe data,cache,dalvik u have 2 reboot 2 recovery
https://mega.co.nz/#!hhBHWb4I!NEgT5TIeEgZEvLKMG22sAB3m1i6Uzk3bXB2wElIEO7o

^^
does fastboot work in your recovery??

bountyman334 said:
Thought i would share this fount a twrp recovery 2.6.3.0 loki-fied and i made a simple swap and it works for all my flashing (am On Spihnx 1.6) <-- Flash this daily becuz am testing g3 & g flex apps and i dont have to switch over to cwm....
but Note when u wipe data,cache,dalvik u have 2 reboot 2 recovery
https://mega.co.nz/#!hhBHWb4I!NEgT5TIeEgZEvLKMG22sAB3m1i6Uzk3bXB2wElIEO7o
Click to expand...
Click to collapse
Not sure ladt time i tru use TWRP need back to LG Flash tool

this is legit am using it now between cm11 and sphinx...but i fiqured out that u have to be on 4.1.2 to use twrp tried it with the stock kitkat and it dosent wrk ...so beware dont use stock kitkat at all by my understanding its boot need to be loki fied first

I think the development stopped

dante_67 said:
I think the development stopped
Click to expand...
Click to collapse
Yup for now because I am not in home. next week I will get back to my comp and then I will continue the development .I compiled with both NDK toolchain 4.6 and 4.8 both compile without error but kernel gets stuck in LG logo.so I will try with linaro tool chain,let's see how it goes.

My own impression, of samsung s2 days, linaro is far more superior to ndk

Flashable TWRP v2.8.7.0 for Sony Z3+ E6553 Ivy_Kitakami

Introduction
Disclaimer: While this TWRP has been tested by myself on my own device to flash, wipe and backup, I make no warranties as to it's performance. Use at your own risk.
WARNING: flashable version contains a kernel boot image which will be flashed to your device along with the recovery image.
Click to expand...
Click to collapse
Installation instructions
This recovery image is for the E6553 single SIM Z3+. Do not use it on another model.
This recovery image requires an unlocked bootloader. You will lose some functionality on your phone if you unlock your bootloader
Do your research and make sure you're using the latest version of the relevant tools if you do decide to unlock.
DO NOT enable MyXperia functionality if you've unlocked your bootloader. You will brick your device.
This first download of this recovery image CANNOT be flashed to your phone and must be used in fastboot mode only
The second download is a flashable recovery
Use the first version to flash the second dual-boot.zip version
Unzip the recovery.zip file to extract the recovery.img file to use in fastboot mode
Code:
C:\>adb reboot bootloader
C:\>fastboot boot recovery.img
C:\>adb push dual-boot.zip /sdcard/dual-boot.zip
C:\>adb push dual-boot.zip.md5 /sdcard/dual-boot.zip.md5
Click to expand...
Click to collapse
Now use the TWRP install feature to install dual-boot.zip. Follow the prompts of the Aroma graphical installer.
CAVEAT: this extends the boot time by about 5 - 10 seconds as ramdisk images need to be unpacked and there's a wait on a keypress to determine whether to enter recovery mode. In order to boot into recovery, press power on. When you see the yellow LED come on then press the down volume button once or twice. You will then boot into TWRP.
NOTE: the dual-boot.zip installs a new 28.0.A.8.251 kernel. If you're using the autoroot kernel from Devries you will need to flash SuperSU to re-root your device
This dual boot/recovery works by flashing the recovery image to the FOTAkernel partition. A custom ramdisk image contains the normal boot image. If the down volume keypress is detected, then the recovery ramdisk is automatically extracted from the FOTAKernel partition and flow of control switches to recovery. If no keypress is detected then the normal ramdisk is extracted and normal android boot ensues.
Those of you who installed version 1.0 please download and install this version 1.1 to fix the error with the startup of the trim area daemon
Download
Binary
Fastboot TWRP Recovery Image v2.8.7.0-e6553-1.0 for Z3+ E6553
Flashable TWRP Recovery Image v2.8.7.0-e6553-1.1 for Z3+ E6553 (MD5: 52d4b7d406308dbd457e8b94210b7c87)
Flashable TWRP Recovery Image v2.8.7.0-e6553-1.1 for Z3+ E6553 - MD5
Sources @ github
device_sony_kitakami
device_sony_ivy
Click to expand...
Click to collapse
Changelog
Code:
Current changelog: -- 29 September 2015
[new] v1.1 fix up problem in combined ramdisk preventing trim area daemon from starting correctly
[new] Flashable recovery - 28 September 2015
[new] Fixed various sys/class issues so that CPU temperature and LED / backlight control work correctly
[new] Updated to use 28.0.A.8.251 kernel (as opposed to the AOSP kernel)
[old] Initial release - 10 September 2015
Click to expand...
Click to collapse
Thanks To
The regular contributors to the Z3+ forum, among others @[NUT], @ChrisJ951, @DHGE, @Devries, @zxz0O0, @Venkat Kamesh, @AndroPlus, @Sacktreter who pass on knowledge and who make the forum a lively and cooperative place
Click to expand...
Click to collapse

People who installed version 1.0 of the Flashable TWRP must please update to version 1.1 to correct a bug.

Awesome work.
Glad you were able to get the screen working for it! Boots up fine w/o issue for me

This is fantastic. Is there any way of getting this to work with a locked bootloader?
Sent from my Xperia Z3+

AMoosa said:
This is fantastic. Is there any way of getting this to work with a locked bootloader?
Sent from my Xperia Z3+
Click to expand...
Click to collapse
I'd venture to suggest that it's highly unlikely that locked bootloader recovery could work. The DM_VERITY is almost a guarantor of that. Just search for CONFIG_DM_VERITY or Verity in the Z3+ forums for more info.
Even if an exploit works, the second it modifies the system partition, the kernel panics and refuses to boot. The only way of preventing that is to flash a new kernel or edit the ramdisk to remove the verity key. And the only way to flash a new kernel / edit the ramdisk is to unlock the bootloader.

Thank you first for development... maazing!
I have unlocked the bootloader via Sony and then used an boot.img from Devries to root as root was my primary goal. I have flashbooted as per instructions the TWRP recovery.img that is provided here by the awesome dl12345 .
However the issue is that I am unable to boot to recovery after rebooting from TWRP. In other words the flashboot works and I am able to make a backup and use TWRP well but it doesn't seem to stick.
Am I doing something wrong. Should I have flashed a ROM first from xperfirm, Flashtools, and/or can I flash a kernel without it effecting the recovery. My knowledge is sketchy but I am totally up for testing if I can help.

elladroid said:
Thank you first for development... maazing!
I have unlocked the bootloader via Sony and then used an boot.img from Devries to root as root was my primary goal. I have flashbooted as per instructions the TWRP recovery.img that is provided here by the awesome dl12345 .
However the issue is that I am unable to boot to recovery after rebooting from TWRP. In other words the flashboot works and I am able to make a backup and use TWRP well but it doesn't seem to stick.
Am I doing something wrong. Should I have flashed a ROM first from xperfirm, Flashtools, and/or can I flash a kernel without it effecting the recovery. My knowledge is sketchy but I am totally up for testing if I can help.
Click to expand...
Click to collapse
This is correct behaviour. You're not actually flashing the recovery image, just temporarily booting a recovery kernel and associated ramdisk. Sony Xperia devices don't have a recovery partition, or more accurately, they don't have a bootloader than can check and load a boot image from a recovery partition.
Technically it's possible to make the boot image check for a ramdisk on another partition and use this instead of the normal ramdisk, but this is step two. Sony should be releasing an open recovery bootloader fairly soon for the Z3+ which will allow this recovery image to be flashed. It's already been released for other devices.
Until Sony releases open recovery for Z3+ or I spend the time trying to implement a feature that probably only has days or weeks of utility (until Sony releases the open recovery for Z3+) , you're stuck with a TWRP that you need to launch every time in fastboot mode.

On the first screen immediately after the TWRP logo comes up, the battery is always being reported at being 50%. Sometimes the correct number is displayed when in the flashing screen. Otherwise works great!
Also, link to Sony Z3+ windows drivers
How to install unsigned drivers in Windows 8.1/10 with secure boot

elladroid said:
Thank you first for development... maazing!
I have unlocked the bootloader via Sony and then used an boot.img from Devries to root as root was my primary goal. I have flashbooted as per instructions the TWRP recovery.img that is provided here by the awesome dl12345 .
However the issue is that I am unable to boot to recovery after rebooting from TWRP. In other words the flashboot works and I am able to make a backup and use TWRP well but it doesn't seem to stick.
Am I doing something wrong. Should I have flashed a ROM first from xperfirm, Flashtools, and/or can I flash a kernel without it effecting the recovery. My knowledge is sketchy but I am totally up for testing if I can help.
Click to expand...
Click to collapse
New version now flashable so that you can boot into recovery...read top post carefully before using.

serrin85 said:
On the first screen immediately after the TWRP logo comes up, the battery is always being reported at being 50%. Sometimes the correct number is displayed when in the flashing screen. Otherwise works great!
Also, link to Sony Z3+ windows drivers
How to install unsigned drivers in Windows 8.1/10 with secure boot
Click to expand...
Click to collapse
Fixed in latest version

http://www.kz3.eu:18998/dual-boot.zip link gives 404 ..

deecept said:
http://www.kz3.eu:18998/dual-boot.zip link gives 404 ..
Click to expand...
Click to collapse
Yes, I've temporarily disabled the link while I resolve a problem relating to the trim area daemon not starting up due to some peculiarity of the dual boot ramdisk. I'll reinstate it as soon as I fix the problem.

dl12345 said:
Yes, I've temporarily disabled the link while I resolve a problem relating to the trim area daemon not starting up due to some peculiarity of the dual boot ramdisk. I'll reinstate it as soon as I fix the problem.
Click to expand...
Click to collapse
Oh, ok, sweet! Looking to flash this to my Z3+. More than happy to test if needed =) Great work on these!!

deecept said:
Oh, ok, sweet! Looking to flash this to my Z3+. More than happy to test if needed =) Great work on these!!
Click to expand...
Click to collapse
Download back online and problem fixed
Those who downloaded the 1.0 please download this 1.1 version and install to correct the problem with trim area daemon startup. Thanks

dl12345 said:
Download back online and problem fixed
Those who downloaded the 1.0 please download this 1.1 version and install to correct the problem with trim area daemon startup. Thanks
Click to expand...
Click to collapse
HI dl12345,
this recovery support Dual model? E6533

hi.question...i get remote: dtb not found error when trying to boot the recovery..any ideas?

didnt get a thing... how do i install?

please, release TWRP for 6533 too
we need custom recovery so bad

Dathrex said:
please, release TWRP for 6533 too
we need custom recovery so bad
Click to expand...
Click to collapse
Pleaseee ????

Brother, please, help us with twrp to E6533, please.
Enviado de meu E6533 usando Tapatalk

Custom kernel Z3+ E6553 - Nuke Verity / Sony RIC and allow SELinux permissive

Introduction
The stock Sony kernels use SONY RIC, SELinux and CONFIG_DM_VERITY that together make it exceptionally hard to root. With the stock kernel, it's impossible to run a modified ROM of any form (incorporating changes to the system partition). Attempting to boot with the stock kernel off a modified system partition results in a kernel stop or panic, manifested either by getting stuck on the Sony screen or a bootloop.
This kernel removes the Sony RIC and CONFIG_DM_VERITY and sets boot and runtime parameters that allow SELinux to be disabled or to be set into permissive mode. Once this kernel is flashed, you can download SuperSU flashable zip and flash it to your phone using the TWRP recovery image I posted in this forum in order to get root on your stock ROM.
This kernel contains no source patches. It's a completely stock kernel from the Sony github repository.
Click to expand...
Click to collapse
Features
SELinux configurable at boot and runtime
Sony RIC disabled
CONFIG_DM_VERITY disabled
Click to expand...
Click to collapse
Installation instructions
This boot image requires an unlocked bootloader. You will lose some functionality on your phone if you unlock your bootloader
Do your research and make sure you're using the latest version of the relevant tools if you do decide to unlock.
Unzip the boot.zip file to extract the boot.img file
Code:
C:\>adb reboot bootloader
C:\>fastboot flash boot boot.img
C:\>fastboot boot recovery.img
C:\>adb push UPDATE-SuperSU-v2.46.zip /sdcard/supersu.zip
Then switch to the TWRP interface, go to the Install menu and flash /sdcard/supersu.zip. Reboot and you're rooted. You can then modify your system partition as you please.
Click to expand...
Click to collapse
NOTE: if you install Xposed you MUST wipe cache/dalvik after installation otherwise you will get an error message telling you that you are running out of storage space and any apps you install with Play store will fail the installation with a 504 error. This is NOT related to the kernel, but is caused by failing to wipe cache after installing Xposed.
Download
Binary
28.0.A.8.251 custom kernel for Z3+ E6553
TWRP Recovery Image V0.1 for Z3+ E6553
Sources @ github
Kernel config
Sony kernel-copyleft repository
Click to expand...
Click to collapse
Changelog
Code:
[B]Changelog[/B]
[new] 12 September 2015- Update to 28.0.A.8.251
[old] 10 September 2015 - Initial release
Thanks To
Code:
[url="http://forum.xda-developers.com/member.php?u=631273"]@Chainfire[/url]. What would we do without SuperSU.....
Click to expand...
Click to collapse

Awesome work, works without any issues.

I must be being really stupid....
Unable to boot into recovery without reflashing recovery.img. I must be missing something!
Otherwise no other issues to speak of. Amazing Thanks!

elladroid said:
I must be being really stupid....
Unable to boot into recovery without reflashing recovery.img. I must be missing something!
Otherwise no other issues to speak of. Amazing Thanks!
Click to expand...
Click to collapse
"Until Sony releases an open bootloader you need to use this image via fastboot boot mode."

really 28.0.A.8.251?
@dl12345
searching for 28.0.A on GitHub gave me:
28.0.A.7.xxx Updated 2 months ago by jerpelea
28.0.A.6.xxx Updated 3 months ago by jerpelea
28.0.A.4.xxx Updated 4 months ago by jerpelea
Did you try the source posted on SONY Developer?
http://developer.sonymobile.com/dow...rchives/open-source-archive-for-28-0-a-8-251/
Does your boot.img work as a replacement for the boot.img flashed with 28.0.A.8.251 FTF?
I ask because I failed booting a boot image compiled from the SONY Developer source and an older kernel from 28.0A.7.24/31 as replacement for the image in the latest 8.251 FTF for my SGP712/karin_windy

DHGE said:
@dl12345
searching for 28.0.A on GitHub gave me:
28.0.A.7.xxx Updated 2 months ago by jerpelea
28.0.A.6.xxx Updated 3 months ago by jerpelea
28.0.A.4.xxx Updated 4 months ago by jerpelea
Did you try the source posted on SONY Developer?
http://developer.sonymobile.com/dow...rchives/open-source-archive-for-28-0-a-8-251/
Does your boot.img work as a replacement for the boot.img flashed with 28.0.A.8.251 FTF?
I ask because I failed booting a boot image compiled from the SONY Developer source and an older kernel from 28.0A.7.24/31 as replacement for the image in the latest 8.251 FTF for my SGP712/karin_windy
Click to expand...
Click to collapse
Correct. The sources on github are old. I dowloaded the archive from the Sony website and compiled it. Yes the boot.img I compiled works perfectly as a replacement. I'm currently running it on my phone.

How to modify system partition
Hi all,
Nob question but need help urgently. After installing the kernel I'm now getting storage space almost full and error 504 due I think to some modifications to the kernel to get root. I'm aware OP did say to modify system partition but don't have a clue how to do so in order to get storage space back and also install apps. Urgent help needed pls.
Cheers and thanks for your assistance.

yawo76 said:
Hi all,
Nob question but need help urgently. After installing the kernel I'm now getting storage space almost full and error 504 due I think to some modifications to the kernel to get root. I'm aware OP did say to modify system partition but don't have a clue how to do so in order to get storage space back and also install apps. Urgent help needed pls.
Cheers and thanks for your assistance.
Click to expand...
Click to collapse
The kernel makes no modifications to the system partition and is unrooted. You need to flash SuperSU to get root.
This error you're getting is caused by the Xposed framework. You've installed the Xposed framework but you forgot to do a wipe dalvik and cache after installing. This is exactly what happens when you forget to wipe cache after installing xposed.
You can try to use the xposed uninstaller which may fix it. If not, you need to do a full wipe and reflash a ROM.

dl12345 said:
The kernel makes no modifications to the system partition and is unrooted. You need to flash SuperSU to get root.
This error you're getting is caused by the Xposed framework. You've installed the Xposed framework but you forgot to do a wipe dalvik and cache after installing. This is exactly what happens when you forget to wipe cache after installing xposed.
You can try to use the xposed uninstaller which may fix it. If not, you need to do a full wipe and reflash a ROM.
Click to expand...
Click to collapse
Thanks very much. It's true I installed Xposed Framework and didn't wipe cache. I have already reinstalled the Rom so will remember this time not to repeat the same mistake.

dl12345 said:
Introduction
NOTE: if you install Xposed you MUST wipe cache/dalvik after installation otherwise you will get an error message telling you that you are running out of storage space and any apps you install with Play store will fail the installation with a 504 error. This is NOT related to the kernel, but is caused by failing to wipe cache after installing Xposed.
Download
[B
Click to expand...
Click to collapse
I'm on .251 (modified system partition) without XPOSED installed. Using the kernel just causes boot loops (Sony Logo then 3 red flashes from the LED) the same way the stock kernel does. Is there something special I need to get SONY RIC / Verity to not run at boot?

This looks like a bad flash. Can you fastboot this kernel?

dl12345 said:
This looks like a bad flash. Can you fastboot this kernel?
Click to expand...
Click to collapse
No luck doing fastboot boot, or fastboot flash boot (both have the same issue of red led 3x then rebooting)
I re-downloaded it and the md5sum matched between the downloads:
768eac3ba2ebcbdaf67e12d8bd11450b /home/chris/Downloads/boot-251.img
768eac3ba2ebcbdaf67e12d8bd11450b /home/chris/Downloads/boot-251.img (2)
EDIT:
Also just in case it matters, the exact build I'm on is
28.0.A.8.251
Edit2: Went back to complete stock from FTF flash and the kernel boots. Need to modify system partition and recheck
Edit3: Flashes SuperSU.zip and it is booting with SU installed. Unsure why my old rom was incompatible with it

ChrisJ951 said:
No luck doing fastboot boot, or fastboot flash boot (both have the same issue of red led 3x then rebooting)
I re-downloaded it and the md5sum matched between the downloads:
768eac3ba2ebcbdaf67e12d8bd11450b /home/chris/Downloads/boot-251.img
768eac3ba2ebcbdaf67e12d8bd11450b /home/chris/Downloads/boot-251.img (2)
EDIT:
Also just in case it matters, the exact build I'm on is
28.0.A.8.251
Edit2: Went back to complete stock from FTF flash and the kernel boots. Need to modify system partition and recheck
Edit3: Flashes SuperSU.zip and it is booting with SU installed. Unsure why my old rom was incompatible with it
Click to expand...
Click to collapse
Me neither - this bootimage has very few modifications: only CONFIG_DM_VERITY and RIC removed, some options for runtime control of SELinux added and the verity keys removed from the ramdisk. It boots fine on a stock 251 ROM for me. The kernel source is .251 source too...
I have noticed that I occasionally get bad flashes and odd behaviour when flashing ROMs (with everything from fastboot to flashtool to TWRP). I think the platform itself isn't totally stable and bug free. Usually I fix it by just wiping and reflashing

Hi @dl12345, can you make the same kernel for Z3 (D6603) or at least point me in direction to know what I need to change by compiling own kernel from sources? Or modifying the original ramdisk..
The issue is that the new Concept M firmware from Sony uses the same security features. Guys (@Gustavo RD78) made successfully kernel for previous Concept L (5.1.1) based firmware, however the same approach seems to fail in case of Marshmallow. Your help will be very appreciated.
EDIT - removed full OP quoted by mistake.

ondrejvaroscak said:
Hi, can you make the same kernel for Z3 (D6603) or at least point me in direction to know what I need to change by compiling own kernel from sources? Or modifying the original ramdisk..
The issue is that the new Concept M firmware from Sony uses the same security features. Guys (@Gustavo RD78) made successfully kernel for previous Concept L (5.1.1) based firmware, however the same approach seems to fail in case of Marshmallow. Your help will be very appreciated.
Click to expand...
Click to collapse
You need kernel source (Sony won't upload it since it's closed beta test).
Also do not quote full OP.
[UPDATE]
AOSP and copyleft source are different things. You need kernel source for concept rom's kernel, and it won't be published so it's impossible to build custom kernel for concept rom.

AndroPlus said:
You need kernel source (Sony won't upload it since it's closed beta test).
Also do not quote full OP.
Click to expand...
Click to collapse
Do I get it right, that I can't justo compile kernel for use with this firmware from AOSP / Sony Copy-left sources?

[kernel][E6533][Z3+ dual][32.2.A.0.224](RIC disable, TWRP, root,dm-verity)

Hello guys.
Today i will post a kernel that i (just run the wizard to) created for Z3+ dual variant version 32.2.A.0.224. My simple contribution!
This kernel contents:
-RIC disable
-TWRP
-root
-dm-verity
How to install it:
Run this command at command prompt,
fastboot flash boot boot.img
Or.....
Use the Flashtools in a fastboot mode, then choose the Flash option by DoomLord.
Please, Don't thanks me. All the hard work was performed by Mr. Tobias Waldvogel in this thread:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
So, if you like this kernel, please pay a coffe for this guy!
Ps. I already tested on my Z3+ and everything it's okay, so i will not responsable about any brinks or damage in use this kernel!
Ps2: DON'T use this kernel on single model. I don't know whats happens!:silly:

Hello，i've already flashed your boot.img. then i try to flash SuperSu2.6.5.zip. Everything is just fine.
But when i enter SuperSu , the app said that i am in system-less mode.
another app can't detected root mode also.
is there anything wrong with me?
it's dual Z3+
Thanks a lot!

youngcube said:
Hello，i've already flashed your boot.img. then i try to flash SuperSu2.6.5.zip. Everything is just fine.
But when i enter SuperSu , the app said that i am in system-less mode.
another app can't detected root mode also.
is there anything wrong with me?
it's dual Z3+
Thanks a lot!
Click to expand...
Click to collapse
no need to flash superSU i think, it's already included in the kernel.

zemetal said:
no need to flash superSU i think, it's already included in the kernel.
Click to expand...
Click to collapse
Sorry guys, i have the same problem here. After a few minutes i discorvery that i used an 'update' (pretty old) superSu zip.
So, i went to the recovery and flash the supersu2.66.zip. After this all programs detected root nomally.
Sorry for inconvenience.

bruno$0 said:
Sorry guys, i have the same problem here. After a few minutes i discorvery that i used an 'update' (pretty old) superSu zip.
So, i went to the recovery and flash the supersu2.66.zip. After this all programs detected root nomally.
Sorry for inconvenience.
Click to expand...
Click to collapse
Working wonderful with SuperSU 2.68 I have a doubt do you have a DRM Restore that works with this Android Version?

Hello, sorry for this noob question. If I flash this to my already rooted Z3+ dual, would it delete all my files and stuff here? Thanks

[/COLOR]
creepyvillager said:
Hello, sorry for this noob question. If I flash this to my already rooted Z3+ dual, would it delete all my files and stuff here? Thanks
Click to expand...
Click to collapse
No flashing a kernel doesn't wipe anything, if you're having a dilemma then take a backup of everything like apps, contacts etc using titanium backup, copy the backup folder to your external memory or computer then flash.
Hope it helps.
P. S ONLY INSTALLING A RECOVERY WIPES EVERYTHING.
---------- Post added at 09:41 AM ---------- Previous post was at 09:25 AM ----------
bruno$0 said:
Hello guys.
Today i will post a kernel that i (just run the wizard to) created for Z3+ dual variant version 32.2.A.0.224. My simple contribution!
This kernel contents:
-RIC disable
-TWRP
-root
-dm-verity
How to install it:
Run this command at command prompt,
fastboot flash boot boot.img
Or.....
Use the Flashtools in a fastboot mode, then choose the Flash option by DoomLord.
Please, Don't thanks me. All the hard work was performed by Mr. Tobias Waldvogel in this thread:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
So, if you like this kernel, please pay a coffe for this guy!
Ps. I already tested on my Z3+ and everything it's okay, so i will not responsable about any brinks or damage in use this kernel!
Ps2: DON'T use this kernel on single model. I don't know whats happens!:silly:
Click to expand...
Click to collapse
Can you tell me how long it took for the first boot?
Cause mine is stuck at 'Starting Applications' for about 8 minutes.
Edit : Couldn't wait it took almost 20mins with no progress so shut it down using power + volume up key and went into recovery wiped dalvik/cache and installed supersu 2.66 and again wiped then rebooted. Now it's showing optimising apps. The only problem is it's not charging. Usually at this stage when i connect my charger the charger led starts glowing but now nothing. Any ideas?

njaya95 said:
Can you tell me how long it took for the first boot?
Cause mine is stuck at 'Starting Applications' for about 8 minutes.
Edit : Couldn't wait it took almost 20mins with no progress so shut it down using power + volume up key and went into recovery wiped dalvik/cache and installed supersu 2.66 and again wiped then rebooted. Now it's showing optimising apps. The only problem is it's not charging. Usually at this stage when i connect my charger the charger led starts glowing but now nothing. Any ideas?
Click to expand...
Click to collapse
Yeah, this also happens to my device when I flashed the kernel.
Edit: It just stuck at the boot screen with blinking red LED notification.

creepyvillager said:
Yeah, this also happens to my device when I flashed the kernel.
Edit: It just stuck at the boot screen with blinking red LED notification.
Click to expand...
Click to collapse
I just found out to use this kernel i should have .244 firmware i bet you're at .185 so update it to .244 then try this kernel. I'm just downloading the firmware now using Xperifirm(https://www.google.com/url?sa=t&rct...9Q4Ht-00R24lisYcw&sig2=ac8ImW1ZY7AvFSZpG9I9mA) and i'll post what i did to the phone after the update.

zemetal said:
no need to flash superSU i think, it's already included in the kernel.
Click to expand...
Click to collapse
It's not, need to flash SuperSU I flashed 2.66 Beta

bruno$0 said:
Hello guys.
Today i will post a kernel that i (just run the wizard to) created for Z3+ dual variant version 32.2.A.0.224. My simple contribution!
This kernel contents:
-RIC disable
-TWRP
-root
-dm-verity
How to install it:
Run this command at command prompt,
fastboot flash boot boot.img
Or.....
Use the Flashtools in a fastboot mode, then choose the Flash option by DoomLord.
Please, Don't thanks me. All the hard work was performed by Mr. Tobias Waldvogel in this thread:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
So, if you like this kernel, please pay a coffe for this guy!
Ps. I already tested on my Z3+ and everything it's okay, so i will not responsable about any brinks or damage in use this kernel!
Ps2: DON'T use this kernel on single model. I don't know whats happens!:silly:
Click to expand...
Click to collapse
Hey can you help me, how to make this kernel SELinux status permissive.

njaya95 said:
Hey can you help me, how to make this kernel SELinux status permissive.
Click to expand...
Click to collapse
I don't know. I just run the script to create the image. Sorry. in a near future when Sony release the MM for M4 dual and share the source code i will try to create a custom kernel from benning for my other device.

bruno$0 said:
I don't know. I just run the script to create the image. Sorry. in a near future when Sony release the MM for M4 dual and share the source code i will try to create a custom kernel from benning for my other device.
Click to expand...
Click to collapse
Okay ?

Running Lollipop 5.0.1 and when i flash the kernel i get not orange/yelllow LED. How do i go into recovery?
Also got no super su app.
I meant to flash it with "fastboot flash recovery boot.img" from Android/android-sdk/platform-tools. Correct?

SugnaB said:
Running Lollipop 5.0.1 and when i flash the kernel i get not orange/yelllow LED. How do i go into recovery?
Also got no super su app.
I meant to flash it with "fastboot flash recovery boot.img" from Android/android-sdk/platform-tools. Correct?
Click to expand...
Click to collapse
It's for 6.0.1 so don't flash it for 5.0.1, update the firmware then flash it cause Sony would have updated somethings in the kernel which won't work with old firmwares. The reason for boot working is maybe because of the phone rebooting from fastboot mode.
Hope it helped. [emoji4]
Sent from my E6533 using XDA-Developers mobile app

Did it need a Unlocked Boot-loader device?

sani007 said:
Did it need a Unlocked Boot-loader device?
Click to expand...
Click to collapse
offcourse.

Sorry for the noob question but I need to know the prerequisites,
Can I flash the Kernel right after flashing stock file OR....
Do I need to first unlock my bootloader
Do I need to have backed up my TA partition

hi there, i wanna update form .185 to .224. is it possible to update without wipe the data? and if it can, if i wanna root it, i just flash this kernel after fw upgrade, then flash supersu via twrp, am i right? thanks

If Xperia Z3+ Dual can't be bootloader unlocked, what's the point in this kernel?!

[Metro][Stock] SOFIAP-T QPRS30.80.64.6.2

100% Stock ROM for the Metro by T-Mobile Moto G Stylus
Requirements:
ADB & Fastboot from here:
https://developer.android.com/studio/releases/platform-tools
ADB & Fastboot set into your OS environment
(This allows adb to be used in any folder)
Instructions here:
https://wiki.lineageos.org/adb_fastboot_guide.html#installing-adb-and-fastboot
7-Zip to extract the .7z file:
https://www.7-zip.org/
Download:
QPRS30.80.64.6.2
Older Downloads:
QPRS30.80.64.6
QPRS30.80.64.3
Flashing Instructions:
1. Extract the zip using 7-Zip
2. Boot into Fastboot
3. Run the flash-all.bat this should automatically start flashing all the partitions
This will wipe everything. If you want to keep your data, before running open the .bat file with a text editor and remove -w from
Code:
fastboot -w reboot
​
(If on another platform than Windows you'll need to change the .bat file to your OS)
Looking for the Retail variant Stock ROM?
See Here:
https://forum.xda-developers.com/mo...t/stock-rom-motorola-g-stylus-retail-t4104451

QPRS30.80.64.6
https://mega.nz/file/nQkRHByR#md9YeMeAS4Vp6_lhL3pm9Bbqx1JrCeMHW8Lbkzr1RQo

cbc0201 said:
QPRS30.80.64.6
https://mega.nz/file/nQkRHByR#md9YeMeAS4Vp6_lhL3pm9Bbqx1JrCeMHW8Lbkzr1RQo
Click to expand...
Click to collapse
Thanks for the download. I added to the OP with the flash-all.bat

DMedina559 said:
Thanks for the download. I added to the OP with the flash-all.bat
Click to expand...
Click to collapse
Okay so I have a question based on my observation maybe stupid may not be I don't care
Q: how do I identify if my phone is the RETUS or the SOFIAP-T?
Q: Sorry this is the observational question,the build number nomenclature in my phone does not have an s at the end of the QPR but in this forum it does but when you download the file it does not. Or does that not matter?
---------- Post added at 03:13 AM ---------- Previous post was at 03:09 AM ----------
LinuxAndroidAlwys said:
Okay so I have a question based on my observation maybe stupid may not be I don't care
Q: how do I identify if my phone is the RETUS or the SOFIAP-T?
Q: Sorry this is the observational question,the build number nomenclature in my phone does not have an s at the end of the QPR but in this forum it does but when you download the file it does not. Or does that not matter?
Click to expand...
Click to collapse
I have QPR30.80.64.6 model XT2043-4

LinuxAndroidAlwys said:
Okay so I have a question based on my observation maybe stupid may not be I don't care
Q: how do I identify if my phone is the RETUS or the SOFIAP-T?
Q: Sorry this is the observational question,the build number nomenclature in my phone does not have an s at the end of the QPR but in this forum it does but when you download the file it does not. Or does that not matter?
---------- Post added at 03:13 AM ---------- Previous post was at 03:09 AM ----------
I have QPR30.80.64.6 model XT2043-4
Click to expand...
Click to collapse
You should be able to tell in the about phone menu in the settings. And the S might be a typo I'm not sure I'll have to check

DMedina559 said:
You should be able to tell in the about phone menu in the settings. And the S might be a typo I'm not sure I'll have to check
Click to expand...
Click to collapse
I figured it out but I'm still confused about the s

LinuxAndroidAlwys said:
I figured it out but I'm still confused about the s
Click to expand...
Click to collapse
The s is just a typo on my end. I'll fix asap

Not sure If I'm in the rightr thread or not but need serious help !!! I had twrp on my phone was trying to reboot system and hit a slot phone went black and will not boot into fastboot turn on, nothing! It is as dead as a dorrnail ie hard bricked . I have loaded all the drivers for phone and qualcomm. Computer only recognizes phone as Qualcomm 9008 mode not bulk mode. Anyone know how to restore phone at least to be able to get into fadtboot? Anyone help would be very much appreciated this is my daily driver and I am screwed without it.

worked great

QPR30.80_64_6_2
https://mega.nz/file/2UMGDb7B#4OZmO_DMUXiJnSkuyf4Y1w3LHVxoXM-P7umpRUWqaAQ

LinuxAndroid4evr said:
Not sure If I'm in the rightr thread or not but need serious help !!! I had twrp on my phone was trying to reboot system and hit a slot phone went black and will not boot into fastboot turn on, nothing! It is as dead as a dorrnail ie hard bricked . I have loaded all the drivers for phone and qualcomm. Computer only recognizes phone as Qualcomm 9008 mode not bulk mode. Anyone know how to restore phone at least to be able to get into fadtboot? Anyone help would be very much appreciated this is my daily driver and I am screwed without it.
Click to expand...
Click to collapse
i did the same thing, booting into slot b got me into the device normally

cbc0201 said:
QPR30.80_64_6_2
https://mega.nz/file/2UMGDb7B#4OZmO_DMUXiJnSkuyf4Y1w3LHVxoXM-P7umpRUWqaAQ
Click to expand...
Click to collapse
Hey man this is my current version as well, but it doesnt have the flashall bat file, do you know if i could just use one from the links in the OP? i am new to flashing roms in this manner and i dont really know how it works

Updated OP with build QPRS30.80.64.6.2

CorporalCactus said:
Hey man this is my current version as well, but it doesnt have the flashall bat file, do you know if i could just use one from the links in the OP? i am new to flashing roms in this manner and i dont really know how it works
Click to expand...
Click to collapse
Yeah using the old flash-all.bat file works with newer builds, just put all the flahsing files in /Recovery-Files/ with the flash-all.bat outisde that folder

Is any way to completely delete Metro PCS bloatware? I have rooted phone. No success to delete bloatware. Can I replace Metro PCS ROM with retail ROM? Is that possible? Any ideas? Thank you

Hello please I used the Moto g stylus as well, using MetroPCS with QPRS30.80-64-6-2, I want to know if this rom is unlocked , will it remove the sim lock on my device as the remote unlock fails. Thanks

Hi new guy here. Got couple moto g stylus (2020 pro). Mine Ive tried out arrow, havoc cr stag, bliss and resurrection. My wife's exact same phone she decided to have me install resurrection remix and magisk root it. ADB installed until last step which was fastboot -w. Had error about not auto formatting RAW format. I managed to fix that but still boot looped or twrp 35. Sofia will load but can't install any rom from zip. Stag logo bootlooeded.. hard to even explain.. damn. Anyway
Any suggestions?

Where is the flash-all.bat ?

MotoLindvall said:
Hi new guy here. Got couple moto g stylus (2020 pro). Mine Ive tried out arrow, havoc cr stag, bliss and resurrection. My wife's exact same phone she decided to have me install resurrection remix and magisk root it. ADB installed until last step which was fastboot -w. Had error about not auto formatting RAW format. I managed to fix that but still boot looped or twrp 35. Sofia will load but can't install any rom from zip. Stag logo bootlooeded.. hard to even explain.. damn. Anyway
Any suggestions?
Click to expand...
Click to collapse
If you still need to figure out the crazy flashing procedure for our device...best answer is make sure you are on STOCK Android 10...if you have updated to Android 11 you will not be able to flash custom ROMs or have a fully functional TWRP recovery...and Magisk root is not good with A11..You can flash GSI on Android 11 Stock firmware or use the DSU loader to install the Beta of Android 12...and the GSI situation is 50/50 if it will boot or not....what I do is flash the A10 stock final upload from the lionnet archive using the ever so awesome Moto flash tool...the tool does everything...and fixed your Beta partition so you can flash custom ROMs...once you finish with the tool reboot into STOCK recovery and format data..reboot to Stock Android 10 once you get to the Android setup welcome screen reboot to boot loader and flash TWRP recovery to both recovery slots...reboot to recovery...and format data...then reboot to fastbootd...your first custom install is recommended to be flashed from fastbootd on both slots...now when you finish reboot to Stock 10 recovery and format data...boot the rom first before and mods installed...then once you boot the rom you can flash mods with TWRP..get in a habit of after new system install format data in stock 10 recovery...now any custom ROM flash at this point forward do from TWRP and before flashing format data in TWRP after format again in stock 10 recovery...gapps install after first boot...Magisk install only after you fully go through the flashing procedure and setup the Rom make sure to enable dev options or it won't boot..and again flash Magisk after full setup and reboot..this procedure works...I keep a copy of stock recovery and TWRP recovery on my sdcard and platform tools on pc...you can flash stock 10 and TWRP in mobile if your rooted with any root kernel mgr so that way you don't have to use pc...the moto flash tool is the best way to setup the phone for custom ROMs.....