yashsingh1/xdaforums huggingface dataset:
[OnePlus 12R / OnePlus Ace 3] 954wrecker:
My issue is unlike every other OnePlus I have ever owned it won't keep the few apps I use each day in memory for some odd reason. I'm running the exact same apps on the 12r that I have on my OnePlus 8 and OnePlus 9 and OnePlus 11 and it's the only phone I own that can't keep apps in memory and has to reload them all day long. I'm tired of factory resetting over and over again this 12R is going back to OnePlus. Looks like XDA has really gone downhill over the years so I'm not expecting much help here.
[OnePlus 12R / OnePlus Ace 3] Zxalilh:
It's so that your phones doesn't lag so much when opening apps. You could custom rom or root your device if you want to change some settings.
[OnePlus 12R / OnePlus Ace 3] njaya95:
Try developer options, keep background activities. Might help.
[OnePlus 12R / OnePlus Ace 3] 954wrecker:
Thanks but I'm literally running 3 other older OnePlus phones with the exact same apps and settings and they have no lag and the apps aren't constantly killed in the background.
[OnePlus 12R / OnePlus Ace 3] 954wrecker:
I've tried every setting and nothing stops the apps from getting killed.
[General Questions and Answers] niceguy167:
This is a generic root question in android 14.

I created some scripts and in them they call Busybox for chroot.

None of the commands run they return directory not found.

If I run the command by itself it executes perfectly.

Here is my test script.

The command Busybox mount will run perfectly fine with just a SU then typing the command in by hand.

The second it's put into a script startu.sh and i run a sh startu.sh from command it just errors out with

Failed: No such file or directory and the path /dev/local/tmp/...........

Thanks for any help :)

#!/bin/bash

busybox mount --bind /dev /data/local/tmp/ubuntu/dev
[General Questions and Answers] niceguy167:
Answered my own issue.

Termux likes tsu for root login.

I was using su and then vi scriptname.sh to edit my script.

After i used tsu and ran a VI I found a bunch of ^M characters at the end of each line I was not seeing using vi in SU I removed them re-saved and in TSU was able to execute the script now :)

Hope this helps someone else :)
[Nothing Phone 2] dogmunch:
currently stuck in a bootloop and cannot enter recovery mode using the button combo, any advice?
[Nothing Phone 2] dogmunch:
little bit more information. its stuck between the boot loader is unlocked screen with the orange text it shows this for a while then it displays nothing on the screen in the dot matrix font, it just loops this
[Nothing Phone 2] dogmunch:
okay bit of an update, managed to get into the bootloader but fastboot on my pc doesnt recognise it :/ got a feeling my phone is ****ed here
[Nothing Phone 2] dlads:
Whatever firmware you're on.

If you're rooted then grab the patched image and boot it from the bootloader screen.

Phone isn't broken.

How did it happen? What did you do?
[Nothing Phone 2] dogmunch:
i think i attempted to boot with a corrupted .img file? thats what makes sense to me, im trying to boot via patched imaged now ill let you know how that goes
[Nothing Phone 2] dogmunch:
attempting to use your 2.5.2 patched ( the one on your guide ) throws this error

FAILED (remote: Failed to load/authenticate boot image: Not Found)

finished. total time: 0.020s
[Nothing Phone 2] dogmunch:
scratch my previous reply ^^

it throws this now instead

FAILED (remote: Failed to load/authenticate boot image: Bad Buffer Size)
[Nothing Phone 2] dogmunch:
scratch that again ^ sorry for the spam of replies but whenever i attempt to boot it just brings me straight back into bootloader
[Nothing Phone 2] dlads:
Are you actually bootloader unlocked?

Have you actually rooted before?

Hard to say how help without more information.

What exactly did you do prior to your phone boot looping?

I know the patched boot image works because I'm using it myself.
[Nothing Phone 2] dlads:
You could also just grab the stock boot image and

Fastboot flash boot boot.img

That will get you in the system if indeed the boot image is the culprit.

What command are you typing?

Should be:

fastboot boot "name of image"

