yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] ldyal09:
Same; samsung galaxy s5 powered by android recovery booting in blue, and goes to a black screen, restarting over and over; here is the log from ODIN (Also ty so much for the help)

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Added!!

<ID:0/003> Removed!!

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> G900V_PF4_Bootloader.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Erase...

<ID:0/003> Set PIT file..

<ID:0/003> DO NOT TURN OFF TARGET!!

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> SingleDownload.

<ID:0/003> aboot.mbn

<ID:0/003> NAND Write Start!!

<ID:0/003> rpm.mbn

<ID:0/003> sbl1.mbn

<ID:0/003> sdi.mbn

<ID:0/003> tz.mbn

<ID:0/003> aboot.mbn

<ID:0/003> sbl1.mbn

<ID:0/003> rpm.mbn

<ID:0/003> tz.mbn

<ID:0/003> sdi.mbn

<ID:0/003> NON-HLOS.bin

<ID:0/003> boot.img

<ID:0/003> recovery.img

<ID:0/003> system.img.ext4
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] Bren123:
Hmmm ok I want you to boot the phone into download mode and install this version of kies to your computer and plug the phone in and tell me what it says or send me a screenshot http://downloadcenter.samsung.com/content/SW/201611/20161118155850485/Kies3Setup.exe

Is it 2:30 am for you to? Lol
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] ldyal09:
Yeah lol 2:30 am here also
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] Bren123:
Check your PM
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] ldyal09:
I let it sit here for a few minutes, still sitting here just says connecting
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] GeTex:
Wow, [MENTION=7563399]hauckk@sfreserves.org[/MENTION] got you into a real mess. I'm not sure yet how to save your phone but I know I could do it, even if I have to JTAG it from the dead. Right now your best bet is going to probably be grabbing the full ship tar from the rooting thread and the official PIT file for your phone(make sure you match 16 to 16 and 32 to 32) then you check repartition but do not check nand erase. What was the last version of android you ran before this?

[MENTION=7563399]hauckk@sfreserves.org[/MENTION] STOP TELLING PEOPLE TO USE THE COMBINATION FACTORY TEST SAMPLE!!!
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] hauckk@sfreserves.org:
I will stop telling people to use it.

Just for curiosity sake and please forgive me but why is the factory Img firmware dangerous?
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] ldyal09:
Android 6.0.1 was my last version of Android on this phone before this issue lol
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] ldyal09:
I am downloading the file from is this the one you meant?

http://xdaforums.com/showpost.php?p=53447942&postcount=1
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] al50:
Unfortunately, those files would be of any use to you if your Bootloader is above OD5. Basically, those files from Misterxtc are for those whose Bootloader/firmwares are able to ODIN back to previous versions. Such as KK and earlier LP OS....not saying that they're not useful, because they are very much so but in your case, they won't help. I sent you a PM sir. Thank you
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] ldyal09:
<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/005> Added!!

<ID:0/005> Odin engine v(ID:3.1203)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Set PIT file..

<ID:0/005> DO NOT TURN OFF TARGET!!

<ID:0/005> Get PIT for mapping..

<ID:0/005> Firmware update start..

<ID:0/005> SingleDownload.

<ID:0/005> aboot.mbn

<ID:0/005> FAIL! (Auth)

<ID:0/005>

<ID:0/005> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

Here is the ODIN Log, sorry haven't had a way of charging the phone, just got a new battery.
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] ldyal09:
Update for anyone following this, replaced the charging port, now it boots up normally, but won't OTA update back to Android 6.0.1; system update shows no update available. Any idea how to get back to 6.0.1?
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] hauckk@sfreserves.org:
Use Samsung kies 3 it will update your phone for you
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] al50:
From your post above, what were you trying to Odin? You didn't mention of what you were trying to Odin and the log you posted didn't have a file listed....of you were on any firmware OE1 and above, your best bet and luck is to Odin the PB1 tar to get you back to a normal operating system.....if you were on MM, try to Odin the PD1 tar.....from skimming through your prior posts, you had flashed all kinds of firmwares....so best thing to do is to try to Odin firmwares THAT ARE TO BE USED FOR THE VZW S5 SM-G900V.......sorry for the uppercase but unless you know what you're flashing and how to deal/work with tar balls unrelated to the VZW S5, use the ones that "trusted" VZW members post or mention of using....I mean no offense to anyone who's helped others along the way, so please don't take it the wrong way.....Nothing personal....
[Honor 8 Questions & Answers] mimin0:
Any way to disable soft keys without rooting? Immersive Mode doesn't work because it disables the keyboard.
[Honor 8 Questions & Answers] XHunter:
I'm Possible

