yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ErgG:
Thank you for your prompt reply.

After the app launched I went into Settings/Apps but not able to see "Recent Apps".....I must be doing something wrong.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Greenspoof:
Recent app is when you click on the square next to homescreen button in the navigation bar. It shows you all your active app. Then you make a prolonged tap on the opened app and click on the setting icon
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ErgG:
Absolutely great Greenspoof....Thank you so much.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] McFlypants:
My Poco F3 is called "M2012K11AC" everywhere, which is - of course - the model name. But it is a bit annoying to have this name in all google apps and when i connect it to my PC. I'd prefer something like "Poco F3".

Can i rename it?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Robert314:
Unlock the bootloader. Then root it with magisk (using a modified boot.img) and then modify the build.prop file (https://www.droidviews.com/edit-build-prop-file-on-android/)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] d3z1k:
I have looked for it and the name "M2012K11AC" does not appear anywhere. Any ideas team? I used JRummy BuildProp Editor.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] McFlypants:
I can't find anything in build.prop too!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Nemix77:
I'd also like to know, let me know if you've found a way to do it.

It's not a super big deal, but if I can change it without breaking the rom I will.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] theoalex50:
Me as well. Hoping someone can help.
[Samsung Galaxy A40 ROMs, Kernels, Recoveries, & Ot] kevios12:
View attachment 5348503