Replace "name of image" with the actual name of the image.
[Nothing Phone 2] dogmunch:
bootloader is unlocked, i was rooted before this, i used a custom rom and attempted to revert back to stock and during this i think i may have used a corrupted .img file
[Nothing Phone 2] dogmunch:
and im attempting to use a custom image now using the fastboot boot command will keep you updated again
[Nothing Phone 2] dogmunch:
not custom image i meant stock image ^^
[Nothing Phone 2] dogmunch:
after flashing stock image im greeted with the ndot NOTHING logo, instead of the booting animation it just stays there and does nothing
[Nothing Phone 2] dlads:
You were on a custom rom? So what method did you use to revert to stock?

I would say without knowing your answer that you should flash a fastboot ROM.. check out Arters or spikes threads and grab the latest firmware then flash it.

Instructions in the thread.

Failing that you could use the EDL flash tool as your device is not in crash dump or black screen of death just yet 😉

Hope you have an EDL V2 cable handy in case.

Shouldn't need it but if you ever do it takes a long time to get one.
[Nothing Phone 2] dlads:
After returning to stock did you factory reset?
[Nothing Phone 2] dogmunch:
i couldnt get my phone to boot which is my issue, its like its rejecting the .img file
[Nothing Phone 2] dogmunch:
and for attempting to revert back to stock, i tried to restore via a backup i had made by orange fox but it just all went south from there, booting into orangefox the backup files are gone
[Nothing Phone 2] dlads:
You don't need to get it to boot to factory reset.. if you're in the bootloader you can boot to the recovery image, if that's not booting then flash that too..

As I've asked, what method did you use to get back to stock? It should seem that your recovery is missing, so other components are probably missing too.

Just flash a fastboot ROM mate.. failing that, use the EDL package, my latest comments at the end of the thread show you how.
[Nothing Phone 2] dlads:
Just seen this.

Id say flash a fastboot ROM from spikes thread..

You're already in no mans land here, so bite the bullet.

This information is that you should have led with mate
[Nothing Phone 2] dogmunch:
ah sorry for that, so your advice is fastboot a custom rom and then attempt to get the stock files?
[Nothing Phone 2] dlads:
A custom rom? Nah

Spikes got a thread with stock ROMs..

Get yourself back to stock, remember how you did it then you can flash what you like knowing how to revert if you need to. 👍🏼
[Nothing Phone 2] dogmunch:
im assuming by spikes thread youre reffering to this

if you cant tell im a little new to all of this but i think ive made that pretty obvious xd
[Nothing Phone 2] dogmunch:
re reading old messages

"as your device is not in crash dump or black screen"

mightve already reached there, pressing start whilst in fastboot leads to crash dump :/
[Nothing Phone 2] dlads:
Yea that's the one mate.. plenty of info in there.

I've never had to use it myself but it's been used by many before...

Id say always leave yourself an escape route when you flash a custom ROM...

If this fails then I would say flash the EDL package, would probably be easier but stick with the fastboot ROM for now.
[Nothing Phone 2] dlads:
That's ok, so long as you can get to fastboot mode (bootloader) then you're good to go.

You're system goes to crash dump mode because the images required to boot the system are missing / corrupt.
[Nothing Phone 2] dogmunch:
just had a proper look through the post and the github, gonna attempt the flash all.bat and let you know how that goes
[Nothing Phone 2] dlads:
Good luck man... Leave a like if it works..

I'm sure you'll be fine.

👍🏼
[Nothing Phone 2] rjfbeoqb3fiwk2bto:
i have used this trick to fix my bootlooping device.

try holding the vol down + power, it typically needs 15-30 seconds, after the screen is off, immediately press vol up + power, this will hopefully make your device get into the recovery mode (i actually use the odin mode in my case but if your device is not samsung then use the recovery mode), but if you also flashed the recovery, if it is also corrupted or not working on your device then according to me which is only 11 year old (its me right now) : impossible to repair.
[Nothing Phone 2] dlads:
That's not true.

Why is it impossible to repair?

If you can get to your bootloader and your bootloader is unlocked then you can flash a fastboot ROM..

In his case his recovery is broken because he's flashed a custom recovery which is now not functional... All of his images which make up his system are borked..

PS: I get you're 11 but don't spread misinformation.

Odin also has no place on non Samsung phones so no point mentioning it here 👍🏼
[Nothing Phone 2] dogmunch:
im feeling so stupid right now xd. i tried to flash all of the stuff from spikes github before by only downloading one part of the zip, i didnt realise that theres 3 parts to it, im hoping installing and flashing it all will fix my issues
[Nothing Phone 2] dogmunch:
yup full stock image download from spike fixed it, thanks for your help through my stupidity thought my phone was a gonner
[Nothing Phone 2] dlads:
You're more than welcome, at least now you have an exit strategy for when you flash another ROM..

