yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] NaBelea2:
Hello,so I was wondering what apps do you guys/girls use to create a folder and password protect it? For things like personal photos,documents etc?

Thanks for any and all answers!
[General Questions and Answers] DiamondJohn:
I have no experience with your deive specifically. But have had devices that cannot boot intp the ROM/Firmware. These devices are ressurected by flashing stock, which is normally (depending on yopur device) from a command window using FASTBOOT, or the device may have a windowws based flashing tool.

Again, I do not know if this is a featire fore certain, however, for a feature rich file-manager, many here at XDA use MiX.

[APP][2.2+] MiXplorer v6.x Released (fully-featured file manager)

[APP][2.2+] MiXplorer (full-featured file manager) Hello everyone! My name is Hootan. I work on XDA in my free time and this file explorer is my favorite Android project! MiXplorer mix of explorers (SD, FTP, Lan, Cloud and other storage...

xdaforums.com

search the thread for the function, and there is also the FAQ, which may have an explanation of how, if it is possible. Its more appropriate to ask functionality question there.

MiXplorer: Q&A and FAQ (User Manual)

MiXplorer: Q&A and FAQ (User Manual) Table Of Contents: i. INTRODUCTION, GETTING MIXPLORER, & INSTALLATION (This post) ii. UI, NAVIGATION, VIEW CONFIGURATION, BOOKMARKS, TABS iii. WORKING WITH FILES & FOLDERS (Copy Move methods, Trash option)...

xdaforums.com
[General Questions and Answers] Tib_7940:
hello can anyone help me out with my realme 7 it got stuck in a bootloop after updating to the realme ui 2.0 and i tried downgrading the software using sp flash tool but when clicking the flash button it shows STATUS_BROM_CMD_FAIL (0Xc0060005) also i cant boot into recovery or fastboot
[General Questions and Answers] SubwayChamp:
Well, this is quite different, stock and custom ROMs have different ways to be applied.

Better now is try to restore the stock ROM that will put the things in its proper place, You shouldn´t use qfil for this, it could end by causing more damage than solution to your device if it is not correctly used, you should use the official tool for your device https://androidmtk.com/download-lenovo-downloader I hope that it solves your mistake.
[General Questions and Answers] SubwayChamp:
You shouldn´t try to downgrade it, better is prepare your device before to receive an update by wiping caches and if it is a major update, formatting data should be meeded in some cases.

Preloader avoided downgrading and got bricked. I´m not sure if the ROM (ofp) contains the files for SP Flash tool, Did you try to use the tool for Realme? https://androidmtk.com/realme-flash-tool
[General Questions and Answers] ithan80:
i had tried with qcomdload,its the same as i see with lenovo downloader,but always had the same message "cannot open raw file". Probably i do something wrong or i haven't download the correct rom.i download the rom from here :https://firmwarefile.com/lenovo-tab-4-10-plus-tb-x704l . i tried 10 minutes ago it says step : sahara ,status :flashing ,time 1000seconds and still flashing, but i must leave for work.But at the begining again the same message ''cannot open raw file'' .
[General Questions and Answers] ithan80:
yes with fastboot.i tried some times but i read that first you must put your device on debug,how is this possible when my device reboots all the time.i think that in order to work Fastboot,the pc must recognize the tablet,mine don't.when i am writing adb devices in fastboot,it recognizes nothing.
[General Questions and Answers] DiamondJohn:
I have no idea what you mean by "debug mode". The devices I have done this step on, required to be put into fastboot/download mode. This mode is entered via a key combination (eg power & vol-down). As such, the phone does not have to boot the normal system and hence you can recover your phone to a working state.
[General Questions and Answers] TheBeast941:
"adb devices" in fastboot?

You're meant to use "fastboot devices" in fastboot.
[General Questions and Answers] TheBeast941:
Alright, suppose I do find a TWRP for the same chipset (ie mt6761 for my device). What information should I need to obtain from my device in order to port the TWRP to it? I'm asking because all porting guides require a copy of the stock recovery image so is there a way to get the information required from my stock rom?

Another question is if I manage to build a TWRP image, how do I test to see if it works on my device? Executing "fastboot boot TWRP.img" seems to hang on the transfer ok screen for a few seconds then the device reboots into Android. Tried temp booting a magisk patched boot.img as well but it would always boot into the boot.img currently flashed onto the device.
[General Questions and Answers] ithan80:
i mean this https://www.xda-developers.com/15-s...ng-fast-adb-fastboot-and-driver-installation/ , you mean something other?
[General Questions and Answers] ithan80:
ok i understand what you mean.i enter fastboot with no problem, the problem is with the comand window, my pc don't recognize the tablet, i connect the tablet in a usb port and nothing happens, as there isn't anything there. I open the tablet enter fastboot mode and again nothing, don't recognize the device. So how will i do anything from a comand window? i also use this https://www.xda-developers.com/15-s...ng-fast-adb-fastboot-and-driver-installation/ and when in the command window write adb devices, nothing happens, there is no device.
[General Questions and Answers] TheBeast941:
If you used the installer in the main thread that won't work anymore, use the link provided in the mod edit to install ADB and Fastboot: https://dl.google.com/android/repository/platform-tools-latest-windows.zip (you'll also need drivers to allow your PC to communicate with your phone, just google drivers for <device name>)

