Related
Hello,
I've been looking through this forum for quite a while, but I have yet to stumble upon a guide that can fix me up for taking the next step after the bootloader unlocking process. Yet, there's been lots of custom roms made for rmx2001. So here I'm with my unlocked rmx2001 or realme 6, wondering if I am missing out on something crucial for the next step because this is my first time doing something like this on a mediatek based phone. Kindly help me out pweese.. thank you;
Update:
I've dwelled deep into the forest, fought clones of sundar pichai, then finally.. successfully flashed my phone with custom recovery.
From what I've had read around this forum and other places, before flashing any custom recovery, the vbmeta.img must be flashed with a patched one, which as usual, there are rules one must follow to modify this certain android component.
This is the first for me, as per Android 8 (or Android 7 with its super confusing arb system took in place), any changes inside the recovery, system, etc are being handled by this vbmeta module.
It seems that vbmeta.img changes for every android or system update and to patch this vbmeta.img, the android version must be the same as what the patch corresponds to... (correct me if I'm wrong; this is my understanding based solely from what I have read, please take this with a big chunk of salt).
I currently have the b.57 update installed on my device, and I only found b.55 here on the next forum's page... the point is I have to wait for the latest patch of vbmeta b.57. Am I understanding this correctly, or am I just talking in elven language to myself? Anyway thank you for reading.
zero help, good for nothing advices. Search on other forums ,you Will get at least real help
cristianwcw said:
zero help, good for nothing advices. Search on other forums ,you Will get at least real help
Click to expand...
Click to collapse
lmao
ignoll said:
From what I've had read around this forum and other places, before flashing any custom recovery, the vbmeta.img must be flashed with a patched one, which as usual, there are rules one must follow to modify this certain android component.
This is the first for me, as per Android 8 (or Android 7 with its super confusing arb system took in place), any changes inside the recovery, system, etc are being handled by this vbmeta module.
It seems that vbmeta.img changes for every android or system update and to patch this vbmeta.img, the android version must be the same as what the patch corresponds to... (correct me if I'm wrong; this is my understanding based solely from what I have read, please take this with a big chunk of salt).
I currently have the b.57 update installed on my device, and I only found b.55 here on the next forum's page... the point is I have to wait for the latest patch of vbmeta b.57. Am I understanding this correctly, or am I just talking in elven language to myself? Anyway thank you for reading.
Click to expand...
Click to collapse
Hi fellow weeb I'm curious of how did you manage to flash custom recovery?
Lyco. said:
Hi fellow weeb I'm curious of how did you manage to flash custom recovery?
Click to expand...
Click to collapse
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
Do you a vbmeta.img for the latest patches b.59 or any guide to extract vbmeta, Just like you said the vbmeta corresponds with the patch.
Lyco. said:
Do you a vbmeta.img for the latest patches b.59 or any guide to extract vbmeta, Just like you said the vbmeta corresponds with the patch.
Click to expand...
Click to collapse
We can just use the vbmeta.img from stock ROM .ozip
Thanks
HemanthJabalpuri said:
We can just use the vbmeta.img from stock ROM .ozip
Thanks
Click to expand...
Click to collapse
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right? Or do you have a stock vbmeta?
Lyco. said:
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right?
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Is this the stock vbmeta? Or do anyone have any?
Lyco. said:
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right? Or do you have a stock vbmeta?
Click to expand...
Click to collapse
No, we don't need to modify anything to it.
--disable-verity and --disable-verification options to fastboot will patch it and flash automatically for you.
Also you can use vbmeta.img from any version of stock .ozip.
I am a Realme C12 user.
Thanks
HemanthJabalpuri said:
No, we don't need to modify anything to it.
--disable-verity and --disable-verification options to fastboot will patch it and flash automatically for you.
Also you can use vbmeta.img from any version of stock .ozip.
I am a Realme C12 user.
Thanks
Click to expand...
Click to collapse
Ok so what would I do if pbrp didn't showed up? And goes to bootloop, Do i just need to flash ofp and use realme flash tool?
I'm a new at flashing firmware so sorry about that
Lyco. said:
Ok so what would I do if pbrp didn't showed up? And goes to bootloop, Do i just need to flash ofp and use realme flash tool?
I'm a new at flashing firmware so sorry about that
Click to expand...
Click to collapse
Then flash stock recovery.
HemanthJabalpuri said:
Then flash stock recovery.
Click to expand...
Click to collapse
So after i flash the stock recovery should I flash the ozip there? And thanks for all the information.
I was trying to rootkit it, but on the last step I got locked in to a fastboot-loop, I eventually got out of it and was able to "install through ADB" through the OTA Oriole software.
Trying to rootkit it again, I messed up and got stuck on the same loop, but when I try to "install through ADB" the OTA file loads up 50% and I get the error "Current SPL 2021-11-05 Target SPL: 2021-10-05 this is considered a downgrade.
Denying SPL because it's SPL downgrade" and it aborts the installation.
Now whenever I try to boot, I get a "your phone is corrupted" message, I press power to continue, I get a message "your phone security is compromised" in orange, than I press power and it hangs on the Google logo on a white screen.
I can still get in to fastboot and all the options.
No idea what to try next.
If I took it to where I bought it, would they send it off to Google and they can fix it? Or do I have a brand new $1150 paperweight?
Thanks for any help.....
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
vbmeta needs to be flashed like this when u are going to want to root. If u already installed the ota there is a thread with the November vbmeta. I think it was on the 6 Pro forums.
sille said:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
vbmeta needs to be flashed like this when u are going to want to root. If u already installed the ota there is a thread with the November vbmeta. I think it was on the 6 Pro forums.
Click to expand...
Click to collapse
Where do I run this from, recovery mode? Do I need any new files?
Glitchedz said:
Where do I run this from, recovery mode? Do I need any new files?
Click to expand...
Click to collapse
In fastboot. As I said. Depends what version you are on. The Oct vbmeta is in the firmware files on the Google image webpage. The November one Is in the 6 pro forums
sille said:
In fastboot. As I said. Depends what version you are on. The Oct vbmeta is in the firmware files on the Google image webpage. The November one Is in the 6 pro forums
Click to expand...
Click to collapse
Sorry, I'm new to this. Do you mean that just have fastboot open on my phone, and type that command into cmd? And where do I put the vbmeta files? Do you have a link to the vbmeta files? I can't find any.
Really really appreciate any help, would love to save the phone.....
Glitchedz said:
Do you have a link to the vbmeta files? I can't find any.
Click to expand...
Click to collapse
Normally you can find the file vbmeta.img inside the "full stock ROM" archive for your phone.
Princip_Loskuta said:
Normally you can find the file vbmeta.img inside the "full stock ROM" archive for your phone.
Click to expand...
Click to collapse
Your reply is 8 months late, but if he didn't figure it out back then he will know now.
Hey sorry,
I have Pixel 6A.
adb shell ls -l /dev/block/by-name shows me that it has vbmeta_a AND vbmeta_b partition.
Would be this right?
fastboot flash boot_ab magisk_patched-[random_strings].img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-87413987
Most root-tutorials (except of Magisk-Homepage) for Pixel 6A doesn't even show anything about vbmeta-stuff.
ephemunch said:
Most root-tutorials (except of Magisk-Homepage) for Pixel 6A doesn't even show anything about vbmeta-stuff.
Click to expand...
Click to collapse
That is because, to the best of my knowledge, you no longer need to touch vbmeta in order to root.
So i rooted my Oneplus Nord 2 and got into a bootloop wiped the device using TWRP booted into rooted OS and wifi and bluetooth are not working. I dont have a backup of EFS partition.
Flash Boot image
Flash vbmeta.img
.\fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
or from twrp.
pankspoo said:
Flash Boot image
Click to expand...
Click to collapse
Didnt work
krugm0f0 said:
Flash vbmeta.img
.\fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
or from twrp.
Click to expand...
Click to collapse
Didnt work
Try flashing stock boot, then vbmeta. Restart phone, let it boot and see if it works.
If yes, reboot to bootloader again, and fastboot flash rooted boot image. My latest image attached. And then vbmeta. Reboot phone.
fellu4485 said:
Didnt work
Click to expand...
Click to collapse
You need to flash stock Boot image not rooted
pankspoo said:
You need to flash stock Boot image not rooted
Click to expand...
Click to collapse
I did
krugm0f0 said:
Try flashing stock boot, then vbmeta. Restart phone, let it boot and see if it works.
If yes, reboot to bootloader again, and fastboot flash rooted boot image. My latest image attached. And then vbmeta. Reboot phone.
Click to expand...
Click to collapse
I can't get WiFi and Bluetooth to work
This error is almost exclusively caused by having the wrong boot.img.
I know you already said you're certain you flashed the correct boot.img, but the fact your phone is showing these symptoms means you likely have the wrong boot.img, as is true in 99.999% of these cases.
The only other possible cause of these symptoms would be because you wiped or corrupted your persist partition.
The persist.img partition contains unique data calibrated to your own device which contains calibration specific to your phone's wifi and bluetooth module/antennas, if you wiped this partition by accident, you will need to find a backup of the persist.img taken from YOUR OWN DEVICE and reflash it, no one else on these forums will be able to provide these for you.
Again, I'll restate that the chances of the persist.img case being the cause here is almost unheard of unless you distinctly remember tampering with the persist image, which you would have had absolute ZERO reason to have done so.
I would highly recommend that you double, triple, and quadruple check you flashed the CORRECT boot.img before resorting to messing with your persist.img, it's likely your download source provided the wrong one, or you mixed up the files in your downloads folder which happens frequently.
just pulled this from my device. haven't patched it yet, but here's a stock august boot image. i used the pre-rooted lineageos rom and pulled the partition into an img file, i see someone just posted a guide in one of the threads without the boot image shared afterwards.. which kind of defeats the purpose for some people that are having a hard time accomplishing that.
edit: i am successfully rooted, but i have no radios. haven't looked into what the solution would be for that yet. i don't think it's been discussed other than that being a thing. share information here if you have any.
edit: link removed because i dissected the boot.img, and it indeed, is not an august boot img
how to manually pull boot.img
install dsu sideloader, install this GSI
enable developer settings, enable 'rooted debugging'
open up a terminal, and enter an adb shell to your device, and use this command
su
find /dev/block/platform -type d -name by-name
Click to expand...
Click to collapse
you will then take the destination it produces and input it into this command below respectively
ls -la /the/path/displayed/from/find
Click to expand...
Click to collapse
you will then have a list of all partitions. you will be shown the hardlink where it is pointed to. copy the device path for one of the boot partitions (/dev/block/sd**)
you then return to the storage folder of the phone using
cd /storage/emulated/0
Click to expand...
Click to collapse
then use dd to copy the partition into a boot.img
dd if=/path/to/boot/partition of=boot.img
Click to expand...
Click to collapse
pull the boot.img from device, reboot, install magisk, patch the boot.img and then flash it. reboot.
In the past we have had issues with cross flashing images from different security patches, causes no radios issue. Did you flash your vbmeta to disable verity and verification
? Check that your still on the right slot too, your active slot may have been changed when in fact your system is on the other slot, sometimes it will still boot this way but leftover partitions from your previous system build sometimes cause issues, sometimes the old modems don't get deleted during a system update and if the active slot gets changed it may still boot the system on the other slot with the old modems on the slot that's set to active. Flash vbmeta with disable verity and verification and make sure u flash vbmeta_a and vbmeta_b. Then if it still doesn't boot with radios working try setting active slot to the one that's not currently set to active and reboot. Just on off chance that it might be leftover modems from old system before u updated.
dmtec said:
just pulled this from my device. haven't patched it yet, but here's a stock august boot image. i used the pre-rooted lineageos rom and pulled the partition into an img file, i see someone just posted a guide in one of the threads without the boot image shared afterwards.. which kind of defeats the purpose for some people that are having a hard time accomplishing that.
edit: i am successfully rooted, but i have no radios. haven't looked into what the solution would be for that yet. i don't think it's been discussed other than that being a thing. share information here if you have any.
Upload files for free - augustboot.img - ufile.io
Download augustboot.img for free from ufile.io instantly, no signup required and no popup ads
ufile.io
Click to expand...
Click to collapse
And thank you for posting the August image. If you have the time please upload a super along with radios if you feel comfortable doing that, my other thread lists partitions to exclude from upload if you care to do that. Either way we appreciate what you've already posted. Would probably help others. I think u said ur device is NOT TMobile? Radios may or may not be carrier brand specific.
PsYk0n4uT said:
In the past we have had issues with cross flashing images from different security patches, causes no radios issue. Did you flash your vbmeta to disable verity and verification
? Check that your still on the right slot too, your active slot may have been changed when in fact your system is on the other slot, sometimes it will still boot this way but leftover partitions from your previous system build sometimes cause issues, sometimes the old modems don't get deleted during a system update and if the active slot gets changed it may still boot the system on the other slot with the old modems on the slot that's set to active. Flash vbmeta with disable verity and verification and make sure u flash vbmeta_a and vbmeta_b. Then if it still doesn't boot with radios working try setting active slot to the one that's not currently set to active and reboot. Just on off chance that it might be leftover modems from old system before u updated.
Click to expand...
Click to collapse
My device is MetroPCS so essentially T-Mobile. I would upload supers and radios if I had the bandwidth to do it, currently my only internet access is a bridged xfinitywifi connection. When i flashed my boot img back over, I had acknowledged that I was already on slot b and only flashed b. when i realized what happened i flashed the original back over to no avail. i'm gonna try flashing vbmeta back over with those parameters.
okay so keeping in mind i've never been able to boot from a no matter what, it just black screens. so, i went back and pulled my vbmeta, and flashed it back over to both slots. i flashed my patched boot to b. maybe i should flash both.. gonna try that next. but once i flashed my vbmeta back over with disable verity and disable verification, i was booting straight into recovery.
i then followed that by wiping userdata and i was able to boot again, this time the normal OOS boot screen followed instead of the carrier boot screen. still no radios though. when i pulled my boot image i stayed in a specific directory, and i haven't been able to download these large archives that have boot files in them because my download speed doesn't exceed 1MB/s at the moment. so i definitely didn't mix anything up.. it's a little mind boggling at the moment because all i did was send that patched boot image over and just that itself, caused the no radios problem.
Did you use your own vbmetas?
Try disabling verity and verification on all vbmetas....
vbmeta.img, vbmeta_system.img and vbmeta_vendor.img. You may or may not need to create a blank. I haven't had to so far but try these. You need each of these images to do it...:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
Check this out to explain a little more about the secure boot and how it works.
Secure boot flow | ConnectCore 8X
www.digi.com
Also check out this link for more on creating blank vbmetas https://android.stackexchange.com/q...-and-generation-of-vbmeta-image/224545#224545
PsYk0n4uT said:
Try disabling verity and verification on all vbmetas....
vbmeta.img, vbmeta_system.img and vbmeta_vendor.img. You may or may not need to create a blank. I haven't had to so far but try these. You need each of these images to do it...:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
Click to expand...
Click to collapse
that was exactly my next step it's funny you mentioned it here. still didn't work, so i dove a little deeper using this really handy tool and deconstructed the vbmeta's into json format. my current a/b vbmeta.img's had a security patch date of july, whereas when i got to my vbmeta_system_b file, i noticed that it had the correct date of august. so i just got done flashing the respective vbmeta over to all slots, and wiped userdata as it seems to require that each go around or else it will boot into recovery.
as oos loads up now i can see that i still have no radios, but this is inconclusive because the last thing i did before this the other day, was wipe both modem1 and modem2 in hopes that they would regenerate themselves possibly. not sure if that's the case so i will flash the backups back over now and report back if this actually helped solve the problem. if not i'm gonna manually edit the vbmeta and repack it if that's possible with/without needing keys in this scenario.
i was going to add the tags
"avb_vbmeta_image_flags_hashtree_disabled" 1,
"avb_vbmeta_image_flags_verification_disabled" 1,
Click to expand...
Click to collapse
prior to realizing that the security patch dates were off, so went with the minor effort first. this will be my next attempt if the the former doesn't work. thanks for the links, those actually helped a lot with understanding what's going on here.
upon trying to pack the vbmeta back together, it spits out an error that it doesn't know what those flags are and fails to compile. so for future reference, that won't work. so i edited just the fingerprint and patch date and flashed it to both slots. it's obvious here that the vbmeta and vbmeta_system are strikingly different, as the og vbmeta retains the keys for all partitions whereas the system one does not.
dmtec said:
just pulled this from my device. haven't patched it yet, but here's a stock august boot image. i used the pre-rooted lineageos rom and pulled the partition into an img file, i see someone just posted a guide in one of the threads without the boot image shared afterwards.. which kind of defeats the purpose for some people that are having a hard time accomplishing that.
edit: i am successfully rooted, but i have no radios. haven't looked into what the solution would be for that yet. i don't think it's been discussed other than that being a thing. share information here if you have any.
edit: link removed because i dissected the boot.img, and it indeed, is not an august boot img
Click to expand...
Click to collapse
and yes i posted a short how to in hopes that others could get an idea of how to root the device. i have posted the boot images for the previous patches but i dont have the time now to even sit and spend on updating so i dont have the boot image to share. do you mind if i link to your post in the other thread?
PsYk0n4uT said:
and yes i posted a short how to in hopes that others could get an idea of how to root the device. i have posted the boot images for the previous patches but i dont have the time now to even sit and spend on updating so i dont have the boot image to share. do you mind if i link to your post in the other thread?
Click to expand...
Click to collapse
my bad for the confusion, it was like right when I posted this someone other than you had posted a guide at the trail end of one of the threads.
you're welcome to share this anywhere, I don't mind. but what happened here is even though I was active in b this whole time, I think the newer boot img resided in a, and I made the mistake of only backing up b. it wasn't until I found the boot image editor tool that I was able to see that it wasn't an august boot image. so therefore I lost it.
im gonna open a second claim on my phone because the first one got stolen before I could get my unlock token, and this is probably just gonna be my development device for now. commandeering my wife's moto 5g stylus isn't gonna fair well for much longer lol.
until I can get an august boot img and vbmeta, this one is just gonna have to sit out for now.
dmtec said:
how to manually pull boot.img
install dsu sideloader, install this GSI
enable developer settings, enable 'rooted debugging'
open up a terminal, and enter an adb shell to your device, and use this command
you will then take the destination it produces and input it into this command below respectively
you will then have a list of all partitions. you will be shown the hardlink where it is pointed to. copy the device path for one of the boot partitions (/dev/block/sd**)
you then return to the storage folder of the phone using
then use dd to copy the partition into a boot.img
pull the boot.img from device, reboot, install magisk, patch the boot.img and then flash it. reboot.
Click to expand...
Click to collapse
when i click on the Gsi link it just starts downloading Lineage 19.1
dmtec said:
my bad for the confusion, it was like right when I posted this someone other than you had posted a guide at the trail end of one of the threads.
you're welcome to share this anywhere, I don't mind. but what happened here is even though I was active in b this whole time, I think the newer boot img resided in a, and I made the mistake of only backing up b. it wasn't until I found the boot image editor tool that I was able to see that it wasn't an august boot image. so therefore I lost it.
im gonna open a second claim on my phone because the first one got stolen before I could get my unlock token, and this is probably just gonna be my development device for now. commandeering my wife's moto 5g stylus isn't gonna fair well for much longer lol.
until I can get an august boot img and vbmeta, this one is just gonna have to sit out for now.
Click to expand...
Click to collapse
I think if you really want to get it going you could probably flash everything to may or July, the required images should be here on this forum.. that should get you to where you can update to August again
ScarletWizard said:
i started over and pulled the boot.img again and it fails to patch
i did dev/block/sde9 which is boot_a
View attachment 5768613
Click to expand...
Click to collapse
Have you tried going back to complete stock and then trying to tpull that boot.img and flashing with magisk? and then once the boot.img is patched and flashed, one thing that to tthis day i forget to do more trhan antyhing is to issue the following command at some piont before rebooting out of fastboot:
fastboot --disable-verity --disable-verification vbmeta vbmeta.img
Or are you having a hard time pulling your boot.img from the jump?/ wshich step is currently tripping you up?
ScarletWizard said:
i pulled the boot img but it fails during patching,
Click to expand...
Click to collapse
So it's failing while you're letting magisk patch it?
ScarletWizard said:
Yes that's what I said
Click to expand...
Click to collapse
so.. so have you n ot tried using a different version of magisk to patch said boot.img?
Look at you go.. right on man.. I'm telling you, some of the most important yet memorable experiences since getting into this **** was when i'd be left out to dsry but would eventually figure out whstever it was that was puzzling me.. looksl ike the same just happened with you. ;-)
ScarletWizard said:
untouched Boot partitions OCTOBER PATCHView attachment 5771677
Click to expand...
Click to collapse
This is the incremental ota and won't do most ppl much good. If u would please use payload dumper and dump the file u will see which partitions the ota updates and those are the partitions someone would have to pull from their updated device and upload in order for everyone to have access to the full. October firmware if you feel like sharing it with us
I flashed an image to my phone, and everything except wifi, bluetooth, and cellular are functional.
I've tried over a dozen methods now, and everything except the radios works just fine.
I've told by getdroidtips.com that I need these files:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
Click to expand...
Click to collapse
Does anyone happen to have these files? I don't have a backup of my phone, so I can't get them.
if you follow the guide I posted, youll be able to recover
All you need is the radios for the security patch you've flashed and reflash those. You didn't mention anything about the update your on. But there are radios for at least one security patch on here and you could get more help in the OnePlus Nord N20 telegram group
dmtec said:
if you follow the guide I posted, youll be able to recover
Click to expand...
Click to collapse
This guide? (https://forum.xda-developers.com/t/downgrading-restoring-to-may-and-rooting-without-a-hitch.4495801/)
Ive tried that with no luck whatsoever. It kept giving me weird errors
PsYk0n4uT said:
All you need is the radios for the security patch you've flashed and reflash those. You didn't mention anything about the update your on. But there are radios for at least one security patch on here and you could get more help in the OnePlus Nord N20 telegram group
Click to expand...
Click to collapse
I'm on 2022-05-05 running Android 11, build number CPH2459_11_A.05
i only have radios for gn2200, not cph2459.
is yours a carrier branded device?
im going to have to edit my posts to reflect the model my files are for since there seems to be another model out
PsYk0n4uT said:
i only have radios for gn2200, not cph2459.
is yours a carrier branded device?
im going to have to edit my posts to reflect the model my files are for since there seems to be another model out
Click to expand...
Click to collapse
Mine is not carrier branded, it's the unlocked model.
Here's your firmware
https://www.getdroidtips.com/oneplus-nord-2t-5g-firmware-flash-file-2/
Bro did you ever get this fixed I did the exact same thing I lost my radio then with my luck I ended up flashing the wrong opf file and to add the cherry on top I had my phone connected to a bad USB port. I moved my phone just enough to make it disconnect while it was flashing left my phone on a annoying boot loop .
Butttttt within a couple of days I got my one plus running like new and rooted. ALL thanks to a OnePlus guru here (ahh @dmtec instructions where spot on (just saw his comment haha he's the guru I'm talking about)) in xda.
If you need help restoring your phone let me know. I don't mind helping out.
Alfa-Q L83r said:
Bro did you ever get this fixed I did the exact same thing I lost my radio then with my luck I ended up flashing the wrong opf file and to add the cherry on top I had my phone connected to a bad USB port. I moved my phone just enough to make it disconnect while it was flashing left my phone on a annoying boot loop .
Butttttt within a couple of days I got my one plus running like new and rooted. ALL thanks to a OnePlus guru here (ahh @dmtec instructions where spot on (just saw his comment haha he's the guru I'm talking about)) in xda.
If you need help restoring your phone let me know. I don't mind helping out.
Click to expand...
Click to collapse
all you need to do is flash the modems that match your system and radios will work again even if other partitions dont match as long as it boots though u may have issues with fingerprint and stuff like that if other partitions arent all matching.....