Develop Bugs

Miui8 7.1.19 global beta official is out

Mi 5
Fastboot 1709M
http://bigota.d.miui.com/7.1.19/gem...19_20170119.0000.00_7.0_global_409e0dc1a0.tgz
Recovery 1438M
http://bigota.d.miui.com/7.1.19/miui_MI5Global_7.1.19_668b027f8d_7.0.zip

Any success with recovery so far? I'll test in a few hours and report back

Installed the latest version via updater app few hours agi. So far everything is fine, no noticable differences.

Can I flash this over LineageOS? Or I need to revert back to MIUI 6.11.10 and then this one through updater?
And, is it nougat based?

verma.avesh said:
Any success with recovery so far? I'll test in a few hours and report back
Click to expand...
Click to collapse
I can't install via recovery... A few of attempts and was impossible ? ...always gave me errors very confused.

neodante said:
I can't install via recovery... A few of attempts and was impossible ? ...always gave me errors very confused.
Click to expand...
Click to collapse
If possible, try flashing 6.11.10 and update this over MIUI. Hope that'll help. I might have tested anyways, but exam on Monday so..

verma.avesh said:
If possible, try flashing 6.11.10 and update this over MIUI. Hope that'll help. I might have tested anyways, but exam on Monday so..
Click to expand...
Click to collapse
Well, maybe days later, just configured other rom.

After OTA update to 7.1.19 , 4K video is, flickering , i tried all 4 settings (50 ,60hz ,none and auto) . Only on 4K video . Before update in same lighting condition I have no problem

Ok guys
After update to this rom I'm bit lost
I was on custom 7.1.1 with TWRP before.
I did fresh start and tried flash this rom from TWRP. No luck
Then I have flashed xiaomi.eu_multi_MI5_6.10.27_v8-6.0.zip and after boot I have rebooted to recovery (still TWRP) and I have flashed the above rom and this time with luck. After successful boot, I have noticed few FC on for example Music.
No I have lost TWRP, can't go back to my TWRP backup.
Wish I never try lol
How do I start again? How do I flash TWRP?
Thanks

demo84 said:
Ok guys
After update to this rom I'm bit lost
I was on custom 7.1.1 with TWRP before.
I did fresh start and tried flash this rom from TWRP. No luck
Then I have flashed xiaomi.eu_multi_MI5_6.10.27_v8-6.0.zip and after boot I have rebooted to recovery (still TWRP) and I have flashed the above rom and this time with luck. After successful boot, I have noticed few FC on for example Music.
No I have lost TWRP, can't go back to my TWRP backup.
Wish I never try lol
How do I start again? How do I flash TWRP?
Thanks
Click to expand...
Click to collapse
Fastboot flash recovery recovery.img

Yeah after few hiccups I'm back to main TWRP backup
Glad I did keep that on my Pc
I had problem with TWRP and encryption that lead me to clear off my phone ?

demo84 said:
Ok guys
After update to this rom I'm bit lost
I was on custom 7.1.1 with TWRP before.
I did fresh start and tried flash this rom from TWRP. No luck
Then I have flashed xiaomi.eu_multi_MI5_6.10.27_v8-6.0.zip and after boot I have rebooted to recovery (still TWRP) and I have flashed the above rom and this time with luck. After successful boot, I have noticed few FC on for example Music.
No I have lost TWRP, can't go back to my TWRP backup.
Wish I never try lol
How do I start again? How do I flash TWRP?
Thanks
Click to expand...
Click to collapse
That happened to me too... Thank goodness that I did not lose the recovery and then installed a 6.0.1 rom ( AICP )
I AM DEFINITELY TIRED OF TO TEST NOUGAT MI5 ROMS !! All have performance problems and bugs, there isn't any that works as good as marshmallow roms.

flashing the fastboot rom will lock the bootloader ?

Ok so I thought full TWRP backup (over 6GB) will back up my photos
Nope I lost all my data

Did anybody has stuttering issue on this after flashing SuperSU?

Is this Nougat based?

Bimalhort said:
Is this Nougat based?
Click to expand...
Click to collapse
Yes... Android 7.0
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
demo84 said:
Ok so I thought full TWRP backup (over 6GB) will back up my photos
Nope I lost all my data
Click to expand...
Click to collapse
TWRP backs up the system partition not the internal storage
---------- Post added at 08:08 PM ---------- Previous post was at 08:07 PM ----------
chhapil said:
Did anybody has stuttering issue on this after flashing SuperSU?
Click to expand...
Click to collapse
No issues here

I made OTA upgrade . After hard reset problems remaining are bad GPS precision and banding only in 4k video at inside light (I tested all anti band settings)

harrez said:
flashing the fastboot rom will lock the bootloader ?
Click to expand...
Click to collapse
Only if you tell MiFlash to do so after flashing.

[QUESTION] changing back to miui

Im using a custom rom installed via twrp,
I wanna go back to miui, will it be fine if clean flashed over the current custom ROM through twrp, or do i need to follow any other way?

Try use ROM xiaomi.eu
---------- Post added at 01:00 AM ---------- Previous post was at 01:00 AM ----------
Or mi-globe.com

jaspad1710 said:
Im using a custom rom installed via twrp,
I wanna go back to miui, will it be fine if clean flashed over the current custom ROM through twrp, or do i need to follow any other way?
Click to expand...
Click to collapse
Its easy..
Clean flash ur MIUI rom... (Using TWRP)
And use lazyflasher to skip dm-verity check..
Here : https://drive.google.com/file/d/0ByWEieei-0nyMTR4R0dxWk9BTms/view?usp=sharing
Done .... Reboot and Enjoy !!

QwertySDuos2 said:
Its easy..
Clean flash ur MIUI rom... (Using TWRP)
And use lazyflasher to skip dm-verity check..
Here : https://drive.google.com/file/d/0ByWEieei-0nyMTR4R0dxWk9BTms/view?usp=sharing
Done .... Reboot and Enjoy !!
Click to expand...
Click to collapse
Wait, i installed miui9 correct version from miui website, i properly did a clean flash (installed correct openg) which im 100% sure, but the phone was stuck at boot logo, but twrp was working with the hardware key combo..pls help
And a peculiar thing is i have been using openg full arm64
Since i first begun using los unofficial, but today after flashing miui its showing that mine is arm and not arm64..pls give ur valuable insights

jaspad1710 said:
Wait, i installed miui9 correct version from miui website, i properly did a clean flash (installed correct openg) which im 100% sure, but the phone was stuck at boot logo, but twrp was working with the hardware key combo..pls help
And a peculiar thing is i have been using openg full arm64
Since i first begun using los unofficial, but today after flashing miui its showing that mine is arm and not arm64..pls give ur valuable insights
Click to expand...
Click to collapse
Format data and cache partitions as ext4 not as f2fs..
Then follow my instructions as before..
Miui has inbuilt gapps..
Why u need opengapps then ??
(Dont flash gapps on miui..)

QwertySDuos2 said:
Format data and cache partitions as ext4 not as f2fs..
Then follow my instructions as before..
Miui has inbuilt gapps..
Why u need opengapps then ??
(Dont flash gapps on miui..)
Click to expand...
Click to collapse
Holyy so flashing the gapps crashed it?

jaspad1710 said:
Holyy so flashing the gapps crashed it?
Click to expand...
Click to collapse
Yeah... Probably coz the gapps in miui are in data partition instead of system partiton (atleast that was the case with miui 8 on my other device the Redmi Note 4G)

Problems with nAOSP 8.1 Oreo Changelog b05 and Open Gapps

Hello
i Have some Problems.
1. After i installed nAOSP 8.1 Oreo Changelog b05 TWRP 3.2.3 changed to 3.1.1
2. Can not installed open Gapps (cannot Mount).
3. Which Gapps i need (tried Arm and Arm64) Both don't will install (error).
4. Factory reset don't work. I push the Button but nothing happen.
5 I install the apk from the Play Store app and the Google services. Both dont work. (Close app)
Can you help me?
ruedi69

ruedi69 said:
Hello
i Have some Problems.
1. After i installed nAOSP 8.1 Oreo Changelog b05 TWRP 3.2.3 changed to 3.1.1
2. Can not installed open Gapps (cannot Mount).
3. Which Gapps i need (tried Arm and Arm64) Both don't will install (error).
4. Factory reset don't work. I push the Button but nothing happen.
5 I install the apk from the Play Store app and the Google services. Both dont work. (Close app)
Can you help me?
ruedi69
Click to expand...
Click to collapse
Have you repartitioned your device? Follow the procedure from the naosp 8.1 thread.

no
When i installed nAOSP 6.0 i put only Partition 14 and 15 togehter. Now i must looking how i do repartition under Ubuntu 18.10. Will take a while.

ruedi69 said:
When i installed nAOSP 6.0 i put only Partition 14 and 15 togehter. Now i must looking how i do repartition under Ubuntu 18.10. Will take a while.
Click to expand...
Click to collapse
If you repartitioned once before then no need to do it again. Just flash twrp mentioned on the first page and proceed to flash the rom

nageswarswain said:
If you repartitioned once before then no need to do it again. Just flash twrp mentioned on the first page and proceed to flash the rom
Click to expand...
Click to collapse
First i flashed TWRP 3.2.3. Then i installed the new rom. After this TWRP was Version 3.1.1

ruedi69 said:
First i flashed TWRP 3.2.3. Then i installed the new rom. After this TWRP was Version 3.1.1
Click to expand...
Click to collapse
Ohhh I think you flashed the 323 to boot partition and before any other occasion you flashed the 311 to fota that you not remembered. So after flashing the ROM the 323 has been replaced by boot.IMG and you are now on only 311 twrp on fota
---------- Post added at 07:02 PM ---------- Previous post was at 07:01 PM ----------
ruedi69 said:
First i flashed TWRP 3.2.3. Then i installed the new rom. After this TWRP was Version 3.1.1
Click to expand...
Click to collapse
Ohhh I think you flashed the 323 to boot partition and before any other occasion you flashed the 311 to fota that you not remembered. So after flashing the ROM the 323 has been replaced by boot.IMG and you are now on only 311 twrp on fota.so now what is your problem
---------- Post added at 07:03 PM ---------- Previous post was at 07:02 PM ----------
Ohhh I think you flashed the 323 to boot partition and before any other occasion you flashed the 311 to fota that you not remembered. So after flashing the ROM the 323 has been replaced by boot.IMG and you are now on only 311 twrp on fota.so you can flash the 323 to fota if you want every time 323.by the way what's your problem now.

nageswarswain said:
Ohhh I think you flashed the 323 to boot partition and before any other occasion you flashed the 311 to fota that you not remembered. So after flashing the ROM the 323 has been replaced by boot.IMG and you are now on only 311 twrp on fota
---------- Post added at 07:02 PM ---------- Previous post was at 07:01 PM ----------
Ohhh I think you flashed the 323 to boot partition and before any other occasion you flashed the 311 to fota that you not remembered. So after flashing the ROM the 323 has been replaced by boot.IMG and you are now on only 311 twrp on fota.so now what is your problem
---------- Post added at 07:03 PM ---------- Previous post was at 07:02 PM ----------
Ohhh I think you flashed the 323 to boot partition and before any other occasion you flashed the 311 to fota that you not remembered. So after flashing the ROM the 323 has been replaced by boot.IMG and you are now on only 311 twrp on fota.so you can flash the 323 to fota if you want every time 323.by the way what's your problem now.
Click to expand...
Click to collapse
I look at the other threads and saw that my Partitions are other as the in the thread cant install opengapps. Then i delete 12/13/14 and make it new like this. All T 83 and formated as F2FS. Now i have a new Problem:
mount: Failed to mount /devblock/platform/msm_sdcc.1/by-num/p12 at /system: Invalid argument
..
Failed to unmount /system: No such volume
Udater process ended with ERROR: 7

ruedi69 said:
I look at the other threads and saw that my Partitions are other as the in the thread cant install opengapps. Then i delete 12/13/14 and make it new like this. All T 83 and formated as F2FS. Now i have a new Problem:
mount: Failed to mount /devblock/platform/msm_sdcc.1/by-num/p12 at /system: Invalid argument
..
Failed to unmount /system: No such volume
Udater process ended with ERROR: 7
Click to expand...
Click to collapse
As we cant see all that happening to you.i will suggest to Flash official ftf and try everything from beginning.After flashing official ftf follow the procedure correctly on the 1st page of nAosp ROM will be better for you.

Most Problems solved
nageswarswain said:
As we cant see all that happening to you.i will suggest to Flash official ftf and try everything from beginning.After flashing official ftf follow the procedure correctly on the 1st page of nAosp ROM will be better for you.
Click to expand...
Click to collapse
Last Problem first: I re-partion it. Wipe all what i found. Date and Cache could not mount. Then i formatted system/Cache and Data ext4. Now i Could it mount. Then i formatted all F2FS again. Would install Android 8.1.0-b05 and opengapps for ARM (Not ARM64). Once again : Error 7
Then I tried to install nAOSProm-7.1.2-b04.zip. Its function.
Then i install nAOSProm-8.1.0-b05 and opengapps again. Wipe dalvikcache and now it works. Why i dont know.
Its now TWRP 3.2.3 and after i flash it into the Fotakernel too.
Want to donate a little bit but This recipient is currently unable to receive money. Try it later
PlayStore works too..
Thanks for your help and your patience

