Hahahah it seems China repeats on itself.
Huawei did a job on XDA
Hahahah it seems China repeats on itself.
Nothing is already a nothingburger seeing how they won't be releasing in the US. Those of us who need a new phone and stick with Android (because many are switching to iPhone despite its limitations) are going to end up with a Pixel or Motorola and the vast majority will go Pixel. The only way that doesn't happen is if Google doesn't allow bootloader unlocking with the 7 series, OnePlus reverses course between now and then, there's an MSM Tool leak despite policy, etc. We still have 5-6 months before the 7 series will presumably be released so there is still time yet but it's not looking good, especially if Qualcomm is the one behind everything, because that would affect all devices using new Qualcomm SoCs.Though I wouldn't communicate it in the same way (please keep it civil folks), I do very much agree that OnePlus has become exactly what they were up against back in 2014. They've become massive hypocrites by shutting out the community that made them. There was so much amazing development on the OnePlus One, which I have proudly owned as a daily driver for over 3 years, that a lot of community invented/inspired goodies ended up in all Android iterations by all brands active in the market today. It was truly revolutionary. And this is how OnePlus thanks us today: with a knife in our collective backs. Under the disguise of "improving security" – which is an easy excuse for a lot of things – companies like OnePlus and of course also Google have been striking development communities hard. Why? Not willing to deal with any liability or unpredictable situations (shareholders like keeping things predictable) I guess. The cool thing, though, is that we're still here and we're still developing!
I currently have high hopes for Nothing. If it'll be anything like Bacon, another community revolution is just around the corner...
can u please tell me how to login MSMdownload tollThere are MSM Tools out for ColorOS on the 10 Pro though. Three of them, in fact, are publicly available, they're just encrypted.
一加10 Pro/9008线刷救砖包ColorOS 12.1 A.04 - 一加手机官方ROM - 一加手机官方ROM下载
本站提供一加全机型ROM下载,包括一加Ace/10R、一加10 Pro、一加9Pro、一加9RT、一加9R、一加8T、一加8 Pro、一加8、一加7T Pro、一加7T、一加7Pro等全系一加机型的升级全量包、降级包、9008线刷救砖包等各种官方和原厂ROM,全部资源完全免费,不限速,无需登录yun.daxiaamu.com
一加10 Pro/9008线刷救砖包ColorOS 12.1 A.07 - 一加手机官方ROM - 一加手机官方ROM下载
本站提供一加全机型ROM下载,包括一加Ace/10R、一加10 Pro、一加9Pro、一加9RT、一加9R、一加8T、一加8 Pro、一加8、一加7T Pro、一加7T、一加7Pro等全系一加机型的升级全量包、降级包、9008线刷救砖包等各种官方和原厂ROM,全部资源完全免费,不限速,无需登录yun.daxiaamu.com
NE2210domestic_11_A.12_2022030701060000.zip - 一加手机官方ROM - 一加手机官方ROM下载
本站提供一加全机型ROM下载,包括一加Ace/10R、一加10 Pro、一加9Pro、一加9RT、一加9R、一加8T、一加8 Pro、一加8、一加7T Pro、一加7T、一加7Pro等全系一加机型的升级全量包、降级包、9008线刷救砖包等各种官方和原厂ROM,全部资源完全免费,不限速,无需登录yun.daxiaamu.com
If Qualcomm is going to start being anti-developer, I guess it's a good thing that Pixel doesn't use their processors anymore.
You can't. This tool is only for the technicians to use to remotely fix your phone. It even uses entirely different encryption from the standard MSM Tools so you can't even extract it to get the images.
I am using OnePlus since OnePlus one my last device is OnePlus 8 pro and so satisfying but OnePlus 10 pro is waste of money. I guess its time to switch from OnePlusYou can't. This tool is only for the technicians to use to remotely fix your phone. It even uses entirely different encryption from the standard MSM Tools so you can't even extract it to get the images.
Oh you can get the images, plenty of oppo decrypt projects out there. The problem is there is no way of talking to edl/sahara/firehose for when you **** up, so having these images is useless if you're bricked.You can't. This tool is only for the technicians to use to remotely fix your phone. It even uses entirely different encryption from the standard MSM Tools so you can't even extract it to get the images.
Nope, tried the extraction, it doesn't work with the tools that are available. I filed an issue about it on the Oppo Decrypt GitHub. The ColorOS one uses a OnePlus OFP file instead of a OnePlus OPS like the other MSM Tools and neither the OPS or OFP decrypter worked with it, same issue with the ColorOS MSM for the 9 I checked. There seems to be different encryption on COS MSM Tools.Oh you can get the images, plenty of oppo decrypt projects out there. The problem is there is no way of talking to edl/sahara/firehose for when you **** up, so having these images is useless if you're bricked.
Nope, tried the extraction, it doesn't work with the tools that are available. I filed an issue about it on the Oppo Decrypt GitHub. The ColorOS one uses a OnePlus OFP file instead of a OnePlus OPS like the other MSM Tools and neither the OPS or OFP decrypter worked with it, same issue with the ColorOS MSM for the 9 I checked. There seems to be different encryption on COS MSM Tools.
I wasn't aware of the change in Sahara until you pointed it out the other day though so yeah, that sucks.
:/mnt/e/android/OnePlus/OP10P/MSM/NE2210 Color OS A.07/NE2210$ ls
BTFM.bin DigestsToSign_20846_persist_yes_userdata_yes.bin.mbn cpucp.elf gpt_main4.bin provision_hynix.xml super.1.5da0ae97.img
ChainedTableOfDigests_20846_all.bin DigestsToSign_nv00000000.bin.mbn devcfg.mbn gpt_main5.bin provision_micron.xml super.2.46fdb373.img
ChainedTableOfDigests_20846_persist_no_userdata_no.bin DigestsToSign_nv10010111.bin.mbn dspso.bin hypvm.mbn provision_samsung.xml tools.fv
ChainedTableOfDigests_20846_persist_no_userdata_yes.bin DigestsToSign_pre_provision.bin.mbn dtbo.img imagefv.elf provision_toshiba.xml tz.mbn
ChainedTableOfDigests_20846_persist_yes_userdata_no.bin DigestsToSign_provision_hynix.bin.mbn dynamic_nvbk.20846.bin keymint.mbn qupv3fw.elf uefi.elf
ChainedTableOfDigests_20846_persist_yes_userdata_yes.bin DigestsToSign_provision_micron.bin.mbn emmc_fw.bin logfs_ufs_8mb.bin rawprogram0.xml uefi_sec.mbn
ChainedTableOfDigests_nv00000000.bin DigestsToSign_provision_samsung.bin.mbn engineering_cdt.img metadata.img rawprogram1.xml userdata.img
ChainedTableOfDigests_nv10010111.bin DigestsToSign_provision_toshiba.bin.mbn featenabler.mbn oplus20846.bin rawprogram2.xml vbmeta.img
ChainedTableOfDigests_pre_provision.bin NON-HLOS.bin gpt_backup0.bin oplus_sec.mbn rawprogram3.xml vbmeta_system.img
ChainedTableOfDigests_provision_hynix.bin ProFile.xml gpt_backup1.bin oplusreserve2.img rawprogram4.xml vbmeta_vendor.img
ChainedTableOfDigests_provision_micron.bin Projectconfig.xml gpt_backup2.bin patch0.xml rawprogram5.xml vendor_boot.img
ChainedTableOfDigests_provision_samsung.bin Setting.xml gpt_backup3.bin patch1.xml recovery.img xbl_config.elf
ChainedTableOfDigests_provision_toshiba.bin XblRamdump.elf gpt_backup4.bin patch2.xml sec_smt.dat xbl_s.melf
DRIVER.ISO abl.elf gpt_backup5.bin patch3.xml shrm.elf zeros_5sectors.bin
DigestsToSign_20846_all.bin.mbn aop.mbn gpt_main0.bin patch4.xml splash.img
DigestsToSign_20846_persist_no_userdata_no.bin.mbn aop_devcfg.mbn gpt_main1.bin patch5.xml static_nvbk.20846.bin
DigestsToSign_20846_persist_no_userdata_yes.bin.mbn apdp.mbn gpt_main2.bin persist.img storsec.mbn
DigestsToSign_20846_persist_yes_userdata_no.bin.mbn boot.img gpt_main3.bin prog_firehose_ddr.elf super.0.bc2dec5a.img
Interesting. It didn't work for me with the A.12 image, I didn't grab A.07 to try it.Code::/mnt/e/android/OnePlus/OP10P/MSM/NE2210 Color OS A.07/NE2210$ ls BTFM.bin DigestsToSign_20846_persist_yes_userdata_yes.bin.mbn cpucp.elf gpt_main4.bin provision_hynix.xml super.1.5da0ae97.img ChainedTableOfDigests_20846_all.bin DigestsToSign_nv00000000.bin.mbn devcfg.mbn gpt_main5.bin provision_micron.xml super.2.46fdb373.img ChainedTableOfDigests_20846_persist_no_userdata_no.bin DigestsToSign_nv10010111.bin.mbn dspso.bin hypvm.mbn provision_samsung.xml tools.fv ChainedTableOfDigests_20846_persist_no_userdata_yes.bin DigestsToSign_pre_provision.bin.mbn dtbo.img imagefv.elf provision_toshiba.xml tz.mbn ChainedTableOfDigests_20846_persist_yes_userdata_no.bin DigestsToSign_provision_hynix.bin.mbn dynamic_nvbk.20846.bin keymint.mbn qupv3fw.elf uefi.elf ChainedTableOfDigests_20846_persist_yes_userdata_yes.bin DigestsToSign_provision_micron.bin.mbn emmc_fw.bin logfs_ufs_8mb.bin rawprogram0.xml uefi_sec.mbn ChainedTableOfDigests_nv00000000.bin DigestsToSign_provision_samsung.bin.mbn engineering_cdt.img metadata.img rawprogram1.xml userdata.img ChainedTableOfDigests_nv10010111.bin DigestsToSign_provision_toshiba.bin.mbn featenabler.mbn oplus20846.bin rawprogram2.xml vbmeta.img ChainedTableOfDigests_pre_provision.bin NON-HLOS.bin gpt_backup0.bin oplus_sec.mbn rawprogram3.xml vbmeta_system.img ChainedTableOfDigests_provision_hynix.bin ProFile.xml gpt_backup1.bin oplusreserve2.img rawprogram4.xml vbmeta_vendor.img ChainedTableOfDigests_provision_micron.bin Projectconfig.xml gpt_backup2.bin patch0.xml rawprogram5.xml vendor_boot.img ChainedTableOfDigests_provision_samsung.bin Setting.xml gpt_backup3.bin patch1.xml recovery.img xbl_config.elf ChainedTableOfDigests_provision_toshiba.bin XblRamdump.elf gpt_backup4.bin patch2.xml sec_smt.dat xbl_s.melf DRIVER.ISO abl.elf gpt_backup5.bin patch3.xml shrm.elf zeros_5sectors.bin DigestsToSign_20846_all.bin.mbn aop.mbn gpt_main0.bin patch4.xml splash.img DigestsToSign_20846_persist_no_userdata_no.bin.mbn aop_devcfg.mbn gpt_main1.bin patch5.xml static_nvbk.20846.bin DigestsToSign_20846_persist_no_userdata_yes.bin.mbn apdp.mbn gpt_main2.bin persist.img storsec.mbn DigestsToSign_20846_persist_yes_userdata_no.bin.mbn boot.img gpt_main3.bin prog_firehose_ddr.elf super.0.bc2dec5a.img
Donno, works for me, at least for A.07. That's how I even got the firehose prog to even start with the edl stuff
But yeah, it's moot b/c protocol
Can u tell me how to get unbrick support for 10 proThere are MSM Tools out for ColorOS on the 10 Pro though. Three of them, in fact, are publicly available, they're just encrypted.
一加10 Pro/9008线刷救砖包ColorOS 12.1 A.04 - 一加手机官方ROM - 一加手机官方ROM下载
本站提供一加全机型ROM下载,包括一加Ace/10R、一加10 Pro、一加9Pro、一加9RT、一加9R、一加8T、一加8 Pro、一加8、一加7T Pro、一加7T、一加7Pro等全系一加机型的升级全量包、降级包、9008线刷救砖包等各种官方和原厂ROM,全部资源完全免费,不限速,无需登录yun.daxiaamu.com
一加10 Pro/9008线刷救砖包ColorOS 12.1 A.07 - 一加手机官方ROM - 一加手机官方ROM下载
本站提供一加全机型ROM下载,包括一加Ace/10R、一加10 Pro、一加9Pro、一加9RT、一加9R、一加8T、一加8 Pro、一加8、一加7T Pro、一加7T、一加7Pro等全系一加机型的升级全量包、降级包、9008线刷救砖包等各种官方和原厂ROM,全部资源完全免费,不限速,无需登录yun.daxiaamu.com
NE2210domestic_11_A.12_2022030701060000.zip - 一加手机官方ROM - 一加手机官方ROM下载
本站提供一加全机型ROM下载,包括一加Ace/10R、一加10 Pro、一加9Pro、一加9RT、一加9R、一加8T、一加8 Pro、一加8、一加7T Pro、一加7T、一加7Pro等全系一加机型的升级全量包、降级包、9008线刷救砖包等各种官方和原厂ROM,全部资源完全免费,不限速,无需登录yun.daxiaamu.com
If Qualcomm is going to start being anti-developer, I guess it's a good thing that Pixel doesn't use their processors anymore.
Maybe. If OnePlus is really set on not remotely flashing anymore, the likelihood of an MSM goes down quite a bit.Yeah... chinese version relased in January.
Global released in (31 march) April.
I'm guessing that will be 1, 2 months till MSM Global.
My OnePlus 9 was all but unusable with the stock unmodified OOS12 software and running OOS11 was not an acceptable compromise so it was either custom ROM or send it back.
Rooting OnePlus 6T: super easy, barely an inconvenience. Benefits: SKINS...rooting a phone seems to be a pain those days and don't give benefits it used to before (mainly used for Titanium Backup) so I guess I could stick with manufacturer Rom...
The Nothing Phone (1) looks promising! I got my son a Pocophone just a few months ago and he's really happy with it. After the 7-day cooldown it was a breeze to unlock and flash a ROM.
The NE2217 (T-Mobile) version would be a piece of cake, but One Plus can't be bothered to update its unlock token page. Most recent phones listed are the 9Pro and N200.Root/unroot on OP 6, 6T, 7 Pro was fun & easy. Go back to stock the same.
On 10 Pro is pure hell !
Exactly, it got leaked but OnePlus put more protections around it. The thing itself is packed as well, I was able to start reversing it, and the protocol commands are COMPLETELY different. A lot of lower level things are much easier to reverse from dynamic analysis rather than static with vmprotect and other packers on. I don't really have time to do a full deep dive analysis on the protocol while not being able to even see it in action, just complete guesses. See https://github.com/bkerler/edl/issues/274 for a brief description in the 3rd post. Even if the loader is sent, the magic to start communication in firehose is now different as well, so after getting past sahara, now you have to deal with firehose.There are MSM Tools out for ColorOS on the 10 Pro though. Three of them, in fact, are publicly available, they're just encrypted.
Honestly I would just stick with OP9 on a supported stable rom of some kind and use it into the ground. Not sure what's going on but look at the dev section for Pixel 6 Pro, you got kernels, and that's about it, and it's been over 6 months since release already. The few roms that did come out are dying or dead.Sounds like it is time to move away from Qualcomm then. I guess my next phone is going to be a Pixel after all. At least there I know that I'll get rapid updates that actually fix bugs rather than this nonsense with OnePlus that forces people to go to custom ROMs just to get basic functionality and a stable device in the first place.
Honestly the holdup is probably on Qualcomm. Sahara is updated v3.x, so all firehose tools we've had stopped working. If MSM was leaked successfully, people would be able to reverse the new protocol, so QCom probably put more restrictions on OEMs to prevent that. Additionally, sources still doesn't seem to be released so nothing really can be built against. Check out any SD8G1 devices and the dev support currently:I've made a mod for this device mate. I've made guides.
Something is different with this device.
I just wish I'd seen it before.
Game over for me pal... Sitting with this crap OOS for another year?? No chance I'm getting the pixel 7 this turd it's getting sold