[ROM][LineageOS][17.1][UNOFFICIAL][Nexus10]

[juankar90]

Hi. I am trying to install the rom but I get error 7. I have tried version 17 and version 16.

I have tried installing from internal memory and from adb from my pc. I always get error 7. And I am without operating system. I do not know what to do.

Can you please help me? I attach the part of the log where the error occurs.

Thank you very much, regards.

 

[ipdev]

Hi. I am trying to install the rom but I get error 7. I have tried version 17 and version 16.

I have tried installing from internal memory and from adb from my pc. I always get error 7. And I am without operating system. I do not know what to do.

Can you please help me? I attach the part of the log where the error occurs.

Thank you very much, regards.

View attachment 5295591

Hi.
This error means the updater (installer) script would not complete if it continued to run.

script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001

It should error out and exit before anything was modified or changed.
Leaving your system as it was before you attempted the install.

Normally that error means there is not enough space in the system partition.
Might also happen if you are using an old or unsupported recovery.
The system partition can not be mounted for some reason.

You should have received a different error if the zip file was corrupt.
Just to be safe, double check your download(s) using the md5sum file that matches the build you downloaded.

--

For Lineage 17.x you need to (re)partition the device and increase the system partition since it will not fit in the stock partition.

Odd that it happens with Lineage 16 since it is built using the stock partition size.
Lineage 16 will fit but, you need to increase the system partition to install GApps.

To increase your system partition, I recommend using REPIT.
[TOOL][UNOFFICIAL][PORT] REPIT: for Nexus 10 [manta] - xdaThread - Link

To download the newest TWRP.
TWRP for Samsung Nexus 10 - twrp.me - WebSite - Link

The image .img files are fastboot/recovery flashable.
The compressed image .img.tar files are to be flashed using ODIN.​

--

Try mounting system and check the size.

TWRP-> Mount Select System​

To check size using the command line.
The df command df -ah will show the sizes of all the mounted partition.

To check size using TWRP.
TWRP-> Wipe->Advanced Wipe-> Select System-> Repair or Change File System

Stock system partition size is 787M.
A modified system partition is a big as you make it.

If system can not be mounted..
You can try wiping system in TWRP and try mounting again.
You may have to format userdata and then wipe all partitions.

Note: Formatting userdata will erase all data.
Backup what you want to save and store it off device.
Copy it to your computer, cloud storage, USB, ...

Cheers.

 

[juankar90]

Hi.
This error means the updater (installer) script would not complete if it continued to run.

script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001

It should error out and exit before anything was modified or changed.
Leaving your system as it was before you attempted the install.

Normally that error means there is not enough space in the system partition.
Might also happen if you are using an old or unsupported recovery.
The system partition can not be mounted for some reason.

You should have received a different error if the zip file was corrupt.
Just to be safe, double check your download(s) using the md5sum file that matches the build you downloaded.

--

For Lineage 17.x you need to (re)partition the device and increase the system partition since it will not fit in the stock partition.

Odd that it happens with Lineage 16 since it is built using the stock partition size.
Lineage 16 will fit but, you need to increase the system partition to install GApps.

To increase your system partition, I recommend using REPIT.
[TOOL][UNOFFICIAL][PORT] REPIT: for Nexus 10 [manta] - xdaThread - Link

To download the newest TWRP.
TWRP for Samsung Nexus 10 - twrp.me - WebSite - Link

The image .img files are fastboot/recovery flashable.​

The compressed image .img.tar files are to be flashed using ODIN.​

--

Try mounting system and check the size.

TWRP-> Mount Select System​

To check size using the command line.
The df command df -ah will show the sizes of all the mounted partition.

To check size using TWRP.
TWRP-> Wipe->Advanced Wipe-> Select System-> Repair or Change File System

Stock system partition size is 787M.
A modified system partition is a big as you make it.

If system can not be mounted..
You can try wiping system in TWRP and try mounting again.
You may have to format userdata and then wipe all partitions.

Note: Formatting userdata will erase all data.
Backup what you want to save and store it off device.
Copy it to your computer, cloud storage, USB, ...

Cheers.

Good morning.
First of all, thank you very much for your reply.

I have been checking the size of the SYSTEM partition with the twrp and it is 787mb.

The twrp I am using the latest version, the 3.5.2_9-0.

I can't recover the operating system I had because I didn't backup and format the partition. But it didn't help me much because it always gave me an error when installing the gaps.

Thank you very much.

Edit:

I have already changed the partition size. I just successfully installed the operating system.
Now I will try to install the gaps.

