yashsingh1/xdaforums huggingface dataset:
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] vladimiroltean:
Ideally, the list of partitions you are restoring at step 1 includes "boot" and "recovery". If it does, then step 2 is no longer needed.

If "fastboot oem lock" is all that you're going to do in fastboot, I think you should be ok. I haven't extensively studied the bootloader code for any hidden traps, though.

Bottom line: don't blame me if anything goes wrong. Scan Lenovo's released source code for calls to send_delete_keys_to_tz.
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] cartman56:
Hi bro can you update the special build? I really like it especially the kernel it so awesomes ☺️
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] Finefeather:
Just another question to the OP. Are you going to update the ROM download link to include the 2 'special' builds because it is not easy to find if it is so deep into the thread.
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] Qscazwdv:
Does this rom also work for the x50f as well.

Please don't put me down or anything. I know how to unlock and flash using fast boot and I know very well how to use twrp but I want to know if this rom will work on the x50f yogatab 3 10 inch not the pro or the plus, thank you. And please for goodness sake dont just ignore me just say yes or no, before you say anything I do know how to root and I am well aware of the dangers of flashing, I'm not an idiot, I also know the dangers of flashing an incorrect firmware.

Will it work. If not why isn't someone on to making the 7.1 for the yt3 x50f
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] vladimiroltean:
Why do you feel the need to point out you're not an idiot on your first post?

The builds in this thread will not work for the YT3-X50F. The SoC architectures are different (msm8976 vs apq8009), so device bring-up is likely to be a lot less straightforward than simply taking the YTX703 sources and changing a few strings here and there.

There are no LineageOS ports for a very simple and obvious reason: nobody made them.

Welcome to the forums.
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] Finefeather:
NO. Read the OP carefully...this is for the Lenovo Yoga Tab 3 Plus, Wifi and LTE versions... only.
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] amphi66:
To ease my mind, is the understanding correct: if one has a full TWRP backup made immediately after the TWRP install w/o other changes, a full "restore" (files + 'image') should work to return to stock? Then a factory restore cleans up the Recovery partition?

A slightly different scenario: if a tablet had been OTA "upgraded" to Android 7.1.2 would the restoration of a full, clean TWRP backup of Android 6.0.1 successfully return it to that version of stock, with the same FR to restore the recovery?

Your experience and knowledge is appreciated!
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] vladimiroltean:
I don't know what it is that you call "factory restore".

There are around 60 partitions on the device. Some of these are unique per-device and are not updated by OTAs (countrycode, persist, userstore etc). You do not need to back these up when you install Lineage, because the process of installing Lineage does not alter them. They are not interesting for this discussion.

Then there are the partitions required by Android: system, data, boot and recovery. You back these up because the process of flashing TWRP/Lineage changes their contents. Of these, it is worth mentioning that the system partition is read-only, and OTA files check for exact, byte-level match against a known checksum. Even mounting the system partition read-only once in TWRP is enough to throw off the checksum that the OTA is expecting, as many of us have painfully come to find out. The data partition, on the other hand, is the main writable partition in Android. It is what holds the application state/pictures/whatever, and reformatting it is what is commonly referred to as "factory reset". That is all that factory reset does. Now I think the Lenovo system partition holds a shadow copy of the recovery image, and under certain circumstances (I forget which, might be on factory reset, might be on every boot), it will also restore it, effectively overwriting TWRP with the stock recovery. If that is your main question, then I don't know, since it's been a long while since I've last seen stock in action. But the takeaway is that restoring system should also restore recovery.

Now there's a third type of partitions among those ~60. They are partitions that are not required by Android, but are specific to Qualcomm's Android implementation. They hold the bootloader and the operating systems for the baseband processor, DSP cores, media codec cores, ARM TrustZone, etc. These are commonly referred to as "firmware". Some quick firmware facts: (1) Lineage does not touch or distribute firmware partitions (2) stock OTAs will update these partitions if they match known checksums (3) TWRP does a poor job at backing these up exhaustively, as they are quite a ****load. For this reason, if you simply restore the Android partitions to Marshmallow but keep the firmware at Nougat, you are walking on uncharted territory, and anything can happen, really (ranging from nothing to everything).