/* Your warranty is now void.
*
* 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 this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

Here is a small collection of undefined ROMs that most likely will not receive updates from me. These ROMS were just for testing but can be used for everyday use. Some have been modifications and some are just classic. They contain the typical bugs that belong to the A40. Still run very well. So have a little joy in it, those who like it easy. I will list the available ROMS below. No screenshots of every single ROM available.

What is Working?

RIL

WiFi

Camera

GPS

BT

Sensors

Adaptive Brightness

Fastcharging

NFC

Microphone

Flashlight

Hotspot

etc...

What is not Working?

- voLTE

- voWiFi

- BTCalls

Undefined ROMS

FusionOS

FlokoROM

HalogenOS(XOS)

Project-Lighthouse

Changelog 2021-06-26

* Initial Build / Release

GAPPS

View attachment 5348489BitGapps

View attachment 5348491NikGapps

View attachment 5348493 FlameGAPPS

Source

FusionOS [GitHub]

FlokoROM [GitHub]

HalogenOS(XOS) [git.halogenos]

Project-Lighthouse [GitHub]

A40: Kernelsource [GitHub]

View attachment 5348495

Kevios12Releases

Kevios12A40Discussion

Samsung Galaxy A40 Group

If you like all of my shared projects and want to make a small donation, click the link below.

View attachment 5348467

Thanks to SamarV-121 for Device BringUP!

Thanks to Undefined ROMS Team!

Thanks to GAPPS for the Logos!

REPORTING BUGS!

As soon as the problem occurs, take a log or more

READ THIS

Undefined ROMS for Samsung Galaxy A40

Device: A40

Maintainer: @kevios12

Contributors: Kevios12

Build Type: Unofficial

ROM Kernel: Linux 4.xx.xx

ROM Firmware Required: ALT+F4 / OneUI 2.0

Based On: AOSP // LineageOS

Android OS version: 11

Security patch level: June 2021 // May 2021

Version Information

Status: Stable

SELinux Status: Enforcing // Permissive

Release Date: 2021-06-26​
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DJ_Enigma:
Hi all,

I sent my phone back to T-Mobile for a warranty repair because a couple of the keys stopped responding to key presses.

Got the phone back today repaired, they have replaced the keyboard. BUT they have also upgraded the firmware on the phone. Now it is WM6.1 and I am unable to restore my (a lot) applications etc from the 2gb backup file on my SD card.

It asks me for an upgrade file which I don't have. It performs the restore anyways but then the phone won't boot.

On performing a hard reset it comes back with WM6.1

I can't even cancel the damn T-Mobile customisations like I could in WM6 (by restarting the device before they install) now it just wipes the handheld again after boot and installs the T-Mobile crap again every time.

Please can someone help me restore my backup file? Where can I Get an upgrade file?

:(

I found a guide here that I would have followed had I know they would upgrade my phone without my consent:

http://spritesoftware.crmdesk.com/answer.aspx?id=329

Is anyone here still on WM6 (not 6.1) able to create an upgrade file for me and host it somewhere?

I know it's a massive ask but I would be forever greatful if someone could help me out with this.

Many Thanks,

Alex.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] SH4YD33:
If you dont want the 6.1 i would check the wiki/search for the 6.0 rom that you had before you sent it in. The older rom should be avaliable somewhere.. You just have to look for it.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] slovoflud:
I say you send it back to T-Mobile and ask for a G1 instead :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DJ_Enigma:
I've spoken to T-Mobile to see if they could change it back and they said there is nothing they can do.

Is there some way to save my current rom to my SD card so that I can go back to 6.0, create an upgrade file for sprite, come back to 6.1 and restore my backup using the upgrade file?

I don't know where I can find the original T-Mobile Rom though :( I've looked on the web and the T-Mobile site.

Sorry I'll admit that I'm a noob at this.

DJ
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] martythebrit:
Is the backup just to save you re-installing programs, or is there data in the backup that isn't backed up somewhere else?

The only thing I would really "lose" on my phone are the contacts which come right back as soon as I set the phone up to sync with exchange again. If I wasn't using exchange I would have all my contacts backed up in Outlook on my PC.

Maybe you just need to re-install your programs again. WM 6.1 does have some nice enhancements over WM 6.0.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Flying Kiwi:
Nothing they can do vs they can't be bothered

Complain to them about much longer GPS lock times (assuming you have the option of installing Tomtom or similar on your phone). I had this problem with the official HTC WM 6.1 upgrade (see this *Hopeless* GPS after 6.1 update thread for more info) and the HTC Service centre reverted the ROM back to 6.0 for free under warranty so if T-Mobile say they cant get the HTC Technical Centre to do this for you, they're not trying hard enough - time to escallate it to the manager! There's no physical reason why they cant revert the ROM and they should have warned you that they would flash the ROM.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DJ_Enigma:
I will lose a lot of data that is not backed up anywhere else. One of the main things is my TomTom favourites, which is full of locations I would have to drive to to save again, and can't drive to without the favourites lol. Other than that it's a lot of apps and customisations like numerous SPB apps that have been tailored to my requirements over the last year.

ffs I hope that's not going to be the case, I use TomTom 6 on my phone ALL the time and I'll be REALLY annoyed if it's not going to perform as well at that. It's the main reason I went for this phone.

I think I will ask for the manager. The pleb I spoke to did even go and ask someone if there was anything they could do.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Flying Kiwi:
GPS was a big drawcard for me also and the difference between HTCs official WM 6.1 vs WM 6.0 ROMs is like night and day (6.1 being night). Give it a test under your new OS just to see how it works with the T-Mobile ROM (I see there's a new 1.70xxxx series T-Mobile Radio - maybe yours has it now) but don't get your hopes up :(

Feel free to mention you know someone who had the ROM officially reverted for free under warranty. Remember, this is something that is possible to get done, I have personal experience of it.

As far as how to backup in the future, I backup all my Music, Videos and Tomtom Navigator 6.032 Maps and POIs etc on my microSDHC card using my Sandisk Cardreader and Windows XPs own backup utility. It's quick, free and works a treat! There's no need to use any special mobile phone backup software just for this sort of thing (although phone settings/configuration etc will require manual re-entering if you don't back them up - but then I'm unsure if it's possible to retain those across different OSs).
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DJ_Enigma:
I tried to use my tomtom yesterday and it took ages to lock on despite having the quick gps downloaded.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Flying Kiwi:
Well then assuming you were out in the open and there's no reason why it shouldn't have got a quick lock (other than the 'up'grade), you know what to do!

For other T-Mobile customers and people considering using the radio in a non- T-Mobile Kaiser (not me!), it may be helpful if you post the ROM and Radio Versions you currently have.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DJ_Enigma:
ROM Version: 3.31.110.1 WWE

Radio Version: 1.70.18.02

Protocol Version: 25.83.40.02H

The sat nave seems better since that first lock, but I've only used it twice.

Is there a way to backup this ROM before I change back to do my upgrade file?

Cheers,

DJ
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Flying Kiwi:
Remember your goal

Repeat after me, this ROM is bad, this ROM needs to go, Old ROM is good, Old ROM is whats needed (for the meantime)!

Once you've got your SD Card contents back, then you can think about where to go from there and T-Mobile I'm sure will be only to pleased to supply you with the upgrade again or do it themselves.
[LG V40 Questions & Answers] Cookies_crumbly:
So i have Korean Version V40 (SKT_KR) on android 10 Q, tried to unlock my bootloader.

First thing i tried was flashing abl_a with V35abl using QFIL, but it got soft-bricked and couldn't get into fastboot mode.

Then i installed stock ROM (android 10Q) using LGUP, after that i redid everything, but i flashed abl_b and it got into fastboot mode on V35 bootloader.

So i thought everything was fine and installed ablpiestock.iso thinking it would work. as you know it was for Android pie and i was on Android 10.

Now im stuck on Fastboot, no download mode, not booting into system, and on the bootloader it only shows power off and restart.

Im just very confused were do i go from here.

Model number LM-v4059N (jydypn)

SKT_KR (Korean version)

Android 10

Device State - Unlocked

Also i know my IMEI if that helps
[LG V40 Questions & Answers] AsItLies:
So no, it won't work with ablpiestock on Q. It's unfortunate but the directions, they were written when the person was on Pie, so they wrote it kind of like everyone else would be on Pie.

But what you should have done, before flashing any partition, is to save off the original of what's in that partition. So, you would have abl Q for whatever Q firmware you used lgup to install.

The v35 eng abl will not boot your device. That's because it's Oreo based, it won't boot anything but Oreo roms. But it can be used to unlock the bootloader, then, you flash YOUR original abl back with it, then reboot, and it should be all set.

If you didn't save your newly flashed (lgup) abl partition, then what did u flash? Kr Open 30f ? If so, I have the abl for that. But mention what u flashed and maybe someone will have it.

cheers
[LG V40 Questions & Answers] Cookies_crumbly:
thank you for your quick reply, yes its V409N30f_00_LGU_KR_OP_0126.

I managed to install v35 eng abl back.

Also, can you sideload download mode from Bootloader?
[LG V40 Questions & Answers] AsItLies:
ahhh good, then follow this link and you'll find the boot+twrp image you need.

So with fastboot, flash this to your current slot boot partition. Then flash this abl to the abl partition. Then, boot to recovery, hold appropriate keys to do that.

follow steps to get recovery / now twrp. If it asks for pw, just cancel. Format data, then reboot recovery. Then flash magisk and dm_verity and you should be all set.

this is abl attached.
[LG V40 Questions & Answers] Cookies_crumbly:
Okay so im trying to understand

First i fastboot flash abl_b kor_30f (im on b part)

Then i fastboot boot twrp

Them Resart into TWRP using power down + volume down

Then go from here?

Because i get error like this should i also flash to abl_b only?

I renamed abl_b to new, and twrp to boot for easier usage
[LG V40 Questions & Answers] AsItLies:
So, no. First and foremost, don't flash anything to anywhere if you don't know what yer doing. That can result in trying to flash too big of an image to a partition that is too small, and you'll the overwrite the images near it, which could (soft) brick the device.

any abl image is only suppose to be flashed to an abl partition. Any Boot image is only suppose to be flashed to a boot partition, etc.

I'd suggest read the directions in the guide again, do ea step one at a time, if yer unsure what to do at any step, post in here, and one of us can clear it up.

cheers
[LG V40 Questions & Answers] Cookies_crumbly:
I first tried loading 30f abl and got this (My active abl was in b):

C:\Users\User\Desktop\adb>fastboot flash abl_b kor_30f_abl_a.img

target reported max download size of 805306368 bytes

sending 'abl_b' (1024 KB)...

OKAY [ 0.024s]

writing 'abl_b'...

FAILED (remote: unknown command)

finished. total time: 0.027s

then i tried with twrp and got the same error:

C:\Users\User\Desktop\adb>fastboot flash abl_b boot-twrp-30f_a.img

target reported max download size of 805306368 bytes

sending 'abl_b' (65536 KB)...

OKAY [ 1.384s]

writing 'abl_b'...

FAILED (remote: unknown command)

finished. total time: 1.386s

im new to this, i really need help
[LG V40 Questions & Answers] AsItLies:
So, I already told you... DO NOT FLASH WRONG PARTITION IMAGES TO WRONG PARTITIONS!!!

You just indicated trying to do exactly what I told you not to do!! You tried to flash the boot+twrp image (that's a BOOT image) to the abl partition!! THE ONLY THING you flash to an abl partition is an ABL IMAGE! NOT A BOOT IMAGE!!

I understand yer new to this, but don't make the mistake of hacking around doing anything u think **might** work. That's the wrong approach, because it could easily make things much worse than they are.

So again, what are you trying to do? One STEP AT A TIME, tell me the state of the device and what your goal is, I'll try to help you get there, but you have to have patience, don't try to run before u can walk.

cheers
[LG V40 Questions & Answers] Cookies_crumbly:
Okay my goal is installing TWRP + CUSTOM ROM

Only thing working now is v35 bootloader, and download mode shows "no command" dialog.

I don't know what i done to the system at this point. Maybe if its better if i install dmz and start from there? im really in deep water now.

please help me, step by step

greatly appreciated
[LG V40 Questions & Answers] AsItLies:
okay. So from what you're saying, your current slot (be it a or b, I don't think we know), has the v35 eng abl flashed to the abl partition, that's why all you get when you try to boot is FastBoot.

To install a kdz (not dmz) and start over, you need to have download mode working, as I think you know. To get download mode to work there are some partitions that have to have the same variant and version, they can't be 'mismatched' for it to work.

And since you don't seem to have backups of the files your flashed over, the best I can recommend is to follow this link. In that link are the files needed to get lgup to work. They should ONLY be flashed to the exact partition they are for! Boot to boot, laf to laf, etc etc. (the only one in there not to use is the one with twrp in the name).

They would have to be flashed with qfil, which I think u have set up and used already. So once you've flashed them in qfil, exit out of qfil by holding pwr button and vol dn button. Then, when u hear windows chime (meaning exit), release pwr and vol dn buttons but then press vol up button. That should take u to lgup (download mode) and you can flash a kdz and start over.

Do that, and we'll go from there. cheers
[LG V40 Questions & Answers] Cookies_crumbly:
They files you shared is for 30c, mine is 30f (Korean version).

Is it okay to use it?

Also is there a certain order do i have to go through? like boot first etc?

cheers for the helps
[LG V40 Questions & Answers] AsItLies:
yes, I know they are not what you currently have. But it will work to get to lgup, not to boot the device, only to get to lgup.

there's no order, I would have told you an order if there was one.

just re-read what I said. This allows you to go directly from qfil to lgup, use the key combo I mentioned.

It's at that point you can re-flash kor 30f, and start fresh.
[LG V40 Questions & Answers] Cookies_crumbly:
Im still getting the same error.

C:\adb>fastboot flash abl abl_30c.img

target reported max download size of 805306368 bytes

sending 'abl' (1024 KB)...

OKAY [ 0.031s]

writing 'abl'...

FAILED (remote: unknown command)

finished. total time: 0.031s
[LG V40 Questions & Answers] AsItLies:
you're suppose to be using qfil, not fastboot.
[LG V40 Questions & Answers] Cookies_crumbly:
But how would i enter QFIL if i cannot enter 9008 mode?
[LG V40 Questions & Answers] AsItLies:
why are u unable to enter 9008 mode?
[LG V40 Questions & Answers] Cookies_crumbly:
I did now, thank you

I was just having problem clicking volume up down button so i thought it was only possible if the phone is booted.

Successfully installed the recovery files and booted into download mode.

Downloading original kdz and hopefully do all this all over again, this time backing up the files :)

Thank you for all your troubles, you single handedly helped me save my phone.
[LG V40 Questions & Answers] Cookies_crumbly:
Another surprise, when i tried to install kdz on the phone, it says:

Error: 0x6004, CrossDL

judypn_lao_eea>@judypn_la

Both refurbish and upgrade options show same result.

This is the same version that i successfully flashed before

edit: shoot, i downloaded the wrong version
[LG V40 Questions & Answers] AsItLies:
Look in the thread on unlocking in the guides forum, you'll find the information in there to deal with that problem. cheers
[LG V40 Questions & Answers] Cookies_crumbly:
Great news, i flashed kdz using patched LGUP with custom cmd line. Now its working as intended, it shows OEM already unlocked in dev options. i patched abl_a to get magisk working ( i think my active slot is A now).

So i got root and magisk, but my goal is still have TWRP and install custom ROM.

So from what i gathered, i install v35 on abl_a, boot into fastboot, flash twrp to boot and flash orignal abl back and restard bootloader.

Or can i just flash twrp into boot_a in QFIL?

cheers
[LG V40 Questions & Answers] AsItLies:
So look at this thread, as it talks specifically about how to handle this. Admittedly it's a long thread and the original post is outdated. So start at the end of the comments and work back. It will answer all your questions.
[Xposed General] AllanonMage:
I'm not clear on the differences between them, and it seems that there are even more alternatives.

Is one better than another?

I just got an Android 10 phone, was previously on 7 for a short time, but was otherwise still on 5 and 6.
[Xposed General] Lord Sithek:
The main difference is that in LSPosed you have to whitelist apps to be hooked instead of blacklist. The second one is that EdXposed seems to break SafetyNet in latest version. And it seems that it's not that actively developed as LSPosed
[Xposed General] Arakawa.:
They both have whitelist and on LSPosed it set in default. But only EdXposed have blacklist. I saw some comment like "have too much modules and too much apps to hook, how painful to check everything by manually".

Yes, Edxposed still break SafetyNet.

Yes, now Edxposed is not that actively update than LSPosed.

https://xdaforums.com/t/something-about-lsposed.4236335/

I personally tried both. Not that much difference. Yeah, because basically LSPosed just forked Edxposed and did a little improvement.

In the end I choose Edxposed rather than LSPosed. Because I can't trust one dev who made a prank about "rm -rf" and the rest dev have no objection to this and even help him to hide it. And those personal attack with filthy language of course.
[Xposed General] cracky.ice:
The developer you mentioned has left the development group long ago
[Xposed General] Michael Westen:
All I wanna know is which one passes safetytest. Installed edxposed for the first time in 2 years only to discover that safetytest is completely fubar'd. And all the tutorials I've found are old and seemingly obsolete.
[Xposed General] VD171:
This moment, LSPosed is alot better than EdXposed.

Simple that.

I say many thanks to EdXposed, but LSPosed is the future.

We Love EdXposed ♥️

We Love LSPosed ♥️

We Love Better Future ♥️
[Xposed General] VD171:
More than 100 commits less than 20 days ♥️

Commits · LSPosed/LSPosed

LSPosed Framework. Contribute to LSPosed/LSPosed development by creating an account on GitHub.

github.com
[Xposed General] Md Husain:
Which prank? Will you share the source of the prank? Plz let us know.

Edit: Sorry, haven't noticed the quoted post, got it.
[Xposed General] mlgmxyysd:
The man left temporarily, but what he had done was still there. And the rest of the developers don't think rm -rf is wrong. The whole development team had problems, they even excused the malicious code. Communities should not forgive this.
[Xposed General] mlgmxyysd:
LSPosed is not a good choice for Xposed: from the software itself, module scopes and Xposed Hide (White) were designed as advanced features for advanced users only, and forcing them to be enabled is abusive and will increase the learning cost for users, increase the cost for module developers, break the functionality of global modules, and make modules much less compatible. On the developer level, the LSPosed development team has been suppressing and abusing other Xposed implementations and their developers since the project's inception, attacking third-party ROM developers with web violence, and committing community divisive acts like this; one of the development team members submitted rm -rf /* malicious code to EdXposed, which was responsible for emptying CI user data. The culprit has no credibility.
[Xposed General] VD171:
We will never forgive.

But it is past.

We just need MORE attention before to accept any commit.

We will have bad people everywhere.

Nothing more.
[Xposed General] VD171:
YES.

Xposed is for ADVANCED USERS only !!!!

Xposed is not a play for kids.

I agree with you about the difficulty for developers, but well, the future is here.

And we will not accept to remain in the past.

Long Life to LSPosed ♥️

But, we love EdXposed too ♥️
[Xposed General] mlgmxyysd:
Put away your false future, Xposed (even ROMs) will die because of LSPosed Developers. You don't know what disgusting things LSPosed Developers are doing behind the scenes.
[Xposed General] VD171:
The point is we need xposed for Android 9, Android 10, Android 11, Android 12, Android 13, Android 14...

We currently have no choices.

Or do you have any?
[Xposed General] mlgmxyysd:
There will be, just need to wait.
[Xposed General] VD171:
I can't wait.

I have a solution, so I will use it.
[Xposed General] VD171:
But, I'm totally open for new XPOSED alternatives.

Let's keep watching :cool: