yashsingh1/xdaforums huggingface dataset:
[G4 Q&A, Help & Troubleshooting] antonyf:
Apologies if this seems well travelled path, and I've certainly led a lot over the internet. But I just wanted to describe my issue and see if I've missed anything!

I've had chronic battery issues, and had a spare and I'd swap them in/out but I came to conclusion that wasn't great as it may not read battery stats well doing two different batteries. I was getting less than 12 hours between batteries. So now i have Powerbear 6500mAh battery and have been using it for a week. Apart from a heavy usage day I can now get 24 hours out of it. Superb.

Then as if by magic, trouble returns! The battery drained 11% overnight in seven hours. That's in airplane mode. 11% of a 6500mAh battery! Battery stats shows nothing has used battery in particular, just phone idle. Wake locks there was nothing significant. Now 5 hours later it's dropped another 43% with not a lot of use, just web and some maps.

Things I've tried:

Making sure the option to store activity logs is off.

Location turned off for all but most vital apps, like maps.

No automatic syncing of anything.

Greenify - and I shut down anything I can.

Wakelocks - ensuring nothing is abnormal, got rid of CityMaps due to excessive wakelocks.

Airplane mode at night - no cell, no wifi.

I rooted and reset the OS about six months ago, so that is my logical next step... but I'd rather understand what could cause 11% of 6500mAh to be drained by doing nothing!

Any thoughts of what I might have missed?

Stats: LG G4. LG-H815. Android 6.0. Build MRA58K. Software V20g-EUR-XX.

Thanks

Antony
[G4 Q&A, Help & Troubleshooting] MattheewHun:
What root method did you choose? SuperSU or Magisk? With Magisk my phone was hot (~70C) and got only 1.5h screen time, when i switched to SuperSU, it was gone.
[G4 Q&A, Help & Troubleshooting] divineBliss:
Install GSam Battery Monitor app from the Play Store and see if it helps show you what's using up the battery.
[G4 Q&A, Help & Troubleshooting] deltadiesel:
I know you are not going to like reading this but

I don't use these extended batteries for a reason. Phone wasn't made for it.

Try your original battery

These extended batteries are also known to crap out after 500 charges

Use battery monitoring app to help you determine what's happening
[G4 Q&A, Help & Troubleshooting] antonyf:
SuperSU

I removed it as it never provided me anything worthwhile. I think it used to just say Android used the power or something vague. :D I can reinstall it, but there was never one specific identifiable reason I remember that.

Then I have to put up with a phone that won't last 6 hours, which is what led me to get additional batteries and now the PowerBear.

That said the following night, it used about 2% overnight... so erratic to say the least! And I have 59% left after 10 hours use. It's just the randomness the other day that spooked me. I did learn it was low on disk space, could have that caused that particularly bad event?
[G4 Q&A, Help & Troubleshooting] MattheewHun:
Did you try switching kernel? I can suggest you to try Imperium Kernel, that will reduce the system's usage. Other than this i have no idea. :\

---------- Post added at 06:47 PM ---------- Previous post was at 06:44 PM ----------

What you said, is nosense for me. Some custom batteries are better than the original. You jsut must be lucky to pick the right one. :)
[G4 Q&A, Help & Troubleshooting] antonyf:
Thanks. I was thinking of doing something like that. Thanks for the heads up, there's a lot of choices... I'll check that one out.
[Huawei P9 Questions & Answers] spartan02sparte:
I had to switch to a stock rom B386, but I'm missing FULL application, so I have to go back on the b360 or b361 and then upgrade to b386 but i find no viable link for the b360 or b361, Someone would have one?

It's urgent
[Huawei P9 Questions & Answers] mariomac66:
you don't want to risk it so. Search the site huawei downgrade to MM. are two firmware one by 75 mb and 1.75 gb. More or less. to be able to perform the procedure. you need the stock recovery. otherwise you can't make anyone else downgrade. even at version B360 or B361.

THANKS
[Huawei P9 Questions & Answers] spartan02sparte:
I have to go back just to find the original applications ???
[Huawei P9 Questions & Answers] spartan02sparte:
I went back android 6 and everything came back, thanks :)
[Huawei P9 Questions & Answers] mariomac66:
im very happy for you bro[emoji106] [emoji106] [emoji106]

