yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] Rasenkai99:
Yes? :confused:

Why I'll do blind build, kek
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] ronhoover88:
So, everything is working on this build?
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] Rasenkai99:
Cts fail, will be fixed in next build

If that doesn't matter to you, rest all is fine iirc.
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] Rasenkai99:
New build is up on OP,

Fixed CTS and switched kernel to one from crd (thanks to neobuddy)
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] raider1304:
what is OP? where can i find download link for new build?
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] ZainBilq:
OP means original post(er), means the very first post of the thread.

You can find the download link in the first post.

or else download it from below link

https://sourceforge.net/projects/z2-plox/files/lineage-17.1-20200701-UNOFFICIAL-phoenix.zip/download
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] raider1304:
rom is smooth simple stock experience great job...screen looks awfully yellowish tho...also there were some initial sytemui force closes during fone setup...overall great port
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] Rasenkai99:
:eek: it's not a port, it's source built ROM.

I'll check that yellowish screen issue.
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] raider1304:
Yelowish screen was due to display mode set to Auto in LiveDisplay option.. Turned it off

---------- Post added at 02:40 PM ---------- Previous post was at 01:53 PM ----------

Thats great! I was thinking its a port... Being source built is why it is unbelievably smooth..

Also, I was wondering - Since the battery life is the only area for this ROM which could use some improvements, can I flash optimusdrunk kernel 90hz over this build? Thanks in advance ur work much appreciated :good:
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] Rasenkai99:
No idea. Take a backup and flash ur desired kernel, however if u get any bugs I wont support it :silly:
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] ZainBilq:
The fact is custom kernel causes bootloop. I already tried. This is just for info.
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] Rasenkai99:
I already know. I expected that to happen, which is why I kept that red colored warning on OP.
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] ZainBilq:
Yup..you mentioned not supported in this thread... please edit it as not supported in this ROM... ;)
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] Rasenkai99:
Mods pls close thread.

Delete if possible.

Thanks.
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] jackeagle:
Mod Edit

Thread closed per [OP] request.

jackeagle

Forum Moderator
[ZTE Axon M Questions & Answers] Atypical:
So for some background, I'm in the USA and I've started to collect some older/cheaper/weirder smartphones. Ever since the early 2010s, I've always had Android. However, I've never done anything with rooting, custom ROMs, bootloaders, any of that. A shameful gap in my knowledge and experience, but for most phones it hasn't been an issue that I've felt like pursuing.

I recently picked up an Axon M for a decent price. AT&T version, but it's GSM unlocked. I don't game on Android, so on paper everything seemed alright. Coming from the BlackBerry KEYOne, going down an Android version is a bit of a hit but otherwise I figured this phone would be a good choice for me. And at first, it really was an awesome experience. I actually enjoyed having the dual-screen way more than I thought I would. This phone also gave me a reason to keep auto-rotate on, which usually I have off. Giving up Autofill kinda sucks, but I enjoy working around limitations.

Ended up putting my SIM card in it and everything, but after a few days it seems like it was slowing down. Using Nova Launcher, and of course I had maybe 20 apps that I had installed, but the KEYone seems to handle the same setup just fine, so I'm not sure what to think.

The battery looks like it's not too hard to change, so should I change the battery? Do I get the Chinese version and see if I can get it back to English? Is there some other version that might work better for me? Do I have to mess with custom ROMs to try to get Android 8? Should I just stick with 7? I really want to daily drive this phone, and when it works I really do love it, I think more than I would love a V60 or G8X DS. So what can I do?
[ZTE Axon M Questions & Answers] 3dcantaloupe:
There is no android 8 for this phone. Heck, you can't even root it yet. I doubt it would be daily drivable after a year or so, since I had mine for almost 2 years and it started to slow down just as you have conveyed. It is a unique phone, and this is the reason to have it. I do hope that someday we can get root and a rom on this phone :)
[Galaxy Note 3 Q&A, Help & Troubleshooting] Ziedorabi:
Hello everyone

I have a Galaxy Note 3 SM-N9005 LTE , I installed TWRP and Flashed LineageOS 17.1 20200609 without ROOTING nor touching the bootloader or the kernel.

The phone works great and smoothly except for the low volume. Also, when watching youtube and I get a notification the sound becomes buzzy , basically if two sources of audio play together the sound gets messed up.

