• If you are experiencing issues logging in, we moved to a new and more secure software and older account passwords were not able to be migrated. We recommend trying to reset your password, then contacting us if there are issues.
  • Nearly done! Migration cleanup is mostly done. There are a small number of issues left that we continue to work on, but all the heavy lifting is done. We still would love to hear feedback over at this thread and also check out the new XDA app! Thanks and we hope you enjoy the new forums, and thanks for your support of XDA <3

[B][2018-09-08][ROM][OFFICIAL][7.1.2]MIUI Fastboot Flashable Zip Project[/B]

Is this project good enough? [Q4 & Q5, state your request in a post]

  • Needs a little improvement!

    Votes: 0 0.0%

  • Total voters
    8

Growtopia Jaw

Senior Member
Oct 29, 2016
126
63
0
17
Johor Bahru
www.growtopiajaw.phpn.ga


UPDATE! URGENT! IMPORTANT! PLEASE READ!​
PLEASE READ THIS ANNOUNCEMENT!!!


May I present to you, The Xiaomi Redmi 5A Fastboot Flashable Zip Project!


#include <std_disclaimer.h>

/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/

Introduction

At first, I only planned to release a Flashable Zip of the persist disk image. I had sensor problems so this was my main goal. I then started to think “Hmm.. why don’t I just bundle it all together since I already had ideas for this project anyway”. Voilà, this is how this project came to life!


Project's main aim