Also, again:

"adb devices" is for when your device is on and in Android

"fastboot devices" is for when your device is on and in fastboot mode.
[General Questions and Answers] Rizwan66:
Bro how can i directly contact you i am not undrstnding cuz i am new to oneplus .. and my android version is still 10.0.12
[General Questions and Answers] Rizwan66:
Can you give me ur whtsapp ar instaa to contact plz
[General Questions and Answers] TheBeast941:
I'm kinda a noob here as well 😅

You should be able to get your questions answered pretty soon by more experienced users
[General Questions and Answers] ithan80:
thank you, i will try it
[General Questions and Answers] xunholyx:
Hi

I don't know what you are talking about here or who you are replying to.

In the future, please use the reply option when replying to someone. That way the person you are replying to will get a notification. Also, someone like me coming across your post can click on what you are replying to and go back to see the conversation and might be able to jump in to help.
[General Questions and Answers] SubwayChamp:
You should get this information and files from the boot image, of course you have to know something about decompile and recompile (there are some pretty tool to do so).

In order to flash anything to some partition you need to unlock bootloader and also critical partitions, a recovery ported this way won´t survive in the boot partition so it has to use atleast a minimal portion of the ramdisk to live in the boot partition, for this you should need a TWRP installer that have to be flashed through TWRP, in the meantime push a copy of the stock boot to your SD card in case you can´t boot to system again.

As I said you TWRP has to be flashed to the boot partition, if it´s not well ported then you will overwrite it and you can´t boot to system so you´d need to flash again the boot image unless the TWRP base has the ability to do so.
[General Questions and Answers] SubwayChamp:
This message is clearly referring to an image that can´t be handle by the tool, I have to assume that you atleast unzipped your file (?). Upload some screenshots from the folder inside to see which files contain. In case you don´t know qfil works with EDL mode and the LDT works with fastboot.
[General Questions and Answers] ithan80:
i manage to get it work and after 60 secs the programm closes by itself,it never finishes the flashing. 3 times now.After many efforts with different versions of lenovo downloader i managed to flash it,but unfortunatelly it reboots again.I will try this https://xdaforums.com/t/my-phone-keeps-rebooting-even-after-odin-flash-stock-tar.3409961/ . i mean i will let it to drain battery.
[General Questions and Answers] acacacac:
Hi there. Any insights to my issue will be appreciated.

I've been running LineageOS on a Nextbit Robin for a few years, from 14 to 15 to 16 everything was great. Now in 2021, Lineage 17.1 briefly arrived and now Lineage 18.1.

My problem is new to 17.1 & 18.1, and did not occur over the past few years in earlier versions of Lineage.

After downloading and installing a 'nightly' update, the phone will boot loop and I'm unable to get it up & running again. For whatever reason the update won't 'take'.

