yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] eyeyousee:
Hold and press Power + Volume Down button until you can see the "home" & "back" touchscreen buttons blinking, wait for about 10 to 15 seconds while blinking then release Power button while keep pressing the Volume Down button, do not release volume down button wait for the phone to restart it will get you to bootloader mode (fastboot usb /recovery).

Are you sure the phone has a "STOCK RECOVERY"? I think the red text means, the RUU update is trying to change the OS version which is not possible for the RUU to do. It's downgrading the OS. If you have stock recovery. do a factory reset in hboot.

The only solution for you I think is to find a NAND backup or flash a Custom Rom.

If the phone can do fastboot, then install a custom recovery, then install a custom rom zip or a nand backup using ext-sdcard.
[One (M7) Q&A, Help & Troubleshooting] masok:
Not sure if the phone has stock recovery, but holding power button and volume down doesnt make a difference.

The touchscreen buttons never blink. The phone just reboots and Im again at the silver HTC logo screen.

Regarding flashing a custom ROM or NAND backup, Ill give that a shot, but I dont know how it will work, knowing that fastboot commands just seem to hang there and dont complete. But Ill definitely try that, thanks for the ideas.
[One (M7) Q&A, Help & Troubleshooting] masok:
Thanks so much for the info, I will try this first thing when I get home, but it looks really promising.

I dont know for sure if the fastboot commands are going to work, since even the fastboot getvar all seems to get stuck, but will sure try this.

Ill let you guys know if I have luck.

Any other ideas will be welcomed.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
it'll work... if it doesnt we'll just have to go for a lower version ruu, and if you can please copy/paste your command prompt output (like i did above), so we can see what's going on.

try to avoid unnecessary fastboot commands, when one get's "stuck", it'll just interfere with the rest of the process; usually unplugging and replugging the usb cable fixes the "stuck bootloader" (but obviously don't unplug while it's flashing!!
[One (M7) Q&A, Help & Troubleshooting] eyeyousee:
I experienced that situation before (those four corner warning) after a bad RUU. But maybe your phone is more serious than i thought!

So, the best thing is to follow the advice of the more experienced "nkk71" person here. Good Luck!:fingers-crossed:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
yeah, the 4 triangles appear after an unsuccessful ruu flash (error 51 partition update fail, i think), then you're stuck in ruu mode.

the two versions numbers appear after the "FAILED (remote: 90 hboot pre-update! please flush image again immediately)" -> the hboot (pre-update) has successfully flashed, so the previous version appears, as well as the version being flashed.... basically hboot from the new flash was successful but the second ruu.zip flash wasnt completed.

if it wasn't completed then only the red OS- line with two versions would show, if however the second flash was executed, but failed (not bypassed, failed) on some partitions, then bootloader will go into constant ruu mode until it's flashed successfully.
[One (M7) Q&A, Help & Troubleshooting] masok:
Well I just tried your suggestions, but no luck.

Fastboot commands are just not working well, they hang.

Fastboot devices works well, I can see the device.

But as mentioned before, basically everything else just hangs, so I got this:

For the commands that I ended up cancelling, I waited more than 5 minutes before doing so.

Also, the flash zip command, now gave an error, but also sometimes it just hangs there not giving any error but not working either

F:\AndroidFiles\HTC One M7 Bricked>fastboot devices
FA3C5W903875 fastboot

F:\AndroidFiles\HTC One M7 Bricked>fastboot reboot-bootloader
rebooting into bootloader... FAILED (command write failed (Unknown error))
Execution time is 2(s)

F:\AndroidFiles\HTC One M7 Bricked>fastboot oem rebootRUU
... FAILED (command write failed (Unknown error))
Execution time is 2(s)

F:\AndroidFiles\HTC One M7 Bricked>fastboot flash zip fw_6.06.401.1_custom.zip
sending 'zip'... (29596 KB) FAILED (command write failed (Unknown error))
Execution time is 2(s)

F:\AndroidFiles\HTC One M7 Bricked>fastboot devices
FA3C5W903875 fastboot

F:\AndroidFiles\HTC One M7 Bricked>fastboot reboot-bootloader
rebooting into bootloader... ^C
F:\AndroidFiles\HTC One M7 Bricked>fastboot devices
FA3C5W903875 fastboot

F:\AndroidFiles\HTC One M7 Bricked>fastboot oem rebootRUU
... ^C
F:\AndroidFiles\HTC One M7 Bricked>fastboot devices
FA3C5W903875 fastboot

F:\AndroidFiles\HTC One M7 Bricked>fastboot flash zip fw_6.06.401.1_custom.zip
sending 'zip'... (29596 KB) FAILED (command write failed (Unknown error))
Execution time is 2(s)

F:\AndroidFiles\HTC One M7 Bricked>

I'll try with some other drivers to see if it makes a difference.

Other suggestions appreciated.
[One (M7) Q&A, Help & Troubleshooting] masok:
I tried with other Windows drivers but its still the same.

Fastboot devices still sees the device, but everything else just hangs there and nothing happens.

I also tried it on a Linux machine and a Macbook (both of which dont require drivers if Im not mistaken), and its exactly the same.

The device is seen, but every command hangs there.

I will keep looking but I really dont know why the fastboot commands are behaving this way.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
ouch, that doesnt look nice at all :(

possibly something is stuck in limbo (maybe due to the failed fastboot oem lock command)

can you try

fastboot oem ?

(that should give you all the oem commands supported)

and try to boot the rom using

fastboot oem boot

^^ that **should** boot the phone then we can manually get rid of the ruu mode flag
[One (M7) Q&A, Help & Troubleshooting] masok:
Still no luck.

I dont think its because of the fastboot oem lock command, I had already tried to perform other commands before that, like getvar all, and I would get the same hang. Also, bootloader still shows UNLOCKED, so Im guessing that when I ran that oem lock, it didnt work.

Heres the output from the last commands

F:\AndroidFiles\HTC One M7 Bricked>fastboot oem ?
... (bootloader) command list
(bootloader) dmesg
(bootloader) last_dmesg
(bootloader) clearaspflag
(bootloader) refurbish
(bootloader) copyFotaBoot
(bootloader) get_identifier_token
(bootloader) checkKeycardID
(bootloader) get_tamper_flag
(bootloader) checkSbl1
(bootloader) checkHWSecurity
(bootloader) enter
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) erase_phone_storage
(bootloader) erase_nfc_record
(bootloader) gotohboot
(bootloader) resetgift
(bootloader) ats
(bootloader) eraseconfig
(bootloader) readconfig
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) readmeid
(bootloader) readpid
(bootloader) writepid
(bootloader) readcid
(bootloader) writecid
(bootloader) readimei
(bootloader) writeimei
(bootloader) readsecureflag
(bootloader) writesecureflag
(bootloader) ddr2gbh
(bootloader) ramdump2gbh
(bootloader) ddr2gstatus
(bootloader) get_temp
(bootloader) writemeid
(bootloader) clear_atsdebug
(bootloader) read_atsdebug
(bootloader) lock
(bootloader) readusername
(bootloader) writeusername
(bootloader) resethtcdebugflag
(bootloader) readredeemrecord
(bootloader) load_emmc
(bootloader) check_emmc_mid
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY
Execution time is 72(ms)

F:\AndroidFiles\HTC One M7 Bricked>fastboot oem boot
... FAILED (status read failed (Too many links))
Execution time is 36(s)

F:\AndroidFiles\HTC One M7 Bricked>fastboot devices

F:\AndroidFiles\HTC One M7 Bricked>fastboot devices
FA3C5W903875 fastboot

F:\AndroidFiles\HTC One M7 Bricked>
[One (M7) Q&A, Help & Troubleshooting] nkk71:
well something is seriously messing with your bootloader,

- from the screenshot it doesnt look like you corrupted hboot,

- you've already tried different PCs and cables, etc

but you cant seem to use any fastboot commands

does anything work?

some examples:

fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot oem last_dmesg
fastboot oem get_identifier_token
fastboot reboot-bootloader
fastboot reboot
fastboot oem boot
fastboot oem rebootRUU

i'm weirded out :confused:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
i'll have to look at that later, as i'm off for tonight, two things though

1- are you using "adb version" 1.0.32 (or some outdated one?) cause the output is somewhat different than what i usually see

2- your execution times look very long even for trivial commands, mine return something like:

OKAY [ 0.181s]

finished. total time: 0.184s

so it could be either a bad fastboot.exe or still a cable/PC/USB port problem
[One (M7) Q&A, Help & Troubleshooting] masok:
Just in case, I downloaded adb version 1.0.32 from:

http://xdaforums.com/htc-one/general/tool-updated-adb-version-1-0-32-fastboot-t2932160

Still same results.

Ill try to get some new USB cables, but I have tried with two, in different computers, so not really sure if it is related to that.

Still, it cant hurt, so Ill look into that and maybe try another pc too.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
oops, just saw this:

...
(bootloader) [2508712] Start Verify: 0
[B][COLOR="Red"](bootloader) [3555752] SD: write failed in CMD25.[/COLOR][/B]
...