So,

Here is the way,

Note-Do it at your own risk!! I'll not be responsible for anything!!

It is not actually rooting your device...:silly:

I'll just tell you the method...

Rest you have to figure it out how to do it because I'm not an owner of Honor 8!!! , Currently my device is Lenovo A6000 Plus:cool:

Requirements::rolleyes:

1. PC

2. ADB Files

3. Custom Recovery ( I recommend - TWRP above 3.0 because I've done it same way on my device)

4. Unlocked Bootloader / Fastboot (You should have it)

5. One working Data Cable

6. Minimum Knowledge of editing Build Prop

7. The flashable zip in the attachment below...

8. You with your Phone!!!....:p:p:D

Now Let's Start... (But 1st Try to understand carefully)

1. Download the Flashable zip & put it in your PC

2. Boot your phone into Fastboot/Bootloader ( In whatever process you want - i) Manually or ii) adb reboot bootloader):)

3. Now try this cmd - fastboot boot (name of the recovery).img [But before this step you must put your recovery into the adb folder];)

After this wait for few seconds... you must be booted into your recovery...

4. Go to Advance > File Manager > Navigate to system > Select build.prop > copy it to where ever storage you want (I prefer internal)

5. Hope you have mtp enable in the recovery mod, if not then reboot the phone into the normal mode then send the extracted file to your pc ( You can also use es file manager/explorer but I will tell the pc method because it is more perfect)

6. Open the build.prop with notepad ++ and try this method which is given by The Hard Gamer in his "[ROM][32bit][port]OCTOS 6.0.1 for lenovo a6000/+" post

EVERYTHINGS WORKING FINE

TO DISABLE NAVBAR EDIT YOUR BUILD.PROP......

-First obviously you need be a Root user

-Backup your build.prop to your PC or anywhere (but backup it!)

-Edit build.prop with a Root Explorer using this line:

qemu.hw.mainkeys=1

you have to add this at the END of the .prop, save and reboot.

[FOR Marshmallow/Android 6.0]

If you're on Marshmallow (Android 6.0) the process is exactly the same, add the line at the end of the build.prop EXCEPT that you must leave 2 spaces after you added the line.

7. Put replace the build.prop file with the new edited build.prop in the flashable zip.... and put it into your root directory of internal/external storage.

8. Now repeat step 2-3.

9. Mount System, if it is already mounted then unmount it then remount it.

10. Go to install > navigate to the flashable zip > Then flash it.

11. Reboot system & Enjoy (If you Can) :angel:

Another Note :-I was here to participate in Honor 8 wining contest so, I can not exactly tell you the right process because you know (I don't own one of the amazing device)... So, If this method works then please hit like :good: & reply me with your experience... Atleast I can deserve this much..:(:mad::D:o

& One important thing...

Sorry For My BAd English!!
[Honor 8 Questions & Answers] Rickyzx:
Thanks. I was also looking for solution of this issue and your solution helped me a lot
[Honor 8 Questions & Answers] mimin0:
I was looking for a method which does not involve custom recovery and unlocked bootloader, should've probably mentioned that. If I go the TWRP way then may as well root it, but then I'd lose OTA.

Don't feel comfortable doing that just yet.
[Honor 8 Questions & Answers] XHunter:
wow

I'm glad to help you!!

Please hit thanks if you really liked it!!

---------- Post added at 10:46 AM ---------- Previous post was at 10:28 AM ----------

I can understand what you want to say!!

But listen,

You can do the whole process without boot the phone in normal mode...

Just unlock the bootloader before the process and relock it after it...

It's that simple..

And It will automatically do a factory reset after unlocking..

My Previous phone was MMX CAnvas A1

I have done many experiments on it like these...

But At the end I still got the OTA updates... Even my SuperSu (By systemless flashable zip) is installed ;)

And you must take some risk in your life to get better results!!:o

Hope you understand!!!