Thank you very much for your help. and many thanks to all the people who collaborate with the project.

 

[juankar90]

Good evening again,

After a few days with android version 10, it was going very slow so I had to install version 16 with android 9.

Let's see how it works.

Regards,.

 

[goodflood]

Simple question, is you Nexus 10 kinda slow?

@PTHugo Yes, but, I don't think it has gone down in quality. I don't know for a fact, but suspect there is some kind of regression. @followmsi has done a great job over the years. If I recall correctly, this has happened before... ROM is fast, fast, fast, then slow, slow, until problem is found and fixed. I tried clearing cache, not sure what else I need to look at or tools to use to run a diagnostic. Can anyone help?

By the way, I use the tablet primarily to read RSS new feeds... for doing anything else, ... users might feel the lag! Honestly, though, it seems okay, then, slow at times, a little inconsistent... or maybe its just me!~

 

[followmsi]

Lineage-17.1 - May 2021

lineage-17.1-20210510-UNOFFICIAL-manta.zip

Changes:
- Google security updates -> May 2021
- Disabled Google AVC codec to fix video on latest versions of Netflix.
- Patched framework/base to support microG
- Latest LineageOS changes for Android 10

Pls check first page for known issues.

For the "System and Cache repartitioning / Opengapps: Error 70" topic pls have a look on the first page.

Enjoy

 

[sloniu82]

Hi.
I'm trying to use one of Magisk module - ACC (Advanced Charging Controller )

But the buit-in test says that cant control charging:

Advanced Charging Controller v2021.2.25 (202102250)
Copyright 2017-present, VR25
GPLv3+

(i) accd is running (PID 2550)

1) Language
2) All commands
3) Documentation
4) Start/restart daemon
5) Stop daemon
6) Export logs
7) Charge once to #%
8) Uninstall
9) Edit config.txt
a) Reset battery stats
b) Test charging switches
c) Check for update
d) Flash zips
e) Exit

#? b


(!) Charger must be plugged to continue...
grep: smb347-usb/uevent/status: Not a directory
grep: smb347-usb/uevent/status: Not a directory
(i) Alright, this may take a minute or so...

grep: smb347-usb/uevent/status: Not a directory
grep: smb347-usb/uevent/status: Not a directory
grep: smb347-usb/uevent/status: Not a directory
grep: smb347-usb/uevent/status: Not a directory
grep: smb347-usb/uevent/status: Not a directory
(!) [manta-battery/charge_enabled 1 0] won't work

(i) Press any key to continue...

What I read, charging control mus be enabled in kernel.
Could you please check if this is possible on Nexis 10?

 

[guidol]

Lineage-17.1 - May 2021
lineage-17.1-20210510-UNOFFICIAL-manta.zip
Enjoy

@followmsi Many Thanks for this build
I updated today from Android 9 / Lineage-16.1 to this version and its running fine for me
I only have waited to update to Lineage 17.1/Android 10 because my son had some games with highscores under Android 9
Great work - real new life for my Nexus 10!

 

[ddrum2000]

@PTHugo Yes, but, I don't think it has gone down in quality. I don't know for a fact, but suspect there is some kind of regression. @followmsi has done a great job over the years. If I recall correctly, this has happened before... ROM is fast, fast, fast, then slow, slow, until problem is found and fixed. I tried clearing cache, not sure what else I need to look at or tools to use to run a diagnostic. Can anyone help?

By the way, I use the tablet primarily to read RSS new feeds... for doing anything else, ... users might feel the lag! Honestly, though, it seems okay, then, slow at times, a little inconsistent... or maybe its just me!~

Mine is extremely laggy too and have very few apps installed, certainly nothing that takes substantial CPU or GPU. Any thoughts on how to decrease lag?

 

[guidol]

Mine is extremely laggy too and have very few apps installed, certainly nothing that takes substantial CPU or GPU. Any thoughts on how to decrease lag?

Maybe you could try to trim the flash with Trimmer (fstrim):

Trimmer (fstrim) - Apps on Google Play

Trim your device NAND chip manually and fix lags.

play.google.com

I also got very few apps installed. Mostly its getting better when clearing the Internet-Cache in Google Chrome or use "SD Maid" to clear some space:

SD Maid 1 - System Cleaner - Apps on Google Play

A maid for your Android, to keep it clean & tidy.

play.google.com

My Nexus 10 is also sometimes lagging, but its better than on my Samsung SM-T900 where also the flasing of the image is very slow.
On the SM-T900 for me it looks like the flash is giving partly up on working correctly