Glad you're sorted 👍🏼
[Android Q&A, Help & Troubleshooting] openavb:
Hi,

I have the Servers Ultimate Pro installed on a Samsung Galaxy phone. All requested permissions have been granted to the application. The Simple menu option starts a server, but not further changes are saved!. When I attempt to create a new server using the Servers menu option, it never shows. Changes are not saved!

I have the app installed on internal storage and the app does not navigate to anything on the sd card. If I try to navigate to the sd card I receive an error message: "Error loading: 'emulated' can't be read. "

Please help!!!

Thank you.
[Android Q&A, Help & Troubleshooting] openavb:
The Samsung Galaxy A54 5G appears as incompatible phone with Servers Ultimate Pro. I tried disabling the Play Store and using the browser only. The pictures below are one from the store and one from the browser, which greyed the phone out.

View attachment 6069609
[Android Q&A, Help & Troubleshooting] openavb:
Please, I really need help. I would appreciate if anyone has a solution for this.

Thank you
[Android Q&A, Help & Troubleshooting] maddler:
App hasn't been updated 2020, not much you can do about that.
[Android Q&A, Help & Troubleshooting] openavb:
Thank you.
[General Questions and Answers] gnuarchbtw:
I have a bricked Nokia 1.3: can get to fastboot, doesn't boot and bootloader was locked when I tampered too much - oem unlocking also not allowed :(

So my question is, is there any way to get it to boot again? I can get access to EDL, and have fully flashed every 'stock' ROM I could find online, none booted. Am I missing something? Or is the only way to get it working to flash an unlocked bootloader? In which case, is there anywhere I could obtain that?
[General Questions and Answers] zinkles:
how did you get it bricked in the first place? flashed wrong ROM? flashing unsuccessful?
[General Questions and Answers] Rob wili:
Here are a few steps you can try:

Check Firmware Compatibility: Ensure that the firmware you're flashing is specifically designed for your Nokia 1.3 model. Using incompatible firmware can lead to boot issues.

Use Official Firmware: If possible, try to obtain the official firmware from the manufacturer's website. Official firmware is more likely to be compatible and reliable compared to third-party sources.

Flash Bootloader: Since the bootloader is locked and OEM unlocking is not allowed, flashing an unlocked bootloader might not be possible through conventional means. However, some users have reported success in bypassing locked bootloaders by using specialized tools or techniques. Be aware that attempting to unlock the bootloader without proper authorization may void your warranty and violate the terms of service.

Seek Professional Assistance: If you've tried multiple firmware versions and still cannot boot your device, consider reaching out to a professional repair service or contacting Nokia support for assistance. They may have access to additional tools or methods to help recover your device.

Community Forums and XDA Developers: Community forums and websites like XDA Developers often have active communities of users who share tips, tricks, and solutions for repairing and customizing Android devices. You may find helpful advice or resources from experienced users who have encountered similar issues with the Nokia 1.3.

In any case, proceed with caution when attempting to flash firmware or modify your device's software, as improper procedures can potentially cause further damage. If all else fails, your last resort may be to consider replacing the device or seeking professional repair services.
[General Questions and Answers] xXx yYy:
@gnuarchbtw

If you're still facing boot issues with your Nokia 1.3 TA-1205 despite flashing various stock ROMs through EDL mode here some hints to fix it:

1. Verify ROM Information:

Double-check model and region: Ensure the stock ROMs you flashed are specifically for the Nokia 1.3 TA-1205 and your region. Flashing an incompatible ROM is a common cause of boot failure.

Source reliability: Download ROMs only from trusted sources like the Nokia website, XDA forums, or reliable communities. Avoid untrusted sources as they might contain corrupted or incompatible ROMs.

2. Flashing Process Scrutiny:

