yashsingh1/xdaforums huggingface dataset:
[LG V30 Guides, News, & Discussion] HadschiH:
Anyone else having trouble with whate seems like hardcoded screen-timeout for the lock-screen ?

Even it there is user-interaction (clicking/scrolling thru notifications) it always turns off after a couple of seconds ... frigging annoying

.. .fixed.. my bad.. i had Glimpse installed . . and set the timeout at 10sec for lockscreen to override default always ... even if the lockscreen did not get activated by Glimpse...

Where is smart-stay gone? i guess it was still implemented in Android 7?

Always-On Display randomizes the postion of the content only every time it restarts ... but once it is on it looks like it (notification/watch) stays the same position .. this is not optimal it should change position every few minutes ... no matter what the brightness is set

>> update: actually it moves 1px to the side every other minute or so (put some stick-it-notes on the screen then wait long enough) ...not sure if it moves back-and-forth .. if you have a full battery there are still a lot of white px which might get overused

Also i dont like the way fingerprint-unlock works: you dont even have to physically press the button FIRST .. often it gets your fingerprint while handling the device and then unlocks the device ... on the V10 you always have to press the button first .. THEN it scanned the finger and on hit it unlocked ...

lots of BS if you ask me .. dunno if google or lg is to blamme ...
[LG V30 Guides, News, & Discussion] Anonshe:
It's good that just touching the sensor unlocks the phone just like it is on almost all phones nowadays. The trade off is worth it.
[LG V30 Guides, News, & Discussion] HadschiH:
there is always a tradeoff between Convenience and Security .. i'd prefer to have physically PRESS the button first .. not just getting near it ...

but it helps that volume-buttons are now on the sides instead of around the FP/Button

*_*
[LG V30 Guides, News, & Discussion] ChazzMatt:
Yeah, the writer is either totally ignorant of corporate PR speak ("Q1" never means the beginning of the quarter, especially the first day) or he willfully misinterpreted for click-bait. When Microsoft would say "H1" (first half) of next year, it was always the last week in June. :p They would never say "June, but practically July" -- they would say H1 on purpose, because technically it could be January of 20xx (so it wouldn't sound so far away). But it never was.
[LG V30 Guides, News, & Discussion] lev04:
sadly i think i will sell my v30 and buy a new mi8. LG is just **** with updates. since april when i bought my v30, i got only 2 or 3 security updates besides the oreo update. and now only the g7, and only in korea, will see android 9 somewhere in q1, as for the rest of the handsets, god knows if and when. unacceptable totally unacceptable, mi8 has already android 9 and a few other updates, 2 or 3.lg could learn something from xiaomi.
[LG V30 Guides, News, & Discussion] amdultra:
The only i want on pie is the nav gesture
[Magisk] zohair_:
Hello,

I have a px5 head unit.

I was trying to get root access on this unit, the kignoroot or whatever its name was didn't work. Using recovery.img which I exteracted from a working update.img, I preformed offline patch using Magisk. Magisk recognized the recovery.img and patched it. When I flashed the image my recovery is gone. There is black screen instead. I know it is working and the options are there.. but I can't see them to be able to use them.

With recovery gone, thanks to Magisk, I think the only hope now is to be able to use adb to restore recovery partition, try booting from sd card, or be able to access the bootloader to flash recovery partition.

so far I tried the commands:

setprop persist.adb.tcp.port 5555

setprop sys.rkadb.root 1

but when I try to connect I get "device unauthorized"!

I am unable to update the unit anymore..!

thanks for your help.
[Magisk] Crescendo Xenomorph:
why the heck you patch the recovery.img in the first place?

the manual patch is only got boot.img aka kernel, not recovery.

this is clearly your fault!

no need to thanks Magisk for destroying your recovery, you destroyed it yourself.
[Magisk] RuralRoots:
Well, about all I can say as a noob is READ, READ, READ. Everything you need is pretty well right here if you take the time to investigate your options. Nobody is going to hold your hand if you choose to follow through. Trashing the developer for your error isn't going to win you any friends either.

I came here some time ago looking for a way in to an SM-J320W a friend had picked up at an auction and I've probably spent close to 70+ hours reading about the various exploits, anomolies, file structures, device security, risks, and potential operational impacts, and indeed the distinct possibility I could even brick the device.

Like you I tried KingoRoot, Kingroot, and SU as relatively easy and benign attacks to no avail.

That led to longer investigation of more intensive attempts like CF-Auto-Root, Magisk, Rooted Boot Images, Custom Recovery ....

Right now I am looking at my Magisk App screen with 4 green checkmarks and a pass by Root Checker. ROOTED! :D

So, for all the other noobs out there:

Do your RESEARCH

Evaluate your OPTIONS

Understand the potential RISKS

Proceed only if you are PREPARED FOR THE CONSEQUENCES

It ain't rocket science, but it is science and you need to understand what you're doing.
[Magisk] zohair_:
Thanks for your responses. I would like to agree with your that it was my fault but can you explain how did Magisk was able to:

1. Unpack the recovery. Img

2. Recognize that the file was in the correct arm64 processor format and the correct one to patch.

3. Patch the file it recognized and unpacked.

4. Made a backup copy of the file before patching it.

5. Repacked the file.

6. Produce a log file affirming that the patching process was Successful!

All of this while it was the wrong file in the first place? It is hard to believe that it was my fault because recovery. Img was the only file accepted by Magisk. I tried all the other firmware files like boot. Img and kernel. Img and others, the only file that was accepted and recognized by Magisk was recovery. Img. Between us Magisk was not able to determine that the file it already patched was actually patched, no matter how many times you repatch that file.

Sorry to prove you wrong sir...!
[Magisk] Didgeridoohan:
I'm going to assume that your device is simply too far removed from a vanilla Android experience for it to be compatible with Magisk. The fact that it recognised and patched the recovery.img when Magisk is designed to alter the boot.img is a big hint... It would have been interesting to see the log from when you patched the file.
[Magisk] J_M_V_S:
Even if the software trashes your whole system, it comes "as is", meaning that you get all the features and all possible bugs too without any kind of warranty. Nobody forced you to install it, so is the user's responsability to take all necessary steps to be able to recover the system to their prior state or assuming the risks involved in not doing so.

What you should and can do is provide as much information about your hardware and software so you may help others in the same situation and maybe make the developer take a look at it.

Understand that with that kind of attitude will not get you far here. As mentioned by others, educate yourself properly before taking any action that might brick your device, if something goes wrong is your sole responsability, but there are a lot of people here willing to help if you treat them with respect.
[Magisk] zohair_:
contents of the log file (magisk_install_log_20181204_054200.log) :

- Copying image to cache

- Device platform: arm64-v8a

- Existing zip found

- Extracting files

- Unpacking boot image

MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/data/user/0/com.topjohnwu.magisk/install/boot.img]

