yashsingh1/xdaforums huggingface dataset:
[8125, K-JAM, P4300, MDA Vario General] fone_fanatic:
are you connected to gprs by any chance? even if you are it shouldn't make thAt sound unless theres data transfer. if your not connected to gprs, not recieving/making a call or message then i'd say your phones refresh rate of the cell signal is too fast. how to change that, i don't know but could have to do with your sim card.

also u could simply turn your speakers off.

i just thought of this but do you have "Broadcast Channels" on?
[8125, K-JAM, P4300, MDA Vario General] futuresbright:
Not just me then i wondered what was going on!!

i drive a wagon with cb radio installed and what seems to be every minute or so i get the same noise.it gets worse when i connect to gprs so bad i have to turn cb off.

never had this problem with c500.

any ideas anyone?
[8125, K-JAM, P4300, MDA Vario General] vivanov:
GPRS is off. "Broadcast Channels" is disabled. Unfortunately turning off the speakers is not an options since they're essential to my work.

Hmm, do you think it could be the SIM card and a simple change of mobile service provider might fix that?

Regards,
[8125, K-JAM, P4300, MDA Vario General] fone_fanatic:
again, i'm not a pro on this topic, but if you could get a hold of another sim card from a friend and plug it into your device and see if it stops doing that then your sim card is the problem. so try a couple cards out, one from your provider and one from another provider and see what happens.
[8125, K-JAM, P4300, MDA Vario General] Sakunen:
My Qtek 9100 does this sound every 10 minutes or so. But I've experiensed that the sound disappears when I move the phone into a better location. I've found a couple of places in my room where this sound doesn't appear. Best way to find such place is to make a phone cal and then while the phone is calling just move it around and see where that annoying sound disappears.

Hope this helps you too. I can imagine that sound driving you mad, as it can be heard so often... For me 4-5 times in an hour was too much.
[Samsung Galaxy S (4G Model)] JaimeZX:
Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.

A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.

So next I restored a backup from CWM.

Unfortunately, after that the phone hangs at the initial Samsung splash screen.

Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.

In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.

My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.

Recommendations? Or am I hosed?

Thanks in advance,
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
Interesting problem. I have bricked my phone a bunch of times and have always been able to get back to at least "download Mode". The method I use to go to "Download Mode" is With the usb cable plugged into the computer only, power off the phone. If phone wont power off, or stay powered off, pull battery, then put battery back in. Now hold vol down and vol up buttons only, keep holding these buttons as you plug the usb cable into the phone. In 3 seconds the download screen should appear. I hope this helps you get your phone back.
[Samsung Galaxy S (4G Model)] ariesgodofwar:
This sounds like a time where a jig would be helpful. Any chance you can have your wife order one, and send to you? http://www.youtube.com/watch?v=D7I4dFX_iJ4

This should put you straight into download mode, and you can then flash.
[Samsung Galaxy S (4G Model)] JaimeZX:
Thanks, guys. I continued fiddling and got the phone into DL mode.

I also noted that when plugging and unplugging the phone, it would show up in zadig as "unknown device."

I tried to load the drivers on that, but (a) it still shows up as "unknown device" and (b) when I run HOC it doesn't see the phone under the list of compatible devices.

So.... still kind of stuck.

Any more ideas?
[Samsung Galaxy S (4G Model)] JaimeZX:
Oop. duplicate post
[Samsung Galaxy S (4G Model)] champ1919:
It's been awhile since I've played with the one clicks, but, "serial gadget" is what I remember seeing when I used them.
[Samsung Galaxy S (4G Model)] JaimeZX:
Right. MORE messing around later and "Serial Gadget" is it.

That said, I still think I have a driver issue. I have tried uninstalling and reinstalling the zadig-recommended drivers for Serial Gadget several times. I also tried manually installing the drivers from Super One Click.

Anyway, now when I load up HOC I get the green <<connected>> at bottom; but then sometimes it wants me to install the drivers (again) and sometimes it gets past that part, but then goes to

Flashing Kernel: 0%

...hangs there for about 10 seconds and then

Failed!

