[ROM][flo|deb][UNOFFICIAL][LineageOS 19.1] -> 2023-02-18

Search This thread

ipdev

Recognized Contributor
Feb 14, 2016
2,302
1
4,584
Google Nexus 10
Nexus 7 (2013)
I am not sure about the LOS update.

---

As for TWRP...
Long story short..
Followmsi's newer TWRP builds are based on his LOS (flo/deb) build tree instead of the default omni branch that twrp uses.
I forget the branch version(s).
He does not have much free time these days so, not able to become the maintainer for flo/deb TWRP.

The flo and deb builds work properly for regular (re-partitioned) flo and deb devices.
If you partitioned your flo/deb for use with Official LineageOS Flox (never released Debx) by adding a separate Vendor partition.
this version of TWRP might not work.

Cheers. :cowboy:
 

Syprus21

Member
Nov 7, 2012
18
5
I have something strange going on...after installing this build, i can get into the bootloader (holding volume down and power)...however, when i select recovery twrp doesn't load anymore...google screen flashes a couple times and then it goes right into the OS. Any idea how to get back to TWRP? What am i missing?
 

curiousde2002

Senior Member
Aug 3, 2009
214
45
Same here:
For the record, my flo is basically unusable with this ROM, lots of Launcher/SystemUI/Recents crashes and hangs regardless of whether it's Trebuchet or Lawnchair; not sure if it's just the memory/storage itself getting slow over time, but tweaking the kernel IO does help a little, but fstrim even every boot doesn't do much. 😕
and almost same here but have not yet tried the TWRP thing:
I am running Android 12, 19-20230113-UNOFFICIAL-deb and I'm receiving the following error messages constantly System UI isn't responding and Process UI isn't responding when using my deb, and Unable to mount storage when I clear Dalvik and Cache in TWRP. Plus, my deb is very slow; almost useless. Does anyone have a solution?
Thanks

I'm using Nova launcher because with Trebuchet the device is unusable.

In the meantime my deb is on the latest build 19-20230129-UNOFFICIAL-deb which seems to be a little better, working very well for a few minutes but then all of a sudden freezes.

So this also doesn't make it really usable.

As the majority of the users seem to be quite happy with these ROMs I'm afraid these issues are signs of a dying hardware.
 
  • Like
  • Sad
Reactions: ipdev and osm0sis

curiousde2002

Senior Member
Aug 3, 2009
214
45
Same here:

and almost same here but have not yet tried the TWRP thing:


I'm using Nova launcher because with Trebuchet the device is unusable.

In the meantime my deb is on the latest build 19-20230129-UNOFFICIAL-deb which seems to be a little better, working very well for a few minutes but then all of a sudden freezes.

So this also doesn't make it really usable.

As the majority of the users seem to be quite happy with these ROMs I'm afraid these issues are signs of a dying hardware.
Today I booted into Safe Mode.
Very good performance, I thought I was using a brand new device.:D

OK, I know that Safe Mode is not really a challenge for the hardware but it makes me hope that it's not dying.

Will try another clean install.
 
  • Like
Reactions: ipdev and osm0sis

Heinz-

Member
Oct 11, 2014
35
6
Nexus 7 (2013)
Google Nexus 5
Hello everybody,

it's me again with a problem.
I'd like to install the actual LineageOS 19 on my good old Nexus 7 (deb).
I know that it has to be repartitioned.
First I installed the TWRP recovery. The device was in bootloader mode, so I can do
fastboot flash recovery twrp-3.4.0-0-deb.img. This worked without errors.
Desktop output:
Code:
Sending 'recovery' (9066 KB)                       OKAY [  0.299s]
Writing 'recovery'                                 OKAY [  1.169s]
Finished. Total time: 1.624s
Then I change into the recovery mode.
All links to the sysrepart_1380_20.zip lead to a Google Drive folder only with LieageOS zips and md5sum files. So I had to look for it by myself. I can't remember from where I downloaded that file but I'm sure that was from this forum.
In recovery mode i installed the zip file by sideloading it:
adb sideload sysrepart.zip
Desktop output;
Code:
* daemon not running; starting now at tcp:5037
* daemon started successfully
serving: 'sysrepart.zip'  (~78%)    adb: failed to read command: Success
Nexus 7 output:
Code:
Updating partition details...
...done
Fill DELinux support is present.
MTP enabled
Starting ADB sideload feature
Installing zip file '/sideloadf/package.zip'
Unmounting system...
##############################
# k23m Nexus 7'13 Reparition #
##############################
Creating log and gpt backup
Removing paritions
Creating new partitions
Formatting new partitions
##############################
Operation completed. Copy backup gpt and log files from
internal storage to PC before rebooting.
##############################
Until here everything should work without errors.