KERNEL [15104080]

RAMDISK [20858336]

SECOND [0]

EXTRA [0]

PAGESIZE [16384]

NAME []

CMDLINE []

CHECKSUM [7415a67292764b19e4067d67731d81ecc63a557b]

KERNEL_FMT [raw]

RAMDISK_FMT [gzip]

- Checking ramdisk status

MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool

Loading cpio: [ramdisk.cpio]

- Stock boot image detected

- Backing up stock boot image

MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool

Compressing to [stock_boot_334712fd9ff58aa61ae0734b157fc1261e8a616f.img.gz]

- Patching ramdisk

MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool

Loading cpio: [ramdisk.cpio]

Add entry [init] (0750)

Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[false]

Remove pattern [,verify]

Remove pattern [,verify]

Save SHA1: [334712fd9ff58aa61ae0734b157fc1261e8a616f] -> [.backup/.sha1]

Loading cpio: [ramdisk.cpio.orig]

Backup mismatch entry: [fstab.rk30board.bootmode.emmc] -> [.backup/fstab.rk30board.bootmode.emmc]

Backup mismatch entry: [fstab.rk30board.bootmode.unknown] -> [.backup/fstab.rk30board.bootmode.unknown]

Backup mismatch entry: [init] -> [.backup/init]

Dump cpio: [ramdisk.cpio]

MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool

MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool

MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool

MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool

Patch @ 00CA4257 [736B69705F696E697472616D6673]->[77616E745F696E697472616D6673]

- Repacking boot image

MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/data/user/0/com.topjohnwu.magisk/install/boot.img]

KERNEL [15104080]

RAMDISK [20858336]

SECOND [0]

EXTRA [0]

PAGESIZE [16384]

