eMAX mini Unbrick Kit + TWRP recovery + Root

zgf

Interesting. We get a picture piece by piece....

With 'collapsing', you mean bricking that have been reported by users in this thread?

Fortunately, I didn"t try any of that.

Now I still have original stock ROM from 25.9. (but rooted), but with stock recovery replaced by TWRP (as was discussed, at that time, in TWRP thread). I can safely boot to TWRP (by Volume Up + Power or from Flashify in running Android), no collapsing/bricking.

Do you think that invoking Factory reset would still brick my phone (as is now: ROM 25.9. + TWRP)?

I.e., do you advice any reason to bother at the moment with flashing the ROM 19.10. from your Unbrick kit (or I will do the sam Unbricking if my phone ever bricks)?

bencebacsi

Yes, I mean bricking. If you've replaced the stock recovery with twrp, then your phone is not in danger anymore. Anyway I tried it by myself as well and my phone got bricked immediately when I tried to boot into (still stock) recovery by vol-up+power.
The Unbrick Kit is not my stuff but issued by the factory. That's an official tool/update, so you may use it confidently. I had no chance to test the 25.9 version (that you still have), so I don't know about the advantages (if any) of the 19.10 update compared to the earlier version.

Gingernut

\n\nDo you know if there will be an update issued soon to fix some bad bugs?

charlik

After use unbrick kit with Download button I have received ROM with these properties:
Android version: 5.0.2
Android security patch level: 2015-11-01
software version: UMI eMAX mini_001_10/19/2015

charlik

Phones received on november have newer firmwares mini_001_10/23/2015.
May be UMI have updated unbrick kit with this firmware..

fabi_92

the exatly command is: fastboot -i 0x1bbb flash recovery iroot_twrp_recovery_emaxmini_15110412.img
one written in the initial post is not the same;)

bencebacsi

fabi_92 replied at 2015-11-26 22:17
the exatly command is: fastboot -i 0x1bbb flash recovery iroot_twrp_recovery_emaxmini_15110412.img
o ...

Oh yeah, you're right. I've changed the name of the uploaded recovery file but not on my machine. However, when I was writing the tutorial, I copied the same command that worked at me. I'm going to correct it. Thanks for notifying.

zgf

charlik replied at 2015-11-26 20:01
Phones received on november have newer firmwares mini_001_10/23/2015.
May be UMI have updated unbric ...

Unfortunately, all three ROMs from three dates (and unknown differences) have the same version number 1.00
Hence System Updates does not recognize that there is (if it is on the OTA server) a ROM to upgrade.
Although that Factory Reset causing to brick is a showstopper bug and UMI had to provide OTA upgrade to fix the issue.

At least, there should have been the OTA upgrade to manually download that an average Joe user can copy it to the memory card and execute by Local System Updates (another option as also availabe in the Settings).

Gingernut

\n\nWhere did the CM 12.1 build originally come from?

TCL/UMI?

Gingernut

We have just found out that the bootloader is locked, maybe this is why CM12.1 doesn't boot.