yashsingh1/xdaforums huggingface dataset:
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
Sorry I don't get you .. this is a BEFORE getvar ?

What's the current ? If there is a new one .. let me have a new one. I need to see the current one to know your device better.

I never see a M8w changed to M8x before.

If you only change CID&MID to Asia_WWE but not flashing any X.XX.707.X firmware .. your firmware still M8w only CID/MID is the problem which is really easy to fix.

Anyway, for now you want to fix the sound problem only, right ?

I get back to you tomorrow after you give me more info ... time to bed now .. good night.
[One (M8) Q&A, Help & Troubleshooting] Amri.NVR:
this is my current getvar all :

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.19.0.0000

(bootloader) version-baseband: 1.23.213311231.14G

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 6.18.1400.1

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B11000

(bootloader) cidnum: HTC__044

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: 205bdca3

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

because i cant find firmware for MID 0P6B62000, so i change CID to HTC_044 & MID to 0P6B11000 to flash RUU Asia_WWE to fix sound. but RUU failed:crying: and sound still not fix

see you tomorrow....good night bro
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
You don't need the full firmware to fix the sound problem.

Your getvar has mixed details - version-main is Marshmallow but the baseband is lollipop. I will give you the Marshmallow adsp first then see whether that will fix your sound problem.

If you want to change back to stock MID 0P6B62000, here is the code

echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x36\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384

For the CID - I suggest you change it to SuperCID 11111111

You can do these CID/MID changes later. Below adsp is flashable on any CID/MID (GSM)

Same how-to as the previous one for OP.

NOTE : If anyone else downloaded this 0P6BIMG.zip, you need to edit (use Notepad++) the mainver: 6.18.1400.1 to your current firmware no.

if not then your bootloader will show OS-6.18.1400.1
[One (M8) Q&A, Help & Troubleshooting] Amri.NVR:
Thank's...i will try tomorrow :highfive:

Update : it's work dude, thanks for your help:highfive:
[One (M8) Q&A, Help & Troubleshooting] internauta2000:
Hi... Same problem with sound, could your help me?

It happened after flash AICP 7.1.2 update, then restore to sense stock rom but not solve the problem...

My device fastboot getvar:

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.19.0.0000

(bootloader) version-baseband: 1.29.214500021.12G

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B10000

(bootloader) cidnum: HTC__102

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: 76df2b54

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

:confused:

UPDATE:

I solved the problem reinstalling stock firmware (I had to re-lock bootloader, my device is S-ON) then re-unlock bootloader and re-install recovery image all via fastboot.

Once done this, I reinstalled my backup from recovery... and the problem was solved, audio is back..!!! :o

-
[One (M8) Q&A, Help & Troubleshooting] tvmans:
I have no audio in phone too. I don't know if it the same issue as is being fixed on this thread, but my phone is not working either. I can use sim data, texting, but cannot make or receive calls, and no audio works.

In case this can be fixed by your flash zip file, i would ask if it is possible for one to me made that would work with my phone.

My fastboot getvar all.

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.19.0.0000

(bootloader) version-baseband: 1.29.214500021.12G

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 6.13.771.4

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B10000

(bootloader) cidnum: O2___001

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: 76df2b54

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Has the phone been modified with custom ROM, or ever s-off, change CID, flash another carrier's firmware, etc. (to the best of your knowledge)?

The main version 6.13.771.4 (which indicates the current firmware) doesn't correspond to O2, as far as I know. The "771" versions correspond to H3G carrier. Firmware numbers for O2 should have "206" such as 6.13.206.5. Unless I'm missing something, I don't see how the "771" firmware could have been installed unless it was modified with s-off, change CID, etc.
[One (M8) Q&A, Help & Troubleshooting] tvmans:
The phone started misbehaving a couple of weeks ago. Fully stock. Android 6 Marshmallow. Never modified in anyway (ROMs Firmware s-on/off) except possibly ota updates, normal user types.

HTC Sense Home would crash and I would not be able to do anything on phone. Returned to factory settings and had same issue.

Ply store would not work. I was able to get a browser by viewing the htc terms and conditions in about. then downloaded latest home sense from apk mirror. This brough some life back into the phone.