But since Android v4.3 the Android itself should do the trim if the device has long time for its own in a unsed state.

 

[followmsi]

Hi.
I'm trying to use one of Magisk module - ACC (Advanced Charging Controller )

But the buit-in test says that cant control charging:

Advanced Charging Controller v2021.2.25 (202102250)
Copyright 2017-present, VR25
GPLv3+

(i) accd is running (PID 2550)

1) Language
2) All commands
3) Documentation
4) Start/restart daemon
5) Stop daemon
6) Export logs
7) Charge once to #%
8) Uninstall
9) Edit config.txt
a) Reset battery stats
b) Test charging switches
c) Check for update
d) Flash zips
e) Exit

#? b


(!) Charger must be plugged to continue...
grep: smb347-usb/uevent/status: Not a directory
grep: smb347-usb/uevent/status: Not a directory
(i) Alright, this may take a minute or so...

grep: smb347-usb/uevent/status: Not a directory
grep: smb347-usb/uevent/status: Not a directory
grep: smb347-usb/uevent/status: Not a directory
grep: smb347-usb/uevent/status: Not a directory
grep: smb347-usb/uevent/status: Not a directory
(!) [manta-battery/charge_enabled 1 0] won't work

(i) Press any key to continue...

What I read, charging control mus be enabled in kernel.
Could you please check if this is possible on Nexis 10?

Sorry .. I do not have the time to look into any Nexus 10 issues anymore.
Also no time for further development nor other device/kernel related changes.
Not sure if and when this will change ..

For the moment I do make monthly builds just including new Google security patches.

Thanks for understanding !

Cheers

 

[followmsi]

Lineage-17.1 - June 2021

lineage-17.1-20210613-UNOFFICIAL-manta.zip

Changes:
- Google security updates -> June 2021
- Disabled Google AVC codec to fix video on latest versions of Netflix.
- Patched framework/base to support microG
- Latest LineageOS changes for Android 10

Pls check first page for known issues.

For the "System and Cache repartitioning / Opengapps: Error 70" topic pls have a look on the first page.

Enjoy

 

[sloniu82]

Sorry .. I do not have the time to look into any Nexus 10 issues anymore.
Also no time for further development nor other device/kernel related changes.
Not sure if and when this will change ..

For the moment I do make monthly builds just including new Google security patches.

Thanks for understanding !

Cheers

Thanks followmsi.
Sure I understand!
The plan was to repropose nexus as picture frame, thats why I searching for baterry management software
Most of these devices, that still are working are like living dead - just can't die
And I don/t want to kill baterry with constantly connected charger.
I'll try other roms/kernels - maybe I find compatibile with this ACC Magisk module.

 

[ma66ot87]

Hey guys,
I just bought 2 Nexus 10 for about 25$ because I saw it is still supported here. Big up to the dev for keeping the ROM going.

To make things perfect it would be great to run Netflix. I can't make it work. I'm rooted with magisk, hid the app and activated magisk hide. I also changed build props to pixel 5 but it keeps saying "device is not supported". Any ideas?

Thanks

 

[followmsi]

Hey guys,
I just bought 2 Nexus 10 for about 25$ because I saw it is still supported here. Big up to the dev for keeping the ROM going.

To make things perfect it would be great to run Netflix. I can't make it work. I'm rooted with magisk, hid the app and activated magisk hide. I also changed build props to pixel 5 but it keeps saying "device is not supported". Any ideas?

Thanks

Tested latest Netflix version from Playstore without problems .. Magisk Hide needs to be enabled to install thru PlayStore.

 

[followmsi]

Lineage-17.1 - July 2021

lineage-17.1-20210721-UNOFFICIAL-manta.zip

Changes:
- Google security updates -> July 2021
- Disabled Google AVC codec to fix video on latest versions of Netflix.
- Patched framework/base to support microG
- Latest LineageOS changes for Android 10

Pls check first page for known issues.

For the "System and Cache repartitioning / Opengapps: Error 70" topic pls have a look on the first page.

Enjoy

 

[ma66ot87]

Tested latest Netflix version from Playstore without problems .. Magisk Hide needs to be enabled to install thru PlayStore.

Ok strange. I did everything by the book and I have quiet some experience with Custom ROMs. Resized system partition flashed Gapps Pico and Magisk and also enabled Magisk hide. I could only get the Netflix APK 4.x to work (every other version prompted me to update or it said "not supported").

With 4.x I had sound issues. It would not play sound only picture. After a restart there would be sound occasionally but disappeared when trying to fast forward or rewind the film.

