yashsingh1/xdaforums huggingface dataset:
[Sprint LG G6 Questions & Answers] umlguy:
I'm in a similar situation, did you ever solve your problem? At this point I'd just like to get back to booting the original Sprint LS993 8.0 ROM. I had previously flashed the H873 8.0 ROM on top of the LS993 with the model fake I found elsewhere (which I can't seem to find now). I just tried loading the US997 9.0 ROM just today as well and it was asking for an unlock.bin file which I don't have ... cause the LS993 AND the H873 are not supported for unlocking by LG. Now the phone seems to be permanently stuck in Fastboot after what seemed like a successful flash of US997 using LGUP. No button combinations will make it do anything else, though having said that it will act like it will do a factory erase with vol-down and power-down quick power-up then down again. I think I may have bricked the thing, hate that. I'm hoping you or someone else has figured out a fix. Thanks.

If I've really bricked it just tell me that so I can throw it out and not worry about it any longer.
[Sprint LG G6 Questions & Answers] patato21:
I only solved this problem on a different phone (LG V30). The US998 Pie update and the VS996 Pie update seemed to brick phones at the LG V30 screen or on the Boot Animation screen. This seemed to be only and issue with phones that have been crossflashed in the past. I only solved this by creating a partition backup .SRF (in Qualcomm 9008 QDLoader mode) with Octoplus JTAG tool from a working Sprint LS998 -> US998 Pie Crosssflash. I then flashed that backup onto the faulty bootlooping phones and this fixed the issue. Flashing several KDZs and even flashing zips did not help here, it seems we need to rebuild or copy the partition table from a working device.

The issue now is how to enter the Qualcomm 9008 mode, as there doesn't seem to be a power button shuffling method to enter it on older SDM821 chips. The only way would be to buy a USB cable that shorts the device, manually open the device and try to short it, or flash a bad partition like abl or tz from T-Mobile firmware which will brick the phone into 9008 mode. We need a genuine factory US997 for donor firmware, and a recipient H871, H873, or LS993.

At this point, it seems to cumbersome to even try this, as LG has left behind the US997 and there is no Pie update in sight for it.
[Sprint LG G6 Questions & Answers] umlguy:
OK, thanks anyway ... lesson learned.
[LG V20 Questions & Answers] puzzimassa:
Is there a way to add kcal support to the stock rom of lineage 15.1? I'm using the second screen version, from this

https://xdaforums.com/v20/development/rom-unofficial-lineageos-15-1-lg-v20-t3775689

and even though it is stable enough to use, I can't use gamma kernel or else the second screen won't work. I can live with a tad of screen retention but I'm worried about permanent damage, if it gets too bad I'll just go back to the other stable version of lineage 15.1 but if anyone can help them please let me know. Thank you
[LG V20 Questions & Answers] SJMarty:
I'm reasonably sure this isn't specific to the V20 but thought I'd start here.

I have a rooted H918. Some/most of the time when installing apps or updates, there is a long pause between the period of time that the download completes (reaches 100%) and when the app/update starts to install. I found a thread or two describing the same issue. The "solution" was to exit the Play Store application, close it, and then relaunch it. After relaunching, the app that was at 100% downloaded will then start to install. However, if there are several installs or updates queued, I have to do the same steps for each app. So, not much of a solution.

I've cleared the app cache, reverted to the base version of the Play Store and then updated to the latest version from APK Mirror. Same behavior continues. The strange thing is that it does not do this all of the time. Sometimes, things download and install right away.

Anyone else observe this behavior? Any suggestions of what to try?
[LG V20 Questions & Answers] crimsonrommer:
Set your cpu governor to performance

---------- Post added at 04:47 AM ---------- Previous post was at 04:46 AM ----------

This is a performance issue, if your cpu is being used too much, it will have a delay
[LG V20 Questions & Answers] SJMarty:
Is there a kernel editor you recommend?
[LG V20 Questions & Answers] crimsonrommer:
i prefer kernel auditor, its much more simpler to use
[LG V20 Questions & Answers] Billy Madison:
Guys, you're like Don Quixote, fighting a windmills that do no harm. Just leave the Playmarket aside and it'll install apps.

You know that after a apk file is downloaded it begins to be compiled by ART/Dalvik, right? That causes the delay after apk is downloaded and begins to be installed. The process which does it is called dex2oat. When I install many apps that dex2oat runs high in battery statistics with 3-4% of battery. When apps are being compiled this process takes both much time AND battery. So, this cause a delay and you're fighting that what can't be fought. And if an app is huge like Chrome compiling takes much more time than if an app is tiny like some sort of Jota+ text editor hence different time between "Sometimes, things download and install right away"

Also, try to update apps when on charge since you loose 10%, 20% or more battery if install many apps in one try, hence you'll got "bad battery life"
[LG V20 Questions & Answers] SJMarty:
The delay that I am seeing is significant. If I just leave the phone alone, it can be as long as 10-15 minutes between the time that the download completes and the app starts to install.

I should clarify that when I say there is a delay, there is a delay after every app install. For example, if I have five apps that need updates and I update all, there will be a long delay between each one of them completing the download and actually starting the install process. However, sometimes, I may have five apps that need updates and they will all install with no delays.

I'm having no problems with battery life.

I went ahead and adjusted the CPU governor to "Performance" and noticed no difference in the behavior. I enabled the CPU monitoring in Developer Options and there is no spiking after the download is complete so I don't believe the compiling process is responsible for the delay.

What prompted me to post my question was that I have two V20s (mine and the wife's) and her phone is not doing this. Both are rooted and running the same ROM (10t).

I'm open to any other ideas...
[LG V20 Questions & Answers] Billy Madison:
Then I can only suggest you tweaked your phone somehow and those tweaks caused a delay. Of course 10-15 mins doesn't attend to compiling, I thought you meant like 15 sec a delay

Wipe to factory state your phone and see after that when and after what tweaks you'll get delays back
[Google Pixel 2 XL Questions & Answers] greysonofusa:
Phone: Pixel 2 XL

Software: 9.0 Pie Stock Unrooted Unmodified also didn't work in 8.0 or 8.1.

Car: 2018 Subaru WRX

Cable: tried 2 off brand USB type a to type c cables.

Connection methods attempted: PTP and File Transfer (MTP)

Any ideas?
[Sony Xperia XZ1 Compact Questions & Answers] 66LUX:
Hi all,

I have an XZ1 compact (Model G8441 non-root) that I'm very happy with, but I can't get it to charge wirelessly.

I bought an adapter with a USB-C plug and it worked to charge the phone at first, but it suddenly stopped working after a few charges.

I figured I had a fault with either the wireless receiver that plugs into the phone or the charger pad.

I tested the receiver via a micro-USB adapter on my old Z5 compact and it charges fine. I also bought another charger pad, and it also won't work on this phone.

When the phone is on the charger pad, the indicator on the pad recognises that something is there and goes from green to blinking red as if charging, but nothing happens on the phone.

If the phone is completely switched off, all I get is a blinking green LED on the phone.

I've tried it with the case on and off.

There have been three updates since I got the phone a few weeks ago. Is it possible that an Oreo software update has broken the low power charging somehow?

Obviously I've rebooted the phone, but I haven't done a factory reset.

I'd appreciate any help you could offer.
[Sony Xperia XZ1 Compact Questions & Answers] moofesr:
You could indeed try downgrading the phone to determine if it's a firmware/software issue or a hardware issue.
[Sony Xperia XZ1 Compact Questions & Answers] Averix:
I'm confused. The XZ1 Compact doesn't have wireless charging. What did you buy to wirelessly charge it? Something that plugs into the USB port and then sits on a wireless charger?
[Sony Xperia XZ1 Compact Questions & Answers] 66LUX:
Yes, I bought a wireless adapter with a USB-C plug that connects to the phone & lays against the back of the phone inside the case. You then place it on a wireless charging pad.

I've done the same thing with several other phones & never had a problem.
[Sony Xperia XZ1 Compact Questions & Answers] mhaha:
Didn't see it explicitly mentioned, did you try using a different USB-C adapter cable? Since the micro USB cable works, we can safely assume the pad's fine. But I didn't see you cross test another type c cable.
[Sony Xperia XZ1 Compact Questions & Answers] 66LUX:
Solved

Hi all,

I managed to fix the problem by replacing the QI receiver attached to the phone with a new one.

Strange that the old one worked if I connected it to a different phone via an adapter (and that it worked to begin with on my phone).

It must have had a problem where it couldn't output enough voltage to charge my new phone, but had enough to charge the old one.

Thanks for your help.
[Sony Xperia XZ1 Compact Questions & Answers] 66LUX:
What I had changed was the charger pad. I tried two different ones, a USB-C powered one and a micro USB powered one. Neither worked.

I have a new QI receiver on order.
[Xiaomi Redmi Note 4 Themes, Apps, and Mods] Akibtech:
Use this camera apk to get ai portrait on both front and back camera.
[Xiaomi Redmi Note 4 Themes, Apps, and Mods] coolpixs4:
please, can you give some images example between miui9 camera vs miui10 AI camera ? to judge the improvement or different of them

thanks
[Xiaomi Redmi Note 4 Themes, Apps, and Mods] Akibtech:
I will try but i can say in my experience picture quality is poor then miui9 but they will improve it future as now it support portrait we should compromise
[Xiaomi Redmi Note 4 Themes, Apps, and Mods] Shiwam.vish:
Not working
[LeEco Le Max 2 Questions & Answers] DrukDroid:
I have had a Leeco Le Max 2 for like one year and it worked just fine. But recently, i've been having some serious issues while charging. The notification LED turns on and off when i plug the cable, and after some hours it charges nothing. I tried a lot of cables, but nothing worked. Im running the oreo AICP ROM right now, i dont know if that may influence.

Please help!!!
[LeEco Le Max 2 Questions & Answers] Maxelpulpo:
Hi,

Did you try to charge it on recovery mode ?

Regards,

Max.
[Google Pixel 2 XL Guides, News, & Discussion] newyesor:
Via Magisk Manager:

This method does not need root, and also does not require a custom recovery.

However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode

REQUIREMENTS -

1 - Setup adb and fastboot on your PC.

2- Stock boot image (boot.img) of your device (extract file from factory image android P)

3 - Last Magisk Manager (v 5.8.3)

4 - Active Internet connection

5 - Active mind and patience.

6 - Devices must is unlock bl.

This Boot-Image is for boot android P PPR1.180610.009:

https://drive.google.com/open?id=166pE9aMk-jqns3JM74enFhsaDY6-c3yJ

Magisk Manager

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

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

Step 1: Patching the stock boot.img

1- Copy the stock boot.img of your device to your phone's internal storage.

2- Install the latest Magisk Manager

3- Launch Magisk Manager app

4- If prompted to install Magisk, select NO THANKS

5- If you're planning to flash the patched boot image,For normal users leave it as the default .img

6-Press Setting>Update Channel>Beta

7- Press Install > Install > Patch Boot Image File, and select your stock boot image file

Navigate to the location of the stock boot.img you copied earlier on, then Select it

8- Magisk Manager should begin downloading the magisk zip file used for patching

9- Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img

Step 2: Flashing the patched boot.img

1- Copy the patched_boot.img from your phone's internal storage to folder adb or platform-tools on PC (directory>SDcard/MagiskManager/patched_boot.img)

2- You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below

How to Flash patched_boot.img using Fastboot

1- Setup adb and fastboot on your PC.

2- Unlock the phone's Bootloader (if its not unlocked)

3-Re-enable USB debugging on the phone

4- Connect the phone to the PC via USB cord

5- Boot into fastboot mode.

code

-adb reboot bootloader

6- Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -

Quote:

Code:

fastboot devices

fastboot flash boot patched_boot.img

fastboot reboot

-Verify root using Root Checker

Try at your own Risk

CREDITS

[MENTION=4470081]topjohnwu[/MENTION] (Magisk)
[Google Pixel 2 XL Guides, News, & Discussion] reawo:
Sadly goes into a bootloop for me - no idea why though
[Google Pixel 2 XL Guides, News, & Discussion] Larzzzz82:
This worked for me. I had magisk installed and took the pie update. No more root. D/l the factory image and extracted the boot image to the files folder...pissmeoff they changed the name of the icon... and magisk patched the image and saved it in its folder. Found the file, moved it to the laptop then flashed it.
[Google Pixel 2 XL Guides, News, & Discussion] newyesor:
I think you made a mistake.
[Google Pixel 2 XL Guides, News, & Discussion] reawo:
I always did that method pre Pie and it always worked but now I end up in a bootloop and I did everything according to guide
[Google Pixel 2 XL Guides, News, & Discussion] newyesor:
I think you use my file(boot.img) for patch_boot.img from magisk manager.

I think you must check your build number devices.

You must use file boot.img from your factory image for root.

9.0.0 (PPR1.180610.009, Aug 2018)	>This is version for my devices

9.0.0 (PPR1.180610.011, Aug 2018, Telstra) >?
[Google Pixel 2 XL Guides, News, & Discussion] reawo:
hey mate thanks for the input, I got a normal non testra (whatever that is) taimen - tried your boot.img and before that I tried the one from the factory image, both result in a boot loop.

I went through all stages of the Android p beta and in the end, to try solve this, I also non wipe flashed the factory image all to get the same result

could you sent me a drive Link to the patched version of yours or something?
[Google Pixel 2 XL Guides, News, & Discussion] newyesor:
This is file patch_boot.img from my devices.

https://drive.google.com/open?id=1nVEpoGam-VY1YT3GBbG6HNfhnT2NqRin
[Google Pixel 2 XL Guides, News, & Discussion] reawo:
Also doesnt work, i thought so - didnt do anything different than when it worked - no idea why it doesn't though

Is there a way to see or read out any protocols regarding this?
[Google Pixel 2 XL Guides, News, & Discussion] Superschmiddi:
I receive also a bootloop and I didnt make any mistake. I also used this method pre Pie, I read that alot of users have problems with rooting Pie atm, even with TWRP
[Google Pixel 2 XL Guides, News, & Discussion] newyesor:
You use adb last version for flash patch_boot.img ?

I think you should flash factory image new again and factory reset your devices.

You are use stock kernel or other kernel on your devices.
[Google Pixel 2 XL Guides, News, & Discussion] reawo:
I downloaded all the latest adb and fastboot. Never touched kernel or did custom recovery, always used the magisk method since i am on a pixel device. i also got the issue that my pc doesnt recognize my pixel from time to time, you think i should do a complete wipe?
[Google Pixel 2 XL Guides, News, & Discussion] newyesor:
I don't sure.

You are use platfrom-tool from sdk lastversion?(for flash via fastboot mode)
[Google Pixel 2 XL Guides, News, & Discussion] newyesor:
[MENTION=4873761]reawo[/MENTION]

I think you should flash factory image new again and factory reset your devices.

Step 1: Patching the stock boot.img

1- Copy the stock boot.img of your device to your phone's internal storage.

2- Install the latest Magisk Manager

3- Launch Magisk Manager app

4- If prompted to install Magisk, select NO THANKS

5- If you're planning to flash the patched boot image,For normal users leave it as the default .img

6-Press Setting>Update Channel>Beta ,and close this app.****

7- Open app again and Press Install > Install > Patch Boot Image File, and select your stock boot image file

Navigate to the location of the stock boot.img you copied earlier on, then Select it

8- Magisk Manager should begin downloading the magisk zip file used for patching (This process is not failed)***

9- Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img

Step 2: Flashing the patched boot.img

1- Copy the patched_boot.img from your phone's internal storage to folder adb or platform-tools on PC (directory>SDcard/MagiskManager/patched_boot.img)

2- You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below

How to Flash patched_boot.img using Fastboot

1- Setup adb and fastboot on your PC.

2- Unlock the phone's Bootloader (if its not unlocked)

3-Re-enable USB debugging on the phone

4- Connect the phone to the PC via USB cord

5- Boot into fastboot mode.

code

-adb reboot bootloader

6- Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -

Quote:

Code:

fastboot devices

fastboot flash boot patched_boot.img

fastboot reboot

-Verify root using Root Checker

Try at your own Risk
[Google Pixel 2 XL Guides, News, & Discussion] sabi95190:
Will work on the verizon variant (bootloader locked)?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Nope. If it were that easy for bootloader locked Verizon phones, it would have been done months ago.
[Google Pixel 2 XL Guides, News, & Discussion] DarkSilentSC:
What happens if you lock the bootloader after all of this?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You'll wipe the phone, lose root, and be stock.
[Google Pixel 2 XL Guides, News, & Discussion] TonikJDK:
When still rooted and modified? You might very well brick it. Relocking while modified is borderline insanity.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
"Borderline"???? More like certifiably insane! ?
[Google Pixel 2 XL Guides, News, & Discussion] Tonyfeng:
newyesor, thank you for your method.

But after I did magisk root according your steps, which the phone indeed root successfully, it doesn't work properly. First ,the battery drains very fast( when I restart the phone the battery would run normally for several hours, but not for long), and one day I restart my phone, it won't boot！The phone starts rebooting again and again. So I made the phone into bootloader and made a factory reset.

Is there a bug in this magisk root for android pie?
[Google Pixel 2 XL Guides, News, & Discussion] cosceola9401:
Can anyone else confirm this works? I will be attempting tonight. I'm currently on the latest (009) Android Pie image. I bought the pixel 2 xl from Google specifically to be able to root but have not found a working method yet for the 9.0 update
[Google Pixel 2 XL Guides, News, & Discussion] soloxp:
I'm I missing sometime here!

unlock your bootloader

unlock_critical

To root Android Pie just install Magisk manager 5.8.3, boot into your Bootloader then temp flash TWRP and flash Magisk.zip and reboot.
[Google Pixel 2 XL Guides, News, & Discussion] TonikJDK:
You are doing something wrong, no offense intended at all just getting to the point. P roots exactly the same as as 8.x did.

Make sure you have the beta Magisk version.

Reboot into bootloader mode.

Fastboot boot TWRP.

Flash the Magisk zip in twrp.

That is how I do it, although the method in this thread works also.
[Google Pixel 2 XL Guides, News, & Discussion] reawo:
RMA'd my device, from there on all things worked as expected. had to RMA since pc's didnt recognize my pixel anymore - did only charge through port. And with the new unit i did the process without any issues.
[Google Pixel 2 XL Guides, News, & Discussion] Teffy:
For some reason magisk fails to install everytime. I installed latest version of manager, set to beta, moved boot img onto device, when I run install it says extracting files and then installation failed.

EDIT: Just did a reboot and tried again and it worked fine, so forget that.
[Google Pixel 2 XL Guides, News, & Discussion] rodcpierce:
Mine patches and installs fine, but then just boots back to fastboot. I know its the correct boot image as when I flash the stock boot image back, it boots just fine. Im using the latest version of Magisk manager.

*edit*

Just did the exact same procedure twice more with the same file, and the third time worked. Odd, but Ill take it!
[Google Pixel 2 XL Guides, News, & Discussion] S3hush:
Magisk App Installation Failed

I put the boot.img on the phone, a Pixel 2

loaded the magisk App

put the magisk v18 zip file on the phone.

I start the app, select install Magisk v18, then select the boot.img file

Then this happens:

-copying boot image to cache

-device platform: arm64-V8a

-existing zip found

-extracting files

-unpacking boot image

-checking ramdisk status

-stock boot image detected

-backing up stock boot image

-patching ramdisk

-repacking boot image

! installation failed

I am not sure where to go from here. Please help
[Google Pixel 2 XL Guides, News, & Discussion] jd1639:
My first question is, is your bootloader unlocked? Second, why bother patching the boot image? Why not just boot twrp and install magisk with that?
[Google Pixel 2 XL Guides, News, & Discussion] matz_92:
Unfortunaly this method does not work for me.

I'm working on a single-board computer i.MX7D with Android Things 1.0.8. I've correctly installed MagiskManager and it has repacked the new image patched_boot.img. Next I have flashed the new image into boot_a and boot_b partitions using fastboot:

fastboot flash boot_a patched_boot.img

target reported max download size of 419430400 bytes
sending 'boot_a' (14720 KB)...
OKAY [ 0.459s]
writing 'boot_a'...
OKAY [ 0.702s]
finished. total time: 1.161s

fastboot flash boot_b patched_boot.img

target reported max download size of 419430400 bytes
sending 'boot_b' (14720 KB)...
OKAY [ 0.463s]
writing 'boot_b'...
OKAY [ 0.702s]
finished. total time: 1.164s

When I reboot the system Magisk shows "Magisk is not installed".
[Google Pixel 2 XL Guides, News, & Discussion] S3hush:
Thank you for responding.

My bootloader is unlocked.

I have tried booting into twrp but it does not decrypt the hard drive and I cannot locate the zip file for Magisk.

I have removed the pin lock on the phone and it still presents the files as encrypted on the phone.

I was attempting to use the img file and load the Magisk file from there but the decrypting problem has me stumped.

I have also tried pushing the Magisk file through the unencrypted TWRP using adb push to a file I can see through the unencrypted TWRP:

C:\Program Files\Android\android-sdk\platform-tools>adb push /Magisk-v18.0.zip/sdcard/data/adb/

adb: usage: push requires an argument

I finally got sideload to start through TWRP but now cannot locate the file on the phone.

C:\Program Files\Android\android-sdk\platform-tools>adb sideload magisk-v18.0.zip

serving: 'magisk-v18.0.zip' (~68%) adb: failed to read command: No error