yashsingh1/xdaforums huggingface dataset:
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] tearex:
if it will be still laggy like previous then no.
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] karthik km:
Next will be smoother I guess
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] KaranSuper:
Please update it with latest security patch.

I want to test it.
[Xiaomi Redmi 2 ROMs, Kernels, Recoveries, & Other ] karthik km:
wew

Really?

May be Later
[HTC Cavalier] martinctv:
I want to take 1 Alert tone from the Dopod C730, and install them in my S630. Can this be done? The alerts says, You have a message. Attached is the file, it is labeled play list 2. It was the only way that I could copy them from the C730, but although it says it is a WM file, I can't get it to play.

Thanks for your help.
[HTC Cavalier] Tranego:
try to go to \application data\sound on your dopod c730 and here you can find all the tones used for allerts not for calls.. there should be one called SMS copy it into your sd and than in your pc..
[HTC Cavalier] martinctv:
Hi, Thanks, but I tried that, it will not allow it. Copy and paste are shaded out.
[HTC Cavalier] Tranego:
hi,

well...sorry but i could specify better...so..on the windows folder options select "show hidden files and folders" and than trought the pc you can see the folder application data \sound and copy the file.

i attach the tone sms
[HTC Cavalier] martinctv:
Thanks I figured it out. I had to use total commander in order to access the folder.
[HTC Cavalier] killswitch:
Thanks a lot, would u mind posting the others as well?
[HTC Cavalier] Tranego:
hey, what do you need?
[HTC Cavalier] killswitch:
the other sounds that come with the Cavalier
[HTC Cavalier] Tranego:
here u are..... sorry for the delay
[HTC Cavalier] Tranego:
sounds dopod
[HTC Cavalier] killswitch:
No thank you I love having the ringers and sms tones :)
[HTC Cavalier] shadowmike:
thank you for sharing the sounds. Working great on the t-mobile shadow.
[Essential Phone Questions & Answers] bardochu:
I am looking for the Rom that can use with the 360 camera, does anyone know?

Thanks.
[Essential Phone Questions & Answers] tech_head:
I haven't found one that is why I will only run the factory rom with root.
[Essential Phone Questions & Answers] bardochu:
How about the LineageOS rom? someone said that's okay for the 360 camera?:confused:
[Google Pixel XL Questions & Answers] droidian1441:
I need some help because I am puzzled on what to do. The other night, I tried to change roms on my Pixel XL. I'm used to being able to just flash everything once in whatever order and be fine (it was much simpler years ago when I got started with modding).

Anyways, I flashed FireHound rom and gapps, but forgot the vendor. I flashed twrp and that put me into a bootloop. It would reboot back into recovery each time. So I reflashed Pixel Dust, the rom I was on before, since I didn't have a backup. I forgot to make one. Lol.

Flashed the vendor, rom, and twrp. Rebooted to a clean rom. However, I'm not rooted. I attempt to go back to twrp - and I can't. It goes straight to Android recovery/ no command screen. I can't get back into twrp.

Since this, I downloaded the newest factory image so I could just reflash and start over and fix it. But I cannot connect to any computer. I've tried multiple cables, multiple computers, and each time I get a "USB device not recognized" error. Device manager shows my device as "Unknown USB device (device descriptor request failed)." I've attempted to reinstall/update the USB drivers, windows won't update it because it says it's already up to date. Windows 10 is what I'm using.

So I am stuck. Can anyone help me? Or did I completely screw everything up?

Thanks in advance,

Sam
[Google Pixel XL Questions & Answers] pkelly517:
Enable USB debugging in Developer Options.
[Google Pixel XL Questions & Answers] droidian1441:
Thanks, I tried that. Still nothing different.
[Google Pixel XL Questions & Answers] pkelly517:
Do you get any response on the phone when in bootloader and USB cable is plugged in?

