[HOW-TO] BQ Aquaris X Pro | [Stock-ROM] Unlock,Recovery,Root,Upgrade (TWRP/Magisk) - BQ Aquaris X Pro Guides, News, & Discussion

Hi everyone.
This Post (post #1) shows the complete process of unlocking, flashing, rooting etc. in general, it may refer to old firmware and/or tool versions but the steps remain the same for newer versions. The chapters rely on each other so to be sure, just follow every step. Note: Check out post #2 for additional information regarding updating, tools, known problems/pitfalls.
----- Info [2021-02-05] -----
BQ/Mundo Reader S.L. stopped producing Smartphones (since ~2019(?)), the website is down since March 2020. Original BQ firmware is still available for download (see post #230):
Last version of BQs website via archive.org: https://web.archive.org/web/20200320014304/https://www.bq.com/en/support/aquaris-x-pro/support-sheet
Direct link to latest firmware file:
Firmware 2.11.0 (Android 8.1.0 Oreo) (MD5: CA7DCCB4BD101AF64DCFFAAB71CBD476 )
https://storage.googleapis.com/otas...-1510-bardockpro_bq-user-2395-Fastboot-FW.zip
----- End of Info [2021-02-05] -----
After all steps you will have your Aquaris X / X Pro with:
- BQ stock ROM
- (unlocked bootloader)
- TWRP recovery
- Magisk
° root access (managed by Magisk)
° (the possibility to install additional Magisk modules)
° pass Google SafetyNet checks
Disclaimer:
I am in no way responsible for anything resulting in you following the provided instructions in this thread.
It worked for me, but that does not mean it will 100% work for you. You are responsible for any side effects and damage caused to your device which includes, but is not limited to software and/or hardware destruction of the device etc. Rooting may void your warranty.
Only continue if you feel safe in what you are doing.
(Thanks to @shifattk for some text parts (seen here).)
Let's start with an index:
Intro
Boot modes
Set up the PC / Get all files
Start from scratch
Update to newest firmware
Notes/Troubleshooting
Links
Changelog
1 Intro
Recently got me the BQ Aquaris X Pro 128GB and wrote this because of the lack of any documentation on xda regarding unlocking/flashing/rooting/...
In this post you will find a collection of information i found spread over various sources.
I don't know if everything is right, so please report any wrong parts or missing information.
Just a sidenote: At the moment i will be using the stock rom, because it is really clean and slim and i don't want to continuously keep on track with all updates some custom roms have (and get along with possible restrictions in functionality). Because of this, an important advantage for the stock rom is that is 'just works'™ and there are regular updates which are (hopefully ) tested by BQ before release.
So here is a screenshot what the default app launcher looks like and which apps are preinstalled
{
"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"
}
The following parts will include:
- unlocking the bootloader
- installing TWRP recovery and Magisk (low level system access, root, ...)
- update BQ firmware
- re-installing TWRP/Magisk/root
Alternatively, one could easier update first and then do all the Recovery- and rootstuff, but I wanted to verify that a system update will be possible without data loss at any time later on. As i read in other forums, it is a bad idea to use the OTA functionality (over-the-air = regular/stock way for system updates) when running a rooted system with unlocked bootloader. (I didn't test this, but i didn't want to find out either..)
Warning: If you used the phone before - backup your files! The phones data will get wiped in the process (at least while unlocking the bootloader)!
Note: I took out my SIM card for the whole process and never set up WLAN, so the phone never got internet access until i disabled the search for software updates. This may prevent the update notifications.
Thanks to
- everyone at the android-hilfe.de forum, especially syscrh and blur for their threads (see [9],[10])
- topjohnwu, developer of Magisk
- Kra1o5, the TWRP maintainer for the Aquaris X Pro
- the BQ team for their firmware and of course for packaging and hosting the firmware
2 Boot modes
Precondition for both modes: phone off, no usb connection
Fastboot mode: vol_down + pwr
(if entered accidentally, long press pwr for >12sec, screen switches off, then phone will reboot (to system) after 10-20secs)
Recovery: vol_up + pwr
(navigate with vol_up and vol_down buttons, select/confirm with power button)
In detail (for new users): while phone is off, press and hold the volume-up/down button and directly after this (still holding vol_up/down) press and hold the power button as well. Hold both buttons until you see the logo and hold for approx. 1 more second. then release both buttons.
For further information or other BQ phones, take a look here: [8]
3 Set up the PC / Get all files
Get Android Debug Bridge (adb) drivers and newest firmware from BQ [1](DE) / [1](EN)
- Install drivers
- extract the firmware zip
If you already got adb on your computer, check the version - some commands may not be availlable.
For adb sideload via TWRP recovery, you should have at least adb version 1.0.32 [2]
You can get the SDK Platform Tools from Google. [3] At the time of writing (2017-09-14), they are on version 1.0.39.
A good choice may be to use the adb tools packaged in the firmware update .zip from BQ.
For the Aquaris X Pro firmware 1.4.3_20170809-1111-bardock-user-983-Fastboot-FW.zip, the tools are on version 1.0.36.
Get the TWRP image file for the Aquaris X Pro [4].
(Take a look at [5] if you own the Aquaris X.)
Get Magisk flashable .zip [6]
To be sure get the uninstaller and the Magisk Manager .apk as well.
4 Start from scratch
preconditions:
- New phone with unmodified stock rom
- Versions as reference:
- using windows 10 here, so some of the following parts may be windows specific. Linux users (ok, debian based linux users) should take a look at the packages 'android-tools-adb' and 'android-tools-fastboot'.
4.1 Prepare phone
Activate developer mode and, from the developer options:
- allow unlocking of the bootloader
- enable USB debugging mode.
Disable software update search:
- Settings -> About phone -> System updates -> untick the checkbox 'Auto-check'
Detail regarding activation of developer options:
cite from [4]
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging.
Click to expand...
Click to collapse
On the same screen enable the option 'OEM unlocking' as well.
Note: User overbim reported in post #240 that the 'OEM unlocking' option was greyed out. After having activated WIFI and having connected to a WLAN the option was accessible short time after that.
4.2 Unlock the bootloader
Go to fastboot mode (Power off, then hold vol_down + pwr).
Connect to PC via USB.
After allowing unlocking in the developer options, you should see:
We will be using the following fastboot commands: (from 'fastboot --help')
flashing get_unlock_ability
Queries bootloader to see if the device is unlocked.
flashing unlock
Unlocks the device. Allows flashing any partition except bootloader-related partitions.
flashing unlock_critical
Enables flashing bootloader-related partitions.
Click to expand...
Click to collapse
Check if bootloader unlocking is allowed, it should give the response '1'
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 1
OKAY [ 0.018s]
finished. total time: 0.020s
If you missed the 'OEM unlocking' option earlier, then you'll get:
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 0
OKAY [ 0.013s]
finished. total time: 0.013s
Stop here and go back to step '4.1 Prepare phone'
FYI, additional information:
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.053s]
finished. total time: 0.053s
Okay, now the first part of the unlocking process:
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot flashing unlock
...
OKAY [ 0.074s]
finished. total time: 0.076s
Choose yes:
wait a couple of minutes, there will be this screen:
After that, you will get to the welcome screen.
Disconnect USB and switch off the phone.
Enter fastbook mode again, connect usb
Now the first lock should be gone:
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.054s]
finished. total time: 0.058s
And now for part two of the unlocking process:
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot flashing unlock_critical
...
OKAY [ 0.075s]
finished. total time: 0.076s
Choose yes again:
You will get the encrypting screen again:
Followed by the screen with the 'Aquaris X' animation and finally the welcome screen.
Disconnect USB, switch off.
Enter fastbook mode again, connect usb and check if both unlocks went fine:
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.058s]
finished. total time: 0.060s
Done.
Stay in fastboot mode for the next step.
4.3 Install TWRP and Magisk
Now we only need one command to flash the TWRP recovery (adjust to your filepaths)
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot flash recovery ..\..\03_TWRP_Magisk\twrp-3.1.1-0-bardock_pro.img
target reported max download size of 536870912 bytes
sending 'recovery' (28078 KB)...
OKAY [ 0.635s]
writing 'recovery'...
OKAY [ 0.180s]
finished. total time: 0.817s
Now we restart the phone and go into TWRP recovery immediately at reboot - there will be an info screen with a 5 second timeout. press volume_up as soon as you see this screen.
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot reboot
rebooting...
finished. total time: 0.006s
Here is the screen you'll see after reboot:
After pressing volume_up, you'll see an options menu
Select 'Recovery' with vol_up/down and chose the option with the power button.
You'll see the options screen again, but this time just wait 5 seconds or press the power button and TWRP recovey will start.
TWRP will ask if it should modify the system partition. Don't apply the modifications, instead choose 'Keep Read Only'.
Note: If you chose 'yes', then take a look at section '6.1 troubleshooting'.
Now we flash Magisk from TWRP with the adb sideload function.
In TWRP choose 'Advanced' and there 'ADB sideload'. Just swipe and start the sideload mode.
From the PC, we initiate the transfer and installation of the Magisk .zip:
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>adb sideload ..\..\03_TWRP_Magisk\Magisk-v14.0.zip
loading: '..\..\03_TWRP_Magisk\Magisk-v14.0.zip'* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Total xfer: 1.69x
Now we can reboot to system. TWRP will be kept (although we only selected the temporary variant before).
This should be the first system bootup after the wipe from the bootloader unlocking process, so you will get to the welcome wizard. At this point I chose to skip the SIM card step (because i did not insert any SIM) and leave the WLAN unconfigured.
In the settings menu, go to 'About Phone' and 'Software Update' and disable the automatic updates
This should prevent any notifications regarding OTA updates as we will update via PC with the .zip firmware downloaded from BQ.
In the system you will notice the Magisk Manager App. Through this App, you can allow and deny root access for any app (a notification will pop up if any app requests root permission).
Enable developer options (see step '4.1 prepare phone') and enable USB debugging mode again.
Allow your PC in the popup notification and check the option to always allow this PC.
5 Update to newest firmware
preconditions:
- some older stock firmware
- unlocked bootloader (both options 'unlock' and 'unlock_critical')
- TWRP recovery
- Magisk
(these should be met if you went through all steps above...)
- newest BQ firmware from step '3 Set up the PC / Get all files'
On the PC go to the folder with the extracted BQ firmware .zip
Create a copy of 8953_fastboot_all_images.bat
Comment out or delete the following lines:
Code:
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot reboot
Here is a patch, if anyone is interested:
Code:
--- 8953_fastboot_all_images.bat 2017-08-09 12:27:24.000000000 +0200
+++ 8953_fastboot_all_images_nuv.bat 2017-09-10 22:07:54.794986400 +0200
@@ -37,8 +37,11 @@
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash cache cache.img
-fastboot flash userdata userdata.img
-fastboot flash recovery recovery.img
+
+rem nuv: omit userdata and recovery to keep data and TWRP
+rem fastboot flash userdata userdata.img
+rem fastboot flash recovery recovery.img
+
rem fastboot flash sec sec.dat
fastboot flash dsp adspso.bin
fastboot flash mdtp mdtp.img
@@ -47,7 +50,9 @@
fastboot erase DDR
fastboot flash boot boot.img
-fastboot reboot
+rem nuv: omit reboot to allow a manual reboot and start of TWRP before first boot of new image
+rem fastboot reboot
+
pause
exit
With the modified batch file ready to start, we connect our phone (phone is switched on and in system) and run the batch.
Code:
[...]
erasing 'DDR'...
OKAY [ 0.020s]
finished. total time: 0.023s
target reported max download size of 536870912 bytes
sending 'boot' (22485 KB)...
OKAY [ 0.502s]
writing 'boot'...
OKAY [ 0.132s]
finished. total time: 0.636s
Drücken Sie eine beliebige Taste . . .
After the batch file finishes, manually reboot the phone and go directly to recovery! Do not boot the system yet!
Reboot:
Code:
fastboot reboot
and choose recovery with volume up and volume down like earlier in section '4.3 Install TWRP and Magisk'
Now we flash Magisk from TWRP with the adb sideload function. (again , see step 4.3 Install TWRP and Magisk'
Code:
adb sideload ..\..\03_TWRP_Magisk\Magisk-v14.0.zip
Reboot to system.
All done.
6 Notes/Troubleshooting
6.1 System update notifications
As written in step '1 Intro' and '4.3 Install TWRP and Magisk' i did not let the phone get an internet connection after the wipe (bootloader unlock) and disabled the software update feature.
I don't know if this will reliably prevent the update notifications.
As a further note, user Schubbie stated on android-hilfe.de [10], that the OTA updates get saved to the path /data/data/com.bqreaders.ota/files/bq_update_ota.zip so maybe you can delete the file if an unwanted update notification pops up.
6.1 Troubleshooting
As an additional information to step '4.3 Install TWRP and Magisk'
At the point after flashing TWRP and starting it the first time, I let TWRP apply the system modifications.
After that i rebooted to check if the TWRP installation was successful...
I got "device is corrupt" when I wanted to boot into system. I continued the boot process with the power button and after that, the phone got stuck at the screen with the BQ logo and the text 'Powered by Android' (waited >10min).
To revive the phone from that state, you can flash the recovery and system images from the BQ firmware .zip
Important: Use the 'old' firmware which is still on your phone - the images have to match your current installation!
Bring the phone into fastboot mode and use the commands:
Code:
1.3.5_20170620-0532-bardock-user-594-Fastboot-FW\fastboot flash recovery recovery.img
1.3.5_20170620-0532-bardock-user-594-Fastboot-FW\fastboot flash system system.img
(In my case, the phone came with 1.3.5, so obviously I used this firmware .zip from BQ)
Now the phone is back to the state unlocked bootloader with stock rom and stock recovery.
Continue with step '4.3 Install TWRP and Magisk'.
7 Links
[1]
Official BQ website - Downloads Aquaris X Pro
https://www.bq.com/de/support/aquaris-x-pro/support-sheet
https://web.archive.org/web/20200320014304/https://www.bq.com/en/support/aquaris-x-pro/support-sheet
(
Firmware 1.4.3 | MD5: 16ff81c74642189a5d09f6b73feb06d5 | https://storage.googleapis.com/otas...0170809-1111-bardock-user-983-Fastboot-FW.zip
Drivers | https://shenron.bq.com/otas/2014/Smartphones/Aquaris_E5_LTE/Tools&Drivers/Drivers qualcomm + adb.rar
)
[2]
TWRP - ADB sideload information
https://twrp.me/faq/ADBSideload.html
[3]
SDK Platform Tools
https://developer.android.com/studio/releases/platform-tools.html
[4]
TWRP recovery
https://twrp.me/bq/bqaquarisxpro.html
Section 'Download Links'
[5]
TWRP - BQ devices
https://twrp.me/Devices/BQ/
[6]
[2017.9.6] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+]
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
https://github.com/topjohnwu/Magisk/releases
[7]
root Alternative
TWRP maintainer for Aquaris X (Kra1o5) mentions SuperSU in a forum about flashing TWRP and rooting
http://www.htcmania.com/showthread.php?t=1312725
http://download.chainfire.eu/supersu
[8]
[info] recovery menu on BQ devices
http://www.mibqyyo.com/en-articles/...lla/discussion/embed/?vanilla_discussion_id=0
[9]
[Anleitung] Aquaris X/X Pro Bootloader entsperren/unlock
https://www.android-hilfe.de/forum/...-pro-bootloader-entsperren-unlock.830125.html
[10]
Aquaris X/X Pro - Firmwareupdate mit Root
https://www.android-hilfe.de/forum/...s-x-x-pro-firmwareupdate-mit-root.834283.html
8 Changelog
2021-12-27: added info in chapter '4.1 Prepare phone' regarding OEM unlocking and WIFI
2021-02-05: added Info regarding BQs website on top of post
2020-07-31: added link to Magisk Github release page
2018-03-23: Added disclaimer...
2017-12-31: Edited info at top of post
2017-12-30: Played with the hide-content-buttons. Hopefully it'll be easier to navigate through the long post now. Adapted First sentences.
2017-12-26: Edited info at top of post
2017-11-18: Added info at top of post, moved changelog to post #1
2017-11-11: Added links to the [<number>] References - wow!
2017-11-11: fixed typos, little cosmetics, little text changes in '4.1 Prepare phone', corrected section references
2017-09-23: added pictures, codeblocks, formating...
2017-09-23: initial post, work in progress
[EOF]

