Database Develop

[Untested][Linux/ Mac] Fastboot package for Oreo January update

Hi all,
this one is for the brave, as it is still untested.
Nevertheless, please find here some information what I did:
Got the latest full OTA package here from xda
Extracted payload.bin into the fastboot compatible .img files
Adapted the "flash_all_except_storage script" in order to automate the flashing and included it
As I have right now (just my luck) an issue with fastboot not detecting my phone, I cannot test right now. Will try again myself in the evening though, at least that is the plan.
In the meantime any brave (no guarantees, no warranties) are welcome to test it. Apart from the above mentioned changes, it is the update as it was distributed by Xiaomi/ Google including the January security patch:
Android 8.0.0 [OPR1.170623.026.8.1.10]
link removed as official version is now available here
I am looking forward to your feedback.
P.S.: For more information how to use it, please have a look here
UPDATE: system.img seems to be not flashable right now and I have no more ideas right now what I could do about it. So sorry guys, back to waiting for Xiaomi again.

downloading...
will report the result later.
EDIT: Sorry, I just saw that it only includes a "flash_all_except_storage.sh" for Linux/Mac.. Could I use the *.bat script from an official fastboot image on this one?

i dont have a Mac, windows 10. how do i flash it ?

soeschelz said:
downloading...
will report the result later.
EDIT: Sorry, I just saw that it only includes a "flash_all_except_storage.sh" for Linux/Mac.. Could I use the *.bat script from an official fastboot image on this one?
Click to expand...
Click to collapse
Rawwr said:
i dont have a Mac, windows 10. how do i flash it ?
Click to expand...
Click to collapse
@ all dear Windows users: The scripts from the official fastboot package require some slight changes, due to some different namings. So far I have done this only for Linux/ Mac and included the appropriate script, but you could still flash the *.img files via the following fastboot commands:
Code:
fastboot oem unlock
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash sbl1 sbl1.img
fastboot flash sbl1bak sbl1.img
fastboot flash rpm rpm.img
fastboot flash rpmbak rpm.img
fastboot flash tz tz.img
fastboot flash tzbak tz.img
fastboot flash devcfg devcfg.img
fastboot flash devcfgbak devcfg.img
fastboot flash dsp dsp.img
fastboot flash aboot aboot.img
fastboot flash abootbak aboot.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 lksecapp lksecapp.img
fastboot flash lksecappbak lksecapp.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlibbak cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cmnlib64bak cmnlib64.img
fastboot flash keymaster keymaster.img
fastboot flash keymasterbak keymaster.img
fastboot set_active a
fastboot reboot

majamee said:
@ all dear Windows users: The scripts from the official fastboot package require some slight changes, due to some different namings. So far I have done this only for Linux/ Mac and included the appropriate script, but you could still either flash the *.img files via the following fastboot commands:
Code:
fastboot oem unlock
fastboot flash modem_a modem.img
Click to expand...
Click to collapse
cant you make a script ? it is hard to enter every code at once

@majamee
I tried to flash manually but no luck. It seem all OK until I flash system.img.
After I enter
Code:
fastboot flash system_a system.img
I got the following error:
Code:
invalid sparse file format at header magi
then it flashes system_a. Same with system_b. All other commands run without any error. After a reboot I'm stuck on bootsplash.
I used fastboot and adb linked in the thread mentioned in first post and had no problem with flashing the first Oreo.
I hope you understand me, I'm very tired and not a native speaker

soeschelz said:
@majamee
I tried to flash manually but no luck. It seem all OK until I flash system.img.
After I enter
I got the following error:
then it flashes system_a. Same with system_b. All other commands run without any error. After a reboot I'm stuck on bootsplash.
I used fastboot and adb linked in the thread mentioned in first post and had no problem with flashing the first Oreo.
I hope you understand me, I'm very tired and not a native speaker
Click to expand...
Click to collapse
Thank you for your helpful feedback. I will see if I can do something about it, except waiting for xiaomi to finally release the fastboot image themselves or I get my ota without reading play services data.

Can you explain me how you extracted payload.bin to .img files

ramesh1686 said:
Can you explain me how you extracted payload.bin to .img files
Click to expand...
Click to collapse
I can tell you the basic instructions, but for the details I have to ask you to please have a look yourself how to do it for your Operating System.
So,
You download both python scripts from here: https://gist.github.com/ius/42bd02a5df2226633a342ab7a9c60f15
You make sure you have installed python and google-protobuf binding for python
You open a terminal/ shell/ cmd and navigate via the "cd" command to the directory the payload.bin and the both .py scripts are
run the following command "payload_dumper.py payload.bin"
I personally did these parts on a Linux system as it was at least for me the easiest way to have python and protobuf set up in no time.
----
Btw. I had another look, if I can do something about the system.img not being flashable at the moment. Nevertheless no luck so far, I begin to wonder if the OTA package is really a full OTA, due to that or just a very big update as it is intended to update Android N to O...
Sorry, for the failed attempt, at least it was worth a try.

