Database Info

Is Root currently available on Oreo?

EDIT: Yes! follow this guide! https://forum.xda-developers.com/ma...e-9-magisk-t3666540/post75359033#post75359033 (twrp has to be on 3.0.1 and use the strike-through magisk zip if you encounter problems. My HW zip also threw up errors but seems to have worked anyways)
Is Root currently available on Oreo?
I feel like the answer should be obvious but I can't seem to get a straight answer. The keywords just pull up old nougat root methods.
The rollback threads make it sound like the answer is no, you need to rollback to get root back.
If there is a method and you can point me to one, ideally something like magisk to bypass safetynet. Magisk's current zip (15.3) which claims to be generic fails throwing the error ! Unable to detect boot image; I don't know what's magisk's end and what's the mate 9 community's responsibility right now.
I'm sorry if this is right under my nose and I'm not seeing it.

Fire HD 10 and Magisk?

Hey everyone -
I have a Fire HD 10 (2017 model) that is successfully rooted with SuperSU. I am wondering if anyone has figured out how to gain root access with Magisk? All the tutorials I have found regarding the switch from SuperSU to Magisk involve flashing some zips in TWRP, which we can't do. Has anyone figured it out?
Ultimately, I'm trying to get DirecTV Now to work, but it doesn't play nicely with rooted devices. The Hide My Root app used to work, but it has stopped. If we can't get Magisk to work, I'd at least be happy if someone has advice on getting DirecTV Now working again!

I tried flashing Magisk 16.0 with 15.3 installer today and got stuck in bootloop. It flashed but would just boot to amazon logo over and over. Have a Ti Backup but it sucks. I'm sure there's a way through adb. I'm still learning. I wanna know the best way to flash any zip in general cause without FF TWRP or some other custom recovery im lost. I'm assuming you'd have to uninstall SuperSu anyhow. My 2 cents. Rebuilding new ROM now, I love spending hours doing the same thing ?. In hindsight I get better each time and find new hacks tricks etc.

You might be able to use tasker with a variation of the code in this thread https://forum.xda-developers.com/apps/magisk/microsoft-intune-company-portal-t3611588/page12

btonetbone said:
Hey everyone -
I have a Fire HD 10 (2017 model) that is successfully rooted with SuperSU. I am wondering if anyone has figured out how to gain root access with Magisk? All the tutorials I have found regarding the switch from SuperSU to Magisk involve flashing some zips in TWRP, which we can't do. Has anyone figured it out?
Ultimately, I'm trying to get DirecTV Now to work, but it doesn't play nicely with rooted devices. The Hide My Root app used to work, but it has stopped. If we can't get Magisk to work, I'd at least be happy if someone has advice on getting DirecTV Now working again!
Click to expand...
Click to collapse
Hide Rooting V1.7 is working for me. I rooted yesterday then realized Dtv now stopped working and had to scramble to fix it. So far that's the answer.

chris_dubs said:
I tried flashing Magisk 16.0 with 15.3 installer today and got stuck in bootloop. It flashed but would just boot to amazon logo over and over. Have a Ti Backup but it sucks. I'm sure there's a way through adb. I'm still learning. I wanna know the best way to flash any zip in general cause without FF TWRP or some other custom recovery im lost. I'm assuming you'd have to uninstall SuperSu anyhow. My 2 cents. Rebuilding new ROM now, I love spending hours doing the same thing . In hindsight I get better each time and find new hacks tricks etc.
Click to expand...
Click to collapse
Sorry for any revival, but is that really possible? I don't really think so, because Magisk, is by definition Systemless, meaning that it doesn't affect the system in any way, but modifies the boot.img. And modifying the boot.img even a tiny bit results in a bootloop, because it fails signature verification. I would be glad to hear any ideas because when we manage to get our Amazon tablet rooted, I would prefer Magisk over anything as I always did, because it is open source and systemless.

Today I successfully rooted my HD8 2016 with SuperSu permanently. Install Magisk Manager but hesitate to install Magisk as afraid of boot loop. Is there any solution to "flash" audio mods zip files without Magisk or TWRP?

lifegap said:
Today I successfully rooted my HD8 2016 with SuperSu permanently. Install Magisk Manager but hesitate to install Magisk as afraid of boot loop. Is there any solution to "flash" audio mods zip files without Magisk or TWRP?
Click to expand...
Click to collapse
This is an unrelated question.

