G2 Mini D620 kernel compilation problem - LG G2 Mini

Hello, I'm trying to compile my own kernel from sources for this piece of hardware, everything went well and I completed the whole process, but with my kernel device doesn't boot up and stuck on boot screen at bootloader stage (fastboot mode). I'm using CNexus Boot.img tools from here. To obtain
PAGE SIZE: 2048
BASE ADDRESS: 0x00000000
RAMDISK ADDRESS: 0x01000000
I've used arm-eabi-4.6, stock and working kernel with command ./boot_info boot_327680.bin so I think, these parameters are ok.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Whole ramdisk image is also taken from stock kernel with command ./split_boot boot_327680.bin. Configuration used ".config" comes from stock kernel too. Even after compilation of pure split image, device won't boot...
This piece of code I'm using to compile kernel image for example:
Code:
./mkbootimg --kernel boot_327680.bin-kernel --ramdisk boot_327680.bin-ramdisk.cpio.gz --cmdline "console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 user_debug=31 msm_rtb.filter=0x37 androidboot.hardware=g2m" --base 0x00000000 --pagesize 2048 --ramdiskaddr 0x01000000 -o test_stock.img
It looks like in newly compiled kernel at the end of file a lot of code is missing.
You may open following files with hex or text editor to see what I mean.
Stock kernel:
https://www.dropbox.com/s/0jidfk7jcsopvy7/stock_boot.bin?dl=0
Compiled one:
https://www.dropbox.com/s/ceui3620ief7m5j/test_stock.img?dl=0
Any suggestions?

Really? No one can help me?

What about dt image in boot image?

Zaaap72 said:
What about dt image in boot image?
Click to expand...
Click to collapse
Thank you for that, didn't really know about that, now I have to find out how to build dt.img or extract it from stock image.
Wysłane z mojego LG-D620 przy użyciu Tapatalka

I managed to build working kernel but something is still wrong with graphics, there is no image, display stays black. I can hear that system boots up and touch is working, adb is working too.
EDIT: Attached here kernel with broken video and logcat of it.
If someone want to test it and help me to find out the problem, do nandroid boot backup first!

Guys for CM we need CAF kernel. Kernel from me is CAF and need couple of fix but system is boot and working.

Lukiqq said:
I managed to build working kernel but something is still wrong with graphics, there is no image, display stays black. I can hear that system boots up and touch is working, adb is working too.
EDIT: Attached here kernel with broken video and logcat of it.
If someone want to test it and help me to find out the problem, do nandroid boot backup first!
Click to expand...
Click to collapse
Which sources did you use?

Garcia98 said:
Which sources did you use?
Click to expand...
Click to collapse
Pure stock sources from LG site.

Lukiqq said:
I managed to build working kernel but something is still wrong with graphics, there is no image, display stays black. I can hear that system boots up and touch is working, adb is working too.
EDIT: Attached here kernel with broken video and logcat of it.
If someone want to test it and help me to find out the problem, do nandroid boot backup first!
Click to expand...
Click to collapse
Can You post a logcat file with that command : logcat *:E

Lukiqq said:
Pure stock sources from LG site.
Click to expand...
Click to collapse
And are you using stock ROM?

Garcia98 said:
And are you using stock ROM?
Click to expand...
Click to collapse
Yes, stock odexed ROM.
PS. Repacked with this method and then compiled stock boot.img is working ok, so I assume something is wrong with zImage instead of ramdisk.

Lukiqq said:
Yes, stock odexed ROM.
PS. Repacked with this method and then compiled stock boot.img is working ok, so I assume something is wrong with zImage instead of ramdisk.
Click to expand...
Click to collapse
Which defconfig did you use?

Garcia98 said:
Which defconfig did you use?
Click to expand...
Click to collapse
I've used extracted config from stock kernel and d620 global, both failed same way...

