[ROM][testing][suez] Lineage-16.0 [05 JULY 2022]

[spartasr]

Yea I figured, but I can't even get google assistant working, I tried downloading the google search and google assistant apps but still nothing. I'm wondering if it has to do with the pico gapps.

 

[Infraviored]

I need some help.
I went through all the pain of opening up and unbricking it with amonet-suez-v1.1.2.zip from https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/.

Then I was in TWRP, I think 3.2.sth.
I tried to adb sideload the latest lineage for my device from this thread.

The installation finished with a red error message like /data partition not found.


I restarted the tablet, which is now stuck in a lineage os bootloop.


I thoughtthe problem might be not having the most recent TWRP. So I brought the tablet into hacked-fastboot, and flashed TWRP 3.6.1.2, which succeeded.


Not I can not even access my recovery anymore. When I try to with volume and pwr, the screen stays black.



A) why is the lineage in a bootloop
B) What about the /data partition missing error
C) How to get my TWRP to work again?


I am out of ideas.

 

[lex66676]

I need some help.
I went through all the pain of opening up and unbricking it with amonet-suez-v1.1.2.zip from https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/.

Then I was in TWRP, I think 3.2.sth.
I tried to adb sideload the latest lineage for my device from this thread.

The installation finished with a red error message like /data partition not found.


I restarted the tablet, which is now stuck in a lineage os bootloop.


I thoughtthe problem might be not having the most recent TWRP. So I brought the tablet into hacked-fastboot, and flashed TWRP 3.6.1.2, which succeeded.


Not I can not even access my recovery anymore. When I try to with volume and pwr, the screen stays black.



A) why is the lineage in a bootloop
B) What about the /data partition missing error
C) How to get my TWRP to work again?


I am out of ideas.

Use amonet-suez-v1.1.2.zip
Short the point

sudo ./bootrom-step-minimal.sh
sudo ./fastboot-step.sh

This post https://forum.xda-developers.com/t/...ck-fire-hd-10-2017-suez.3913639/post-79169423

This tablet does not die, you will succeed. ))

 

[Infraviored]

Use amonet-suez-v1.1.2.zip
Short the point View attachment 5872199
sudo ./bootrom-step-minimal.sh
sudo ./fastboot-step.sh

This post https://forum.xda-developers.com/t/...ck-fire-hd-10-2017-suez.3913639/post-79169423

This tablet does not die, you will succeed. ))

But I did exactly this. Shorted it, got TWRP working, I think version 3.2.sth.
Then I tried to adb sideload the latest lineage for my device from this thread.

The installation finished with a red error message like /data partition not found.

 

[lex66676]

But I did exactly this. Shorted it, got TWRP working, I think version 3.2.sth.
Then I tried to adb sideload the latest lineage for my device from this thread.

The installation finished with a red error message like /data partition not found.

Lastest TWRP version
- 3.6.1-9.2
but I have lineage 14 installed and TWRP 3.6.1-9.2 , it has fewer video bugs.

 

[droidjunkie]

But I did exactly this. Shorted it, got TWRP working, I think version 3.2.sth.
Then I tried to adb sideload the latest lineage for my device from this thread.

The installation finished with a red error message like /data partition not found.

why are you trying to "adb sideload" a OS install? you put the rom on your sd card and install it that way. do not use adb sideload.

 

[Infraviored]

why are you trying to "adb sideload" a OS install? you put the rom on your sd card and install it that way. do not use adb sideload.

Normally I always sideload roms to not have to rely on an SD card at all. Maybe this indeed was the probelm, I will try.

 

[gr4f1n]

Disclaimer: I've got no ideas of what I'm doing!

So I spent some time but dod manage to setup the gapps pico. The solution ended up with increasing the system partition size. Rough steps (probably some of them are excessive or not necessary, but I got no ideas what I was doing). I (almost) followed this idea.

Pre-requisites:
1. Make sure you have `gdisk`. I got it form this archive: parted_gdisk_fdisk_mkfs.ext4-AARCH64.zip as described in this thread.

Steps:
1. Reboot into TWRP recovery.
2. Push files to your device.

