UMIDIGI A15T V1.0_20240424 ROM - SPFT release

bencebacsi Post time 2025-4-3 18:38:21 | Show all posts   [Copy link]
1 7957
View: 7957|Reply: 1

UMIDIGI A15T V1.0_20240424 ROM - SPFT release

  [Copy link]
Post time 2024-5-15 03:07:28 | Show all posts |Read mode
This is the SP Flash Tool release of the
V1.0_20240424 system software
for UMIDIGI A15T

Flash tool operation is recommended to experienced users only. If you are not yet an experienced flash tool user, please carefully read the flash tool tutorial before proceeding, and strictly follow each instruction.

Except if an authorized or responsible expert directly asked you to do that,
never format the flash chip of your device or you instantly lose your warranty!

UMIDIGI A15T receives all updates automatically via FOTA method. You need this tool only in case of emergency (if you've bricked your phone), if you want to apply a clean install or if you want to clear all root access and custom recovery to make your phone able to receive FOTA updates again. Moreover, flashing with SPFT is the only option to repair (replace) damaged system software.




Changelog:
First release for manufacturing



FOTA version: UMIDIGI_A15T_V1.0_20240424_20240424-1401

--------------------------------------------------------------------------------
SP Flash Tool

Resources:

Flashtool tutorial: http://bit.ly/SPFTguide

ROM:
>>> UMIDIGI_A15T_V1-0_20240424.rar <<<
Extract the .rar file before use. The scatter file (MT6785_Android_scatter.txt) is inside the extracted folder, together with the other components.

SPFT:
SP_Flash_Tool_v5.2316.rar

VCOM driver: Windows 10 and 11 can automatically install it. Please make sure that your Windows is logged in with administrator rights and your computer has a working internet connection when first time connecting your phone.


Here's an optional solution to start the flashing process on your UMIDIGI A15T if the standard method doesn't work.
It's especially useful if your phone is bricked or is stuck in bootloop

1. Connect your phone to USB.
2. Start the flashing process with the Download button in the flasher app.
3. Press and hold the power button of your phone until the flashing process starts (red bar appears at the bottom of the app window), then release it. In this process you have to keep the power button pressed for about 10 seconds.
4. Wait until the flashing process finishes.



Kind request from users:
Please report any kind of new issues you experience after installing this update only if you've already flashed this ROM with SP Flash Tool in Firmware Upgrade mode. In rare cases a FOTA update can cause more or less serious malfunctions but that means only the update process went wrong, not a badly developed ROM. An updated stock ROM, especially related to the basic functions will not cause any new issues but will solve some of the existing ones.

0

threads

1

posts

8

credits

New Member

Rank: 1

credits
8
Post time 2025-4-3 18:38:21 | Show all posts
When I swipe to close an app on the history screen,
force stopping is called from com.DDU.launcher and the app cannot move to background operation.
As a result, I cannot receive notifications from the app.
Is this behavior correct?

  1. 04-03 19:31:52.975  1460  3261 I ActivityManager: Force stopping jp.naver.line.android appid=10181 user=0: from pid 22717
  2. 04-03 19:31:52.976  1460  3261 I ActivityManager: Killing 24430:jp.naver.line.android/u0a181 (adj 700): stop jp.naver.line.android due to from pid 22717
  3. 04-03 19:31:52.983  1460  3261 I ActivityManager: Killing 24685:com.google.android.webview:sandboxed_process0:org.chromium.content.app.SandboxedProcessService0:0/u0a181i19 (adj 0): isolated not needed
  4. 04-03 19:31:53.020  1460 13445 V ActivityManager: Death received in com.android.server.am.ActivityManagerService$AppDeathRecipient@9da6a61 for thread android.os.BinderProxy@66f0986
  5. 04-03 19:31:53.120  1460 13457 V ActivityManager: Death received in com.android.server.am.ActivityManagerService$AppDeathRecipient@ecfd56c for thread android.os.BinderProxy@f0cf735
  6. 04-03 19:31:53.120  1460 13457 V ActivityManager: Got obituary of 24430:jp.naver.line.android
  7. 04-03 19:31:53.121  1460  1594 W ActivityManager: setHasOverlayUi called on unknown pid: 24430
  8. 04-03 19:31:55.973  1460  3261 W ActivityManager: Unable to start service Intent { cmp=com.DDU.secureguard/com.zhuoyi.security.service.service.SecurityServiceAppManager } U=0: not found

  9. u0_a44       22717   719 16823324 300056 0                  0 S com.DDU.launcher
  10. u0_a181      24430   719 35843776 448376 0                  0 S jp.naver.line.android
Copy the Code
You have to log in before you can reply Login | WELCOME TO UMIDIGI COMMUNITY

Points Rules

Quick Reply Top Back to list