So... driver thing you think?

Thanks again,
[Samsung Galaxy S (4G Model)] Theraze:
If you reboot the phone after the 0% hanging for 10 seconds, does it go to the yellow exclamation mark screen? If so, just reflash again and you should be back to working... both my and my wife's phone always did that when I had to flash a kernel. :)
[Samsung Galaxy S (4G Model)] champ1919:
That's just another download screen that theraze is describing.
[Samsung Galaxy S (4G Model)] Theraze:
Exacatly. But the alternate download screen always came up after restarting the phone after a 'failed' flash where it stayed at 0% where it was successfully communicating through the cable. That just meant to not break the drivers or unplug anything... just reboot fast and finish up quickly. :D
[Samsung Galaxy S (4G Model)] JaimeZX:
Okay - I can definitely try that! It had not occurred to me to try and reboot the phone right then.

Question, though - when I get the "Failed!" Then HOC essentially hangs, when it says something along the lines of "ending session..." and never progresses from there. So how do you "restart quickly?" Because I have to like, close and reopen HOC. I guess I will see if it succeeds at ending the session when I reboot.

I will try it again. Strange though, sometimes HOC accepts the existing driver (I managed to DL the Samsung driver installer) and sometimes it wants to reinstall "WinUSB." does that make sense? Is the WinUSB an acceptable one?
[Samsung Galaxy S (4G Model)] TwitchyEye:
The winusb is the right driver for heimdall, it doesn't like the Samsung driver.
[Samsung Galaxy S (4G Model)] champ1919:
Samsung drivers and the one click drivers clash. Yes, uninstall Samsung completely if you want to use the one click.
[Samsung Galaxy S (4G Model)] JaimeZX:
Hm. Thanks for that - might be part of the problem.

Dunno what I did differently, if anything, but last night I tried flashing again and this time it went through! I was very glad to see the whole HOC process completed successfully!

So anyway - thanks so much for the help, guys. :)
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] SS4Luck:
So I've spent most of tonight installing and modding the hyperdrive rom on my phone and need two figure two things out.

1) what is the lock icon on the very top right?

2) is there a way to hide the signal bars? I really don't need them there

Here's a pic for references for #1
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] cinsity:
Wanam exposed.

Notification bar icons set to transparent
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] mwebb34:
Tap the lock and watch what it does
[Nexus 7 Q&A, Help & Troubleshooting] iifuzz:
I have been having issues getting the drivers to work on my PC for fastboot and adb so I tried using flashify app to flash my boot loader... Now my nexus starts up to the Google screen and a "Start" button appears at the top... If i click start, nothing happens... I can move it to recovery and boot into recovery fine.. I can also switch it to boot into the boot loader, and the boot loader seems to load ok... any ideas?
[Verizon Samsung Galaxy S III] Robc65:
My son ended up setting a screen lock pin on my cell phone and 30 minutes later he brings me the phone and tells me he can't remember the pin. I read on the verizon website that if you enter the wrong pin 5 times there will be an option to unlock the phone using my google credentials. I don't see this prompt on my phone. It's a verizon S3 running Android 4.1 something. USB debugging is not turned on and the phone has not been rooted.

Does Android 4.1 not include the option to unlock using your gmail account?

I even called Verizon and they told me I should be seeing the prompt.

I saw a few apps on the play store that claim to be able to unlock your phone via USB connection, but they only work up to version 4.0.

Worst case I know I can factory reset the phone, but I have a lot of photos on my internal storage and also don't want to lose all my text messages. I have never done a backup unfortunately.....

Is there a way around this or am I screwed? ......

Thanks in advance

Rob
[One (M7) Q&A, Help & Troubleshooting] joe7wu:
Shall we have a centralized place for discussion (or better, solutions) related to the bootloop issue happened on HTC One GPe? Apparently I'm not the only one in this situation, and having a single thread will help others to find the solution more easily.

The problems are basically having a soft bricked GPe and only bootloader is accessible. The GPe device is real, S-On, locked or relocked, with stock firmware of OS-3.58.1700.5 and HBOOT 1.54, but without a working rom.

