yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
so in short , can i flash all fastboot file rom through miflash even though it is not my stockrom? will my phone be dead? btw my phone is poco f3 global and i want to flash poco f3 china fastboot file rom through miflash would it be possible?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
In practice, miflash is used to flash only the fastboot stock roms.

What I tried to do is go from European to global and vice versa, it works, I have never tried to flash the Chinese rom, however I do not recommend it because there are no Google services. The Chinese one is meant for China so the network may not work in your country. It might work but I can't give you the certainty I never did.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
thankyou for giving me knowledge and understanding i appreciate it v:D
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
@khazzey It's a pleasure if I can help.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
way back, i flashed android 12 stock rom and it doesnt support twrp encryption, so that i decided to go back to my stock rom android 11 using fastboot miiflash, when im already at flashing, miflash stated crclist error couldnt flash my stock rom back then tried to reboot my phone to fastboot again after that, my phone wont boot up even fastboot or recovery it is completely dead and when i connect it to miflash it needs edl authentication, i paid it and flashed my stock rom back so that from now on i am afraid to install twrp again the repair cost 30 dollars, i wonder why my phone got hard bricked theres nothing wrong flash that ive done
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
Unfortunately you are not the only one who has had problems after installing android 12.

It's still too early and android 12 is still in its infancy, however I don't think the problem is due to twrp.

The crc or sparse error did it to me too miflash, sometimes it solves restart the pc, phone, change usb port, reinstall the drivers, reload the rom. Miflash is a bit pretentious ...
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
i was wondering why i got my hard brick state i tried to reboot my phone and it automatically hard bricked
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
then when i got edl auth and booted back my phone normally, i tried to flash again the twrp via install recovery ramdisk of vasishath after reboot hard bricked again i payed double as h3ll thats why im afraid to put twrp back and flash custom rom again.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
It must be said that twrp is also in an embryonic stage so it can create problems, unfortunately it is a new phone and the development of these things takes time by the developers, it is always a risk

I only used the one from nebrassy, and I successfully flashed xiaomi.eu, both beta and stable. For the moment I avoid flashing android 12, I don't want to risk a hardbrick.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
The TGZ-format is another form of a compressed folder (just like ZIP, RAR, etc..)

You need to extract it first and use ADB.

You can only use Recovery ROMs in TWRP. (because TWRP is a Recovery Mode)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
oh. I'm sorry that happened. Was it through Fastboot ? That sucks lol

Unfortunately, it's always hit n miss with these tools... I wouldn't even trust ADB/Fastboot 100%. ADB is by Google, but each phone manufacturer still cooks their own soup in how they implement it, and you won't know right off the bat.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
it all started when i flashed android 12 using twrp then go back to stock rom using mi flash because twrp cant decrypt data, going back to miflash i had crclist or sparse error when i tried to flash my global stockrom again then tried to reboot again my phone to fastboot mode charaaaaaan!!! no recovery and fastboot state, spend 30 dollars to had an edl account auth, when its already flashed stock rom via edl account, i tried to flash twrp vasishath build through adb reboot fastboot and booted up twrp, when i am going to install recovery ramdisk it shows error cannot repack twrp boot failed, when rebooted and again unfortunately it begans to hard bricked again, payed 30 dollars again using edl account flash hows that even possible i didnt have the wrong flash one and i even dont flash wrong rom and locked bootloader, my bootloader is always unlocked i never close it back how is it possible that i hard bricked my phone i cant even explain it.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
Oh ok. Then that Mi Flash Error must've occurred at the stage where it flashes the boot.img (responsible for Fastboot Mode & Recovery Mode)

I want to try out Android 12 as well, but I'll wait. I use MIUI and want to try out Xiaomi's version of Android 12, but it's very early (first MIUI build with Android 12 came out). I also use my phone for banking stuff and authentication, so setting my phone up again takes a lot of time and is a pain in the ass.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
i wonder if is it affecting my flashing process because i use windows 10? way back before i am using windows 7 and everything works flawlessly.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
Nah. That's not a problem. I use Win10 too, and so do many others
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
the big question here is why does my phone went back to hard bricked when I already flashed stock rom using miflash with edl account auth then my bootloader is unlock also how's that even possible?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
i am trying to install twrp via fastboot
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
when booted up and planning to install recovery ramdisk the flash was failed and got hard bricked again lol
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
wtf ?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
im not lying fck as h3ll android 12 literally destroyed my phone.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
View attachment 5441809

@dreamytom and @RollDload can i flash this on my poco f3 using mi flash even though i am global? btw that fastboot rom is china based and has a .tgz file
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
and for example i am able to flash this china stock rom, can i go back to my global one? using miflash too?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
It might work, but I don't guarantee it, I never did! Then, however, the Chinese Rom does not have Google and does not even have all the languages, plus it has all the apps designed for the Chinese market.

