Magisk patched boot.img for OOS 11.0.6 - OnePlus 7T Questions & Answers

Can anyone share magisk 24 patched boot.img for 11.0.6.1 version of stock global rom?

I was able to extract and patch boot.img from the update file. Now my problem is I can't get PC to recognize the device. Obviously already tried reinstalling device drivers + ADB, turned on/off USB debugging and default USB setting. Any ideas? Alternatively, any way to flash boot.img or get root without PC?

yeah, if someone can provide the patched boot img for 11.0.6.1 HD65AA, that would be great!

See Guides section

@sathya
I have extracted for you stock boot.img from OnePlus 7T OxygenOS 11.0.6.1.HD65AA OnePlus7TOxygen_14.O.32_OTA_0320_all_2202112234_3f24a87f818973
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
Zippyshare.com - [now defunct] Free File Hosting
So if you are running now OxygenOS 11.0.6.1.HD65AA without any mods and root just paste this boot.img file into main directory of your phone.
Start Magisk and select this file and let it patch. After patch copy magisk patched boot.img to your folder on your PC where you have fastboot files.
Would be easier to change name of patched file just to boot.img
Enter to fastboot mode on your phone and flash patched file using commands:
fastboot flash boot boot.img
Restart phone and you are rooted
I am always using this method.
But I just downgrade from OOS11 to 10 becuase is just terrible.
Wanna know more details PM me.

Here y'all go
magisk_patched-24100.img | by benv1 for OnePlus 7T
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com

ystokar said:
I was able to extract and patch boot.img from the update file. Now my problem is I can't get PC to recognize the device. Obviously already tried reinstalling device drivers + ADB, turned on/off USB debugging and default USB setting. Any ideas? Alternatively, any way to flash boot.img or get root without PC?
Click to expand...
Click to collapse
solved problem by deep cleaning of my phone's USB-C port...

Related

Yureka downgrade lollipop 5.0 to kitkat 4.4.4

Hello Members, I am about to share the final method for downgrading Yureka Lollipop to Kitkat Stock Rom.
You need to download these files
1. CM11 FASTBOOT SIGNED.ZIP DOWNLOAD LINK: http://builds.cyngn.com/factory/tomato/cm-11.0-XNPH05Q-tomato-signed-fastboot.zip
2. FASTBOOT DRIVERS DOWNLOAD LINK: https://drive.google.com/file/d/0B0_IwOvcRE4gWkpiRTBlenJoR1k/view?usp=sharing
3.LIST OF COMMANDS AND BAT FILE INCLUDED DOWNLOAD LINK: https://drive.google.com/file/d/0B0_IwOvcRE4gODk4R09GTDVVWW8/view?usp=sharing
You can enter each commands step by step or click on the bat file. But don't prefer the bat file procedure, you may get errors. I'm not responsible for any hard brick. try with on own risk.
Procedure:
1. Download these above files
2. Create a Folder name it as "Flash".
3. Extract CM11 Fastboot Signed and Fastboot Zips in that "Flash" Folder which you have just created.
4. Open the Folder and CLICK on the SHIFT button and right clicked on the mouse. You can see the "Open Command Window Here".
5. Clicking on " Open Command Window from here" will open a command window.
6. Switch off your yureka and press volume plus button and connect to the computer.
7. You will see the phone has been started in Fastboot Mode.
8. Now, You need to enter the given commands one bye one or just click on FLASH_ALL.bat file, which will flash everything easily.
9. Final step is to Reboot in Normal Mode.
10. You will be in KITKAT.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For more detail, I have uploaded a video in youtube. Please watch it. If I Helped you then please HIT THANKS.
fastboot
I am unable to set in fastboot device...
I tried a lot..can you please tell me the process of fastbooting the device
after done that procedure am i able to flash any custom rom based on cm 11 ?
after done that procedure am i able to flash any custom rom based on cm 11 ? or i have to rerooted my phone again ? plz send me rply bcoz i m going to downgrade to kitkat from buggy lollypop .

