yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Guides, News, & Discussion] hacker812c:
Thanks for participate my friend

Some users repport root perfectly
[Treble-Enabled Device Guides, News, & Discussion] hacker812c:
hello my friend havoc fail with magisk root

In this moment unique sokution is this rootif possible press thanks in First thread
[Treble-Enabled Device Guides, News, & Discussion] hacker812c:
NikGapps download

NikGapps - Browse /Releases at SourceForge.net

A Custom Google Apps Package that Suits Everyone Needs!

sourceforge.net
[Treble-Enabled Device Guides, News, & Discussion] hacker812c:
This method is tested in Android 10 and 11
[Treble-Enabled Device Guides, News, & Discussion] fleafred:
Hello again hacker812c !

My rom is yours :SuperiorOS Android 11 for Samsung Galaxy A51 ,working fine .

I have error 7 too .My twrp is 3.5.0 and my phone is A51 arm 64 a/b...

Any idea ?

Have a nice day .
[Treble-Enabled Device Guides, News, & Discussion] fleafred:
Hello everybody,

Still no idea ?

(I don't want to try framaroot...!

See U.
[Treble-Enabled Device Guides, News, & Discussion] JuanTamqd21:
is there any unistaller for this? I used this to gain magisk root and now that I have it, can i unisntall this supersu?
[Treble-Enabled Device Guides, News, & Discussion] speedson:
since you found a solution in another post. could you have deleted this request or marked it as no longer necessary.

solong

speedson 🤘 🙃 🤘
[Treble-Enabled Device Guides, News, & Discussion] Proibito04:
Same here, have you fixed?
[Treble-Enabled Device Guides, News, & Discussion] fleafred:
No !

I flashed RefinedUI wich is very fast and stable.

Bye !
[Treble-Enabled Device Guides, News, & Discussion] mOlDaViA:
Not working on SuperiorOS A51. Update error 7.
[Treble-Enabled Device Guides, News, & Discussion] hacker812c:
Some users confirmed sucessfull
[Xiaomi Poco X3 NFC Questions & Answers] kapiten22:
I'm not a gamer, I only play chess, I just watch a whole lot of Youtube and Tiktok, some fantasy sports apps, reddit, whatever, pretty easy on the phone. After like two months, one day it got like the old TVs "snow" during bootup, it lasts for one second, but it always shows during bootup. Also, once the screen goes to sleep I can't do anything to wake up the phone. I use fingerprint, doesn't work. What I noticed is that only the screen doesn't wake up, phone actually works, because I do have a vibration when I try the wrong finger also apps keep running. Now I set it to never sleep and it's ok, but of course I don't want it to continue like that. It's under warranty so I can exchange it but does anyone know anything about it? It's on MIUI Gobal 12.0.7

Thanks
[Xiaomi Poco X3 NFC Questions & Answers] jeryll:
recommended:

- try to factory reset your phone

- reflash MIUI via fastboot with Miflash

...in both cases backup your internal storage because it will be probably formatted...

... honestly, that behavior looks to me like HW issue, so return it if it's still under warranty, if none of the above helped
[Huawei Mate 10  Guides, News, & Discussion] snkchaos:
I notice this version doesn't get updated so it may be different from EU/Asia version.

I connected this to all in one type c 3.0 hub with 4k hdmi support to a monitor that is 2560x1080. It only does 1920x1080 or phone mode at 2160x1080. I'm pretty sure this can be set to 2560x1080 since phone mode can output 2160x1080.
[Magisk] Jesus is God Almighty:
Someone has made a good guide to unlock the new phone from Shift, the 6mq with the 3 essential features any phone should have. Removeable battery, Jack phone and Micro SD!

Here is the guide: SHIFT6mq - Bootloader unlock / Root / Custom Recoveries / ROMs | SHIFTPHONES

And if anyone wanna have a look on the new phone from Germany... *Looking around for the links*

Shift Shop | SHIFT6mq (preorder) (shiftphones.com)

SHIFTPHONES - Nachhaltige Technologie aus Deutschland

It is a small German Company, this phone is the replacement of my LG V20 - although have yet to use it as my daily driver. I have now rooted the Shift 6mq and gotten Stock Light on it without Google. The Shift Team are working on 2 systems for it, a Google version and a non-google version!

I don't know if Magisk is in all support of the Phone, but it does seem to work nicely as far as I can see. If I hit into any issues I will report them.

Dearly regards

- Darkijah
[Xiaomi Poco X3 NFC Questions & Answers] CreepaMonsta:
Hello guys,

So I bought my phone almost 2 months ago and it performs good most of the time. However my Antutu Benchmark is really low for a device that was advertised with 300k Antutu benchmark score which is weird. In the following Screenshot you can see that my score is almost 100k less than the advertised 300k. I don't know if I should return the device or if it's my fault.. Even though I don't have much space left, it shouldn't affect the GPU performance that much. To be honest, I feel like the performance is sufficient for my usage but I'm still wondering what's causing this low score. Anyone has an idea?
[Xiaomi Poco X3 NFC Questions & Answers] Abdullah.Csit:
Just Unlocke bootloader And flash Custom roms with good kernel

You will got 291k and even 300k

what's your current miui version ?
[Touch Diamond, MDA Compact IV General] mterrey:
Hi,

I've got one of those 3 Mobile Broadband dongles and have been trying to use the sim card in my HTC Touch Diamond and surf the net in 3G on there. The only problem is I've got no idea how to set it up and the 3 Mobile support site in less that useless! Has anyone else successfully done this?

Thanks!

Mark
[Touch Diamond, MDA Compact IV General] 964rs777:
the website would be useless.

3 dont sell the diamond so they are not going to support it.

try using the settigs off a phone they do sell.might work.
[Touch Diamond, MDA Compact IV General] mterrey:
sounds like a good plan.. all I need now is those settings :) anyone here happen to have the 3g mobile settings for their 3 mobile phone to hand? :)
[Touch Diamond, MDA Compact IV General] mterrey:
It worked out quite simply in the end. All I needed was the APN set to three.co.uk in the settings - simple as that. Thanks all for your help..
[Fire Original Android Development] ggow:
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 here before flashing it!
* YOU are choosing to make these modifications.
*/