Remember from my post a few pages back that we have a repository on Github for TWRP-flashable firmware images. In the OP only zips compiled for the Nougat firmware are linked, but if you compile your own from GitHub you also get Marshmallow.

You should take my answer as purely informative - if you know your way around, none of these is a real issue.
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] amphi66:
Thanks for the detail response. That helps a lot.

What prompts these questions is what seems strange behavior by the tablet. I actually like it, coming most recently from (actually still using) a Samsung Tab Pro running Resurrection Remix, but am finding some Lenovo difficulty with erratic boots (some apps sometimes do not load or crash) or there are periodic strange lags. Then all seems fine.

I am focusing on either the external 32GB sdCard itself or card management. I haven't quite figured out why Root Explorer shows it empty, but Link2SD has many files installed. Under System/Storage I see just shy of 64 GB of storage (32GB system + 32GB sdCard which is correct), but elsewhere I can only see the internal 32GB minus some use.

Is there special treatment required for the Tab 3 Plus sdCard?
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] vladimiroltean:
Be more specific. Where is "elsewhere"? There is no special treatment that I know of.
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] amphi66:
A 32GB sdCard is formatted to provide expanded storage, NOT removeable to transfer files.

This seems to be supported by Device Storage in System Settings which shows 22.31GB used of 58.16GB available: Internal Shared Storage 20.52 GB used of 29.12GB, SD card 1.8 GB used of 29.04 GB avaialable. So far, so good.

Browsing the file structure in Root Explorer however, only Primary (or 0) storage is shown with 15.31GB used, 8.60GB free.

Attempting to look at /mnt/media_rw (where I would expect the external sdcard) it appears empty with the same storage report as the /mnt folder. No sign of the install files that Link2SD says are stored on the sdCard. I can paste files there, but the storage report still appears incorrect.

That's about as detailed as I can get. Just trying to understand it all.

Thanks
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] vladimiroltean:
By "expanded storage" do you mean the adoptable storage that was introduced in Marshmallow? https://source.android.com/devices/storage/adoptable

If you do, then it's not what you think it is. Google's implementation of adoptable storage does not augment the size of the internal data partition with the size of the external sdcard, but the sdcard merely replaces the data partition altogether. Samsung and basically all other manufacturers of high-end devices were put off by this (and for good reason, since there's no valid use case, if you have >8GB internal storage) and decided to not ship adoptable storage at all in their flagships..
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] amphi66:
So the Yoga's definition of the storage is incorrect. I do not have 32GB internal, plus 32 external. Too bad, but this explains some of the issue. Thanks again.
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] vladimiroltean:
It's not a Yoga thing. You still have both the internal and the external space, it's just that the internal is no longer available for the SDK to use. Reformat the sd card as portable (basically FAT32/exFAT) and you should get your extra space.
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] Finefeather:
I experienced a similar thing with Root explorer on my Huawei Mate 8 with Android 7, and I have stopped using it. I may be wrong here but could it be possible that Root Explorer needs an update? I have the latest Lineage Rom installed...not the one one in the OP...the one linked a few pages back it is... 14.1-20180407... and I must say this ROM is really good. So far I have had no problems generally except for the build in video player, but I am going to try a different one soon. I am happy with this rom and won't be downgrading. Maybe we will see an Oreo version soon :)
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] amphi66:
Thanks. I have just finished wiping the tab and was drafting an eBay ad. At the moment I have a clean, factory reset stock (awaiting setup), but with TWRP Recovery. Not sure it makes sense to flash stock recovery.