I then installed Pacs_SD_ReMix_v7 onto the phone and there is no longer any crashing. audio does not work, and phone calls do not work. sms & wifi work fine.

If I can get a o2 Ireland (bought over by 3 Ireland) firmware and ROM I'd reflash it. I didn't backup my stock flash or firmware because i believe they were corrupt.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
So the phone was never modified by you, until you started having issues. Then you unlocked the bootloader, TWRP and custom ROM?

Re-installing firmware is a good place to start, for audio issues such as the one you are experiencing. Stock signed firmware is here (with instruction on how to flash at the bottom of the same post): https://xdaforums.com/showpost.php?p=60218734&postcount=5

The question, is which one to use. AFAIK, the firmware for O2 should be 6.13.206.5, but that doesn't match what it presently says for version-main in your getvar (6.13.771.4). Presumably one or the other will work.

Bear in mind, you will need to relock the bootloader in order to flash signed firmware, and that will wipe all data on the phone (and also render it unable to boot until you restore a ROM).

After flashing firmware, unlock bootloader again, install TWRP. Then either flash a custom ROM, or you can restore a stock TWRP backup (stock ROM) of the same number firmware ended up working, using the files and instructions here: https://xdaforums.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

After that, hopefully your audio issue will be fixed.
[One (M8) Q&A, Help & Troubleshooting] tvmans:
O2 (206) was bought over by Hutchison 3 (771) in 2013. My phone was a o2 phone. I'm guessing, but i don't know, that 3 must have pushed out an OTA FW update that broke my phone.

I flashed the 6.13.206.5 FW you linked to and followed all your instructions and now the phone is perfect again.

Thanks so much for your help.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
You're welcome. I'm glad it worked.

It's interesting that the H3 firmware was able to be installed to the phone. And maybe it was intended that way. But if so, it clearly didn't work out as intended (caused the audio issue).
[Huawei Mate 9 Questions & Answers] Shtihi:
hello people.. i have the chinese version of the mate 9 MHA-AL00

and i installed the gms core and all google services worked flawlessly for a week or so.. till now!

now for somehow i cant update apps in google play store or download new ones..

what should i do? is anyone here experienced this too?

i cleaned cache and reinstalled allmost everything.. still dosent work. i gave all permissions (even in the lockscreen) but no go.

help :)
[Huawei Mate 9 Questions & Answers] kipsyprince:
We are all in the same boat its annoying this happened to me too after the B135 update got in
[Huawei Mate 9 Questions & Answers] Shtihi:
its good to know im not alone in this..

is there any workaround?
[Huawei Mate 9 Questions & Answers] magma2000:
Guys. Uninstall truecaller and Google play works.
[Huawei Mate 9 Questions & Answers] ba703863:
I tried every single way to solve the problem, including enable all the permissions for google play, enable unknown source download and install, clear cache and data in google play store and google play service, factory reset, connect to VPN, etc. restart the phone is the temporary solution.

I know US version doesn't have this problem. It is probably due to the GMS installed specifically in AL00 model.

I would recommend install third party market like apkpure, 9apps for now and wait for the update to solve this problem.
[Huawei Mate 9 Questions & Answers] magma2000:
Uninstall truecaller and it will work...
[Huawei Mate 9 Questions & Answers] ba703863:
i don't even have truecaller installed
[XDA Assist] ChivalrousKomodo27:
Hi guys, in first instance, sorry if i had a bad english.

Okay, accidentally i´ve deleted mi device´s internal storage, from TWRP so i can´t use it, i can enter to fastboot mode but i cant enter to bootloader, i´ve trying flash a clean copy of TWRP but when i finish the flash and go to ''Recovery'' option in fastboot it shutdowns, i hope that you guys can help me.

Thanks
[XDA Assist] Razvan:
Hi there,

Try to flash stock firmware first. If not working, here is the best place for your device:

[FAQ] Frequently Asked Questions For Moto X (2014) [UPDATED-05/10]

Good luck
[XDA Assist] ChivalrousKomodo27:
Thanks, iÂ´ve reflashed the stock rom via RSDLite and it worked :)
[Google Pixel Guides, News, & Discussion] kkh786:
I'm getting major throwback to my earlier AMOLED screen phones.

