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

[chairmanmiaow]

So I'm revisiting this again as the household spare suez tablet has slowly crawled to a standstill and needs a rebuild: previously it was running the last build @ggow posted + opengapps + magisk with no problem and for many months worked fine.

Reflashing it back to the same state has proved confusing and I can't remember what I did last time - the device hasn't been repartitioned so perhaps I debloated the lineageos install a bit first before flashing opengapps pico but who knows, it was ages ago

I wanted the easy life and I've largely moved from opengapps to nikgapps anyway so thought I'd flash the 67Mb NikGapps-core-arm64-9-20201231-signed.zip after lineageos on the suez, especially as peeps here have said nikgapps work. But I'm instead getting unequivocal failure and: "This Addon can only be flashed on top of NikGapps".

Err... So nikgapps doesn't work then? I don't mind repartitioning the suez manually with parted so I can flash opengapps pico but does anyone know something I don't?

 

[chairmanmiaow]

Ok I can answer my own question - pulling the logs from the tablet turned this up:

unknown fuse request opcode 17 df: /sideload: Function not implemented unknown fuse request opcode 17 df: /sideload: Function not implemented

So it turns out that you can't adb sideload NikGapps-core-arm64-9-20201231-signed.zip but you can adb push it to /sdcard and then install it via TRWP on the tablet. Afterwards you can then adb sideload the NikGapps SetupWizard addon and Magisk with no issues.

Hopefully that might help out anyone else running into problems reinstalling from scratch.

 

[Shack70]

Ok I can answer my own question - pulling the logs from the tablet turned this up:

unknown fuse request opcode 17 df: /sideload: Function not implemented unknown fuse request opcode 17 df: /sideload: Function not implemented

So it turns out that you can't adb sideload NikGapps-core-arm64-9-20201231-signed.zip but you can adb push it to /sdcard and then install it via TRWP on the tablet. Afterwards you can then adb sideload the NikGapps SetupWizard addon and Magisk with no issues.

Hopefully that might help out anyone else running into problems reinstalling from scratch.

You can just copy the files to your tablet then flash using TWRP. No need to use ADB unless you want to.

 

[chairmanmiaow]

You can just copy the files to your tablet then flash using TWRP.

Yes, that's exactly what my post just said.

No need to use ADB unless you want to.

No, you can't use ADB sideload even if you want to for NikGapps. Which is also exactly what my post just said.

 

[chairmanmiaow]

I now remember why I'd been putting off rebuilding the suez for so long - getting the full set of basics installed, working and playing nice together is an exercise in pure pain compared to any of the other hundreds of devices I've done over the years. My desired "full set" is as follows:

