yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] koreiryuu:
Lol, I wasn't going to open it, just hypothetically supplying that if the hardware was the problem and I was determined to get it fixed, would that be the only option? But don't worry, I'm not going to do any more damage than I must ;)

The first time around I didn't pay attention to the info pouring into the command prompts, so I missed the unable to mount bits. The second time around and from now I'll make sure to pay attention report any information that seems off.

I completed what you told me. During "Format" I kept getting "Unable to mount '/cache'", and when I went to advance wipe the wipe kept failing and giving the same "Unable to mount /cache" message. The five selects were Dalvik Cache, Data, System, Cache, and Internal Storage. The Dalvik Cache is what kept making the advance wipe fail, when it was no longer selected (but everything else was), the wipe would succeed.

I otherwise followed the instructions decided to try and flash the Guru ROM anyway and this time no unable to mount messages, though I will say that it restarted itself (when it was finished maybe?) and I can't be 100% sure there weren't any error messages before the restart. The phone is now boot looping like it did before, but when I get it successfully shut off (I'll wait 10 minutes to make sure the splash doesn't pop up), holding vol. down + power just starts the boot loop again instead of starting bootloader.
[One (M7) Q&A, Help & Troubleshooting] Seanie280672:
you will need to hold down the volume down and the power button together whilst the lights on the bottom flash 10-15 times, when they stop flashing, release the power button, but continue to hold down the volume down, it should go to bootloader now.

Try using the format cache option in TWRP (next to clear Dalvik-cache). This is because fastboot erase cache formats cache into an unreadable format for whatever reason.
[One (M7) Q&A, Help & Troubleshooting] koreiryuu:
Alright.

-Reflashed twrp recovery.

-Wipe/Format data - Everything formatted successfully, no unable to mount or other odd messages

-Reboot to recovery

-Wipe/Slide to Factory Reset - Everything formatted successfully, no odd messages

-Advance wipe/Select everything - Absolutely no problems, no unable to mount messages, no failed messages, everything successful

-I completely re-downloaded the Guru ROM from the original link you supplied me, deleting the old one, and flashed it, unplugging my phone, selecting the [Wipe data partition] option, Stock recovery, and Stock Radio options. Installation reaches 100% without any negative messages whatsoever.

When the Guru ROM finishes flashing, the phone resets itself and goes back into a constant boot loop.
[One (M7) Q&A, Help & Troubleshooting] Seanie280672:
that's very strange, all I can think to do is try and reflash the original firmware, see if that correct it, download and put in the same folder as abd and fastboot, plug your phone into the computer and put it into fastboot USB mode, open a command window from that folder and type these commands.

firmware: http://www.androidfilehost.com/?fid=23501681358543602

fastboot oem rebootRUU
fastboot flash zip 5.12.502.2.firmware.zip
fastboot flash zip 5.12.502.2.firmware.zip - yes twice

make sure you get a successful message at the end, if any other message, do not restart your phone, it will brick.

take note of HTC's typo, it says after the flash, FAIL: please flush image again immediately, what they meant to say was please FLASH image again immediately, that's why twice.

after, you will need to reboot to bootloader and then into recovery and try and flash the guru reset again.
[One (M7) Q&A, Help & Troubleshooting] koreiryuu:
Let me take a post to reiterate how appreciative I am of you taking the time to help me through this. I really am truly grateful.

I will update when I get a chance to go through the process you described.
[One (M7) Q&A, Help & Troubleshooting] koreiryuu:
It failed the first time without giving me the "flush again" message. I figured that since it didn't give me the proper message that things were not happening the way expected, but I flashed it twice just to say I followed instructions. I've attached an image. Ill try to keep the device plugged in and on until you reply. Please advise.
[One (M7) Q&A, Help & Troubleshooting] koreiryuu:
Since my last message, I used my command prompt and "fastboot reboot-bootloader" to get back to bootloader, flashed twrp again and formated/advance wiped/factory settings, redownloaded the 5.12.502.2.firmware.zip and redid the process and got the exact same results as my last post. I went back to twrp because it will turn my screen off and conserve battery while I wait for a reply.
[One (M7) Q&A, Help & Troubleshooting] clsA:
The Android-info fail message means your phone is not the correct one

you can edit the android-info.txt to match your phone in 7zip (open in 7zip right click and edit the info.txt)

