Related
To change Boot Logo u need Logo converter and Dragonface tool and extract to any folder.
4shared.com/rar/LpFtKLSqce/A10_A13_A31_Dragonface_V207_EN.html
4shared.com/zip/Oreu3YCLba/LogoGen.html
step 1 create or download any logo likes u in .bmp format.
step 2 convert ur logo with logo converter to initlogo.rle file
step 3 open dragonface.exe click firmware n choose u A13/A10/A31 .img firmware n wait until procses is done, clik picture music tab and click boot logo to change manufacture name logo with u own logo,and click android logo to change phone model logo.
if u done all just save it n flas it again to ur device.
I was wondering if it were possible to change the bootloader logos (not the boot animation, which displays during the Android startup process) for the HD 8.9" (jem). Would we be able to change both the white & orange and white & blue "Kindle Fire" logos, or would we only be able to modify the white & blue logo? I know the second logo must be modifiable somehow, as Hashcode did it when he wrote the 2nd bootloader image for the HD devices.
Using existing bug in bootloader only 2nd one is possible to change. Orange logo is shown by the stock amazon bootloader which is signed and those the device will refuse to boot it if you will modify it. To modify the second bootlogo you should recompile 2nd bootloader and rebuild boot.img
ipipipipip said:
Using existing bug in bootloader only 2nd one is possible to change. Orange logo is shown by the stock amazon bootloader which is signed and those the device will refuse to boot it if you will modify it. To modify the second bootlogo you should recompile 2nd bootloader and rebuild boot.img
Click to expand...
Click to collapse
1) So I would need to modify initlogo.rle and then recompile the u-boot file?
2) After that, would I need to flash that file to the bootloader partition on the Kindle?
3) Finally, would the new u-boot bootloader brick my kindle?
If you flash it in place of second bootloader you are safe (second bootloader is built-in into "boot" partition), if you alter actual "bootloader" partition -- you'll get a brick (it is signed, and its integrity is checked by xloader (also signed xD)) (and I'm not sure if it is possible to recover from this state without disassembling the device and connecting directly to emmc pins).
TL;DR; It's not possible to get rid of orange kf logo, but you can change the blue one.
ipipipipip said:
If you flash it in place of second bootloader you are safe (second bootloader is built-in into "boot" partition), if you alter actual "bootloader" partition -- you'll get a brick (it is signed, and its integrity is checked by xloader (also signed xD)) (and I'm not sure if it is possible to recover from this state without disassembling the device and connecting directly to emmc pins).
TL;DR; It's not possible to get rid of orange kf logo, but you can change the blue one.
Click to expand...
Click to collapse
Sorry for the (really) late reply, but I read the post, and I was planning on building CM for myself. Would I flash the u-boot file directly to the boot partition, or does it need to be wrapped into a ROM boot image somehow? Also, if if needs to be embedded into the boot image (and I'm assuming it does), where would it need to be placed?
There is a prebuilt binary of uboot (in the device specific files) https://github.com/KFire-Android/android_device_amazon_jem/tree/cm-12.0/prebuilt/boot that is attached to the boot.img while building the ROM
ipipipipip said:
There is a prebuilt binary of uboot (in the device specific files) https://github.com/KFire-Android/android_device_amazon_jem/tree/cm-12.0/prebuilt/boot that is attached to the boot.img while building the ROM
Click to expand...
Click to collapse
I figured that out, and I was able to change the 2nd bootloader image successfully.
However, whenever I directly reboot to recovery without pressing and holding the volume up button (i.e.: when choosing to reboot to recovery from within TWRP or Android), the blue and white "Kindle Fire" logo shows up instead of my custom image. I'm thinking that this is because the initlogo.rle is also baked into the custom bootloader partition (which I think uses u-boot as well). Would there be any way to decompile the bootloader (not the u-boot.binary in the device-specific files), replace initlogo.rle, and then recompile into a usable bootloader image?
the initlogo.rle is also baked into the custom RECOVERY partition
Click to expand...
Click to collapse
don't touch the partition called "bootloader" without correct signature you'll get a brick that is quite hard to recover.
recovery partition is built almost the same way as the boot one, and I suppose you may use the same uboot binary (the one with replaced initlogo.rle) for it, just place it with a specific offset into your TWRP (or whatever you use) recovery image.
https://github.com/KFire-Android/android_device_amazon_jem/blob/cm-12.0/boot.mk#L53
ipipipipip said:
don't touch the partition called "bootloader" without correct signature you'll get a brick that is quite hard to recover.
recovery partition is built almost the same way as the boot one, and I suppose you may use the same uboot binary (the one with replaced initlogo.rle) for it, just place it with a specific offset into your TWRP (or whatever you use) recovery image.
https://github.com/KFire-Android/android_device_amazon_jem/blob/cm-12.0/boot.mk#L53
Click to expand...
Click to collapse
I'll try that out. Thanks so much for the help!
Hy nexus friends,
I need help from someone with a 791F 32GB. I dont know if a 790 or a 16gb version is identical.
It would be great if someone with a rooted device can make a backup for me of the bootloader bin files.
aboot, sbl1, rpm, tz, sdi, sbl1b, tzb, rpmb, abootb, misc, laf, persist.
I flashed the hammerhead bootloader and stuck at 9008 mode.
It will be ver great if someone could help me.
Some partition apps could make a backup or with the dd command.
If i fet a solution, i would post it here. At the moment i had the device and the tools that i flashed for test a nexus 5 sbl. So write is possible.
Thanks for help guys
Where can I see if my phone is 791F?
i have the US Nexus 5X 32GB. Tell me what to do and I'll get you what you need.
tacofromhell said:
Where can I see if my phone is 791F?
Click to expand...
Click to collapse
Model number on the phone box and I believe in the bootloader screen: turn off phone then hold volume down and power.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Model number on the phone box and I believe in the bootloader screen: turn off phone then hold volume down and power.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Ok. Just rebooted into bootloader and under "Variant" it says LGH791 but no F, sorry
Thx for your help.
You can backup the partitions with some partition backup apps or with dd.
If you look with a file explorer in /dev/block/platform/soc.0/f9824900.sdhci/by-name/XXXXX , XXXX there are the partiton names.
If you want to copy with adb, make adb shell, su, and then:
dd if= /dev/block/platform/soc.0/f9824900.sdhci/by-name/cmnlib of=sdcard/cmnlib.img
Around 36 partitons are in the MM build. System, cache, userdata are not needed..
konsolen said:
Thx for your help.
You can backup the partitions with some partition backup apps or with dd.
If you look with a file explorer in /dev/block/platform/soc.0/f9824900.sdhci/by-name/XXXXX , XXXX there are the partiton names.
If you want to copy with adb, make adb shell, su, and then:
dd if= /dev/block/platform/soc.0/f9824900.sdhci/by-name/cmnlib of=sdcard/cmnlib.img
Around 36 partitons are in the MM build. System, cache, userdata are not needed..
Click to expand...
Click to collapse
Have you found a solution to get booting again? Been searching and tried multiple methods to repair my boot image on the H791 I own.
I have worked with another XDAer who extracted and now have the bootimage files from several stock H791 files available. They include the GPT from the stock image MDA89E and the boot image files from bootloader-bullhead-bhz10i.img bootloader-bullhead-bhz10k.img and bootloader-bullhead-bhz10m.img. Let me know if you still need these. I see 11 files in the boot image. During some testing I flashed over the sbl1 on my device and lost the ability do anything but go into QUSB DL mode 9008 as well.
As I am writing this I am now wondering if there is a separate set of SBL etc. files for the International variant? We may need to extract from the 791 tot file available the needed files if we do not have another method of obtaining them. Let me know if you have found a workable way to flash the needed boot images in place. Thanks.
nate0 said:
Have you found a solution to get booting again? Been searching and tried multiple methods to repair my boot image on the H791 I own.
I have worked with another XDAer who extracted and now have the bootimage files from several stock H791 files available. They include the GPT from the stock image MDA89E and the boot image files from bootloader-bullhead-bhz10i.img bootloader-bullhead-bhz10k.img and bootloader-bullhead-bhz10m.img. Let me know if you still need these. I see 11 files in the boot image. During some testing I flashed over the sbl1 on my device and lost the ability do anything but go into QUSB DL mode 9008 as well.
As I am writing this I am now wondering if there is a separate set of SBL etc. files for the International variant? We may need to extract from the 791 tot file available the needed files if we do not have another method of obtaining them. Let me know if you have found a workable way to flash the needed boot images in place. Thanks.
Click to expand...
Click to collapse
I'm on the same boat , hope you have something to boot it up
It's been more than 3 weeks, my 5X just brick itself . And LG doesn't support 5X in my country . I'm very very hoping you will find solution.
Apayah said:
I'm on the same boat , hope you have something to boot it up
It's been more than 3 weeks, my 5X just brick itself . And LG doesn't support 5X in my country . I'm very very hoping you will find solution.
Click to expand...
Click to collapse
I think the only way from my perspective so far is to manually flash the needed QComm/boot image/boot loader files with something that can interface with the phone. I am pretty sure I know a method to manually do this but need the flash programmer that works with this device to accomplish. Or if there is a way to add MSM8992 support to the BoardDiag tool, that would work...I have not given up, just have not had a whole lot of time to work on this the past 2 days.
nate0 said:
I think the only way from my perspective so far is to manually flash the needed QComm/boot image/boot loader files with something that can interface with the phone. I am pretty sure I know a method to manually do this but need the flash programmer that works with this device to accomplish. Or if there is a way to add MSM8992 support to the BoardDiag tool, that would work...I have not given up, just have not had a whole lot of time to work on this the past 2 days.
Click to expand...
Click to collapse
I see boardiag for n5 , please don't give up ?.
And i see blank flash file for N6
Try to connect the usb cable with the pressed vol up button. Normaly the lg download screen should pop up.
Its possible then to flash a tot file with the lg up tool.
But i found only one tot file around the i net.
It will be flashed but hang in the bootscreen.
A org. tot or kdz file were great or a solution to create such a file.
konsolen said:
Try to connect the usb cable with the pressed vol up button. Normaly the lg download screen should pop up.
Its possible then to flash a tot file with the lg up tool.
But i found only one tot file around the i net.
It will be flashed but hang in the bootscreen.
A org. tot or kdz file were great or a solution to create such a file.
Click to expand...
Click to collapse
I can go to download mode but it can't hang , the screen turns to black Immediately. I'm just waiting for another way .
Apayah said:
I can go to download mode but it can't hang , the screen turns to black Immediately. I'm just waiting for another way .
Click to expand...
Click to collapse
Yes. The FW download screen is not an option here. Seems those of us currently needing a solution or method is do to the phone being in QC emergency mode only. I can see my phone in device manager only as with the QC HUSB 9008 drivers.
nate0 said:
Yes. The FW download screen is not an option here. Seems those of us currently needing a solution or method is do to the phone being in QC emergency mode only. I can see my phone in device manager only as with the QC HUSB 9008 drivers.
Click to expand...
Click to collapse
Yes it same , i got that to.
So what is blank flash? on N6 thread .
链接：https://pan.baidu.com/s/1TmQ9jmdAym2NYt_YGyt2Cg 引脚：g5cg
Note:
This is not bootanimation, this is to change the splash screen (the 'Robin' boot logo which is displayed when device is switched ON)
This is for Nextbit Robin Only..
(For other devices, please send me your splash.img so that I can create a tool for you too.)
Requirements:
1. Rooted Nextbit Robin (any ROM) or just unlocked bootloader
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
1. Download & Extract this: Nextbit_Robin_Splash_Maker.zip
2. Make sure you have a picture in PNG format with resolution 1080x1920px.
3. Now rename your picture as logo.png & replace it inside "pics" folder of the extracted folder.
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img and flashable zip file, which you can find inside the "output" folder after completion.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though..)
You may get it from the stock firmware itself.
I have also attached the stock splash.img from 10/6/16 - 00WW_1_450.
Now, choose any one easy method to flash:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Also, changing the splash screen doesn't mean you can get rid of the 5 seconds timeout in bootloder unlocked warning, that's actually present in the bootloader (aboot partition).. (To get rid of that, you either need to patch it up to set the timeout to 0, or you may have to unset the unlock & tamper bit similar to this.. And, I'm not doing this, since I don't own a Robin as of now)
Hit the Thanks :good: button if it worked for you
You are welcome to post the splash images that you created (along with the picture)..
Awesome. Thanks for this.
Made these from a few images i found on google so all credit goes to the original owners and the OP of course.
[Flashable zip]
BTW @GokulNC the battery image does not change when building the logo. This could be because of newer firmware maybe and updated image? Whatever it is I'd love to help test whatever fix that could be implemented
Now if only we could figure out how to remove the annoying pestering startup warning about unlocking the device
AnierinB said:
BTW @GokulNC the battery image does not change when building the logo. This could be because of newer firmware maybe and updated image? Whatever it is I'd love to help test whatever fix that could be implemented
Click to expand...
Click to collapse
I'm not sure.. I just found a battery pic in it and put it as it is..
Maybe it's loaded from the boot.img (unpack it and check it out)
Jacobwitt said:
Now if only we could figure out how to remove the annoying pestering startup warning about unlocking the device
Click to expand...
Click to collapse
Try locking the bootloader and see if still that warning persists..
Code:
fastboot oem lock
If that didn't help, send the aboot partition of your device (Both stock locked aboot and unlocked one)..
I'll check that out..
AnierinB said:
Made these from a few images i found on google so all credit goes to the original owners and the OP of course.
[Flashable zip]
Click to expand...
Click to collapse
made that my new wall paper lol.
souphail said:
made that my new wall paper lol.
Click to expand...
Click to collapse
Here is the updated Logo and wallpaper. Added a basic ether compound (Device Code-name is ether) and rearranged some things,
So I noticed another bug that is pretty interesting.. when you don't use a battery logo and just the logo.png the battery logo shows stock boot logo (when battery dies and then plug in) even though its not in my pics folder.. must be another instance of it in the splash.img
I just watched this and thought I was on my thread for a second xD Nice video man!
But for future reference it's pronounced A-NY-RIN, but don't worry everyone gets it wrong haha.
Alexenferman is not responsible for any damages or bricks made to your device. Please do some research if you have any concerns about rooting, its features and downsides. You are choosing to make these modifications, you should blame yourself for any mistakes you make.
Rooting may require a factory reset, please backup your data. Rooting will void your device warrany. By rooting your device, you will not be able to install OTA updates on your phone.
US carrier specific devices such as Verizon and Sprint might not be bootloader unlockable, therefore, not rootable.[/B]
You will need:
Platform Tools (Download from here)
Motorola Drivers
Windows or Linux PC
Bootloader Unlocked Moto E 2020
Your phone must be bootloader unlocked. Rooting your phone and not unlocking the bootloader will result in a soft brick.
Download the latest Magisk Manager APK from Github: https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.0/MagiskManager-v8.0.0.apk
Install the APK file. Make sure to enable "Unknown Sources" in the Settings app
Patching the boot image
To retrieve the boot image in order to patch it, you will need to download the stock ROM for your specific variant.
Download the ROM from your variant from here: https://mirrors.lolinet.com/firmware/moto/ginna/official/
To check which region is your device, go to Settings > About Phone > Software Channel.
After downloading, open the ROM zip file with an archive manager.
Extract the boot.img file only.
Transfer the boot.img file on your phone.
On your phone, open the Magisk app.
Select "Install" > "Install" > "Select and Patch a File"
Locate the boot image in the internal storage on your phone. Select the boot.img file.
Transfer the magisk_patched.img file on your computer.
Rooting the device
Boot the device into fastboot mode by holding the [Volume Down] and [Power] buttons.
Connect your phone to your PC.
On your PC, open a fastboot console window.
Type:
Code:
fastboot devices
Your phone serial number should be displayed along with the word "fastboot" or "device" in the console.
Now, type the following commands:
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Replace patched_boot.img with the path to your boot image we patched previously.
To reboot the device, type:
Code:
fastboot reboot
Once the device rebooted, open the Magisk app.
If you see the "Magisk is installed" message, you have successfully rooted your device!
You are done!
To view instructions with images, follow these instructions: https://www.alexenferman.com/articles/MotoE2020/root-moto-e-2020-magisk
I can confirm this works, I was about to give up on root or TWRP until I saw this. I'm now rooted, but I still can't find a download link for the latest TWRP for the Ginna model.
Hypercore said:
I can confirm this works, I was about to give up on root or TWRP until I saw this. I'm now rooted, but I still can't find a download link for the latest TWRP for the Ginna model.
Click to expand...
Click to collapse
Me neither, can anyone provide a TWRP for ginna?
I eventually found it after a ton of digging. I've uploaded it to my drive to assure the link stays active for anyone else who may need it.
For peace of mind, here's the VirusTotal scan HERE.
And here is the link to twrp-3.4.0-10_0-ginna HERE.
Hypercore said:
I eventually found it after a ton of digging. I've uploaded it to my drive to assure the link stays active for anyone else who may need it.
For peace of mind, here's the VirusTotal scan HERE.
And here is the link to twrp-3.4.0-10_0-ginna HERE.
Click to expand...
Click to collapse
Confirmed working. Tyvm!
Before I brick my phone. Can anyone confirm if the Tracphone version XT2052DL is rootable?
I'd like to know, too. Can we root our Tracfone XT2025DLs? Anyone successful?
dragonfire0501 said:
Before I brick my phone. Can anyone confirm if the Tracphone version XT2052DL is rootable?
Click to expand...
Click to collapse
Ranthalion75 said:
I'd like to know, too. Can we root our Tracfone XT2025DLs? Anyone successful?
Click to expand...
Click to collapse
I have one too and I've tried to unlock the bootloader however Motorola's website says the bootloader for this phone is not unlockable. It seems like this is what's preventing me from being able to install a different firmware like the stock one or root the device.
I do not know if there is any sort of workaround for this
For some reason on a Moto E, after rescuing using the Moto rescue assistant and then using
you guys can also use OFox Recovery and swipe magisk to root
Thank you. I used this guide to root my Moto E
QPGS30.82-135-2_Root.img
This method works well for QPGS30.82-135-2, but I just attempted it with QPGS30.82-135-9 and unfortunately the Magisk patched boot image will not work. I tried it 3 times, re-patching boot image each time. I suppose Motorola updated something in android to block this?
i can't get this to work at all, i cannot find a matching stock firmware being qpg30.82-135, there's no extra S and nothing else after the 135, got this phone from my motorola insiders rewards and now it's bootlooping after trying the 135-2 patched image
Has anyone been able to root and hopefully install a custom recovery on the lastest update? Mine is QPGS30.82-135-14, and so far I've only been able to get orangefox to boot but couldn't get it to decrypt my storage or install magisk. I tried twrp first, but to no avail, touch screen still doesn't work on it, so now I'm asking on a few different threads for this phone lol. Any help would be great!
Do you know of an updated method to get it to flash correctly? I was able to boot into ofox, but couldn't get it to properly flash. Ended up stuck on a screen that said my phone was unlocked and couldn't be trusted and that it'll reboot in 5 seconds. I don't know much about ofox either, been using twrp for years lol, it looks too different. Anyhow, any help would be appreciate much!
ace120ms said:
you guys can also use OFox Recovery and swipe magisk to root
Click to expand...
Click to collapse
You have to fastboot boot it anyway I don't have this phone anymore so idk
bouyakasha said:
This method works well for QPGS30.82-135-2, but I just attempted it with QPGS30.82-135-9 and unfortunately the Magisk patched boot image will not work. I tried it 3 times, re-patching boot image each time. I suppose Motorola updated something in android to block this?
Click to expand...
Click to collapse
I have the same problem with QPGS30.82-135-9. I can't get it to boot after Magisk patched boot image.