9 Additional information, comments, ...
9.0 Latest working versions:
9.0.1 Android Oreo (Android 8.1.0)
Firmware 2.11.0 (Android 8.1.0 Oreo)
Download BQ Firmware 2.11.0 for BQ Aquaris X Pro
Download BQ Firmware 2.11.0 for BQ Aquaris X
TWRP 3.4.0-0 [2019-07-20]
Download TWRP for BQ Aquaris X Pro
Download TWRP for BQ Aquaris X
Magisk v20.4 stable (20400) / Magisk Manager App v7.5.1 (267)
Download from Magisk Forum Thread
Download from Magisk Github release page
Minimum required versions for Oreo:
BQ Firmware: 2.0.0 (Android Oreo 2.1.0)
prerelease from beta (see screenshot below for details)
the official update .zip (confirmed by iss0 in post#95))
TWRP 3.2.1-1 (<-- new version needed for Oreo)
Magisk v16.7 beta (see screenshot below)
MagiskManagerApp 5.8.3 (129)
9.0.2 Android Nougat (Android 7.1.1)
[2018-04-21]
BQ Firmware: 1.8.0
TWRP 3.2.1-0
Magisk v16.0
MagiskManagerApp 5.6.4 (112)
9.1 Update to firmware 1.5.1
As of 18.11.2017, BQ forgot to include adb and fastboot binaries in the new firmware package 1.5.1.
To update, simply copy the following files from the previous firmware package to the new directory:
Code:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
Proceed with instructions from post #1, section '5 Update to newest firmware'.
Don't forget to modify the .bat (comment out userdata, recovery and the reboot) and don't boot up to system after flashing. Directly go to recovery and reflash Magisk. (as described in section '5 Update to newest firmware'.)
The update has been successfully tested by ryazor (post #16) and me coming from firmware 1.4.3 and updating to 1.5.1)
For reference (maybe BQ will replace the .zip later), here is the checksum for the firmware which doesn't contain the binaries:
1.5.1_20171110-0910-bardockpro-user-1336-Fastboot-FW.md5
Code:
738664221520D446F689DCDDD5C611DF *1.5.1_20171110-0910-bardockpro-user-1336-Fastboot-FW.zip
9.2 Adb and fastboot on Linux/Ubuntu
User torbol reported that the adb and fastboot versions packaged with Ubuntu 16.04 are too old and don't support the commands for unlocking the bootloader. See his blog linked in Post #22 for further information.
Solution is to manually fetch the newer versions from the Android SDK.
9.3 Use of adblockers
If you want to use adblockers like AdAway which rely on the /system/etc/hosts file, you'll have to enable the support in the Magisk Manager app.
Symptom when trying to use the app without the switch: phone freezes when the app is given root access and tries to write it's changes.
9.3.1 Magisk v18.0 and up
Starting with Magisk v18.0, the setting for systemless hosts changed a little.
go to settings and tap the entry 'Systemless hosts', a notification toast will pop up at the bottom of the screen: 'added systemless hosts module'
check the modules tab; there will be a new module for systemless hosts support
reboot to activate the module
start your adbocker app and apply the /system/etc/hosts file changes
9.3.1 Before Magisk v18.0
Open MagiskManager, hop to settings and enable the switch 'Systemless hosts' (subtext "Systemless hosts support for Adblock apps").
9.4 Update TWRP
- Connect USB cable to PC
9.4.1 Flash new TWRP
- Boot into fastboot mode
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.5.1_20171110-0910-bardockpro-user-1336-Fastboot-FW>fastboot flash recovery ..\..\03_TWRP_Magisk\2017-12_Magisk-v15.0_TWRP-3.2.1-0\twrp-3.2.1-0-bardock_pro.img
target reported max download size of 536870912 bytes
sending 'recovery' (28152 KB)...
OKAY [ 0.636s]
writing 'recovery'...
OKAY [ 0.203s]
finished. total time: 0.845s
Stay in fastboot mode.
9.4.2 Reflash Magisk
Now reboot and directly start recovery:
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.5.1_20171110-0910-bardockpro-user-1336-Fastboot-FW>fastboot reboot
rebooting...
finished. total time: 0.002s
- Start adb sideload mode ('Advanced' | 'ADB sideload').
Reflash Magisk:
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.5.1_20171110-0910-bardockpro-user-1336-Fastboot-FW>adb sideload ..\..\03_TWRP_Magisk\2017-09_Magisk-v14.0_TWRP-3.1.1-0_xda-post\Magisk-v14.0.zip
Total xfer: 1.69x
Reboot to system.
9.5 Update Magisk
9.5.1 Update MagiskManager app
- Start MagiskManager
- when prompted (see screenshot) install new version.
9.5.2 Install new Magisk Version
Variant 1 (Update via TWRP recovery | adb sideload)
- Ignore the Update Notification in the MagiskManager app for the Magisk update (in this case v14.0 --> v15.0)
- Connect USB cable to PC
- Boot into TWRP recovery
- Start adb sideload mode ('Advanced' | 'ADB sideload')
Code:
E:\backups\android\BQ-Aquaris-X-Pro\04_firmware\1.5.1_20171110-0910-bardockpro-user-1336-Fastboot-FW>adb sideload ..\..\03_TWRP_Magisk\2017-12_Magisk-v15.0_TWRP-3.2.1-0\Magisk-v15.0.zip
Total xfer: 1.82x
Reboot to system.
Variant 2 (Update via MagiskManagerApp)
- Open MagiskManager App
- Tap 'install' on Update notification
- Choose 'Direct Install'
- Update will be installed
- Reboot
9.6 Uninstall Magisk+TWRP/Get back to stock
Use the following steps to unroot/uninstall Magisk and TWRP.
You'll need a PC with adb and fastboot and installed drivers, of course.
Tested with:
- BQ Firmware: 1.8.0
- TWRP 3.2.1-0
- Magisk v16.0
- MagiskManagerApp 5.6.4 (112)
9.6.1 Uninstall Magisk
- Open MagiskManager app
- select 'uninstall' | 'complete uninstall'
- wait a minute or so
- reboot via power button
- phone will be booting, do one reboot (at least for me), booting again
- phone is back in system without Magisk
9.6.2 Uninstall TWRP/Install stock recovery
- Get BQ Firmware .zip which matches your currently installed system (For example '1.8.0_20180323-0901-bardockpro-user-1421-Fastboot-FW.zip')
- Extract the file 'recovery.img'
- Connect the phone to PC via USB and boot into fastboot mode:
Code:
adb reboot bootloader
- Flash stock recovery:
Code:
fastboot flash recovery recovery.img
- wait a minute or so (just to be sure)
- reboot phone:
Code:
fastboot reboot
- phone boots,
- phone is back in system
Congratulations, not you got your phone in stock state with one exception: the bootloader is still unlocked! That means, that the google safety net check will fail (CTS profile).
Now you could re-lock the bootloader if you want to completely go back to the factory state, but if you choose to do so, keep in mind that the phone will be erased completely when locking the bootloader!
9.7 re-locking the bootloader
This chapter describes how to re-lock the bootloader. After doing that, your phone will be in the default factory state regarding all previous modifications.
Before going on, you should have uninstalled Magisk and TWRP (see chapter '9.6 Uninstall Magisk+TWRP/Get back to stock').
Warning: All data+settings will be erased when locking the bootloader! (Everything; That means apps, app settings, personal data like pictures, music, etc.)
As reference, here are the tool versions I used in my successful test:
Code:
>adb version
Android Debug Bridge version 1.0.40
Version 4797878
Installed as D:\programme\Android\platform-tools\adb.exe
Code:
>fastboot --version
fastboot version 28.0.0-4797878
Installed as D:\programme\Android\platform-tools\fastboot.exe
Follow these steps to lock the bootloader:
- action: switch off phone
- action: remove SIM and Micro-SD
- action: enter fastboot mode: vol_down + pwr
- action: connect usb cable
Code:
>fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1
OKAY
Code:
>fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY
Code:
>fastboot flashing lock_critical
OKAY
- reboot
- screen: 'erasing'
- reboot
- screen: 'Aquaris X' boot screen
- screen: 'Encrypting' with green android logo
- screen: 'Aquaris X' boot screen
- several minutes ...
- screen: 'Welcome'
- action: restart with power button
- action: choose 'fastboot' with volume buttons and confirm with power button
Code:
>fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY
Code:
>fastboot flashing lock
OKAY
- reboot
- screen: 'erasing'
- reboot
- screen: 'Aquaris X' boot screen
- screen: 'Encrypting' with green android logo
- several minutes ... (approx. 3 minutes)
- screen: 'Welcome'
- action: disconnect usb cable
- action: switch off with power button
- action: enter fastboot mode: vol_down + pwr
- action: connect usb cable
Code:
>fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY
Code:
>fastboot reboot
Rebooting
Finished.
- phone will be booting to system.
- action: skip through the welcome screens
- action: go to settings | system | about phone | tap 'build number' 7 times
- action: go to settings | system | developer options | OEM unlocking
- note: without internet connection, the OEM unlocking option will be greyed out.
- action: connect to wifi, go back to the system menu and wait a minute
- action: go back to developer options | OEM unlocking
- action: switch off OEM unlocking
- action: disconnect usb cable
- action: switch off with power button
- action: enter fastboot mode: vol_down + pwr
- action: connect usb cable
Code:
>fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY
Code:
>fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 0
OKAY
Code:
>fastboot reboot
Rebooting
Finished.
DONE
9.8 update the phone via official OTA
This chapter describes how to use the OTA update feature. Personally, I like the other way (flashing the update zip) much more and think the other way is easier, but I recently did this, because I needed the OTA for the Oreo beta, so here is the information.
Precondition: Phone with stock rom (obviously), uninstalled Magisk+TWRP (stock recovery)! See chapter '9.6 Uninstall Magisk+TWRP/Get back to stock'. The bootloader can stay unlocked.
- Go to settings | about phone | System updates | update (check for updates)
- You should get a notification similar to the following one in the screenshot:
- Download and install the System update
done
9.8 Install TWRP+Magisk on BQ FW 2.0.0 (Android Oreo 2.1.0)
colors: PC, phone
Started with the stock firmware 2.0.0 (Android 8.1.0 Oreo) with unlocked bootloader (and stock bootimage and recoveryimage).
> adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
>fastboot flash recovery twrp-3.2.1-1-bardock_pro.img
target reported max download size of 534773760 bytes
sending 'recovery' (35304 KB)...
OKAY [ 0.813s]
writing 'recovery'...
OKAY [ 0.250s]
finished. total time: 1.063s
> fastboot reboot
rebooting...
finished. total time: 0.016s
Don't boot. Directly go to recovery
Advanced | ADB Sideload
>adb sideload Magisk-v16.4.zip
Total xfer: 1.68x
9.9 to be continued
[...]
10 Changelog (this post)
2020-07-31: updated latest version info
2019-10-12: updated latest version info
2019-10-08: updated latest version info
2019-06-15: updated latest version info
2019-06-05: updated latest version info
2019-05-22: updated latest version info
2019-05-20: updated latest version info
2019-05-03: updated latest version info
2019-04-18: updated latest version info
2019-04-02: updated latest version info
2019-02-04: updated latest version info
2019-01-26: updated latest version info
2019-01-14: updated latest version info
2018-12-17: updated+expanded section '9.3 Use of adblockers'
2018-12-08: updated latest version info
2018-11-04: added chapter '9.7 re-locking the bootloader'
2018-10-30: rearranged the chapters, fixed 9.7/9.8
2018-10-21: updated latest version info
2018-09-29: updated latest version info
2018-09-01: updated latest version info
2018-08-xx: updated latest version info
2018-07-12: updated latest version info
2018-07-08: updated latest version info
2018-05-08: updated latest version info + added 9.8 BQ FW 2.0.0 / Oreo 2.1.0
2018-04-22: added 9.6 and 9.7 - Uninstall + OTA updates
2018-03-28: updated latest version info
2018-04-21: updated latest version info
2018-03-23: updated latest version info
2018-03-11: updated latest version info
2018-02-22: updated latest version info
2018-02-10: updated latest version info
2018-01-13: updated latest version info
2018-01-12: updated latest version info
2018-01-03: added latest version info
2017-12-30: added hide-content buttons
2017-12-29: changes in 9.5 - How to update Magisk
2017-12-26: added 9.4 + 9.5 - How to update TWRP and Magisk
2017-12-26: added 9.3 with information for adblocker users (systemless hosts file/AdAway)
2017-11-19: added 9.2 with Information for linux users
2017-11-18: added additional/dynamic information here in post #2, general documentation still in post #1

many thanks for the guide
just a question
If we choose to Keep Read Only in TWRP, at the next reboot the recvoery was overwrited by stock....

ironia. said:
many thanks for the guide
just a question
If we choose to Keep Read Only in TWRP, at the next reboot the recvoery was overwrited by stock....
Click to expand...
Click to collapse
Hi ironia,
hm..
There is no single restart in between the steps mentioned below. I think i had kind of the same problem when restarting at any point.
When i chose to apply the TRWP changes, my phone did not boot anymore, so that was no option for me.
The steps i mean are from section '4.3 Install TWRP and Magisk':
choose 'Keep Read Only' on first TWRP start
flash Magisk from TWRP with the adb sideload
reboot to system from TWRP
get to the welcome wizard
Did you restart before finishing the steps?

I still don't know where do I need to type all of that commands can you please explain a bit ? My phone is already in Fastboot Mode but where do I need to type those commands in?

roanepv said:
I still don't know where do I need to type all of that commands can you please explain a bit ? My phone is already in Fastboot Mode but where do I need to type those commands in?
Click to expand...
Click to collapse
Hi roanepv,
the commands are for the Windows/DOS command prompt on the PC.
You can open the prompt with win+r and type 'cmd' then you'll have to change to the correct directory where you downloaded the files...
Keep in mind that you can brick your phone if something goes wrong.

On the first step I open cmd then I type this? : C:\Users\André\Downloads\BQ\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot flashing get_unlock_ability
---------- Post added at 01:27 PM ---------- Previous post was at 12:39 PM ----------
roanepv said:
On the first step I open cmd then I type this? : C:\Users\André\Downloads\BQ\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot flashing get_unlock_ability
Click to expand...
Click to collapse
It says is not a recognized as an internal or external operable program or batch file. What to do?
---------- Post added at 01:51 PM ---------- Previous post was at 01:27 PM ----------
roanepv said:
On the first step I open cmd then I type this? : C:\Users\André\Downloads\BQ\1.4.3_20170809-1111-bardock-user-983-Fastboot-FW>fastboot flashing get_unlock_ability
---------- Post added at 01:27 PM ---------- Previous post was at 12:39 PM ----------
It says is not a recognized as an internal or external operable program or batch file. What to do?
Click to expand...
Click to collapse
Ok , I unlocked bootloader with BQ Firmware Flash Tool and then proceed to install TWRP , everything went fine but ADB Sideload is taking alot to start.... Can I flash Magisk Directly without ADB?

You'll have to copy the zip to the phone, but yes, you can install the zip from within TWRP.

Thank a lot for the detailed guide which is extremely helpful indeed! I've gone through all the steps and everything works fine! Thanks again.

vomil said:
Thank a lot for the detailed guide which is extremely helpful indeed! I've gone through all the steps and everything works fine! Thanks again.
Click to expand...
Click to collapse
Hi vomil, thanks for the feedback!
Hoped it would work when reproducing everything step by step.

Thank you for this comprehensive guide. It worked like a charm!

Hello, I've been trying to install modules on the Magisk manager but they don't install whatever the method I use.
I tried installing it directly from the modules download page within the app, it downloads and shows it installing on the terminal, I then reboot but when I go to the modules section I have no modules installed.
I tried flashing directly from within the app, rebooted, no modules installed again..
I even tried flashing from TWRP it said successful installation, I rebooted but still as always no modules were installed again...
Does anyone shares this problem or knows a way of fixing it? Thank you for your time.
I'm using app version 5.4.0(57) and Magisk version 14.0
Sent from my Aquaris X Pro using Tapatalk

Hi krillin666,
i didn't use the module feature so far.
Can you give me a link to a module i can test? What should i do? Add it in Magisk Manager, reboot and check if its still there?

nuv said:
Hi krillin666,
i didn't use the module feature so far.
Can you give me a link to a module i can test? What should i do? Add it in Magisk Manager, reboot and check if its still there?
Click to expand...
Click to collapse
Hello, just try any module really, because I tried at least 10 different.
You could try installing the busybox module or the xposed for example.
As I said I tried 3 different methods, the easiest one is to go to the downloads tab and search for a module and install it, reboot and then go to the modules tab to see if it's installed.
Thank you.
Sent from my Aquaris X Pro using Tapatalk

Hi krillin666,
took TaskerRootBuildProp-1.03.zip from here: https://forum.xda-developers.com/showpost.php?p=71862904&postcount=12243
used the '+' Sign in MagiskManager to add the module:
Directly after install:
Rebooted via power button menu.
After reboot in MagiskManager:
..seems to work I guess? (Didn't verify otherwise, but according to your previous post, the module entry should not be there if i had the same problem?)

Will step 5 (upgrading Firmware) work with the new FW 1.5.1 without losing data?
Thanks in advance!
Update: Yes, can confirm, it works

ryazor said:
Will step 5 (upgrading Firmware) work with the new FW 1.5.1 without losing data?
Thanks in advance!
Click to expand...
Click to collapse
UUh, new firmware -- I don't know yet. Don't know if i can update this weekend.
If you are faster than me, please give feedback, i will refresh some information in first/second posts.
Better create a TWRPbackup before
edit: I have not looked into the update .zip yet - if the batch file is identical/similar to the one before, it should work accourding to section 5 ... I hope so...

nuv said:
Hi krillin666,
took TaskerRootBuildProp-1.03.zip from here: https://forum.xda-developers.com/showpost.php?p=71862904&postcount=12243
used the '+' Sign in MagiskManager to add the module:
View attachment 4335160
Directly after install:
View attachment 4335161
Rebooted via power button menu.
After reboot in MagiskManager:
View attachment 4335162
..seems to work I guess? (Didn't verify otherwise, but according to your previous post, the module entry should not be there if i had the same problem?)
Click to expand...
Click to collapse
Strange, that doesn't happens to me at all maybe it's a bug. What's the magick version and manager you're using?
Sent from my Aquaris X Pro using Tapatalk

krillin666 said:
Strange, that doesn't happens to me at all maybe it's a bug. What's the magick version and manager you're using?[...]
Click to expand...
Click to collapse
oh, sorry, forgot to mention; the same as yours: Magisk v14.0 and Manager App 5.4.0 (57).
edit: maybe try with the simple module I linked in my prev. post?

ryazor said:
Will step 5 (upgrading Firmware) work with the new FW 1.5.1 without losing data?
Thanks in advance!
Update: Yes, can confirm, it works
Click to expand...
Click to collapse
Hey, thank for testing! Seems BQ forgot to include adb and fastboot in the update package
I assume, you used the binaries from the prev. zip (1.4.3)?
Successfully updated the phone myself and will update thread posts 1+2 shortly.

Related

[GUIDE]Unlocking, Rooting, Adding CWM, Customizing XPERIA S 6.1.A.2.45 Stock ROM

Note: All the methods used here not belongs to me,
ALL CREDITS GOES TO ITS MAKERS
Here I am giving you some external threads and some guide lines explaining how to unlock,root,adding Recovery, Flashing Custom ROMS and How to unroot, locking bootloaders to get official OTA updates..
Lets start with usual warning, I'm not responsible if your Xperia S gets bricked
[UNLOCKING BOOTLOADER]
There is a great thread explaining how to unlock and relock bootloader by DooMLoRD, its very useful and I tested it and worked perfectly.Here is the link,
UNLOCKING AND RELOCKING BOOTLOADER XPERIA S
If you found its useful don't forget to thank him.
[ROOTING XPERIA S WITH 6.1.A.2.45]
Here I will give you two methods,
FIRST METHOD
This is for unlocked bootloader only and only for Xperia S LT26i. I have tested and working perfectly in my SXS
Warning: This is Exclusively for Xperia S with 6.1.A.2.45. I am not sure about other Other ROMS
Before Rooting you must have downloaded this,
1.Root Kit.zip (Zip containing everything you wanted to root)
2.Flashable SuperSU App (Thanks to Chainfire )
Inside the folder you have one .txt file its the commands you have to use in cmd, Any how I am adding the same below,
1.You must have enabled USB debugging in developer option under settings
2.Copy the "CWM-SuperSU-v0.96.zip" into your SD card
3.Switch off and connect your phone in fast boot mode (pressing Power button + Vol up)
If asked for drivers, update driver manually by directing to "USB driver folder" inside the "Root Kit folder".
Verify whether there is a BLUE LED is coming up.
Now you are in fastboot mode, type the commands line by line,
fastboot devices
Click to expand...
Click to collapse
you will get something like this,
PSDN: DW925S3BFT&POI fastboot
Click to expand...
Click to collapse
Now type this,
fastboot flash boot recovery-nozomi.img
Click to expand...
Click to collapse
you will be seeing this,
sending 'boot' (5414 KB)...
(bootloader) USB download speed was 9847kB/s
OKAY [ 0.579s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00002000-0x0000bfff
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.851s]
finished. total time: 2.432s
Click to expand...
Click to collapse
so the recovery image is flashed into the phone, now reboot device using below command,
fastboot reboot
Click to expand...
Click to collapse
Now the phone will boot into recovery mode and select the option “Install zip from SDCard”. Browse to the folder where you had copied the SU zip file (CWM-SuperSU-v0.96.zip), select it and install it.
Now select the “Reboot System” option and while it is booting press the VOL UP button to boot back into the fastboot mode. Now run
fastboot flash boot kernel.sin
Click to expand...
Click to collapse
You should see something like this
sending 'boot' (5590 KB)...
(bootloader) USB download speed was 9588kB/s
OKAY [ 0.612s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00002000-0x0000bfff
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 2.976s]
finished. total time: 3.589s
Click to expand...
Click to collapse
If its showing with "Okay and Finished", then you are done, Congrats now you have a rooted phone (check for SuperSU app inside the phone drawer)​Note:
1.If you can't enter into fastmode after image flashing (sometimes you need to have a better timing to enter into flashmode during reboot by pressing vol up and power button), then do this,
Press power and volume up button till u get a vibration followed by three vibrations (now your phone is switched off, so you can enter into fastboot normally) IMPORTANT: Dont remove the usb cable ever till rooting finishes
2.If any step fails after flashing recovery image you can't able to enter into your phone, don't be panic we have solution for everything.
Flashing stock rom with flashtool will solve this issue.
SECOND METHOD
Follow thread here,
Root with Recovery by Bin4ry
Note:
It's the easiest method, but every time i tried, i am doing it wrongly, but you can use this as well for rooting.Don't forget to thank Bin4ry
[ClockWorkMod Recovery]
If you want to know "why recovery is need?" go through some search .
For stock Roms
Just download this and enjoy recovery.
RecoverX by LEDelete. Don't forget to thank him.
[Flashing Custom ROMs]
You will get a variety of Custom ROMs available for XSX, choose what you are in need of, am here adding some Custom ROMs and there respective links (but its not the end, there are many more search it)
10/03/2012 - KA15 Xperia SSpeed released|Stablity update|Smooth & Fast|4.0.4 | Direct Link
10/03/2012 - KA02 Xperia SSpeed released! Modded stock rom|Smooth & Fast | Direct Link
10/02/2012 - [AOKP][JB] Xperia S | Direct Link
09/30/2012 - [DEVELOPMENT] - CM9.1 | Direct Link
09/30/2012 - Erachter ROM v4.1 | Very smooth | Good battery life | Direct Link
09/28/2012 - [email protected] Rom v5.2 [Simple, Clean & Fast] | Bug Free and battery friendly | Jelly Bean Animation | Direct Link
09/27/2012 - [ICS] XcreaM-3.2 | Stable Highly and easily customizable | Direct Link
09/15/2012 - MIUI 2.9.14 | Direct Link
09/07/2012 - [Xperia S][ICS] ExtremeICSrom v3 [Fast & Smooth] | Direct Link
05/01/2012 - Ultimate Xperience™ |[UICSv1.0] | [USensev1.0] | Direct Link
Note: Don't forget to thank the authors
[CWM in Custom ROMs]
Mostly in all Custom ROms there are recoveries but rarely we can't find in some ROMs, for that you have to download the flashable recovery zip along with the ROMs, If you forget to do a recovery flash and you are unable enter recovery mode don't be panic, remember we have solutions everything, just go through this forum to know about doing recovery through PC.
Recovery through PC
Now its all done, Enjoy..
Note: For unrooting you have to flash the stock kernels
Note: Customization of SystemUI.apk will be posted soon.
If there is any problem with this threada kindly inform through PM, If any links not working let me know before blaming me
Hit thanks if i helped you.:laugh:.​
http://forum.xda-developers.com/showthread.php?t=1526866
Yeah I know that post well, I got my basic from that post alone, thank you for adding that too in the thread. This is exclusively for XPERIA S with 6.1.A.2.45.
Sent from my LT26i using xda app-developers app

Unlock Bootloader on Android 5.1.1 A5CN701?

I've been trying to unlock the bootloader since the A5CN701 update. Here's how i've tried:
1. Go to developer options -> Tick OEM Unlocking
2. Use the launcher.bat from IntelAndroid-FBRL-05-16-2015.7z from this topic http://forum.xda-developers.com/nokia-n1/general/play-store-howto-t3118965
3. Use the T4 option and the tablet ends up like this (because the bootloader is locked):
{
"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"
}
4. Use fastboot and enter this code:
Code:
fastboot oem unlock
Then the cmd console and the tablet should look like this:
5. Select ''Yes: change device state'' using the UI on the N1 but here's all i've received:
The result is :''Fail: couldn't change state''
So that's pretty much about how i've tried to unlock the bootloader. I don't know why i couldn't change the device state! Is there anyone that can help me?
I posted this topic so that everyone can join and make suggestions & solutions to rooting the A5CN701 firmware!
Any help would be much appreciated!
P/s: sorry for the sloppy photos, i didn't have time to crop and edit them
it's no use,I use the same way and i get my device state-unlocked.
C:\Dociments and Settings\fldministrator>cd C:\platform-tools
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot oen unlock
<bootloader) Please confirm the device state action using the UI-<bootloader) Userdata erase required, this can take a while ---
OKAV [ 5.844s]
finished- total time: 5.844s
C:\platform-tools>
and then I use the old way to root the device,only end like this.
copy needed files to our deuice
target reported nax download size of 536870912 bytes
sending ^/tmp/recouery.zip^ <3477 KB> • • •
OKAV [ 0.297s]
writing ^/tmp/recovery.zip^ • • •
FAILED <remote: not allowed to flash this partition>
finished, total tine: 0.516s
target reported max download size of 536870912 bytes
sending ^/tmp/recouerv. launcher^ <400 KB> • • •
OKAV [ 0.203s]
writing '/tmp/recouerv. launcher' • • •
FAILED <remote: not allowed to flash this partition>
finished, total tine: 0.422s
we need to stop logcat before replacing it
<bootloader> Start partitioning
OKAY [ 0.406s]
finished, total tine: 0.406s
target reported max download size of 536870912 bytes
sending ^/system/bin/logcat'<178KB
OKAY 【0.219s】
writing '/systen/bin/logcat^•••
FAILED <remote: not allowed to flash this partition>
finished, total tine: 0.422s
issue fastboot oem ''stop.partitioning command to start cwn recouerv:
<bootloader> Stop partitioning
OKAY 【0.391s】
finished, total tine: 0.391s
sorry,can't upload img
PS:if you unlock,the device only stay in bootloader,if you want to open and normal use device,you must lock it.
乄Rain丶Man said:
it's no use,I use the same way and i get my device state-unlocked.
C:\Dociments and Settings\fldministrator>cd C:\platform-tools
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot oen unlock
<bootloader) Please confirm the device state action using the UI-<bootloader) Userdata erase required, this can take a while ---
OKAV [ 5.844s]
finished- total time: 5.844s
C:\platform-tools>
and then I use the old way to root the device,only end like this.
copy needed files to our deuice
target reported nax download size of 536870912 bytes
sending ^/tmp/recouery.zip^ <3477 KB> • • •
OKAV [ 0.297s]
writing ^/tmp/recovery.zip^ • • •
FAILED <remote: not allowed to flash this partition>
finished, total tine: 0.516s
target reported max download size of 536870912 bytes
sending ^/tmp/recouerv. launcher^ <400 KB> • • •
OKAV [ 0.203s]
writing '/tmp/recouerv. launcher' • • •
FAILED <remote: not allowed to flash this partition>
finished, total tine: 0.422s
we need to stop logcat before replacing it
<bootloader> Start partitioning
OKAY [ 0.406s]
finished, total tine: 0.406s
target reported max download size of 536870912 bytes
sending ^/system/bin/logcat'<178KB
OKAY 【0.219s】
writing '/systen/bin/logcat^•••
FAILED <remote: not allowed to flash this partition>
finished, total tine: 0.422s
issue fastboot oem ''stop.partitioning command to start cwn recouerv:
<bootloader> Stop partitioning
OKAY 【0.391s】
finished, total tine: 0.391s
sorry,can't upload img
PS:if you unlock,the device only stay in bootloader,if you want to open and normal use device,you must lock it.
Click to expand...
Click to collapse
If you have got your device unlocked, can you boot into the recovery menu where the option ''Install update from ADB'' is? I can't seem to boot into the recovery menu on the A5CN701? If we can get there, I'm sure we'll figure it out
When running "fastboot flash fastboot droidboot.img" and "fastboot flash boot boot.img" with the files from A5CN507_update.zip i get the IntelAndroid-FBRL-07-24-2015 to run TWRP or CWM.
Drivknuten said:
When running "fastboot flash fastboot droidboot.img" and "fastboot flash boot boot.img" with the files from A5CN507_update.zip i get the IntelAndroid-FBRL-07-24-2015 to run TWRP or CWM.
Click to expand...
Click to collapse
you reboot into the Temporary CWM success?
Xkernels said:
you reboot into the Temporary CWM success?
Click to expand...
Click to collapse
Yes
Drivknuten said:
Yes
Click to expand...
Click to collapse
please, you could post your image?
colorado48 said:
If you have got your device unlocked, can you boot into the recovery menu where the option ''Install update from ADB'' is? I can't seem to boot into the recovery menu on the A5CN701? If we can get there, I'm sure we'll figure it out
Click to expand...
Click to collapse
No,if you unlock device,only stay in bootloader,no matter what your choice,reboot to recovery or power off or anything else. yesterday,i see Root Dell Venue 8 7840 on Android 5.1 Lollipop, which also intel device and run android 5.1.1, it must Flashing Old Firmware and Droidboot,then use the old way to root it, just like the #4 said, but i don't have the N1's old Firmware and Droidboot, so i can't try. now,we just wait #4 upload the img and do what need to do.
---------- Post added at 04:30 AM ---------- Previous post was at 04:25 AM ----------
Drivknuten said:
When running "fastboot flash fastboot droidboot.img" and "fastboot flash boot boot.img" with the files from A5CN507_update.zip i get the IntelAndroid-FBRL-07-24-2015 to run TWRP or CWM.
Click to expand...
Click to collapse
I have the A5CN507_update.zip,could you please tell me how to flash the old droidboot.img and boot.img,
Thx~ plaese
---------- Post added at 04:34 AM ---------- Previous post was at 04:30 AM ----------
p233 said:
please, you could post your image?
Click to expand...
Click to collapse
do you mean you need A5CN507_update.zip?
I have it, it's in a Chinese cloud drive,if you want it ,i can give you the url.
乄Rain丶Man said:
No,if you unlock device,only stay in bootloader,no matter what your choice,reboot to recovery or power off or anything else. yesterday,i see Root Dell Venue 8 7840 on Android 5.1 Lollipop, which also intel device and run android 5.1.1, it must Flashing Old Firmware and Droidboot,then use the old way to root it, just like the #4 said, but i don't have the N1's old Firmware and Droidboot, so i can't try. now,we just wait #4 upload the img and do what need to do.
---------- Post added at 04:30 AM ---------- Previous post was at 04:25 AM ----------
I have the A5CN507_update.zip,could you please tell me how to flash the old droidboot.img and boot.img,
Thx~ plaese
---------- Post added at 04:34 AM ---------- Previous post was at 04:30 AM ----------
do you mean you need A5CN507_update.zip?
I have it, it's in a Chinese cloud drive,if you want it ,i can give you the url.
Click to expand...
Click to collapse
Here is the original old version download link
http://forum.xda-developers.com/nokia-n1/general/nokia-n1-chinese-version-5-1-1-update-t3183529 #3
p233 said:
please, you could post your image?
Click to expand...
Click to collapse
Right now my device is in a bootloop and i have too much work to get anything done with the device right now. So no pic right now.
乄Rain丶Man said:
I have the A5CN507_update.zip,could you please tell me how to flash the old droidboot.img and boot.img,
Thx~ plaese
---------- Post added at 04:34 AM ---------- Previous post was at 04:30 AM ----------
Click to expand...
Click to collapse
1. extract the droidboot.img & boot.img from the A5CN507_update.zip.
2. adb reboot recovery
3. fastboot oem unlock
4. fastboot flash boot boot.img
5. fastboot flash boot boot.img
6. download "IntelAndroid-FBRL-07-24-2015" unzip, run launcher.bat type "ACCEPT" select number 4 or 5 (i have only tested those two). Then option T4 if i remember correctly.
7. Now the device should start receiving the files and start in TWRP or CWM depending on the choices you have made.
Drivknuten said:
Right now my device is in a bootloop and i have too much work to get anything done with the device right now. So no pic right now.
1. extract the droidboot.img & boot.img from the A5CN507_update.zip.
2. adb reboot recovery
3. fastboot oem unlock
4. fastboot flash boot boot.img
5. fastboot flash boot boot.img
6. download "IntelAndroid-FBRL-07-24-2015" unzip, run launcher.bat type "ACCEPT" select number 4 or 5 (i have only tested those two). Then option T4 if i remember correctly.
7. Now the device should start receiving the files and start in TWRP or CWM depending on the choices you have made.
Click to expand...
Click to collapse
2.adb reboot bootloader?
can you provide some pic?
Xkernels said:
2.adb reboot bootloader?
can you provide some pic?
Click to expand...
Click to collapse
Yes that should be adb reboot bootloader.
NO pics possible, my device is in a bootloop and i dont have the time to fix the device until the weekend.
Hi, i seem to have the same problem. ie, N1 stuck in fastboot mode. i have folowed the instructions above, ie;
- successfully unlocked it (fastboot mode reports DEVICE STATE - unlocked)
- extracted boot.img and flashed using fastoboot flash boot boot.img (successful) twice
however, when i run the FBRL script, using option T4 the same problem remains as per the earlier post, ie, it fails at the following point;
writing ^/tmp/recovery.zip^ • • •
FAILED <remote: not allowed to flash this partition>
the script then fails in the same way for recovery.launcher and logcat.
any ideas?
my device now stays in fastboot mode, whether i try chose recovery mode, normal boot etc nothing chances and each time i power cycle it comes back to fastboot mode.
please help. thanks
pdt100 said:
Hi, i seem to have the same problem. ie, N1 stuck in fastboot mode. i have folowed the instructions above, ie;
- successfully unlocked it (fastboot mode reports DEVICE STATE - unlocked)
- extracted boot.img and flashed using fastoboot flash boot boot.img (successful) twice
however, when i run the FBRL script, using option T4 the same problem remains as per the earlier post, ie, it fails at the following point;
writing ^/tmp/recovery.zip^ • • •
FAILED <remote: not allowed to flash this partition>
the script then fails in the same way for recovery.launcher and logcat.
any ideas?
my device now stays in fastboot mode, whether i try chose recovery mode, normal boot etc nothing chances and each time i power cycle it comes back to fastboot mode.
please help. thanks
Click to expand...
Click to collapse
Try "fastboot flash fastboot droidboot.img" with the droidboot.img from the A5CN507_update
Drivknuten said:
Try "fastboot flash fastboot droidboot.img" with the droidboot.img from the A5CN507_update
Click to expand...
Click to collapse
Hi, i was able to submit the command successfully however no change unfortunately. any other ideas? thanks
Drivknuten said:
Right now my device is in a bootloop and i have too much work to get anything done with the device right now. So no pic right now.
1. extract the droidboot.img & boot.img from the A5CN507_update.zip.
2. adb reboot recovery
3. fastboot oem unlock
4. fastboot flash boot boot.img
5. fastboot flash boot boot.img
6. download "IntelAndroid-FBRL-07-24-2015" unzip, run launcher.bat type "ACCEPT" select number 4 or 5 (i have only tested those two). Then option T4 if i remember correctly.
7. Now the device should start receiving the files and start in TWRP or CWM depending on the choices you have made.
Click to expand...
Click to collapse
Then did you root your device successfully?or did you rollback to old version?
乄Rain丶Man said:
Then did you root your device successfully?or did you rollback to old version?
Click to expand...
Click to collapse
Nah i bricked it,
the same thing to me, after i relock bootloader, it jump into a big problem: bootloop, whenever i turn on devices, it just show "android" screen
It's been a while now, can anybody confirm that a root for A5CN701 is on the way?
Drivknuten said:
Nah i bricked it,
Click to expand...
Click to collapse
Oflyt...