Lukiqq said:
I've used extracted config from stock kernel and d620 global, both failed same way...
Click to expand...
Click to collapse
If you upload the source that you used to GitHub I vould help you more, because I doubt that you used stock kernel source code plus stock defconfig, as in logcat appears some errors of missing functions that are defined in stock kernel source

partyzant_x said:
Can You post a logcat file with that command : logcat *:E
Click to expand...
Click to collapse
Here you go, kernel compiled from clean LG sources + Garcia98 config file cyanogenmod_g2m_defconfig. Still working system with black screen

I give up... tried one more time with Zaaap72 CM kernel sources and this time I've got bootloop right after first LG logo appear :-/

Still no ideas? C'mon DEVS! Any help would be greatly appreciated!

OT.
Are you THE Lukiqq, who made kernels for spica???

judas1977 said:
OT.
Are you THE Lukiqq, who made kernels for spica???
Click to expand...
Click to collapse
Indeed, now I'm the one who needs help

Hmm.. i think i cannot help you, because i have LG G2 Mini twin brother - L90. But making own kernel from clean LG sources comes trough my mind)

Related

[Q] How to remove/disable kernel's autoroot?

Now I'm using rage kernel 3.0 (GB). The the problem is everytime I install newer version Bysybox and reboot my phone it will revert to version 1.19.3-cm71 with. So, My Backup, Lucky Patcher, etc. doesn't work properly. Since I can't find many GB kernel, can I remove/disable kernel's autoroot?
Thanks.
PS. My phone is Xperia Active (ST17i SATSUMA)
Rapier- said:
Now I'm using rage kernel 3.0 (GB). The the problem is everytime I install newer version Bysybox and reboot my phone it will revert to version 1.19.3-cm71 with. So, My Backup, Lucky Patcher, etc. doesn't work properly. Since I can't find many GB kernel, can I remove/disable kernel's autoroot?
Thanks.
PS. My phone is Xperia Active (ST17i SATSUMA)
Click to expand...
Click to collapse
Yes, you can remove the kernel's autoroot feature. You will have to unpack the ramdisk and remove a few lines in the init.rc file. These lines can be deleted -
Code:
#DooMLoRD: launching autoroot
start autoroot
# DooMLoRD: autoroot service
service autoroot /sbin/autoroot.sh
user root
oneshot
disabled
Then repack the ramdisk and boot.img file. Good luck
abcdjdj said:
Yes, you can remove the kernel's autoroot feature. You will have to unpack the ramdisk and remove a few lines in the init.rc file. These lines can be deleted -
Code:
#DooMLoRD: launching autoroot
start autoroot
# DooMLoRD: autoroot service
service autoroot /sbin/autoroot.sh
user root
oneshot
disabled
Then repack the ramdisk and boot.img file. Good luck
Click to expand...
Click to collapse
Ah, thanks. But it seem like I have to start to study about kernel.Can you give me some guide?
Rapier- said:
Ah, thanks. But it seem like I have to start to study about kernel.Can you give me some guide?
Click to expand...
Click to collapse
I would recommend you to use Android Kernel Kitchen as it is fully automated and does the job perfectly. All instructions are provided within the tool itself. You can find Kernel Kitchen here - http://forum.xda-developers.com/showthread.php?t=1659584
Or you can see this tutorial too - http://forum.xda-developers.com/showthread.php?t=2316750
abcdjdj said:
I would recommend you to use Android Kernel Kitchen as it is fully automated and does the job perfectly. All instructions are provided within the tool itself. You can find Kernel Kitchen here - http://forum.xda-developers.com/showthread.php?t=1659584
Or you can see this tutorial too - http://forum.xda-developers.com/showthread.php?t=2316750
Click to expand...
Click to collapse
can I change kernel logo with it?
abcdjdj said:
Yes, you can remove the kernel's autoroot feature. You will have to unpack the ramdisk and remove a few lines in the init.rc file. These lines can be deleted -
Code:
#DooMLoRD: launching autoroot
start autoroot
# DooMLoRD: autoroot service
service autoroot /sbin/autoroot.sh
user root
oneshot
disabled
Then repack the ramdisk and boot.img file. Good luck
Click to expand...
Click to collapse
I've manage to extract the boot.img. But I can't find init.rc file anywhere. Did I do something wrong?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And in what program I can edit it?
Edit: Now I successfully extract the ramdisk using manual alternating method. Thanks.
prantoroy said:
can I change kernel logo with it?
Click to expand...
Click to collapse
Yes. The kernel logo is in the rle format. But Kernel Kitchen allows you to convert normal pictures to rle and vice-versa. So to change the kernel logo you must replace logo.rle
@abcdjdj, I just extracted the builded boot.img and I found that the command line is still there. I think the problem is here:
It asked for configuration file after I select build boot.img (with edited ramdisk of course). What should I do here? Select the "before edit ramdisk" one?
Rapier- said:
@abcdjdj, I just extracted the builded boot.img and I found that the command line is still there. I think the problem is here:
It asked for configuration file after I select build boot.img (with edited ramdisk of course). What should I do here? Select the "before edit ramdisk" one?
Click to expand...
Click to collapse
When you split the boot.img it must have asked to save the configuration so try building the boot.img with that configuration.
abcdjdj said:
When you split the boot.img it must have asked to save the configuration so try building the boot.img with that configuration.
Click to expand...
Click to collapse
I just tried it. And after create a new boot.img, I tried extract it again to see if it work. But it appear that init.rc still have the lines that I delete before.
Edit: Now, I'm done with it. I just forget to re-build the ramdisk so it use the old one. Now, I just flashed the new boot.img to my phone and it doesn't boot. It does vibrate one time but nothing more.
Note:
The command lines I delete is not exactly the same as you point it's
Code:
#DuMOHsmol:
instead of
Code:
#DooMLoRD:
And I do delete some blank lines. Is this the cause?
More SS:

How can i extract ramdisk ?

Hello guys
I have a little problem.
I builded kernel, but i have got only image and Zimage.
How can i extract ramdisk (for mkbooimg) ? Thanks
gigitux said:
Hello guys
I have a little problem.
I builded kernel, but i have got only image and Zimage.
How can i extract ramdisk (for mkbooimg) ? Thanks
Click to expand...
Click to collapse
I usually do that using dsixda's Android Kitchen
or I leave the zImage as it is, and flash it with some tools (flashable zip that already made to flash zImages)
omarainea said:
I usually do that using dsixda's Android Kitchen
or I leave the zImage as it is, and flash it with some tools (flashable zip that already made to flash zImages)
Click to expand...
Click to collapse
I can't :'(
Please test this, it would kernel 3.1 :|
Image: http://www.mediafire.com/download/o9907fm1q7leq58/Image
Zimage: http://www.mediafire.com/download/g16fszrme64g344/zImage
Thanks
Install p7zip-full package. Then the kernel from which you need ramdisk, just do this- 7z e kernel_name.elf
It'll give 3 files, 0(zImage), 1(Ramdisk), 2(cmdline).
Cheers,
AJ
Abhinav2 said:
Install p7zip-full package. Then the kernel from which you need ramdisk, just do this- 7z e kernel_name.elf
It'll give 3 files, 0(zImage), 1(Ramdisk), 2(cmdline).
Cheers,
AJ
Click to expand...
Click to collapse
Yep, i try, but i have black screen when boot smarthphone.
Perhaps i do an error....
gigitux said:
Yep, i try, but i have black screen when boot smarthphone.
Perhaps i do an error....
Click to expand...
Click to collapse
As far as i know, tearing down kernel with 7zip (or similar) breaks symlinking. I've read that somewhere, don't remember where. Either way, it breaks something. You could unpack kernel.elf with Flashtool, it will give you image, ramdisk.gz, and maybe file called cert or 3 (it depends). If kernel is boot.img instead of kernel.elf, just rename it to kernel.elf.
if you need help on packing/repacking kernel or ramdisk, PM me, I will help you as much as I can.
evildev said:
As far as i know, tearing down kernel with 7zip (or similar) breaks symlinking. I've read that somewhere, don't remember where. Either way, it breaks something. You could unpack kernel.elf with Flashtool, it will give you image, ramdisk.gz, and maybe file called cert or 3 (it depends). If kernel is boot.img instead of kernel.elf, just rename it to kernel.elf.
if you need help on packing/repacking kernel or ramdisk, PM me, I will help you as much as I can.
Click to expand...
Click to collapse
There are links for download Image and zImage.
gigitux said:
Hello guys
I have a little problem.
I builded kernel, but i have got only image and Zimage.
How can i extract ramdisk (for mkbooimg) ? Thanks
Click to expand...
Click to collapse
Reported!
This should be in Q&A section not in Development section! REPORTED!
Anyway, you can use championswimmer's Android Kernel Kitchen to extract your kernel for getting zImage, ramdisk and the contents of the ramdisk :good:
Garcia98 said:
This should be in Q&A section not in Development section! REPORTED!
Anyway, you can use championswimmer's Android Kernel Kitchen to extract your kernel for getting zImage, ramdisk and the contents of the ramdisk :good:
Click to expand...
Click to collapse
It won't work. If you want just to extract use flashtool. Unpacking with 7-zip will destroy symlinks and packing again will never work. To use flashtool rename boot.img to boot.elf. Choose Tools>Extractors>Elf and choose your boot.elf file you renamed previously. Then press dump and close. It should be in the same folder with the boot.elf file. (boot.elf was always a renamed boot.img file ) BTW wrong section
Andrewasth said:
It won't work. If you want just to extract use flashtool. Unpacking with 7-zip will destroy symlinks and packing again will never work. To use flashtool rename boot.img to boot.elf. Choose Tools>Extractors>Elf and choose your boot.elf file you renamed previously. Then press dump and close. It should be in the same folder with the boot.elf file. (boot.elf was always a renamed boot.img file ) BTW wrong section
Click to expand...
Click to collapse
I said that to OP and he gave me links to his zImage and image.
I don't possess great knowledge concerning android, but I wan't to help if someone is stuck, give instructions, etc. But to do someone else's work, well...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Andrewasth said:
It won't work. If you want just to extract use flashtool. Unpacking with 7-zip will destroy symlinks and packing again will never work. To use flashtool rename boot.img to boot.elf. Choose Tools>Extractors>Elf and choose your boot.elf file you renamed previously. Then press dump and close. It should be in the same folder with the boot.elf file. (boot.elf was always a renamed boot.img file ) BTW wrong section
Click to expand...
Click to collapse
I'm pretty sure that championswimmer's tool works, because I used it just a week ago to extract a kernel and it worked like a charm
However, Flashtool method is OK too
Garcia98 said:
I'm pretty sure that championswimmer's tool works, because I used it just a week ago to extract a kernel and it worked like a charm
However, Flashtool method is OK too
Click to expand...
Click to collapse
Nah, it doesn't. But we can use 7z e kernel.elf and then extract ramdisk from champ's kernel kitchen so it'll not break the symlinks.
Cheers,
AJ

[Q] [ROM][CM12][D618] Rom does not boot

Hello, friends who own G2 Mini. I'm trying for the past weeks to build AOSP (Lollipop) to the D618 variant. Even though I was able to build the zip files and flash them, the ROM won't boot. Instead of booting, I get an error in LG logo with fastboot stuff at the corner of the screen. I believe it's kernel related but I have no idea how to fix, that's where you guys participate. Could you guys help me, please?
The sources I'm using for Kernel is LG original sources, I built the zImage from the .TXT in that source.
Here's a picture of the error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you guys.
Hello, I was wondering if I could install a pure Android lollipop on a AT&T Moto X 2014?
Sent from my XT1097 using XDA Free mobile app
mmaslo1124 said:
Hello, I was wondering if I could install a pure Android lollipop on a AT&T Moto X 2014?
Sent from my XT1097 using XDA Free mobile app
Click to expand...
Click to collapse
I don't know because this is G2 Mini forum.
Go to Moto X section.
Same apply to your case
http://forum.xda-developers.com/showthread.php?p=57798377
Happy new year to everyone on the forums!
Sent from my D620r [CM12]
Vagelis1608 said:
Same apply to your case
http://forum.xda-developers.com/showthread.php?p=57798377
Happy new year to everyone on the forums!
Sent from my D620r [CM12]
Click to expand...
Click to collapse
So you mean that if I make a zImage-dtb it will work? (Sorry for dumb questions =) )
jfpsb said:
So you mean that if I make a zImage-dtb it will work? (Sorry for dumb questions =) )
Click to expand...
Click to collapse
I mean that there is an issue with your compiled dtb.img
http://forum.xda-developers.com/showthread.php?p=57812554
Happy new year to everyone on the forums!
Sent from my D620r [CM12]
Vagelis1608 said:
I mean that there is an issue with your compiled dtb.img
Click to expand...
Click to collapse
So, I compiled a .dtb file from msm8226-g2mds_global_com .dts files, made all the changes in the defconfig file to point to this .dtb file to build the prebuilt kernel with it (I was even able to build the dt.img using dtbToolCM, just to see if it would work). Okay, the zImage-dtb was built fine, I used it in my AOSP build but the error was still the same from OP. Do you know what could be wrong? And to be honest, I'm not really sure how to use that mkbootimg.mk to build AOSP, could you help me?
My defconfig looks like this after the changes:
Code:
#
# Boot options
#
CONFIG_USE_OF=y
CONFIG_BUILD_ARM_APPENDED_DTB_IMAGE=y
CONFIG_BUILD_ARM_APPENDED_DTB_IMAGE_NAMES="msm8226_g2mds"
CONFIG_ZBOOT_ROM_TEXT=0
CONFIG_ZBOOT_ROM_BSS=0
CONFIG_ARM_APPENDED_DTB=y
CONFIG_ARM_ATAG_DTB_COMPAT=y
CONFIG_CMDLINE="console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 user_debug=31 msm_rtb.filter=0x37 androidboot.hardware=g2mds"
# CONFIG_XIP_KERNEL is not set
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
# CONFIG_AUTO_ZRELADDR is not set
Now I really don't know what the heck is wrong here, I hope someone could help me. Thanks.
Extract dtb.img from stock kernel using Android Image Kitchen and put it in your kernel (again, using AIK)
Happy new year to everyone on the forums!
Sent from my D620r [CM12]
Worked
Vagelis1608 said:
Extract dtb.img from stock kernel using Android Image Kitchen and put it in your kernel (again, using AIK)
Click to expand...
Click to collapse
So, I did that (unpacked the boot.img and repacked with my prebuilt zImage) and worked fine, no longer kernel errors, but the phone still won't boot. Do you have any ideas? For sure it's not kernel related anymore (I believe). The phone just stay in LG logo, don't go to boot animation, then reboots to recovery. Thank you very much for the AIK tip by the way.
jfpsb said:
So, I did that (unpacked the boot.img and repacked with my prebuilt zImage) and worked fine, no longer kernel errors, but the phone still won't boot. Do you have any ideas? For sure it's not kernel related anymore (I believe). The phone just stay in LG logo, don't go to boot animation, then reboots to recovery. Thank you very much for the AIK tip by the way.
Click to expand...
Click to collapse
Just grab dmesg and logcat from your ROM with adb and see if you can find what goes wrong.
Sent from my D620r [Stock 4.4.2]
Vagelis1608 said:
Just grab dmesg and logcat from your ROM with adb and see if you can find what goes wrong.
Sent from my D620r [Stock 4.4.2]
Click to expand...
Click to collapse
Ok, I'll try. Thanks a lot.
New problem
I have a new problem now, friends. I'm trying to build CM12 now (I put AOSP aside for a moment). I can get it built everytime, the problem is that it never boots and I have no idea why (like always). And I can't take any dmesg or logcats, don't work either. So, down below there's a video showing the problem. Any ideas? Thanks.
MORE INFO: that weird thing in the corners never leave the screen, even in recovery mode. You guys think it's something related to kernel?
http://youtu.be/Z3cnXFfbciY
I tried more stuff but nothing works. I'm about to give up on this. Any help?

