[RECOVERY][UNOFFICIAL_MOD][DECRYPTION][UPDATED-02-01-2019] TWRP 3.2.3-4 for nitrogen

nijel8

Senior Member
Dec 24, 2011
2,356
5,560
0
All over US
Your TWRP is working but I rooted my device for nothing... Mi Max 3 can't capture RAW photos even when Camera2API is enabled :( Xiaomi sucks!

EDIT: You have to manually edit build.prop to add or enable "persist.camera.HAL3.enabled=1". Now I can take RAW photos! :)
Who me...?
jk

Great work, I just installed your TWRP instead older TWRP and only then official 10.2 OTA update went through and installed without a single hiccup and all data intact. I only lost root, but I guess I will just have to reinstall Magisk again...
You always need to root again after rom install which overrides partitions, doesn't matter if root is in /system or systemless.
 
  • Like
Reactions: JulianJenner

choubix1

New member
Dec 19, 2018
2
0
0
I tried to restore a backup using TWRP and I bricked my phone (soft brick so I had to flash the Xiaomi global 10.2 fastboot rom using the xiaomi fast tool, then unlaock bootloader and resintall TWRP + magisk...)

How to properly perform a a backup and restore for next time time? thanks!
 

JulianJenner

Senior Member
Apr 17, 2013
4,796
1,936
253
Arnhem
I tried to restore a backup using TWRP and I bricked my phone (soft brick so I had to flash the Xiaomi global 10.2 fastboot rom using the xiaomi fast tool, then unlaock bootloader and resintall TWRP + magisk...) How to properly perform a a backup and restore for next time time? thanks!
What version of ROM did you save backup?
What did you do exactly? And how did you do that?
 

nijel8

Senior Member
Dec 24, 2011
2,356
5,560
0
All over US
I tried to restore a backup using TWRP and I bricked my phone (soft brick so I had to flash the Xiaomi global 10.2 fastboot rom using the xiaomi fast tool, then unlaock bootloader and resintall TWRP + magisk...)

How to properly perform a a backup and restore for next time time? thanks!
You just backup and restore, nothing special about it...
Next time grab recovery logs for both backup/restore operations... But don't think recovery is your problem if no errors were thrown...
 
  • Like
Reactions: WinterR

nijel8

Senior Member
Dec 24, 2011
2,356
5,560
0
All over US
Works perfect! Is your kernel running on Xiaomi.eu, too?
Do you add some features in future?
How can I help you testing LOS16?
By running the recovery as hard as you can for now...:D
This kernel haven't seen Android yet, much less MIUI... Doubt it will boot on MIUI as is, it's pure as it gets for AOSP/Lineage based roms... Shoud work on GSIs too.
BTW all modules/drivers are built-in so no worries there like the oreo kernel we were building from Xiaomi sources... This one is only ~23MB all-in-one single image... v.4.4.153
I will be adding reasonable features after I get it running in Android.
For major kernel mods see @mario_R... He is the kernel guy here...
 
Last edited:
  • Like
Reactions: silvbm

mario_R

