If we're going to start messing around, we really need to start specifying 10.0.0.13 and 10.0.0.16 and putting together an organized repo of partitions.
https://drive.google.com/open?id=1J5_igi3ekdHM-nXT72wKyfHK9pxfI0gcIs it possible for someone to pull all these partitions?
aop.img
bluetooth.img
boot.img
dsp.img
dtbo.img
LOGO.img
modem.img
oem_stanvbk.img
qupfw.img
storsec.img
multiimgoem.img
uefisecapp.img
recovery.img
vbmeta.img
vbmeta_system.img
opproduct.img
system.img
vendor.img
product.img
The super.img method isn't working for me
I'm still confused as to how the super partition factors in and what it will take to get a backup of 10.0.0.16 and put it on slot a. Manually? Is that even desirable?
Worked perfectly!!! I can't thank you enough! The only issue is logo.img(a&b) failed. My fingerprint scanner won't register a fingerprint for some reason?@ntzrmtthihu777 said it took them back to that. I don't know why it worked for them, because that super.img only has data on system_a. I'm on slot b and on the November 1, 2019 Android security patch level. I'm still waiting to see if it worked for @DanDroidOS.
Worked perfectly!!! I can't thank you enough! The only issue is logo.img(a&b) failed. My fingerprint scanner won't register a fingerprint for some reason?
I'm trying again, don't see why my fingerprint won't register? Thanks for all your help!@DanDroidOS , I uploaded a fix for the LOGO_a.img and LOGO_b.img; it was just case sensitivity. If the images are renamed with LOGO capital letters:
fastboot flash LOGO_a LOGO_a.img
fastboot flash LOGO_b LOGO_b.img
But, since you've already downloaded and if you don't rename the lower case logo to LOGO, you could type:
fastboot flash LOGO_a logo_a.img
fastboot flash LOGO_b logo_b.img
Maybe this quote from this thread at https://forums.oneplus.com/threads/oneplus-7-pro-fingerprint-scanner-not-working-properly.1043768/ would work:I'm trying again, don't see why my fingerprint won't register? Thanks for all your help!
UPDATE: Still no fingerprint? Everything else perfect 10.0.16!
UPDATE #2: I dialed *#808# and ran fingerprint tests and all passed. Still can't register a fingerprint.
Thank you but sadly I have tried that I also tried switching to guest mode to try and register a fingerprint and even booted up in safe mode still nothingMaybe this quote from this thread at https://forums.oneplus.com/threads/oneplus-7-pro-fingerprint-scanner-not-working-properly.1043768/ would work:
"first remove all the stored fingers, then clear the cache in recovery (see below for how), then try re-registering. Make sure when you do that your fingers are clean and dry. If still fails, try registering someone else's finger as a test.
Boot the phone into recovery mode and clear the cache.
1. Power off phone.
2. Power on phone whilst holding down the volume down button (this takes slightly longer to react than you would expect and after the initial splash screen goes blank for a slightly un-nerving amount of time. But just wait).
3. Enter the PIN/Password you use to unlock the phone when prompted.
4. Choose a language.
5. Choose "Wipe data and cache" (don't worry this is only a path to a submenu, it won't delete your data).
6. Choose "Wipe cache" (IMPORTANT - MAKE SURE YOU DON'T TAP ERASE EVERYTHING).
7. It will confirm that you have selected clear cache and ask you to say YES.
8. When it says success choose "Reboot""
Thank you but sadly I have tried that I also tried switching to guest mode to try and register a fingerprint and even booted up in safe mode still nothing
https://drive.google.com/open?id=1J5_igi3ekdHM-nXT72wKyfHK9pxfI0gcIs it possible for someone to pull all these partitions?
aop.img
bluetooth.img
boot.img
dsp.img
dtbo.img
LOGO.img
modem.img
oem_stanvbk.img
qupfw.img
storsec.img
multiimgoem.img
uefisecapp.img
recovery.img
vbmeta.img
vbmeta_system.img
opproduct.img
system.img
vendor.img
product.img
The super.img method isn't working for me
I also asked OnePlus https://www.oneplus.com/support/contact for a MSM image for the OnePlus 7T Pro 5G McLaren, since it's critical for safe development. In my case, they did not say no, they just gave me a boilerplate response of, "About your concern we would like to inform you that we will take this as feedback and pass it along to our developer team so that this update can be rectified in the upcoming updates in the near future." They emailed me again asking for a further response and I haven't replied yet, because that second email was more obviously automated and did not have a name like the first one did. I think they could possibly let a tech post it to XDA, etc., if convinced by someone with experience like a XDA Recognized Developer.
I would like to create a hybrid super.img with Global 7T Pro img & 5G 7T Pro img. (maybe keeping modem/vendor/kernel from 5G) It should be possible.
I can't compile lpunpack. (Ubuntu 18.10) Still can't extract super.img for individual images... and what about repack? (in order to create hybrid super.img)
Has anyone been able to get that super.img extracted?
I get this error every time!
eosdev@eosdev-ubuntu:~/Firmware_extractor$ ./extractor.sh firmware.zip
Create Temp and out dir
Extracting firmware on: /home/eosdev/Firmware_extractor/out
./extractor.sh: line 168: gawk: command not found
./extractor.sh: line 207: gawk: command not found
As much as I love(d) arch (currently a gentooist) thats the exact type of distro
that binaries floating around the web are not going to work for forever. You
can build your own lpunpack, which will definitely work on your system, but
I don't know how to do that outside of using the lineageos/etc build tree
yet, however.
In my case, I just want a clean hybrid img in order to activate the dual sim function. That's all I want, the TMO firmware is perfectly fine... (and replace boot/shutdown animations with original McLaren bootanimations) This super.img pull procedure and the ability to push/restore it back is a huge step forward for our McLaren 5G. At least there is a bit of light the end of the tunnel. (even without the damn MSM Tool)
@ntzrmtthihu777 Can you post the super.img extracted... at least that way we can flash images individually. (and test replacing/swapping images)
Also... you do have a 7T Pro too? lol... You have the full kit required... lol (we also need the 7T Pro images... lol)
Just renamed the super.zip to firmware.zip. Installed gawk and still nothing, no error but empty output folder
tekhd@TEKHDX:~/Desktop/oneplus/Firmware_extractor-master/tools/Linux/bin$ ./lpunpack super.img
sudo -i
apt install unace unrar zip unzip p7zip-full p7zip-rar sharutils rar uudeview mpack arj cabextract file-roller
apt install liblzma-dev python-pip brotli lz4
pip install backports.lzma protobuf pycrypto
apt install gawk