Related
Here is my full gui tool for creating boot logo files, for a number of Motorola Devices.
You get a preview of the picture, exactly how it would look on your device.
Features
Open Existing Logo.bin files
Open Existing Flashable zip files
Create logo.bin files
Create Flashable zip files
Export images from Logo.bin / Flashable zips.
Instructions
To use, you just double click on the treeview entries, select your picture, and repeat that process for all of the files that would be in logo.bin You then go to File / Save, and then save either as a .bin file, for flashing using fastboot, or as a Flashable zip file, for flashing using TWRP or CWM. In general, boot_logo is used on a factory locked device, and as a result, you probably should clear that one, as you would be wasting your space. logo_battery is your 0-3% indicator when the battery is run dry, and you plug it in to charge. logo_unlock is the actual boot screen logo you see on unlocked devices.
You can also open existing logo.bin files, wither from zip files, or directly, in order to modify them. Custom mode is for the advanced users, or for cases where a new Motorola device is released, where its logo.bin contains files that are not known. This tool auto-detects whether the file is the pre-kitkit format or not, and pictures that are larger than screen resolution, or in the case of pre-kitkat format, 540x540 is automatically scaled down. Upscaling options are provided, but centering the image is the default selection.
Bugs
None that I am aware of. If any are found, report them.
Limitations
The tool will not create any logo.bin files that are greater than 4MiB. This is a device limitation, specifically the logo flash partition is exactly 4MiB in size on all the known devices that I specifically support with this tool. As such, you may have to downscale or reduce the bpp formats of your images, to get them all to fit within the 4MiB. (Moto X Play has 6MiB, and Moto X Style has 8MiB).
Version History
Version 2.4 - Released Oct 21, 2015 - Download
All 3 Moto G listings merged into one listing, due to screen size and logo.bin size being the same across ALL 3 of them.
Updated the Moto E listing, with the 2nd gen, (no seperate listing due to both generations having same screen size, and same logo.bin max size.)
Older versions:
Version 2.3 - Released Oct 19, 2015
[new] Added Moto X Play, Moto X Style (Pure), and Moto G 3rd Gen to device list.
Moto X Play has a 6 MiB logo.bin size
Moto X Style (Pure) has a 8 MiB logo.bin size
Version 2.2 - Released Sept 15, 2014
[new] Metadata added to created logo.bin files - The following data is present.
Version of this program that created the bin file. (was present since Version 2.0)
Motorola Device Selected
Motorola Device Resolution
User Comment
Version 2.1 - Released Sept 9, 2014
[new] Default logo_charge image predefined, where applicable.
[new] logo_boot and logo_unlocked are now linked together, unless you load different images for each of them.
[new] Duplicate images loaded no longer wastes space in logo.bin
Version 2.0 - Released Sept 8, 2014
[new] Last selected device is now remembered between sessions.
[new] Added in Moto G 2nd Gen. (2nd gen does not have a logo_charge in its current firmware.)
[new] Added in Moto X 2nd Gen. (Larger screen in Moto X 2nd Gen, logo_charge and logo_lowpower present. The one thing that bugs me, is that motorola did not expand the logo partition size, still retains it at 4MiB for that device, so one is pretty limited in full screen picture complexity.)
[fixed] Fixed a few bugs that were introduced in Version 1.9
Version 1.9 - Released Sept 3, 2014
[new] Added in the stock images for logo_battery, logo_lowpower, and logo_unplug, that the program will put into the logo.bin, if you don't specify a custom logo for these images.
Version 1.8 - Released Aug 30, 2014
[changed] Turns out Moto G as of the Android Kitkat 4.4.4 OTA update supports logo_charge. Updated accordingly, and put a note in the tool tips on its use case.
Version 1.7 - Released Aug 24, 2014
[changed] Big performance boost of saving logo.bin/flashable zips.
Version 1.6 - Released Aug 22, 2014
[fixed] Fixed a null reference bug that happens if you switch logo.bin versions right from program startup, as well as a few other potential null reference bugs.
Version 1.5 - Released Aug 20, 2014
[changed] More improvements to the logo compression algorithm.
[new] Added Landscape mode
[new] Logo fill/Layout options can now be set per image, for example, logo_battery with fill on landscape, and logo_boot with center on portrait.
Version 1.4 - Released Aug 17, 2014
[changed] Made the device selector a combo box. Each device prepopulates the tree with the logo options available to it, as well as controlling what logo.bin formats are available.
[fixed] Corrected a bug in 540x540 color encoding/decoding.
[fixed] Corrected a bug where if 540x540 formats were selected, and you didn't pick an image for at least one of the logos, the process would error out with an exception.
[new] Added some info to the about box, regarding optional donations via bitcoin or paypal.
Version 1.3 - Released Aug 17, 2014
[changed] DotNetZip library now statically linked.
[changed] Source code now lives on Github
Version 1.2 - Released Aug 17, 2014
[new] Added Support for Raw 540x540x24bpp logo.bin format
[changed] No longer creates temp files for any of the processes.
[changed] updater-script and update-binary are now built in.
[fixed] Loading of images no longer locks them from being renamed/deleted till the program is closed. (They are loaded into program memory.)
[fixed] logo.bin can now be loaded from any zip file, even if logo.bin is not at root within that zip file, such as from stock firmware zip files.
[changed] Process of creating zip/bin now outright aborts if there was an error loading every image loaded in the process.
[changed] An opportunity to abort the process is presented if you try to save bin/zip with no images loaded.
[new] Tool tips now added on the tree nodes for logo_boot, logo_battery, and logo_unlocked. As I do not have a Moto E, I cannot determine what causes logo_lowpower and logo_unplug to show, to be able to advise on these.
[new] logo.bin and flashable zips can be dragged and dropped onto the application.
Version 1.1 - Released Aug 16, 2014
[new] Added Export Image
[changed] Far fewer temp files created, and the program attempts to clean up after itself.
[new] Progress info added on file loading
[fixed] Progress info runs smoother now.
[new] Now info is displayed as to how much logo.bin is too large by, when the selected images result in too large a logo.bin
Version 1.0 - Released Aug 15, 2014
Initial Release
XDA:DevDB Information
[APP] Motorola Boot Logo Maker, App for the Moto G
Contributors
caitsith2
Source Code: https://github.com/CaitSith2/MotoBootLogoMaker
Version Information
Status: Stable
Current Stable Version: 2.4
Stable Release Date: 2015-10-21
Created 2014-09-17
Last Updated 2015-10-21
Reserved
Is "logo_battery" the one that appears when the phone is at 0%?
And when does the "logo_unlocked" screen appear?
@caitsith2 ..... Very nice I've added thanks ..... I have been using caroc's script to create my logos and paint.net to modify the images ..... this App makes it much simpler :good:
rpcll said:
Is "logo_battery" the one that appears when the phone is at 0%?
And when does the "logo_unlocked" screen appear?
Click to expand...
Click to collapse
logo_battery is indeed your phone at 0% image. logo_unlock is typically the image you should replace, as that as the one that contains the unlock warning screen.
And when does the "logo_boot" screen appear?
When I boot my phone i see logo_unlocked screen
@caitsith2 ..... The comments I made in post #3 were made when I had run your App to see what it looked like but had not used it to try and make a boot logo. I have to say that the GUI interface is attractive and that made me comment as I did. When I used your App it failed to make a single logo, each time leaving me with just a "white" illuminated screen before the bootanimation started.
Having made 20 or 30 Boot Logos both for myself and others I have an ample supply of images to use, with the knowledge that each of the images has already successfully been used in the creation of Boot Logos for the XT1034 Moto G.
Looking at the files associated with your App, I see that you have used (word for word) two files (1) update-binary and (2) updater-script which have been associated with other scripts dating back to 2013 but you have not kept the same file structure i.e. ..... META-INF>com>google>android..... and it's in the folder "android" that files (1) & (2) above appear. Is it possible that you have missed this?
I haven't tried flashing with "fastboot" - I prefer to flash through Recovery and I think the majority of noobs prefer that easier method so maybe you could check your scripting. I used 12 different images all of which have been used to successfully create Boot Logos so maybe you could check
I was able to create a new bootlogo from scratch, but wasn't able to open any logos from this thread (http://forum.xda-developers.com/showthread.php?t=2686441) to edit them.
metpolds said:
@caitsith2 ..... The comments I made in post #3 were made when I had run your App to see what it looked like but had not used it to try and make a boot logo. I have to say that the GUI interface is attractive and that made me comment as I did. When I used your App it failed to make a single logo, each time leaving me with just a "white" illuminated screen before the bootanimation started.
Click to expand...
Click to collapse
For this, bit, you may have missed that you should be replacing logo_unlocked, as that is the logo your phone is going to show, if you did indeed unlocked it.
If you could help me out, upload one or two of your unsuccessful zips, and I will have a look.
metpolds said:
Looking at the files associated with your App, I see that you have used (word for word) two files (1) update-binary and (2) updater-script which have been associated with other scripts dating back to 2013 but you have not kept the same file structure i.e. ..... META-INF>com>google>android..... and it's in the folder "android" that files (1) & (2) above appear. Is it possible that you have missed this?
Click to expand...
Click to collapse
Actually, the program creates the directory structure in the zip file itself. Just open up the zips created. You will see that the zip contains
META-INF>com>google>android>updater-script
META-INF>com>google>android>update-binary
logo.bin
All of which are part of a normal flashable zip file.
metpolds said:
I haven't tried flashing with "fastboot" - I prefer to flash through Recovery and I think the majority of noobs prefer that easier method so maybe you could check your scripting. I used 12 different images all of which have been used to successfully create Boot Logos so maybe you could check
Click to expand...
Click to collapse
rpcll said:
I was able to create a new bootlogo from scratch, but wasn't able to open any logos from this thread (http://forum.xda-developers.com/showthread.php?t=2686441) to edit them.
Click to expand...
Click to collapse
Okay, I had a look at the contents of some of them, and was not aware of a third logo.bin format, which is just a raw 540x540x24bpp image.
Guess I will have to specifically add support for that format. You should be able to edit the logos that look like they fill the entire screen in the mean time, as that requires using the "kitkat" formatted logo.bin format.
Delgado666 said:
And when does the "logo_boot" screen appear?
When I boot my phone i see logo_unlocked screen
Click to expand...
Click to collapse
logo_boot is strictly for boot-loader locked phones, while logo_unlocked is strictly for boot-loader unlocked phones.
@caitsith2 ..... SUCCESS :laugh:..... Your comments have cleared up the misunderstanding that I think at least two of us were to having i.e. If we are using an unlocked bootloader then we have to chose "logo_unlocked" whereas if our bootloader is still locked then we must use "logo_boot". I used 4 of my previous "failed" images and had 100% success this time around.
I endorse what I said originally, the GUI is elegant and a pleasant and effective advance on the cmd line scripts that most of us have been using, in consequence I have "rated" the thread. Please take the following comments as suggestions NOT as criticism. I think you will find that 90% of the thread users have unlocked their bootloaders and you could consider changing the tree "titles" to more clearly indicate which is which ..... alternatively ..... you could add a couple of lines to the instructions to clear up any misunderstanding.
I take heed of your comments regarding the two META-INF scripts and apologise for not researching deeper.
I think this thread deserves more publicity and will do what I can in this respect.
metpolds said:
@caitsith2
I endorse what I said originally, the GUI is elegant and a pleasant and effective advance on the cmd line scripts that most of us have been using, in consequence I have "rated" the thread. Please take the following comments as suggestions NOT as criticism. I think you will find that 90% of the thread users have unlocked their bootloaders and you could consider changing the tree "titles" to more clearly indicate which is which ..... alternatively ..... you could add a couple of lines to the instructions to clear up any misunderstanding.
I take heed of your comments regarding the two META-INF scripts and apologise for not researching deeper.
I think this thread deserves more publicity and will do what I can in this respect.
Click to expand...
Click to collapse
And now, you no longer have to worry about those META-INF files, as I have now embedded them into the program,
And the tree now shows a tool-tip as to the purpose of the items, when you hover the mouse over the item.
The next version will be built with the Ionic.Zip.dll zip library built into the program, so that the program can truly stand alone.
Yeah, additional awareness would be good, as this should work with any motorola phone that has a flashable boot logo.
Phones that are Moto E and later, will likely have logo_boot, logo_unlocked, logo_battery, logo_lowpower, and logo_unplug.
Moto X/Moto G/Droid Ultra has logo_boot, logo_unlocked, logo_battery.
Motorola phones released mid-late 2012 have just logo_boot and logo_unlocked. Motorola phones released early 2012 (Droid 4) and earlier, have just the raw 540x540 logo. Although those phones only have 1MiB partitions, it will never be exceeded on those devices.
Very nice, does everything I need.
Got to repeat myself here ..... this App is by far the best which has emerged in this Forum in respect of creating boot logos ..... the GUI is by far the best, cleanest, easiest and is simplicity itself to use ..... had to "bump" it back to top of the queue, couldn't let it languish on page 2.
I second that!! indeed this is one of the best app for me that i have found till now for creating boot logos
thanks for the tools
like this
check my bootlogos: here
Version 1.5 released. Check OP for details.
Version 1.6 released. Fixed a fairly major bug.
Excelent! i will change my bootlogo once a week with this!
Do you plan to make custom boot animations possible with this on a future update? Or this is just for the logos?
Anyway, thank you for efforts on this :good:
UncolourTV said:
Excelent! i will change my bootlogo once a week with this!
Do you plan to make custom boot animations possible with this on a future update? Or this is just for the logos?
Anyway, thank you for efforts on this :good:
Click to expand...
Click to collapse
This is just for the boot logos and anything that Motorola decides to store in the boot logo partition.
Hey Guys ~
Greetings from Codeworm7
If anyone wants any bootanimation to be ported to the Moto E or even made from Scratch, please do so by commenting on this thread.:good:
Any/All requests will be answered within 3 days time. If the requested boot animation cannot be made/source files are not available, the user will be notified in a day.
Please adhere to the following points:
1. Do give me detailed information about your screen resolution. e.g. - 000x000 L x B
2. Model No. and Version
3. Processor/RAM/ROM information
All the devices should be rooted in order to install these boot animations.
Cheers!!
---- I WILL NOT BE RESPONSIBLE FOR BROKEN OR BRICKED DEVICES" ---- (Although all the Bootanimations will tested and then posted with the link to the user)
burning skull
can you make the boot animation for burning skull...
thanks in advance...
Hello
I wrote yet another Mediatek logo packer/unpacker and wanted to share.
Sorry if it's not the appropriate place for such an announcement. It probably should go to the development section, if a moderator can move it, please do so.
Basically, it lets you modify the boot logo; that's what I made the tool for, for my personal enjoyment.
I know of alternatives, some already announced here:
https://forum.xda-developers.com/android/development/tools-unpack-repack-boot-img-utility-t3154621
https://forum.xda-developers.com/android/general/tool-mtklogotool-unpackrepack-logo-bin-t3777181
https://github.com/bgcngm/mtk-tools
I owe these tools precious information about the MTK logo structure - but I just didn't feel like hacking them.
How is it different from other existing tools?
supports recent devices, at least supports *my* phones! (mt6737 based)
supports different color modes (16 bits, 32 bits)
configurable to some extent (just a YAML configuration file to edit if you have a clue about your logo resolution)
command line tool to unpack and pack, does not actually flash the device
written in Rust, cross platform (at least tried on win-amd64, linux-amd64, android-arm64) and hopefully easily hackable
If there is an MTK logo image this tool cannot unpack, I'd be happy to improve it if you send me the raw disk image.
Please note I cannot provide extensive support for actual logo replacement, I'm not in Android business.
Links on github:
- binaries
- source code
arlept
Only for
BQ Aquaris X2 (zangya)
BQ Aquaris X2 PRO (zangyapro)
Vsmart Active 1 (PQ6001 - rebranded X2 PRO)
Hello,
Since BQ shut down the JSON request service in October 2020, there have been no valid free alternatives in order to recover bricked devices with locked bootloader... and there certainly won't be any more from BQ (the bankruptcy procedure of Mundo Reader S.L. - BQ started in Spain at the beginning of February).
For this reason I've released a special emergency package + related instructions, that I have put together and tested over the past few weeks.
You may find everything in :
Web mirror on Yandex
or
Drivers/Tools + Firmware Repository on Telegram
Spoiler: Screenshots
Stage A - Emergency Package QFIL Flash
{
"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"
}
. .
Stage A - Emergency Package - First Boot
..
Stage B - IMEI / Baseband NVRAM checks & fix
...
The unbrick process requires:
1 compulsory stage ( A = Unbrick Flash )
1 additional stage ( B = IMEI / baseband fix ), which is only required if there are IMEI and/or SIM issues after the unbrick
Note: Please keep in mind that this is NOT a trivial 5 minute process. Anyone who owns a bricked X2 / X2 PRO device must read / follow the instructions carefully and spend around 1-2 hours to fully recover his device.
---------------------
Side Note : Such Emergency Package and related A-B instructions have been assembled & tested to use them ONLY with BQ Aquaris X2 - BQ Aquaris X2 PRO - Vsmart Active 1, that were running vendor-official firmware builds or conventional-unofficial releases (LineageOS, Ubports, etc.).
It is NOT technically compatible with the same HW models, that have been tampered instead to use a so-called "secure" firmware... = if this is your situation, please read the spoiler.
Spoiler: Side Note
Side Note : There are mainly non-technical reasons why, even after Europol dismantled Encrochat network on June 2020, no users with such tampered devices are finding any helpful wipe/flash-instructions in the public domain.
Indeed, the advices for the second/new owners of such (no longer working) devices haven't changed at all.
According to their specific scenarios/behaviours, it's up to them to choose from the following available options :
Try to return the device to the seller & get the money back
.
Contact the Police and provide the device & any information about the seller
.
Disassemble the device & resell the parts (all except the motherboard) as second-hand spare parts
.
Replace the motherboard with a (new or used) compatible one
wow thanks to you and the people that work on that guide !
is it suppose to work on old encrochat phone? cause i get this error with every firehose file.
Hello @randomrepairtech
randomrepairtech said:
wow thanks to you and the people that work on that guide !
Click to expand...
Click to collapse
You're welcome .
randomrepairtech said:
is it suppose to work on old encrochat phone? cause i get this error with every firehose file.
Click to expand...
Click to collapse
Such Emergency Package and related A-B instructions have been assembled & tested to use them ONLY with BQ Aquaris X2 - BQ Aquaris X2 PRO - Vsmart Active 1, that were running vendor-official firmware builds or conventional-unofficial releases (LineageOS, Ubports, etc.) = NOT technically compatible with the same HW models, that have been tampered instead to run such "secure" firmware.
Spoiler: Side Note
Side Note : keep in mind that there are mainly non-technical reasons why, even now - more than 8 months after the dismantling of the network, no users with such tampered devices are finding any helpful wipe/flash-instructions in the public domain.
Indeed, the advices for the second/new owners of such devices (no longer working) haven't changed at all.
According to their specific scenarios/behaviours, it's up to them to choose from the following available options :
Try to return the device to the seller & get the money back
.
Contact the Police and provide the device & any information about the seller
.
Disassemble the device & resell the parts (all except the motherboard) as second-hand spare parts
.
Replace the motherboard with a (new or used) compatible one
Hello, I really need your help, I think I just bought one of those phones with encrochat, but I would like to be sure, could you tell me if there is any way to know if it is one of those infected phones? first of all, Thanks
Sorry if you don't understand me, but I don't speak English, what you're reading is translated
RawMain said:
Hello @randomrepairtech
You're welcome .
Such Emergency Package and related A-B instructions have been assembled & tested to use them ONLY with BQ Aquaris X2 - BQ Aquaris X2 PRO - Vsmart Active 1, that were running vendor-official firmware builds or conventional-unofficial releases (LineageOS, Ubports, etc.) = NOT technically compatible with the same HW models, that have been tampered instead to run such "secure" firmware.
Spoiler: Side Note
Side Note : keep in mind that there are mainly non-technical reasons why, even now - more than 8 months after the dismantling of the network, no users with such tampered devices are finding any helpful wipe/flash-instructions in the public domain.
Indeed, the advices for the second/new owners of such devices (no longer working) haven't changed at all.
According to their specific scenarios/behaviours, it's up to them to choose from the following available options :
Try to return the device to the seller & get the money back
.
Contact the Police and provide the device & any information about the seller
.
Disassemble the device & resell the parts (all except the motherboard) as second-hand spare parts
.
Replace the motherboard with a (new or used) compatible one
Click to expand...
Click to collapse
Hello, I really need your help, I think I just bought one of those phones with encrochat, but I would like to be sure, could you tell me if there is any way to know if it is one of those infected phones? first of all, Thanks
Sorry if you don't understand me, but I don't speak English, what you're reading is translated
RawMain said:
Only for
BQ Aquaris X2 (zangya)
BQ Aquaris X2 PRO (zangyapro)
Hello,
Since BQ shut down the JSON request service in October 2020, there have been no valid free alternatives in order to recover bricked devices with locked bootloader... and there certainly won't be any more from BQ (the bankruptcy procedure of Mundo Reader S.L. - BQ started in Spain at the beginning of February).
For this reason I've released a special emergency package + related instructions, that I have put together and tested over the past few weeks.
You may find everything in :
Web mirror on Yandex
or
Drivers/Tools + Firmware Repository on Telegram
Spoiler: Screenshots
Stage A - Emergency Package QFIL Flash
View attachment 5232541 . View attachment 5232543 . View attachment 5232547
Stage A - Emergency Package - First Boot
View attachment 5232549.View attachment 5232551.View attachment 5232553
Stage B - IMEI / Baseband NVRAM checks & fix
View attachment 5232555.View attachment 5232557.View attachment 5232559.View attachment 5232561
The unbrick process requires:
1 compulsory stage ( A = Unbrick Flash )
1 additional stage ( B = IMEI / baseband fix ), which is only required if there are IMEI and/or SIM issues after the unbrick
Note: Please keep in mind that this is NOT a trivial 5 minute process. Anyone who owns a bricked X2 / X2 PRO device must read / follow the instructions carefully and spend around 1-2 hours to fully recover his device.
---------
Click to expand...
Click to collapse
Hello, I really need your help, I think I just bought one of those phones with encrochat, but I would like to be sure, could you tell me if there is any way to know if it is one of those infected phones? first of all, Thanks
Sorry if you don't understand me, but I don't speak English, what you're reading is translated
Thanks, good job.
I have a BQ Aquaris X5 Plus (gohan) in the same situation, bricked and locked bootloader.
I have stock ROM (2.7.0_20181002-1711-gohan-user-684-Fastboot-FW.zip) and BQ Firmware Flash Tool 5.0, but I don't have the JSON file to unlock it.
Qualcomm HS-USB QDLoader 9008 port is present, I could follow the instructions in this post, I can get most of the content of "EMERGENCY_PACKAGE" from the stock ROM, I only need the files for QFIL (firehose, RawProgram and Patch). I have searched long without result.
I would appreciate help.
Hello
xap3 said:
Thanks, good job.
Click to expand...
Click to collapse
You're welcome.
xap3 said:
I have a BQ Aquaris X5 Plus (gohan) in the same situation, bricked and locked bootloader.
[...]
Qualcomm HS-USB QDLoader 9008 port is present, I could follow the instructions in this post, I can get most of the content of "EMERGENCY_PACKAGE" from the stock ROM, I only need the files for QFIL (firehose, RawProgram and Patch). I have searched long without result.
Click to expand...
Click to collapse
The partitions you find inside the BQ fastboot firmware packages aren't enough to make full emergency/rescue packages. Several reserved partitions are missing indeed.
You can try to make a partial QFIL/EDL package... but keep in mind that such partial packages can't solve in most cases of BQ bricked devices with locked bootloader.
So, as for any BQ device with Qualcomm SOC, if you need/want to make a full QFIL/EDL package for Aquaris X5 Plus (gohan), you'll need anyway another working X5 Plus, in order to extract :
A full EDL dump of EMMC storage partitions, that will allow you to get those missing reserved partitions too
.
A QCN backup, that can be edited & used to restore/fix baseband + IMEIs of your KO device
Programmer & patch / rawprogram files for X5 Plus aren't so hard to find. Through a Google search - such as for instance this one - you can easily find the related references on Spanish and German forums.
Side note: this thread is only for messages / information exchange about the emergency package for BQ Aquaris X2 - X2 PRO & Vsmart Active 1 too (since such phone is just a rebranded X2 PRO without NFC hardware).
For any further & specific discussion/message about X5 Plus, you'd better post a new thread.
RawMain said:
The partitions you find inside the BQ fastboot firmware packages aren't enough to make full emergency/rescue packages. Several reserved partitions are missing indeed.
...
Click to expand...
Click to collapse
Thanks for your answer. I have a lot to learn ...
RawMain said:
Side note: this thread is only for messages / information exchange about the emergency package for BQ Aquaris X2 - X2 PRO & Vsmart Active 1 too (since such phone is just a rebranded X2 PRO without NFC hardware).
For any further & specific discussion/message about X5 Plus, you'd better post a new thread.
Click to expand...
Click to collapse
Sorry for using this thread to request help from another model.
Sincerely, thank you very much.
RawMain said:
Only for
BQ Aquaris X2 (zangya)
BQ Aquaris X2 PRO (zangyapro)
Vsmart Active 1 (PQ6001 - rebranded X2 PRO)
Hello,
Since BQ shut down the JSON request service in October 2020, there have been no valid free alternatives in order to recover bricked devices with locked bootloader... and there certainly won't be any more from BQ (the bankruptcy procedure of Mundo Reader S.L. - BQ started in Spain at the beginning of February).
For this reason I've released a special emergency package + related instructions, that I have put together and tested over the past few weeks.
You may find everything in :
Web mirror on Yandex
or
Drivers/Tools + Firmware Repository on Telegram
Spoiler: Screenshots
Stage A - Emergency Package QFIL Flash
View attachment 5232541 . View attachment 5232543 . View attachment 5232547
Stage A - Emergency Package - First Boot
View attachment 5232549.View attachment 5232551.View attachment 5232553
Stage B - IMEI / Baseband NVRAM checks & fix
View attachment 5232555.View attachment 5232557.View attachment 5232559.View attachment 5232561
The unbrick process requires:
1 compulsory stage ( A = Unbrick Flash )
1 additional stage ( B = IMEI / baseband fix ), which is only required if there are IMEI and/or SIM issues after the unbrick
Note: Please keep in mind that this is NOT a trivial 5 minute process. Anyone who owns a bricked X2 / X2 PRO device must read / follow the instructions carefully and spend around 1-2 hours to fully recover his device.
---------
Click to expand...
Click to collapse
Hi, i have the Aquaris X2 but i think it is in a worse state than just bricked. The phone looks like this and can take pictures and check the time. Unrecognizable by the pc and QFIL, unable to install drivers, unable to do anything. This are all the apps the phone has. Wonder if it is even possible to fix it.
Bushi1312 said:
Hi, i have the Aquaris X2 but i think it is in a worse state than just bricked. The phone looks like this and can take pictures and check the time. Unrecognizable by the pc and QFIL, unable to install drivers, unable to do anything. This are all the apps the phone has. Wonder if it is even possible to fix it.View attachment 5405939
Click to expand...
Click to collapse
Had you success recovered your phone? I have an Aquaris X2 with the totally same problem.
Tried @RawMain 's solution but failed during load partition process. I knew it's because I have no correct programmer file, but don't know how to solve it.
RawMain said:
Only for
BQ Aquaris X2 (zangya)
BQ Aquaris X2 PRO (zangyapro)
Vsmart Active 1 (PQ6001 - rebranded X2 PRO)
Hello,
Since BQ shut down the JSON request service in October 2020, there have been no valid free alternatives in order to recover bricked devices with locked bootloader... and there certainly won't be any more from BQ (the bankruptcy procedure of Mundo Reader S.L. - BQ started in Spain at the beginning of February).
For this reason I've released a special emergency package + related instructions, that I have put together and tested over the past few weeks.
You may find everything in :
Web mirror on Yandex
or
Drivers/Tools + Firmware Repository on Telegram
Spoiler: Screenshots
Stage A - Emergency Package QFIL Flash
View attachment 5232541 . View attachment 5232543 . View attachment 5232547
Stage A - Emergency Package - First Boot
View attachment 5232549.View attachment 5232551.View attachment 5232553
Stage B - IMEI / Baseband NVRAM checks & fix
View attachment 5232555.View attachment 5232557.View attachment 5232559.View attachment 5232561
The unbrick process requires:
1 compulsory stage ( A = Unbrick Flash )
1 additional stage ( B = IMEI / baseband fix ), which is only required if there are IMEI and/or SIM issues after the unbrick
Note: Please keep in mind that this is NOT a trivial 5 minute process. Anyone who owns a bricked X2 / X2 PRO device must read / follow the instructions carefully and spend around 1-2 hours to fully recover his device.
---------
Click to expand...
Click to collapse
Many thanks for your efforts, it's really clear and detail to do the job.
But... I can't unbrick my X2 cause loading partition error. One friend posted his problem as this in another thread (about load partition error,). Though you provided 4 programmer files, where could I download more to try? Or if we can full re-write all firmwares in this phone? Such as remove all partitions and re-build/re-write them?
(I had join the TG group and not found more information...)
Bushi1312 said:
Hi, i have the Aquaris X2 but i think it is in a worse state than just bricked. The phone looks like this and can take pictures and check the time. Unrecognizable by the pc and QFIL, unable to install drivers, unable to do anything. This are all the apps the phone has. Wonder if it is even possible to fix it.
Click to expand...
Click to collapse
Pokers Lin said:
Many thanks for your efforts, it's really clear and detail to do the job.
But... I can't unbrick my X2 cause loading partition error. One friend posted his problem as this in another thread (about load partition error,). Though you provided 4 programmer files, where could I download more to try? Or if we can full re-write all firmwares in this phone? Such as remove all partitions and re-build/re-write them?
(I had join the TG group and not found more information...)
Click to expand...
Click to collapse
Hello @Bushi1312 & @Pokers Lin
The situation of both your tampered devices is just the same as in post 3 of this thread = read the side note and related spoiler.
I have now included such note in the opening post too.
RawMain said:
Hello @Bushi1312 & @Pokers Lin
The situation of both your tampered devices is just the same as in post 3 of this thread = read the side note and related spoiler.
I have now included such note in the opening post too.
Click to expand...
Click to collapse
Thanks for your answer... so, you mean that my X2 had been installed as a "secured firmware" (named "encrochat"?) ? It's a bad news for me. Anyway, thank you very much, at least I can know why it's so hard to be fix now.
RawMain said:
Hello @Bushi1312 & @Pokers Lin
The situation of both your tampered devices is just the same as in post 3 of this thread = read the side note and related spoiler.
I have now included such note in the opening post too.
Click to expand...
Click to collapse
So basically it is impossible to fix it, right?
Bushi1312 said:
So basically it is impossible to fix it, right?
Click to expand...
Click to collapse
to fix what ?
do install the emergency firmware and unlock the firmware with ''fastboot flashing unlock''
then re install your genuine firmware with the emergency mode.
as simple as that
hello to everyone , i am in encrochat case , and i need a encrochat that was used from may 2020 .
i will buy , please can anyone help me ?
i need to prove that have a malware .
thanks in advance .
I have a BQ X2 with private mode could this solution work on it ?
It would be nice if someone could port WearOS to the Samsung Galaxy watches with Exynos 9110 SoC.
Many people still have older GWs because they bought them before the GW4 came out.
Look here:
[CLOSED] [ROM - DEV] WearOS 2 for Gear S3
DISCLAIMER Your warranty is now void (if you still have one). Read the steps carefully! I am not responsible for data loss, bricked devices or devices which will need USB soldering! If you do not know what you're doing, stop here! Latest...
forum.xda-developers.com
And help him.
Best Regards
Hi
I recently found the Exynos 9110 (GWA1) kernel source and i made it downloadable, i hope people would find this post then download the kernel source and port some android wear stuff on it.
Anyway here's the link : )
oh yeah oops i did not find the combination firmware : C
linux-4.9-exynos9110.zip
drive.google.com