Fastboot Rom (miui 8/9, Los13, AOSP) With Gapps, Root And Some Other Stuffs


Papka__

Members
Mar 21, 2016
510
82
Hi,

Would like to share ROM technically build by me and inspired from http://4pda.ru/forum/index.php?showtopic=713227&view=findpost&p=51522890.
This ROM built based on China Dev and Xiaomi.eu.
What is built in:
1. Root. Fully working, Selinux enforced, with SuperSu 2.82.
2. OTA working (China based ROM only!!!!!)
2. GAPPS updated
3. Init.d enabled
4. Some optimization scripts included.
5. Throttling problem resolved.
6. Additional icons added.
7. Google keyboard (China based ROM only)
8. MoreLocale for localization (China based ROM)
9. Some interface stuff
10. Xperia keyboard added (only xiaomi.eu based)
11. Unnecessary market services disabled. Reboot device after first boot!!!!!!!
12. Grid changed to 5x6. (7.2.9)

Links:
Images based on China dev 8.4.26: https://drive.google.com/open?id=1md4-JK6XKusZVj4BOT4jUJzZNLiL4frQ
Images based on China stable 8.5.1.0: https://drive.google.com/file/d/0B7Nb0mR1oVUWc3MxMGRZVzhGcTQ/view?usp=sharing
Images based on China stable 9.2.3.0: https://drive.google.com/open?id=1i74M02Go4Pw6ypnrsscwuqHr1CUTU44V
SuperSu 2.82: https://drive.google.com/file/d/0B7Nb0mR1oVUWMUhYdzR6enYybjg/view?usp=sharing
Toolbox: https://drive.google.com/open?id=0B7Nb0mR1oVUWUlBRbEhaU3NtMWc