I did find the advice to reformat the sdCard as portable resolved my (operator error) mis-understanding of how the Yoga 3 Plus handled storage. Still having issues with crashing apps and an inability to change the default video player. Will try a clean flash again.
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] Finefeather:
I have been using this ROM for a while and the most annoying thing about it for me is the Cast option, which is found in the Screen settings. It does not want to connect to my TV for screen casting.

I even flashed the stock 7.1.1 ROM and it works perfectly there.

Was hoping that [MENTION=7398554]vladimiroltean[/MENTION] could look at this. This problem is going to force me to stick with the stock Nougat rom because I use screen casting often with my other devices...and it is an essential feature these days. I have a smart TV and so use it a lot.

Any chance of looking at this please...
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] vladimiroltean:
Ok, since I don't have a TV, I'll borrow my parents' Chromecast for performing tests. Thanks for reporting.
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] Finefeather:
Thanks you are a star and a gentleman :) Will install when you find the answer and give feedback. This ROM is otherwise streets ahead of the stock rom and I can't wait to reinstall Lineage again.

---------- Post added at 07:06 PM ---------- Previous post was at 06:54 PM ----------

I think I need to tell you that I have been using your last rom which you posted...(lineage-14.1-20180407-UNOFFICIAL-YTX703F)...I don't know if the OP version works but this one is the latest and works well for me. I do not know what the differences are...but you sure do...so will you be changing the version linked in the OP?

Thanks again...:good:
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] vladimiroltean:
You don't need to bother. If the latest build is broken it'll need fixing anyway. Only if the fix is not trivial (which I should be able to find out soon if it is) should we go looking for an archive build that works.
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] waleed.star99:
i hope u could create stable rom for daily use ASAP and hurry up porting android 8 :)
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] vladimiroltean:
I don't want to be thick, but I am able to cast using the tablet as a Miracast source, and another Android device as a Miracast sink (using the "WiFi-Display(miracast) sink" app by SOHO Nishikawa). I'm going to try out Chromecast too as soon as I get it.

What are you trying to stream, and what is the smart TV model?
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] Finefeather:
Yes I know that app but it does not cast to a TV.

On the Lineage Display settings screen at the bottom there is a "Cast" option, There is a drop down box on the top right of this cast option....when pressed it says "Enable wireless display" and has a tick box to enable it. If you have turned on casting on the TV the TV is shown on this screen and if you select it it connects with the TV...which is connected to the same WIfi channel as the tablet. Now on the Stock 7.1.1 Rom it connects fine and you can cast and mirror everything from the tablet to the TV....but on the Lineage Rom it does see and detect my TV, the same as the stock rom but when i select it to connect it just does not connect...it just brings up one of those round about connecting png icons and never connects. I am connected to the same wifi network. On the Lineage rom I can see all the Smart TVs which are casting. My TV is a Hisense Smart TV which has Netflix, Youtube etc build into the smart part. We also have Chromecast on the other non smart TV and this built in Stock cast feature works fine with both, without any other app on the tablet. My Huawei has the feature called "MirrorShare" whch is identical, just another name.

When this did not work I first tried quite a few of the casting/mirroring apps in the app store but none worked.

Thanks and keeping fingers crossed....:)

---------- Post added at 12:23 AM ---------- Previous post was at 12:18 AM ----------

@vladimiroltean just a suggestion, but if you trace the source code in that area of the 2 roms you might be able to see the difference....between the stock rom and the lineage rom...
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] vladimiroltean:
I think you're going to be in for a big surprise if I tell you that we don't have source code for the stock ROM. So your suggestion won't work.

But back to Miracast/Google cast. I know you said "Yes I know that app but it does not cast to a TV", but I doubt you understood my testing scenario, since the app is not even *supposed* to cast to a TV. It turns Android into a Miracast *sink*, basically the equivalent of a smart TV.

