Develop Bugs

How to go from Lineage OS 14.1 to stock? (Updated with the process & latest links)

How to go from Lineage OS 14.1 to stock? (Updated with the process & latest links)
I am currently on lineage OS 14.1 (7.1.2) dated 18.09.2017.
I want to go back to stock firmware as I am facing some issues with lineage.
How to find the latest firmware. Found this website which has all the images https://firmware.center/firmware/Motorola/Moto Z Play/Stock/XT1635-02/
But I am unable to select the correct one for my device. (do not want to brick it). Also found another thread stating latest firmware
https://forum.xda-developers.com/moto-z-play/help/addisonnpns26-118-22-1cid50subsidy-t3675521
I am an Indian MOTO Z Play
Is there a way to go full stock and also start to receive OTA updates. Can someone provide me with full guide with links?

First you need exactly your software channel and the build of your baseband and bootloader. You know how to get this information?

After a lot of tries, finally was able to go back to stock. Will be compiling a guide for other to follow with links.
On latest 7.1.1 with August patches.
Is there a problem with audio fx,
Even viper4android not working.

kkube said:
After a lot of tries, finally was able to go back to stock. Will be compiling a guide for other to follow with links.
On latest 7.1.1 with August patches.
Is there a problem with audio fx,
Even viper4android not working.
Click to expand...
Click to collapse
I'll be waiting for it.

Process to go from custom rom back to stock (August update)
There are several guides on going back from custom rom to full stock, but still I made this guide with latest links. I just went from LOS 14.1 back to full stock. Below is the step I took:
1) Download and install minimal ADB AND FASTBOOT
I used version 1.4.2 which is the latest version https://www.androidfilehost.com/?fid=745425885120698566
2) Download and install motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
3) Download the latest firmware
I used ADDISON_NPNS26.118-22-1 which has august security updates https://www.androidfilehost.com/?fid=673368273298986785
4) Extract the zip file (firmware) and move all its contents to the folder where you have installed minimal adb and fastboot
5) Create a text file, add the following text to it and save it as "launch.bat" in the same folder.
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
Click to expand...
Click to collapse
6) Switch off your phone and open it in fastboot mode (press power and volume down button for few seconds after phone as switched off)
7) Connect your mobile to your computer
8) Click on the launch.bat file that you saved and it will install stock firmware on to your mobile. It will take a couple of minutes. (It will wipe everything on your mobile so take a backup of your important data)
9) Once the process is complete, it will ask you to enter any key, after which it will reboot itself.
Once rebooted, you will have full stock, non rooted, and latest firmware with august patches.

Is this works with European version of Moto Z Play? Like I bought it from France. Thanks.
And can we do OTA updates after doing this?

Thank you so much for this guide, my phone was rebooting to recovery every single time and nothing worked. I flashed this rom as you said and my phone just booted and it's working. I can't believe it.
Is this works with European version of Moto Z Play? Like I bought it from France. Thanks.
Click to expand...
Click to collapse
My phone is reteu and after flashing is still on reteu, so it should be fine, dont worry. Also you should get any future updates via OTA.

kkube said:
There are several guides on going back from custom rom to full stock, but still I made this guide with latest links. I just went from LOS 14.1 back to full stock. Below is the step I took:
1) Download and install minimal ADB AND FASTBOOT
I used version 1.4.2 which is the latest version https://www.androidfilehost.com/?fid=745425885120698566
2) Download and install motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
3) Download the latest firmware
I used ADDISON_NPNS26.118-22-1 which has august security updates https://www.androidfilehost.com/?fid=673368273298986785
4) Extract the zip file (firmware) and move all its contents to the folder where you have installed minimal adb and fastboot
5) Create a text file, add the following text to it and save it as "launch.bat" in the same folder.
6) Switch off your phone and open it in fastboot mode (press power and volume down button for few seconds after phone as switched off)
7) Connect your mobile to your computer
8) Click on the launch.bat file that you saved and it will install stock firmware on to your mobile. It will take a couple of minutes. (It will wipe everything on your mobile so take a backup of your important data)
9) Once the process is complete, it will ask you to enter any key, after which it will reboot itself.
Once rebooted, you will have full stock, non rooted, and latest firmware with august patches.
Click to expand...
Click to collapse
Thanks a lot for this guide! Just wanted to ask if it's safe and stable to root this and pass safetynet check.
Thanks for you time