I had issue with "invalid sparse file format at header magi" before (also extracted image from OTA), but it flashed successfully. Flashing just took longer than usual. However I had issues with failed video recording and the only fix for me was to use full flash of stock fastboot ROM. There might be something missing in extracted images from OTA package.

I have unpacked the latest payload.bin file from Android 8.0.0 [OPR1.170623.026.8.1.10] and the size of the system.img is 3.2 GB . This is too much?
The system partition has a size of 3072 MB. It's some error of unpacking?

Fastboot ROM is available http://bigota.d.miui.com/8.1.10/tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b.tgz
Source: http://en.miui.com/thread-1596182-1-1.html

Fastboot commands for flashing honor 9 lite

Please gve the fastboot command for Oreo for flashing
Boot.img
Recovery.img
System.img
...........................,.......,..........
These comments are not working
Fastboot flash boot
Fastboot flash recovery
Please help me

Curious8 said:
Please gve the fastboot command for Oreo for flashing
Boot.img
Recovery.img
System.img
...........................,.......,..........
These comments are not working
Fastboot flash boot
Fastboot flash recovery
Please help me
Click to expand...
Click to collapse
The fastboot commands you are executing are lacking the image file and have the incorrect partition target.
Code:
fastboot flash ramdisk "boot-image-filename.img"
fastboot flash recovery_ramdisk "recovery-image-filename.img"
fastboot flash system "system-image-filename.img"
fastboot flash vendor "vendor-image-filename.img"

@Curious8
If you will flash anything - it' a good idea you have FULL-Update from your Build on your PC !
Find FULL-Update with HuaweiFirmwareFinder and download.
Extract with HuaweiExtractor from Update.app (inside Update.zip) 3 img : ramdisk.img, recovery_ramdis.img, system.img
The Extractor do automatic 3 *.img.header. This 6 files copy to your ADB-Folder.
NOW you can flash any developer-rom. If this not work reset your phone to stock-rom with
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
this help for self-repair if
- bootloader unlocked
- FRP unlock
the commands you write is for Android older OREO ! With OREO we have new Partition-Names and new commands.

Need Odm And Product Image

Need clt-l29c432 odm.img product.img fle

Mi A2 stuck on TWRP Screen after phone reset.

Hello, I was using Mi A2 with TWRP and magisk installed with boot-loader unlocked. I was on Andriod Pie Oct 2019 updated. Today, i moved to Realme XT and reset the A2 from setting. Now my phone stuck on TWRP Logo Screen. I tried restarting so many time but it still comes back to same twrp screen.
I also try flashing recovery using mi flash method but still no success. It shows "Flash devcfg_a error"
One more thing, i want to add here is that before phone reset, Nov 2019 security update was failing to installed. I installed the TWRP after Oct 2019 update.
Please help me in resolving this issue. This is first time, i am using xda forums. If i failed to follow the procedure of creating thread, i apologized. Please guide me.

imubad said:
Hello, I was using Mi A2 with TWRP and magisk installed with boot-loader unlocked. I was on Andriod Pie Oct 2019 updated. Today, i moved to Realme XT and reset the A2 from setting. Now my phone stuck on TWRP Logo Screen. I tried restarting so many time but it still comes back to same twrp screen.
I also try flashing recovery using mi flash method but still no success. It shows "Flash devcfg_a error"
One more thing, i want to add here is that before phone reset, Nov 2019 security update was failing to installed. I installed the TWRP after Oct 2019 update.
Please help me in resolving this issue. This is first time, i am using xda forums. If i failed to follow the procedure of creating thread, i apologized. Please guide me.
Click to expand...
Click to collapse
Issue resolved. After following below guide that i find online outside of XDA.
Below are the Steps on How to manually Install Official Android Firmware on your Xiaomi Mi A2 via Fastboot -
1) Extract the Fastboot Firmware and Open Images folder where you'll find all the System, Boot, and other Image files.
2) Extract and paste the ADB and Fastboot files to the Fastboot Firmware Images folder, which you extracted in Step 1.
3) Open Fastboot via CMD and Paste all the below Commands -
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
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 xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash pmic_a pmic.img
fastboot flash pmic_b pmic.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 hyp_a hyp.img
fastboot flash hyp_b hyp.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 abl_a abl.elf
fastboot flash abl_b abl.elf
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 userdata userdata.img
fastboot flash splash splash.img
fastboot flash mdtpsecapp_a mdtpsecapp.img
fastboot flash mdtpsecapp_b mdtpsecapp.img
fastboot flash storsec storsec.mbn
fastboot reboot
4) Enjoy!

