Hi to all...
I have found that changing bootlogo has 3 ways:
1)param.bin
2)initlogo,logo.bin
3)model.rle at /
Our Gio has the bootlogo in /GIO.rle so to edit it, you have to extract boot.img of your favorite rom by android image kitchen and replace it by micro fire tool and repack it and then flash it via recovery.Please note that flashing boot image via apps will not affect.
Related
Hi!
I update the Idol suite for 4.7 6039 phone version, it is a Windows tools ( sorry).
Log:
It use ADB tools
Can unlock bootloader
Flash TWRP 3.0.0-0 for Idol 4.7
Backup yur phone ROM (need root)
Can boot in bootloader mode
Can reboot from bootloader mode
Can boot in to recovery
Can simply reboot the phone
Can extract the files from a ext4 image, like system.img
Can flash a single image
Can pull to edite the build.prop file and create a flash zip for it
Can boot in to twrp 3.0.0-0 with out flashing ( useful to recover the phone)
Can pull the apks from system and create a flash zip ( If you want to change something in apps or change a pp for another than you want to flash it again )
Can edite the apk files and create a flash zip
Can create a new Splash image and a zip to flash it
It have idol drivers for windows
NOTE:
Some tools are not mine, I simply put everything together in one place!
I am not responsible for any damage they may cause to your device.
Use it at your responsability
Extract the folder from zip in to descktop and execute the Idol_Suite_V3.exe file.
New_Idol_4.7_Suite.zip
Any issue please tell me!
Enjoy it!
The tool is update:
Now you can modify boot and recovery to.
thank you dude.
You can upload the file again
Thanks!!!
Hi Persona78, first can i say what a fantastic job you have done, most of my research on the idol 3 4.7 points back to you, hats off sir!
I'm still having a problem and i'm really at a loss here after about a week of no returns.
adb refuses to recognise my 6039y when in bootloader so i cannot flash recovery, or ROM, or any command. I have all drivers installed correctly, vendor id of 0x1bbb is set in a.ini file in adb_usb.ini, i keep search for different approaches but turning up nothing!
Are there anything to suggest? I would be most appreciative!
Thanks, Marlin
I have a boot.img file that i can use to root my Samsung J2 SM-J260F - if I flash this with Odin everything is Ok. Now I want to edit a file in the ramdisk of the boot.img to make the phone boot on power. However simply unpacking the Boot.img and unzipping the ramdisk then repacking fails - even when i do not edit anything in the ramdisk. When the repacked boot.img is flashed with Odin the device gets into a boot loop.
I am using the Carliv Image Kitchen for Androidv1.3 tool to do the packing and unpacking.
Is there some specific aspect of the Samsung boot.img such as a signature that is causing this to fail?
Progress update
The only unpacking tool that seemed to correctly repack the image was MTK_Extractor_V2.63 - all of the other (many) utilities I tried did not seem to repack the ramdisk correctly and caused the phone to boot into the recovery screen.
Changing the init.rc and init_samsungexynos7570.rc files as follows finally led to success.
In file init.rc
delete everything under "on charger" then add back setprop sys.powerctl reboot
Under "service lpm /system/bin/lpm"
delete class sec-charger critical and replace with trigger late-init
In file init_samsungexynos7570.rc
delete everything under "on property:ro.bootmode=charger"
AndyJN said:
I have a boot.img file that i can use to root my Samsung J2 SM-J260F - if I flash this with Odin everything is Ok. Now I want to edit a file in the ramdisk of the boot.img to make the phone boot on power. However simply unpacking the Boot.img and unzipping the ramdisk then repacking fails - even when i do not edit anything in the ramdisk. When the repacked boot.img is flashed with Odin the device gets into a boot loop.
I am using the Carliv Image Kitchen for Androidv1.3 tool to do the packing and unpacking.
Is there some specific aspect of the Samsung boot.img such as a signature that is causing this to fail?
Click to expand...
Click to collapse
Did you unlocked the bootloader?
Also i would recommend you to use a custom recovery like TWRP to flash boot.img
AndyJN said:
I have a boot.img file that i can use to root my Samsung J2 SM-J260F - if I flash this with Odin everything is Ok. Now I want to edit a file in the ramdisk of the boot.img to make the phone boot on power. However simply unpacking the Boot.img and unzipping the ramdisk then repacking fails - even when i do not edit anything in the ramdisk. When the repacked boot.img is flashed with Odin the device gets into a boot loop.
I am using the Carliv Image Kitchen for Androidv1.3 tool to do the packing and unpacking.
Is there some specific aspect of the Samsung boot.img such as a signature that is causing this to fail?
Click to expand...
Click to collapse
TBM 13 said:
Did you unlocked the bootloader?
Also i would recommend you to use a custom recovery like TWRP to flash boot.img
Click to expand...
Click to collapse
Which.... does not exist. J2 Core doesnt get the same love.
I recommend Android Image Kitchen (AIK) by Osmosis. Havent failed me once in my case.
Prove N. said:
Which.... does not exist. J2 Core doesnt get the same love.
Click to expand...
Click to collapse
I'm sorry, my bad.
has anyone tried to port the 9 pie firmware from J260A to other J260F/M/G?
Hi everyone!
I need to edit an APK in stock ROM (system.img) of my device. I have unpacked system.img and repacked with some programs on Windows. But When I unpack and repack the system.img file and change it with original system.img file (even though I didn't change any APK or anything), I can flash it through fastboot or port 9008 successfully. BUT When I try to start my phone, It stuck on MI Logo screen.
So There is no problem with flash any rom. But I want to unpack rom and edit an APK then repack it. This is my issue. How can I do it? I think there is a problem on unpack/repack step. I'll be glad if anyone can help me about it.
Thanks in advance!
p.s. I can't flash a recovery rom because of I can't run phone.
Hi guys i hope every body is ok i wanna get root for my smart tv brandt 32 ( andriod 6 ) the original manufacter of this device is konka (chinese brand )
i have access to the stock recovery i was able to extract the boot.img and recovery.img files from system using adb shell commands but i couldn't port the recovery with twrp auto porter or patch the boot with magisk
i will upload my stock boot.img and recovery.img and my tv spec below on attachment hoping someone can port the recovery or patch the boot for me
NOTE : i was able to unpack both of the recovery and the boot with andriod image kitchen and im ready to upload the unpaked files if that necessary
(i tried the repack stock recovery and it's work perfectly )
finaly guys you are my only hope to root this device i hope someone can help me and thanks for ur time
i tried to patch boot.img with magisk on two of my rooted phones but both showed errors, the first one (unsopported) and the other (unable to unpack boot image), even if it worked how would you run the fastboot commands? because direct usb connection with pc doest work on mine.
Then i tried to follow a tutorial to make a custom recovery but it requires a custom recovery of a phone with the same chipset which i couldnt find.
too bad one click root apps didnt work , i would have a better chance if i could wire my tv to pc (could you?).
This is the Stock Splash Boot Screen of Redmi Note 7(lavender),
You can flash this via a custom recovery,
Might help if you have installed a custom splash and want to get stock splash screen back.
Downloads :
Stock-lavender-splash-flashable(by-Deepesh).zip | by Deepesh for Redmi Note 7
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
If you want to flash via fastboot then just extract the upper file and in the extracted folder you will find "splash.img" this is the splash image you can flash it by the command;
fastboot flash splash <the file>