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.

Teclast M40 Disable dm-verity

I'd like to share the method I find to disable dm-verity. The method has been discussed on Hovatek, but I find it could be done even easier.
1. Make a blank but signed vbmeta image
Code:
avbtool make_vbmeta_image --key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096 --flags 0 --padding_size 20480 --output vbmeta.img
2. Reboot into fastbootd (userspace fastboot)
Code:
adb reboot fastboot
3. Flash vbmeta image
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Done!

AnKHqz said:
I'd like to share the method I find to disable dm-verity. The method has been discussed on Hovatek, but I find it could be done even easier.
1. Make a blank but signed vbmeta image
Code:
avbtool make_vbmeta_image --key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096 --flags 0 --padding_size 20480 --output vbmeta.img
2. Reboot into fastbootd (userspace fastboot)
Code:
adb reboot fastboot
3. Flash vbmeta image
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Done!
Click to expand...
Click to collapse
Have you unlocked the bootloader? Which vbmeta_sign.img file did you use?

AllexBast said:
Have you unlocked the bootloader? Which vbmeta_sign.img file did you use?
Click to expand...
Click to collapse
Yes, of course. The vbmeta.img I used is generated by the following command, and the key I used to sign the image is the same as that one I used to unlock the bootloader. I am not sure if signing the image is needed and whether signing the image with different key works or not.
Code:
avbtool make_vbmeta_image --key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096 --flags 0 --padding_size 20480 --output vbmeta.img

AnKHqz said:
I'd like to share the method I find to disable dm-verity. The method has been discussed on Hovatek, but I find it could be done even easier.
1. Make a blank but signed vbmeta image
Code:
avbtool make_vbmeta_image --key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096 --flags 0 --padding_size 20480 --output vbmeta.img
2. Reboot into fastbootd (userspace fastboot)
Code:
adb reboot fastboot
3. Flash vbmeta image
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Done!
Click to expand...
Click to collapse
nice im gonna try this on my tablet

AnKHqz said:
Yes, of course. The vbmeta.img I used is generated by the following command, and the key I used to sign the image is the same as that one I used to unlock the bootloader. I am not sure if signing the image is needed and whether signing the image with different key works or not.
Code:
avbtool make_vbmeta_image --key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096 --flags 0 --padding_size 20480 --output vbmeta.img
Click to expand...
Click to collapse
does this vbmeta zero work for android 11? Or is it only working for android 10?

blaze2051 said:
does this vbmeta zero work for android 11? Or is it only working for android 10?
Click to expand...
Click to collapse
I haven't succeeded in getting A11 to boot on Teclast M40 yet, so I can't give you the answer. Does Tectlast M40 support A11 now?

AnKHqz said:
I haven't succeeded in getting A11 to boot on Teclast M40 yet, so I can't give you the answer. Does Tectlast M40 support A11 now?
Click to expand...
Click to collapse
I believe i read somewhere that zero vbmeta does not work on android 11. Only seems to work on android 10 and below or it just might be a unisoc or mediatek thing

blaze2051 said:
I believe i read somewhere that zero vbmeta does not work on android 11. Only seems to work on android 10 and below
Click to expand...
Click to collapse
I dont even understand why vbmeta needs to be tampered with to begin with.
According the Android Verified Boot documentation (se recommended bootflow), if the bootloader is in an unlocked state, the AVB should let the device boot even if it encounters signiture key verification errors during the boot process.

NightLord said:
I dont even understand why vbmeta needs to be tampered with to begin with.
According the Android Verified Boot documentation (se recommended bootflow), if the bootloader is in an unlocked state, the AVB should let the device boot even if it encounters signiture key verification errors during the boot process.
Click to expand...
Click to collapse
the vbmeta i think it has to do more with boot.img or recovery.img maybe even the super.img
sometimes on AB devices you have to flash vbmeta with command --disable-verity --disable-verification
in order to get getvar is-userspace = yes in order to flash system.img, at least it was in my case with the LG G8 and LG v60

Question Flashing TWRP doesn't work (Xiaomi Redmi 9t)

Hello,
After unlock his bootloader, I try to install TWRP recovery on my smartphone with :
Bash:
fastboot flash recovery twrp.img
Bash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
But he reboot always on the fastboot mode when I push simultaneously on power and volume + and when I don't push on any button.
I use these file :
twrp.img
vbmeta.img
Thanks for your help .

TWRP by brigudav- i flashed only twrp renamed to recovery.img and patched os via that stock recovery will not back.

Rename the file change nothing to me.
As information, when I try in try
Bash:
fastboot boot recovery.img
i get :
Bash:
FAILED (remote: unknown command)
in fastboot
and
Bash:
FAILED (remote: Unrecognized command boot)
in fastbootd
I've test lineage recovery and that's the same : impossible to boot on other recovery except the stock MI-Recovery 3.0 .

I get the exactly same errorwhile try booting twrp.img is there no custom recovery for lime that works?

GrandTouque said:
Hello,
After unlock his bootloader, I try to install TWRP recovery on my smartphone with :
Bash:
fastboot flash recovery twrp.img
Bash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
But he reboot always on the fastboot mode when I push simultaneously on power and volume + and when I don't push on any button.
I use these file :
twrp.img
vbmeta.img
Thanks for your help .
Click to expand...
Click to collapse
The twrp image is just for another device, for davinci and not for lime. But i got the same problem with correct twrp image

ex-it said:
The twrp image is just for another device, for davinci and not for lime. But i got the same problem with correct twrp image
Click to expand...
Click to collapse
You are right, I try to flash a unofficial TWRP that I found at this thread and now I've just a black screen when I boot on it but I can now boot on the OS with this "recovery".

Finally, I've found this one on this thread who works .

How To Guide Method to get Stock realme UI dialer and contact apk by changing firmware from India To philipines in Realme 8 Pro Device.

Disclaimer: I am not responsible for bricked devices, dead SD cards, etc!
Don't Lock your device bootloader.
1.) First of all you need
laptop,
Usb data cable,
Minimal adb & fastboot setup,
firmware.
MCT ofp extractor tool.
and Your device.
Download below files.
Firmware link:
https://rms01.realme.net/sw/RMX3081export_11_C.19_2022072820470000.zip
MCT OFP extractor tool:
https://drive.google.com/file/d/1-MgGdT9fxi2LtJ1DIOxLVSM67thj9EpG/view?usp=drivesdk
Minimal adb & fastboot setup:
https://ava4.androidfilehost.com/dl/OqBAMk5-7QCuTzL-IhX9ZA/1661345244/10763459528675595887/ADB+&+FASTBOOT.rar
2.) Extract the ofp file package by mct ofp extract tool.
3.) Request to unlock your device bootloader by in-deapth test apk, once approved then you can start deep testing and unlock bootloader.
4.) connect your device with laptop.
5.) Open minimal adb & fastboot terminal.
and flash this images files by below cmd.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash metadata metadata.img
fastboot flash opporeserve2 opporeserve2.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
Note: Flash this only 3 super images
fastboot flash super super.0.c5548a43.img
fastboot flash super super.1.bbada0de.img
fastboot flash super super.2.1400563f.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta vbmeta.img
fastboot flash userdata userdata.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
fastboot reboot
Your device will reboot to system.