Only way to root and still pass safetynet is via magisk
But unfortunately it needs a custom kernel with f2fs fix. However with 7.1 update motorola fixed it but broke some other things.
There is not a custom kernel for 7.1, so till then no way to root and have safety net.
But you can easily root via magisk

akshaypatil869 said:
Thanks a lot for this guide! Just wanted to ask if it's safe and stable to root this and pass safetynet check.
Thanks for you time
Click to expand...
Click to collapse
Only way to root and still pass safetynet is via magisk
But unfortunately it needs a custom kernel with f2fs fix. However with 7.1 update motorola fixed it but broke some other things.
There is not a custom kernel for 7.1, so till then no way to root and have safety net.
But you can easily root via magisk

Does anyone receive the update with September patch via OTA after back to stock following post #5 instructions?

This a fantastic guide - THANKS!!! - I have linked to it giving credit. Thanks!

I have also a thread, if you follow that one. Bootloader is locked/ u will be able to get ota'$

[Q] Stuck in boot animation after formatting userdata?

My nexus 5x is stuck in the boot animation (spinning circles) after erase/format of userdata (for at least 30 minutes, and tried holding power to reboot several times with the same result).
I recently updated to the latest Oreo build in the same way that I always have in the past. This time the only thing different was that I wiped userdata. I had already updated from 7.1.2 to the 8.0.0 August build, and then to the September build without any problems.
I got tired of lagging and other issues so I did a factory reset and wipe data using settings. After that the steps I used to flash the October update:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot erase userdata
fastboot format userdata
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
This is the first time that I've formatted and erased userdata so I think that's what caused the problem. I've never had a problem until now and the only reason I tried those two commands is because none of the recent nexus images come with a userdata.img file. What can I do to get back up and running with a successful boot?
Thanks much!
Update:
I flashed the userdata.img file from the stock 7.1.1 build (the last build that included a userdata.img file that I was able to find). After reboot it continued to hang on the spinning circles. Then I went ahead and flashed the full 7.1.1 build and it booted to the initial setup screen like normal.
Since that worked, I flashed the October 8.0 update and it's now stuck at the Google logo (plain white google text on black background) while overheating. Any advice at this point would be appreciated. I don't really want to go back to 7.1.2 and be stuck there.

Flash the complete Oreo-firmware. If you cleaned everything, why to trust in functionality of a big update?

rp158 said:
Flash the complete Oreo-firmware. If you cleaned everything, why to trust in functionality of a big update?
Click to expand...
Click to collapse
I did flash the complete Oreo (October update). I resolved the issue by flashing 7.1.2 with the vendor and cache img from 7.1.1 and letting the OTA updates happen. Now I'm on the October 8.0 update.
I'm not sure what the problem was, maybe a corrupted download of the OPR4.170623.009, Oct 2017. I resolved the issue before I did an SHA-256 Checksum.

How to get to Oreo from Custom 7.1.1 Rom

Hello all,
I'm currently running this stock+ 7.1.1 (Nov. security patch) custom rom (Found it here - https://forum.xda-developers.com/moto-z-play/development/rom-nov-patch-npns26-118-22-2-8-t3717037 )
and am on TWRP 3.2.0-0.
I'd like to flash the official Oreo update but after doing a lot of research It looks like I need to be on the stock 7.1.1 February patch in order to sideload 8.0 (https://forum.xda-developers.com/moto-z-play/help/sideload-addison-oreo-8-0-update-noob-t3779630) but I'm having a hard time getting a clear answer on how to go about that. It sounds like I can fastboot flash stock 7.1.1 feb. but I'm seeing posts about how the bootloader can be bricked and I honestly have no idea what I'm doing
Should I just wait for a Custom Stock 8.0/8.1 ROM like the one I'm running now that I can just flash in TWRP?

