[ROM][testing][mustang] Lineage-16.0 [25 Jan 2022]

[douginoz]

For those wondering if they can install this on their latest tablet, I had the latest stock Fire OS rom, 7.3.2.1 installed on a Fire 7 version 9, M8S26G model.
I used the hw method to unlock the tablet, then installed twrp 3.3.1-0, lineage-16.0-20210312-UNOFFICIAL-mustang.zip, and gapps.

The latest (as of this writing) gapps, namely
open_gapps-arm-9.0-nano-20211028.zip
open_gapps-arm-9.0-mini-20211028.zip
open_gapps-arm-9.0-stock-20211028.zip

Don't work with this ROM, but the previous one from 20211021 (at least, the nano (speed good), stock (unusably slow), and mini ones) do.
I'll continue testing but so far, the setup app is working ok.

 

[douginoz]

A couple of things I noticed missing from the Settings app. When you enable developer mode, the developer menu item doesn't appear. Also, the Multiple Users menu item isn't there. Both can be searched for within Settings.
I also tried installing Plex but no videos play even though I used that other app to enable WebM as default. I suspect Plex ignores that anyway. I also tried configuring Plex to use an external video player and installed vlc. Nothing played.
This is on Lineage-16.0 12 Mar 2021 version.

 

[monsieur goonie]

hello, was wondering what it would take to port this Los version to ford version of Amazon fire 7.


regards

 

[dathappy]

Thanks for making LineageOS work on the Fire 7. It's so much faster now.
@ggow
Since you already fixed the cameras, I was wondering if there's any chance to get a release with this fix?
I'd love to use it with the motion detection feature of the fully kiosk browser.

 

[illfell58]

For those wondering if they can install this on their latest tablet, I had the latest stock Fire OS rom, 7.3.2.1 installed on a Fire 7 version 9, M8S26G model.
I used the hw method to unlock the tablet, then installed twrp 3.3.1-0, lineage-16.0-20210312-UNOFFICIAL-mustang.zip, and gapps.

The latest (as of this writing) gapps, namely
open_gapps-arm-9.0-nano-20211028.zip
open_gapps-arm-9.0-mini-20211028.zip
open_gapps-arm-9.0-stock-20211028.zip

Don't work with this ROM, but the previous one from 20211021 (at least, the nano (speed good), stock (unusably slow), and mini ones) do.
I'll continue testing but so far, the setup app is working ok.

Hi, I also have the same tablet hardware version as you with fire os 7.3.2.1. I've been trying to perform the hardware unlock method with the contact point suggested in the main post but the script gives me an error every time. Did you use one of the other three pads?

The full terminal message I get is:

sudo ./bootrom-step.sh
[2021-11-25 00:15:12.317302] Waiting for bootrom
[2021-11-25 00:15:22.883141] Found port = /dev/ttyACM0
[2021-11-25 00:15:22.922628] Handshake

* * * If you have a short attached, remove it now * * *
* * * Press Enter to continue * * *


Traceback (most recent call last):
File "main.py", line 161, in <module>
main()
File "main.py", line 82, in main
load_payload(dev, "../brom-payload/build/payload.bin")
File "/mnt/SEAGATE2000/Android Files/Android Custom ROMs/Fire 7 2019 Unlock/amonet-mustang/modules/load_payload.py", line 99, in load_payload
dev.write32(0x10007008, 0x1971) # low-level watchdog kick
File "/mnt/SEAGATE2000/Android Files/Android Custom ROMs/Fire 7 2019 Unlock/amonet-mustang/modules/common.py", line 147, in write32
self.check(self.dev.read(2), b'\x00\x01') # arg check
File "/mnt/SEAGATE2000/Android Files/Android Custom ROMs/Fire 7 2019 Unlock/amonet-mustang/modules/common.py", line 84, in check
raise RuntimeError("ERROR: Serial protocol mismatch")
RuntimeError: ERROR: Serial protocol mismatch

It seems to work for a second after the "Press Enter to continue" message but then it spits out an error once I press the key.

 

[Rortiz2]

Hi, I also have the same tablet hardware version as you with fire os 7.3.2.1. I've been trying to perform the hardware unlock method with the contact point suggested in the main post but the script gives me an error every time. Did you use one of the other three pads?

The full terminal message I get is:

sudo ./bootrom-step.sh
[2021-11-25 00:15:12.317302] Waiting for bootrom
[2021-11-25 00:15:22.883141] Found port = /dev/ttyACM0
[2021-11-25 00:15:22.922628] Handshake

* * * If you have a short attached, remove it now * * *
* * * Press Enter to continue * * *


Traceback (most recent call last):
File "main.py", line 161, in <module>
main()
File "main.py", line 82, in main
load_payload(dev, "../brom-payload/build/payload.bin")
File "/mnt/SEAGATE2000/Android Files/Android Custom ROMs/Fire 7 2019 Unlock/amonet-mustang/modules/load_payload.py", line 99, in load_payload
dev.write32(0x10007008, 0x1971) # low-level watchdog kick
File "/mnt/SEAGATE2000/Android Files/Android Custom ROMs/Fire 7 2019 Unlock/amonet-mustang/modules/common.py", line 147, in write32
self.check(self.dev.read(2), b'\x00\x01') # arg check
File "/mnt/SEAGATE2000/Android Files/Android Custom ROMs/Fire 7 2019 Unlock/amonet-mustang/modules/common.py", line 84, in check
raise RuntimeError("ERROR: Serial protocol mismatch")
RuntimeError: ERROR: Serial protocol mismatch

