Making complete Fastboot ROMs & Factory OTAs - by self for warranty/recovery... - Xiaomi Black Shark 2 Guides, News, & Discussion

Avoid and pass by a fool and a madman

---

Wow, great post and great work bro, this post is very informative indeed. I hope that you can finish you tool soon, I can help testing it if you need testers.

---

wga0 said:
Universal Image Extractor:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It seems that I succeeded in making the Universal Image Extractor. With the latest update engine, it works on any ota for any brand, any version, including the incremental also. But still, lots of work remained....
Complete Fastboot ROMs:
Now, you can build the complete Fastboot ROMs with some more info in your phone, even if your phone's manufacture never release it. To make it complete, you need to include the other roms which is not inside the ota(update.zip), and some more info such as partition type&align, because android has dynamic partitions and it can be changed between the different versions. If your roms were deleted and the partition info gone, you need it definitely.
Unfortunately, this(backup other roms not contained in the ota) requires root or rooted recovery. If you done root, backup all of your roms except userdata, all of the partition info, and keep it safe. If possible, make the fastboot rom yourself with those files/info. In black shark 2/pro cases, fortunately, the partition info is not changed upto now...
First, these code should come first to recover the partition info. It does re-partitioning and align including the two slots.
Code:
%fastboot_cmd% flash partition:0 gpt_both0.bin
%fastboot_cmd% flash partition:1 gpt_both1.bin
%fastboot_cmd% flash partition:2 gpt_both2.bin
....(all partitions)
In BS2/pro cases, it has align.bin info. It also should be flashed here to align the partition position
Second, the bootloader needed to be changed as the fastboot roms uses, and reboot into bootloader again. In cases that the bootloader has changed, extreme caution is required. If compatibility is not guaranteed, never try this (Fastboot ROMs). When doing this, flash only one bootloader to check the boot compatiblity, and after reboot successfully, flash the other slot.
Code:
%fastboot_cmd% flash abl_a abl.img
%fastboot_cmd% reboot-bootloader
timeout /t ....
In BS2/pro Android 10 cases, it's changed completely, you should never try this (Fastboot ROMs)
Third, re-setting and flash all the roms (including which is not inside the ota) are required to be fully recovered
Code:
%fastboot_cmd% oem simconfig set SS
%fastboot_cmd% flash avb_custom_key pkmd.bin
%fastboot_cmd% erase ddr
%fastboot_cmd% erase userdata
%fastboot_cmd% erase ....(all security key related)
%fastboot_cmd% flash roms...
More than Fastboot ROMs & Factory OTAs:
And now with the tool, it seems that I found a way to build a flashable update.zip, same as the factory OTA or Fastboot ROMs. It seems like it has both pros. It doesn't require rooting, unlocking bootloader, etc... Even if your phone's manufacturer never release the factory OTA, even if your phone never boot(bricked), you still could build and flash(update/rollback/recover) it without rooting & unlocking...
Here's the idea. (I found this inside the update_engine & OTA packaging sources)
With the universal image extractor, you can build any images and that images are stock(factory) images signed by the manufacturer. So, if I add(import) that ota packaging sources into the tool, I can build the factory OTA itself anytime with the tool. But unfortunately, although that factory OTA contains all signed, stock images & info, zip file itself isn't signed by the manufacturer and rejected by the system. (can't be flashed using 1027 code). Then... what if I can use it in bootloader or recovery? Stock recovery of BS has only one function, factory reset. Then fastboot?
It seems that I found a way to build an update.zip, same as the Factory OTA but can be used in bootloader, and a way to update(not flash) it in bootloader, bypassing the signature check of update.zip itself. So ideally, it doesn't require anything root or unlock, and can be updated and boot successfully through the locked bootloader because all of the images inside the zip are signed by manufacturer. Further, you don't need to push it into phone anymore. After entering bootloader, one command is enough. It's easier and powerful than both Fastboot and Factory OTA images. (not as powerful as complete Fastboot ROMs that contains all the roms which is not in OTAs...)
A bad things is..... this is just an possibility(idea) found inside the source codes currently.... and requires a lots of works in windows, like the universal image extractor.
Click to expand...
Click to collapse
Thank you for your thread. I'm going to study this!