I'm definitely no expert but I've tried a few different things and nothing seems to avoid this issue. I've always used TWRP but tried the new Lineage Recovery to see if that might help the issue. I used to use OpenGapps but as there's no Android 11 OpenGapps yet I used NikGapps when setting up Lineage 18.1.

My 'initial' set up of 17.1 and now 18.1 goes fine - I was running 18.1 for the beginning of April until today when I tried to install the weekly update.

But in my inexpert way of describing things, something in the Lineage update process seems to have broken for me in the newest versions relative to how routine it was in earlier versions over the past years.

Any advice? Thank you. What if any new habits do I need to adopt to make sure I'm able to successfully install new updates and not soft brick my phone?
[General Questions and Answers] I_like_root_pls:
I need help as my brain is melting. My blu G90 pro is bootlooped. I saw the noob friendly guide to bootloop recovery, but I can't boot my phone into recovery mode. I can only boot into fastboot mode. ADB won't connect and I am at a loss right now.

I got bootlooped after following these instructions

Copy the boot/recovery image to your device

Press the Install button in the Magisk card

If you are patching a recovery image, make sure “Recovery Mode” is checked in options.

In most cases it should already be automatically checked.

Choose “Select and Patch a File” in method, and select the stock boot/recovery image

The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img.

Copy the patched image to your PC with ADB:

adb pull /sdcard/Download/magisk_patched_[random_strings].img

Flash the patched boot/recovery image to your device.

For most devices, reboot into fastboot mode and flash with command:

fastboot flash boot /path/to/magisk_patched.img or

fastboot flash recovery /path/to/magisk_patched.img if flashing a recovery image

Reboot and voila!

I don't have a custion recovery as there isn't twrp for blu g90 pro.
[General Questions and Answers] SubwayChamp:
I never had a device updating with a single ROM for years but I think that maybe it's time to a fresh install wiping caches, dalvik and maybe formatting data, if available some kind of selected files in a form of firmware (to use it as base) and finally flashing the latest LOS available.

Regarding the Gapps these are the recommended https://wiki.lineageos.org/gapps.html
[General Questions and Answers] SubwayChamp:
Firstly to recover the ability to boot again you can go back to the latest working state by re-flashing the stock image either boot or recovery.

Most of devices actually use DM-verity, maybe you should try flashing a blank/generic vbmeta image after to flash the patched image.
[General Questions and Answers] acacacac:
Thanks for the reply.

After the fist 17 update issue there was a complete wipe of the phone and I started over, so whatever issue isn't causing updates to 'take' isn't stemming from that.

Flashing the latest LOS is straightforward enough and will get me going, but after that I still don't understand why I am having the phone soft brick when trying to update thereafter, which is my issue.
[General Questions and Answers] SubwayChamp:
I'm not sure what you mean with "Flashing the latest LOS is straightforward enough and will get me going" so TWRP will flash it anyway no matter what you did previously but a major upgrade might require a complete wipe, in this case going from LOS17 to LOS18, I mean it's not that it can cause issues only on the normal functioning or instability or battery drain or something more but the flashing process itself can be obstructed in some cases resulting in this.

As it could be that there is not instruction on how to flash this update doing that will be the most recommendable, also in case you didn't, some times you'd need to disable the zip signature verification.

Edit: Also some times after to flash the ROM you should reboot for first time to system prior to flash the Gapps, if you didn't this way and plus flashing not authorized Gapps package as it seems is the case one of them or both errors could cause the issue.
[General Questions and Answers] Droidriven:
Sounds like the short circuited cable caused damage to your phone's charging port/pins. It may be as simple as replacing the USB port component or you may have damaged something deeper.
[General Questions and Answers] Droidriven:
Seems to me that your problem may be related to your device's "rescan interval". What kind of system is your Wifi being provided by? If your Wifi is provided via a satellite dish or via a substandard service provider or network, you may be recieving intermittent internet signal, this would cause random disconnects.