Senior Member
Mar 28, 2014
399
477
103
25
By running the recovery as hard as you can for now...:D
This kernel haven't seen Android yet, much less MIUI... Doubt it will boot on MIUI as is, it's pure as it gets for AOSP/Lineage based roms... Shoud work on GSIs too.
BTW all modules/drivers are built-in so no worries there like the oreo kernel we were building from Xiaomi sources... This one is only ~23MB all-in-one single image... v.4.4.153
I will be adding reasonable features after I get it running in Android.
For major kernel mods see @mario_R... He is the kernel guy here...
So I've compiled the kernel from your sources using GCC 4.9 few min ago but unfortunately bugs remains same as on my previous sources. So it's:
-no sound (overall, system doesn't play music, no ringtones, notifications, alarm app shows error called "Error" while switching alarm sounds)
-videos doesn't work work. Including YouTube, Messenger, Telegram etc... Videos can be played via MX Player using SW and HW+ decoders. Normal HW doesn't work. Of course without any sound. Already took some logs so let's see if I can fix it
 

babay911

Member
Mar 27, 2016
10
1
0
Hi ! We, some testers and fans of your mod.recovery for MM3 and was not able to directly ( even Magisk ) , start stock global ! To launch a localized firmware , restore backup and ...... , no complaints . We want you to tell us how to launch a Global flow from your recovery? And desirable on counts ! The answer is to branch Mi or Max 3 here : your thread on XDA ! Sincerely, Babay911 !
 

JulianJenner

Senior Member
Apr 17, 2013
4,796
1,936
253
Arnhem
I tried to restore a backup using TWRP and I bricked my phone (soft brick so I had to flash the Xiaomi global 10.2 fastboot rom using the xiaomi fast tool, then unlaock bootloader and resintall TWRP + magisk...) How to properly perform a a backup and restore for next time time? thanks!
Hi ! We, some testers and fans of your mod.recovery for MM3 and was not able to directly ( even Magisk ) , start stock global ! To launch a localized firmware , restore backup and ...... , no complaints . We want you to tell us how to launch a Global flow from your recovery? And desirable on counts ! The answer is to branch Mi or Max 3 here : your thread on XDA ! Sincerely, Babay911 !
The situation - I think - is:
I'll describe what I think, and then the more skilled-android-gurus will correct it if my thought is wrong.
Stock-Factory MIUI ROMs work with an encrypted partition.
This TWRP works perfectly with non-encrypted data partitions (like xiaomi.eu ROM, and Trebled AOSP-->)
When you start this TWRP, it avoids encryption, but it may cause additional problems.
Your device has a factory-partitioned encrypted partition.
With TWRP you successfully save all partitions (including encrypted partitions)
You then use TWRP, perform the Format data operation, and then the partition is no longer encrypted.
And when you want to restore the previous backup (including the encrypted partition), bootloop is created due to the incompatibility of the encrypted and unencrypted partitions.
 
Last edited:

nijel8

Senior Member
Dec 24, 2011
2,356
5,560
0
All over US
Updated... Automatic OTA install finally fixed!

The situation - I think - is:
I'll describe what I think, and then the more skilled-android-gurus will correct it if my thought is wrong.
Stock-Factory MIUI ROMs work with an encrypted partition.
This TWRP works perfectly with non-encrypted data partitions (like xiaomi.eu ROM, and Trebled AOSP-->)
When you start this TWRP, it avoids encryption, but it may cause additional problems.
Your device has a factory-partitioned encrypted partition.
With TWRP you successfully save all partitions (including encrypted partitions)
You then use TWRP, perform the Format data operation, and then the partition is no longer encrypted.
And when you want to restore the previous backup (including the encrypted partition), bootloop is created due to the incompatibility of the encrypted and unencrypted partitions.
Not likely... TWRP backup is pure file per file tar archiving, decryption doesn't matter as long as files are accessible. It's not block or binary backup.

@babay911 I really don't understand what you are saying exactly so not able to offer any help, sorry...
Is it the Global ROM not booting in general after clean install(never failed on me) or is it not booting after data restore(possible) or the full restore is not booting!? Please, explain your problem in details more clear. You can do it on 4PDA or PM in russian... Thanks.
 
Last edited:
G

GuestK00171

Guest
Updated... Automatic OTA install finally fixed!


Not likely... TWRP backup is pure file per file tar archiving, decryption doesn't matter as long as files are accessible. It's not block or binary backup.

@babay911 I really don't understand what you are saying exactly so not able to offer any help, sorry...
Is it the Global ROM not booting in general after clean install(never failed on me) or is it not booting after data restore(possible) or the full restore is not booting!? Please, explain your problem in details more clear. You can do it on 4PDA or PM in russian... Thanks.
I've got boot problems after complete backup and restore of MIUI. It boots up, but launcher did not start, blank screen, phone not usable. No security was set for screen before backup!
 

nijel8

Senior Member
Dec 24, 2011
2,356
5,560
0
All over US
Can I just ask what's the difference from the 12-29 (3.2.3-3) version which I have running now, because OTA installed through it without a problem last week?


Sent from my Mi Max 3 using Tapatalk
You will see the problem with incremental OTAs. Full rom OTAs are fine... And btw there is that thing a.k.a changelog on first page.

I've got boot problems after complete backup and restore of MIUI. It boots up, but launcher did not start, blank screen, phone not usable. No security was set for screen before backup!
"complete backup" means... what?
No such problems here restoring boot, system, vendor and data from same stock miui version... Force closes, hangups etc are possible if you mix data/system/vendor from different miui versions. No boot at all possible if boot doesn't match system and vendor. Same goes 1000% for sure if you restore system and vendor regular(file based) backups with dm-verity enabled boot(stock miui). There is so much that can go wrong if you don't do backup/restore the right way.
 
Last edited:
  • Like
Reactions: silvbm and palmdude
G

GuestK00171

Guest
"complete backup" means... what?
No such problems here restoring boot, system, vendor and data from same stock miui version... Force closes, hangups etc are possible if you mix data/system/vendor from different miui versions. No boot at all possible if boot doesn't match system and vendor. Same goes 1000% for sure if you restore system and vendor regular(file based) backups with dm-verity enabled boot(stock miui). There is so much that can go wrong if you don't do backup/restore the right way.
It is a bug in your recovery. I've backup all partitions (not internal Data like pics eg.) and restored them...two times...no complete boot! Done 1000% the same with OrangeFox TWRP and my phone boots correct. I tested with Xiaomi.eu 9.1.3 without active lookscreen security.