Related
So.... Pokemon Go has a lot to answer for......
I have run into a really strange problem when trying to install an OTA on my *unrooted* Oneplus 2. I have been trying to fix this for days but I have completely run out of ideas.
I originally had a working stock Oxygen 3 (Marshmallow) rom with TWRP recovery on my device (not sure of the version). The device was rooted and apart from not being able to install OTAs, I was fairly happy with the setup. Then along came the Pokemon GO update that banned rooted devices. Ok, "big deal" I thought. I was quite content playing Ingress instead (a far better game by the way that doesn't rely on a "pay to win" structure). I really wasn't too worried but then I found out about "systemless root" and "Magisk". I thought that if I installed this correctly I could still play a bit of Pokemon GO when I wanted to and could toggle a root button in Magisk Manager to install OTAs when they became available.
This is where the problems started.
I followed a guide on how to unroot and install Magisk and "Phh's Superuser". The problem was that the Phh Superuser was being denied permissions for Magisk Manager, there were no pop up notifications prompting me to give it access, just toast notifications. I couldn't for the life of me figure out how to give it permission so the "enable root" slider button kept sliding back, not allowing root. This is when I used SuperSU ver 2.76 (Magisk version) and it seemed to work fine. I now had a stock Marshmallow rom with TWRP and Magisk Manager all working exactly how they should be. I could toggle root and play Pokemon GO, then return to a rooted state when I needed to.
"Awesome, mission accomplished." I thought. Now I just need to toggle root off, download the latest OTA and install it through Flashfire.
First I made a complete nandroid backup (as I've done with other devices many times before) through TWRP. I even copied the backup folder to my PC in case something went wrong.
Well, this is when the nightmare started.
The first mistake I made was to use Flashfire when it clearly stated that Oneplus devices were currently untested. Not sure if it was a big issue or not, but it was a mistake none the less. The second mistake I made was to not stop the stock recovery being replaced when prompted before the reboot. I assumed (and it even states in the app) that the custom recovery should be reverted back to the stock recovery when attempting to apply OTA updates.
So I went ahead and rebooted, waiting for the OTA to install. I'm fairly sure from memory that it went into the stock recovery, flashed the OTA and restarted.
This is when the phone soft bricked.
"Oh well, that is why I made the backup." I thought.
I reflashed TWRP in fastboot mode and attempted to restore my backup. No dice, the phone was still soft bricked.
(And by "soft bricked" and "boot looping" I mean the Oneplus logo was in the middle of the screen, "Powered by Android" was at the bottom and the two blue LEDs for the buttons either side of the fingerprint scanner/home button remained on. This for me was the tell tale sign of the soft brick because these two light go off after a few seconds after rebooting usually.
So from here I have tried EVERYTHING. All I really want now is a working stock (rooted) Marshmallow rom with TWRP. I have downloaded many different full rom zips and attempted to flash them through TWRP with no success, I have returned to stock recovery and tried flashing signed roms with no success, I've even tried flashing the official CM13 rom for Oneplus 2 (with the correct GAPPs and kernel) through TWRP with no luck.
But here is where it gets interesting......
There are a few things that are really weird...
1. I have always been able to get into Fastboot mode and ADB and Fastboot commands "work".
* Operations succeed but don't stick (for example trying to flash TWRP versions 3.0.2-1 and 3.0.2-2 through Fastboot mode result in no recovery being there at all.
2. I can flash TWRP recovery though Fastboot mode but ONLY VERSIONS 3.0.2-0 and lower. I can also successfully flash the stock recovery.
3. I can flash OxygenOS 2.2.1 but NOT ANY VERSION RELEASED AFTER THAT. Doing so results in the soft brick "bootloop" I mentioned earlier.
4. Attempting to flash the official CM13 rom for Oneplus 2 doesn't work either. Originally I got the error 7 message, but after editing "Updater-script" in the rom and re-zipping, the process seemed to work fine in TWRP but the reboot gave me... you guessed it... a softbrick.
I have flashed custom roms on a few different devices before so I'm not a COMPLETE newbie when it comes to this stuff, but I am by no means a developer or even anything close to one. I have bricked this phone in the past (long story, involved getting it without an invite and it being shipped to me with spyware on it) but I used a guide very similar to this and it worked a treat.
www(dot)androidbrick(dot)com/unbrick-oneplus-one-two-3-qualcomm-hs-usb-qdloader-9008
So, thinking that this process would format all partitions and start me from scatch I tried it. It worked fine but I was still unable to upgrade from Oxygen OS 2.2.1 or install TWRP versions 3.0.2-1 or 3.0.2-2.
I have tried all sorts of things. I have wiped, flashed and wiped again. Factory resets, dirty flashes, clean flashes.... everything. All sorts of different sources for the TWRP images and Oxygen roms... nothing seems to work.
It's just so weird considering it's not a hard brick... just a soft brick.
So I really need my phone so I am sitting on this current build because it is the only one that works.
Here are some details of the current build I am using. (using CPU-Z app)
Model: Oneplus 2 (ONE A2001)
Android version: 5.1.1
Oxygen OS version: 2.2.1
Bootloader: Unknown
Build ID: ONE A2001_14_160226
Java VM: ART 2.1.0
OpenGL ES: 3.1
Kernel Architecture: aarch64
Kernel version: 3.10.49-perf+ (56)
Root access: Yes
Super user app: SuperSU Free v2.46 (Chainfire)
OEM unlocking: Enabled
USB debugging: Enabled
And these are some of the ZIPs and IMGs that refuse to be flashed to my device.
TWRP-3.0.2-1-oneplus2
TWRP-3.0.2-2-oneplus2
Grarak's TWRP recovery IMG for Oneplus2 (modified to install CM13) according to this guide:
missingtricks(dot)net/oneplus-2-official-cyanogenmod-13
cm-13.0-20160924-NIGHTLY-oneplus2
OnePlus2Oxygen_14_OTA_019_all_1606041303_bd42fc5cc5cc4ab2
And also my TWRP backup named 2016-09-16--09-44-09
I am really at a loss as to what to do next. ANY help ANYONE could give me would be greatly appreciated. I have been all over the net looking for ways around this bt have had no luck.
As I've said, I'm not a huge tech head, but I'm not a newbie either. The only thing I can think of is that somehow one of the partitions (maybe boot? ) may have been corrupted somehow when messing around with systemless root. But I don't know how considering it's "systemless". If anyone knows how to check for corrupted partitions on the Oneplus 2 please let me know and I'll try it. Maybe formatting these partitions might help (????), but I don't want to permanently brick my phone.
But I don't know how I've got this particular build working if one of the partitions has been corrupted. And the corrupted partition thing is just a guess.....
Please, anyone, someone point me in the right direction. Again, any and all feddback is welcomed and would be very much appreciated.
This is all Pikachu's fault.
Kamakiriash said:
A very long post...
Click to expand...
Click to collapse
The normal way too update from OOS 2 to OOS 3 is:
Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
Reboot recovery via TWRP so that you now have a recovery that's compatible with the new bootloader
Wipe data, cache & dalvik-cache (but not internal storage)
Flash the OOS 3 signed flashable zip again to update the system
Flash one of the modified SuperSU zips if you want root
Reboot system
All the files you need are in post #1 of this thread.
Thank you so much Spannaa!
I was clearly missing a vital step here and let it be a lesson to anyone else in this situation....
As Spannaa said......
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
4. Wipe data, cache & dalvik-cache (but not internal storage)
5. Flash the OOS 3 signed flashable zip AGAIN to update the system.
Again, thankyou Spanna for your quick and accurate response.
The order in which you flash zips and imgs is very important it seems.
You really saved me.
I restored the TWRP backup and I am back to where I started.
Is it now possible to apply OTAs when I toggle the root off in Magisk manager and install using the stock recovery? What do you think would be the best way to do this?
And would it be worth moving to the official build of CM13 for Oneplus 2?
Thanks again, Spannaa. :victory:
Kamakiriash said:
Thank you so much Spannaa!
I was clearly missing a vital step here and let it be a lesson to anyone else in this situation....
As Spannaa said......
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
4. Wipe data, cache & dalvik-cache (but not internal storage)
5. Flash the OOS 3 signed flashable zip AGAIN to update the system.
Again, thankyou Spanna for your quick and accurate response.
The order in which you flash zips and imgs is very important it seems.
You really saved me.
I restored the TWRP backup and I am back to where I started.
Is it now possible to apply OTAs when I toggle the root off in Magisk manager and install using the stock recovery? What do you think would be the best way to do this?
And would it be worth moving to the official build of CM13 for Oneplus 2?
Thanks again, Spannaa. :victory:
Click to expand...
Click to collapse
Glad you're sorted.
Not sure about Magisk as I've never used it.
CM13 is OK but whether it's worth you moving to it is your choice. Personally, I prefer TipsyOS!
Hi,
I face the exact issue with same Oxygen OS and TWRP versions mentioned, I have tried the above steps but there are some problems:
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
Click to expand...
Click to collapse
when I checked the option (Zip signature verification) in TWRP, the installation failed with error "Zip signature verification failed! Error installing zip file '/sdcard/oneplus.zip'", but it's successfully installed when I unchecked (Zip signature verification) option.
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
Click to expand...
Click to collapse
second problem is that after installing the TWRP 3.0.2-2 (or above), then reboot recovery, I can't access the recovery again and the phone stuck on bootloop.
any idea ?
Aood said:
Hi,
I face the exact issue with same Oxygen OS and TWRP versions mentioned, I have tried the above steps but there are some problems:
when I checked the option (Zip signature verification) in TWRP, the installation failed with error "Zip signature verification failed! Error installing zip file '/sdcard/oneplus.zip'", but it's successfully installed when I unchecked (Zip signature verification) option.
second problem is that after installing the TWRP 3.0.2-2 (or above), then reboot recovery, I can't access the recovery again and the phone stuck on bootloop.
any idea ?
Click to expand...
Click to collapse
I don't have a OP2 anymore but that post was seven months ago and the instructions worked for numerous users.
Don't enable zip signature verification in TWRP - it's unnecessary.
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option and then reboot recovery directly from TWRP.
thanx for replay Spannaa,
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option and then reboot recovery directly from TWRP.
Click to expand...
Click to collapse
I have already did that, but same issue once I reboot "directly from TWRP" , the TWRP doesn't show up and bootloop start again.
Aood said:
thanx for replay Spannaa,
I have already did that, but same issue once I reboot "directly from TWRP" , the TWRP doesn't show up and bootloop start again.
Click to expand...
Click to collapse
Last chance and then I'll leave this for someone that has the OP2.
Are you rebooting recovery "directly from TWRP" or rebooting system?
Is your bootloader still unlocked?
Last chance and then I'll leave this for someone that has the OP2.
Are you rebooting recovery "directly from TWRP" or rebooting system?
Is your bootloader still unlocked?
Click to expand...
Click to collapse
Yes, rebooting recovery "directly from TWRP"
and bootloader loader is unlocked,..
anyway it's not important to fix the phone, it's almost one year since last time I use it, yesterday I saw it in the drawer and try to figure out the issue..,
Hi,
I've downgraded my phone ZE520KL couple months ago but I've forgotten that VOLTE is only available on 7.0...
I've recieved the OTA notification, downloaded the package on the phone, but when it reboots it is going on TWRP & then if I'm rebooting it doesn't continue the upgrade process.
What am I missing? (on my previous phones this wasn't so tricky...) Should I use the Install method directly from TWRP? If Yes on which zip? Is it possible to find the one that I've downloaded directly with my phone?
bibile said:
Hi,
I've downgraded my phone ZE520KL couple months ago but I've forgotten that VOLTE is only available on 7.0...
I've recieved the OTA notification, downloaded the package on the phone, but when it reboots it is going on TWRP & then if I'm rebooting it doesn't continue the upgrade process.
What am I missing? (on my previous phones this wasn't so tricky...) Should I use the Install method directly from TWRP? If Yes on which zip? Is it possible to find the one that I've downloaded directly with my phone?
Click to expand...
Click to collapse
Same like me before. Have you rooted your phone yet? if yes then try this, it work for me though (Backup your phone is recommended)
1. Download busybox, supersu and no-verity file
2. Using flashfire app, choose flash zip or ota option
3. Add ota 'WW-ZE520Kl-.....'
4. Add firmware 'UL-ASUS-....'
5. Remove tickmark from 'Inject supersu'
And flash, it will reboot but do not boot to system. You must boot to twrp, flash no-verity file, busybox and supersu or your phone will not boot. Then reboot, done.
If this method is helpful, do reply to me
Btw, sorry for my poor english.
[email protected]@ said:
Same like me before. Have you rooted your phone yet? if yes then try this, it work for me though (Backup your phone is recommended)
1. Download busybox, supersu and no-verity file
2. Using flashfire app, choose flash zip or ota option
3. Add ota 'WW-ZE520Kl-.....'
4. Add firmware 'UL-ASUS-....'
5. Remove tickmark from 'Inject supersu'
And flash, it will reboot but do not boot to system. You must boot to twrp, flash no-verity file, busybox and supersu or your phone will not boot. Then reboot, done.
If this method is helpful, do reply to me
Btw, sorry for my poor english.
Click to expand...
Click to collapse
Thanks, works wonderfully! Flashfire flashed the new OTAs successfully but the phone didn't then boot (or it bootlooped). A quick Google search led me to your response and the dm-verity file fixed the boot!
I also didn't flash Busybox in case you needed to know and before flashing the OTAs I checked the "Automount" and "Mount systeam as R/W" in Flashfire otherwise the app would just get stuck in a blank screen.
EDIT: WiFI isn't working, tried already deleting the files in /data/misc/wifi, /persist and /data/misc/dhcp as suggested in various threads but still nothing. Anyone know how to fix it before I attempt to do a full backup and wipe?
vEEGAZ said:
Thanks, works wonderfully! Flashfire flashed the new OTAs successfully but the phone didn't then boot (or it bootlooped). A quick Google search led me to your response and the dm-verity file fixed the boot!
I also didn't flash Busybox in case you needed to know and before flashing the OTAs I checked the "Automount" and "Mount systeam as R/W" in Flashfire otherwise the app would just get stuck in a blank screen.
EDIT: WiFI isn't working, tried already deleting the files in /data/misc/wifi, /persist and /data/misc/dhcp as suggested in various threads but still nothing. Anyone know how to fix it before I attempt to do a full backup and wipe?
Click to expand...
Click to collapse
Deleting files in /data/misc is not helped. Try this:
1. Check your selinux permissive or enforcing. If permissive, you should re-root your phone. Remember to flash busybox too or it will may some crash. Still not working follow step 2.
2. Re-flash the ROM using twrp. No data will be lost. Don't forget to re-root or it will not boot.
3. Try the lastest fw .68 or .75 though someone told that the .28 ota file had issue on wifi.
[email protected]@ said:
Deleting files in /data/misc is not helped. Try this:
1. Check your selinux permissive or enforcing. If permissive, you should re-root your phone. Remember to flash busybox too or it will may some crash. Still not working follow step 2.
2. Re-flash the ROM using twrp. No data will be lost. Don't forget to re-root or it will not boot.
3. Try the lastest fw .68 or .75 though someone told that the .28 ota file had issue on wifi.
Click to expand...
Click to collapse
Reflashing through TWRP worked Although I did it after backing up all the apps and did a factory reset which didn't even fix the wi-fi problem. But then Flashfire is useless if TWRP is capable of flashing OTAs right?
vEEGAZ said:
Reflashing through TWRP worked Although I did it after backing up all the apps and did a factory reset which didn't even fix the wi-fi problem. But then Flashfire is useless if TWRP is capable of flashing OTAs right?
Click to expand...
Click to collapse
Not really. Since OTA file can't flash through twrp. It really annoying for someone (like me ), so for the easiest way is just flash it using Flashfire, no need to use computer to flash stock recovery .
@vEEGAZ
yep, that's what I've been saying for months. I've never used anything but TWRP to flash my phone. I've downgraded, gone custom and back to stock many times.
@[email protected]@
I flash OTA's through TWRP every time there's an update.
wang1chung said:
@vEEGAZ
yep, that's what I've been saying for months. I've never used anything but TWRP to flash my phone. I've downgraded, gone custom and back to stock many times.
@[email protected]@
I flash OTA's through TWRP everything there's an update.
Click to expand...
Click to collapse
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
[email protected]@ said:
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
Click to expand...
Click to collapse
edit your updater-script and it'll flash no problem.
[email protected]@ said:
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
Click to expand...
Click to collapse
Yeah that's what I encountered aswell back 2-3 years ago, I remember I couldn't flash any OTAs via TWRP but apparently now you can. That's why I also used Flashfire in the first place but after running out of all options for the wi-fi problem I decided to give TWRP a try et voilà, it worked
wang1chung said:
edit your updater-script and it'll flash no problem.
Click to expand...
Click to collapse
I've tried that and still not working.
@[email protected]@
I JUST did it....on 1711.75 now. There was no recovery partition update either so I didn't have to reflash TWRP after :good:
I did have a bootloop issue after but fixed that by flashing the no-verity file. I'm not sure if that's related to having magisk installed though.
wang1chung said:
@[email protected]@
I JUST did it....on 1711.75 now. There was no recovery partition update either so I didn't have to reflash TWRP after :good:
I did have a bootloop issue after but fixed that by flashing the no-verity file. I'm not sure if that's related to having magisk installed though.
Click to expand...
Click to collapse
1. After reflashing rom through twrp, i lost my twrp. Oh, but when i use Flasfire, it isn't lost.
2. Not sure but after flashing ROM your boot will change to normal so it may not related to magisk or supersu. Maybe it beacause of the twrp, i've tried reflash stock recovery once and i can updated it without flash no-verity file though i've installed magisk.
[email protected]@ said:
1. After reflashing rom through twrp, i lost my twrp. Oh, but when i use Flasfire, it isn't lost.
2. Not sure but after flashing ROM your boot will change to normal so it may not related to magisk or supersu. Maybe it beacause of the twrp, i've tried reflash stock recovery once and i can updated it without flash no-verity file though i've installed magisk.
Click to expand...
Click to collapse
1. You will only lose TWRP if there is a recovery partition update in the stock firmware, yes, but that doesn't happen with every update. I think I read of a way to block it from updating the recovery partition but can't find the article right now. If flashfire works, use it, I just like TWRP for the other features like making and restoring nandroid backups.
2. I dirty flashed the update again through TWRP, verified the bootloop issue and then installed magisk (through TWRP) and it resolved the bootloop issue. No-verify file not required.
wang1chung said:
1. You will only lose TWRP if there is a recovery partition update in the stock firmware, yes, but that doesn't happen with every update. I think I read of a way to block it from updating the recovery partition but can't find the article right now. If flashfire works, use it, I just like TWRP for the other features like making and restoring nandroid backups.
2. I dirty flashed the update again through TWRP, verified the bootloop issue and then installed magisk (through TWRP) and it resolved the bootloop issue. No-verify file not required.
Click to expand...
Click to collapse
1.Ok, i got it.
2. The way using TWRP is keep the root ( root or not boot) and stock recovery is contrary ( can't root but will boot) or just flash custom kernel through twrp (not root required).
simple question :
- you are talking about OTA & Firmware...
I've downloaded again from asus website Version WW-V14.2020.1711.75 (I assume it is the latest firmware). Are you simply giving the example of an OTA that is released post the firmware version I have to install to have the 7.0 base?
Or is it anything that I'm missing...
From your explanations I should only :
- install flashfire
- flash the latest firmware
- boot into TWRP & flash no verity
- reboot the system
Right?
bibile said:
simple question :
- you are talking about OTA & Firmware...
I've downloaded again from asus website Version WW-V14.2020.1711.75 (I assume it is the latest firmware). Are you simply giving the example of an OTA that is released post the firmware version I have to install to have the 7.0 base?
Or is it anything that I'm missing...
From your explanations I should only :
- install flashfire
- flash the latest firmware
- boot into TWRP & flash no verity
- reboot the system
Right?
Click to expand...
Click to collapse
Yep, you can also flash the latest .zip via TWRP instead of using Flashfire, it's 100% working for me. Just REMEMBER to flash the no-verity file otherwise you'll end up in a bootloop.
I have newest oreo fw from asus website. Ive unlocked bootloader with official app. Now i want WTRP and root with magisk. I want to know how to flash updates to get all wroking?
1. Flash TWRP via fastboot?
2. Flash Magisk via TWRP?
3. When update will release i must flash whole fw from asus website with TWRP and then no-verity file to boot?
4. Or can i use flashfire app to flash fw from asus website and then no-verity zip?
What is the best solution to have updated system without use PC? Step by step guide will be great THX
Im confuse.
Im using 1711.75 with magisk 15.3 and twrp 3.2.1.0
I have the full firmware of initial oreo
I just have to install flashfire
Flash the full firmware oreo that i have then rboot to twrp to flash no verify zip?
ktl20 said:
I have newest oreo fw from asus website. Ive unlocked bootloader with official app. Now i want WTRP and root with magisk. I want to know how to flash updates to get all wroking?
1. Flash TWRP via fastboot?
2. Flash Magisk via TWRP?
3. When update will release i must flash whole fw from asus website with TWRP and then no-verity file to boot?
4. Or can i use flashfire app to flash fw from asus website and then no-verity zip?
What is the best solution to have updated system without use PC? Step by step guide will be great THX
Click to expand...
Click to collapse
iamROOTX said:
Im confuse.
Im using 1711.75 with magisk 15.3 and twrp 3.2.1.0
I have the full firmware of initial oreo
I just have to install flashfire
Flash the full firmware oreo that i have then rboot to twrp to flash no verify zip?
Click to expand...
Click to collapse
The safest and true way to flash any ota update without any issues by using stock recovery, don't use twrp or flashfire or any other apps.
follow the steps below:
1. When you are rooted and twrp installed, to getback to full stock boot and recovery without wiping data, flash the latest raw image available. For oreo the latest available one for ze520kl is WW_ZE520KL_15.0410.1712.31_M3.10.47.16_Phone-user.raw.zip.
2. Now flash the ota update available normally via stock recovery.
3. Flash oreo support twrp-3.2.1-0 and magisk zip.
4. Done.
I'm periodically upload the latest available ota update for ze520kl in the ze520kl ota update links thread.
Here is the latest one.
I've got my hands on this phone today. So I went on and unlocked bootloader and installed TWRP (with all in one tool).
But now when I want to root my phone through twrp, i can't access my files. I see the root folders, but when I go to /sdcard there are only a bunch of folder with random letters.
I don't know what's wrong. It is not asking for a password or anything.
Twrp has decryption issues currently. It's mentioned in the thread.
No need to install it yet, just boot to it.
If you're wanting to install magisk, just go into adb sideload in twrp and sideload magisk from your PC.
hartleyshc said:
Twrp has decryption issues currently. It's mentioned in the thread.
No need to install it yet, just boot to it.
If you're wanting to install magisk, just go into adb sideload in twrp and sideload magisk from your PC.
Click to expand...
Click to collapse
Thank you for your quick reply!
Is it bad that it is already flashed permanent? Or do I need to flash original recovery again?
I'll try and sideload it. Haven't done that before.
bokkoman said:
I've got my hands on this phone today. So I went on and unlocked bootloader and installed TWRP (with all in one tool).
But now when I want to root my phone through twrp, i can't access my files. I see the root folders, but when I go to /sdcard there are only a bunch of folder with random letters.
I don't know what's wrong. It is not asking for a password or anything.
Click to expand...
Click to collapse
The current TWRP has decryption issues as its based on the Oreo tree and encryption/decryption works differently on pie.
Here is a post i did so follow it for easy instructions.
Funk Wizard said:
The current TWRP has decryption issues as its based on the Oreo tree and encryption/decryption works differently on pie.
Here is a post i did so follow it for easy instructions.
Click to expand...
Click to collapse
I read in your post that you not recommend to flash twrp, but I already did. How do return to original recovery?
bokkoman said:
I read in your post that you not recommend to flash twrp, but I already did. How do return to original recovery?
Click to expand...
Click to collapse
Nothing to worry about. You can dirty flash the latest full zip from my update thread or just wait for the next OTA as and when it comes flash the full zip that will overwrite the recovery partition to stock. For now TWRP is basically useless so i did not recommend to flash the installer instead just boot in it sideload magisk or kernel if you need to and retain stock recovery.
Feel free to ask anything if you are still in doubt :fingers-crossed:
Funk Wizard said:
Nothing to worry about. You can dirty flash the latest full zip from my update thread or just wait for the next OTA as and when it comes flash the full zip that will overwrite the recovery partition to stock. For now TWRP is basically useless so i did not recommend to flash the installer instead just boot in it sideload magisk or kernel if you need to and retain stock recovery.
Feel free to ask anything if you are still in doubt :fingers-crossed:
Click to expand...
Click to collapse
Thanks for the info! I'll wait for an update.
When that update comes, can i just install it from the settings? Or would i have to manually download it and install it thru TWRP/sideload?
And i guess I lose root after i update so i would have to boot into twrp and install magisk again.
bokkoman said:
Thanks for the info! I'll wait for an update.
When that update comes, can i just install it from the settings? Or would i have to manually download it and install it thru TWRP/sideload?
And i guess I lose root after i update so i would have to boot into twrp and install magisk again.
Click to expand...
Click to collapse
As and when the update comes, just let the system download and install the zip. It will auto download and install the full zip when it detects root/system modifications, just make sure you uninstall/deactivate all mods/magisk modules/ substratum overlays before you update. You can check for easy instruction on the third post of the update thread. I will update the thread as and when the OTA is released.
Also you guessed it right the update will unroot the device so you have to root it again so you can either do the same sideload way or just do it from the magisk manager - uninstall - install ota (do not reboot) - install magisk to second slot - reboot :good:
I will again update the detailed instructions for easy understanding and and when we have the update :good:
Just stay subscribed to the update thread :good:
Hi fellows
I wanted to root my Mi 9T, but I don't want to flash a custom rom, I just want to have root on the official rom (global stable).
As I understand, the correct procedure is:
-unlock nootloader
-flash twrp
-flash magisk
But I have a couple of doubts about this, in particular about updates:
-If my phone is unlocked and I have root, will I still receive official updates from xiaomi?
-if yes, do they install via twrp? Do they fail installation? Do I loose root/bootloader unlock if I install them on unlocked/rooted phone?
-if no, is there an alternative way to install updates without losing root every time?
In other words, what is the best way to have a rooted phone but with official, up-to-date rom? (I have no problems downloading/installing updates manually, but having to reapply root every time would be annoying)
Master_T said:
Hi fellows
I wanted to root my Mi 9T, but I don't want to flash a custom rom, I just want to have root on the official rom (global stable).
As I understand, the correct procedure is:
-unlock nootloader
-flash twrp
-flash magisk
But I have a couple of doubts about this, in particular about updates:
-If my phone is unlocked and I have root, will I still receive official updates from xiaomi?
-if yes, do they install via twrp? Do they fail installation? Do I loose root/bootloader unlock if I install them on unlocked/rooted phone?
-if no, is there an alternative way to install updates without losing root every time?
In other words, what is the best way to have a rooted phone but with official, up-to-date rom? (I have no problems downloading/installing updates manually, but having to reapply root every time would be annoying)
Click to expand...
Click to collapse
As I know you could receive updates if you unlock your bootloader and flash magisk, I don't have experience with that, I've read that from other brands people do this and still get their updates.
If I'm wrong correct my.
• You will receive the ota but it won't install
• You'll have to install the full rom and reflash Magisk everytime
• Orange Fox recovery can install ota BUT not available for Mi 9T/K20
I'm not sure about Mi 9t (have to wait for bootloader unlock), but it was so on Redmi 3s: I can install OTA updates, it goes through TWRP, but after every update I have to flash Magisk.
It was several years ago, so probably they've changed something
Thanks for your replies guys.
I can now confirm (just tested) that to update a rooted mi9t all you have to do is this:
-flash update zip with twrp (you have to download the update zip from somewhere, like mifirm website, the one downloaded by the update tool is encrypted and won't work!)
-flash magisk
-reboot
Very simple! No need to reflash magisk modules, just the magisk base package and everything works as expected ?
Master_T said:
Thanks for your replies guys.
I can now confirm (just tested) that to update a rooted mi9t all you have to do is this:
-flash update zip with twrp (you have to download the update zip from somewhere, like mifirm website, the one downloaded by the update tool is encrypted and won't work!)
-flash magisk
-reboot
Very simple! No need to reflash magisk modules, just the magisk base package and everything works as expected
Click to expand...
Click to collapse
Which twrp and magisk do you use?
grinandbearit said:
Which twrp and magisk do you use?
Click to expand...
Click to collapse
First TWRP that came out (LR Team), but that is because it was the only one available at the time, there might be better ones out now, check the TWRP thread for more info.
Magisk, I used the latest stable release.
Master_T said:
Thanks for your replies guys.
I can now confirm (just tested) that to update a rooted mi9t all you have to do is this:
-flash update zip with twrp (you have to download the update zip from somewhere, like mifirm website, the one downloaded by the update tool is encrypted and won't work!)
-flash magisk
-reboot
Very simple! No need to reflash magisk modules, just the magisk base package and everything works as expected
Click to expand...
Click to collapse
I think it is more simple to do the update and reflash magisk instead of searching for the update package manually, isn't it?
Edit: wrong quote
fabsen said:
I think it is more simple to do the update and reflash magisk instead of searching for the update package manually, isn't it?
Click to expand...
Click to collapse
You mean flash the fastboot rom using a computer and then reinstall twrp and magisk?
Seems more convoluted to me, since you still need to download the rom from an external website and additionally you need a pc and you need to reflash twrp every time.... it'll probably work fine, but it seems more complicated to me
Master_T said:
You mean flash the fastboot rom using a computer and then reinstall twrp and magisk?
Seems more convoluted to me, since you still need to download the rom from an external website and additionally you need a pc and you need to reflash twrp every time.... it'll probably work fine, but it seems more complicated to me
Click to expand...
Click to collapse
Nah, I mean you flash the update you get the usual way. And then magisk afterwards. At least I've never lost twrp with OTA updates.
fabsen said:
Nah, I mean you flash the update you get the usual way. And then magisk afterwards. At least I've never lost twrp with OTA updates.
Click to expand...
Click to collapse
You mean the one downloaded through the miui updater? I can't flash that with twrp, it's encrypted. In fact, I can't even open the zip file with file manager, it says the file is corrupted. How do you decrypt/use it?
Few days ago I got OTA update while having magisk root and TWRP installed. It rebooted phone into TWRP and installed itself through TWRP. So it seems Xiaomi can now detect what recovery you are using and instead send you recovery OTA instead? Sadly I lost TWRP and root this way and needed to find newer TWRP (old one didnt boot and caused bootloop). Rom also didnt boot (after flashing new TWRP) until I flashed magisk.
Thank you all, it's nice to find this post before I create a new with the same questions.
I bought a new "Mi 9t", it received the latest OTA update, and it has been unlocked after waiting 170 hours.
MIUI Version: MIUI Global 10.3.11 Stable
Android Version: 9 PKQ1.190302.001
Model Name: M1903F10G
Now I need to root it without flashing twrp, I need to be on the Stock recovery because I don't want to lose the OTA update.
I ran this command :
Code:
C:\adb>fastboot boot recovery.img
Downloading ‘boot.img’ OKAY [ 1.404s]
booting OKAY [ 0.127s]
Finished. Total time: 1.560s
but the device reboot to MI-Recovery 3.0, can someone correct me if I'm wrong? also which twrp version support MIUI Global 10.3.11 Stable?
Matthas said:
Few days ago I got OTA update while having magisk root and TWRP installed. It rebooted phone into TWRP and installed itself through TWRP. So it seems Xiaomi can now detect what recovery you are using and instead send you recovery OTA instead? Sadly I lost TWRP and root this way and needed to find newer TWRP (old one didnt boot and caused bootloop). Rom also didnt boot (after flashing new TWRP) until I flashed magisk.
Click to expand...
Click to collapse
Weird, I tried that (downloading update from the updater app and rebooting to twrp to auto-flash it), but TWRP said update was corrupted. I had to download an unencrypted version from mifirm site to flash it with twrp.
Maybe it's a problem with the version of twrp? Which one are you using? I'm using the one from LR Team
Master_T said:
Weird, I tried that (downloading update from the updater app and rebooting to twrp to auto-flash it), but TWRP said update was corrupted. I had to download an unencrypted version from mifirm site to flash it with twrp.
Maybe it's a problem with the version of twrp? Which one are you using? I'm using the one from LR Team
Click to expand...
Click to collapse
oh I wish I knew After update when I went to flash back old twrp and magisk it resulted in bootloop so I was flashing all twrp I could find just to make them boot and then be able to flash magisk. However name of my file is "recovery-TWRP-3.3.1-0607-REDMI_K20-CN-wzsx150" I think its "fixed" chinese one.
Is "recovery-TWRP-3.3.1-0607-REDMI_K20-CN-wzsx150" support for MIUI Global 10.3.11 Stable?
Can I boot from it to root Mi 9T without flashing?
akha666 said:
Is "recovery-TWRP-3.3.1-0607-REDMI_K20-CN-wzsx150" support for MIUI Global 10.3.11 Stable?
Can I boot from it to root Mi 9T without flashing?
Click to expand...
Click to collapse
Is any expert have an answer to my questions?
Schnedi said:
• You will receive the ota but it won't install
• You'll have to install the full rom and reflash Magisk everytime
• Orange Fox recovery can install ota BUT not available for Mi 9T/K20
Click to expand...
Click to collapse
How do i root global stable rom 10.3.11 without bootlooping? Just rooting and no twarp .
Didn't see anyone else confirming that the Magisk OTA install works with Android 10, so... confirming that it does.
Let OTA finish but don't reboot.
Go to Magisk Manager and "Install" Magisk - select the bottom option (includes the OTA phrase)
Reboot
Profit.
No problems noticed in a half-day of use.
Did you do this from Pie or from Android Q beta? Also, did you uninstall Magisk from the manager before you did the OTA?
Anybody know if this worked smoothly with their Viper4Android app?
This worked form me going from Android 9 with Magisk to Android 10
I'm glad I waited and saw this before moving to Android 10. This worked like a charm for me as well.
gregoryx said:
Didn't see anyone else confirming that the Magisk OTA install works with Android 10, so... confirming that it does.
Let OTA finish but don't reboot.
Go to Magisk Manager and "Install" Magisk - select the bottom option (includes the OTA phrase)
Reboot
Profit.
No problems noticed in a half-day of use.
Click to expand...
Click to collapse
Is this working on Novemeber 2019? i am rooted with magisk and twrp , but the OTA says error to download, try again. and never downloads and installed it.
---------- Post added at 09:16 PM ---------- Previous post was at 09:16 PM ----------
gregoryx said:
Didn't see anyone else confirming that the Magisk OTA install works with Android 10, so... confirming that it does.
Let OTA finish but don't reboot.
Go to Magisk Manager and "Install" Magisk - select the bottom option (includes the OTA phrase)
Reboot
Profit.
No problems noticed in a half-day of use.
Click to expand...
Click to collapse
Is this working on Novemeber 2019? i am rooted with magisk and twrp , but the OTA says error to download, try again. and never downloads and install it.
Ota usually gives me error cant install so i flash factory image without (-w) wiping then i reflash kernel and magisk, result is updating to latest image with everything stays at it is
kmry said:
Is this working on Novemeber 2019? i am rooted with magisk and twrp , but the OTA says error to download, try again. and never downloads and install it.
Click to expand...
Click to collapse
Is your recovery stock? It may not be clearly stated as I haven't read the thread in its entirety, but the OTA will fail with TWRP installed. It likely will also fail if the system partition is modified.
EDIT: I re-read your post. You clearly note using TWRP.
Nightf0x_007 said:
Ota usually gives me error cant install so i flash factory image without (-w) wiping then i reflash kernel and magisk, result is updating to latest image with everything stays at it is
Click to expand...
Click to collapse
How do you flash it, with flash fire, trough TWRP or from fastboot?
kmry said:
How do you flash it, with flash fire, trough TWRP or from fastboot?
Click to expand...
Click to collapse
Factory image flash via adb using pc, then i boot to twrp and reflash kernel and magisk
Anyone know how to get the native led configuration without using a custom rom or the lightflow app?
Should I update Magisk and manager before I do this?
My Magisk installed is 18.1 and it lists 20.1 as available
Magisk Manager installed is 7.0 and 7.4 is listed as available
If you wanna follow the official instructions :
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Nightf0x_007 said:
Factory image flash via adb using pc, then i boot to twrp and reflash kernel and magisk
Click to expand...
Click to collapse
i decided to flash the complete ota trough TWRP, installed normally but TWRP was gone, so installed again, then magisk then EX kernel, thanks.
kmry said:
i decided to flash the complete ota trough TWRP, installed normally but TWRP was gone, so installed again, then magisk then EX kernel, thanks.
Click to expand...
Click to collapse
Yes this also works, this was the procedure i was following before, but i dont have twrp installed in my device, it causes bootloop and device sensors errors idk why so i fastboot it, once i tried updating by flashing ota zip via twrp but device didnt bootup maybe cause twrp is not installed so since that what i do is reflashing factory image without -w
Nightf0x_007 said:
Yes this also works, this was the procedure i was following before, but i dont have twrp installed in my device, it causes bootloop and device sensors errors idk why so i fastboot it, once i tried updating by flashing ota zip via twrp but device didnt bootup maybe cause twrp is not installed so since that what i do is reflashing factory image without -w
Click to expand...
Click to collapse
do i have to delete the "-w" command only on the "flash-all.bat" or on the "flash-all.sc" too?
kmry said:
do i have to delete the "-w" command only on the "flash-all.bat" or on the "flash-all.sc" too?
Click to expand...
Click to collapse
Just the flash-all.bat if your using Windows. :good:
kmry said:
do i have to delete the "-w" command only on the "flash-all.bat" or on the "flash-all.sc" too?
Click to expand...
Click to collapse
.bat file only