In my test, your smart TV is my Nexus 7 (since I don't have a TV, as stated).

And since having the YTX703 as a Miracast source works for me, it should also work for you, I reckon. As long as we get different results, we should iron out the differences in testing environments until we can at least agree if it should or shouldn't work.

If the Chromecast works for me too (which you're saying it doesn't work for you), I'm going to ask you for the output of "logcat" taken immediately after your noticed failure to connect.
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] Finefeather:
I understand exactly what you are saying. I have connected 2 of my devices with this app and it works fine except for the screen resolution which is not good because of the choices on the app. However there is no place to connect on the peer device if the peer device is a TV. A smart TV connects to a WiFi with a password which is not available to enter in the TV. This app works like Bluetooth, you just give it the ok. Anyway when you try it on Chromecast you'll get what I'm trying to say? of course I'll be very interested if you can get it to work on Chromecast. Till then take care.... I'm off to sleep now here in south Africa ?
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] Finefeather:
[MENTION=7398554]vladimiroltean[/MENTION] Hi this is a logcat of the cast problem. This is the first time I have done this and so if it's not correct please let me know...I tried to capture the log and immediately saved it after the problem...

If you search the log you will find 2 TVs shown in the log... "Smart TV" and "Den TV". The "Den TV" has chromecast and the "Smart TV" is the Hisense. I can access any of these with any of our 4 android phones without installing any apps. Android has a built in Cast/Mirror function on all these phones, they are named differently by phone makes. I have re installed Lineage 14.1 - 7.1.2 and it detects both of our TVs using the Cast option in the Display settings screen, but when I select one it starts to connect but after a few second it just stops and for a while the selected TV is removed from the cast screen...in a few seconds it re detects it. I do not know much about android but reading the log it seems to me that it has some problem with the wifi...but I am not qualified to make any real diagnosis.

https://1drv.ms/f/s!AkEE1n-K7QEfmUKqvQfgOPqlnnZq
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] vladimiroltean:
Thanks for the log. This is weird, but for me, casting to Chromecast works just fine. I'm looking at your log, and it indeed appears that the cause of your Wi-Fi Display failing is that your p2p interface goes down immediately after the association process.

I do not have an explanation for it. I will also try to cast to one of the TV's at work tomorrow.

In the meantime, the "popular wisdom" on the LineageOS review board seems to be to put "p2p_no_group_iface=1" in /system/etc/wifi/p2p_supplicant_overlay.conf.

Keeping in mind that (1) I don't have a satisfactory explanation on what this change might affect and why (2) until I can reproduce the problem, this is just a Hail Mary; here's a TWRP zip that will perform said change for you. Let me know if it changes anything for the better (it shouldn't break anything).
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] Finefeather:
This is not working. It does seem to try to connect to my smart tv a little longer but then it aborts as usual. I think I may have misled you a little, or not given you enough, because I can connect to Chromecast and Chromecast is not the issue it is Smart TVs which have the Miracast protocol which fail. I have been searching around and have found this same problem mentioned with Lineage roms quite a few times. It seems as if Lineage has taken the route to not support Miracast technology because raw android, being google, may want to herd people towards Chromecast. So Miracast is different to Chromecast and Android does support it because most phones I have used lately have it, maybe it just needs to be enabled or a driver added. Anyway Lenovo stock rom definitely connects to both Chromecast and Miracast and my Hisense TV seems to be Miracast. It seems than most people are not aware of these 2 protocols and casting is not just casting. I have linked a few things for your info.

https://jira.lineageos.org/browse/BUGBASH-33?attachmentOrder=desc

https://xdaforums.com/galaxy-s2/development-derivatives/rom-cm14-unstable-t3465152/page98

https://rootmygalaxy.net/how-to-enable-miracast-on-moto-z-play/
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] vladimiroltean:
No, that is nonsense. AOSP supports Wi-Fi Display (Miracast) at the framework level, and LineageOS, being an AOSP derivative, also supports Wi-Fi Display at the framework level. That being said, actual device support comes down to the individual device maintainers (us), and depends on a lot of support from the SoC. But if it works in stock, it should work in Lineage too, no question about it.