THANKS
[Honor 9  Questions & Answers] RobertHarkness:
Any updates on the release of STF-L09C10B100? or could someone make a back of it on twrp and please upload so i can restore my device?
[Honor 9  Questions & Answers] tnotb1:
wtrp baackup doesn#functionts for me to use honor 9 normally. It stucks after emui setup process: https://xdaforums.com/honor-9/help/help-to-restore-l09-bootloop-t3651641/post73290581#post73290581 and https://xdaforums.com/honor-9/help/help-to-restore-l09-bootloop-t3651641
[Huawei MediaPad X2] steve5000:
Hi has anyone had this problem, i just installed a backup which i had previously made but when i checked the system/bin was not reinstalled, and the bootanimation in the cust folder was unchanged.

well i reinstalled the backup again and this time it worked. This is a bit worrying anyone else had this?
[Mate 8 Q&A, Help & Troubleshooting] jallil-k1:
Hello every one i once bricked my phone after a bad flash i tried every thing to solve it but nothing worked for me their was always this error FAILED remote command not allowed and i had no twrp i was just stuck in erovery . i even lost hope and give it to repair centers but no one know how to fix it.

the solution was very simple the Dload Method you just need to know which version you're in and you thins methode will work for you 100%

i was in b560 so i download the firmware and extracte it to the dload folder on my sdcard i tried for the first time but it didnt work i tried the seconde time and it works but i had THis build NRD90M test keys so i downloaded the rollback package B500

and flash the b320 a few moment i had the update 321 ans 560 and 580 and now every thing works fine.

So my freinds do not give up and spend money on dc unlock just try this method.
[Android Q&A, Help & Troubleshooting] yourrealking:
I posted the following question a few days ago, but there have been no replies.

https://xdaforums.com/nexus-6p/help/adjust-screen-gamma-value-t3651947

So, I just wonder if screen gamma value is adjustable in Android at all? Of course it is unlikely to be achievable in stock ROM's, but what if you are using a custom ROM that you can build from source?

Or is the gamma value fixed in hardware or in the binary from the manufacturer that custom ROM developers cannot modify?
[HTC Vox] lepatchouli:
hello,

I retrieve the ROM update on the site htc and Roma are corupted before it blocks 100%. :mad::mad::mad:

My telephone is no longer usable, some body can help me ( i lookink for this rom ) :D

Thanks for your help
[HTC Vox] lastOne:
can you get into bootloader mode ?
[HTC Vox] lepatchouli:
rom s710 hs

hello,

i try bootloader mode with Rom of dr gonzo without succes

we waiting the new rom froom htc

Thanks
[X Style (Pure) Q&A, Help & Troubleshooting] XxperexX:
I was at 24.49-18-16 with unlocked bootloader and twrp and wanted to go back to stock, so i followed the guide at https://xdaforums.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110/page1 to do so because in it it says that having an unlocked bootloader wont prevent you applying ota updates, and there is no image or stock recovery for 18-16, so instead i downgraded to 18-8 via fastboot without unlocking the bootloader hoping i can just ota update back to 18-16, however when i try and do so in the stock recovery it just says "error"

i tried using the moto device manager on pc with all the correct drivers but it keeps saying under maintenance, so is there anyway to upgrade my device via ota back to 18-16?

Thanks
[X Style (Pure) Q&A, Help & Troubleshooting] acejavelin:
If you had TWRP your bootloader is unlocked already, shouldn't be an issue.

You can see what the error in stock recovery is when it is, when that screen is displayed hold POWER and tap VOL UP for he log and post the error message.
[X Style (Pure) Q&A, Help & Troubleshooting] XxperexX:
I did so and this came up:

Supported API: 3

Finding update package...

Opening update package...

Verifying update package...

Installing update...

Source: motorola/clark_reteu/clark:6.0/MPHS24.49-18-8/4:user/release-keys

Target: motorola/clark_reteu/clark:6.0/MPHS24.49-18-16/12:user/release-keys

Verifying current system...

"/modem/image/adsp.b01" has unexpected contents.

E:Error in /cache/Blur_Version.24.221.8.clerk_reteu.reteu.en.EU.zip

(Status7)

Installation aborted.
[X Style (Pure) Q&A, Help & Troubleshooting] acejavelin:
Your modem flash didn't take properly when going back to 18-8... Reflash the modem stack from 18-8

fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin

And verify you get an OKAY after each step, if you don't, then repeat the command (sometimes twice) until you do, then apply the update again.
[X Style (Pure) Q&A, Help & Troubleshooting] XxperexX:
Ah, ur a life saver, it worked :)

So when the nougat update comes for my device i can upgrade without problems?
[X Style (Pure) Q&A, Help & Troubleshooting] acejavelin:
Should be able to, as long as you stay stock...