Now I rebooted my Nexus and tried to install te system zip by sideload:
adb sideload lineage-19.1-20230113-UNOFFICIAL-deb.zip
Desktop output:
Code:
Total xfer: 0.01x
Nexus 7 output:
Code:
Updating partition details...
...done
Full SELinux support is enabled.
MTP Enabled
Starting ADB sideload feature...
Installing zip file ’/sideload /paclage.zip’
Unmounting system...
Target: google/razorg/deb:6.0.1/MOB30X/3036618:user/
release-keys
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 1
The last line shows up in red.

What do I do wrong? Something very simple I suppose.
Can someone explain me that?

Thank you... :oops:
 

brewer75

Senior Member
Feb 15, 2013
310
101
Pickerington
Nexus 7
Motorola Xoom
Hello everybody,

it's me again with a problem.
I'd like to install the actual LineageOS 19 on my good old Nexus 7 (deb).
I know that it has to be repartitioned.
First I installed the TWRP recovery. The device was in bootloader mode, so I can do
fastboot flash recovery twrp-3.4.0-0-deb.img. This worked without errors.
Desktop output:
Code:
Sending 'recovery' (9066 KB)                       OKAY [  0.299s]
Writing 'recovery'                                 OKAY [  1.169s]
Finished. Total time: 1.624s
Then I change into the recovery mode.
All links to the sysrepart_1380_20.zip lead to a Google Drive folder only with LieageOS zips and md5sum files. So I had to look for it by myself. I can't remember from where I downloaded that file but I'm sure that was from this forum.
In recovery mode i installed the zip file by sideloading it:
adb sideload sysrepart.zip
Desktop output;
Code:
* daemon not running; starting now at tcp:5037
* daemon started successfully
serving: 'sysrepart.zip'  (~78%)    adb: failed to read command: Success
Nexus 7 output:
Code:
Updating partition details...
...done
Fill DELinux support is present.
MTP enabled
Starting ADB sideload feature
Installing zip file '/sideloadf/package.zip'
Unmounting system...
##############################
# k23m Nexus 7'13 Reparition #
##############################
Creating log and gpt backup
Removing paritions
Creating new partitions
Formatting new partitions
##############################
Operation completed. Copy backup gpt and log files from
internal storage to PC before rebooting.
##############################
Until here everything should work without errors.

Now I rebooted my Nexus and tried to install te system zip by sideload:
adb sideload lineage-19.1-20230113-UNOFFICIAL-deb.zip
Desktop output:
Code:
Total xfer: 0.01x
Nexus 7 output:
Code:
Updating partition details...
...done
Full SELinux support is enabled.
MTP Enabled
Starting ADB sideload feature...
Installing zip file ’/sideload /paclage.zip’
Unmounting system...
Target: google/razorg/deb:6.0.1/MOB30X/3036618:user/
release-keys
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 1
The last line shows up in red.

What do I do wrong? Something very simple I suppose.
Can someone explain me that?

Thank you... :oops:
I can't help you troubleshoot other than to let you know that the TWRP you are using is WAY out of date. Look at the first page of this posting and download 3.7.0_9-0-deb_followmsi.img, then see if your problems persist.
 
  • Like
Reactions: ipdev

TamD

Member
Mar 25, 2017
46
23
My auto-rotate went wonky right after the 19.1 install. So, I was pretty sure it do with the OS upgrade.
When I was troubleshooting there seemed to be quite a few apps that deal with auto-rotate.... didn't work for me, but maybe you could try a few and see if you get any improvement?
Best of Luck!
Okay, might need to apologize for my posting "RE Auto-Rotation". It seems that my cure for my Auto-Rotation issue of clearing the app caches was a fluke. It now looks as if my auto-rotation magically began working after clearing the application caches right before completely failing in a permanent way. So, my apologies for all those that might have followed my misguided lead.
I am now using the app "Rotation control" to manually change orientation......
 
  • Like
Reactions: mookdawg7 and ipdev

ipdev

Recognized Contributor
Feb 14, 2016
2,302
1
4,584
Google Nexus 10
Nexus 7 (2013)
Hello everybody,