adb push ~/Downloads/parted_gdisk_fdisk_mkfs.ext4-AARCH64/gdisk /
adb push ~/Downloads/lineage-16.0-20220705-UNOFFICIAL-suez.zip /sdcard
adb push ~/Downloads/open_gapps-arm64-9.0-pico-20220215.zip /sdcard

3. (Not suer if this step has to be done no or later at step 10) Install lineage-16.0-20220705-UNOFFICIAL-suez.zip.
4. Get into adb shell.
5. Check the mount point via `mount`. You will need it later, so don't clean the console! Important part of the output is this:

/dev/block/mmcblk0p15 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p15 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)

6. From [B]/dev/block/mmcblk0p15[/B] you need to get the device name, which in my case was /dev/block/mmcblk0.
7. Allow gdisk executing: chmod +x gdisk.
8. Using gdisk, remove and re-create the cache (the command history is lost, so the commands are written from memory):

# gdisk dev/block/mmcblk0
> p
  13          208896        10229759   1.4 GiB (this is already updated size)    8300  system
  14        10229760        10387455   77.0 MiB    8300  cache
  15        10387456        60619775   24.0 GiB    8300  userdata
> n (delete partition)
> 13 (partition number)
> n (delete partition)
> 14 (partition number)

9. At this point you have to re-create the system partition with slightly bigger size, and cache with the smaller one. I simply split the cache in 2, calculated the system end partition, created it, and created cache in the rest space.
10. On your tablet, go to `wipe` menu, and restore the `cache` and `system`. It will restore the file system on both.
11. (Not suer if this step has to be done no or before at step 3) Install lineage-16.0-20220705-UNOFFICIAL-suez.zip.
12. Install gapps.
13. Reboot device into system.
14. Profit.



If you did manage to repro, the details, especially about step 8 are very welcome.

 

[MarvinMod]

im using 12.1 currently so my son can have his youtube and games working. unless 16 has been fixed for youtube and such but from what im reading, its still an issue.
the only issue i have with 12.1 which runs great is that it will show that it is charging but still show 1% battery life even after days on the charger. if i reboot, same issue but if i turn it off then back on its charged to 99%.
i read through the 12.1 thred and figured id post here where most are active, do i need to update anything or reflash anything to correct this issue or any insight on how to move forward? thanks in advance.

 

[LearnEnglish]

Hi there. L16 rom has an error that Youtube zoom in a part of video many times. How can I fix it? thanks

 

[MarvinMod]

Hi there. L16 rom has an error that Youtube zoom in a part of video many times. How can I fix it? thanks

Apparently progress has seemed to hult on this project. Move to 12.1

 

[LearnEnglish]

Apparently progress has seemed to hult on this project. Move to 12.1

I think I will com back to 14.1. thank you

 

[smithbill]

I have two of these FireHD10 (suez) which until recently I was using as Alexa devices, but I've found Alexa on them to be rather 'hard-of-hearing' & infuriatingly slow in her responses. So I bought a couple of Amazon Echo Flex devices which were recently reduced to £10 each and they are much more responsive.

So I decided to reflash one of my FireHD's with this Lineage 16 ROM. I was still on TWRP 3.6.1-9.2, so that was fortunate. The ROM flashed without issue.

I tried flashing OpenGapps Nano & Pico, but ran into the Error 70 I think others have reported (to do with partition space I think). So I used NikGapps core (the older version P from 2020), it flashed fine and PlayStore works okay (although I think it updated itself after booting & I had to force-stop & clear data a couple of times).

I also rooted it by installing Magisk 26.1, but you do have to do the 'patch boot.img' method & flash the resulting img file to the boot partition in TWRP.

Now I've installed Google Speech Services & Home Assistant Companion app from the PlayStore & can get movement notifications from my ZigBee motion sensors!

So still some life left in my FireHD tablets

 

[Infraviored]

gdisk does not work for me.

I have
/dev/block/mmcblk0p15 on /data type ext4 (rw,seclabel,relatime,data=ordered) /dev/block/mmcblk0p15 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered) /dev/block/mmcblk0p14 on /cache type ext4 (rw,seclabel,relatime,data=ordered)

