Accidentally flashed boot to TWRP - OnePlus 5 Questions & Answers

Good evening!
Well, my problem is, that trying to install TWRP as recovery (which I did). After doing it, I used the following command -stupidly because I wasn't thinking- thinking it was another thing:
flashboot flash boot twrp.img
Now, everytime I try to boot my OP5, it loads the TWRP.
Now, what can I do? I have the full 4.5.12 OTA that I downloaded from a post in the original OP5 forum, but the one I have installed in my phone is the 4.5.10 or 4.5.11 (I'm not sure now, the last one available before the .12).
Thank you very much!

enlapse said:
Good evening!
Well, my problem is, that trying to install TWRP as recovery (which I did). After doing it, I used the following command -stupidly because I wasn't thinking- thinking it was another thing:
flashboot flash boot twrp.img
Now, everytime I try to boot my OP5, it loads the TWRP.
Now, what can I do? I have the full 4.5.12 OTA that I downloaded from a post in the original OP5 forum, but the one I have installed in my phone is the 4.5.10 or 4.5.11 (I'm not sure now, the last one available before the .12).
Thank you very much!
Click to expand...
Click to collapse
1.Unzip the full OTA file
2. Take boot.img from OTA file
3. Execute following command:
flashboot flash boot boot.img

Thank you very much!
But what if my version is not the same as the OTA I have? Will that affect? Because my version is for sure lower than what I have.

enlapse said:
Thank you very much!
But what if my version is not the same as the OTA I have? Will that affect? Because my version is for sure lower than what I have.
Click to expand...
Click to collapse
You can flash the OTA (if it's over 1GB) in TWRP too.
That will simply update your software to the latest version and will hopefully also bring your phone to a working state.

In other words, what you did was flash TWRP to the boot partition instead of the normal recovery partition. Simply reflash the boot.img to the boot partition and you should be good to go. The boot.img is mostly the kernel and doesn't usually change much from OTA to OTA so you should be fine.

Related

How to Root Honor 8 FRD-L09 (NOUGAT 7.0 EMUI 5.0 With Bluetooth, NFC, system apps)

I had been struggeling myself alot with this but after looking everywhere I collected pieces of information all over XDA and fixed it.
Since all the information is scatterd around everywhere I thought it would be good to make a complete piece here.
I have only tested this with the device: (Honor 8 FRD-L09)
If anyone got this working on other devices please leave a comment so I can add it to this list for other people to see.
So here it goes:
1- First you need to be have an unlocked bootloader.
2- Flash via fastboot the new TWRP with decryption support Here
3- Download two files:
a- update.zip Link (1.5G)
b- update_data_full_hw_eu.zip Link(1.05G)
4- Flash these two files using TWRP (a then b)
5- Reflash TWRP (using fastboot)
Finally, to root, you need to flash this patched prerooted boot.img B378 root boot image (from SD card): Link(15.8MB)
You can do this with OldDroids TWRP or with surdu_petrus TWRP: Link(36.2MB) and Link(24,2MB)
1- Flash OldDroids or surdu_petrus TWRP
2- Select "Install" -> Click "Images" -> Go to External SD and select your rooted_b378_boot.img
3- When it asks where to install click boot.
4- Then reboot and install phh's superuser from the playstore (its the only superuser that works for now)
5- Install JRummy's Busybox Installer and install to /vendor/xbin
Done!
Note: To get AdAway working, go to Preferences, then scroll down to "Target hosts file" and set it to "custom target". Then set Custom target to "/vendor/etc/hosts"
If you have any questions feel free to send me a message I had much trouble with it too.
Credits to: morpheus302, Atarii, OldDroid, surdu_petrus and phhusson
thierrybla said:
I had been struggeling myself alot with this but after looking everywhere I collected pieces of information all over XDA and fixed it.
Since all the information is scatterd around everywhere I thought it would be good to make a complete piece here.
So here it goes:
1- First you need to be have an unlocked bootloader.
2- Flash via fastboot the new TWRP with decryption support Here
3- Download two files:
a- update.zip Link (1.5G)
b- update_data_full_hw_eu.zip Link(1.05G)
4- Flash these two files using TWRP (a then b)
5- Reflash TWRP (using fastboot)
Finally, to root, you need to flash this patched prerooted boot.img B378 root boot image (from SD card): Link(15.8MB)
You can do this only with OldDroids TWRP: Link(36.2MB)
1- Flash OldDroids TWRP
2- Select "Install" -> Click "Images" -> Go to External SD and select your rooted_b378_boot.img
3- When it asks where to install click boot.
4- Then reboot and install phh's superuser from the playstore (its the only superuser that works for now)
5- Install JRummy's Busybox Installer and install to /vendor/xbin
Done!
Note: To get AdAway working, go to Preferences, then scroll down to "Target hosts file" and set it to "custom target". Then set Custom target to "/vendor/etc/hosts"
If you have any questions feel free to send me a message I had much trouble with it too.
Credits to: morpheus302, Atarii, OldDroid and phhusson
Click to expand...
Click to collapse
Hello!
Can you please specify for which variants of the FRD is this valid?
Thank you
RM
omartins said:
Hello!
Can you please specify for which variants of the FRD is this valid?
Thank you
RM
Click to expand...
Click to collapse
I have only tested it on the FRD-L09
I can't say for sure if it works on the others, I'm sorry.
If you got this working on a different device please let me know.
Quick Question: I have installed normal TWRP 3.1.0.0, every time i want to install the newest SuperSu Beta, it resets TWRP completely. Is your guide also going to work for me, or do i have another problem?
david320te said:
Quick Question: I have installed normal TWRP 3.1.0.0, every time i want to install the newest SuperSu Beta, it resets TWRP completely. Is your guide also going to work for me, or do i have another problem?
Click to expand...
Click to collapse
Yes SuperSU doesn't work as far as I know you need Phh Superuser.
But if you already have nougat 7.0 B380 you can just begin at the boot.img installing step and it should work for you too.
Good luck!
Ok, but you linked "twrp-3.1.0.0-eva", i've installed "twrp-3.1.0.0-frp" - do you know, where the difference is?
Edit:
Well, something has gone wrong. Doesn't boot...stays on that screen forever...i tried restoring the backup i took while the system was read only with TWRP
david320te said:
Ok, but you linked "twrp-3.1.0.0-eva", i've installed "twrp-3.1.0.0-frp" - do you know, where the difference is?
Edit:
Well, something has gone wrong. Doesn't boot...stays on that screen forever...i tried restoring the backup i took while the system was read only with TWRP
Click to expand...
Click to collapse
The difference is that the TWRP that I linked can flash .img 's
wich you need to flash the boot.img
Try to get back in TWRP and start at step 1 just do the whole guide then your phone should boot again
david320te said:
Ok, but you linked "twrp-3.1.0.0-eva", i've installed "twrp-3.1.0.0-frp" - do you know, where the difference is?
Edit:
Well, something has gone wrong. Doesn't boot...stays on that screen forever...i tried restoring the backup i took while the system was read only with TWRP
Click to expand...
Click to collapse
The "twrp-3.1.0.0-eva" is for the Huawei P9, the "twrp-3.1.0.0-frD" is for the Honor 8.
And first boot after TWRP install can take longer that usual:
Q: Why does booting take so long?
A: Because of the decryption process which need to finish
its work before twrp tries to access /data partition.
Click to expand...
Click to collapse
Try flashing the pre-rooted boot.img via fastboot command line.
Worked for me.
Code:
Copy the pre-rooted boot.img to the adb/fastboot directory
(have usb debugging enabled etc etc, connect phone to computer)
Start a cmd box
adb reboot fastboot
fastboot flash boot rooted_b378_boot.img
reboot device.
N01tra said:
The "twrp-3.1.0.0-eva" is for the Huawei P9, the "twrp-3.1.0.0-frD" is for the Honor 8.
And first boot after TWRP install can take longer that usual:
Try flashing the pre-rooted boot.img via fastboot command line.
Worked for me.
Code:
Copy the pre-rooted boot.img to the adb/fastboot directory
(have usb debugging enabled etc etc, connect phone to computer)
Start a cmd box
adb reboot fastboot
fastboot flash boot rooted_b378_boot.img
reboot device.
Click to expand...
Click to collapse
I can boot into TWRP no Problem, as i said, i restored the backed up image (somehow after a factory reset, the stock apps as well as the keyboard was gone, i could not type in my wifi password) in TWRP, but it sat for about 10 Minutes on that screen when i turned the phone off.
I do not have very good Broadband, so i will start at the first step, installing the update files, linked in the first post.
N01tra said:
The "twrp-3.1.0.0-eva" is for the Huawei P9, the "twrp-3.1.0.0-frD" is for the Honor 8.
And first boot after TWRP install can take longer that usual:
Try flashing the pre-rooted boot.img via fastboot command line.
Worked for me.
Code:
Copy the pre-rooted boot.img to the adb/fastboot directory
(have usb debugging enabled etc etc, connect phone to computer)
Start a cmd box
adb reboot fastboot
fastboot flash boot rooted_b378_boot.img
reboot device.
Click to expand...
Click to collapse
You are right it is for P9 but it worked for me regardless though :fingers-crossed:
david320te said:
I can boot into TWRP no Problem, as i said, i restored the backed up image (somehow after a factory reset, the stock apps as well as the keyboard was gone, i could not type in my wifi password) in TWRP, but it sat for about 10 Minutes on that screen when i turned the phone off.
I do not have very good Broadband, so i will start at the first step, installing the update files, linked in the first post.
Click to expand...
Click to collapse
Yeah.. A FactoryReset seems to be a big "no no" after flashting TWRP as it will delete the keyboard and other stuff.
I was in that situation and restored a TWRP backup which got me back to booting into android, but somehow the Camera and LED (flashlight) didn't work.
Restoring an older and a complete backup did not help. Flashing the Update files did not help.
Eventually I ended up following the Honor 8 Rollback steps; going from Emui 5 (android 7) back to Emui 4.1 (android 6).
That also means the Bootloader is locked again, so you'll have to re-unlock it again (if you still have the code, you can use it again).
My steps after the Rollback:
- OTA updated back to Emui 5,
- Factory reset (BEFORE installing TWRP) and reboot.
- Enabled USB debugging,
- Unlock bootloader,
- Flashed TWRP and immediately after that I booted into recovery and rebooted,
- Rebooted to Fastboot (via adb reboot bootloader),
- Fastboot flashed that pre-rooted b378 boot.img and rebooted,
- Installed Phh's root.
N01tra said:
Yeah.. A FactoryReset seems to be a big "no no" after flashting TWRP as it will delete the keyboard and other stuff.
I was in that situation and restored a TWRP backup which got me back to booting into android, but somehow the Camera and LED (flashlight) didn't work.
Restoring an older and a complete backup did not help. Flashing the Update files did not help.
Eventually I ended up following the Honor 8 Rollback steps; going from Emui 5 (android 7) back to Emui 4.1 (android 6).
That also means the Bootloader is locked again, so you'll have to re-unlock it again (if you still have the code, you can use it again).
My steps after the Rollback:
- OTA updated back to Emui 5,
- Factory reset (BEFORE installing TWRP) and reboot.
- Enabled USB debugging,
- Unlock bootloader,
- Flashed TWRP and immediately after that I booted into recovery and rebooted,
- Rebooted to Fastboot (via adb reboot fastboot),
- Fastboot flashed that pre-rooted b378 boot.img and rebooted,
- Installed Phh's root.
Click to expand...
Click to collapse
I had the same as you describe here but I fixed it by flashing the 2 files I posted up here (a and b)
After doing it step by step as described in the first post, it worked I also flashed the P9 TWRP, just to make sure. It works! But i already miss Resurrection Remix from my Mi4c...
However, does this mean TWRP Backups are useless? :/
david320te said:
After doing it step by step as described in the first post, it worked I also flashed the P9 TWRP, just to make sure. It works! But i already miss Resurrection Remix from my Mi4c...
However, does this mean TWRP Backups are useless? :/
Click to expand...
Click to collapse
I'm glad to hear it works! :highfive:
TWRP backups never worked for me I always just flash it clean and then have titanium backup do the rest
Have a nice day
Hi,
maybe what I am going to ask sounds silly but as I am a kind of newbie hope you will forgive me
Why do we have to install a prerooted 378 image instead of a prerooted 380 Image. Aren't we on 380?
Where does this 378 image come from? Until now I only saw Nougat's 360 & 380 Roms.
I am already on 380 but my root doesn't seem to work properly so I wanted to give a try to thierrybla's OP's post but I don't know if to follow his instructions by using OldDroids TWRP to install his suggested prerooted 378 Image or instead by using OldDroids TWRP to install the other thread's Prerooted 380 img.
What shall I do if I'm already on 380 but would like to try thierrybla's procudure so see if I finally get a well-rooted 380 rom?
Any help would be appreciated.
fourcc said:
Hi,
maybe what I am going to ask sounds silly but as I am a kind of newbie hope you will forgive me
Why do we have to install a prerooted 378 image instead of a prerooted 380 Image. Aren't we on 380?
Where does this 378 image come from? Until now I only saw Nougat's 360 & 380 Roms.
I am already on 380 but my root doesn't seem to work properly so I wanted to give a try to thierrybla's OP's post but I don't know if to follow his instructions by using OldDroids TWRP to install his suggested prerooted 378 Image or instead by using OldDroids TWRP to install the other thread's Prerooted 380 img.
What shall I do if I'm already on 380 but would like to try thierrybla's procudure so see if I finally get a well-rooted 380 rom?
Any help would be appreciated.
Click to expand...
Click to collapse
Hey,
Your question is not stupid I can see why you are confused but everytime I tried to root or preroot something it didn't work for me I also run 380 and once I tried the prerooted 378 made by atariii it worked so there is no reason te be skeptical because I was in the same situation as you and this worked for me just give it a try you won't be disappointed
Thanks for your quick answer!!!
Ok, so I understand it is safe to install prerooted 378 image while being on nougat's 380. Thanks, I will try it right now!
fourcc said:
Thanks for your quick answer!!!
Ok, so I understand it is safe to install prerooted 378 image while being on nougat's 380. Thanks, I will try it right now!
Click to expand...
Click to collapse
Tell me how it went !
Goodluck!
Hey thierrybla, it worked beautifully! Thanks!
The only thing I did different is too install the prerooted image with Fastboot instead of the Oldroid Twrp.
I was afraid of messing my good working TWRP setup and decided to try what N01tra user suggested.
It worked like a charm! Thanks again!
fourcc said:
Hey thierrybla, it worked beautifully! Thanks!
The only thing I did different is too install the prerooted image with Fastboot instead of the Oldroid Twrp.
I was afraid of messing my good working TWRP setup and decided to try what N01tra user suggested.
It worked like a charm! Thanks again!
Click to expand...
Click to collapse
that's fine too I'm glad it worked good for you!
Have a nice day!

Help with soft brick

Hi guys,
I got the ASUS Zenfone 3 Zoom and started playing with it. Unfortunately I managed to soft brick it and somehow I can't go back to stock. Here are all the things I did. I would be happy to get any ideas what to try next:
1. unlocked the bootloader - using asus's official unlock tool
2. flashed twrp recovery - twrp-3.2.1-0-Z01H-20180304.img, using:
adb reboot bootloader
fastboot flash recovery twrp.img
3. updated asus's firmware to the latest official one:
copying UL-Z01H-WW-71.60.139.30.zip onto internal memory
android detects the update and applying it using android
4. Enabling lock pattern at boot (from android settings). Correct pattern required even when booting into recovery
5. Installing supersu via twrp:
adb reboot recovery
installing supersu
wiping caches (the cache partition cannot be wiped)
6. SuperSu working (tested via android)
7. Reading about Magisk. Trying to install magisk via twrp. Magisk's installer complained that the system is not vanilla (due to SuperSu modifications). Have to uninstall SuperSu to return to previous state.
8. Tried uninstalling SuperSu from the program itself (in android). The uninstaller got stuck. The phone become unresponsive and had to reboot.
9. Found a script packaged as an executable zip (to be installed via twrp) that will uninstall SuperSu and return system to pristine state (SuperSu makes a backup of the files it changes before installation) - UPDATE-unSU-signed.zip. Uninstallation worked.
10. Magisk installation still complained about the bootloader. Then things started to go wrong. I unpacked the latest firware UL-Z01H-WW-71.60.139.30.zip, took out boot.img and tried to flash just the bootloader
fastboot flash boot boot.img
11. Upon reboot the phone got stuck at the ASUS logo. Reboot into recovery and into fastboot still works (soft brick). Still shows unlock pattern at boot.
12. I tried flashing the original firmware using TWRP (install a zip). However the installation threw some errors. Unsuccessful.
13. I've tried flashing the system.img from the original firware using fastboot but still it's stuck at the ASUS logo at boot.
fastboot flash system system.img
Here I am stuck. I've read that TWRP cannot install properly the ASUS official firmware but if you flash the original recovery, it can probably flash it properly. Another thing that I think might explain why I cannot get out of the soft brick is that I've enabled the lock pattern at boot, which effectively encrypted some parts of the phone and I have a strong feeling this interferes with the boot process. I will look for a script/installable zip (via twrp) that can remove the lock.
I really need ideas/suggestions before I make something that will turn my phone into a hard brick. Thanks.
What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you
Thanks
+)KEV1N(+ said:
What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you
Click to expand...
Click to collapse
Thanks,
I tried to find a stock recovery images but unsuccessful. Can you tell me where to get it from?
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
-- [link] removed due to XDA regulations
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.
mollonado said:
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.
Click to expand...
Click to collapse
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
It came preloaded with Nougat? Interesting.
+)KEV1N(+ said:
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
It came preloaded with Nougat? Interesting.
Click to expand...
Click to collapse
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?
mollonado said:
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?
Click to expand...
Click to collapse
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.
+)KEV1N(+ said:
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.
Click to expand...
Click to collapse
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.
mollonado said:
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.
Click to expand...
Click to collapse
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?
mollonado said:
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?
Click to expand...
Click to collapse
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.
+)KEV1N(+ said:
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.
Click to expand...
Click to collapse
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,
mollonado said:
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,
Click to expand...
Click to collapse
First off, my apologies for this late reply (Been superbusy with school and internship assignments)
Secondly, and that is why I only use magisk. Because once you mess with the host file, depending on what module you install, it can range from tripping safetynet to bootlooping.
So quick question, is it still in this state right now since 9 days ago?
Greetings,
Kevin
+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
I made a mistake and could not install recovery stock, I followed what you wrote in the beginning install MM recovery and so I did a hard reset and I was able to install the most current recovery stock and installed ROM Oreo, Thanks. Sorry, I'm on google translator.

Help Plz...Stock recovery missing and unable to install any recovery !

Thanks in advance......i'm so frustrated feel ripping my **** off.. being struggling with this for 3 days...
I was on official stock 7.0 nougat (generic russian), genesis kernel drmfix & Twrp for about a year with no issue. In fact that's my 1st and only attempt in flashing this phone. Decided to upgrade to 8.0. Big mistake!?!
Used Emma flash to flash the latest stock 8.0 release for my region, Asia. It booted up fine, all was well. I read that flashing stock will simply remove root and twrp. But i realized stock recovery was missing as well. And i can't restore any kind of recovery no matter what i tried. Suggestions please !
When i tried to enter recovery, the phone simply vibrated twice, and then 3 times quickly. If i continue holding the buttons, it goes into a loop of black screen and boot screen.
Tried flashing twrp via adb/fastboot. It appeared successful . No error messages. File size and time taken was also reported. But no recovery upon rebooting.
Fastboot flash recovery twrp.img
I can only flash roms using Emma, Flashtool ftf always fail with a 'no loader' found message.
Tried re-flashing mm, nougat and oreo via Emma. Phone runs well for all but again no stock recovery.
Don't know what else to do or what the problem is......
If i reflash to stock rom and relock boot loader without any recovery, it that dangerous?
Baron Zemo said:
Thanks in advance......i'm so frustrated feel ripping my **** off.. being struggling with this for 3 days...
I was on official stock 7.0 nougat (generic russian), genesis kernel drmfix & Twrp for about a year with no issue. In fact that's my 1st and only attempt in flashing this phone. Decided to upgrade to 8.0. Big mistake!?!
Used Emma flash to flash the latest stock 8.0 release for my region, Asia. It booted up fine, all was well. I read that flashing stock will simply remove root and twrp. But i realized stock recovery was missing as well. And i can't restore any kind of recovery no matter what i tried. Suggestions please !
When i tried to enter recovery, the phone simply vibrated twice, and then 3 times quickly. If i continue holding the buttons, it goes into a loop of black screen and boot screen.
Tried flashing twrp via adb/fastboot. It appeared successful . No error messages. File size and time taken was also reported. But no recovery upon rebooting.
Fastboot flash recovery twrp.img
I can only flash roms using Emma, Flashtool ftf always fail with a 'no loader' found message.
Tried re-flashing mm, nougat and oreo via Emma. Phone runs well for all but again no stock recovery.
Don't know what else to do or what the problem is......
If i reflash to stock rom and relock boot loader without any recovery, it that dangerous?
Click to expand...
Click to collapse
https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479
1. Download 'Modded boot img for 34.4.A.2.118' from that thread
2. Flash stock with Emma
3. Don't turn on the phone, go to fastboot and flash the boot img and TWRP img
levone1 said:
https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479
1. Download 'Modded boot img for 34.4.A.2.118' from that thread
2. Flash stock with Emma
3. Don't turn on the phone, go to fastboot and flash the boot img and TWRP img
Click to expand...
Click to collapse
Hi, Thanks for the reply
1. Done
2. Which do i choose in Emma? Software update content (erases user content) or Firmware update versions.
Also must i choose the stock rom which must tally with boot img 34.4.A.2.118? ie. the rom version which ends with .118?
3. Fingers crossed.
Baron Zemo said:
Hi, Thanks for the reply
1. Done
2. Which do i choose in Emma? Software update content (erases user content) or Firmware update versions.
Also must i choose the stock rom which must tally with boot img 34.4.A.2.118? ie. the rom version which ends with .118?
3. Fingers crossed.
Click to expand...
Click to collapse
Yes, flash 118 fw. If you want to save data, back it up first.
levone1 said:
Yes, flash 118 fw. If you want to save data, back it up first.
Click to expand...
Click to collapse
I have given up I followed the instructions explicitly.
Tried flashing latest stock from different regions via Emma, Flashtool/xperifirm and ftfs from online depositories. Then flashed with the corresponding downloaded boot.img, then TWRP without any rebooting inbetween. Even created patched boot.img from extracted .elf files to try. There was no error messages or anything.
Recovery runs fine. But starting normally it either boot loops are stuck at Sony logo.
Is there any other way to get the drm restored? Can i root it via common methods and work my way from there?
Baron Zemo said:
I have given up I followed the instructions explicitly.
Tried flashing latest stock from different regions via Emma, Flashtool/xperifirm and ftfs from online depositories. Then flashed with the corresponding downloaded boot.img, then TWRP without any rebooting inbetween. Even created patched boot.img from extracted .elf files to try. There was no error messages or anything.
Recovery runs fine. But starting normally it either boot loops are stuck at Sony logo.
Is there any other way to get the drm restored? Can i root it via common methods and work my way from there?
Click to expand...
Click to collapse
Did you full wipe before flashing, or when flashing, (check boxes in 'wipe' section)?
levone1 said:
Did you full wipe before flashing, or when flashing, (check boxes in 'wipe' section)?
Click to expand...
Click to collapse
If i use flash tool, i ticked all boxes under Wipe sin during stock rom flashing. All the rest (exclude sin & misc TAs) are unchecked. No other wiping during the process.
If i use Emma, there's no chance to wipe anything, it's auto flash stock rom, then flash boot.img, then flash Twrp, then reboot to a boot loop.
btw, i've tried latest twrp 3.2.3 and 3.2.1
Also, when i flash stock, is stock recovery supposed to return? Twrp just gets removed, and i don't have any recovery at all.
Am i cursed?
Baron Zemo said:
If i use flash tool, i ticked all boxes under Wipe sin during stock rom flashing. All the rest (exclude sin & misc TAs) are unchecked. No other wiping during the process.
If i use Emma, there's no chance to wipe anything, it's auto flash stock rom, then flash boot.img, then flash Twrp, then reboot to a boot loop.
btw, i've tried latest twrp 3.2.3 and 3.2.1
Also, when i flash stock, is stock recovery supposed to return? Twrp just gets removed, and i don't have any recovery at all.
Am i cursed?
Click to expand...
Click to collapse
I don't think you can boot to Sony stock recovery. If you flash stock 118, then flash modded boot img and TWRP, and reboot, I don't know why it wouldn't work. Many have done it. Just to be sure -
1. To enter recovery, you power off, then press power and volume down together, until vibration.
2. First boot takes a while. Wait a good 10 minutes to be sure.
levone1 said:
I don't think you can boot to Sony stock recovery. If you flash stock 118, then flash modded boot img and TWRP, and reboot, I don't know why it wouldn't work. Many have done it. Just to be sure -
1. To enter recovery, you power off, then press power and volume down together, until vibration.
2. First boot takes a while. Wait a good 10 minutes to be sure.
Click to expand...
Click to collapse
There's why it's so odd to me. Not the 1st time i'm doing this too. I would have waited even longer if it was stuck, but it was looping continuously back to the start.
I suspect could simply be a hardware fault developed. Anyway, i've given up. Probably best excuse to get a new phone
Many thanks for trying to help :good:
I haven't been able to get mine to reboot to recovery either, so i just boot recovery.img from fastboot anytime I want to mod. Kinda annoying but I haven't figured a way around it.

Patched Boot from latest OTA 10.0.3.0

Hello everyone
Someone in the russian forum (4pda) shared this patched boot from january ota
I flashed it and the device booted correctly without facing any problem, now magisk works again
Link to download : https://mega.nz/#!R5NAgQKJ!yfm886jSAA_x1raUzxRlq-t53AFjaFvU7Q_AH-fXRlY
Tested and it works. Thanks
help
guyz my adb cant load the patched boot img even when it is in the same folder any help plss
veddeomi said:
guyz my adb cant load the patched boot img even when it is in the same folder any help plss
Click to expand...
Click to collapse
Put the patched boot in adb folder
Reboot your phone into fastboot mode
Then open cmd : fastboot flash boot patched_boot_3.0.img
you can save ur time by using the below toolkit
https://forum.xda-developers.com/mi-a2/development/tool-mi-a2-xtrem-toolkit-t3879660
and just download Magisk from XDA and use the tool to install it using the ADB Sideload.
that is what i did and worked perfectly on Pie after Jan Update.
Does it work with v10.2 ?
Or i must update to v10.3 to flash this patch ?
beny ms said:
Does it work with v10.2 ?
Or i must update to v10.3 to flash this patch ?
Click to expand...
Click to collapse
U have to update first
Abrilabr said:
U have to update first
Click to expand...
Click to collapse
Okay ,thanks mate
i flashed it successfully but i get bootloop. this patch not working my phone
Oline1032 said:
i flashed it successfully but i get bootloop. this patch not working my phone
Click to expand...
Click to collapse
You should unlock your phone's bootloader first
And update to 10.0.3.0
medkim said:
You should unlock your phone's bootloader first
And update to 10.0.3.0
Click to expand...
Click to collapse
dude bootloader is unlocked
Oline1032 said:
dude bootloader is unlocked
Click to expand...
Click to collapse
are you in january patch ?
it's weird, your phone should boot normally, maybe you missed something
i was on 10.0.2.0.PDIMIFJ with unlocked bootloader and patched boot.img. when OTA update is avaiable, i restored boot.img using Magisk and installed the update, then patched boot.img again using Magisk.
After reboot, phone keeps restarting while showing Android One screen.
Then I flashed this patched 10.0.3.0, but phone is stuck at Android One screen (there should be moving color bar)
Now I'm trying to downgrade to 10.0.2.0.PDIMIFJ using MiFlash without erasing user data
Edit: still boot loop at Android One screen after flashing 10.0.2.0.PDIMIFJ without erasing user data. Phone shows the Android recovery screen with error message "can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device"
HRSE said:
i was on 10.0.2.0.PDIMIFJ with unlocked bootloader and patched boot.img. when OTA update is avaiable, i restored boot.img using Magisk and installed the update, then patched boot.img again using Magisk.
After reboot, phone keeps restarting while showing Android One screen.
Then I flashed this patched 10.0.3.0, but phone is stuck at Android One screen (there should be moving color bar)
Now I'm trying to downgrade to 10.0.2.0.PDIMIFJ using MiFlash without erasing user data
Click to expand...
Click to collapse
I have encountered the same problem.
It seems like there is something wrong with the encryption of the phone because I need to format the userdata partition to stop the bootloop.
Fulva said:
I have encountered the same problem.
It seems like there is something wrong with the encryption of the phone because I need to format the userdata partition to stop the bootloop.
Click to expand...
Click to collapse
Good for you that you are still on 10.0.3.0
Now my phone is wiped, and back to 10.0.2.0. I gained nothing and lost too much.
HRSE said:
i was on 10.0.2.0.PDIMIFJ... Edit: still boot loop at Android One screen after flashing 10.0.2.0.PDIMIFJ...
Click to expand...
Click to collapse
My jasmine 6/128 was on 10.0.2.0.PDIMIFJ, unlocked, rooted - Magisk with Modules, /system partition changed, automatic .Updates disabled
Thus, checking for January OTA and seeing that it is ready, I made these steps:
1. downloaded stock 10.0.2.0.PDIMIFJ http://en.miui.com/download-353.html (actually, I made it much earlier);
2. flashed it in fastboot preserving /data (there is "flash_all_except_data.bat" in unpacked ROM directory);
3. rebooted, downloaded OTA 10.0.3.0, installed OTA, rebooted without bootloop;
4. used phone for a while (root gone, all user applications, except for 1 rather specific, working - including Nova, phone calls, SMS, etc, OK);
5. Took patched boot image from 4pda, and booted it into phone in fastboot ("fastboot boot pached_boot.img"); NOTE: not flashed, but booted for safety!
6, As phone was working OK with booted patch, I started Magisk and "installed" it; thus Magisk patched my stock 10.0.3.0 boot in phone, and saved original stock in /data partition.
7. after reboot I had everything restored - Magisk modules and su, root permitions for applications, etc.
P.S. Seems like 10.0.3.0 PDIMIXM OTA is withdrawn by Xiaomi due to numerous bootloops in stock phones.
So if you already updated to this OTA, use these attachments at your own risk, or better wait for 10.0.4.0
Aerobatic said:
My jasmine 6/128 was on 10.0.2.0.PDIMIFJ, unlocked, rooted - Magisk with Modules, /system partition changed, automatic .Updates disabled
Thus, checking for January OTA and seeing that it is ready, I made these steps:
1. downloaded stock 10.0.2.0.PDIMIFJ http://en.miui.com/download-353.html (actually, I made it much earlier);
2. flashed it in fastboot preserving /data (there is "flash_all_except_data.bat" in unpacked ROM directory);
3. rebooted, downloaded OTA 10.0.3.0, installed OTA, rebooted without bootloop;
4. used phone for a while (root gone, all user applications, except for 1 rather specific, working - including Nova, phone calls, SMS, etc, OK);
5. Took patched boot image from 4pda, and booted it into phone in fastboot ("fastboot boot pached_boot.img"); NOTE: not flashed, but booted for safety!
6, As phone was working OK with booted patch, I started Magisk and "installed" it; thus Magisk patched my stock 10.0.3.0 boot in phone, and saved original stock in /data partition.
7. after reboot I had everything restored - Magisk modules and su, root permitions for applications, etc.
Click to expand...
Click to collapse
somehow my phone doesn't show the january OTA update anymore (it was still there a few hours ago!)
Hey guys if i root using patched boot image will i still be able to install updates?
one08 said:
Hey guys if i root using patched boot image will i still be able to install updates?
Click to expand...
Click to collapse
No you should restore stock boot first
one08 said:
Hey guys if i root using patched boot image will i still be able to install updates?
Click to expand...
Click to collapse
Yes you can receive updates, but only if you did not made any changes to system files !

Spent 6+ Hours Trying To Get Rooted Android 10

I tried rooting my OP6T on Android 10, and was up half the night. Recovered from a hard brick twice, using the Qualcomm serial flash tool thing. I was trying to flash Majisk, and read that it had to be done via a custom recovery like TWRP. All the guides said that it to boot TWRP, then basically flash TWRP using itself so that it says. Fastboot kept saying "Remote Unknown Command" when using "fastboot boot" like all the guides said. Then someone told me to run "fastboot flash boot twrp.img". This caused the first hard brick. I guess because I wrote the recovery over the boot partition. I then found a post somewhere where someone said that Oneplus Devs removed the boot command from Fastboot for some reason. No idea why!! But no one else in the OP6T TWRP thread reported issues. Maybe they were all installing TWRP on an Android 9.x build that diden't have this issue? Eventually after recovering and flashing several layers on OTA updates through the local upgrade option, I was back on A10 OB2. But I still wanted root and hadn't got TWRP working yet. Then I found a random post buried in a random thread somewhere saying that custom recoveries on A10 are useless at this point period because TWRP can't flash the system partition, as it's read only. Not sure if this only applies to OP devices?
I am now back to where I started. I would still like twrp for backups, but since it's not cooperating, I try the alternative option for Masisk, involving the patched boot.img file. I download the patched the patched boot file in this thread. Flashed it with "fastboot flash boot boot.img", and got my 2nd hard brick. It would get stuck at the bootloader warning screen and no fastboot.
Now i've lost my data, 6+ hour of time, and no closer than I was before.
I am going to take a break now, cause I need an operational phone this week. Word of advice: If you're not a developer that knows exactly what they are doing, don't even attempt to get root on an Android 10 build!
You can install Magisk,manager,extract the boot img from the OOS zip file using payload_dumper,copy that boot img. to your phone,patch the image with magisk,copy to your PC then fastboot the patched image to your phone .And yes,you cannot have twrp yet.
I'm on the open beta 2 of Android 10 and I have root and TWRP. It's possible.
It's not that hard, you don't even need twrp to install magisk. in android 10.
download open beta 2 Android 10. Extract payload.bin from it. Use payload_dumper to extract boot
install magisk apk, and patch boot.
go to fastboot use the
"Fastboot flash boot_a patched_boot.img "
and you are done.
Sh4d0wk1ng said:
It's not that hard, you don't even need twrp to install magisk. in android 10.
download open beta 2 Android 10. Extract payload.bin from it. Use payload_dumper to extract boot
install magisk apk, and patch boot.
go to fastboot use the
"Fastboot flash boot_a patched_boot.img "
and you are done.
Click to expand...
Click to collapse
I think I see what I did! I need to use "fastboot flash boot_a" (or b), and not just "fastboot flash boot". Not sure how you know whether to use a or b without a custom recovery though? Because AFAIK, the fastboot command for that is broken.
Not sure what payload dumper is, but I should be able to use the the same patched boot image that everyone else used since it's for that same ROM, now that I known exactly where to flash it to (besides A or B).
When I flashed to "boot" before, I must have overwritten some kind of low-level pre-bootloader, lol.
Thank you
Bhamilton0347 said:
I'm on the open beta 2 of Android 10 and I have root and TWRP. It's possible.
Click to expand...
Click to collapse
How did you achieve this? Do you have to start with A9 with TWRP, and then somehow upgrade to A10 without overwriting it with stock recovery?
I found this guide, but step 2 does not make sense to me. How could you flash TWRP inside of the Masisk Manager app?
I imagine you still can't flash system with TWRP, but everything else works?
Thank you
roman gabriel said:
You can install Magisk,manager,extract the boot img from the OOS zip file using payload_dumper,copy that boot img. to your phone,patch the image with magisk,copy to your PC then fastboot the patched image to your phone .And yes,you cannot have twrp yet.
Click to expand...
Click to collapse
I think the issue was that I flashed to the wrong place. See above. Thank you.
I'm feeling extremely lazy rn and I don't feel like explaining all of the trouble I went through to get it working, but you should be able to just fastboot flash these images to their respective partitions and you should have both TWRP and Magisk. It's got Magisk 20.1, the modified one so that EdXposed will work. But they're functionally the same.
https://drive.google.com/file/d/149TqVLqKr7Rc8xygMDoUyY_SLoATQrRq/view?usp=drivesdk
Let me know if it works.
Note: this is the boot.img for the second open beta of Android 10 for the OnePlus 6T. This may also work on the stable and first beta release as well as even on the 6, but I do not know. Also, your SIM card may not be showing up, but this problem disappeared for me a minute or two after boot.
Bhamilton0347 said:
I'm feeling extremely lazy rn and I don't feel like explaining all of the trouble I went through to get it working, but you should be able to just fastboot flash these images to their respective partitions and you should have both TWRP and Magisk. It's got Magisk 20.1, the modified one so that EdXposed will work. But they're functionally the same.
https://drive.google.com/file/d/149TqVLqKr7Rc8xygMDoUyY_SLoATQrRq/view?usp=drivesdk
Let me know if it works.
Note: this is the boot.img for the second open beta of Android 10 for the OnePlus 6T. This may also work on the stable and first beta release as well as even on the 6, but I do not know. Also, your SIM card may not be showing up, but this problem disappeared for me a minute or two after boot.
Click to expand...
Click to collapse
Thank you. I can't risk it right now. But i'll try sometime. Anyone wanna be the guinea pig?
If it works well, it should be very useful to the community.
I am brand new to Majisk by the way. It's been a couple years since I was rooted.
flyoffacliff said:
Thank you. I can't risk it right now. But i'll try sometime. Anyone wanna be the guinea pig?
If it works well, it should be very useful to the community.
I am brand new to Majisk by the way. It's been a couple years since I was rooted.
Click to expand...
Click to collapse
It's 100% safe and I can guarantee it'll boot as long as you're on an international OP6T on the Android 10 open beta 2. I reuploaded and included the stock boot.img as well so just in case you do have any problems, you can just fastboot flash it and you'll be able to boot right up (no hard brick or anything)
Bhamilton0347 said:
It's 100% safe and I can guarantee it'll boot as long as you're on an international OP6T on the Android 10 open beta 2. I reuploaded and included the stock boot.img as well so just in case you do have any problems, you can just fastboot flash it and you'll be able to boot right up (no hard brick or anything)
Click to expand...
Click to collapse
Great. Thank you. I might wait for the next stable build though. It just came out on H2OS, so shouldn't be too long now.
Man it just worked smooth for me. I was already on OB2 and I followed this below link. Half way down, I realised it was for OP6 and not 6T. However I had proper twrp and I just followed the procedure.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213
EDIT: I faced problems with wifi connectivity. So I had rebooted to TWRP and reflashed OB2, TWRP and Magisk again to get it working. An issue with
"fastboot flash boot" command I guess.
flyoffacliff said:
I think I see what I did! I need to use "fastboot flash boot_a" (or b), and not just "fastboot flash boot". Not sure how you know whether to use a or b without a custom recovery though? Because AFAIK, the fastboot command for that is broken.
Not sure what payload dumper is, but I should be able to use the the same patched boot image that everyone else used since it's for that same ROM, now that I known exactly where to flash it to (besides A or B).
When I flashed to "boot" before, I must have overwritten some kind of low-level pre-bootloader, lol.
Thank you
I wasn't sure either but I know that the boot on the oneplus 6t android 10 it has two partitions. I just flashed it on boot_a and it works. I could attempt to install twrp on the other partition but I don't really needed it. good luck and let us know how it went.
Click to expand...
Click to collapse

			
				
I had a bit more luck with the adventure this time! Successfully flashed TWRP and Magisk, but then Emojis were completely broken at the OS level. Apparently this is caused by a partition issue, but not sure how this happened. I tried a script to fix it that someone posted and it did not work. So I took this as an opportunity to flash the latest ROM to fix it.
I went into TWRP, ran the full update ZIP, then the TWRP installer, then the Magisk installer (all without rebooting). Apparently it does not switch slots automatically when you run it from recovery instead of the "local update" option? TWRP was fine after the update, but Masisk was not, despite me flashing the ZIP. No idea why! But I switched back to the other slot that was still rooted, used Magisk Manager to flash it to inactive slot, and switched slot back to one with new OS. Success! Funny how different methods work/fail with different people. Thanks for the help everyone. I just noticed 10.3.1 is no longer posted on the OnePlus website download page, hope it didn't get pulled again!
EDIT: Does each slot just have its own system and cache partition? Everything else is like data and modem is combined, right?
https://forum.xda-developers.com/oneplus-6t/how-to/root-oneplus-6t-loosing-data-android-10-t4041865
follow this guide.. work 100%. Tested.

Categories

Resources