Have you checked to make sure that your adb/fastboot programs are at the latest revision?
[Google Pixel XL Questions & Answers] droidian1441:
I've updated the adb/fastboot versions from the sdk. I've updated the USB drivers. Or attempted to. And I get no response from the phone when in any mode.
[Google Pixel XL Questions & Answers] pkelly517:
Got any friends with a Linux machine? It's been ages since I used Windows to talk to my phone. I'll plug it in when I get home, though, to see if my phone is recognized.
[Google Pixel XL Questions & Answers] droidian1441:
No I don't. But I suppose I could set up a Linux virtual machine and try it that way. It's been a while since I've used Linux. You think it could work?
[Google Pixel XL Questions & Answers] DR3W5K1:
Yes

http://bernaerts.dyndns.org/linux/74-ubuntu/354-ubuntu-xenial-android-adb-fastboot-qtadb)
[Google Pixel XL Questions & Answers] pkelly517:
I'm not sure. I think a virtual box would still use the windows drivers. Good luck.
[Google Pixel XL Questions & Answers] DR3W5K1:
I was referring to Linux not a virtual machine. Sorry if I confused you.
[Google Pixel XL Questions & Answers] droidian1441:
No problem. Going to give Ubuntu alongside windows a shot. See if it works. Thanks for the idea!
[Google Pixel XL Questions & Answers] Siddhantroyal:
hello did you find any solution >??
[Google Pixel XL Questions & Answers] 5.1:
[MENTION=9472364]Siddhantroyal[/MENTION]

Did you try this solution: https://xdaforums.com/pixel-xl/how-to/guide-fix-mtp-driver-windows-10-t3570625

Cheers...
[Google Pixel XL Questions & Answers] Siddhantroyal:
hello thanks for responding.the issue is a little bit different with my phone.it is showing up as a usb device and not as a mobile/unknown device
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] ruev1:
Google translator

Hello,

Specialists, Try the version pa_n7000-5.1-20150628 for days now on the GT-N 7000

to load

Currently on mobile (now again) 4.1.2 Build XXLSZ (have already tried with other builds and PhilZ)

Attempt:

PhilZ- cwm6-XXLSZ-OXA-4.63.tar recorded OK !! (yellow triangle, CWM)

pa_n7000-5.1-20150628 played over SD: ERROR 7

Updater script file in Notepad ++ changed from assert to semicolon at the end of asssert.

Saved, sent to SD, Mount & Storage and so on.

Again started from SD ... Error 7 !!

Hope you can give me some tips !! Rudolf
[Desire Q&A, Help & Troubleshooting] Nouriko:
Hi All!

So I was trying to increase empty space through removing some bloatware apps, and accidentally deleted the com.mediatek app.

Now my htc Desire 620g phone doesn't proceed after htc logo, can anyone please help??:(

Any help is appreciated!!

Device Name: htc desire 620g dual sim

OS: Android 4.4.2

Root: yes, using Kingoroot

Note: Stock recovery appears in Chinese, so I don't know if there's an option to at least copy important data to external sdcard.
[Huawei P20 Questions & Answers] Bilal_687:
Hi, Guys I have a P20 that is a single sim version I with like to know It its possible to make it a dual sim version if so can you please explain me how will really appreciate it
[Huawei P20 Questions & Answers] Ephixi4:
Unless it has 2 sim readers and it's just a software lock / single sim tray, it's not possible.
[P8lite Q&A, Help & Troubleshooting] LubaCZ4:
Hello people,

My grandpa gave me his P8 lite a some time ago. I want to start using this phone now, but his account is still logged in the phone. I'm a bit worried from the factory reset protection when I hard reset the phone. Sadly, he doesn't remember the password for his G account and the number that he registered it with doesn't exist anymore.

I'm asking, if I remove his account in the phone settings (I know the pincode so I can get into the phone) and then hard reset the phone, the FRP won't trigger?