It is funny considering the experiments I've done today with the TV at work (LG webOS.TV UJ670V - Miracast). I was close to reproducing your issue: without the p2p fixup patch, the Wi-Fi connection to the TV would drop the first 3 times or so. But then it worked the 4th time, and did not disconnect again. With the p2p fixup patch, it never failed.

Plus, Chromecast never failed (we get same results there), and connecting to an Android tablet as a Miracast sink also never crashed.

At this point, I think it's easiest I do one more YTX703F clean build for you to test, to make absolute sure we're running on the same codebase (to explain why we're seeing different results). Stay tuned.
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] Finefeather:
Well that was interesting. However, This problem ONLY comes up with the Lineage ROM. When I flash the Stock 7.1.1 ROM it works perfectly on this TV, and every other Android phone in our house works perfectly on this TV...We have a Huawei Mate 8, A Samsung S6, An LG G3 and they all work perfectly, so I cannot understand your reference to HDCP... But I have also been searching and found a supposed fix...which does not work either, which is adding "wlan.wfd.hdcp = disable" to the build.prop...whatever that may be :confused: But my problem is I do not know enough Linux to get too deep into this like you.

I am going to flash this rom tomorrow and see if it works...it is Nougat 7.1.1 and they do have the source code available which might be of interest to you if it works.

https://xdaforums.com/android/development/rom-unofficial-resurrectionremix-lenovo-t3583143

I did see your name pop up in one of the posts so maybe you know this rom and can warn me if it will break anything before I flash it :)

Also I do have Magisk installed now on your rom and it works great, but the problem was there before I installed Magisk.

Thanks for your efforts this far...take care...
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] vladimiroltean:
I haven't run Resurrection Remix, although I don't expect the results to be any different, since it's most likely based on our sources.

Do you have any custom ROMs where Miracast to that particular TV works? Or just stock ROMs? I admit this is the first time I'm being faced with a HDCP TV.
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] Finefeather:
No at the moment I only have this Lenovo tab I am customizing...I have done hundreds of phones and Tabs before with CM but just recently cleaned up my drives. All our phones are stock now.

---------- Post added at 10:30 PM ---------- Previous post was at 09:54 PM ----------

I flashed the RR rom and I can't even get past the Setup Wizard which just keeps closing. So aborting that. Will try again tomorrow...
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] NY1M6gTOR3Rj6AGKXTcx:
I still have a problem playing local h264 videos with the latest experimental ROM. I now went back to a build from March 2017 where video playback is flawless.
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] vladimiroltean:
Understood. [MENTION=4490861]Finefeather[/MENTION]'s WFD logs also exhibit some breakage around the h264 codecs, so I think it's safe to assume that there's something fishy around there.
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] NY1M6gTOR3Rj6AGKXTcx:
Could this be related to the latest firmware?
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] torrezea:
Dude

There will be a future rom for the version x50F 10.1 2GB? Thank you!
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] vladimiroltean:
Dude

Coming from me? No.

But I cannot predict the future. If somebody else makes it happen (perhaps even you), then why not.
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] vladimiroltean:
FYI, [MENTION=7107043]NY1M6gTOR3Rj6AGKXTcx[/MENTION], I cannot reproduce any local playback issues for h264 videos. Tested with "Gravity - 2K Trailer" from http://www.h264info.com/clips.html.

If you want debugging to proceed smoothly going forward, please tell me which video and player application you are having issues with.
[Lenovo Yoga Tab 3 Plus ROMs, Kernels, Recoveries, ] janforman:
Video acceleration won't work for me too, so I downgraded to previous version of LOS lineage-14.1-20180224-UNOFFICIAL-YTX703F.

So there must be something strange, I tried many times. Complete cleanup, flash image, flash GApps nothing more.

Nothing works it's not related to specific video. I have 64GB version with 4GB RAM (this version have slightly different motherboard maybe it's it).