btonetbone said:
Hey everyone -
I have a Fire HD 10 (2017 model) that is successfully rooted with SuperSU. I am wondering if anyone has figured out how to gain root access with Magisk? All the tutorials I have found regarding the switch from SuperSU to Magisk involve flashing some zips in TWRP, which we can't do. Has anyone figured it out?
Ultimately, I'm trying to get DirecTV Now to work, but it doesn't play nicely with rooted devices. The Hide My Root app used to work, but it has stopped. If we can't get Magisk to work, I'd at least be happy if someone has advice on getting DirecTV Now working again!
Click to expand...
Click to collapse
So far no. But don't worry. The HD 10 can be unlocked, it's just a matter of its done. Unfortunately, we don't have it easy. The HD 10 is built sorta convoluted. It's 64 but in some cases, 32 in the rest. Something's can't pick up on it. I have a thing or two I am working on. Unfortunately I am dead in the water PC wise until after 10 am. I need a new mouse. And I don't have a spare.
If anyone wants to help... mediatek uses their own fastboot executable, mtboot.exe. I still need to gather all the files to build it and or the binary (they aren't in the right places at all). But it would be nice if the mtboot.exe could be located somewhere on the web.
Also in the Amazon source code for the kernel, they left a potential honey pot. Datool, also known as fbtool. They left the module in their source, and I can't figure out why. In the source it lists some usb props, vendor and product IDs and lists three boot modes: unknown, brom, and preloader. It's also tied into sp flash tool somehow. When you compile the datool at the mediatek source, it will put the tablet into preloader mode. So prehaps it can also put it in brom. But if we can get datool to do a proper dump, we might be able to get SP flash tool working.
That's been my findings the past few days.
Now when I get a mouse, hopefully I will have the first test rom built today.

lifegap said:
Today I successfully rooted my HD8 2016 with SuperSu permanently. Install Magisk Manager but hesitate to install Magisk as afraid of boot loop. Is there any solution to "flash" audio mods zip files without Magisk or TWRP?
Click to expand...
Click to collapse
Sorry, this might be a stupid question. I am new to Magisk Manager.
Did you install both SuperSU and Magisk Manger on HD8 2016? Which one is managing the root access of APPs? How does it work?

Dan_firehd said:
Sorry, this might be a stupid question. I am new to Magisk Manager.
Did you install both SuperSU and Magisk Manger on HD8 2016? Which one is managing the root access of APPs? How does it work?
Click to expand...
Click to collapse
The only thing we have available at the moment for flashing is flash fire, on the HD 10. I have magisk on a few devices. It's pretty cool once you get the hang of it. It's different and took me a while to get to the point of liking it. I think it will be amazing on the HD 10 because the hardware is great. I haven't tried it on my fire 7 yet. I don't have a rooted HD 8.
Sent from my MotoG3 using XDA Labs

DragonFire1024 said:
... The HD 10 is built sorta convoluted. It's 64 but in some cases, 32 in the rest. Something's can't pick up on it.
Click to expand...
Click to collapse
No, it's not. Same way many (arguably most) 64-bit devices behave in a 32/64 hybrid world. Someday 'everything' Android will be 64-bit or greater with 32-bit being religated to history - much 8/16-bit is today. Not there yet, especially on economy devices using older hardware. Amazon is not doing anything weird.

Dan_firehd said:
Sorry, this might be a stupid question. I am new to Magisk Manager.
Did you install both SuperSU and Magisk Manger on HD8 2016? Which one is managing the root access of APPs? How does it work?
Click to expand...
Click to collapse
Only SuperSu manage the root access. Magisk manager without Magisk installed is only an app.

Dan_firehd said:
Sorry, this might be a stupid question. I am new to Magisk Manager.
Did you install both SuperSU and Magisk Manger on HD8 2016? Which one is managing the root access of APPs? How does it work?
Click to expand...
Click to collapse
The SuperSu do the root management. Magisk manager is great on my phone, but it creates disaster on my HD 8 when testing the Magisk installing from the Manager. It made my HD8 boot loop at Amazon logo, no way to boot. I have to sideload the stock ROM then rooting again.

DragonFire1024 said:
If anyone wants to help... mediatek uses their own fastboot executable, mtboot.exe. I still need to gather all the files to build it and or the binary (they aren't in the right places at all). But it would be nice if the mtboot.exe could be located somewhere on the web.
Also in the Amazon source code for the kernel, they left a potential honey pot. Datool, also known as fbtool. They left the module in their source, and I can't figure out why. In the source it lists some usb props, vendor and product IDs and lists three boot modes: unknown, brom, and preloader. It's also tied into sp flash tool somehow.
Click to expand...
Click to collapse
Wondering if your still looking into fbtool - I think your right about its potential in fixing bricks/installing roms. Got a link to the mtboot source still?
Brainstorming how to unbrick patched Fire 7's here:
Fire 7 (2019, mustang) unbrick, downgrade, unlock & root
Make sure to read this guide completely before starting. You will lose all data on the tablet, make a backup of important data before you start. What you need: - a Linux installation. Don't use a VM! Use a live USB, if you don't have Linux...
forum.xda-developers.com
Currently thinking about fbtool and a custom lineage compile, with hacked secureboot, fastboot enabled lk.bin and a preloader which skips rpmb. Further info on mtk's fastboot implementation would be useful.

Question What is your current/and or favorite rom for the OP9?

I wanted to see what other users were using on their setups, as I have been using evolution-x on my personal device, but sadly it hasn't been getting updates lately, so what do you all use?

Ethanadams642 said:
I wanted to see what other users were using on their setups, as I have been using evolution-x on my personal device, but sadly it hasn't been getting updates lately, so what do you all use?
Click to expand...
Click to collapse
I'm on stock A12 rooted with magisk 23.0. passing safety net using magisk hide and all my modules. Call screen module and AdAway. Going to flash anything that comes along our way in the future A12. There is a sapphire aospa for the pro already. Reason I'm going to start flashing is I've had the proper version of the msm tool on my desktop since the beginning. I've read horror stories of errors when folks try and msm their device back to stock. Well I tried just patching boot.img to gain root on new A12 build and broke my boot and set-up. All I could reach is fastboot. Plugged in msm tool and in 500+ sec, wallah I'm restored to stock 11.4. I did however find the correct way to root A12 since though . Hopefully lineage will come out with A12 for us first. Enjoy the device I am. Ps live caption is broken.

mattie_49 said:
I'm on stock A12 rooted with magisk 23.0. passing safety net using magisk hide and all my modules. Call screen module and AdAway. Going to flash anything that comes along our way in the future A12. There is a sapphire aospa for the pro already. Reason I'm going to start flashing is I've had the proper version of the msm tool on my desktop since the beginning. I've read horror stories of errors when folks try and msm their device back to stock. Well I tried just patching boot.img to gain root on new A12 build and broke my boot and set-up. All I could reach is fastboot. Plugged in msm tool and in 500+ sec, wallah I'm restored to stock 11.4. I did however find the correct way to root A12 since though . Hopefully lineage will come out with A12 for us first. Enjoy the device I am. Ps live caption is broken.
Click to expand...
Click to collapse
Thinking of going back to stock root, as my Evo build is out of date with no sign of na update or A12, but am also thinking of checking out havoc

Question ROM in op 9 tmobile version

Hello everyone! I just bought an Amazon renewed Op 9, and I wanted to ask How to install Evolution X or Lineage OS, since maybe the instructions are different from the global Version and T Mobile version Add more step to installation or simply can not be achieved

Convert T-Mobile OnePlus 9 to Global (or other) firmware
** USE THIS AT YOUR OWN RISK. ** READ THROUGH THE STEPS BEFORE ATTEMPTING. IF AT ANY POINT WHILE READING THESE STEPS YOU GET CONFUSED, YOU PROBABLY SHOULDN'T ATTEMPT THIS. ** BACKUP YOUR FILES AND APP DATA AS THIS WILL WIPE YOUR PHONE. ** BACKUP...
forum.xda-developers.com
Start here. Since I have a locked SIM, I used the MSM conversion package linked in the OP (https://forum.xda-developers.com/t/...r-other-firmware.4277169/page-3#post-85143501).
This will get you to the stock global ROM. After, you will need to update to the most recent OOS 11 ROM: https://android.googleapis.com/packages/ota-api/package/580d47a7dde5862a306c07ff939cc4fe1520860f.zip
From here, you have a few options depending on whether or not you want to go Android 11 or 12 (since both Evolution X and Lineage OS are offered on both). Android 11 is pretty straightforward. Follow the directions in the thread to upgrade. For 12, you should be able to do the same. HOWEVER, if you become stuck with two SIM cards, neither of which show a SIM installed, you will need 1) an unlock.bin from OnePlus for your device, 2) to root your device using Magisk, 3) to apply the Magisk module found here: https://forum.xda-developers.com/t/tmo-oos-cos-data-fix.4392895/
I'm running a debloated OOS 12 and had to root and apply the fix. Custom/Lineage ROMs may not have this issue, but it's something to be prepared for if you don't want to waste as much time as I did reflashing everything. Please note that this is a very simple step by step tutorial. READ READ READ to ensure you don't brick your device. Most bricks can be recovered with the MSM fortunately.'
Please let me know if you have any questions, and I will try my best to answer. I am by no means an expert, but I feel comfortable messing around with my phone now, enough that I don't have to consult the forums for every little thing.
Good luck, and most of all, have fun!