Tool and method confirmation: Use the correct flashing tool recommended for your device and ROM, e.g.
[General Questions and Answers] gnuarchbtw:
Well in short my stupidity... Not exactly sure what happened for it to brick, but reflashed nearly every partition one by one and bootloader became locked and phone didnt boot past fastboot mode... Just gives error saying 'No valid operating system could be found. The device will not boot.'
[General Questions and Answers] gnuarchbtw:
Thanks for this :) but I think maybe its possible that the required stock rom isn't available anywhere online. The checksums of aboot vs abootbak and similar don't seem to match, so clearly the roms I am flashing are not the true stock. Equally, haven't seen anything for this model on XDA, nokia etc. so I think it's screwed now...
[General Questions and Answers] gnuarchbtw:
Did a bit more research... Looks like some phones with locked bootloader can accept a user set root of trust as well as OEMs? Does anyone know more about this? Or if its even possible here? I know I'm not getting past Qualcomm's boot security... And don't want to waste time on something that just can't be done.
[General Questions and Answers] mvikrant97:
Your device has to be flashed in EDL mode.

Which tool did you use to flash it in EDL mode?
[General Questions and Answers] gnuarchbtw:
Have tried QPST/QFIL on windows, bkerler's EDL on Linux, and I can successfully flash with both, but I've realised that none of them can flash to super partition, not sure why. But could it be causing any issues?
[General Questions and Answers] mvikrant97:
Yes super partition is important.
[General Questions and Answers] gnuarchbtw:
Sorry for continuously coming back here... But I still can't seem to figure this out. What could possibly be preventing super from being flashed? I can flash a small image to it, but the stock super image of around 2GB doesn't flash... And also, why would not having valid super stop me from booting to recovery as I can't do that either?
[General Questions and Answers] mvikrant97:
I can try with Unlock Tool which is a licensed software.
[General Questions and Answers] gnuarchbtw:
Sorry completely forgot about this since I did manage to get it fixed... All I had to do was use a hex editor to flip the bit that says 'sys.oemunlockallowed' in system.img and then it allowed unlocking :)
[Touch HD General] Farcorfe:
Can anyone help with resolving this problem? The lower softkey backgrounds have changes to grey ISO black. It happened before with a game, but the the problem went when I uninstalled it.

Now the problem came back after I put CE Star on, but even after I removed CEStar, cleared the installation folders and soft reset a few times the problem remains. I could be wrong to blame CES, but it was the last program on before the issue came up.

I tried disabling and re-enabling touchflo, changing themes around and back to black etc. I left it switched off overnight to think about settings sticking but still no joy.

Grateful for any suggestions and thanks.

[Edit : It seems to have been caused by "big5vcs.tbl" and/or "GBxxx.tab" (xxx I forgot the full filename) being left behind in the \Windows directory. Deleting them and a soft reset resolved the softkey colour issue.]
[Touch HD General] wan576:
I have the exact same problem on my HTC Touch HD. But idont have those 2 files you mentioned..does anyone know exactly why this happens? there must be some other file for me in my windows directory that must be causing it. how did you know which files were to be deleted?
[Touch HD General] Farcorfe:
I'm always wary when installing potentially incompatible programs.. especially with the HD and its huge screen. Take some time to poke around the windows folder and look for any orphan files. In my case suspect files as I named above were dated on the date/time I put CE-Star on, so I knew they should be safe to delete.

This still leaves room for error though, so be sure of what you're doing. I suggest you try to back track and remove software/revert settings changes in reverse order until you fin the culprit! Searching here may also help if you have suspicious programs.
[Touch HD General] wan576:
Solved!

Great news..i'm able to solve the problem..now i have the black soft keys back! What i did was used Memmaid to see what was starting up with windows, and disabled the items i didnt need to start up..in my case, it was Mapking_sms.exe and batti__sumthing__.exe.

After disabling those, a soft reset got everything back in order again... fewh..

hope this helps other people as i have searched for a solution for this problem for weeks!!
[Google Pixel 8] ratze_x:
How can i move the lock screen clock from top left to a different position?

Not just dynamic clock which just centers the clock but free movement like ie display the clock bottom right.

Any mod available? Tested evox and crdroid and didnt find such :( /me=blind?
[Xoom General] motofan82:
Hello I recently got the vintage device.

I have a question.How can I install a working google play store?I am on 4.04 software version and I can't even open my account? Thanks.b
[General Questions and Answers] rjfbeoqb3fiwk2bto:
is it possible to get the system app privileges by using a not preinstalled system app? like thermal guardian, it was meant to be preinstalled but is not on some devices, manually installing thermal guardian seems to still have all of thermal guardian capabilities of modifying settings, so is creating a whole different app with the same package name and signature will give the app the privilege?

is it legal? is it ethical? will it even work?
[General Questions and Answers] DiamondJohn:
I have avoided making apps system apps by cheking their SELinux failures (ser apps have less privs) and adding magisk allows in a boot script.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] razorloves:
​

LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.

All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Wiki for more details.

Downloads:

pixel 3: https://download.lineageos.org/blueline

pixel 3 xl: https://download.lineageos.org/crosshatch

gapps zip: (use arm64) https://wiki.lineageos.org/gapps#downloads

Initial Install Instructions (for when you're on a non lineage rom):

pixel 3: https://wiki.lineageos.org/devices/blueline/install

pixel 3 xl: https://wiki.lineageos.org/devices/crosshatch/install

Update Instructions (from old 21 to new 21):

pixel 3: https://wiki.lineageos.org/devices/blueline/update

pixel 3 xl: https://wiki.lineageos.org/devices/crosshatch/update

Upgrade Instructions (from 20 to 21):

pixel 3: https://wiki.lineageos.org/devices/blueline/upgrade

pixel 3 xl: https://wiki.lineageos.org/devices/crosshatch/upgrade

Notes:

1. lineage roms come with adb root that you can enable in developer options, but if you want root for apps, you can grab the magisk apk, then adb sideload it in lineage recovery.

2. The newest radio & bootloader img's are included in the official lineage rom zip, so no need to worry about updating those manually.

3. When you format data in lineage recovery, you might see an error like "cant send spi message". you can ignore it. The same thing happens with google's stock rom and recovery.

Changelog:

https://download.lineageos.org/devices/blueline/changes

https://download.lineageos.org/devices/crosshatch/changes

Known issues:

esim works on lineage-21, but new ones can't be added while on lineage-20 or 21. so, if you need to add one then you need to be on older lineage version or on stock.

Bug reporting:

https://wiki.lineageos.org/how-to/bugreport

THANKS:

Huge thanks to mkbestas. He practically did all the work bringing lineage 21 to the pixel 3 thru 7 line of devices.

Source Code:

crosshatch device repo: https://github.com/LineageOS/android_device_google_crosshatch/tree/lineage-21

blueline device repo: https://github.com/LineageOS/android_device_google_blueline/tree/lineage-21

kernel repo: https://github.com/LineageOS/android_kernel_google_msm-4.9/tree/lineage-21

crosshatch vendor repo: https://github.com/TheMuppets/proprietary_vendor_google_crosshatch/tree/lineage-21

blueline vendor repo: https://github.com/TheMuppets/proprietary_vendor_google_blueline/tree/lineage-21

Android version: 14

Kernel version: 4.9.337
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] fakugd:
Thank you, Sir, for keeping this beautiful device alive!.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] razorloves:
fyi

if you're wanting to update from my unofficial 21 to official 21, you can't use the Updater app in settings because it doesn't allow rom zip install with different signatures.

so you'll have to do it manually in recovery.

just go into lineage recovery and adb sideload the lineage 21 rom zip.

and if you have gapps and/or magisk, tap advanced -> reboot to recovery. then adb sideload the android 14 gapps zip and/or the magisk apk.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] devsk:
On crosshatch, updating to official 21 from unofficial 21 is leading to Settings, Bluetooth and Phone app crashing. It was all working fine on unofficial 21 build.

I did the sideload sequence for rom, gapps, magisk 2 times already. Still crashing!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] devsk:
Looks like Magisk Props Hide module is broken. Disabling it fixed this issue.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] edeed:
had this issue on unofficial build too but on browsers can't replay a video after it was paused
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] devsk:
For some reason, eSIM is broken on my wife's Pixel3 with LOS 21. I can't connect, I can't erase and I can't add the new one: as soon as Fi app reaches "Download" and I say "yes", it just comes out with error about not being to add.

Anybody else seeing an issue with eSIM on Pixel3?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lpedia:
This is to be expected if the eSIM wasn't added in stock or in a LOS earlier than 20. eSIMs can't be added in LOS 20 or LOS 21 but will continue to work if added in an earlier OS.

From the first post in this thread:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] PN0327:
My fingerprint wasn't regconized. But it's fine now after rebooting though.