It seems to work for a second after the "Press Enter to continue" message but then it spits out an error once I press the key.

This isn't the correct place to discuss about the unlock. You should ask for help here.

RuntimeError: ERROR: Serial protocol mismatch

Means the tablet was in Preloader Mode (08ed:2000) when you tried the script so probably you have a patched (HW) revision which prevents you from triggering bootROM mode.

 

[illfell58]

This isn't the correct place to discuss about the unlock. You should ask for help here.

Directly asking the person who seemed to have hands on experience sounded like the fastest option, my bad. Since I imagined that the hardware method wouldn't work I was surprised to see another person with seemingly the same device having gotten the exploit to work. I'll ask there too.

Means the tablet was in Preloader Mode (08ed:2000) when you tried the script so probably you have a patched (HW) revision which prevents you from triggering bootROM mode.

Do I have any other option? From your post it sounds like I'm out of luck. Any guesses as to how douginoz managed to get it to work if the devices have the same model number though? Or is the model number kept even after the hardware undergoes a revision?

 

[Rortiz2]

Directly asking the person who seemed to have hands on experience sounded like the fastest option, my bad. Since I imagined that the hardware method wouldn't work I was surprised to see another person with seemingly the same device having gotten the exploit to work. I'll ask there too.

Do I have any other option? From your post it sounds like I'm out of luck. Any guesses as to how douginoz managed to get it to work if the devices have the same model number though? Or is the model number kept even after the hardware undergoes a revision?

Im not sure if model number has something to do actually. But yeah, if it's a patched HW revision nothing can be done (at the moment). If it's not a patched HW unit, all I can say is keep trying and make sure you're shorting the correct pin + you're using something conductive.

 

[illfell58]

Im not sure if model number has something to do actually. But yeah, if it's a patched HW revision nothing can be done (at the moment). If it's not a patched HW unit, all I can say is keep trying and make sure you're shorting the correct pin + you're using something conductive.

I see. Any way to definitively identify which hardware revision I have? The only information the PCB has on it says "A1926_MB_PCB_V7" on top of the battery connector.

 

[dathappy]

I had issue with notifications being delayed. Since I don't use messaging on the tablet I can't say if the messaging app would be affected too. For me it was Home Assistant and my Doorbell.

I tried disabling the battery saving feature for those two apps as well as some other system apps which sounded like it could help. I also checked via ADB to make sure the apps are whitelisted.
Unfortunately it did not work, so I disabled deep sleep altogether (adb shell dumpsys deviceidle disable).
Now notifications come in as expected and battery drain did not increase noticeably.

 

[astrononix3000]

In a post on another topic you said that meanwhile you just concentrate on 14.1 development. So would you recommend to install the discontinued version of 14.1 from now on as you will update it sooner or later again? Or did you mean it any different?

 

[thebigphatmaster]

I would also like to know this (assuming the black screen issue has been fixed on 14) as unfortunately no cameras on 16 has become a deal-breaker

 

[keeepinitgansta]

I've got youtube (vanced) working fine on this lineage 16 build but am having issues with Wifi staying connected and the constant wifi searching is draining the battery fast.

 

[ggow]

Hello, hope everyone is well.
I haven't got a mustang tablet at the moment. They were damaged in the flood that happened.

I have done a build which should fix the cameras, would someone be willing to test it for me before releasing it?
Let me know if you're willing to test and I'll message you with the link on PM.

 

[Graysters]

Hi ggow! Great to see you back!

I'm assuming this Is this just for mustang, or could it work on austin?


(I can help on austin, but sadly no mustang unit here either!)


Cheers,

Graham

 

[ggow]

Hi Graham,

Won't work on Austin. Mustang is a different beast.

 

[thebigphatmaster]

I have a mustang unit (well my daughter does) in a pretty minimally set-up state after leaving L14 because of the black screen issue - presumably its just a case of flashing the rom and gapps via twrp?

 

[ggow]

I have a mustang unit (well my daughter does) in a pretty minimally set-up state after leaving L14 because of the black screen issue - presumably its just a case of flashing the rom and gapps via twrp?

Should be able to just dirty flash the rom if you previously flashed opengapps. I'll PM you the link.

 

[keeepinitgansta]

Hello, hope everyone is well.
I haven't got a mustang tablet at the moment. They were damaged in the flood that happened.

I have done a build which should fix the cameras, would someone be willing to test it for me before releasing it?
Let me know if you're willing to test and I'll message you with the link on PM.

I can test the camera build as well if you'd like.

Would you be able to look at the unstable wifi issue by any chance?

 

[ggow]

I can test the camera build as well if you'd like.

Would you be able to look at the unstable wifi issue by any chance?

PM'd.

Can't look at the WiFi, as I have no tablet at the moment. I remember it been quite solid on my home setup. What problems are you seeing?