it's me again with a problem.
I'd like to install the actual LineageOS 19 on my good old Nexus 7 (deb).
I know that it has to be repartitioned.
First I installed the TWRP recovery. The device was in bootloader mode, so I can do
fastboot flash recovery twrp-3.4.0-0-deb.img. This worked without errors.
Desktop output:
Code:
Sending 'recovery' (9066 KB)                       OKAY [  0.299s]
Writing 'recovery'                                 OKAY [  1.169s]
Finished. Total time: 1.624s
Then I change into the recovery mode.
All links to the sysrepart_1380_20.zip lead to a Google Drive folder only with LieageOS zips and md5sum files. So I had to look for it by myself. I can't remember from where I downloaded that file but I'm sure that was from this forum.
In recovery mode i installed the zip file by sideloading it:
adb sideload sysrepart.zip
Desktop output;
Code:
* daemon not running; starting now at tcp:5037
* daemon started successfully
serving: 'sysrepart.zip'  (~78%)    adb: failed to read command: Success
Nexus 7 output:
Code:
Updating partition details...
...done
Fill DELinux support is present.
MTP enabled
Starting ADB sideload feature
Installing zip file '/sideloadf/package.zip'
Unmounting system...
##############################
# k23m Nexus 7'13 Reparition #
##############################
Creating log and gpt backup
Removing paritions
Creating new partitions
Formatting new partitions
##############################
Operation completed. Copy backup gpt and log files from
internal storage to PC before rebooting.
##############################
Until here everything should work without errors.

Now I rebooted my Nexus and tried to install te system zip by sideload:
adb sideload lineage-19.1-20230113-UNOFFICIAL-deb.zip
Desktop output:
Code:
Total xfer: 0.01x
Nexus 7 output:
Code:
Updating partition details...
...done
Full SELinux support is enabled.
MTP Enabled
Starting ADB sideload feature...
Installing zip file ’/sideload /paclage.zip’
Unmounting system...
Target: google/razorg/deb:6.0.1/MOB30X/3036618:user/
release-keys
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 1
The last line shows up in red.

What do I do wrong? Something very simple I suppose.
Can someone explain me that?

Thank you... :oops:
As @brewer75 noted, update to followmsi's latest twrp build.
flo_deb TWRP - [gDrive] - Link

You might also want to check your fastboot/adb version.
Platform Tools - [developer.android] - Link

I do not think the 1380 (re)partition script is currently enough.

---

I just did a clean flash on my deb.
twrp-3.7.0_9-0-deb_followmsi.img - Link
lineage-19.1-20230129-UNOFFICIAL-deb.zip - Link
open_gapps-arm-12L-pico-20220705-UNOFFICIAL_MOD.zip - Link

My system partition is 1480M.
Lineage and OpenGApps Pico use up 1394M.
Leaving 86M free in system.

Though the years, I have (re)partitioned my deb a few times.
The last few times was using REPIT.

[TOOL][UNOFFICIAL][PORT] REPIT: for Nexus 7 (2013) [deb][flo]
xda Thread - Link

Cheers. :cowboy:
 
  • Like
Reactions: mookdawg7

TamD

Member
Mar 25, 2017
46
23
I am not sure about the LOS update.

---

As for TWRP...
Long story short..
Followmsi's newer TWRP builds are based on his LOS (flo/deb) build tree instead of the default omni branch that twrp uses.
I forget the branch version(s).
He does not have much free time these days so, not able to become the maintainer for flo/deb TWRP.

The flo and deb builds work properly for regular (re-partitioned) flo and deb devices.
If you partitioned your flo/deb for use with Official LineageOS Flox (never released Debx) by adding a separate Vendor partition.
this version of TWRP might not work.

