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.
Related
Hey guys was wondering about flashing my HTC Touch Diamond, But I want a decent ROM.
Something that's not too packed up full of junk, Easy to use and a better performance.
Also maybe a guide to unlocking/debranding this phone along with a flash guide if that's not too much?
cheers.
xelasha said:
Hey guys was wondering about flashing my HTC Touch Diamond, But I want a decent ROM.
Something that's not too packed up full of junk, Easy to use and a better performance.
Also maybe a guide to unlocking/debranding this phone along with a flash guide if that's not too much?
cheers.
Click to expand...
Click to collapse
From one newbie to another, you should read the sticky posts... they are full guides and information about flashing your phone's ROM / Radio etc.
The forum 'Search' facility is your friend, it like's to be used. That's what I did and found all I needed to know about the available ROM's and Flashing process without having to ask a single question.
The New World ROM introduced a much-improved version of the Open Firmware interpreter, version 3.0, which added many missing features, fixed most of the bugs from earlier versions, and had the capability to run CHRP boot scripts. The Toolbox ROM was embedded inside a CHRP script in the System Folder called "Mac OS ROM", along with a short loader stub and a copy of the Happy Mac icon (in Mac OS X 10.2 and higher, this was replaced with a silhouette of the Apple logo on a blank gray screen) suitable for display from Open Firmware. Once the ROM was loaded from disk, the Mac boot sequence continued as usual. As before, Open Firmware could also run a binary boot loader, and version 3.0 added support for ELF objects as well as the XCOFF files versions 1.0.5 and 2.0 supported. Also, version 3.0 (as well as some of the last releases of version 2.x, starting with the PowerBook 3400) officially supported direct access to the Open Firmware command prompt from the console (by setting the auto-boot? variable to false from Mac OS, or by holding down Command-Option-O-F at boot).
rajas
new rom
Android NBHCREATOR [v0.3] on Ubuntu. FROYO SUPPORT & ADVANCED SETTINGS [July-29-2010]
NBHCreator v 0.3
NBHCreator makes the nbh file for flashing android to nand.
This utility works for Vogue, Polaris and Kaiser.
Currently supporting Donut, Eclair and Froyo
Prerequisites:
1. you need to be running Ubuntu (other Debian distros may work, give it a try) NBHCreator v2.0 will be cross-platform
2. you need to have wine installed ( I am using v1.1.42)
Make sure to "Completely" uninstall previous versions before installing newer versions.
Directions as follows:
a. select the zImage you wish to make an nbh for... try one from here:Working Kaiser GPS!! or here:DZO
b. change parameters to your liking...
c. click on the "compile" button...
d. select output folder.
and Flash Away...
Please Search for how to flash if you don't know how.
that being said...
I welcome any and all criticisms of this program
and I would appreciate any advice, suggestions, questions or comments.
Version 0.3b
-Fixed Window issues.
-For now...do not save output to a FOLDER on the Desktop.
-DOES NOT WORK YET WITH 2.6.32 ZIMAGES
Version 0.3 (07-29-2010)
-Now Supporting Froyo
-New Advanced Settings for things like Clock speed and Memory.
-Added a Date Stamp option for output filename.
-Removed internal Error checking[/B]
-This version has window issues with the xfce desktop environment. fixed in 0.3b
Version 0.2b (07-01-2010)
-Fixed false errors when creating for Vogue and Polaris
Version 0.2 (06-15-2010)
- Added ability to select zImage with name extentions ie... "zImage-12-06-10"
- Output filename now refects device type ie... "VOGUIMG, POLAIMG and KAISIMG"
- Added some error checking to make sure nbh was built correctly
- misc internal code fixes.
-False Error messages are popping up for vogue and polaris. Resulting nbh should still be usable. Fixed in 0.2b.
Version 0.1 (06-09-2010)
- should work for Kaiser, Vogue and Polaris
- Device specific options
- Settings for hw3d (donut/eclair)
- Settings for Resolution 240x320, 320x428, 320x480
- Settings for Panel Type 1, 2, 3
- Settings for Battery Capacity
- Settings for ppp.nostart (Data)
- May not work with loser's editor (let me know...)
- more options to come
- NBHs are all being named KAISIMG.NBH will be fixed in v0.2
Honestly? I think it rocks, since I'm to lazy to build my own NBH's
I see the similarities, and also the differences, and I think you should continue development personally, it's a different approach, and I can see the possibility to add to it by being able to include boot splashes perhaps, or edited initrd/zimage combinations for instance.
So yeah, keep at it
Yep, sounds like a great idea. A nbh editor is good for beginners, but it would be nice to be able to build your own. Could open up a lot of opportunities for customization.
Just make a Windows and a Mac port as well, for the future.
ok....so far progress is going along very well. I have this functioning on my setup
but I still have to work out making it transferable to other computers.
while I work on this, are there any additions that you would like to see added.
I will see if I can squeeze any changes into the beta release.
What language and GUI toolkit are you using?
It would be fairly portable if written in Python with GTK or Tk.
I am using gambas2 in ubuntu.
I am still trying to port my visual basic knowledge to gambas. it doesn't all function the same.
I have minimal experience in Python. but if you know any good tips I am all open for suggestions.
Now available for testing
really???? no feedback at all???
I have to get around to install Ubuntu, and I don't have the hard disk space for it just yet. Been meaning to go buy a terabyte hard drive to dual boot.
got sources or anything like that so I can haz on gentoo?
currently attempting to break open the deb, will fall back to a vm in worst case.
Edit: As I expected, I found the solution right after posting. Run NBHCreator.gambas from /usr/bin
I'm fairly new to Ubuntu and I've never use Wine before so can't work out how to get this running
The package installed, along with it's dependencies. Now what? How do I run it?
Sorry if this is basic stuff...
richard.
Working ok here. Still need to flash it onto my Kaiser - will report back if I find any problems.
Thank - this is a handy little tool
Edit: Hmm, output file only 4.8K so something is not right. Probably down to me so I'll keep playing.
richard_s said:
Edit: As I expected, I found the solution right after posting. Run NBHCreator.gambas from /usr/bin
richard.
Click to expand...
Click to collapse
The install deb should have created a 'start menu' item under /Applications/Other/NBHCreator
that is confirmed under the default Ubuntu window manager 'Gnome'
however I have not tested it in KDE or any other non-gnome window manager.
what window manager are you using?
poly_poly-man said:
got sources or anything like that so I can haz on gentoo?
currently attempting to break open the deb, will fall back to a vm in worst case.
Click to expand...
Click to collapse
let me know if you get it. I don't have the source available at the moment. it's on my wife's computer.
richard_s said:
Working ok here. Still need to flash it onto my Kaiser - will report back if I find any problems.
Thank - this is a handy little tool
Edit: Hmm, output file only 4.8K so something is not right. Probably down to me so I'll keep playing.
Click to expand...
Click to collapse
the resulting nbh must be 3M
DON'T FLASH IF IT ISN'T 3M.
make sure the zImage file is named 'zImage' and not somthing like 'zImage-12-06-10'
I am fixing the next version to allow different names for zImage.
mnjm9b said:
the resulting nbh must be 3M
DON'T FLASH IF IT ISN'T 3M.
make sure the zImage file is named 'zImage' and not somthing like 'zImage-12-06-10'
I am fixing the next version to allow different names for zImage.
Click to expand...
Click to collapse
No - I won't be flashing it! The file name is definitely just 'zImage'. Oh well I'll wait for the next version and try again.
richard_s said:
No - I won't be flashing it! The file name is definitely just 'zImage'. Oh well I'll wait for the next version and try again.
Click to expand...
Click to collapse
I haven't built in a error log into the program but could you run
the NBHCreator.gambas in a terminal and post the output.
what device are you building for and what are your settings?
After restarting Ubuntu your program it is all working as expected. Sorry about that - I should have thought to try that first
yeah, had to throw it into a virtual machine. Nice tool, though.
If someone describes the process in great detail (including the binary formats and all that), I can make a slightly more portable version, if you'd like.
I will be releasing a more cross-platform version after I work out all the bugs.
Keeping it ubuntu for now keeps the distribution of a crappy program to a minimal.
on that note... V0.2 will be out very shortly.
this will address
-input filename variations ie.. 'zImage-12-06-10'
-output filename specific to correct device ie.. 'VOGUIMG,POLAIMG and KAISIMG'
-error checking
-misc fixes
TPT Helper is designed for the ZTE phones. It helps you to easily repartition the phone and for the ZTE Blade, convert it to the Gen 2 memory layout to let you run the latest custom ROMs. ZTE phones supported so far are the ZTE Blade/Orange San Francisco, ZTE Skate/Orange Monte Carlo and the Orange San Francisco II/T-Mobile Vivacity.
Features:
*Download TPT files giving different partition layouts
*Download TPT files which will convert and install a ROM in one go
*Build your own TPT choosing partition size, recovery and splash image (in the given range)
*Start the TPT from inside the app on some roms, no need to use the hardware buttons manually
*Check the file is intact
*Unzip the TPT files to the correct location
*Verify that all the files you're about to flash are intact
*Clean up afterwards to avoid accidental flashes
https://market.android.com/details?id=com.amphoras.tpthelper
The Gen 1 to Gen 2 TPT files linked to in the app were created by wbaw.
Translations:
French translations by Alex131089.
German translations by FelixL.
Russian translations by top4ek.
Chinese translations by wuxipaopao.
Serbian translations by Sokobeg.
Czech translations by dejf.
Polish translations by arnoldziq.
If you'd like to help with translations, you can add/update them here:
http://www.getlocalization.com/TPT_Helper/
If you've added some, let me know so I can credit you with it.
TPT Helper Copyright © 2011 David Phillips
TPT Helper is free software: you can redistribute it and/or modifyit under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
TPT Helper is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with TPT Helper. If not, see <http://www.gnu.org/licenses/>.
You can see a copy of the full license by picking the "License" option from the menu.
You can get a copy of the source code for this version from https://github.com/Amphoras/TPT-Helper/tree/V2.0.1
it just checks the ram and reports gen1/2 so its not of much use.
a european blade flashed with a tpt having 256mb ram(chinese tpt) gets detected as gen 1 even if it is 2
It tries to detect which you have at the first start. If it doesn't detect correctly, it gives you the option to pick the correct results. Could you post the output from /proc/iomem please?
Amphoras said:
It tries to detect which you have at the first start. If it doesn't detect correctly, it gives you the option to pick the correct results. Could you post the output from /proc/iomem please?
Click to expand...
Click to collapse
sorry bro i didn't try this app but suggested it to someone here at xda i think it was gen2ram unlock thread and someone replied me.
saaransh9 said:
sorry bro i didn't try this app but suggested it to someone here at xda i think it was gen2ram unlock thread and someone replied me.
Click to expand...
Click to collapse
I think that must have been a different app. This one didn't check these things until the version I uploaded to the market last night.
Does creating a TPT with own sizes also work with a Gen1 phone (better said a TPT upgraded Gen1 to Gen2 phone)?
zte blade stuck on green droid
hi. i downloaded ask mr pigfish and run it on my zte blade which informed me that am on gen 1. i later downloaded tpt helper from android marker. firstly i downloaded the tpt then chevked md5sum did the match unzipped it and finally clixked on check image. then the phone ran some green numbers and lettrrs and later went into recovery mode. from there i could not switch on my phone. it always went to recovery mode. then i tried switchin it on pressing power + the vol - button and it stuck on the green android logo. i had not rooted it so i cant flash a rom. please help on what to do. since i cant go to recovery mode right now
[email protected]
Update: The instructions below are for the AGM X1 eu version, for the AGM X1 International version follow this thread, it's a work in progress and not available yet.
As you might be aware the AGM X1 is a fantastic rugged android, aside from the great hardware, the source code of the phone is available to devs. The combination of excellent ruggedness, hardware and open source makes the AGM X1 "the best choice in phones" at the moment for me period.
Unfortunately the information on how to root and install the available Lineage OS port is not very clear
I spent a few hours trying to find the best place to start and it's quite difficult to find
https://w3bsit3-dns.com/forum/index.php?showtopic=814951
This page contains a post below the main top section of the page.
https://w3bsit3-dns.com/forum/index.php?showtopic=814951
Here's the start of the important stuff with some additional information that I added
"The jist of the thread
TWRP 3.1.0 for AGM X1
---------------------
AGM-X1-flash-TWRP-root.zip ( 21,66 ?? )
https://w3bsit3-dns.com/forum/dl/post/10034644/AGM-X1-flash-TWRP-root.zip
OR
Download TWRP + ROOT from Google
https://drive.google.com/open?id=0B871Z4mt2B7Qb0RLMVlSemR4Szg
sha256sum
AGM-X1-flash-TWRP-root.zip b34b19f6666f0456f68e3a452c97aacf2fd3f1b06819ef7a633d95259d22a25f
SR3-SuperSU-v2.79-SR3-20170114223742.zip e147970ca377a184a177092f4c4a8022420cc30785fdaf95e16703da8312426d
Now here comes the difficult part, trying to decipher the following text
Text from thread (bad english)
Installation takes place in a similar way as inthis post, Except that you need to choose the same name! The fifth! The item and the installation of the root rights occurs automatically when you exit TWRP.
Can anyone help me with this, I cannot decipher the above paragraph. Also note that this forum is broken and not working correctly as a site (many issues including: no registration available and also the important link in the paragraph above does not work)https://forum-lw-1.xda-cdn.com/images/smilies/rolleyes.gif
P.s not interested in king root method (too many mentions of malware), will use twrp.
Update: (thanks to Skill3r)
clearer guide - also note that this zip contains twrp 3.0 instead of 3.1 due to backups not working with 3.1 (important)
https://forum.xda-developers.com/an...m-snapdragon-617-4gb-64-t3533020/post71877054
The steps :
First You need to download this package and extract it : http://www53.zippyshare.com/v/3sgYq5cu/file.html
sha256sum
AGM-X1-flash-TWRP - Skill3r MOD.rar a0e755dc513b716e5a5369481f0761a4c6a9ec60401bd9c0c060579da87f3668
Contents with sha256 hash
adb.exe f05ff055b2ce9213d0b349da7ef713664d66a13134be76820cd072cd1e44211a same as twrp 3.1 version
AdbWinApi.dll 14a51482aa003db79a400f4b15c158397fe6d57ee6606b3d633fa431a7bfdf4b same as twrp 3.1 version
AdbWinUsbApi.dll 041c6859bb4fc78d3a903dd901298cd1ecfb75b6be0646b74954cd722280a407 same as twrp 3.1 version
fastboot.exe 632f4f2039b76082f2c090f6aec43893e93e8b32d0aae6b7cfa03f9b71d5d897 same as twrp 3.1 version
One-key-flash-twrp.bat f3e5a611166e970cb41a0040979da305b9d91abc44537cab9af94110381fbf54 different from 3.1 version
recovery_AMG-X1_es_by_MDSdev.img 3eb8df185afaacaae4a754ba3c18e5e86ea140f0b115ab73d28fe2ba64088fae different from 3.1 version
SR3-SuperSU-v2.79-SR3-20170114223742.zip e147970ca377a184a177092f4c4a8022420cc30785fdaf95e16703da8312426d same as twrp 3.1 version
1) Enable the developper settings
Go to Settings>About phone and hit "kernel version" 7 times to unlock
2) Enable the OEM bootloader unlock
Find in settings>dev options
3) Enable the USB debugging
Also in settings>dev options
4) Plug an usb cable and when the windows ask for the RSA identity of the computer, allow it and check to always allow the computer.
5) Shutdown your phone
6) Press VOL down + power and after long press the power button
7) Now in recovery mode, go to reboot to bootloader, a green message is shown with fastboot.
8) Now launch the One-key-flash-twrp.bat in package and plug your phone
9) Press any key and follow the instructions in the script.
10) TWRP should launch, you need to swipe to allow modifications in system
11) Press a key in the script, TWRP should reload, TWRP is now installed in the phone, you need to allow modifications in system again.
12) To root the phone, you just need to exit TWRP, he gonna ask to root the phone, you just need to swipe to root the phone.
Now you have TWRP installed and the phone is rooted.
If something goes wrong and bootloop the phone, please just follow the AGM instructions with the original package and the procedure to reflash the rom (on the external SD card and with VOL UP + VOL Down + Power)
I've made progress, but I'm stuck on finding a suitable driver for the adb interface on windows XP for the AGM X1.
For drivers I've tried
NOT WORKING! Google USB drivers
https://developer.android.com/studio/run/win-usb.html
sha256sum
latest_usb_driver_windows.zip 1ee1d023a99ffac962af4454eb9b9900f6858c687b4d5311e8fb361548d6c078
NOT WORKING!
https://forum.hovatek.com/thread-16965.html
which should bring you here
https://drive.google.com/file/d/0B4S-Z726VJ2SLW9zNXdqWDBQQkE/view
sha256sum
a3312727a77c3ab89e0d7463cd252cffec554a182f78195f6908f62132c5c174
The important file in the zip archive is
SHA-256 08e5e7e5f30801b363f08a6106425faa1c505bd048a18c846a5b3e5959a4998e
Called
Setup.exe
Qualcomm_USB_Driver_V1.0.exe
among others.......
MD5
906c4effd6a20be22ea026a43a3cb7b3
SHA-1
89df6ca0d893d9355741d8ca11cdebea1fbbb095
NOT WORKING!
Univeral drivers
https://github.com/koush/UniversalAdbDriver
https://adb.clockworkmod.com/
sha256sum
UniversalAdbDriverSetup.msi 4e77e303bba6cf84588bdb6da91f7a875d406f7930cbe9f4d2aae0b643c0c928
NOTE: Problem installing: universal adb driver, there was a problem with this windows installer
Does any one have any advise please. Obviously I've checked the Manufacturers site they have not provided a driver. The chipset is Qualcomm MSM8952.
Thanks in advance.
Hello, for the drivers, simply plug the phone on USB and select CD in options (where you can check 'simply reload' mtp etc ...)
On the computer you can install the drivers now
Hi Skill3r,
Recommended (MAYBE THE DRIVERS WORK ON OTHER VERSIONS OF WINDOWS, BUT LINUX IS SO MUCH EASIER/BETTER)
I gave up on Windows XP. Now I'm using Xubuntu 16.04 LTS and EVERYTHING IS CONNECTING TO THE COMPUTER with this guide (without going to qtadb installation)
http://bernaerts.dyndns.org/linux/74-ubuntu/354-ubuntu-xenial-android-adb-fastboot-qtadb
p.s the vendor ID is "Qualcomm, Inc": with the code: 05c6 (it's in that github download in the link above, no need to add it specially just follow the guide)
The phone is recognized no special drivers required IT ALL THERE ALREADY! I took the commands from the bat file, changed (take away .exe e.g fastboot.exe to fastboot)
So the problem I'm getting now just after loading twrp with this command
fastboot boot recovery_AGM-X1_es_by_MD5dev.img
And this problem is............
That the touchscreen is unresponsive and I'm unable to check the box and swipe to allow TWRP to modify the system.
I have the AGM X1 International edition.
For me also:
Wenn I´m in the TWRP menu, i´m nt able to click on a button or swipe the last button, because the Touchscreen doesn´t work.
How can I solve this problem, install twrp and root the phone? because i would install LINAGEOS...or what is the best Rom/Custom Rom for the agm x1?
Please help me.
thanks
Both twrp image files below (twrp 3 and 3.1) have the touchscreen problem
sha256
AGM-X1-TWRP-3.1.0.img 22b7d529511b0b191c09e850c14b0d4ed6e32cdddc6defd688bcd78d40be2528
recovery_AMG-X1_es_by_MDSdev.img 3eb8df185afaacaae4a754ba3c18e5e86ea140f0b115ab73d28fe2ba64088fae
motsch_, what version of AGM X1 do you have, international?
Have you found any references to this problem in the main discussion pages.
We need to look for any references to this problem, or special img's for this version of phone.
Here's the older xda thread on the agm x1
https://forum.xda-developers.com/ge...ualcomm-snapdragon-617-4gb-64-t3533005/page12
Hi,
how can I see which version does i have?
For the moment i havent found any solution for installing twrp.
I have rooted the phone with Kingroot.
Doesnt exist a solution for us?
We can go to "settings" > "about phone" > scroll to bottom and let me know the
hardware version
software version
kernel version
I know mine is X1 international not EU as I just bought it and the EU version is discontinued, it has the following
hardware version: V1.00
software version: L1253.6.03.01.BYD
kernel version: 3.10.73
Also is there any awesome developers out there that would be interested in making a TWRP version - forked from the original TWRP and put on github.
And maybe then make your own port of Lineage, again with all changes to original Lineage forked on github.
Open Source and transparency of course is the reason for this.
Any one else with a AGM X1, please chime in because if we can get just a few dollars together we can get this done very quickly.
I pledge $25 for round one
Here's a reference to the touchscreen issue
https://translate.google.com/transl.../index.php?showtopic=814951&st=460&edit-text=
08/01/17, 18:45
"Am11go,
I downloaded AGM X1 TWRP Supersu from the caps, it helped, booted TWRP, but the screen did not react at all, like all buttons except on / off, it extinguishes the screen and does not include anymore ... Apparently the hands are crooked, although with bv5000 It was. How to determine which TWRP, under which version?"
if you can find a solution, can you let me please know that?
Found on 4PDA :
Demanda Sam, dit - il. TWRP assemblé avec le noyau et DTB de L1253.6.02.01.BYD. Maintenant , l'écran tactile fonctionne très bien.
hxxps://4pda.ru/forum/dl/post/10490628/twrp_3.0_L1253.6.02.01.BYD.zip
hxxps://4pda.ru/forum/dl/post/10490629/twrp_3.1_L1253.6.02.01.BYD.zip
AGM X1
HARDWARE & VERSIONS
International version
screen: Edo rm67191 fhd Amoled non-oleofobic non-sunlight readable
HW: Qualcomm MSM8952 hs8952qc
Hw other: RAM 4 Gb LPDDR3 933 mhz
fingerprint reader – FPC1020
notification led – aw2013
camera – Omnivision OV13850 13MP ??
SW: Android 5.1.1 LMY47V
L1253.6.02.01.BYD
EU version
screen: Samsung s6e3fa3 fhd super amoled oleofobic?? non-sunlight readable??
HW: Qualcomm MSM8952 hs8952qc
SW: Android 5.1.1 LMY47V
L1253.6.02.01.EU
Gold version
screen: like international?
HW: same?
SW: like international?
reference discussions: https://4pda.ru/forum/index.php?showtopic=793964
https://forum.xda-developers.com/ge...gm-x1-qualcomm-snapdragon-617-4gb-64-t3533005
https://www.movilesdualsim.com/foros/agm-x1-sd617.1152/
about screen: https://www.devicespecifications.com/en/editor-review/993738/3
http://gearopen.com/phones/agm-x1-review-rugged-smartphone-not-drown-but-froze-53924/
KERNEL SOURCE
https://github.com/zhaochengw/android_kernel_agm_agma3eu
KERNEL CONFIGS EU vs INTERNATIONAL MAIN DIFFERENCE
EU
CONFIG_TOUCHSCREEN_GT1XX=y
CONFIG_TOUCHSCREEN_GT1X_GESTURE=y
CONFIG_TOUCHSCREEN_GT1X_FH=y
# CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_V20 is not set
INTERNATIONAL
# CONFIG_TOUCHSCREEN_GT1XX is not set
CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_V20=y
CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_I2C_V20=y
CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_RMI_DEV_V20=y
CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_TEST_REPORTING_V20=y
CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_FW_UPDATE_V20=y
# CONFIG_TOUCHSCREEN_SYNAPTICS_GLOVE is not set
I compared the kernel configs from latest international lollipop rom with the one from Flyme OS 5 (compatible with x1 EU). I have not a boot.img from latest EU firmware, but should not matter.
This should explain the black screen when trying to install EU rom on International X1.
I found these options are not enabled in standard kernels, they may be of interest:
CONFIG_MSM_VPU CONFIG_POWER_AVS_MSM CONFIG_USB_MSM_ACA
reference: how extract kernel configs with extract-ikconfig (from kernel_dir/scripts)
https://github.com/MotorolaMobilityLLC/kernel-msm/issues/73
ROMS
EU: stock,lineage 13, flymeOs 5-6 https://4pda.ru/forum/index.php?showtopic=814951
INTERNATIONAL: only stock (latest is L1253.6.03.02.BYD)
lineage 13 (removed) https://4pda.ru/forum/index.php?showtopic=814951&st=300#entry62399105
PORTING ROMS AND KERNELS
From EU to International:
take EU roms and replace boot.img with one from International roms? (kernel and dtb table??)
From other Phones:
- Similar MSM8952 Phones: https://www.gizmotimes.com/lists/phones-qualcomm-snapdragon-617-processor/19660
- Guides: https://forum.xda-developers.com/android/general/how-to-port-roms-easy-100-t2804390
https://forum.xda-developers.com/showthread.php?t=2707438
http://ohheyitslou.blogspot.it/2011/09/ohheyitslou-custom-android-kernel-guide.html
- Interesting Kernels: https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836
On Snapdragon 617 at the moment should be possible Overclock, but I have found no Voltage control patches from other phones kernels.
TWRP
EU: https://4pda.ru/forum/index.php?showtopic=814951
INTERNATIONAL: https://4pda.ru/forum/index.php?showtopic=814951&st=300#entry62309514
TWRP 3.0 for android 5, TWRP 3.1.0 should be for android 6 and it may have problems with restoring
TWRP reference info https://www.movilesdualsim.com/tema/twrp-by-mdsdev-para-el-x1.168070/
Hi liamotoub,
Thanks for the information. So Lineage OS is not available on the international version of the AGM X1 yet. I see.
Also Thank you skill3r for the links, I see they are 404 now unfortunately.
liamotoub, you seem to know what you're doing? would you consider taking on this as a project.
It's certainly worth keeping an eye on 4PDA, pitty I cannot read russian. If any members of 4PDA in the loop regarding the AGM X1 international are reading this please chime in. Thank you all
Hello, unfortunately I'm not a programmer, I just do "trial and error".
404 is a 4pda.ru error for not registered users, follow this guide to register
hxxps://doorsgeek.blogspot.it/2015/08/4pdaru-loginregister-captcha-tutorial.html
To read just use google translate
hxxps://translate.google.com/translate?hl=it&sl=ru&tl=en&u=https%3A%2F%2F4pda.ru%2Fforum%2Findex.php%3Fshowtopic%3D793964%26st%3D1300&sandbox=1
PS. another phone with a lot of ROMs (android 5 6 7) and similar hardware of X1 (msm8952) is ZTE Nubia Z11 mini
hxxps://translate.google.com/translate?hl=it&sl=ru&tl=en&u=https%3A%2F%2F4pda.ru%2Fforum%2Findex.php%3Fshowtopic%3D803370&sandbox=1
and what can i do with the "twrp_3.0_L1253.6.02.01.BYD.img" from the download from 4pda?
I would install twrp on my x1
motsch_ said:
and what can i do with the "twrp_3.0_L1253.6.02.01.BYD.img" from the download from 4pda?
I would install twrp on my x1
Click to expand...
Click to collapse
With TWRP you can flash another image (lineage OS for example, when we find or make a suitable version for the international version AGM X1)
TWRP will also give you the option to get root permissions, so you can use certain apps that require it. It's like the difference between user and administrator account in windows. It's called rooting because Android is based on Linux, the root account is the account with "super user" privileges, your phone will be open to allow more areas of the system to be used/wrote to/read. It allows your phone it's full potential.
With TWRP we can also do backups and restores of the entire existing ROM and phone contents
So TWRP is the first step before we get the ROM (lineage OS) on the phone https://forum-lw-1.xda-cdn.com/images/smilies/cowboy.gif
Another option for rooting is available called King Root however this comes with a lot of MALWARE AND ADWARE and it is advised not to use it. Besides it doesn't have all the flashing, backup and restore tools anyway. It just gets you root.
That is why we really need to find a working copy of TWRP for the AGM X1
INSTRUCTION TO COMPILE KERNEL (with android ndk on linux 64bit)
git clone hxxps://github.com/zhaochengw/android_kernel_agm_agma3eu
cd android_kernel_agm_agma3eu
export ARCH=arm64
export SUBARCH=arm64
export CROSS_COMPILE=/opt/android-ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/aarch64-linux-android-
[adapt commandline to your installation or use the one in the kernel sources (toolchains/aarch64-linux-android-4.9/bin)]
make xconfig
[load your agm X1 config file, EU version is in arch/arm64/configs/agma3eu_defconfig,and make your changes]
make -jX
[where X is number of your cpu cores]
bootimg/dtbTool -o dt.img -s 2048 -p ./scripts/dtc/ ./arch/arm/boot/dts
bootimg/mkbootimg --ramdisk bootimg/ramdisk_agma3eu.img --ramdisk_offset 0x01000000 --base 0x80000000 --tags_offset 0x00000100 --pagesize 2048 --kernel arch/arm64/boot/Image.gz --cmdline "console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlyprintk" --dt dt.img --output boot.img
Image.gz ramdisk_agma3eu.img dt.img will be incapsulated in boot.img.
Test if kernel works:
#adb push boot.img boot
If not boot restore previous boot image.
notes:
1.if you load the international kernel config, and you got some errors related to VENDOR, enable
CONFIG_MACH_HIS_SMARTPHONE CONFIG_HIS_BOOT_INFO
and fill CONFIG_HIS_VENDOR_NAME: Android CONFIG_HIS_PRODUCT_NAME:agma3eu
2.if you got an error related to msm_dba_internal.h not found, edit
drivers/video/msm/msm_dba/msm_dba.c and replace #include <msm_dba_internal.h> with #include "msm_dba_internal.h"
PS. replacing my boot.img is not sufficient to make Lineage 13 and FlymeOS5 work, they go in bootloop.
I've uploaded the TWRP versions for the AGM X1 "International version" from the 4PDA links above, to save somebody the trouble of signing up. Version 3.1 is what you want I think (but maybe the backups/restores don't work on v3.1 as skill3r has pointed out or maybe the international version is different?)
SHA-256
72422060a34a995a6f29da1c0a6d5737f7df3ad426d0a7105267730f22e74b9c
File name twrp_3.0_L1253.6.02.01.BYD.zip
Download: https://mega.nz/#!0yZCyIaA!lUnmyeQNinQlzIcwfWZ8F5l6Pz2jlumxzhVx57U6G-M
SHA-256
96c92a52805c0db4fc84c652199887e93a30dae3fe3ead36e14715f7fc736d22
File name twrp_3.1_L1253.6.02.01.BYD.zip
Download: https://mega.nz/#!FmxmFKgK!cCfNsGj3gRMVkl_EI6ROI2-5RbFQsuyElFxRIvN76ug
Also, liamotoub, send me your PayPal address and I'll send a few dollars your way, that information is great thus far
These 2 files should be TWRP 3.0.3 and 3.1.0 right?
I want to point out that also the latest 3.1.1 ( relased for the gold X1 by a Spanish forum, movilesdualsim) works on international X1 mega:#!vB9g3Aab!_gyrr6rP_rJDheGgIseI2u2TglNw1vmv7dDjUnDYJb4 with not encrypted phone.
To try it without touching the recovery partition use:
#adb reboot bootloader
#fastboot boot recovery_name.img
EDIT: it give some problems when flashing new INTernational ROMs, because they think the phone is GOLD and refuse to install due to their updater-script; should be sufficient to modify the build.prop of this recovery or a similar file, with international version "signature".
TWRP 3.0.3 3.1.1, those that I tried, fail to recognize encrypted fylesistems, so backups of this kind will not work.
Another minor bug is the wrong date (1970) in automatic naming of backups folder, but that's common on most phones.
I managed to make FlymeOs 5.1 boot on international X1, but I don't recomend it, it's full of bloatwares and wifi and other things looks to be not working
https://mega.nz/#!djJ3jbbT!Kr6qMyTcggsrYyPeDnySHpp7EOgUZnG-tvTqewdqkmk
Make full working nandroid backup before trying it.
To port lineage 13 I think marshmallow kernel sources are needed, with present sources only lollipop roms could be ported AFAIK, like CM 12.1.
Question to X1 users: on stock rooted rom, do root requesting apps (afwall, kernel audiutor etc) start at boot time? On mine no, I have to start them manually.
On stock rom beware of these preinstalled apps, may be adware:
com.gangyun.beautysnap
com.oupeng.max.hisense
Is there any specific advantage using the TWRP movilesdualsim 3.1.1 version rather than the 4PDA versions other than a slightly higher version.
If I encrypt my phone would there be any other issues other than not being able to do twrp backups and restores? It would still work?
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