Not responsible to any device bricked if not followed instructions well
I tried wiping user data and flashing userdata.img to complete wipe ,what worked for me
If you need your phones internal storage dont wipe data and I dont know whether it is going to work or not as I did not tried it .
#Note wiping userdata will delete all internal 64 GB of data will with all apps
#using the commands as it is in this post will wipe user data so think and perform executing commands
In order to install magisk 14.6 on OREO on MI A1
Prerequisite
1) previous stock ROM with all image files http://en.miui.com/download-333.html http://en.miui.com/download-333.html
1A)Replace oero Update stock fastboot images (boot,system,userdata) with Nougat rom (oero stock rom files: https://forum.xda-developers.com/mi-...-2017-t3722184)
2) fastboot and adb files https://forum.xda-developers.com/sho....php?t=2588979
3) Basics of cmd and android fastboot,twrp flashing
Note: Follow the steps very well ,else phone might work efficiently
Lets it start
Steps:
1) Boot into fastboot (Volume down + Power)
2)complete flash all files/images wiping user data(experimental: skip the last 2 userdata commands to save your data,this do not guarantee stability of OREO )
You can use these commands if dont know how to
Code:
fastboot getvar product 2>&1 | findstr /r /c:"^product: *tissot" || [user=279333]@ECHO[/user] "error : Missmatching image and device" & exit /B 1
fastboot oem unlock
fastboot erase modem_a
fastboot flash modem_a modem.img
fastboot erase modem_b
fastboot flash modem_b modem.img
fastboot erase sbl1
fastboot flash sbl1 sbl1.img
fastboot erase sbl1bak
fastboot flash sbl1bak sbl1.img
fastboot erase rpm
fastboot flash rpm rpm.img
fastboot erase rpmbak
fastboot flash rpmbak rpm.img
fastboot erase tz
fastboot flash tz tz.img
fastboot erase tzbak
fastboot flash tzbak tz.img
fastboot erase devcfg
fastboot flash devcfg devcfg.img
fastboot erase devcfgbak
fastboot flash devcfgbak devcfg.img
fastboot erase dsp
fastboot flash dsp adspso.bin
fastboot erase sec
fastboot flash sec sec.dat
fastboot erase splash
fastboot flash splash splash.img
fastboot erase aboot
fastboot flash aboot emmc_appsboot.mbn
fastboot erase abootbak
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase lksecapp
fastboot flash lksecapp lksecapp.img
fastboot erase lksecappbak
fastboot flash lksecappbak lksecapp.img
fastboot erase cmnlib
fastboot flash cmnlib cmnlib.img
fastboot erase cmnlibbak
fastboot flash cmnlibbak cmnlib.img
fastboot erase cmnlib64
fastboot flash cmnlib64 cmnlib64.img
fastboot erase cmnlib64bak
fastboot flash cmnlib64bak cmnlib64.img
fastboot erase keymaster
fastboot flash keymaster keymaster.img
fastboot erase keymasterbak
fastboot flash keymasterbak keymaster.img
fastboot erase boot_a
fastboot flash boot_a boot.img
fastboot erase boot_b
fastboot flash boot_b boot.img
fastboot erase system_a
fastboot flash system_a system.img
fastboot erase system_b
fastboot flash system_b system.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot reboot
3)reboot into system once setup device (required to initialize system)
4)reboot fastboot (power off and hold volume down +power button)
5)boot twrp 3.1.1 (file size: 30,932 kb) https://androidfilehost.com/?fid=745849072291685548
command:
fastboot boot recovery-3.1.1-1.img
6)install twrp-installer-tissot.zip (file size :7,892kb) https://androidfilehost.com/?fid=673791459329053463
#if sd card isn't showing then sideload twrp-installer-tissot.zip
command:
adb sideload twrp-installer-tissot.zip
7)reboot recovery (dont boot into system this may cause wifi,camera broken,laggy)
8)flash Magisk-v14.6(1468).zip https://forum.xda-developers.com/att...6&d=1513897917 with twrp ,or you can sideload
like Command:
adb sideload Magisk-v14.6(1468).zip
9)reboot system
#if device wont start(boot up) after 40 - 60 seconds the hold power for restart
10)device will reboot and magisk 14.6 will be installed with oreo
I'm guessing you won't be able to get OTA update afterwards.
silv3rfox said:
I'm guessing you won't be able to get OTA update afterwards.
Click to expand...
Click to collapse
Root is combined with boot image so if you flash system image again then root or magisk wont disappear it will be there
So long story short updates will downloaded and installed in other partition to go in other partition change partition from twrp
Rushikesh googlelar said:
Root is combined with boot image so if you flash system image again then root or magisk wont disappear it will be there
So long story short updates will downloaded and installed in other partition to go in other partition change partition from twrp
Click to expand...
Click to collapse
Long story short, as soon as you install TWRP and Magisk, OTA will fail and you can't install it.
Related
I have a bootloader unlocked Google Pixel. On my computer I have Fastboot and ADB
I wanted to flash the Android 8.0 factory images from here:
https://developers.google.com/android/images#sailfish
I downloaded and extracted the zip, booted into download mode, and ran the flash-all.bat
When I do that it goes for a short while then terminates with the following:
error: failed to load 'image-sailfish-opr6.170623.012.zip': Not enough space
I have gone into TWRP and wiped everything as well as formatted but it hasn't let me run the factory image due to space.
What can I do?
EDIT: My problem was solved by mannunikhil:
mannunikhil said:
Try these step by step, this is manual flashing
Since you have already run flash-all.bat, bootloader and radio img had been already flash or you can flash them again if feel so.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Extract the zip "image-sailfish-opr6.170623.012.zip " to adb/fastboot location
Then to fix slot_b:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
Then erase/format system_b..
Fastboot erase system_b
And erase/format userdata ...
Fastboot erase userdata
Then proceed to fix slot_a
fastboot flash aboot aboot.img
fastboot flash apdp apdp.img
fastboot flash boot boot.img
fastboot flash bootlocker bootlocker.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash hosd hosd.img
fastboot flash hyp hyp.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash pmic pmic.img
fastboot flash rpm rpm.img
fastboot flash tz tz.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Finally, "fastboot reboot".
Click to expand...
Click to collapse
Tate Adams said:
I have a bootloader unlocked Google Pixel. On my computer I have Fastboot and ADB
I wanted to flash the Android 8.0 factory images from here:
https://developers.google.com/android/images#sailfish
I downloaded and extracted the zip, booted into download mode, and ran the flash-all.bat
When I do that it goes for a short while then terminates with the following:
error: failed to load 'image-sailfish-opr6.170623.012.zip': Not enough space
I have gone into TWRP and wiped everything as well as formatted but it hasn't let me run the factory image due to space.
What can I do?
Click to expand...
Click to collapse
there are couple of things that I can think of as of now,
1 ) Take backup of internal storage and run flash-all.bat as original (do not remove -w from the batch file),
2) Update Android SDK / Google USB Drivers with latest version and flash it again.
Sadly updating those didn't help. Everytime I try to install factory image it says it cannot allocate about 4 time the amount it says my max is. Any way to clear data from TWRP? I was quick to clear data so I have no backup to go back to. I'll take anyone's suggestions but I've lost hope.
Tate Adams said:
Sadly updating those didn't help. Everytime I try to install factory image it says it cannot allocate about 4 time the amount it says my max is. Any way to clear data from TWRP? I was quick to clear data so I have no backup to go back to. I'll take anyone's suggestions but I've lost hope.
Click to expand...
Click to collapse
suggest you to check the disk space where your windows temp directory set to.
during flashing it needs to unzip image-sailfish-opr6.170623.012.zip to temp folder
Tate Adams said:
Sadly updating those didn't help. Everytime I try to install factory image it says it cannot allocate about 4 time the amount it says my max is. Any way to clear data from TWRP? I was quick to clear data so I have no backup to go back to. I'll take anyone's suggestions but I've lost hope.
Click to expand...
Click to collapse
Try these step by step, this is manual flashing
Since you have already run flash-all.bat, bootloader and radio img had been already flash or you can flash them again if feel so.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Extract the zip "image-sailfish-opr6.170623.012.zip " to adb/fastboot location
Then to fix slot_b:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
Then erase/format system_b..
Fastboot erase system_b
And erase/format userdata ...
Fastboot erase userdata
Then proceed to fix slot_a
fastboot flash aboot aboot.img
fastboot flash apdp apdp.img
fastboot flash boot boot.img
fastboot flash bootlocker bootlocker.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash hosd hosd.img
fastboot flash hyp hyp.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash pmic pmic.img
fastboot flash rpm rpm.img
fastboot flash tz tz.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Finally, "fastboot reboot".
mannunikhil said:
Try these step by step, this is manual flashing
Since you have already run flash-all.bat, bootloader and radio img had been already flash or you can flash them again if feel so.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Extract the zip "image-sailfish-opr6.170623.012.zip " to adb/fastboot location
Then to fix slot_b:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
Then erase/format system_b..
Fastboot erase system_b
And erase/format userdata ...
Fastboot erase userdata
Then proceed to fix slot_a
fastboot flash aboot aboot.img
fastboot flash apdp apdp.img
fastboot flash boot boot.img
fastboot flash bootlocker bootlocker.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash hosd hosd.img
fastboot flash hyp hyp.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash pmic pmic.img
fastboot flash rpm rpm.img
fastboot flash tz tz.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Finally, "fastboot reboot".
Click to expand...
Click to collapse
Thank you mannunikhil! I wish I could extend a hug and a hand shake to you. Fixed it for me! Also thank you lonelytibetj even though I was unable to get that to work, I appreciate the reply. Love you all.
Tate Adams said:
Thank you mannunikhil! I wish I could extend a hug and a hand shake to you. Fixed it for me! Also thank you lonelytibetj even though I was unable to get that to work, I appreciate the reply. Love you all.
Click to expand...
Click to collapse
Glad it worked out for you. Cheers ?
mannunikhil said:
Try these step by step, this is manual flashing
Since you have already run flash-all.bat, bootloader and radio img had been already flash or you can flash them again if feel so.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Extract the zip "image-sailfish-opr6.170623.012.zip " to adb/fastboot location
Then to fix slot_b:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
Then erase/format system_b..
Fastboot erase system_b
And erase/format userdata ...
Fastboot erase userdata
Then proceed to fix slot_a
fastboot flash aboot aboot.img
fastboot flash apdp apdp.img
fastboot flash boot boot.img
fastboot flash bootlocker bootlocker.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash hosd hosd.img
fastboot flash hyp hyp.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash pmic pmic.img
fastboot flash rpm rpm.img
fastboot flash tz tz.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Finally, "fastboot reboot".
Click to expand...
Click to collapse
That's works. Thanks man ?
mannunikhil said:
Try these step by step, this is manual flashing
Since you have already run flash-all.bat, bootloader and radio img had been already flash or you can flash them again if feel so.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Extract the zip "image-sailfish-opr6.170623.012.zip " to adb/fastboot location
Then to fix slot_b:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
Then erase/format system_b..
Fastboot erase system_b
And erase/format userdata ...
Fastboot erase userdata
Then proceed to fix slot_a
fastboot flash aboot aboot.img
fastboot flash apdp apdp.img
fastboot flash boot boot.img
fastboot flash bootlocker bootlocker.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash hosd hosd.img
fastboot flash hyp hyp.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash pmic pmic.img
fastboot flash rpm rpm.img
fastboot flash tz tz.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Finally, "fastboot reboot".
Click to expand...
Click to collapse
when i flash aboot.img it shows target reported max downloaded size of 53670912 bytes error: cannot load aboot.img:ni error how can i solve it
updating google pixel
when i use adb it says:
archive does not contain boot.sig
archive does not contain recovery.img
package missing system.img
Dont know what to do im out of date just like my phone thanks ...
phoe zay said:
when i flash aboot.img it shows target reported max downloaded size of 53670912 bytes error: cannot load aboot.img:ni error how can i solve it
Click to expand...
Click to collapse
By at this stage I assume you have already enabled OEM unlocking and bootloader is unlocked. Now, 1st I would like you to use USB 2.0 port on your computer to follow the entire procedure and not USB 3.0 port.
If this doesnt help, update your adb drivers and re-download the image file and try.
thisnish87 said:
when i use adb it says:
archive does not contain boot.sig
archive does not contain recovery.img
package missing system.img
Dont know what to do im out of date just like my phone thanks ...
Click to expand...
Click to collapse
You need to extract all the files from all the zips in one location and then follow the procedure.
Hi. I am in a similar boat, but for android 9.0 Pie. Would you be able to post instructions for manually flashing stock on my Pixel 3XL? I would really appreciate it if you knew and wouldn't mind sharing. Thanks!
mannunikhil said:
Try these step by step, this is manual flashing
Since you have already run flash-all.bat, bootloader and radio img had been already flash or you can flash them again if feel so.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Extract the zip "image-sailfish-opr6.170623.012.zip " to adb/fastboot location
Then to fix slot_b:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
Then erase/format system_b..
Fastboot erase system_b
And erase/format userdata ...
Fastboot erase userdata
Then proceed to fix slot_a
fastboot flash aboot aboot.img
fastboot flash apdp apdp.img
fastboot flash boot boot.img
fastboot flash bootlocker bootlocker.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash hosd hosd.img
fastboot flash hyp hyp.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash pmic pmic.img
fastboot flash rpm rpm.img
fastboot flash tz tz.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Finally, "fastboot reboot".
Click to expand...
Click to collapse
sahilmp3 said:
Hi. I am in a similar boat, but for android 9.0 Pie. Would you be able to post instructions for manually flashing stock on my Pixel 3XL? I would really appreciate it if you knew and wouldn't mind sharing. Thanks!
Click to expand...
Click to collapse
Follow the instructions here:
https://developers.google.com/android/images
TYSM!!!!!!! luv u
mannunikhil said:
Try these step by step, this is manual flashing
Since you have already run flash-all.bat, bootloader and radio img had been already flash or you can flash them again if feel so.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Extract the zip "image-sailfish-opr6.170623.012.zip " to adb/fastboot location
Then to fix slot_b:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
Then erase/format system_b..
Fastboot erase system_b
And erase/format userdata ...
Fastboot erase userdata
Then proceed to fix slot_a
fastboot flash aboot aboot.img
fastboot flash apdp apdp.img
fastboot flash boot boot.img
fastboot flash bootlocker bootlocker.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash hosd hosd.img
fastboot flash hyp hyp.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash pmic pmic.img
fastboot flash rpm rpm.img
fastboot flash tz tz.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Finally, "fastboot reboot".
Click to expand...
Click to collapse
How would I remove the fastboot reboot at the end if I run the flash-all.sh. Tried using vim to just remove it, but I don't see that command. Where is it being executed? In the "image-sailfish-opr6.170623.012.zip"? If so where in the zip
Thank you
Hi guys
I have pixel 1 and I was on android 10
I had some problems so I decided to downgrade
I downloaded Android 7.1 recovery sailfish
Extracted the zip file
And flashall.bat
Bootloader and radio were ok
But when it comes to zip file
It gives me a massage
That zip file is too big and dosent goes
Then boots to Google logo and loop
I tried another sailfish recovery and another
The same problem
I the way by extracting zip file and flash every single img file
Every thing goes okey
But when I reboot it loops again
In fastboot mode it shows that bootloader sector is _b
Is that correct and what is the difference between sector a and sector b
Hello just got a pixel to try out so I can compare the experience when I get the pixel 2. But I am on android oreo/8 how would I go about downgrading to 7.1.2 so I can throw a custom rom on here?
And why do I see roms say marlin/sailfish?
Download the factory 7.1.2 image from Google. Flash that, then the custom 7.1.2 rom. Sailfish is the code name for the Pixel, and Marlin is the Pixel XL.
hi! i try to downgrade to sailfish-nmf26q 7.1.1 , in fastboot mode
fastboot flashing unlock
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
fastboot flashing lock
but only enter in recovery. (bootloop)
wazaone said:
hi! i try to downgrade to sailfish-nmf26q 7.1.1 , in fastboot mode
fastboot flashing unlock
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
fastboot flashing lock
but only enter in recovery. (bootloop)
Click to expand...
Click to collapse
Why are you trying to manually flash individual partitions and relocking the bootloader. Under almost no circumstances should you really be trying to do either of these things on the pixel series devices. Go to Google and look for factory images for your device. Download the proper 7.1.2 image for your device and extract it into your adb folder. From here you should edit the flash_all.bat to remove the -w if you would like to retain /media/. Then run the script while in fastboot and wait for it to finish. Note at a few points it will look like the script is hanging but it is not. For future reference locking this device with anything non-stock will trigger dm-verity and can result in hard bricking the device. If you don't have a good reason to be locking the bootloader and aren't on full stock DO NOT try to lock the device.
This is note to myself since I seem to forget what I did last month.
This guide assumes you are familiar with ADB and fastboot with a good working connection to the phone. YMMV. Continue at your own risk.
This also assumes you have a working Magisk (ver 18.1 or higher).
0) from essential.com, download the fastboot image zip. Unzip the content to a directory.
0) copy files flash_a.bat and flash_b.bat from below to the directory.
1) adb devices
2) adb reboot bootloader
3) fastboot devices
4) fastboot getvar current-slot (remember the current active slot)
5) flash_(the other slot).bat
6) fastboot reboot
6a) Once you are booted back in your current working slot, use Magisk to install a copy to the other slot. Once Magisk finishes installing, it will change the active slot to the other slot and reboot into that slot.
7a) Here is flash_a.bat
Code:
fastboot flash nvdef_a nvdef
fastboot flash boot_a boot
fastboot flash system_a system
fastboot flash bluetooth_a bluetooth
fastboot flash abl_a abl
fastboot flash dsp_a dsp
fastboot flash modem_a modem
fastboot flash vendor_a vendor
fastboot flash cmnlib_a cmnlib.mbn
fastboot flash cmnlib64_a cmnlib64.mbn
fastboot flash tz_a tz.mbn
fastboot flash devcfg_a devcfg
fastboot flash hyp_a hyp.mbn
fastboot flash keymaster_a keymaster
fastboot flash mdtp_a mdtp
fastboot flash mdtpsecapp_a mdtpsecapp
fastboot flash pmic_a pmic
fastboot flash rpm_a rpm.mbn
fastboot flash xbl_a xbl
fastboot reboot-bootloader
7b) Here is flash_b.bat
Code:
fastboot flash nvdef_b nvdef
fastboot flash boot_b boot
fastboot flash system_b system
fastboot flash bluetooth_b bluetooth
fastboot flash abl_b abl
fastboot flash dsp_b dsp
fastboot flash modem_b modem
fastboot flash vendor_b vendor
fastboot flash cmnlib_b cmnlib.mbn
fastboot flash cmnlib64_b cmnlib64.mbn
fastboot flash tz_b tz.mbn
fastboot flash devcfg_b devcfg
fastboot flash hyp_b hyp.mbn
fastboot flash keymaster_b keymaster
fastboot flash mdtp_b mdtp
fastboot flash mdtpsecapp_b mdtpsecapp
fastboot flash pmic_b pmic
fastboot flash rpm_b rpm.mbn
fastboot flash xbl_b xbl
fastboot reboot-bootloader
If something goes wrong, you can switch back the active partition to the original partition and recover.
From my experience, you do not have to use the full dump. The OTA package provided by the Essential website will do as well. Once you boot in twrp you can flash the OTA zip to the inactive slot and redo the rooting process.
aridmal said:
From my experience, you do not have to use the full dump. The OTA package provided by the Essential website will do as well. Once you boot in twrp you can flash the OTA zip to the inactive slot and redo the rooting process.
Click to expand...
Click to collapse
The provided .bat file only updates the files the are part of the monthly OTA package and not the full dump. The main benefit is the installing of pre-rooted boot image file so that one does not have redo the rooting and install TWRP afterwards.
github magisk easy, fast, works!
These are image files that are extracted from the payload of the android P OTA: https://drive.google.com/open?id=1gLRvB3A7uxbt5xgh9ntKiLfspzi1wcuK
Warning: You will erase all of your data
Code:
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash aboot_a aboot.img
fastboot flash aboot_b aboot.img
fastboot flash sbl1_a sbl1.img
fastboot flash sbl1_b sbl1.img
Run the code and then factory reset in recovery, and you will have android P.
Will you looae all data?
HoangP05 said:
These are image files that are extracted from the payload of the android P OTA: https://drive.google.com/open?id=1gLRvB3A7uxbt5xgh9ntKiLfspzi1wcuK
Warning: You will erase all of your data
Code:
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash aboot_a aboot.img
fastboot flash aboot_b aboot.img
fastboot flash sbl1_a sbl1.img
fastboot flash sbl1_b sbl1.img
Run the code and then factory reset in recovery, and you will have android P.
Click to expand...
Click to collapse
:good::good::good:
Thank you very much :good::good::good::good:
Oh my God thanks, easy, speed, nice, you are a the best
Thanks!
I created my XDA user (after 4 years using this forum) just to thank you. Feel special
Are these images from untouched Pie 10.0.1.0?
aryacebe said:
Are these images from untouched Pie 10.0.1.0?
Click to expand...
Click to collapse
Yes it is, but you can update directly to pie now I believe, and i saw people saying that the later version is better. You can still follow my instruction if you want!
HoangP05 said:
Yes it is, but you can update directly to pie now I believe, and i saw people saying that the later version is better. You can still follow my instruction if you want!
Click to expand...
Click to collapse
Not because I don't need the new version, but I need system.img and boot.img from my current android version (10.0.1.0), it is because my ota couldn't be installed, I think my system or boot is tampered when I rooted my phone :crying:
Wanna ask, is it safe if I only flash only boot and system? My A2 Lite already on 10.0.1.0 Pie
Only do:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
Will this take you back to stock, I have rooted Oreo and would like to go back to stock, are there any risks using this method, e.g. boot loop, etc... will it relock the boot.
I'm getting a Bootloop with this methode.
Question: By flashing this would my device be eligible to receive the stock OTA Android One release of Android 10 once it's released?
Thanks
ConsistentCarl said:
Question: By flashing this would my device be eligible to receive the stock OTA Android One release of Android 10 once it's released?
Click to expand...
Click to collapse
In theory the images here are stock, extracted from a full OTA (or Recovery) package.
Stock images won't hurt future OTAs (as long as they match the "current version" you're running)
Hi all, just received and updated the 11.1.6.6 via OTA... but after reboot I'm locked on the two white dots around the one red icons, and the phone doesn't start anymore.. so it's NOT a bootloop, but just blocked situation..
I'm rooted... what can I do to exit from this situation as well?
Just tried with VOL UP + POWER combo, but this casue only a power off, or a new reboot, but the situation doesn't change and the screen still stuck on the dots animation..
EDIT:
Had to resolve with a full wipe factory reset, no other way.
There was another way. You could've downloaded the latest update package onto your PC, used PayloadDumper to extract the payload.bin file found inside the zip file, extracted Android's 'Platform tools' into the output folder of the payload dump and then ran these commands without wiping while your phone is connected in fastboot:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash opproduct opproduct.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
You'd lose root but your phone would be updated to the latest OS and your data would hold.
You can then follow the root guide to patch the boot.img extracted from the payload file and let magisk do its thing.