but then

gdisk dev/block/mmcblk0 GPT fdisk (gdisk) version 1.0.8 Problem opening dev/block/mmcblk0 for reading! Error is 2. The specified file does not exist!

 

[Infraviored]

I finally got this working.

But just realized the cameras are missing. When I try to download apps relying on the camera sensors, they tell me there are none.

Is there any way to enable them?

 

[droidjunkie]

I finally got this working.

But just realized the cameras are missing. When I try to download apps relying on the camera sensors, they tell me there are none.

Is there any way to enable them?

As can be seen in the first few posts, the camera is not currently working.
https://forum.xda-developers.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/post-84492297
that post talks more about this issue. this rom is not intended to be used as a daily driver. If you need everything to be working I would suggest either going back stock or looking at the 2 older lineage versions if what you need is working on them.

Edit:
Here is the link to the post that lists what is working and what isnt working. fixed = works, todo = does not work

[ROM][testing][suez] Lineage-16.0 [05 JULY 2022]

Disclaimer /* * I am not responsible for bricked devices, dead SD cards, thermonuclear war, * or you getting fired because the alarm app failed. * Please do some research if you have any concerns about features included * in the products you find...

forum.xda-developers.com

 

[Infraviored]

As can be seen in the first few posts, the camera is not currently working.
https://forum.xda-developers.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/post-84492297
that post talks more about this issue. this rom is not intended to be used as a daily driver. If you need everything to be working I would suggest either going back stock or looking at the 2 older lineage versions if what you need is working on them.

Edit:
Here is the link to the post that lists what is working and what isnt working. fixed = works, todo = does not work

[ROM][testing][suez] Lineage-16.0 [05 JULY 2022]

Disclaimer /* * I am not responsible for bricked devices, dead SD cards, thermonuclear war, * or you getting fired because the alarm app failed. * Please do some research if you have any concerns about features included * in the products you find...

forum.xda-developers.com

Many thanks for the info!

My goal is not using the tablet daily, but as an interface for my Homeassistant. For this I need the camera detection working so the screen lights up when a user approaches.


From the list I see that camera is in fact not working in the mist recent version. But when was ist still working? It not working refers to all builds in the Google drive in post 1? So I need a lower version lineage?
Can I stick with my current TWRP?

 

[droidjunkie]

Many thanks for the info!

My goal is not using the tablet daily, but as an interface for my Homeassistant. For this I need the camera detection working so the screen lights up when a user approaches.


From the list I see that camera is in fact not working in the mist recent version. But when was ist still working? It not working refers to all builds in the Google drive in post 1? So I need a lower version lineage?
Can I stick with my current TWRP?

As far as I am aware, yes you can keep the same recovery version.

 

[bbt995]

I have two of these FireHD10 (suez) which until recently I was using as Alexa devices, but I've found Alexa on them to be rather 'hard-of-hearing' & infuriatingly slow in her responses. So I bought a couple of Amazon Echo Flex devices which were recently reduced to £10 each and they are much more responsive.

So I decided to reflash one of my FireHD's with this Lineage 16 ROM. I was still on TWRP 3.6.1-9.2, so that was fortunate. The ROM flashed without issue.

I tried flashing OpenGapps Nano & Pico, but ran into the Error 70 I think others have reported (to do with partition space I think). So I used NikGapps core (the older version P from 2020), it flashed fine and PlayStore works okay (although I think it updated itself after booting & I had to force-stop & clear data a couple of times).

I also rooted it by installing Magisk 26.1, but you do have to do the 'patch boot.img' method & flash the resulting img file to the boot partition in TWRP.

Now I've installed Google Speech Services & Home Assistant Companion app from the PlayStore & can get movement notifications from my ZigBee motion sensors!

So still some life left in my FireHD tablets

your method is absolutely correct, I followed the instructions and it worked, thank you

 

[bbt995]

Before: In recovery Wipe data, cache..
Step 1: Flash rom
Step 2: Flash nikgapps-core-arm64-9-20201231
End : not Wipe again