Related
Hey all! I'm trying to root my OnePlus 7t but I'm on 10.0.5 stock and I can't find a patched boot.img, or even a stock one to patch in Magisk. I'm on the global variant. If someone could point me in the right direction, that would be grand. I have already read mostly all the posts...
I have the US version which I think is also the global version. Here's my patched boot.img for 10.0.5
https://drive.google.com/file/d/12tZN5D7dmovIeqsx8sTF-B0z2gxA6LG8/view?usp=sharing
Here's the stock boot for 10.0.5 as well if you screw something up.
https://drive.google.com/file/d/1nS0hqVCyntXHjbTzOH7H8-b29-IlAOIt/view?usp=sharing
Don't ask why the file sizes are so different. It just gets smaller for some reason after patching it in magisk.
I just booted with an older one and flashed the latest magisk
Need 10.0.5 boot.img stock & magisk patched for indian varient
Hey .... Can you help me with the 10.0.5 boot.img , stock & magisk patched for indian varient HD1901 of 7t
ChongoDroid said:
I just booted with an older one and flashed the latest magisk
Click to expand...
Click to collapse
I had tried booting with 10.0.3 while on 10.0.5 , Did not turn out well .
Has anyone on 10.0.5 tried booting w/ the above 10.0.5 patched img ?
Stock and Magisk patched boot.img files for HD1905 7T update version 10.0.5:
dropbox.com/s/887ibs0yorxgs2v/boot.img?dl=0
dropbox.com/s/sxrayyjn562susu/magisk_patched.img?dl=0
SkippRunning said:
Stock and Magisk patched boot.img files for HD1905 7T update version 10.0.5:
dropbox.com/s/887ibs0yorxgs2v/boot.img?dl=0
dropbox.com/s/sxrayyjn562susu/magisk_patched.img?dl=0
Click to expand...
Click to collapse
Do I only need to flash the patched img or both ?
And do they need to be flashed to both A and B slots ?
Thanks for sharing
hightech316 said:
Do I only need to flash the patched img or both ?
And do they need to be flashed to both A and B slots ?
Thanks for sharing
Click to expand...
Click to collapse
I would try fastboot boot before you use fastboot flash just to make sure that the device will boot successfully with the images. You should only need to fastboot boot magisk_patched.img, then open Magisk Manager and install Magisk by choosing the direct install option in the list. You only need the steps I mentioned to have root, and if you flash it to A and B at once you can get stuck in a bootloop. I had that happen at one point from flashing both partitions, and I dont recommend trying it.
SkippRunning said:
I would try fastboot boot before you use fastboot flash just to make sure that the device will boot successfully with the images.
Click to expand...
Click to collapse
Thanks , this can save a headache !
hightech316 said:
Thanks , this can save a headache !
Click to expand...
Click to collapse
Ya, I tried every relevant boot image I could find in the forums, and the device didnt work properly with any of them. The only one that allowed the device to boot successfully caused the wifi and sounds to not work. So I downloaded the full update from OnePlus and extracted it to a folder, then used payload dumper to extract all of the individual images out of the payload.bin file from OnePlus. I copied the boot.img into the phone storage and installed Magisk Manager, then patched the stock boot.img and copied it from the phone to my pc. Then I used fastboot boot magisk_patched.img to make sure the image I made would work. I booted the device and inside Magisk Manager I chose direct install in the list of options and everything went smoothly, and I didnt need to rely on finding images online that would hopefully work.
smokeythebear3 said:
I have the US version which I think is also the global version. Here's my patched boot.img for 10.0.5
https://drive.google.com/file/d/12tZN5D7dmovIeqsx8sTF-B0z2gxA6LG8/view?usp=sharing
Here's the stock boot for 10.0.5 as well if you screw something up.
https://drive.google.com/file/d/1nS0hqVCyntXHjbTzOH7H8-b29-IlAOIt/view?usp=sharing
Don't ask why the file sizes are so different. It just gets smaller for some reason after patching it in magisk.
Click to expand...
Click to collapse
Thanks a bunch for the share. That was the missing piece that I've been looking for. I have the HD1905 variant and I just used Magisk to patch the stock file you provided. After testing, I'm finally rooted. Thanks again.
For whatever reason OnePlus removed the 10.5.8 update from their server. Therefore we can't patch to boot img.
The steps I took were
1. Patch 10.5.6 boot the img in fastboot
2. Reboot into system setup magisk
3. Reboot again in fastboot
4. Boot magisk patched img
5. Go into magisk and install and choose direct install
6. Profit with a 10.5.8 device without the wifi/gps/Bluetooth issues.
Thought I'd share my experience as I bought second hand and it had the latest update and couldn't find the download link to the full system update.
Might want to mention which Magisk, the known problem with Canary?
Also why patch 10.5.6 and not 8
dladz said:
Might want to mention which Magisk, the known problem with Canary?
Also why patch 10.5.6 and not 8
Click to expand...
Click to collapse
He dont have the 10.5.8.full rom to extract and patch the img
So he probably patch the 10.5.6 img , he just boot it temporary on fastboot , going to magisk ,installing magisk and when he's rebooting , he's on 10.5.8 rooted..
Here's stock boot for 10.5.8IN11BA if anyone needs it https://mega.nz/file/sb4WwSBS#jrCL7tek0SLbynTqbPU-s_j5g0cKFRsC4u7DR7S7sCI
cultofluna said:
He dont have the 10.5.8.full rom to extract and patch the img
So he probably patch the 10.5.6 img , he just boot it temporary on fastboot , going to magisk ,installing magisk and when he's rebooting , he's on 10.5.8 rooted..
Click to expand...
Click to collapse
Can't you get it from the updater?
dladz said:
Can't you get it from the updater?
Click to expand...
Click to collapse
Not if you have already updated via the OTA..
He probably got the OTA ( full zip) install it and then boot it..
If you've updated via local upgrade , then the full ROM zip has been saved on internal storage ...
But the easiest way to update and keep root is to just take the ota through the updater..dont reboot go to magisk manager , install magisk on inactive slot , ...done...
Patched img only needed to root after unlocking bootloader ..
Not anymore....
Bought the device updated already and can't find the 10.5.8AA build at all on OnePlus
facing the same issue... if anyone have the 5.8 aa it would be a great help <3
empreror said:
facing the same issue... if anyone have the 5.8 aa it would be a great help <3
Click to expand...
Click to collapse
Patch the 10.5.6 boot IMG and the fastboot boot <patchedmagisk.img>
Setup magisk and reboot into bootloader again to boot the patched image
Then go into magisk and do direct install and finally have working wifi etc.
10.5.8AA Oneplus Pro8 boot.img
https://sourceforge.net/projects/op8pro1058aa/files/10.5.8AA.img/download
bigjailerman said:
10.5.8AA Oneplus Pro8 boot.img
https://sourceforge.net/projects/op8pro1058aa/files/10.5.8AA.img/download
Click to expand...
Click to collapse
Is this the stock boot.img or rooted patched img?
Aporzio said:
Is this the stock boot.img or rooted patched img?
Click to expand...
Click to collapse
Tried it, it's patched.
Aporzio said:
Is this the stock boot.img or rooted patched img?
Click to expand...
Click to collapse
Yes it is patched...sorry for delay
bigjailerman said:
Yes it is patched...sorry for delay
Click to expand...
Click to collapse
Not a problem. I'm glad you didn't answer lol. I ended up teaching myself how to pull the img files from a payload.bin.
JKurtz87 said:
Patch the 10.5.6 boot IMG and the fastboot boot <patchedmagisk.img>
Setup magisk and reboot into bootloader again to boot the patched image
Then go into magisk and do direct install and finally have working wifi etc.
Click to expand...
Click to collapse
Can you be please more specific? I am new here and want to know what does it mean boot temporarily ? This command will boot your device temporray and after reboot it disappear ?
fastboot boot <patchedmagisk.img>
I recently bought a Chinese phone from a relatively unknown manufacturer, so I was unable to find any TWRP images that match the device, I was wondering if it was possible to extract the boot image directly from a GSI ROM. My end goal is to install Magisk so if there is a better way to go about this please let me know.
can you tell model and brand
Hsnmastoor said:
can you tell model and brand
Click to expand...
Click to collapse
Thank you for replying,
The phone is the Cubot X20 pro, it is running the Unofficial Pixel Experience GSI ROM.
XDA-Developer30 said:
Thank you for replying,
The phone is the Cubot X20 pro, it is running the Unofficial Pixel Experience GSI ROM.
Click to expand...
Click to collapse
your welcome its mediatek download stock rom extract it and port twrp with hovatek twrp porter
Hsnmastoor said:
your welcome its mediatek download stock rom extract it and port twrp with hovatek twrp porter
Click to expand...
Click to collapse
Mediatek (MTK) Auto TWRP recovery porter by Team Hovatek
If you wish to root your Mediatek Android phone, we'd dropped a guide on rooting using Magisk and stock boot.img at https://www.hovatek.com/forum/thread-21427.html , no custom recovery is required. Se
forum.hovatek.com
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
LinhBT said:
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
Click to expand...
Click to collapse
Thank you for the reply, I forgot to mention that I used Hsnmastoor's method successfully.
LinhBT said:
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
Click to expand...
Click to collapse
I use the boot.img file from the stock rom of my device, I patch it with magisk but I always end up in bootloop
how can i root my device?
elmapq said:
I use the boot.img file from the stock rom of my device, I patch it with magisk but I always end up in bootloop
how can i root my device?
Click to expand...
Click to collapse
And your device is...???
LinhBT said:
And your device is...???
Click to expand...
Click to collapse
Tecno Spark 6 ke7
LinhBT said:
And your device is...???
Click to expand...
Click to collapse
I have a Vortex V22 MTM6761 There is no stock rom. It has unofficial GSI Pixel experience plus 13.0 running on it. I too would like to root. How can I retrieve the boot.img file from the GSI rom? Or how can I pull it from the phone via terminal and fastboot? All help is greatly appreciated! Happy Saint Patricks Day!
For devices which powered by MediaTek SOC, after flash the patched boot.img, you will need to flash patched blank vbmeta.img in order to bypass AVB with follow command :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
in which vbmeta.img is a patched blank vbmeta of your device
LinhBT said:
For devices which powered by MediaTek SOC, after flash the patched boot.img, you will need to flash patched blank vbmeta.img in order to bypass AVB with follow command :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
in which vbmeta.img is a patched blank vbmeta of your device
Click to expand...
Click to collapse
Thank you for the quick reply. I'm not sure I quite understand your message.
Flashing a vbmeta.img will give me a boot.img? I have a GSI PixelExperience 13.IMG file. The command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img was flashed along with it. It was running a different rom prior to flashing the GSI PixelExp 13.IMG
All I want to do is Root the device. I've been told over and over I need the boot.img partition to modify for Root access, but I can't get unless i'm in Root or have access to the current ROM BOOT.IMG, Correct?
Why is the BOOT.IMG or Payload.BIN missing from GSI IMG ROMS? is there another way to convert or pull from a ROM like that?
defcondoc said:
Thank you for the quick reply. I'm not sure I quite understand your message.
Flashing a vbmeta.img will give me a boot.img? I have a GSI PixelExperience 13.IMG file. The command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img was flashed along with it. It was running a different rom prior to flashing the GSI PixelExp 13.IMG
All I want to do is Root the device. I've been told over and over I need the boot.img partition to modify for Root access, but I can't get unless i'm in Root or have access to the current ROM BOOT.IMG, Correct?
Why is the BOOT.IMG or Payload.BIN missing from GSI IMG ROMS? is there another way to convert or pull from a ROM like that?
Click to expand...
Click to collapse
Yep, I think u misunderstanding me from my very first msg. What I meant back there was : GSI ROM is what called Generic System Image. Which means, it has ONLY system.img that you will need to flash into system partition of the device. Therefore, if you need the boot image in order to patch it with Magisk or else, you will need to extract the boot.img of the CURRENT ROM which is already running on your device ( and normally, it should be stock ROM ). Cuz to be in short, GSI ROM does not have any boot.img for you to seek for, my friend!
.
LinhBT said:
Yep, I think u misunderstanding me from my very first msg. What I meant back there was : GSI ROM is what called Generic System Image. Which means, it has ONLY system.img that you will need to flash into system partition of the device. Therefore, if you need the boot image in order to patch it with Magisk or else, you will need to extract the boot.img of the CURRENT ROM which is already running on your device ( and normally, it should be stock ROM ). Cuz to be in short, GSI ROM does not have any boot.img for you to seek for, my friend!
Click to expand...
Click to collapse
Thank you for the message my friend. I understand that part of it. There is no stock ROM, at least I don't think there is on it. It is a a/b system but I've tried to go back to factory reset but it does not work and goes into a boot loop. So I load the GSI pixel experience rom to get it working again.
So what you are saying is, if I do not have the stock ROM, I cannot get the BOOT.IMG, Correct? So I am pretty much out of luck to get a boot.img from a GSI? Is there another generic ROM I could use that would have a boot.IMG? Ive tried a dozen ROMS and the latest pixel experience 13 unofficial rom was the only one that worked. Maybe Im trying the wrong ROM's. I do know I need A/B versions of them, I think.
If anyone else might know a way to help get me out of this situation, I would greatly appreciate. Thank you my friends!
defcondoc said:
Thank you for the message my friend. I understand that part of it. There is no stock ROM, at least I don't think there is on it. It is a a/b system but I've tried to go back to factory reset but it does not work and goes into a boot loop. So I load the GSI pixel experience rom to get it working again.
So what you are saying is, if I do not have the stock ROM, I cannot get the BOOT.IMG, Correct? So I am pretty much out of luck to get a boot.img from a GSI? Is there another generic ROM I could use that would have a boot.IMG? Ive tried a dozen ROMS and the latest pixel experience 13 unofficial rom was the only one that worked. Maybe Im trying the wrong ROM's. I do know I need A/B versions of them, I think.
If anyone else might know a way to help get me out of this situation, I would greatly appreciate. Thank you my friends!
Click to expand...
Click to collapse
You need to understand the basic core point is : GSI is ALWAYS system image only my friend. Boot.img can be found only on FULL ROM, not GSI. And there's always stock ROM for ANY DEVICES, what you need to do is just Google with keywords : Your-Device-Full-name Stock ROM Download. Then choose the correct one which is currently running on your device and download it. Boot.img will be right there on the zip.
LinhBT said:
You need to understand the basic core point is : GSI is ALWAYS system image only my friend. Boot.img can be found only on FULL ROM, not GSI. And there's always stock ROM for ANY DEVICES, what you need to do is just Google with keywords : Your-Device-Full-name Stock ROM Download. Then choose the correct one which is currently running on your device and download it. Boot.img will be right there on the zip.
Click to expand...
Click to collapse
Thank you! I do realize the obvious. If I was able to find it, I wouldn't be asking for help. I have rooted close to a hundred phones with stock ROM's going back over a decade.
What I'm asking is, What if the stock rom cannot be found? There is no other alternative way? I challenge finding this particular stock ROM.
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB.
I have searched over and over for months on various search engines and found nothing. Maybe the ROM is uploaded somewhere in a different language other than English. I would be absolutely stunned if the stock rom was found on the internet.
Can I extract boot.img from terminal via fastboot or other linux or win program?
I have 2 models I cannot find stock ROM's for:
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB - manufacture date year 2022
Moxee M2160 Model MH-T6000 2APQU-MH-T6000 Q6006_V1.0 - manufacture date year 2022
Can anyone find anything? I have scoured the web for months!
I can't believe there is nothing available for these phones.
Please let me know if you can find a stock ROM. I would love to learn where and how you found them. As I've have found nothing for months and months.
Thank you!!!
defcondoc said:
Thank you! I do realize the obvious. If I was able to find it, I wouldn't be asking for help. I have rooted close to a hundred phones with stock ROM's going back over a decade.
What I'm asking is, What if the stock rom cannot be found? There is no other alternative way? I challenge finding this particular stock ROM.
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB.
I have searched over and over for months on various search engines and found nothing. Maybe the ROM is uploaded somewhere in a different language other than English. I would be absolutely stunned if the stock rom was found on the internet.
Can I extract boot.img from terminal via fastboot or other linux or win program?
Click to expand...
Click to collapse
You CAN extract the boot.img via terminal ONLY IF you're on a ROOTED devices!
I extracted system.img from galaxy a90 5g's firmware.
And what is the next step to port a90's firmware to my galaxy a32 4g (sm-a325n)?
(I do not have root access to my device.
So I used odin to port a90 5g's firmware.
But when I try to do it, It always fails).
I will look forward for your reply
Thank you
I'm going to take a wild guess here but your A32 is probably using dynamic partitions (system, vendor, odm and product) inside super.img. Unless you have TWRP to flash the system partition of it specifically, you won't be able to install A90's system.img
Or
An alternative would be to unpack your A32's super.img and replace the system.img inside with the A90 system.img
May I ask you how to unpack and repack super.img (to replace system.img)?
And how to flash repacked super.img (which contains a90's system.img)
Via odin (because odin does not support .img file flashing)
And it is able to boot if I only replace system.img? (or should I replace a90 5g's boot.img too?)
And doesn't it void knox warranty?
Starwars8k said:
May I ask you how to unpack and repack super.img (to replace system.img)?
Click to expand...
Click to collapse
I use SuperR's kitchen paid version
Starwars8k said:
And how to flash repacked super.img (which contains a90's system.img)
Click to expand...
Click to collapse
Do you not have TWRP?
Starwars8k said:
Via odin (because odin does not support .img file flashing)
Click to expand...
Click to collapse
Just pack the super.img into a .tar with 7zip or something
Starwars8k said:
And it is able to boot if I only replace system.img? (or should I replace a90 5g's boot.img too?)
Click to expand...
Click to collapse
Only system.img
Starwars8k said:
And doesn't it void knox warranty?
Click to expand...
Click to collapse
Yes
Why is knox broken?
Any ways to prevent?
Starwars8k said:
Why is knox broken?
Any ways to prevent?
Click to expand...
Click to collapse
Because it's not meant to be flashed on your phone, Samsung considers it custom.
And no, no way to prevent.
Do I need to unlock bootloader before flashing a32's super.img which contains a90's system.img instead of a32's ?
Starwars8k said:
Do I need to unlock bootloader before flashing a32's super.img which contains a90's system.img instead of a32's ?
Click to expand...
Click to collapse
Yes
Are you sure flashing a90's system.img to my a32 will not break compatibility and work perfectly?
Starwars8k said:
Are you sure flashing a90's system.img to my a32 will not break compatibility and work perfectly?
Click to expand...
Click to collapse
It won't work well because of the different chipset
Then I'll not port whole system.img
I just need dex firmware.
What firmware should I extract to use samsung dex?
And how to port It
Starwars8k said:
Then I'll not port whole system.img
I just need dex firmware.
What firmware should I extract to use samsung dex?
And how to port It
Click to expand...
Click to collapse
Pretty easy to answer this one... YOU CAN'T
Okay... I will port a90's whole system.img
Although a32 4g has unofficial twrp, my device is sm-a325n and it doesn't work.
And is it able to flash system.img eventhough a32 uses dynamic partition?
Does system.img contains samsung dex?
Starwars8k said:
Okay... I will port a90's whole system.img
Although a32 4g has unofficial twrp, my device is sm-a325n and it doesn't work.
And is it able to flash system.img eventhough a32 uses dynamic partition?
Does system.img contains samsung dex?
Click to expand...
Click to collapse
I already said: YOU CAN'T PORT THE WHOLE SYSTEM.IMG
A90 has VERY VERY different hardware. A32 has Mediatek and A90 has Snapdragon chipset.
I see.
Thank you for your advice.
I can't find an answer to the question is it possible to root the latest MIUI 13, A12 by Magisk and patching the boot.img as usual.
I have done it dozens of times with all MIUI12 versions, but can't risk with A13.
Anyone done it? Thanks.
Dont worry... I rooted Magisk ,work corectly
miki1320 said:
Dont worry... I rooted Magisk ,work corectly
Click to expand...
Click to collapse
Thanks for the reply.
In the fastboot TGZ file there is a vbmeta.img
Do I have to patch that file too? I have read somewhere, that the vbmeta.img needs to be patched instead of the boot.img.
Please, confirm.
Cheers.
Just a quick UP. Has anyone rooted by the Magisk method? And did you patch the boot.img or vbmeta.img file? Thanks.