I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks
leofung_wai said:
I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks
Click to expand...
Click to collapse
Hey,
If you've only booted the image, then you only need to reboot and the image is lost, the only way that it would be permanent is if it was flashed: fastboot flash not: fastboot boot.
Usually what happens is when you obtain a firmware to install or in your case change region, and you wish to root this firmware you would extract payload.bin then use fastboot enhance to extract the boot.img
Then copy to your phone and patch it with the latest stable Magisk (in this case 24.3)
So again, if you've only booted the image then just reboot your phone and it'll turn on using the actual flashed boot.img from the firmware, not the one you booted.
If that doesn't work then you must have flashed it. In which case you can either re-flash your original boot.img or boot then direct install a correctly patched image for the correct firmware (after a success boot) via Magisk.
leofung_wai said:
I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks
Click to expand...
Click to collapse
Here's a good "how to" to follow.
https://www.droidwin.com/how-to-root-oneplus-10-pro-via-magisk-patched-boot-img/
Canuck Knarf said:
Here's a good how to to follow.
https://www.droidwin.com/how-to-root-oneplus-10-pro-via-magisk-patched-boot-img/
Click to expand...
Click to collapse
No he has changed region. This is for color OS...he's already done all this.
If you read the OP, he's already on EU 11_A.12
This would just make matters much worse
dladz said:
No he has changed region. This is for color OS...he's already done all this.
If you read the OP, he's already on EU 11_A.12
This would just make matters much worse
Click to expand...
Click to collapse
what you talking about ...it applies to all ...if hes on colors os....oxgyen os..he stills needs ...boot img...vender_boot...and vbmeta. img and magisk
Canuck Knarf said:
what you talking about ...it applies to all ...if hes on colors os....oxgyen os..he stills needs ...boot img...vender_boot...and vbmeta. img and magisk
Click to expand...
Click to collapse
Are you suggesting that the boot.img in color OS is the same as it is in OOS?
You're mistaken if you do think that
They're completely different operating systems, have different system.img's boot.img's, in fact most if not all images are different, to suggest he should obtain a firmware that he's just changed FROM is a bad suggestion..
That's what I'm talking about.
As per the OP, he has changed region, he is no longer using color OS ( the site you suggested is referring to this firmware)
He is now on oxygen OS using the firmware EU 11_A.12
If he was to attempt to use a color OS boot image his phone would continue to be in a boot loop but for a different reason.
Again, this would make things much much worse.
If what he's advised is true then he's successfully changed OS/region and now wants to root, the only thing he's done thus far is to boot a boot image. I think he's flashed it as booting is not permanent, to suggest to go ahead and attempt to obtain a color OS boot image or vendor image is absolutely ridiculous.
He's on an EU firmware. So he requires an EU boot image.
He's in boot loop cause he is booting to A slot...
Thanks for everyone's reply i did change the boot to A and reflash everyone again it can boot now but when i try to root again , it stuck into fastboot mode
dladz said:
Are you suggesting that the boot.img in color OS is the same as it is in OOS?
You're mistaken if you do think that
They're completely different operating systems, have different system.img's boot.img's, in fact most if not all images are different, to suggest he should obtain a firmware that he's just changed FROM is a bad suggestion..
That's what I'm talking about.
As per the OP, he has changed region, he is no longer using color OS ( the site you suggested is referring to this firmware)
He is now on oxygen OS using the firmware EU 11_A.12
If he was to attempt to use a color OS boot image his phone would continue to be in a boot loop but for a different reason.
Again, this would make things much much worse.
Click to expand...
Click to collapse
oxygen OS using the firmware EU 11_A.12.... He still needs boot img ...vender_boot form the firmware EU 11_A.12 . to root
leofung_wai said:
Thanks for everyone's reply i did change the boot to A and reflash everyone again it can boot now but when i try to root again , it stuck into fastboot mode
Click to expand...
Click to collapse
you need to load the firmware EU 11_A.12 to b slot using fastboot enhance
He already had boot?? What are you talking about???
He had a functional OS, in order to root you only need ONE image.
The boot image which comes from OOS. The link you sent is for Color OS?? Make sense now ??
He just needs to patch it correctly and boot it then direct install.
Im going over this again with someone who's incapable of understanding the basics.
Canuck Knarf said:
you need to load the firmware EU 11_A.12 to b slot using fastboot enhance
Click to expand...
Click to collapse
You do realise that booting an image does not need to be directed don't you?
Only by flashing should you direct the image to a particular slot.
By flashing you are permanently flashing an image.
I don't think you understand this so I'll make it simple for you.
You want to root your phone. You have an image you've just patched, from boot.img to magisk_patched.img
Firstly you would want to send this via fastboot, you do not need fastboot enhance for this.
The preferred way to do this is to fastboot boot magisk_patched.img
Why is this preferred??
Because if it fails as it may. Then you are not stuck in a boot loop, you just reboot and you're back in the OS.
The 2nd method is flashing.
fastboot flash boot_a magisk_patched
Press enter.
fastboot flash boot_b magisk_patched
Press enter
fastboot reboot
Press enter.
Now although this can work it is not the preferred method because you aren't just booting the image you are flashing it, this means that if it fails you cannot just reboot and get back to the OS you have to either obtain a new boot image and patch it although you cannot do this yourself as your phone no longer boots or you obtain an already patched boot image, again the last one I wouldn't recommend..
Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root
leofung_wai said:
Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root
Click to expand...
Click to collapse
Ok so if you've got into the system..
You need to follow the instructions I have in my guide in order to get root...
You can use the boot image I have there.
leofung_wai said:
Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root
Click to expand...
Click to collapse
It is always better to patch boot.img of your own version (you can dump it from payload dumper etc.) and then only fastboot boot patched_image.img and then directly install it via Magisk.
Boot this image.
192 MB folder on MEGA
mega.nz
Yes i did dump from my own and patched by magisk cancy , but it still ...get in normally
Do not flash it.
If your phone boots to the OS, then open Magisk and click install. Direct install and you're done
leofung_wai said:
Yes i did dump from my own and patched by magisk cancy , but it still ...get in normally
Click to expand...
Click to collapse
If you've patched your own image and booted it then click Magisk then install. Then direct install and you're done..
dladz said:
Do not flash it.
If your phone boots to the OS, then open Magisk and click install. Direct install and you're done
Click to expand...
Click to collapse
thanks i success root by your image now
but i had a question, i messed up the slot B and now can only boot through slot A Will it affect anything
Related
Not used to giving guides
TWRP Backup - https://forum.xda-developers.com/oneplus-6t/how-to/dp3-twrp-backup-t-mobile-magisk-t3952304
But you need to download the the QB3 update zip and upack the payload.bin with a payload dumper
Make sure your device is on international and unlocked of course
Boot into Twrp recovery and copy the system.img and vendor.img onto device
Flash both images in respective partitions and on both A and B slot
Wipe data after flashing and reboot into bootloader
From directory of the rest of IMG you've extracted you'll want use fastboot and flash:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
Then reboot and done
Don't delete files just yet
Haven't tried but certain you can root this way:
After you've setup your device you can download magisk manager. Select the boot.img on you pc, in your dump folder, and copy it to your device again. In the magisk manager patch the boot image you copied, and copy that onto your PC
Now boot into bootloader and use command
fastboot flash boot magisk_patched.img
Or if that doesn't work try
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
And if device doesn't boot for any reason just flash back the stock boot.img
Enjoy
-About TWRP- (from my knowledge)
DON'T FLASH TWRP
I think recovery is running in boot.img now I'm not sure
But it seems we may need to patch the bootloader to have the recovery in there
Ive unpack both boot IMG from dp3 and Twrp IDK if they're made different but they look different unfortunately I don't understand enough to patch but hopefully that helps idk
So I wouldn't try flashing or booting into recovery it'll just freeze and flashing will mess up the whole device and you'll have to use msmtool again and redo process
ayjays said:
-About TWRP- (from my knowledge)
DON'T FLASH TWRP
I think recovery is running in boot.img now I'm not sure
But it seems we may need to patch the bootloader to have the recovery in there
Ive unpack both boot IMG from dp3 and Twrp IDK if they're made different but they look different unfortunately I don't understand enough to patch but hopefully that helps idk
So I wouldn't try flashing or booting into recovery it'll just freeze and flashing will mess up the whole device and you'll have to use msmtool again and redo process
Click to expand...
Click to collapse
It's not about patching.
Flash stock boot.img to both slots as I'm guessing you aren't sure which one your on.
I'll give u a twrp that works for qb3 also proper instructions.
T-Mobile version downside is we can't flash ota and we can't boot qb3 wth fastboot twrp so flashing the twrp.img now replaces kernel in boot.img.
Thanks, so I'll have to use the "flash recovery Twrp.img" command now?
Or, is it a custom one Twrp only for dp3?
And thank you by the way I'll probably post a guide using a backup from Twrp then
And I'm aware of checking the active slot with a command but I have trouble switching to the opposite after rebooting because of set_active command maybe I'm doing something wrong
ayjays said:
Thanks, so I'll have to use the "flash recovery Twrp.img" command now?
Or, is it a custom one Twrp only for dp3?
And thank you by the way I'll probably post a guide using a backup from Twrp then
Click to expand...
Click to collapse
Our recovery is built in boot.img.
Uploading now
---------- Post added at 10:10 PM ---------- Previous post was at 09:42 PM ----------
Boot to fastboot
fastboot getvar all
See which slot is active.
If it's slot a then this
fastboot flash boot_a qb3-twrp.img
If it's slot b then this
fastboot flash boot_b qb3-twrp.img
Once flashed choose boot recovery and once it boots u can flash stock boot.img back then flash magisk 19.4 while in twrp.
U must use USB drive decryption isn't working yet. Or adb sideload.
I've only tested this on T-Mobile version running qb3.
All credits to @mauronofrio I used his source with some modifications
https://www.androidfilehost.com/?fid=6006931924117924335
ayjays said:
Thanks, so I'll have to use the "flash recovery Twrp.img" command now?
Or, is it a custom one Twrp only for dp3?
And thank you by the way I'll probably post a guide using a backup from Twrp then
And I'm aware of checking the active slot with a command but switching to it after rebooting because I of set_active command maybe I'm doing something wrong
Click to expand...
Click to collapse
Did you try what I posted
twinnfamous said:
It's not about patching.
Flash stock boot.img to both slots as I'm guessing you aren't sure which one your on.
I'll give u a twrp that works for qb3 also proper instructions.
T-Mobile version downside is we can't flash ota and we can't boot qb3 wth fastboot twrp so flashing the twrp.img now replaces kernel in boot.img.
Click to expand...
Click to collapse
twinnfamous said:
Did you try what I posted
Click to expand...
Click to collapse
Not yet, but if you flash the stock boot image after then would there be any point in flashing the patch boot before hand? And, what I was looking for is a more permanent solution. So, that it'll boot and you can go to Twrp whenever without having to use a PC.
If that's the case and it works then nevermind but I remember and if I'm mistaken that, even if you flash the Twrp installer it'll still boot loop after the installation.
If that's still a problem maybe someone more skilled than I, or even you, can patch the stock bootimg themselves. And, eveb get it working for the future time on Q
Maybe unpacking and looking inside the boot.img and Twrp.img, the repacking with the proper adjustments
ayjays said:
Not yet but if you flash the stock boot image after then would there any point in flashing the patch boot before hand. And, what I was looking for is a more permanent solution. So, that it'll boot and you can go to Twrp whenever without having to use a PC.
If that's the case and it works then nevermind but I remember and if I'm mistaken that, even if you flash the Twrp installer it'll still boot loop after the installation.
If that's still a problem maybe someone more skilled than I, or even you, can patch the stock bootimg themselves. And, eveb get it working for the future time on Q
Maybe unpacking and looking inside the boot.img and Twrp.img, the repacking with the proper adjustments
Click to expand...
Click to collapse
I'm aware of the permanent solution your looking for. This is the first step. With magisk installed u can simply use the installer in my android file host by selecting modules push the + sign and find the installer then without rebooting install magisk direct install. Then u can boot to recovery with advanced reboot menu. U can also just do everything in twrp. After u flash twrp.img .
ayjays said:
Not used to giving guides
But you need to download the the QB3 update zip and upack the payload.bin with a payload dumper
Make sure your device is on international and unlocked of course
Boot into Twrp recovery and copy the system.img and vendor.img onto device
Flash both images in respective partitions and on both A and B slot
Wipe data after flashing and reboot into bootloader
From directory of the rest of IMG you've extracted you'll want use fastboot and flash:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
Then reboot and done
Don't delete files just yet
Haven't tried but certain you can root this way:
After you've setup your device you can download magisk manager. Select the boot.img on you pc, in your dump folder, and copy it to your device again. In the magisk manager patch the boot image you copied, and copy that onto your PC
Now boot into bootloader and use command
fastboot flash boot magisk_patched.img
Or if that doesn't work try
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
And if device doesn't boot for any reason just flash back the stock boot.img
Enjoy
Click to expand...
Click to collapse
Just like my guide last month on OnePlus forums as I am jacksummers, even if u do this we still have no calling ability whatsoever. SMS is barely working and it still blows for us. I have been trying everything to get the whole thing to not only flash and install but be able to boot with no hardware mismatch... It won't work unless we can resign the firmware with OnePlus signing keys after changing everything to say "single" still. Since we cannot change the phone. There is still something in the phone that comes back as op6tsingle
fullofhell said:
Just like my guide last month on OnePlus forums as I am jacksummers, even if u do this we still have no calling ability whatsoever. SMS is barely working and it still blows for us. I have been trying everything to get the whole thing to not only flash and install but be able to boot with no hardware mismatch... It won't work unless we can resign the firmware with OnePlus signing keys after changing everything to say "single" still. Since we cannot change the phone. There is still something in the phone that comes back as op6tsingle
Click to expand...
Click to collapse
My phone is off rn but I receive calls and texts and I've been receiving calls on my T-Mobile OnePlus 6t since I flashed it... Make sure you're on international version
the only problems i ran in myself so far are app optimzations and when i'd recieved calls and answer my voice would sound weird to them but id hear them perfectly (not my problem lol jk jk)
ayjays said:
My phone is off rn but I receive calls and texts and I've been receiving calls on my T-Mobile OnePlus 6t since I flashed it... Make sure you're on international version
the only problems i ran in myself so far are app optimzations and when i'd recieved calls and answer my voice would sound weird to them but id hear them perfectly (not my problem lol jk jk)
Click to expand...
Click to collapse
Yeah u need to flash every other partition in the bin dump. If it tells u u cannot bc it's a critical partition then ya can't. Once u do so u will have full function and on calls. It's basically everything in the payload.bin but abl,xbl, hyp, and a few others that tell ya they're critical partitions. Once u do that everything works Perfectly.. my main issue was the call issue u described..but do as I suggest and all will work
fullofhell said:
Yeah u need to flash every other partition in the bin dump. If it tells u u cannot bc it's a critical partition then ya can't. Once u do so u will have full function and on calls. It's basically everything in the payload.bin but abl,xbl, hyp, and a few others that tell ya they're critical partitions. Once u do that everything works Perfectly.. my main issue was the call issue u described..but do as I suggest and all will work
Click to expand...
Click to collapse
That's why I said to flash system and vendor in Twrp wipe data then flash the other ones I stated above in fastboot mode everything should be flashed without a problem just follow my guide it's not hard
I'm uploading twrp backup soon with root
DO AT YOUR OWN RISK I WONT BE RESPONSIBLE FOR ANYTHING!!!!!!
EVERYTHING SO FAR WORKS WITH JUST A LIL LAG HERE AND THERE
Tmo oneplus 6t fastboot flash one click Android Q DP3. i test it with and without wiping data. i just put all the files together. just run the flash bat. You need to be on latest beta. i tested myself twice.
root= Download patch q boot.img.
fastboot flash boot img after first boot. then just download canary magisk manager. a quick google search will bring it up
have fun and remember anything goes south you can msm tool back to stock!
flash all: https://drive.google.com/open?id=1D_-B5z-rHGDr6RHjDQA0hz-janrsypdv
patch boot img: https://drive.google.com/open?id=1nbiapy6HZH4VNK4JuEF9KxSIlsBRKgsX
omariscal1019 said:
DO AT YOUR OWN RISK I WONT BE RESPONSIBLE FOR ANYTHING!!!!!!
EVERYTHING SO FAR WORKS WITH JUST A LIL LAG HERE AND THERE
Tmo oneplus 6t fastboot flash one click Android Q DP3. i test it with and without wiping data. i just put all the files together. just run the flash bat. You need to be on latest beta. i tested myself twice.
root= Download patch q boot.img.
fastboot flash boot img after first boot. then just download canary magisk manager. a quick google search will bring it up
have fun and remember anything goes south you can msm tool back to stock!
flash all: https://drive.google.com/open?id=1D_-B5z-rHGDr6RHjDQA0hz-janrsypdv
patch boot img: https://drive.google.com/open?id=1nbiapy6HZH4VNK4JuEF9KxSIlsBRKgsX
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6t/development/dp3-twrp-backup-t-mobile-magisk-t3952304 TWRP backup good job on the not wiping data though
ayjays said:
That's why I said to flash system and vendor in Twrp wipe data then flash the other ones I stated above in fastboot mode everything should be flashed without a problem just follow my guide it's not hard
Click to expand...
Click to collapse
Hi, yes we are saying the same thing.. also note, for me, Calls last for a day, then broken again. Cannot use daily if u need to make phone calls. Testing with TMobile modem.img to see if resolved.
fullofhell said:
Hi, yes we are saying the same thing.. also note, for me, Calls last for a day, then broken again. Cannot use daily if u need to make phone calls. Testing with TMobile modem.img to see if resolved.
Click to expand...
Click to collapse
i made a one click fastboot let me what happens so.ican remove it and add t mo modem
omariscal1019 said:
i made a one click fastboot let me what happens so.ican remove it and add t mo modem
Click to expand...
Click to collapse
Will do buddy. Setting mine up as we speak.. I am down to just my fajita right now, bricked my pixel 3 again as I'm working on an exploit to unlock my locked down version ....
Can you relock bootloader after this? Don't want twrp or root
supaet said:
Can you relock bootloader after this? Don't want twrp or root
Click to expand...
Click to collapse
Not sure try "fastboot oem lock" in the bootloader after
Hi Guys
UPDATE 2: (2/11/2019) Boot img now patched to Magisk V20.1 and added Google Drive as a mirror
UPDATE: It has come to my attention that some users are having issues with this version, please note this is still in beta and root isn't fully supported yet, also please make sure your running the latest magisk manager (version 7.3.5 at the time of this update) BEFORE flashing the patched boot IMG, those currently having issues, try flashing the stock IMG provided and installing the latest magisk manager then flashing the patched IMG
here is a working magisk patched boot img for you guys wanting root on your new android 10 open beta 1 software.
PLEASE BE AWARE THIS DOESNT COME WITH TWRP, THIS MAY ALSO BREAK THE ORIGINAL STOCK RECOVERY, BY FLASHING THIS BOOT IMG, YOU TAKE FULL RESPONSIBILITY FOR YOUR DEVICE AND NEITHER I OR XDA WILL BE HELD RESPONSIBLE
this DOESNT contain TWRP but is just rooted with magisk v20.0
simply flash the provided file in fastboot with the following command
Code:
fastboot flash boot magisk_patched.img
Code:
fastboot reboot
Please note this will ONLY work with the OnePlus 6T
i have also provided the stock android 10 boot img in case anything goes wrong
DOWNLOADS::
[CURRENT VERSION - Magisk V20.1]
Mega -> https://mega.nz/#!YI5BkICC!66fiUUdmg1EgGcTNExHZ52IoliVY4HBMBdwxErpI-co
Google Drive -> https://drive.google.com/file/d/1xyRPzsKh1kQXK0_RpdnesuR85vc6FvRf/view?usp=sharing
[OLD Versions]
[Magisk V20.0]
https://mega.nz/#!cQRFwA7b!R1yLz1ozFUTEOLXv-OREK-oF5YeUGN1PrWvSSh22vHw
Stock Boot img
https://mega.nz/#!1BAnRCoK!nu6UVAnR2yHnbaf54FEhc7U_3oEyP1q2BFMU0LK7XC4
Credits:
@oneplus for the phone and stock boot image
@topjohnwu for magisk and his boot image patcher
Trying now. Will report.
Update: Well, after a reboot, it is just sitting at the spinning animated boot logo...been like 10 minutes.
Also couldn't enter recovery after flashing the new patched boot img.
Update 2: Flashed back stock boot.img then recovery worked and phone booted fine.
Do i need a computer for this ?
techlogik said:
Trying now. Will report.
Update: Well, after a reboot, it is just sitting at the spinning animated boot logo...been like 10 minutes.
Also couldn't enter recovery after flashing the new patched boot img.
Update 2: Flashed back stock boot.img then recovery worked and phone booted fine.
Click to expand...
Click to collapse
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
charlie95113 said:
Do i need a computer for this ?
Click to expand...
Click to collapse
yes because fastboot command is needed, henced done using pc.
mywebslave said:
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Click to expand...
Click to collapse
Only the active partition gets flashed by default that is booting...it does that fine. I don't think Magisk is compatible on the OP6T for rooting and patching the new boot.img.
Same thing even manually flashing both. It just sits with the spinning boot animation for eternity.
I also used the payload extractor and took the stock boot.img and patched it with Magisk myself. Same issue. So obviously Magisk just doesn't suppor this phone yet and Devs need to work on it.
Thx
techlogik said:
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Only the active partition gets flashed by default that is booting...it does that fine. I don't think Magisk is compatible on the OP6T for rooting and patching the new boot.img.
Same thing even manually flashing both. It just sits with the spinning boot animation for eternity.
I tried patching the stock boot.img myself as well, it ends up being the exact same size as the TS for this method...same problem.
Thx
Click to expand...
Click to collapse
Weird I was able to do the local update and install magisk to the inactive partition prior to reboot. On reboot worked fine just no recovery.
Maybe it just doesn't like this particular one. I used the latest canary version.
I'll try patching one when I get home and see how it goes. If it works out I'll post it here.
mywebslave said:
Weird I was able to do the local update and install magisk to the inactive partition prior to reboot. On reboot worked fine just no recovery.
Maybe it just doesn't like this particular one. I used the latest canary version.
I'll try patching one when I get home and see how it goes. If it works out I'll post it here.
Click to expand...
Click to collapse
Yes, I did the same thing. Also, as mentioned above, I used the payload extractor and grabbed the stock boot.img right from the Beta1 zip file.
Then, cppied over to the phone, used Magisk with Canary build as well, then flashed both boot_a and b directly with the patched file. Just sits at the animated boot spinning.
Flash stock images back, boots right up. I'm on a OP6T unlocked US phone on VZW. No problems with any other build beta or stable with twrp or magisk and custom kernels.
Thanks
techlogik said:
Yes, I did the same thing. Also, as mentioned above, I used the payload extractor and grabbed the stock boot.img right from the Beta1 zip file.
Then, cppied over to the phone, used Magisk with Canary build as well, then flashed both boot_a and b directly with the patched file. Just sits at the animated boot spinning.
Flash stock images back, boots right up. I'm on a OP6T unlocked US phone on VZW. No problems with any other build beta or stable with twrp or magisk and custom kernels.
Thanks
Click to expand...
Click to collapse
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.
mywebslave said:
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.
Click to expand...
Click to collapse
So should we be using this instead?
Sent from my ONEPLUS A6013 using Tapatalk
mywebslave said:
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.
Click to expand...
Click to collapse
Gave this a try, no luck. Stuck in bootloop but as soon as I flashed back the stock boot, it booted up just fine
zhenliang1102 said:
Gave this a try, no luck. Stuck in bootloop but as soon as I flashed back the stock boot, it booted up just fine
Click to expand...
Click to collapse
And this one?
fastboot --set_active=a
fastboot flash boot magisk_patched.img
fastboot --set_active=b
fastboot flash boot magisk_patched.img
fastboot --set_active=a
fastboot reboot
when i flash the magisk_patched.img and my cellphone reboot my cellphone does not recognize my simcard and have no network, am back on the stock boot.img
cultofluna said:
And this one?
fastboot --set_active=a
fastboot flash boot magisk_patched.img
fastboot --set_active=b
fastboot flash boot magisk_patched.img
fastboot --set_active=a
fastboot reboot
Click to expand...
Click to collapse
I doubt this would work because the patched image is only 26mb while the stock boot image is 64mb. Someone mentioned this in the OB thread
Black screen after the update
[Solved] I am facing a serious issue. I was on Magisk v20.0 and Twrp 3.3.1-1
- I uninstalled Magisk
- Installed the OTA from local
- Installed Magisk on the second partition
- Reboot
Phone rebooted
But I am getting a totally blacked out screen. Calls work, vibration, Oneplus gestures work, just the screen is black (even in safe mode)
Can anyone please help me get this sorted (with data preserved if possible) I didn't back up the data cuz I wanted to do it after I updated to 10 (as downgrading wipes the system)
Problems:
ADB is not working (unauthorized) as I haven't turned on any developer options yet and can't due to black screen.
No way to unroot at this point without adb or twrp.
Thanks in advance.
UPDATE: Flashed boot.img and it worked. I guess magisk.img is not compatible or I am doing it wrong. My bet is on the latter.
Hy, do you have proximity sensor problem after update?! Thanks...is anything i can do?
jack5225 said:
[Solved] I am facing a serious issue. I was on Magisk v20.0 and Twrp 3.3.1-1
- I uninstalled Magisk
- Installed the OTA from local
- Installed Magisk on the second partition
- Reboot
Phone rebooted
But I am getting a totally blacked out screen. Calls work, vibration, Oneplus gestures work, just the screen is black (even in safe mode)
Can anyone please help me get this sorted (with data preserved if possible) I didn't back up the data cuz I wanted to do it after I updated to 10 (as downgrading wipes the system)
Problems:
ADB is not working (unauthorized) as I haven't turned on any developer options yet and can't due to black screen.
No way to unroot at this point without adb or twrp.
Thanks in advance.
UPDATE: Flashed boot.img and it worked. I guess magisk.img is not compatible or I am doing it wrong. My bet is on the latter.
Click to expand...
Click to collapse
Same happened to me
Phone boots to a Black screen
adb reboot bootloader -> works
fastboot flash boot boot.img -> works
Only Patched boot.img -> boots to black screen
Sent from my ONEPLUS A6010 using Tapatalk
Same for me. Softbrick and phone doesn't boot. It also encrypted my whole /data with diferent password i think and I had to wipe whole /data partition. System boots after wiping data storage but as soon as I install magisk it doesn't want to boot again. I guess I will wait for final image and TWRP support.
i couldnt flash it manually (via cmd), but all in one tool managed it well.
worked fine and quick,thank you
Crazy that some phones it is working and others it doesn't. Nothing we are doing wrong, OP has work to do still. I can imagine this official update to Q is going to cause a support fiasco...if you want to root that is. ROFL. All works fine with stock though upgrade. Understand it is Beta, but they claim a November official release
We are going to need some Dev help. Or going to need to sell this phone and upgrade to the 7t or Pro..haha
Hello everyone :laugh:!
Tried rooting the Nokia 4.2, did not know which img to use exactly so I tried one from some other shady site and messed up. Luckily, the recovery partition was still working. After trying to boot lots of images, I got tired and accidentally even flashed a Nokia 6.2 TWRP image to my recovery partition. Then I completely messed up. The phone only gets into fastboot now. May I please ask some help of you? I've been trying for days to fix things. I just wanted to root the original firmware. Now when I try to flash TWRP, it even says that the 'recovery' partition has no partition table! I can still write to boot_a and boot_b though. The phone originally had the October patch level, but before bricking it I upgraded it to the December level.
Kind regards,
Alexander47u
Search on google and try do download and flash the stock firmware (unrooted)
Phone does not get detected by QFIL
thegamingcat13 said:
Search on google and try do download and flash the stock firmware (unrooted)
Click to expand...
Click to collapse
I have tried this using QFIL, however the phone is not detected. The phone also goes into fastboot as soon as the cable is plugged in, even when the phone is off.
Have also installed appropiate drivers for QFIL, but no luck.
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Works, Thank you!
thegamingcat13 said:
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Click to expand...
Click to collapse
Thank you! This worked flawlessly.
#metoo
Haha, I have done the EXACT same thing as you. Now I can only enter fastboot mode and when I try to flash anything I have downloaded I get an error about missing partitions. I have looked everywhere for details on the partition sizes, mount points and so on but nobody has uploaded the information. In the end I went and purchased a second device in order to dump the entire stock ROM in order to fix the first phone. I've got the second phone running in ADB-mode but I can only backup to an .ab file so now I am back at square one. All of the guides I can find on how to dump the ROM involves flashing TWRP recovery but THERE IS NONE FOR THE 4.2 :crying: And after researching Android forensics I have found a guide to dumping the ROM but it needs root access in the phone shell. All I wanted was root (and LineageOS). Does anyone feel like patching the stock ROM and making a zip-file containing the img-files from all of the partitions?
Hi. You need to check which slot is in use, A or B. You can also choose slot A or B with fastboot. Then you flash the images to the partitions by appending _a or _b to the partition name.
E.g.
fastboot --set-active=a
fastboot flash boot_a boot.img
Etc.
You also need to make sure you have a recent version of fastboot, as the fastboot in some Linux package managers or blog posts for Windows give you the older one, which does not support changing active slots.
Inside the stock rom that can be found online, there is another archive containing the needed images.
alexander47u said:
Hi. You need to check which slot is in use, A or B. You can also choose slot A or B with fastboot. Then you flash the images to the partitions by appending _a or _b to the partition name.
E.g.
fastboot --set-active=a
fastboot flash boot_a boot.img
Etc.
You also need to make sure you have a recent version of fastboot, as the fastboot in some Linux package managers or blog posts for Windows give you the older one, which does not support changing active slots.
Inside the stock rom that can be found online, there is another archive containing the needed images.
Click to expand...
Click to collapse
Thanks for the tip! Looks like I solved it earlier, I found a "user_update" zip in one of the downloaded ROMs and used fastboot update user_update.zip. Wuhu! I did not specify the slot but the system boots up. On the first boot I got an error message asking me to restore factory settings which seemed to work. Now all I need to do is get root access... Alexander, did you manage to flash a rooted recovery now? Thanks in advance!
You need to put the stock boot.img unaltered on a sdcard or the internal storage and then run the Magisk android app. It will offer an option to patch the boot.img. Then you can place the patched boot.img back on your computer and flash it using fastboot.
alexander47u said:
You need to put the stock boot.img unaltered on a sdcard or the internal storage and then run the Magisk android app. It will offer an option to patch the boot.img. Then you can place the patched boot.img back on your computer and flash it using fastboot.
Click to expand...
Click to collapse
I was able to succesfully patch boot.img with magisk, then I copied the patched boot image to my computer with linux. Fastboot flash boot boot.img worked but upon reboot I got an error message saying "corrupt data" and offered to do a factory reset. Any chance you can upload your patched boot image so I can use yours?
Magisk boot.img patched.
http://s000.tinyupload.com/index.php?file_id=49342816027254664129
Posted
alexander47u said:
Magisk boot.img patched.
http://s000.tinyupload.com/index.php?file_id=49342816027254664129
Click to expand...
Click to collapse
You legend! Thank you. Now to see if I can get it to work... what security patch is this up to?
Oslokalle said:
You legend! Thank you. Now to see if I can get it to work... what security patch is this up to?
Click to expand...
Click to collapse
Up to March. I used the stock rom that is floating around on the internet. Not sure if I am allowed to post stock roms.
I was able to update to April using Magisk but not any further than that.
thegamingcat13 said:
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Click to expand...
Click to collapse
Tried this using a user_update.zip file from www[.]getdroidtips[.]com/stock-rom-nokia-4-2-firmware/. My phone boots again, but Wi-Fi doesn't work. My model # is TA-1133. What should I do?
Edit: tried to install the latest security OTA from t[.]me/nokiarepoen/379, V2.29C, but I get
Code:
E:Package is for source build 00WW_2_29B but expected 00WW_1_17I
. Is there a base user_update for build 00WW_2_29B floating around?
Oslokalle said:
Thanks for the tip! Looks like I solved it earlier, I found a "user_update" zip in one of the downloaded ROMs and used fastboot update user_update.zip. Wuhu! I did not specify the slot but the system boots up. On the first boot I got an error message asking me to restore factory settings which seemed to work. Now all I need to do is get root access... Alexander, did you manage to flash a rooted recovery now? Thanks in advance!
Click to expand...
Click to collapse
Kindly provide me that zip too.
Hi all, I'd like to share my experiences here about trying to patch boot.img for the Blackview BV6300 Pro which is one of the countless MediaTek Helio P70 (aka MT6771) China phones that can be had for a bit of change at every corner nowadays. It features a fairly non-clutter generic Android 10 ROM.
I bought it because of good feature/price ratio. I also like the fairly idiot-proof MTK Preloader/SP Flash Tool combo and expected no big problems having the phone patched. Apparently that estimate was wrong.
I extracted the boot.img (at exactly 32768k) and started patching it with the latest Magisk Manager (8.0.4). When set to "Stable" the patched result came out less than 12Megs which struck me as very odd, so I did not bother trying to flash that and switched to "beta". Et voila, out came a patched image that appeared to have just the right size.
Unfortunately, after flashing the patched image, the device detected a modified boot signature and flagged "Red State, rebooting in 5s", effectively entering a boot loop. Going back to stock, then unlocking the bootloader with fastboot and reflashing patched boot changed the "Red State" to "Orange State" but the boot loop persisted.
The boot loop message also suggests to either reflash stock or "disable verified boot". Yeah, but... Magisk Manager 8.0.4 seems to have lost the "Advanced Options" menu that had been there in previous versions, allowing users to toggle dmverity while patching boot images... so I wonder how to get around this!? Any suggestions?
Any solution for this, or any suggestions to try??
Have you tried this?
https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/
Didgeridoohan said:
Have you tried this?
Click to expand...
Click to collapse
Thanks for your suggestion but it seems like this requires TWRP and, as far as I know, no TWRP recovery is available for the BV6300 Pro.
You have to unlock your bootloader FIRST and not after.Start from scratch and it will work,im sure.Cheers!!!
First make the new,i mean flash fresh firmware blablabla.Extract your firmware,copy boot img to phone,install magisk manager and patch the boot img(im sure you can do it without root(on my Redmi 9 it works),copy patched boot imhg to pc and use adb to flash,but be sure your bootloader is unlocked before.Good luck.
We must unlock the bootloader with fastboot mode or we can do it through developer options??
black_knight_ said:
We must unlock the bootloader with fastboot mode or we can do it through developer options??
Click to expand...
Click to collapse
Fastboot
Bitmixer have you manage to root your phone?
Because i still get a bootloop when flashing the patched boot image...
black_knight_ said:
Bitmixer have you manage to root your phone?
Because i still get a bootloop when flashing the patched boot image...
Click to expand...
Click to collapse
black_knight_ said:
Bitmixer have you manage to root your phone?
Because i still get a bootloop when flashing the patched boot image...
Click to expand...
Click to collapse
Did you flashed vbmeta.img ,thats important.
-CALIBAN666- said:
Did you flashed vbmeta.img ,thats important.
Click to expand...
Click to collapse
DId you mean to follow the guide of : https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/ so we can disable verified boot, because that requires twrp and it is no supported on our device.
Or something else?? And where we find vbmeta.img that disable verified boot?
black_knight_ said:
DId you mean to follow the guide of : https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/ so we can disable verified boot, because that requires twrp and it is no supported on our device.
Or something else?? And where we find vbmeta.img that disable verified boot?
Click to expand...
Click to collapse
Ive flashed vbmeta with adb on my phones,like my Redmi 9,when you dont have vbmeta i think u cant do anything with flashing something,just google for it or look here for it,good luck!!!
Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.
I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.
235anders15 said:
Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.
Click to expand...
Click to collapse
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D
sam_htc_touch said:
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D
Click to expand...
Click to collapse
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot
235anders15 said:
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot
Click to expand...
Click to collapse
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well
sam_htc_touch said:
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well
Click to expand...
Click to collapse
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process
sam_htc_touch said:
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process
Click to expand...
Click to collapse
Just for the benefit of all (if it matters), noticed that Magisk wasn't passing the Safety Net check and was showing failed for all 3. Used this fix and all is well now (Used the Sept 13 update on the page)
previously patching with stable 11.1.1.1 and broke some major functionality (eg: wifi crash, mess up video player and codec), now try to patch with magisk version, will update later
abhi0039 said:
I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.
Click to expand...
Click to collapse
stable.img from there (and the other ones) dont fastboot boot on my OSS 1.1.1.1 fastboot mode.
I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!
F5:ed said:
I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!
Click to expand...
Click to collapse
Press and hold vol up, down , power at the same time for a while it will boot to fastboot.
I got boot loop after updating to 11.1.2.2
Any new boot img?
izik.avi said:
I got boot loop after updating to 11.1.2.2
Any new boot img?
Click to expand...
Click to collapse
Haven't tested yet but here you go
rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
This one works great. Thank you.
The attached file in #13 above worked, thank you!
In case someone would like to now "How to do it" until next time this is how I did it:
How to install OOS update and root via created patch.img file in the Magisk app
1. Download the full version eg the OOS 11.x.x.x.zip file on the computer, and copy the file to the phone's internal memory as well.
2. Run the payload_dump program (https://androidfilehost.com/?fid=1899786940962605222) to extract a boot.img from the computer. You have to extract the payload.bin file from the OOS 11.x.x.x.zip file and place it in the Input folder, then run the exe-file and wait for payload to complete, then copy over the boot.img file found in the Output folder to the phone.
3. Go to Magisk app on the phone, click on the top install "Magisk", click "Select and patch a file", search for the boot.img file you created.
4. Now, Magisk will create a patched magic.img file from the boot.img file (can be called eg magic_patched-23000_xt8QR.img)
5. Copy the magisk_patched-xxxxxxx.img to your computer's "Root folder" where you have stored ADB files, etc
6. Now install the OOS 11.x.x.x zip file (should be in the mobile's Internal memory) via Settings> System> System updates and the "gear"> Local upgrade
7. When done, DO NOT reboot but go directly to Fastboot mode + connect cable to the computer
8. On the computer, type from your "Root folder":
fastboot flash boot magisk_patched-xxxxxxx.img
9. Reboot the phone - you are rooted!
rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?
raymund08 said:
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?
Click to expand...
Click to collapse
Yes
rippledrums said:
Yes
Click to expand...
Click to collapse
Thank you
Can confirm OP fastboot commands and patched boot img are working for 11.1.1.1.I uninstalled magisk by mistake and could regain root, quick and painless
Can anyone help me? flashed patched boot to A and B Slot. But Magisk is N/A. Any idea?