Is there any way to downgrade from Android 12 to 11 and still keep root? If I flash the downgrade zip, can I still patch the boot img with Magisk before rebooting?
[GUIDE] How to Root OnePlus 7T without TWRP
- Thread starter mauronofrio
- Start date
I tryed to root my phone with this instructions here, but after reboot I have no root. I tried the here offered images and also my own image which was build with magisk.
Does somebody know what my problem can be?
Does somebody know what my problem can be?
Hi all,
Wondering if the upgrade guide of the OP still works on the 7T for moving from Android 11 to 12 as it did serve me well since day one (Was it Android 10?)
I am currently running 11.0.9.1.HD65BA and want ro switch to HD1903_11_F.17
I'm running the latest public magisk build (25.2)
Many thanks!
Edit: It works fine.
Wondering if the upgrade guide of the OP still works on the 7T for moving from Android 11 to 12 as it did serve me well since day one (Was it Android 10?)
I am currently running 11.0.9.1.HD65BA and want ro switch to HD1903_11_F.17
I'm running the latest public magisk build (25.2)
Many thanks!
Edit: It works fine.
Last edited:
Hello and sorry for my poor english,
is somebody has same problem on op7T : i root my phone since long time patching boot.img with magisk.
i try to do it with last version 12 i receive via ota, but my phone does not boot when i flash it with fastboot (I stay on 1 icon).
I tried with boot found on this tread... it boot on boot animation, but reboot imediately.
I dont understand why i receive via ota HD1901_11.F.20_3200_202301310046. My phone is in global mode and that one seems to be india.
is somebody has same problem on op7T : i root my phone since long time patching boot.img with magisk.
i try to do it with last version 12 i receive via ota, but my phone does not boot when i flash it with fastboot (I stay on 1 icon).
I tried with boot found on this tread... it boot on boot animation, but reboot imediately.
I dont understand why i receive via ota HD1901_11.F.20_3200_202301310046. My phone is in global mode and that one seems to be india.
Last edited:
You could always download the full ROM from this thread, extract the boot.img and patch it yourself with Magisk.
You could download the stock ROM from this thread, extract the stock boot.img and flash it in fastboot mode to try and get your system running again. You could try the Global version and the India version.
Then you can patch it yourself with Magisk and flash it again.
Do you have HD1907 maybe? This has happened to me also when upgrading converted HD1907 to OOS 12 through OTA.
Hello thanks for answer.
I have HD1900 (OP7T).
My phone is running since i flash it again with ota rom i receive using adb sideload.
My problem is when i patch boot.img from my image. if i try to install it, the phone reboot always in bootloader mode
I do it again with boot.img extract from rom i download , and it's works fine
THANKS A LOT
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
62So today with some testers i managed to make root on OnePlus 7T, I want to specify that 95% of the work was done by @topjohnwu (Magisk creator). For now you should use only Magisk Canary files
I will explain 2 different guides:
First Root Guide:
Second Root Guide:
Third Root Guide:
Guide by @gpz1100
TIPS:
Actually you should use onlyMagisk canary filesMagisk 20.3
You can get the stock boot images from the fastboot rom: https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
Actually i'm using magisk manager canary and magisk canary debug to patch the boot.img, I don't recommend updating magisk, if you don't want to see the updates install the normal magisk manager
Magisk 20.3 fully support OnePlus 7T and 7T Pro
HOW TO UPDATE a ROM and KEEP ROOT:
Download:
Patched/Stock Boot Images: https://www.androidfilehost.com/?w=files&flid=300177
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Donations:
Credits:
@RohanAJoshi47Thinking out loud here for a universal general method.
Goal: To get root/magisk installed
Requirements: Stock device with unlocked bootloader only (no other mods), most recent ota update applied and system rebooted. Fastboot and adb windows executables.
1) Enable advanced reboot and usb debugging in developer options
2) Reboot to bootloader
3) Boot to twrp (obtain image from https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961 ) fastboot boot twrp.img (or whatever you named it).
4) Once booted, enter adb
adb shell
5) type
dd if=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img
exit
5.5) Copy file to the pc
adb pull /tmp/boot.img stock_boot.img
6) Reboot phone back to android
6.5) Copy boot.img back to phone
adb push stock_boot.img /sdcard/boot.img
7) Make sure wifi or lte is connected
8) Install Magisk Manager apk (from OP)
9) Open Magisk Manager and select advanced options. Enable both of these:
Preserve force encryption
Preserve avb 2.0/dm-verity
Tap 3 horizontal lines top left and select settings, choose channel Canary.
Then select option to install Magisk (not manager). Choose the option that say from file.
10) Point to the boot.img on the internal storage (/sdcard).
11) It will do its thing then come back with a done message. File /sdcard/download/magisk_patched.img will be created.
12) You need to copy this file to your pc, either use mtp or adb
adb pull /sdcard/download/magisk_patched.img
13) Reboot the phone into bootloader mode using the power button.
14) Flash the file from #12 - fastboot flash boot magisk_patched.img
15) Done!
These steps might seem much, but really this process is fairly simple and straight forward. The main benefit is you're patching the exact kernel/boot.img that's from your device. No version or region issues to be concerned about. Given all the boot.img files between the different threads on here, I think this is safer.
This also eliminates the need to boot into an older kernel that may have issues with the current build (experienced this myself, only had lte, no wifi).
Thoughts?
Update 12-23-2019: Updated step 9 to include setting advanced options before patching, channel selection.
Update 1-1-2020: Cleaned up paths as /sdcard from twrp is only a virtual path, not present once booted in android. Clarified commands in steps 4-6.5.
If you want to test the image before actually flashing, use:
fastboot boot magisk_patched.img
Once phone is booted, open magisk manager and check to successful installation status. If all is good, reboot back into bootloader and follow step 1416Hey there.. Can you somehow share your educated guess about a fully functioning twrp for thud device? I read about the android 10 changes on the twrp page and so I'm aware of the issues. Coz I really miss full system access in case something goes wrong with a module etc..
Totally not asking for an Eta, just wanted to read your thoughts
The TWRP can't be compiled under android 10, there are a bit of problems, let's explain some of them:
1. The twrp used the -eng build to include a lot of modules needed for a working twrp, in android 10 -eng builds can't be used anymore, so the code should be re-written;
2. .arm modules can't be used anymore in android 10 so they should be re-write in .cpp;
3. android 10 introduced /super partition (it existed also on Pie but it was never used), so a new method to manage system, vendor and product partitions (maybe also odm? i don't remember now), these 3 partitions are included dynamically in this big partition and TWRP actually is not able do manage it (It's not really easy, there is a metadata, the partitions can only mounted in read only mode, to flash a new partition you should write in the metadata also the size of the new partition and a lot of newer things). Obviously on a/b devices there is only 1 /super partition that contains system, vendor and product partitions 2 times (because of 2 slots). Teorically this is a minor problem, to flash rom is need only of a new update_engine_sideload (but this is the next point);
4. update_engine_sideload should be updated to support /super partition (Easy thing, i already did it, also if i didn't tested it)
5. Decrytpion changed again in Android 10, there are a bit of things to do to make it working again
Actually the main problem is the point 1, without that is stupid to work on others things. when the twrp will be bootable (compiled under android 10) maybe all others devs (me included) can start work to the others points and maybe some new problems will come.12
Just read through the pages...This was posted on page 9 by @Hanuta1. I have adapted it a little as not all of it is required anymore.
1. Download the OxygenOS 10.0.4 zip for your region and device from OnePlus
2. Extract the boot.img with payload_dumper
3. After extracting the boot image copy the boot image to your device.
4. Install Magisk Manager
5. Open Magisk Manager and go to the Advanced Settings and set Preserve AVB 2.0/dm-verity.
6. Press install for magisk and take option two where you can select an image file.
7. Select the image file which you copied to your device and patch it. After patching you can find the file in your downloads folder (maybe you need to replug your device into your computer)
8. Copy the patched file on your computer.
9. Boot into fastboot mode and then flash the patched image to your device with "fastboot flash boot imagename_patched.img"
10. If all is successfull then type into the command window "fastboot reboot" and your device should then reboot into a rooted oxygen OS.10
done, 38,21 MB. Try to boot from it.
edit: done it works
Patched boot.img, European, from OnePlus7TOxygen_14.E.06_OTA_006_all_1910122142_a6ac3d238.zip
https://drive.google.com/open?id=1JnIBeRQ-9s-JfIwcgKNwO_zBodj4gcGw
MD5: f7ba21d9107c52096cad47c2cfd4882b
SHA-1: a662582f8c34f2f59158a7f677de957055a670b7
New posts
-
OneUI 5.1 for Exynos Galaxy S10 series
- Latest: OffsetPikachu55
-
-
-