- EVEN MORE IMPORTANT: This ROM only works on devices using the bootloader hack.

- IMPORTANT: Do not update Magisk via the Magisk Manager App, your device will enter a bootloop if you do. Instead update Magisk via TWRP only. If you do this by accident then it is recoverable by just flashing the latest version of the ROM again (with gapps etc as required). This will be fixed in a later update.

Rules

- Please search the thread before asking questions

- Please try to stay on topic, I know it's not always possible

- Please report bugs here

- Report only one issue per bug report

- When reporting bugs please post a logcat and/or dmesg where possible

- Saying something isn't working without proper explanation will not attract any attention.

Downloads

- Lineage-16.0 for Amazon Fire 7 (mustang)

Source Code

https://github.com/lineage16-mustang/kernel_amazon_mustang

https://github.com/lineage16-mustang/device_amazon_mustang

Thanks

- @k4y0z and @xyz` for the bootloader hack

- LineageOS
[Fire Original Android Development] ggow:
⏱ Change log / Release Notes

29 January 2022

- [Build] Dated 25 January 2022

- [fixed] Cameras not working at all

12 March 2021

- [fixed] Can't sign into google

- [fixed] Built in browser does not work

15 February 2021

- Initial Release
[Fire Original Android Development] ggow:
🛠 Worklist / Tasks

- [fixed] Bluetooth works

- [fixed] WiFi working

- [fixed] Audio works

- [done] Sensors working

- [fixed] Touch sounds are working

- [done] Test audio format playback - mp3 working

- [done] Tested video playback with NewPipe which is working

- [fixed] No adb during boot

- [done] Wired headphones working

- [fixed] Built in browser does not work

- [fixed] Can't sign into google

- [todo] Magisk update by app

- [todo] Support aptX-HD encoder for bluetooth

- [todo] Cameras not working at all

- [todo] Youtube, NewPipe, video playback
[Fire Original Android Development] ggow:
New Build is Up

15 February 2021

- Initial Release

- Stable with no crashes

- Change log on Post #2

- Task list on Post #3

- Cameras do not work for the moment

- Uses pie blobs from fireos 7

- Factory reset from TWRP is required
[Fire Original Android Development] YodaDude2011:
Will be checking this out! Let you know if I see any bugs
[Fire Original Android Development] YodaDude2011:
So far everything seems to be working perfectly. The only issues i can find are for some reason the default browser will not work and connection to google servers when signing in fails, which may very well be my crappy wifi but who knows. Well done @ggow good to see you back
[Fire Original Android Development] platypoid:
Not sure if it is your problem with signing in to Google but when I do older equipment sign ins I need to go to Google with another device and there is a place where Google gives you a code or something to sign in with - I forget now but have had to do it when setting up various things like old phones, or registering thing to connect to google and send email, etc.
[Fire Original Android Development] ggow:
Thanks for the feedback. The default browser is borked on this build for some reason, noted on tasklist. Are you saying you couldn't sign in to google play services at all?

I don't use gapps so wouldn't have picked this up.
[Fire Original Android Development] platypoid:
I was just about to load this and then I realized - Mustang is newer version of the Fire ? Does this mean I cannot load this on Austin Fire 7 ?

Thanks
[Fire Original Android Development] YodaDude2011:
Alright, I might have to push the apk for Chrome or something

No, this rom is for the 2019 fire 7
[Fire Original Android Development] YodaDude2011:
Yes, I cannot sign in at all. I even tried installing chromium and trying to sign in and it still failed. It'll pull up like the android setup thing and say checking for updates. After sitting like that for a couple minutes It'll say connection to Google server failed
[Fire Original Android Development] platypoid:
Try going to your google account then security and look for App Passwords

It will let you set up devices that can't support two factor authorization and generate a passcode.
[Fire Original Android Development] YodaDude2011:
I can't even get into my account. I haven't been able to even log in, it fails before the long in screen
[Fire Original Android Development] platypoid:
I just installed 14.1 on my Austen Fire. I was getting the same thing of endless checking for updates.

I restarted device, then checked setup as new, then it went through and asked for my google email and then the password. It then sent a message to gmail on my other fire and asked if it was okay for new device. Soon as I checked okay on the other Fire it made my Austen log in work .
[Fire Original Android Development] ggow:
I'll check that here, maybe the same issue as why the stock browser is not working.
[Fire Original Android Development] ggow:
I just checked, and can't complete the setup wizard successfully. Stuck at the Error couldn't sign in screen without option to do anything but going back for retry. I'll look into this and add it to the list.
[Fire Original Android Development] angry_goldfish:
I upgraded my old Mustang tablet today from the old Lineage 14.1 without a data wipe and everything seems to work. I'll wipe data if I have any weird problems.

I have noticed that my wifi unexpectedly turned itself off in two instances and seemed like it was having trouble associating with the AP in another. If I get a logcat of what is going on I'll post it.
[Fire Original Android Development] -ANDROlD-:
@ggow sorry to be offtopic but you seem to be of experience with Mustang.

I have a new fire 7 version 6.3.1.5 shipped and I assume won't work with the known hardware exploit?

Looking at a unrelated bootloader unlock thread from years ago that makes me want to attack from a hardware perspective on the PCB.

Do you know if anyone has tried accessing SPI/JTAG/UART for the Mustang specifically?

Also a alternative could be to cross reference a CVE list with the Linux kernel version or the CPU or the bootloader or the libc or something to gain temp root to flash TWRP?

There's got to be something that could be utilized. Stagefreight for example has been patched for years on mainline android and linux kernels but since fireos is a fork it might not always have applied every patch so there's probably a gaping hole somewhere left untouched.

Maybe one of the spectre exploits as some of the variants affected ARM CPUs

(meant version 6.3.1.5 not 6.1.3.5)
[Fire Original Android Development] ggow:
Read here on how to here to unlock your device:

Fire 7 (2019, mustang) unbrick, downgrade, unlock & root

Make sure to read this guide completely before starting. You will lose all data on the tablet, make a backup of important data before you start. What you need: - a Linux installation. Don't use a VM! Use a live USB, if you don't have Linux...

xdaforums.com
[Fire Original Android Development] -ANDROlD-:
Thanks for response.

The software route is patched. I'll keep trying with the hardware method but I think that's patched too so I'm trying to find another path if possible
[Fire Original Android Development] ggow:
Is there a new hardware version that blocks the bootrom exploit?
[Fire Original Android Development] -ANDROlD-:
I'm not certain if it's hardware or patched via software but my device has never been updated and it shipped version 6.3.1.5

It is patched for the Amonet software exploit I can confirm that.

When trying to enter bootrom mode from bridging the unmarked contact point under the shield I still get the following on linux dmesg when connecting USB:

[ +0.000003] usb 1-1.2: Product: MT65xx Preloader

[ +0.000002] usb 1-1.2: Manufacturer: MediaTek

I might not have the perfect connection so I can't be certain I'll try a couple more times. I'll probably have to attemp JTAG/UART/SPI because it looks like it might be. Are updates signed? I wonder if I can roll back firmware or if it is a newer PCB revision.
[Fire Original Android Development] Rortiz2:
If bootrom is not accessible, you most likely have the new hardware revision with USBDL disabled. The updates are signed yes. If you can downgrade the tab via stock recovery (I think Amazon removed the "Apply update from ADB Sideload" option so you probably can't), you'll probably end up with a nice brick due to RPMB.

About UART, TX / RX pads can be accessed if you flip off the motherboard. You can check a detailed picture of where they are located here.
[Fire Original Android Development] umaro:
Thank you for releasing this! It's working great! Except for gapps not working. I'm anxiously awaiting your update for that, but just wanted to say thank you and great job!
[Fire Original Android Development] astrononix3000:
Wow, very nice to bring Lineage 16 to mustang! I was a little bit confused about your release of Lineage 14 as it seems to have some unfixed issues and a looong discussion about it... I don't want to try it then and rather wait for this build being usable.

Are you considering to bring Lineage 16 also to austin and ford later? Thanks for your great work! :)
[Fire Original Android Development] Michajin:
Curious if bootrom is accessible on any of these with the battery disconnected. I found the maverick (hd10 2019) was. I will charge my mustang up this weekend (if i get time) and see if i can find alternate ways to access the bootrom. Does anyone know when the bootrom was totally disabled and if it was MediaTek or software disabled?
[Fire Original Android Development] -ANDROlD-:
The PostmarketOS wiki states it uses 921600 baud 8N1 for future reference.

I haven't tested anything yet but do you think it's possible to attain a root shell?
[Fire Original Android Development] -ANDROlD-:
I tried on 6.3.1.5 without battery without luck but I wasn't perfectly precise with the wire tbh.

It appears it was totally disabled with some version between 6.2.x.x - 6.3.1.5 roughly 3 months into 2020.

I'm thinking it was a patch that re-wrote some of the firmware because a CVE was issued for the mediatek CPU vulnerability "CVE-2020-0069" so bad that Google themselves (with other companies) stepped in because they have a lot of devices shipped and Amazon bundled up the patch themselves as they sold the tablet. (Mediatek only cares about selling chips evidenced in their GPL theft)
[Fire Original Android Development] Rortiz2:
I don't think you can get a root shell via UART. You should mention that this device is using Little Kernel (LK) and not UBOOT (which gives you shell access via UART) if that's what you meant.

If I remember correctly, if you patch the cmd line to set the prinkt.disable_uart flag to 0 (that's actually what a amonet does via lk-payload), you can get the standard Android shell with UART once it starts the kernel (but still not a root shell).

Yes, the baud rate of preloader (MT65xx) it's 921600 and the baud rate of bootrom (MT6627 / USBDL) it's 115200.

Anyway, I don't think this is the best place to talk/discuss about this. It's not related to the ROM at all and could confuse some people who want to install it.
[Fire Original Android Development] Michajin:
It seems whatever happened, happened to devices across the board on amazon. About March 2020 all the purchased ones, had the bootrom disabled. HD8 2018, HD10 2019, fire 4k, fire7 2019.... all had the same thing happen in the same time frame.
[Fire Original Android Development] Michajin:
My point is, i do not think a OTA blocked it... If you had the vulnerability it is still there. I am more than willing to test this theory, but i have to find a way to lock and restore factory os.
[Fire Original Android Development] astrononix3000:
Yes, it's a little bit confusing. Does that mean I cannot install this ROM on some later manufactured versions of mustang? Or even flash TWRP?
[Fire Original Android Development] Rortiz2:
Yes, that is correct.

Amazon has already started releasing new HW revisions of many of its products (Fire TV Stick 4K / 2nd gen, Fire HD8 8th gen, etc.) to disable bootrom (they probably burned some efuse) and prevent people from unlocking their devices with amonet/kamakiri.

Anyway, I'm not sure if they did the same with mustang (Fire 7 '9th gen). If someone else reported problems during unlocking (i.e tablet doesn't go over to MT6627), we would need to check SN to find out which devices can be unlocked (as we did in mantis).
[Fire Original Android Development] SirDigitalKnight:
Hey, I'm also on 14.1 and want to flash this as Sonos app no longer supports android 7. Can I just flash this on top 14.1? Do I need to install a new version of Gapps?

Thanks for any help.

Well I ended up doing a fresh install of the ROM and of Gapps for 9.0.

Like others here, it will not let me into Google to finish setting it up and gives the "There was a problem communication with Google servers. Try again later." error.
[Fire Original Android Development] ggow:
New Build is Up

12 March 2021

- [fixed] Can't sign into google

- [fixed] Built in browser does not work
[Fire Original Android Development] astrononix3000:
Nice, I'm already looking forward to working cameras :)
[Fire Original Android Development] ggow:
Working cameras will be in the next release (y)
[Fire Original Android Development] SirDigitalKnight:
Latest update does indeed seem to be working very nicely. One issue I notices was when trying to restore system from a cloud back up, the Google app restarts twice and then crashes.
[Fire Original Android Development] shimbob:
Hey, thank you for putting it together. Was gifted a Fire 7 Mustang, this all worked on first try. Except youtube. All youtube gives me is a black screen. It thinks it's playing the video but nothing's showing up. Widevine issue?
[Fire Original Android Development] fmc000:
@ggow , can we expect a similar ROM for the older FIRE devices, like Ford?
[Fire Original Android Development] ggow:
I think it's possible, been looking into it. However it may result in loss of cameras and other functionality at least in the short term.

I'm wanting to get all the amazon devices I work on onto lineage-16.0, easier to work on one rom for all.
[Fire Original Android Development] Sooperphone:
Got this working on my fire 7. Pretty amazing!

Having issues with YouTube playback with new pipe though. Setting default video format to WebM seems to fix it. Playback also doesn't work in Firefox.
[Fire Original Android Development] ScanuRag:
I'm having the same issue. I can't play YouTube in the app, on Firefox, or in NewPipe. I also can't play videos on cnn.com in Firefox. Setting the format to webp in NewPipe does fix it though.
[Fire Original Android Development] ggow:
Added video playback to the todo list
[Fire Original Android Development] G01:
Got this working on my fire 7. Mostly great so far.

A couple of things I noticed:

- after sign in it hangs checking for updates and fails. Hitting cancel works though.

- Tried to setup 2nd user account fort my daughter managed through Google Family Link and it failed (tried multiple things with no success).

- installed YouTube and YouTube kids, no video just audio.

- installed Chrome browser through Google Play. YouTube.com works there.

Love the Rom and the updates. Thank you.
[Fire Original Android Development] klamation:
I just wanted to add that I tested this on my Fire 7 (sage colour) as well. I got this device well over a year ago, around black friday in 2019, and I never connected it to wifi, so it was on whatever FireOS version it was on. Took me a while to remember how to install it, but with the XDA forum post (https://xdaforums.com/t/fire-7-2019-mustang-unbrick-downgrade-unlock-root.3944365/) I was successful.

I simply upgraded it the first try, which ended up consuming close to 8GB of space, so I went through TWRP and did a format on the storage and reinstalled, which put it down to about 6GB of used space. Not bad, got 10GB free.

Performance is really nice. I haven't fully tested everything yet, and I'm willing to go without a camera (they aren't great anyway), but I love what you did, ggow. Thanks for knowing more than I ever expect to!
[Fire Original Android Development] astrononix3000:
Hi, are you planning to release a new version in the near future? :)
[Fire Original Android Development] rudironsoni:
Hi!

Is there any update with video playback working?

I'm using 14.1 and will be awesome to have 16 working on our devices.

I can stick without the camera, is useless anyway, but not without video playback.
[Fire Original Android Development] stickfiretv2020:
Do you have a lk.bin handy for this? Looking into fbtool, for flashing this directly through modified fastboot, need a lk.bin which has secureboot disabled and fastboot enabled, is it possible to compile lineage like this?