P8000 Custom Cyanogen Mod Bootlogo

Hi I changed from Eragon to CM and for me the Eragon Bootlogo was still present (maybe I am not the only one) but I want a CM Bootlogo at CM Rom so I decided to build my own logo.bin and share it with you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The pictures are sorted that way:
1 2 3 4 5 6 7
8 9 . . . . .
You could flash the files with SP Flash Tool (The original scatter file from Elephones latest stock rom is included in each Logo folder so it should work for everyone).
or you could now also flash the files through TWRP recovery as @walter79 wrote in the first post thx for this!
each folder includes now the logo.img too
I have tested all logos by my self and they work for me but I am not responsible for bricked devices so you should know what you are doing!
you also could build your own logo with this tool from @ankadnikov : http://forum.xda-developers.com/showthread.php?t=1953726 thx!
I used Image Resizer for Windows to scale the pictures to 1080x1920 https://imageresizer.codeplex.com/
and
TinyPic 3.18 (free) to reduce the file size http://www.efpage.de/Tinypic.html
feel free to share your own created boot logos here!
if there are questions I will try to answer them
You can install it easy with TWRP.
Unzip zip and copy logo.bin to sdcard and rename it to logo.img
Boot in to recovery.
Click INSTALL and select INSTALL IMAGE
Select logo.img and logo partition.
walter79 said:
You can install it easy with TWRP.
Unzip zip and copy logo.bin to sdcard and rename it to logo.img
Boot in to recovery.
Click INSTALL and select INSTALL IMAGE
Select logo.img and logo partition.
Click to expand...
Click to collapse
Yes sure but the files where curently logo.bin and not flashable through recovery at the moment
You can flash it try it. Switch from zip install to image install. It worked well.
walter79 said:
You can flash it try it. Switch from zip install to image install. It worked well.
Click to expand...
Click to collapse
thx you are right you simly have to rename from logo.bin to logo.img as you wrote in the first post. I did not read correctly sorry

[TOOL][VINCE] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)

This is the Xiaomi Redmi 5 Plus's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​
I want to specify that this tool can't bypass Xiaomi Bootloader Unlock procedure but all others function are working
Make this tool to enable diag port open without root permissions... My phones imei id is lost
not unlock bootloader my device. is redmi5plus.
[question]
So you are saying that this tool isnt compatible with other phones? Is the Device list updated over the years or what?
Please give us the tutorial and link of downloaded files that needed to flash in this Phone, I'm having a hard time to understand How this thing work

[Guide] Unbricking P20

So I kinda bricked my phone when trying to go back from Beta 9.0 to Latest Official. So I decided to give some kind of guide to try and assist the people Who also got stuck. Beware that I couldnt get ADB to work as it kept complaining about drivers which I couldnt make work but it was due toe phone being bricked. If you can get into ADB and have TWRP already loaded then you can simply transfer the three files from below to your phone and follow this guide with the below three files. It works perfectly : https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If you have the same issue as me then follow the following procedure :
I have the Dual Sim EML-L29C185 (How do I know this?) Well at first I didnt so I had to figure out. So let look at the following :
EML-L29 - Dual Sim Model
C185 - South African Region Model which you can get from the following post : https://forum.xda-developers.com/8-lite/how-to/huawei-regional-codes-t3740473
So now that you know the model number go to this site and type in the model number eg : eml-l29c185 and you will get a list of firmwares for your phone : https://pro-teammt.ru/firmware-database/?firmware_model=eml-l29c185&firmware_page=0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click on the file list and in the example below you will see 4 files but only need three. The EM09 and L29 have the same update.zip and same update_data_full_public.zip but different EML-XXX_hw_meafnaf/update_full_EML-XXX_hw_meafnaf.zip files so get the three files you need for your model.
Now download the Huawei Multitool from here : http://4pda.ru/forum/index.php?showtopic=759172&st=0#entry51396624
and The update.zip extractor from here : https://forum.xda-developers.com/showthread.php?t=2433454
We need to manually flash all the broken image files in the phone with the Multitool but the files we need to flash are inside the update.zip file and thats why need the extractor.
So unzip the update .zip file. Then point the extractor to the folder so you can extract the files needed by the Multitool.
The following Three files need to be flashed
System [Called System.img]
Boot [Called Ramdisk.img]
Recovery [Called Recovery_Ramdisk.img] make sure it is in the folder and rename it correctly. Mine was recovery_ramdis.img without the K so had to rename it otherwise multitool wont flash it]
You can also flash it manually without multitool with the following commands :
fastboot flash ramdisk ramdisk.img
fastboot flash system system.img
fastboot flash recovery_ramdisk recovery_ramdisk.img
Start your phone in Recovery mode : Switch off. Hold vol down and keep holding it and plug usb cable in. Or in TWRP reboot Bootloader.
Start multitool and click on the unbrick tab on top and follow the instructions. That worked for me.
After it was done I transfered the 3 downlaoded files to the phone and followed the procedure to make sure all 3 files are flashed because multitool only uses the update.zip file and i dont think it fixed all the region stuff but this procedure did :
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
One more