And press thank button if it helped!!
[G 2014 Q&A, Help & Troubleshooting] Plabon7:
i am on RR5.8.0 ROM. which kernel should i use for BETTER BATTERY and also PERFORMANCE?
[XDA Assist] :
I currently have a HTC One M8 (Bell Canada), I've been in stores visted all kinds of websites that want my "IMEI" which I don't know what it does or it's used for

So I don't like the option of giving it to a website for money. My only other option is to go into a store and have some guy charge me 50$ to do it but it would take 24 hours. Another option would be

To go directly through bell which since my phone is inactive they want 75$ + Tax. I mean I'm not a cheap guy but with christmas coming up, perhaps someone on here can give me the cheapest course.

Even if you had steps I would do it myself if need be. Please contact me back. With regards Conrad Selvaggio.
[XDA Assist] Art Vanderlay:
Hi and welcome to XDA.

Your device has a dedicated forum here:

HTC One (M8) > One (M8) Q&A, Help & Troubleshooting

All questions regarding your device belong in the forum linked above. You'll need to create an account first so you can post in the main forums.

Good luck :)
[LG V20 Questions & Answers] ThaHaloMilitia:
https://chat.whatsapp.com/0R66Ft4lGMj8fXO58WZqww
[LG V20 Questions & Answers] ThaHaloMilitia:
As well as the Telegram Group

https://telegram.me/joinchat/EFrFAwupz3-Gzo6EKRDF8A
[Google Pixel XL Guides, News, & Discussion] tdimarzio:
After a week of head scratching and attempted process of elimination, I've finally figured out (or at least gotten closer to) the root cause of the Wi-Fi issue I have been experiencing on my Pixel XL 128.

What I noticed is that my speedtest (Ookla app) results were occasionally significantly lower than they should be. What they should be (when ISP bandwidth and WiFi link speed are not the bottleneck) is ~180 Mbps. This is what I would get consistently (say, 19 times out of 20) with my Nexus 6P. With my Pixel, I would rarely get ~180 Mbps and usually get between 100 and 130 Mbps. This is while the actual Wi-Fi link speed is 866 Mbps with excellent signal strength. Basically, standing next to the router. My first order was to rule out defective hardware so I performed a factory reset and immediately following I was now getting ~180 Mbps in speedtest app. Reinstalled my ~225 apps and Wi-Fi was still ~180mbps in speedtest. Few days go by and everything is still fine. Then, without warning and with no obvious change, the Wi-Fi speed drops back down to 130 Mbps or below. Nothing fixes it. Not soft rebooting. Not cold booting. Not resetting network to factory resetting. Not rebooting the router. Nothing. Then, I discover by accident that when the Pixel is charging the speed jumps back up to ~180 Mbps very consistently. I can actually watch the speed change in real-time if I unplug the power while the speed test is in progress.

So, I called Google about this and the tech reproduced the same exact behavior on his Pixel XL, which, frankly, amazed me. I mean, what are the chances that his download bandwidth max is 180Mbps just like mine? Anyway, I wasn't going to argue with him. Was just glad he reproduced the issue and said he is escalating it to level 2 engineering. He suggested a fix would be forthcoming in the next week but I'm not sure how he would know that.

Incidentally, I am running NPF26J.

I cannot remember if this issue was present in NDE63V.
[Google Pixel XL Guides, News, & Discussion] tdimarzio:
Unfortunately, the issue is not fixed in NMF26O

With charger connected:

On battery:
[Google Pixel XL Guides, News, & Discussion] z3pp3lin:
Unchecking BT scanning under location worked for me.
[Google Pixel XL Guides, News, & Discussion] tdimarzio:
Hmm ... I just tried turning Wi-Fi and Bluetooth scanning on and off (multiple combinations) and had no effect on my Wi-Fi speed test.

What effect did it have for you?
[Google Pixel XL Guides, News, & Discussion] z3pp3lin:
A 1mb file would take like 5 min to download from the play store but had no issues from a browser. Now it works fine from the play store. Some say it could be an issue connecting to 5GHz. http://xdaforums.com/pixel-xl/help/wifi-download-playstore-slow-t3485494/page4
[Google Pixel XL Guides, News, & Discussion] tdimarzio:
Oh, OK. We have completely different issues then. A 1 MB file would take a fraction of a second to download for me even under the problem condition state. What I am seeing is that download rate drops from ~22 MB/s to ~15 MB/s when I take the phone off the charger. This should not be happening though because my Nexus 6P was always able to achieve 180 mbps (~22 MB/s) whether on the charger or not.

