Related
wzsx150's TWRP was released but I didn't see a thread here, so here's recovery that everyone would flash.
MEGA mirror: https://mega.nz/#F!g4NX3QQD!mU5-gR9Eu4A8YSR9jEu5PQ
DISCLAIMER:
This is build for the CN variant of ROG Phone 2, I don't know if it works on other variants, but it's possible to restore the official recovery back to your phone.
Current version is 3.3.1-1004.
Original post on https://weibo.com/6033736159/I9XKmocRd
I am on latest ww rom, and it boots to twrp, then instantly reboots to stock recovery.
Nevermind, jut did a backup!!!!!!!!!!!!!!
How do we flash this?
Cammarratta said:
How do we flash this?
Click to expand...
Click to collapse
Fastboot flash boot recovery.img
suzook said:
Fastboot flash boot recovery.img
Click to expand...
Click to collapse
The whole process requires ROM's boot.img to participate and I think recovery-TWRP-3.3.1-1004-ASUS_ROG2-CN-wzsx150.img-tmp isn't a complete file, so you shouldn't just flash that directly to your phone. I wish I know how to decrypt the batch file and localize it in English so non Chinese speakers would use it too. I'll make a simple guide if the original developer doesn't make a English one.
FYI: The current build of this TWRP only has Simplified Chinese and English language, also has a modified splash image with author's info on it.
zestybaby said:
The whole process requires ROM's boot.img to participate and I think recovery-TWRP-3.3.1-1004-ASUS_ROG2-CN-wzsx150.img-tmp isn't a complete file, so you shouldn't just flash that directly to your phone. I wish I know how to decrypt the batch file and localize it in English so non Chinese speakers would use it too. I'll make a simple guide if the original developer doesn't make a English one.
FYI: The current build of this TWRP only has Simplified Chinese and English language, also has a modified splash image with author's info on it.
Click to expand...
Click to collapse
Rename the file...delete the -tmp. That should be self explanatory, and the 1st screen that pops up when twrp boot. CLEARLY has a language button. press it, select english. Simple. The Author of this, has been around forever.
suzook said:
I am on latest ww rom, and it boots to twrp, then instantly reboots to stock recovery.
Nevermind, jut did a backup!!!!!!!!!!!!!!
Click to expand...
Click to collapse
So does it work on ww?
is there a way to fix touch input not working on twrp?
Cammarratta said:
is there a way to fix touch input not working on twrp?
Click to expand...
Click to collapse
Working fine here
Cammarratta said:
is there a way to fix touch input not working on twrp?
Click to expand...
Click to collapse
So i had to reflash and now my touch isnt working. You gets yours working?
Yeah. I reflashed and made sure there was no lock screen set or fingerprint and now it's working. Makes updating Roma really easy since since I'm in the latest we rom.
Cammarratta said:
Yeah. I reflashed and made sure there was no lock screen set or fingerprint and now it's working. Makes updating Roma really easy since since I'm in the latest we rom.
Click to expand...
Click to collapse
So I've bought the tencent version CN, which will arrive soon but with WW rom flashed on it. So I can just download latest WW update and flash the zip through TWRP, correct?
Yes. If you have this twrp you can flash and it'll update it.
Can I just check, with ROG phone II we don't use 'fastboot flash recovery recovery.img' , we instead use 'Fastboot flash boot recovery.img' to flash this twrp? Sorry, but I'm used to the fastboot flash recovery, so just wanted to make sure... Thanks
It's just that @suzook said it needs to be 'fastboot flash boot recovery.img'
Oh yes, and also, I'm guessing BL must be unlocked to flash this recovery?
EDIT: Nevermind about the flashing process, I see there is no seperate recovery partition to flash and the twrp img is the same size as the extracted rom boot img, so yes, it should be as @suzook mentioned.
I'd still like to confirm that flashing twrp MUST have BL unlocked, or not?
@reg66 I suggest you use this method first https://forum.xda-developers.com/rog-phone-2/how-to/flashing-ww-rom-changing-cn-fingerprint-t3969765
reg66 said:
Can I just check, with ROG phone II we don't use 'fastboot flash recovery recovery.img' , we instead use 'Fastboot flash boot recovery.img' to flash this twrp? Sorry, but I'm used to the fastboot flash recovery, so just wanted to make sure... Thanks
It's just that @suzook said it needs to be 'fastboot flash boot recovery.img'
Oh yes, and also, I'm guessing BL must be unlocked to flash this recovery?
EDIT: Nevermind about the flashing process, I see there is no seperate recovery partition to flash and the twrp img is the same size as the extracted rom boot img, so yes, it should be as @suzook mentioned.
I'd still like to confirm that flashing twrp MUST have BL unlocked, or not?
Click to expand...
Click to collapse
Bl absolutely needs to be unlocked, otherwise the recovery won't flash.
ermacwins said:
@reg66 I suggest you use this method first https://forum.xda-developers.com/rog-phone-2/how-to/flashing-ww-rom-changing-cn-fingerprint-t3969765
Click to expand...
Click to collapse
Yep, no worries, I'll use that apk to unlock BL, but is the rest of it necessary? My phone will already have FP changed to WW by seller (Giztop)..
reg66 said:
Yep, no worries, I'll use that apk to unlock BL, but is the rest of it necessary? My phone will already have FP changed to WW by seller (Giztop)..
Click to expand...
Click to collapse
My opinion? Bl unlock, completely reflash the ww rom yourself, this way your fresh, and know it's done properly.
Now we need custom roms ??
This recovery installs OK for me on my CN phone converted to WW rom, but if I use the TWRP "Root Phone" option in Advanced to root and install Magisk, it disables the Wifi, and after rebooting the phone it goes into a bootloop that I can't recover from (not even restoring from TWRP backup) and I have to reflash WW rom to recover. I repeated this refleash/reroot process 3 or 4 times and it happened every time with breaking wifi and then reboot failing.
So it works, but I wouldn't use the built-in rooting yet until it is ironed out.
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.
Im getting very frustrate sorry for this message if its to mush to ask for
i have Oneplus 7T
and the bootloader is unlocked
I installe the lateste update OS OxygenOS 10.0.8 (EU)
And what to root it with magisk and i cant flash it in anyway i try to with cmd
So i need some help to get it to work .anyone in here that have the time to send me a guide
there are so many and i cant get to work
So what i need is a easy guide that show me how to do it step by step
zagget said:
Im getting very frustrate sorry for this message if its to mush to ask for
i have Oneplus 7T
and the bootloader is unlocked
I installe the lateste update OS OxygenOS 10.0.8 (EU)
And what to root it with magisk and i cant flash it in anyway i try to with cmd
So i need some help to get it to work .anyone in here that have the time to send me a guide
there are so many and i cant get to work
So what i need is a easy guide that show me how to do it step by step
Click to expand...
Click to collapse
So where are you stuck?
Let's go step by step:
So you have unlocked the bootloader and now you have the stock boot img for you rom patched?
Have you tried to install the patched img through adb?
Fastboot flash boot nameofimg.img
Make sure is the patched img.
Once you do that you have to go to magisk web site https://******************/ download the lastest apk.
Install remember to allow your browser to install unknown apps.
Once that happens magisk Wil tell you that it needs to install some extra things let it do it and it will reboot.
I know you said you tried it but in this guide you also get the patched boot img.
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
lil_kujo said:
So where are you stuck?
Let's go step by step:
So you have unlocked the bootloader and now you have the stock boot img for you rom patched?
Have you tried to install the patched img through adb?
Fastboot flash boot nameofimg.img
Make sure is the patched img.
Once you do that you have to go to magisk web site https://******************/ download the lastest apk.
Install remember to allow your browser to install unknown apps.
Once that happens magisk Wil tell you that it needs to install some extra things let it do it and it will reboot.
I know you said you tried it but in this guide you also get the patched boot img.
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Click to expand...
Click to collapse
The bootloader is onlocked YES
Im not sure about the ADB i dont now how it works ? I use to flash my OnePlus fon with cmd and before that twrp
And yes i have tryed fastboot and all you write , even with one patched img from my fon and dig from in here It wont work
zagget said:
The bootloader is onlocked YES
Im not sure about the ADB i dont now how it works ? I use to flash my OnePlus fon with cmd and before that twrp
And yes i have tryed fastboot and all you write , even with one patched img from my fon and dig from in here It wont work
Click to expand...
Click to collapse
when in fastboot if you write fastboot device does it show the number I'd of your device?
Also under developer option I guess you have advance reboot turned on and USB debugging on.?
Hey
lil_kujo said:
when in fastboot if you write fastboot device does it show the number I'd of your device?
Also under developer option I guess you have advance reboot turned on and USB debugging on.?
Click to expand...
Click to collapse
Sorry for the late repley
it show my Fon in fast boot
And i have set all things in dev like you say
it still will no accept any installing ??
I have magisk made a boot.img with magisk and put in my pc , and still the fastboot do nothing ???
Sorry for me being such a fool and for all my Q
Maybe its better to reset the Fon and punt on the lataest firmware and start from the begining ?
zagget said:
Sorry for the late repley
it show my Fon in fast boot
And i have set all things in dev like you say
it still will no accept any installing ??
I have magisk made a boot.img with magisk and put in my pc , and still the fastboot do nothing ???
Sorry for me being such a fool and for all my Q
Maybe its better to reset the Fon and punt on the lataest firmware and start from the begining ?
Click to expand...
Click to collapse
Place the boot.img in the fastboot folder file. What I had to do since I had downloaded this fastboot zip but it was two in one, forgot the name but I had to put the boot.img into the file folder of fastboot so when I open adb or whatever it will detect the boot.img file.
As Yelloman said you do have to put the img file in the Fastboot folder in order for it to transfer the img to your device.
I have unlocked bootloader for my Oneplus 7t. Can someone guide me from here?
Thanks for your repleys both of you two guy and i got to work now . thansk for your Help
-X3RX3S- said:
I have unlocked bootloader for my Oneplus 7t. Can someone guide me from here?
Click to expand...
Click to collapse
There is a forum on xda about it or just read this one. You should head first to the original thread.
zagget said:
Im getting very frustrate sorry for this message if its to mush to ask for
i have Oneplus 7T
and the bootloader is unlocked
I installe the lateste update OS OxygenOS 10.0.8 (EU)
And what to root it with magisk and i cant flash it in anyway i try to with cmd
So i need some help to get it to work .anyone in here that have the time to send me a guide
there are so many and i cant get to work
So what i need is a easy guide that show me how to do it step by step
Click to expand...
Click to collapse
Did u fastboot oem unlock, or did you use a different method?
Hey i was attempted to install TWRP and got stuck in download mode boot loop. Fixed it by flashing stock firmware. I noticed a small error with my camera so i tried to lock bootloader again to see if that would fix the issue. But after flashing stock firmware a second time after locking the bootloader it didnt work and im stuck in download mode boot loop again. Only this time i dont get the option to unlock the bootloader and i cant enter the OS in order to enable OEM Unlock.
Here is the error screen: https://prnt.sc/q8vmG--mTHxY
Anyone know how to get out of this mess? Thanks
Am i doomed?
cheen11 said:
Hey i was attempted to install TWRP and got stuck in download mode boot loop. Fixed it by flashing stock firmware. I noticed a small error with my camera so i tried to lock bootloader again to see if that would fix the issue. But after flashing stock firmware a second time after locking the bootloader it didnt work and im stuck in download mode boot loop again. Only this time i dont get the option to unlock the bootloader and i cant enter the OS in order to enable OEM Unlock.
Here is the error screen: https://prnt.sc/q8vmG--mTHxY
Anyone know how to get out of this mess? Thanks
Click to expand...
Click to collapse
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
BlackMesa123 said:
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
Click to expand...
Click to collapse
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
cheen11 said:
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
Click to expand...
Click to collapse
Shouldn’t be a big deal unless there’s something Carrier specific required by your phone. Just make sure you don’t lock your bootloader again while using custom binaries or you might soft brick your device again. To bypass the camera lock you can use a SafetyNet fix module for Magisk which will spoof the bootloader status to the camera HAL
cheen11 said:
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
Click to expand...
Click to collapse
You can try also the NEE for Nordic Countries...
BlackMesa123 said:
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
Click to expand...
Click to collapse
Am i supposed to flash only AP or all of them? I have only ever flashed AP and worked without problems but after locking the bootloader i only get the above error boot loop.
cheen11 said:
Am i supposed to flash only AP or all of them? I have only ever flashed AP and worked without problems but after locking the bootloader i only get the above error boot loop.
Click to expand...
Click to collapse
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
BlackMesa123 said:
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
Click to expand...
Click to collapse
Ah, once choosing all the files it worked, thanks a bunch
BlackMesa123 said:
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
Click to expand...
Click to collapse
I dont know if im using the right files but i still get the same boot loop (https://prnt.sc/1lCk2FQEymPn) after adding twrp-3.7.0_12-2-a52sxq.img.tar to AP and vbmeta_disable.tar to USERDATA.
cheen11 said:
I dont know if im using the right files but i still get the same boot loop (https://prnt.sc/1lCk2FQEymPn) after adding twrp-3.7.0_12-2-a52sxq.img.tar to AP and vbmeta_disable.tar to USERDATA.
Click to expand...
Click to collapse
Are you flashing the patched vbmeta in the TWRP XDA thread or another one? Also the latest TWRP version is 3.7.0-3 so flash that one.
BlackMesa123 said:
Are you flashing the patched vbmeta in the TWRP XDA thread or another one? Also the latest TWRP version is 3.7.0-3 so flash that one.
Click to expand...
Click to collapse
Im using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-note10-lite-exynos.4350891/
I tried flashing that along with this: twrp-3.7.0_12-3-a52sxq.img.tar
But i still get the boot loop. Not sure if i can keep trying to re-flash these if the boot loop already happened
cheen11 said:
Im using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-note10-lite-exynos.4350891/
I tried flashing that along with this: twrp-3.7.0_12-3-a52sxq.img.tar
But i still get the boot loop. Not sure if i can keep trying to re-flash these if the boot loop already happened
Click to expand...
Click to collapse
You must use the patched vbmeta linked in the a52s TWRP thread, flash that one and you should boot fine in TWRP.
BlackMesa123 said:
You must use the patched vbmeta linked in the a52s TWRP thread, flash that one and you should boot fine in TWRP.
Click to expand...
Click to collapse
Hmm i tried using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-0-3-for-galaxy-a52s-5g.4488419/
But this time i got a fail with odin: https://prnt.sc/9HfVrQtC-gSO
cheen11 said:
Hmm i tried using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-0-3-for-galaxy-a52s-5g.4488419/
But this time i got a fail with odin: https://prnt.sc/9HfVrQtC-gSO
Click to expand...
Click to collapse
I think it has something to do with the space in “New folder” name, try to copy the TWRP tar in a path that has no spaces
BlackMesa123 said:
I think it has something to do with the space in “New folder” name, try to copy the TWRP tar in a path that has no spaces
Click to expand...
Click to collapse
Oh yeah good catch, i renamed the folder and didnt consider that it might not be updated it odin. It finally worked, thanks again for the help very much appreciated
Hmm i guess problems keep popping up. I guess its best that i just post here instead of creating a new thread. Im successfully in the TWRP UI but now i cant boot to system, it will just restart 2 times and then boot to TWRP. Also it fails to backup the boot image (with the error "Unable to mount storage") which i read in a tutorial that you were supposed to do.
cheen11 said:
Hmm i guess problems keep popping up. I guess its best that i just post here instead of creating a new thread. Im successfully in the TWRP UI but now i cant boot to system, it will just restart 2 times and then boot to TWRP. Also it fails to backup the boot image (with the error "Unable to mount storage") which i read in a tutorial that you were supposed to do.
Click to expand...
Click to collapse
As mentioned in the TWRP thread guide, you must format your data partition in TWRP in order to be able to boot back in the OS.
I found on another page here the CPH2451 patched A07 boot. I followed all the directions to the letter. I have done this on my OP8Pro many times. After flashing init_boot (fastboot flash init_boot patched.boot.img) I'm now in a bootloop. I reset first the didn't setup anything after update to A07. Any help would be appreciated.
Anyone have another boot.img that's patched or maybe the stock boot?
I'm waiting for this as well
have you tried changing your active slot to the other one and see if you can boot?
use fastboot to see which slot you are on, then set it as the other and reboot
this will get your current slot
Code:
fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.034s
set your active slot opposite of what you are currently on (slot b)
Code:
fastboot set_active a
if you are on b, set it to a
if you are on a, set it to b
give that a try and see if you can boot. you can revert it back it it doesnt help. worth a shot though.
shootind5nukes said:
I found on another page here the CPH2451 patched A07 boot. I followed all the directions to the letter. I have done this on my OP8Pro many times. After flashing init_boot (fastboot flash init_boot patched.boot.img) I'm now in a bootloop. I reset first the didn't setup anything after update to A07. Any help would be appreciated.
Anyone have another boot.img that's patched or maybe the stock boot?
Click to expand...
Click to collapse
You didn't by chance flash a patched boot.img to your init_boot partition did you? That could very well cause a soft brick. For rooting, you would need to patch init_boot and flash to init_boot.
Init_boot isn't the same as boot.
H4X0R46 said:
You didn't by chance flash a patched boot.img to your init_boot partition did you? That could very well cause a soft brick. For rooting, you would need to patch init_boot and flash to init_boot.
Init_boot isn't the same as boot.
Click to expand...
Click to collapse
I was very careful not to do that.
You flashed to boot not init_boot you need to reflash the boot.img to boot partition then boot your phone. Then you can go back and fastboot flash init_boot_a magisk_patched_init_boot.img
Then the same to init_boot_b do it to both slots you can extract the boot image with payload dumper and flash it to boot partition that should get you back running
shootind5nukes said:
I found on another page here the CPH2451 patched A07 boot. I followed all the directions to the letter. I have done this on my OP8Pro many times. After flashing init_boot (fastboot flash init_boot patched.boot.img) I'm now in a bootloop. I reset first the didn't setup anything after update to A07. Any help would be appreciated.
Anyone have another boot.img that's patched or maybe the stock boot?
Click to expand...
Click to collapse
shootind5nukes said:
I was very careful not to do that.
Click to expand...
Click to collapse
Both slots need to be flashed the init_boot read my post
shootind5nukes said:
I was very careful not to do that.
Click to expand...
Click to collapse
Somehow you screwed up the boot partition that's why it won't boot
str8str said:
You flashed to boot not init_boot you need to reflash the boot.img to boot partition then boot your phone. Then you can go back and fastboot flash init_boot_a magisk_patched_init_boot.img
Then the same to init_boot_b do it to both slots you can extract the boot image with payload dumper and flash it to boot partition that should get you back running
Click to expand...
Click to collapse
I assure you I did not flash to boot. I am the type that reads instructions 100 times. I know I must have did something wrong but it wasn't that.
https://www.droidwin.com/msm-download-tool-read-back-mode-create-oneplus-backup/
If you want to back up so you have all the bace files your phone will still connect to the MSM tool and you don't need to unlock the bootloader and you can extract every partition this way you can use the fast food tool to flash your phone this increases the recovery and boot image you don't need the payload.bin file
AkayamiShurui said:
https://www.droidwin.com/msm-download-tool-read-back-mode-create-oneplus-backup/
If you want to back up so you have all the bace files your phone will still connect to the MSM tool and you don't need to unlock the bootloader and you can extract every partition this way you can use the fast food tool to flash your phone this increases the recovery and boot image you don't need the payload.bin file
Click to expand...
Click to collapse
I forgot to mention this does work on bricked devices
Anybody with a corrupt boot.img that needs a factory one...
Does this one work ?
I would think it would work?
as it's a generic kernel image.
https://dl.google.com/android/gki/gki-certified-boot-android13-5.15-2023-02_r1.zip
shootind5nukes said:
I found on another page here the CPH2451 patched A07 boot. I followed all the directions to the letter. I have done this on my OP8Pro many times. After flashing init_boot (fastboot flash init_boot patched.boot.img) I'm now in a bootloop. I reset first the didn't setup anything after update to A07. Any help would be appreciated.
Anyone have another boot.img that's patched or maybe the stock boot?
Click to expand...
Click to collapse
Well if you trying to update to A.08 don't try flashing the boot.img I, I tried everything too and almost bricked my phone twice. if rooted you can't update with incremental updates in the USA ROM you only can do that with the EU ROM because they get a full ROM every time.
So I downloaded the EU ROM using oxygen updater App from play store then I used the OPLocalUpdate_For_Android12 App to force the update locally. The EU ROM looks the same to me so far but when we get a full ROM update in USA will switch back. Hope that helps