Remember, that once on Nougat you will NOT pass SafetyNet checks with an unlocked bootloader (no Android Pay, Pokemon Go, Netflix, etc) but there is no way to go back to a locked bootloader at this time so this is more of a heads up than a recommendation to do anything. Once on Nougat you can root with Magisk and do a bypass or wait for the official firmware image to be able to relock.
[X Style (Pure) Q&A, Help & Troubleshooting] Stupendous:
Hi there,

Sorry for hijacking this thread, but I've got a similar problem with the OTA update. Any help would be appreciated.

The error message I get is as follows:

Supported API: 3

Finding update package...

Opening update package...

Verifying update package...

Installing update...

Source: motorola/clark_reteu/clark:6.0/MPHS24.49-18-16/12:user/release-keys

Target: motorola/clark_reteu/clark:7.0/NPHS25.200-15/14:user/release-keys

Verifying current system...

E3005: "/bt_firmware/image/btfw30.tlv" has unexpected contents.

E:unknown command [log]

E:Error in @/cache/recovery/block.map

(Status7)

Installation aborted.
[X Style (Pure) Q&A, Help & Troubleshooting] acejavelin:
Your Bluetooth firmware is incorrect... Since you are on 18-16 already it's a little trickier, but luckily the BT firmware hasn't changed in awhile.

Find MPHS24.49-18-8 reteu and

fastboot flash bluetooth BTFM.bin

And try again... If that fails you might have to start over and go completely back to 18-8, then OTA to 18-16, then to Nougat. ?
[X Style (Pure) Q&A, Help & Troubleshooting] Stupendous:
Thank you.

That worked like a charm on the first try. *tips hat*
[X Style (Pure) Q&A, Help & Troubleshooting] DellCri:
Man, Can you help me? I was on lineageOs 14.1 and flash stock ROM 29.49-18-8 and then OTA update to 18-16. But for OTA Nougat this error apear...

verifying current system...

E3005: "/system/vendor/lib/libllvm-qcom.so" has unexpected contentes.

E:unknow command [log]

thanks
[X Style (Pure) Q&A, Help & Troubleshooting] donutboy3:
THANK YOU!

now i can cancel my appointment at Hair Club for Men!

---------- Post added at 08:04 AM ---------- Previous post was at 08:03 AM ----------

THANK YOU!

now i can cancel my appointment at Hair Club for Men!

THANK YOU!

now i can cancel my appointment at Hair Club for Men!

---------- Post added at 08:05 AM ---------- Previous post was at 08:04 AM ----------

THANK YOU!

now i can cancel my appointment at Hair Club for Men!

THANK YOU!

now i can cancel my appointment at Hair Club for Men!

---------- Post added at 08:09 AM ---------- Previous post was at 08:05 AM ----------

:Dsorry for the multi post...
[LeEco Le 1S Guides, News, & Discussion] stealthinator16:
I have seen a lot of people using unofficial and third-party methods to root, which can result in a lot of adverse circumstances to say the least.

So I'm presenting a complete noob-friendly guide to rooting.

Prerequisites

:

