Database Develop

Downgrade OOS 4 to 3.5.4.

Hi everybody,
I have a probleme with my OP3T.
I have upgraded the OS from 3.5.4 to 4, but I don't succed to root the phone, mainly because of the TWRP (flash with 3.0.3.0) that doesn't access to the SD card (twrp asks a password I don't have, so that stay encrypted).
When I try to follow this guide, I always have an error with the recovery stock (recovery downloaded from the oneplus support) during the sideload step (I also try to dowload the rom with twrp, but no success...)
So my question:
Does someone can help me to come back to 3.5.4 until twrp is supported by 4.0 ?
Thank you very much

I'm in the same boat. When sideloading 3.5.3 ota it fails after approximately 45%.

I had the same problem. Steps I did in order to make phone functional:
If you don't have TWRP, you have to install it.
Then, you should wipe your phone entirely from TWRP (Factory Reset, Format Data, Advanced Wipe->Dalvik/ART;System;Data;Internal Storage).
Reset the phone and enter TWRP once again.
Copy the official ZIP with OOS 3.5.x ROM into phone's memory, then flash it.
Flash SuperSU, otherwise your phone won't boot.
I don't take any responsibility, in case you mess something up with your phone.

Okay, my solution was to: 1. boot up in fastboot mode 2. Disable encryption by opening a command prompt in administrater mode and type fastboot format userdata. 3. Install 3.5.3 from Twrp.
Not ideal to disable encryption but now I got a working phone
---------- Post added at 04:59 PM ---------- Previous post was at 04:54 PM ----------
djseban2 said:
I had the same problem. Steps I did in order to make phone functional:
If you don't have TWRP, you have to install it.
Then, you should wipe your phone entirely from TWRP (Factory Reset, Format Data, Advanced Wipe->Dalvik/ART;System;Data;Internal Storage).
Reset the phone and enter TWRP once again.
Copy the official ZIP with OOS 3.5.x ROM into phone's memory, then flash it.
Flash SuperSU, otherwise your phone won't boot.
I don't take any responsibility, in case you mess something up with your phone.
Click to expand...
Click to collapse
Thx. I might have forgotten to reset the phone after wipe, before installing 3.5.4 which is why it wouldn't install even from twrp. My solution worked though - encrypting it again will be for another day. Sick of geeking

So once you have working 3.5.3/4 can you return it to stock - I mean by relocking bootloader and reflashing stock recovery? So then to receive 4.0 via OTA?
Thanks

white43 said:
So once you have working 3.5.3/4 can you return it to stock - I mean by relocking bootloader and reflashing stock recovery? So then to receive 4.0 via OTA?
Thanks
Click to expand...
Click to collapse
Yes, it's entirely possible, but what's the point? You can flash stock recovery->lock bootloader->sideload OOS 4.0, and you are stock . From what I've read, not everyone got 4.0 through OTA yet.

Do you have to be on a specific version of twrp to do this? I cant flash 3.5.4 back using the latest twrp (3031)
EDIT
Never mind all OK, was just begin inpatient

white43 said:
So once you have working 3.5.3/4 can you return it to stock - I mean by relocking bootloader and reflashing stock recovery? So then to receive 4.0 via OTA?
Thanks
Click to expand...
Click to collapse
Do you have a link for the stock 3.5.X recovery? Link from O+ download section won't work..

They provide the so-called Oxygen Stock REC for OP3T here: downloads.oneplus.net/
But I always got different MD5 after downloading the img they provided.

spida_singh said:
Do you have to be on a specific version of twrp to do this? I cant flash 3.5.4 back using the latest twrp (3031)
EDIT
Never mind all OK, was just begin inpatient
Click to expand...
Click to collapse
Hey I am in same boat, does TWRP version matters to return from 4.0.2 to 3.5.3.
I have TWRP(3031) and SU 2.79. I want to revert for battery as well xposed.

uttam.ace said:
Hey I am in same boat, does TWRP version matters to return from 4.0.2 to 3.5.3.
I have TWRP(3031) and SU 2.79. I want to revert for battery as well xposed.
Click to expand...
Click to collapse
It will work with 3.0.3-1 TWRP but you have to flash the ROM twice because of filesystem and put the files twice on the internal memory. Reboot recovery twice forced.
I think TWRP 3.0.4.0 should work better but I do not used it on my phone to restore from 4.0.2 to 3.5.4 so you could try and let us know
---------- Post added at 06:35 PM ---------- Previous post was at 06:32 PM ----------
https://forums.oneplus.net/threads/how-to-restore-to-3-5-4-from-4-0-2-on-op3t.493963/
I made this but you can flash it at your own risk.
To me it worked.
And another tutorial I found but not tried is here https://forum.xda-developers.com/showpost.php?p=70310185&postcount=308

Oneplus 3T downgrade bootloader locked
Hello everyone!
I have a OP3T locked by frp and android nougat oxygen 4.0.3. Is there any solution to downgrade the android to oxygen 3.x??
Thank you guys,
Cheers!

spida_singh said:
Do you have to be on a specific version of twrp to do this? I cant flash 3.5.4 back using the latest twrp (3031)
EDIT
Never mind all OK, was just begin inpatient
Click to expand...
Click to collapse
I tried using TWRP 3.0.4.1,
I was able to flash. thing is, while flashing zip in twrp, it won't show any progress for 2-10 minutes.
then it will show finished flashing
---------- Post added at 07:12 PM ---------- Previous post was at 07:07 PM ----------
I want to share my experience,
Latest TWRP 3.0.4.1 made all difficulty easy,
I was in oxyzen os 4.1.6.
then tried sideload, it fails,
then installed TWRp and flash 3.5.4 via TWRP, (have to flash data,system,cache,internal storage) before flashing,
then it just booted, no issue

Bricked P8 lite 2017

Hello guys,
this is my first thread and I have a serious problem:
First, I unlock the bootloader and flash TWRP on it. It seems working, because every time it's booting there comes a message, that I can't trust this device, cause it's unlocked.
The problem is, when i go in fastboot mode, it says "FRP locked") and in the dev-options I can't change the setting (oem unlock). Now when its connected with PC (fastboot Mode), and I try everytime to flash Data there is this error: "FAILED (remote: Command not allowed)"
So...I format all data with TWRP (no OS anymore). Now I know there is no custom ROM for this device out. I was totally fckd up.
I download the update.zip (Stock Rom update) from another Thread and unpack boot.img, recovery.img and system.img from update.app (cause I don't know how to flash it otherwise).
I tried to flash every 3 img. data with TWRP - only the boot.img and recovery.img was installed. Now my device is Bricked because of Im stupid.
So I can only try to flash data with holding vol+ and vol- and power. I also tried eRecovery, but everytime, I tells me that there was a problem by downloading the package.
The fastboot mode is useless, cause there is this bug (read above).
Can you tell me, is there a method to flash update.zip, or another way, or is this device totally broken?
Thanks!!:crying:

Which firmware you had before brick?

MobileTechArena said:
Which firmware you had before brick?
Click to expand...
Click to collapse
I think it was the EMUI 5.0.1 Version (newest) with Android 7.0

70X1C said:
I think it was the EMUI 5.0.1 Version (newest) with Android 7.0
Click to expand...
Click to collapse
PRA-LX1?

MobileTechArena said:
PRA-LX1?
Click to expand...
Click to collapse
Exacly

70X1C said:
Exacly
Click to expand...
Click to collapse
Download here rescue system file, restore that in TWRP. Then flash stock.boot.img via fastboot flash boot boot.stock.img command , then you can update to B110 OTA.
---------- Post added at 04:18 PM ---------- Previous post was at 04:15 PM ----------
To make TWRP to find rescue files, first backup recovery or something in TWRP, then TWRP will make new folder with backup files that you can raplace with files from rescue system.

MobileTechArena said:
Download here rescue system file, restore that in TWRP. Then flash stock.boot.img via fastboot flash boot boot.stock.img command , then you can update to B110 OTA.
---------- Post added at 04:18 PM ---------- Previous post was at 04:15 PM ----------
To make TWRP to find rescue files, first backup recovery or something in TWRP, then TWRP will make new folder with backup files that you can raplace with files from rescue system.
Click to expand...
Click to collapse
The problem is, that I flash the stock recovery on the device (I have no TWRP anymore)
And there is this problem with fastboot..(read above)

70X1C said:
The problem is, that I flash the stock recovery on the device (I have no TWRP anymore)
And there is this problem with fastboot..(read above)
Click to expand...
Click to collapse
Then try to put UPDATE.APP into dload and do Force update.

70X1C said:
The problem is, that I flash the stock recovery on the device (I have no TWRP anymore)
And there is this problem with fastboot..(read above)
Click to expand...
Click to collapse
Is you FRP locked? Try to unlock bootloader again, fastboot oem unlock "your unlock code". Then try to flash TWRP again. Don't bother with Dload and forced update as that doesn't work.

MobileTechArena said:
Is you FRP locked? Try to unlock bootloader again, fastboot oem unlock "your unlock code". Then try to flash TWRP again. Don't bother with Dload and forced update as that doesn't work.
Click to expand...
Click to collapse
I have no idea of the cause, but dload never worked for me too.

This only works if you can boot to Android and Developer Options menu opens for you (if they don't you'll end up with bricked device).
Boot into the Fastboot mode and relock your device (Command: "fastboot oem relock (unlock code)" ).
Then you'll be able to unlock the OEM Lock from the Developer Options menu. (And after it you can go back to Fastboot and unlock the bootloader again to reinstall the TWRP).

You still need help?

MobileTechArena said:
Download here rescue system file, restore that in TWRP. Then flash stock.boot.img via fastboot flash boot boot.stock.img command , then you can update to B110 OTA.
---------- Post added at 04:18 PM ---------- Previous post was at 04:15 PM ----------
To make TWRP to find rescue files, first backup recovery or something in TWRP, then TWRP will make new folder with backup files that you can raplace with files from rescue system.
Click to expand...
Click to collapse
Where exactly is the rescue system file? I can't seem to find it

theholycutu said:
Where exactly is the rescue system file? I can't seem to find it
Click to expand...
Click to collapse
Looks like they removed it from that site. If i find it somewhere i will share it.
.

MobileTechArena said:
Looks like they removed it from that site. If i find it somewhere i will share it.
.
Click to expand...
Click to collapse
Thanks a lot

theholycutu said:
Where exactly is the rescue system file? I can't seem to find it
Click to expand...
Click to collapse
https://mega.nz/#!k0MzQL5T!yHj-2n9DuGvb-ZdsemOgw4k3vQTMy7CJXIGFAhJlplo
Sorry I have seen the thread just before.
Please let me know when you downloaded it. I'll take it out again.

ChinHon said:
https://mega.nz/#!k0MzQL5T!yHj-2n9DuGvb-ZdsemOgw4k3vQTMy7CJXIGFAhJlplo
Sorry I have seen the thread just before.
Please let me know when you downloaded it. I'll take it out again.
Click to expand...
Click to collapse
I downloaded it thanks a lot

:good:

please help me. i also have a bricked p8 lite 2017. but i can boot into. TWRP,fastboot,system upgrade
---------- Post added at 10:15 PM ---------- Previous post was at 10:08 PM ----------
man i also have a bricked p8 lite 2017, did you solve your problem? help me please

EXE bahotin said:
please help me. i also have a bricked p8 lite 2017. but i can boot into. TWRP,fastboot,system upgrade
---------- Post added at 10:15 PM ---------- Previous post was at 10:08 PM ----------
man i also have a bricked p8 lite 2017, did you solve your problem? help me please
Click to expand...
Click to collapse
I get ERROR: 255 and I have tried a lot of options and still haven't got to any solutions.. still attempting to solve it, too

[GUIDE][GSI]Flashing GSI's with TWRP Fixes and Workarounds

Follow these easy steps
Makes sure you have the GSI image on your sdcard before starting this.
1.Unlock Bootloader
2. Boot into bootloader, check your slot if on B switch to A and vice versa.(fastboot set_active a/b)
3.Download twrp and flash it (fastboot flash boot boot.img)
4.Boot into twrp,Format data or in bootloader run this command "fastboot format userdata" to get rid if encryption else gsi wont boot then go to reboot switch slots to your opposite one, go to "install" navigate to your sdcard where you place the gsi , look for 'select image" then flash your gsi.
5.To flash gapps if your using a aosp gsi go to twrp then go into /wipe/advanced wipe/ select system on the options then "repair or change file system" then press on "resize file system" this will resize your system partiton back to 2.7gigs and allow you to flash gapps.
6.Go back to "reboot" and select the opposite slot that you selected on step 4, then reboot to system ignore the "no system image detected" message
7.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" updated link with .45 update vbeta.img https://www.mediafire.com/file/by0s4xv6op9so0d/vbmeta.img/file
8. Your gsi "should" boot
Group support Zenfone5z GSI:
https://t.me/Zenfone5zGSI
Downloads:
https://forum.xda-developers.com/pr...vice-development/pie-erfan-gsi-ports-t3906486
https://forum.xda-developers.com/project-treble/trebleenabled-device-development AOSP based GSI's
Fixes and WorkArounds
Bluetooth incall audio fix, go to /vendor/etc and delete, a2dp_audio_policy_configuration.xml. and reboot
Volte Fix for GSi credits to rohan and kalish on telegram group
Install the ims.apk(adb push it to /system/app) attached and add this lines to /system/build.prop and reboot
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
For root( magisk) on stock latest .45 pie update and on gsi's flash this patched boot.
https://www.mediafire.com/file/5v40eov7vp320k7/.45patched_boot.img/file

How is this different from other GSI's?

Does anyone of the GSI has VoLTE working.,?

mmahith18 said:
How is this different from other GSI's?
Click to expand...
Click to collapse
These are the ported DSI from various OEMs, for eg. Oxygen OS, H2OS, MIUI, etc.
---------- Post added at 03:07 PM ---------- Previous post was at 03:05 PM ----------
@rafyvitto
Thanks a lot for sharing this XDA thread, can you also mention which GSIs are currently at least booting on Zenfone 5Z? Would really appreciate that.
Thanks though.

hamzain said:
These are the ported DSI from various OEMs, for eg. Oxygen OS, H2OS, MIUI, etc.
---------- Post added at 03:07 PM ---------- Previous post was at 03:05 PM ----------
@rafyvitto
Thanks a lot for sharing this XDA thread, can you also mention which GSIs are currently at least booting on Zenfone 5Z? Would really appreciate that.
Thanks though.
Click to expand...
Click to collapse
To my knowledge and by the guys on the telegram group, oxygen os boots and has some bluetooth issues same with hydrogenOS fyi its one the most stable gsi's from erfan, Pixel beta Q also works but has quite a lot of issues, i havent tested sony/miui or any of the other gsi's sorry.

rafyvitto said:
To my knowledge and by the guys on the telegram group, oxygen os boots and has some bluetooth issues same with hydrogenOS fyi its one the most stable gsi's from erfan, Pixel beta Q also works but has quite a lot of issues, i havent tested sony/miui or any of the other gsi's sorry.
Click to expand...
Click to collapse
Thanks.
I'm sorry, I'm asking too much, is VoLTE working.?

hamzain said:
Thanks.
I'm sorry, I'm asking too much, is VoLTE working.?
Click to expand...
Click to collapse
Yes you need to install the apk and add the build.prop lines in first post.

rafyvitto said:
Yes you need to install the apk and add the build.prop lines in first post.
Click to expand...
Click to collapse
Thanks.
---------- Post added at 07:29 PM ---------- Previous post was at 07:02 PM ----------
rafyvitto said:
Yes you need to install the apk and add the build.prop lines in first post.
Click to expand...
Click to collapse
One more question, Hdrfix.zip has to be flashed only for OOS or for any GSI?

hamzain said:
Thanks.
---------- Post added at 07:29 PM ---------- Previous post was at 07:02 PM ----------
One more question, Hdrfix.zip has to be flashed only for OOS or for any GSI?
Click to expand...
Click to collapse
Only for hydrogen/OSS as i stated in first post correct.

Here you can find the latest updates on efrans gsi's https://build.lolinet.com/file/GSI/ , the post he made on treble forum dosnt have the latest gsi's.

rafyvitto said:
Only for hydrogen/OSS as i stated in first post correct.
Click to expand...
Click to collapse
Thanks, I will get back with the reviews.

Ok.
So today being a holiday, gave hefty 10 hours to try every single GSI mentioned in this thread. And here are my findings:
1. MIUI port - Boots, buttery smooth, no mobile data or VoLTE, as mentioned in the OP, ims.apk doesn't get installed, hence unusable.
2. OOS port - Bootloops, tried multiple times, no success.
3. One UI - Unable to flash the image, says unable to write in the system partition.
4. Xperia Port - Again, boot loop.
5. HOS - Unable to boot.
Did not try Android Q.
One more thing, as per the instruction, when I try to 'Format Data' through TWRP, it says unable to erase data, data partition busy.
I followed step by step for all the mentioned ROMs, can someone help me?
Also, ims.apk is uninstallable, tried many times.

hamzain said:
Ok.
So today being a holiday, gave hefty 10 hours to try every single GSI mentioned in this thread. And here are my findings:
1. MIUI port - Boots, buttery smooth, no mobile data or VoLTE, as mentioned in the OP, ims.apk doesn't get installed, hence unusable.
2. OOS port - Bootloops, tried multiple times, no success.
3. One UI - Unable to flash the image, says unable to write in the system partition.
4. Xperia Port - Again, boot loop.
5. HOS - Unable to boot.
Did not try Android Q.
One more thing, as per the instruction, when I try to 'Format Data' through TWRP, it says unable to erase data, data partition busy.
I followed step by step for all the mentioned ROMs, can someone help me?
Also, ims.apk is uninstallable, tried many times.
Click to expand...
Click to collapse
1. The app has to be pushed to /system/app should work that way.
2. You should be able to wipe data if you go to bootloader switch to slot were trwp is not installed then switch back to were it IS installed then boot twrp and wipe data, thats what i do and it works.
3. Try the updated gsi's from the link i posted a few post back.

Also, i added lates .45 vbeta.img and patched boot.img for root on first post, enjoy guys.

rafyvitto said:
Also, i added lates .45 vbeta.img and patched boot.img for root on first post, enjoy guys.
Click to expand...
Click to collapse
I tried so many times, but the results are unchanged, only MIUI boots.
But when I pushed the ims.apk and added the lines to build.prop it got stuck at bootloop.
I tried everything, I just need OOS to boot.
Also, one more thing I noticed is, MIUI boots only when I don't flash permissive2.zip, when I flash this zip even MIUI fails to boot
---------- Post added at 02:01 PM ---------- Previous post was at 02:01 PM ----------
rafyvitto said:
Also, i added lates .45 vbeta.img and patched boot.img for root on first post, enjoy guys.
Click to expand...
Click to collapse
I donwloaded all the newest GSIs and followed the instructions properly.
---------- Post added at 02:02 PM ---------- Previous post was at 02:01 PM ----------
rafyvitto said:
1. The app has to be pushed to /system/app should work that way.
2. You should be able to wipe data if you go to bootloader switch to slot were trwp is not installed then switch back to were it IS installed then boot twrp and wipe data, thats what i do and it works.
3. Try the updated gsi's from the link i posted a few post back.
Click to expand...
Click to collapse
And I also did the slot switching, but 'Format Data' still says 'Failed to mount /data, partition busy'

https://sourceforge.net/projects/mactavishao-builds/ found more oem framework gsi's havent had time to flash any yet.

rafyvitto said:
https://sourceforge.net/projects/mactavishao-builds/ found more oem framework gsi's havent had time to flash any yet.
Click to expand...
Click to collapse
Excellent keep up the good work

Added, use "fastboot format userdata" in bootloader, to the steps in case formatting data does not work in twrp.

rafyvitto said:
Added, use "fastboot format userdata" in bootloader, to the steps in case formatting data does not work in twrp.
Click to expand...
Click to collapse
Which is the most stable as of now?... Can't be stable as stuck but best to it

rafyvitto said:
Added, use "fastboot format userdata" in bootloader, to the steps in case formatting data does not work in twrp.
Click to expand...
Click to collapse
Thanks.

October update is out - QP1A.190711.148

October 2019 Release | Q 10 - Q Release 2 - QP1A.190711.148 | Open Market
https://www.essential.com/developer/current-builds

chanh2018 said:
October 2019 Release | Q 10 - Q Release 2 - QP1A.190711.148 | Open Market
https://www.essential.com/developer/current-builds
Click to expand...
Click to collapse
Won't root for me.

you mean magisk not working with this build?

mcdull said:
you mean magisk not working with this build?
Click to expand...
Click to collapse
No, it's not working for ME.
Sent from my PH-1 using XDA Labs

avd said:
Won't root for me.
Click to expand...
Click to collapse
Were you able to root the previous 10 build? I have the 148 rooted with Magisk canary, same as the previous two builds (just root, no TWRP). Not sure if it makes a difference, but I don't do OTA updates. I always download and flash the OTA image in adb sideload, then flash the patched boot.img in fastboot.

kt-Froggy said:
Were you able to root the previous 10 build? I have the 148 rooted with Magisk canary, same as the previous two builds (just root, no TWRP). Not sure if it makes a difference, but I don't do OTA updates. I always download and flash the OTA image in adb sideload, then flash the patched boot.img in fastboot.
Click to expand...
Click to collapse
oh cool, so flashing boot images work with the latest canary of MM?! will do that then this evening as well :fingers-crossed:

JimmyCash030 said:
oh cool, so flashing boot images work with the latest canary of MM?! will do that then this evening as well :fingers-crossed:
Click to expand...
Click to collapse
Yes, it does work for me. I've always been doing updates like this, on 9 and 10. Download both OTA and the full image, extract boot.img from the full image, patch it with Magisk, then sideload OTA image in adb, reboot, and finally fastboot flash the patched boot.img. Never had a problem. The only thing is that you have to use Magisk canary build with 10; stable or beta doesn't work.

kt-Froggy said:
Yes, it does work for me. I've always been doing updates like this, on 9 and 10. Download both OTA and the full image, extract boot.img from the full image, patch it with Magisk, then sideload OTA image in adb, reboot, and finally fastboot flash the patched boot.img. Never had a problem. The only thing is that you have to use Magisk canary build with 10; stable or beta doesn't work.
Click to expand...
Click to collapse
yeah worked for me as well with the latest canary MM !!

Magisk 19.4 works just fine on latest 148 build if need be I can upload magisk rooted boot. Img

https://www.androidfilehost.com/?fid=1899786940962605417
MD5:49484e6733bba257051eef831eb25689
This is for QP1A.19711.148
Magisk-Patched-Boot.img

allenjthomsen said:
https://www.androidfilehost.com/?fid=1899786940962605417
MD5:49484e6733bba257051eef831eb25689
This is for QP1A.19711.148
Magisk-Patched-Boot.img
Click to expand...
Click to collapse
getting back to the topic at hand, I flashed this, then TWRP on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now I got to plug this in and swap slots to reinstall TWRP.
Is possible that magisk and twrp are back to not playing nice to each other again?
(I'll test this out if I get a chance to swap slots)
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
avd said:
getting back to the topic at hand, i flashed this, then twrp on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now i got to plug this in and swap slots to reinstall twrp.
Is possible that magisk and twrp are back to not playing nice to each other again?
(i'll test this out if i get a chance to swap slots)
Click to expand...
Click to collapse
now i'm just sitting here looking at the boot animation. Will let it go a little further to see if it starts.

Honestly i couldnt tell you i only rooted havent used twrp much yet because of the lack of android 10 custom roms havent seen a need to use it as of yet.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
And any further information on this would be great.

allenjthomsen said:
Honestly i couldnt tell you i only rooted havent used twrp much yet because of the lack of android 10 custom roms havent seen a need to use it as of yet.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
And any further information on this would be great.
Click to expand...
Click to collapse
pretty much everything for this phone resides in t.me/ESSENTIALPH1DEV

avd said:
getting back to the topic at hand, I flashed this, then TWRP on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now I got to plug this in and swap slots to reinstall TWRP.
Is possible that magisk and twrp are back to not playing nice to each other again?
(I'll test this out if I get a chance to swap slots)
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
now i'm just sitting here looking at the boot animation. Will let it go a little further to see if it starts.
Click to expand...
Click to collapse
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again

rignfool said:
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
Click to expand...
Click to collapse
Flashing the patched image provided just sits there looking at the boot animation.
I'll play with it tonight.
It's a Sprint phone. Could that be the issue?
Sent from my PH-1 using XDA Labs

I flashed September build like this no problem however when I try and adb the October build I cannot get into recovery, when trying it just boots back into system however I can get into fastboot, any ideas?

I'm no expert but did this ans it worked:
1. In TWRP recovery (created nandroid and wiped cache)
2. Flashed full update zip from official download link, then TWRP, then wipe cache
3. Reboot system and let it settle
4. Reboot into TRWP and flashed Canary Channel zip file
5. Wipe cache
6. Reboot system
Hope this helps.

jionny said:
I flashed September build like this no problem however when I try and adb the October build I cannot get into recovery, when trying it just boots back into system however I can get into fastboot, any ideas?
Click to expand...
Click to collapse
Try using the fastboot image (not the OTA the image one) from the essential site.
Download it, remove the "fastboot or something wipe userdata maybe?" line from the flashall.bat script (or from flashall.sh if you're on Mac/Linux)
Then run the flashall.bat or flashall.sh script (again .bat for Win, .sh for the rest)
Should get you working again, albeit without root & twrp
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
rignfool said:
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
Click to expand...
Click to collapse
? I always have trouble remembering, not anymore it seems

gavinfernandes2012 said:
Try using the fastboot image (not the OTA the image one) from the essential site.
Download it, remove the "fastboot or something wipe userdata maybe?" line from the flashall.bat script (or from flashall.sh if you're on Mac/Linux)
Then run the flashall.bat or flashall.sh script (again .bat for Win, .sh for the rest)
Should get you working again, albeit without root & twrp
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
I always have trouble remembering, not anymore it seems
Click to expand...
Click to collapse
Are you able to give more precise instructions on fastboot instructions?

jionny said:
Are you able to give more precise instructions on fastboot instructions?
Click to expand...
Click to collapse
Nevermind, got the instructions from essentials site. flashed via fastboot which erased everything had to do a complete setup again

Flashing Magisk v20 bootloops to recovery

Hello,
I attempted to root my Mi CC9 / 9 Lite and currently have a bootloop.
What I did:
-Flash TWRP from fastboot (success)
-Boot into TWRP (success)
-Wipe / Factory reset (success)
-Flashing Magisk v20 zip file (success)
-Then, reboot system sends me to TWRP again.
What I tried:
-The phone is not bricked. When I factory reset again from TWRP and boot to system, it boots up.
-Signing the boot image after flashing magisk using the zip file here (This did not work. Flashing the zip file returned a verification error)
Not quite sure how to root my phone at this point. Any help would be much appreciated. Thank you.

You need the Enable encryption zip...it will boot it up.. boot loop is cause from MIUI trying to encrypted and failing.
Flash the zip in this thread... go to the fstab zip that will help you
https://forum.xda-developers.com/mi-cc9/development/recovery-twrp-pyxis-unofficial-t3990493

[email protected] said:
You need the Enable encryption zip...it will boot it up.. boot loop is cause from MIUI trying to encrypted and failing.
Flash the zip in this thread... go to the fstab zip that will help you
https://forum.xda-developers.com/mi-cc9/development/recovery-twrp-pyxis-unofficial-t3990493
Click to expand...
Click to collapse
Where do I find it?

dupreme said:
Where do I find it?
Click to expand...
Click to collapse
Direct link from OP.
https://www.mediafire.com/folder/zqk7a9qj5ltyd/Mi 9 Lite (pyxis)

[email protected] said:
Direct link from OP.
https://www.mediafire.com/folder/zqk7a9qj5ltyd/Mi 9 Lite (pyxis)
Click to expand...
Click to collapse
Thank you. I tried flashing the fstab zip after flashing magisk and it did not change the situation. Shall I first flash the auto-decrypt TWRP img and then try again?

dupreme said:
Thank you. I tried flashing the fstab zip after flashing magisk and it did not change the situation. Shall I first flash the auto-decrypt TWRP img and then try again?
Click to expand...
Click to collapse
What I do is this: I Boot in recovery and format data then I go to advance wipe and select data and then repair and select ext4 and swipe and then reboot recovery and flash the MIUI rom and then I reboot the recovery and mount system and vendor and flash the zip and then reboot and wait for it... you know it will boot up because after it boots up the bootanimation increases it's light before the actual booting in the system and the rest you can figure out... hope this helps you out.

[email protected] said:
What I do is this: I Boot in recovery and format data then I go to advance wipe and select data and then repair and select ext4 and swipe and then reboot recovery and flash the MIUI rom and then I reboot the recovery and mount system and vendor and flash the zip and then reboot and wait for it... you know it will boot up because after it boots up the bootanimation increases it's light before the actual booting in the system and the rest you can figure out... hope this helps you out.
Click to expand...
Click to collapse
I'll try that. Thanks a lot. Do you use the auto-decrypt (the one you linked) TWRP in this, or just regular TWRP. I am using just the pyxis TWRP.

Can anyone elaborate on what needs to be done? The previous responses did not explain how to ROOT the phone.
What I have just tried:
-flashed the TWRP img here
-did a wipe
-sent Magisk and the fstab zips to storage and flashed them (fstab first)
still gives bootloop to recovery. How to root this phone?
Thank you

dupreme said:
Can anyone elaborate on what needs to be done? The previous responses did not explain how to ROOT the phone.
What I have just tried:
-flashed the TWRP img here
-did a wipe
-sent Magisk and the fstab zips to storage and flashed them (fstab first)
still gives bootloop to recovery. How to root this phone?
Thank you
Click to expand...
Click to collapse
After you unlock the bootloader I just put it in fastboot mode and fastboot boot "(whatever you have it called... I renamed it recovery) recovery.img and then press the volume up button and then I install the image through TWRP and reboot recovery and then follow the steps.
---------- Post added at 04:07 PM ---------- Previous post was at 04:06 PM ----------
dupreme said:
I'll try that. Thanks a lot. Do you use the auto-decrypt (the one you linked) TWRP in this, or just regular TWRP. I am using just the pyxis TWRP.
Click to expand...
Click to collapse
I used the TWRP for the team win recovery project website.
---------- Post added at 04:25 PM ---------- Previous post was at 04:07 PM ----------
dupreme said:
Can anyone elaborate on what needs to be done? The previous responses did not explain how to ROOT the phone.
What I have just tried:
-flashed the TWRP img here
-did a wipe
-sent Magisk and the fstab zips to storage and flashed them (fstab first)
still gives bootloop to recovery. How to root this phone?
Thank you
Click to expand...
Click to collapse
Fstab zip is last because it's the encryption fix

[email protected] said:
After you unlock the bootloader I just put it in fastboot mode and fastboot boot "(whatever you have it called... I renamed it recovery) recovery.img and then press the volume up button and then I install the image through TWRP and reboot recovery and then follow the steps.
---------- Post added at 04:07 PM ---------- Previous post was at 04:06 PM ----------
I used the TWRP for the team win recovery project website.
---------- Post added at 04:25 PM ---------- Previous post was at 04:07 PM ----------
Fstab zip is last because it's the encryption fix
Click to expand...
Click to collapse
I tried a combination of what you suggested and this guide and the phone booted up with root. However, opening the Magisk manager immediately says "your device needs additional setup" or something similar, and asks to flash a zip file. When I select flash, it says rebooting in 5 sec and stays in bootloop. Have you come across this?

use twrp by brigudav. It has also s built-in Magisk installer.

JimmyBondi said:
use twrp by brigudav. It has also s built-in Magisk installer.
Click to expand...
Click to collapse
Can you share a link? I could not find an XDA thread. Thank you.

dupreme said:
I tried a combination of what you suggested and this guide and the phone booted up with root. However, opening the Magisk manager immediately says "your device needs additional setup" or something similar, and asks to flash a zip file. When I select flash, it says rebooting in 5 sec and stays in bootloop. Have you come across this?
Click to expand...
Click to collapse
TBH no because as Soon as I got TWRP I flash another rom Mi Globe rom to be exact and use the method I posted.