Related
Anyone know how to flash or boot TWRP on that Android 10 OB 1. I tried booting with fastboot and it just sits on the fastboot mode screen and flashing it just continuously kicks me back to the bootloader.
I'm not on OB1, but from what I understand the command to boot TWRP doesn't work yet. And you can't flash TWRP in fastboot (can only flash it in TWRP or Magisk). Depending on what TWRP file/fastboot command, you might not even be flashing it to the right partition!
I believe the sequence is:
1) Install Magisk Manager
2) Fastboot flash patched boot image
3) Reboot, open Magisk Manager
4) Flash TWRP installer zip, like it is a Magisk module.
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
And more info here: https://forum.xda-developers.com/oneplus-7-pro/help/rooting-android-10-t3964863
Hi,
I was on Oxygen OS 10.0.0. Rooted with twrp-3.3.1-4-enchilada and magisk 20.1. (I had used this guide to do it. https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213) Today I downloaded the zip for 10.0.1 from the Oxygen Updater app and tried to flash it like I have done for OOS 9 in the past as usual. I went to recovery (I did not backup), I just wiped my data (not internal storage), cache and system. After that I tried to install the new zip but I got an error. It just said error unable to install. Didn't mention why. I tried flashing the older OOS 10 zip and got the same error.
So I thought I will try flashing on the other slot. I was on slot B. I switched to slot A and got the same error.
So I thought I will try to sideload. When I tried that I got the same error. So I thought I will try to reflash the twrp img itself. I went to fastboot mode and tried runnning this command
fastboot boot twrp-3.3.1-14-enchilada-Q-mauronofrio.img
It showed me this error
Sending 'boot.img' (65536 KB) OKAY [ 1.609s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Now I don't have any recovery at all. I have just the unlocked bootloader and no OS nor recovery. What can I do to flash TWRP again and install either OOS 10.0.1 zip or 10.0.0 zip? Any help will be great.
Thanks
Arnavzz said:
Hi,
I was on Oxygen OS 10.0.0. Rooted with twrp-3.3.1-4-enchilada and magisk 20.1. (I had used this guide to do it. https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213) Today I downloaded the zip for 10.0.1 from the Oxygen Updater app and tried to flash it like I have done for OOS 9 in the past as usual. I went to recovery (I did not backup), I just wiped my data (not internal storage), cache and system. After that I tried to install the new zip but I got an error. It just said error unable to install. Didn't mention why. I tried flashing the older OOS 10 zip and got the same error.
So I thought I will try flashing on the other slot. I was on slot B. I switched to slot A and got the same error.
So I thought I will try to sideload. When I tried that I got the same error. So I thought I will try to reflash the twrp img itself. I went to fastboot mode and tried runnning this command
fastboot boot twrp-3.3.1-14-enchilada-Q-mauronofrio.img
It showed me this error
Sending 'boot.img' (65536 KB) OKAY [ 1.609s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Now I don't have any recovery at all. I have just the unlocked bootloader and no OS nor recovery. What can I do to flash TWRP again and install either OOS 10.0.1 zip or 10.0.0 zip? Any help will be great.
Thanks
Click to expand...
Click to collapse
So basically what happened there is TWRP doesn't boot with the oxygenos 10 bootloader. You will need to use the MSM download tool to unbrick your device.
Sent from my ONEPLUS A6003 using Tapatalk
Kaleshwar said:
So basically what happened there is TWRP doesn't boot with the oxygenos 10 bootloader. You will need to use the MSM download tool to unbrick your device.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
But how is that? I was on stable OOS 10 before rooting following this link https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213. As per this, the first step is to flash twrp and that image did flash back when I did it. Any idea why it doesn't work now?
Also, do you have any links for the MSM download tool and any guide if there is?
Thanks
Arnavzz said:
But how is that? I was on stable OOS 10 before rooting following this link https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213. As per this, the first step is to flash twrp and that image did flash back when I did it. Any idea why it doesn't work now?
Also, do you have any links for the MSM download tool and any guide if there is?
Thanks
Click to expand...
Click to collapse
The problem isn't TWRP it's the bootloader. That's all I know. And for the MSM download tool. See attached link below.
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Sent from my ONEPLUS A6003 using Tapatalk
Do not boot the twrp from fastboot it won't work
Just do
Fastboot flash boot twrp.img
Then reboot the device to twrp it will boot to trwp and then flash the new a10 zip and immediately afterwards flash the twrp zip
chintu1234 said:
Do not boot the twrp from fastboot it won't work
Just do
Fastboot flash boot twrp.img
Then reboot the device to twrp it will boot to trwp and then flash the new a10 zip and immediately afterwards flash the twrp zip
Click to expand...
Click to collapse
This doesn't work. It flashes successfully but when I select Reboot Recovery and press the power button, it boots back to the bootloader.
Maybe wrong twrp img
Try the older 3.3.1-12 twrp.img and then try
Also try the following as well
Fastboot flash boot_a twrp.img
Fastboot flash boot_b twrp.img
And try just reboot not reboot to recovery
Kaleshwar said:
The problem isn't TWRP it's the bootloader. That's all I know. And for the MSM download tool. See attached link below.
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
Thanks so much for that! I have been able to recover the phone using MSM download tool. Now will update to 10 using the phones OTA.
However, I have one question, if I update to OOS 10.0.1, do you think this original post on rooting OOS 10, will work for it? https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213 Or do you suggest to not root and wait?
Arnavzz said:
Thanks so much for that! I have been able to recover the phone using MSM download tool. Now will update to 10 using the phones OTA.
However, I have one question, if I update to OOS 10.0.1, do you think this original post on rooting OOS 10, will work for it? https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213 Or do you suggest to not root and wait?
Click to expand...
Click to collapse
You can try it . Looks pretty solid.
Sent from my ONEPLUS A6003 using Tapatalk
Put the TWRP zip and stock boot img on phone (a TWRP img is not a TWRP zip)
Remove Magisk modules first to avoid issues (in TWRP if you cannot boot to system. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242)
Update through local update to 10.3.2 is what I prefer to do. Then I do the following.
Reboot to let phone finish whatever. reboot into bootloader.
1. Fastboot TWRP img - fastboot flash boot twrp-3.3.1-18-enchilada-Q-mauronofrio.img - ( https://sourceforge.net/projects/ma...3.3.1-18-enchilada-Q-mauronofrio.img/download )
2. Use volume up to recovery and power button to boot to recovery
3. Flash 10.3.2 stock boot img while in TWRP (or current ROM stock boot img).
4. Flash TWRP zip while in TWRP (https://sourceforge.net/projects/ma...-enchilada-installer-mauronofrio.zip/download ) or Blu zip (https://github.com/engstk/android_device_oneplus_enchilada/releases)
5. Reboot to recovery
6. Flash Magisk 20.3 while in TWRP
(Flash a Q kernel if you want one other than stock)
7. Reboot system
You are now rooted
Stock boot 10.3 img
https://mega.nz/#!PO5x1bYA!dKq3pbxUdpb16zhuqM_idqvWNLnsu4Ky4IAmYQiQUDw
Most stock boot imgs
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
I had similar situation last evening.
I made the mistake of having a factory reset on rooted 9.0.8 and then trying to flash the 10.0.1
I got the same error, so I had to connect my mobile to my laptop, fastboot to the newest TWRP, flash the TWRP, flash the 9.0.9, flash the 10.0.1, flash magisk 20.x and then everything was working.
xpakage said:
Put the TWRP zip and stock boot img on phone (a TWRP img is not a TWRP zip)
Remove Magisk modules
Update through local update 10.3 or current ROM
Reboot
1. Fastboot TWRP img - fastboot flash boot twrp-3.3.1-16-enchilada-Q-mauronofrio.img - ( https://androidfilehost.com/?fid=4349826312261678088 )
2. Use volume up to recovery and power button to boot to recovery
3. Flash 10.3 stock boot img while in TWRP (or current ROM stock boot img).
4. Flash TWRP zip while in TWRP ( https://androidfilehost.com/?fid=4349826312261678087 ) or Blu zip (https://github.com/engstk/op6/releases/download/r112/blu_spark_r112-oos_op6-op6t_0dd5f9228.zip)
5. Reboot to recovery
6. Flash Magisk 20.1 while in TWRP
(Flash a Q kernel if you want one other than stock)
7. Reboot system
You are now rooted
Stock boot 10.3 img
https://drive.google.com/file/d/1w44cUg815g-H1h_6gObUVPLDTc_dtiMX/view
Most stock boot imgs
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Click to expand...
Click to collapse
This worked for me.. Finally. PS - I did in a slightly different order. I installed twrp first, booted into twrp, made sure I was in slot A. If I wasnt, I rebooted to recovery. If I still wasnt I set slot to A manually then rebooted to recovery again. Flashed the stock boot img you linked to boot, then rebooted to recovery slot b (same process I did to get to slot a) then flashed the stock boot img to boot again THEN finally installed magisk. Booted to system, where it hanged a bit, rebooted before getting into android, but booted in just fine after that..
For some reason if you don't flash stock img to slot A (and maybe slot B too, I did this for good measure) before installing magisk everything dies a horrible death and breaks, which can't even be recovered from /boot /system backups..
EDIT: Tried to reboot into recovery, which reverted back to stock for some reason after doing the above steps. So I proceeded to install the bluspark recovery, rebooted into recovery, made sure I was in slot b, made a back up of the boot image, then flashed bluspark kernel. Got stuck at the unlocked bootloader screen. Rebooted into recovery, restored my /boot back. Still stuck when I try to boot into system. Fixed it by booting back into recovery in slot A flashing stock boot img, then into slot b stock boot, then magisk, but also installed bluspark kernel here because I had a feeling I would lose twrp from flashing to stock boot img, and that the issue was caused by twrp (both twrp-3.3.1-16-enchilada-installer-mauronofrio and twrp-3.3.1-x_blu_spark_v9.108_op6 have this issue). Guess what? Turns out I was right. Having twrp breaks everything after you install magisk, so you need to flash the stock boot img before flashing magisk for some reason.. and cant install twrp again unless you dont mind bricking your phone.
EDIT2: F2FS works, just boot into recovery via fastboot (this should be slot b), change /data to f2fs, boot back into fastboot then into recovery again by fastboot (slot b again), flash stock boot img > magisk > bluspark kernel > f2fs_fstab.zip > f2fs_optimize.zip > factory reset/wipe (from twrp before rebooting), done just reboot into system. You of course lose twrp because magisk doesnt like twrp on oos 10.x for some reason, and will need to set everything up again to cause of the wipe. If you dont factory reset/wipe from twrp before booting into system your system will crash and reboot every time you boot into android, then have to do all the steps I listed again.
EDIT3: Never mind, I was wrong, f2fs makes almost all your apps and storage unusable. Not sure if it's cause of the rom (OOS10.3.0) or because we have to flash stock boot.img and get rid of twrp before booting into system. Either way, f2fs has never really been stable or fun to get working so better to stick to ext4.. that few percent performance boost isnt worth it.
EDIT4: This is my last update. After experimenting with different things, bricking my phone, restoring it via fastboot rom, many many times, I've verified the simplest and cleanest way to install magisk.. Do note you wont be able to keep twrp.
Method A - If you already have twrp
Boot recovery into slot a, flash your rom's stock boot.img, then boot into your recovery in slot b (dont boot into slot a recovery because slot a wont have twrp anymore), flash your rom's stock boot.img, magisk and (optional) your kernel of choice (or not) in that order, then you can boot boot into system. That's it.
Method B - If you don't have twrp
Boot into fastboot, and from your cmd/terminal run fastboot flash boot yourtwrp.img (I suggest Mauronofrio's twrp-3.3.1-16-enchilada-Q-mauronofrio.img or newer). Use your volume buttons to select boot into recovery. Make sure your active slot is B, (if it isnt, install twrp (bluspark and Mauronofrio's twrp both work great) by zip, then follow the steps above in method A). Once you've verified you're in slot B flash your rom's stock boot.img, magisk and (optional) your kernel of choice (or not) in that order, then you can boot into system. That's it.
Maybe @mauronofrio or @eng.stk can verify why magisk or twrp bricks the system when you install them together on OOS 10.
not working
sir i follow your steps but phone is stuck on boot i have official version a10 10.3.0 update on 25.12.19
pls tell me how i get root access....
gauravkapoor99150 said:
sir i follow your steps but phone is stuck on boot i have official version a10 10.3.0 update on 25.12.19
pls tell me how i get root access....
Click to expand...
Click to collapse
U need to flash the magisk v22 zip file through the .108 TWRP recovery
Sent from my ONEPLUS A6003 using Tapatalk
RASTAVIPER said:
U need to flash the magisk v22 zip file through the .108 TWRP recovery
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
sir can you send me a link
lemon07r said:
Maybe @mauronofrio or @eng.stk can verify why magisk or twrp bricks the system when you install them together on OOS 10.
Click to expand...
Click to collapse
@mauronofrio wrote the following in his TWRP thread a while ago:
So little update, after some tests i'm sure there is a compatibility problem between twrp and magisk, i was able to get only one of them, so actually i don't know how to proceed, i need to understand if it is a twrp problem or a magisk problem, TWRP is in stand-by for now.
There are not problems on Android Pie, if you need of the twrp on android Q just flash in boot partition the Q .img (fastboot flash boot twrp.img) and then reboot from fastboot in recovery. Before publishing the twrp I had not tested magisk and twrp together.
On Android 10 use only magisk 19.4
Click to expand...
Click to collapse
xpakage said:
Put the TWRP zip and stock boot img on phone (a TWRP img is not a TWRP zip)
Remove Magisk modules first to avoid issues (in TWRP if you cannot boot to system. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242)
Update through local update to 10.3.2 is what I prefer to do. Then I do the following.
Reboot to let phone finish whatever. reboot into bootloader.
1. Fastboot TWRP img - fastboot flash boot twrp-3.3.1-18-enchilada-Q-mauronofrio.img - ( https://sourceforge.net/projects/ma...3.3.1-18-enchilada-Q-mauronofrio.img/download )
2. Use volume up to recovery and power button to boot to recovery
3. Flash 10.3.2 stock boot img while in TWRP (or current ROM stock boot img).
4. Flash TWRP zip while in TWRP (https://sourceforge.net/projects/ma...-enchilada-installer-mauronofrio.zip/download ) or Blu zip (https://github.com/engstk/android_device_oneplus_enchilada/releases)
5. Reboot to recovery
6. Flash Magisk 20.3 while in TWRP
(Flash a Q kernel if you want one other than stock)
7. Reboot system
You are now rooted
Stock boot 10.3 img
https://mega.nz/#!PO5x1bYA!dKq3pbxUdpb16zhuqM_idqvWNLnsu4Ky4IAmYQiQUDw
Most stock boot imgs
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Click to expand...
Click to collapse
Basically worked for me, too, with 2 exceptions:
- this tool to remove magisk modules etc. wouldn't be flashed, always ended in an unnamed error; probably the cause for some other problems?
- flashing boot.img (V 10.3.4 from this thread) didn't work for me, I always ended up in twrp's splash screen
- got it solved by dirty flashing the full V 10.3.4 ROM (again from the above thread)
Many thanks once again!
Hello.yesterday i tried to root my OnePlus 7 pro.i unlocked the bootloader first and then I have installed the twrp on slot a and slot b.then I have installed magisk,from this moment the WiFi on my phone stopped working.(when I am turning them on the automatically turned off)I tried again to flash stock ROM and twrp but when I install magisk I had the same problem.Then somehow I accidentally bricked the phone and today I have the stock ROM with unlocked bootloader and I need your help to root.
You my friend need to learn how to write clearly xD.
Continuing where you left off this is how you achieve root with Magisk:
1.Boot into the bootloader
2. Using cmd (I assume you installed ADB drivers and fast boot drivers already if not Youtube a guide) use the following command:
fastboot boot <twrp image file here>
once you're in TWRP you can flash the TWRP install ZIP.
Once you're done with that Reboot -> Recovery.
3. Flash Magisk and you're done.
I doubt you're really bricked. Since you have the bootloader unlocked just do the button combo to get into recovery or the bootloader.
Thats the method i did.the real problem is the magisk.are there stable or better magisk versions?
The phone now is stock and unrooted
panagiwtis90 said:
Thats the method i did.the real problem is the magisk.are there stable or better magisk versions?
Click to expand...
Click to collapse
20.3 is the latest version and works perfectly fine on mine
o.o
How is it not stable?
I dont know if i did something wrong.the only difference from HermitDash method is that this comand (fastboot boot <twrp image file here>) not worked for me so i used this
fastboot flash boot_a path-to-twrp.img" and this fastboot flash boot_b path-to-twrp.img"
panagiwtis90 said:
I dont know if i did something wrong.the only difference from HermitDash method is that this comand (fastboot boot <twrp image file here>) not worked for me so i used this
fastboot flash boot_a path-to-twrp.img" and this fastboot flash boot_b path-to-twrp.img"
Click to expand...
Click to collapse
Can you Share a screen capture of your twrp file and your fastboot command
I will try again later and post screenshots
Dont understand.
HermitDash said:
You my friend need to learn how to write clearly xD.
Continuing where you left off this is how you achieve root with Magisk:
1.Boot into the bootloader
2. Using cmd (I assume you installed ADB drivers and fast boot drivers already if not Youtube a guide) use the following command:
fastboot boot <twrp image file here>
once you're in TWRP you can flash the TWRP install ZIP.
Once you're done with that Reboot -> Recovery.
3. Flash Magisk and you're done.
I doubt you're really bricked. Since you have the bootloader unlocked just do the button combo to get into recovery or the bootloader.
Click to expand...
Click to collapse
I dont understand why they say after you boot into twrp from fastboot to reflash twrp.zip file in twrp. I never do and it still works the same. And when you do flash the twrp.zip it says your now unrooted flash magisk. And when you flash magisk it actually then unroots magisk. The best way to root the oneplus 7 pro is using payload extractor and patching the boot.img with magisk. and booting magiskpatched.img then after installing the magisk manager go to modules and flash twrp from there. alot easier.
Can you explain this easier method you said here to try it as i am a noob?
panagiwtis90 said:
Can you explain this easier method you said here to try it as i am a noob?
Click to expand...
Click to collapse
Okay, new to this thread. Where are you at right now? Booting? Which OS, TWRP, Magisk versions?
I am at 10.3 stock rom without root and twrp(just unlocked bootloader)
panagiwtis90 said:
I am at 10.3 stock rom without root and twrp(just unlocked bootloader)
Click to expand...
Click to collapse
I am on the same version what I did was find the patched boot image with magisk for Android 10 flashed it using adb then installed magisk manager and I had root.
https://forum.xda-developers.com/on...atched-boot-image-oneplus-7-pro-t3964345/amp/
panagiwtis90 said:
I am at 10.3 stock rom without root and twrp(just unlocked bootloader)
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
Follow this guide and you won't need to use the patched boot,img file. I've never liked using the patched boot img.
Thank you GeekMcLeod your method worked
amaroney55 said:
I dont understand why they say after you boot into twrp from fastboot to reflash twrp.zip file in twrp. I never do and it still works the same. And when you do flash the twrp.zip it says your now unrooted flash magisk. And when you flash magisk it actually then unroots magisk. The best way to root the oneplus 7 pro is using payload extractor and patching the boot.img with magisk. and booting magiskpatched.img then after installing the magisk manager go to modules and flash twrp from there. alot easier.
Click to expand...
Click to collapse
It's just easier than having to manually extract the boot.img
fastboot boot twrp is just to get twrp up and running then flashing the script actually installs it.
Yes it does say that it'll unroot you but for those that are unrooted already this step doesn't do anything.
After flashing you reboot TWRP so it works fresh post-script.
Then install magisk as usual and reboot to system done.
This is if you want both TWRP and Magisk all done at the same time vs booting the boot.img installing Magisk then installing TWRP where I can have it all done within TWRP which is the usual route people take to get to root.
My comment below in red font:
amaroney55 said:
I dont understand why they say after you boot into twrp from fastboot to reflash twrp.zip file in twrp. I never do and it still works the same.
Fastboot boot twrp just remotely boots a "temporary" (one time) instance of TWRP, but does not install TWRP to the device. Flashing the TWRP installer zip is for installing TWRP on the device. This is optional and a matter of personal preference, and not needed to achieve root. What the installer zip does, is extract the boot.img and injects TWRP, then installs that modified boot.img back to the phone.
And when you do flash the twrp.zip it says your now unrooted flash magisk.
Correct. When the installer zip patches the boot.img to install TWRP (as described above), root is removed.
And when you flash magisk it actually then unroots magisk.
Not correct. Magisk roots the phone. If you flashed Magisk and did not have root, what may be happened, is that you may have flashed Magisk to one slot, then somehow booted to the other (unrooted) slot.
The best way to root the oneplus 7 pro is using payload extractor and patching the boot.img with magisk. and booting magiskpatched.img then after installing the magisk manager go to modules and flash twrp from there. alot easier.
Manually patching the boot.img is certainly a valid way to achieve root, and maybe more reliable. I'd hesitate to say it is "easier".
Also, if you flash TWRP as a Magisk module, you will still need to flash Magisk again to have root. Flashing TWRP by that method will still unroot the phone, same as the other method (as I described above).
Click to expand...
Click to collapse
---------- Post added at 08:56 AM ---------- Previous post was at 08:44 AM ----------
panagiwtis90 said:
I dont know if i did something wrong.the only difference from HermitDash method is that this comand (fastboot boot <twrp image file here>) not worked for me so i used this
fastboot flash boot_a path-to-twrp.img" and this fastboot flash boot_b path-to-twrp.img"
Click to expand...
Click to collapse
You did it wrong. Those two command do completely different things. So the difference in commands is a big one.
As I mentioned above, fastboot boot TWRP.img just remotely boots a temporary (one time) instance of a boot.img that has been patched to include TWRP. Then the correct way to install TWRP to the phone is (from the temporary booted TWRP) flash the TWRP installer zip, which properly extracts your phone's boot.img partition, patches it to install TWRP, then installs the modified boot.img back to the phone.
Fastboot flash boot TWRP.img does something completely different. It flashes the img to the boot partition. "Flash" is the action in this case, and "boot" is the location (not the action). The TWRP img is not meant to be installed to the phone. Don't know for sure, but I highly suspect that boot.img has some differences depending on your 7 Pro model. So when folks incorrectly flash TWRP.img, they are replacing the phone's kernel and breaking WiFi, and sometimes cell network and/or Bluetooth. Again, the correct way to install TWRP is to use the installer zip (as described in the previous paragraph) which properly takes your phones specific boot.img and patches it.
What folks should understand, is that A/B partition devices (like the 7 Pro) do not have a discrete recovery partition. Recovery is part of the boot partition, which also contains the kernel. So by doing "flash boot" you are messing with the kernel in ways you should not, and therefore results like broken WiFi is not surprising.
---------- Post added at 09:06 AM ---------- Previous post was at 08:56 AM ----------
panagiwtis90 said:
Thats the method i did.the real problem is the magisk.are there stable or better magisk versions?
Click to expand...
Click to collapse
Magisk if fine. Your issues are due to pilot error, as I've described above.
Hi, I am running the latest MIUI on my redmi note 7 pro. I unlocked the bootloader and tried to flash both orange fox and twrp recoveries. The flashing process completes fine but when I try to boot the device to recovery mode or system it says this device has been destroyed. I tried to boot into recovery using fastboot boot recovery_name.img but that doesn't work either. Please help.
check out Technobuzznet's video on Youtube regarding system has been destroyed. I had followed his steps and came out of it victorious.
You should flash stock ROM using Mi flash first then flash a custom recovery you want and afterwards flash vbmeta file.
I would recommend to connect device to fastboot mode first and then flash the vbmeta file using command fastboot flash vbmeta vbmetafile, then try to reboot to recovery, if this doesn't help then you can try the flashing method mentioned above.
Here is how I fixed it.
1. Flashed the vbmeta.img from pixel experience plus rom zip by
fastboot flash vbmeta vbmeta.img
2. Rebooted into fastboot mode again and flashed latest orangefox.img
3. Booted into orangefox deleted system, dalvik, cache,
4. Formatted data partition (cause it was encrypted)
5. Flashed PE plus rom.
12S Ultra unofficial TWRP - link MEGA
Credit - UnofficialTWRP
They released TWRP under 12S Pro, but the code name is Thor which stands for 12S Ultra, and after flashing, I do confirm this is for 12S Ultra.
now they have a proper 12S Ultra section!
Download the image and rename as recovery.img for simplicity.
fastboot boot recovery.img (or full file name)
in TWRP, go to "Advanced" and "flash this twrp."
edit: the recovery image file is too large to be flashed directly via fastboot, so you need to boot first then flash using twrp!
edit2: backup and restore function may not be working properly on this version of twrp! I get boot loops everytime I do a full system backup and full restore after bricking the device, especially on the data partition. Clean installing rom then restoring data only still get boot loops. so use it with caution.
I suggest you to use 3rd party backup apps to do backups on apps and data, and stick to the flashing and other functions only for twrp.
original source unofficialtwrp.com
Nabicook said:
12S Ultra unofficial TWRP - link MEGA
Credit - UnofficialTWRP
They released TWRP under 12S Pro, but the code name is Thor which stands for 12S Ultra, and after flashing, I do confirm this is for 12S Ultra.
Download the image and rename as recovery.img for simplicity.
fastboot boot recovery.img (or full file name)
in TWRP, go to Advanced and flash this twrp.
original source unofficialtwrp.com
Click to expand...
Click to collapse
Awesome thanks. But why not Fastboot flash recovery recovery.img?
No. You must type fastboot flash boot recovey. img
dungnghien said:
No. You must type fastboot flash boot recovey. img
Click to expand...
Click to collapse
No I'm pretty sure it's:
fastboot flash recovery twrp.img
However my question was why the method outlined by @Nabicook vs this method. Is it because of the dual partition?
GodKingKnight said:
Awesome thanks. But why not Fastboot flash recovery recovery.img?
Click to expand...
Click to collapse
Because not only it is the method unofficialtwrp suggested, but also the size of the recovery img file is too large to be flashed via fastboot.
I already tried
fastboot flash recovery recovery.img
fastboot flash recovery_a recovery.img
and so on, but all failed.
only way to properly install this version of twrp is to boot first then let twrp to install itself to both a/b partitions.
Hi!
I'm following your guide...and after uploading recovery nothing happens
rebooting into recovery through ADB or just using buttons...still sends me into fastboot mode
What can I do?
joiliko said:
Hi!
I'm following your guide...and after uploading recovery nothing happens
rebooting into recovery through ADB or just using buttons...still sends me into fastboot mode
What can I do?
Click to expand...
Click to collapse
are you sure you did
fastboot boot (your recovery file name).img
it should automatically boot into twrp without touching anything from fastboot mode.
then install twrp through the advanced option in twrp
Nabicook said:
are you sure you did
fastboot boot (your recovery file name).img
Click to expand...
Click to collapse
Great many thanks! I was actually doing flash boot
Nabicook said:
then install twrp through the advanced option in twrp
Click to expand...
Click to collapse
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
joiliko said:
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
Click to expand...
Click to collapse
yeah you can try flashing stock boot img, and if that doesnt work, you can download fastboot rom and flash stock rom using flash all without wiping data(there is .bat file that says something like install without formatting).
That will fix any kind of brick issues of xiaomi device, and you just redo the twrp part.
joiliko said:
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
Click to expand...
Click to collapse
How to Extract payload.bin and get stock boot image file
To extract the payload.bin file from Android stock firmware and get stock boot image file, you should refer to the instructions given in here.
www.droidwin.com
My idea worked!
I used the method above to extract boot.img & flashed it successfully
Can someone tell me why wipe data and settings dosent work on my 12s ultra every time reboots the twrp after i press the icon... Im try at 7.5 version the same and on 7.2