1. A computer ( I'm using Windows 10 but any OS would do)

2. A USB cable

3. Basic computer know-how

Part 1 (Getting computer ready)

Download sdk tools (adb and fastboot) from here

Note that in the entire guide I'm using official products.

So in Windows, download the zip and extract it in any folder.

Now download latest twrp recovery from here

The lastest version as of 7th August, 2017 is 3.1.

The downloaded file will be named as twrp-x.x.x-0-x3.img.

Now rename this as recovery.img (this will make our work easier)

Now move that file to platform-tools folder which we extracted earlier.

Also, I suggest downloading Intel USB drivers for Android from here

Part 2 (Getting Phone Ready)

Unlocking bootloader didn't format my phone but taking a backup is still important.

Now go to Settings<About Phone and click on Build until it says "You have become a developer"

Now back to main settings menu and find "Developer Options". And turn USB debugging on.

Download magisk install.zip, unistall.zip ans apk from here

Now connect your phone to PC via USB cable.

Step 3 (Rooting!!)

Now open platform-tools folder and press Shift+ right click.

Select "open command prompt here".

Now a terminal will open.

Type

adb devices

Now you will get a prompt on your phone. Accept it.

Now type

adb reboot bootloader

Your phone will automatically reboot and fastboot will come up.

Now type

fastboot oem unlock

[Alert! If you get <waiting for device> right click on start menu, select the unrecognized device and install Intel driver in it. Google for detailed instruction]

The process will start and you will get something like

(Okay ....)

(Okay....)

And type prompt. Now type

fastboot flash recovery recovery.img

Flashing will start.

When you get type prompt again, type

fastboot reboot

And when the screen switches off, hold power up+power button.

(

fastboot reboot emergency

should work but it's effect was same as

fastboot reboot

If you get something like red state... verification failed... Then it's a good news.

Wait a few seconds and then twrp will launch. I suggest swiping on the first screen

[because letv is almost dead and we can't expect any updates. Plus my bootloader was relocked in my first attempt when I didn't swipe.]

(I suggest wiping dalvik cache and cache)

Now you can just reboot your phone normally.

Now install magisk apk.

Now reboot again to recovery. (Easiest way is Update app>tree dots menu> reboot to recovery)

When twrp starts, go to install> download and find magisk zip. Swipe to install.

Reboot and you have a fully rooted phone!!
[LeEco Le 1S Guides, News, & Discussion] Theda Singh:
Will it work with Le1s eco x509

Will the given method work with le 1s eco x509
[LeEco Le 1S Guides, News, & Discussion] stealthinator16:
Yes it will!
[LeEco Le 1S Guides, News, & Discussion] deepu_:
Im stuck in <waiting for any device>. I've installed the Intel drivers , what do you mean by select unrecognized device and install the Intel driver in it?
[LeEco Le 1S Guides, News, & Discussion] iamDeadpool:
Intel driver will not work try downloading drivers from skyneel for our phone
[LeEco Le 1S Guides, News, & Discussion] stealthinator16:
Intel drivers worked for my leeco le 1s. Ideally, Intel drivers should work for all devices.

I'll make a tutorial with screenshots on setting up the drivers whenever I get time.
[LeEco Le 1S Guides, News, & Discussion] junaidshaik96:
i cant find "open command prompt here" with shift+ Right click in platform-tools folder
[LeEco Le 1S Guides, News, & Discussion] stealthinator16:
Make sure the directory is writable .
[LeEco Le 1S Guides, News, & Discussion] sumashash:
It works perfectly on x507, thanks bro
[LeEco Le 1S Guides, News, & Discussion] eighty9sid:
Orange State

There was a prompt for TWRP update and Magisk Update.

After it has started showing Orange State instead of Red State.

The phone got rebooted and all installed apps were deleted.

Xposed got uninstalled.

Playstore, Googlemaps got unistalled.

Camera is working.

Calling is working.

Now it shows Orange State.

Is it safe.

Can we bring it to red state?

As per this link

https://www.androidauthority.com/verified-boot-warnings-in-android-6-0-marshmallow-650368/

Orange warning: Your device is in an “unlocked” state. This means that your operating system can’t be checked to make sure that it’s safe to use.

Red warning: The operating system on your device has been changed or corrupted and is not safe to use. The device may not work properly and could expose your data to corruption and security risks.

Orange State seems to be a better state than red.
[LeEco Le 1S Guides, News, & Discussion] stealthinator16:
I too got orange state when I had to reroot my device after it got bricked, but there was no issue, everything worked perfectly.
[LeEco Le 1S Guides, News, & Discussion] Valambok:
Hi l used this very step by step guides but sadly l got stuck at the :-

Alert! If you get <waiting for device> right click on start menu, select the unrecognized device and install Intel driver in it. Google for detailed instruction]

The process will start and you will get something like

(Okay ....)

(Okay....)

Here l select the unrecognized device and install the Intel drivers but it stuck at the "Okay,,,,Okay" prompt. Meaning that l didn't get this okay prompts and it keeps me on waiting the whole day.

Secondly, till this command l stop it and power down the phone, so after l power back on and try opening the "Application" folder, then it's not working anymore, it shuts down itself.

Please help!!
[LeEco Le 1S Guides, News, & Discussion] stealthinator16:
Don't power off your phone. Post a screenshot of what exact problem you face with driver installation.
[LeEco Le 1S Guides, News, & Discussion] ondou:
Phone Dead

Hi, after completing this step by step guides my Le 1s can't boot to normal anymore, even if I try booting up system from twrp also it doesn't help, I cant even power off now. So, please please help me out again on how to get back to a normal phone. Thanks in advance.

N.B: My phone shows Orange state
[Zenfone 5 Q&A, Help & Troubleshooting] gelogelogelo:
Hello, this may sound dumb. But, what happens when you format/delete/erase and reflash dnx and ifwi? I'm trying to experiment because when I relock the bootloader, it shows that the bootloader version is 59.1A. That is not the version of the locked bootloader. And also on stock rom it freezes even when my bootloader is locked that's why I wanted to do this. I want some serious answers so please answer seriously. Thank you! :)
[Zenfone 5 Q&A, Help & Troubleshooting] nheolinkin:
dnx is bootloader (software but not hardware) and ifwi is bios which give command to bootloader. Basicly, bios tell the bootloader how it should config hardware for the kernel (boot.img) to work proberly.

So perhaps you don't wanna format/delete/or erase them. Reflashing is totally fine. It's just like "reinstall" or "update".
[Android General] Shaul_Kriheli:
First, i am new to this community so if my thread is not at the right forum i apologize.

I received my xiaomi redmi note 4X weeks ago and i noticed its performance decreased gradually.

First, it was all smooth but then the animations started to stutter a bit in Instagram and chrome and was unnoticeable and now its pretty noticeable and also found in system apps such as settings or security .

I have tried flashing the global ROM again, and then the EU ROM and Global DEVELOPERS ROM.

I thought that the problem is with the MIUI ROM so i flashed Resurrection Remix ROM and still the problem exists.

Any ideas on how i can solve this?

Thanks in advance for everyone:)
[P8lite Q&A, Help & Troubleshooting] Uncle_new_to_rooting:
Greetings! I`m feeling awfully embarrassed about my lack of knowledge & success with repairing my phone, not to mention the shame about making a thread about it. Alas, hope dies last, and i humbly ask for your guidance. I sincerely apologize , as well as thank you, for the time which you have given by reading this.

What has happened

: I made an attempt to root my Android phone for the first time, but apparently, i horribly failed, causing my phone to become stuck in a bootloop. I have read atleast a dozen of different threads & tutorials by now , which either did not help for my specific problem, or / and i`m just too dumb to follow the examples right. At first, i could not access neither stock recovery or fastboot, but i have disconnected the battery and now i can enter fastboot mode.

Some basic specs about the phone :

Phone model before trying to root:

Huawei P8-lite , ALE-L21.

Operating system before trying to root:

Android Marshmallow 6.

The current state of the phone :

The phone is stuck in a bootloop and cannot start successfully.

I can access fastboot mode by holding down the "Volume -" button & flash images to the phone.

I cannot access stock recovery.

What I have tried to do :

Flash images to the phone`s memory, but there seems to be no result.

Create a folder named "dload" on the memory card & place a file named "Update.app" inside. After doing so, powered up the phone , while holding power & buttons "Volume +" and "Volume -" at the same time. There seemed to be no effect since i could not visually see any changes on the screen.

As i mentioned earlier, i have read about a dozen different guides by now ( hence i feel dumb for not being able to fix it), but the three main examples were these threads :

https://xdaforums.com/p8lite/general/step-step-guide-to-unlock-bootloader-t3150616

https://xdaforums.com/p8lite/help/huawei-p8lite-bootloop-update-t3179184

https://xdaforums.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994

I hope that, with your experience and guidance, it might still be possible to successfully reanimate & root my phone (As i have read : as long as fastboot is available, there is still hope!).
[P8lite Q&A, Help & Troubleshooting] HoldMySoul69:
Jup. Hell you have hope!

1. From update.app extract boot.img and flash with fastboot, and it should be okey. To root MM use Magisk or Chainfire 2.64 both are systemless root, because MM, don't like system mode root! :)
[P8lite Q&A, Help & Troubleshooting] Uncle_new_to_rooting:
Greetings, thank you for your advice, but i have already tried doing so , based on this thread as an example (chapter 4): https://xdaforums.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994. Sadly, that did not help. Perhaps there might be a specific Update.app version of the file , of which i must flash these images?
[P8lite Q&A, Help & Troubleshooting] HoldMySoul69:
Witch Firmware you had? B... Maybe i will help you!
[P8lite Q&A, Help & Troubleshooting] Sonofapo:
try to download OpenKirin TWRP recovery (https://xdaforums.com/p8lite/orig-development/twrp-t3583180) and flash it via fastboot. This recovery is able to flash emui update.app zip too so you can install it via TWRP. I tried with b895 (vodafone) from b598 and it worked.
[P8lite Q&A, Help & Troubleshooting] Uncle_new_to_rooting:
Greetings, i am afraid that i am unaware of the firmware number on my phone. I do remember , howerer, that the phone model was ale-l21 , as well as that the OS version was marshmallow (6).