All right
so you can't install stock ROM with twrp the only way is through Lenovo rescue and smart assistant?
[GSI][13] LineageOS 20 TrebleDroid-based
- Thread starter AndyYan
- Start date
so you can't install stock ROM with twrp the only way is through Lenovo rescue and smart assistant?
This 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.
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 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.
kevinco1
Senior Member
Does your device have a Unisoc processor?
If so, this issue has been fixed with the latest PHH build. Just waiting for the next LOS 20 build to be released with the fix integrated
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 cable
Last edited:
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 ROM
Last edited:
See the image edit problem solved changed the SD card use a trusted one! Edit 2. I am stack at leneage logo for a half an hour at a first boot... SNAFU (Situation Normal All Fu$_&#d Up)
edit problem solved changed the SD card use a trusted one! Edit 2. I am stack at leneage logo for a half an hour at a first boot... SNAFU (Situation Normal All Fu$_&#d Up)Attachments
Last edited:
I am stuck at first boot leneage logo for more than an hour, not normal. I would be very grateful if someone please explain the steps I need to follow in order to flash effectively that particular custom ROM please 
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.I am stuck at first boot leneage logo for more than an hour, not normal. I would be very grateful if someone please explain the steps I need to follow in order to flash effectively that particular custom ROM please
Make 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.
Cheers mate. Well what I actually did and worked was:
1) wipe: cache, dalvik, data, system, internal storage
2) format data
3) install leneage from SD card
4) reboot
And it worked like charm
Last edited:
YesMake 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.
I know, I only use bgn
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.Cheers mate. Well what I actually did and worked was:
1) wipe: cache, dalvik, data, system, internal storage
2) format data
3) install leneage from SD card
4) reboot
And it worked like charm
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.
Or maybe I should submit this bug to phh.
I can give you another example, the behavior is exactly the same on 2 of my devices. I only submitted the logs for one because I use it more often, and encountered it there first. I guarantee you, I'm the first one to submit a report on this, the chances of it being independently reported by someone else are slim to none.
Last edited:
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.
Does someone know how to solve this?
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.
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.
kevinco1
Senior Member
Agreed on the Nova suggestion, been using it for 5+ years and haven't looked back
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
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.
Yes, flash recovery in AP slot.
The TWRP file needs to be named recovery.img, and that img file needs to be compressed in a tar file. The name of the tar doesn't matter, but you must name the TWRP file recovery.img, or it will fail to flash.
Download AIK Mobile and use it to unpack the img file you got (not original, but the one the patching script produced). Just name it recovery.img and put it in the same folder as AIK, then run the unpack script from a command prompt. If it's ok, you should see some folders/files in the outputted ramdisk directory. Maybe the img doesn't have valid contents. Or in other words, it's possibly corrupt.1
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.1
Issues powering off from where? TWRP? Android?
If the partitions in your super partition don't have shared_blocks, you should be able to mount it this way from TWRP terminal:
mount -o rw,remount /
mount -o rw,remount /system_root
This of course assumes you have a super partition.
As for Magisk, just patch your stock boot.img, flash with Odin from download mode.1
Never seen this behavior on any gsi that I've ran on both of my Samsung devices.1
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.
The best place to file a bug report is here, it's where most gsis derive their code from:
-
33
MUST-READ BACKGROUND - Android 13 and the two approaches:
As some of you already know, due to various reasons, @phhusson , who kickstarted the GSI trend and committed to it over the years, is backing out from future development - there won't be any AOSP 13+ builds or patches directly from him. He did most of the heavylifting for fixing bugs and implementing features, and selflessly supported more than his AOSP GSIs and more than devices he own. For the situation of GSIs today, we owe him a big thank-you.
Earlier, inspired by @PeterCxy , I took the "light" approach, which starts over from AOSP's generic gsi_* target and adds the minimum amount of fixes needed for my own devices, intentionally leaving many legacy devices behind. For more details about it, visit its own thread.
Meanwhile, a number of existing builders incl. myself have formed the TrebleDroid organization, with PHH himself helping us in technical issues. TD will forward-port PHH's final patches (v415) onto Android 13 and attempt to fix new issues. This is still a new and ongoing process, but if done right, will have compatibility and feature-completion on par with past PHH-based GSIs. This thread contains LOS builds based on TrebleDroid's collective work, which supposedly suits legacy devices, Samsung, etc. better than "light".
Disclaimer:
No flashing instructions will be offered. If you're here in this forum, you should know what you're doing.
No guarantees that everything would work. This is a GSI, bugs are bound to happen.
MUST-READ - reporting bugs:
If you want to report a bug, then you MUST try reproducing on an AOSP reference build of around the same date from TrebleDroid, and ONLY proceed to report here when it's specific to this GSI. This filters out bugs common to all TD-based GSIs, which you should still let me know, but it might not be mine to fix. I might silently ignore your report if you skip this.
Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Scroll down for the naming rules of variants.
Compressed as .xz archives - extract first.
Stuff on GitHub (builders-only):
Most things should be self-explanatory. Not the cleanest code, but should help if you need some clues.
- lineage_build_unified - my unified script for building
- lineage_patches_unified - my unified patches for building
- The LineageOS team
- @phhusson - shaped the treble community, and still takes care of TrebleDroid at a higher level
- @PeterCxy - coded critical fixes such as sysbta
- The TrebleDroid builders
- ...and more
https://paypal.me/AndyCGYan9Notes:
- I now have a rather taxing day job, and can't devote nearly as much time/effort into this as I did as a student, or even a year ago.
- I now daily-drive "light", so I can't test TD-based builds as extensively as before. For the same reason, I likely won't build/upload any TD-based "personal" build either.
- While most >=A13 GSIs out there are going to be TD-based, some perform better than others - some devs have their own patches that haven't been merged into TD yet. I myself will stay close to TD's raw patchset as much as possible, without picking patches from others left and right. If you find another GSI working better, don't just complain - try to narrow down which ones, and the intersection of them might be an unmerged patch that, if approved, would be merged into TD and benefit all.
- GAPPS builds are offered as-is without guarantees. As a Chinese I can't/won't help with GAPPS/SN issues - please help each other out.
- ADB is intentionally insecure, even on first boot (turned on by default and no authentication needed). GSIs are more fragile compared to device-specific custom ROMs, both on first boot (no-boot issues) and on subsequent boots (after tuning certain Treble settings), and I insist that no-auth ADB is a must-have for debugging and general fail-safe.
- Signature spoofing (MicroG) is supported, but only for priv-apps. This is a security consideration from PHH.
- On *S variants, install PHH-SU and you'll get basic root for apps, good for devices that don't play well with Magisk or when you don't need modules.
- Refer to this post for explanation/workaround of an MediaTek-specific kernel bug that causes no internet.
6Updated all variants with July security patches. [Insert obligatory backup-and-test warning here]
I just realized that I haven't included PHH-SU app in *S (while I did over at Light) - this has been corrected.
@Jonny - although I still very much doubt that the uname change is related to the alarm, adding it back is trivial, so now it's back.6Updated all variants with Android 13 QPR2 and March security patches. [Insert obligatory backup-and-test warning here]
As usual with "feature drops", things can change or break majorly.
Fixed in-call audio on Snapdragon 8 Gen 2 (SM8550), tested on OnePlus 11, should pave the way for future QCOM SoCs as well. Users of other SM8550 devices like Xiaomi 13 and RedMagic 8 Pro/+ might want to try this out too. Also pushed to TD upstream, so in case you don't like LOS, it's still coming to your favorite TD/-based GSI later.
Imported some SN fixes from HentaiOS - GAPPS users should now get CTS profile match as well.
Fixed videos sometimes getting stuck after pausing and resuming, thanks @Cozzmy13 for working it.
Fixed two-pane layout in Settings for tablets - set an appropriate density then force stop Settings for it to take effect.
And finally for builders, starting this month LOS has moved to Git LFS for hosting their Chromium webviews. Please re-init the repo with "--git-lfs" flag BEFORE syncing again or you will hit errors. If you already have a bad sync, clear the residue and re-init:
Code: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_*