NAME []

CMDLINE []

CHECKSUM [7415a67292764b19e4067d67731d81ecc63a557b]

KERNEL_FMT [raw]

RAMDISK_FMT [gzip]

Repack to boot image: [new-boot.img]

KERNEL [15104080]

RAMDISK [21090778]

SECOND [0]

EXTRA [0]

PAGESIZE [16384]

NAME []

CMDLINE []

CHECKSUM [f8b4e9f25b0c488e9a96a66263730d46737766b8]

MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool

Cleaning up...

****************************

Patched image is placed in

/storage/emulated/0/Download/patched_boot.img

****************************

- All done!

EOF

=========================================

The Name of the firmware file is update. Img extracted from kgl_px5_6.0(20171102).rar (the link to download this file is posted somewhere here on the forum)

Version of Magisk: 5. 9.1

I think a reproduction of the same log is possible using the recovery. Img extracted from that firmware.
[Magisk] zohair_:
Why do I have this feeling that I am the one who is being treated with disrespect here..?
[Magisk] J_M_V_S:
Device details? Android version? Are you using Magisk 17.1 for some particular reason? (At the time of this post, Magisk 18.0 was the latest stable release). You should also attach or link boot.img that you're trying to patch (saying is "somewhere in the forum" is not really helpful).
[Magisk] Crescendo Xenomorph:
First: You blamed Magisk for what's clearly your fault.

Second: Of course Magisk will be able to patch stock recovery.img since it's essentially a SECONDARY OS in your phone albeit minimal, to recover your phone to working state.

It got it's own kernel and such, like an almost complete OS. Of course Magisk will be able to patch it & recognized it as a correct file to patch (it got untouched kernel which is compatible in it).

But if you patch it, you'll get what you get now: broken recovery, since it's not designed to patch recovery and no one crazy enough to attempt to patch a recovery with Magisk.

So, about disrespect: research before blaming. As anyone says: no one forced you to use Magisk. It's free & power come with great responsibility.

Magisk will give you degree of freedom to tinker with your phone, like root & xposed. But if you use them wrong, well, don't blame it if your phone's broken.

Just flash your phone with complete stock firmware and start over. ;)

No hard feeling.
[Magisk] zohair_:
The device is a rockchip sdk3026. This head unit is popular on your forum as px5.

Android version is 6 Marshmallow.

I wasn't using Magisk 17.1 directly, I was using Magisk GUI and the "Boot Image Modification Tool" version 17.1 was used by the main program.

I downloaded the firmware from here. I cannot access that link anymore.

I will provide you with an ftp link soon where you can down load all the needed files.

Thanks for tying to help.
[Magisk] zohair_:
1.

2.

3. no comment...!
[Magisk] Crescendo Xenomorph:
head here: https://xdaforums.com/android-auto/...eneral/mtcd-px5-headunits-repository-t3619906

there's a link for the firmware you need.

as for the instruction of how to flash it, better search in those subforum as I don't have the head unit myself.

as for root info: https://xdaforums.com/android-auto/mtcd-software-development/root-oreo-t3779605

you're welcome ;)
[Magisk] freddie.here:
Hi, for the J320W, did you root it at 7.1 ? If so, do you mind sharing the steps ? I only found one rooting approach but only for 6.0.1 . Many thanks in advance !
[Samsung Galaxy S8 Questions and Answers] mmerlin10:
I have been using Nexus phones for years with custom ROMs that have option to enable arrow keys on the left/right border of the Navbar. This is super adictive feature to move cursor back/forth. Is there any way to get those on S8? I checked numerous apps for customizing the Navbar but didn't find any that could do this. Some keyboards have option to show arrow keys (e.g. Smart Keyboard Pro that I use) but it is not elegant as it takes space vs. the option in Navbar that is sumply so cool... I am not yet ready to move away from stock ROM on my new S8 - maybe once Lingeage will get stable :)
[Samsung Galaxy S8 Questions and Answers] mmerlin10:
So, after some more search I found a great solution - Custom Navigation Bar app (https://xdaforums.com/android/apps-games/app-custom-navigation-bar-customize-t3590967) that works exactly like I want. I can add the left/right arrows. i am using the following settings:

- Type: Keycode

- Keycode: Dpad Left / Right

- Icon: Chevron left / right

Hope it helps to somebody :)
[LineageOS Questions & Answers] chaz572:
I'd like to install Lineage 15.1 on a Nexus 6 (shamu platform) with encryption. I did what seemed straightforward, and got encryption going. It now requests my 4x4 pattern on boot.