Just noticed my Pixel has those infamous streaks. Those used to be earlier generation AMOLED like the Galaxy Nexus. Especially visible on grey backgrounds?!

I thought manufacturers fixed these issues.

Anyone else see these?

Test to see on your Pixel use the Tapatalk app in dark mode and you will see it on the background grey.

Once you see you can't "unsee"

I just want to smoke sure I'm not a isolated case before deciding what to do about it.

Thanks.

KKH

Sent from my Pixel
[Google Pixel Guides, News, & Discussion] maulich:
I don't see any streaks on my device.....
[Google Pixel Guides, News, & Discussion] Chaos2Theory:
None at all here as well, and i develop on it so the screen is on about 9-12 hours a day at least.
[Google Pixel Guides, News, & Discussion] k.s.deviate:
Do you mean visible streaks when a black background moves across a dark blue or grey background? Almost like a trail?
[Google Pixel Guides, News, & Discussion] kkh786:
The streaks or thin black lines and are stationary in the background.. mostly seen in shades of grey.

It used to be common with older generation AMOLED screens. Manufacturing defect was the common reason.

I'm not sure what to do now as other than this issue my device is perfect. RMA will be a hassle.

Will Google send me out a device before I send the current one back?

Sent from my Pixel
[Google Pixel Guides, News, & Discussion] k.s.deviate:
Gotcha, I thought you were referring to the trail of darkness that is visible when a black background moves over a grey or blue one. This would be normal AMOLED behavior.

However stationary lines... I've never seen that before, definitely not on my Pixel. I would hope Google would send out a device first so you aren't out a phone. But expect a holding charge on the card used to purchase the device.
[Google Pixel Guides, News, & Discussion] bwheelies:
Mine has the lines. Really have to look to see them. Doesn't bother me the way it would years ago.
[Google Pixel Guides, News, & Discussion] kkh786:
I agree it doesn't bother me as much as it would in the past but I have gone for RMA. If it's the same and not worse on the replacement then I'll just live with it.

There was an interesting video by Erica Griffin where she touches on this issue. Interesting watch. ☺️

Sent from my Pixel
[Google Pixel Guides, News, & Discussion] bwheelies:
I only see it on XDA!
[Google Pixel Guides, News, & Discussion] parkman7:
I had it on my first Pixel, it was very obvious actually. Could even see it watching normal videos. I since swapped for the Pixel XL, and I still have at least one darker mark, visible when I pull down the notification panel. It is however very hard to see, I have to be looking for it so it doesn't bother me. But seems kinda weird.. my Nexus 6 never had any of those issues. (And I had 3, thank goodness for accidental coverage lol cracked the screen twice)
[Google Pixel Guides, News, & Discussion] kkh786:
My replacement is much better but there are still some streaks. However I need to look for them. They are not that obvious. I'll stick with the handset for the time being. Guess this is a side effect of AMOLED tech.

Sent from my Pixel
[Google Pixel Guides, News, & Discussion] guysalami:
RMA'd twice due to AMOLED issues (streaks/tints), on my 3rd device and same issues so I gave up and decided to just live with it. At this price point this is a bit disappointing. Had the same issues with Samsung AMOLEDs as well but was able to return them and get near flawless displays so I know that they can manufacture them to better tolerances. I'm using a screen equalizer app from the play store to overlay a transparent green area on the pink side of the display to hide it from myself which works pretty good but sucks that this is the case.
[Google Pixel Guides, News, & Discussion] kkh786:
My two Pixels didn't have any tints whatsoever. The streaks only. Current one is much better so I'm sticking with it. Never seen a perfect OLED screen. It's a perk I guess. LG P-OLED are the worst. Dirty blotches! Yuck!

Sent from my Pixel
[Upgrading, Modifying and Unlocking] gokhun:
Hello,

I installed wm6 to my p525 and now I have to downgrade it to wm5. But i can't install wm5 rom to it. How can I do this? Please help me :(
[Upgrading, Modifying and Unlocking] louco21:
do you speak french because i can help you but i'm french so it's most easy for me to explain in french!
[Upgrading, Modifying and Unlocking] fq1124:
you can directly use .nb0 rom .it can let you go back to wm5.dont use .cap its dangerous and cant work.but you boot will keep 07.....
[Upgrading, Modifying and Unlocking] gokhun:
I don't know french. But I can translate it ;) Please tell me how i can do this
[Upgrading, Modifying and Unlocking] jackleung:
Do a search on my posts. I posted this before.
[Upgrading, Modifying and Unlocking] billdownunder:
Hi guys

have a P525, originally purchased in UAE(English).

have sucessfully flashed to various WM6 Mobiz roms, v10, 18, 19 etc

now want to revert back to WM5, as PIM does not transfer, etc and many other programs (from WM5 ) do not work in WM6 environement.

Baut cannot revert back to WM5.

- downloaded various ASUS WM5 ROM, WWE, WWE ARA all versions 3.43 etc

- have tried using both bootloaders 06xxxxx and 07xxxxx

- with any official ASUS ROM, always get the following error

ROM image found :\MiniSD Card \Galaxy.cap

Language(English), is compatable with the device language(Unassigned).

then click System- Rom update , and imiditaely get the error:

ROM update cannot be applied to this regions version!

- i have also tried the ASUS.UnlockLangID ( runing this before attempting above update), but no difference, same error.

- i have also tried changing the local in system properties, to English, Arabic, Thai and reatempt falshing with ASUS WM5 roms but always get same error message as above.

PLEASE HELP

were can get .nb0 WM5 ROMs please?

Any other assitance would be apreciated, thanks guys

thanks
[Galaxy Tab S Q&A, Help & Troubleshooting] Cookiekiller:
Hi @ all,

I need a little help to upgrade my SM-T805 from 4.4.2 to 6.0.1 (T805XXU1CPH5).

I had rooted my SM-T805 in the past with this [GUIDE] How to root without tripping knox - Kitkat and Lollipop, Locked bootloader

Now my question is - It is possible to upgrade to 6.0.1 with keeping root an knox at 0x0?

And when it is possible i need some hints. :)

My first idea was to download the firmware and flash it with Flashfire but I do not know if this is the right way and whether there are certain things to consider.

Thanks in advance

Cookie

P.S.: Sry 4 my bad english, I'm a german guy ;)
[Galaxy Tab S Q&A, Help & Troubleshooting] edan1979:
I think you cannot. since mm need new bootloader. and kingroot no longer working.
[Google Pixel XL Questions & Answers] Bassem9:
Hello guys,

This is my first post but this has been frustrating me for a while.

Just a little background info:

I've had in order a Nexus 4, Nexus 5, Nexus 6p and now the Pixel XL.

It's been a while since I've fiddled around and rooted my phones... maybe my last rooted phone was the nexus 5.

Anyway, I've been wanting to use android pay for a while now on my XL.

My Pixel is a pre-order and stock out of the box I was getting the "your phone might be rooted or bootloader is unlocked" error.

At first, I thought maybe it is because I had copied my data and settings from the nexus 6p which had the bootloader unlocked and maybe that affected the pixel? unlocked the bootloader by default or smthg...

So I went ahead and put the pixel into fastboot and tried to lock the booloader... I got that the bootloader is already "LOCKED"... So what now? :confused:
[Google Pixel XL Questions & Answers] dsmitty166:
I had a similar issue. It appears that the latest OTA has broken this for some users. I ended up wiping and flashing the full factory image to solve this.
[Google Pixel XL Questions & Answers] Bassem9:
That's weird because I was on 7.1 out of the box and hadn't updated. And now on 7.1.1 and I still have the same issue.

This is just really annoying... Are there any trusted alternative apps for mobile payments?
[Huawei Nova/Nova Plus Questions & Answers] droidbot1337:
Hello, my Nexus 5 recently died (rip) and I'm looking for a replacement. I'm currently deciding between a Huawei P9 and nova. My problem is that I can't seem to find where to buy the Nova. I found a few on eBay but I'm hoping someone here could help. I'm a T-Mobile user so if anyone has some info on how the new ova works I would appreciate it. Thanks in advance for any and all help!
[Huawei Nova/Nova Plus Questions & Answers] wangdaning:
Not sure, the consumer.huawei US site does not even list it. My guess is it is not released in the US. Just make sure if you buy one you get a model that is compatible with your carriers bands. If you look at GMSarena they break down which models have which bands.
[HTC One X] grim61:
Hi,

