I have made some Boot Logos for Motorola phones and would like to share them with the community.
Although the project was initially for Moto G5 Plus (Potter), I have made all versions with the text motorola on the boot images.
Features :
N/A hidden
Redesigned bootloader menu
Some other minor changes in boot logo images
These Boot Logos can also be flashed to other Motorola Devices with 1080X1920 screen resolution like:
Moto G4
Moto G4 Plus
Moto G5
Moto G5s
Moto G5s Plus
Moto X4
Moto Z2 Play
Other Motorola phone users may use the version of the boot logo with motorola written on the image instead of moto g5 plus.
Use VX.0_BL_9-3_by_4 Zip for Moto G5 Plus.
Use VX.1_BL_9-3_by_4 Zip for other Motorola devices.
The file names with DT at the end stand for Boot Logos suited for Dark Theme.
All Boot Logos have been posted on SOURCEFORGE and more would be added in the coming future. The designs have been separated into two folders and further organized inside each folder by version numbers starting with V1. All the zips are functionally the same and you can flash whichever version you like. The only difference is in the text shown on the Boot Logo image. Head down for viewing previews and downloading the boot logos.
How to Install (via Custom Recovery)
Download the desired ZIP file to your phone
Boot to your Custom Recovery
Go to Install
Go to the location where you have saved the ZIP file
Install the ZIP file and reboot
How to Install (via Fastboot)
Download the desired ZIP file to your PC
Extract logo.bin from the zip file into your adb folder on your PC
Boot to Fastboot
Enter these commands in adb: fastboot flash logo logo.bin
Reboot
Boot Logo Previews
Boot Logo Downloads
If you are unable to download from SOURCEFORGE on your phone, request desktop site from your browser menu to enable download.
Credits: Thanks to the versatile tool made by CaitSith2 for enabling users to customize their phones for all these years.
Disclaimer: Motorola Logo and Batwing Logo is owned by Motorola Inc. Some of the artworks are not entirely my own creation.
Nice work boi
marshmello_61 said:
Nice work boi
Click to expand...
Click to collapse
Thank you bro!
It may be me, but I've been searching your files for the correct one with no luck. Been wanting your dark version for the Moto G5s Plus, but can only find moto g5 plus... which are not compatible. Potter will not install on a Sanders phone. This is the Sanders forum.
Can you please link me to the dark version boot logo for Moto G5s Plus (Sanders)? Thank you so much
Edit: 9-3_by_4_V3.1DT.zip is not available on Sourceforge desktop site.
JJ5150 said:
It may be me, but I've been searching your files for the correct one with no luck. Been wanting your dark version for the Moto G5s Plus, but can only find moto g5 plus... which are not compatible. Potter will not install on a Sanders phone. This is the Sanders forum.
Can you please link me to the dark version boot logo for Moto G5s Plus (Sanders)? Thank you so much
Edit: 9-3_by_4_V3.1DT.zip is not available on Sourceforge desktop site.
Click to expand...
Click to collapse
No, it is not your fault. I have revised the entire catalogue and changed the original post too. My naming scheme had become too convoluted. Also some zips were not flashing so I pulled all files and uploaded fresh. The file you are searching is this: https://sourceforge.net/projects/pr...ola Series/V3/V3.1DT_BL_9-3_by_4.zip/download
Functionally boot logo for moto G5 plus is same as that of Sanders. But since non Potter users won't like moto G5 plus written on boot screen, I made one with Motorola for everybody to use.
The ones you need are in Motorola Series folder on sourceforge. You can visit via the links on original post.
The imgur post has been updated to reflect the correct names. Thanks for pointing it out.
Announcement
New Boot Logo Added : V5
Preview (Light Theme): https://imgur.com/VXyH5c3
Preview (Dark Theme): https://imgur.com/0BXYqfF
Download from SOURCEFORGE: https://sourceforge.net/projects/project-9-three-by-four/files/Boot Logo/Motorola Series/V5/
Related
[Guide] How to install TWRP & root Lenovo Vibe B A2016A40 (single & dual SIM version)
Here's how I rooted my phone. This assumes some previous knowledge of using ADB and TWRP. If you need to, I strongly recommend SIM-unlocking your phone BEFORE you do this - I used this ebay service which cost £1.99 and I received the codes 36 hours later.
Please note that although this worked on my phone, I accept no responsibility if you brick your phone doing this
1. Update your ROM to the latest version, open Settings -> About and tap on Build Number seven times to enable Developer options then check USB debugging & OEM unlocking of the bootloader.
2. Connect your phone to your PC, start ADB and type adb devices - this will bring up a prompt on your phone that you need to respond to. Type adb reboot-bootloader
3. Once in bootloader mode, type fastboot oem unlock. Hit the Volume Up key to confirm.
4. Disconnect the phone from the PC and pull the battery for at least 3 seconds.
5. Download the SuperSU flashable zip https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip and copy it to a microSD card and insert it in the phone.
6. Download TWRP recovery to your PC http://www.mediafire.com/file/4hb66m26kfkw9qt/twrp.img and copy it to the same folder as your ADB (I use Minimal ADB & Fastboot https://androidmtk.com/download-minimal-adb-and-fastboot-tool ).
7. Start the phone in bootloader mode by holding the Power and Volume Up buttons together until you see white text on the screen. Use the Volume Up button to navigate to Fastboot then select it by pressing Volume Down. Connect the phone to your PC.
8. Type fastboot flash recovery twrp.img
9. Disconnect the phone from the PC and pull the battery for at least 3 seconds.
10. Start the phone in Recovery mode by holding the Power and Volume Up buttons together until you see white text on the screen. Use the Volume Up button to navigate to Recovery then select it by pressing Volume Down.
11. You should then see TWRP starting. Tick the box to agree then swipe the blue button to the right.
12. Tap on Wipe then Format Data. Do not miss out this step or TWRP won't be able to mount the /data partition.
13. Tap the Back button then Factory Reset and swipe the blue button to start.
14. Tap the back button then Install then Select Storage -> microsd card then your SuperSU file then swipe the blue button to the right to flash it.
15. Tap on Reboot System and your phone should boot to your newly rooted OS! Don't panic if the first boot takes 5 or 10 minutes. If it gets stuck, pull the battery & try again.
16. Make sure you disable System Updates as they will no longer work with the non-stock recovery. Hopefully it shouldn't be too long until there's an AOSP or LineageOS ROM for this phone
Thank you
This worked like a charm - although I was hesitant knowing there would be no way back, would it?
It *should* be possible to extract the stock recovery from a recent stock firmware - I just haven't found any (my phone came with S219, and was upgraded to S235 prior to rooting). That in theory would open the path to a stock upgrade, if one would like to have it.
Re LineageOS: There's an unofficial build for a codename 'al732row' but I'm in doubt this would match a dual-sim A2016a40. I'll wait for another update or two (three releases within 72 hours, then 2 weeks silence?).
For now I won't complain: this was a bargain even without LinOS - those dirt cheap devices often get stuck with Lollipop.
Another edit: The Nougat LineageOS ROM by CarlosArriagaCM (http://www.cyanogenmods.org/forums/topic/lineage-os-14-1-vibe-b-al732row-nougat-7-1-rom/) seems to be limited to the LATAM version of the B (aka A2016b30). For A2016a40 (EMEA version) no cigar
steve8x8 said:
This worked like a charm - although I was hesitant knowing there would be no way back, would it?
It *should* be possible to extract the stock recovery from a recent stock firmware - I just haven't found any (my phone came with S219, and was upgraded to S235 prior to rooting). That in theory would open the path to a stock upgrade, if one would like to have it.
Re LineageOS: There's an unofficial build for a codename 'al732row' but I'm in doubt this would match a dual-sim A2016a40. I'll wait for another update or two (three releases within 72 hours, then 2 weeks silence?).
For now I won't complain: this was a bargain even without LinOS - those dirt cheap devices often get stuck with Lollipop.
Another edit: The Nougat LineageOS ROM by CarlosArriagaCM (http://www.cyanogenmods.org/forums/topic/lineage-os-14-1-vibe-b-al732row-nougat-7-1-rom/) seems to be limited to the LATAM version of the B (aka A2016b30). For A2016a40 (EMEA version) no cigar
Click to expand...
Click to collapse
You can flash the dual-SIM stock ROM using SP Flash Tools so you're never going to end up with a bricked device
Thank you much. I rooted, installed twrp and i updated TWRP to 3.1.0-0
https://forum.xda-developers.com/android/development/recovery-3-1-0-0-lenovo-vibe-b-t3603304
Any custom rom available for Lenovo Vibe B (A2016A40 version)?
Best Regards,
Vlad
@dwl99 ?
Vlad Paul said:
Thank you much. I rooted, installed twrp and i updated TWRP to 3.1.0-0
https://forum.xda-developers.com/android/development/recovery-3-1-0-0-lenovo-vibe-b-t3603304
Any custom rom available for Lenovo Vibe B (A2016A40 version)?
Best Regards,
Vlad
@dwl99 ?
Click to expand...
Click to collapse
Not that I can find. There is one for the a2016b30 but the camera doesn't work.
There's a new (20170614) release. Still there's "E3004: This package is for device: al732row,A2016b30" in the updater-script. Should we invite Carlos to Europe?
(And there should be a ROM thread for this device. Last time I checked there was none.)
steve8x8 said:
There's a new (20170614) release. Still there's "E3004: This package is for device: al732row,A2016b30" in the updater-script. Should we invite Carlos to Europe?
(And there should be a ROM thread for this device. Last time I checked there was none.)
Click to expand...
Click to collapse
Hi! Do you have a2016a40 model? Wich TWRP you have installed, 3. 1.0-0 ? Not working latest rom build?
steve8x8 said:
There's a new (20170614) release. Still there's "E3004: This package is for device: al732row,A2016b30" in the updater-script. Should we invite Carlos to Europe?
(And there should be a ROM thread for this device. Last time I checked there was none.)
Click to expand...
Click to collapse
@Carlos Arriaga replied me will release a new fixed build soon. I hope will working on our model of phone a2016a40.
Look his reply here:
https://forum.xda-developers.com/showthread.php?p=72692660
steve8x8 said:
There's a new (20170614) release. Still there's "E3004: This package is for device: al732row,A2016b30" in the updater-script. Should we invite Carlos to Europe?
(And there should be a ROM thread for this device. Last time I checked there was none.)
Click to expand...
Click to collapse
New build release on 19.06. 2017. Working on model a2016a40?
Short answer: No, no change between 0614 and 0619.
Long answer: You may check this yourself: Open the ZIP file in your favourite archiver tool, and extract the file META-INF/com/google/android/updater-script, then inspect the first line (assert()) for A2016a40.
Disclaimer: Even if the new ROM would be accepted by an A2016a40 I couldn't test it right away (no access to the device anymore / yet again).
steve8x8 said:
Short answer: No, no change between 0614 and 0619.
Long answer: You may check this yourself: Open the ZIP file in your favourite archiver tool, and extract the file META-INF/com/google/android/updater-script, then inspect the first line (assert()) for A2016a40.
Disclaimer: Even if the new ROM would be accepted by an A2016a40 I couldn't test it right away (no access to the device anymore / yet again).
Click to expand...
Click to collapse
Thank you for reply @steve8x8 . No luck for a2016a40 users
assert(getprop("ro.product.device") == "al732row" || getprop("ro.build.product") == "al732row" || getprop("ro.product.device") == "A2016b30" || getprop("ro.build.product") == "A2016b30" || abort("E3004: This package is for device: al732row,A2016b30; this device is " + getprop("ro.product.device")
Click to expand...
Click to collapse
I hope to help us @Carlos Arriaga
I'm somewhat afraid there'll be only one way to get @CarlosArriaga to support the a40 variant: purchase one (70€), send it to him (almost same amount). Any volunteers?
steve8x8 said:
I'm somewhat afraid there'll be only one way to get @CarlosArriaga to support the a40 variant: purchase one (70€), send it to him (almost same amount). Any volunteers?
Click to expand...
Click to collapse
Sorry, im homeless, i don't have 1 dolar to eat something.
I found a comparison of the two sub-models: http://www.phonemore.com/compare/phones/lenovo-vibe-b-a2016b30-vs-lenovo-b-a2016b40/4710928 - most prominent difference is 3G and LTE bands, but I'd presume this would be handled by the modem part of the firmware (which isn't part of LineageOS).
If I could get my hands on FCC documents (although I'm in doubt that a40 and b30 would have separate ones) I'd have a closer look.
Any pointers to stock firmware are welcome (but if that comes in MTK format I'm lost I'm afraid).
If I were @CarlosArriaga I'd check too for the model of phone I know, even with a disclaimer in 96pt.
But: nobody stops you from modifying the updater script to include the other model (and as the OP said, with MTK flash tools recovery from a bad flash would be easy - if you got the stock firmware, that is).
Due to lack of the actual hardware (for yet a few months) I'm limited to speculating and using a magnifying glass on the code itself - if time permits.
Does the ZTE Blade A510 look very similar to the Vibe B? Almost identical characteristics, same CPU type? There are rumours about LineageOS support planned for the Blade.
Answering myself: an A510 scatter file I came across shows more partitions than the Vibe has, so this may be close but not close enough.
ZTE has a device called A2016 though. Coincidence?
steve8x8 said:
Does the ZTE Blade A510 look very similar to the Vibe B? Almost identical characteristics, same CPU type? There are rumours about LineageOS support planned for the Blade.
Answering myself: an A510 scatter file I came across shows more partitions than the Vibe has, so this may be close but not close enough.
ZTE has a device called A2016 though. Coincidence?
Click to expand...
Click to collapse
Nothing new for our model a40? No chance to develop @Carlos Arriaga a LineageOS build for this model? The developer is very quiet.
Hello,
Sorry my english I use a translator.
TWRP & root Lenovo Vibe B A2016A40, instructions very good.
But there is no unofficial Android 7 for Lenovo Vibe B A2016A40?
For Lenovo Vibe B A2016A30 gives Android 7. I know that.
Unfortunately, my smartphone Lenovo Vibe B A2016A40 does not.
Twrp error reports installation. Error 7.
TWRP (3.1.0-0 at least, I didn't upgrade to 3.1.1) installed properly on the A2016a40. The check for the model in the updater script is what gives you an error (is there a translation table to lookup the value of 7 you got?).
As had been said before, it's possible to change the updater script to skip the check and repackage the zip, but nobody knows yet what will happen to your phone, and whether it can be restored using SP Flash Tool. We all are keen to learn about this...
(reply removed)
Hi, I want help in unbricking the Moto e2 as there is no know way to unbrick the device except blank flash file. I want you to make a way to unbrick our devices as in this thread all developer will make new roms. I just want you to make a way to unbrick our devices.
Ex:-mmcblk0,qfil.....
Please all developer make a way to unbrick our devices.thanks in advance.
What I did was download rom and use fastboot to flash the part I messed up. In my case the recovery and boot. There is also the Moto tool and the moto e 2015 tool. Haven't tried them but they have options for it. No links as it has been a while since I messed with my Moto e. You should be able to find them through search here or on Google.
Hey guys. I've been in touch with Motorola about my bricked Moto G6, and they seem way too incompetent to simply provide me with a blank-flash file for my device. Allow me to begin by copy pasting the paragraph i typed to Motorola.
"Hi. I am in search of the Blank-flash file for the Moto G6 XT1925-6. Lenovo seems to be very bad at understanding what the blank-flash file actually is which is sad when you take into consideration that they developed the software for the device. Again, to clarify, it is the BLANK FLASH file for the device, not the ROM. I am not attempting to unlock the boot-loader as it has already been unlocked (motorola seems to think this is what i want to do as well and are refusing to support me in unlocking the boot-loader). I repeat, I am in search of the B L A N K F L A S H file for the moto G6 XT1925-6. If somebody out there could either extracty theirs from their device and send it over, or better yet, one of the bright minds over at Motorola who designed the device could graciously bless me with a small piece of their software so I can enjoy their phone again, that would be great. Please do respond as soon as possible. I have provided a blank-flash file as example so you don't get too confused, as well as the blank-flash folder I am using which will actually contain logs about the attempted flash of the blank flash file. I attempted to use the blank-flash file from Android PIE, as you can see it is labeled PPS and not OPS.
AGAIN, since this seems to be so difficult for motorola to understand, it is the blankflash file i am in search of, not the method to unlocking the boot-loader. Thank you."
The device is being detected in Windows 10 as a Qualcomm device which suggests it is still possible to flash it with a blank-flash file in order to reach fast-boot and re-flash the stock firmware.
NOPE see below
I have been searching for this little piece of software for over a week only to fine the blank-flash files for the G6 PLUS and PLAY versions, not just the mid-range G6 model. Below, as promised to be included, is the blankflash file i was attempting to use which does contain logs of the attempted flash. For ease's sake i have also provided a link to just the logs so you don't have to extract the rar.
Logs: NOPE see below
Blankflash file attempted to use: NOPE see below
Thank you for taking the time out of your day to search for this file. I'd love to start actually using the Moto g6 again rather than using it as a paperweight and relying on my Samsung J3 Orbit as a main driver. Sad.
EDIT: even SADDER, I have been prevented from providing crucial informational links aiding in resolving the issue due to XDA policy. If you would like these links, you're going to have to obtain them from me elsewhere (unless i circumvent the policy and post them in a broken link like suuuuch.)
https ://pastebin.com/QE6UBZq6
I also need a blank flash file for moto G6. we can find the flash file of G6 play and plus but not mid-range Moto G6. It's not fair My phone was dead after OTA update and now it is a totally useless piece of ****. If we get that small blank flash file then we may bring our devices back to life. Please help us.:crying::crying:
error blankflash
Hi guys, have you solved it?
running the file I get this error: sahara download()-io error
dibarbosaa said:
Hi guys, have you solved it?
running the file I get this error: Sahara download()-io error
Click to expand...
Click to collapse
No, still searching for a solution and yes the existing blank flash file gives us that error. So we need to wait for another working one.:crying:
Приветсвую привратники здравого смысла!
Hello dear happy owners of Moto G6 bricks.
Please, would you be so kind as to accept me into your team of elite owners of useless nutcrackers based on the Motorola Moto G6.
My XT1925-5 device was also hardbricked, after upgrading to Android 9.0 Pie and installing the latest security updates.
Also, when trying to flash the blankflash_PPS29.26 utility.bat receive
error: Sahara Download IO Error.
Email me if there are any positive results when getting a smartphone memory dump and creating a new blankflash for the latest OTA.
This is my contact email ([email protected]) if there are people willing to collaborate to write a new Blank Flash together.
I have to admit, when I joined XDA not long ago, I thought my easily bricked Moto G6 Play (Jeter) was a special case or that I was uniquely special when it comes to comatosing devices. Now, a few months and several more limping devices later, I see there truly is a seemingly growing mass of useless Motorola Moto owners out there. Whats worse is the Lenovo/Motorola Rescue Assistant wont rescue me because the Baseband and IMEI are erased on my device. Guess its time to take the next big step...invest in another G6 and see how long it is before I tater that one too!
Any news here, guys?
So, have anyone tried Android 12 on haydn?
Note : Works with K40 Pro as well thanks to @makiothekid
Refer second post
Here are the bugs from Xiaomi Global Community
Mi 11i/Mi 11X Pro:
1."Earphone" icon doesn't show in status bar when earphone is inserted.
2.Unable to find TV device in Cast.
3.There may be crashes after making an emergency call and checking the call records.
(source)
--------------------------------------------------------------
Wanna try it?
Here's Android 12 (AOSP)
Here's the guide from XDA Developers
UNLOCK YOUR BOOTLOADER
MIGHT BRICK YOUR PHONE SO DO IT AT YOUR OWN RISK
How to flash Android 12 betaThe Android 12 beta ROM comes in the form of a .tgz extension, commonly referred to as a Fastboot ROM. To flash this ROM, you also need to have a Windows PC and phone with an unlocked bootloader. Instructions to unlock the bootloader of your phone can be found on your device’s subforums on XDA.
To flash the downloaded file, follow the instructions below:
Download the MiFlash Tool on your PC that can be found here. After downloading, extract the tool and install it. It is also advised to have ADB and Fastboot installed.
Reboot your phone into Download mode by powering it off and then pressing both the Power and Volume Down buttons together.
Connect your phone to the computer using the USB cable.
Download the Fastboot ROM .tgz file and extract it and make sure you remember the extract location, as you will need to paste the address into MiFlash Tool. Make sure there are no spaces in the extract location path.
Run MiFlash Tool on your PC and in the address bar within the tool, paste the extract location from Step 4.
Click “Refresh” within MiFlash and the app should automatically recognize your device.
Click “Run” within MiFlash to flash the ROM file to the device.
The progress bar within MiFlash will turn green, which indicates that the ROM was successfully installed. Your device should boot automatically to the new version.
------------------------------------------
Can i flash it on my K40 Pro?
Edit1: Just flash it on K40 Pro/Mi 11i. Lack of features compare official Pixel Devices.
No new quick setting menu, can't change accent colors, icon shape and fonts. Change can't screen framerate to 122hz. But it's a clean firmware compare with MIUI.
I can recommend this for people refer stock firmware over MIUI or want to review and send it to google.
I can't not recommend to flash in this stage, if it's your main devices. Nothing happen to my device though, just a precaution
Edit2: Successfully rooted without any problem.
Edit3: Magisk can be install but not work yet. Battery seem to be way better than Stock MIUI
makiothekid said:
Can i flash it on my K40 Pro?
Edit1: Just flash it on K40 Pro/Mi 11i. Lack of features compare official Pixel Devices.
No new quick setting menu, can't change accent colors, icon shape and fonts. Change can't screen framerate to 122hz. But it's a clean firmware compare with MIUI.
I can recommend this for people refer stock firmware over MIUI or want to review and send it to google.
I can't not recommend to flash in this stage, if it's your main devices. Nothing happen to my device though, just a precaution
Edit2: Successfully rooted without any problem.
Edit3: Magisk can be install but not work yet. Battery seem to be way better than Stock MIUI
Click to expand...
Click to collapse
For your 1st point, it's just Android 12 rom for our device in order to test the compatibility, don't expect it will have Pixel's exclusive features. #3 surprise me, and Xiaomi should feel embarrassing about that.
khanhdx said:
For your 1st point, it's just Android 12 rom for our device in order to test the compatibility, don't expect it will have Pixel's exclusive features. #3 surprise me, and Xiaomi should feel embarrassing about that.
Click to expand...
Click to collapse
About #3 12 hours at work and i still have 68% of juice left.
note about battery life.. I'm seeing about the same longevity compared to MIUI with MIUI optimisations turned off. couldn't quite understand why it drained so quickly with optimisations on
bit disappointed we're not seeing the fancy new ui in this version of the beta for the 11i
Greetings, I'm developing an application to install twrp on any Motorola G series, it's an autorun application that aims to facilitate the installation of the twrp image on these devices, through it you can choose the twrp model and version that you want to install on your device, it automates the entire installation process for you, the only thing you need to do is connect your device in bootloader mode to the pc and run the executable.
I plan to add support for all Motorola G-line handsets, currently the only supported handsets are as follows:
• Moto G1 (2013)
• Moto G1 (2013) 4G
• Moto G3
• Moto G4 (Play and Plus)
• Moto G5 (all variants)
• Moto G6 (all variants)
• Moto G7 (all variants)
• Moto G8 (Plus and Power)
• Moto G9 (Power)
I've tested it on some devices like G5 and G7, but I need someone who can test it on other devices.
The procedure is very simple, I leave the project link available on github:
- https://github.com/AndersonLeandrog/RunTWRP
How to use
1. Download the autorun and then extract all its content to your desktop.
2. Connect your mobile phone to computer via bootloader.
3. Open the extracted folder and run the 'autorun' file.
4. Follow the procedures on the console if you do not have Motorola drivers installed, select an option according to your system, if you have already select the 'Do not install' option in the console.
5. Select the model of the device you want to install twrp on, through its numbering in the list
6. Next select the version of TWRP you want to install on your Motorola. (The files will be downloaded directly from the official TWRP server - twrp.me)
7. After selecting the version wait for the TWRP installation process on your device, if everything runs normally a success screen will be displayed on the console.
I'm grateful if anyone can return any feedback to me.
That's awesome news !
Glad to know that new people want to keep our devices alive !
Thank you so much for this !
Damage1972 said:
That's awesome news !
Glad to know that new people want to keep our devices alive !
Thank you so much for this !
Click to expand...
Click to collapse
I'm glad you liked it, I had this project in my drawer and I had some free time to continue it, soon all devices will be supported!
Does it support the G5S plus (sanders)?
Great project... Does this require root access?
I hope this works for me moto g6 play.