yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco F1 Questions & Answers] eilegz:
ok after following this advice

to deal with that error it flashed without issue

View attachment 5712209

But sadly the same as before poco logo boot loop :(
[Xiaomi Poco F1 Questions & Answers] NOSS8:
You haven't flashed anything because you must have an error at the end of the flash since you don't lock the bootloader.

Again,try a version of miflash corresponding to the year of your phone or don't use Miflash, open the folder of the tgz file you extracted and use the Bat file"flash-all"
[Xiaomi Poco F1 Questions & Answers] eilegz:
tried the flash_all.bat but this appearView attachment 5712217
[Xiaomi Poco F1 Questions & Answers] NOSS8:
Which rom did you try to flash?
[Xiaomi Poco F1 Questions & Answers] eilegz:
downloaded this one https://xiaomifirmwareupdater.com/miui/beryllium/
[Xiaomi Poco F1 Questions & Answers] NOSS8:
These are firmware not full roms.

Download here a fastboot rom TGZ

https://xiaomifirmwareupdater.com/miui/beryllium/
[Xiaomi Poco F1 Questions & Answers] eilegz:
im mistaken the link but it was the full one had to extract the tgz then the tar and that get me the folder with the rom
[Xiaomi Poco F1 Questions & Answers] NOSS8:
try a version of miflash corresponding to the year of your phone.(older version).
[Xiaomi Poco F1 Questions & Answers] eilegz:
going to try this one https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115 since poco f1 released on august 2018
[Xiaomi Poco F1 Questions & Answers] eilegz:
FInished flashing using the old mi flash still same issue poco logo boot loop :(
[Xiaomi Poco F1 Questions & Answers] NOSS8:
Same https://xdaforums.com/t/recovery-dont-stick-can-fastboot.4493095/post-87439937

Post the Miflash log +or- 20/25ko
[Xiaomi Poco F1 Questions & Answers] eilegz:
fastboot and flash log right?
[Android TV General] fcata:
The Philips TV 55PUS7303/12 is stuck on the Philips logo. I updated the newest software with the help of Philips representative. After several attempts, the operation succeeded, but the TV turns on and freezes on the Philips logo. Out of 30 tries, once it started on the TV channel but after 1 minute it restarted again on the Philips logo.

The remote control or any other command does not work as long as it is stuck in the logo.

To restart, it only works disconnected from the power.

What can be done (what parts can be replaced) to make it work other than changing the motherboard?

Any suggestion is welcome. Thank you.
[Android TV General] fcata:
I followed the following steps after blocking the TV on the logo:

1. I contacted Philips TV support. With their help, I re-softened the TV with the latest software version. After this operation, the TV is also stuck on the Philips logo. I was advised to take the TV to a Philips representative for hardware repair.

2. I took the TV to the local Philips representative. They tested it, resoftened it and it remains stuck on the Philips logo. After 20-30 startup attempts, it starts normally and after 30 seconds it freezes and restarts on the Philips logo. When the Philips logo is blocked, no command from the remote or local control works anymore. They recommended replacing the main board of the TV, which costs half of a new TV. The new TV is a 3-year newer model and has a 2-year warranty.

3. I want to repair the motherboard (not buy a new one) which will cost me decently and not half of a new TV. In my opinion, a memory is defective and when the booting process starts, it freezes at a certain point. The resoftware was carried out successfully, but the hardware part of the TV has problems. Any suggestion is welcome..
[Android TV General] fcata:
When connecting the power, the TV always starts but stops on the Philips logo. During this time, no command on the TV or remote control works. It can be turned off by unplugging. Sometimes it starts correctly but after a maximum of 1 minute the image freezes and immediately restarts and stops on the Philips logo. It's not a software problem, but a hardware problem.
[Android TV General] Mystix82CZ:
Hi, i had same problem and tried everything. In the end, the TV had to be serviced to change motherboard. But it hasntbeen ok since anyway. After repair, often restarting.
[P3300, MDA Compact III ROM Development] dodadent:
When i try to go in Bootloader, i have whitescreen.

Thnks
[P3300, MDA Compact III ROM Development] e_cool:
Remove sim and memory card then try again.. :)
[P3300, MDA Compact III ROM Development] -chip-:
Thanks a lot, I had the same problem and it worked fine...
[OnePlus Nord Questions & Answers] vr15:
Dirac Audio Tuner is not upto the mark. I have uninstalled it and installed Dolby Atmos but it is not compatible with nord. I had trouble uninstalling dirac.

Earlier,

adb shell pm uninstall --user 0 com.oneplus.sound.dirac

command worked. Since Oppo acquired oneplus, Oppo made modifications in oxygen OS, few Packages names are changed.

Now,

adb shell pm uninstall --user 0 com.oplus.multimedia.dirac

command does the job for uninstalling dirac.

I think Dolby Atmos is not supported by Nord. Please tell best alternative equalisers that are supported by oneplus nord !!
[Samsung Galaxy S7 Edge Questions and Answers] Cooleffect:
Hello everyone,

My phone stopped working a year ago and when I sent it to repair they said I have to buy a new motherboard and they Trip Knox my phone. It stopped working a few days ago again and I tried to flash it with Odin but no matter what firmware version, cable or USB port I use, I always encounter writing permission error. The “BL” part will pass successfully but I encounter the error msg when it comes to “AP" section. I tried different firmwares and different Odin versions but when I use different firmwares it gives me a red error line on Download screen which indicates that firmware is old. There is no red line error when I use the latest firmware version which apparently means the firmware version is suitable. But the writing permission error always exists and leads to firmware installation failure. So I thought Odin is denying my write privileges because they've previously modified my recovery/rom when Trip Knoxed. and the phone is bricked. Is there any way I can flash my phone again?
[Samsung Galaxy S7 Edge Questions and Answers] Cooleffect:
So no one knows anything about these kinds of problems!? 🤷🏻‍♂️
[Samsung Galaxy S7 Edge Questions and Answers] rezha_levie:
maybe your problem is emmc
[Samsung Galaxy S7 Edge Questions and Answers] Delgoth:
Looks like Bootloader is Rev 8

Kernel is Rev 6

And System is Rev 7

Try and set them all to the revision of the BL or System?
[Redmi 9C Questions & Answers] DeMoN009:
Any one have fastboot driver for Redmi 9 (cattail). My device isnt detected in Fastboot when in mi unlocker in PC.
[Redmi 9C Questions & Answers] ze7zez:
1. latest adb/fastboot from google

2. change port to USB 2.0 and/or computer

3. change the USB cable
[General Questions and Answers] shweetlu:
So I bricked my UleFone Note 8 when trying to install a GSI ROM.

Have been trying to recover using SP Flash Tool.

Was getting the

Error 3154: BROM ERROR: S_DA_SDMMC_WRITE_FAILED (3154)​

every time I was trying to flash. So I decided to flash one file at a time.

All files went ok, except "super" (references to super-sign.img) It's a 2.1GB file.

So I can see, it's not a connection issue of any kind. Maybe the size of this file bringing an issue?

View attachment 5712015

BTW I'm using SP Flash Tool from my Linux Mint PC.

Would really appreciate some help on this pls.
[General Questions and Answers] shweetlu:
Update:

I just remembered that when I initially tried installing the GSI ROM, I experienced this error (I was using fastboot adb method):

target reported max download size of 16777216 bytes

wiping userdata...

Invalid logical-block-size 512: must be a power of 2 and at least 4096.

Segmentation fault (core dumped)

Maybe this is causing the Error 3154: BROM ERROR: S_DA_SDMMC_WRITE_FAILED (3154) and thus the super file is not be flashed successfully?
[General Questions and Answers] susabakusa impostorusa:
u need to use miracle box thundernif u want to flash it.

Download it here: www.androidfilehost.com/?fid=11410963190603915389
[Google Pixel 6] Frankenscript:
Pretty much as the title says. I'm stock and unrooted, but the idea of an update that blows a physical fuse and can't be undone gives me the shakes. So I held off since it came out. We're about a month into deployment of the update, so I'm now considering applying it. Has anything in terms of major bugs/performance problems come out that should factor into my decision? I've read various threads here and not seen much major stuff.

Thoughts and input? Thanks in advance.
[Google Pixel 6] MattPLfc:
One reason for not going to Android 13 would be that It can mess up the wireless charging function . Mine has not worked properly since I updtaed , even after the patch ( which was supposed to fix it ) it still doesnt work .
[Google Pixel 6] Frankenscript:
Thanks. I've never used wireless charging but I appreciate this caveat to the A13 update.
[Google Pixel 6] MattPLfc:
Other than that all seems good , bit annoying for me as I use wireless charging a lot , have one in my car and this was a major factor in me buying a Pixel 6 . Had high hopes when they rolled out a patch pretty quick but nothing seemd to of changed .
[Google Pixel 6] Frankenscript:
Sad to hear it broke.

I'm afraid to accept major updates after the very final update ever for my OnePlus 6T broke several key functionalities I relied on. That led me to the Pixel 6, which I don't love but it is working "fine" and I hope A13 won't nuke me. I will likely update this weekend unless I hear something widespread and impactful to how I use the phone.
[Google Pixel 6] miss:
accessibility service not possible in non-store apps
[Google Pixel 6] PHANX0M:
WHAT... That's horrible... ACR won't work ) :
[Google Pixel 6] Lughnasadh:
Just go to app info, click on 3 dot menu to bypass restriction.
[Google Pixel 6] Jaitsu:
I updated and I'm pretty happy. IIRC there's now a "developer" Android 12 build that works on the Android 13 bootloader if it ends up not being for you for any reason. I haven't seen any significant issues, though now I see people mentioning wireless charging I did notice it kept popping up the little "100%" screen every 5 or 6 minutes like I'd just put it on the charger when I was using the one in my car, after it hit full, but not the one in my room that provides a higher wattage. Either way, not a big issue to me.

