UMIDIGI Power 5S V1.0_20211202 ROM - SPD release

bencebacsi

This is the SPD Flash Tool release of the
V1.0_20211202 system software
for UMIDIGI Power 5S

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 Power 5S 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:

• System language improvements
• FM frequency range adjusted to 76MHZ~108MHZ
• Other minor bug fixes and system optimization
  

FOTA version: UMIDIGI_Power_5S_V1.0_20211008_20211202-1630

--------------------------------------------------------------------------------
SP Flash Tool
Resources:

Flashtool tutorial: https://bit.ly/SPDguide

ROM: >>> UMIDIGI_Power_5S_V1-0_20211202.rar <<<

Extract the .rar file before use. The scatter file (MT6765_Android_scatter.txt) is inside the extracted folder, together with the other components.

SPD Upgrade tool: UpgradeDownload_R25.21.1401.rar

SPD drivers: SPD_Driver_R4.20.0201.rar



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 an SPD Flasher. 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.

magixx

I am unable to flash magisk patched boot.img.
I've enabled Developer Mode + OEM unlocking and I can flash UMIDIGI_Power_5S_V1-0_20211202.pac using SPD_Upgrade_Tool_R26.21.2801.
But using platform-tools_r31.0.3-windows for fastboot fails.

1. > .\adb.exe reboot bootloader
   
2. > .\fastboot flashing unlock
   
3. FAILED (remote: 'unknown cmd.')
   
4. fastboot: error: Command failed
   
5. > .\fastboot.exe oem unlock
   
6. FAILED (remote: 'Unlock bootloader fail.')
   
7. fastboot: error: Command failed
   
8. > .\fastboot.exe flashing unlock_critical
   
9. FAILED (remote: 'Not implement.')
   
10. fastboot: error: Command failed
    
11. > .\fastboot.exe flash boot_a .\boot_patched.img
    
12. Sending 'boot_a' (65536 KB)                        OKAY [  2.065s]
    
13. Writing 'boot_a'                                   FAILED (remote: 'Flashing Lock Flag is locked. Please unlock it first!')
    
14. fastboot: error: Command failed
    

Copy the Code

What am I doing wrong?

plumpkibbles

magixx replied at 2021-12-14 13:58
I am unable to flash magisk patched boot.img.
I've enabled Developer Mode + OEM unlocking and I can  ...

You don't need '_critical' at the end; just 'fastboot flashing unlock' - then it will prompt you to accept or deny the action pushed from fastboot.

You don't need fastboot to flash boot.img or recovery.img either, just open SP Flash tool and where the boot or recovery image is located, click the path where the stock images are and select your TWRP or patched boot image is located. I.e. 'C:\users\user\Downloads\bla bla'.. where ever you have the images stored. Remember: deselect all other images and make sure either boot or recovery are the only ones checked on the left.

Also, it helps to start with a 'fresh' device (just written ROM or data wipe), enable developer options, then enabling the OEM Flashing and USB Debug in Dev options. Then issue the fasatboot flashing unlock command and proceed to flash TWRP or boot from either fastboot or SP Flash - either one will work.

Example after enableing USB debug: ./adb devices (lists devices attached via ADB) - ./adb reboot bootloader (goes right to fastboot) - ./fastboot flashing unlock (then press volume up) - ./fastboot erase boot - ./fastboot erase system - ./fastboot erase recovery - ./fastboot flash recovery recovery.img (TWRP) - ./fastboot flash boot boot.img (patched boot). That's all command line, no skips. You don't necessarily need the patched boot.img for flashing a new system too; just root. Is there any point to rooting anymore though; with all the Android recent options enabled and such? Just wondering.
One BIG step you're going to have to do; once you flash your images including TWRP, absolutely make sure you boot into recovery and not normal system boot. If you do no boot into recovery, TWRP will be overwritten with the stock recovery image. May or may not actually happen, but has happened to me every time on my A5 Pro (currently on Android 10 Pixle Experience UI).

Hope that helped!

andres3016

Help, I'm having trouble whit the flashing process. I don't know what else to do.