It says I am fully up to date. No updates
proposed.
Probably based on android level and security update date
The vendor file looks to refer to 2023.05.09
when base for custom OS seems to be
Android TQ3A from 2023.09.01
and /e/OS itself refer to 2024.06.05
.
Which path would you suggest Piero next time its crashes?
Do you have an “original box” for the phone? Leaving aside the firmware for a moment, (if this was the choice) which of these physical variants do you think you have?
GM1910 is the Chinese variant OnePlus 7 Pro running HydrogenOS (with GM21 build tag)
GM1911: India
GM1917: Global/US Unlocked
GM1913: EU
GM1920: EU 5G
I do not have the box. I bought it second hand. I did an easyinstall e/os when I got the phone. It was on 1917 back then.
hmmm … the following favours GM1917: Global/US Unlocked
I think that the following ROM would be a good one for you to have in reserve.
Source: https://xdaforums.com/t/oneplus-7-pro-5g-rom-ota-oxygen-os-repo-of-oxygen-os-builds.3930585/
Navigation: Signed flashable zips > GM21AA Global and India > GM1917_11_H.41 (Global but India and EU, delivered to OOS 11 users): GM1917_11.H.41_4410_202303232056
MD5: 1ccb5dc4196b7979673ef1cf8338dd76
What's inside ?
$ md5sum 0aed83c2-3b6a-4c32-bfea-569f02f73f08.zip
1ccb5dc4196b7979673ef1cf8338dd76 0aed83c2-3b6a-4c32-bfea-569f02f73f08.zip
Regular unzip
0aed83c2-3b6a-4c32-bfea-569f02f73f08/META-INF/com/android/metadata
reads:
android_version=12
build_type=user
google_patch=20221205
oplus_hex_nv_id=A1
oplus_project_numbers=18815
os_version=V12.1
ota-id=OnePlus7ProOxygen_21.P.41_GLO_4410_2303232056
ota-property-files=payload_metadata.bin:2196:222497,payload.bin:2196:3335902388,payload_properties.txt:3335904642:354,metadata:69:918
ota-required-cache=0
ota-streaming-property-files=payload.bin:2196:3335902388,payload_properties.txt:3335904642:354,metadata:69:918
ota-type=AB
ota_version=OnePlus7ProOxygen_21.P.41_GLO_4410_2303232056
patch_type=1
post-build=OnePlus/OnePlus7Pro/OnePlus7Pro:12/SKQ1.211113.001/P.202303230244:user/release-keys
post-build-incremental=P.202303230244
post-sdk-level=31
post-security-patch-level=2022-12-05
post-timestamp=1679576657
pre-device=OnePlus7Pro
product_name=OnePlus7Pro
reserve-image-size=0
security_patch=2022-12-05
security_patch_vendor=2022-12-05
version_name=GM1911_11_H.41
wipe=0
payload-dumper-go produces
/extracted_20240815_073452
/extracted_20240815_073452$ ls -s
total 7935684
220 abl.img 98304 boot.img 56 devcfg.img 480 hyp.img 153868 modem.img 72 qupfw.img 3555332 system.img 1048580 vendor.img
200 aop.img 504 cmnlib64.img 65536 dsp.img 256 keymaster.img 78192 odm.img 2885432 reserve.img 3116 tz.img 124 xbl_config.img
860 bluetooth.img 388 cmnlib.img 24576 dtbo.img 14984 LOGO.img 1464 oem_stanvbk.img 24 storsec.img 8 vbmeta.img 3108 xbl.img
Reading list
According to this article from Oxygen Updater there may have been some mismatch in the final vendor update between variants. https://oxygenupdater.com/article/372/.
Indian 7-series had to receive H.38, or the “final-final-final” build as we call it. Other regions/devices aren’t supposed to receive anything beyond H.36/F.20. See also, Feb 2023, OxygenOS 12 H.38 for OnePlus 7/7 Pro [IN ONLY]
The article closes with a link to OxygenOS 12 MP3 for OnePlus 7/7 Pro.
This 2019 https://xdaforums.com/t/oneplus-7-pro-5g-rom-ota-oxygen-os-repo-of-oxygen-os-builds.3930585/ (already linked above) sets things out as follows:
Packages with build tag GM21AA are intended for the following variants:
GM1911: India
GM1917: Global/US Unlocked
Packages with build tag GM21BA are intended for the following variant:
GM1913: EU
GM1910 is the Chinese variant OnePlus 7 Pro running HydrogenOS (with GM21 build tag)
- Decide if you want to use GM21AA (does not fit with Europe, but you say yours is USA), this is what is linked above.
This article GM1917_11_H.41 now available is dated May 2023.
This article OnePlus 7 Series - A Circle dedicated to the OnePlus 7, 7 Pro, 7T and 7T Pro. has a number of articles dated April May 2023.
Edit, how come the punk Upgrade worked ?
/e/OS e-2.2-t-xxx-dev-guacamole appears to be a very well built ROM, seemingly with the components specified for firmware upgrade here https://wiki.lineageos.org/devices/guacamole/fw_update/.
What's inside /e/OS-t-guacamole ?
./payload-dumper-go e-2.2-t-20240717417775-dev-guacamole.zip
guacomole-test/e-2-2-t/extracted_20240815_083049$ ls
abl.img bluetooth.img cmnlib64.img devcfg.img dtbo.img keymaster.img modem.img storsec.img tz.img vendor.img xbl.img
aop.img boot.img cmnlib.img dsp.img hyp.img LOGO.img qupfw.img system.img vbmeta.img xbl_config.img
2 Likes
That is nice aibd, thank you very much. It is such a jungle with all the different possible versions. So I did indeed have 1917 originally. By which method do I install this type of file?
1 Like
PLEASE JUST READ THE PAGES LINKED !
RESULT OF HOURS OF RESEARCH MADE IN YOUR PLACE…
1 Like
Okay, you are right, I am sorry. To much on my head at the moment. Thank you very much for all the research and help. I totally appreciate that.
Did you manage to install it? I think I saw another topic in which you have 1.22 T.
Morning Cooler, I installed e/ 2.2 directly using sideload method. I already installed all apps ect when I got the information from piero and aibd. I was trying to discover how to do a brand new install starting from Android 11 upgrading to 12, and then install e/os. I have now the proper routine thanks to the both of them.
I will do that next time my phone gives me trouble but for now I will leave my punk install 
for what it is. When it runs, it runs and I am happy.
Thank you eosfan for your response.
Can you please let me know if everything works good (especially all cameras?
I might install it soon and would like some measurement.
Yep everything has been working fine for the last week. Did not encounter any errors yet.
Good Luck!
Which Recovery do you have running now? I assume “stock” /e/OS (Lineage)?
It says E recovery version 2.2
This topic was automatically closed after 35 days. New replies are no longer allowed.