Related
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!
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.
This bootlogo is very simple, it basically is a pixel bootlogo as a complement for the pixel bootanimation. This is my first creation(not really, I just took the first frame of the appropriately sized pixel bootanimation and slapped it wherever possible). I think it hides the N/A or bad key on the boot screen better than the original logo so it should look like you never unlocked in the first place
to flash just reboot to bootloader and type in cmd(or terminal)
Code:
fastboot flash logo logo.bin
ap4ss3rby said:
This bootlogo is very simple, it basically is a pixel bootlogo as a complement for the pixel bootanimation. This is my first creation(not really, I just took the first frame of the appropriately sized pixel bootanimation and slapped it wherever possible). I think it hides the N/A or bad key on the boot screen better than the original logo so it should look like you never unlocked in the first place
to flash just reboot to bootloader and type in cmd(or terminal)
Click to expand...
Click to collapse
Where is the file?
Railsonsan said:
Where is the file?
Click to expand...
Click to collapse
Seems I forgot to attach it, check it out
So my google pixel has been boot looping the past couple days now.
I've read that many others have had this issue, but none of that has helped. First I tired factory resetting it using the recovery mod, then I reloaded the latest factory image using my computer.
Honestly I don't know what else to try.
The cycle is usually as followers. Warning screen - logo screen - repeat.
After a few times i got the EX4 file screen but then it just repeats some more.
It is unlocked but that's it, never got around to doing anything else with it.
If anyone can help me it'd be greatly appreciated, really don't wanna have to buy a new phone ya know.
Leo226 said:
So my google pixel has been boot looping the past couple days now.
I've read that many others have had this issue, but none of that has helped. First I tired factory resetting it using the recovery mod, then I reloaded the latest factory image using my computer.
Honestly I don't know what else to try.
The cycle is usually as followers. Warning screen - logo screen - repeat.
After a few times i got the EX4 file screen but then it just repeats some more.
It is unlocked but that's it, never got around to doing anything else with it.
If anyone can help me it'd be greatly appreciated, really don't wanna have to buy a new phone ya know.
Click to expand...
Click to collapse
Go here:
[Guide] Pixel XL Android 9.0.0 (Pie) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + August 2018 Security Patch
Do #4 then #8.
Homeboy76 said:
Go here:
[Guide] Pixel XL Android 9.0.0 (Pie) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + August 2018 Security Patch
Do #4 then #8.
Click to expand...
Click to collapse
For #4, Flash all command doesn't work. But I can manually run the batch file, That's how I've tried doing doing it before.
The one I've been using is "marlin-ppr1.180610.010-factory-3b90270c.zip" I assumed it was the most recent one although "marlin-ppr1.180610.009-factory-90a4fa8b.zip." seems like it is just as recent.
Am I supposed to use some how both?
For #8 Simply doesn't work, just says Error: Cannot load 'twrp.img'.
Any actual detailed guides on this stuff? Because honestly it's just a confusing mess, seems like I'm doing it right. But clearly I'm not.
Leo226 said:
For #4, Flash all command doesn't work. But I can manually run the batch file, That's how I've tried doing doing it before.
The one I've been using is "marlin-ppr1.180610.010-factory-3b90270c.zip" I assumed it was the most recent one although "marlin-ppr1.180610.009-factory-90a4fa8b.zip." seems like it is just as recent.
Am I supposed to use some how both?
For #8 Simply doesn't work, just says Error: Cannot load 'twrp.img'.
Any actual detailed guides on this stuff? Because honestly it's just a confusing mess, seems like I'm doing it right. But clearly I'm not.
Click to expand...
Click to collapse
Well first your bootloader is definitely unlocked correct? I assume it is because you did say you saw the warning screen but I like to err on the side of caution. Second, you're saying that when you plug the phone into the PC that it is recognized and you are able to run commands via fastboot right? If you can run commands, but certain commands aren't working properly, I would say that it is your version of the platform tools and that you need to make sure you have the latest version. Platform tools is the folder that usually houses ADB and fastboot along with the other files necessary. These are updated occasionally and I know for a fact that outdated versions do cause issues sometimes. The next step if you can run commands would be to try a different USB port on the PC. Some ports are different when comparing the back and front and top ports. If none of that seems to do anything I would say lastly to try a different USB to USB C plug. I'm only listing all of these things because I've had to go through all of these issues myself at one point or another, but I do hope it's something simple.
I didn't mention this but obviously the files that you're flashing with fast boot have to be in the same folder as fastboot, I don't know your level of knowledge and expertise so I don't mean to sound condescending I just wanted to make sure I added that.
Leo226 said:
For #4, Flash all command doesn't work. But I can manually run the batch file, That's how I've tried doing doing it before.
The one I've been using is "marlin-ppr1.180610.010-factory-3b90270c.zip" I assumed it was the most recent one although "marlin-ppr1.180610.009-factory-90a4fa8b.zip." seems like it is just as recent.
Am I supposed to use some how both?
For #8 Simply doesn't work, just says Error: Cannot load 'twrp.img'.
Any actual detailed guides on this stuff? Because honestly it's just a confusing mess, seems like I'm doing it right. But clearly I'm not.
Click to expand...
Click to collapse
@Leo226;77325519
Verify bootloader unlocked: Turn phone off > Press Power and Volume Down keys (At the same time) until phone vibrates and you see 'Start'
The bottom line should read: ' device is Unlocked'
You missed a step.
Start over and take your time.
Use this factory image: marlin-ppr1.180610.009-factory-3b90270c.zip
Unless your Carrier/provider is Telus then use this one: marlin-ppr1.180610.010-factory-3b90270c.zip (Telus)
Do #4 - Install Factory Image 'keep' data
4C. Extract the factory Image to the platform-tools folder or the folder that has fastboot in it.
Then do #8.
The #8 error is because you either didn't copy the twrp file to the directory/folder with fastboot in it or you typed the command incorrect.
This is a detailed Guide
Homeboy76 said:
@Leo226;77325519
Verify bootloader unlocked: Turn phone off > Press Power and Volume Down keys (At the same time) until phone vibrates and you see 'Start'
The bottom line should read: ' device is Unlocked'
You missed a step.
Start over and take your time.
Use this factory image: marlin-ppr1.180610.009-factory-3b90270c.zip
Unless your Carrier/provider is Telus then use this one: marlin-ppr1.180610.010-factory-3b90270c.zip (Telus)
Do #4 - Install Factory Image 'keep' data
4C. Extract the factory Image to the platform-tools folder or the folder that has fastboot in it.
Then do #8.
The #8 error is because you either didn't copy the twrp file to the directory/folder with fastboot in it or you typed the command incorrect.
This is a detailed Guide
Click to expand...
Click to collapse
Sigh well everything is up to date most recent. Switched usb drives to see if it makes a difference.
Was not aware I needed to use the "09" factory image, been trying the "10".
So just flashed that, still in bootloop obviously, don't know if installing twrp would even do anything because as I said the command won't work..
It just says "cannot load 'twrp.img' . No such file exist"
The file is there, right in the platform tools folder with fastboot, adb and everything else. So not sure why it's acting like it's not.
Are their other files I need for it?
Check the properties of twrp.img and make sure it is named correctly.
Sent from my Pixel XL using Tapatalk
Leo226 said:
Sigh well everything is up to date most recent. Switched usb drives to see if it makes a difference.
Was not aware I needed to use the "09" factory image, been trying the "10".
So just flashed that, still in bootloop obviously, don't know if installing twrp would even do anything because as I said the command won't work..
It just says "cannot load 'twrp.img' . No such file exist"
The file is there, right in the platform tools folder with fastboot, adb and everything else. So not sure why it's acting like it's not.
Are their other files I need for it?
Click to expand...
Click to collapse
So, I'm going to 'assume' after updating everything and extracting the factory image to the folder with fastboot in it. You were able to use the flash-all.bat command. Yes?
Open Windows Explorer and make sure it is set to show the extension. The default is to not show the extension. Then look in the folder with the twrp file you renamed twrp.img. Does it look like this, twrp.img.img? If yes remove the last .img.
"Are their other files I need for it?" No.
Homeboy76 said:
So, I'm going to 'assume' after updating everything and extracting the factory image to the folder with fastboot in it. You were able to use the flash-all.bat command. Yes?
Open Windows Explorer and make sure it is set to show the extension. The default is to not show the extension. Then look in the folder with the twrp file you renamed twrp.img. Does it look like this, twrp.img.img? If yes remove the last .img.
"Are their other files I need for it?" No.
Click to expand...
Click to collapse
Correct, was able to flash by double clicking the batch file.
As for the twrp, yes already had made sure that the name was correct since I have had that issue with other things before.
"fastboot boot twrp.img" still does not work. I have even tried redownloading everything, placing them in it's own folder together, on and on. Nothing.
At this point I'm not even sure if installing twrp will even do anything though.
For my boot loop problem I thought just flashing the latest factory image would fix it. Clearly I was wrong.
Leo226 said:
Correct, was able to flash by double clicking the batch file.
As for the twrp, yes already had made sure that the name was correct since I have had that issue with other things before.
"fastboot boot twrp.img" still does not work. I have even tried redownloading everything, placing them in it's own folder together, on and on. Nothing.
At this point I'm not even sure if installing twrp will even do anything though.
For my boot loop problem I thought just flashing the latest factory image would fix it. Clearly I was wrong.
Click to expand...
Click to collapse
hi leo,
Have you fixed the bootloop issue yet? If yes, how?
My Pixel XL is now having same bootloop issue as yours, but my phone takes all fastboot cmds, and it just keep bootlooping.
If you just get trouble to touch the file twrp.img, I have some tips for you here:
1. I read that you are using Windows environment, so first right click the file "twrp.img", and make sure at bottom of the pop-up proprieties window, the file is not "locked", if you see it's locked, you can check the unlock box to unlock it. This is usually happen to downloaded files put in windows system partition;
2. I read that you double-click the flash-all.bat file to executive the command, please right-click on the file, and select "Run as Administrator", this way will make sure windows security policy won't prevent you from running all the cmds you intended.
3. If above 2 items you checked and not solve the twrp.img access issue, just try to download a new copy from internet again, and put in another partition folder, and repeat the above two steps. Or even try another PC/Mac.
Thanks,
Lei
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.