Sorry if this has been answered already, but I can't find anything about it. As far as I can see, the only way to have working Magisk now on EMUI 9.0 is to install it to recovery_ramdisk and use that to boot the phone. That is working fine. Is there any way to install TWRP as well, since it can't go in the recovery_ramdisk partition? I tried
Code:
fastboot flash erecovery_ramdisk
to flash it to eRecovery, but that didn't work and gave me this error:
Code:
FAILED (remote: Command not allowed)
Any ideas?
The specific reason I wanted to get into TWRP was to install the HyperPlus custom kernel, and I can't think of another way to do it.
you have unlocked bootloader ?
Where you found TWRP for EMUI9?
I was trying to use the Oreo 3.2.1 TWRP. I'm now realising that might not work...
where magisk img u flash for your phone
Could you let me know your process to flash magisk to EMUI 9? What version stock rom do you have?
Thanks!
stridechicken said:
Sorry if this has been answered already, but I can't find anything about it. As far as I can see, the only way to have working Magisk now on EMUI 9.0 is to install it to recovery_ramdisk and use that to boot the phone. That is working fine. Is there any way to install TWRP as well, since it can't go in the recovery_ramdisk partition? I tried
Code:
fastboot flash erecovery_ramdisk
to flash it to eRecovery, but that didn't work and gave me this error:
Code:
FAILED (remote: Command not allowed)
Any ideas?
The specific reason I wanted to get into TWRP was to install the HyperPlus custom kernel, and I can't think of another way to do it.
Click to expand...
Click to collapse
You have to install TWRP to recovery_ramdisk, then install the TWRP .img to erecovery_ramdisk from inside TWRP. Then you can install the patched magisk .img to recovery_ramdisk via fastboot.
Tristl said:
You have to install TWRP to recovery_ramdisk, then install the TWRP .img to erecovery_ramdisk from inside TWRP. Then you can install the patched magisk .img to recovery_ramdisk via fastboot.
Click to expand...
Click to collapse
where can i get twrp for emui 9.0 or 9.1 ?
daniel11609 said:
where can i get twrp for emui 9.0 or 9.1 ?
Click to expand...
Click to collapse
Sadly, there isn´t any "official" TWRP recovery for Android 9.0 Pie / EMUI 9.0 on P10 Plus available. However I have been using this one: https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3914798 (TWRP for Mate 9, works for P10 Plus because of similar chipset) successfully for emergency tasks like removing failing Magisk modules and getting out of bootloop, accessing the filesystem or writing *.img files. Be careful though, I don´t think it will work for installing zips or system updates.
Tristl said:
Sadly, there isn´t any "official" TWRP recovery for Android 9.0 Pie / EMUI 9.0 on P10 Plus available. However I have been using this one: https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3914798 (TWRP for Mate 9, works for P10 Plus because of similar chipset) successfully for emergency tasks like removing failing Magisk modules and getting out of bootloop, accessing the filesystem or writing *.img files. Be careful though, I don´t think it will work for installing zips or system updates.
Click to expand...
Click to collapse
thanks a lot, i really need it rn as well, because i have usb debugging disabled and ran into a bootloop.
---------- Post added at 11:01 PM ---------- Previous post was at 10:56 PM ----------
daniel11609 said:
thanks a lot, i really need it rn as well, because i have usb debugging disabled and ran into a bootloop.
Click to expand...
Click to collapse
im pretty lost right now, i had "oem unlock" disabled, so fastboot shows FRP lock, i cant flash anything. how to get around that when i cant enter my system?
edit: fixed it just booted without root and enabled adb to fix magisk
Tristl said:
You have to install TWRP to recovery_ramdisk, then install the TWRP .img to erecovery_ramdisk from inside TWRP. Then you can install the patched magisk .img to recovery_ramdisk via fastboot.
Click to expand...
Click to collapse
so it would replace the eRecorery? Isnt that quite risky because the erecovery might safe you when i get softbricks / bootloops etc
Related
Hi all,
Since there is no TWRP for the MI A2 in Android Pie we can only use magisk to root.
The problem is that Xiaomi does not release the update zip and we can not patch the boot.img of the last security patch.
I have discovered a method to extract the boot img without root and then be able to patch it to have ROOT!
Nevermind, now TWRP supports PIE...
UNLOCKING THE BOOTLOADER:
Tap 7 times in build number for enable developer options
Enable OEM Unlock in developer options
Reboot the phone in fastboot:
Code:
adb reboot bootloader
Unlock the BL:
Code:
fastboot oem-unlock
Unlock critical flashing:
Code:
fastboot flashing unlock_critical
Reboot and wait for the phone boot up:
Code:
fastboot reboot
Now you have the bootloader unlocked!
INSTALLING TWRP AND MAGISK:
Download TWRP 3.3.0-0
Boot to the TWRP:
Code:
fastboot boot twrp-3.3.0-0-jasmine_sprout.img
It will ask for decryption password, click on cancel
Swipe for allow system modifications
Go to install and select the Magisk.zip
Install it and reboot
Wait for the phone boots up
Now install Magisk.apk
Enjoy root!
DOWNLOADS:
TWRP
MAGISK.APK
https://twrp.me/xiaomi/xiaomimia2.html
joaomiguelsm said:
https://twrp.me/xiaomi/xiaomimia2.html
Click to expand...
Click to collapse
Oh f*** I didn't see that TWRP...
Updated!
Rortiz2 said:
Oh f*** I didn't see that TWRP...
Updated!
Click to expand...
Click to collapse
would you help? i just flashed this twrp which worked fine but i'm not able to flash custom roms . or whenever i try to, it got failed with a massage "updater process ended with error 1".
your guidance would be helpful..thanks
Amnvlad said:
would you help? i just flashed this twrp which worked fine but i'm not able to flash custom roms . or whenever i try to, it got failed with a massage "updater process ended with error 1".
your guidance would be helpful..thanks
Click to expand...
Click to collapse
That's because the ROM's are only for Android Oreo.. Wait until anyone compile a ROM for Android pie.
Sent from my Mi A2 using Tapatalk
Where do we get Magisk.zip? From the website? Sorry been away from the rooting scene for a long time.
Also I'm guessing this only use TWRP temporarily?
how does one go about to keep the usual ota after unlocking and flashing magisk?
L.E. does the unlock wipe the data on the phone?
---------- Post added at 09:15 AM ---------- Previous post was at 09:14 AM ----------
[/COLOR]
Rortiz2 said:
That's because the ROM's are only for Android Oreo.. Wait until anyone compile a ROM for Android pie.
Sent from my Mi A2 using Tapatalk
Click to expand...
Click to collapse
Hi Terresa. Havoc OS, RR, Pixel roms, aren't they pie based roms ? I am getting the same error while flashing any ram using temp TWRP. I also tried going back to stock Orio and followed the same procedure still can't flash any roms . I followed every tutorial on MI A2 forums stil could not manage to install any rom
I can't install the TWRP when I reboot by holding down the volume + key with the "Fastboot reboot" command. The phone restarts normally
After flashing magisk i dont need to flash recovery?
lately I did a clean install of OOS 10.0.1 on my International 6t. Installed OOS and magisk from TWRP.
After booting there was a Magisk Manager in applications claiming that Magisk itself was not installed. I tried to install Magisk from Manager, but failed. Then I reboot the phone into the recovery and TWRP was gone!! There was only a stock recovery. Well, I tried to run TWRP from computer with 'fastboot boot .\twrp-3.3.1-28-fajita-Q-mauronofrio.img'. Error - "remote: unknown command".
I searched forum and found a thread fastboot boot twrp.img FAILED (remote: unknown command). @dbarrett480 wrote: 'Twrp can't flash anything to system in A10 right now, so unless that is fixed there is no point at this moment anyway. A10 uses a virtualized system partition which doesn't allow R/W access to system....'. Does it mean that rooting is not possible with stock OOS and only possible solution is to use custom ROM?
It is. Look for the patched boot.img and flash that through fastboot. Make sure to install magisk manager first.
BesoC said:
Well, I tried to run TWRP from computer with 'fastboot boot .\twrp-3.3.1-28-fajita-Q-mauronofrio.img'. Error - "remote: unknown command".
I searched forum and found a thread fastboot boot twrp.img FAILED (remote: unknown command). @dbarrett480 wrote: 'Twrp can't flash anything to system in A10 right now, so unless that is fixed there is no point at this moment anyway. A10 uses a virtualized system partition which doesn't allow R/W access to system....'. Does it mean that rooting is not possible with stock OOS and only possible solution is to use custom ROM?
Click to expand...
Click to collapse
The information you found is outdated. I'm surprised you didn't properly read through the official TWRP thread here, more specifically this post clarifies the error in your use of fastboot (or better said: the use of fastboot according to the mistakes made by OnePlus). Which is also mentioned several times in the page you linked to.
As a senior member, please don't create new threads inquiring information you could easily find. Even though the methods to obtain it have been challenging for a short while, being able to achieve root has never been interrupted for this device. Even without being able to modify system files. Systemless rules!
Wrapped with delicious Fajita [emoji896]
bokkoman said:
It is. Look for the patched boot.img and flash that through fastboot. Make sure to install magisk manager first.
Click to expand...
Click to collapse
So, should do following:
Install Magisk Manager
Flash patched boot.img through fastboot
Install TWRP
Install Magisk
Is it correct?
The patched boot.img already contains magisk.
But you don't need twrp to be rooted, unless you really want to use it for something else... But i don't use it anymore. So I'm fully stock, except that I'm unlocked and rooted.
So it should be:
1. Install magisk manager.
2. Flash boot.img
3. Enjoy. But check magisk manager if it was successful.
bokkoman said:
The patched boot.img already contains magisk.
But you don't need twrp to be rooted, unless you really want to use it for something else... But i don't use it anymore. So I'm fully stock, except that I'm unlocked and rooted.
So it should be:
1. Install magisk manager.
2. Flash boot.img
3. Enjoy. But check magisk manager if it was successful.
Click to expand...
Click to collapse
Regarding all that was said here, is rooting possible by following these steps?
Reboot
Fastboot TWRP img
Use volume up to recovery and power button to boot to recovery
Flash 10.0.1 stock boot img from TWRP
Flash TWRP zip
Reboot to recovery
Flash Magisk 20.1
Flash kernel if want
Reboot system
Click to expand...
Click to collapse
BesoC said:
Regarding all that was said here, is rooting possible by following these steps?
Click to expand...
Click to collapse
Yes, this tutorial with the twrp should work ...
BesoC said:
Regarding all that was said here, is rooting possible by following these steps?
Click to expand...
Click to collapse
That's only if you need TWRP.
But for what I've been reading, you don't need TWRP and then i suggest to not install it.
Just flash everything stock and keep it that way. Only thing to flash is the patched boot.img with root in it.
You can always update Android from the settings and patch/install boot with magisk manager on inactive slot. This will keep your device rooted without the need of TWRP.
Here what I found:
https://forum.xda-developers.com/showpost.php?p=81111389&postcount=145
Today I installed the new update, 10.0.1 for OP 6T and then I discovered that there is no magisk patched boot.img yet. I extracted it with payload dumper, patched with the installed magisk and flashed successfully.
I uploaded it to my drive for others. https://drive.google.com/open?id=1kb...VgWNaWgLN6j17b
The commands for flashing are:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Maybe someone can add it to the first post.
original 10.0.1 boot.img https://drive.google.com/open?id=1HP...Du8zCOFMXInjXq
Click to expand...
Click to collapse
I used this method to root 10.0.01
https://forum.xda-developers.com/oneplus-6t/how-to/ultimateguide-t4004367
I went from rooted 9.0.17 to 10 to 10.0.01
Never had an issue and everything works fine for me.
Today I installed the new update, 10.0.1 for OP 6T and then I discovered that there is no magisk patched boot.img yet. I extracted it with payload dumper, patched with the installed magisk and flashed successfully.
I uploaded it to my drive for others. https://drive.google.com/open?id=1kb...VgWNaWgLN6j17b
The commands for flashing are:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Maybe someone can add it to the first post.
original 10.0.1 boot.img https://drive.google.com/open?id=1HP...Du8zCOFMXInjXq
Click to expand...
Click to collapse
My phone get stuck on the boot animation by following this guide. I have not factory reset my phone.
DrXperience said:
My phone get stuck on the boot animation by following this guide. I have not factory reset my phone.
Click to expand...
Click to collapse
I still don't get why people don't use the good old way:
fastboot flash boot twrp.img (latest version)
If you just need root use twrp to flash Magisk zip
If you need twrp flash twrp installer also
Reboot
All the mess before was because we didn't have a working TWRP! Now that we have it don't need to use patched boot img made by others.
Hello all...
Just a quick question as I am reading and seeing so many different answers. I have the UNLOCKED US version OnePlus 8 Pro (IN2025) Which is currently running Oxygen OS 11.IN11AA (Android 11 Official). I have successfully unlocked the bootloader and am ready to root with Magisk. I am at a loss because I dont know which Magisk to use or how to properly flash it. I have Magisk Manager 8.0.2 and have Magisk version 21.0
I have also downloaded the patched boot image from here... https://forum.xda-developers.com/oneplus-8-pro/how-to/root-patched-boot-img-android-11-op8-t4174919
What am I doing wrong? Can someone please just give me a quick rundown... I am not new to rooting just haven't done in in over a year. Thank you!
Don't think your doing anything wrong, just need to get that image on your pc, and fastboot flash it to both a/b slots then reboot your phone and you should have root available
adb reboot bootloader
fastboot boot (name of image).img - Try this one first as it just allows you to see if the phone boots up fine, if it does reboot back into the bootloader and then do the following...
fastboot flash boot_a (name of image).img
fastboot flash boot_b (name of image).img
fastboot reboot
How do I get Magisk 21.0 to install through Magisk Manager?
You don't, that's why you've downloaded a patched img, that has been patched with magisk already, just need to flash it accordingly
CraigHardy said:
You don't, that's why you've downloaded a patched img, that has been patched with magisk already, just need to flash it accordingly
Click to expand...
Click to collapse
This is what I am getting after following your directions to a T!
I also flashed to both partitions. Please see attachments. I sent 2 screenshots.
You don't do the install from magisk, have to copy the patched img to a pc where you have adb/fastboot installed then install from command prompt
CraigHardy said:
You don't do the install from magisk, have to copy the patched img to a pc where you have adb/fastboot installed then install from command prompt
Click to expand...
Click to collapse
I did not do the install through Magisk Manager I did the install via adb and fastboot in fastboot mode. It Said flash successful. But when I go into Magisk Manager after rebooting, nothing changes.
Doesn't work. Download the patched image, put it on the phone, use magisk canary manager to patch it again, transfer it off your phone, then boot into Fastboot and flash it.
It has to be patched in the phone it will be installed to otherwise it will not work.
akinkoff85 said:
I did not do the install through Magisk Manager I did the install via adb and fastboot in fastboot mode. It Said flash successful. But when I go into Magisk Manager after rebooting, nothing changes.
Click to expand...
Click to collapse
Use the beta magisk.
Re-patch it in your newly updated magisk manager then flash to both slots..
Also verify the size of the file prior to flashing.. Mine was 96MB
Here is the exact size.
Problem uploading image
I am a little confused now... I uninstalled root for a few days and now have the second release of android 11... I am in fastboot mode doing fastboot flash boot... then the file name and all it says is waiting for device?? Any help??
dladz said:
Use the beta magisk.
Re-patch it in your newly updated magisk manager then flash to both slots..
Also verify the size of the file prior to flashing.. Mine was 96MB
Click to expand...
Click to collapse
Indeed, using the beta version worked for me! Thanks for the tip!
imval said:
Indeed, using the beta version worked for me! Thanks for the tip!
Click to expand...
Click to collapse
No worries man, glad you're sorted
CraigHardy said:
Don't think your doing anything wrong, just need to get that image on your pc, and fastboot flash it to both a/b slots then reboot your phone and you should have root available
adb reboot bootloader
fastboot boot (name of image).img - Try this one first as it just allows you to see if the phone boots up fine, if it does reboot back into the bootloader and then do the following...
fastboot flash boot_a (name of image).img
fastboot flash boot_b (name of image).img
fastboot reboot
Click to expand...
Click to collapse
What is the explanation as to why one needs to fastboot flash Magisk to both slots instead of using the following command:
adb reboot bootloader
fastboot getvar current-slot
*in my case Slot B*
fastboot flash boot_b magisk_patched.img
fastboot reboot
rodken said:
What is the explanation as to why one needs to fastboot flash Magisk to both slots instead of using the following command:
adb reboot bootloader
fastboot getvar current-slot
*in my case Slot B*
fastboot flash boot_b magisk_patched.img
fastboot reboot
Click to expand...
Click to collapse
You can, however flashing to both slots is seemingly easier.
Personally I wouldn't flash at all.
Just boot to avoid the possibility of a bad boot.
akinkoff85 said:
Hello all...
Just a quick question as I am reading and seeing so many different answers. I have the UNLOCKED US version OnePlus 8 Pro (IN2025) Which is currently running Oxygen OS 11.IN11AA (Android 11 Official). I have successfully unlocked the bootloader and am ready to root with Magisk. I am at a loss because I dont know which Magisk to use or how to properly flash it. I have Magisk Manager 8.0.2 and have Magisk version 21.0
I have also downloaded the patched boot image from here... https://forum.xda-developers.com/oneplus-8-pro/how-to/root-patched-boot-img-android-11-op8-t4174919
What am I doing wrong? Can someone please just give me a quick rundown... I am not new to rooting just haven't done in in over a year. Thank you!
Click to expand...
Click to collapse
Watch this video it helped me out allot
dladz said:
You can, however flashing to both slots is seemingly easier.
Personally I wouldn't flash at all.
Just boot to avoid the possibility of a bad boot.
Click to expand...
Click to collapse
I did not know that one can just boot a magisk_patched.img instead of flashing.
rodken said:
I did not know that one can just boot a magisk_patched.img instead of flashing.
Click to expand...
Click to collapse
It's preferable.
There are some things to note.
1st. You are only booting it, meaning if you reboot; you will start using the installed / flashed image and the booted image will be lost.
2nd. For the above reason. If you want to make root permanent you have to open magisk after opening and then click install - install directly.
As magisk will already have root access, it will be able to accomplish patching, if you tried this whilst unrooted it would fail, or not be an option.
3rd. By booting you avoid the potential bootloop problems you can and almost will have at some point if you always flash, bad images are pretty rife for a number of reasons.
I've got a large guide for rooting in the guides section which covers all the bases and their shortcomings /benefits.
hi, i have a question yesterday i have unlocked my mate 10 lite (RNE-L21) boot loader for doing that, i used the huawei multi tool form Team MT and now i want install the twrp recovery,my question is how can i approach this step? what recovery should i download using the multi tool?
my phone is mate 10 lite: RNE-L21
and the build number is RNE-L21 8.0.0.346 (C432patch01)
i hope anyone can help me thanks.
Tilt6x said:
hi, i have a question yesterday i have unlocked my mate 10 lite (RNE-L21) boot loader for doing that, i used the huawei multi tool form Team MT and now i want install the twrp recovery,my question is how can i approach this step? what recovery should i download using the multi tool?
my phone is mate 10 lite: RNE-L21
and the build number is RNE-L21 8.0.0.346 (C432patch01)
i hope anyone can help me thanks.
Click to expand...
Click to collapse
IMO the best TWRP for RNE on Oreo is TWRP 3.2.1-0 by pretoriano80 , link:
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
-Alf- said:
IMO the best TWRP for RNE on Oreo is TWRP 3.2.1-0 by pretoriano80.
Click to expand...
Click to collapse
hi, i downloaded the recovery but when i try to boot it (in fast boot mode) without flashing i get this
(when i type: fastboot boot recovery.img)
Downloading 'Boot.img'...
OKAY [ 0.858s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.874s
(i have the boot loader unlocked because when i boot i get "your phone has bee unlocked and cannot be trusted")ù
i hope, you or someone can help me, thanks
Tilt6x said:
when i try to boot it (in fast boot mode) without flashing
Click to expand...
Click to collapse
Hello, I’m not sure I fully understand your question, mostly what you mean by "without flashing".
TWRP is basically an advanced recovery for a phone that can act as a replacement of the Stock recovery. So if you want to use TWRP, you have to install it over Stock recovery. In fastboot mode run command
fastboot flash recovery_ramdisk (name-of-TWRP-file).img
Once it’s completed, type the command
fastboot reboot
and unplug your phone.
-Alf- said:
Hello, I’m not sure I fully understand your question, mostly what you mean by "without flashing".
TWRP is basically an advanced recovery for a phone that can act as a replacement of the Stock recovery. So if you want to use TWRP, you have to install it over Stock recovery. In fastboot mode run command
fastboot flash recovery_ramdisk (name-of-TWRP-file).img
Once it’s completed, type the command
fastboot reboot
and unplug your phone.
Click to expand...
Click to collapse
sorry but i was afraid of me being dumb with android mod and a friend of mine told me to "boot" the recovery without flashing it before, but now i used the huawei multi tool and prorerly flashed your recovery and my phone i working fine, now i need your help one last time, please tellme how can i root my device now that i have the twrp recovery installed. thanks
Tilt6x said:
sorry but i was afraid of me being dumb with android mod and a friend of mine told me to "boot" the recovery without flashing it before, but now i used the huawei multi tool and prorerly flashed your recovery and my phone i working fine, now i need your help one last time, please tellme how can i root my device now that i have the twrp recovery installed. thanks
Click to expand...
Click to collapse
Download Magisk v17.1 & Magisk Manager v5.9.1.:
https://github.com/topjohnwu/Magisk/releases?after=manager-v6.1.0
Transfer downloaded Magisk 17.1.zip file to SD card.
Boot your device into TWRP recovery.
Tap on Install button and select Storage - Micro SDCard. Select Magisk 17.1.zip file. Swipe to confirm the flash.
Once Magisk is flashed, reboot the device.
Once device boots up, install Magisk Manager.
Done.
Tilt6x said:
sorry but i was afraid of me being dumb with android mod and a friend of mine told me to "boot" the recovery without flashing it before, but now i used the huawei multi tool and prorerly flashed your recovery and my phone i working fine, now i need your help one last time, please tellme how can i root my device now that i have the twrp recovery installed. thanks
Click to expand...
Click to collapse
You can install the latest Magisk without problems. I am running open kirin's latest LOS 16 and I prefer it to Huawei's stock EMUI 8
Attempted to update from the latest stable 10.3.12 to 11 by flashing the full OTA zip in TWRP.
Install failed and phone locked up.
Attempting to boot to recovery or system results in Qualcomm Crashdump Mode.
I can get to Fastboot, but I'm not sure if I should try flashing twrp.img or pull boot.img from the OTA or what.
Anyone have any suggestions?
SMcC2 said:
Attempted to update from the latest stable 10.3.12 to 11 by flashing the full OTA zip in TWRP.
Install failed and phone locked up.
Attempting to boot to recovery or system results in Qualcomm Crashdump Mode.
I can get to Fastboot, but I'm not sure if I should try flashing twrp.img or pull boot.img from the OTA or what.
Anyone have any suggestions?
Click to expand...
Click to collapse
An attempt to flash TWRP and reflashing should go.
Hi,
I'm having kinda same issue.
I'm on stable A11 oneplus 6t,
i'm trying to boot into twrp in order to install new recovery and root with magisk.
when fasboot boot twrp.img i'm getting a qualcomm crashdump.
tried different twrp img's with no success..
maybe someone figure it out?
thanks
BenoMosko said:
Hi,
I'm having kinda same issue.
I'm on stable A11 oneplus 6t,
i'm trying to boot into twrp in order to install new recovery and root with magisk.
when fasboot boot twrp.img i'm getting a qualcomm crashdump.
tried different twrp img's with no success..
maybe someone figure it out?
thanks
Click to expand...
Click to collapse
I did not have time to wait so before bed I just reset everything.
I ended up using the MSM tool located here:
The Complete Guide to Unbrick OnePlus 6/6T from a Hard-Brick using MSMDownload Tool
Unlocked bootloader, installed TWRP & Magisk, installed A11 zip, everything is working again now.
Good luck!
BenoMosko said:
Hi,
I'm having kinda same issue.
I'm on stable A11 oneplus 6t,
i'm trying to boot into twrp in order to install new recovery and root with magisk.
when fasboot boot twrp.img i'm getting a qualcomm crashdump.
tried different twrp img's with no success..
maybe someone figure it out?
thanks
Click to expand...
Click to collapse
Hey, I'm having the same issue. Did you end up figuring out how to solve this?
Artificial_Intelligence said:
Hey, I'm having the same issue. Did you end up figuring out how to solve this?
Click to expand...
Click to collapse
Flash temporary recovery first ( lineage recovery ) then from fastboot.. boot into recovery.
You will see lineage recovery.
Select apply update - > update from adb ....
Then "adb sideload <twrp image>.img...
(probably it ask to verify choose yes)
Go back select advanced restart ( not sure the right word ) -> reboot to recovery.
Then you will have twrp installed.
If you only want to root why not flash magiskpatched image there no need TWRP just to root.
s.seila said:
Flash temporary recovery first ( lineage recovery ) then from fastboot.. boot into recovery.
You will see lineage recovery.
Select apply update - > update from adb ....
Then "adb sideload <twrp image>.img...
(probably it ask to verify choose yes)
Go back select advanced restart ( not sure the right word ) -> reboot to recovery.
Then you will have twrp installed.
If you only want to root why not flash magiskpatched image there no need TWRP just to root.
Click to expand...
Click to collapse
Hm but how would I install lineage recovery? Flashing recovery through fastboot doesn't work on the new devices anymore right?
I also tried booting lineage recovery without flashing but that also didn't work (although it didn't get stuck on crashdump but booted into the regular OS instead).
I did notice that it seems to be related to OOS 11 firmware. On 10 booting into TWRP works just fine and as soon as I upgrade to 11 it stops working (maybe this means it's fixable?). What I used as a workaround for now is to have 10 firmware in one slot, upgrade other slot to 11 and flash TWRP to both slots from the 10 slot. Seems to work so far but is not ideal IMO. I'm not a developer sadly but maybe someone smarter than me will come up with a solution.
What do you mean by "new device"?? New OOS version right??
I use this method all the time with oos 11.x.x.x.x to install TWRP so i can install Custom ROM later.
no need to go to oos 10 you can flash it from newest oos11.
---------------------------------------------------------------------------------------------------------------
First boot into fastboot mode.
to install lineage recovery
fastboot flash boot <lineage recovery image>.img
download from here https://download.lineageos.org/fajita
menualy select and boot to recovery. It will boot to lineage recovery.
lmao it appear in two posts. deleted 1.