Change boot logo on your Poco!

Hey, i made program that generates logo image for Poco. It needs Java 8 or higher!
Download: click
How to use:
Download, unzip pocosplasher-release.zip
Edit images in res/ folder (MAKE SURE that your images are BMP-24!)
Launch pocosplasher.jar with console:
Code:
java -jar pocosplasher.jar
Flash FLASH_ME.img with fastboot:
Code:
fastboot flash logo FLASH_ME.img
How to rollback logo:
Flash ORIGINAL.img with fastboot:
Code:
fastboot flash logo ORIGINAL.img
Please, report bugs and issues.
I've read somewhere that bootlogo is related to Bootloader & firmware updates. So if i changed it, i must relflash custom logo every time?
Is that correct?
thanhnvt194 said:
I've read somewhere that bootlogo is related to Bootloader & firmware updates. So if i changed it, i must relflash custom logo every time?
Is that correct?
Click to expand...
Click to collapse
Some ROM such as MIUI, has own logo image, and you needs to reflash your image again.
Hey,
Thanks for the tool, It works, here's my custom logo which replaces the Bootlogo with a Zotac gaming logo.
Screenshots attached
Image has been cropped, but on screen everything is anyways black so don't worry
P.S: All works are properties of their respective owners
P.P.S: ENJOY!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks! Been waiting for this mod.
thanhnvt194 said:
I've read somewhere that bootlogo is related to Bootloader & firmware updates. So if i changed it, i must relflash custom logo every time?
Is that correct?
Click to expand...
Click to collapse
No
---------- Post added at 11:53 AM ---------- Previous post was at 11:52 AM ----------
curoviyxru said:
Hey, i made program that generates logo image for Poco. It needs Java 8!
Download: click
How to use:
Download, unzip pocosplasher-release.zip
Launch pocosplasher.jar with console:
Flash FLASH_ME.img with fastboot:
How to rollback logo:
Flash ORIGINAL.img with fastboot:
Please, report bugs and issues.
Click to expand...
Click to collapse
Can u make a zip in recovery my previous device redmi 3s had a zip for it and u can make ur own boot.img with it
didn't people said that due to the F1 can't be saved if bricked because of no EDL mode, changing stuffs like this is not recommended?
Also, can someone please make a dark Pixel boot logo? (like for example here or here, although I dont know if the Pixel 1 2 3 has any differences)
edit: welp I just went and it it anyway. Attached is the modified img for dark Pixel boot logo, plus a flashable zip with both the boot logo and animation and audio from Pixel 2
Thanks! I waited for this mod
I just made pixel 2-like splash screen!
It also worked with java 11. Thanks again
Can you help me if I replace any of the images in the res folder the pocosplasher java doesnt work when everything is default in res folder it make a flash_me.img but not when i replace any image. Help....
Or can you please make one IMG for this img
Pls make a .IMG boot logo from this IMG.
aayush0508 said:
Pls make a .IMG boot logo from this IMG.
Click to expand...
Click to collapse
+1
pipyakas said:
didn't people said that due to the F1 can't be saved if bricked because of no EDL mode, changing stuffs like this is not recommended?
Also, can someone please make a dark Pixel boot logo? (like for example here or here, although I dont know if the Pixel 1 2 3 has any differences)
edit: welp I just went and it it anyway. Attached is the modified img for dark Pixel boot logo, plus a flashable zip with both the boot logo and animation and audio from Pixel 2
Click to expand...
Click to collapse
Works perfectly. Thanks!
updated my firmware & vendor to 9.3.14 today and the flashing of the logo img on fastboot is not working, anyone?
aayush0508 said:
Can you help me if I replace any of the images in the res folder the pocosplasher java doesnt work when everything is default in res folder it make a flash_me.img but not when i replace any image. Help....
Click to expand...
Click to collapse
It's because the size of the image is invalid. I don't know the specific either, but just reduced the size to 1080x1920 worked
aayush0508 said:
Pls make a .IMG boot logo from this IMG.
Click to expand...
Click to collapse
I attached the one I made using your image below. Tested and working
eurochild said:
updated my firmware & vendor to 9.3.14 today and the flashing of the logo img on fastboot is not working, anyone?
Click to expand...
Click to collapse
I just tried on 9.3.14 firmware, still working fine
pipyakas said:
It's because the size of the image is invalid. I don't know the specific either, but just reduced the size to 1080x1920 worked
I attached the one I made using your image below. Tested and working
I just tried on 9.3.14 firmware, still working fine
Click to expand...
Click to collapse
I just tried it and it's working. Ty
pipyakas said:
It's because the size of the image is invalid. I don't know the specific either, but just reduced the size to 1080x1920 worked
I attached the one I made using your image below. Tested and working
I just tried on 9.3.14 firmware, still working fine
Click to expand...
Click to collapse
Thank you man it worked appreciate it.
Anyone make white pixel splash screen
How to backup stock splash screen?
AstroBiswas said:
How to backup stock splash screen?
Click to expand...
Click to collapse
system/media/bootanimation.zip
AsusZenFone3Deluxe said:
system/media/bootanimation.zip
Click to expand...
Click to collapse
Not boot animation the yellow poco logo that appears first after bootup