is you phone modelid: PN0712000

cidnum: CWS__001 ?

is your bootloader locked / relocked / unlocked ?

when flashing the firmware
[One (M7) Q&A, Help & Troubleshooting] koreiryuu:
Its modelid is PN07120 (I'm guessing the other two 0s are placeholders)

cidnum is indeed CWS__001

Bootloader is *TAMPERED* and *UNLOCKED*

This is what the file android-info displays all in one line without any linebreaks or whatnot:

modelid: PN0712000

cidnum: CWS__001

mainver: 5.12.502.2

btype:1

aareport:1

hbootpreupdate:3

What should I change?
[One (M7) Q&A, Help & Troubleshooting] clsA:
have you posted your fastboot getvar all ?

I didn't see it.

I have never had the 5.12.502. firmware or the Guru Reset fail so I'm kind of at a loss of what you should do next.
[One (M7) Q&A, Help & Troubleshooting] koreiryuu:
I'll edit my original post to include the fastboot getvar all info.
[One (M7) Q&A, Help & Troubleshooting] Seanie280672:
edit your first post again and remove your imei and serial number from your fastboot getvar all, its very dangerous to post them.

did you check the md5 of the firmware you downloaded, theres no reason for it to fail other than a bad download, your output matches the firmware details.
[One (M7) Q&A, Help & Troubleshooting] clsA:
Yes edit and remove serial no and IMEI from getvar results

I can't imagine getting a corrupt download of just 24mb but did you md5 check your downloads before trying to flash them ?
[One (M7) Q&A, Help & Troubleshooting] koreiryuu:
Excuse me. Though I am tech savvy and competent, I am ignorant in the way of the mobile device. It has been edited, thank you for the warning.

I do not know what that means. However, I will say I am aware of two things.

A. When I try to change or edit a file in that firmware.zip (like when I try to edit/delete the android-info.txt), the zip prevents me saying "This archive is corrupted", however, when I right-click and "repair this archive", the new .zip it creates let's me edit the files just fine. I haven't actually tampered with the files, but because of the post saying that android-info may have incorrect information, I played around and learned what I'd have to do. I've tried flashing the zip with the original .zip, the "repaired" .zip, I've tried redownloading the firmware.zip three times and trying to flash it from the original download folder (C:/.../[username]/Download), redownloading and flashing from my Desktop, and then a third time back into the adb folder. I don't know how to md5 check my downloads, but I'll Google it and figure it out.

B. Is it just me or does there seem to be a large number of users in this forum with an HTC One M7 doing this exact same thing? Is a new update bricking these phones? Remember, I wasn't running any 3rd party apps, no custom roms, I wasn't even rooted.. I hadn't dropped my phone recently, had it splashed with liquid, nor anything else out of the ordinary. It just seems weird this would randomly happen to my device.

EDIT:

I used Google to learn about md5 checksums. I redownloaded the firmware again just to be safe, moved it to my adb folder, then md5 checked the file. I've attached the image to show all of this: The md5 checksums match. I went back into rebootRUU and tried reflashing just to make sure and the same message, which I guess I expected. Please advise.
[One (M7) Q&A, Help & Troubleshooting] clsA:
Humm I'm not sure what's going on

here's the last firmware flash i did
[One (M7) Q&A, Help & Troubleshooting] koreiryuu:
Yep, see yours has a reason next to "FAILED" (remote: 41 model id check fail) so you could resolve the issue. Mine just says (99 unknown fail). Does that mean unresolvable? Any kind of debugger that can give me specifics on why exactly it's failing?
[One (M7) Q&A, Help & Troubleshooting] clsA:
your reason is android_info fail

it seems with your hboot 1.57 and the hboot in the firmware being the same

it's failing instead of overwriting it. HTC has been changing a lot of things recently and if this is the way things are going to continue I'll probably move to another phone.

Your stuck for 2 reasons ... you didn't s-off and HTC is changing the rule's on how you can flash and update your device. The Guru Reset has worked for me on a few phones and I really don't know why it's failing on yours.

Theirs a thread on fixing a active command line overflow

maybe the recovery in it will allow you to flash the Guru reset

Here's the thread

[FIX][GUIDE][INFO][01-JUN-2014]M7 "Active Cmdline Overflow" error
[One (M7) Q&A, Help & Troubleshooting] Seanie280672:
the problem with active cmdline overflow is it tends not to work on HBOOT 1.55 and above, and as he's s-on, he cant downgrade, most users are having to downgrade to 1.44 to get it to work, this one is definatly a strange can of worms.
[One (M7) Q&A, Help & Troubleshooting] koreiryuu:
I am presuming that I am not going to be able to get my phone to s-off?
[One (M7) Q&A, Help & Troubleshooting] Seanie280672:
not without a working rom on it, unless you take it to a shop that can hardware s-off it for you by java-card.

s-off on hboot 1.57 is very difficult by software.

have you tried a custom rom, sorry I cant remember.
[One (M7) Q&A, Help & Troubleshooting] clsA:
It would be possible to s-off if you could get recovery / rom / and a kernel installed
[One (M7) Q&A, Help & Troubleshooting] smokeytime420:
have you tryed running a ruu.exe from the computer

1.) Go to Fastboot

