Related
Hey all,
I put the 02.02.10 build on my sdcard, and it booted perfectly. I still had a problem reading SMS in my native language because there is no out-of-the-box support for my language.
On many threads that I found, people said they added few fonts to system.sqsh, I tried to use it as everyone explained( with squashfs-tools 3.1 because version 4 doesn't work with android ), but I'm stuck on the second boot screen( the nexus splash screen), it loops forever( gave it 25 minutes before I tried a second attempt).
I backed up the old system.sqsh so I can have a working android, but I need to find a way to add these fonts.
Thanks.
Please use the sticky 'General Android Questions' please
As per above post
Thread closed
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.
Bootlogo for all Mediatek and Spreadtrum Devices
COPYRIGHTS : I don't own any pictures I use in making these. If you're the owner of these pictures, PM me and I'll give you credits.
REQUESTS: Message me privately to ask any questions and to request the certain resolution of the boot logo or a picture.
Now your warranty is now void.
I'm not responsible for breaking any devices you own. Flash at your own risk!
This will be ONLY available for Mediatek and Spreadtrum Devices.
Qualcomm,Broadcom and Other Chip Manufacturers are not supported.
Flashing Method:
No need to wipe, Directly Flash it Thru TWRP/CWM.
Bug Reporting:
If any of these doesn't work tell me what's your device model then send me your Logo.bin and I'll make you another one.
Logo Requests
If you want to make a Boot Logo for your own ROM:
Make one using any photo editing apps such as GIMP photo editor, Adobe Photoshop and etc.
Make sure it is suitable for your screen resolution.
Then send it to me Via PM.
Thread Changes
First Release: For MediaTek Devices
BOOTLOGO LINKS
FIRST RELEASE:
For all Mediatek Devices with 720p resolution (720x1280)
UNIVERSAL:
APPLE WHITE: https://mega.nz/#!O5hCEShK!CAfN-oOxSrED_51UT7POo6QpJIoYaLqHN0WvrQgfYqE
APPLE BLACK: https://mega.nz/#!WwJUDT6A!yF_77YOHvXnfH_SB8UBR5JG2mnJ6DHIT5aAUqRDE1qs
GOOGLE: https://mega.nz/#!7hpxGCpT!_gOoHcYn2zaFMwwfpOFxvo3SL0GUyETucR9m-9QdcfE
WITH LENOVO BRANDING (but still compatible with Other Devices)
BATMAN ONE : https://mega.nz/#!b95nFIrJ!CIz0i0BCYBoyN7w31GMuCnfCA9m8EQt73YjnZJvkkoE
BATMAN TWO:https://mega.nz/#!XhRwETjT!VF0C6PA4vZlJMpA7vPomx3H2k5dGTMMWrXHKYiK8D5U
IRON MAN ONE:https://mega.nz/#!b0xUVBwB!n7tGo-2r7qrJBXXkw1Q1Hq7gxBDOo_ErgV1tXjQVJJ8
IRON MAN TWO: https://mega.nz/#!C9RU3AjA!aEcUAEr_A2do6AoH7h9geDPFruObMD4zKERS8xosGtk
JOKER: https://mega.nz/#!mk5HgAxL!LaqVbDHv7gfd45H6Lb5zCrXwMN7jklCIRnEbsgZDlGw
STOCK LENOVO:https://mega.nz/#!3spQAATL!mJpZzfwQn1pMUTd7CaG2oN4cPGQu6wgq2_-Bw7uZjb4
RREMIX: https://mega.nz/#!fopjBaJJ!rLbckAi0xcvT3DLz08XWP-AJpGRk-6jayFBsvVzA8gY
WITH MOTOROLA BRANDING (but still compatible with Other Devices)
MOTO: https://mega.nz/#!rsIE2JAZ!gi5jFNFbq_SGm-4ijm_sI-t25vXs5mkDsDbBnvVFrOc
BOOTLOGO FOR SPREADTRUM DEVICES - Coming Soon
BOOTLOGO PREVIEW - Coming Soon
Reserved 1
Reserved 2
Hi
I am a big fan of MultiRom and DualBoot and any other "multibooting" solutions
So I decided to take a look at DualBoot since it is more than less easy solution…
So I added S9/9+ (Exynos) properties to devices.json, but there are other known bug with DualBoot, so I fixed it by patching the kernel…
But then I get other TouchWizard Related Bug ?, after bootingup the rom I can't unlock the device, after entering the code System UI is ForceClosing and need to enter code other time ?, so it's impossible to unlock the device ?
If somebody can help to fix this problem we will get working DualBoot Patcher
Thanks
Can someone please help?
I tried to use the modded .json file from VagKout but on the one hand it crashes randomely and always on the ´Roms´ page an on the other there is no S9 shown in the list of devices?!
Thanks...
Just got my s9 and this was the first thing I looked for, I miss this I used to use on my s8+ all the time. Any update to this?
[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE][SIZE=+2]Specific to[/SIZE]
Motorola One Action
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
{
"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"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters...
...
...
...To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
FAQs for Device Thread link
Index for Device Thread Link
Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here.
I'm not planning on adding every Rom or Mod,
but if you have a suggestion for other links
Please post them here.
FAQs
Models XT2013-1, XT2013-2
Codename: Troika_Sprout
UnLocking the Bootloader
ReLocking the Bootloader
[Fixing] Baseband <not found> / IMEI=0 / No Network After Flash / Issues
Fixing your Moto stuck in Qualcomm QHSUSB_Bulk or qloader mode
Using Lenovo's MOTO Smart Assistant to Update/Repair/Backup
Custom Roms/Recovery/Root/
https://forum.xda-developers.com/one-action/how-to/twrp-magisk-root-motorola-one-action-t3975883
Firmware
Firmware likely at
https://mirrors.lolinet.com/firmware/moto/
Specs
https://www.gsmarena.com/motorola_one_action-9739.php
https://www.getdroidtips.com/list-m...e/#Motorola_One_SeriesCodename_and_Model_Name
Hi,
Can anyone tell me if this is phone supports Wi-Fi Calling in the UK please?
Motorola one Action Rom help
Hey soo i use XDA since my 6th class (Not with this Account ) many Phone and Roms so no i have an Rom question i have an Moto one Action yeah is really nice..but im a people how Love Testing Roms
But for this Phone they are Not many Roms in the Internet but Yesterday i found this this articel (Link below )so my question is have anyone tried this Rom
or i try to make one Rom for this Phone but i need Help im only 18 but i will try it to Port MIUI so can anyone Help me
Thanks
And a Happy new year
Ps: greetings from Germany and sorry for my english xD
Link of this Rom i found:
getdroidtips.com/aosp-android-10-motorola-one-action
Hi ?
where is the option to enable fingerprint locking as could be done in moto G5? ?
Hello!
Anybody knows why the content on the status bar isn't on the status bar? I enabled developer options and chose the "Hide" option on the device cutout tab
mirunica said:
Hello!
Anybody knows why the content on the status bar isn't on the status bar? I enabled developer options and chose the "Hide" option on the device cutout tab
Click to expand...
Click to collapse
When you choose to hide the cutout, it blacks out the top portion of the screen in an attempt to hide the camera cutout. It's not trying to take the shape of the cutout. It's just trying to hide it by blacking out the rest of the space.
Thing is...if you choose to hide the cutout, I think that's what it's supposed to do. I could be wrong though. But I think it's normal for this case that the status bar is also moved below that "virtual cutout". Basically it's treating the entire top portion of the screen as a giant "notch". In my opinion, that's a waste of space, so I'd suggest to better leave it default.
However, if you wanna have the status bar on a black background, so that the camera is not that obvious, and basically hide it a little better, while also having the status bar up top, simply choose a different wallpaper, one where the top part is black, or edit one, so that the top part of it is black. But...I think that might look kinda weird. So if that's what you're looking for, go for it. If not, just use a regular dark/black wallpaper.
Personally, that camera cutout doesn't bother me that much. And I prefer it over a regular notch in the middle of the screen. But that could be just my personal preference.
I have enabled hidden screen recorder in adb settings where I can get the settings and how to save recordings
sd_shadow said:
This thread has been created
for
Questions & Answers/Troubleshooting
Specific to
Motorola One Action
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
Please keep discussion focused, on questions pertaining to this Device
List of supporters...
...
...
...To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to readForum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
FAQs for Device Thread link
Index for Device Thread Link
Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here.
Click to expand...
Click to collapse
So this won't work for my Moto one action (2013-4?)
"SIM 2 Not Allowed"
When placing two chips in the device, sim 2 does not work and a message "SIM 2 not allowed" appears.
How to solve this and use the two chips normally?
Hey brother if this helps I relocked mine but got the same screen but I did see a message via CMD Windows 10 during fastboot when relocking the bootloader saying that I had to go under developer options and enable OEM bootloader unlock then re send the command via fastboot in CMD so I did so and that pesky warning screen on my motto one action about unlocked bootloader went away that's also after using the rescue software to rid of TWRP, Magic and root and put the original stock firmware north american latest back on my phone.
TDJANUBIS said:
Hey brother if this helps I relocked mine but got the same screen but I did see a message via CMD Windows 10 during fastboot when relocking the bootloader saying that I had to go under developer options and enable OEM bootloader unlock then re send the command via fastboot in CMD so I did so and that pesky warning screen on my motto one action about unlocked bootloader went away that's also after using the rescue software to rid of TWRP, Magic and root and put the original stock firmware north american latest back on my phone.
Click to expand...
Click to collapse
Sorry for dup post new to this form pls delete reply post thank you
I'm hoping someone here can help me. I unfortunately do not understand much about build.prop but I'm wanting to understand. I've factory reset my phone without fixing my issue so I took a look at my recovery logs which look like this tmp/recovery.log, I am hoping someone has a stock build.prop for the xt2013-4 and what is the best way to tell if there is something wrong with the phone?
Anyone who's still on stock (android 10) mind getting the device fingerprint for me please?
Ariold said:
Anyone who's still on stock (android 10) mind getting the device fingerprint for me please?
Click to expand...
Click to collapse
ro.system.build.fingerprint=motorola/troika_m1/troika:10/QSBS30.121-12-12-7/702ad:user/release-keys
Sorry for posting even more questions, but I'd like to know:
I'm currently on LineageOS 18.1 (https://forum.xda-developers.com/t/rom-unofficial-troika-11-lineageos-18-1.4276001/) and wanted to try out the LineageOS 17.1 (https://forum.xda-developers.com/t/rom-unofficial-troika-10-lineageos-17-1.4158525/)
TWRP seems to flash the ROM just fine, with no errors, but when I try to flash Gapps, it gives me error 20 (incompatible android version). Anyone have any ideia why that might be happening?
For reference I'm using TWRP 3.3.1, and I'm doing a clean flash.
Also, if I wanted to get my device back to stock. Like, factory stock, as if just purchased. What would be the best of doing it?
Someone posted a link with the stock roms but they're not flashable with TWRP. (https://mirrors.lolinet.com/firmware/moto/troika/official/RETBR/)
Lastly, while I am satisfied and grateful for the custom ROMs currently available, I must admit there aren't many options to choose from at the moment. Why is that? Is it not popular? Or not a worthwhile device? Or are developers simply not interested?
Thanks in advance for any answer
Ariold said:
Sorry for posting even more questions, but I'd like to know:
I'm currently on LineageOS 18.1 (https://forum.xda-developers.com/t/rom-unofficial-troika-11-lineageos-18-1.4276001/) and wanted to try out the LineageOS 17.1 (https://forum.xda-developers.com/t/rom-unofficial-troika-10-lineageos-17-1.4158525/)
TWRP seems to flash the ROM just fine, with no errors, but when I try to flash Gapps, it gives me error 20 (incompatible android version). Anyone have any ideia why that might be happening?
For reference I'm using TWRP 3.3.1, and I'm doing a clean flash.
Click to expand...
Click to collapse
The dev is active, I suggest asking in the rom thread.
Ariold said:
Also, if I wanted to get my device back to stock. Like, factory stock, as if just purchased. What would be the best of doing it?
Someone posted a link with the stock roms but they're not flashable with TWRP. (https://mirrors.lolinet.com/firmware/moto/troika/official/RETBR/)
Click to expand...
Click to collapse
You need to flash stock firmware with fastboot.exe or LMSA
Ariold said:
Lastly, while I am satisfied and grateful for the custom ROMs currently available, I must admit there aren't many options to choose from at the moment. Why is that? Is it not popular? Or not a worthwhile device? Or are developers simply not interested?
Thanks in advance for any answer
Click to expand...
Click to collapse
Motorola devices have largely lost the interest of Devs.
As android has matured and most unique features that custom roms had, are now part of stock android.
Most people that care about the android version, buy a new device every year or two.
So fewer people are using custom roms.
and Roms are built by the owners of the devices.
sd_shadow said:
The dev is active, I suggest asking in the rom thread.
Click to expand...
Click to collapse
Ops. I don't know why I didn't think of posting there first. Sorry!
sd_shadow said:
You need to flash stock firmware with fastboot.exe or LMSA
Click to expand...
Click to collapse
Got it, thanks a lot for the links!
sd_shadow said:
Motorola devices have largely lost the interest of Devs.
As android has matured and most unique features that custom roms had, are now part of stock android.
Most people that care about the android version, buy a new device every year or two.
So fewer people are using custom roms.
and Roms are built by the owners of the devices.
Click to expand...
Click to collapse
I see... I thought it was something exclusive to this device but in that case it's more of a general "problem".
Like I said, I'm happy with what we have of course! I was just curious because I think the Moto One Action has some potential, so when I came here for the first time I thought it would have a more active scene.
Thanks for the quick response btw!
Ariold said:
Ops. I don't know why I didn't think of posting there first. Sorry!
Got it, thanks a lot for the links!
I see... I thought it was something exclusive to this device but in that case it's more of a general "problem".
Like I said, I'm happy with what we have of course! I was just curious because I think the Moto One Action has some potential, so when I came here for the first time I thought it would have a more active scene.
Thanks for the quick response btw!
Click to expand...
Click to collapse
Also Motorola is a small part of the Android market.
With so many Android OEMs, and fewer active Devs, you just don't see many options for many devices anymore.