LOS13 (GAPPS+rooted): https://drive.google.com/open?id=0B7Nb0mR1oVUWV2FYWGlvdW44Z2M
All credits for LOS13 should go to Harrynowl, tank0412 (https://forum.xda-developers.com/mi-pad/development/unofficial-lineageos-13-0-xiaomi-mi-pad-t3565760). Note, you need to set your bootloader to "unlock" state.
AOSP (GAPPS+rooted): https://drive.google.com/open?id=1l6j5g0D5aZd7koLKXS8DojPdOh29ot_n
All credits for AOSP go to Димас Удянский (https://4pda.ru/forum/index.php?showtopic=713227&view=findpost&p=61360993)
Note, you need to set your bootloader to "unlock" state.

How to install:
Download and extract Toolbox. Download images you're going to flash.
Extract (to be able to extract, you should use archiver, supporting RAR5 (WinRar 5.x for example)) images to ROM subfolder inside Toolbox. Open command line in Toolbox folder. Run tool.bat. Look on the screen. If somtheng will be wrong - you will be informed. Inside menu, choose what you would like to do. You don't need specially to change bootloader state. Toolbox will do this for you.
For those, who didn't understood why this is done - you can flash this rom without TWRP and unlocking your tab. So no bootloader errors.
Key feature of customized China Dev - you will have OTA and built in add-ons together. Applying OTA will not remove add-ons.

MIUI9 resolved problem with normal OTA. After first boot go to Settings->Installed apps->Updater, do Force stop and clear data and cache.

I tested this on my own MiPad 2. It's working for me. But all you will do - will be done at your own risk.

All credits not to me, but to forum http://4pda.ru/forum/index.php?showtopic=713227 and a guy LVware

P.S. If you have problems with Market (error like [RH-01], unable to get into Play Market and so on), but not like looping on applications download, remove your google account in settings and add it again.
 
Last edited:
As you modify the tablet did you try or made Dolby Atmos work with the tab? I tried many times to make it work with no success.
 
I will have a look when will build xiaomi.eu based version. Major focus for original dev based - to have OTA and all other stuffs at the same time.
 
  • Like
Reactions: kostas83
I get erorr when write flashh_all in cmd

fastboot getvar product 2>&1 | findstr /r /c:"^product: *latte" || echo Missmatching image and device

C:\Flash_tool>fastboot flash bootloader bootloader.img || exit /B 1
target reported max download size of 268435456 bytes
sending 'bootloader' (32768 KB)...
OKAY [ 1.172s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 1.203s

C:\Flash_tool>

any solution? flash on win 10 64bit
 
Sometimes I had the same error like you with 'FAILED (status read failed (Too many links))'.
Restarting the pad in fastboot mode and several times connecting and disconnecting the USB solved the problem for me.
I don't know what the reason/problem was but it seemed to be a occasionally occurring error with the driver espc. recognition of the pad.
(I'm also using win10x64)
 
It should work... Probably drivers problem. W10 - this is something... I use W7 and no problems at all. It's all about Microsoft...
 
Maybe it would be better if you could make a recovery version of your rom as most of us have TWRP an EU Roms so It will be easy to flash it with TWRP over the EU Roms that Running in the tab as the weekly Roms of the forum.
 
No matter what king of recovery you have. You should use fastboot mode to flash. It's not connected to recovery. Only thing is, that is you use custom recovery, you should comment/delete row "fastboot oem verified" in flash script.
 
No matter what king of recovery you have. You should use fastboot mode to flash. It's not connected to recovery. Only thing is, that is you use custom recovery, you should comment/delete row "fastboot oem verified" in flash script.

I have flashed this rom with fastboot, but there was TWRP installed and now I can`t go to recovery (error 02). What should i do now? is there a fastboot command to allow unsigned recovery?
 
No, it was latest xiaomi.eu. It works just fine (finally got gapps working!) , but i cant get to recovery.
 
you not commented out this - "fastboot oem verified"?
2 ways -
1. flash original recovery
2. "fastboot oem unlock"

Then "fastboot format data" to avoid market error. All user data will be lost.
 
I didnt delete "fastboot oem verified" i missed your post here.

tried "fastboot oem unlock" but i get something like unable to unlock (var locked=yes)
done data format, I guess it leaves me with flashing original recovery. Which file is it? boot.img, bootloader.img or something else?
 
Easiest way - download China based ROM from this thread and flash it. Original recovery will be flashed automatically there. After that, you can flash same xiaomi.eu ROM from fastboot, but only if english language is not enough for you.
I would stay with this china modified ROM. As profit you will get OTA without any problems.
Later today I will publish china ROM based on 6.9.15 with MoreLocale built-in. So some localization will be possible also there.
 
Flashing these ROM's with this this flashing tool not wiping data. Problem is that I, by mistake, included "fastboot oem verified" into flashing tool. And for you there is no other way, but to get back original recovery to boot into. I already fixed this and published new version of flashing tool and china based ROM.
 
Last edited:
One question @Papka__ :
I'm now using xiaomi.eu with TWRP.
When I flash your xiaomi.eu-version including the optimizations,init.d... , do I still have TWRP or is my recovery reseted to the original xiaomi?
and when TWRP is preserved, what happens if i install a new xiaomi.eu-version from this website the next weeks (without your modifications). Will the optimizations be lost?
Thanks for your reply.
 
@Papka__
In both bat's comments you write "Should not be used in case of switching from any custom ROM with TWRP to ROM based on ORIGINAL MIUI dev ROM." Well I have, in theory, TWRP and want to switch to stock recovery.
So which bat should I use?
 
One question @Papka__ :
I'm now using xiaomi.eu with TWRP.
When I flash your xiaomi.eu-version including the optimizations,init.d... , do I still have TWRP or is my recovery reseted to the original xiaomi?
and when TWRP is preserved, what happens if i install a new xiaomi.eu-version from this website the next weeks (without your modifications). Will the optimizations be lost?
Thanks for your reply.

1. TWRP will stay and you will get usual 03 error on boot. It was a problem in previous version of installation batch. It's fixed now.
2. You will be able to install new version of xiaomi.eu ROM from TWRP, but added-ons like root/init.d/trrottle fix will be lost.

I'm planned to create weekly versions of xiaomi.eu ROM, but due to some reasons, I can't re-flash my device now. So maybe I'll skip this week. I also didn't got such feeling that xiaomi.eu ROM needed as a fastboot flashable.
I have no idea how many times it was used. Few comments in this thread. So let's see.
I'm not doing this for myself. I'm not using xiaomi.eu version.
My recommendation is to go with original dev based ROM, if MoreLocale is covering your localization expectations.
 
@Papka__
In both bat's comments you write "Should not be used in case of switching from any custom ROM with TWRP to ROM based on ORIGINAL MIUI dev ROM." Well I have, in theory, TWRP and want to switch to stock recovery.
So which bat should I use?

Haha... It's probably in readme? Copy/paste error. I'll fix this.
To move from any custom to original China based ROM option 2 should be used.
 
Ok, thanks.
But whats then the advantage of using the china.dev based rom? Because of OTA? But when you use OTA, all the added-ons will be lost anyway?
 
Ok, thanks.
But whats then the advantage of using the china.dev based rom? Because of OTA? But when you use OTA, all the added-ons will be lost anyway?

That's why this customized ROM created, to have OTA and to have add-ons after applying OTA. This is the key benefit of this ROM.
For xiaomi.eu ROM it's not possible to do this. That's why weekly ROM should be re-created. For China based I'm not going to create on weekly basis. Once for 3-4 weeks is enough. Flash, apply 2-3 OTA's and you are up to date. :)