twrp_suez_3.6.1-9.2 (not 3.7 as I need to install Magisk 25.2)
lineage-16.0-20220705-UNOFFICIAL (@ggow's final released build)
NikGapps-core-arm64-9-20201231 (because I don't want to bother repartitioning just for opengapps pico)
Magisk 25.2 + modules
Multiple user profiles
Working google services/gmail/play store (obviously)

The tablet is now 95% of the way there but one last annoying hold-out is the interplay between magisk and google services - fortunately I don't actually need the tablet to pass validation but I would like it to. Searching this thread turned up the old advice to uninstall magisk first and then the gmail app will suddenly stop crashing - reinstalling magisk again afterwards gets the desired combination of working gmail+magisk. So far so good.

Has anyone figured out how to keep gmail+magisk working and get SafetyNet Attestation to pass? I currently seem to have only two options:

1: flash universal-safetynet-fix + magisk props which fixes attestation but breaks gmail app completely
2: uninstall universal-safetynet-fix + magisk props completely (not just disable) and have working gmail app

Magisk Hide or using enforce denylist to mask google services/apps doesn't seem to work. I've tried a few other hacky bodges and workarounds with no luck.

Any suggestions? Again I luckily don't actually need the stupid suez to pass SafetyNet Attestation so can technically live without it, but the loose end is so aggravating...

 

[Shack70]

I now remember why I'd been putting off rebuilding the suez for so long - getting the full set of basics installed, working and playing nice together is an exercise in pure pain compared to any of the other hundreds of devices I've done over the years. My desired "full set" is as follows:

twrp_suez_3.6.1-9.2 (not 3.7 as I need to install Magisk 25.2)
lineage-16.0-20220705-UNOFFICIAL (@ggow's final released build)
NikGapps-core-arm64-9-20201231 (because I don't want to bother repartitioning just for opengapps pico)
Magisk 25.2 + modules
Multiple user profiles
Working google services/gmail/play store (obviously)

The tablet is now 95% of the way there but one last annoying hold-out is the interplay between magisk and google services - fortunately I don't actually need the tablet to pass validation but I would like it to. Searching this thread turned up the old advice to uninstall magisk first and then the gmail app will suddenly stop crashing - reinstalling magisk again afterwards gets the desired combination of working gmail+magisk. So far so good.

Has anyone figured out how to keep gmail+magisk working and get SafetyNet Attestation to pass? I currently seem to have only two options:

1: flash universal-safetynet-fix + magisk props which fixes attestation but breaks gmail app completely
2: uninstall universal-safetynet-fix + magisk props completely (not just disable) and have working gmail app

Magisk Hide or using enforce denylist to mask google services/apps doesn't seem to work. I've tried a few other hacky bodges and workarounds with no luck.

Any suggestions? Again I luckily don't actually need the stupid suez to pass SafetyNet Attestation so can technically live without it, but the loose end is so aggravating...

I'm using opengapps and have no issue with gmail so I can't help you there. For SafetyNet Attestation I'm using the Hide Props Magisk module and not the universal fix one. https://forum.xda-developers.com/t/...safetynet-prop-edits-and-more-v6-1-2.3789228/

I use Google Pixel 4xl V12 as the footprint with no safetynet issues.. Hope this helps.

 

[8bitword]

Thank you for your excellent work @ggow!

I am currently on lineage 14.1 and I have locked bootloader and corrupt recovery. I broke recovery by using flashify to flash the new version of twrp. I can only get temporary root using KingoRoot.
Is there any way to flash recovery? I tried PartitionsBackup app that shows recovery and recovery_x partitions.
Does a locked bootloader allow me to flash a stock rom and install stock recovery or will it break it?

Cheers.

 

[chairmanmiaow]

Having fixed suez #1 I've moved on to suez #2 and promptly find myself in the same situation as @8bitword - I forgot to check through the replies here first and decided to "update" twrp by flashing twrp_suez_3.6.1-9.0.img to recovery using the standard twrp app from the playstore. Whoops.

I should have done dd if=/sdcard/twrp_suez_3.6.1-9.0.img of=/dev/block/platform/soc/11230000.mmc/by-name/recovery_x and have now done so but I still don't have a working recovery unsurprisingly. Is this fixable? I'm in a slightly better position as I can still boot to a working lineageos 16 with root - the bootloader was unlocked and unless the ill-advised twrp flash broke it it presumably still is.

To go back to stock if I remember rightly you put the suez into download mode and then just adb sideload update-kindle-blah-blah.bin right? The latest suez firmware from Amazon is FireOS 5.3.7.3 though which I can't imagine is still hackable using the old amonet method though. Does anyone know what the latest version of FireOS for the suez is still usable and where it might be obtained?

 

[chairmanmiaow]

And come to think of it, I still have suez #1 to hand which is a fully working hacked bootloader+twrp+lineageos+root setup. Could I dd the relevant partitions to .img files on the suez #1 and then dd those imgs to the relevant partitions on suez #2 to restore working order?

 

[Shack70]

And come to think of it, I still have suez #1 to hand which is a fully working hacked bootloader+twrp+lineageos+root setup. Could I dd the relevant partitions to .img files on the suez #1 and then dd those imgs to the relevant partitions on suez #2 to restore working order?

I'm not sure this would work or not. If you go the other route and restore a stock rom, I would use an older version that is rootable and then follow this threads instructions: https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/

 

[greenbot2018]

Thanks to you folks the ol' Fires never quit, made it to another android generation. Great work guys. I passed on this image this last year but it looks like the big bugs are worked out. Working great for our needs. Thanks again!

 

[_ck_]

This big beautiful 10 inch tablet is back restocked on Woot for only $25 again, happens a few times a year if you miss it.

They give free shipping if you have an Amazon Prime account.

They are refurbished but mine arrived in a nice Amazon box carefully prepped and other than light brush strokes on the screen which probably would disappear with a screen protector it's almost like new.

Even with the newest amazon rom you can still root/bootloader-unlock it, just takes several more steps and an hour of your time.

I'm not in a position financially to do it right now but anyone who is might want to consider drop shipping one to some of the developers around here to make sure we keep getting updates to this rom and maybe the next.

Not sure if ggow needs another or some of the other people who were active in similar devices.

This is the link but purposely breaking it in case that's not allowed on xda, not sure?

woot.com /offers/amazon-fire-hd-10-2017-your-choice-29

> Amazon Fire HD 10 (7th Gen, 2017) 10.1" Display
> $24.99 Condition Refurbished
> Free Standard shipping for Prime members
> 4 days left - OR - until sold out

 

[8bitword]

And come to think of it, I still have suez #1 to hand which is a fully working hacked bootloader+twrp+lineageos+root setup. Could I dd the relevant partitions to .img files on the suez #1 and then dd those imgs to the relevant partitions on suez #2 to restore working order?

@chairmanmiaow, if copying the working recovery and recovery_x files to your other device fixes it I'd greatly appreciate a copy! ;⁠-⁠)

If I could flash stock recovery and get back to original firmware I might do the bootloader hack and get lineage 16 on there. But with the modified gpt on lineage 14.1 I don't know if it will break it.

 

[URBANsUNITED]

Maybe I missed that point...

But How to get Netflix running on this Mod?

Thanks alot!

URBANsUNITED

 

[chairmanmiaow]

@chairmanmiaow, if copying the working recovery and recovery_x files to your other device fixes it I'd greatly appreciate a copy! ;⁠-⁠)

If I could flash stock recovery and get back to original firmware I might do the bootloader hack and get lineage 16 on there. But with the modified gpt on lineage 14.1 I don't know if it will break it.

Well I've had a good poke around the partitioning and setup of mmcblk0 on a "good" and "bad" suez tablet for comparison and it looks like - unsurprisingly - there's probably considerably more to it than just dd'ing a recovery partition or two. For example:

"good" suez

suez:/ # ls -alh /dev/block/platform/soc/11230000.mmc/by-name/ | tail -n +4 | awk '{print $8,$9,$10}' MISC -> /dev/block/mmcblk0p9 PMT -> /dev/block/mmcblk0p2 boot -> /dev/block/mmcblk0p11 boot0hdr0 -> /dev/null boot0hdr0_real -> /dev/block/mmcblk0boot0p1 boot0hdr1 -> /dev/null boot0hdr1_real -> /dev/block/mmcblk0boot0p2 boot0img0 -> /dev/null boot0img0_real -> /dev/block/mmcblk0boot0p3 boot0img1 -> /dev/null boot0img1_real -> /dev/block/mmcblk0boot0p4 boot_amonet -> /dev/block/mmcblk0p16 boot_x -> /dev/block/mmcblk0p11 cache -> /dev/block/mmcblk0p14 dkb -> /dev/block/mmcblk0p4 kb -> /dev/block/mmcblk0p3 lk -> /dev/null lk_real -> /dev/block/mmcblk0p5 metadata -> /dev/block/mmcblk0p8 proinfo -> /dev/block/mmcblk0p1 recovery -> /dev/block/mmcblk0p12 recovery_amonet -> /dev/block/mmcblk0p17 recovery_x -> /dev/block/mmcblk0p12 reserved -> /dev/block/mmcblk0p10 system -> /dev/block/mmcblk0p13 tee1 -> /dev/null tee1_real -> /dev/block/mmcblk0p6 tee2 -> /dev/null tee2_real -> /dev/block/mmcblk0p7 userdata -> /dev/block/mmcblk0p15

"bad" suez

suez:/storage/93CF-1B05/fireN # ls -alh /dev/block/platform/soc/11230000.mmc/by-name/ | tail -n +4 | awk '{print $8,$9,$10}' MISC -> /dev/block/mmcblk0p9 PMT -> /dev/block/mmcblk0p2 boot -> /dev/block/mmcblk0p16 boot0hdr0 -> /dev/block/mmcblk0boot0p1 boot0hdr1 -> /dev/block/mmcblk0boot0p2 boot0img0 -> /dev/block/mmcblk0boot0p3 boot0img1 -> /dev/block/mmcblk0boot0p4 boot_x -> /dev/block/mmcblk0p11 cache -> /dev/block/mmcblk0p14 dkb -> /dev/block/mmcblk0p4 kb -> /dev/block/mmcblk0p3 lk -> /dev/block/mmcblk0p5 metadata -> /dev/block/mmcblk0p8 proinfo -> /dev/block/mmcblk0p1 recovery -> /dev/block/mmcblk0p17 recovery_x -> /dev/block/mmcblk0p12 reserved -> /dev/block/mmcblk0p10 system -> /dev/block/mmcblk0p13 tee1 -> /dev/block/mmcblk0p6 tee2 -> /dev/block/mmcblk0p7 userdata -> /dev/block/mmcblk0p15

I think at this point just to save time/effort it's time to reset back to stock and redo unlocking the bootloader from scratch again. It's worth double checking first of course but it does seem that it's still possible to unlock even the latest official Amazon suez firmware. Bit of a pain in the ass but it's entirely my fault - I know how fragile these things are but still half-arsed the TWRP upgrade even though I had misgivings at the time.

@8bitword - if you just want to get back to stock you can indeed just flash straight over the top of your existing system and basically fully recover. In your case you didn't even have the unlocked bootloader status or custom recovery setup to lose in the first place so you're just replacing a lightly mangled stock os with a fresh minty stock os. I need to comb through the other suez threads first just to refresh my memory on how to reflash stock though - I think you just put it in fastboot mode and then you can send the stock bin from a PC via adb or odin/fastboot.

Can anyone save me the effort and remind me?

 

[chairmanmiaow]

Maybe I missed that point...

But How to get Netflix running on this Mod?

There's some instructions back from reply #201, presumably they still 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

 

[chairmanmiaow]

Ok to answer my own question this is how to recover from a bad twrp/flash. Combing through the original amonet root scripts was the key.

In my case I didn't want to brick it or cut off what access I still had as the bootloader was locked again and there was no working recovery available but it could still boot to lineageos with working root. This is what the partition map looked like via adb shell:

suez:/sdcard # fdisk -l /dev/block/mmcblk0 Found valid GPT with protective MBR; using GPT Disk /dev/block/mmcblk0: 61071360 sectors, 1148M Logical sector size: 512 Disk identifier (GUID): b998c40e-777a-4999-9548-19f4211da93d Partition table holds up to 128 entries First usable sector is 34, last usable sector is 61071326 Number Start (sector) End (sector) Size Name 1 1024 7167 3072K proinfo 2 7168 16383 4608K PMT 3 16384 18431 1024K kb 4 18432 20479 1024K dkb 5 20480 22527 1024K lk 6 22528 32767 5120K tee1 7 32768 43007 5120K tee2 8 43008 123903 39.5M metadata 9 123904 124927 512K MISC 10 124928 141311 8192K reserved 11 141312 174079 16.0M boot_x 12 174080 208895 17.0M recovery_x 13 208896 3515391 1614M system 14 3515392 4383743 424M cache 15 4383744 60619775 26.8G userdata 16 60619776 60845055 110M boot 17 60845056 61070335 110M recovery

Extract the original recovery.bin from the amonet-suez-v1.1.2.zip and adb push it to /sdcard. Then via adb shell as root:

dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p17

Then adb reboot recovery and immediately reboot the tablet back into the freshly restored Amazon recovery.

From there you can choose update from adb and adb sideload update-kindle-Fire_HD10_7th_Gen-40.6.5.9_user_659662020.zip to reflash the current Amazon firmware. After installing and rebooting my tablet started looping through the "optimising storage and apps" - if that happens to you then rebooting to recovery again and formatting data/reset to defaults fixed that and the tablet then finally made it all the way back to the "Welcome to Fire" introduction screen.

Obviously this procedure will completely wipe and default the tablet and I've only tried it once - YMMV.

@8bitword: Presuming your partition table looks exactly like mine did then the exact same procedure should apply to you. If not post it here.

Hope that helps someone else - looking backwards through the thread other people have done this several times lol. I guess next I'll find out if the whole unlock+root procedure is still valid in Feb 2023.

 

[8bitword]

Thank you for your assistance, Lineage 16.0 working fine.

 

[spartasr]

Sorry if this was asked already, but as anyone figured out a way to get hands free Alexa or Google voice assistant working? I thought about trying to get pixel launcher but not sure if that would support it. I am getting the feature is currently unavailable message when trying to activate it.

 

[smithbill]

Sorry if this was asked already, but as anyone figured out a way to get hands free Alexa or Google voice assistant working? I thought about trying to get pixel launcher but not sure if that would support it. I am getting the feature is currently unavailable message when trying to activate it.

As far as I am aware, to get handsfree Alexa working, you *have* to use FireOS (that's why I ended up returning to stock FireOS). But with root, you can replace the launcher & debloat it quite a lot whilst keeping Alexa alive.