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?
Related
Hi all,
I'm on OpenBeta9 and have /data formatted with f2fs. Couldn't find a clear indication of what TWRP version (and SuperSU) is compatible with this setup.
Could you please assist?
Thanks
Normaly, twrp-3.0.2-1.28-oneplus3 and SR5-SuperSU-v2.78-SR5-20161130091551. But in my case, i had a encrypt problem with the recovery
MrSkyFail said:
Normaly, twrp-3.0.2-1.28-oneplus3 and SR5-SuperSU-v2.78-SR5-20161130091551. But in my case, i had a encrypt problem with the recovery
Click to expand...
Click to collapse
Hi MrSkyFail, thanks for the reply.
Was your problem preventing you to use TWRP normally, or something I could work around?
Also, would you have download links? SuperSU should be easy for me to find, by TWRP is always a mess, since it's a mod version.
Thanks
andrea.ippo said:
Hi MrSkyFail, thanks for the reply.
Was your problem preventing you to use TWRP normally, or something I could work around?
Also, would you have download links? SuperSU should be easy for me to find, by TWRP is always a mess, since it's a mod version.
Thanks
Click to expand...
Click to collapse
For TWRP : http://forum.xda-developers.com/devdb/project/dl/?id=21835
Yeah, i couldn't decrypt my phone in recovery. I try with beta 9 official i lose my TWRP recovery for offical recovery and works.
---------- Post added at 01:27 PM ---------- Previous post was at 01:25 PM ----------
Look this : http://forum.xda-developers.com/oneplus-3/how-to/rom-oxygenos-beta-9-nougat-update-t3519069
MrSkyFail said:
For TWRP : http://forum.xda-developers.com/devdb/project/dl/?id=21835
Yeah, i couldn't decrypt my phone in recovery. I try with beta 9 official i lose my TWRP recovery for offical recovery and works.
---------- Post added at 01:27 PM ---------- Previous post was at 01:25 PM ----------
Look this : http://forum.xda-developers.com/oneplus-3/how-to/rom-oxygenos-beta-9-nougat-update-t3519069
Click to expand...
Click to collapse
I found out that if you only flash OB9 from TWRP, even though you formatted your /data partition and is f2fs, if you don't flash SU before your first boot, your phone becomes encrypted and you will have TWRP pin issues.
The other issue I found was that if you flash OB9, then try flashing SU (I'm running SR5 right now), it doesn't want to boot. The only way I got it to work is after you flash OB9, Mount /system and delete a couple of google apps (for me, I deleted Calendar and gmail; you can download these after you boot up from playstore), then flash SU, then reboot, and profit.
So order of things for me:
1. Wipe (make sure /data is f2fs)
2. Flash OB9
3. Flash TWRP (modded 1-28)
4. Reboot to recovery (you may have to do a manual power off then volume down + power on)
5. Mount /system and delete calendar and gmail apps
6. Flash SU (SR5; I think there's a newer version but I haven't tried it with the new one).
7. Wipe Dalvik and Cache
8. Reboot System
If everything is done correctly, your phone will reboot twice.
You will have dm-verity and unlocked bootloader warning screens.
First boot takes about 3-5 min.
Why would deleting a couple google apps be necessary? I don't get it. And this applies for having cache f2fs too I assume?
Stupifier said:
Why would deleting a couple google apps be necessary? I don't get it. And this applies for having cache f2fs too I assume?
Click to expand...
Click to collapse
You may only need to mount /system before you flash SU. I can't find the post at the moment but this was mentioned (delete a few apps) when OB8 first came around.
Only the /data partition has F2FS support on stock OB8 and OB9.
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.
Hello!
I just flashed the newest TWRP for Google Pixel, and everything seems to be going fine except a few things..
When I attempt to change slots within TWRP I get "E:Error getting bootctrl module" but I can switch active slots via bootloader fastboot... but for convenience sake, I'd like to know why I cant do that from recovery..
First thing I did was completely go back to stock on slot a and b, then I fastbooted the twrp image, installed it, then I rebooted into bootloader, changed slots, flashed recovery, went back to slot A, installed rom which is the LineageOS 14.1 from: https://forum.xda-developers.com/pixel-xl/development/rom-lineageos-14-1-nightlies-google-t3601893 because I dont want Oreo yet..too buggy imho, afterwards I flashed Magisk after initial boot...
I also noticed that the rom installed in slot B when I was in Slot A, not sure why?
I'm also having issues with having Elementalx Kernel + Magisk installed at the same time, Youtube wont work at all, and causes a kernel panic after sitting on the Youtube screen (frozen) for awhile.. so right now everything is working with just Magisk and the ROM, but I'd really like to use Elementalx and also be able to change slots from TWRP...
Please let me know what I did wrong!
Thanks.
No one ?
If I were you I would reflash the phone to stock then use fastboot format userdata to erase everything on it and install twrp again using latest zip from twrp website. Running 8.0 + EX kernel and magisk no bugs no crashes smooth stable. Also make sure to use magisk 14.2
george241312 said:
If I were you I would reflash the phone to stock then use fastboot format userdata to erase everything on it and install twrp again using latest zip from twrp website. Running 8.0 + EX kernel and magisk no bugs no crashes smooth stable. Also make sure to use magisk 14.2
Click to expand...
Click to collapse
I've already done all that.
Why are you changing slots ? Is there a necessity you can just flash your rom and magisk on the default slot.
---------- Post added at 09:42 AM ---------- Previous post was at 09:35 AM ----------
I would try not changing slots while flashing recovery.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
I think because you flashed recovery on slot b rom got installed on slot b.
KeithGS said:
No one ?
Click to expand...
Click to collapse
Twrp flashes to both boot partitions. You don't need to flash it twice. All custom roms switch slots when flashed. Welcome to Pixels. Something appears broken in new Twrp 3.1.1-0 for switching slots in Twrp. I am experiencing the same thing with the E. Boot control error.
Golf c said:
Twrp flashes to both boot partitions. You don't need to flash it twice. All custom roms switch slots when flashed. Welcome to Pixels. Something appears broken in new Twrp 3.1.1-0 for switching slots in Twrp. I am experiencing the same thing with the E. Boot control error.
Click to expand...
Click to collapse
Ok, so it's not just me, good... thanks man.
KeithGS said:
Ok, so it's not just me, good... thanks man.
Click to expand...
Click to collapse
Yes, now there is 3 of us can't switch slots in Twrp. Just have to do it in fastboot for now.
Golf c said:
Yes, now there is 3 of us can't switch slots in Twrp. Just have to do it in fastboot for now.
Click to expand...
Click to collapse
Anything I can do about the EX problem?
KeithGS said:
Anything I can do about the EX problem?
Click to expand...
Click to collapse
Im running Sharkey R2. But Ex flashes the same.
Did you
1. Flash stock boot image
2. Flash Ex
3. Flash Magisk
Golf c said:
Yes, now there is 3 of us can't switch slots in Twrp. Just have to do it in fastboot for now.
Click to expand...
Click to collapse
Add me to the list. Whenever I try to flash xposed, it tries to boot into the last ROM I installed. Would it be worth going back to RC2?
Akomack said:
Add me to the list. Whenever I try to flash xposed, it tries to boot into the last ROM I installed. Would it be worth going back to RC2?
Click to expand...
Click to collapse
Twrp 3.1.1.1 fixes the slot switching. I don't know about your exposed problem.
Golf c said:
Yes, now there is 3 of us can't switch slots in Twrp. Just have to do it in fastboot for now.
Click to expand...
Click to collapse
Golf c said:
Twrp 3.1.1.1 fixes the slot switching. I don't know about your exposed problem.
Click to expand...
Click to collapse
After I posted I was going to try going back to RC2 and noticed that 3.1.1.1 was up. I didn't know of the update. All is well.
After installed xposed, it gave me a twrp bootloop, switched slots in twrp and it works great.
It's really weird, I never noticed an issue with switching slots until I tried a Ground Zero ROM.
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
I use stock recovery and official miui global rom in my phone along with magisk root. Everytime a new update comes i restore stock images from magisk, then apply the update, then again boot into twrp (just boot), flash the magisk and done. That way i maintain the stock recovery, OS, and root as well.
Yesterday i got the official Pie update from Xiaomi, i restored the stock images from magisk, updated to Pie. But now if i try to boot into twrp to flash magisk, it asks for decryption password. My phone is encrypted, from past one year twrp used to work completely fine after i entered the password (encrypted with lock screen pw) but now it says decryption failed. I have tried everything-
1. Removing the lock screen and encryption altogether.
2. Changing the encryption/lock screen pw to pattern/pin/password
But no luck, it says decryption failed. I'm unable to boot into twrp.
Also one weird thing, if i set pattern encryption pw, it asks for alphanumeric pw in twrp decryption screen. And vice versa. I've tried many twrp versions including the latest one. HELP!
Solved by using OrangeFox Recovery (OrangeFox-R9.0-2-whyred-MIUI-Pie.zip) from https://sourceforge.net/projects/orangefox/files/whyred/
Magisk works along with full encryption with lock screen password
Reboot took me to system reboot
avguser23 said:
Also updating twrp works same way
Click to expand...
Click to collapse
Reboot took me to system reboot and phone's stock recovery opened when I went to recovery mode
---------- Post added at 04:48 PM ---------- Previous post was at 04:26 PM ----------
akhu5 said:
Solved by using OrangeFox Recovery (OrangeFox-R9.0-2-whyred-MIUI-Pie.zip) from
Magisk works along with full encryption with lock screen password
Click to expand...
Click to collapse
Also, it would be really helpful, if you told me the steps and precaution to install orangefox, I am wishing to flash pixel experience and use Gcam. But I seem to be stuck in recovery flashing.
Binish Joshi said:
Reboot took me to system reboot and phone's stock recovery opened when I went to recovery mode
---------- Post added at 04:48 PM ---------- Previous post was at 04:26 PM ----------
Also, it would be really helpful, if you told me the steps and precaution to install orangefox, I am wishing to flash pixel experience and use Gcam. But I seem to be stuck in recovery flashing.
Click to expand...
Click to collapse
Cause orange didn't restart into recovery mode and booted into system.
akhu5 said:
Also one weird thing, if i set pattern encryption pw, it asks for alphanumeric pw in twrp decryption screen. And vice versa. I've tried many twrp versions including the latest one. HELP!
Click to expand...
Click to collapse
The dots translate into numbers in the following pattern:
1 2 3
4 5 6
7 8 9
Please note that this is what I read somewhere else when searching for my solution to the original problem (Can't decrypt Pie storage using password from Oreo).
arcanemachine said:
The dots translate into numbers in the following pattern:
1 2 3
4 5 6
7 8 9
Please note that this is what I read somewhere else when searching for my solution to the original problem (Can't decrypt Pie storage using password from Oreo).
Click to expand...
Click to collapse
This didn't work in my case, the only thing that worked was orangefox
Got problem with encryption in TWRP on brand new Mi Max 3 with Pie. I started with twrp-3.2.3-0-nitrogen, which ask about a pass after instalation. In this thread I found so OrangeFox Recovery should solve problem, but - this recovery is in .zip file to flash from recovery, which I did not have... In desperation I flashed twrp-3.3.1-0-nitrogen, and this
works!!