imubad said:
Issue resolved. After following below guide that i find online outside of XDA.
Below are the Steps on How to manually Install Official Android Firmware on your Xiaomi Mi A2 via Fastboot -
1) Extract the Fastboot Firmware and Open Images folder where you'll find all the System, Boot, and other Image files.
2) Extract and paste the ADB and Fastboot files to the Fastboot Firmware Images folder, which you extracted in Step 1.
3) Open Fastboot via CMD and Paste all the below Commands -
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
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 xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash pmic_a pmic.img
fastboot flash pmic_b pmic.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 hyp_a hyp.img
fastboot flash hyp_b hyp.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 abl_a abl.elf
fastboot flash abl_b abl.elf
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 userdata userdata.img
fastboot flash splash splash.img
fastboot flash mdtpsecapp_a mdtpsecapp.img
fastboot flash mdtpsecapp_b mdtpsecapp.img
fastboot flash storsec storsec.mbn
fastboot reboot
4) Enjoy!
Click to expand...
Click to collapse
Now, my phone is on 9 (pkq1.180904.001.v10.0.2.0.pdimifj) and Dec 5, 2018 patch. I am still having installation problem with March 2019 update.

imubad said:
Now, my phone is on 9 (pkq1.180904.001.v10.0.2.0.pdimifj) and Dec 5, 2018 patch. I am still having installation problem with March 2019 update.
Click to expand...
Click to collapse
Download November 2019 official fastboot image for stock ROM 10.0.17.0 and flash it in fastboot using "falsh_all_except_data.bat".
All necessary instructions are here in "Xiaomi Mi A2 Guides, News, & Discussion" forum, just try to search in xda instead of going outside.
E.G. link to official fastboot image 10.0.17.0 was first published in https://forum.xda-developers.com/mi-a2/how-to/november-2019-security-patch-available-t4002373 (what a surprise?), and then added to OP of https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849 storing links to previous existing official images (getting stranger and stranger, is not it?)

[GUIDE] Flashing the latest firmware updates to your OnePlus 6T

This guide exists next to [GUIDE] Extracting the latest firmwares from ROM update package and they supplement eachother.
General word about firmware updates:
A lot of people know of the importance and benefits of keeping your device firmware updated, just like you keep your custom ROM updated. If you don't keep them updated, you might not get the best out of your custom ROM (like: more bugs, system stability and performance problems/less speed.. also, vendor components, e.g Qualcomm and other chips, have security patches in the firmware.. "Vendor patch level" vs Android "Security patch level").
Besides incremental firmware updates from each OxygenOS release with a small changelog, too many people are missing out on huge jumps such as that they are running an Android 11 custom ROM, while their firmware was never updated so it remained a firmware originally shipped with an Android 10 (or earlier) OxygenOS release. Staying behind on huge jumps like these, causes the biggest list of problems with stability and performance. Therefore it is advisable to keep your firmware updated, and note that even small incremental updates (based on the same Android version) tend to give performance, security and stability benefits.
Prerequisites
For flashing the latest firmware, you need to have the firmware files (NOT the ROM update .zip file.. but a bunch of .img's) first. You can get them in multiple ways:
- Look for someone on XDA that has shared them, after they extracted the firmwares from the ROM update .zip file. This saves you time, but if you want to do it by yourself then first follow the "Extract firmwares" guide. An example of a reason for doing it yourself is: you want to be sure of the authencity, completeness and integrity of firmware files (that is everything but guaranteed if you DL it from another user)
- Do it yourself, as described above, and for this use the guide linked above
So after this stage, you have the firmware .img files, as required to proceed:
GUIDE STARTS BELOW THIS LINE
1) Get adb and fastboot from https://dl.google.com/android/repository/platform-tools-latest-windows.zip
2) Extract the above (adb and fastboot) to a folder named "FW update". We assume that's the location all of the extracted firmware (.img) files are, like they would be if you followed the "Extract firmwares" guide to get them
So, now that your adb and fastboot are in the same folder as all required firmware files, you can proceed.
3) Actual flashing instructions, a very simple process
Code:
1) Boot to Recovery
2) Enter Fastboot (e.g for LineageOS recovery: "Advanced" > "Enter Fastboot")
3) Connect phone to PC with USB cable
4) Open cmd (command prompt) in your adb / fastboot binaries location folder (in cmd, enter cd [location of your "FW update" folder.. or alternatively copy cmd.exe from system32 to "FW update" folder & open it there),
5) Start flashing..
Enter commands 1 by 1:
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all fw_4j1ed fw_4j1ed.img
fastboot flash --slot=all fw_4u1ea fw_4u1ea.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all LOGO LOGO.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all oem_stanvbk oem_stanvbk.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all vendor vendor.img
fastboot flash --slot=all xbl xbl.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot reboot
Done, now your phone will boot up with the updated firmwares.

What's the command to flash system IMG? Can I use this process to flash A11 update from A9 MSM tool?

Doesn't this give can't flash on critical partitions error? Or am I missing something?