But TWRP can't decrypt the phone. I figured maybe it was 4x4 pattern support, so I rebooted and changed my disk encryption password to a password. Lineage now requests my password on boot, and then boots fine. TWRP requests a password and doesn't decrypt.

So I do some googling and find out that LOS 15.1 now uses file-based encryption (FBE), and there isn't enough room on the shamu recovery partition for a TWRP that supports FBE. Is that still the case? I'm running TWRP 3.2.3-0. Does shamu TWRP 3.2.3-0 still not include FBE support due to space considerations?

Fine, more than one way to solve this. I don't mind re-installing the phone and starting from scratch. Is there a way to fresh-install Lineage 15.1 on a shamu, and tell it specifically to use full-disk encryption (FDE), and not FBE, so that TWRP will be compatible with the phone's encryption?

Could someone either post or point me to a little writeup on how to do this? Thanks so much!
[LineageOS Questions & Answers] Ibuprophen:
I don't have this device but, your best bet is to post this question within the following Official TWRP thread that's specific to your device for support and guidance.

https://xdaforums.com/showthread.php?t=2946534

If necessary, you can always try to obtain some member guidance within the following Q&A thread that's specific to your device and variants if you are unable to obtain any support from the above thread.

https://xdaforums.com/showthread.php?t=3068327

Good Luck!

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
[HTC Excalibur] qaplus:
At the bottom of Dash there's a small hole next to the mini-usb. What is that for?
[HTC Excalibur] papamopps:
maybe the microfon??
[HTC Excalibur] Mikey:
Could be used for headphones
[HTC Excalibur] Bupahs:
Its for attaching a lanyard. If you open the battery cover you can see the "loop".
[HTC Excalibur] c_shekhar:
For allowing the phone to breath properly...;)
[HTC Excalibur] outerdepth:
It's what Mikey said. It's for a special set of headphones. I think it's for a headset with Microphone. ;)
[HTC Excalibur] Yianaki:
:eek:

You people are FOOLS it isn't a lanyard. It is for hello kitty phone charms!

It serves no useful purpose whatsoever, except to help make your Windows Mobile Smartphone the cutest thing evar!

Hello Kitty Forevar!
[HTC Excalibur] Mikey:
lol...you actually spent time and looked for that? I know you did lol
[HTC Excalibur] tennisshoeninja:
LMAO its really a reset buttom POKE IT!
[HTC Excalibur] cswroe:
I try to refrain from poking suspicious holes......
[HTC Excalibur] outerdepth:
You never know what kind of trouble that could land you in...
[HTC Excalibur] Rip Syntaxx:
Amen to that.
[HTC Excalibur] port2600:
Dumping Outlet

That is where your HTC craps from
[HTC Excalibur] ayyu3m:
**** hole?
[HTC Excalibur] Mikey:
it also known as the "NO NO Hole" by certain women :)
[HTC Excalibur] pfunkside:
poop shoot :eek:
[HTC Excalibur] Joe USer:
I have a lanyard attached to mine, the problem is that the phone is too large and heavy for a neck lanyard for any decent amount of time.
[HTC Excalibur] superminipoo:
I like to poke holes.

the square hole is nothing. i looked at it.
[HTC Excalibur] egosumpaul:
Holly crap! I´ve been trying 6 months to attach a parabolic antenna to that hole... LOL!

I agree that the phone is pretty heavy for a lanyard, I used one once and the result was a hurting neck.:p
[HTC Excalibur] Joe USer:
I have a retractable belt lanyard that works well. But you need cargo pants for something like the dash to fit in without getting squeezed.
[Xiaomi Redmi Note 5 Pro Questions & Answers] LinkRibe:
I have a Redmi note 5 (whyred) arb4 with stock MIUI

Bootloader unlocked, TWRP recovery and magisk installed

The magisk module does nothing, I have it activated but it does nothing, the only way i've found to enable the gcam is flashing through recovery but it gets disabled on the next reboot.
[Xiaomi Redmi Note 5 Pro Questions & Answers] 5460:
Magsik module enabling Camera2 API is not working for me either. While other modules work.

