[ROM] [unlocked] [douglas,giza] [OTAs] Lineage-14.1 [26 JUL 2021]

[Rortiz2]

I am not sure google apps like spoofed signatures. I have noticed this with other signatures too. While this makes both safety net checks pass, apps like YouTube, Keep Notes, Google either crash, or give you errors like "There was an error signing into your account".

Last time I was using Walmart Onn 7 or 8 or something to make ctsProfile pass. Same thing happened. I reverted back to the default signature and google apps started working again.

I see, I guess you tried to clean flash the new update? If it still doesn't work I guess I'll revert back to original fingerprints.

 

[anujdatar]

I see, I guess you tried to clean flash the new update? If it still doesn't work I guess I'll revert back to original fingerprints.

No, I have not tried to clean flash it yet, I did an OTA update. I just figured it was a fingerprint issue like before. But you are right, I should do that. I'll try clean flashing in the morning and get back to you.

 

[dadtrash]

Hey there,

You probably couldn't use the adb unlock method because as you said FireOS wasn't accessible at all.

That's quite interesting, could you send me some pictures of what did you short, please?

Thanks.

The adb issue happened after installing you rom, which runs very stable even for some games that need some power to render graphics.

When trying to "adb devices", I receive the following answer

dirk@v-debian:~/firehdroot$ adb devices
List of devices attached
G000KU067XXXXXX no permissions (user in plugdev group; are your udev rules wrong?); see [http://developer.android.com/tools/device.html]

Unfortunately, there was no android message coming in order to approve the adb connection on the tablet.

I tried to switch off/on the "Android-Debugging feature" in developer's menu. But no change.

adb via TWRP is still working. But as usual very slow.

Regarding shorting, I sent a picture via PM to you.

 

[anujdatar]

The adb issue happened after installing you rom, which runs very stable even for some games that need some power to render graphics.

When trying to "adb devices", I receive the following answer

dirk@v-debian:~/firehdroot$ adb devices
List of devices attached
G000KU067XXXXXX no permissions (user in plugdev group; are your udev rules wrong?); see [http://developer.android.com/tools/device.html]

Unfortunately, there was no android message coming in order to approve the adb connection on the tablet.

I tried to switch off/on the "Android-Debugging feature" in developer's menu. But no change.

adb via TWRP is still working. But as usual very slow.

Regarding shorting, I sent a picture via PM to you.

Okay, so when you connect the table to your computer you want to change it from "Charging Only" to "File Transfer". Tap on the charging notification to do this. The permissions issue should go away.

If you know you are only going to use your tablet with your PC, you can change the default behavior.

Settings > Developer Options > Networking > Default USB configuration. You can change this to "File Transfer". I believe the default is "No data transfer". Just be sure you are only ever going to connect the tablet to a trusted PC. Otherwise you can manually switch between usb profiles every time you connect.

 

[dadtrash]

Okay, so when you connect the table to your computer you want to change it from "Charging Only" to "File Transfer". Tap on the charging notification to do this. The permissions issue should go away.

If you know you are only going to use your tablet with your PC, you can change the default behavior.

Settings > Developer Options > Networking > Default USB configuration. You can change this to "File Transfer". I believe the default is "No data transfer". Just be sure you are only ever going to connect the tablet to a trusted PC. Otherwise you can manually switch between usb profiles every time you connect.

Hi thanks!

It works on windows, but not on debian. Not sure what's different.

 

[anujdatar]

Hi thanks!

It works on windows, but not on debian. Not sure what's different.

are you using adb from android studio or from the apt repository? sometimes you actually do have to change udev rules. i think you should be able to find instructions on what rule to add on google or stackoverflow

 

[Rortiz2]

Hi thanks!

It works on windows, but not on debian. Not sure what's different.

Have you tried setting up Android Udev Rules for Linux?

 

[Rortiz2]

No, I have not tried to clean flash it yet, I did an OTA update. I just figured it was a fingerprint issue like before. But you are right, I should do that. I'll try clean flashing in the morning and get back to you.

I will wait for your report then, thanks.

 

[dadtrash]

Have you tried setting up Android Udev Rules for Linux?

Setting up udev was the solution, now it works. Thanks!

Simoultaneuosly, I am having a karnak device. For that setting up udev was not required. lsusb shows that the karnak is spoofing a Google Pixel. For that it seems to be built into adb already on debian.

 

[gqbigpaps]

I will wait for your report then, thanks.

Clean install seems to solve the problem. I guess the OTA was the culprit.

 

[anujdatar]

Clean install seems to solve the problem. I guess the OTA was the culprit.

Cool, thanks. I will do that. Haven't gotten around to it yet. If it is some configs stored by Google services, then maybe just a factory reset might fix it too.

The charge port on my tablet has been acting funny. It refuses to charge from time to time, battery level's been stuck at 25% since last night. I've tried a few temporary fixes, but they're just that - temporary. Haven't found a suitable replacement yet. I ordered some micro-usb ports, but the mounts don't match this tablet.

 

[lex66676]

Professional work, thank you so much, bugs and problems have not been revealed.(Fire HD 2017 lineage-14.1-20210813-UNOFFICIAL-douglas )

 

[anujdatar]

Okay, so seem to have fixed the charge port issue, at least temporarily. Re-soldered the existing USB port, hope it lasts this time. Just using a hot air station to reflow solder in the existing joints did not work for long last time.

I will wait for your report then, thanks.

Clean install seems to solve the problem. I guess the OTA was the culprit.

If it is some configs stored by Google services, then maybe just a factory reset might fix it too.

A simple factory reset from TWRP seems to have fixed the issue for me. I guess Google does not like the device signature being changed on an active device. I guess that was the issue last time too, I changed the device signature after I had already set everything up.

All Google apps seem to be working just fine now. No crashes yet. It also passes both SafetyNet checks.

Thanks.

 

[SamDungUser]

Okay, so seem to have fixed the charge port issue, at least temporarily. Re-soldered the existing USB port, hope it lasts this time. Just using a hot air station to reflow solder in the existing joints did not work for long last time.





A simple factory reset from TWRP seems to have fixed the issue for me. I guess Google does not like the device signature being changed on an active device. I guess that was the issue last time too, I changed the device signature after I had already set everything up.

All Google apps seem to be working just fine now. No crashes yet. It also passes both SafetyNet checks.

Thanks.

When Magisk says SafetyNet API Error lmao

 

[anujdatar]

When Magisk says SafetyNet API Error lmao

Hmm.. haven't seen that one before..

 

[SamDungUser]

Also, one thing to note. There's a bug within the casting feature within the douglas devices. Casting to anything won't work.

Example:

On your fire tv stick you enable casting to the stick, when you go to Display > Cast on the tablet and enable wireless display give it a minute and it shows up. You press it and it seems to start but it quickly disconects and the fire tv stick says display mirroring is exiting and on TVs it just goes black and disconnects. I don't know what will fix it or if giza has this exact issue.

 

[anujdatar]

When Magisk says SafetyNet API Error lmao

I think that could happen if you installed Magisk using the new apk. I don't think it works too well with this device/os combo.. Try installing the zip using twrp. I know that is not the supported method anymore, but I've had better luck with that, with recent versions.

you could also try to hide your magisk installation. i don't think SafetyNet checks for it, but won't hurt (i think)..

 

[Rortiz2]

New build is up

2021-08-26 [douglas] [giza]

• Updated wpa_supplicant_8 HAL.
• Now building libwifi-hal-mt66xx.
• Rebased the kernel source to the latest Amazon sources (Fire_HD8_7th_Gen-5.3.7.3.tar.bz2).
• Set build characteristics to tablet.
• Dropped prebuilt lights HAL, now building it.
• UID_SYS_STATS are fully functional now.
• [Kernel]: Upstreamed Power/PM drivers.
• Synced with LineageOS sources (cm-14.1).

NOTE: OTA should roll out in a few minutes. If it doesn't, you can always update by manually flashing the ZIP through TWRP.

 

[cultofrobots]

Verification fails on OTA update for giza.

 

[Rortiz2]

Verification fails on OTA update for giza.

Yeah, it does as well for douglas, not sure what's wrong. Try to update manually, please.