2.) Run the commands

fastboot oem lock

fastboot reboot-bootloader

fastboot oem rebootRUU

3.) Run the RUU

The first command locks your bootloader (allowing RUU), the third command allows the RUU to run on your phone without having to actually boot all the way (normally it just boots into this screen for you).

When looking for your ruu make sure u get the one for your service provider also with the same android and sense version otherwise it will never work I went through 5 or 6 ruus before I found the right one make sure it's an exe file as well I'm running on sprints htcone m7

O ya I dosnt matter if your s-off or not my phone has it on right now and I'm using viper one 6.2.18

The ruu puts you back to stock but it should b working again
[One (M7) Q&A, Help & Troubleshooting] Seanie280672:
there is no ruu for his phone which is why he's having to use the guru-reset file, the confusion is why that guru reset file or the firmware.zip isn't flashing correctly, I suggest you read the whole thread first. :good:
[One (M7) Q&A, Help & Troubleshooting] smokeytime420:
i did

I actually did read the whole thread if I didn't think this would matter I wouldn't have posted to waste everyone's time I have seen ruu.exe for all variants of the HTC one I had to find one for sprint which was a pain in the butt but I found it it just takes some searching and I tryed the method y'all were trying and I never got it to work I found forums with plenty of other questions not mentioned here but I like the variety of users this one has and response time

I have had the same issue this is what I did to fix the issue and managed to get my phone running the way I wanted it to afterwards
[One (M7) Q&A, Help & Troubleshooting] Seanie280672:
trouble is, without s-off, you can only flash current version or the next version up, you cant just flash any ruu whether its for your phone or not, it must be one or the other.

when flashing firmware, and s-on, you cant skip 6 steps like from 2.x.xxx.xx to 5.x.xxx.xx this would lead to a hard brick, you must follow suit 2x 3x 4x 5x 6x, as each ruu contains a firmware file, you can only flash current version or the next step up.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
there has been successful repairs with S-On, even on hboot 1.57, but still no real solution what factors allow which recovery to boot

but anyway, i doubt he has the active cmdline overflow problem

isn't bootloader still unlocked? (and he has to flash the signed firmware, not the one he 'repaired')
[One (M7) Q&A, Help & Troubleshooting] smokeytime420:
heres everything that happened to me

Ok so u can understand where I'm coming from I installed a custom Rom as soon as I got my HTC one didn't like the Rom so managed to get it back to the stock Rom through an older ruu (all this was with s-on as well I have never turned this off) this was when Android 4.4.3 first came out for sprint after the updates I rooted the phone no problem I started installing a custom Rom and some how instead of installing itself it wiped almost everything on my phone the only thing I could do was get into fastboot and bootloader nothing else well as I said it took some time and a lot of research and I found another ruu method other than the way ur doing it but it's as I said it took me a while too find all the right items also to b sure to check the md5 on the download I did come across some fake ones