[KERNEL] Stock Kernel with Magisk

Android 11 (R)
HK_58.1.A.1.178
Stock Kernel With Magisk Inside
Download:
AFH
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
----------
Contribution by @Nezorflame: Step-by-Step Guide, MEGA Folder Link
Contribution by @fengmubai: Script to Remove system_ext Record from ramdisk, Google Drive Folder Link
Brillant!
What's the step-by-step process with using adb or newflasher to:
0. Unlock my Xperia 5 ii and root it
1. Get Android 11 with magisk.
2. And get Orangefox or Twrp ?
Thanks a lot for your help for me and other users
My dream is a kernel with WireGuard integrated. Is this possible?
Yoannjap said:
Brillant!
What's the step-by-step process with using adb or newflasher to:
0. Unlock my Xperia 5 ii and root it
1. Get Android 11 with magisk.
2. And get Orangefox or Twrp ?
Thanks a lot for your help for me and other users
Click to expand...
Click to collapse
[CLOSED] Delete
Here was a Guide. Someone said people don't care about Me or My Work so...
forum.xda-developers.com
Thank you
When we'll see custom kernels for our Xperia 5 II?
Top man. Thanks!
I fought for hours with fastboot drivers unlocking my bootloader on A11 only to find Magisk didn't work with this phone.
MrN1484 said:
Top man. Thanks!
I fought for hours with fastboot drivers unlocking my bootloader on A11 only to find Magisk didn't work with this phone.
Click to expand...
Click to collapse
It works, just the ramdisk has to be patched (Sony needs to fix that actually).
In case someone needs it, here's the stock kernel from the latest A11 build (58.1.A.5.159).
Contents:
stock unpatched image
AIK-repacked image with the system-ext record commented out in fstab
Magisk-patched version (latest beta v22.1)
Link to the folder: MEGA
Nezorflame said:
In case someone needs it, here's the stock kernel from the latest A11 build (58.1.A.5.159).
Contents:
stock unpatched image
AIK-repacked image with the system-ext record commented out in fstab
Magisk-patched version (latest beta v22.1)
Link to the folder: MEGA
Click to expand...
Click to collapse
Big thank you for providing this. You got the AS52 if I remember right?
T3chDelicious said:
Big thank you for providing this. You got the AS52 if I remember right?
Click to expand...
Click to collapse
Yup, that's right.
Nezorflame said:
Yup, that's right.
Click to expand...
Click to collapse
Perfect! Thanks again for providing the fixed boot image.
I've updated the Magisk-patched version to the latest v23 release.
It's in the same folder as before, but if you need it separately, here's the link: https://mega.nz/folder/yi5mlDJR#a775v2eDTNc8-UmLKfkQhA/file/Tn42zShD
Nezorflame said:
I've updated the Magisk-patched version to the latest v23 release.
It's in the same folder as before, but if you need it separately, here's the link: https://mega.nz/folder/yi5mlDJR#a775v2eDTNc8-UmLKfkQhA/file/Tn42zShD
Click to expand...
Click to collapse
Works perfect, thank you, exactly what I was looking for. Made my day.
Do you maybe have a working/not-encrypted recovery for 58.1.A.5.159 aswell?
Edit: Nevermind, Orange Fox works well!
[TWRP][UNOFFICAL] OrangeFox Recovery Project [R10.0]
/* * Your warranty is now void. * * We're not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in...
forum.xda-developers.com
I do as https://github.com/topjohnwu/Magisk/issues/3752 said,
Patch 58.1.A.5.159 boot.img with magisk
use Image Kitchen and unpack boot.img
Locate fstab.qcom and edit with notepad++ remove the system_ext line and save
Repack and flash the new .img ,fastboot flash boot_a & boot_b boot.img
but there is also a bootloop with xperia1 II ... so is there any solution to this issue now?
xda177 said:
I do as https://github.com/topjohnwu/Magisk/issues/3752 said,
Patch 58.1.A.5.159 boot.img with magisk
use Image Kitchen and unpack boot.img
Locate fstab.qcom and edit with notepad++ remove the system_ext line and save
Repack and flash the new .img ,fastboot flash boot_a & boot_b boot.img
but there is also a bootloop with xperia1 II ... so is there any solution to this issue now?
Click to expand...
Click to collapse
Use Nezorflames kindly shared boot kernel from post #13. I even upgraded to 58.1.A.5.222 and that boot.img still works rooted without any bootloops or problems
For anyone having a headache of a time here is an updated IMG modified thru android kitchen + Magisk Patch'd Already all you need to do is download and flash.
For - XQ-AT51_Customized US_58.1.A.5.222-R6B
Link As well- https://drive.google.com/file/d/1JqR2DAZR2dmQxOAUdEOuj2TlxDpHV5h0/view?usp=sharing
I've updated the kernel files (original, repacked and Magisk-patched) for the XQ-AS52 58.1.A.5.280 firmware on the MEGA folder. Using it myself so works fine here
carbon271 said:
For anyone having a headache of a time here is an updated IMG modified thru android kitchen + Magisk Patch'd Already all you need to do is download and flash.
For - XQ-AT51_Customized US_58.1.A.5.222-R6B
Link As well- https://drive.google.com/file/d/1JqR2DAZR2dmQxOAUdEOuj2TlxDpHV5h0/view?usp=sharing
Click to expand...
Click to collapse
can you please do this for us with XQ-AS62 i cant get the phone to boot
carbon271 said:
For anyone having a headache of a time here is an updated IMG modified thru android kitchen + Magisk Patch'd Already all you need to do is download and flash.
For - XQ-AT51_Customized US_58.1.A.5.222-R6B
Link As well- https://drive.google.com/file/d/1JqR2DAZR2dmQxOAUdEOuj2TlxDpHV5h0/view?usp=sharing
Click to expand...
Click to collapse
can you please do this for us with XQ-AS62 i cant get the phone to boot

Categories

Resources