I now went back to Lineage 16 had almost the same problems but Netflix 4.x is now running with sound and no issues. But I still have the strange issue that some apps which should run won't run saying the device is not supported.

Running Magisk 23.0 Maybe that's the issue?

 

[goodflood]

Hello~!

Ran in to a problem. I updated to @followmsi latest ROM, magisk (already installed), no gapps package (just fdroid)... and the tablet does not come on. I did have the battery changed recently and it dies at about 42%. But, I left it charging overnight. On power press, the battery icon appears and show battery as full, but then tablet does not turn on ... just cycles on and off. I somehow am able to get into TWRP. I reflashed... nothing! Funning this is that the battery icon percentage does not show in TWRP and apparently this is a know issue with... someone on a website said software... (there was a message about selinux or something somewhere) and someone said hardware, i.e. battery. What should I try?

Thanks!

EDIT 1: I did get into TWRP and installed MAY ROM. Same thing... can't boot into system... back to battery logo loop.

EDIT 2: So, I somehow managed to be in TWRP, then, booted to system. Battery did show as 0%. The new replacement battery I have had for a while sometimes, drains out completely and then some. I managed to let it charge to 100%... then updated to July ROM. Besides being a little slow for a few minutes, the ROM feels normal ... All is good!

 

[lobstapowa]

I dirty flashed to the latest build from June's which was working fine and but kept running into bootloops after flashing to July.

I can restore back to a nandroid backup to June's build with no issue via TWRP but nothing I've done so far is helping me avoid the bootloop situation when I try to update to July. I let it sit but no progress even after about 2.5 hours. I tried restoring back to June and disabling everything in Magisk but it still bootloops. I'm on version 23 of Magisk.

I've now uninstalled Magisk both after restoring and via the zip in TWRP and I'm clearing dalvik and cache before I flash the new build as well as before booting to system. Other than maybe a corrupted download except when I wiped data and just installed the build without gapps and magisk it booted with no issue. I'm out of ideas on what to try next if erasing Magisk doesn't work.

Aside from just flashing the build and starting over from scratch.

 

[ipdev]

I dirty flashed to the latest build from June's which was working fine and but kept running into bootloops after flashing to July.

I can restore back to a nandroid backup to June's build with no issue via TWRP but nothing I've done so far is helping me avoid the bootloop situation when I try to update to July. I let it sit but no progress even after about 2.5 hours. I tried restoring back to June and disabling everything in Magisk but it still bootloops. I'm on version 23 of Magisk.

I've now uninstalled Magisk both after restoring and via the zip in TWRP and I'm clearing dalvik and cache before I flash the new build as well as before booting to system. Other than maybe a corrupted download except when I wiped data and just installed the build without gapps and magisk it booted with no issue. I'm out of ideas on what to try next if erasing Magisk doesn't work.

Aside from just flashing the build and starting over from scratch.

The issue could be GApps also.

Since you note that the July build work on it's own, would lead me to believe it might be with one of the addon.d scripts.
If GApps are not re-installing correctly after the rom flash, you will definitely get a bootloop or infinite boot.

Try installing GApps after you install the July build.
Use the same GApps package/setup you used with the June build.

Here are two ways to do a clean(ish) dirty flash.
Restore you June backup and make sure everything is working..

To be safe.
Backup what you want to save and store it off device.
Copy it to your computer, cloud storage, USB, ...


Clean(ish) dirty flash.
Keep data only.

1. Boot into TWRP.
2. Wipe system.
   
   TWRP-> Wipe-> Advanced Wipe-> Select System then Swipe to Wipe.​
3. Install the July build.
4. Install GApps.
   
   The same GApps build you did with you June build.​
5. Install Magisk.
6. Wipe cache(s).
   
   TWRP-> Wipe-> Advanced Wipe-> Select Dalvik/ART Cache and Cache then Swipe to Wipe.​
7. Reboot to system.

Clean flash, restore data only.
Restore data from backup.

1. Boot into TWRP.
2. Wipe system and data.
   
   TWRP-> Wipe-> Advanced Wipe-> Select System and Data then Swipe to Wipe.​
3. Install the July build.
4. Install GApps.
5. Install Magisk.
6. Restore only Data from your June TWRP backup.
7. Wipe cache(s).
   
   TWRP-> Wipe-> Advanced Wipe-> Select Dalvik/ART Cache and Cache then Swipe to Wipe.​
8. Reboot to system.

You might have issues but, it should hopefully boot.
Issues might come from data.
Settings, user set permissions, apps and app updates are stored in data.

Hope it helps more than confuse.

Cheers.