I'm not even sure if the network services work in your region, (each country has its own and in the global there are all those needed to work in the countries where it is sold) I use the stable xiaomi.eu v12.5.14 which is based on that but optimized to work outside of China, honestly I'm fine with that, you can try that
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
i already tried yhe chinese version weekly and theres a google play store on it the on that destroyed my phone chinese 12.0 android early stage
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
can i have the link(xiaomi.eu) be sure i can flash it without twrp i dont want the recovery file of it
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
if theres a fastboot rom can i have one?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
No, the stable xiaomi.eu v12.5.14 only has a recovery file, but you have to use this twrp:

https://xdaforums.com/t/recovery-alpha-teamwin-recovery-project.4272625/

And this is the Rom I'm talking about:

xiaomi.eu_multi_HMK40_POCOF3_V12.5.14.0.RKHCNXM_v12-11.zip | by Xiaomi.eu for Generic Device/Other

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
im so afraid the second time around my phone was hard bricked because i tried to install twrp and it failed got error
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
don't risk it then ...
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
this global **** rom sucks definitely drained my battery so fast
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
The European stock is better, when I still had the 12.5.3_eea I only charged it once a day and it made me more than 10 hours of use
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Alin45:
@khazzey Always is risky to flash custom ROMs...even another stock ROMs other than the one who came installed to ur phone....so, long story short, if u wanna flash other ROMs u have to assume the risks.

Regarding to flashing xiaomi.eu ROMs (and other custom ROM who can be flashed by TWRP), u can use TWRP to install ROMs without flashing it (fastboot boot xxxxx.img). Btw, xiaomi.eu ROMs have TWRP included in the ROM, so it will be installed automatic with the ROM.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
oh i get it i will boot twrp up and not install it, will use twrp to install custom rom.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
Yes. Try to first just recover your phone with EEA or Global, whatever came with your phone.

Not sure if Chinese ROM is recommend....

And watch some YouTube videos about the process, if you're unsure.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
which one do you prefer? EEA or xiaomi eu? if xiaomi.eu whats the difference between RKKCNXM and RKHCNXM?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
Xiaomi.eu is a Custom ROM created by hobby developers. They are not affiliated with Xiaomi. Unlocked bootloader is required to flash this.

Xiaomi.eu uses the latest Chinese ROM as its base (China always gets updates first). It's then modified to better suit other markets, not only China. It also comes with built-in Custom Recovery TWRP and has latest system apps like Mi Phone with Call Recording etc.

EEA (~European Economic Area) and Global are Stock ROM.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
for the moment i'm preferring the latest stable of xiaomi.eu.

Both stocks (EEA \ Global) and castom (beta \ stable) have their pros and cons.

Like in the eea the battery lasts a little longer and has a few minor bugs, but it has been more than two months without an update and has certainly less functionality than the castom.

Xiaomi.eu for its part also has the latest security patches, being based on the latest Chinese update (they are more up to date and they are the first to do so) then what I like is that it uses the launcher by xiaomi. So the phone, address book and message apps are not Google's and I prefer them.In addition, there are some more features that in the stable versions there are not and perhaps never will be, you have to come to a compromise. The question to ask is: what am I willing to give up?

I like to change, but with this thing that you have to set it all over again every time it's a bit of a bummer, so I'm a little fed up
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
ive successfully and bravely flashed xiaomi eu to my device latest 12.5.14 its good but when i play mobile legends it cannot maintain 60 fps it is fps dropping :(
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
I'm glad you managed to flash without problems, unfortunately on the games department I can't help you because I generally don't play, I didn't know it was worse in that department 😟
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
im just like ironman, what ever it takes i will take the risk of having hard bricked again but fortunately it works haha game fps sucks on this rom
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
btw le me ask you, there are lots of member here on xda why nobody shares about edl account for free or any tutorials?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
This is the classic million dollar question 😜.

Edl accounts are generally reserved for authorized service centers, then for the rest I do not know is a good question. However, if a hardbrick still happens to you, I suggest you take it to a service center, most of the time they repair it for free.

I have a question, but to activate the edl mode you had to open the phone and short circuit the pins of the board?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] khazzey:
as long as in device manager you'll see your phone driver 9008 hs loader there is no need to short circuit pins and when its not detected long press volume down and power button it will automatically detect qloader mode. Your question is so called testpoint.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
​

Disclaimer

/*
* This ROM will eat your cat
* 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.
*/

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.

- This ROM only works with unlocked Fires!

Rules

- Please search the thread before asking questions

- Please report bugs here

- Report only one issue per bug report

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

Prerequisites for Installation