Thanks for any help/answer :)
[P8lite Q&A, Help & Troubleshooting] erayrafet:
If you remove his account from the settings, there won't be a problem.
[P8lite Q&A, Help & Troubleshooting] LubaCZ4:
Thank you! It worked
[P8lite Q&A, Help & Troubleshooting] erayrafet:
You're welcome
[Samsung Galaxy S8 Questions and Answers] ReturnAc:
My s8（G950N，Exyons 8895 cpu）always randomly reboot，I didn't open the auto reboot.... I have updated the firmware from AQH2 to AQL3 ，and the problem didn't solved.....

Anyone can help me？thx！
[Moto Z Play Questions & Answers] carolnap:
Guys i looked everywhere, i have almost 19 files of blank flash with me, i tried every file. :(

most of them i get this error

**** Log buffer [000001] 2018-04-26_17:50:55 ****

[ 0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 4.007] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.007] Check qboot_log.txt for more details
[ 4.008] Total time: 4.009s
[ 4.008]
[ 4.008] qboot version 3.40
[ 4.008]
[ 4.008] DEVICE {
[ 4.008] name = "\\.\COM4",
[ 4.008] flags = "0x64",
[ 4.008] addr = "0x61FE5C",
[ 4.008] api.bnr = "0x2932F80",
[ 4.008] }
[ 4.008]
[ 4.008]
[ 4.008] Backup & Restore {
[ 4.008] num_entries = 0,
[ 4.008] restoring = "false",
[ 4.008] backup_error = "not started",
[ 4.008] restore_error = "not started",
[ 4.008] }
[ 4.008]

Sometimes i get this error:

**** Log buffer [000001] 2018-04-26_18:50:06 ****

[ 0.000] Opening device: \\.\COM3
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 70 (0x46)
[ 0.004] ...cpu.sn = 2664816212 (0x9ed5de54)
[ 0.004] Opening singleimage
[ 0.005] Loading package
[ 0.006] ...filename = singleimage.pkg.xml
[ 0.007] Loading programmer
[ 0.008] ...filename = programmer.mbn
[ 0.008] Sending programmer
[ 0.227] Handling things over to programmer
[ 0.227] Identifying CPU version
[ 0.233] Waiting for firehose to get ready
[ 60.789] Waiting for firehose to get ready
[120.875] ...MSM8953 unknown
[120.875] Determining target secure state
[120.882] Waiting for firehose to get ready
[180.966] ...secure = no
[181.005] Waiting for firehose to get ready
[241.083] Configuring device...
[241.086] Waiting for firehose to get ready
[301.165] Waiting for firehose to get ready
[361.257] Waiting for firehose to get ready
[421.340] Waiting for firehose to get ready
[481.421] ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
[481.421] Check qboot_log.txt for more details
[481.422] Total time: 481.423s
[481.422]
[481.422] qboot version 3.40
[481.422]
[481.422] DEVICE {
[481.422] name = "\\.\COM3",
[481.422] flags = "0x64",
[481.422] addr = "0x61FE5C",
[481.422] sahara.current_mode = "0",
[481.422] api.buffer = "0x2D9D020",
[481.422] cpu.serial = "2664816212",
[481.422] cpu.id = "70",
[481.422] cpu.sv_sbl = "0",
[481.422] cpu.name = "MSM8953",
[481.422] storage.type = "eMMC",
[481.422] sahara.programmer = "programmer.mbn",
[481.422] module.firehose = "0xEEBC8",
[481.422] cpu.ver = "0",
[481.422] cpu.vername = "unknown",
[481.422] api.bnr = "0x2CD8388",
[481.422] }
[481.422]
[481.422]
[481.422] Backup & Restore {
[481.422] num_entries = 0,
[481.422] restoring = "false",
[481.422] backup_error = "not started",
[481.422] restore_error = "not started",
[481.422] }
[481.422]

i was at 7.0 and got a update *april* i just clicked and forgot that my phone was rooted, when i look back my cellphone was off . cant access bootloader...

and no blank flash help me.

OBS: used windows 10, 3.0 USB and Vmware with windows 7.

Qualcomm driver installed.

what should i do? :rolleyes:
[Moto Z Play Questions & Answers] usuario do Z play:
I get these errors too, in my case I did downgrade the oreo 8.0.0 patch from March to Nougat 7.1.1 after I was applying a patch by OTA. I had forgotten that this was how hardbrick got, lol. now I'm hoping to get the blankflash for Oreo 8.0.0 and hope to revive my Z Play.

translated from google translate
[Moto Z Play Questions & Answers] Systemlessly:
Guys, you all know that expecially on this Motorola phone you need to avoid flashing an older bootloader to apply after an OTA update. It ends with hardbrick, that is not the first time we've seen this on this forum.
[Moto Z Play Questions & Answers] carolnap:
but , my rom was 7 , so none of this bootloaders are old. i just cant find one to fix and cant understand this error what means.
[Moto Z Play Questions & Answers] echo92:
Have you you tried the blankflash here? https://xdaforums.com/showpost.php?p=73402033&postcount=181

If so and it doesn't work, or your device was previously updated to the stock 7.1.1 or 8.0 stock firmware, then you may well have to either wait for a newer blankflash or send your device for a service repair.

Generally, if you downgrade your device stock firmware, please do not use OTA updates.
[Moto Z Play Questions & Answers] carolnap:
hello, i used, it always stucked on "waiting for the firehose to come"

and then error

so if i use the oreo blankflash... ill only be able to use oreo from now on.

it that what u means?

obs: i think is stock 7.1.1
[Moto Z Play Questions & Answers] echo92:
Try the blankflash a few times, sometimes it fails to receive a response from your device (hence waiting for the firehose). Alternatively it could mean the blankflash is too old for your bootloader to rescue it (blankflashes appear to only be able to repair bootloaders that are older or as new as the blankflash supplied bootloader).

If you use the Oreo blankflash, then your bootloader would be likely updated to the Oreo bootloader. In theory, you could flash older stock firmware, but again, using OTA updates on a device with downgraded stock firmware is a really bad idea.

However, that is dependent on even if we get an Oreo blankflash, as these are leaked from internal Motorola development. As such, we're very lucky to have them...
[Moto Z Play Questions & Answers] carolnap:
can you tell me if metters that i use windows 10 or windows 7, because both give me the same error.

and when is at waiting the firehose i listen to a driver sound that is unpluggin and then pluggin ...
[Moto Z Play Questions & Answers] echo92:
Hmm, are you seeing your device present in Device Manager? It should either show up as Motorola ADB interface or perhaps fastboot addison_s, or is it showing up as Qualcomm HS_USB 9008 or similar?

Do you have the Motorola ADB drivers installed? Also, do you have driver signature enforcement disabled if you are running a 64 bit build of Windows? (one guide to disable enforcement is here: https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/ )