After finding the right ruu for the exact Android and sense versions of my phone did it work I still have all the ruu's I used but not everyone uses sprint also I'm new so I can't add urls to my messages otherwise I'd give him the sites I found all the ruus
[One (M7) Q&A, Help & Troubleshooting] Seanie280672:
what your saying is you flashed the same software/firmware that was already on your phone, a custom rom doesn't change that, for instance, my firmware is 5.11.401.10, if I flash a custom rom which is built on the newer firmware which is 6.06.401.x although its based on that firmware, it wont actually physically upgrade my firmware, only the rom, my actual device firmware will remain as 5x, its not possible to back flash whilst s-on and if you managed it then I know of a 100 dev's who would love to hear how you did it.
[One (M7) Q&A, Help & Troubleshooting] smokeytime420:
Everything I said I've done is what I did everything u said I understand but everything I've told you is what has happened to me I'm actually using the phone as we speak if what I did seems odd sorry but that's the easiest way I could put it but that was everything I've done it actually took me 4 to 5 months to get my phone up and running again I went to a lot of different forums even in this one a few times but this issue wasn't really touched on to much when I first messed up my phone it took awhile but I found what I was looking for and here I am

I have a bad habbit of trying out experimental versions of apps and roms so think that's what happened the first time around this time I used a more stable version of the Rom I wanted

Try the htc1guru website he has some ruu.exe just make sure u find the right one before trying to install it on ur phone
[Nexus 5 Q&A, Help & Troubleshooting] toprock23:
Hey all. My current setup is the Latest PA 4.43. Franco R57. Baseband M897A-2.050.1.16. I'm constantly getting dropped calls and I'm not sure where to go from here. I've already tried updating PRL and updating profile. Should I try an older radio? Flash diff kernel?
[Nexus 5 Q&A, Help & Troubleshooting] simms22:
maybe its just your area? all areas cant be 100% great, there are areas with a bad/terrible signal:angel:. but trying other things wont hurt. if youre undervolting, it can affect it.
[Nexus 5 Q&A, Help & Troubleshooting] fergdizzle9090:
would a kernel affect calls in anyway? i just flashed stock 4.4.4 and r57 franco and cant make any calls and my bars drop to 0 when i try to. hmmm
[Android Q&A, Help & Troubleshooting] law16:
I've been flashing for some time now starting with the g1 and recently have ran into a string of problems with my Samsung devices and this KNOX bs...now my HTC devices have been always golden. Even when restoring to factory image for warranty its been very quick or easy with the help of great developers here on XDA.....was planing on getting a note 4 but from the looks of it Knox and Samsung are not to friendly with the flashing community I'm guessing I should stick to HTC? Or is there a better choice for me
[8125, K-JAM, P4300, MDA Vario General] paulorosa:
Cyber.VoiceCommander.v1.61.Build.601061

http://www.pxdxa.com/read.php?tid=13826
[8125, K-JAM, P4300, MDA Vario General] brins0:
Ahem, no warez...

Read the rules...
[Xperia Z2 Q&A, Help & Troubleshooting] RevolverForce:
I flashed the wrong rom on my Xperia Z2, I tried fixing it by flashing tft file, but I couldn't even get the device into flashmode (Power + Vol up), It just never vibrates, when I put it in the charger it just keeps blinking red.

What's the proper fix for this? and is this a soft-brick or hard-brick? Please help.
[Xperia Z2 Q&A, Help & Troubleshooting] stanley08:
Flashmode is not Power button + Volume up. But...

Connect USB to ur computer

Then Hold the Volume Down key on your phone while u connect the USB Cable to the phone.

If you successfully get to flashmode, then u can flash an FTF file for ur phone. (This will also wipe internal sd files if you don't untick 'data' under wipes) Then again, phone might not boot properly if you don't wipe as u said something about custom ROM.

OR Follow these steps I found on Sony website

1. Download the PC Companion software from http://www.sonymobile.com/gb/tools/pc-companion/

and install it on your PC.

2. Install and open PC Companion then select Support Zone.

3. Phone Software Update.

4. Start.

5. Repair Phone

6. Continue

7. Accept data removal

8. Next

9. Wait for prepare

10. Select Phone

11. Follow the connection steps
[Xperia Z2 Q&A, Help & Troubleshooting] RevolverForce:
Tried using flashtool with Vol down buut

18/058/2014 23:58:26 - ERROR - Drivers need to be installed for connected device.

18/058/2014 23:58:26 - ERROR - You can find them in the drivers folder of Flashtool.

I'm sure that I have the drivers installed as I tried earlier today to unlock the bootloader through flashtool (which didn't really work out) and it recognized the device just fine.

right now it doesn't even show the Sony logo..I'll try PC Companion method in seconds..

