Database Users

Unable to install 4.2.2 upodate

I have clockworkmod recovery installed and when I install the update it fails. Cannot remember the error sorry. Why is this happening. Here is a screenshot my about phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using xda app-developers app

Here is the error I am getting.
sent from my nexus 4 using google mind control

The OTA installer checks every single file it intends to patch before anything happens.
If a single file that is checked has been changed by even one byte, not one patch operation will occur.
The message you are getting means you did something to change or remove that file compared to how it was in the stock ROM.
Note that the installer halts on the first error of this type; there could be zero or many more of these errors awaiting you.
In short, OTAs are not meant for patching random non-Stock ROMs.

I installed beats from play store. Gutted. Just backing up all my data and gonna factory reset and try again
sent from my nexus 4 using google mind control

R: Unable to install 4.2.2 upodate
I had error 7 with TWRP recovery. Then I installed clockworkmod and it worked.
Nexus 7 3G - Tapatalk

Androll79 said:
I have clockworkmod recovery installed and when I install the update it fails. Cannot remember the error sorry. Why is this happening. Here is a screenshot my about phoneView attachment 1728828
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i have the same problem.but i flash stock recovery with WugFresh toolkit and wait until OTA update notification.and you will get your android running 4.2.2 version.

Odp: Unable to install 4.2.2 upodate
Guys, guys, guys. You need STOCK recovery for official updates.
Sent from my BMW E34 using XDA App

I searched many threads when I rooted and unlocked my Nexus 7 3g, to avoid this "status 7" problem.
I chose Wug´s nexus toolkit, unlocked and rooted my device. After that, I installed, via toolkit, the TWRP recovery.
When I received the system update notification, my device asked me to reboot, then a screen of TWRP appeared to me. I just rebooted the system and now, without update, I don´t even get the message again.
I assume that the Wug´s toolkit flashed a grouper version of TWRP. What I have to do now ? I would like to do the things manually. Maybe flash a factory image from here with this method.
I´m very noob with this kind of thing, because I still have a old milestone 2 with a locked bootloader. The method to flash ROM in milestone 2 is quite different...
Anybody can help me ?

There is modified OTA floating somewhere that skips check, worked for me since it reported that GoogleCalendar.apk was different than it should be....