I found an audio fix for LineageOs 14 and 13 should I try installing it with TWRP ?

Thank you a lot
[Galaxy Note 3 Q&A, Help & Troubleshooting] Grn-gab:
I have the same problem, and I haven't found a solution to it yet, except disable system notifications!
[Touch Diamond, MDA Compact IV ROM Development] Bardia Garsha:
I posted this on Diamond thread, had about 30 viewings but not even a single comment. So i thought that maybe here's the right place to ask the question. (so no double-posting is intended).

I got the diamond in London (through Orange UK) , unlocked it , did hardspl, changed the radio to 05 and have now come on holidays to a country (Iran) whose network is 2G.

When I put the local SIM Card in Diamond , it recognizes the various networks and asks me to choose one and register. But as soon as I hit register, it tries to register for ages and finally fails to do so.

Is there anyway I can get over this problem and use this European-version Diamond in Iran?

I also have my Hermes and Kaiser with me (both are from Orange UK) and they both work fine with the 2G network here in Iran (of course, on these two devices i've flashed hundreds of custom roms but the Diamond is still on a stock rom)

I noticed that boinger66 is having a thread discussing Diamond in 2G India. but it doesn't seem to pertain to this specific issue.

Could this problem be ROM related? I mean could the rom on a device have anything to do with its registering or not registerin on a specific network ?

Thanks a million times for any suggestion.
[LG V35 Guides, News, & Discussion] granazias:
Hi there!

Recently i've crossflashed my V35 from AT&T to NAO USA ULM firmware.

Before flashing the new firmware,my default messaging app was the common stock LG app,but after flash,the default app is Google's messages.

I've downloaded and installed many versions of the stock LG app from apkmirror,but unfortunately non of these are working..when i try to use it as default messaging app,it always crashes and stops.

I tried disabling the Google messages,just in case of conflicting apps,so i can use the other app,but no result.

Ok the Google message app is working flawlessly,but i want to have the old class school app too as an alternative..any idea?
[LG V35 Guides, News, & Discussion] floatingtrees:
If you're rooted maybe try installing it as a system app? Also grant it the permissions it requires
[LG V35 Guides, News, & Discussion] granazias:
No i am not rooted..i've granted all permissions it requires but it doesn't work.

Thank you for your reply anyway.
[LG V35 Guides, News, & Discussion] Android#:
This is not normal and shouldn't happen. Was the stock messaging app missing altogether? What option did you use in LGUP when you cross flashed, whether it was a clean install or you used upgrade option and kept your data? Did you use any batch programs to remove bloatware? No matter what, it still is very strange that a kdz not include LG stock message app. This could also pose a security/malware risk as some out of ordinary behavior by OS could point to it having being altered. Which android version kdz (exact kdz name from lg firmwares download site would be great) is it and where did you download it from? My understanding is that usually kdz file cannot be altered so this is very strange. If you let me know which kdz it was, I can try test it on my spare v35.
[LG V35 Guides, News, & Discussion] granazias:
Hello and thank you for your reply.

Yes the LG stock messaging app was missing from the begin..when i flashed the kdz and when i completed the whole set up of my device,i started checking if everything was fine.

When i opened the message app,to make my in app settings,i saw it was the Google message app and not the ordinary stock LG app.

For cross flashing i used the Partition DL mode for clean install..i dont know if this caused that problem,but i dont think show,because i've used the same method for my V30 without problem.

I never used any programs to remove bloatware..before cross flash i just disabled some AT&T apps but my device was working perfectly.

The kdz was downloaded from lg-firmwares.com,and the version was the V350ULM20f_00_NAO_US_OP_0218.kdz

It will be very kind of you if you can test it too and give me some feedback.

Thank you in advance!
[LG V35 Guides, News, & Discussion] Android#:
Sorry, I was mistaken and also, I misread your original post. Since the days of LG V30 I haven't used LG's default Messaging app much as I started using Hangouts to call and text entirely, so I didn't even notice that messaging app had switched sometime in the last year or so. It seems that I have the same 20f version kdz from same website installed on my both V35 and don't have LG's messaging app either. I did look around online and although i didn't find any definite answer, it seems that a while ago probably starting with Android Pie LG messaging app stopped being offered or supported. You probably had Oreo when the phone was on AT&T and it had the LG's default messaging app preinstalled but once you went to Pie ULM kdz it was not bundled with the 20f kdz. By looking at dates on apkmirror website, it does seem that LG last updated it in February 2019. I also installed LG Smartworld and tried getting the messaging app that way but it is not offered there either. The ones offered on apkmirror and elsewhere on web do force close as you mentioned :( If you do get it working please share details or let's hope someone knows more and have a workaround. Good luck.
[LG V35 Guides, News, & Discussion] granazias:
Hi!

Before crossflash i was on Pie with security patch level July 2019..this is how i received the phone from the seller..maybe this is the way the ULM kdz is been released without the LG stock messaging.

I dont know if a pre-20f ULM version has it included.

Maybe somebody else can give us this info.

Thank you anyway for your help.
[Windows Mobile Development and Hacking General] gbds:
Hi all

after browsing the last few days and getting used to skiing spb mobile shell the best i could find i am now searching for a bit more, menus etc

Anyway my questions is this

if i change the settings or XML pages, is there an emulator so i can test run my new layout on my pc before i transfer it to my phone? or anyway to test in on my pc itself?

Just that i will be making noob mistakes and dont fancy like resetting my phone every 5 mins for the next year!!

thanks

GBDS
[Lenovo Z6 Pro Questions & Answers] lawong:
hi all, as the tittle said, is lenovo z6 pro using emmc or ufs storage type?

thanks in advance .
[Lenovo Z6 Pro Questions & Answers] Chema_F:
UFS
[Google Pixel 2 Questions & Answers] BB_ILI:
Good day to all!

I`d like to know if there a reason why google services are preinstalled on the actual custom roms.

As far as i know the battery life of the device could be doubled without them.
[OnePlus 8 Guides, News, & Discussion] eljefe27:
Thanks worked on.my TMobile OnePlus.
[OnePlus 8 Guides, News, & Discussion] dzontra83:
I can confirm working on OOS 1.5.6 too. I downgraded from 10.5.9 with downgrade rom, which restores OOS to 10.5.6, and followed your guide and it worked as a charm. The only problem is that i cannot lock back the bootloader, cause it breaks FP again. Did you maybe try to lock it to try? Nice work man.
[OnePlus 8 Guides, News, & Discussion] TheKnux:
T-Mobile OnePlus 8 here. Stock firmware, orginally had my bootloader unlocked, rooted with TWRP and Magisk, backed up modem, converted to international firmware (10.5.7), lost signal, had to restore modem, ota'd to 10.5.9, unlocked bootloader again, rooted, etc. All while having a working FP the whole time. Ended up flashing EdXposed via Magisk, broke SafetyNet, etc, did a factory reset on TWRP (3.4.0-1 test), wiped data, rebooted recovery, rebooted system, booted back to TWRP. Installed Magisk to see if it'll boot with root, same thing. MSM'd back to T-Mobile firmware, then converted to international again. After the conversion was done and I unlocked bootloader and rebooted to system, my FP was broken. Ended up MSM'ing back to T-Mobile stock to see if it would work again, nothing.

TL;DR does this method only work if I had a working FP to begin with like it did stock out of the box?
[OnePlus 8 Guides, News, & Discussion] dzontra83:
Just follow the guide, you'll have it working. You just have to backup your current persist
[OnePlus 8 Guides, News, & Discussion] TheKnux:
So back it up even though it's broken? I'm on T-Mobile stock again, locked BL. Should I unlock, root, then pull persist and back it up?
[OnePlus 8 Guides, News, & Discussion] dzontra83:
Exactly, a T-Mobile user confirmed guide to work, check 2nd post
[OnePlus 8 Guides, News, & Discussion] TheKnux:
While on 10.5.7, unlocked bootloader, I flash TWRP, then reboot, and it boots back to TWRP. When I flash Magisk 20.4 zip in TWRP, it goes to boot, then enters CrashDump Mode. When I try and use the flash-all to downgrade to 10.5.4, I get a bunch of fastboot "cannot flash critical partitions" errors, it fails, and goes back to CrashDump Mode. What am I doing wrong? Also, is it really necessary to downgrade to an earlier version of OOS to use Engineering Mode or can I use 10.5.7?
[OnePlus 8 Guides, News, & Discussion] dzontra83:
When you unlock bootloader, only boot into TWRP, then install magisk, i thin it Is still recommend to only boot into TWRP, not to flash it.
[OnePlus 8 Guides, News, & Discussion] TheKnux:
Thank you so much, that worked! New problem, what do I do since I can't downgrade to an earlier OOS (10.5.4)?

Performing the test on T-Mobile 10.5.7, when performing the test, nothing is failing after pressing start test. Its all passing, what should I do?

When trying to downgrade using the 10.5.4 MSM Tool. it gives an error of "Unsupported Target TMO" and "param preload" and fails.
[OnePlus 8 Guides, News, & Discussion] dzontra83:
Did you follow the instructions in test exactly? In second test you must't press the sensor.

Can help you with TMobile model, I have international one.
[OnePlus 8 Guides, News, & Discussion] TheKnux:
I figured it out. I was just being a dumbass I guess. Has anyone noticed the fingerprint sensor not being able to read that well compared to before it was broken? It seems like it fails a lot more before it succeeds. Unless now that it's working, we can perform the calibration again and it'll work better?
[OnePlus 8 Guides, News, & Discussion] dzontra83:
Don't know about that, mine works just fine
[OnePlus 8 Guides, News, & Discussion] TheKnux:
So I think I messed up, I ended up performing the calibration again, while it was already working, and now it says "fingerprint hardware not present" any suggestions on how to fix? I performed the instructions in the guide (again) and nothing worked. When the error pops up, if I press back, the error message goes away and the FP icon is there. When I tap on it, it lights up white but doesn't vibrate or register anything. I already used the MSM tool to go back to Tmobile stock, then used the fastboot ROM to go to Global 10.5.7, followed the guide again, still nothing.
[OnePlus 8 Guides, News, & Discussion] dzontra83:
The initial backup of the persist.img should do the trick, if you repeat the process once again, it should work
[OnePlus 8 Guides, News, & Discussion] TheKnux:
I tried that, multiple times. Still not working. Is it possible for someone to upload their persist.img so I can try it or is it device specific? Granted, I pulled my initial persist.img from stock rooted Tmobile ROM AFTER I broke it even though it worked before (long story). I wasn't able to downgrade to 10.5.4 because when I tried using the MSM tool, it gave me a TMO device error and I couldn't use a fastboot ROM to go to 10.5.4 cause it kept entering CrashDump mode every time it tried rebooting to fastboot to finish the flash process .
[OnePlus 8 Guides, News, & Discussion] dzontra83:
Your cannot use someone else's persist, you must't use yours.
[OnePlus 8 Guides, News, & Discussion] TheKnux:
What about someone else's DATA and ENGINEERINGMODE folders? I've tried everything. Even recalibrating multiple times. It's not giving me a bunch of errors like it did before, just one error. The last error is FAIL! OPERATION_STEP_GET_KB_CALIBRATION TEST FAIL:GF_ERROR_GENERIC

Just wondering, what is the point of downgrading to an earlier OOS? If I was able to do it on the Tmobile firmware with success, is there an importance in downgrading?
[OnePlus 8 Guides, News, & Discussion] starcms:
Thank you so very very much!!! I have a T-Mobile 7T Pro 5G McLaren which hasn't had a working fp in almost 2 months. I hadn't made a backup of persist before the fp broke, so I thought I was completely screwed. Luckily, I did make a backup of persist before trying to use the fp calibration tool myself without any luck shortly after it broke (basically just clicking stuff and guessing lol). Found this thread and I had my FP scanner working again perfectly in less than 15 minutes!!!! Thank you soooo much for all the hours and effort you put into figuring this out!!!!!!!

Didn't have to run the msm tool to revert to older version of OOS and lose all my data either!!

Just one question and it's just for my curiosity. Why do we delete "gf_persist.so" from our original persist.img before copying/pasting into /persist partition after "calibration"? Is gf_persist.so not a file containing part of the original calibration? Is that the file which is being fixed by running the hidden calibration commands?
[OnePlus 8 Guides, News, & Discussion] TheKnux:
If anyone can help me, it would be much appreciated. https://xdaforums.com/oneplus-8/help/broken-persist-img-problems-t4129587
[OnePlus 8 Guides, News, & Discussion] antnyhills:
I would assume that file is what is being "fixed" yes. If you were to use your original the guide would not work. I would love to see what in that file changes to simplify the guide, but that is nearly impossible based on the type of file it is.
[OnePlus 8 Guides, News, & Discussion] starcms:
Do you know what the correct/default permissions of the files in /persist/data and /persist/engineermode should be?

Edit: The reason I am asking is because the FP sensor works perfectly (100%, never misses a scan, literally always on first try) when I am using it to unlock an app or in an app. On the main lock screen it works about 90% of the time on first try. But on the ambient screen, it only works maybe 25% of the time at most. The vast majority of the time it fails the first three scans and the camera pops up and unlocks for me. It's definitely not a calibration issue since it works inside of Android perfectly and the only issues are at the lock screen and especially on the ambient lock screen. Never had this issue before I broke it. Tried wiping cache from Ambient app as some had suggested in other fp threads but of no help. Any advice?
[OnePlus 8 Guides, News, & Discussion] antnyhills:
I doubt it has anything to do with this fix, I would try adding your fingerprints again.
[OnePlus 8 Guides, News, & Discussion] GolfislikeLife:
desperately need someones help with guide and video.

[MENTION=4781115]antnyhills[/MENTION] or whoever completed guide successfully. I am new to all all of this and have read through the steps and watched the video and still am confused by step one for trying to run in adb shell or with emulator get permission denied error. Not sure how to fix or even run the command and yes I am rooted which is what confuses me the most? The rest of the guide I have already completed. Would like to figure this out tonight USA time so I don't have to send it in the morning with my already approved RMA. Thanks in advance. Kevin
[OnePlus 8 Guides, News, & Discussion] antnyhills:
After typing 'SU' you have to grant permissions to ADB via Magisk.
[OnePlus 8 Guides, News, & Discussion] GolfislikeLife:
Thanks much for the help and it worked with no errors.

Thanks and after backing up ready for next steps. The one question I have is the codes 801 and 808 don't work on my stock dialer to get into factory mode. They take me to a blank screen like I never entered anything. Any ideas.
[OnePlus 8 Guides, News, & Discussion] antnyhills:
Did you perform my guide here ( https://xdaforums.com/oneplus-8-pro/how-to/guide-unlock-factory-mode-root-t4118527 ) first?
[OnePlus 8 Guides, News, & Discussion] GolfislikeLife:
I responded earlier but something happened and lost my reply. Yes I did follow your guide to the letter but still the phone codes never went through successfully so what might I being doing wrong. I installed the factory unlock file through TWRP and Magisk is the only thing I can think of that might be incorrect? Thanks in advance for your patience with me and sooner rather than later will have success. Thanks, Kevin.
[OnePlus 8 Guides, News, & Discussion] dzontra83:
Did someone managed to successfully lock the bootloader after this guide, and keep the FP to work (not to result in soft brick or lose the FP again)?
[OnePlus 8 Guides, News, & Discussion] starcms:
I think the only safe way to relock and not corrupt persist/lose FP is to use the appropriate MSM tool for your device (which completely resets your phone/lose all data but also relocks the bootloader). Not "fastboot oem lock"
[OnePlus 8 Guides, News, & Discussion] dzontra83:
I know that, but it breaks fp when you use MSM tools.
[OnePlus 8 Guides, News, & Discussion] starcms:
Oh, I didn't realize that. I thought only fastboot oem lock was causing issues.

My only guess is the checksum for persist no longer matches after following the directions in OP to fix it (or after having corrupted it in the first place) so even running the MSM tool causes it to be seen as "invalid" and corrupts it again.

But even after relocking by "fastboot oem lock" or running the MSM tool, you should be able to still use the DD command to restore your backed up, fixed, persist.img (which you should have made a backup of and stored in at least 2 different places not on the phone after fixing it), even with bootloader locked and no root, once booted into stock recovery. Restore with DD command, reboot, and you should be good again with bootloader locked.

From your PC while phone is booted into Android with ADB debugging enabled with bootloader locked and using your fixed persist.img:

adb reboot recovery
adb push persist.img /sdcard/
adb shell
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
exit
adb reboot

Let me know if that works for you.
[OnePlus 8 Guides, News, & Discussion] dzontra83:
Does not work, wont let me flash persist.img - permission denied

Edit: It did work (with new working perisist.img as you told me) but when i unlocked the bootloader, gained root, and flashed it with su command after adb shell. So u still cannot lock your bootloader and keep FP alive