posar said:
Convert T-Mobile OnePlus 9 to Global (or other) firmware
** USE THIS AT YOUR OWN RISK. ** READ THROUGH THE STEPS BEFORE ATTEMPTING. IF AT ANY POINT WHILE READING THESE STEPS YOU GET CONFUSED, YOU PROBABLY SHOULDN'T ATTEMPT THIS. ** BACKUP YOUR FILES AND APP DATA AS THIS WILL WIPE YOUR PHONE. ** BACKUP...
forum.xda-developers.com
Start here. Since I have a locked SIM, I used the MSM conversion package linked in the OP (https://forum.xda-developers.com/t/...r-other-firmware.4277169/page-3#post-85143501).
This will get you to the stock global ROM. After, you will need to update to the most recent OOS 11 ROM: https://android.googleapis.com/packages/ota-api/package/580d47a7dde5862a306c07ff939cc4fe1520860f.zip
From here, you have a few options depending on whether or not you want to go Android 11 or 12 (since both Evolution X and Lineage OS are offered on both). Android 11 is pretty straightforward. Follow the directions in the thread to upgrade. For 12, you should be able to do the same. HOWEVER, if you become stuck with two SIM cards, neither of which show a SIM installed, you will need 1) an unlock.bin from OnePlus for your device, 2) to root your device using Magisk, 3) to apply the Magisk module found here: https://forum.xda-developers.com/t/tmo-oos-cos-data-fix.4392895/
I'm running a debloated OOS 12 and had to root and apply the fix. Custom/Lineage ROMs may not have this issue, but it's something to be prepared for if you don't want to waste as much time as I did reflashing everything. Please note that this is a very simple step by step tutorial. READ READ READ to ensure you don't brick your device. Most bricks can be recovered with the MSM fortunately.'
Please let me know if you have any questions, and I will try my best to answer. I am by no means an expert, but I feel comfortable messing around with my phone now, enough that I don't have to consult the forums for every little thing.
Good luck, and most of all, have fun!
Click to expand...
Click to collapse
Its neccesary the root for the steps?

Yasser.d said:
Its neccesary the root for the steps?
Click to expand...
Click to collapse
It's necessary to root if you experience the dual SIM issue on a 12 ROM. Otherwise, you can run unrooted just fine.

posar said:
It's necessary to root if you experience the dual SIM issue on a 12 ROM. Otherwise, you can run unrooted just fine.
Click to expand...
Click to collapse
But for backup and stuff like that? the root its needed or not? where i find a tutorial for root for my t mobile version :ccc

Yasser.d said:
But for backup and stuff like that? the root its needed or not? where i find a tutorial for root for my t mobile version :ccc
Click to expand...
Click to collapse
Sorry for the delayed response; I wanted to find a guide that explained the process better than I could. Here are the steps to root:
Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
I was able to extract the boot.img using the win64 build of Payload Dumper. If I'm reading this article correctly, you shouldn't need to worry about patching vendor_boot.img or vbmeta.img unless you are rooting ColorOS (I didn't have to patch either when rooting OOS 12).

posar said:
Sorry for the delayed response; I wanted to find a guide that explained the process better than I could. Here are the steps to root:
Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
I was able to extract the boot.img using the win64 build of Payload Dumper. If I'm reading this article correctly, you shouldn't need to worry about patching vendor_boot.img or vbmeta.img unless you are rooting ColorOS (I didn't have to patch either when rooting OOS 12).
Click to expand...
Click to collapse
Oh thank you very much! I'm new to oneplus and I'm afraid of doing something wrong, in xiaomi's it was a little easier.
I'll try when I have the bootloader unlocked (I'm still waiting for the oneplus email for the unlock token) so I can root and have a backup with the app in the tutorial.
Later I will try to update to oxygenos 12 I think, I liked oxygen os11 and I don't know if it's worth the change to new roms

Yasser.d said:
Oh thank you very much! I'm new to oneplus and I'm afraid of doing something wrong, in xiaomi's it was a little easier.
I'll try when I have the bootloader unlocked (I'm still waiting for the oneplus email for the unlock token) so I can root and have a backup with the app in the tutorial.
Later I will try to update to oxygenos 12 I think, I liked oxygen os11 and I don't know if it's worth the change to new roms
Click to expand...
Click to collapse
I like OOS 12, but some people have had complaints. I haven't noticed any glaring bugs or anything crazy. Battery life has been great, no issues with bluetooth, no crashes or anything.
I'm personally keeping my eye on the Pixel Experience 12 ROM and will probably be flashing to that once the bugs are ironed out.

posar said:
I like OOS 12, but some people have had complaints. I haven't noticed any glaring bugs or anything crazy. Battery life has been great, no issues with bluetooth, no crashes or anything.
I'm personally keeping my eye on the Pixel Experience 12 ROM and will probably be flashing to that once the bugs are ironed out.
Click to expand...
Click to collapse
ohh I understand, but pixel experience 12 is the one that doesn't have security certificates from banks and stuff? I do not remember the app but it was the one that said that it passed the test or it did not pass

after that fix dual sim is working?

Yasser.d said:
ohh I understand, but pixel experience 12 is the one that doesn't have security certificates from banks and stuff? I do not remember the app but it was the one that said that it passed the test or it did not pass
Click to expand...
Click to collapse
I haven't heard this, but I haven't really been keeping track. I guess I'll find out.
gioodo said:
after that fix dual sim is working?
Click to expand...
Click to collapse
To my knowledge dual sim can't work on the T-Mobile OnePlus 9. It doesn't even have a dual sim tray.

Question My phone came with android 13. Am i hosed?

Hello, newbie here. I bought a google pixel 6a earlier today for experimenting with custom roms. After unboxing it found that it shipped with android 13. I saw the anti rollback warning here and i wonder what i should do.
Shoudl i try and return it or can i save it in a way? I havent connected it to the internet at all or anything like that. It's almost exactly as it was shipped. Any advice? Thanks.
Edit:
Okay i am totally new to this and maybe the warning doesn't mean what i think it does. Does it just mean that theres an increased risk of bricking a device or that after android 13 custom Roms wont work?

I forget the exact technical details, but it only means that you can't go back to Android 12 (because hackers rollback to A12 to exploit a vulnerability/bug that they fixed in A13). That being said, Google did release a way to rollback though I don't know much about it (never tried it).
I don't think you need to return the phone. I've never had to rollback to A12. It's already been like 8 months that A13 was released. I'm happy with A13 and the 6a.

Just enjoy your device, mate.
There's an increased risk for bricking your device if you're new to this and don't double check everything you do. Be sure to ask (always Google first tho, haha) if you're not certain about something you're about to do.
Sending your device back and buying a new one is not really a solution imo, likely all devices are going to come with A13 out of the box. FWIW, I was already on A13 when I was able to unlock my bootloader and switch to custom ROMs.

if he wants to root his device he can't enjoy it. because there is no root for 13 yet and you can't roll back to 12 because of a "efuse" that blows when 13 is installed.

Lada333 said:
Just enjoy your device, mate.
There's an increased risk for bricking your device if you're new to this and don't double check everything you do. Be sure to ask (always Google first tho, haha) if you're not certain about something you're about to do.
Sending your device back and buying a new one is not really a solution imo, likely all devices are going to come with A13 out of the box. FWIW, I was already on A13 when I was able to unlock my bootloader and switch to custom ROMs.
Click to expand...
Click to collapse
there is no root for 13 or I would have upgraded. I take that back there is but all the roms have stuff that does not work on them . like revanced or other things.

Alldayismokebomb said:
there is no root for 13 or I would have upgraded. I take that back there is but all the roms have stuff that does not work on them . like revanced or other things.
Click to expand...
Click to collapse
Not sure what you mean by "no root for Android 13"... Yes you can get get root access on Android 13 using Magisk, and yes it has been available since the launch of Android 13.

Alldayismokebomb said:
there is no root for 13 or I would have upgraded. I take that back there is but all the roms have stuff that does not work on them . like revanced or other things.
Click to expand...
Click to collapse
Rooting A13 has been available without any issues for many many months now.
What do you mean by things not working on all A13 ROMs? What things? ReVanced works flawlessly for me, running crDroid A13.

Alldayismokebomb said:
if he wants to root his device he can't enjoy it. because there is no root for 13 yet and you can't roll back to 12 because of a "efuse" that blows when 13 is installed.
Click to expand...
Click to collapse
I rooted my Pixel 6a with A13 a month ago using guide from here. Also tried GrapheneOS for a bit. Had zero issues.

The guide for LineageOS tells you to upgrade to Android 13 before installing it anyway.