HD1925 OnePlus 7t Pro McLaren 5g - Crowdsourced Data Request.

Search This thread

ntzrmtthihu777

Senior Member
May 17, 2015
126
73
ntzrmtthihu777 said:
So, I've been doing some work on getting LineageOS to work on this device. No idea as of right now
if it will work on any other carrier variants (I think they don't allow for bootloader unlocking?).

Currently everything 'works' (some is buggy but that may be more to do with the fact that 17.1 is not
currently finished) with the exception of two things I've tested/noticed (other stuff may be broken
but I've not seen them yet): audio in calls (I can make/take calls but I can't hear or be heard. Audio
works as I can play music in the LineageOS music app and record/playback the recording in the app)
and the fingerprint sensor (pretty sure I'm just missing some part from the stock ROM).

What I'm asking is that all owners of stock (unlocked/rooted is probably fine, custom kernels prob
not) collect some logs for me during specific activities so I can determine what is missing and maybe
produce a rom for you guys to test out without losing some features.

I'd like three things:
1. Follow the instructions here and upload the oem_log folder to somewhere and share it.
2. A logcat of boot up through making a phone call and hang up. To take this, you'll need
developer mode and adb debugging enabled on the phone and the platform tools (adb
primarily) set up for your operating system. From either cmd.exe (windows) or Terminal.app (OSX)
or your preferred terminal emulator (Linux, too many options to list them all), enter this command:
Code:
adb logcat > logcat.call.log
Then, power your phone off, hook it up via USB to the machine, power it on, place the call,
say a few words, hang up. Then press ctrl+c in the cmd/terminal/whatever window to
end the logging session.
3. A logcat of boot up through enrolling a fingerprint in the phone and unlocking via
the fingerprint. Same procedure, but the command is:
Code:
adb logcat > logcat.finger.log

Optionally, for those with rooted phones, I'd like these logs as well:
4. A dmesg during boot up through making a call and hangup. Same procedure as #2, but the
command is
Code:
adb shell su -c dmesg > dmesg.call.log
5. A dmesg during boot up through enrolling a fingerprint in the phone and unlocking
via the fingerprint. Same procedure as #3 but the command is
Code:
adb shell su -c dmesg > dmesg.finger.log

The files gathered from #2-5 will be in the current directory you executed the logcat command
from. On windows it will say this right before where you type the command, and on OSX/Linux
this will probably be in your home directory, unless you changed the directory first. I expect OSX
or Linux users to be a bit more savvy about this already.

The files may contain unique data to your phone (serial number, IMEI, other things) but android
filters out all but the last two numbers of the phone you are calling, so its generally ok. However,
I do not suggest posting links to these files here, but you can message me them directly here.
If/when you do this, please make note of the exact model number of your phone (not sure if
all 5g phones are HD1925 or not), current firmware version, and baseband version. These can
all be found in settings->about phone or so.
Hopefully we can get all this sorted out before too long and have working lineage builds quickly.
Thanks in advance and happy hacking!
 
Last edited:

champ784

Senior Member
May 31, 2013
421
153
Richmond
Nexus 9
Google Pixel 3a
So, I've been doing some work on getting LineageOS to work on this device. No idea as of right now
if it will work on any other carrier variants (I think they don't allow for bootloader unlocking?).

Currently everything 'works' (some is buggy but that may be more to do with the fact that 17.1 is not
currently finished) with the exception of two things I've tested/noticed (other stuff may be broken
but I've not seen them yet): audio in calls (I can make/take calls but I can't hear or be heard. Audio
works as I can play music in the LineageOS music app and record/playback the recording in the app)
and the fingerprint sensor (pretty sure I'm just missing some part from the stock ROM).

What I'm asking is that all owners of stock (unlocked/rooted is probably fine, custom kernels prob
not) collect some logs for me during specific activities so I can determine what is missing and maybe
produce a rom for you guys to test out without losing some features.

I'd like three things:
1. Follow the instructions here and upload the oem_log folder to somewhere and share it.
2. A logcat of boot up through making a phone call and hang up. To take this, you'll need
developer mode and adb debugging enabled on the phone and the platform tools (adb
primarily) set up for your operating system. From either cmd.exe (windows) or Terminal.app (OSX)
or your preferred terminal emulator (Linux, too many options to list them all), enter this command:

Then, power your phone off, hook it up via USB to the machine, power it on, place the call,
say a few words, hang up. Then press ctrl+c in the cmd/terminal/whatever window to
end the logging session.
3. A logcat of boot up through enrolling a fingerprint in the phone and unlocking via
the fingerprint. Same procedure, but the command is:


Optionally, for those with rooted phones, I'd like these logs as well:
4. A dmesg during boot up through making a call and hangup. Same procedure as #2, but the
command is

5. A dmesg during boot up through enrolling a fingerprint in the phone and unlocking
via the fingerprint. Same procedure as #3 but the command is


The files gathered from #2-5 will be in the current directory you executed the logcat command
from. On windows it will say this right before where you type the command, and on OSX/Linux
this will probably be in your home directory, unless you changed the directory first. I expect OSX
or Linux users to be a bit more savvy about this already.

The files may contain unique data to your phone (serial number, IMEI, other things) but android
filters out all but the last two numbers of the phone you are calling, so its generally ok. However,
I do not suggest posting links to these files here, but you can message me them directly here.
If/when you do this, please make note of the exact model number of your phone (not sure if
all 5g phones are HD1925 or not), current firmware version, and baseband version. These can
all be found in settings->about phone or so.

Hopefully we can get all this sorted out before too long and have official lineage builds quickly.
Thanks in advance and happy hacking!
If I can get my hands on my laptop, I'll see if I can help out with this. Will PM you if I can manage it!
 

twinnfamous

Senior Member
May 31, 2012
1,252
702
sacramento

Open up msm tool and press f8 when the screen pops up use crtl+a to select all partitions the PW is oneplus then ok . Then press readback button .Power off phone and connect phone while holding both volume buttons to USB keep holding the buttons till it shows it's connected and readback will start and you should have all img files and bin files in C/
 

ntzrmtthihu777

Senior Member
May 17, 2015
126
73
Open up msm tool and press f8 when the screen pops up use crtl+a to select all partitions the PW is oneplus then ok . Then press readback button .Power off phone and connect phone while holding both volume buttons to USB keep holding the buttons till it shows it's connected and readback will start and you should have all img files and bin files in C/

This would require the MSM tool specific to this device, would it not? If it doesn't, man, I need to get some folks
to do this.
 

twinnfamous

Senior Member
May 31, 2012
1,252
702
sacramento
This would require the MSM tool specific to this device, would it not? If it doesn't, man, I need to get some folks
to do this.

I've done it. But my bootloader is not unlocked and the OnePlus website says my IMEI is invalid. Use msm tool found in this forum. I used the one from my op7pro. This is something alot should have tried just from owning previous oneplus devices
 
  • Like
Reactions: omariscal1019

kirschdog1

Senior Member
Open up msm tool and press f8 when the screen pops up use crtl+a to select all partitions the PW is oneplus then ok . Then press readback button .Power off phone and connect phone while holding both volume buttons to USB keep holding the buttons till it shows it's connected and readback will start and you should have all img files and bin files in C/
There is no msm tool for the 5g McLaren... ?
 

a63548

Senior Member
Apr 6, 2009
375
336
@ntzrmtthihu777 Thank you very much for continuing to work on developing for this phone! :) Just sent you a PM with the logcats for the calls and fingerprint, oem_log, and screenshots of phone information.

Please let me know if there is more I can help with
 

ntzrmtthihu777

Senior Member
May 17, 2015
126
73
@ntzrmtthihu777 Thank you very much for continuing to work on developing for this phone! :) Just sent you a PM with the logcats for the calls and fingerprint, oem_log, and screenshots of phone information.

Please let me know if there is more I can help with
Is it within your wheelhouse to try the readback the previous poster in this thread mentioned?
Shouldn't require the bootloader unlock, and you'd have the most virgin dump to provide to the
rest of us for the moment.
 

DanDroidOS

Senior Member
Jul 26, 2009
449
103
Southern California
dandroidos.com
Open up msm tool and press f8 when the screen pops up use crtl+a to select all partitions the PW is oneplus then ok . Then press readback button .Power off phone and connect phone while holding both volume buttons to USB keep holding the buttons till it shows it's connected and readback will start and you should have all img files and bin files in C/
The MSM tool is asking for a password?

Edit: Nevermind the password is oneplus:)
 
Last edited:

a63548

Senior Member
Apr 6, 2009
375
336
Is it within your wheelhouse to try the readback the previous poster in this thread mentioned?
Shouldn't require the bootloader unlock, and you'd have the most virgin dump to provide to the
rest of us for the moment.

Reading back the files as I type :) Are there any files/partitions I should keep out of the archive I will be uploading for here? I selected all of them, but for safety would prefer to leave out any that might not be good to put online.

Edit: Completed! :)

Total uncompressed size 19GB (mainly due to super.img) Compressed size is 3.9GB. Sending you a link through PM.

K4F3Yig.jpg


Code:
01/16/2020  03:43 AM    <DIR>          .
01/16/2020  03:43 AM    <DIR>          ..
01/16/2020  03:38 AM         8,388,608 abl.elf
01/16/2020  03:38 AM        67,108,864 aging.bin
01/16/2020  03:38 AM        33,554,432 aging_mod.bin
01/16/2020  03:38 AM           106,496 ALIGN_TO_128K_1.bin
01/16/2020  03:39 AM           106,496 ALIGN_TO_128K_2.bin
01/16/2020  03:38 AM           524,288 aop.mbn
01/16/2020  03:39 AM           262,144 apdp.mbn
01/16/2020  03:38 AM       100,663,296 boot.img
01/16/2020  03:38 AM         1,048,576 BTFM.bin
01/16/2020  03:39 AM         1,048,576 catecontentfv.bin
01/16/2020  03:39 AM           524,288 catefv.bin
01/16/2020  03:39 AM         2,097,152 cateloader.bin
01/16/2020  03:38 AM           131,072 cdt.bin
01/16/2020  03:38 AM           524,288 cmnlib.mbn
01/16/2020  03:38 AM           524,288 cmnlib64.mbn
01/16/2020  03:30 AM           524,288 config.bin
01/16/2020  03:38 AM       178,257,920 core_nhlos.bin
01/16/2020  03:38 AM         1,048,576 ddr.bin
01/16/2020  03:38 AM           131,072 devcfg.mbn
01/16/2020  03:39 AM             4,096 devinfo.bin
01/16/2020  03:39 AM         1,048,576 dip.bin
01/16/2020  03:38 AM        67,108,864 dspso.bin
01/16/2020  03:38 AM        25,165,824 dtbo.img
01/16/2020  03:30 AM        10,485,760 dynamic_nvbk.bin
01/16/2020  03:29 AM           524,288 frp.bin
01/16/2020  03:39 AM           131,072 fsc.bin
01/16/2020  03:39 AM         2,097,152 fsg.bin
01/16/2020  03:38 AM         2,097,152 fw_ufs1.bin
01/16/2020  03:38 AM         2,097,152 fw_ufs2.bin
01/16/2020  03:38 AM         2,097,152 fw_ufs3_a.bin
01/16/2020  03:38 AM         2,097,152 fw_ufs3_b.bin
01/16/2020  03:38 AM         2,097,152 fw_ufs4_a.bin
01/16/2020  03:38 AM         2,097,152 fw_ufs4_b.bin
01/16/2020  03:38 AM         2,097,152 fw_ufs5_a.bin
01/16/2020  03:38 AM         2,097,152 fw_ufs5_b.bin
01/16/2020  03:38 AM            20,480 gpt_backup0.bin
01/16/2020  03:38 AM            20,480 gpt_backup1.bin
01/16/2020  03:38 AM            20,480 gpt_backup2.bin
01/16/2020  03:38 AM            20,480 gpt_backup3.bin
01/16/2020  03:39 AM            20,480 gpt_backup4.bin
01/16/2020  03:39 AM            20,480 gpt_backup5.bin
01/16/2020  03:38 AM            24,576 gpt_main0.bin
01/16/2020  03:38 AM            24,576 gpt_main1.bin
01/16/2020  03:38 AM            24,576 gpt_main2.bin
01/16/2020  03:38 AM            24,576 gpt_main3.bin
01/16/2020  03:39 AM            24,576 gpt_main4.bin
01/16/2020  03:39 AM            24,576 gpt_main5.bin
01/16/2020  03:38 AM         8,388,608 hyp.mbn
01/16/2020  03:38 AM         2,097,152 imagefv.elf
01/16/2020  03:29 AM           524,288 keystore.bin
01/16/2020  03:38 AM           524,288 km4.mbn
01/16/2020  03:39 AM             4,096 limits.bin
01/16/2020  03:39 AM        67,108,864 logdump.bin
01/16/2020  03:39 AM         8,388,608 logfs_ufs_8mb.bin
01/16/2020  03:38 AM        16,777,216 logo.bin
01/16/2020  03:39 AM         1,048,576 mdm1m9kefs1.bin
01/16/2020  03:39 AM         1,048,576 mdm1m9kefs2.bin
01/16/2020  03:39 AM         1,048,576 mdm1m9kefs3.bin
01/16/2020  03:39 AM             4,096 mdm1m9kefsc.bin
01/16/2020  03:39 AM         1,048,576 mdm1oemnvbktmp.bin
01/16/2020  03:38 AM         1,048,576 mdmddr.bin
01/16/2020  03:30 AM         1,048,576 mdm_oem_dycnvbk.bin
01/16/2020  03:30 AM         1,048,576 mdm_oem_stanvbk.bin
01/16/2020  03:38 AM         4,194,304 mdtpsecapp_a.bin
01/16/2020  03:38 AM         4,194,304 mdtpsecapp_b.bin
01/16/2020  03:38 AM        33,554,432 mdtp_a.bin
01/16/2020  03:38 AM        33,554,432 mdtp_b.bin
01/16/2020  03:38 AM        16,777,216 metadata.img
01/16/2020  03:29 AM         1,048,576 misc.bin
01/16/2020  03:39 AM         2,097,152 modemst1.bin
01/16/2020  03:39 AM         2,097,152 modemst2.bin
01/16/2020  03:39 AM           262,144 msadp.mbn
01/16/2020  03:38 AM            32,768 multi_image.mbn
01/16/2020  03:38 AM       314,572,800 NON-HLOS.bin
01/16/2020  03:39 AM       314,572,800 op1.img
01/16/2020  03:30 AM       268,435,456 op2.img
01/16/2020  03:30 AM     1,717,989,376 opproduct_a.bin
01/16/2020  03:31 AM     1,717,989,376 opproduct_b.bin
01/16/2020  03:29 AM         1,048,576 param.bin
01/16/2020  03:29 AM        33,554,432 persist.img
01/16/2020  03:38 AM            81,920 qupv3fw.elf
01/16/2020  03:38 AM       134,217,728 rawdump.bin
01/16/2020  03:38 AM       100,663,296 recovery.img
01/16/2020  03:39 AM         8,290,304 reserve1.bin
01/16/2020  03:39 AM        16,580,608 reserve2.bin
01/16/2020  03:39 AM        16,580,608 reserve3.bin
01/16/2020  03:39 AM        16,580,608 reserve4.bin
01/16/2020  03:39 AM            28,672 sec.elf
01/16/2020  03:39 AM        34,226,176 splash.bin
01/16/2020  03:39 AM         8,388,608 spunvm.bin
01/16/2020  03:29 AM             8,192 ssd.bin
01/16/2020  03:30 AM        10,485,760 static_nvbk.bin
01/16/2020  03:39 AM           131,072 storsec.mbn
01/16/2020  03:37 AM    15,032,385,536 super.img
01/16/2020  03:39 AM             2,759 ToolLog.txt
01/16/2020  03:39 AM         1,048,576 toolsfv.bin
01/16/2020  03:38 AM         4,194,304 tz.mbn
01/16/2020  03:39 AM           524,288 uefivarstore.bin
01/16/2020  03:38 AM         2,097,152 uefi_sec.mbn
01/16/2020  03:38 AM            65,536 vbmeta.img
01/16/2020  03:38 AM            65,536 vbmeta_system.img
01/16/2020  03:38 AM         3,670,016 xbl.elf
01/16/2020  03:38 AM           131,072 xbl_config.elf
 
Last edited:

kirschdog1

Senior Member

a63548

Senior Member
Apr 6, 2009
375
336
Not for McLaren 5g!!

Pretty sure in this case we are just using the MSM tool to make a backup/dump all of the partitions using the readback mode. I just did this successfully, and the phone is fine. Not sure, but I think using the MSM tool to restore/write anything would be where issues such as bricking would arise.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    ntzrmtthihu777 said:
    So, I've been doing some work on getting LineageOS to work on this device. No idea as of right now
    if it will work on any other carrier variants (I think they don't allow for bootloader unlocking?).

    Currently everything 'works' (some is buggy but that may be more to do with the fact that 17.1 is not
    currently finished) with the exception of two things I've tested/noticed (other stuff may be broken
    but I've not seen them yet): audio in calls (I can make/take calls but I can't hear or be heard. Audio
    works as I can play music in the LineageOS music app and record/playback the recording in the app)
    and the fingerprint sensor (pretty sure I'm just missing some part from the stock ROM).

    What I'm asking is that all owners of stock (unlocked/rooted is probably fine, custom kernels prob
    not) collect some logs for me during specific activities so I can determine what is missing and maybe
    produce a rom for you guys to test out without losing some features.

    I'd like three things:
    1. Follow the instructions here and upload the oem_log folder to somewhere and share it.
    2. A logcat of boot up through making a phone call and hang up. To take this, you'll need
    developer mode and adb debugging enabled on the phone and the platform tools (adb
    primarily) set up for your operating system. From either cmd.exe (windows) or Terminal.app (OSX)
    or your preferred terminal emulator (Linux, too many options to list them all), enter this command:
    Code:
    adb logcat > logcat.call.log
    Then, power your phone off, hook it up via USB to the machine, power it on, place the call,
    say a few words, hang up. Then press ctrl+c in the cmd/terminal/whatever window to
    end the logging session.
    3. A logcat of boot up through enrolling a fingerprint in the phone and unlocking via
    the fingerprint. Same procedure, but the command is:
    Code:
    adb logcat > logcat.finger.log

    Optionally, for those with rooted phones, I'd like these logs as well:
    4. A dmesg during boot up through making a call and hangup. Same procedure as #2, but the
    command is
    Code:
    adb shell su -c dmesg > dmesg.call.log
    5. A dmesg during boot up through enrolling a fingerprint in the phone and unlocking
    via the fingerprint. Same procedure as #3 but the command is
    Code:
    adb shell su -c dmesg > dmesg.finger.log

    The files gathered from #2-5 will be in the current directory you executed the logcat command
    from. On windows it will say this right before where you type the command, and on OSX/Linux
    this will probably be in your home directory, unless you changed the directory first. I expect OSX
    or Linux users to be a bit more savvy about this already.

    The files may contain unique data to your phone (serial number, IMEI, other things) but android
    filters out all but the last two numbers of the phone you are calling, so its generally ok. However,
    I do not suggest posting links to these files here, but you can message me them directly here.
    If/when you do this, please make note of the exact model number of your phone (not sure if
    all 5g phones are HD1925 or not), current firmware version, and baseband version. These can
    all be found in settings->about phone or so.
    Hopefully we can get all this sorted out before too long and have working lineage builds quickly.
    Thanks in advance and happy hacking!
    2
    Open up msm tool and press f8 when the screen pops up use crtl+a to select all partitions the PW is oneplus then ok . Then press readback button .Power off phone and connect phone while holding both volume buttons to USB keep holding the buttons till it shows it's connected and readback will start and you should have all img files and bin files in C/

    This would require the MSM tool specific to this device, would it not? If it doesn't, man, I need to get some folks
    to do this.
    2
    @ntzrmtthihu777 Thank you very much for continuing to work on developing for this phone! :) Just sent you a PM with the logcats for the calls and fingerprint, oem_log, and screenshots of phone information.

    Please let me know if there is more I can help with
    Is it within your wheelhouse to try the readback the previous poster in this thread mentioned?
    Shouldn't require the bootloader unlock, and you'd have the most virgin dump to provide to the
    rest of us for the moment.
    1
    This would require the MSM tool specific to this device, would it not? If it doesn't, man, I need to get some folks
    to do this.

    I've done it. But my bootloader is not unlocked and the OnePlus website says my IMEI is invalid. Use msm tool found in this forum. I used the one from my op7pro. This is something alot should have tried just from owning previous oneplus devices
    1
    Pretty sure in this case we are just using the MSM tool to make a backup/dump all of the partitions using the readback mode. I just did this successfully, and the phone is fine. Not sure, but I think using the MSM tool to restore/write anything would be where issues such as bricking would arise.
    Now that we have every partition we need someone to make .ops if that's even possible. That msm tool should work with our device if we had .ops I believe.

    ---------- Post added at 02:46 PM ---------- Previous post was at 02:41 PM ----------

    I'm pretty sure that this will not work on the McLaren 5g edition but maybe Im wrong?? Has anyone with the McLaren edition 5g used this to restore?? Dan?
    Like @a63548 said for a backup it for sure works, I can confirm it works as I just dumped all my partitions with it. A restore is another matter, I wouldn't mess around until we get confirmation it works.