Related
I need help. I was rooted with TWRP on Android Pie. I can't figure out how to flash or boot TWRP on Android 10 stable. Can someone please advise on the procedure to get TWRP and root with Magisk. Thank you!
Android 10 very friendly with root
There is an unofficial twrp for Android Q . Download it and temporarily Mount that image and install root.zip. after completing the installation of magiks . Install offical twrp zip to your phone. Done! Now your phone turns on with root.
As the previous response mentioned, unofficial TWRP version -70 just came out yesterday, fixing the "fastboot boot" command. You can now root Android 10 the same as you (probably) did with Pie: fastboot boot twrp.img, then flash twrp installer, and flash Magisk.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
redpoint73 said:
As the previous response mentioned, unofficial TWRP version -70 just came out yesterday, fixing the "fastboot boot" command. You can now root Android 10 the same as you (probably) did with Pie: fastboot boot twrp.img, then flash twrp installer, and flash Magisk.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Click to expand...
Click to collapse
I was able to boot into TWRP... What is the command to flash the Installer file?
akinkoff85 said:
I was able to boot into TWRP... What is the command to flash the Installer file?
Click to expand...
Click to collapse
?????
After you boot to TWRP, you enter your password to decrypt.
You then select the button that says install and navigate to the TWRP_install.zip file.
You will then select additional zip files, one of those being the Magisk.zip.
If you don't install Magisk after TWRP, you will get a bootloop/softbrick.
TWRP requires Magisk.
tech_head said:
?????
After you boot to TWRP, you enter your password to decrypt.
You then select the button that says install and navigate to the TWRP_install.zip file.
You will then select additional zip files, one of those being the Magisk.zip.
If you don't install Magisk after TWRP, you will get a bootloop/softbrick.
TWRP requires Magisk.
Click to expand...
Click to collapse
I installed twrp only and it booted up fine
All done I figured it out and got Root
Maybe it's changed recently, but Magisk was a requirement.
But if you have TWRP why not root?
redpoint73 said:
As the previous response mentioned, unofficial TWRP version -70 just came out yesterday, fixing the "fastboot boot" command. You can now root Android 10 the same as you (probably) did with Pie: fastboot boot twrp.img, then flash twrp installer, and flash Magisk.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Click to expand...
Click to collapse
Thank you. I was struggling for a few days on Android 10 stable, wondering why I couldn't flash root, but eventually found that fastboot boot command wasnt working on 10. So I waited a few days in hopes there would be a way. So just wanted to thank you for this post. Going to try soon. Appreciate it.
---------- Post added at 03:47 AM ---------- Previous post was at 03:46 AM ----------
tech_head said:
Maybe it's changed recently, but Magisk was a requirement.
But if you have TWRP why not root?
Click to expand...
Click to collapse
Good point.
wiswis said:
I installed twrp only and it booted up fine
Click to expand...
Click to collapse
In seems to vary for folks (exact variables not clear), but in many circumstances, flashing TWRP without Magisk will result in no longer booting to OS.
Flashed another rom with twrp and no magisk and it booted up fine. I formatted my phone before the install, maybe that has to do with it
i had magisk running nicely since i installed debloater module ,,,after that my phone gone to bootloop.......now when i uninstall magisk then it turns on normally but if i install magisk then it bootloops again ...any fix for this ?
is anyone know how to root tecno spark 6 go ?
i need this badly..
if anyone do that previously, i would like to thank him..
Lets hope someone looks into Tecno Spark 6 go Ke5k Im also want to custom rom
First you need to unlock your bootloader. Then..
1. Download your stock rom(Try to get the latest version) & empty vbmeta.img.
2. Install magisk. Patch boot.img(From your stock rom).
3. Now flash emptyvbmeta.img and patchedboot.img in fastboot mode.
I76 said:
First you need to unlock your bootloader. Then..
1. Download your stock rom(Try to get the latest version) & empty vbmeta.img.
2. Install magisk. Patch boot.img(From your stock rom).
3. Now flash emptyvbmeta.img and patchedboot.img in fastboot mode.
Click to expand...
Click to collapse
can you explain more or link a site that goes indepth?
0xphantom said:
is anyone know how to root tecno spark 6 go ?
i need this badly..
if anyone do that previously, i would like to thank him..
Click to expand...
Click to collapse
did you manage to do it? i just got it and need to enable camera2api for gcam
I76 said:
First you need to unlock your bootloader. Then..
1. Download your stock rom(Try to get the latest version) & empty vbmeta.img.
2. Install magisk. Patch boot.img(From your stock rom).
3. Now flash emptyvbmeta.img and patchedboot.img in fastboot mode.
Click to expand...
Click to collapse
I tried this ... didn't work for me... I was hoping to try get Orangefox or twrp custom ROM recovery, but my phone's not listed....both on twrp and orangefox
KE5-H6123ABC-QGo-GL-220822V553
Please can someone help me....been trying for weeks now
@Daniel. said:
I tried this ... didn't work for me... I was hoping to try get Orangefox or twrp custom ROM recovery, but my phone's not listed....both on twrp and orangefox
KE5-H6123ABC-QGo-GL-220822V553
Please can someone help me....been trying for weeks now
Click to expand...
Click to collapse
Am also in need of this.... i tried the first method.... didn't work for me either
Please we need help with this issue, have tried magisk, one click root apps nothing is working, have tried a lot of methods....non as worked so far... please anyone
I have successfully rooted KE5K but it's worthless without Custom recovery,
I locked bootloader again.
So I decided to buy New phone which has available custom recovery.
@Daniel. said:
Please we need help with this issue, have tried magisk, one click root apps nothing is working, have tried a lot of methods....non as worked so far... please anyone
Click to expand...
Click to collapse
Unlock bootloader using fastboot tools
Fastboot OEM unlock
Or
Fastboot flashing unlock
Falsh your device's empty Vbmeta.img
Fastboot flash vbmeta vbmeta.img
Reboot and install magisk latest version
Patch your device'S boot.img in magisk
Go-to bootloader and open fastboot mode, and flash patched magisk boot.img
Fastboot flash boot patched_magisk.img
Done, you rooted your device.
kendra$551 said:
I have successfully rooted KE5K but it's worthless without Custom recovery,
I locked bootloader again.
So I decided to buy New phone which has available custom recovery.
Unlock bootloader using fastboot tools
Fastboot OEM unlock
Or
Fastboot flashing unlock
Falsh your device's empty Vbmeta.img
Fastboot flash vbmeta vbmeta.img
Reboot and install magisk latest version
Patch your device'S boot.img in magisk
Go-to bootloader and open fastboot mode, and flash patched magisk boot.img
Fastboot flash boot patched_magisk.img
Done, you rooted your device.
Click to expand...
Click to collapse
Hey if we flash the vbmeta.img will my phone boot
Hi there,
I´ve got an Update for my BV9900.
My Problem is, I can use this BV9900_EEA_S900AA_V1.0_20200522V12_20200523-0035 Version
only for non rooted StockRom.
If I root my phone first, the Update will reboot TWRP Recovery and not his Flashmode.
If I Start the Update on an unrooted System it works.
But then I have the Problem, that I cannot root it anymore with my boot.img and twrp.img.
Can someone help me?
Kind Regards,
Chris
Please install the magisk manager app on your phone and check what if the ramdisk is "no" or "yes"
Ramdisk is Set "no"
dhchris said:
Ramdisk is Set "no"
View attachment 5267407
Click to expand...
Click to collapse
Here is a detailed guide
Install Magisk in Recovery and Root Android [No Ramdisk]
In this guide, we will show you how to install Magisk in the recovery partition and then root your Android device that doesn't have Ramdisk.
www.droidwin.com
dhchris said:
Hi there,
I´ve got an Update for my BV9900.
My Problem is, I can use this BV9900_EEA_S900AA_V1.0_20200522V12_20200523-0035 Version
only for non rooted StockRom.
If I root my phone first, the Update will reboot TWRP Recovery and not his Flashmode.
If I Start the Update on an unrooted System it works.
But then I have the Problem, that I cannot root it anymore with my boot.img and twrp.img.
Can someone help me?
Kind Regards,
Chris
Click to expand...
Click to collapse
The problem is that your phone doesn't support 'ramdisk'. So to root, you now have to patch recovery.img
This will also disable DM verity
Hope i have understood your question properly. Very sorry if i have misunderstood it.
I tried it with my patched File before but get a bootloop.
I'll try it a seconds time with patching from my rooted System
Tab E said:
The problem is that your phone doesn't support 'ramdisk'. So to root, you now have to patch recovery.img
Magisk will also disable DM verity.
Click to expand...
Click to collapse
dhchris said:
I tried it with my patched File before but get a bootloop.
I'll try it a seconds time with patching from my rooted System
Click to expand...
Click to collapse
Once you solve the bootloop, before patching the img try the command
adb disable-verity
It might be DM verity that is stopping your phone to boot
I´ve got a TWRP Recovery image that I flashed.
Should I patch these or the recovery from stock Image?
The Stock that I have is the actual running version not the version that I want to update (come from OTA)?
adb disable-vertiy doesn´t work:
"verity cannot be disabled/enabled - USER build"
flashing the magisk-patched file generated in new version doesn´t work. bootloop
Do you know about a flashable BV9900_EEA_S900AA_V1.0_20200522V12_20200523-0035 ?
dhchris said:
flashing the magisk-patched file generated in new version doesn´t work. bootloop
Do you know about a flashable BV9900_EEA_S900AA_V1.0_20200522V12_20200523-0035 ?
Click to expand...
Click to collapse
Sorry I didn't see your earlier message. Did you flash the patched TWRP recovery or patched stock recovery?
patched stock from older rom. the newer rom is only on ota.
I´ve no files from this
EDIT:
The ways I tried it:
1. Stock system with installed magisk/TWRP - root works but many functions are buggy
so I tried to flash the new version by OTA. Download fine, but reboot to recovery (not flashing update)
2. Installed OTA (new version) on clean stock first rom.
Update flashing works fine but cannot install root (TWRP/Magisk from patched old recovery version)
Should I try to patch the older twrp(working on stock)?
Or should I disable the option in magisk "perserve force encryption"?
Or can I find any patchable file on running system?
Many questions :-(
When you flashed TWRP did you flash it to both partitions?
fastboot flash recovery_a twrp.img
fastboot flash recovery_b recovery.img
Things i="dhchris, post: 84768453, member: 598070"]
patched stock from older rom. the newer rom is only on ota.
I´ve no files from this
EDIT:
The ways I tried it:
1. Stock system with installed magisk/TWRP - root works but many functions are buggy
so I tried to flash the new version by OTA. Download fine, but reboot to recovery (not flashing update)
2. Installed OTA (new version) on clean stock first rom.
Update flashing works fine but cannot install root (TWRP/Magisk from patched old recovery version)
Should I try to patch the older twrp(working on stock)?
Or should I disable the option in magisk "perserve force encryption"?
Or can I find any patchable file on running system?
Many questions :-(
[/QUOTE]
I think try disabling that option. It sometimes causes bootloops
Tab E said:
When you flashed TWRP did you flash it to both partitions?
fastboot flash recovery_a twrp.img
fastboot flash recovery_b recovery.img
Click to expand...
Click to collapse
No, ok
Must try it a bit later.
Have to go out with the family
Try to flash the patched on a and b.
If doesnt work, will try flashing without encryption.
Okay flash recovery_a / recovery_b doesn´t work. command error.
flashing patched without verification works, but no twrp
dhchris said:
Okay flash recovery_a / recovery_b doesn´t work. command error.
flashing patched without verification works, but no twrp
Click to expand...
Click to collapse
OK. Now that you have root access, try flashing TWRP with the TWRP app. After flashing, Reboot to recovery from the TWRP app
TWRP-App in Rootmode crashes, trwp-app non rootmode showns not my device
Told me, device not rooted
Try https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en
App
had to reflash the stock system. bootloop...
now I tried it again.
Installed Stock, then updated it by OTA.
Installed MagiskManager and patched...
rebooted and flashed patched twrp.img in recovery.
installed the twrp manager... no root
MagiskManager shows me Installed N/A
dhchris said:
had to reflash the stock system. bootloop...
now I tried it again.
Installed Stock, then updated it by OTA.
Installed MagiskManager and patched...
rebooted and flashed patched twrp.img in recovery.
installed the twrp manager... no root
Click to expand...
Click to collapse
Do you have twrp? If yes flash the magisk zip. By installing twrp, you are removing the root access gains by patching the stock recovery.
Backup first, that's a must as always.
If coming from OOS 10 base -
1. Flash OOS 11 OB1/hotfix, after its completion do not reboot
2. Install official/unofficial twrp recovery image to ramdisk from advance menu in TWRP
3. Reboot to recovery
4.a. install magisk(optional) and reboot
4.b. repeat 1 and 2, reboot again then, 4.a.
If already on OOS 11 OB1/hotfix-
1. Flash the attached boot.img from bootloader
2. Reboot to recovery from bootloader itself(booting to system at this point will result in bootloop)
3. Follow the process as mentioned for OOS 10
Thx to Soft_M for boot image
NOTE: Above method is not compatible with OB2
OB2,OB3, closed release users directly flash official latest TWRP zip
NOTE: Installing TWRP on OB3 with any given method will cause safety net to fail
man thanks, that saved me from a bootloop from magisk...
Does this work with the HOTFIX build for OB1?
sw1tchback said:
Does this work with the HOTFIX build for OB1?
Click to expand...
Click to collapse
Yes it does, actually I tested this method on hotfix
Whats your widevine status on OOS11? Mine is l3 on unlocked bootloader.
parthrathore said:
Whats your widevine status on OOS11? Mine is l3 on unlocked bootloader.
Click to expand...
Click to collapse
For unlocked bootloader, l3 always
So you have tested official TWRP 3.5.2-9.0 on OOS Open Beta 2 and it works fine? Interesting
CrysisLTU said:
So you have tested official TWRP 3.5.2-9.0 on OOS Open Beta 2 and it works fine? Interesting
Click to expand...
Click to collapse
I confirm
I flashed oos beta2 and try to boot into twrp image through bootloader.but got to crushdump screen
What do I need to do on Beta 2 to get magisk and twrp installed? Currently none of them installed, magisk patched boot.img causes loop
romanuks said:
What do I need to do on Beta 2 to get magisk and twrp installed? Currently none of them installed, magisk patched boot.img causes loop
Click to expand...
Click to collapse
you can follow these steps:
1. install magisk app
2. boot patched boot img with magisk from another thread https://forum.xda-developers.com/t/...beta-1-for-oneplus-6-6t.4304161/post-85408313 through bootloader
3. patch boot image via magisk(if magisk ask you to allow reboot when you first time open it,don't allow it).
4. reboot your phone.you are good to go.
megaslx said:
you can follow these steps:
1. install magisk app
2. boot patched boot img with magisk from another thread https://forum.xda-developers.com/t/...beta-1-for-oneplus-6-6t.4304161/post-85408313 through bootloader
3. patch boot image via magisk(if magisk ask you to allow reboot when you first time open it,don't allow it).
4. reboot your phone.you are good to go.
Click to expand...
Click to collapse
Patching magisk from bootloader leads me to a bootloop though
megaslx said:
you can follow these steps:
1. install magisk app
2. boot patched boot img with magisk from another thread https://forum.xda-developers.com/t/...beta-1-for-oneplus-6-6t.4304161/post-85408313 through bootloader
3. patch boot image via magisk(if magisk ask you to allow reboot when you first time open it,don't allow it).
4. reboot your phone.you are good to go.
Click to expand...
Click to collapse
flash the above attached image and reboot to recovery directly, then follow the given procedure
voske15 said:
flash the above attached image and reboot to recovery directly, then follow the given procedure
Click to expand...
Click to collapse
so,on ob2 and 3, the pure twrp img will boot into crush dump,but patched boot partition won't?
megaslx said:
so,on ob2 and 3, the pure twrp img will boot into crush dump,but patched boot partition won't?
Click to expand...
Click to collapse
After testing it out, seems that is the case
edit: deleted
I had OB3 than I tried to "fastboot boot" latest TWRP to use PixelExperience. I got the QUALCOM message.
So I did the stupid thing to "fastboot flash boot" the latest TWRP. Now I'm bricked.
I will try to flash this one and see what happens. I was trying @mauronofrio unbrick guide, but it goes only until 10.3.8.
Julianocas said:
I had OB3 than I tried to "fastboot boot" latest TWRP to use PixelExperience. I got the QUALCOM message.
So I did the stupid thing to "fastboot flash boot" the latest TWRP. Now I'm bricked.
I will try to flash this one and see what happens. I was trying @mauronofrio unbrick guide, but it goes only until 10.3.8.
Click to expand...
Click to collapse
It worked. I've manage to get into TWRP and flash the stock O11. Thanks.
any actual guide to get twrp working on B3?
TheUndertaker21 said:
any actual guide to get twrp working on B3?
Click to expand...
Click to collapse
Just use FKM to flash a twrp and magisk. it should freakinglish work.
I got a Pixel 3 that I've been trying to root for a while. I've got the bootloader unlocked (OEM unlocking). I noticed that my Factory image is 9.0.0 (PD1A.180720.031, Sep 2018, Verizon) and I'm not sure if the Verizon is the reason it's not working. That is definitely my current build though. I've tried making the image with both the stable build (Magisk v23.0) and the current canary build.
I was able to boot it again by flashing the main boot.img in Fastboot. I've tried installing it on both boot_a and boot_b together and separate and it still doesn't work. I've been using fastboot flash boot boot.img not twrp
Does anyone have any idea of what I can try or what I'm doing wrong?
stoigeboiii said:
I got a Pixel 3 that I've been trying to root for a while. I've got the bootloader unlocked (OEM unlocking). I noticed that my Factory image is 9.0.0 (PD1A.180720.031, Sep 2018, Verizon) and I'm not sure if the Verizon is the reason it's not working. That is definitely my current build though. I've tried making the image with both the stable build (Magisk v23.0) and the current canary build.
I was able to boot it again by flashing the main boot.img in Fastboot. I've tried installing it on both boot_a and boot_b together and separate and it still doesn't work. I've been using fastboot flash boot boot.img not twrp
Does anyone have any idea of what I can try or what I'm doing wrong?
Click to expand...
Click to collapse
Try patching boot image with magisk 19. Boot it first. If booting okay then flash magisk patched image to boot a & b. Plz let me know if any luck.
stoigeboiii said:
I got a Pixel 3 that I've been trying to root for a while. I've got the bootloader unlocked (OEM unlocking). I noticed that my Factory image is 9.0.0 (PD1A.180720.031, Sep 2018, Verizon) and I'm not sure if the Verizon is the reason it's not working. That is definitely my current build though. I've tried making the image with both the stable build (Magisk v23.0) and the current canary build.
I was able to boot it again by flashing the main boot.img in Fastboot. I've tried installing it on both boot_a and boot_b together and separate and it still doesn't work. I've been using fastboot flash boot boot.img not twrp
Does anyone have any idea of what I can try or what I'm doing wrong?
Click to expand...
Click to collapse
Did you do the "fastboot flashing unlock" step (this will wipe your phone) to unlock your bootloader? OEM unlocking does not unlock the bootloader, it only allows it to be unlocked with fastboot.
Generally speaking, Verizon phones cannot be bootloader unlocked. However a few people have successfully unlocked new phones, fresh out of the box, that have never been connected to Verizon. It appears the bootloader is not permanently locked until the initial connection to Verizon.
dcarvil said:
"fastboot flashing unlock"
Click to expand...
Click to collapse
When i typed that it said already unlocked
Device already unlocked
I don't think I have a verizon Model but I actually have no clue
ashish_jha said:
magisk 19
Click to expand...
Click to collapse
I tried to do this with Version 19.4 but no luck
Any other ideas?
stoigeboiii said:
I tried to do this with Version 19.4 but no luck
Any other ideas?
Click to expand...
Click to collapse
But did u patch it with magisk before booting?
stoigeboiii said:
I tried to do this with Version 19.4 but no luck
Any other ideas?
Click to expand...
Click to collapse
There are several things you can try:
How are you transferring the the images between your phone and PC? MTP can corrupt files, so use adb push/pull or SFTP.
Since you are on Android 9, you should be able to boot TWRP without installing it. Copy magisk.zip to your phone, do "fastboot boot trwp.img", then Install from TWRP. If you use Magisk 23, rename magisk.apk to magisk.zip. If you use 19.4 or 20.4, just download the zip file.
Search the Magisk support forum at https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382 for similar problems and solutions.
If all else fails, give me the md5sum of your patched boot image. I'll patch that image, and compare the md5sums to see if I get the same result.