1. flashing the GPe RUU by graffixnyc from this thread won't work because of the signature verification failure, which makes sense since it's not signed by HTC (the firmware.zip flashes through because it's signed by HTC).

2. fastboot oem unlock does not work and shows the following error:

(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.543s]
finished. total time: 0.543s

3. fastboot flash unlocktoken Unlock_code.bin fails silently, i.e. the confirmation screen does not show up on device.

4. trying s-off the device is not feasible without a working rom and unlocked bootloader.

5. fastboot boot <custom_recovery>.img fails for both CWM and TWRP:

downloading 'boot.img'...
OKAY [ 1.123s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.123s

6. fastboot erase cache and factory reset does not help.

Any other options so we could have a try? [MENTION=2605798]nkk71[/MENTION] [MENTION=3525160]SaHiLzZ[/MENTION]
[One (M7) Q&A, Help & Troubleshooting] SaHiLzZ:
Thank you for creating this thread. The same issue is happening for converted devices with relocked bootloader as well.

I'm out of options as neither fastboot oem unlock nor fastboot flash token unlock.bin are working, and without these not much to do.
[One (M7) Q&A, Help & Troubleshooting] joe7wu:
It seems like some mechanism has been changed in the latest firmware that prevents the original unlocking method.
[One (M7) Q&A, Help & Troubleshooting] BinaryFabric:
This seems to be happening more and more. I'm in the same boat. Tried to update a GPe HTC One and got stuck.

I have contacted HTC support as stated in this thread:

http://xdaforums.com/showthread.php?t=2492469&page=5

They we able to help get his up and running. Hopefully they can help me out to with out the need to pay extra charges.

I will update on the progress, but seeing as we are entering the weekend, it will probably only be next week.

I miss my phone :(
[One (M7) Q&A, Help & Troubleshooting] Stevefr:
Thanks for the thread and the clear summary. I have exactly the same issue with my stock Gpe and am anxiously waiting for a solution.
[One (M7) Q&A, Help & Troubleshooting] mderksen:
Create a new unlock_code.bin file using htcdev.com. This worked for me. I tried to use a unlock_code.bin file which i used when using Sense. This older bin-file didn't work so i tried to create a new one. This worked for me and my bootloader is unlocked now.
[One (M7) Q&A, Help & Troubleshooting] BinaryFabric:
I think he is talking about the method on the device, not from HTC Dev.

On the device, using "fastboot oem unlock" or the HTC Dev method dosent work.

As stated above the first returns an error and the .bin method shows a success message, but nothing actually happens.

This is my situation anyways.
[One (M7) Q&A, Help & Troubleshooting] SaHiLzZ:
Any one with locked, not relocked bootloader having the same issue. Wonder how Google will fix this..
[One (M7) Q&A, Help & Troubleshooting] alcaloide_:
+1 I'm having the same problem

Edit: They should make this a sticky thread for as long as the problem exist
[One (M7) Q&A, Help & Troubleshooting] The_Doctor_Who:
I am also having the same issue on my google play edition. S-On. I reflashed a stock recovery image so I could update to stock ROM. Now, I am stuck in a bootloop. I cannot reload any kind of custom recovery (I say that I can't. When I do, the phone will not boot into recovery. It just jumps to the Google screen, attempts to load the OS and then restarts). I AM able to unlock and relock using fastboot oem unlock and lock. I've attempted to reload the firmware and it seems to work (via cmd loading), but the loop process begins again. I attempted to flash a 4.3 firmware I found, but received the blue screen of nothingness when I did.

I'm lost. Possibly only solution is sending back in for repair. I just got the phone and this is annoying as heck..
[One (M7) Q&A, Help & Troubleshooting] joe7wu:
Yeah, a sticky thread will help a lot. Anyway, I'm still waiting for those people who got in touch with HTC and see how it goes. A bit worried about the fact that I'm in Canada and a friend in US bought this phone for me. Not sure how the custom support will be like in my case.
[One (M7) Q&A, Help & Troubleshooting] elisaw99:
So, a thought just occurred to me - i haven't updated any of my tools for fastboot since i originally unlocked the system a few months ago.

I am not currently at home, so i cannot check on this, but perhaps this will help others....

The current sdk tools version is 22.3 : http://developer.android.com/sdk/index.html

Could perhaps updating these tools help us re-unlock our phones?

If someone checks and tries this, and then the fastboot oem unlock command, let me know if it is simply a windows software thing.
[One (M7) Q&A, Help & Troubleshooting] BinaryFabric:
OK so I emailed HTC, they told me that because the phone was issued from Google, it was Google who was in charge of the warrenty. They gave me the Google customer care number "Google’s US hardware support number: 1.855.836.3987 they are open 24/7." just in case anyone needs it.

I just got off the phone and after talking with them I got the impression that they are aware of the problem but that there is currently nothing that they can do to fix it.

It seemed as though he was hinting at a fix in the future, possibly a flashable zip, but I dont know.

Anyways he had me go into recovery mode, and do a factory reset. I didnt even know I was able to do this. Unfortunately it didn't help.

At the end we had to set up an RMA. They are sending out a phone and then I will need to return mine. :(

Being currently in Israel they were unable to send it here, so they are going to send it to the US, and they I will send mine back from here.

Kinda sux, I was hoping for a quick fix.

Hope this helps somebody...
[One (M7) Q&A, Help & Troubleshooting] The_Doctor_Who:
Interesting. I chatted with an HTC rep this morning and I am sending the phone to an HTC repair facility in Houston. I wish Google would just do an exchange. DId they give you a hard time? Should I just call them and ask for an exchange?
[One (M7) Q&A, Help & Troubleshooting] BinaryFabric:
They didn't give me a hard time at all. They were actually pretty cool about it.

They tried to help me out, they saw they couldn't, so they said they would send me a new one. I even went as far as telling them that I was playing around with it trying to unlock and flash 4.4(not too specific of course), and that they should just give me a flashable zip to use because I could get it into RUU mode.

I'm not sure if it makes a difference but I bought the phone in August. So i guess the only real question is, is if you still have warranty.
[One (M7) Q&A, Help & Troubleshooting] The_Doctor_Who:
Thanks! I assume it is a one year warranty? My issue is that I bought it used. I wonder if they will give me a hard time about that.

---------- Post added at 03:48 PM ---------- Previous post was at 03:34 PM ----------

Well, i just got off the phone with them. I'm glad you had more success than I! The lady said she could not identify a troubleshot and, since I did not buy from them under my account, they couldn't help me.
[One (M7) Q&A, Help & Troubleshooting] elisaw99:
Huh. Interesting. Maybe i just need to call Google. I did try factory reset, but that didn't work. Probably best to do what you did and just ask for a new one to be sent, if they cannot resolve. I did buy it with my google account, so i might be in luck (I probably about when you did, around August).
[One (M7) Q&A, Help & Troubleshooting] BinaryFabric:
I would give it a shot
[One (M7) Q&A, Help & Troubleshooting] The_Doctor_Who:
Let us know how it goes! II will be sending mine to HTC tomorrow
[One (M7) Q&A, Help & Troubleshooting] Stevefr:
I just got off of the phone with Google. Rep indicated that many have been going through this problem. They are sending out a new phone right away and I will send mine back upon receiving the new one. Bought the phone in July from Google Play Store. Great customer service!
[One (M7) Q&A, Help & Troubleshooting] elisaw99:
I just got off of the phone with google support. The guy I spoke to didn't know anything about these issues with 4.4. He only tried a simple recovery with me, asking me to wipe everything and then reboot. Of course that didn't work, as it just went back into the startup loop.

So, he did an RMA with me, and I guess i will be getting a new HTC one from Google.

I did mention how i tried unlocking and relocking the system and everything in between to get this to work - he didn't seem to be concerned with such things, and simply indicated that they would replace the phone since it is still under warranty.

It is interesting to me, since Google's website suggests that all phones except the Nexus are warrantied by the manufacturer. Maybe that is an error.

Regardless, they will be sending me a new HTC one in 5-7 business days. For my own purposes, I nay not try to unlock and root again.... it is a shame not to restore the last status of the system when i had twrp. but i would rather have 4.4.

[MENTION=5576996]The_Doctor_Who[/MENTION] - good luck with yours. it's unfortunate that Google couldn't help you.
[One (M7) Q&A, Help & Troubleshooting] thebeastglasser:
I have the same-ish problem here. I just decided to relock the bootloader so I could flash the Brightstar RUU (converting from a GPe ROM), and after flashing it, I couldn't unlock the relocked bootloader.

The difference is that I actually have S-OFF, so is it possible for me to flash a pre-unlocked version of the bootloader?

S-OFF

HBOOT: 1.55.00

OS - 3.22.1540.1

Sense 5.0
[One (M7) Q&A, Help & Troubleshooting] ipfreelytech:
yes.

I just did some testing. Flash this zip in RUU mode: https://www.mediafire.com/?7do7pl987dorkbd that will give you the older hboot from 4.3

you can then use fastboot oem unlock and you are presented with the unlock screen on the phone!

afterwards flash the 4.4 firmware.zip from RUU mode: http://www.mediafire.com/download/am4jx7jbx2niilv/4.4 firmware.zip so everything matches.

this post only applies if you are s-off
[One (M7) Q&A, Help & Troubleshooting] Debizzle:
Guys I have had the same issue i just kept going back to the bootloader and kept clicking "factory reset" or "recovery" until it sticked and went on into to recovery. I had TWRP for my recovery btw!!!
[One (M7) Q&A, Help & Troubleshooting] The_Doctor_Who:
Thank you! I'm glad they were able to help you out!
[One (M7) Q&A, Help & Troubleshooting] DavidXSU:
This happened to me after I tried to flash a 4.4 ROM I was on an older sense 5 ROM because ive been at boot camp. I probably should have read more and been more careful..now I'm relocked with s-on
[One (M7) Q&A, Help & Troubleshooting] jayplusone:
This fixed it for me thanks!
[One (M7) Q&A, Help & Troubleshooting] Genzun:
I have same problem as anyone here at moment device S-ON , Hboot : 1.54 , Mainver : 3.58.1700.5 and can not unlock bootloader , i think we must wait have RUU exactly from HTC for KK 4.4 maybe appear on End of January 2014...
[One (M7) Q&A, Help & Troubleshooting] joe7wu:
According to Cult of Android, an updated version of Kitkat (4.4.1) is coming to HTC One GPe soon. Since Google is very well aware of this issue with GPe now, hopefully the new firmware will fix everything.
[One (M7) Q&A, Help & Troubleshooting] ipfreelytech:
hopefully it also fixes the Exchange email issue in 4.4. That was the deal breaker for me as i need exchange for work. Luckily I had a backup of 4.3 to revert.
[One (M7) Q&A, Help & Troubleshooting] joe7wu:
Yeah, I noticed that on all my kitkat phones as well. But luckily for me I can just disable it.
[One (M7) Q&A, Help & Troubleshooting] joeistek:
Has Anybody have a Fix??? I need help i cant afford the deductible on my AT&T insurance
[One (M7) Q&A, Help & Troubleshooting] idealz:
*bumping this thread..

I have a similar but not as devastating situation here as well....

I had a gpe S-off/unlocked bootloader, but I sent my htc one back for warranty repair (usb was not recognizing my phone, phone wasn't charging, all sorts of problems related to the usb connection). What I got in return was a S-on/1.54 hboot/android 4.4 gpe....

so fastboot oem unlock doesn't work... but I at least have a working rom to be able to use the phone....

what are my options to get unlocked bootloader/root/s-off??

I can't unlock the bootloader unless I have S-off since android 4.4 ruined oem unlock... most s-off methods need root to get s-off.... but I can't get root without an unlocked bootloader...

tried the temproot method with firewater s-off.... failed... can't achieve temproot.....

any help is appreciated
[One (M7) Q&A, Help & Troubleshooting] idealz:
Bump
[One (M7) Q&A, Help & Troubleshooting] SaHiLzZ:
None at the moment