I can enable it by flashing in recovery (OrangeFox), and after a reboot, it still works. Quite strange.
[Nexus 5X Q&A, Help & Troubleshooting] nitsi:
I looked through many threads, posts, websites, and tutorials, but none of them say how to literally wipe my device completely (it could be that it's not possible), what I want to do is completely remove literally everything so that it's like a brand new hard drive without even any files in it.

'Factory Reset' doesn't remove everything because android still boots after a factory reset and android wouldn't be able to boot if there were no files on the device. TWRP doesn't remove everything either because how is twrp running, and I can still see the androids root directories in twrps file manager (TWRP does tell me that there's no OS installed, but then why is there still a functioning file system with actual files in them).

I want to completely wipe everything so that any future roms I download will have no way to be affected by any old kernels/roms/apps that I have installed in the past. I want to clean install android on top of a literally empty phone hard drive. If this isn't possible then what's the closest to that that I can get? Cuz I tried various roms and I had bugs that persisted between multiple roms even though other people said that they didn't have these issues.

In case you're wondering: I'm currently running LineageOS 15.1, oreo 8.1
[Nexus 5X Q&A, Help & Troubleshooting] Xeust:
Your best bet it to wipe using stock image. Reinstall TWRP and wipe system, cache and data before installing new ROM
[Nexus 5X Q&A, Help & Troubleshooting] peterpv:
I agree with the advice given by Vanschtezla.

Also, if you would completely wipe all data on the phone's storage then that would also wipe the partition table. The storage area is divided into partitions which are mounted to for example /system /data and /cache when your phone boots.

Also there is no real need to "wipe everything" as you say as that could brick your phone. If you just boot TWRP and wipe using "Factory reset" and additionally: System then everything should be clean enough to install a new ROM. Depending on the ROM it will wipe the System partition anyway.

Kernels reside in the system partition so when you wipe System, any Kernel is gone

Pre installed (system) Apps sit in the System partition so wipe System and they are gone

User Apps sit in the data partition so wipe data (that is included in the Factory reset) and they're gone

All in all I think you're expecting issues that simply do not exist. Especially if you just follow the instructions of the (custom) ROM you want to install.
[Nexus 5X Q&A, Help & Troubleshooting] nitsi:
THANK YOU!

This is exactly what I was looking for! Why don't any "How to wipe your phone" guides say these things (even the ones that get more technical don't mention what exactly gets deleted for each wipe option, which is why from your perspective it was probably very weird to read my question).
[Xiaomi Mi A2 Lite Questions & Answers] LionHeart90:
Hello everyone, a couple of months now are also thanks to you in the world of modding. Yesterday (i have a Xiaomi Mi A2 Lite) during the installation of a custom ROM using ADB, typing in the fastboot command "erase system", I wrote erase a_boot for error because before I was reading a post about it and I wrote it. Yes I know, I was too stupid. Result? The phone does not start up either in recovery or in fastboot mode, and from the PC it is recognized as COM port. I have already documented about it and tried to flash everything with the Qualcomm tool after installing the drivers but nothing. I tried the EDL by activating it manually to unlock port 9008, but still during the flash gives me error. I tried everything, do it all over again in a newly formatted and clean PC from any other driver, but nothing. During the flash, even if I put the firmware in the same directory, it still gives me error. Guys I'm desperate please. I do not know what else to do. I hope to receive your answers
[Xiaomi Mi A2 Lite Questions & Answers] Kineceleran:
Try to flash stock rom with Mi Flash "64-bit"

Here is a link for 64 bit version: https://yadi.sk/d/cel5Nm2sE1OpMg

In EDL mode
[Xiaomi Mi A2 Lite Questions & Answers] Pierre_C:
Hello,

If you use Windows write it in CMD in Adminastrator,

bcdedit /set testsigning off

After that try flash via MiFlash a stock rom. IMPORTANT, Select clean all only.

If this not work use a Deep Flash Cable,

- Shutdown your phone

- Connect the usb cable to your computer

- Start pressing the button

- Wait 10 seconds

- Connect the cable to your phone

- Wait 5 seconds

- Stop pressing the button

Normaly the led flash, You are in EDL mode

Flash a stock rom via MiFlash with clean all option.

To leave EDL mode you need to press on power button 20 seconds.

PS: Soory for my very bad English

Pierre