Cheers. :cowboy:
I have been using the N7-13_TWRP_flo2flox_Injector_Addon-AK3-signed.zip patch to patch every version of TWRP that I have used since the unfortunate event that allowed TWRP (unchanged) to make my N7 unbootable. I am using it now with the latest version of TWRP. It is a fantastic piece of work. (I don't know if there is a Deb. version). Just flash immediately after installing latest build of TWRP.
Link: https://forum.xda-developers.com/t/...uch-recovery-2017-05-19.2380100/post-85724759
 
Last edited:

bencak

Member
Oct 17, 2012
16
0
heelo guys. i have one problem. have old nexus 7 2013 wifi - flo.
on power on displayed, this is writing cmd:

C:\Users\Home>adb devices
List of devices attached
06db207c device

and on the fastboot mode device not recognize. i have try another cable, another usb port, and lock and unlock bootloader, another adb driver in the device manager, only android adb interface have yellow ! in the driver... i have no ideas, what i try..

What is my problem? please help me.
 

shangjiyu

Member
Jun 10, 2012
39
14
heelo guys. i have one problem. have old nexus 7 2013 wifi - flo.
on power on displayed, this is writing cmd:

C:\Users\Home>adb devices
List of devices attached
06db207c device

and on the fastboot mode device not recognize. i have try another cable, another usb port, and lock and unlock bootloader, another adb driver in the device manager, only android adb interface have yellow ! in the driver... i have no ideas, what i try..

What is my problem? please help me.
change usb default configuration in developer options
 

hfmls

Senior Member
Aug 12, 2009
576
77
Vila Nova de Famalicão
all good, perfect ROM; fast and simple.

Deactivated all animations and now is smooth and very responsive.

Good enough for a wall mount with spotify/youtube and doorbell app. Awesome stuff. Thank you guys for your work.

BTW: Auto-rotate doesn't work, don't know why. Installed adviced application to force, and it works now. No automatic. Maybe my sensor is gone?


Also, after install this ROM and Gapps pico i always get bluetooth keeps stopping? And it won't scan or detect.
Already formatted everything and it was working before.

Did i broke something? I have backup before i repartitioned everything. Any help would be great, thank you.


adb root
adb shell
dd if=/dev/block/mmcblk0p2 of=/sdcard/modemst1.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/modemst2.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/persist.img


I did this backup, should i restore it ?

EDIT2: restored all those files, all good and perfect now! :) :) :)
 
Last edited:
  • Like
Reactions: ipdev

followmsi

Senior Member
Oct 10, 2013
4,238
13,240
Hey, everybody,
followmsi has on his google drive a new build of lineage-19.1-20230129-UNOFFICIAL-flo.zip and a new TWRP 3.7.0. Does anyone have any experience,
what's new? Has anyone tested this build?

Edit:
Tried and tested. The installation went without problems (both TWRP and Flo) and everything works as we are used to.

Thanks for testing !

This build (19.1-20230129) did include following changes ..

- Use discard mount option for /cache and /data
- minor patch in hardware/qcom-caf/msm8960/display
- minor pathch in frameworks/native

Same changes are in latest builds too.
 

followmsi

Senior Member
Oct 10, 2013
4,238
13,240
I am not sure about the LOS update.

---

As for TWRP...
Long story short..
Followmsi's newer TWRP builds are based on his LOS (flo/deb) build tree instead of the default omni branch that twrp uses.
I forget the branch version(s).
He does not have much free time these days so, not able to become the maintainer for flo/deb TWRP.

The flo and deb builds work properly for regular (re-partitioned) flo and deb devices.
If you partitioned your flo/deb for use with Official LineageOS Flox (never released Debx) by adding a separate Vendor partition.
this version of TWRP might not work.

Cheers. :cowboy:

Thanks .. like described .. some new TWRP builds from time to time.

Pls check here for more details about the used sources ..


 

followmsi

Senior Member
Oct 10, 2013
4,238
13,240
LineageOS 19.1 - February 2023

New builds ..

lineage-19.1-20230218-UNOFFICIAL-flo.zip

lineage-19.1-20230218-UNOFFICIAL-deb.zip


Changes:
- Google security updates -> February 2023
- Use discard mount option for /cache and /data
- minor patch in hardware/qcom-caf/msm8960/display
- minor pathch in frameworks/native
- Latest LineageOS changes for Android 12

Pls check first page for known issues and more information.

Tested flo build with opengapps pico and Magisk 25.2 and v2.4.0-MOD_1.2.

As SDK level increased to version 32 we have to use new gapps for Android 12L.
Pls check latest gapps builds here .. https://drive.google.com/drive/folders/1O-I01LDvno57ztnxIW_bSnVWEk8-6Ics
Thanks to @ipdev for the opengapps packages !

Enjoy Android 12L :p
 

alvincata

New member
Feb 10, 2017
4
0
LineageOS 19.1 - February 2023

New builds ..

lineage-19.1-20230218-UNOFFICIAL-flo.zip

lineage-19.1-20230218-UNOFFICIAL-deb.zip


Changes:
- Google security updates -> February 2023
- Use discard mount option for /cache and /data
- minor patch in hardware/qcom-caf/msm8960/display
- minor pathch in frameworks/native
- Latest LineageOS changes for Android 12

Pls check first page for known issues and more information.

Tested flo build with opengapps pico and Magisk 25.2 and v2.4.0-MOD_1.2.

As SDK level increased to version 32 we have to use new gapps for Android 12L.
Pls check latest gapps builds here .. https://drive.google.com/drive/folders/1O-I01LDvno57ztnxIW_bSnVWEk8-6Ics
Thanks to @ipdev for the opengapps packages !

En
 

Top Liked Posts