1) You are correct in that the official Oreo OTA requires either the Feb 2018 security patch Nougat 7.1.1 firmware or the most recent leaked Oreo soak test. The most straightforward way would be to download the Feb 2018 stock firmware and flash that via fastboot. You do not have to re-lock your bootloader to flash the stock ROM, but I would recommend you take a backup of your device in TWRP and keep the backup safe, in case the flash goes wrong.
Here's a link for the fastboot stock ROM for the Feb 2018 stock firmware: https://forum.xda-developers.com/showpost.php?p=76180201&postcount=21
Flashing commands and the guide for setting up your computer with ADB and fastboot can be found here https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190 If you do not want to re-lock your bootloader, you can omit the second set of commands and if you wish to keep your data, you can try and omit fastboot erase userdata though you may wish to include the erase userdata command for a clean flash.
Thus, if you wish to simply revert back to stock with the Feb 2018 firmware - no bootloader locking, and try to keep your data - you could use these commands (though I have used the same set of flashing commands in the ADB terminal to flash stock firmware, I do not own a Moto Z Play - I have a G4 Plus, so you may wish to wait for a Z Play owner's input. These are however standard fastboot flashing commands for Motorola stock firmware).
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase DDR
fastboot oem fb_mode_clear
1a)You may wish to verify that the number of system.img sparsechunks is the same in the above command list as in the unpacked firmware folder.
1b)Be aware this procedure will replace TWRP with stock recovery, remove root and any modifications you've made. If you are not happy with that, then you may wish to wait for the Oreo TWRP flashable stock ROM.
1c)This procedure should update your bootloader to the Feb 2018 C1:14 bootloader. Please do not downgrade your device's stock firmware to older stock versions if you can avoid this - or if you do downgrade, in general do not use OTA updates. This warning also includes attempting to downgrade to the Dec 2017 firmware to use the Oreo soak test OTA - do not use the Oreo soak OTA if you have downgraded from the Feb 2018 stock bootloader. Downgrading your stock firmware is not usually the issue, but doing so leaves your device with a newer bootloader but older system (.e.g Feb 2018 bootloader, Dec 2017 system firmware). This downgrade mismatch between the bootloader and system is what can lead to hard bricks, particularly if the OTA-supplied bootloader and your device's bootloader are substantially different (eg. the OTA attempts to flash a much older bootloader or a different bootloader over your newer bootloader - OTA updates do not appear to verify your bootloader version, they just assume your bootloader is the same version as your system firmware). The blankflashes we have do not appear to rescue devices bricked with previously flashed with the newest bootloaders, so be careful if you do downgrade your stock firmware. If you see yourself downgrading in the future, you may wish to wait for the TWRP flashables, which do not usually affect your bootloader version. Only full stock ROMs and stock OTA updates care about the bootloader version.
1d)After flashing the Feb 2018 firmware, your device should be booting. However, if you encounter any instabilities, you may have to factory reset your device. Depending on how different the TWRP flashable of the Dec 2017 firmware you have is and the stock firmware, you may not see any instability, but that's why the TWRP backup before you flashed the stock firmware is there, in case you have to erase your data.
1e)Then, you should be able to sideload the Oreo OTA or if you're somewhere where the OTA has been deployed, you should see a notification to download. It seems that the OTA will take some time to install and appears to stall at certain points, so you may wish to allow plenty of time for the flash. Also, ensure your device is powered or has plenty of battery whilst the flash is proceeding. Also, I think we do not currently have a fastboot Oreo stock ROM, so if you choose to root or modify your device after flashing Oreo, ensure you have a backup.
2)You could wait for the TWRP flashable if that's easier - as I mentioned above, you would not have to worry about your bootloader version since TWRP flashables don't affect the bootloader (though I recall some ROMs have a bootloader requirement) and may allow you to keep TWRP on your device. Hopefully there's an Oreo TWRP flashable coming along.

Another alternative to what echo92 posted is to upgrade to 7.1.1 December security patch, apply the 4 soak tests and then the final OTA.