Also, try with the original USB Motorola cable or a high quality USB data cable. You could try the following too (credit to: https://xdaforums.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 )

Follow the below steps.

1. Keep your mobile connected using USB, obviously.

2. using one hand keep power button and volume down button pressed at same time and using other hand click blank-flash.bat file.

3. It might be possible that blank-flash.bat scritps get finished earlier, in that case, keep clicking .bat file continuously, you don't need to close previous cmd window. For me it took 5-6 run to get script detect/communicate with device. Here idea is that your mobile should get detected when you press power button+volume button while blank-flash.bat file is still executing.

4. keep trying step 3 unless you dont see below logs.

However, if you were originally on 7.1.1 then downgraded to 7.0, then took the April OTA update, depending on what 7.1.1 firmware you had, you may have to wait for the Oreo blankflash or pay for a service repair, as the blankflashes we have may be too old, and won't rescue a corrupted 7.1.1 bootloader (since downgrading stock firmware does not downgrade your bootloader in many cases. Hence, taking an old OTA - which does not check your bootloader version - corrupts your newer bootloader when the OTA flashes an old bootloader onto your device).

That being said, given you were rooted in the first place, the OTA should have failed as it detected root. What happens when you power off your device and then hold down the power and volume down keys, anything?
[Moto Z Play Questions & Answers] carolnap:
hi,

-- on device manager is showing Qualcomm HS_USB 9008

-- driver signature enforcement disabled ( ive done that)

-- original USB Motorola cable (im using this one)

-- That being said, given you were rooted in the first place, the OTA should have failed as it detected root. What happens when you power off your device and then hold down the power and volume down keys, anything?

well my cellphone shut down in the middle of update and nothing happens when i press those keys.

thanks for helping me, but i really dont know why when i finnaly get those message of waiting the firehose it get the error. it should be working right, i dont think its driver anymore...

on the 0.233 (in the picture) is where i hear the sound of driver unpluggin and the pluggin so i stop pressing vol down and power...

but nothing happens after that. even if i keep pressing the sound continue and the error is the same
[Moto Z Play Questions & Answers] echo92:
Ah, if your device shut down in the middle of the update, then that suggests a definite hard brick (presumably when the OTA attempted to flash the old April 2017 bootloader onto a 7.1.1 bootloader and corrupted the newer bootloader).

The info you've provided suggests that your device is communicating in the Qualcomm fallback mode (HS_USB 9008) to your computer, hence why you're hearing the driver sounds. However, the multitude of 'waiting for firehose' suggests that the blankflash is still not communicating properly with your device. As I understand it, when the blankflash communicates with your device, it sends over a (signed) programmer to establish a connection and to verify your device CPU and bootloader are suitable for sending over the new bootloader. If it is not suitable, the blankflash is left waiting for a reply (waiting for firehose) before timing out. That suggests the blankflashes you're using are too old for your device bootloader, especially if you're getting MSM8953 unknown, which likely points to the blankflash being unable to identify your CPU/chipset and/or bootloader and so cannot authorise the transfer.

For more info: https://github.com/openpst/sahara/blob/master/README.md

Also, here's an interesting article on firehose programmers (the part of the blankflash that authorises the transfer of the new bootloader) and why some OEMs don't want to give them out, as you could in theory compromise the bootloader security: https://alephsecurity.com/2018/01/22/qualcomm-edl-1/
[Moto Z Play Questions & Answers] carolnap:
what you means by definite hard brick, ill not able to recover even with the blankflash oreo?
[Moto Z Play Questions & Answers] echo92:
By definite hard brick, I mean you may likely need to wait for a much newer blankflash than any we have available. Hard bricks are very difficult to resolve without the correct/newest blankflashes. As I mentioned earlier, any blankflash you use can only work if it's flashing a 7.1.1 or newer bootloader onto a device that was formally updated to 7.1.1 - any blankflashes designed for 7.0 or blankflashes for older 7.1.1 builds may not work. Again, you may wish to repeat using the blankflash as sometimes it takes a few tries to get the connection working.

The Oreo blankflash should work, as that likely carries the newest bootloader available. However, I have no idea when that will be leaked, or if it will even be leaked. You may be able to find a member who knows a sympathetic Motorola engineer to get an updated blankflash from, or a factory Oreo stock fastboot ROM, but those are leaks and as such it is very difficult to know if or when they will be released.

If you need a device in a hurry, you would likely be best served by possibly paying for a motherboard replacement or buying a new device, and putting your Z Play aside in the hope there's a rescue blankflash in the future.
[Moto Z Play Questions & Answers] djdelarosa25:
What date was the security patch of Nougat that you flashed? [MENTION=741872]echos[/MENTION]97 told me that if it was the Feb 2018 one, (which was the one directly before the March and April Oreo builds), you might have been safe to update via OTA. Perhaps you flashed an older build?
[Moto Z Play Questions & Answers] carolnap:
i have this file next to the rom

BUILD REQUEST INFO:

SW Version: addison-user 7.0 NPNS25.137-24-1-4 5 release-keysM8953_10222.33.04.62R

MBM Version: C1.06

Modem Version: M8953_10222.33.04.62R

FSG Version: FSG-8953-04.81

Build Fingerprint: motorola/addison/addison:7.0/NPNS25.137-24-1-4/5:user/release-keys

VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:

System Version: 25.201.5.addison.retail.en.US

Model number: XT1635-02

Android Version: 7.0

Baseband Version: M8953_10222.33.04.62R

Build Number: addison-user 7.0 NPNS25.137-24-1-4 5 release-keys

Build Date: Thu Mar 16 08:38:42 CDT 2017

OTHER MISC VERSION INFO:

Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm

Regulatory Info (eLabel): regulatory_info_default.png

Blur Version: Blur_Version.25.201.5.addison.retail.en.US

Version when read from CPV: addison-user 7.0 NPNS25.137-24-1-4 5 release-keys

was the first update i got when i started the rom

right now i dont even knw if was april
[Moto Z Play Questions & Answers] djdelarosa25:
You didn't answer my question. You posted that you flashed back to Nougat after flashing Oreo. May I ask again, what date was the security patch of the Nougat firmware that you flashed?

EDIT: Apologies, seems like you flashed way back to 7.0. Well, if that's the case, I think there's nothing you can do but wait for the Oreo firmware to become available. If you flashed back to Feb 2018 7.1.1, this may not have been an issue.
[Moto Z Play Questions & Answers] echo92:
If that's the stock ROM they flashed, Googling the build number suggests it was March 2017. If they had formally updated to 7.1.1, their bootloader would have been at least the August 2017 build. The large disparity in firmware build versions is the likely reason they hard bricked when taking the Nougat April 2017 OTA patch. Credit to: https://xdaforums.com/moto-z-play/how-to/moto-z-play-reteu-firmware-otas-t3557917
[Moto Z Play Questions & Answers] carolnap:
i didnt flashed oreo anytime

guys, i was with a custom rom, and flashed this rom (last topic)

so i got the update after reboot the cellphone (right after flashed this rom) ok?

and then the cellphone died.
[Moto Z Play Questions & Answers] carolnap:
why 7 is a problem and not 7.1

7 is older...
[Moto Z Play Questions & Answers] djdelarosa25:
Not all 7.1.1 builds are SAFE to flash, ONLY the latest build prior to the Android version jump - in this case, the Feb 2018 patch

7.0 is way older. If you came from Oreo and flashed Feb 2018 7.1.1 Nougat, you would still have the Oreo bootloader. In this case, updating back to Oreo would work, as it is the same bootloader version. But if you flashed 7.0 and accepted an OTA, this would brick your device due to bootloader incompatibility. AFAIK, you can't skip OTA releases. You'd have to update to the next patch before the next one if your device is a few builds outdated.

I have to credit my friend [MENTION=7970352]echo92[/MENTION] here for all the knowledge. Though to be fair, I haven't completely gotten the whole idea and I ask for your help again in helping this poor fellow.
[Huawei P20 Pro Questions & Answers] szmidt344:
Hi,

I've installed from gplay an app control center.

It needs an overlay permission.

After that "displaying over other apps" is still on my notifications.. and can't be turned off.

Anyone solve this and hide?
[Huawei P20 Pro Questions & Answers] orangecroc:
Turn off banner notifications for android system?
[Huawei P20 Pro Questions & Answers] szmidt344:
Already did
[Huawei P20 Pro Questions & Answers] a500user2013:
The notification seems to persist until you tap it and open the settings, change something and then change it back and then close the settings activity
[Huawei P20 Pro Questions & Answers] ampfet:
Found a workaround and created a guide.

https://xdaforums.com/huawei-p20-pro/how-to/disable-displaying-apps-huawei-emui-8-t3795342
[Huawei P20 Pro Questions & Answers] Loragejt:
Yeah!! It worked!! Thanks!
[Huawei P20 Pro Questions & Answers] yjamal01:
Xiaomi

I have the same issue on the Mi Mix 3...this didnt work for me but I installed an app that works