[BQ Aquaris X Pro Guides, News, & Discussion] nuv:
Hi [MENTION=9615172]crucco37[/MENTION],

I am surprised about the confusion..

if you had a running system with TWRP+Magisk before the update, all you need to do is to follow the steps from section '5 Update to newest firmware'.

Today, I updated to BQ FW 2.5.1 and copied the shell window as reference and commented a bit:

Microsoft Windows [Version 10.0.17763.292]
(c) 2018 Microsoft Corporation. Alle Rechte vorbehalten.

C:\Users\$MYUSERNAME>E:

E:\>cd E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\2.5.1_20190114-1551-bardockpro_bq-user-1492-Fastboot-FW

E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\2.5.1_20190114-1551-bardockpro_bq-user-1492-Fastboot-FW>cmd
Microsoft Windows [Version 10.0.17763.292]
(c) 2018 Microsoft Corporation. Alle Rechte vorbehalten.

E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\2.5.1_20190114-1551-bardockpro_bq-user-1492-Fastboot-FW>cmd
Microsoft Windows [Version 10.0.17763.292]
(c) 2018 Microsoft Corporation. Alle Rechte vorbehalten.

I just started 'cmd a couple of times because the .bat exits the shell and i did want to have the command window open afterwards.

The 8953_fastboot_all_images_nuv_2.5.1.bat from the next command is the default .bat, only with the 2 lines commented out (in the .sh script you should use the hashtag '#' to comment the lines instead of 'rem')

( rem fastboot flash userdata userdata.img

rem fastboot flash recovery recovery.img )

E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\2.5.1_20190114-1551-bardockpro_bq-user-1492-Fastboot-FW>8953_fastboot_all_images_nuv_2.5.1.bat
for not erase modemst1 and modemst2
target reported max download size of 534773760 bytes
sending 'tz' (1499 KB)...
OKAY [ 0.061s]
writing 'tz'...
OKAY [ 0.031s]
finished. total time: 0.092s
target reported max download size of 534773760 bytes
sending 'sbl1' (378 KB)...
OKAY [ 0.031s]
writing 'sbl1'...
OKAY [ 0.032s]
finished. total time: 0.077s
target reported max download size of 534773760 bytes
sending 'rpm' (170 KB)...
OKAY [ 0.045s]
writing 'rpm'...
OKAY [ 0.017s]
finished. total time: 0.062s
target reported max download size of 534773760 bytes
sending 'aboot' (616 KB)...
OKAY [ 0.050s]
writing 'aboot'...
OKAY [ 0.027s]
finished. total time: 0.077s
target reported max download size of 534773760 bytes
sending 'devcfg' (39 KB)...
OKAY [ 0.049s]
writing 'devcfg'...
OKAY [ 0.017s]
finished. total time: 0.067s
target reported max download size of 534773760 bytes
sending 'lksecapp' (56 KB)...
OKAY [ 0.034s]
writing 'lksecapp'...
OKAY [ 0.034s]
finished. total time: 0.067s
target reported max download size of 534773760 bytes
sending 'keymaster' (220 KB)...
OKAY [ 0.034s]
writing 'keymaster'...
OKAY [ 0.033s]
finished. total time: 0.067s
target reported max download size of 534773760 bytes
sending 'cmnlib' (200 KB)...
OKAY [ 0.036s]
writing 'cmnlib'...
OKAY [ 0.031s]
finished. total time: 0.068s
target reported max download size of 534773760 bytes
sending 'cmnlib64' (254 KB)...
OKAY [ 0.031s]
writing 'cmnlib64'...
OKAY [ 0.031s]
finished. total time: 0.062s
target reported max download size of 534773760 bytes
sending 'tzbak' (1499 KB)...
OKAY [ 0.063s]
writing 'tzbak'...
OKAY [ 0.031s]
finished. total time: 0.094s
target reported max download size of 534773760 bytes
sending 'sbl1bak' (378 KB)...
OKAY [ 0.031s]
writing 'sbl1bak'...
OKAY [ 0.031s]
finished. total time: 0.063s
target reported max download size of 534773760 bytes
sending 'rpmbak' (170 KB)...
OKAY [ 0.016s]
writing 'rpmbak'...
OKAY [ 0.016s]
finished. total time: 0.047s
target reported max download size of 534773760 bytes
sending 'abootbak' (616 KB)...
OKAY [ 0.047s]
writing 'abootbak'...
OKAY [ 0.016s]
finished. total time: 0.063s
target reported max download size of 534773760 bytes
sending 'devcfgbak' (39 KB)...
OKAY [ 0.031s]
writing 'devcfgbak'...
OKAY [ 0.031s]
finished. total time: 0.063s
target reported max download size of 534773760 bytes
sending 'lksecappbak' (56 KB)...
OKAY [ 0.031s]
writing 'lksecappbak'...
OKAY [ 0.031s]
finished. total time: 0.062s
target reported max download size of 534773760 bytes
sending 'keymasterbak' (220 KB)...
OKAY [ 0.031s]
writing 'keymasterbak'...
OKAY [ 0.031s]
finished. total time: 0.062s
target reported max download size of 534773760 bytes
sending 'cmnlibbak' (200 KB)...
OKAY [ 0.031s]
writing 'cmnlibbak'...
OKAY [ 0.016s]
finished. total time: 0.047s
target reported max download size of 534773760 bytes
sending 'cmnlib64bak' (254 KB)...
OKAY [ 0.031s]
writing 'cmnlib64bak'...
OKAY [ 0.016s]
finished. total time: 0.047s
erasing 'misc'...
OKAY [ 0.031s]
finished. total time: 0.047s
erasing 'boot'...
OKAY [ 0.047s]
finished. total time: 0.047s
target reported max download size of 534773760 bytes
sending 'modem' (86016 KB)...
OKAY [ 1.906s]
writing 'modem'...
OKAY [ 0.625s]
finished. total time: 2.547s
target reported max download size of 534773760 bytes
erasing 'system'...
OKAY [ 0.578s]
sending sparse 'system' 1/6 (516696 KB)...
OKAY [ 12.563s]
writing 'system' 1/6...
OKAY [ 4.016s]
sending sparse 'system' 2/6 (516941 KB)...
OKAY [ 13.064s]
writing 'system' 2/6...
OKAY [ 4.845s]
sending sparse 'system' 3/6 (521744 KB)...
OKAY [ 13.142s]
writing 'system' 3/6...
OKAY [ 5.000s]
sending sparse 'system' 4/6 (519043 KB)...
OKAY [ 12.173s]
writing 'system' 4/6...
OKAY [ 4.750s]
sending sparse 'system' 5/6 (517520 KB)...
OKAY [ 12.081s]
writing 'system' 5/6...
OKAY [ 5.078s]
sending sparse 'system' 6/6 (69860 KB)...
OKAY [ 1.609s]
writing 'system' 6/6...
OKAY [ 0.516s]
finished. total time: 89.431s
target reported max download size of 534773760 bytes
erasing 'cache'...
OKAY [ 0.063s]
sending 'cache' (6248 KB)...
OKAY [ 0.156s]
writing 'cache'...
OKAY [ 0.078s]
finished. total time: 0.297s
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.375s]
writing 'dsp'...
OKAY [ 0.125s]
finished. total time: 0.500s
target reported max download size of 534773760 bytes
sending 'mdtp' (17390 KB)...
OKAY [ 0.406s]
writing 'mdtp'...
OKAY [ 0.125s]
finished. total time: 0.547s
erasing 'splash'...
OKAY [ 0.047s]
finished. total time: 0.047s
target reported max download size of 534773760 bytes
sending 'splash' (176 KB)...
OKAY [ 0.031s]
writing 'splash'...
OKAY [ 0.031s]
finished. total time: 0.063s
erasing 'DDR'...
OKAY [ 0.031s]
finished. total time: 0.031s
target reported max download size of 534773760 bytes
sending 'boot' (28045 KB)...
OKAY [ 0.611s]
writing 'boot'...
OKAY [ 0.203s]
finished. total time: 0.829s
rebooting...

