Related
I have created video guide regarding rooting and TWRP installation on one plus 6 which helps ,specially for noobs.
As this menthod is simple one no A, B partations nothing just simple flash and root and you get permanent recovery which takes backup (except data partition) for safety and become future flashholic person ?
Video guide:
https://youtu.be/SnI_uuNL5sk
REQUIREMENT:
LATEST FIRMWARE OXYGEN OS 5.1.5
(UDATE:IF YOU UPDATED TO OOS 5.1.6 THEN FOLLOW THIS GUIDE AFTER UNLOCKING BOOTLOADER LINKS GIVEN IN VIDEO DESCRIPTION. THIS IS OFFICIAL TWRP AND EASIET ROOTING METHOD
https://youtu.be/frXzBnPsoOs)
DOWNLOAD:
TWRP AND ROOT FILE:
https://googleweblight.com/i?u=http...lbeta-twrp-oneplus-6-t3798439&hl=en-IN&tg=524
Download two files from above thread from two links at top in that thread don't download anything else.
ONE PLUS ADB DRIVERS:
https://drive.google.com/file/d/1ntEb7biGJxenlhJun--i4czQIdNJh8fp/view
After unlocking bootloader phone reboots and it boots in to OOS there you have to again go to
Settings-About phone- build number tap eight times- go back to settings menu- tap developer option enable USB debugging and enable advance reboot
And then long press power button and select bootloader mode again and continue for TWRP flashing and Rooting
[I have not shown this repeated process in video]
Follow procedure exactly as shown in video
1)This rooting process passes safety net check so you can use banking(security) apps on rooted device
2)You can nandroid backup your Rom Except app data
3) It's permenant recovery
We can discuss all things regarding rooting here also
Worst Guide I've ever seen
Why open this thread? There was already another one on rooting and 2 on twrp
Hitman478[emoji769 said:
;76724880]Why open this thread? There was already another one on rooting and 2 on twrp
Click to expand...
Click to collapse
Agreed, the other rooting threads are good enough and it's not exactly difficult.
E.g. root without twrp
1. Download modified boot image
2. Fastboot boot boot.img
3. Install Magisk using using Magisk manager
4. Reboot
Enjoy root
I don't get how people keep managing to break their phones
Sent from my ONEPLUS A6003 using Tapatalk
---------- Post added at 12:59 PM ---------- Previous post was at 12:57 PM ----------
I think the majority is with twrp and people probably swiping to allow system modifications which will cause inability to boot on stock kernel due to dm-verity
Sent from my ONEPLUS A6003 using Tapatalk
This is by far the easiest method. Why use the slot A&B method when that can be very confusing. I know he posted this in one of the other threads but I think it was lost in amongst the threads.
Sent from my ONEPLUS A6003 using Tapatalk
Dude .. I hope to create a video on how to flash stock global ROM through TWRP.
Thanks.
Alex240188 said:
Agreed, the other rooting threads are good enough and it's not exactly difficult.
E.g. root without twrp
1. Download modified boot image
2. Fastboot boot boot.img
3. Install Magisk using using Magisk manager
4. Reboot
Enjoy root
I don't get how people keep managing to break their phones
Sent from my ONEPLUS A6003 using Tapatalk
---------- Post added at 12:59 PM ---------- Previous post was at 12:57 PM ----------
I think the majority is with twrp and people probably swiping to allow system modifications which will cause inability to boot on stock kernel due to dm-verity
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
I used that TWRP from that video and for me at least, It allowed modifications and I could boot back into the ROM no problem.
Sent from my ONEPLUS A6003 using Tapatalk
in stock works? new
emuwar said:
in stock works? new
Click to expand...
Click to collapse
Yes
Sent from my ONEPLUS A6003 using Tapatalk
Will this leave TWRP as permanent recovery and with permanent root? or is it just temporary? Thanks
hallo dare said:
Will this leave TWRP as permanent recovery and with permanent root? or is it just temporary? Thanks
Click to expand...
Click to collapse
I was only on stock rom for a few minutes until I flashed xXX rom. Twrp and root has stuck around a few reboots so I think it is permanent.
Sent from my BTV-W09 using Tapatalk
tdamocles said:
I was only on stock rom for a few minutes until I flashed xXX rom. Twrp and root has stuck around a few reboots so I think it is permanent.
Sent from my BTV-W09 using Tapatalk
Click to expand...
Click to collapse
Its permanent tested
Now the official TWRP is available and you can use this guide to Root Oneplus 6 easily
I wish I could just find a guide how to install oneof those nice ROM's. Looks like this just not to install ROM in TWRP as used to be.
Thank you so much for this guide
Vatumb said:
Now the official TWRP is available and you can use this guide to Root Oneplus 6 easily
Click to expand...
Click to collapse
Can you please tell me if this is still valid for the 9.0.2 (current) build? Everything seems a bit dated right now.
Thanks
Mine is the AL-10. I flashed the Oreo update a while back and it was working just fine. Yesterday I received a 1MB security patch through OTA which simply bricked my phone. I was on my way home from college, the update popped up and as it said only 1MB, I proceeded with it and my phone didn't boot up after that. Tried every basic fix including factory reset but it's still not booting up!
Note: The changelog in the patch said it fixed in-game sound issue.
I was finally able to fix it by flashing system,cust,recovery manually. Dunno why Huawei pulled this stunt on me! Lost all my data
I identified the issue: It's Magisk.
The patched boot image causes the device to get stuck at boot.
Yup. You're suppose to flash the stock boot and recovery for an OTA (unless you have the erecovery flashed as TWRP like I do). I too did the same thing once, learned my lesson lol.
agraceful said:
Yup. You're suppose to flash the stock boot and recovery for an OTA (unless you have the erecovery flashed as TWRP like I do). I too did the same thing once, learned my lesson lol.
Click to expand...
Click to collapse
Tnx, I learned it the hard way too. But the thing is, Magisk isn't working anymore after the update.
I received it too .and my phone is working well
---------- Post added at 06:50 AM ---------- Previous post was at 06:46 AM ----------
SirDarknight said:
Tnx, I learned it the hard way too. But the thing is, Magisk isn't working anymore after the update.
Click to expand...
Click to collapse
flash it By Adb
How did you flash Magisk? Which TWRP did you use? Could you tell me? I'm lost without V4A on my phone LOL
Edit: Update!
See My Guide: [Guide] Pixel 3 XL Android 9.0.0 (Pie) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + September 2018 Security Patch
Doubtful being that the article's date is from May...
jrac86 said:
Doubtful being that the article's date is from May...
Click to expand...
Click to collapse
Edit: OP updated!
Fake News...
It's a feature of Magisk. You install Magisk manager and it will save a patched version of your boot.img that you can pull and flash in fastboot mode.
Sent from my Pixel 2 XL using Tapatalk
bxlegend said:
It's a feature of Magisk. You install Magisk manager and it will save a patched version of your boot.img that you can pull and flash in fastboot mode.
Click to expand...
Click to collapse
Some think the link is "clickbait."
I thought if you installed MM only, you could patch a boot.img with MM. Are you saying that when you install MM it does it without intervention?
Last time I did it you had to get a boot image, transfer it to the device, MM can then patch it, you transfer it back to a PC, flash in fastboot.
Pretty sure we need to wait for a few things, twrp for the Pixel 3, and Google to release the images.
the phone is starting to get to hands on people
it's not like samsung where we can make twrp and root without the device
we need to get images and do testing too
kachaffeous said:
Pretty sure we need to wait for a few things, twrp for the Pixel 3, and Google to release the images.
Click to expand...
Click to collapse
Edit: OP updated
TheUndertaker21 said:
the phone is starting to get to hands on people
it's not like samsung where we can make twrp and root without the device
we need to get images and do testing too
Click to expand...
Click to collapse
Edit: OP updated.
I'm curious what the new Titan security chip will do for rooting and custom rooms. Sounds like something that if done right it can be flashed, but it could present a roadblock depending on how it was implemented.
Images are up.
Sent from my taimen using XDA Labs
---------- Post added at 08:01 PM ---------- Previous post was at 07:12 PM ----------
Current boot patch doesn't work. John will have his phone today.
https://twitter.com/topjohnwu/status/1052993970303889418
Sent from my taimen using XDA Labs
I found this out the hard way
Thought I bricked my phone; black screen. Finally after holding down the power button for a second it said boot incompatible or something in the bootloader. There was a new message I hadn't seen before on a Pixel bootloader. (It also says "button combo" in that message area if you use the buttons to get to bootloader.)
Current boot patch doesn't work.
Click to expand...
Click to collapse
No luck here. I patched the boot img with magisk and it fails to boot. @topjohnwu Please save us. I'll test if needed. I flashed back to stock boot and am good to go.
Factory images are up
Thanks for giving it a try,,,was hoping it would work but I doubted it. Hopefully Magisk can be updated for root! If not, this is going back,,,not enough of a worthy upgrade esp if root is not possible.
northmendo said:
No luck here. I patched the boot img with magisk and it fails to boot. @topjohnwu Please save us. I'll test if needed. I flashed back to stock boot and am good to go.
Click to expand...
Click to collapse
I think I can still cancel my order but I''m hopeful it wont come to that.
Archangel said:
Thanks for giving it a try,,,was hoping it would work but I doubted it. Hopefully Magisk can be updated for root! If not, this is going back,,,not enough of a worthy upgrade esp if root is not possible.
Click to expand...
Click to collapse
Root will come. Give it time
Same tried patching boot.img, fails to boot. Reflashing stock boot.img fixes it. Never really looked at the sizes before, but the patched_boot.img is roughly half the size of the stock boot.img
I am running 10.05, I can't decide whether to install twrp, dd root, or magdisk. Given that I have the most current version of oxygen os, what would be the best way to root my phone?
Don't misinterpret my ignorance for lazyness, a majority of guides I've seen aren't recent and don't go over pros & cons of the method.
Thank you, I'm willing to donate for help.
Edit: I'm stupid, I was in wrong forum. Please ignore this post and what I've said!
You only need a patched image if you don't want to install TWRP. If you install TWRP, I'd simply ADB sideload Magisk to get root.
That's what I've done and it works just fine.
This assumes that you're using a OnePlus 7 Pro, and not a 7T Pro. Not got a 7T, so can't comment on that.
Sent from my GM1913 using Tapatalk
Bagpuss said:
You only need a patched image if you don't want to install TWRP. If you install TWRP, I'd simply ADB sideload Magisk to get root.
That's what I've done and it works just fine.
This assumes that you're using a OnePlus 7 Pro, and not a 7T Pro. Not got a 7T, so can't comment on that.
Click to expand...
Click to collapse
Edit: I'm stupid, I was in wrong forum. Please ignore this post and what I've said!
Lossyx said:
TWRP doesn't work on devices launched with Android 10, which has been discussed many times.
My reply above stands true, a patched boot image is the only way as for right now.
(And we're on a 7T Pro forum)
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Are you positive? I see TWRP install guides everywhere. From what I've read TWRP with magdisk (not SuperSU, us it's not open source) is the best way to root with the most flexibility. What if I'm running 10.03.0GM21AA, and there is no patched image? Do I need to roll back?
Lossyx said:
There is only one way to root, and that is by using a patched image. Check the guides section, there's probably a patched image of your device, if not, you'll have to make your own.
And what's your version? AA or BA?
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
AA. So do I need to roll back? I bought the OP7P because I stupidly assumed it would be as easy/flexible to root as my past OP devices. It's ironic I switched from a Samsung devices to a OP for the ability for a stress-free rooting experience and I got the same problem lol. I might just return the phone for another, I'd prefer something with an SD card slot anyway.
What's the best phone with SD card feature that can run TWRP magdisk without issues like using banking apps and Netflix?
Forgive my ignorance, I am still in the learning process.
Lossyx said:
TWRP doesn't work on devices launched with Android 10, which has been discussed many times.
My reply above stands true, a patched boot image is the only way as for right now.
(And we're on a 7T Pro forum)
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
No we're on a 7 Pro forum. And TWRP works fine on the 7 Pro, but you need a patched version of some sort last time I checked.
sixisixsix said:
I am running 10.05, I can't decide whether to install twrp, dd root, or magdisk. Given that I have the most current version of oxygen os, what would be the best way to root my phone?
Don't misinterpret my ignorance for lazyness, a majority of guides I've seen aren't recent and don't go over pros & cons of the method.
Thank you, I'm willing to donate for help.
Click to expand...
Click to collapse
To root my phone, I didn't even use TWRP. I downloaded the lastest OOS version from OnePlus, extracted the boot image, copied that to my phone, Magisk patched that boot image file (you don't need root for that, you can use the Magisk manager). Then unlocked the phone, and installed the bootloader I just patched while the phone was in bootloader mode (fastboot flash boot boot.img or whatever).
Might not be the easiest, but I think it's clean, however back then I did not know about the option to properly use TWRP. Maybe I can find it, but I know it's possible to just unlock the 7 Pro, and then from the bootloader boot to TWRP once without flashing it, and install Magisk.
QUBiCA said:
No we're on a 7 Pro forum. And TWRP works fine on the 7 Pro, but you need a patched version of some sort last time I checked.
Click to expand...
Click to collapse
Oh damn, I'm actually stupid... How did I miss were on 7 Pro?!
@sixisixsix please ignore everything I've said! I will edit my posts.
Sorry once again
Sent from my OnePlus7TPro using XDA Labs
sixisixsix said:
AA. So do I need to roll back? I bought the OP7P because I stupidly assumed it would be as easy/flexible to root as my past OP devices. It's ironic I switched from a Samsung devices to a OP for the ability for a stress-free rooting experience and I got the same problem lol. I might just return the phone for another, I'd prefer something with an SD card slot anyway.
Click to expand...
Click to collapse
I've found OP devices (having owned two now) to be easy to root, and very friendly to the mod/root community such as XDA. Samsung is the opposite, in my experience (although each Sammy device is different, some better than others in this regard).
The main complexity with the 7 Pro is not that it is an OP device per se; but that it has something called A/B partitions, which are used for "seamless" OTA updates (Pixel devices use this scheme also - as well as a number of other phones).
The thing with A/B partition devices, is that they do NOT have a discrete recovery partition that you can just flash TWRP to. Therefore, you need to patch the boot.img partition (which on A/B devices contains both kernel and recovery, along with ramdisk). It is a little trickier, and somewhat more of a learning curve. But once you've learned that basic difference, it is not too bad.
It seems that the list A/B partitions devices is growing. So while I'm not an expert in the industry or anything, it appears that this is where Android is going (A/B is certainly not going away anytime soon, in any case).
So while the SD card feature is a legitimate difference (and a discriminator for some), I would say you should not make the A/B partition difference scare you away from OP devices. Maybe "too much information", but you can read more about the A/B partition scheme here: https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
---------- Post added at 10:13 AM ---------- Previous post was at 10:05 AM ----------
QUBiCA said:
To root my phone, I didn't even use TWRP. I downloaded the lastest OOS version from OnePlus, extracted the boot image, copied that to my phone, Magisk patched that boot image file (you don't need root for that, you can use the Magisk manager). Then unlocked the phone, and installed the bootloader I just patched while the phone was in bootloader mode (fastboot flash boot boot.img or whatever).
Might not be the easiest, but I think it's clean, however back then I did not know about the option to properly use TWRP. Maybe I can find it, but I know it's possible to just unlock the 7 Pro, and then from the bootloader boot to TWRP once without flashing it, and install Magisk.
Click to expand...
Click to collapse
Certainly a valid approach (fastboot flash a patched boot image). The "other" (TWRP) method works as well, and probably a little easier for most folks:
1) Unlock bootloader
2) fastboot boot twrp.img
Note that this is just remote booting a TWRP image, not installing it. It simply allows the next steps. You can't flash a TWRP image directly, for the reason I've noted above.
3) Once booted to TWRP, flash TWRP installer zip (OPTIONAL). This patched the boot.img so that TWRP is installed. You only need to do this if you want TWRP installed on the phone.
4) Also in "booted" TWRP, flash the Magisk zip.
The main fundamental difference, is that Magisk is patching the boot.img for you, instead of doing it yourself. Have the files (TWRP.zip and Magisk) on the phone before starting the process, and it is really pretty simple and fast.
The nice thing about the patched boot.img method, is that is worked even when TWRP method did not. This applied to when the phone was first released, and the command "fastboot boot" was broken (therefore not possible to fastboot boot TWRP). This happened again when the device was updated to Android 10. Although the developer got fastboot boot working fairly quickly in both circumstances.
Lossyx said:
Edit: I'm stupid, I was in wrong forum. Please ignore this post and what I've said!
Click to expand...
Click to collapse
redpoint73 said:
I've found OP devices (having owned two now) to be easy to root, and very friendly to the mod/root community such as XDA. Samsung is the opposite, in my experience (although each Sammy device is different, some better than others in this regard).
The main complexity with the 7 Pro is not that it is an OP device per se; but that it has something called A/B partitions, which are used for "seamless" OTA updates (Pixel devices use this scheme also - as well as a number of other phones).
The thing with A/B partition devices, is that they do NOT have a discrete recovery partition that you can just flash TWRP to. Therefore, you need to patch the boot.img partition (which on A/B devices contains both kernel and recovery, along with ramdisk). It is a little trickier, and somewhat more of a learning curve. But once you've learned that basic difference, it is not too bad.
It seems that the list A/B partitions devices is growing. So while I'm not an expert in the industry or anything, it appears that this is where Android is going (A/B is certainly not going away anytime soon, in any case).
So while the SD card feature is a legitimate difference (and a discriminator for some), I would say you should not make the A/B partition difference scare you away from OP devices. Maybe "too much information", but you can read more about the A/B partition scheme here: https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
---------- Post added at 10:13 AM ---------- Previous post was at 10:05 AM ----------
Certainly a valid approach (fastboot flash a patched boot image). The "other" (TWRP) method works as well, and probably a little easier for most folks:
1) Unlock bootloader
2) fastboot boot twrp.img
Note that this is just remote booting a TWRP image, not installing it. It simply allows the next steps. You can't flash a TWRP image directly, for the reason I've noted above.
3) Once booted to TWRP, flash TWRP installer zip (OPTIONAL). This patched the boot.img so that TWRP is installed. You only need to do this if you want TWRP installed on the phone.
4) Also in "booted" TWRP, flash the Magisk zip.
The main fundamental difference, is that Magisk is patching the boot.img for you, instead of doing it yourself. Have the files (TWRP.zip and Magisk) on the phone before starting the process, and it is really pretty simple and fast.
The nice thing about the patched boot.img method, is that is worked even when TWRP method did not. This applied to when the phone was first released, and the command "fastboot boot" was broken (therefore not possible to fastboot boot TWRP). This happened again when the device was updated to Android 10. Although the developer got fastboot boot working fairly quickly in both circumstances.
Click to expand...
Click to collapse
Thank you for taking the time to respond to my post in such detail! Wouldn't installing TWRP give me more flexibility for future updates? If I go the flashed image route won't I need erase my data on my phone every time I update?
sixisixsix said:
Thank you for taking the time to respond to my post in such detail! Wouldn't installing TWRP give me more flexibility for future updates? If I go the flashed image route won't I need erase my data on my phone every time I update?
Click to expand...
Click to collapse
I don't think TWRP would give you more flexibility when it comes to updates, unless you are planning on switching ROMs often, but if this phone is your daily driver I would recommend against that.
If you unlock the phone your data will be wiped, but only once. After that it is completely up to you, if you switch ROMs and pick something that is completely different from stock, it is indeed recommended to wipe data to prevent weird issues. But for a regular system update (if you simply stick with the stock ROM and use Magisk for root, you can still receive normal updates from OnePlus), or an update of the same custom ROM, you do not need to wipe data. I wiped data only once, when I unlocked it, because I had to.
Flashing/installing TWRP generally is not necessary and like @redpoint73 explained, with the "new" A/B system, it is not advised to flash TWRP as it is combined with the boot image (which your phone needs to start up, and is updated after every update, so after every update you will lose TWRP again if I am correct). What @redpoint73 explained is that instead of installing (AKA flashing) TWRP, it is possible to just start it up (boot it) once without installing it. From there you can install Magisk on your stock OnePlus ROM and use the benefits of a rooted system.
QUBiCA said:
Flashing/installing TWRP generally is not necessary and like @redpoint73 explained, with the "new" A/B system, it is not advised to flash TWRP as it is combined with the boot image (which your phone needs to start up, and is updated after every update, so after every update you will lose TWRP again if I am correct).
Click to expand...
Click to collapse
It is correct that you lose the TWRP install when you update (as well as losing root). But it is just a simple matter of flashing the TWRP installer zip after the update (I do this the same time as re-flashing Magisk after OTA update), which takes about 10 seconds to accomplish. I wouldn't personally take that as a reason to "not" flash TWRP. But it is a personal preference whether to install TWRP or not. The reasons to have TWRP installed on the phone are much reduced from previous devices. In the past I would have said that being rooted without a custom recovery is asking for trouble. But now, with A/B partitions, along with the fastboot stock ROMs, the choice becomes much less clear. To the point that installing TWRP is purely optional.
I still personally believe that having TWRP installed gives you more recovery options. But again, it is a personal choice, and certainly not mandatory by any means.
---------- Post added at 09:11 AM ---------- Previous post was at 09:01 AM ----------
sixisixsix said:
Wouldn't installing TWRP give me more flexibility for future updates?
Click to expand...
Click to collapse
Actually, no (as QUBiCA touched on above).
Reason being, OTA updates will still come through on this device (even rooted). And you can still flash (or put OTA files on the phone to flash) using the built-in update engine in the phone's settings menu. Which gives you the option to update to either A/B partition slot. Plus, you can just re-flash TWRP (if desired) and Magisk after the update, straight from the Magisk Manager.
The trick is to make sure you do NOT reboot immediately after an OTA update (when rooted). Then simply open Magisk Manager, flash TWRP as if it were a Magisk module (optional, if you want TWRP installed again). Then install Magisk again through the Magisk Manager as well.. Now you can reboot, and you will be updated with root.
sixisixsix said:
If I go the flashed image route won't I need erase my data on my phone every time I update?
Click to expand...
Click to collapse
No (again, just backing up the answer already provided). There is not a big difference between the two methods. In either case, you are patching the boot.img partition to be rooted (whether you flash a patched boot.img, or you have Magisk patch it for you). And in both cases, you don't need to wipe your data.
redpoint73 said:
It is correct that you lose the TWRP install when you update (as well as losing root). But it is just a simple matter of flashing the TWRP installer zip after the update (I do this the same time as re-flashing Magisk after OTA update), which takes about 10 seconds to accomplish. I wouldn't personally take that as a reason to "not" flash TWRP. But it is a personal preference whether to install TWRP or not. The reasons to have TWRP installed on the phone are much reduced from previous devices. In the past I would have said that being rooted without a custom recovery is asking for trouble. But now, with A/B partitions, along with the fastboot stock ROMs, the choice becomes much less clear. To the point that installing TWRP is purely optional.
I still personally believe that having TWRP installed gives you more recovery options. But again, it is a personal choice, and certainly not mandatory by any means.
---------- Post added at 09:11 AM ---------- Previous post was at 09:01 AM ----------
Actually, no (as QUBiCA touched on above).
Reason being, OTA updates will still come through on this device (even rooted). And you can still flash (or put OTA files on the phone to flash) using the built-in update engine in the phone's settings menu. Which gives you the option to update to either A/B partition slot. Plus, you can just re-flash TWRP (if desired) and Magisk after the update, straight from the Magisk Manager.
The trick is to make sure you do NOT reboot immediately after an OTA update (when rooted). Then simply open Magisk Manager, flash TWRP as if it were a Magisk module (optional, if you want TWRP installed again). Then install Magisk again through the Magisk Manager as well.. Now you can reboot, and you will be updated with root.
No (again, just backing up the answer already provided). There is not a big difference between the two methods. In either case, you are patching the boot.img partition to be rooted (whether you flash a patched boot.img, or you have Magisk patch it for you). And in both cases, you don't need to wipe your data.
Click to expand...
Click to collapse
So if I used the patched version of 10.3.0 and another new version comes out I can just download it through settings and I will remained rooted?
Sent from my Redmi Note 8 Pro using Tapatalk
sixisixsix said:
So if I used the patched version of 10.3.0 and another new version comes out I can just download it through settings and I will remained rooted?
Sent from my Redmi Note 8 Pro using Tapatalk
Click to expand...
Click to collapse
NO.
You need to go through the process and flash Magisk from inside Magisk Manager.
tech_head said:
NO.
You need to go through the process and flash Magisk from inside Magisk Manager.
Click to expand...
Click to collapse
Okay so I downloaded magdisk manager, I flashed the patched version of 10.03, then when I rebooted I hit install update on magdisk and when the phone rebooted it was no longer rooted.
Even the guides for flashing aren't in depth enough for me. Can you help me out real quick?
sixisixsix said:
So if I used the patched version of 10.3.0 and another new version comes out I can just download it through settings and I will remained rooted?
Click to expand...
Click to collapse
You should get the OTA update and be able to download it through settings. BUT, after you install the update, you still need to do as I already said in order to remain rooted:
redpoint73 said:
The trick is to make sure you do NOT reboot immediately after an OTA update (when rooted). Then simply open Magisk Manager, flash TWRP as if it were a Magisk module (optional, if you want TWRP installed again). Then install Magisk again through the Magisk Manager as well.. Now you can reboot, and you will be updated with root.
Click to expand...
Click to collapse
---------- Post added at 09:28 AM ---------- Previous post was at 09:00 AM ----------
sixisixsix said:
Okay so I downloaded magdisk manager, I flashed the patched version of 10.03, then when I rebooted I hit install update on magdisk and when the phone rebooted it was no longer rooted.
Even the guides for flashing aren't in depth enough for me. Can you help me out real quick?
Click to expand...
Click to collapse
You seem to be mixing the two processes: Install update in Magisk is for when you update in the future. You shouldn't have to do this rooting the existing ROM with the patched boot.img method.
For the patched boot.img method, you should just be able to flash the patched boot.img, flash the Magisk apk, and open Magisk, and it should say rooted.
My recommendation is follow this guide: https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
I can't possibly see how it can be any more in depth.
Hello,
did somebody already try to root redmi 9a? This tutorial https://forum.xda-developers.com/redmi-9/how-to/guide-root-access-redmi-9-mediatek-t4149531/page2 would work even on this device?
Thanks in advance for any reply :fingers-crossed:
I hope something will be released soon for this cheap phone
A procedure is in experimentation. U will get to know the result soon. A person with the device approached me for help, i tried to guide him in GitHub. Let's see where it goes.
Sounds good! Anyway i'll try first method posted as soon as xiaomi let me unlock bootloader :good:
Did anyone actually did it or did you try? It didnt work for me. I want to hear your experiences even if you failed.
moutsatsa said:
Did anyone actually did it or did you try? It didnt work for me. I want to hear your experiences even if you failed.
Click to expand...
Click to collapse
Redmi 9A has bootloader issue. It's not accepting modified partitions for boot. Need some kind of signature check disabler. One user executed all possible methods to root according to my guide but nothing. Since i don't have the device, i can't help directly. U all try to patch boot.img using Canary magisk and report back. Don't forget to renable magisk_patched.img to boot.img before flashing. First try to boot directly from modified "boot.img" using fastboot boot boot.img. If u have root report back.
I would suggest enthusiastic android users to not buy xiomi devices in the first place.
I tried get root without success.
I patched original boot.img with Magisk and then flash in fastboot mode, but I get bootloop
I flashed with original boot.img to fix it.
I hope someone more experienced can do it.
leeco85 said:
I tried get root without success.
I patched original boot.img with Magisk and then flash in fastboot mode, but I get bootloop
I flashed with original boot.img to fix it.
I hope someone more experienced can do it.
Click to expand...
Click to collapse
Try booting from fastboot without flashing the image first. i'd give it a go myself, but still waiting for BL unlock countdown to finish.
You no longer need to wait for unlocking bootloader, if you have a used MI account where you unlocked your previous Xiaomi devices before.
As per my experience, I have gotten Redmi Note 4 first & I waited for unlock permission for 4 days. After that, I used the same account to unlock my next devices Note 5 Pro, Note 8 Pro, with the same account in the 1st day of buying those phones without any wait.
It is limited to 1 phone per month, though
---------- Post added at 04:00 AM ---------- Previous post was at 03:56 AM ----------
Ayan Chakraborty said:
Redmi 9A has bootloader issue. It's not accepting modified partitions for boot. Need some kind of signature check disabler. One user executed all possible methods to root according to my guide but nothing. Since i don't have the device, i can't help directly. U all try to patch boot.img using Canary magisk and report back. Don't forget to renable magisk_patched.img to boot.img before flashing. First try to boot directly from modified "boot.img" using fastboot boot boot.img. If u have root report back.
I would suggest enthusiastic android users to not buy xiomi devices in the first place.
Click to expand...
Click to collapse
Why does it matter to rename magisk_patched.img to boot.img?
I have this phone, and tried many solutions without success! Magisk with stable release results in a boot loop.
Magisk canary works in terms of not having bootloop, but rooting is not successful!
It has some issue with the CPU model (as iti is not qualcom) and it is also only 32-bit (dunno why nowadays).
We need a TWRP then flash with a MagiskXXX.zip there! This is the only solution I see now (as a trial). But there is no TRWP nor unofficial TWRP for this model!
Someone should do that first
guaro94 said:
I hope something will be released soon for this cheap phone
Click to expand...
Click to collapse
Yeah definitely in future
---------- Post added at 08:31 AM ---------- Previous post was at 08:29 AM ----------
sauron3256 said:
Try booting from fastboot without flashing the image first. i'd give it a go myself, but still waiting for BL unlock countdown to finish.
Click to expand...
Click to collapse
Yes it's big problem for mi/redmi devices
Tyrigi said:
Hello,
did somebody already try to root redmi 9a? This tutorial https://forum.xda-developers.com/redmi-9/how-to/guide-root-access-redmi-9-mediatek-t4149531/page2 would work even on this device?
Thanks in advance for any reply :fingers-crossed:
Click to expand...
Click to collapse
Did you try it?
The only method to root redmi 9A now is given in the TWRP form of redmi 9A
Use it to get root in your device.