Also, if your phone's service provider or network is also substandard or if you are in an area with poor signal reception such as in rural areas or low-lying areas, this would cause your phone's cellular to have connection issues.
[General Questions and Answers] Droidriven:
The only times I have encountered "APN settings are unavailable for this user" is when using a SIM card that has not been activated or has been deactivated.
[General Questions and Answers] I_like_root_pls:
How would I go about doing this? I can't find any resources, either because of my lack of experience, or there aren't any.

Please keep in mind I started learning about this stuff a week ago.
[General Questions and Answers] TheBeast941:
By treating my boot.img as a recovery.img then flashing the output to my boot partition, i managed to port TWRP to my device! However, when attempting to install Magisk (v22.0) either by flashing a patched boot.img or by flashing a zip through TWRP, Magisk seems to install while overwriting TWRP so that on the next boot there is no TWRP when rebooting to recovery. Is there any workaround to get TWRP and Magisk at the same time? I don't want to go ahead and install v22.1 since it still seems pretty new.
[General Questions and Answers] SubwayChamp:
You didn't mention yet which image you patched and flashed to gain root, either boot or recovery image I guess you got it from your stock firmware, so following with this assumption, you should flash again either the boot or recovery stock (not the patched one) to restore your device to its original state.

Regarding the second part most of devices after to attempt to root them they need to disable DM verity in order to can boot.

- Firstly re-flash as indicated previously either the recovery or the boot image.

- Reboot to system and check if USB debugging and OEM unlock options are still enabled.

- Send device to fastboot.

- From here on it should be that you simply patched the wrong image, some devices need the boot and some need the recovery image. If you flashed the other image right now and still you can't boot then..

- Download this file and place it to the same adb/fastboot folder directory to avoid an unnecessary/erroneous/misspelled/mismatched path https://mega.nz/file/dnAS3AhD#g5PnSg-0UKFvyhZSZ8Em6gKO2Do7avaUepPmsH75-Bg (In case your device doesn't require a signed vbmeta then it'll work).

- Type in fastboot (with device connected to PC)

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

in case this command doesn't work type

fastboot flash vbmeta vbmeta.img

you have to get a successful message, after that you should flash your patched image (always that is the indicated)

- Method 2 is editing with a hex editor your boot image and removing/replacing from it for 0 values all the verity flags and then patching it with Magisk to finally flash it.

- Method 3 is signing your own vbmeta image, I guess that the last 2 methods are as you said by now out of your skill.
[General Questions and Answers] SubwayChamp:
Well, this is exactly what I warned previously, your TWRP needs to be fixed in the ramdisk partition to live together so any time you flash something it is not overwritten.

You should port it from a TWRP that already was made for an A-B device (processor similarities required) the Android Ones edition are an example on how it works and additional search for a TWRP installer , look inside and see which values you should replace for those from your device to make it compatible.

This is an example of what I'm saying, from my current device https://xdaforums.com/t/recovery-unofficial-twrp-3-5-1_9-0-for-android-9-10-11-custom-roms.4123287/
[General Questions and Answers] Rizwan66:
Ok bro
[General Questions and Answers] Rizwan66:
Guys need help ...

I hve 7tpro mclaren hd1925 T mobile and i am not getting any software updates and there is no option to update it manully ...

I am still on 10.0.12

Can anyone help me with this plz...
[General Questions and Answers] Placyd:
I need help. My Huawei Y6 Pro 2019 (MRD-LX2) EMUI 9.10.0 C636E7R1P7 won't boot and tells me "Serious problems occured when the device boot, you are recommended to do factory data reset". How do I get past this without doing a factory data reset?
[General Questions and Answers] SubwayChamp:
This is the latest firmware for your device, it's based on A11 but it's a beta build https://www.oneplus.com/global/support/softwareupgrade/details?code=PM1574162297465 anyway I'm not sure if you should wait eons for TM to release its own update in case your device is locked.

Here you have the XDA Forum for your device https://xdaforums.com/c/oneplus-7t-pro-mclaren.9893/