Folks,
You need to stare at the actual error message.
If the failed assert() is complaining about a file (e.g. see the OP's 2nd image attachment) then THAT FILE IS THE PROBLEM. It means that it was altered or removed by a root-privileged operator from the way it was in the stock ROM.
If the failed assert is complaining about a build number, then it is possible that using a different recovery will allow the OTA to succeed.
So you have a couple of choices:
A) Go and find the stock version of the file and put it back into your ROM (with the correct file ownership and permission modes) and repeat the OTA install. Seems like a dumb idea though, as the installer stops on the first error encountered - you will need to keep repeating this process until you have restored all changed files. Could be only one file, could be a few, could be many. Note also that this applies to the boot image, too. Got a custom kernel? You'll need to put the stock boot image back in place, too.
B) Back up your apps using TiB or Carbon. While you are at it, take a nandroid backup too. Install the Factory 4.2.2 ROM, reinstall your fave custom recovery, and root the factory ROM. Boot it up, enter your Google creds, restore your apps & data (Carbon or TiB). Yep, you are gonna have to redo your homescreens. Big deal; that's something you would do anyway when hopping between ROMs (unless you have this covered already by using a non-stock Home/Launcher app which has its' own backup/restore capability)
C) Just wait a little bit - your ROM Dev will probably release a version based on 4.2.2. At that time you can do some stupid thing like overflashing the replacement ROM without wiping.
Unless you know exactly what you are doing, running a modified OTA with *all checks* suppressed is a seriously brain-dead idea. (Removing only the build version check should allow alternate recovery use - but for goodness sake, the OTA nukes the recovery anyway, so what's the big deal about putting the 4.2.1 stock recovery back in place ahead of the OTA?)
Look, running the Stock OTA is going to remove your recovery and very likely disable your root. You are going to need to put your recovery back and re-root anyway. Doing things the right way is barely more effort than what you are going to need to do the crufty way.
good luck

Moto G4 XT1625 Nougat OTA (crazy?) Error

Hello hello,
First time poster as I don't know crap to help folks since I'm just learning *ahem*, and I've come across an issue that has me completely stumped with a recently purchased refurbished Moto G4...
([Edit/Update]: So apparently new users can't embed links, and so it appears that my Imgur photos are also not posting...?)
TLDR: OTA to Nougat refuses to install on XT1625...because Consumer Celluar?
So here's the long version... Bought a refurbished Moto G4 XT1625 (not amazon) with the intention of using it as a learning aid for unlocking, rooting, etc.
Unlocked the bootloader, flashed TWRP, backed up, rooted via Magisk, backed up. After a couple days, up pops the OTA notification. "Yay" I thought. Then "Oh wait, I heard root + OTA can be difficult". So I read. A lot.
Fast forward and of course the OTA failed when I just accepted it. However, I captured the file, pulled up the stock ROM download from the official Moto website after checking that the build numbers matched, and proceeded to unroot and reflash that stock ROM (except for bootloader and gpt files). I booted back up, got the notification again, and hit OK. Fail. So I booted into recovery and tried to sideload OTA (using "Blur_Version.24.31.65.athene.retail.en.US.zip" pulled from "com.motorola.ccc.ota-20171028-062630.tar.gz"). Fail.
Maybe somehow I misread the multiple how-tos out there, and I'm screwing something up in the process here?
After numerous rinse and repeats of the above steps, I cannot for the life of me get past this damn error which (assuming my inexperienced eyes are reading it properly) seems to say that the current CCMyConsumer.apk on my phone is somehow wrong (corrupted/incorrect/missing?), and so the OTA's response to me is a big FU.
Verifying current system...
E3005: "/oem/app/CCMyConsumer/CCMyConsumer.apk" has unexpected contents.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This seems.......weird to me? If I have both the stock ROM and am using the actual OTA, why would a random provider's app be screwed up, much less screwing up the update.
Also, if it matters at all, here's that particular directory tree in a file manager...an apk file doesn't appear to even be there?
Could a lack of existence be the "unexpected contents?"
So, the question as in the TLDR, any ideas on what the cause or solution to this error or overall OTA issue could be? I'm at a loss.
The only other item I noticed is that my "Settings" now crashes if I attempt to navigate into "Apps" within its menu. However, if I navigate directly into an App's info page via the app drawer, I can access those. Not saying this is related, I have no idea, but being the only other oddity, and since it persists through flashes, I figured I'd mention it (even if unrelated, I am still curious what could be going on there too...).
Thanks in advance for any help, education, or peace of mind. =P

NobodyByChoice said:
Hello hello,
First time poster as I don't know crap to help folks since I'm just learning *ahem*, and I've come across an issue that has me completely stumped with a recently purchased refurbished Moto G4...
([Edit/Update]: So apparently new users can't embed links, and so it appears that my Imgur photos are also not posting...?)
Unlocked the bootloader, flashed TWRP, backed up, rooted via Magisk, backed up. After a couple days, up pops the OTA notification. "Yay" I thought. Then "Oh wait, I heard root + OTA can be difficult". So I read. A lot.
Fast forward and of course the OTA failed when I just accepted it.
Click to expand...
Click to collapse
Do you still have TWRP installed? You cannot flash an OTA update with TWRP installed. You'll have to find and flash the original Nougat ROM which will remove TWRP. Then accept the OTA update and let it install. Then, if you need TWRP, flash it again. I know because I was in the same boat when I accidentally accepted the OTA update with the Sept security patch and it screwed up my phone (XT1625) royally. Check out this thread which describes my process.
https://forum.xda-developers.com/mo...boots-twrp-t3701768/post74463378#post74463378
Link to XT1625 firmware: https://androidfilehost.com/?fid=673368273298984458

lmacmil said:
Do you still have TWRP installed? You cannot flash an OTA update with TWRP installed. You'll have to find and flash the original Nougat ROM which will remove TWRP. Then accept the OTA update and let it install. Then, if you need TWRP, flash it again. I know because I was in the same boat when I accidentally accepted the OTA update with the Sept security patch and it screwed up my phone (XT1625) royally. Check out this thread which describes my process.
https://forum.xda-developers.com/mo...boots-twrp-t3701768/post74463378#post74463378
Link to XT1625 firmware: https://androidfilehost.com/?fid=673368273298984458
Click to expand...
Click to collapse
Thanks for the advice, sorry for the late reply as I was out of the country. I do understand the need to get rid of TWRP first, but I'll read through your recommended threads and see what happens!

[TOOL][PIXEL XL] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)

This is the Pixel's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​

Amazing work! EVERY ONE OF US NEEDS TO LEARN command line, but it's always excellent to see amazing devs make an all in one like this for the guys that refuse to learn the hard (right) way, and for vets that aren't quite smart enough to make a tool like this themselves, like me, but appreciate the **** out of this little gem making my first custom Oreo ROM from stock rooted a breeze! Perhaps a little bold, but im still calling it, OG PIXEL XL NOT DEAD just when I was losing faith! Bravo!
PS:. Donation incoming once my current "being a broke ass" sit-e-ation ends here in a few weeks.

awareunlikeu said:
Amazing work! EVERY ONE OF US NEEDS TO LEARN command line, but it's always excellent to see amazing devs make an all in one like this for the guys that refuse to learn the hard (right) way, and for vets that aren't quite smart enough to make a tool like this themselves, like me, but appreciate the **** out of this little gem making my first custom Oreo ROM from stock rooted a breeze! Perhaps a little bold, but im still calling it, OG PIXEL XL NOT DEAD just when I was losing faith! Bravo!
Click to expand...
Click to collapse
Thanks, all need to learn command line, but this tool help a lot, the advanced options are really good too, see it when you have some time

mauronofrio said:
Thanks, all need to learn command line, but this tool help a lot, the advanced options are really good too, see it when you have some time
Click to expand...
Click to collapse
Just peeped them briefly,. Mad props!

Damn dude, this is amazing. Will definitely give it a shot in the next few days!
Question about the install/uninstall apks feature: how does this work? Is it batch or one at a time?
EDIT: Also, to flash TWRP, do I need to be in bootloader mode and do I need to disable security on my phone before flashing? Will I lose root when flashing it? I'm using the latest Magisk.
Sent from my Google Pixel XL using XDA Labs

Finally i got a solution for Nexus and Pixel Factory Image flash, now it works perfectly

Thank. I've been using the Unified Android Toolkit from Skipsoft for a while now, but a lot of functions are blocked. I'll give this a go.

tutusinghsohi said:
Thank. I've been using the Unified Android Toolkit from Skipsoft for a while now, but a lot of functions are blocked. I'll give this a go.
Click to expand...
Click to collapse
Thanks, remember to give me a feedback

I saw now that i forgot to unlock the flash factory image option for all 4 Pixel, i have released an update to solve that, tell me if it works

I'm running purenexus 7.1 ROM and would like to go to Oreo stock but retain root. Is this the right tool for me?

l2yangop said:
I'm running purenexus 7.1 ROM and would like to go to Oreo stock but retain root. Is this the right tool for me?
Click to expand...
Click to collapse
You can't retain root after flashing a factory image. You can root the oreo factory image after you have flashed it

I take it this is for windows only?

Thanks
Thanks for this toolkit
My phone was loop in no command screen . And you save me
I have questions about this toolkit
- can I use it to flash any custom rom or just original image
- can I root my phone with toolkit
- there is another virgin of toolkit can be use in a pixel book
Best wishes,

Ahmad Alsaeed said:
Thanks for this toolkit
My phone was loop in no command screen . And you save me
I have questions about this toolkit
- can I use it to flash any custom rom or just original image
- can I root my phone with toolkit
- there is another virgin of toolkit can be use in a pixel book
Best wishes,
Click to expand...
Click to collapse
You can't directly flash a custom rom with this tool, you need a TWRP already flashed on your phone and you can use "Recovery Zip Flasher" ( I do not recommend it ), i think is better to put the rom on your phone and flash it from your phone.
This tool can't root directly your phone, but gives all you need to root it (Bootloader Unlock and the flash of a TWRP).
Pixel book? This tool is only available for Windows, maybe you can use it on pixelbook with a virtual machine, but i don't know how pixel book works

With the new update a i make a new recovery flasher option for devices with project treble. Test it and told me if it works

Deleted

does this still work?

eightieskhild said:
does this still work?
Click to expand...
Click to collapse
Yes

This is a virus... how is this on XDA?
Trojan:Win32/Spursint.F!cl

revamper said:
This is a virus... how is this on XDA?
Trojan:Win32/Spursint.F!cl
Click to expand...
Click to collapse
This is not a virus, it's a false positive
https://www.virustotal.com/#/file/8...596c988acd17efa83f70e691c3d1ad7d2ff/detection
as usual, you need to breath your mouth without knowing what you're talking about

Boost E4 1766 Only Boots to TWRP

-Screwed up somewhere as my goal was to install LineageOS and try to use it on an At&t mvno.
-Package was unopened for months, so it still had the older firmware.
-Everything seemed okay after I unlocked the bootloader.
-Then I installed TWRP.
-Did a backup of everything using TWRP before I was going to try and root the device.
-I knew something was wrong when no verity opt encrypt and Magisk gave some error message and failed.
-Now whenever I boot the device, I get a N/A in the top left corner and then goes into TWRP.
-Restoring the backup using TWRP did nothing.
-I thought this would be the solution (dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1M), but I get the bad key first and then N/A before going back to TWRP.
https://forum.xda-developers.com/moto-e4/help/moto-e4-metro-variant-rebooting-to-twrp-t3825841
What should I do now?
Any help would be appreciated. Even links to other posts that dealt with this issue is fine. Be aware that my skill level is only a little better than following Youtube videos.
Thank you.

N/A is normal. It will be there forever after you unlock bootloader. Did you format data in TWRP and type yes to format?

Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.

ah-le-le said:
Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.
Click to expand...
Click to collapse
once you flash TWRP you have to flash a no verity zip and probably magisk and definitely format data to remove encryption for your phone to boot.

Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ah-le-le said:
Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
Click to expand...
Click to collapse
I can't read that, LoL. Maybe... Failed toount data? That's because you're still encrypted.
Put the zips on external storage. Format data, type yes.
Now reboot recovery (not system) then flash the zips.
And you can take screenshots in TWRP.

Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.

One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.

ah-le-le said:
Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.
Click to expand...
Click to collapse
ah-le-le said:
One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.
Click to expand...
Click to collapse
Use caution going with a custom ROM on this device, especially with a mvno. You may score far more hurt than benefit. Also consider what you are trying to accomplished going with custom ROMs given the clean stability of Moto stock ROMs. Toss in Xposed framework and a few modules like Gravitybox for full control/customization.
OTA updates can not be processed with a custom recovery (one of several prerequisites that your device no longer meets). You may get notified but the update won't install; you'll be dumped into TWRP. You can easily disable the update engine and corresponding notifications on a rooted device.

Lineage OS 17.1 Post Installation Issues

Hi
I recently completed installing official LineageOS 17 on my 6T using TWRP, not the recovery on Lineage wiki page. Restarted the phone a few times and playing with it for a couple of days. Things seem to be working well. I do have a few doubts though:-
(1) About the A/B partition thing. I did a simple wipe prior to installation and I am not sure I have installed it on the correct partition. How can I check to make sure ? Can I copy partitions now and if so, how ?
(2) I do not plan to use payment apps on the phone but I do plan to use the protonmail apk which I have already installed. How safe is it to leave the bootloader unlocked especially when the "Automatic System Updates" is on ?
Thanks

1. There is no wrong partition. Every update / installs will alternate between A/B partition. If it boots don't worry about it.
2. You can't lock the boot loader unless you make your own build and sign it. So it must remain unlocked. There is a guide for doing this if you want in the guide section.

OhioYJ said:
1. There is no wrong partition. Every update / installs will alternate between A/B partition. If it boots don't worry about it.
Click to expand...
Click to collapse
Thanks so much for allaying my fears. I read somewhere that in case of issue with Lineage partition, the mobile will try to boot up the other partition which might have older version of Android OS, causing a brick.
I was thinking of configuring my gmail account on the stock email app and was apprehensive that an unlocked bootloader might cause a safety block from Google.

anuk221 said:
Thanks so much for allaying my fears. I read somewhere that in case of issue with Lineage partition, the mobile will try to boot up the other partition which might have older version of Android OS, causing a brick.
I was thinking of configuring my gmail account on the stock email app and was apprehensive that an unlocked bootloader might cause a safety block from Google.
Click to expand...
Click to collapse
On a clean / first install of Lineage you would typically install it twice to get it on both A/B partitions. The other option is to use the copy partitions zip. The zip is mentioned in the Lineage wiki I believe
It's not a safety block, you just will come up as not certified, which likely is already the case. This will not cause you any problems other than certain apps won't appear in the play store. (Such as Netflix, things like that).
I have a installing Lineage guide here. See the section on Magisk about getting the device to be certified again. There is a cliff notes version in the second post as well, you can see my Install method and update method.
The other partition would only try and boot if Lineage failed to boot. If you didnt install it twice, it would be an easy fix now to just install it again, or use the copy partitions zip. Usually I just update or install without worry, but I would backup just to be safe in this case since your steps are a little out of order. Always better to be safe than sorry.

OhioYJ said:
I have a installing Lineage guide here. See the section on Magisk about getting the device to be certified again. There is a cliff notes version in the second post as well, you can see my Install method and update method.
Click to expand...
Click to collapse
Thanks for the link. I had checked your guide amongst others prior to installation.
I was getting the following startup screen on boot and it didnt lead into TWRP recovery or bootloader even when I used the "volume up+power" combination at startup :-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Which is what led me to think that I hadnt done a clean/proper install. I had used "Tool ALL IN One" to unlock the bootloader and I had deviated from wiki and gone the TWRP route for recovery since I was not sure if selecting "Apply Update" in recovery and then "Apply from ADB" would work.
Anyways, I redid the whole thing again last night using Lineage OS recovery. I still get the above screen at startup but now when I select the power button, it takes me into LineageOS recovery.
Again everything seems to be working well prima facie, except that this time when I insert a Sandisk USB C Dual Drive, I get a message "Issue with Sandisk USB Drive. Tap to fix". The drive works fine on my 8T !

anuk221 said:
Thanks for the link. I had checked your guide amongst others prior to installation.
Click to expand...
Click to collapse
Different devices have different kernels with different things enabled / disabled, giving them different capabilities. Honestly I've never tried thumb drives on my phones, I guess I could try one on my 6T and 8T and see what I get later. I'll see if I can find an adapter cable, as I don't have a USB C drive.
You do have to let go of the power button for a moment to get into fastboot. It will pause when it gets to that bootloader unlocked screen. At least that's always been my experience.
Every time you install LOS on the 6T it replaces TWRP with LOS recovery. TWRP must be re-flashed everytime if that's what you prefer to use. That's why that step is in my guide.

OhioYJ said:
Different devices have different kernels with different things enabled / disabled, giving them different capabilities.
Click to expand...
Click to collapse
That is correct. The drive in question is a 64GB drive formatted in exFAT. I tried another drive, 32GB formatted in NTFS and it was being detected by both the 6T and the 8T ! Probably an issue with the exFAT kernels as you pointed out.
I am surprised though that some very basic features which I had assumed would be available seem to be missing - No option of ungrouping/declubbing sms conversations, no option of exporting to SIM, no option of getting timestamp in call log. In that sense LOS appears to be more of a de-googled version of android than a standalone OS.