[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

Motorola One Vision July update

Good news, motorola anounced the July update for the Motorola One Vision in his blog.
https://support.motorola.com/rola/e...family/motorola-one-vision/documents/MS141417
This update includes the july 1 security update
I don't know the delay but today in August 1 the update is available

I got my device in May and already recieved the June update, so it's not the first for me.
But I believe one vision was released later (June) for some regions.

luisjoseb said:
Good news, motorola publishied the first update for the Motorola One Vision in his blog.
https://support.motorola.com/rola/e...family/motorola-one-vision/documents/MS141417
This update includes the july 1 security update
I will update the post when this come to the device!!!
Click to expand...
Click to collapse
Do you know if this update solve the bootloop caused by enable fingerprint along with developer option ?

AndresOrue said:
Do you know if this update solve the bootloop caused by enable fingerprint along with developer option ?
Click to expand...
Click to collapse
Awaiting the update. But I don't think what you have described is the actual issue. I have fingerprint and developer options enabled and the device works just fine.
From what I have read, the issue is fingerprint + changing the default USB configuration. Isn't it?

baunthiyal said:
Awaiting the update. But I don't think what you have described is the actual issue. I have fingerprint and developer options enabled and the device works just fine.
From what I have read, the issue is fingerprint + changing the default USB configuration. Isn't it?
Click to expand...
Click to collapse
I changed that setting the first time and the phone enter in a bootloop and because I had to reset everything, I didn't try again . In this moment, I have developer option enable and the fingerprint disable.

AndresOrue said:
I changed that setting the first time and the phone enter in a bootloop and because i had to reset everything, I didn't try again . In this moment i have developer option enable and the fingerprint disable.
Click to expand...
Click to collapse
Here's my journey with Vision as of now -
1. Got this phone last week
2. Added fingerprints
3. Updated to PSA29.137-17
4. Enabled developer options
5. Changed all animation rates in developer options to 0.5
I'm not sure you should try steps 1-4. But personally, I didn't have the issue you have described.

baunthiyal said:
Here's my journey with Vision as of now -
1. Got this phone last week
2. Added fingerprints
3. Updated to PSA29.137-17
4. Enabled developer options
5. Changed all animation rates in developer options to 0.5
I'm not sure you should try steps 1-4. But personally, I didn't have the issue you have described.
Click to expand...
Click to collapse
Thanks mate. I enabled fingerprint and developer option and it works. Seems that the problem was what You said, enable fingerprint and changing the default USB configuration.

i just installed this update and after i checked the app for new android update it told me:
integrity system corrupted
You will not be able to get any future updates.
Go to the store and official rom will be installed
Something like this .. Do you see this aswell?

I have bought my one vision the day it became available in my country, June 3rd, I have April's security patch and nothing to update, is there any other security patch available?

ᕙ(⇀‸↼)ᕗ said:
i just installed this update and after i checked the app for new android update it told me:
integrity system corrupted
You will not be able to get any future updates.
Go to the store and official rom will be installed
Something like this .. Do you see this aswell?
Click to expand...
Click to collapse
This is normal with bootloader unlocked.
View attachment 4793287

xt1970-3 touch not working
i got a xt1970-3 from customer and touch is not working, i tried to flash with fastboot " XT1970-3_KANE_RETEU_9.0_PSA29.137-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" the same version in phone, i flashed logo.bin, boot.img, system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2, system.img_sparsechunk.2, system.img_sparsechunk.3, system.img_sparsechunk.4, system.img_sparsechunk.5, system.img_sparsechunk.6, system.img_sparsechunk.7, system.img_sparsechunk.8, system.img_sparsechunk.9, system.img_sparsechunk.10, system_other.img_sparsechunk.0, system_other.img_sparsechunk.1, system_other.img_sparsechunk.2,
and now phone in bootloop mode, please i want to known how to flash this again

rizni said:
i got a xt1970-3 from customer and touch is not working, i tried to flash with fastboot " XT1970-3_KANE_RETEU_9.0_PSA29.137-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" the same version in phone, i flashed logo.bin, boot.img, system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2, system.img_sparsechunk.2, system.img_sparsechunk.3, system.img_sparsechunk.4, system.img_sparsechunk.5, system.img_sparsechunk.6, system.img_sparsechunk.7, system.img_sparsechunk.8, system.img_sparsechunk.9, system.img_sparsechunk.10, system_other.img_sparsechunk.0, system_other.img_sparsechunk.1, system_other.img_sparsechunk.2,
and now phone in bootloop mode, please i want to known how to flash this again
Click to expand...
Click to collapse
This is how I flash full firmware without wiping userdata.
Code:
fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.nbl1.bin
fastboot flash ldfw_a ldfw.bin
fastboot flash ldfw_b ldfw.bin
fastboot flash keystorage_a keystorage.bin
fastboot flash keystorage_b keystorage.bin
fastboot flash bootloader_a bootloader.bin
fastboot flash bootloader_b bootloader.bin
fastboot flash modem_a modem.bin
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.10
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot fastboot flash vendor_a vendor.img
If you want to wipe userdata you could just add "fastboot erase userdata" at the end.
If that won't work it's probably broken digitizer or something.

thank you for quick guide, the phone is on now but the touch not working, it must be something to do with hardware
thank you

luisjoseb said:
Good news, motorola anounced the July update for the Motorola One Vision in his blog.
https://support.motorola.com/rola/e...family/motorola-one-vision/documents/MS141417
This update includes the july 1 security update
I don't know the delay but today in August 1 the update is available
Click to expand...
Click to collapse
I got the update yesterday

wtf
tys0n said:
This is normal with bootloader unlocked.
View attachment 4793287
Click to expand...
Click to collapse
I just noticed that new update is out.. so I tried click to update and woala it works.
OEM unlocked..
So with bootloader unlocked you are still able to get updates..

ᕙ(⇀‸↼)ᕗ said:
I just noticed that new update is out.. so I tried click to update and woala it works.
OEM unlocked..
So with bootloader unlocked you are still able to get updates..
Click to expand...
Click to collapse
There is no update for me
And Google Duo not work

ed.shevsky said:
There is no update for me
And Google Duo not work
Click to expand...
Click to collapse
i dont use duo, but i tried to root it and failed.. so i flashed stock boot.img
then tried to update
Maybe that flashed boot.img helped it or IDK.
you can try it- find your firmware
download it - extract it- find boot.img- place it in your home folder
use fastboot (instal adb tools and drivers ) with command (fastboot flash boot boot.img)
your phone must be in download mode - (power off, then press power and volume down button)
Is it avaible for your country?

ᕙ(⇀‸↼)ᕗ said:
i dont use duo, but i tried to root it and failed.. so i flashed stock boot.img
then tried to update
Maybe that flashed boot.img helped it or IDK.
you can try it- find your firmware
download it - extract it- find boot.img- place it in your home folder
use fastboot (instal adb tools and drivers ) with command (fastboot flash boot boot.img)
your phone must be in download mode - (power off, then press power and volume down button)
Is it avaible for your country?
Click to expand...
Click to collapse
Sorry, my fault. My phone is locked, so I don't need to flash boot.img
May be you know a method to force OTA update?
And about Google Duo. The program stop working after Play Market version updated. Once I fix it by factory reset. But I don't want do it every time

ᕙ(⇀‸↼)ᕗ said:
I just noticed that new update is out.. so I tried click to update and woala it works.
OEM unlocked..
So with bootloader unlocked you are still able to get updates..
Click to expand...
Click to collapse
Ok nice. Still didn't work for me but I'm flashing it with fastboot now instead.

ᕙ(⇀‸↼)ᕗ said:
i dont use duo, but i tried to root it and failed.. so i flashed stock boot.img
then tried to update
Maybe that flashed boot.img helped it or IDK.
you can try it- find your firmware
download it - extract it- find boot.img- place it in your home folder
use fastboot (instal adb tools and drivers ) with command (fastboot flash boot boot.img)
your phone must be in download mode - (power off, then press power and volume down button)
Is it avaible for your country?
Click to expand...
Click to collapse
Did you also get error about "too many links" when trying to flash magisk patched boot?