This project is mainly for those who want to return to stock MIUI firmware without flashing (MiFlash Tool) with PC (currently/ doesn't have a PC). Each and every one of the disk images provided with MIUI's Fastboot Firmware will be available here individually in a highly compressed Flashable Zip format.


REQUIREMENTS

  • TWRP (MANDATORY!)
  • Unlocked Bootloader (ALSO MANDATORY!)


Bugs

1. Unable to flash system-signed.zip and userdata-signed.zip [FIXED] *V9.5.10.0.NCKMIFA
2. Unable to flash boot-signed.zip and firmware-update.zip [FIXED] *V9.6.2.0.NCKMIFD


Features

  • Highly compressed disk images
    Example: system.img 3.0GB --> 0.9GB!


Installation

Just flash zip in TWRP!


Changelog

2018-09-08
2.1 Third Update
Based on latest MIUI V9.6.4.0.NCKMIFD Fastboot Firmware
- Fixed updater-script weird characters issue ("FX TextEdit" app problem)
- Brought back userdata-signed.zip with original fastboot firmware contents in it
- New zip signing method (Should work with TWRP "Verify Zip Signature")
- Fixed boot-signed.zip and firmware-update.zip ERROR: 6 issue
- Tested updater-script one by one (Should work now without ERROR: 6 issue)

Previous Changelogs:

2018-08-23
2.0 Second Update
Based on latest MIUI V9.6.2.0.NCKMIFD Fastboot Firmware
- Used some images from recovery firmware to reduce release time
- Switched system-signed.zip to set_metadata format
- Fixed major flaw in big flashable zips (Small tmpfs size, disk image not fully extracted and failed to flash)
- Removed tmpfs resize usage in big flashable zips
- Switched userdata-signed.zip to format partition only
- Combined adspso.bin, cmnlib64.mbn, cmnlib.mbn etc. to firmware-update-signed.zip

2018-08-03
1.0 Initial Release
Based on latest MIUI V9.5.10.0.NCKMIFA Fastboot Firmware

Download

1. V9.6.4.0.NCKMIFD
https://www.mediafire.com/folder/zpwzd4ld2f8n4/V9.6.4.0.NCKMIFD
2. V9.6.2.0.NCKMIFD
https://www.growtopiajaw.phpn.ga/project/romxiaomi-redmi-5a-fastboot-flashable-zip-project-v2/
3. V9.5.10.0.NCKMIFA
https://www.growtopiajaw.phpn.ga/project/romxiaomi-redmi-5a-fastboot-flashable-zip-project/

XDA:DevDB Information
[2018-09-08][ROM][OFFICIAL][7.1.2]MIUI Fastboot Flashable Zip Project, ROM for the Xiaomi Redmi 5A

Contributors
Growtopia Jaw, ezrawk
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x

Version Information
Status: Stable
Current Stable Version: 7.1.2
Stable Release Date: 2018-09-08

Created 2018-08-08
Last Updated 2018-11-15
 
Last edited:

Growtopia Jaw

Senior Member
Oct 29, 2016
126
63
0
17
Johor Bahru
www.growtopiajaw.phpn.ga
Flashable zip contents and it's usage

  • boot-signed.zip
    This zip contains MIUI's stock bootloader image. Flashing this will restore your boot partition to stock.

  • cache-signed.zip
    This zip contains MIUI's stock cache image. Flashing this will restore your cache partition to stock.
    *Cache partition is normally used to store temporary TWRP/ Android OS files.

  • cust-signed.zip
    This zip contains MIUI's stock vendor image. Flashing this will restore your vendor partition to stock.
    *This is actually the vendor partition for Xiaomi phones. It stores your phone's proprietary drivers for your phone's hardware like display drivers, Open GL, sound drivers and more..

  • firmware-update-signed.zip [v2 and above only]**
    This zip contains MIUI's stock adspso.bin, cmnlib64.mbn, cmnlib.mbn etc. images. Flashing this will restore the below mentioned image's partition to stock.
    *Images contained in this flashable zip:

    • adspso.bin
    • cmnlib64.mbn
    • cmnlib.mbn
    • devcfg.mbn
    • emmc_appsboot.mbn
    • keymaster.mbn
    • lksecapp.mbn
    • mdtp.img
    • NON-HLOS.bin
    • rpm.mbn
    • sbl1.mbn
    • splash.img
    • tz.mbn

    These images are originally distributed with MIUI's official recovery zip. I decided to include them here is because it is more easy to release for the project and it will save a lot of time preparing it for a release than manually converting each and every fastboot images to raw disk image format and then highly compressing it.

    These images will be available in each and every release of MIUI's recovery zip. All of the images in this zip are required to be flashed when you upgrade/ downgrade a release or it may introduce bugs like Wi-Fi not working in your MIUI ROM.

  • mdtp-signed.zip [v1 only]*
    This zip contains MIUI's stock mdtp image. Flashing this will restore your mdtp partition to stock.
    *According to @mirfatif's thread, this partition contains files for "boot verification and Qualcomm SafeSwitch technology to lock and track theft phones".

  • misc-signed.zip
    This zip contains MIUI's stock misc image. Flashing this will restore your misc partition to stock.
    *From my understanding from several sources, this partition contains CID (Carrier and Region ID), USB configuration settings and several hardware settings related files.

  • persist-signed.zip
    This zip contains MIUI's stock persist image. Flashing this will restore your persist partition to stock.
    *This particular partition is what most users have problem from. It contains sensor driver files. (If you have problems like proximity sensor/ rotate screen not working, this is the zip you need to flash).

  • recovery-signed.zip
    This zip contains MIUI's stock recovery image. Flashing this will restore your recovery partition to stock.
    *THIS IS NOT TWRP! THIS IS MIUI'S STOCK RECOVERY! FLASHING THIS WILL REMOVE YOUR TWRP!
    *Everyone using custom ROM should already/ must know this partition (Stop using custom ROM if you don't know what this partition is for! :silly:

  • splash-signed.zip [v1 only]*
    This zip contains MIUI's stock splash image. Flashing this will restore your splash partition to stock.
    *This partition contains an image file.. Yep, an image file.. But for what? Well, the screen you first see when you turn on your phone duh! (The MIUI logo) Not the bootanimation!

  • system-signed.zip
    This zip contains MIUI's stock system image. Flashing this will restore your system partition to stock.
    *Everyone should know this.. This is where the ROM's main files are located. Android OS's main partition like Android Nougat, Oreo, Pie etc.

  • userdata-signed.zip
    This zip contains MIUI's stock data image. Flashing this will restore your data partition to stock.
    *This is also a must know partition.. This is where most of your apps, images and games are stored. It is also where the OS's permanent cache a.k.a dalvik/ ART (Android Runtime) are stored.

*v1 only: It means that this flashable zip is only available in V9.5.10.0.NCKMIFA and it has been integrated into firmware-update-signed.zip in the next release and above.
**v2 and above only: It means that this flashable zip is only available in V9.6.2.0.NCKMIFD and above. It is not available in v1.
 
Last edited:
  • Like
Reactions: ezrawk

Growtopia Jaw

Senior Member
Oct 29, 2016
126
63
0
17
Johor Bahru
www.growtopiajaw.phpn.ga
ANNOUNCEMENT

Once again, project has been updated to MIUI V9.6.4.0.NCKMIFD! Other than that, there are flaws in the previous release (again). I tested each and every one of the zip before releasing. These zips should work this time (hopefully).

I will halt this project as my Microsoft Azure Free Subscription has expired (30 days). I rely on cloud virtual machine to get these things done. I don't have a PC at home and it will be very hard to release project updates without a PC. Currently I use my phone (Xiaomi Redmi 5A) for all of the work (even when writing this post). Every single release that I've released are possible because of Microsoft Azure. I can't do things without it.

To make up for my mistakes, I've added two things to this release:
1. Brought back userdata-signed.zip (Actual files in it)
2. New zip signing method (Should now work with TWRP's "Zip Signature Verification" Yay!)

I spent a two days preparing this (From yesterday and at about 1 a.m. in the morning to 9 a.m.) with both tired and sleepy mode...

I will be flashing this zips to prove that it's working (Will provide screenshots also!)

Well, that's all for now.

Thank you all for understanding!
 
Last edited:

Growtopia Jaw

Senior Member
Oct 29, 2016
126
63
0
17
Johor Bahru
www.growtopiajaw.phpn.ga
Eemmmm...
What's the different with official recovery firmware from bigota miui?
It's the same stock firmware, right?
Yes, you are right but.. Some of the disk images in official fastboot firmware are unavailable in official recovery firmware (Example: persist).. And some people may prefer to only download a single disk image. Some people also may have limited Internet quota and try to save every single MB if they can..

Another reason is that some disk image can't be written in MiFlash tool (Example: persist).. Some people will accidentally delete/ corrupt the partition and so far till now, I've found no article online about how to fix Xiaomi Redmi 5A persist partition/ sensors
 

Growtopia Jaw

Senior Member
Oct 29, 2016
126
63
0
17
Johor Bahru
www.growtopiajaw.phpn.ga
can i ask something? this is for minimalize the storage used? or what?
It's the same as official firmware (unmodified & clean) but it is highly compressed to save Internet quota especially for those who have limited Internet quota

Example: normal recovery firmware zip = 1 GB+

This project zip = many choices (you can download it individually)

system.img = 0.9 GB (normal is 3GB if uncompressed)
userdata.img = 0.2 GB (normal is 2.9 GB if uncompressed)
 
Last edited:

Azocke5531

Member
Jul 25, 2017
21
5
0
Yes, you are right but.. Some of the disk images in official fastboot firmware are unavailable in official recovery firmware (Example: persist).. And some people may prefer to only download a single disk image. Some people also may have limited Internet quota and try to save every single MB if they can..

Another reason is that some disk image can't be written in MiFlash tool (Example: persist).. Some people will accidentally delete/ corrupt the partition and so far till now, I've found no article online about how to fix Xiaomi Redmi 5A persist partition/ sensors
Ok, now I understand
About standalone bootloader zip, is that contain a locked or unlocked bootloader?
 

Growtopia Jaw

Senior Member
Oct 29, 2016
126
63
0
17
Johor Bahru
www.growtopiajaw.phpn.ga
Ok, now I understand
About standalone bootloader zip, is that contain a locked or unlocked bootloader?
This zip only contains boot image. Your question about "locked and unlocked bootloader" is totally unrelated to the boot image zip.

About locked/ unlocked bootloader, that is only changed (locked/ unlocked) in Mi Unlock Tool (which is the tool you used to unlock your phone in the first place). Only this tool, fastboot and manual terminal command input can change the unlock/ locked state.

Long story short, unlock/ lock bootloader is NOT the same with bootloader image (boot image). Boot image is just a partition. Unlock/ locked state is a state whether your phone's bootloader is unlocked or not.
 

r6680jc

Senior Member
Sep 6, 2009
390
63
28
Yogyakarta & Purbalingga
This zip only contains boot image. Your question about "locked and unlocked bootloader" is totally unrelated to the boot image zip.

About locked/ unlocked bootloader, that is only changed (locked/ unlocked) in Mi Unlock Tool (which is the tool you used to unlock your phone in the first place). Only this tool, fastboot and manual terminal command input can change the unlock/ locked state.

Long story short, unlock/ lock bootloader is NOT the same with bootloader image (boot image). Boot image is just a partition. Unlock/ locked state is a state whether your phone's bootloader is unlocked or not.
A little correction:
boot partition is kernel partition, boot.img is kernel image file.

bootloaders:
PBL (primary bootloader), SBL(secondary bootloader)/XBL(extesible bootloader), aboot/appsboot (OEM bootloader), abootbak (OEM bootloader backup?)

Unlocking bootloader usually done to aboot and abootbak, abootbak partition may contains excactly the same image as aboot partition.

--------------------------------------------------------------------

Could someone with unlocked BL Redmi 5A dump the aboot and abootbak partitions, and share them here please?
They're main "ingredients" to unlock BL instantly without permission, only needs to enter EDL mode.
(Going to figure out if Redmi 5A's SBL/XBL will accept officially unlocked aboot from another Redmi 5A or if it needs more works).
 

Growtopia Jaw

Senior Member
Oct 29, 2016
126
63
0
17
Johor Bahru
www.growtopiajaw.phpn.ga
A little correction:
boot partition is kernel partition, boot.img is kernel image file.

bootloaders:
PBL (primary bootloader), SBL(secondary bootloader)/XBL(extesible bootloader), aboot/appsboot (OEM bootloader), abootbak (OEM bootloader backup?)

Unlocking bootloader usually done to aboot and abootbak, abootbak partition may contains excactly the same image as aboot partition.

--------------------------------------------------------------------

Could someone with unlocked BL Redmi 5A dump the aboot and abootbak partitions, and share them here please?
They're main "ingredients" to unlock BL instantly without permission, only needs to enter EDL mode.
(Going to figure out if Redmi 5A's SBL/XBL will accept officially unlocked aboot from another Redmi 5A or if it needs more works).
Yep, that's pretty much a very detailed explanation. Totally forgotten about the word "kernel" :silly: was looking for that word actually :)

--------------------------------------------------------------------

Didn't see that coming.. You can't unlock your Redmi 5A officially? Update info please..
 

r6680jc

Senior Member
Sep 6, 2009
390
63
28
Yogyakarta & Purbalingga
Yep, that's pretty much a very detailed explanation. Totally forgotten about the word "kernel" :silly: was looking for that word actually :)

--------------------------------------------------------------------

Didn't see that coming.. You can't unlock your Redmi 5A officially? Update info please..
I'm still waiting halfway (about 180 hours).

Yours unlocked?
Would you dump the two bootloader partitions (aboot and abootbak) and upload them here?
 

Growtopia Jaw

Senior Member
Oct 29, 2016
126
63
0
17
Johor Bahru
www.growtopiajaw.phpn.ga
not stopping halfway, it's like a backup plan, just in case after 360h of waiting and end up failed to unlock.
Try waiting after 360 hours first. I'll try to prepare and provide you the backup if it really does fail to unlock.

Last time when I took a backup from someone, the backup contains some kind of device information from his phone (I accidentally wiped a partition and requested backup from him). I was using a custom ROM at that time (It doesn't have any problems with security thingy). Then, I decided to return back to MIUI because graphics performance is bad in custom ROM (I can't even open Real Racing 3. It keeps force closing). After flashing MIUI and the backup, I rebooted the phone. Then, it suddenly says "This device is associated with an existing account. For security reasons, you need to enter password to verify the device." This is what it looks like:


I recommend you to wait for the period to finish first. If it really really doesn't work, you can try it out with your method.
 
Last edited:
  • Like
Reactions: Gulabsheer