Question Cannot activate Magisk after MUI Update

Hello,
I had a working Setup with TWRP + Magisk.
Then I had the stupid idea to accept the OTA update to MIUI 14.0.6.0 (eu).
As I lost my root permissions, I decided to install Magisk again. I used the boot.img from the rom and installed it via fastboot from magisk_patched-XXXX.img.
When I look into the Magisk App (v26.1), it still states: "Installed N/A".
I also tried to flash the patched boot image via TWRP, but there is no way to gain root access anymore :/
Current Version: MIUI V14.0.6.0.TKHCNXM | stable
Can somebody give me a hint, what i'm doing wrong? I also tried to flash the _a and _b slot...
Thanks,
Stefan
stefan_at_localhost said:
Hello,
I had a working Setup with TWRP + Magisk.
Then I had the stupid idea to accept the OTA update to MIUI 14.0.6.0 (eu).
As I lost my root permissions, I decided to install Magisk again. I used the boot.img from the rom and installed it via fastboot from magisk_patched-XXXX.img.
When I look into the Magisk App (v26.1), it still states: "Installed N/A".
I also tried to flash the patched boot image via TWRP, but there is no way to gain root access anymore :/
Current Version: MIUI V14.0.6.0.TKHCNXM | stable
Can somebody give me a hint, what i'm doing wrong? I also tried to flash the _a and _b slot...
Thanks,
Stefan
Click to expand...
Click to collapse
You'll want to use fastboot to boot recovery (not flash)
And install the recovery via the on device gui
Also, I would use orangefox recovery, it was built from twrp, but has more features.
Use "method 2" in this guide:
https://theandroidrush.com/how-to-flash-orangefox-recovery-on-xiaomi-phone/
Hi,
I flashed the patched magisk boot via orangefox, but no success. Magisk still N/A
Step1: Patch boot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step2: Flash via TWRP or Orangefox
no screenshot available
Step3: Result, no Magisk (N/A)
I don't understand this. Is there a greater change in MUI14?
I also installed the Magisk APK via TWRP and Orangefox, but no other result.
Thanks,
Stefan
After serveral hours of debugging I found out, that there was a post on the net, which recommended to install the debug version of Magisk. This was a first step into the right direction. But the GUI crashed and removed the Magisk App.
The strange thing was, that all other whitelisted root apps worked. But no access to change the Whitelist.
So I tried to get the GUI back. But there was no way.
When I installed the APK, it was automatically killed and removed :/
After reinstalling via the xiaomi.eu repair (update) script I decided to to try an older Magisk Version (26.0). This crashed also, but I was able to re-run the app again.
Finally it seems that Magisk implemented a change, that crashes with my MIUI version. I will observe this and try to file a bug report.

Categories

Resources