- Unlocked Bootloader

- TWRP Installed

Install/Upgrade the ROM

- Boot to TWRP

- Go to wipe and wipe: system, data, cache

- Go to install and flash ROM.zip

- Flash G-APPS (Optional)

- Reboot

Downloads

Lineage-18.1- for Amazon Fire HD 8" 2018

G-APPS (ARM)

Source Code

- Kernel Source: https://github.com/mt8163/android_kernel_amazon_karnak

- Device Tree: https://github.com/mt8163/android_device_amazon_karnak/

XDA:DevDB Information

Lineage-18.1 for Fire HD8 (karnak), ROM for the Amazon Fire HD 8 and HD 10

Contributors

Kaijones23, Rortiz2, t0x1cSH, k4y0z

ROM OS Version: Android 11

ROM Kernel: Linux 4.x

Version Information

Status: Testing

Current Beta Version: 0.1

Beta Release Date: 2021-10-28

Created 2020-10-25

Last Updated 2021-10-28
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
Changelog

[10-27-21]

* Fixed Codecs by Downgrading the kernel Patches from Fire OS, Somehow Amazon Devs Messed This up :/

* Fixed Camera, Camera Recording Still Dim and Lag, Photo Mode is in Normal Op

* Changed Build to Userdebug

[10-28-21]

* Fixed Codecs Glitching out thanks to Rortiz2

* Updated Fingerprint to Redfin

* Enhanced Wifi 5G

* General System Improvements
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
Worklist / Tasks

- [Fixed] Codecs not working

- [Fixed] Camera not working

- [Fixed] switch to userdebug build

- [Fixed] Fixed glitches in the codecs

- [Fixed] persistent notification from "Android System"

- [Fixed] Live Display Flickering

- [Fixed] fix Codecs fdsan being crashed.

- [Fixed] Updated Signature spoofing To Pixel 5

- [todo] Fix Camera Dim in Recording Mode

- [todo] Make graphics smoother
[Fire HD 8 and HD 10 Original Android Development] blakegriplingph:
Noice one fam, keep it up!
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
yes it will still work if you did that method
[Fire HD 8 and HD 10 Original Android Development] Amelios:
Getting stuck during initial setup "Getting your tablet ready..." Seemed like it could connect to wifi, but then would fail to communicate after that. Maybe a Gapps issue (using nano)?
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
try using a different Gapps package
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
I Have released the new build please update, This is an mandatory fix to the codecs and the camera :)
[Fire HD 8 and HD 10 Original Android Development] Amelios:
No dice. Had the same issues with both nano and stock GApps. Wiped and reflashed a couple of times.

I feel like I might've had some sort of weird wifi-related issue with a previous release, but don't remember getting stuck like this. Can't make it through any of the initial setup (even when I try to do offline).
[Fire HD 8 and HD 10 Original Android Development] tiiash:
Had the same issue and, due to the comment of @Kaijones23, tried to fix it by using MindTheGapps. With this package, I could pass the "getting your tablet ready" step but was then stuck in a setup loop. Whenever the setup came to the speech activation step (which I wanted to deny), it jumped back right to the beginning.

So maybe MindTheGapps isn't the right choice either?

Additionally, today's update introduced a strange flickering of the display color temperature. Everytime I tap the screen, the color changes. It is almost as if nightmode would constantly toggle (this is unrelated to Gapps and happens also when flashing only the rom itself).
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
mind the gapps will work and i will fix the problem next update, you can turn it on night mode cause that stops it from flickering
[Fire HD 8 and HD 10 Original Android Development] man89_au:
Yes. I tested the 27 Oct beta.

I had same issues for videos with newpipe and YouTube.

Mind your gapps work on my device.

Confirm that SD card is detected on boot
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
do you have the latest twrp? if not you can download here

https://cdn.discordapp.com/attachments/618551795915948042/902978379404443648/new_twrp.img
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
Released the update for Fixing livedisplay issues by adding the vendor hal with the lineage
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
I have uploaded the updated version of the ROM
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
i would use vandced instead of newpipe temporary until we work on fixing the issues
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Yes, we're aware of that issue already. My patch only fixed the fdsan error (and after that, some apps like VLC started working). The newpipe crash is completely different (needColorConvertWithNativeWindow). As kai suggested already, you can use Vanced youtube in the meantime (since it's working now).
[Fire HD 8 and HD 10 Original Android Development] temijun:
Thanks for the amazing work and brining this device back to life.

On the 20211028 build, I noticed that we are spoofing the device fingerprint Pixel 5. I tried SafetyNet test which came back as failing the basic test. This is needed to install apps like Netflix and Disney Plus.