I think I have bricked my old htc one x! I have tried to fix the issue by spending the last few days reading through and trying as many of the solutions on this site as I can but I seem to be constantly running into roadblocks in my attempt at fixing it.

Basically I had cyanogenmod on it for the last 3 years and had lent it to my mother to use (I could never get google play working but everything else was ok), after years of thinking I should really put some stock RUU on it for her, because cyanogen is different to what all her friends had and she couldn't do things in quite the same way.

I relocked the bootloader and started to install an HTC X RUU for t-mobile (first mistake - I am in australia) and this did not work, I then downloaded what I think is a compatible RUU and the battery had dropped below the minimum 30% I needed, and was slowly losing power, I tried to unlock the bootloader again so I could fix it but the battery was too low to unlock it (I tried to use "fastboot flash unlocktoken Unlock_code.bin") and the phone seemed to alternate between a restart loop and just being stuck in the bootloader.

This is the error I get when I try to unlock it

"C:\Users\laptop\Downloads\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin

< waiting for any device >

target didn't report max-download-size

sending 'unlocktoken' (0 KB)...

OKAY [ 0.138s]

writing 'unlocktoken'...

FAILED (remote: battery low)

finished. total time: 0.353s"

After researching and looking at similar issues, the only fix seemed to be to use a bat file

"@echo off

:start

fastboot getvar battery-voltage

fastboot reboot-bootloader

ping /n 6 localhost >nul

goto start

"

I've spent all day running this trying to get the phones voltage up to 3680 so I can then unlock the bootloader and put on a customer clockwork or something so the phone can charge from fastboot/bootloader or just black screen, I only need 10% I believe however the bat file works great from 2700-3500 or so, (this takes maybe 3 hours) then the bat file bombs out with errors such as

"C:\Users\laptop\Downloads\Minimal ADB and Fastboot>fastboot reboot-bootloader

< waiting for any device >

rebooting into bootloader...

FAILED (command write failed (No error))

finished. total time: 0.004s

C:\Users\laptop\Downloads\Minimal ADB and Fastboot>ping /n 6 localhost 1>nul

C:\Users\laptop\Downloads\Minimal ADB and Fastboot>goto start

C:\Users\laptop\Downloads\Minimal ADB and Fastboot>fastboot getvar battery-voltage

< waiting for any device >

getvar:battery-voltage FAILED (command write failed (No error))

finished. total time: 0.004s

C:\Users\laptop\Downloads\Minimal ADB and Fastboot>fastboot reboot-bootloader

< waiting for any device >

rebooting into bootloader...

FAILED (command write failed (No error))

finished. total time: 0.004s"

Is there any help anyone could give me ? I honestly have looked all over the place seeking a fix but am having real trouble :(

Any help would be appreciated ! :)
[HTC One X] 5m4r7ph0n36uru:
Did you at any time think of shutting the phone off, or leave it to discharge until it shuts of by itself? This way you could fully charge it as long as it is turned off, power it on holding volume down and then try to unlock again.

If you succeed you could flash the latest TWRP 3.0.2-0, and flash a CM21.1 (new layout), as well as the according GApps to obtain all needed PlayService files. If done so after a reboot you could setup a Google account and everything else. But make sure to flash ROM and GApps in one run. Don't reboot prior to flashing the appropriate GApps which would, in case of my example, be OpenGApps, ARM, 6.1 pico.
[HTC One X] grim61:
Thanks for the reply, I've managed to get it up to 3650 voltage and it then allowed me to unlock the bootloader through a combination of the bat file and charging whilst it was dead.

Now I will try and put a nandroid backup or something on it, I am having big trouble finding an RUU for vodafone australia that matches the CID:

radio. 5.1204.162.29

cid: vodap021

mid: pj4611000

main version: 3.14.862.27

Any advice here at all ?:(