Root? Roms? Custom Recovery? Bootlocker Unlock? Anyone?

Someone needs to start this. I can't believe no one has yet looked at this. Tell me someone has achieved some of this please.
GodKingKnight said:
Someone needs to start this. I can't believe no one has yet looked at this. Tell me someone has achieved some of this please.
Click to expand...
Click to collapse
I also was wondering everytime i came to this forum, why no developer yet did not showup here. Is asus not devs friendly.. i am planning to buy it but only after i will see some hope of custom rom development.
nadeem_naddy said:
I also was wondering everytime i came to this forum, why no developer yet did not showup here. Is asus not devs friendly.. i am planning to buy it but only after i will see some hope of custom rom development.
Click to expand...
Click to collapse
I am also checking 5z forums daily
Asus have launched kernel sources and it is project treble supported and custom rom development is easy so looking forward for some development to start:crying::crying::crying:
i was planning to buy this phone as i wanted to flash resurrection remix but guess have to wait
The phone released recently, and very late in the year. Most devs are on treble phones, or ones like the OnePlus 6. The phone is probably treble compliant, so in theory owners can use any treble ROM.
TWRP to ZS620KL (snapdragon 845, 8/256GB)
I am looking for TWRP to ZS620KL (snapdragon 845, 8/256GB) can anyone help me? It does not work for ZE620KL, unfortunately. I need a good TWRP urgently.
jakubdg said:
I am looking for TWRP to ZS620KL (snapdragon 845, 8/256GB) can anyone help me? It does not work for ZE620KL, unfortunately. I need a good TWRP urgently.
Click to expand...
Click to collapse
Have you unlocked the bootloader ??
is it same as zenfone 5 2018
If yes then share the method
Akash1998 said:
Have you unlocked the bootloader ??
is it same as zenfone 5 2018
If yes then share the method
Click to expand...
Click to collapse
Yes I have unlocked bootloader. I used official asus apk
Then downloaded twrp-3.2.1-0-X00Q-20180508.img
Next fastboot flash boot recovery.img and fastboot flash recovery recovery.img - I saw Bootloader Version is empty
Now I dont know how I have older bootloader version WW_user_80.11.37.53 but I do not have twrp.
Edit: Please use my updated guide:
https://forum.xda-developers.com/zenfone-5z/how-to/guide-zenfone-5z-how-to-root-downgrade-t3815877
Here is what i did to root the 5Z ZS620KL:
1. Download the unlock app AND the installed firmware from asus:
download
2. Install adb and fastboot
download
3. Copy the app to the phone, start it and follow the on screen instructions > bootloader unlocked
Warning: When booting the phone you will now see a warning message!
4. Unzip the downloaded firmware and use a tool to extract the boot.img from the payload.bin. I used payload_dumper.
download
5. Copy the extracted boot.img from payload_output folder to the 5z.
6. Download magisk manager app from the officiall thread on xda, install it and use it to patch the boot.img on your phone (install>install>patch boot.img)
download
7. Copy the patched_boot.img back to your computer (the original boot.img will be approx 65mb the patched one approx 19mb)
8. Start your phone in fasboot mode (hold "power + volume up" to switch on your phone). You will see "FastBoot Mode" in red letters on screen. Connect your phone to the computer using the usb cable.
9. Open a command line and check if your phone is recognized by executing:
Code:
fastboot devices
You should see the serial number of your phone.
10. Change to the path where you copied your patched_boot.img and use fastboot to flash the patched_boot.img to your device:
Code:
fastboot flash boot patched_boot.img
11. Start your phone from the fastboot menu using volume up/down and power to select.
Bugs/problems:
- You will see three warning messages while booting, at least i do. One for the unlocked bootloader and the next one comes twice saying "There is an internal problem with your device. Contact your manufacturer for details." which you have to confirm.
- I used the latest stable Magisk V16.0 + Manager V5.8 and Magisk hide is not working. It does not save the apps marked for hide. Maybe some write error?
I have purchased zenfone 5Z but it's model number on box is ZS621KL. I see the guide posted for rooting and TWRP install is for ZS620KL. is this same guide applicable to my model as well or this is a different version something like zenfone 5 and Not zenfone 5 Z
isthisadagger said:
Here is what i did to root the 5Z ZS620KL:
1. Download the unlock app AND the installed firmware from asus:
download
2. Install adb and fastboot
download
3. Copy the app to the phone, start it and follow the on screen instructions > bootloader unlocked
Warning: When booting the phone you will now see a warning message!
4. Unzip the downloaded firmware and use a tool to extract the boot.img from the payload.bin. I used payload_dumper.
download
5. Copy the extracted boot.img from payload_output folder to the 5z.
6. Download magisk manager app from the officiall thread on xda, install it and use it to patch the boot.img on your phone (install>install>patch boot.img)
download
7. Copy the patched_boot.img back to your computer (the original boot.img will be approx 65mb the patched one approx 19mb)
8. Start your phone in fasboot mode (hold "power + volume up" to switch on your phone). You will see "FastBoot Mode" in red letters on screen. Connect your phone to the computer using the usb cable.
9. Open a command line and check if your phone is recognized by executing:
Code:
fastboot devices
You should see the serial number of your phone.
10. Change to the path where you copied your patched_boot.img and use fastboot to flash the patched_boot.img to your device:
Code:
fastboot flash boot patched_boot.img
11. Start your phone from the fastboot menu using volume up/down and power to select.
Bugs/problems:
- You will see three warning messages while booting, at least i do. One for the unlocked bootloader and the next one comes twice saying "There is an internal problem with your device. Contact your manufacturer for details." which you have to confirm.
- I used the latest stable Magisk V16.0 + Manager V5.8 and Magisk hide is not working. It does not save the apps marked for hide. Maybe some write error?
Click to expand...
Click to collapse
where can I find payload.bin ?
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
where can I find payload.bin?
---------- Post added at 06:29 PM ---------- Previous post was at 06:08 PM ----------
where can I find payload.bin ?
I need help...
when I try upload twrp twrp-3.2.1-0-X00Q-20180508.img
(SK620KL snap845 8/256GB unlocked)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot twrp-3.2.1-0-X00Q-20180508.img
target reported max download size of 268435456 bytes
sending 'boot' (25244 KB)...
OKAY [ 0.552s]
writing 'boot'...
OKAY [ 0.103s]
finished. total time: 0.658s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.1-0-X00Q-20180508.img
target reported max download size of 268435456 bytes
sending 'recovery' (25244 KB)...
OKAY [ 0.557s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.570s
then in Fastboot Mode I have: BOOTLOADER VERSION - Error
the phone does not start ((
maybe other recovery.img??
When and where you have find a TWRP recovery for ZenFone 5 z (SK620KL) ??????!!!!!!!!!!!?????????
Reflash stock recovery if you can but you flash wrong TWRP for your model of your device ..... You soft brick or hard brick your device
Before READ the tutorial step by step and watch the model of the device ............ It's the base for an hacker
You have ZenFone 5 z with stock rom like pixel rom with the snp 845 what do you need ? why you want install TWRP no custom rom at this moment just trebble project but it's not for now the best way
And ZenFone 5 received Android P just wait
jakubdg said:
I need help...
when I try upload twrp twrp-3.2.1-0-X00Q-20180508.img
(SK620KL snap845 8/256GB unlocked)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot twrp-3.2.1-0-X00Q-20180508.img
target reported max download size of 268435456 bytes
sending 'boot' (25244 KB)...
OKAY [ 0.552s]
writing 'boot'...
OKAY [ 0.103s]
finished. total time: 0.658s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.1-0-X00Q-20180508.img
target reported max download size of 268435456 bytes
sending 'recovery' (25244 KB)...
OKAY [ 0.557s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.570s
then in Fastboot Mode I have: BOOTLOADER VERSION - Error
the phone does not start ((
maybe other recovery.img??
Click to expand...
Click to collapse
If your computer is able to use fastboot.exe.
Please try
Download WW__ZS620KL_80.10.8.54_MP_user_20180517175955_release.zip
Extract this zip file.
Connect your 5Z with your computer.
Start cmd, and move into path to folder (WW__ZS620KL_80.10.8.54_MP_user_20180517175955_release) .
Type `flashall_AFT.cmd`.
amanfdk said:
I have purchased zenfone 5Z but it's model number on box is ZS621KL. I see the guide posted for rooting and TWRP install is for ZS620KL. is this same guide applicable to my model as well or this is a different version something like zenfone 5 and Not zenfone 5 Z
Click to expand...
Click to collapse
Go to system>about phone> sofware version and check your version. Mine starts with WW_80.11.37.69. You need to download the right firmware version from asus (WW or JP). It should work for ZS621KL.
isthisadagger said:
Go to system>about phone> sofware version and check your version. Mine starts with WW_80.11.37.69. You need to download the right firmware version from asus (WW or JP). It should work for ZS621KL.
Click to expand...
Click to collapse
Mine is also similar. So have you tried this guide is our working for you.
Renaf2 said:
When and where you have find a TWRP recovery for ZenFone 5 z (SK620KL) ??????!!!!!!!!!!!?????????
Reflash stock recovery if you can but you flash wrong TWRP for your model of your device ..... You soft brick or hard brick your device
Before READ the tutorial step by step and watch the model of the device ............ It's the base for an hacker
You have ZenFone 5 z with stock rom like pixel rom with the snp 845 what do you need ? why you want install TWRP no custom rom at this moment just trebble project but it's not for now the best way
And ZenFone 5 received Android P just wait
Click to expand...
Click to collapse
I wanted to install twrp + root + adaway or other adblock nothing more... I used this info getdroidtips.com/root-twrp-recovery-asus-zenfone-5z
Now I have problem, 5Z still rebooting when I go to recovery or bootloader or start system
---------- Post added at 11:54 AM ---------- Previous post was at 11:27 AM ----------
GSPD said:
If your computer is able to use fastboot.exe.
Please try
Download WW__ZS620KL_80.10.8.54_MP_user_20180517175955_release.zip
Extract this zip file.
Connect your 5Z with your computer.
Start cmd, and move into path to folder (WW__ZS620KL_80.10.8.54_MP_user_20180517175955_release) .
Type `flashall_AFT.cmd`.
Click to expand...
Click to collapse
It works!!! Thank you very much! )
How can I install twrp, root? I want to run adaway or adblock
I have another question, now I have version ww_user_80.10.8.54 I would like to have new version WW-80.11.37.86. How can I install? OTA not work, how can I install zip file from asus.com/Phone/ZenFone-5Z-ZS620KL/HelpDesk_BIOS ? I would like to have a new version with twrp/root
jakubdg said:
I have another question, now I have version ww_user_80.10.8.54 I would like to have new version WW-80.11.37.86. How can I install? OTA not work, how can I install zip file from asus.com/Phone/ZenFone-5Z-ZS620KL/HelpDesk_BIOS ? I would like to have a new version with twrp/root
Click to expand...
Click to collapse
Talking about the steps what I have done for update my 5z.
Put the zip file that you downloaded on /sdcard/
And reboot.
After these steps, the device will find the update and let you to operate to update.
Please try .
GSPD said:
Talking about the steps what I have done for update my 5z.
Put the zip file that you downloaded on /sdcard/
And reboot.
After these steps, the device will find the update and let you to operate to update.
Please try .
Click to expand...
Click to collapse
It works! Super, I have WW-80.11.37.86
How can I install twrp and root?

[GUIDE] How to root your Asus Zenfone 6 without TWRP | Info about A/B

Hey guys and girls,
This is a bit of copy and paste for from my guide for the HTC U12+. I thought it might be helpful to people here too.
If you find mentions of the HTC U12+ please notify me and I will correct them.
I couldn´t find any guide on how to root the Asus Zenfone 6 without twrp yet, so I thought maybe it´s good to have one. It´s also useful for people who don´t like to boot/flash the recovery but want root access.
I also decided now to do a little write up about the A/B slot partition system.
General Information about the A/B slot partition system and seamless updates
Google firstly introduced seamless updates on the Pixel Phones and with it the A/B partition system.
So this means, contrary to non A/B devices, there are two copys of most partitions except userdata.
We have two system (system_a and system_b), two boot (boot_a and boot_b) and two vendor (vendor_a and vendor_b) partitions, amongst others (can be found further down in the partition list but let´s concentrate on these).
When booted in the OS, one slot is actively used and the other is "inactive".
The main advantage that emerges now is, that in case an OTA arrives the "inactive" partitions get updated, while the OS is running. That means while the actual OTA is happening you can use your phone just like you always do.
The following reboot will boot into the former "inactive" slot and use the seamless updated partitions. This happens seamless and just with a reboot. So OTAs are much faster!
If you are interested further here are some links:
https://www.xda-developers.com/list-android-devices-seamless-updates/
https://source.android.com/devices/tech/ota/ab/
https://source.android.com/devices/tech/ota/ab/ab_faqs
Here’s another writeup from the XDA portal!
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
But here are a few tips and tricks:
How to reboot to bootloader to be able to use fastboot:
From booted OS with buttons: Press and hold power down until the screen goes black, then press and hold power and vol up to enter bootloader
non responding and the phone isn´t booting: press and hold power plus volume up to enter bootloader
From the OS or recovery via ADB (requires USB Debugging enabled in dev options):
Code:
adb reboot bootloader
How to get the active slot:
Code:
fastboot getvar current-slot
How to set the active slot:
A word of advice. If you don´t know what you´re doing you should probably not change slots. Because my U12+ only has a working A Slot. The B slot is without the first OTA or flashing a RUU unbootable.
Set active slot to a:
Code:
fastboot --set-active=a
Set active slot to b:
Code:
fastboot --set-active=b
How to extract the boot.img from a firmware.zip
1. Download the firmware zip from here : https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/
2. Follow the steps described here: https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
3. Obtain your boot.img
How to root your phone without TWRP
Prerequisites:
- unlocked bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries (can always be found here
- working adb and fastboot environment
- magisk-patched boot.img
How to:
1. Download the latest magisk manager from here and install it on your phone: https://github.com/topjohnwu/MagiskManager/releases
2. Get a boot.img that fits your current firmware. Look at the point above, how to extract it from an Asus firmware zip.
Important: if you decide to use a pre-patched boot.img (available below), download it and place it in your fastboot folder, then skip to step 11!
3. Copy the extracted boot.img to your phone
4. Open the magisk manager app and tap two times on install
5. Now choose patch boot.img file and select the previously extracted boot.img you copied to your phone in the upcoming file chooser
6. Wait for the boot.img to be patched
7. Now connect your phone to your pc and make sure usb debugging is enabled in developer options
8. Open up a terminal in your fastboot folder and make sure adb is working by typing
Code:
adb devices
into terminal which should return your serial number
9. Pull the patches boot.img to your fastboot folder via:
Code:
adb pull /sdcard/Download/magisk_patched.img
10. Reboot to bootloader:
Code:
adb reboot bootloader
11. Flash the magisk patched boot.img:
Code:
fastboot flash boot magisk_patched.img
12. Congratulations you´re now rooted.
Pre-Magisk-Patched boot.imgs
Important: Make sure to download the correct version, that matches your firmware.
Downloads: https://www.androidfilehost.com/?w=files&flid=295609
Is it possible to do this and still get OTA updates from ASUS?
sidamos77 said:
Is it possible to do this and still get OTA updates from ASUS?
Click to expand...
Click to collapse
You need to unlock the bootloader for this which will prevent you from getting ota updates automatically from asus. But you can install updates manually.
Ok, great, thank you.
Remember, this will void your warranty (as per Asus' own definition). Sad, but true.
I would root it in an instant, but am hesitant due to warranty being void.
Any way to unofficially unlock the Bootloader?
vasra said:
Remember, this will void your warranty (as per Asus' own definition). Sad, but true.
I would root it in an instant, but am hesitant due to warranty being void.
Click to expand...
Click to collapse
In Europe unlocking the bootloader and rooting doesn't legally void warranty. It was ruled this way a few years ago.
Freak07 said:
[...]
Pre-Magisk-Patched boot.imgs
Important: Make sure to download the correct version, that matches your firmware.
Downloads: https://www.androidfilehost.com/?w=files&flid=295609
Click to expand...
Click to collapse
The folder WW_PHONE-16.1210.1904.75-0 which is the firmware my device has, is empty. Do you still have the prepatched boot.img of that version ? ASUS doesn't have that version for download anymore.
Thanks in advance.
If not: how can I update manually since I do not get any OTA Updates with a locked Bootloader ?
GRöder said:
how can I update manually since I do not get any OTA Updates with a locked Bootloader ?
Click to expand...
Click to collapse
https://swedroid.se/forum/threads/snabba-fragor-snabba-svar-zenfone-6.165775/page-26#post-2433773
https://swedroid.se/forum/threads/snabba-fragor-snabba-svar-zenfone-6.165775/page-37#post-2442236
Use Translator.
I managed to update my device using the stock recovery. (There is a option like "apply update from sdcard") Now it is on the -133 Firmware, so I should've been able to use the existing, pre-patched boot of that firmware. When I tried to flash it, I got the following error:
Code:
fastboot flash boot magisk_patched.img
target reported max download size of 805306368 bytes
sending 'bootb' (47064 KB)...
OKAY [ 1.094s]
writing 'bootb'...
FAILED (remote: (bootb_b) No such partition)
finished. total time: 1.106s
the getvar command returns the following output:
Code:
fastboot getvar current-slot
current-slot: b
finished. total time: 0.009s
Do you have any advice for me ?
Edit:
After being curious and trying
Code:
fastboot flash boot_a magisk_patched.img
which worked, I tried to flash it at the active slot b explicitly:
Code:
fastboot flash boot_b magisk_patched.img
which worked, too. I'm having root, now.
The point is, to specify the partition precisely (e.g. with _a or _b).
Thank you for the guide, maybe you could add my findings to make it easier for others to root their devices, @Freak07 .
GRöder said:
I managed to update my device using the stock recovery. (There is a option like "apply update from sdcard") Now it is on the -133 Firmware, so I should've been able to use the existing, pre-patched boot of that firmware. When I tried to flash it, I got the following error:
the getvar command returns the following output:
Do you have any advice for me ?
Edit:
After being curious and trying which worked, I tried to flash it at the active slot b explicitly: which worked, too. I'm having root, now.
The point is, to specify the partition precisely (e.g. with _a or _b).
Thank you for the guide, maybe you could add my findings to make it easier for others to root their devices, @Freak07 .
Click to expand...
Click to collapse
Did you download the latest adb and fastboot binaries from the link I provided in the OP?
Or did you use already existing ones or from a toolkit/easy installer etc. from somewhere on xda?
To me it sounds you were using outdated binaries.
Fastboot flash boot boot.img detects the active slot automatically if you’re on the latest binaries. Did it like this on the zenfone like on all other A/B devices I’ve owned so far and it works just fine.
Freak07 said:
Did you download the latest adb and fastboot binaries from the link I provided in the OP?
Or did you use already existing ones or from a toolkit/easy installer etc. from somewhere on xda?
To me it sounds you were using outdated binaries.
Fastboot flash boot boot.img detects the active slot automatically if you’re on the latest binaries. Did it like this on the zenfone like on all other A/B devices I’ve owned so far and it works just fine.
Click to expand...
Click to collapse
That might have been the the point. In fact, I did download them, but I used (definately outdated, because on my pc since literally years) a minimal adb and fastboot installation.
I didn't think about it, as this is my first A/B device.
I won't try it now with the latest ones, because it worked and I don't want to destroy something (since we still dont have a working TWRP for backup & recovery) but I guess you're right, and the problem were the outdated binaries.
Thank you.
GRöder said:
If not: how can I update manually since I do not get any OTA Updates with a locked Bootloader ?
Click to expand...
Click to collapse
Download the new Firmware from Asus and copy it to the root of sdcard. Unplug the usb cable or reboot or search for update in settings. It will find the update file and display a notification.
isthisadagger said:
Download the new Firmware from Asus and copy it to the root of sdcard. Unplug the usb cable or reboot or search for update in settings. It will find the update file and display a notification.
Click to expand...
Click to collapse
In fact, I tried that before I tried the stock-recovery-method (found it at the ASUS FAQ-pages), but it didn't work, even after a reboot, no notification showed up.
GRöder said:
I managed to update my device using the stock recovery. (There is a option like "apply update from sdcard") Now it is on the -133 Firmware, so I should've been able to use the existing, pre-patched boot of that firmware. When I tried to flash it, I got the following error:
Code:
fastboot flash boot magisk_patched.img
target reported max download size of 805306368 bytes
sending 'bootb' (47064 KB)...
OKAY [ 1.094s]
writing 'bootb'...
FAILED (remote: (bootb_b) No such partition)
finished. total time: 1.106s
the getvar command returns the following output:
Code:
fastboot getvar current-slot
current-slot: b
finished. total time: 0.009s
Do you have any advice for me ?
Edit:
After being curious and trying
Code:
fastboot flash boot_a magisk_patched.img
which worked, I tried to flash it at the active slot b explicitly:
Code:
fastboot flash boot_b magisk_patched.img
which worked, too. I'm having root, now.
The point is, to specify the partition precisely (e.g. with _a or _b).
Thank you for the guide, maybe you could add my findings to make it easier for others to root their devices, @Freak07 .
Click to expand...
Click to collapse
sorry guy,
how you unlocked the bootloader ? for me official tool asus doens't work. error due to internet connection is the message.
please can you explain every step ? thanks
Ya how do we unlock the bootloader without asus knowing it
MirkoMirko9 said:
sorry guy,
how you unlocked the bootloader ? for me official tool asus doens't work. error due to internet connection is the message.
please can you explain every step ? thanks
Click to expand...
Click to collapse
nikhil18 said:
Ya how do we unlock the bootloader without asus knowing it
Click to expand...
Click to collapse
I used the official app, while the device was connected to the internet. So yes, ASUS knows that I unlocked the device.
The device was still at the -75 firmware, when I did it.
 @MirkoMirko9 If you can live with asus knowing that you unlocked the device, try it again with active internet connection.
As far as I know, there is no other method yet.
unable to unlock bootloader with the official unlock device tool, it is showing network error although my network is alright. Any workaround?
QuazIqbal said:
unable to unlock bootloader with the official unlock device tool, it is showing network error although my network is alright. Any workaround?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=79817571&postcount=31
magisk_patched boot.img for .156 firmware is uploaded to the patched boot.imgs folder

[Updated][GUIDE]: How to unbrick your Zenfone 6 Android P/Q (ZS630KL)

Hello.
This guide will help you unbrick your device in case your devices hangs as it boots, and always boots into fastboot mode and recovery is unavailable and the like.
Note: Unlocked bootloader is not required to do any of the actions described in this guide.
Disclaimer: I'm in no way responsible for the actions you perform and whatever happens to your device due to these actions. Proceed at your own risk.
This guide is roughly based on the one @_Kuroi_ made. I have stripped out the OTA updating portion because at least currently I have the latest firmware for android 9 and 10. If you need instructions for applying an ota please read the original thread.
Prerequisites:
Service Firmware (Full QFIL) Only for WW SKU
If anyone would like to mirror these feel free to just send me a message and I'll add it to the OP.
WW-16.1220.1909.194 (Last Android 9/Pie Version)
Here
WW-17.1810.2009.176 (Latest at the time of posting Android 10/Q Version)
Here
Platform tools of Android SDK.
Latest package can be downloaded from: Windows | Linux. Somewhat optional but good to have.
Step 1 - Preparing the environment
Download and extract either the Android 9 or Android 10 Service firmware. Depending on what your phone was running before it was bricked.
Step 2 - Flashing service firmware
Connect your phone via USB
Enter fastboot mode
1.1 Turn off your device, then while holding down the volume up button press and hold the power button Release the power button when it powers up (keep holding the volume up button)
Open CMD (windows) | Terminal (unix)
CD into the folder with service firmware from item #2 from the step above.
Make sure your phone is detected by typing fastboot devices/FONT]
[*]Ensure battery is at least 20% charged. Aside from normal means, it's possible to check the battery charge via fastboot oem get-batcap.
Sample output: (bootloader) bat cap = 35, which means that the battery is 35% charged.
IMPORTANT NOTE BEFORE CONTINUING:
By default, flashing with one of the scripts wipes your userdata, in other words, it performs a factory reset.
[*]Run the script
1. 1. Windows: In the CMD you opened earlier, type flashall.cmd[/COLOR]
1. 2. Unix: In the Terminal you opened earlier, type ./flashall.sh
Note: An obvious note, do not disconnect your device from your PC while flashall script is running. Your device will reboot a few times during the execution.
[*]Once script outputs format logdump... and the phone reboots, service firmware will be flashed.
Your phone is now unbricked Congrats!
That's pretty much it. If you followed the steps above correctly, you should once again have a running phone.
If you have any questions, do not hesitate to ask.
Cheers.
Thanks for the files
I found some sites that might publish service fws
Spoiler: links
Rom stock / raw và bypass FRP cho Asus Zenfone 6 (ZS630KL) - vnROM
Rom stock / raw và bypass FRP cho Asus Zenfone 6 (ZS630KL) DOWNLOAD: WW_ZS630KL_17.1810.2011.183_M3.18.40.20_Phone-user.raw.zip / OneDrive / GDrive2 / GD3 WW_ZS630KL_17.1810.2010.179_M3.18.40.19_Phone-user.raw.zip / AFH / OneDrive / GDrive2...
vnrom.net
ZS630KL | Halab Tech Support
support.halabtech.com
{Mod edit: Links removed - Oswald Boelcke, Moderator}
Search for zs630kl | GSM HOSTING FILES
gsmhostingfiles.com
ZS630KL | Kurdish Firmware
kurdishfirmware.com
Search for zs630kl | VietNam GSM Services
vngsmservices.com
https://addrom.com/stock-raw-rom-and-bypass-frp-for-asus-zenfone-6-zs630kl/https://forum.gsmnigeria.com/threads/asus-zenfone-6-zs630kl-i01wd-firmware-complete-here.469https://firmwarex.net/asus-zenfone-6-i01wd-zs630kl-official-firmware/https://www.joelzr.com/2020/03/kumpulan-firmware-asus-raw-zip-dan-aft.htmlhttps://www.fullstockfirmwaredownload.com/asus/
FIRMWARE ASUS | Clan SOFT
www.clansoft.net
IMEI Source Forum
forum.imeisource.com
Mostrando resultados para 'zs630kl'. - Clan GSM
https://forum.imeisource.com/search/416782/?q=zs630kl&o=date
Asus Zenfone 6 ZS630KL/I01WD Firmware Here
Asus Zenfone 6 ZS630KL/I01WD Firmware Complete Here, All Link Google Drive Zenfone 6 ZS630KL/I01WD Download CSC_ZS630KL_16.0904.1810.58_M1.6.11.raw_Lock-132155848436752587 WW_ZS630KL_16.1210.1903.67_M2.6.17.12_Phone-user.raw-132010344012194561...
www.martview-forum.com
404 Error - Page Not Found! | Original Flash File Website GivemeRom
www.givemerom.com
https://firmware.gem-flash.com/index.php?a=downloads&b=folder&id=32713
ASUS Zenfone 6 I01WD (ZS630KL) Firmware | Qualcomm SDM855
Kali ini Firmware27 akan berbagi Firmware ASUS Zenfone 6 (2019) I01WD ZS630KL Qualcomm snapdragon 855, Firmware ini bisa digunakan untuk m...
www.firmware27.com
I was getting an error when I first tried executing flashall script
Code:
"flash boot boot.img BEGIN"
fastboot: error: boot partition is smaller than boot image
"flash failed and exit"
fastboot: error: boot partition is smaller than boot image
"FLASH FAIL"
fixed by running update_edl script
I also got an error saying 'QMSL_MSVC10R.dll' is missing. That's Microsoft Visual C++ 2010 Redistributable.
I also got another error when running flash all script
Code:
.\flashall.cmd
Spoiler
Code:
"=========================================== "
" format "
"=========================================== "
"enable flash and erase"
"format ADF..."
fastboot: error: Cannot generate image for ADF
"Format ADF fail and try again."
0
fastboot: error: Cannot generate image for ADF
"Format ADF fail and try again."
1
fastboot: error: Cannot generate image for ADF
"Format ADF fail and try again."
2
fastboot: error: Cannot generate image for ADF
"failed and exit"
"format asdf..."
fastboot: error: Cannot generate image for asdf
"Format asdf fail and try again."
0
fastboot: error: Cannot generate image for asdf
"Format asdf fail and try again."
1
fastboot: error: Cannot generate image for asdf
"Format asdf fail and try again."
2
fastboot: error: Cannot generate image for asdf
"failed and exit"
******** Did you mean to fastboot format this f2fs partition?
Erasing 'userdata' OKAY [ 0.588s]
Finished. Total time: 0.607s
"wait for 30 seconds for bootloader to be ready..."
"reboot-bootloader..."
fastboot: error: Cannot generate image for ADF
fastboot: error: Cannot generate image for asdf
"failed and exit"
< waiting for any device >
Erasing 'userdata' OKAY [ 0.587s]
CreateProcess failed: %1 non è un'applicazione di Win32 valida. (193)
fastboot: error: Cannot generate image for userdata
"enable charging mode"
OKAY [ 0.002s]
Finished. Total time: 0.003s
"turn off uart"
OKAY [ 0.011s]
Finished. Total time: 0.011s
"turn off framdump mode"
(bootloader) *arg: n
(bootloader) GetForceRamdump(): false
OKAY [ 0.013s]
Finished. Total time: 0.013s
"disable flash and erase"
"Download_PASS"
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.006s
that's because I replaced fastboot of service fw with a newer fastboot exe
I upgraded to the latest android 11 version (UL-ASUS_I01WD-ASUS-18.0610.2101.132-1.1.1-user.zip) by placing the firmware file from asus download page to internal storage, rebooted, clicked on the notification saying an upgrade was available
changelog from asus website
I also found out from a thread in this section saying that you can use a script (vm03/payload_dumper: Android OTA payload dumper - GitHub) hosted on github to dump img files from the full ota that gets published from asus.
You only need termux app and then run
Code:
pkg install python
python -m pip install --upgrade pip
python -m pip install protobuf
python -m pip install bsdiff4
#gain access to storage where payload.bin is located
termux-setup-storage
python payload_dumper.py payload.bin
i got
Code:
Failed to load/authenticate boot image: Load Error
when rebooting the phone to twrp
Fixed by flashing boot and dtbo images to a/b slots
another problem was mtp not working when i pressed Format Data in twrp. Rebooting twrp again made mtp work again. adb sideload worked too
Guys, can you share the link for the latest raw firmware ?
latest raw firmware is available on halabtech and kurdish firmware, search with google
WW_ZS630KL_18.0610.2101.132_M3.23.44.19_Phone-user.raw.zip
sadly both sites let you download it only if you pay
raw firmware should only be available to repair centers so all the zips you find have been leaked

Categories

Resources