Database Develop

[A2017U][B20][B27] stock files and TWRP system backup

Here you can download stock files from the B20 and B27 firmwares for the A2017U (US variant), as well as TWRP backups. Included are:
TWRP system image (in its own folder)
unmodified byte-for-byte (DD) system image (system.img)
boot.img
recovery.img
aboot.img
bluetooth.bin
fbop.img
modem.bin
B20: https://mega.nz/#F!rcFCQZ7C!vn457hU1zDwc0uVpvm5otw (now includes stock image of B20 provided by ZTE for bootloader-unlocked users)
B27: https://mega.nz/#F!6YsTVZqC!7THrXFGOhIH_1eCgCnxqbA
NOTE: if you're currently on B20_Boot, it's highly recommended that you go back to B20 before attempting any sort of update from B20 to B27! Evidence suggests you may end up bricked if you don't!
Thanks to @tenfar for his tool (http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204) and to @DrakenFX for the ADB commands and the how-to for restoring stock (http://forum.xda-developers.com/axon-7/how-to/guides-info-info-a2017u-bootloader-t3440254).

Good to know!
Sent from my Nexus 6P using Tapatalk

I don't recommend unlocking the bootloader at this time since it breaks OTA. Once @tenfar gets his app to work with b20 locked we should be able to keep root after OTA eventually. Of course non of that matters once custom ROMs start coming.

Awesome work! Now we have something to fall back on in case something goes wrong.

KyJelly69 said:
I don't recommend unlocking the bootloader at this time since it breaks OTA. Once @tenfar gets his app to work with b20 locked we should be able to keep root after OTA eventually. Of course non of that matters once custom ROMs start coming.
Click to expand...
Click to collapse
Agreed.
I will say that a part of me thinks ZTE will release Nougat for the Axon 7 sooner than later. I don't have any hard evidence to support the idea, but some of the comments the mods have made over on the ZTE forums make me feel like there will be Nougat before there's another Marshmallow update for the US model. And I think they're going to try to get Nougat out ASAP (perhaps before the 2016 Nexus devices are announced).
It's all speculation, though.

rczrider said:
Agreed.
I will say that a part of me thinks ZTE will release Nougat for the Axon 7 sooner than later. I don't have any hard evidence to support the idea, but some of the comments the mods have made over on the ZTE forums make me feel like there will be Nougat before there's another Marshmallow update for the US model. And I think they're going to try to get Nougat out ASAP (perhaps before the 2016 Nexus devices are announced).
It's all speculation, though.
Click to expand...
Click to collapse
I feel the same way. I already unlocked my bootloader however. But I feel that, since I unlocked it without going through ZTE, I can lock it back and pull an Ota. If not, I'm sure nougat will be flushable through twrp some way, somehow
Sent from my ZTE A2017U using Tapatalk

osmosizzz said:
I feel the same way. I already unlocked my bootloader however. But I feel that, since I unlocked it without going through ZTE, I can lock it back and pull an Ota. If not, I'm sure nougat will be flushable through twrp some way, somehow
Click to expand...
Click to collapse
Is there anyone who has already re-locked bootloader successfully?

osmosizzz said:
I feel the same way. I already unlocked my bootloader however. But I feel that, since I unlocked it without going through ZTE, I can lock it back and pull an Ota. If not, I'm sure nougat will be flushable through twrp some way, somehow
Click to expand...
Click to collapse
Probably. I know that with some phones, the upgrade from LP to MM required a new bootloader (security). I'd be surprised if the upgrade from MM to Nougat would require a new bootloader, though.

Thank you for the files. Is the A2017UV1.o.oB20 folder available anywhere else than MegaPoop?

sorry, but i dont have the idea... my query is, can i install this on my zte axon 7 chinese variant (a2017)?

benlenspace said:
sorry, but i dont have the idea... my query is, can i install this on my zte axon 7 chinese variant (a2017)?
Click to expand...
Click to collapse
Short answer : NOP ,
the Chinese variant have FULL FACTORY IMAGES so you really don't need any of this. (you guys are lucky in that dept.)

Theoretically, could someone update from B20 to B20_Boot, unlock the bootloader, and then reflash the B20 fastboot, boot, recovery, and system to go back to complete stock B20 with an unlocked bootloader? This might allow people to get back on the OTA path while still maintaining an unlocked bootloader.

DrakenFX said:
Short answer : NOP ,
the Chinese variant have FULL FACTORY IMAGES so you really don't need any of this. (you guys are lucky in that dept.)
Click to expand...
Click to collapse
thanks for the reply... i wanted to install the US (2017u) rom in my chinese variant zte axon 7 because i wanted to activate "my voice" in English... that's the mean point...

rczrider said:
My gray came yesterday and so I used @tenfar's tool (http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204) to dump boot and recovery, then install TWRP and get a dump of system.
Click to expand...
Click to collapse
Dude you are my savior! Your system image worked on my Axon 7!! You saved my phone!
Can I pay you a beer or something? :highfive:
EDIT: WiFi is not working anymore

XblackdemonX said:
Dude you are my savior! Your system image worked on my Axon 7!! You saved my phone!
Can I pay you a beer or something? :highfive:
EDIT: WiFi is not working anymore
Click to expand...
Click to collapse
Do a Factory reset now that is sort of fresh install....
And check which update you are right now with the new system.?

DrakenFX said:
Do a Factory reset now that is sort of fresh install....
And check which update you are right now with the new system.?
Click to expand...
Click to collapse
Thank you but I did do a factory reset. I've read somewhere else that the WiFi issue is related to the modified boot.img

benlenspace said:
thanks for the reply... i wanted to install the US (2017u) rom in my chinese variant zte axon 7 because i wanted to activate "my voice" in English... that's the mean point...
Click to expand...
Click to collapse
What Language is your Default Language setting?
Cuz My Voice for what I can tell works base on Default Device Language Settings.
Meaning if your default is Chinese you need to change it to English.
Try mine from English to Spanish and works when I speak My Voice in spanish and I change it back to English.
XblackdemonX said:
Thank you but I did do a factory reset. I've read somewhere else that the WiFi issue is related to the modified boot.img
Click to expand...
Click to collapse
So you should try flashing OP boot.img and to a Factory reset after see if that works

DrakenFX said:
So you should try flashing OP boot.img and to a Factory reset after see if that works
Click to expand...
Click to collapse
I just tried that but it doesn't work. It gets stuck on the ZTE logo and doesn't move.
I've only managed to make to boot with the modified boot.img but then WiFi is dead :crying:

XblackdemonX said:
I just tried that but it doesn't work. It gets stuck on the ZTE logo and doesn't move.
I've only managed to make to boot with the modified boot.img but then WiFi is dead :crying:
Click to expand...
Click to collapse
OK, download this boot.img and try.....again,
https://www.androidfilehost.com/?fid=24671309938033033

DrakenFX said:
OK, download this boot.img and try.....again,
https://www.androidfilehost.com/?fid=24671309938033033
Click to expand...
Click to collapse
Same thing, stuck on the ZTE logo

Question Update Failling

Heya,
I magisked my S21 ultra and when i want to check for updates it says registration failed?
It did not do that before I magisked it.
So I need to restore everything to fix it or ?

you need to be specific on your concern what apps says registration failed? it's better to provided screenshot of your issue

Here is the screenshot
Sorry it took so long

caspaas said:
Here is the screenshot
Sorry it took so long
Click to expand...
Click to collapse
it is not recommend to update your OS directly from Setting while Magisk is installed ...your phone would go into bootloop(unusable state) there are also stories of people that are force to buy new device because of this silly mistake also installing OS update from Setting would uninstall Magisk also worse case scenario would lock your bootloader too which as your provably know it's nightmare
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io

You modify your system and expect samsung to push an update on your device? That won't work.

Riyal said:
You modify your system and expect samsung to push an update on your device? That won't work.
Click to expand...
Click to collapse
*laugh in Android 8 because i did not receive Android 9 update*

Riyal said:
You modify your system and expect samsung to push an update on your device? That won't work.
Click to expand...
Click to collapse
yeah sorry , had a Asus ROG 2 before this and it got OTA updates while rooted so.
New to samsung.

caspaas said:
Heya,
I magisked my S21 ultra and when i want to check for updates it says registration failed?
It did not do that before I magisked it.
So I need to restore everything to fix it or ?
Click to expand...
Click to collapse
yea you gotta restore everything in order to fix

Question I have ne2217. Help root and Global. Please!!!!

These threads have to many things going on, and now I am thoroughly confused. I just want to go to global from stock T-Mobile. I have downloaded so many things and I don't know what to use or not use. I have network unlocked and my bootloader is unlocked. I can enter fastboot and fastbootd.

Loustsoul said:
These threads have to many things going on, and now I am thoroughly confused. I just want to go to global from stock T-Mobile. I have downloaded so many things and I don't know what to use or not use. I have network unlocked and my bootloader is unlocked. I can enter fastboot and fastbootd.
Click to expand...
Click to collapse
There is no way to do it as of now. No one bothered making a conversion from T-Mobile to global with the 10 as there is no reliable MSM tool in case something were to go wrong in the conversion process. The most you can do on the T-Mobile version is unlock and root right now. I personally would love to be on global instead of T-Mobile firmware, but I doubt it will happen with the 10 Pro (although there is work being done on getting a useable MSM tool currently, so who knows).

jeffsga88 said:
There is no way to do it as of now. No one bothered making a conversion from T-Mobile to global with the 10 as there is no reliable MSM tool in case something were to go wrong in the conversion process. The most you can do on the T-Mobile version is unlock and root right now. I personally would love to be on global instead of T-Mobile firmware, but I doubt it will happen with the 10 Pro (although there is work being done on getting a useable MSM tool currently, so who knows).
Click to expand...
Click to collapse
All that'd take would be extracting your boot.img and flashing? Any issues with magisk?

Grin59 said:
All that'd take would be extracting your boot.img and flashing? Any issues with magisk?
Click to expand...
Click to collapse
For root? Just use the global patched boot.img and boot into OS, go to Magisk and perform a direct install. No issues at all with root on T-Mobile firmware. I've been rooted ever since they allowed us to unlock the bootloader and get our tokens.

Removed

EtherealRemnant said:
Really all you should need to do to convert to global is unlock the bootloader, take the NA downgrade package, and flash it with Fastboot Enhance. Make sure you go to the partitions screen and search for cow and delete every one of them so there is room for the image and if you get any other errors, don't continue. Once the flash is successful (the bar will seem to stop, just let it sit for a bit and it will continue), choose English on the phone screen and go through the menus to find where to wipe the phone and then reboot.
There is a risk of a brick if something goes wrong so without the MSM Tool, this is at your own risk, but Fastboot Enhance doesn't tend to brick phones like fastboot scripts do as long as you stop if it gives you an error.
Here is the NA downgrade package.
https://oxygenos.oneplus.net/2370_sign_NE2215_11_A_OTA_0130_all_bb1e47_10100001.zip
Click to expand...
Click to collapse
Yeah, technically should work. Unfortunately the risk is too high without having the MSM in case something goes wrong. Especially if it's your daily phone, like it is mine. But if anyone wants to give it a go, let us know how it goes, just know it could brick your phone and there's no current way to restore it without sending it to OnePlus or paying a scam artist to restore it.

Removed

Can I get my boot.img off of my phone or do I need to download it? Also the 10 pro is not listed in the software on the oneplus website. Where can I get the official stuff I need? Im happy with just root for now, I just want to use Magisk and do the updates......

EtherealRemnant said:
Fastboot Enhance really shouldn't brick. It's flashing the official downgrade package so unless OnePlus changed the hardware between the two significantly (which seems unlikely both because they haven't before other than minor changes like removing dual SIM and adding mmWave to the 9 Pro as well as the added cost of doing so), it should work fine. I made a tutorial for the OnePlus 9 using Fastboot Enhance to convert regions and nobody has reported a brick yet and this is after seeing 30+ bricks from people using fastboot scripts that prompted me to make the guide. Bricks with FBE happen if people ignore warnings about cow partitions or missing partitions and flash anyway. Like it doesn't even reboot the device after the flash is done so if the flash gets cut off in the middle, you just would need to flash the zip again before rebooting. Since all the flashing takes place in fastbootd from the start, it's possible to recover unlike regular flashing where it starts in fastboot and finishes in fastbootd so you're hosed if something goes wrong and you can't get back to fastboot.
I get it though, I wouldn't want to risk my device either. And I made sure to point out the brick risk, even if it's small, because I would never want to take that choice away from someone.
Click to expand...
Click to collapse
Im willing to try but I am too unsure of what to use as far as the correct boot and rom.... You seem to have way more knowledge than I and I would greatly appreciate your help.

Removed

EtherealRemnant said:
Fastboot Enhance really shouldn't brick. It's flashing the official downgrade package so unless OnePlus changed the hardware between the two significantly (which seems unlikely both because they haven't before other than minor changes like removing dual SIM and adding mmWave to the 9 Pro as well as the added cost of doing so), it should work fine. I made a tutorial for the OnePlus 9 using Fastboot Enhance to convert regions and nobody has reported a brick yet and this is after seeing 30+ bricks from people using fastboot scripts that prompted me to make the guide. Bricks with FBE happen if people ignore warnings about cow partitions or missing partitions and flash anyway. Like it doesn't even reboot the device after the flash is done so if the flash gets cut off in the middle, you just would need to flash the zip again before rebooting. Since all the flashing takes place in fastbootd from the start, it's possible to recover unlike regular flashing where it starts in fastboot and finishes in fastbootd so you're hosed if something goes wrong and you can't get back to fastboot.
I get it though, I wouldn't want to risk my device either. And I made sure to point out the brick risk, even if it's small, because I would never want to take that choice away from someone.
Click to expand...
Click to collapse
The only downside I could see then it's that we don't even have the full T-Mobile firmware to flash back to in case it starts to flash global but then failed. I'm tempted to take the plunge and try (would be nice to be on Android 13 now instead of waiting months for T-Mobile to get the update) but just don't want to end up bricking with no way to recover. Also, in the past I know people were using the MSM to convert to global or EU, does using the global downgrade script alone work for converting? I might take a look at your guide for the 9 series and try with the 10 pro. I guess I can always send it in if it does brick, still have my 9 pro I can use in case something goes wrong.

Removed

EtherealRemnant said:
It is a legitimate concern that you can't get back to T-Mobile firmware if something goes wrong and that is definitely something to think about.
I can tell you that the downgrade package is as close as you can get to the MSM Tool in terms of a restore without an MSM. I have used the downgrade packages to convert between regions on my 9 and never had any issues except for when I used the India MSM Tool for the 9 Pro on my 9 and kept losing touchscreen in OOS12. That was only fixed with an MSM Tool modded to get me back on regular global 9 firmware.
Click to expand...
Click to collapse
Well I'm taking the plunge so I'll update after if it's successful or not. Was able to delete all the COW partitions and start the flash no issue, so just have to wait for it to finish.

Removed

I will say this is my 2nd 10 pro because I did this exact method being described and it flashed rebooted all that but when trying to open any app I was greeted with a message that said.. "this app has been disabled due to security".

tman23 said:
I will say this is my 2nd 10 pro because I did this exact method being described and it flashed rebooted all that but when trying to open any app I was greeted with a message that said.. "this app has been disabled due to security".
Click to expand...
Click to collapse
Yeah, don't think it's going to work. Can't fully get out of the setup screen (or if you do it just stays at black screen only able to pull down quick settings and not enter options or anything). Wiped after flashing and won't work. I guess I could try using Fastboot Enhance to flash some of the global update zips and see if that does anything.

From what I've seen and read, switching regions on this phone is quite easy. You just need to use the full downgrade zip of that region and flash it basically. No messing around with FBE. NE2210/3/5/7 all share the same hardware, the full downgrade zips are actually interchangeable from what I've read/seen. There's only been one full zip for NE2217 released, IIRC, so the process to go back would involve a lot of upgrading incrementally. EDIT: I was wrong. There is no true full T-Mobile NE2217 ZiP available.. really sad.
But to go to/from NE2213 to/from NE2215, just take the downgrade zip, with a fully unlocked bootloader, and local update it.
Someone can correct if I'm wrong, but this seems to be the method most people have been using with success. That being said, as said above, root is very easily achievable by just BOOTing a patched global boot.img if you just want to root and maintain your original software.

Prant said:
From what I've seen and read, switching regions on this phone is quite easy. You just need to use the full downgrade zip of that region and flash it basically. No messing around with FBE. NE2210/3/5/7 all share the same hardware, the full downgrade zips are actually interchangeable from what I've read/seen. There's only been one full zip for NE2217 released, IIRC, so the process to go back would involve a lot of upgrading incrementally. But to go to/from NE2213 to/from NE2215, just take the downgrade zip, with a fully unlocked bootloader, and local update it.
Someone can correct if I'm wrong, but this seems to be the method most people have been using with success.
Click to expand...
Click to collapse
I haven't really heard of anyone converting the 10 due to lack of MSM. Also, haven't seen any full zips for the 2217 (T-Mobile version), so if you have a link to it that would be very useful. Also on 2217, you can't flash from in system as it's disabled in firmware (unless the separate apk works).

Stalk the forums enough, I think I've read every post here since I got the device back in March. There's a handful of people here successfully converted regions without any extra work. I believe there are actually 2 now for 2217. Here and here.
EDIT: As mentioned later in the thread even these are not full images for NE2217.

Prant said:
Stalk the forums enough, I think I've read every post here since I got the device back in March. There's a handful of people here successfully converted regions without any extra work. I believe there are actually 2 now for 2217. Here and here.
Click to expand...
Click to collapse
Thank you, not sure how I missed those. If my attempt to restore the device doesn't work I'll try restoring it by flashing T-Mobile firmware again.

Question Where are proximity, compass, auto brightness sensors stored in android 12 OOS?

As the title states, my auto brightness, compass and proximity sensors are all broken, I believe this is a failure of a partition similar to persist.img where the fingerprint used to be stored.
Had this issue a while back but I hadn't noticed the compass being broken
I've ran through the tests in engineer mode *#*#4636#*#* and the results are all null for the above sensors.
Factory wipe did nothing, moving between bases 12-13 did nothing, installing a GSI only affected only system.
I'd rather not RMA if I don't have to..
Any ideas anyone??

Have you tried installing lineage and then reverting back?
https://www.droidwin.com/how-to-install-lineageos-rom-on-oneplus-10-pro

g96818 said:
Have you tried installing lineage and then reverting back?
https://www.droidwin.com/how-to-install-lineageos-rom-on-oneplus-10-pro
Click to expand...
Click to collapse
That's a GSI buddy, yes I've installed them all.. but they only affect system so the issues will remain as the partitions that house the sensors aren't affected...
Similar thing happened on the 8 pro with the fingerprint, the perist partition was the culprit.
Have mentioned all this in the OP.

dladz said:
That's a GSI buddy, yes I've installed them all.. but they only affect system so the issues will remain as the partitions that house the sensors aren't affected...
Similar thing happened on the 8 pro with the fingerprint, the perist partition was the culprit.
Have mentioned all this in the OP.
Click to expand...
Click to collapse
i see. i'm not paying attention to any roms for this phone since there's no msm available to use without paying.
I haven't been followed this thread, but you could try flashing this fastboot rom. I'm not sure if anyone tested it, but the 9RT version worked great to convert COS to OOS without side effects.
OnePlus 10 Pro Fastboot ROMs (and how to make for any device)
First of all and most importantly, I want to say that this is not my work. This is a port of the work done by @abhinavgupta371 and @HELLBOY017 for the OP9RT. I merely made sure there weren't extra or missing files and edited the .bat and .sh...
forum.xda-developers.com
Here's the original post it was built from
[FASTBOOT][ROM][UNOFFICIAL][OP9RT] OxygenOS A.04-A.08 for MT2110 devices
Greetings, I've appreciated @abhinavgupta371, @HELLBOY017 for initial version of this firmware and @penguinus for continuous support and testing. PLEASE NOTE THAT FASTBOOT ROMS CAN ONLY BE USED IN DEVICES WITH AN UNLOCKED BOOTLOADER!!! AND BE...
forum.xda-developers.com

g96818 said:
i see. i'm not paying attention to any roms for this phone since there's no msm available to use without paying.
I haven't been followed this thread, but you could try flashing this fastboot rom. I'm not sure if anyone tested it, but the 9RT version worked great to convert COS to OOS without side effects.
OnePlus 10 Pro Fastboot ROMs (and how to make for any device)
First of all and most importantly, I want to say that this is not my work. This is a port of the work done by @abhinavgupta371 and @HELLBOY017 for the OP9RT. I merely made sure there weren't extra or missing files and edited the .bat and .sh...
forum.xda-developers.com
Here's the original post it was built from
[FASTBOOT][ROM][UNOFFICIAL][OP9RT] OxygenOS A.04-A.08 for MT2110 devices
Greetings, I've appreciated @abhinavgupta371, @HELLBOY017 for initial version of this firmware and @penguinus for continuous support and testing. PLEASE NOTE THAT FASTBOOT ROMS CAN ONLY BE USED IN DEVICES WITH AN UNLOCKED BOOTLOADER!!! AND BE...
forum.xda-developers.com
Click to expand...
Click to collapse
Have you used fastboot enhance to flash a rom?
AFAIK it's just a case of deleting the cows then extracting the payload then flashing it in fastbootd

I think the partition needs nuking then rebuilding.
On the 8 pro they used MSM, different ROMs and and fastboot, nothing worked.
Have you any idea where these sensors information is stored? What partition?

Anyone else have any idea?
Finding out where the proximity, compass and auto brightness sensor data is kept would help me

Answered my own question.
It is indeed within the persist partition.
How to Fix Android 10’s Sensors Bug Caused by Corrupted Persist Partition
A step-by-step guide on how to fix the Android 10 Sensors bug caused by corrupted Persist partition, on devices like Google Pixel, Xiaomi Mi A3, and others.
www.thecustomdroid.com

To fix this is need someone elses persist.img
Could someone extract theirs so i can use it please?
Theres nothing i can use in there i'm just using it as the files in mine are corrupt.
To pull it it's quite simple.
Connect your phone to your computer and open an ADB terminal then type the following
adb shell
Press enter and allow the prompt on your phone if you get one.
su
Press enter and allow the root prompt on your phone
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Press enter, this will put a file called persist.img on the root of your phone, it contains functional calibrated files for auto brightness, fp reader, proximity sensor and compass.
I'm not able to see your fingerprints or anything like that, its just going to be used to restore my device to a functional state.
Hope someone can help with this, anyone who's rooted can do this and it won't affect them.
Cheers
PS: if this works, then we'll have a fix for broken sensors if anyone should run into it, i'm happy to share mine once it's working

dladz said:
To fix this is need someone elses persist.img
Could someone extract theirs so i can use it please?
Theres nothing i can use in there i'm just using it as the files in mine are corrupt.
To pull it it's quite simple.
Connect your phone to your computer and open an ADB terminal then type the following
adb shell
Press enter and allow the prompt on your phone if you get one.
su
Press enter and allow the root prompt on your phone
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Press enter, this will put a file called persist.img on the root of your phone, it contains functional calibrated files for auto brightness, fp reader, proximity sensor and compass.
I'm not able to see your fingerprints or anything like that, its just going to be used to restore my device to a functional state.
Hope someone can help with this, anyone who's rooted can do this and it won't affect them.
Cheers
PS: if this works, then we'll have a fix for broken sensors if anyone should run into it, i'm happy to share mine once it's working
Click to expand...
Click to collapse
it doesn't seem like a file that gets updated during updates since it's not in the payload file. I can send you my vanilla persist.img from the moment i first rooted, but idk if 2215 and 2213 images are the same. AFH is giving me errors again with uploading. I'll PM you a google link instead.

g96818 said:
it doesn't seem like a file that gets updated during updates since it's not in the payload file. I can send you my vanilla persist.img from the moment i first rooted, but idk if 2215 and 2213 images are the same. AFH is giving me errors again with uploading. I'll PM you a google link instead.
Click to expand...
Click to collapse
I appreciate that mate, thank you.
I'm just updating to A_17
But you're right, it doesn't update it, i've just used fastboot enhance and flashed a payload from A_13, same issue.
It's so horrible man, missing these things isn't breaking the phone but it's really inconvenient.

dladz said:
I appreciate that mate, thank you.
I'm just updating to A_17
But you're right, it doesn't update it, i've just used fastboot enhance and flashed a payload from A_13, same issue.
It's so horrible man, missing these things isn't breaking the phone but it's really inconvenient.
Click to expand...
Click to collapse
yea it sucks, especially since oppo isn't releasing the msm tools.
hope the file works for you. it came out of my A.10 rom. hopefully A.10 shared more files than just the boot image.

It flashed and did affect the fingerprint but unfortunately didn't fix the other sensors.
Restored mine and my FP is working again but all other sensors are broken.
I think RMA is the only way at this point.

Just found this.
[Guide] About repairing/fixing the persist partition
Disclaimer: I am not responsible for the results of any of these operations. Everyone knows that the persist partition is responsible for sonsors and carrier network etc. Once this partition is failed or lost, your phone will go wrong. I just...
forum.xda-developers.com
Going to give this a whirl.. I reckon it could work.

dladz said:
Just found this.
[Guide] About repairing/fixing the persist partition
Disclaimer: I am not responsible for the results of any of these operations. Everyone knows that the persist partition is responsible for sonsors and carrier network etc. Once this partition is failed or lost, your phone will go wrong. I just...
forum.xda-developers.com
Going to give this a whirl.. I reckon it could work.
Click to expand...
Click to collapse
It didn't..

dladz said:
It didn't..
Click to expand...
Click to collapse
were you able to solve the problem?

crhistiandavidbonilla47 said:
were you able to solve the problem?
Click to expand...
Click to collapse
Nope...still can't use proximity, nor auto brightness, I'll send it back prior to the end of my contract, then sell it..but not until then.
I don't believe there is a fix for it.

dladz said:
Nope...still can't use proximity, nor auto brightness, I'll send it back prior to the end of my contract, then sell it..but not until then.
I don't believe there is a fix for it.
Click to expand...
Click to collapse
without a doubt my worst purchase was this device

crhistiandavidbonilla47 said:
without a doubt my worst purchase was this device
Click to expand...
Click to collapse
Haha, try to see the good, you live and you learn..
I've bought some stinkers, Nokia Lumia 800, note 4, Sony Z1, Huawei p20 pro, HTC Evo 3D.
You take the good with the bad.
You'll learn to avoid this problem in future, I'm sure you'll have another problem with a future phone and you'll learn from that too.
Just try to see the good.
Performance is unreal
Battery life is superb
Speakers are great.
Cameras are top notch.
We have root.
We have some mods
We have TWRP
Sure no ROMs but that could change (maybe)
Lot of updates.
RMA is solid.
For most people that above list is way more than enough.

dladz said:
Haha, try to see the good, you live and you learn..
I've bought some stinkers, Nokia Lumia 800, note 4, Sony Z1, Huawei p20 pro, HTC Evo 3D.
You take the good with the bad.
You'll learn to avoid this problem in future, I'm sure you'll have another problem with a future phone and you'll learn from that too.
Just try to see the good.
Performance is unreal
Battery life is superb
Speakers are great.
Cameras are top notch.
We have root.
We have some mods
We have TWRP
Sure no ROMs but that could change (maybe)
Lot of updates.
RMA is solid.
For most people that above list is way more than enough.
Click to expand...
Click to collapse
Yeah, you are right

Question April update?

How is Google so slow now at releasing things? They only have a few phones to update, my Samsung's are always start of each month without fail lol

Why you so eager that you can't wait a few days?

It's available now.

it has been up for about 5 hours

kevinireland11 said:
How is Google so slow now at releasing things? They only have a few phones to update, my Samsung's are always start of each month without fail lol
Click to expand...
Click to collapse
Layoffs, poor employee morale, and Google moving away from innovation and a move to deplete resources from projects/divisions that are not returning enough profit.

If you've ever had to deal with Google customer "service" for any technical issues before, you already know why. Sometimes you get lucky and find a unicorn of a tech to help, but it's usually an infuriating mess dealing with them.
But, to be honest, I'd rather have a delayed update than a rushed and buggy update. Quality control is important.

kevinireland11 said:
How is Google so slow now at releasing things? They only have a few phones to update, my Samsung's are always start of each month without fail lol
Click to expand...
Click to collapse
After all we are all just humans ... they sure have their reasons

I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?

JimSmith94 said:
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
Click to expand...
Click to collapse
No problems here.

JimSmith94 said:
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
Click to expand...
Click to collapse
Rooted, Kirisakura Kernel, Apr. update. All good here.

JimSmith94 said:
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
Click to expand...
Click to collapse
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it??? Please help me, thanks.
The mobile phone system is running normally.

LHui said:
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it???
The mobile phone system is running normally.
Click to expand...
Click to collapse
Assuming you're rooted, that message is normal and can be ignored.

JimSmith94 said:
Assuming you're rooted, that message is normal and can be ignored.
Click to expand...
Click to collapse
The red eio corruption message isn't normal, but it can be ignored. You may be thinking of the "Your bootloader is unlocked....." message.
LHui said:
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it??? Please help me, thanks.
The mobile phone system is running normally.
Click to expand...
Click to collapse
It usually takes an update to get rid of that message. Flashing back to an earlier month and then updating again should get rid of the message. You can also just ignore it until the next update.
Sometimes flashing an old boot image (your phone likely won't boot) and then flashing a newer boot image gets rid of that message as well.

JimSmith94 said:
Assuming you're rooted, that message is normal and can be ignored I am root and magisk on my device..
Click to expand...
Click to collapse

Lughnasadh said:
The red eio corruption message isn't normal, but it can be ignored. You may be thinking of the "Your bootloader is unlocked....." message.
It usually takes an update to get rid of that message. Flashing back to an earlier month and then updating again should get rid of the message. You can also just ignore it until the next update.
Sometimes flashing an old boot image (your phone likely won't boot) and then flashing a newer boot image gets rid of that message as well.
Click to expand...
Click to collapse
I refresh init_boot.img or prompt this message.

Can someone please explain to me....
On official site for factory images there is only one factory image for april update as far as I can see.
(TQ2A.230405.003.E1, Apr 2023)
Does the E1 on the end means that it's for specific carrier?
If it is, does it matter for us that have unlocked phones?

ozyk100 said:
Can someone please explain to me....
On official site for factory images there is only one factory image for april update as far as I can see.
(TQ2A.230405.003.E1, Apr 2023)
Does the E1 on the end means that it's for specific carrier?
If it is, does it matter for us that have unlocked phones?
Click to expand...
Click to collapse
No, the E1 does not mean that -- in the past, the ending of the version number can indicate something like that, but if there is no other monthly version, it's safe to say that is not the case. Linked below is a post on how the version numbers are determined and/or how to read them...
When there is no carrier specific version of firmware updates, it means the factory firmware image is applicable to all. If there is any specific version, it is identical in most ways, it just has special data/setup/applications(not apps or programs) that usually help the device's radio connect to the carrier's network optimally -- and from what I've read somewhere, all subsequent updates have said modifications included in them anyways. But if you're not certain, always flashing the "global" version is a safe bet; at worst, you're just not implementing the optimal "code" for the device's radio to the carriers network is all.
June 13, 2023 TQ3A.230605.012 Global - Platform-Tools v34.0.3 has a different bug- Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com

simplepinoi177 said:
No, the E1 does not mean that -- in the past, the ending of the version number can indicate something like that, but if there is no other monthly version, it's safe to say that is not the case. Linked below is a post on how the version numbers are determined and/or how to read them...
When there is no carrier specific version of firmware updates, it means the factory firmware image is applicable to all. If there is any specific version, it is identical in most ways, it just has special data/setup/applications(not apps or programs) that usually help the device's radio connect to the carrier's network optimally -- and from what I've read somewhere, all subsequent updates have said modifications included in them anyways. But if you're not certain, always flashing the "global" version is a safe bet; at worst, you're just not implementing the optimal "code" for the device's radio to the carriers network is all.
June 13, 2023 TQ3A.230605.012 Global - Platform-Tools v34.0.3 has a different bug- Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you very much for that explanation, I'll read up on it from the provided link.

LHui said:
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it??? Please help me, thanks.
The mobile phone system is running normally.
Click to expand...
Click to collapse
I had the same issue, but everything works normally without any issues. I regularly flash custom roms and factory images, so if you still want to fix this issue, restore a factory image using the Android flash tool.

Any info on whether the fingerprint scanner is being fixed or at east bettered with this?