Moto Z play wont boot to system after flashing TWRP and installing magisk

I have a Moto Z Play that had the stock current version of Oreo installed, and I was able to unlock my bootloader and I went through the steps in the guide to install TWRP and Magisk, followed by f2fsfix. After installing TWRP I could still boot to system, but then after installing Magisk and f2fsfix, I'm unable to boot to system I just get the screen saying my device isn't trusted and will boot in 5 seconds, but just stays on that screen.
I've tried using the magisk uninstaller and reinstalling, and it hasn't worked. I've tried uninstalling and reinstalling magisk by flashing and booting to TWRP, neither has worked. Also I've been using TWRP 3.2.3.0 Addison, and I've tried both Magisk 18.1 and 16.0.
Anyone have any idea as to what may be going on, or how I can rememdy the situation? Let me know if there's additional information you need about the device.

Same thing happened to me. Tried many times but after flashing magisk it couldn't boot to system just get stuck on bootlogo. Luckily i had a twrp backup, i just restored and I'm on nougat now with working imei. Only thing that makes me worry is now i have the stock nougat rom but oreo bootloader.
---------- Post added at 10:41 PM ---------- Previous post was at 10:40 PM ----------
I would suggest you to roll back to nougat

khanpatriot said:
Same thing happened to me. Tried many times but after flashing magisk it couldn't boot to system just get stuck on bootlogo. Luckily i had a twrp backup, i just restored and I'm on nougat now with working imei. Only thing that makes me worry is now i have the stock nougat rom but oreo bootloader.
---------- Post added at 10:41 PM ---------- Previous post was at 10:40 PM ----------
I would suggest you to roll back to nougat
Click to expand...
Click to collapse
So if I didn't have a TWRP recovery file would there be a version of the stock rom that I could download and flash to get things working?

So you have an efs backup? As it's something most important otherwise you will loose your imei(not permanently) but it won't show by *#06#. Or in settings.
---------- Post added at 05:10 AM ---------- Previous post was at 05:04 AM ----------
If u want to go back to stock nougat here's the owsum rom i tested and running currently.... by supahcookie.
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
But keep in mind first make your efs backup with chinese twrp. Sorry i forgot where from i downloaded but search a little bit hope u will find. Regards

khanpatriot said:
Same thing happened to me. Tried many times but after flashing magisk it couldn't boot to system just get stuck on bootlogo. Luckily i had a twrp backup, i just restored and I'm on nougat now with working imei. Only thing that makes me worry is now i have the stock nougat rom but oreo bootloader.
---------- Post added at 10:41 PM ---------- Previous post was at 10:40 PM ----------
I would suggest you to roll back to nougat
Click to expand...
Click to collapse
Just had a chance to do that and it looks like I'm back in buisiness. Thanks!

