First of all, this guide expects you to have some basic knowledge how to use fastboot, have working ADB/fastboot connection on your computer and understand the fact that this may brick your phone if you mess up.
I am NOT responsible for anything! This will wipe everything on your phone, so get backups if needed.
This guide is written for X720 and supplied files are ONLY for X720. Same procedure will work on X727, but you will have to get right files yourself.
All files are from stock 23S, just extracted, converted and repacked for your convenience.
Read the whole guide before doing anything. If you're unsure about anything, don't do it.
Here we go:
1. Download .zip containing files from Mega: https://mega.nz/#!5boxDYrL!_O-oD05yhiU5FbCmYuf47VH4Qar5RhV5LKwyHa39bWM
2. Extract files to path where you are able to flash them using fastboot (ie. same folder with fastboot)
3. Boot your phone to bootloader (Vol- & Power)
4. Flash everything:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format data <-- THIS WILL WIPE YOUR PHONE INCLUDING INTERNAL STORAGE
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash ddr ddr.mbn
fastboot flash cmnlib cmnlib.mbn
fastboot flash hyp hyp.mbn
fastboot flash pmic pmic.elf
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash xbl xbl.elf
fastboot flash keymaster keymaster.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash bluetooth BTFM.bin
fastboot flash devinfo devinfo.bin5. Reboot, and let it boot up (takes some time)
6. Flash TWRP, wipe everything and install ROM (you have done this before, won't write a guide)
Credit for this guide goes to @darkobas
get error
C:\Program Files (x86)\Minimal ADB and Fastboot\x720_upgrade_23s>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
I'm only guessing, since many have flashed this successfully, but maybe a bad download or incompatible fastboot.
Presterin said:
I'm only guessing, since many have flashed this successfully, but maybe a bad download or incompatible fastboot.
Click to expand...
Click to collapse
thx
i will try again.
Does anyone know which ones are safe to flash over the existing rom? I do not wish to wipe or break current rom.
I flashed everything except system and boot on top of Omni rom. Everything works great.
Does anyone know where I can get all of the files for my x727, I considered using the files from these OTA zips but I think some of the files are missing like the modem firmware and system.img.
On x720 some of the files were divided into scatter files, had to do some research to get them sorted.
Which fastboot is compatible with system.img? Because of me too :"target reported max download size of 536870912 bytes
Invalid sparse file format at header magi". minimal fast boot 1.42
Edit: ok..as long as the post I wrote started installation
Should/Can we install the latest fastboot? Mine is on shop altered 17s from over a year a go, which to be fair runs great; i just fancy a change.
Thanks
write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do
Any solution?
Hasancaktar said:
write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do
Click to expand...
Click to collapse
Stuck here as well
Hasancaktar said:
write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do
Click to expand...
Click to collapse
First, you provided no information. For example what phone do you have, what OS etc.
I am guessing EUI: It would be alot easier to simply flash the firmware for your device instead of flashing the exact same pieces of it one at a time. By extracting the bits from the full OS.
This is a old outdated guide that has way too many steps, and it was made a long time ago. Since the name of the guide is upgrading firmware, I assume thats what you are trying to do.
Since you are hoping to flash firmware, I will go ahead and assume that you already have your bootloader unlocked, have flashed Twrp and are rooted? You can accomplish updating your firmware with one step. > Go to Lineage 15.1 page and go to downloads section. Here you will see firmware listed, download the firmware to your device. One flash in Twrp will install all of the radio and sensor files needed.
Hint: always boot to recovery first, checking the Twrp installation boxes if present> this is a best practice to avoid bricking your phone.
If you have any issue after following the steps I mentioned ( Its possible because of the fastboot commends) You may need to clean wipe reset and start fresh
Before you begin disable any passwords and fingerprints within the system settings.
Boot to recovery > click wipe > advanced wipe > check cache ( not Dalvik, just cache) > swipe> press home key to return to main menu.
Click install >Navigate to your download folder and select firmware > swipe to install > clear cache again> reboot to recovery
If there are any check boxes to check for TWRP installation, check them >
Once back in recovery reboot to system > Finished
Great guide Thanks.
It saved me from a system wipe and a nightly not recognized by TWRP...:crying:
tsongming said:
First, you provided no information. For example what phone do you have, what OS etc.
I am guessing EUI: It would be alot easier to simply flash the firmware for your device instead of flashing the exact same pieces of it one at a time. By extracting the bits from the full OS.
This is a old outdated guide that has way too many steps, and it was made a long time ago. Since the name of the guide is upgrading firmware, I assume thats what you are trying to do.
Since you are hoping to flash firmware, I will go ahead and assume that you already have your bootloader unlocked, have flashed Twrp and are rooted? You can accomplish updating your firmware with one step. > Go to Lineage 15.1 page and go to downloads section. Here you will see firmware listed, download the firmware to your device. One flash in Twrp will install all of the radio and sensor files needed.
Hint: always boot to recovery first, checking the Twrp installation boxes if present> this is a best practice to avoid bricking your phone.
If you have any issue after following the steps I mentioned ( Its possible because of the fastboot commends) You may need to clean wipe reset and start fresh
Before you begin disable any passwords and fingerprints within the system settings.
Boot to recovery > click wipe > advanced wipe > check cache ( not Dalvik, just cache) > swipe> press home key to return to main menu.
Click install >Navigate to your download folder and select firmware > swipe to install > clear cache again> reboot to recovery
If there are any check boxes to check for TWRP installation, check them >
Once back in recovery reboot to system > Finished
Click to expand...
Click to collapse
I hate to be that person, but where the heck is the firmware dl's on the LIneage site? I did search and search. Thanks in advance.
jackpollard said:
I hate to be that person, but where the heck is the firmware dl's on the LIneage site? I did search and search. Thanks in advance.
Click to expand...
Click to collapse
https://forum.xda-developers.com/le-pro3/development/rom-lineageos-15-0-leeco-le-pro3-t3683720
amdol said:
https://forum.xda-developers.com/le-pro3/development/rom-lineageos-15-0-leeco-le-pro3-t3683720
Click to expand...
Click to collapse
Thank you! My flaw was looking on https://lineageos.org/ and not on here.
ajegile said:
get error
C:\Program Files (x86)\Minimal ADB and Fastboot\x720_upgrade_23s>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
get the same. iam not shure if i have the x722 or x720. they look same
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.
Hello everyone,
I need help to start on flashing g7 play etc. In the old days I flashed phones like galaxy s3, s4, s5 and Note 4, but I'm not an expert in all of this.
Then I changed to iPhone 6s and now I want to come back to Android.
My goal:
de-googled moto g7 play
Android 9/10 -> would prefer 10
if possible -> root
My Device:
moto g7 play - XT1952-1
(bootloader unlocked)
---
Build number:
PPYs29.105-134-7
---
If have read most of the Threads for the g7 play, but at the moment I'm a little scared to brick it.
I have some questions:
1. I copied together for myself a Instruction (at the end of post). Could you tell me if this is OK like this, or do I have to do additional things before start?
2. In my copied instruction, at the point of flashing the GSI (Instruction ROM: -> Step 1)
What does "Dirty flashing your g7 play" mean? Do I have something additional to do, before following the instruction, or is dirty flashing the following instruction of the post?
3. Modded phh -> I have no information about this, could you explain, or give me link?
4. Overlay -> I have no information about this, could you explain, or give me link?
Thanks for your help
---
INSTRUCTION: (it is a quick&dirty instruction)
ROM:
lineage-17.1-20200309-UNOFFICIAL-treble_a64_bvN.img.xz
DTBO:
dtbo.img
(https://drive.google.com/file/d/1pV6-LbNoMG0J8vcyAWN0QWYGx67vxBgT/view?usp=sharing)
---
---
Instruction ROM:
step 1
Dirty flashing your g7 play -> what does that mean, what to do???
step 2
extract the gsi
step 3
put phone in fastboot mode and enter the commands
$ fastboot -w
$ fastboot flash dtbo dtbo.img
$ fastboot flash system [this is where you put your android 10 img]
$ fastboot boot twrp.img
(https://forum.xda-developers.com/g7-play/development/gsi-images-g7-play-t3980807
#1)
------------------------
TWRP:
twrp.img
---
Instruction TWRP:
step 1
Fastboot boot twrp.img
step 2
Copy twrp to your external sdcard, or use adb push twrp.img /tmp/twrp.img
step 3
Go to Advanced > install recovery ramdisk then navigate to tmp or your external sdcard and select the twrp.img you copied
step 4
Use wipe > format > type "yes" to continue then use reboot > recovery from twrp's menus
step 5
Once twrp starts up again, wipe data & system, make sure system is mounted, then flash a GSI. Flash the universal disabler afterwards.
If you get a failed to unmount error, manually mount all partitions and reflash whatever it errored on
step 6
Optional: Flash my modded phh for root. (Install the apk after.) Never use Magisk! It will fail to root, cause a bootloop, or break twrp
FIX navbar on a GSI:
$ adb root
$ adb shell
$ setprop persist.sys.phh.mainkeys 0
$ reboot
(https://forum.xda-developers.com/g7...ery-dirty-ported-twrp-g7-play-t3947205/page41
#403)
------------------------
Modded phh: -> LOS16 & 17
modded-phh-superuser.zip
phh-su.apk
(https://forum.xda-developers.com/showpost.php?p=81503713&postcount=240)
------------------------
Overlay: -> what does that mean???
treble-overlay-moto-g7play.apk.zip
(https://forum.xda-developers.com/g7...ery-dirty-ported-twrp-g7-play-t3947205/page41
#404)
------------------------
@ggg777
First make sure you install the stock OS to both slots, including the bootloader. I forgot to flash bootloader_b, and got stuck in EDL last week. You don't want that to happen and it's not easy to get out of. If you do this first, you will not have to worry about getting bricked.
Use my instructions found here for twrp. Inside the instructions you'll also find a link to my modded phh. Flashing a GSI can be done with twrp or fastboot. You also don't need the dtbo.img anymore since it's embedded inside of twrp. The trickiest part really, is just getting twrp installed. If you're using twrp to install a GSI, wipe system, data, dalvik, then flash the image to system. (You'll get a location prompt.) After installing a GSI, copy the overlay to /vendor/overlay, and set permissions on it to 0644, then reboot. Flash modded phh for root if you're using LOS 16 or 17. I think it's already included in Phh's AOSP builds.
There's also a trick to dual boot your OS. I keep one slot with stock installed, that's debloated and rooted with magisk. The other slot I use for flashing GSIs. Twrp can't restore encrypted data for stock, but you can format /data using "yes" then switch slots and use "reboot recovery" to boot up stock with magisk. To swap back to the GSI, fastboot boot twrp, format data, switch slots from the reboot menu, reboot to recovery. If twrp starts, you changed slots successfully. Then just restore data for lineage and bootup.
Oh by the way, "dirty flashing" is just flashing an OS update without wiping data first. I don't recommend it though. Sometimes bugs from older builds will get carried over. You don't need to do that to install LOS 17 or Android 10. It might've been true at one time, but it isn't now. You can just do your wipes and flash the latest build.
Thanks for your Help
How can I check if both partitions are with stock and bootloader?
Is there a trick to copy a working partition to the oter?
I would flash like it is written in this: [Guide][Channel][Stock]Moto g7 play Factory Firmware Images
(https://forum.xda-developers.com/g7-play/how-to/channel-moto-g7-factory-firmware-images-t3996303)
Would it flash both partitions (if only one is written)?
Thanks for your help
ggg777 said:
Thanks for your Help
How can I check if both partitions are with stock and bootloader?
Is there a trick to copy a working partition to the oter?
I would flash like it is written in this: [Guide][Channel][Stock]Moto g7 play Factory Firmware Images
(https://forum.xda-developers.com/g7-play/how-to/channel-moto-g7-factory-firmware-images-t3996303)
Would it flash both partitions (if only one is written)?
Thanks for your help
Click to expand...
Click to collapse
Typically if you've taken an OTA then you already have both slots filled. You can check with...
Code:
fastboot getvar all
Near the bottom you'll see some slot information. If slot b is active, then you should already be covered. I still think it's best to manually flash both slots though. If you've never updated then slot b is definitely empty. This is what I do...
Code:
fastboot flash boot_a boot.img
fastboot sending image boot_a...
Successful!
Image not signed blah blah something that isn't important...
Hit the up arrow on the keyboard then just change _a to _b
Code:
fastboot flash boot_b boot.img
Same with system, only I run through the list of sparse chunks in one shot, then hit the other slot. Use the big series of sparse chunks (0-7) on both slots. Skip the two that would normally go to system_b.
Code:
fastboot flash system_a system.image_sparsechunk.0
fastboot flash system_a system.image_sparsechunk.1
fastboot flash system_a system.image_sparsechunk.2
etc...
Then on the other side the same way.
Code:
fastboot flash system_b system.image_sparsechunk.0
fastboot flash system_b system.image_sparsechunk.1
fastboot flash system_b system.image_sparsechunk.2
etc...
When you get to oem, do not use oem_other.img, flash oem.img to both slots instead. Basically just make sure you do that with everything. E.g. dsp_b modem_b. I'm sure you get the idea by now.
Hello Spaceminer,
I have little knowledge in working with terminal in debian (I used man fastboot and tried some things like changing slots but this did not work). And then I tried some of these things and was to scared to brick it so I flashed it with RDS Lite (I hate to use Windows ) last night.
With RDS Lite flashing was no problem and I got a OTA, so slots a and b are not empty. After that I used your TWRP-Guide which you linked and it worked
BUT
Then I was trying to flash a GSI (arm32binder64ab):
lineage-17.1-20200309-UNOFFICIAL-treble_a64_bvN.img
Havoc-OS-v3.0-20191226-A64AB-Unofficial.img
system-quack-arm32_binder64-ab-vanilla.img
it completed but failed to boot:
Start Up Failed:
---
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
No bootalbe A/B slot
Failed to boot Linux, falling back to fastboot
Boot up failed
---
TWRP is always available with:
fastboot -> recovery
Could you please help me to handle this?
I would really love to use this phone de-googled with root permission cause I'm sad of spying on me by Gafa and the moto g7 play (I hate the size of the bigger ones) looks like the perfect model for me
PS: I have some screenshot's if you need
ggg777 said:
Hello Spaceminer,
I have little knowledge in working with terminal in debian (I used man fastboot and tried some things like changing slots but this did not work). And then I tried some of these things and was to scared to brick it so I flashed it with RDS Lite (I hate to use Windows ) last night.
With RDS Lite flashing was no problem and I got a OTA, so slots a and b are not empty. After that I used your TWRP-Guide which you linked and it worked
BUT
Then I was trying to flash a GSI (arm32binder64ab):
lineage-17.1-20200309-UNOFFICIAL-treble_a64_bvN.img
Havoc-OS-v3.0-20191226-A64AB-Unofficial.img
system-quack-arm32_binder64-ab-vanilla.img
it completed but failed to boot:
Start Up Failed:
---
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
No bootalbe A/B slot
Failed to boot Linux, falling back to fastboot
Boot up failed
---
TWRP is always available with:
fastboot -> recovery
Could you please help me to handle this?
I would really love to use this phone de-googled with root permission cause I'm sad of spying on me by Gafa and the moto g7 play (I hate the size of the bigger ones) looks like the perfect model for me
PS: I have some screenshot's if you need
Click to expand...
Click to collapse
Hey im in a smiliar situation with the G7 Play (XT1952-2)
I have the same goal of running this phone without google..
I would like to install LineageOS with microG (signature spoofing)
Have you been successful with this? Do you have a A-Z list of instructions for a fellow newbie?