I tried the standard HideProps and they all seem to fail. I wonder if there is something related to the ROM.
[Fire HD 8 and HD 10 Original Android Development] NellyWhads:
Upon seeing this thread I have elected to pull the trigger on a 2021 Fire 10. Thanks for all your work on this - though I'm long out of touch with my java skills (used to maintain the GS3 for Ground Zero Roms), I will at least be more than happy to beta test.

Cheers, and stay well
[Fire HD 8 and HD 10 Original Android Development] dontpanic-xda:
I didn't think there was a way yet to unlock any of the Amazon Fires newer than 2020.

Has this changed?
[Fire HD 8 and HD 10 Original Android Development] acat550:
Lol there isn't. Hence his message thanking him for his work while part of the fire 8 crew.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
You should install magisk to be able to disable that , it happens to me ill figure that fix out
[Fire HD 8 and HD 10 Original Android Development] NellyWhads:
Well this really dated me now didn't it. I haven't even flashed a fresh ROM on my OP5 in 2 years.

It seems I'll wait for the bootloader unlock to install this. In the mean time, I don't imagine an extra vote of appreciation will go unappreciated.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
This is not for fire hd 8 2020 it’s for the 2018 version tho
[Fire HD 8 and HD 10 Original Android Development] NellyWhads:
Noted
[Fire HD 8 and HD 10 Original Android Development] JerseyChewi:
Excellent work, Kai! We were still using the old Pie ROM where 5GHz wifi was broken. It's working great now. The whole ROM seems to hold up very well in general. LINE Chat and Snapchat refuse to start for some reason, but no great loss there.
[Fire HD 8 and HD 10 Original Android Development] SergeantFury:
Small and weird issue: even if muted, the speakers seem to turn on and play quiet static anyway if an open app is playing audio. This is most noticeable when playing a game with volume muted. Please let me know if logs would be relevant here.

Edit: Remembered another problem, although this one might be an issue with Android 11 in general. The default launcher and widget permissions for the home screen seem to unset themselves after every reboot.
[Fire HD 8 and HD 10 Original Android Development] entelecheia:
Somehow I lost recovery mode in flashing the ROM. My bootloader appears to have relocked itself, as well. Now, any attempt to boot or flash a new recovery image via fastboot returns the dreaded "the command you input is restricted on locked hw". I'm at a loss, any thoughts?

The device is running 18.1 fine (previously 14.1) and is rooted.
[Fire HD 8 and HD 10 Original Android Development] SergeantFury:
If you tried to flash through fastboot, you accidentally removed the exploit that unlocks the bootloader, if I recall correctly. You need to be flashing everything through the recovery on-device, since that version of TWRP has been modified to reapply the exploit after every flash (if you've flashed anything with it, you'll notice the blue messages prefixed [amonet].)

That said, you can re-open the tablet and reapply the exploit, and everything will be fine again. Just take a backup since running the exploit wipes everything.
[Fire HD 8 and HD 10 Original Android Development] Kovaelin:
I also had this issue. I noticed it when I had a video on YouTube paused. It was an issue on 15.1 too.
[Fire HD 8 and HD 10 Original Android Development] r2d2rogers:
I have flashed this on two tablets, but they both have the same bluetooth address. Is there a fix that works on 18.1 for defining unique bluetooth addresses?
[Fire HD 8 and HD 10 Original Android Development] glate:
Updated from the Lineage 14.1 by dirty flashing this ROM. Not recommended I'm sure but it worked well and the ROM seems to be running smoothly. Glad to have you back @Kaijones23 - really hoping this ROM breathes new life into these tablets.
[Fire HD 8 and HD 10 Original Android Development] thebluelegend:
Hey Kai, thanks for the ROM, it is surprisingly functional for how old the device is.

I got an issue to report, it seems that currently, the ROM does not connect to WPA3 Wifis at all, I attached part of the Logcat that gives details about the error.

11-16 13:04:03.697 960 960 I wpa_supplicant: wlan0: Trying to associate with SSID 'WIFINAME'
11-16 13:04:03.698 960 960 W wpa_supplicant: wlan0: WPA: Failed to select authenticated key management type
11-16 13:04:03.698 960 960 W wpa_supplicant: wlan0: WPA: Failed to set WPA key management and encryption suites

I am pretty sure it's just my WPA3 devices because it connects just fine to an extender I have that is WPA2. More details about the Wifi is that it uses a mixed WPA3-SAE/WPA2-PSK security and that both 2.4 and 5GHz do not connect.
[Fire HD 8 and HD 10 Original Android Development] d1nd141:
I confirm the issue with WPA3. Switched my Ubiquiti AP to WPA2 only and the connection works fine. Setting to WPA2/Wpa3 and the device does not connect at all.

The connection to WPA3 worked for 2 days after flashing.