i'm out of ideas, looks like it's fried

maybe someone else has any idea?

---------- Post added 10th May 2015 at 00:13 ---------- Previous post was 9th May 2015 at 23:58 ----------

@alray

any ideas?
[One (M7) Q&A, Help & Troubleshooting] alray:
(bootloader) [3555752] SD: write failed in CMD25.

and

(bootloader) [24002438] [ERR] Cmd35 polling status timed out, MCI_STATUS:
(bootloader) 0x4C0000
(bootloader) [24006906] [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [24009054] sdcc_erase, CMD35 fail
(bootloader) [24012749] emmc_erase(2704): sd_erase_sector failed!

Makes me believe its a bad emmc. Looks like the emmc can still communicate: reset & initialization of the emmc works fine, the board can read the clock rate and all other info of the emmc fine, can read random blocks without problems (see CMD17). But each time it tries to write (or erase) a block it fails (CMD25 and CMD35 error)

So yes i think its fried or like if it was stuck in some kind of "read only" mode. Not the first I see this CMD25 error in this forum but usually it comes with the CMD17/18 read error [SD_HW_ERROR].

:(

edit:

Btw that would explain why some fastboot commands are working an others not.

fastboot oem get_identifier_token for example only require to read the appropriate blocks where the data and encryption key to generate the token are stored.

fastboot oem lock will require to write to some blocks of the pg1fs partition to change the bootloader status.
[One (M7) Q&A, Help & Troubleshooting] masok:
Thats not good news, but I guess Ill keep trying, I have nothing to lose here.

Also, for some reason, there seems to be a bit of a difference with some commands now.

fastboot getvar all still doesnt complete and hangs there, but before, I had tried nkk71

fastboot flash zip fw_6.06.401.1_custom.zip

And it hanged there on the sending or would just fail.

Now it seemed to start, it sended the zip, and it started writing, but it hanged on checking custom ID.

I will keep trying

F:\AndroidFiles\HTC One M7 Bricked>fastboot devices
FA3C5W903875 fastboot

F:\AndroidFiles\HTC One M7 Bricked>fastboot flash zip fw_6.06.401.1_custom.zip
sending 'zip'... (29596 KB) OKAY
sending time = 2.446 secs
writing 'zip'... (bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
^C
F:\AndroidFiles\HTC One M7 Bricked>fastboot devices
???????????? fastboot
[One (M7) Q&A, Help & Troubleshooting] nkk71:
hate to be the bearer of bad news, but looks like the chip is now completely fried out :(

i'm guessing the hardware was degrading over time, (probably also why the first ruu failed), and has now reached eol :(
[One (M7) Q&A, Help & Troubleshooting] masok:
The ???????????? fastboot shows after running a command that hangs. If I unplug it and plug it again, or hold the power button until it restarts, I can see the device connected properly again:

FA3C5W903875 fastboot
[Android General] SupFanat:
Firstly I asked about automated turning on if the charger is plugged in. I still want to get the answer.

Is another question possible as well? Can a software be made which allows the user to set timeout for the device to turn it off?

Say, only 10 hours without charger are allowed and then the device is off to save battery but can be turned back on either manually or by plugging charger.
[Galaxy Tab S Accessories] methslushee:
found this nice deal online for SanDisk 128GB microSDXC Memory Card Ultra Class 10 UHS-I - $80 w/ free expedited shipping

Offer ends: MAY 9 '15

http://www.bhphotovideo.com/c/produ..._sdsdqui_128g_a46_128gb_ultra_micro_sdxc.html
[Galaxy Tab S Accessories] Tinderbox (UK):
Great Price i wish i was in the US, i need a couple of 128gb :(

John.
[XDA Assist] s.ctrltst:
I have a Galaxy S4 (SGH-M919V) which is the Canadian Variant (Wind/Mobilicity). I used Cyanogenmod Installer and it identified my phone as jfltecan (Canadian Variants) which is good, it got my phone rooted and CM on it but it was KitKat and CM didn't support Lollipop on jfltecan.

Therefore, I manually flashed a jfltetmo (T-Mobile) nightly-may-1st which is similar to SGH-M919V by opening up the script update file and getting rid of the "assert" code that checks if you have the correct phone and correct file. I have SGH-M919V phone and jfltetmo file. was successful and got 5.1.1 Lollipop and my sim working. Few days later, now there's multiple nightlies and I try to use the built in updater to get the most recent nightly. I download it and tap to install it, it takes me to CWM recovery, and displays the following. (Problem #1)

Finding update package...

E: unknown volume for path [@/cache/recovery/block.map]

E: Can't mount @/cache/recovery/block.map

Installation aborted.

Rebooting...

That didn't work but I had that installation zip file downloaded therefore I went to recovery and manually installed it, is displayed the following. (Problem #2)

Finding update package...

Opening update package...

Installing update...

This package is for device: jfletmo, jflte; this device is jfltecan.

(Status 7)

Installation aborted.

The status 7 can be fix by opening up the script update file and removing "assert" code but I don't want to do that for every nightly I will install. Can anyone help me to a solution to problem 1 and 2 or at least one of them. I would really absolutely appreciate it. Thank You.
[XDA Assist] jd1639:
Hi, thank you for using XDA Assist. I suppose you could edit your build.prop on your device to show the product and device that's listed in the assert line of the rom's updater.script. But be careful as flashing stuff not for your specific device can brick it.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] FalconGrey:
[Q] Unable to sync Samsung account. "sync is currently experiencing problems"

This is only happening with Contacts and Calendar on the Samsung Account Sync. All other accounts sync up fine and such.

I've tried deleting the account association and then reattaching the phone to my Samsung account. I can edit my Samsung Profile fine, but if I try to sync it keeps coming back with the "sync is currently experiencing problems" error. I have even tried deleting the contact data and cache along with contact storage data and cache to see if there was a glitch in the data causing it but no dice. Did the same to Calendar and calendar storage and same thing, no dice. This WAS working with 4.4.4 but stopped after the upgrade to 5.0.1

Unit IS a T-Mobile Note 4 910T running on StraightTalk with an AT&T Sim from my old Note 3 that died horribly. (Sadly the Note 3 went for a trip in my clothes washer and didn't survive... ) Would the fact that it is using the old Sim from an AT&T for StraightTalk have anything to do with this? It was suggested that StraightTalk would use a different Sim for a T-Mobile and have the phone run T-Mobile's network instead of AT&T but I don't know if that is true or not. I know many here know a LOT more than I ever will from my old T-Mobile MDA days so came here. (And that old beast STILL runs awesome and won't die!)

Anyone have any helpful suggestions to try? Just backed up with Kies3, also backed up with Titanium Backup Pro and have a full TWRP backup too so willing to try anything but about to give up on Samsung Account. (It's not TOO important that it is needed, just hate having SOMETHING not working right when the rest does!)
[Nexus 6 Q&A, Help & Troubleshooting] Warrior 3000:
So long time galaxy user! s3/s5 user for years. Made the jump to nexus 6 and i LOVE this thing! I will never go back to a galaxy and its bloated android!

what are some things i should know about the nexus or some little tricks?
[Nexus 6 Q&A, Help & Troubleshooting] GuestK0087:
Read the sticky threads but start here:

http://xdaforums.com/showthread.php?t=2948481

Welcome! :)
[Verizon Samsung Galaxy S6] clead23:
Whenever I record a video while playing music through the phone, (galaxy s6) the music is making a hissing sound and almost blurred out. . I'M thinking the microphone gain is too high... Anyone else having this issue and is there a solution?
[Sprint Samsung Galaxy Note 3] sammyDC:
is there a current list of 5.0+ lollipop roms in the one place (stable and running)

thx !
[Sprint Samsung Galaxy Note 3] daswahnsinn:
Are you looking for CM or TW ROMs? CM ROMs have been out and are stable; as for TW ROMS lollipop sort of just hit as an OTA but they're some ports from the S6 and Note4 out that are stable.
[Sprint Samsung Galaxy Note 3] sammyDC:
Really either...just want to play around...(learned to root and stuck on 5.0 (and as a side note wanting to learn how to go from 5.0 to 4.4) )

Thanks again.
[Sprint Samsung Galaxy Note 3] daswahnsinn:
To go back to 4.4.4 all you have to do is use Odin to flash the stock tar or just use CWM/TWRP recovery and flash a custom ROM. You wil be back on 4.4 with the 5.0 baseband.
[Sprint Samsung Galaxy Note 3] sammyDC:
Some said u couldn't go back from 5.0 to 4.4 via a simple CWM flash... i had problems doing it with gummy, fre, and various other roms. But did so with MO ARs today...interestingly (had tried 4-5 other 4.4 roms but to no available)
[Sprint Samsung Galaxy Note 3] daswahnsinn:
I haven't done a fresh flash. What I did was restore a backup, from 4.4.4, when i removed knox and a few other apks and couldn't get it to boot back up. So i assumed one could flash a rom but can't say with certainty. I hoping someone comes out with a deodex knox free stock rom soon but remaining patient. I wish i had the time to do it myself but we all know that happens.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] cotr:
the file i have is an EXE. how am i supposed to get this to run on my Hermes? when i move it to my phone, it gives me an error.

help is appreciated.
[Android Q&A, Help & Troubleshooting] ajituchiha:
Hello, I am new here so if i posted in the wrong area feel free to move the thread.

As the title suggests I want to Install a Settings.apk which i made for MT6582 in my device MT6592 because I do not have a MT6582 to test the modded Settings.apk, please help me
[Note Edge Accessories] Mr. Moe:
I received my wireless back cover a few days ago. I use it with my TYLT vu wireless charging dock..when I set the phone on there, it shows its charging when I go to bed, but when I wake up in the morning the phone is almost dead. Phone is hot but down to 18% battery.

This never happened with my Note 3. ANY help would be appreciated.
[Note Edge Accessories] cvaria:
i've had my wireless oem backplate since launch (had to import) never had an issue . the problem is probably that tylt vu charger. check your cables too

i have about 20 random qi chargers all over the place because they are so cheap. i've had the mos luck with the this

http://www.ebay.com/itm/Qi-Wireless...29239542&tpos=unknow&ttype=price&talgo=origal

see also:

http://xdaforums.com/google-nexus-5/accessories/ebay-tilted-qi-charger-review-please-t2611246
[Note Edge Accessories] christran12:
I had the same problem and it turned out that the terminal/contacts on the phone that connects to the charging cover was not making good contact. I used an X-Acto knife and bent the contact up a bit and it finally made good contact. It's been charging great ever since.

If you're look at the phone from the back, it's the two horizontal spring-pins on the left side, just under the two vertical ones (these are for the Smartcase sensors). The one's at the top-right side is for the NFC.
[Nexus 6 Q&A, Help & Troubleshooting] mrgwap:
I was just wondering if cyanogenmod 12.1 lockscreen has the ability to have the blurry see through effect
[Miscellaneous Android Development] Nikita Pro Android:
I compiled this kernel using linaro 4.8 toolchain from official LGE-D295 kernel sources and adding these some features:

Added CPU underclock to 249 & 192 Mhz (default CPU freqs is 0.3-1.2 GHz, so you need to set up underclock in Kernel Auditor)

Added support for FAST CHARGE function (disabled by default - for enable use Fast Charge)

Default governor changed to ondemand

Default I/O sheduler changed to CFQ

Added new CPU governors: interactive, conservative, pegasusQ

Added some new I/O shedulers: BFQ, SIO, SIOPLUS, FIOPS, FIFO, VR, ZEN.

Information:

Developer: Nikita Pro Android

Tester: kubarek777 (4pda)

Kernel version: 3.4.10

Device model: D295

ROM: STOCK 4.4.2

Installation:

1. Download and put to storage: >>>LINK<<< (v1.0)

2. Go to recovery and wipe cache.

3. Flash downloaded .zip and reboot.

4. Reboot again!

5. This is all.

To set up CPU frequency and another kernel parametres use: Kernel Auditor

Source code: https://github.com/NikitaProAndroid/android_kernel_lge_msm8610_l70pds/tree/master
[Miscellaneous Android Development] caxwan:
The link not available, new link please..
[Android General] flamery:
Hi Guys, I had a bit of a genius idea for an App. Anyways I have got a quote from someone who can create it for me, what I am wondering is though, how difficult do Google make it to get an app uploaded. Do I need a developer license or upfront payment etc. I don't plan on releasing anymore (not anytime soon), what sort of difficulties/costs are involved? Also how does device compatibility work, do I need to list all compatibly devices or its it just based on O/S version?
[YU Yureka Q&A, Help & Troubleshooting] kane111:
I request someone to please provide me with a link to the CM12 stock recovery of yu yureka as i soft bricked my phone yesterday and i cannot download the whole CM12 firmware restore files at the moment. thank you!
[YU Yureka Q&A, Help & Troubleshooting] ashish_zarekar:
you mean you are able to go into recovery ?

or only able to see boot logo ?

if you soft brick your mobile i have solution for it.

Dont be panic. this will work for you.

i also had broke my yureka.

first of all you need to download tools and fast boot image.

Download Fastboot image

Download Flash tool

dont worry above tool has name for kitkat but this works for lollipop also.

now extract both zip file in one folder this is necessary.

now connect you mobile in fastboot mode.

now Run flash-all.bat.

CMD will open and it will do all the stuff for you.

dont disconnect you mobile

at the last CMD will close by itself now disconnect cable and start you phone :D :fingers-crossed: :highfive:
[YU Yureka Q&A, Help & Troubleshooting] Siddhesh.K15:
http://d-h.st/oYvV