finished. total time: 0.031s
Drücken Sie eine beliebige Taste . . .

Here, you have to be fast, because in this example, the 'fastboot reboot' command will reboot after flashing, so you have to sit next to the flashing process and wait for the reboot.

When the phone reboots, you'll have to hit a volume key at the screen which says 'software can't be checked for corruption' with the 5 sec timeout.

View attachment 4281239

Select recovery and start recovery with the power button.

View attachment 4281240

Wait untill TWRP has been started.

Inside TWRP select 'advanced' and 'adb sideload' and swipe to start the sideload mode.

E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\2.5.1_20190114-1551-bardockpro_bq-user-1492-Fastboot-FW>cd ..

E:\backups\android\BQ-Aquaris-X-Pro\04_firmware>cd ..

E:\backups\android\BQ-Aquaris-X-Pro>cd 03_TWRP_Magisk

E:\backups\android\BQ-Aquaris-X-Pro\03_TWRP_Magisk>cd 2018-12-08_Magisk-v18.0\

E:\backups\android\BQ-Aquaris-X-Pro\03_TWRP_Magisk\2018-12-08_Magisk-v18.0>adb sideload Magisk-v18.0.zip
adb server version (39) doesn't match this client (40); killing...
* daemon started successfully
Total xfer: 1.61x

E:\backups\android\BQ-Aquaris-X-Pro\03_TWRP_Magisk\2018-12-08_Magisk-v18.0>

Now, in TWRP, select 'reboot system' and you are ready.

-----------------------------------------------------------------------------------------------

I hope with the text above it should be clear now, but hoping to de-confuse you I will try to answer your questions in detail ;)

Which bootscreen do you mean? The first picture is fastboot mode

View attachment 4281235

This should be the mode the phone boots into right after running the .bat/.sh

TWRP has not been touched at this point (and to be precise, TWRP will not be modified anywhere when updating.)

We comment out 2 lines:

- The one with userdata is for ... your personal user data :p and settings

- the one with recovery is TWRP. We don't flash it because we don't want the stock recovery, but keep TWRP

? I do not understand. Why 'not enough time'? With the volume buttons, you stop the normal booting process at this point:

View attachment 4281239

and get to the menu where you can choose which mode should be entered (normal boot to system, recovery, fastboot, ...)

View attachment 4281240

The only "time critical" thing is to hit one volume button at the warning screen, but after that, you have all the time you need.

see my listing above (from today, updating to 2.5.1)

Alternatively take a look at post#1, section '4.3 Install TWRP and Magisk' and read from the text passage "Now we flash Magisk from TWRP with the adb sideload function. [...]"

The boot screens remain stock all the time.. (?)

Ah, great. Alternative to adb sideload. That's perfectly fine. I just prefer the sideload, because at the point where the install is needed, the phone is still connected to the PC and I think it's easier, but as always, there are multiple ways.

No need to uninstall anything when updating firmware with the USB flash method.

That doesn't make sense to me. The boot.img should match your firmware.

Btw. the boot.img will get patched by magisk, so the order is:

- old boot.img (patched by magisk)

- flashing the complete firmware including the boot.img from the new firmware .zip

- reboot into TWRP without an attempt to boot to system

- install Magisk (adb sideload or flash the zip): this patches the stock boot.img

- first reboot into the new system

:crying: