tdm

This is news to me. I'm not terribly familiar with qcom devices on this level, but in the past when I was working at Cyanogen, I had a co-worker sign a new device with a freshly generated key. He told me that it was a one-time operation that could not be reversed or changed. I'd be interested in hearing more about this. But even if it is possible, I have strong doubts that any mainstream device would be setup to do this.

That is not possible. If it were, anyone could do the same and it would defeat the purpose of verification. Only the OEM has the signing key and only the OEM can create signed images to pass verified boot. As mentioned, yes, some of the IdeaLTE bits/blobs are used to build Lineage. But only those necessary to support the hardware. In general, OEMs that do stupid and/or sneaky things place them into the upper layers of Android which Lineage does not use. Briefly, code running on Qualcomm devices (and most/all Android devices) can be divided into four broad

FxTec does not build anything. Chen only distributes what FxTec gets from IdeaLTE. EDIT: And further, I know that FxTec does not have the device signing keys. So if they did build something, it wouldn't boot with a locked boot loader.

Uhhhmmmm, you do realize that the Copperhead team is rather antagonistic to Lineage, right? It's not surprising that they would slam Lineage as being insecure. They do raise some valid points (particularly about verified boot), but most are bogus and/or outdated. Verified boot requires a locked boot loader. You cannot run any custom software with it enabled, including this ROM. That may be fine at the time of release (though with a BSP that is already 4 months out of date, probably not). But as soon as the OEM stops updating, you have a choice of running with verified boot and

That's an interesting perspective. May I ask how you came to that conclusion? My feeling is exactly opposite. The OEM may or may not provide security updates for a period of time after release. My copy of the BSP is on tag LA.UM.7.4.r1-05500-8x98.0 which was released August 23, 2019. Incremental updates may have newer code, I'm not sure because I don't do OTAs. But either way, IdeaLTE will stop publishing updates at some point. As a member of Lineage and former Cyanogen employee, I can assure you that many/most of the Lineage developers care a great deal about secu

I can certainly look into this. I also hate to waste 4gb of storage for no benefit to me (because I never use OTAs). But do understand that it's pretty low priority. Also note that it will require repartitioning the device, which makes most folks nervous. And I'll need to make a non-AB version of lineage. In other words it's a fair bit of work and will take some time.

I don't use VoLTE, so I'll need others to test. But I'll do my best to make it work.

Just a quick update... I had two weeks off for the holidays and I am back this week. I've experimented with building a vendor image but that looks like it will take a fair amount of time. So next I looked at a method of overlaying changes over the vendor files instead of building the entire vendor image. This is easier and significantly reduces the amount of data transfer (both from github to me and from my website to you) so I will probably continue down that path for the official Lineage release. But for now, I'm pretty tired of playing with vendor files

I was answering this very question as you posted. Lineage isn't quite ready yet so there's that. But after it's working well, I don't think there will be much of any reason to use ungoogled stock. Some folks have expressed that they like the landscape lock in the stock launcher, so there's that. But I imagine that some sort of landscape lock will probably be added to Lineage at some point.

Well...... yes but not exactly. Lineage is built on the open source portion of Android (AOSP) and the portions of the Qualcomm code that are released as open source (the CodeAurora project, or CAF). The portions that Qualcomm does not release as open source are taken as binary blobs from the stock firmware and integrated into the Lineage build to make a complete package. Because this is a sort of legal gray area, these blobs are kept strictly partitioned from the Lineage project and made available under the github account TheMuppets (really!) The portions t

I have not made one for the Pro1 yet. Not out of complexity or anything, just because it's not needed. The original stock files are made available by FxTec, which is a much easier way to retrieve them than messing with EDL.

I'm not really an OTA expert, but I believe the OTA takes the active slot data plus the patches and applies them to the inactive slot while the device is in use. When complete, it switches the active slot and asks to reboot. There is no such thing as a slot-specific update.

This is one of the nice things about A/B devices. You can root one slot and extract images from the other slot. In the case of an OTA, you can root the older inactive slot and extract the new one. And in any case, if you want a way to read and write the boot partition, I can do that with EDL. I've done it with several devices in the past. Example: https://forum.xda-developers.com/axon-7-mini/development/unlock-tuliptool-unlock-twrp-custom-boot-t3682781 EDIT: Also, I forgot to mention that FxTec has made fastboot packages for stock available, which contain the b

Unfortunately, no. The BSP is proprietary. FxTec has shared the BSP code with a few developers, but it is not generally available. This is one of the reasons that Lineage exists. And please don't get upset at FxTec and IdeaLTE. The bulk of the BSP is licensed to OEMs by Qualcomm. It is only through the generosity and trust in developers that FxTec has made the BSP available to developers at all. They did not need to do this and, in fact, are not really supposed to do it. Also note FxTec and IdeaLTE could release their device code if they chose, but it wouldn't do much good w

I'm not going to try right now, but the short answer is no because the kernel binary is not signed with the device keys, which means the stock kernel modules in /vendor would not load and WiFi would not work. You could work around this by putting the stock kernel binary into my boot image. However, at that point, you may as well use a stock boot image. Additionally, the following things come to mind: The adups properties are not present. This will likely prevent OTA updates from downloading. Which is fine, because: The build is signed with test keys, so recovery will refuse to

I'm not quite sure what you are asking. No, this is not "plain" Android -- it is the full stock BSP build minus adups and gms. The sources are relatively stable at this point. I just did a sync a few minutes ago and there are a couple of recent changes: (1) a fix to the sensors config to avoid a crash when referencing the motion sensor, (2) a fix to the keyboard kernel driver to enable suspend/resume, and (3) a fix to allow storing camera pictures on the sdcard. I'll probably incorporate these into a new build at some point, but they are relatively minor.

I am pleased to announce a new member of the Pro1 ROM family: "Ungoogled Stock". What is it? This is the stock ROM as built from the BSP directly from IdeaLTE with the following changes, and only these changes: Removed AdUps OTA update code. Removed GMS (Google Apps). Where is it? The current version is: http://files.nwwn.com/android/pro1/QX1000-user-nogms-noadups-20191208.zip MD5: 01c90007a843328b869bb294c8f88330 SHA1: 3aff440c50ec2464437c5698bc1c7740ed827c34 Source synced to BSP as of Nov 29, 2019. How do I flash it

Yes, I removed the oldfirehose_base file. That was just for testing. Both of the qfp files linked from the web page have the old firehose now.

I'm a bit confused. I just downloaded the 20191028 file successfully. The index links to the LineageOS page and the Factory Restore page. But if you followed the link in the OP of this thread you should land on the Factory Restore page directly. The links for all the restore files are there and should be working.

Yes the old firehose was verified to work. I updated the main package. Please download a fresh copy and it should work.

My web page answers that, mostly. There are situations where the device must be disassembled to enter EDL, but they are exceedingly rare. Almost always either the PBL will fail to load XBL and panic to EDL (this is what devyl 's device did), or XBL will load and check for the data short on the USB connector that the EDL cable provides. So really you only need to disassemble the device if XBL is functional enough for PBL to load but not functional enough to make it to the USB check.

Oh, and just so everyone knows... This tool and the linked factory packages are meant to do a "normal" factory restore. It does not, by design, reset every single bit that the factory programs. For example, it will not reset the frp partition which contains the boot loader lock flag and the Android factory reset allowed flag. Nor will it reset the radio parameters. Etc. I wrote this tool and I have full access to the underlying capabilities of the programmer. If a normal factory reset does not work, I can generate packages to read and write every single bit on the flash

I'd like to expand on this a bit. If you screw up your device then you are responsible for fixing it. Returning the device to the retailer is bad for several reasons: (1) you screwed up and you are making someone else eat the cost of your mistake which is not cool. (2) the retailer has less incentive to stock the device (and any non-mainstream device generally) because they are seen as less reliable and thus less profitable. (3) the reputation of FxTec suffers. So resist the temptation to take the device back and claim that it "just stopped working". Not only is it un

@devyl I have added the 2019-12-03 package. You can try it to see if it works.

Hard reboot is done by holding the power button down for about 10 to 15 seconds. But I suspect that won't work either. I can make a package for the 20191203 build, perhaps that might work?