beebop483 said:
I have a Moto Z Play that had the stock current version of Oreo installed, ... [...]
Anyone have any idea as to what may be going on, or how I can rememdy the situation? Let me know if there's additional information you need about the device.
Click to expand...
Click to collapse
For Oreo Moto Z Play current and probably last version there exists a pre patched boot.img to flash at the end of the twrp thread. Please have a look there if you still need it, but be aware that it is only for the exact os version.
Alberto97 said:
I patched it for you, just flash this bootimage (only for OPNS27.76-12-22-9 build, it might break ...
Click to expand...
Click to collapse
Also note that I did not test it by now, just saved it for usage when I need root.

beebop483 said:
I have a Moto Z Play that had the stock current version of Oreo installed, and I was able to unlock my bootloader and I went through the steps in the guide to install TWRP and Magisk, followed by f2fsfix. After installing TWRP I could still boot to system, but then after installing Magisk and f2fsfix, I'm unable to boot to system I just get the screen saying my device isn't trusted and will boot in 5 seconds, but just stays on that screen.
I've tried using the magisk uninstaller and reinstalling, and it hasn't worked. I've tried uninstalling and reinstalling magisk by flashing and booting to TWRP, neither has worked. Also I've been using TWRP 3.2.3.0 Addison, and I've tried both Magisk 18.1 and 16.0.
Anyone have any idea as to what may be going on, or how I can rememdy the situation? Let me know if there's additional information you need about the device.
Click to expand...
Click to collapse
uninstall magisk with uninsatllmagisk.zip from twrp

slow boot on Android Pie with twrp

Please point me to the right thread if there is one.
Since upgraded to Android Pie and TWRP 3.23, my 5T got very slow boot mainly because it stuck at splash screen (the one has powered by android) for about 2min every boots/reboots. I tried restoring to stock recovery, it does boot normally.
This slow boot happens on all Pie updates including 9.0.5 with twrp 3.3.0. Any solution?

same here, waITING FOR SOLUTION

fitzpete said:
same here, waITING FOR SOLUTION
Click to expand...
Click to collapse
using Blue Spark 9.100 version no any kind of booting problem here.

Already using TWRP 3.3.0-x blu_spark v9.100, also try blu_spark r165-oos, still the same.
It will boots normally only with stock recovery.

semson said:
Already using TWRP 3.3.0-x blu_spark v9.100, also try blu_spark r165-oos, still the same.
It will boots normally only with stock recovery.
Click to expand...
Click to collapse
What about 'Magisk incl. modules'?

same here.
too slow to boot for both normal boot and recovery boot.
not sure if it a magisk related or not.

nicorvienne said:
What about 'Magisk incl. modules'?
Click to expand...
Click to collapse
I've two modules activated: magisk manager for recovery mode & oneplus 5t camera library fix (for gcam). complete removal of them doesnt help anything, still slow boot.

semson said:
I've two modules activated: magisk manager for recovery mode & oneplus 5t camera library fix (for gcam). complete removal of them doesnt help anything, still slow boot.
Click to expand...
Click to collapse
try - MagiskManager > uninstall > restore images > reboot TWRP > wipe cache > flash ROM > wipe > flash Magisk > reboot

Alright I tried it. after restored the image TWRP is gone, reboot and it is already stock recovery; booting is fine as it is stock recovery. Anyway I re-flashed OOS 9.0.5 with stock recovery, after 1st boot to system I installed TWRP via fastboot, booting slows down as it was,,, nothing's changed.
The only thing I didn't try to wiping data, I cannot afford losing everything and I don't' believe it matters as I have perfectly fine booting on stock recovery.

semson said:
Alright I tried it. after restored the image TWRP is gone, reboot and it is already stock recovery; booting is fine as it is stock recovery. Anyway I re-flashed OOS 9.0.5 with stock recovery, after 1st boot to system I installed TWRP via fastboot, booting slows down as it was,,, nothing's changed.
The only thing I didn't try to wiping data, I cannot afford losing everything and I don't' believe it matters as I have perfectly fine booting on stock recovery.
Click to expand...
Click to collapse
this behavior is existing with Magisk 18.1 as well with 19.1?

Yes same slow boot on magisk 18. I doubt if it is related, with twrp it boots slow already even magisk is not installed.

i have this issue too. running the latest codework twrp. not sure if this caused it to slow down because it wasn't this slow before the update.

I've always removed the 'compatibility.zip' from the OOS PIE ROMS, that way I was able to keep the Oreo version of TWRP installed;
twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t.img
This is also nice, in case some people decide they don't like PIE and want to easily revert back.
I've never had any issues like this.

DoR3M3 said:
I've always removed the 'compatibility.zip' from the OOS PIE ROMS, that way I was able to keep the Oreo version of TWRP installed;
twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t.img
This is also nice, in case some people decide they don't like PIE and want to easily revert back.
I've never had any issues like this.
Click to expand...
Click to collapse
I'll try to rollback to 3.2.3 version and see how it goes.
Thanks for the suggestion.
---------- Post added at 09:12 AM ---------- Previous post was at 08:30 AM ----------
Unfortunately.
Rollback to 3.2.3 with both version (codeworkx, blu_spark)
still slow to boot.

i have this issue too.
---------- Post added at 09:39 AM ---------- Previous post was at 09:36 AM ----------
aillez said:
I'll try to rollback to 3.2.3 version and see how it goes.
Thanks for the suggestion.
---------- Post added at 09:12 AM ---------- Previous post was at 08:30 AM ----------
Unfortunately.
Rollback to 3.2.3 with both version (codeworkx, blu_spark)
still slow to boot.
Click to expand...
Click to collapse
how is stiuation?

CanKartaL84 said:
i have this issue too.
---------- Post added at 09:39 AM ---------- Previous post was at 09:36 AM ----------
how is stiuation?
Click to expand...
Click to collapse
same as before. around 2 minutes to reboot.

If anyone still having this issue, I found it links to encryption of Dual Apps zone. "Format Data" from TWRP and this issue gone, do backup before proceeding and you will lose everything.

semson said:
If anyone still having this issue, I found it links to encryption of Dual Apps zone. "Format Data" from TWRP and this issue gone, do backup before proceeding and you will lose everything.
Click to expand...
Click to collapse
Do we have a new solution rather than formatting data now in year 2020?