I used this too as a base to extract the kernel etc for patching. I'm surprised that its such a good tool from the manufacturer. It will recover your tablet from just about any state except an actual hardware fault.
I am trying to install stock ROM by using smart assistant. I am in third step, connecting the device by pressing volume up no response at all .. any idea? Edit: I purchased a brand new cable problem solved. For anyone experimenting with custom ROMs please make sure you are using quality cableThis is a great way.
IF you are certain you only erased the vendor partition, you can also find the latest stock vendor image file and flash it using TWRP. There is a website for downloading the stock firmware but I can't remember its name.
smart assistant is the best to get back to a working device. I've used it several times.
I installed again stock ROM then twrp, I didn't make any wipe just install at system image but I got error again regarding custom ROMNo, no, no. You don't wipe any partitions. You need the Lenovo firmware vendor partition to be there. I don't even wipe the data partition, and have had no problem. Treble firmware only works if every partition, except for system, is stock. I suggest you restore all of the Lenovo firmware via TWRP and reboot to make certain it still works. Then you can reboot to TWRP and follow my suggested steps.
Magisk is not required, but I use it.
Hey, it took me long to get to this backlog, but still no good news for you - the logs don't really ring any bells to me, and I was unable to replicate it on Samsung (Galaxy Quantum2) or not (OnePlus 11). I'll put this aside until another example pops up, sorry about that.
Have you tried installing Magisk 26.1 (available at https://github.com/topjohnwu/Magisk ? It solves a lot of compatibility problems.
Make sure you got the right image. On your tablet, the td based images are the only ones that will work from here:
Cheers mate. Well what I actually did and worked was:
Yes I know, I only use bgnMake sure you got the right image. On your tablet, the td based images are the only ones that will work from here:
The `lineage-20-light` ones will not work.
Glad it worked. After lineage stabilizes a day or so, you might try restoring your older data from TWRP (backup your current data first). This method has worked a couple of times for me.
If not a bug fix, then how about a workaround that let's the ROM boot without factory reset? Even if the logs don't indicate the cause, you could surely see that it was stuck in the booting process.Hey, it took me long to get to this backlog, but still no good news for you - the logs don't really ring any bells to me, and I was unable to replicate it on Samsung (Galaxy Quantum2) or not (OnePlus 11). I'll put this aside until another example pops up, sorry about that.
Use a different launcher. Lineage inbuilt launcher is trash, Trebuchet or whatever it's called. But I think this LOS uses a modified AOSP QuickStep launcher, instead of Trebuchet. No difference, QuickStep is just as bad. I personally use Nova, no issues with folders there. Installing Nova is one of the 1st things I do after a clean boot of any new gsi.Hello,
I'm new to GSIs and installed the light version (bgN) on my Tablet (Lenovo TB-J716F). Everything works nice but I get the warning "this device is not play protect certified", so I tried installing the TD-Version which works fine except for how the folder is displayed? I also can't set a folder name.
View attachment 5931209
Does someone know how to solve this?
Use a different launcher. Lineage inbuilt launcher is trash, Trebuchet or whatever it's called. But I think this LOS uses a modified AOSP QuickStep launcher, instead of Trebuchet. No difference, QuickStep is just as bad. I personally use Nova, no issues with folders there. Installing Nova is one of the 1st things I do after a clean boot of any new gsi.
Flashing recovery should never need the repartition option anyway. And it's best to not use repartition unless you really have to, you could brick the device.
I can't answer that for you, it's your decision. Fingerprint has lately been working fine for me on gsis. But every gsi is different, every device is different. The installed underlying firmware can play a big role too. So there are no guarantees. If stock is working better for you overall, i'd say go back to it. My gsi experiences have been mostly good, but it won't be so rosy for everyone else.
Issues powering off from where? TWRP? Android?Evening all, I have the latest BVN A64 Andy Yan image installed on my SM-T510 after initially following MagenDanz' guide including his version of TWRP but am still having issues with powering the device off? Also I am unable to install magisk
I get an error stating " Failed to mount system_root, I have flashed multi disabler previously in TWRP
Thanks in advance
Try another gsi. Probably same behavior on others though, most gsis share a lot of source code. If a bug exists in one, it's probably also in others released around the same date. But some bugs/issues are device-specific. Not much you can do except file a bug report and wait.
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.
rm -rf external/chromium-webview/prebuilt/* rm -rf .repo/projects/external/chromium-webview/prebuilt/* rm -rf .repo/project-objects/LineageOS/android_external_chromium-webview_prebuilt_*