Edit:PC Companion is asking me to make sure that the battery level is above %80, when I was flashing the new rom, the battery level was around %50, should I care about this, or is it just an extra precaution? because I don't really see a way for me to know the battery level.
[Xperia Z2 Q&A, Help & Troubleshooting] stanley08:
I'm sure 50% is enough to install through PC Companion unless ur battery is bad.

And do you by anymeans use windows 8? If you do, Did you disable driver signature while installing Flashmode, Fastboot and Z2 drivers from the C:\Flashtool\drivers folder, or where ever u installed flashtool to.
[Xperia Z2 Q&A, Help & Troubleshooting] RevolverForce:
I believe I didn't disable driver signature, I connected the device to a different usb port too just to be sure, my OS is windows 8.1.

PC Companion is updating the phone right now, I'll see how it turns out and report back to you, thanks.

Edit:It worked, my phone is alive, thank you, stanley <3
[Xperia Z2 Q&A, Help & Troubleshooting] stanley08:
There's no keeping that Bad Boy down! :D Cheers mate! :)
[Asus Padfone X and S] davietr:
Has anyone, that has rooted, tried using xposed modules on this device? If so, how well is it working? Thanks
[Asus Padfone X and S] Agent:
I'm using it now and it works just fine
[Asus Padfone X and S] ghost0001:
I installed Xposed with these modules: Greenify, Play Store Fixes, RootCloak, XuiMod, YouTube AdAway, and YourTube. All work execpt XuiMod so far. I tried the hardware torch(flashlight) option and it failed. I am looking more into it and if I find out more I will update.
[LG Optimus Black] Krystalik23:
my cellphone have no signal, i can't call o send sms, but 2g/3g works, how can it be? what can i do? :confused: :crying:

i tried by changing rom, even with cyano, it doesn't work. Actually i have (again) the default rom
[LG Optimus Black] androcraze:
So, you changed from what to what?

Sounds like a radio issue.
[LG Optimus Black] Krystalik23:
I changed from stock to cm10.1 and again stock, but it has not worked from the first stock.

What should i do?
[LG Optimus Black] androcraze:
Normally it's the other way around (SMS & Talk good, 3G screwed); that's an APN settings issue.

I wondering if this is a SIM card issue or an IMEI number issue. Your carrier can't connect you if they can't identify your phone.

Dunno. Damn odd. Have you contacted your carrier to see if they can even see your phone?
[T-Mobile LG G3] aimfire72:
Hi, I've noticed that my screen seems to have a warmer color tone to it, along with an slight overall yellow tint. You can see it best on light gray colors. I also had an AT&T model for a few days (returned) and that phone had a cooler, overall blue tint to it. You could really see the difference with the phones side by side. I've talked to friends with a AT&T and a Verizon version, they said their screens have the cooler toned blue tint.

So what tint is your screen, if any?

I'm wondering, maybe Tmobile just calibrates their screens for the warmer look... or is there something wrong with mine? Thanks.
[T-Mobile LG G3] YiZK:
Settings > Accessibility > Color Adjustment

turquoise circle over camera is the best setting for me.
[T-Mobile LG G3] aimfire72:
Yes, but what was the screen tone before you did that?
[T-Mobile LG G3] aimfire72:
OK... no one here today? lol

So I just went to T-Mobile store to compare, side by side... The screens are their demo phones actually looked worse than mine, almost a green tone to them and not nearly as bright. One thing for sure, they did not have the blueish tint to them, was more of a green/yellow. I'm beginning to think that since every carrier seems to have messed around with the software so much, they probably also adjusted the screen calibrations as well. I'm going to check at the Verizon store and another T-Mobile just to verify
[T-Mobile LG G3] Derekwolfee:
Mine is t-mobile and bright white.. The nexus 5 had the same issue, 2 different screen manufacturers one with a warmer almost yellow screen and the other blue cooler feel.. I've been lucky with both my nexus 5 and g3 both are bright white screens and no yellow. You could try swapping it and hope you get a better screen.
[T-Mobile LG G3] shook187:
Why with every new phone release this topic comes up? We know every screen's not made the same, some is warm some are cool.
[T-Mobile LG G3] aimfire72:
Because when people pay $600+ for a new phone that's main feature is the screen, they want to make sure nothing is wrong with theirs.