Just be sure to read the other threads about updating to 13 and sideload the OTA after you update if you want to be certain you won't accidentally brick booting the un-updated partition after updating. It gave me a hassle sideloading from both of my PCs, but if you use USB 2.0 it'll go through, just... reeeeeally... sloooowly - so you could let it go overnight.
[Google Pixel 6] Frankenscript:
So, even unrooted and stock I have to fuss with the side load update thing?
[Google Pixel 6] Jaitsu:
You don't have to, it's just eliminating an unlikely risk. It'll work fine after just updating. Even if the update somehow failed you'd be safe as it would just roll back; the risk only lies in if you update, successfully boot, and then something causes Android to fail to boot, which should never happen if you're not rooted and tinkering with things.

Basically:

* Your phone has two "system" slots.

* Either taking an OTA from an automatic system update, or manually sideloading it, updates the slot you're not on, then switches to it.

* When you update to 13 and it successfully boots, a flag is set that permanently prevents booting with an older bootloader. (This is a one-time thing and shouldn't happen again with future updates.)

* At this point, if something caused Android to fail to boot, it might try to boot into the un-updated system slot. Because that flag is set and it still has the old bootloader, it wouldn't boot and would be bricked.

* Sideloading the OTA again (or even getting another automatic update, but that won't happen immediately) ensures this won't happen by updating the other slot.

Personally I'd just do it because I'm paranoid (and moreso because I personally do root and tinker with things I shouldn't all the time :p).
[Google Pixel 6] miss:
with any apk file, any application?

I use many that are not from any official store, such as motomedialink, which needs to have accessibility permission to work
[Google Pixel 6] Lughnasadh:
As long as the accessibility permission has been restricted for that app because of the new policy (applies to Notification Access permission as well), it should work.
[Google Pixel 6] Frankenscript:
So far the update to A13 seems to have gone smoothly. I honestly haven't noticed anything different yet.
[Google Pixel 6] Frankenscript:
For what it's worth, one benefit I've noticed so far is that certain applications don't get shut down so aggressively as under A12. Despite all the tweaks I made previously, Angry Birds 2 would get shut down pretty much as soon as I did anything else on the phone, and Sound Profile would shut down randomly. Both of these seem fixed under A13.

Haven't noticed a downside yet in terms of how I use the phone.
[Google Pixel 6] Pakabidu:
I've been on A13 for two weeks now and everything seems to run smoothly, definitely dropped phone temperatures. I don't use wireless charging so can't tell about that. I'm on 13.0.0 (TP1A.220624.021.A1, Aug 2022) rooted. Tried loading 13.0.0 (TP1A.220905.004.A2, Sep 2022) but it won't boot, I'm getting "your device is corrupt it can't be trusted and may not work properly" error, had to revert back to previous one. Shame as I'm struggling with biometrics and this new update was suppose to fix the issue. Might try to flash_all with -w option this weekend to see if it makes any difference, can't be asked to be setting up my phone from scratch after three days of festival 😵‍💫👽
[Tilt, TyTN II, MDA Vario III General] xtrahuge:
After changing to and exchange server, memory on my tilt has become an issue. I need help to make the tilt store email data on the SD card. I have a tilt with WM6.1.

Thanks,

HUGE
[Tilt, TyTN II, MDA Vario III General] smjoshi:
http://xdaforums.com/showthread.php?t=372296

Take a look at this. Hope fully this will address your problem. When I tried it, it did not seem to work for me. and since this isn't such a burning issue for me, I haven't tried to debug it

Satish
[Tilt, TyTN II, MDA Vario III General] xtrahuge:
Thanks, that seems to have worked perfectly.

HUGE
[Sony Xperia XZ3 Questions & Answers] Akhir98:
Hi, My XZ3 bottom speaker has suddenly stopped working. The top speaker (earpiece) is working fine while watching videos or making a phone call. I mostly use wireless handsfree so it is not bothering me that much.

But, when I turn on the speaker mode during phone call or while having a video call on WhatsApp, the top speaker has no sound. Thus, I can't hear other person.

The issue I think is that the Phone app and WhatsApp uses only bottom speaker for video calls.

So, is there any method to enable top speaker or stereo mode in Whatsapp video call and Phone call?

FYI, temproot is enabled on my device SOV39.
[Xiaomi Poco F4 (Munch) / Redmi K40S] akashk07:
--Edit: Thread moved to:

https://xdaforums.com/t/rom-android13-evolutionx-official-munch.4504789/
[Xiaomi Poco F4 (Munch) / Redmi K40S] akashk07:
Reserved
[Xiaomi Poco F4 (Munch) / Redmi K40S] DidierMoulin:
@akash.galaxy07 thanks for building this rom! I wanted to try it, but download folder is empty.

And: is this a parallel build to the other evoultion x thread or are you continuing, ie taking over?
[Xiaomi Poco F4 (Munch) / Redmi K40S] akashk07:
Updated the link

Please check again.

No, I'm taking it over, applied for official too.
[Xiaomi Poco F4 (Munch) / Redmi K40S] DidierMoulin:
That's good news.
[Xiaomi Poco F4 (Munch) / Redmi K40S] jeet.shubha711:
Can anyone help me to install EvoX ony poco f4 5g. I was using EvoX on my old phone. So I know the basics. But I want to know that which recovery is recommended for this device and what should be kept in mind ?
[Xiaomi Poco F4 (Munch) / Redmi K40S] psklf:
Flash whichever recovery you desire.

TWRP or Orange
[Xiaomi Poco F4 (Munch) / Redmi K40S] Dimon909:
Hi. Auto brightness does not work. I installed the stock roms through the bootloader. Then install TWRP. Through TWRP installed the Evolution, reset the date, reboot phone. Roms work, auto brightness dont working.
[Xiaomi Poco F4 (Munch) / Redmi K40S] DidierMoulin:
Did you format DATA (not "reset date")?. Autobrightness works for me. Did you use latest version?
[Xiaomi Poco F4 (Munch) / Redmi K40S] Dimon909:
no. I have previous version. Not from 29.09.22. Will try install new. And yes, a made full reset data.
[Xiaomi Poco F4 (Munch) / Redmi K40S] DidierMoulin:
But did you FORMAT or WIPE data, I had to format data.
[Xiaomi Poco F4 (Munch) / Redmi K40S] Dimon909:
Format DATA - yes. Without format data phone didn't turn on.

And at last version of rom the brightness not working . curiously. At other custom roms work, but this - not.
[Xiaomi Poco F4 (Munch) / Redmi K40S] DidierMoulin:
Sorry, you're actually right. I remembered it working, but obviously it was another rom, just checked. Auto brightness doesn't work here.
[Xiaomi Poco F4 (Munch) / Redmi K40S] Dimon909:
Good. Let's wait until fix it problem. I like Evolution roms.
[Xiaomi Poco F4 (Munch) / Redmi K40S] Abel05:
+1 It does not work
[Xiaomi Poco F4 (Munch) / Redmi K40S] idiot_user:
is smart charging working? I have smart charging enabled on default threshold but my devices charges to 100%.
[Xiaomi Poco F4 (Munch) / Redmi K40S] DidierMoulin:
Same here
[General Questions and Answers] sensei punk:
I had purchased a refurbished Motorola V3xx a few years ago just for carrying with me for work for calls and because of crime where I used to work. Anyways, its a branded AT&T firmware.

I have been having issues with the phone of late, mainly it constantly says no signal and goes on an infinite power off and on loop unless I plug it into the charger where it then stays on. Sometimes, even while it has signal, it will just randomly reboot.

After some hunting online, its near impossible to find any firmwares anywhere for this phone and the ones I have been able to find, either don't work (it just throws out an error in the flash&backup software) or the sites will list firmwares but no download links...or in the case of two sites, you had to pay to download the firmwares.

I was hoping maybe someone here maybe from back in the day might still have any firmwares or monsterpacks for the V3xx hidden away somewhere...

Bootloader is 03.08

Software version is R26111MLD-AS_U_96.B0.0FR

View attachment 5712037
[General Questions and Answers] sd_shadow:
Try here

https://firmware.center/firmware/Motorola/! Motorola Old Phone/

or

[Index] Motorola Stock Firmware

Motorola Firmware [INDEX] Helpful Information Welcome, this thread has been created to encompass everything you may need to find Motorola Firmware. Please only post in this thread with feedback on how to improve this document. Do not post "Thank...

xdaforums.com
[General Questions and Answers] sensei punk:
Thank you

I found a few on the first link, unfortunately none of them worked, they were all for bootloader 03.02 and mine is 03.08
[OnePlus 7 Pro Questions & Answers] vladvlad12:
Hello everyone!

I am looking for ROMS for 7pro. Something like MIUI, but unfortunately there has not been any update to MIUI for 7 pro.

I wait for your recommendations about some roms to test that look like MIUI or different than classics androids/pixels/etc...

Thanks all!
[OnePlus 7 Pro Questions & Answers] Amosika:
The project is dead because the developer was the same one who developed kango os and he lost his servers. Donations was coming in. I guess if we want to see the work continue, there has to be donations
[MTCD  Android Head Units Q&A] TobiBe92:
Hey, i bought this Navi more than 1 year ago and i noticed that i cant update any apps on the google playstore anymore. I cant even upgrade my Google Playstore. I click on install and it just load forever and nothing happens. My Infos:

Model:

PX6 (1280x720)

BuildNr.:

rk3399-userdebug 10 QQ2A.200305.004.A1 eng.hct2.20210428.172823 test-keys

Kernel Ver.:

4.19.111+

#2968

MCU:

MTCE_HT_V3.71_1 / Dec.19 2020

Canbus version

V3.88.024BYPS (s99_r1040)

CPU

Dual-Core Cortex A72 @ 1.8 G

Quad-core Cortex A53 @ 1.5G

latest SecurityupdatE:

5 May 2020

Google Play Systemupdate

1. Aug. 2021

Its an Android 10 Vanku Navi.

I dont havy any Custom Firmware and i dont want one. I cant find any updates for the basic MTCE_HT MCU.

Any help please?

Thanks.
[MTCD  Android Head Units Q&A] TobiBe92:
No one knows something? :/
[MTCD  Android Head Units Q&A] marchnz:
Read its all here
[MTCD  Android Head Units Q&A] mrbele:
I have the same question, if you got the answer, please let me know.
[MTCD  Android Head Units Q&A] Kullerkeks77:
Good day everybody

I bought a Pumpkin Radio Android 9.

So far I am very satisfied.

My question is, is there another system update or MCU update for my radio

Current MCU is: MTCE_HT_V3. 30_1

I am attaching 2 more pictures
[Touch HD General] askadc:
Hello,

I have observed a number of posts in various forums regarding guidance about buying HD from India. Here are my experiences. Hope this will resolve a few queries:

HTC Touch HD: Brought from: www.clove.uk.

Price: GBP 445 + GBP 37 DHL delivery.

Delivery in : 2 days to Kolkata.

Customs Charges: (Assessed in New Delhi): Rs. 2196.99.

Any furthur queries are welcome here!
[Samsung Galaxy J5 (2015) ROMs, Kernels, Recoveries] daviiid99:
What's working:

​

What's not working:

​

( If you wanna report a bug, please, catch a logcat first with the error, then describe how to reproduce it and your phone model & rom version.

e.g. "adb logcat -d -b main -b system -b events -v time > logcat.txt"

or use an Android app)

How to upgrade:

​

Galaxy J5 Downloader is the recommended tool for J5 users to upgrade my builds

Download

Installation notes:

​

A reboot is required for SIM card to work since i've removed SIM card activation from setup!

Confirmed working GApps

Download

Update history

​

2022-09-28:

2022-09-24:

2022-09-22:

2022-09-19:

2022-09-18:

2022-09-15:

XDADevDB Information

LineageOS, ROM for the Galaxy J5 (2015)(2016)

Contributors : @Ivan_Meler @html6405

ROM OS Version: 13.x

Security Patch Level: 2022-09-05

AOSP Build ID: TP1A.220905.004.02

SELinux state: Enforcing

ROM Firmware Required: Marshmallow (J5 2015) | Nougat (J5 2016)

ROM Kernel: Linux 3.10.108

Kernel Source: Kernel

Status: Stable

Created 2022-09-15

Last Updated 2022-09-28
[Samsung Galaxy J5 (2015) ROMs, Kernels, Recoveries] alisadty:
Hi David, thank you very much

My own J500H

I am downloading now for

I will install it tomorrow
[Samsung Galaxy J5 (2015) ROMs, Kernels, Recoveries] Tajil:
Thanks a lot for this Tiramisu !!

auto Reserved!
[Samsung Galaxy J5 (2015) ROMs, Kernels, Recoveries] Fever070720:
can it split screen?
[Samsung Galaxy J5 (2015) ROMs, Kernels, Recoveries] daviiid99:
No, it's an agressive RAM feature like PIP

android Go disable it by default
[Samsung Galaxy J5 (2015) ROMs, Kernels, Recoveries] Noxii:
David, you actually did that. You are a god of this phone
[Samsung Galaxy J5 (2015) ROMs, Kernels, Recoveries] daviiid99:
It's an alpha but it will be stable in the upcoming months :)
[Samsung Galaxy J5 (2015) ROMs, Kernels, Recoveries] Noxii:
i didnt found any bugs rn so, cool
[Samsung Galaxy J5 (2015) ROMs, Kernels, Recoveries] Jagdishjangu:
Very nice
[Samsung Galaxy J5 (2015) ROMs, Kernels, Recoveries] Noxii:
yeah
[Samsung Galaxy J5 (2015) ROMs, Kernels, Recoveries] milanpeterjani83:
Hi! I have a question. Can RIL be fixed?
[Samsung Galaxy J5 (2015) ROMs, Kernels, Recoveries] Difficul:
Sad I don't use j5 anymore, can you build a gsi bvs?
[Samsung Galaxy J5 (2015) ROMs, Kernels, Recoveries] daviiid99:
No, I don't build gsis sorry
[Samsung Galaxy J5 (2015) ROMs, Kernels, Recoveries] daviiid99:
No, it's broken forever, sorry