I can only envision this being either a hardware defect in my particular device or a bug in the network driver. Since nobody else seems to be reporting this, I'm starting to lean towards this being a defect in my Pixel XL.
[Google Pixel XL Guides, News, & Discussion] z3pp3lin:
I know but it seems no one has exactly the same wifi issue and some things work for some but not others. Never hurts to try everything we can.
[Google Pixel XL Guides, News, & Discussion] tdimarzio:
Agreed.

I factory reset and now the problem is gone. So now I'm leaning towards a bug in the network stack.

Will post an update here when I have one.
[Google Pixel XL Guides, News, & Discussion] tdimarzio:
So ... 2 days after the factory reset the problem has returned. Went to bed last night and the wifi speed was normal. Wake up this morning and the problem has returned. I have no explanation. It's as if the WiFi performance is on a timer that starts when you factory reset. There must be a software explanation for this but I'm having no luck with Google. They won't let me past tier 1 help desk that just offers to RMA the phone.
[Google Pixel XL Guides, News, & Discussion] tdimarzio:
Just had a slight light-bulb moment while trying to think about what might have changed between last night @ 1 AM and this morning at 9 AM. Thinking back to the fact that the problem disappears when the charger is plugged in, so, having something to do with power, I remember that last night I ran the phone low enough for the automatic "battery saver" mode to kick in. Before last night and since the last factory reset I hadn't run it that low. So, I'm thinking (only theory at this point) that the "battery saver" mode does something to the wifi that does not get reversed when it comes back out of battery saver mode. I'll keep investigating down that line of thought. If I factory reset again (which I really hate doing since it takes me a solid 5 hours to get everything back to my working state) then I would disable the automatic battery saver mode and see if that prevents the problem from ever reoccurring.
[Google Pixel XL Guides, News, & Discussion] desiregeek:
They probably throttled the speed to use less power when unplugged so Wifi speed is slower when unplugged.
[Google Pixel XL Guides, News, & Discussion] dwibbles33:
This is an interesting theory, I'm interested in seeing what you come up with.
[Google Pixel XL Guides, News, & Discussion] tdimarzio:
Well, we'll know in a week or so if it's device specific at least. Google is sending me a new one. If the problem reoccurs then at least there will be one less item in the process of elimination. If I find out anything new in the meantime I'll post it here.
[Google Pixel XL Guides, News, & Discussion] tdimarzio:
So, I received my replacement Pixel XL 128 yesterday and I've already returned the "old" one. So far I'm not experiencing the WiFi performance issue on this new Pixel XL, however, in the past the issue has taken some days to develop following a factory reset. So, now we wait and see if the problem returns on this new Pixel XL. If it returns, we'll know it's a software issue. I'll post an update here when I have one.
[Google Pixel XL Guides, News, & Discussion] tdimarzio:
Incidentally, and not related to the subject of this thread at all, the screen color calibration is ever so slightly different between this Pixel XL and my original Pixel XL. Specifically, the white balance is a little more to the warm side on this one. I understand that's par for the course with OLED screens though. Maybe over time the screen will change to be more like my original Pixel XL. It's nothing that bothers me too much, but I do prefer the color calibration more on my original Pixel XL.
[Google Pixel XL Guides, News, & Discussion] tdimarzio:
Update:

Well, it's not a hardware issue. My brand new RMA Pixel XL 128 is exhibiting the EXACT same WiFi performance issue. It was fine for a few days and then yesterday the battery dropped low enough for battery saver mode to kick in. Now the WiFi performance is apparently permanently limited until / unless I perform a factory reset. Strange that more people aren't reporting this.
[Google Pixel XL Guides, News, & Discussion] Alcolawl:
Pretty strange, but the reason why people probably aren't reporting it is they're most likely not performing constant speed tests on their phone. My connection at home is around 330 mbps. The WiFi is capable of achieving this speed as well, but when I speed tested my Nexus 5X sometimes it'd be less than that (like ~250). I chalked it up as weak battery powered radio bull****tery and then realized I'd never need that speed on my phone anyways lol.