And here the Oficial OnePlus Forum site for general discussion https://forums.oneplus.com/forums/oneplus-7tpro-support/
[General Questions and Answers] kos25k:
Hello.I have a Vorke Z6 tv box running a custom Pie rom.Only bug is that bluetooth sound is delayed about 1 second.Is it possible to make or edit something so sound will be ok?I searched also on tv boxes forums, but didnt find something..Thanks for possible help.
[General Questions and Answers] TheBeast941:
Sorry if I didn't explain this clearly, but I flashed the TWRP image to my boot partition ("fastboot boot" doesn't seem to work for me so I can't temporarily boot into TWRP, I can only flash it onto my boot partition in order to get into TWRP). so that every time I reboot to recovery, I get into TWRP recovery, not the stock recovery. However, my issue comes from when I flash the Magisk zip through my ported TWRP recovery (currently flashed onto my boot partition), where the next time I boot or reboot into recovery it just boots straight to Android (then flashing back the boot image with TWRP restores my TWRP recovery and Magisk disappears obviously)

I also tried taking my TWRP image and patching it via the in-app patcher on Magisk Manager, and when flashing the output of that (which, by expectation, should contain TWRP and Magisk) onto my boot partition I get the same issue: prescence of Magisk and absence of TWRP.
[General Questions and Answers] Pichuku:
Hi

I need a help for my mi phone

Is there any option for both always on display and floating windows work

If I turn on UI optimization AOD is not working and if I turn it off floating window is not working

What if I need both in redmi
[General Questions and Answers] SubwayChamp:
Again, this behaviour is exactly what you have to expect and it was exactly what I said you previously, firstly you can't reboot to TWRP by the commands so flashing it is required or also using the combination buttons will work, second,is normal that every time that you reboot to recovery you encounter there TWRP and not the stock so this one is just a tiny space into the boot partition and it was overwritten so it's gone, third, as I said you previously you should need to flash the boot image again into the boot partition so your device as it was overwritten by a different image lost the ability to boot it's mean that you'll boot to android because that, as for the final part Magisk can't do that.

What I were trying to say you is that if you use as base a "normal" TWRP without the ability to survive in the boot partition (as the stock recovery does) then the result can't be different though if your model is that then your copy will be that and can't be other than that.

But in the other hand if you use as base a TWRP that has the ability to do so most probably you won't need to add many more to your ported TWRP,

I hope you understand what I'm saying.

And the other step is additionally/apart of to make/port a TWRP for your device as it seems that you achieved (just check if it is the proper one) then also you should make/port a TWRP installer, what do TWRP installer does? without deeper describe it; just fix it into a tiny portion of the boot so it doesn't dissapear on every reboot. For that reason I linked to a thread so you can see that this TWRP for my current device has 2 files and not only 1.

Take a look inside the TWRP installer and maybe you can use it as base, of course is just for learning and personal use, you shoudn't share with anyone without the permission of the author.
[General Questions and Answers] SubwayChamp:
I have both working all the time (or intermittently) so not always use AOD always on.

AOD looks like if device is with screen on but not really to the way that floating windows can interact with. Floating windows feature needs a device with screen completely on, I mean when the user is interacting with some app while the AOD mode manages notifications other way.

Probably there are other ways that I personally don't know, maybe some app that can act a way of some sort of ambient display app, or with some line command/tasker, maybe some Magisk module?
[General Questions and Answers] pyereciae2788:
Quite a lot of root-related questions here... But anyway, I stopped by to ask if it's possible for android to not mark numbers as phone numbers (where it gets highlighted with the ability to call it). I've seen numbers like IDs (and some dates) get identified as a phone number. It's a bit annoying to see on any non-phone numbers.
[General Questions and Answers] Scridgeon:
Can a MOD please help me change my username?
[General Questions and Answers] DiamondJohn:
To get the MOD's attention, try the thread

[All XDA Members] Requests to Moderators and Admins

Rather than sending a PM to an individual Moderator, please feel free to ask questions in need of Moderator or Admin assistance. We will all be monitoring this thread, and someone will reply without much delay. In order to hopefully address some...

xdaforums.com

Or I would even try simply reporting one of your own posts requesting the change,