Related
I've tried to root using Magisk to SuperSU but I'm into the same issue, The device get stuck on the boot screen until I re-flash the stock boot image, is there any solution for that's?
Not yet. Did this really require a thread of its own ?
skymera said:
Not yet. Did this really require a thread of its own ?
Click to expand...
Click to collapse
I just want to know how much will take so that it will be available.
rsm23 said:
I just want to know how much will take so that it will be available.
Click to expand...
Click to collapse
Nobody here can see in the future...
https://forum.xda-developers.com/showpost.php?p=74161852&postcount=3634
here try this Good Luck !
On my phone SuperSU 2.82 SR5 works fine. On other phones not, or SR3 woks....
Magisk 1.4 or 1.42 beta not working. I did not get boot loops, but not working.
rsm23 said:
I've tried to root using Magisk to SuperSU but I'm into the same issue, The device get stuck on the boot screen until I re-flash the stock boot image, is there any solution for that's?
Click to expand...
Click to collapse
Follow this guide brother
Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))
baskaflyfer said:
Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))
Click to expand...
Click to collapse
How did you achieve this?
baskaflyfer said:
Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))
Click to expand...
Click to collapse
This is a good news. Cannot wait for more details!
baskaflyfer said:
Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))
Click to expand...
Click to collapse
Does this seems ok to you : https://forum.xda-developers.com/oneplus-3t/how-to/magisk-oxygen-os-8-0-op3-3t-t3689901 ?
ashokmor007 said:
Follow this guide brother
Click to expand...
Click to collapse
Thanks, but I don't like SuperSU
---------- Post added at 08:41 AM ---------- Previous post was at 08:39 AM ----------
mr.charlie said:
Does this seems ok to you : https://forum.xda-developers.com/oneplus-3t/how-to/magisk-oxygen-os-8-0-op3-3t-t3689901 ?
Click to expand...
Click to collapse
Thanks, but too much of a hassle for me right now.
I think I'll just wait for an official Magisk update to be released, at this point
baskaflyfer said:
Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))
Click to expand...
Click to collapse
! We are looking forward to your description: how to take the steps? !
papzi57 said:
! We are looking forward to your description: how to take the steps? !
Click to expand...
Click to collapse
Be carefully, you can lose you data!!! For me all work fine)))
1.Flash Oreo via trwp
2.Downgarde bootloader for DM-Verity
3. Flash Magisk via twrp
4. Turn off the phone manualy
5.Turn on & boot in twrp
6.Do the backup of boot
7.And edit boot.win in hex editor on pc
Code:
androidboot.selinux=permissive
screen in attachment
8.And flash boot back, reboot.
P.S When you set selinux permissive via fastboot you'll have freeze (braking) in system - i don't know how it say
baskaflyfer said:
edit boot.win in hex editor
Click to expand...
Click to collapse
This worked for me too, but maybe some other users need more information on the boot partition
Oreo compatible TWRP: Download (Credits: @akhilnarang)
OOS Open Beta 25: Download (Official OnePlus Website)
Magisk 14.3 (Beta): Download (stolen from this thread)
Magisk Manager 5.4.0: Download (GitHub)
You are responsible, if it kills your device, but this was my way:
1. Full Backup in TWRP
2. Reboot into Fastboot Mode
3. Flash Oreo compatible TWRP
4. Use Volume Keys to select and boot into recovery
5. Install OOS Open Beta 25
Then i did a reboot and Steps 1&2 again but i don't think this is required.
6. Install Magisk 14.3 Beta
7. Create an image of the boot partition
Code:
adb shell
dd if=/dev/block/sde18 of=/sdcard/boot.img
exit
8. Copy the boot.img file to your computer
9. Open this file in a hex exitor, add the following text after "buildvariant=user" (image in baskaflyfer's answer) and save the file:
Code:
androidboot.selinux=permissive
10. Reboot into fastboot mode
11. Flash modified boot image
12. Reboot to OOS
13. Install the Magisk Manager APK
Is it safe?
Do you dirty flash open beta 25?
Why need I modifyed the boot. img? Why don't modifyeed it the Magisk for me?
Sent from my Pixel 2XL using XDA-Developers Legacy app
papzi57 said:
Is it safe?
Do you dirty flash open beta 25?
Why need I modifyed the boot. img? Why don't modifyeed it the Magisk for me?
Click to expand...
Click to collapse
I am not able to tell you how safe this method is.
Yes, i did a dirty flash of OOS Open Beta 25, but some apps lost their data (Jodel, photoTAN, ...) but not Google Authenticator :fingers-crossed:
I think the modification of the boot.img is device-specific. I can not tell you details about this because i don't know that either.
There might be another way to set selinux=permissive as recently described in this thread, but your bootloader need to allow the following command:
Code:
fastboot oem selinux permissive
If you are able to perform this command in fastboot mode, maybe you don't need to modify the boot.img manually. Just reboot to fastboot mode after the installation of Magisk in TWRP and type that command.
davidlueder said:
This worked for me too, but maybe some other users need more information on the boot partition
Oreo compatible TWRP: Download (Credits: @akhilnarang)
OOS Open Beta 25: Download (Official OnePlus Website)
Magisk 14.3 (Beta): Download (stolen from this thread)
Magisk Manager 5.4.0: Download (GitHub)
You are responsible, if it kills your device, but this was my way:
1. Full Backup in TWRP
2. Reboot into Fastboot Mode
3. Flash Oreo compatible TWRP
4. Use Volume Keys to select and boot into recovery
5. Install OOS Open Beta 25
Then i did a reboot and Steps 1&2 again but i don't think this is required.
6. Install Magisk 14.3 Beta
7. Create an image of the boot partition
Code:
adb shell
dd if=/dev/block/sde18 of=/sdcard/boot.img
exit
8. Copy the boot.img file to your computer
9. Open this file in a hex exitor, add the following text after "buildvariant=user" (image in baskaflyfer's answer) and save the file:
Code:
androidboot.selinux=permissive
10. Reboot into fastboot mode
11. Flash modified boot image
12. Reboot to OOS
13. Install the Magisk Manager APK
Click to expand...
Click to collapse
Is Magisk stable? Did you try any modules and which ones? Are they working fine?
ishanp said:
Is Magisk stable? Did you try any modules and which ones? Are they working fine?
Click to expand...
Click to collapse
I did not try any modules but multiple apps that require root: AirDroid, AFWall+, Amaze (Root enabled). They're working fine.
Additionally, this magically fixed my ctsProfile. Magisk's SafetyNet-Test is successful on my device now.
Edit: I was able to install ViPER4Android FX for Magisk v14+ (v2.5.0.5) by ShadySquirrel without any errors, but driver status tells me that it is not enabled. Maybe because they officially just support ROMs up to Android Lollipop.
davidlueder said:
Edit: I was able to install ViPER4Android FX for Magisk v14+ (v2.5.0.5) by ShadySquirrel without any errors, but driver status tells me that it is not enabled. Maybe because they officially just support ROMs up to Android Lollipop.
Click to expand...
Click to collapse
Try in terminal after boot:
Code:
su
setenforce 0
Restart ViperFX app. Please report, I am on SuperSU but will jump the moment my fav modules start working
Also I'm using Viper4Arise (bundled with Magnum Opus) right now. If that didn't work you can use that.
LineageOS 15.1 (Beta v1.01) originally for Moto E5 Play (james) working on Moto E5 (Nora)
Very Important!!!!
I've just found the way to boot sucessfully LOS 15.1 on nora_row, the ROM was originally made by @MotoJunkie01, so I'm not taking this ROM as mine, I've mentioned that I'm not a dev, I just love to share what I found, I hope this won't cause any problem and it will be useful for you guys.
Previously I've shared how to root Moto E5 (Nora) because there wasn't any specific info for that variant, TWRP and Root Guide was only for Play/Plus, and then after some attemps, I finally found a way to use TWRP and how to flash LOS 15.1
Disclaimer
I'm not responsible for any dead SD cards/phones
If your phone turns into a nuclear bomb
If your dog/cat complain about you
Advertisment
The ROM is working almost fine but "Keep in mind that I have XT1944-2" also it is a beta ROM and if my previous guide of root didn't work properly, you shouldn't try to install it, because it may result on a brick or something else, as always is mentioned, try by your own risk.
BUGS
Working:
RIL
Bluetooth
WiFi
Not Working:
Camera
You tell me
Requirements
1. The most important and obviously, unlocked bootloader, a computer, and just basic knowldge
2. Stock ROM zip, in case of something is wrong and because you'll need to extract boot.img, here are the links and a guide to recover your phone in case of brick: https://forum.xda-developers.com/moto-e5/how-to/firmware-moto-e5-xt1944-4-dual-sim-t3820901
3. TWRP recovery. You can get it here: https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323
4. You may wonder how to install TWRP, I must admit that it's not possible on Nora (causes brick) but searching here in XDA I've found that you can boot into TWRP without installing and also if you make a backup it will work in case of emergency
5. Platform tools folder that contains fastboot and adb drivers (your boot.img must be extracted here): https://www.dropbox.com/s/c3c8rev5e40gy5b/platform-tools-latest-windows.zip?dl=0
6. Remember to put the ROM and Gapps on your SD:
ROM: https://drive.google.com/open?id=1F2rC7zIZPqod3vMC1t22uhNYMQbf56K6
Gapps: https://drive.google.com/drive/folders/1rHf5XIs7XK3kWFFLekjrK0ub_bKnSlUI
Instructions
1. First of all boot into bootloader or fastboot (power & volume down) and connect your phone to your PC
2. At this point it is supposed that you have downloaded platform tools folder and all necessary zips (stock ROM, LOS, gapps), then inside the folder press Shift+Right Click, and select "open CMD window here" for Windows 7, on Windows 8 and up just click "Archive", then when CMD it's open, type: fastboot boot twrp_james.img Your phone automatically will reboot into TWRP.
3. The recovery will delay 1 or 2 minutes to start and it will ask us for our key to decrypt data. Just press cancel, because we don't have that key, and that option is not working and swipe to allow modifications. Don't mount anything, what it is already mounted is fine, only you can mount SD Card, in case that is not mounted, if you don't have a SD Card you wouldn't be able to make a backup
4. Go to backup section, and choose SD Card to put your backup there, remember that the Backup couldn't be saved on Internal Storage because the ROM will wipe Internal Storage and System, then if you choose all the partitions nothing wrong would happen, but if you are not pretty sure, just skip data and cache
5. The time that TWRP will took to backup depends on the things that you have on your system (Ignore red letters that show some errors)
6. Then go to Wipe section and swipe to perform a factory data reset. Now, select Wipe and then Format Data, and follow all prompts to commence formatting and then go to reboot section and choose bootloader because remember that TWRP is not installed and we nned to reboot the recovery, then use again CMD to boot into TWRP
7. Then we are again on TWRP, then press Install, select SD Card and look for the ROM zip and Gapps and swipe to flash, it's very fast the installation, wait until it finish and reboot your device into bootloader, It will be with red letters, but don't be affraid.
8. Another important thing, that ROM, contains boot.img from Moto E5 Play, that's what I told you, that you will need to use boot.img from stock ROM, then go to Platform Tools Folder and again open CMD (Shift+Left Click for W7) and type: fastboot flash boot boot.img Wait until it finish and type fastboot reboot
9. And that's all, first boot will delay, be patience. Additionally I couldn't find a way to skip force encrypt, so the phone will be encrypted and it will reboot, sometimes if you reboot the ROM it would reboot again, it's normal, As this ROM it's unnofficial it will show tha your device is uncertified but you can hide that notifications and use your phone normally.
Magisk, Xposed and Substratum work, but choose carefully what are you going to install because some modules will cause problems or a bootloop, if you need some help write your comments and experiences. YouTube for some reason open but didn't shows anything.
THANKS & MENTIONS:
Thanks to @SuperR. for his awesome Windows Kitchen;
Thanks to @CodyF86 for breaking ground and building TWRP for the james;
Thanks and credits to @phhusson for his Phh-Treble Vanilla GSIs;
Thanks to @Deivid_21 for sharing working gapps
Thanks to the entire LineageOS team;
This is great news. Slowly but surely, development for the entire Moto E5 series is growing. Great work on this OP.
MotoJunkie01 said:
This is great news. Slowly but surely, development for the entire Moto E5 series is growing. Great work on this OP.
Click to expand...
Click to collapse
Yeah thank you, but I was unable to find a no verity kernel for E5, Play and Plus have got it, but this one not, then thanks for sharing a LOS 15.1 it's cool just the only bug was the camera but because of that encryption the ROM became laggy, I wish I could have a good computer to compile but well it seems to hard, anyway i hope more coming ROMS because it's sad that LOS 16 it's already released and we hardly have got just one but it's appreciated the time and effort for this one
Fersho said:
Yeah thank you, but I was unable to find a no verity kernel for E5, Play and Plus have got it, but this one not, then thanks for sharing a LOS 15.1 it's cool just the only bug was the camera but because of that encryption the ROM became laggy, I wish I could have a good computer to compile but well it seems to hard, anyway i hope more coming ROMS because it's sad that LOS 16 it's already released and we hardly have got just one but it's appreciated the time and effort for this one
Click to expand...
Click to collapse
Yeah that's my dilemma as well. I have neither the time nor regular access to a high quality machine to compile. I have a port for Lineage 16.0 for the E5 Play which boots and functions somewhat. When I can smooth some things out and get it a bit more stable, I'll post it as well.
You should post a no-verity kernel for the E5 for others to use. It would be appreciated I'm sure.
MotoJunkie01 said:
Yeah that's my dilemma as well. I have neither the time nor regular access to a high quality machine to compile. I have a port for Lineage 16.0 for the E5 Play which boots and functions somewhat. When I can smooth some things out and get it a bit more stable, I'll post it as well.
You should post a no-verity kernel for the E5 for others to use. It would be appreciated I'm sure.
Click to expand...
Click to collapse
For real? I would really love to test Pie, pls upload it, then I'm trying to post a no-verity kernel but then how am I going to extract the necessary things? I had seen a tutorial to unpack boot.img but then I don't know how to disable dm vrity or where are the files located on Moto E5 Play/Plus kernel
Fersho said:
For real? I would really love to test Pie, pls upload it, then I'm trying to post a no-verity kernel but then how am I going to extract the necessary things? I had seen a tutorial to unpack boot.img but then I don't know how to disable dm vrity or where are the files located on Moto E5 Play/Plus kernel
Click to expand...
Click to collapse
Here is an easier method -- install the stock boot image on your device using either fastboot or TWRP. Then, in TWRP, install this boot image patch script -- https://drive.google.com/file/d/1oLrNL3OYhwlCCLOtLdQEQM4tGsIucsPQ/view?usp=drivesdk
It will unpack, patch, repack and flash the modified boot image back to your boot partition, disabling dm-verity. Then use TWRP to make a backup of your /boot partition. Using a file manager, rename the backup from boot.emmc.win to boot.img and you're done. You'll then have a no-verity kernel in boot.img format. The file can then be installed by other members using fastboot or TWRP.
Once you're done, you can simply use TWRP to reinstall or restore your previous ROM configuration.
MotoJunkie01 said:
Here is an easier method -- install the stock boot image on your device using either fastboot or TWRP. Then, in TWRP, install this boot image patch script -- https://drive.google.com/file/d/1oLrNL3OYhwlCCLOtLdQEQM4tGsIucsPQ/view?usp=drivesdk
It will unpack, patch, repack and flash the modified boot image back to your boot partition, disabling dm-verity. Then use TWRP to make a backup of your /boot partition. Using a file manager, rename the backup from boot.emmc.win to boot.img and you're done. You'll then have a no-verity kernel in boot.img format. The file can then be installed by other members using fastboot or TWRP.
Once you're done, you can simply use TWRP to reinstall or restore your previous ROM configuration.
Click to expand...
Click to collapse
It doesn't works, also using zip on LOS/Stock it doesn't boot
Fersho said:
It doesn't works, also using zip on LOS/Stock it doesn't boot
Click to expand...
Click to collapse
I will patch a boot image to disabled dm-verity for the Moto E5. I'll post soon as I get some free time.
MotoJunkie01 said:
I will patch a boot image to disabled dm-verity for the Moto E5. I'll post soon as I get some free time.
Click to expand...
Click to collapse
Thanks, but finally I removed encryption, but men, it was very hard for me and it took me like 3 or 4 hours, but well the procedure is a llitle bit confusing, and I couldn't create a boot.img just ported the ones already shared for Play/Plus and seemed to work "fine", If I got some time I would make another tutorial but I guess that it will be long
Here is a no-verity kernel for the xt1944-2 Moto E5
From Build No. OPP27.91-25
https://drive.google.com/file/d/1NcyuFRgvvRiS5MT5Jxl3uS3XHCnULBMc/view?usp=drivesdk
In case anybody needs it.
MotoJunkie01 said:
Here is a no-verity kernel for the xt1944-2 Moto E5
From Build No. OPP27.91-25
https://drive.google.com/file/d/1NcyuFRgvvRiS5MT5Jxl3uS3XHCnULBMc/view?usp=drivesdk
In case anybody needs it.
Click to expand...
Click to collapse
Thank You, Do you believe that I don't have XT1944-2 I have XT1944-4 I notice that when I've seen something in settings, then It's only flash the kernel and that's all?
Fersho said:
Thank You, Do you believe that I don't have XT1944-2 I have XT1944-4 I notice that when I've seen something in settings, then It's only flash the kernel and that's all?
Click to expand...
Click to collapse
I'll do a no-verity for xt1944-1 also. In fact, I'll try and cover all variants for which I have firmware access. You can try to boot the kernel for xt1944-2 prior to flashing it, by using:
fastboot boot no-verity_xt1944-2.boot.img
If it boots, you should be safe in flashing it to your /boot partition. In any event, I'll post some no-verity kernels for the Moto E5 variants.
so if i have the xt1944-3 can I use this tutorial? and what twrp recovery should I use..? or should i just wait
SeerePetrova said:
so if i have the xt1944-3 can I use this tutorial? and what twrp recovery should I use..? or should i just wait
Click to expand...
Click to collapse
Well I've only tested on XT1944-2/4 you should try by your own risk, then for TWRP use the one that is made for Moto E5 Play, then boot into TWRP using fastboot boot "twrp-james.img" don't try to install because it wont work
Any plans to get the remaining hardware working? I tried flashing factory Vendor image from the XT1921-1 retail firmware for the hell of it to see if that might change anything with the camera and flash, but it didn't. LOS logs a crash.
01-04 06:43:08.824 F/libc (622): CANNOT LINK EXECUTABLE "/vendor/bin/hw/[email protected]": library "[email protected]" not found
01-04 06:43:08.825 F/libc (622): Fatal signal 6 (SIGABRT), code -6 in tid 622 (motorola.hardwa), pid 622 (motorola.hardwa)
01-04 06:43:09.162 F/DEBUG (712): pid: 622, tid: 622, name: motorola.hardwa >>> /vendor/bin/hw/[email protected] <<<
01-04 06:43:09.162 F/DEBUG (712): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
01-04 06:43:09.180 F/DEBUG (712): Abort message: 'CANNOT LINK EXECUTABLE "/vendor/bin/hw/[email protected]": library "[email protected]" not found'
Click to expand...
Click to collapse
I might not have been looking in the right place but the imgtuner file name in /vendor/lib/hw is: [email protected]
If I had any idea how to fix this I would try.
weakNPCdotCom said:
Any plans to get the remaining hardware working? I tried flashing factory Vendor image from the XT1921-1 retail firmware for the hell of it to see if that might change anything with the camera and flash, but it didn't. LOS logs a crash.
I might not have been looking in the right place but the imgtuner file name in /vendor/lib/hw is: [email protected]
If I had any idea how to fix this I would try.
Click to expand...
Click to collapse
I was hoping the camera commits had been added to the GitHub repositories by now, but they have not as of this date. A manual fix can likely be accomplished by replacing the camlibs in the Lineage build with the camlibs from the stock build. Unfortunately, due to my work schedule, I don't get a lot of spare time for development, but if anybody wants to try, simply copying/replacing the camlibs from stock to Lineage should fix the camera.
MotoJunkie01 said:
I was hoping the camera commits had been added to the GitHub repositories by now, but they have not as of this date. A manual fix can likely be accomplished by replacing the camlibs in the Lineage build with the camlibs from the stock build. Unfortunately, due to my work schedule, I don't get a lot of spare time for development, but if anybody wants to try, simply copying/replacing the camlibs from stock to Lineage should fix the camera.
Click to expand...
Click to collapse
Im new to the android rom/firmware file structure. just want to make sure I understand. are you referring to the .so camera libraries in vendor/lib? or do you mean the actual /core/java/android/hardware framework files in the source?
Res Remix system-180818-arm-aonly-gapps.img
camera works good... flash too
apparently i still have force encrypt though and the phone can definitely get laggy
tbirdguy said:
Res Remix system-180818-arm-aonly-gapps.img
camera works good... flash too
apparently i still have force encrypt though and the phone can definitely get laggy
Click to expand...
Click to collapse
That's right, camera and flashlight are working on RR OS GSI Official, but that lag is horrible, well it's only while scrolling and system ui, but the rest of the apps are working fine, to disable encryption you must flash no verity kernel that it's attached on previous commentaries and also to edit fstab.qcom then you'll skip encryption, but it doesn't affect on performance because even you skipped encryption the device still laggy, also on Pie is the same, but some extra bugs like graphic glitches, anyway I couldn't find a way to fix that lag, even using apps like L Speed
Fersho said:
That's right, camera and flashlight are working on RR OS GSI Official, but that lag is horrible, well it's only while scrolling and system ui, but the rest of the apps are working fine, to disable encryption you must flash no verity kernel that it's attached on previous commentaries and also to edit fstab.qcom then you'll skip encryption, but it doesn't affect on performance because even you skipped encryption the device still laggy, also on Pie is the same, but some extra bugs like graphic glitches
Click to expand...
Click to collapse
Just FYI the no verity kernel results in a bootloop on the TMO XT1921-3
Hi All,
I have experimented and developed a simpler root method via Magisk. I AM NOT RESPONSIBLE FOR ANY LOSS OR BRICKED DEVICES OR WORLD GOING CRAZY.
Requirements
Unlocked Bootloader
Magisk Manager 8.0.2 or above
One Plus 8 Pro
Patience.
Steps:
1. Download google platform tools and extract them somewhere with a short path
2. Extract boot image from beta rom or stable rom (Currently I am on Beta 3)
3. Copy extracted boot image to phone (use easy to remember path, e.g. Downloads folder)
4. Install Magisk Manager 8.0.2
5. IMPORTANT >>> Switch update channel of Magisk Manager in settings to Beta to get Beta 21 update of Magisk
6. Select install in Magisk section and click select and patch a file, then patch previously extracted (step 2 and 3) boot image
7. Disconnect and reconnect the data cable to refresh the folder contents
8. Copy patched boot image to adb folder in the PC (step 1)
9. Reboot phone to bootloader
10. Give the quoted command via CMD or PowerShell (without quotes) “fastboot flash boot magisk_patched.img”
11. If successful type” fastboot reboot”
12. Enjoy your rooted phone.
RESERVED
Khalid Ghouri said:
Steps:
1. Download google platform tools and extract them somewhere with a short path
2. Extract boot image from beta rom or stable rom (Currently I am on Beta 3)
3. Copy extracted boot image to phone (use easy to remember path, e.g. Downloads folder)
4. Install Magisk Manager 8.0.2
5. IMPORTANT >>> Switch update channel of Magisk Manager in settings to Beta to get Beta 21 update of Magisk
6. Select install in Magisk section and click select and patch a file, then patch previously extracted (step 2 and 3) boot image
7. Disconnect and reconnect the data cable to refresh the folder contents
8. Copy patched boot image to adb folder in the PC (step 1)
9. Reboot phone to bootloader
10. Give the quoted command via CMD or PowerShell (without quotes) “fastboot flash boot magisk_patched.img”
11. If successful type” fastboot reboot”
12. Enjoy your rooted phone.
Click to expand...
Click to collapse
Same instructions as we already have in the guide section.
Kollachi said:
Same instructions as we already have in the guide section.
Click to expand...
Click to collapse
Yeah, just what's needed... another guide for people to not follow properly!
Kollachi said:
Same instructions as we already have in the guide section.
Click to expand...
Click to collapse
I didn't want to say it.
Also I feel there's a step missing to fastboot boot the image first rather than flashing it to avoid issues with the patched image not booting...
But yeah the guide already exists
Khalid Ghouri said:
...
Click to expand...
Click to collapse
@Khalid Ghouri THREAD CLOSED as a subject matter related thread already exists: https://forum.xda-developers.com/oneplus-8-pro/how-to/root-uk-eu-patched-magisk-boot-img-t4175033
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
Click to expand...
Click to collapse
OnePlus 7T OxygenOS 10.0.16.HD65AA Global boot.img
Stock:
https://srv-store5.gofile.io/download/cSmFwc/boot.img
Magisk Patched:
https://srv-store5.gofile.io/download/cSmFwc/magisk_patched.img
thexile said:
OnePlus 7T OxygenOS 10.0.16.HD65AA Global boot.img
Stock:
https://srv-store5.gofile.io/download/cSmFwc/boot.img
Magisk Patched:
https://srv-store5.gofile.io/download/cSmFwc/magisk_patched.img
Click to expand...
Click to collapse
please upload from some hosting, gofile.io can't download thanks
thexile said:
OnePlus 7T OxygenOS 10.0.16.HD65AA Global boot.img
Stock:
https://srv-store5.gofile.io/download/cSmFwc/boot.img
Magisk Patched:
https://srv-store5.gofile.io/download/cSmFwc/magisk_patched.img
Click to expand...
Click to collapse
Thanks. Installed and works. Rooted. Magisk installed.
Which magisk version is patched?
A download error occurs.
Can you please upload the patched file to another link, the above is not working. Thank you.
thexile said:
OnePlus 7T OxygenOS 10.0.16.HD65AA Global boot.img
Stock:
https://srv-store5.gofile.io/download/cSmFwc/boot.img
Magisk Patched:
https://srv-store5.gofile.io/download/cSmFwc/magisk_patched.img
Click to expand...
Click to collapse
Can you pls write a guide about how to flash those img files. Sorry im a noob
Thanks!
See this post. Make sure you upgrade first to the latest release and have Magisk installed.
[ROOT/MAGISK] OOS 10.0.14 Magisk patched_boot.img GLOBAL
For future use or other versions like OOS EUROPE,INDIA, etc. , you can patch your own boot.img with my tool here But for now just follow the instructions Boot.img patched with MAGISK 20.4 on OOS 10.0.14 HD65AA (GLOBAL) Only for OOS 10.0.14...
forum.xda-developers.com
kurskoo40 said:
Can you pls write a guide about how to flash those img files. Sorry im a noob
Thanks!
Click to expand...
Click to collapse
1) Download and install ADB and Fastboot package 1.4.3 into C:\adb folder: https://www.mediafire.com/file/ccnnv843a20tqbn/minimal_adb_fastboot_v1.4.3.zip/file
2) Download and install OnePlus USB drivers:
https://oneplususbdrivers.com/download/1647/
3) Enable "Developer Options" and then "USB debugging":
a) OnePlus 5T and later: Settings > About phone > Build number
b) Reveal Developer options:
Once you’ve found the screen with your Build number, you'll need to tap on it seven seven times. That's right: seven times. After a few taps, you'll see a small pop-up alert telling you that "You are now X steps away from being a developer" with a number that counts down with every additional tap. Then tick on "USB debugging" option.
4) Plug in your stock OP7T USB-C cable into your OP7T on small end and Windows 10 laptop USB-2.0 port on large end (it should recognize phone and on phone screen pops up "allow USB debugging" which you should tick "Yes"
5) Open "Command Prompt" while your FILE EXPLORER has C:\adb folder opened by holding Left Shift Key and Right mouse click inside that window or manually change directory to C:\adb foder by typing at the C:\Users\.... "cd \adb"
6) type "adb devices" in your command prompt and if your phone is connected and recognized appropriately, it should say "xxxxxxx device"
7) type "adb reboot bootloader" and phone will reboot into bootloader or fastboot mode.
8) type fastboot flash boot patchboot.img (patchboot is actually the name of the Magisk patched boot file you downloaded)
9) type fastboot reboot and phone will reboot into Oxygen that's rooted--must install MagiskManager.apk to install module and allow root
Boot - 10.0.16 - HD65AA - Stock Global - OP7T
boot_10.0.16HD65AA_GLO_stock_op7t.img
drive.google.com
Boot - 10.0.16 - HD65AA - Magisk_Patched Global - OP7T
boot_10.0.16-HD65AA_GLO-magisk_patched_op7t..img
drive.google.com
Worked perfect, thanks guys, I even splurged and bought Gofile 3 cups of coffee.
Thx for this guide!
Can i use these img-files also in Europe? Or do i need the Europe-versions for this?
When others files needed, can you please share these?
Thx
pitchdown said:
Thx for this guide!
Can i use these img-files also in Europe? Or do i need the Europe-versions for this?
When others files needed, can you please share these?
Thx
Click to expand...
Click to collapse
I have flashed 10.0.0.15 and 10.0.0.16 with root from magisk
10.0.0.15 is working well
10.0.0.16 --> can not enable wifi. This will be disabled after enabling.
Anybody with a solution for this?
Is there a also a repositity available where all magisk-images are available for Europe?
Running a One Plus 7T in the Netherlands here.
any patch boot.img for the lastest android 11 global rom?
Hello erveryone. I managed to extract the stock boot.img of the last update (OnePlus7TOxygen_14.O.25_OTA_0250_all_2103170010) and patched it with Magisk (installed Canary version to avoid any issues) if anyone interested. Just flashed it with my phone, no issues :
magisk
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
jayreen said:
Hello erveryone. I managed to extract the stock boot.img of the last update (OnePlus7TOxygen_14.O.25_OTA_0250_all_2103170010) and patched it with Magisk (installed Canary version to avoid any issues) if anyone interested. Just flashed it with my phone, no issues :
magisk
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Is this android 11?
If not has anyone seen a stable release?
pitchdown said:
I have flashed 10.0.0.15 and 10.0.0.16 with root from magisk
10.0.0.15 is working well
10.0.0.16 --> can not enable wifi. This will be disabled after enabling.
Anybody with a solution for this?
Is there a also a repositity available where all magisk-images are available for Europe?
Running a One Plus 7T in the Netherlands here.
Click to expand...
Click to collapse
FastbootRoms - Browse /OnePlus 7T at SourceForge.net
sourceforge.net
These are fastboot roms but are very simple. If you have unlocked boot loader all you need to do is drop the contents of this zip into your adb folder . It will overwrite some stuff. Open the location with powershell and run flash-all.bat
I just updated mine to global this way. But I see European also. It's not newest but you can update with oto .16
atmcnelis said:
Is this android 11?
If not has anyone seen a stable release?
Click to expand...
Click to collapse
Disregard I found the 11 beta 4 ota and updated and no wipe of data. Just downloaded and did local upgrade.
OnePlus 7 & 7T OxygenOS 11 (Android 11) Open Beta 4 update released
Android 11-based OxygenOS 11 Open Beta 4 update is here for the OnePlus 7 & 7T series as the OnePlus 7 skips the Open Beta 3 update.
piunikaweb.com
Can someone be kind to share Magisk Patched boot.img for EU Variant please - 10.0.16.HD65BA
drjat said:
Can someone be kind to share Magisk Patched boot.img for EU Variant please - 10.0.16.HD65BA
Click to expand...
Click to collapse
Your welcome.
DISCLAIMER* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.PRE REQUIREMENTS:- SDK Platform-tools (Get it here)
-boot.img from Stock Rom
-Patience
LET'S BEGIN!
Extract the SDK Platform tools folder to an easily accessible directory
UNLOCKING THE BOOTLOADERNOTE: THIS WILL ERASE ALL DATA FROM YOUR DEVICE SO MAKE SURE TO TAKE A BACKUP IF NECESSARY
-Extract the SDK Platform tools folder to an easily accessible directory
- Go to Settings > About Tablet > Tap build number 7 times. Go back to main page of Settings > System > Developer
options and enable OEM unlocking and USB Debugging
- Reboot the system to bootloader (Press Vol - and Power key or type "adb reboot bootloader" by opening a command prompt window in Platform tools directory)
- To unlock bootloader type the below code
fastboot flashing unlock
- The device will do a factory reset and restart itself
-After Setting up your device install the magisk app from here
ROOTING [MAGISK]METHOD-1 (FASTBOOT)- Transfer your boot.img to Internal Stroage
- After installing the magisk app Go to Install > Select and Patch a File
- Select the boot.img you transferred to Internal Storage. Magisk will patch your boot.img and display the output folder after the process.
- Transfer the Patched boot.img to SDK Platform tools folder and rename it to boot.img
- Reboot to Bootloader and type the below command:
fastboot flash boot boot.img
-Reboot the device by typing:
fastboot reboot
-Check Magisk manager and the device must be rooted now
METHOD-2 (TWRP)- Install TWRP by following this guide
- Download the magisk apk. Transfer it to SD-Card and flash it from twrp
- Reboot your device
CREDITS@topjohnwu Magisk
@adazem009 For TWRP recovery
Press Thanks button if this guide was useful to you!
@Johannj22
We would appreciate if you provide all help in the open on the thread itself. Please do not post Telegram links and request users to visit you there for help. TG links can only be posted by Devs on Development threads in the OP only. Please read THIS.
PATCHED BOOT IMAGE FROM YT-X705FThis is a magisk patched boot.img from the latest firmware for YT-X705F. Please don't use it for other models (YT-X705L, YT-X705X)
TNSMANI said:
@Johannj22
We would appreciate if you provide all help in the open on the thread itself. Please do not post Telegram links and request users to visit you there for help. TG links can only be posted by Devs on Development threads in the OP only. Please read THIS.
Click to expand...
Click to collapse
Noted sir. It won't happen again
what version of ROM you use .
the last one is not work with magisk
I use this version YT_X705F_S001135_210909_ROW
yes this one is the last one see date from post yet,
but magisk will not work with this version anymore.
i collect from earlier version this "boot.img" does it match with a android roms 10 from lenovo ?
Loserintheend said:
yes this one is the last one see date from post yet,
but magisk will not work with this version anymore.
i collect from earlier version this "boot.img" does it match with a android roms 10 from lenovo ?
Click to expand...
Click to collapse
You just have to make sure you use the boot.img from the exact firmware you are on now. Let me know if it worked.
Johannj22 said:
I use this version YT_X705F_S001135_210909_ROW
Click to expand...
Click to collapse
so S001135 was last Offizial ROM from Lenovo , just was waiting to install this one as root.
because every three month Lenovo release OTA-Update for some Update and get worse.
After rooting tablet and lenovo release update, " boot.img" must be change back to install OTA Update from lenovo .
Now it seams this OS will be stable on Lenovo YT_X705F SMART TAB.
But still probs on running differnt APPS on this doomed crap tablet, for this issue i'm looking on LineageOS
Loserintheend said:
so S001135 was last Offizial ROM from Lenovo , just was waiting to install this one as root.
because every three month Lenovo release Update for some Update and get worse.
After rooting tablet and lenovo release update, " boot.img" must be change back to install update from lenovo .
Now it seams this OS will be stable on Lenovo YT_X705F SMART TAB.
But still probs on running differnt APPS on this doomed crap tablet, for this issue i'm looking on LineageOS
Click to expand...
Click to collapse
If you are on the same firmware S001135 then just use the boot.img I posted above. It should work. Also It would be better to disable system updates. I am creating a seperate post for running GSI of LineageOS and other ROMS.
Johannj22 said:
If you are on the same firmware S001135 then just use the boot.img I posted above. It should work. Also It would be better to disable system updates. I am creating a seperate post for running GSI of LineageOS and other ROMS.
Click to expand...
Click to collapse
No way to disable updates , after every reboot this tablet ask you again. Only mark, i will update rom manuell.
BTW im also switch off all this spying GOOGLE Apps , and a lot of this junk apps from google .
Loserintheend said:
No way to disable updates , after every reboot this tablet ask you again. Only mark, i will update rom manuell.
BTW im also switch off all this spying GOOGLE Apps , and a lot of this junk apps from google .
Click to expand...
Click to collapse
SO you are not able to root the device?. I am on latest update and I rooted it. You can install the latest firmware from Rescue and Smart assistant. Just flash it onto your device. The downloaded ROM should be saved in C:\ProgramData\RSA\Rom files\YT-X705Fxxxx\.......There you should fine boot.img
Johannj22 said:
SO you are not able to root the device?. I am on latest update and I rooted it. You can install the latest firmware from Rescue and Smart assistant. Just flash it onto your device. The downloaded ROM should be saved in C:\ProgramData\RSA\Rom files\YT-X705Fxxxx\.......There you should fine boot.img
Click to expand...
Click to collapse
i told you i do it twice , but by the last ROM i was waiting .. read my issue #9
Loserintheend said:
i told you i do it twice , but by the last ROM i was waiting .. read my issue #9
Click to expand...
Click to collapse
Waiting?. I am sorry I think its the language barrier ..I don't understand certain things you say.
Any help provided for X705X tab,It got A10 update.How can I get stock rom and boot image for the latest update?
Finally I find out RSA mentioned in this threads and able to download stock firmware
vygavedha said:
Finally I find out RSA mentioned in this threads and able to download stock firmware
Click to expand...
Click to collapse
Yes use RSA and flash the stock firmware. This stock firmware you flashed should be saved in your system's C:\ProgramData\RSA\Rom Files folder. Just get the required image files from there/
I did not flashed. I just downloaded the firmware. But it seems it is downloaded with some extension(.bmp Or pac which I did not check well).
How can I extract boot img from this?
I renamed to zip and extracted. But could not find any image files.
Can you help how did you do the extraction?
vygavedha said:
I did not flashed. I just downloaded the firmware. But it seems it is downloaded with some extension(.bmp Or pac which I did not check well).
How can I extract boot img from this?
I renamed to zip and extracted. But could not find any image files.
Can you help how did you do the extraction?
Click to expand...
Click to collapse
Send me a screenshot
Johannj22 said:
Send me a screenshot
Click to expand...
Click to collapse
Sure. I have deleted the downloaded file. I will redownload the same and update the screen shot tomorrow