As for this issue, it looks like you're onto something here and the fact that the Google tech was able to replicate this issue is even more intriguing. I hope they keep contact with you in regards to whether or not a fix has been found yet.
[Google Pixel XL Guides, News, & Discussion] tdimarzio:
I hope so too. Of course, I'll continue to post updates here as I have them. I wish I could just not let it bother me, but it's not in my personality unfortunately.
[Google Pixel XL Guides, News, & Discussion] tdimarzio:
So I factory reset my replacement Pixel XL which as expected has restored the WiFi performance to the normal state. This time I have disabled the automatic enablement of battery saver mode. We'll see if this prevents the issue from reoccurring.
[Google Pixel XL Guides, News, & Discussion] tdimarzio:
Latest update - The problem has reoccurred, even with "battery saver" mode completely disabled. This is bizarre. I was pretty confident that as long as the phone never entered battery saver mode I would be in the clear. Now, about 3 or 4 days since my last factory reset, the problem has reoccurred for no apparent reason. I am at a loss. This morning the WiFi was performing optimally (no artificial 130 mbps ceiling), then I went to a family gathering, took a bunch of pictures and came home. Now the 130 mbps ceiling is back. What's also interesting is Comcast recently increased the speed of the internet connection. Before it was 180 mbps down. Now it's 230 mbps down. Just had to reboot the cable modem to get the update. However, the 130 mbps ceiling did not change. This means the performance limitation is not proportionate to the internet bandwidth. In other words, whether the internet pipe is 180 mbps, 230 mbps or 500 mbps, the Pixel XL will always be capped around 130 - 140 mbps once the issue kicks in. If I simply plug in the AC power to the Pixel, speedtest increases to 230 mbps. This is reproducible 20 times out of 20. Really hope Google fixes this at some point.
[Google Pixel XL Guides, News, & Discussion] Drashnar:
Wow, this is pretty concerning. I wonder if anyone else is having this issue? I don't have enough bandwidth down to test it, or I'd try.
[Google Pixel XL Guides, News, & Discussion] Alcolawl:
I get 330 down and 25ish up at home reliably on a hardlined connection. I'll grab the speedtest.net app, run a few tests and update this post when I get home.

EDIT: Can confirm that the phone is throttled when discharging on battery!

Desktop hardlined to an ASUS RT-AC1900P which talks to a Motorola SB6190 Gigabit Modem. Same test server, same time of day.

Pixel XL on my 5 GHz network standing in the same room:

Ran another test with it plugged into the charger while laying in bed (in between two walls where the router is) and got 195 mbps down and a similar upload speed. The Download was climbing too, given more time it would've easily exceeded 200 mbps.
[Google Pixel XL Guides, News, & Discussion] tdimarzio:
Excellent! Well, not really excellent that you too are experiencing the issue, but excellent that finally someone else can corroborate the issue.

In addition to the wifi performance increasing while on the charger, you should find that the wifi performance while on battery returns to full speed (matching that of on charger) if you perform a factory reset. Of course, that's an inconvenience. If you're feeling so inclined, would be great for you to reproduce that as well.

Lastly, if you do perform a factory reset and find wifi performance has been restored while on battery, you should expect the issue to reoccur after some arbitrary amount of time for no known reason, ultimately requiring another factory reset to resolve it.
[Google Pixel XL Guides, News, & Discussion] PsiPhiDan:
This is disconcerting. I hope Google hasn't just thrown your issue out the window. This should be fixed.
[Google Pixel XL Guides, News, & Discussion] tdimarzio:
I agree. Unfortunately, I haven't heard a peep from Google and, besides this thread, haven't seen another mention of the issue at all. I'm starting to become resigned to living with this issue indefinitely :(
[Google Pixel XL Guides, News, & Discussion] bcantana:
I have been seeing this issue since getting my Pixel XL in January and someone on Reddit made this same correlation between speeds while charging and while on battery. Hopefully Google is still looking into it.

https://www.reddit.com/r/GooglePixel/comments/61zj7f/strange_issue_with_wifi/

https://productforums.google.com/fo...jJ0JjR9hs;context-place=forum/phone-by-google
[Google Pixel XL Guides, News, & Discussion] DespairFactor:
This seems like power being regulated and lowering the drain from the wireless card. This is likely done by design, perhaps CodeAurora has so changes for this as it is a QCOM Wi-Fi stack.