yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] thisisapoorusernamechoice:
Oh really cool, I hadn't seen this root method yet. I'll be trying it tonight.

Either way I'm hopeful that with your provided files I'll make more headway into getting a build out.
[General Questions and Answers] atomic_hedgehog:
Sorry if it wasn't clear from my post, but I wasn't able to extract the blobs with that script. I got "

Unable to find helper script at ./../../../tools/extract-utils/extract_utils.sh" when running it and nothing else.
[General Questions and Answers] thisisapoorusernamechoice:
Oh yeah no worries I understood that. I meant with the vendor/bin and odm/bin you previously provided, I'm still hopeful I can get a build out now, that was the specific thing holding me up currently.

I asked you to try running that script because right now the vendor repo I currently have constructed is somewhat Frankenstein-ed together between stuff I was able to extract from my CPH2515 and stuff you and others have provided from the CPH2513. I hope it doesn't matter, but I'm guessing an optimized build would pull all of these files from one source. Plus ideally I think we would want the vendor blobs pulled from rooted Android 14, for the best results building LineageOS 21 (vs pulling from Android 13 possibly being better for building LineageOS 20).
[General Questions and Answers] atomic_hedgehog:
I managed to get it working after recreating the directory tree to match what was in the LineageOS wiki + downloading some of the tools listed there. However, I got some errors like "!! vendor/lib64/vendor.qti.hardware.radio.uim@1.2.so: file not found in source". Hopefully this won't affect anything.

Gofile - Free Unlimited File Sharing and Storage

Gofile is a free, secure file sharing and storage platform. With unlimited bandwidth and storage, you can easily store and share files of any type without any limits. Our advanced features, such as CDN support and password protection, make Gofile the ideal choice for individuals and businesses...

gofile.io
[General Questions and Answers] CINOBER:
Want to use for developer functions ?

Can You Run a Virtual Machine on a Smartphone? How Does It Work?

With smartphones increasingly becoming capable devices, did it ever cross your mind to run a virtual machine on them? Is it even possible? How?

www.makeuseof.com

Ps: because i cant see other motive why want to root ...

out of age where the root procedure was hw optimalization (4x18 Ghz + 8GB ram)...security ? if kernel pass rest of the boot ? what want to do?

yout phone will be the test space ? and try to rewrite te OP system or what ?
[General Questions and Answers] thisisapoorusernamechoice:
Really cool! Thank you very much! I've got a build going now, if it doesn't pan out I'm using these next. I think no matter what, ultimately it's going to be for the best for all of us that you've gotten this from running Android 14 rather than 13. Thank you again!

I desperately want to root my phone but I have the CPH2515 not CPH2513 (it's the T-Mobile branded N30). All the posts I've seen about trying any of your boot.img files to root my device haven't worked. In addition there are no full firmware files available that I can find to get CPH2515 back to stock. If I mess up, I don't know that I have a way to unbrick my device.
[General Questions and Answers] 11gperry:
Well I don't know if it's any help, but I do have a soft-bricked MetroPCS CH2515 I'm willing to donate for trial and error. I patched the wrong boot.img myself so it's of no use to me.

I am also in the process of brute-forcing a firmware zip for the CH2515 that is on gsm mafia as well (Owner is uncontactable), I'm unsure on the revision but it may come in handy.
[General Questions and Answers] logiccircuit:
n30 - Google Drive

drive.google.com

In the 14_201 directory again, ossi.tar.gz
[General Questions and Answers] logiccircuit:
CPH-EDL - Google Drive

drive.google.com

This is the full CPH2515 EDL firmware file from GSMmafia, extracted and then re-compressed without a password. No guarantees whatsoever that it'll unbrick your phone if needed.

This file is identical to the CPH2513 file on GSMmafia. The version-info.txt file references the 2465,2467,2513, and 2515. But the build.prop file claims it's for the 2467. It might be a universal EDL for all four, and the 2467 might be considered the 'base' phone. But again, no guarantees whatsoever.

To root your phone, you should be able to pull the boot.img from the CPH2515 OTA that's been floating around the web. Have you checked into that?
[General Questions and Answers] 11gperry:
I can say pretty confidently MSM and the OnePlus Device Flasher did not accept this particular firmware for the CPH2515 variant.

I received a device handle error at 3% in this particular instance using EDL.

It was worth a shot though!
[General Questions and Answers] logiccircuit:
Unfortunate. The 3% device error is probably the Qualcomm Validated Image Programming (VIP) security check failing.

As an experiment, I downloaded a couple others available on GSMmafia.

They're all the same thing - a build.prop file that specifically names the CPH2467, and a version-info.txt that lists the other models. Maybe they're all supposed to have a distinct build.prop, and the checksum file and .sig are supposed to be different. Or since version-info.txt has a checksum for each model, maybe a legit MSM tool does some online verification that we don't have access to, idk
[General Questions and Answers] thisisapoorusernamechoice:
There is just now a March-dated android 14 update for the CPH2515, update file size approximately 5.6GB. Is there any way possible to pull this update file without root? I'm not particularly hopeful but either way I'm still slogging through build errors
[General Questions and Answers] 11gperry:
I'm not entirely sure how to do it, but I believe using a Man In The Middle setup should work. However, if the update was already downloaded you may be able to recapture it after a device format, depending on wether or not it it is already installed pending restart.

Another possible option is using Shizuku and a compatible file browser such as FV Browser to locate and copy the OTA's folder.

On a side note if this android update can be preserved, all currently bricked CPH2515 models should have a avenue to be restored.
[General Questions and Answers] thisisapoorusernamechoice:
This was an excellent tip thank you. I agree you're right it's vital I figure out a way to pull this update file. At 5.6GB it has to be a full firmware file. This is embarrassing but I'm having trouble locating where the update file is actually downloaded to. I know other OnePlus devices have used ether /.ota or /sdcard/Android/data/com.oneplus.ota but neither exist on mine.
[General Questions and Answers] Yeedatoy:
Yes. Use mt manager and extract it just like a zip. Or am I misunderstanding? You don't get a download file if you open the oxygen updater app? What I mean is you pull the boot image with mt manager, not payload dumper or anything like that. It's a huge waste of time when all your need to do is extract one file. You don't even need the boot image, magisk will patch it from the payload.bin directly. It will actually extract it from the full 5gb zip file normally but it's broken on the latest release
[General Questions and Answers] 11gperry:
Honestly I tried digging around for the OTA folder for the last revision update before this but I lost my patience, I know it should be kicking around ./Android/ or root.

The other possibility is T-Mobile/Metro could of locked it down in some obscure location. Sadly nothing about the CPH2515 model has been anything standard.
[General Questions and Answers] 11gperry:
Unfortunately the firmware by T-Mobile/Metro has never been directly released by OnePlus or captured via MiTM or root outside of minor OTAs for the NA variant.
[General Questions and Answers] Yeedatoy:
Data/ota or data/OnePlus ota
[General Questions and Answers] Yeedatoy:
You can actually get into almost any folder without root on this device oddly. I was able to go into dev/block/byname and access everything. You should be able to find the boot from there. Let me dig around and see if I can find anything. To be clear it's cph2515 and which month is needed?
[General Questions and Answers] 11gperry:
I just needed the latest update that came out in March before android 14 rolled out just now, mostly to snipe the boot.img from it.

I believe the other user needed to retain a copy of the Android 14 release OTA.
[General Questions and Answers] Yeedatoy:
On another note. For anyone rooted I suggest using the exposed mod Lucky Tool. You can change about anything on the device. Also just by installing APKs from Realme and other oppo devices you can get spacial audio, edge lighting and damn near anything. This phone has partitions for every other model released that is by another sub brand. It's just a config file that determines what is active
[General Questions and Answers] Yeedatoy:
Okay. I'll look around. I only had one update and it was to a14. There's another a13 release for the T-Mobile version? I guess I should stop being lazy and just read the whole thread. Hopefully I'll come up with something. I was able to dig up some stuff for my variant that wasn't easily accessible. Give me 20 minutes or so
[General Questions and Answers] Yeedatoy:
What is the 010109 update? It's incremental
[General Questions and Answers] Yeedatoy:
Well. Probably not what is needed but if someone does let me know. Incremental. You need the APK from OnePlus to install since there's no local update section on our phones

METADATA_HASH=oGbWrfAK1ZqNrTQbTzX+9BIsDEftWdJZtlxDdjVHcHQ=

METADATA_SIZE=796546

security_patch_vendor=2023-07-05

oplus_separate_soft=22872

ota_target_version=CPH2515_11.A.18_0180_202306302120

security_patch=2023-07-05

oplus_rom_version=V13.1.0

oplus_update_engine_verify_disable=0
[General Questions and Answers] Yeedatoy:
Anyone try this? This guy is a master dev for lg. I think he worked for them.

GitHub - AeonLucid/OnePlusOTA: Download OnePlus OTA updates

Download OnePlus OTA updates. Contribute to AeonLucid/OnePlusOTA development by creating an account on GitHub.

github.com
[General Questions and Answers] Yeedatoy:
There's these:

CPH2515export_11_A.24_2023101217580130

CPH2515export_11_A.18_2023063021200119

CPH2515export_11_A.15_2023053017270000

CPH2515export_11_A.14_2023052414550000
[General Questions and Answers] Yeedatoy:
Can you give me the exact name of the update or close to it? Also the stock file manager will direct you to where your update was stored
[General Questions and Answers] 11gperry:
Unfortunately the phone itself is soft-bricked. The update was a "cph2515_13.1.0.625(EX01)" update that only comes through a OTA.

Pretty much the Metro CPH2515 at least, did not have access to the update storage, even with Shizuku. I do know many people use the CPH2513 version, which is the North America unlocked version.

On a side note, the export files you shared are configured for the CPH2467 in the build.prop for MSM and Flash Tool, it seems, as another user pointed out. Modifying the build.prop for other device specific variations (which are noted in the file) is not enough to send the firmware to the device.

The CPH2515 version seems to be hyper sensitive to boot.img files to identical phones with a different configuration or even from a slightly different update. I would love to coin the term "Tracfone Syndrome' for this haha.

Edit: Oddly enough though, I was able to unlock the bootloader and gain full Fastboot/ADB access.
[General Questions and Answers] Yeedatoy:
I have OnePlus full system dumps pulled up and I may have the boot image for every update unless I have the wrong device. There's firmware for 2 variants here so I think I may have it. Does anything look correct here? I know it's the N30 5g I just want to make sure one of these is the T-Mobile variant

qssi-user-14-UKQ1.230924.001-1706770327543-release-keys--IN

qssi-user-14-UKQ1.230924.001-1701959973846-release-keys--US

qssi-user-13-TP1A.220905.001-1698921269974-release-keys--IN

qssi-user-13-TP1A.220905.001-1698921269974-release-keys--US

qssi-user-13-TP1A.220905.001-1693192137603-release-keys--US

qssi-user-13-TP1A.220905.001-1693192137603-release-keys--IN

qssi-user-13-TP1A.220905.001-1692247458933-release-keys--IN

qssi-user-13-TP1A.220905.001-1688035494034-release-keys--IN

qssi-user-13-TP1A.220905.001-1684750626159-release-keys--IN

qssi-user-13-TP1A.220905.001-1682403789650-release-keys--IN

qssi-user-13-TP1A.220905.001-1680878860896-release-keys--EUEX

qssi-user-13-TP1A.220905.001-1680878860896-release-keys--IN

qssi-user-13-TP1A.220905.001-1678963494026-release-keys--IN

qssi-user-13-TP1A.220905.001-1678376266199-release-keys--IN default
[General Questions and Answers] Yeedatoy:
There are 3 versions here but OnePlus makes this extremely difficult with their fingerprint format. The cph2513, the ce 3 5g and I'm assuming the cph2515. These get automatically uploaded though a tool by request. I'm not sure how to do it though. This is where I get most of my files to build magisk modules as firmware for thousands of devices is here. Here's a link for future reference as it's an essential site to access

Android Dumps / oneplus / op5958l1 · GitLab

GitLab Enterprise Edition

dumps.tadiphone.dev
[General Questions and Answers] thisisapoorusernamechoice:
I might've found the folder but I can't access it read or write, so not certain.

Edit: also I've done the entire update process short of the reboot, so if I understand correctly the update file needs to be stored somewhere on this device. I'm keeping my battery between 20-30% so it can't automatically reboot itself. It's going to force the issue on 4/6 I believe it said
[General Questions and Answers] 11gperry:
Honestly I'm not quite sure, I know what is shown is the US unlocked and International models.

I could try around with the "qssi-user-13-TP1A.220905.001-1698921269974-release-keys--US" dump.

In theory if it is the last A13 revision before the A14 drop, the boot.img would allow a full boot if it is correct, as only the boot.img was modified on my device.

If it does not work, I would be able to confirm that the US unlocked boot.img is not compatible with the T-Mobile/Metro variant and put that contradiction to rest.

Honestly though, I do believe those dumps could be of great help to the community! I'm sure many people with other revisions will be very grateful with this. Thank you!
[General Questions and Answers] Yeedatoy:
Remember you can do fastboot boot the magisk patched image first. If it boots, then flash it. That way you can test without ending up bricked
[General Questions and Answers] 11gperry:
Sadly the device was soft-bricked a couple days ago. For some reason my model did not allow the fast boot boot command and I was forced to throw a Hail Mary and Fastboot flash a wrong CPH2515 image which was actually an outdated CPH2513 boot.img. This was with the latest Fastboot and ADB tools on Linux.

And yes I was definitely impatient, the fault was 100% my own. However now I have a device I'm free to test all I want for now, I suppose.
[General Questions and Answers] Yeedatoy:
What file manager? Try Mt manager and grant it shizuku access
[General Questions and Answers] Yeedatoy:
Damn, that's odd. Do you have another phone?
[General Questions and Answers] 11gperry:
Oh yes, I have a Pixel 7 and a Moto Stylus 5G 2023 at the moment, both rooted. I am tempted to donate my N30 though for whoever wants to take a shot at development and rooting for the stubborn CPH2515 model. I got it from metro for $40 and it should carrier unlock after 180 days after recovery of the firmware.
[General Questions and Answers] Yeedatoy:
It's probably not allowing it to boot because dmverity and verification isn't disabled. You can use the bugjager mobile adb app to flash from your pixel 7 if you're using a PC. It also has some other functionality that may help pull some files. If we knew what block the boot image was in we could pull it with adb. You only flashed one slot correct? So the other boot image either a or b is still correct?

If you want to take a shot at it you can download an empty vbmeta image and flash it to remove dm verity and verification and then you'll be able to boot images. If the device is unlocked you should be able to switch slots and boot though

Edit. Autocorrect turned vbmeta into camera
[General Questions and Answers] 11gperry:
I will try that when I get back! Unfortunately switching boot slots to the clean slot causes the same issue except with a immediate black screen before reboot, so I do believe the vbmeta partition might very well fix it!

I do know the phone gets to the logo with the magisk patched image, so I suppose that may be it failing security checks at that point.
[General Questions and Answers] thisisapoorusernamechoice:
FV file manager with shizuku access
[General Questions and Answers] dukemccoy:
I was able to do this before when it was on Android 13, but in December it force pushed out Android 14 (CPH2513_14.0.0.0(EX01)) which unrooted my device (thanks Google) and now I'm unable to successfully install a magisk patched boot.img using fastboot - I read something about fastboot being disabled or something. I've tried on multiple boxes, Linux and Windows, all I get is this:

sudo fastboot boot magisk_patched-27000_QRluy.img

Sending 'boot.img' (163840 KB) OKAY [ 5.851s]

Booting FAILED (remote: 'unknown command')

fastboot: error: Command failed

I'm stuck at square zero, and I'm pretty disgusted with this whole situation as I need this phone rooted as soon as possible to control a medical device. I'll buy another device that I can actually root and use as if I own the stupid thing.
[General Questions and Answers] thisisapoorusernamechoice:
Yeedatoy​

since I'm now able to at least see and access the OTA app itself (still not its storage directory yet) shouldn't there be a way to extract and/or decompile the com.oplus.ota apk for the purpose of discovering where it's querying and downloading this 5.6GB update file that I know must exist?

Edit: the OTA apk from my CPH2515 is attached
[General Questions and Answers] logiccircuit:
Try this (in fastboot):

sudo fastboot getvar current-slot
sudo fastboot flash boot_X magisk_patched-27000_XXXXX.img

...obviously changing boot_X and the magisk-patched*.img info as necessary.

Or try it with fastboot boot instead of fastboot flash first, if you want to be safe.
[General Questions and Answers] logiccircuit:
@thisisapoorusernamechoice I'm not clear, are you still on Android 13?

Android Dumps / oneplus / op5958l1 · GitLab

GitLab Enterprise Edition

dumps.tadiphone.dev

This is the correct version of the phone, as @Yeedatoy mentioned above.

Specifically the qssi-user-14-UKQ1.230924.001-1710758598586-release-keys--P-US-TMOBILE-USKU branch is the most recent, and is the only one there obviously for T-Mobile.

You should be able to grab the boot.img from there and try to fastboot boot (patched)boot.img, assuming you're on Android 14. Or try patching it and using fastboot boot (patched)boot.img anyway on Android 13, maybe it'll work?
[General Questions and Answers] thisisapoorusernamechoice:
I'm still on 13 only because I wanted to try to pull the downloaded update file from my own device. If you're correct and this is essentially that file, I'll definitely update ASAP and see if I can root with that boot.img file
[General Questions and Answers] logiccircuit:
I'm certain that op5958l1 is the correct model - it's seen several times in that 2515 update OTA that's been floating around the web for a while now (which is v600, if that's useful to you). With the US-TMOBILE part of the branch title, plus the files only being added 3 days ago, it's pretty convincing.

But, it's not my phone, and not my files, so I can't verify anything. Cannot guarantee results.

While you're still on Android 13, you could try a fastboot boot (patched).img using the v600 boot.img that's in the OTA. Might work, might not.

When I first got my N30, I accidentally flashed a rooted v600 boot.img instead of the v611(?) that my phone was on. None of my connectivity worked, but it booted fine. Since I was rooted, I imaged the boot partition using dd, and got myself fixed up right away.

You could have a similar experience, or your phone could explode. Again cannot guarantee results.
[General Questions and Answers] thisisapoorusernamechoice:
I would love to try any of this but I've tried payload-dumper-go on the payload.bin inside the update.zip for that CPH2515 OTA and all the .img files come out as 0B
[General Questions and Answers] logiccircuit:
Further to the files on the gitlab link in my last post, this is in the my_manifest/build.prop file:

ro.product.vendor.brand=OnePlus
ro.odm.build.fingerprint=OnePlus/CPH2515/OP5958L1:14/RKQ1.211119.001/T.R4T1.1712fcc_5d06-10bca:user/release-keys
ro.vendor.product.oem=CPH2515
ro.build.id=RKQ1.211119.001
ro.build.product=CPH2515
ro.product.bootimage.brand=OnePlus
ro.product.vendor.device=OP5958L1

So I'm much more confident that it's the right files for your phone, for an Android 14 environment. That boot.img should be your pathway to root.

(Results not guaranteed tho)
[General Questions and Answers] logiccircuit:
https://drive.google.com/drive/folders/180S8WDCQ7e-BWimjg8ip-5i-2pLTcYW5?usp=sharing

There's a zip file named oneplus.600.magisk.zip which I lifted from another post on xda. It's the boot.img files for a v600 build for the 2515.

But, not my phone, not my files. Results not guaranteed.
[General Questions and Answers] logiccircuit:
I forgot - unfortunately the payload.bin dumpers all have the same problem: they don't work in incremental OTAs.

At least, I've never found one that works.
[General Questions and Answers] g96818:
just going to give you a warning since you're using 2515.

Don't! Pull your own boot images since Tmo updates don't always align with 2513 or CE 3 Lite, even if the base hardware is the same op5958l1.
[General Questions and Answers] thisisapoorusernamechoice:
Are we supposed to do the following when attempting to use magisk on this device:

From the official magisk installation instructions.

Edit: actually probably not, I didn't realize when I asked but this is the first OnePlus device I've worked with in a while without a vbmeta partition
[General Questions and Answers] logiccircuit:
It has a vbmeta partition, but it's normally inside the super partition on an installed & running system.

I've never needed to do a vbmeta flash, but the 2515 might have different requirements.
[General Questions and Answers] logiccircuit:
n30 - Google Drive

drive.google.com

If anyone needs it, I've uploaded the newest CPH2513 full update (14.0.0.302), and a magisk'd boot.img created from the boot.img file in the update.
[General Questions and Answers] thisisapoorusernamechoice:
Thank you! This should make pulling the binary blobs much easier now!!

To any other CPH2515 owners reading along, I successfully used the boot.img from this dump (TMO branch) with magisk and now I'm rooted!

Edit: to confirm, I now have ADB access available to certain things that I simply did not before I rooted. Adaway (my beloved) also working.
[General Questions and Answers] 11gperry:
Glad to see it worked out for you! Unfortunately the vbmeta trick had no effect for my CPH2515. Also, to which dumb are you referencing? My phone is still on the last A13 update so I'm not 100% sure if It'll work, but side loading as a manual OTA should in theory.
[General Questions and Answers] Yeedatoy:
Disabling dmverity will allow you to boot a patched image. Without doing so you can only flash images..not boot because verified boot will detect that the image was modified
[General Questions and Answers] Yeedatoy:
Watch.