Related
Ok so I'm exhausted at this point because I can't find a fix anywhere, and am fairly certain the issue I've been having is due to my flashing a custom ROM with an incompatible Firmware or something of the sort.
The basics are I have an HTC One M7 from Verizon that was on JB when I first purchased it. I HATED Blinkfeed, but also a lot of the sense things. I had previously rooted and put a custom rom on my HTC Incredible and had a totally amazing experience.
So I ran with the M7 and custom rom for over 6 months without issue. Finally I found out that dev's had found the exploit to get rooted users up to date with the new 4.4.2 KitKat. So I read up on the flashing instructions from a couple of different sources, researched the Developers I was interested in Rom's from, and eventually flashed a Venom Rom. Well immediately my freshly wiped clean rooted, s-off phone, now running
3.1.605.1, HBoot 1.56, and supercid started having troubles. I would wipe/flash/boot run on the ROM for a few days, it would crash, I would wipe/flash STOCK/boot let that sit for a while, then wipe/flash another ROM/ boot etc.etc.
So now to the issue. I cannot get audio out of anywhere else on the phone besides just holding it up against my head. No speaker phone functionality, No headset, No ringtones, No Notification sounds, No touch sounds of any kind, ZIP, NADA. No matter what I flash STOCK/Custom ROM/XXYYzz same issue no sounds. I can place calls and get calls fine, but only if I am actually holding my phone to feel it vibrate. If I'm in a call people can hear me just fine as long as I am holding the phone to my ear and talking. If I try plugging in my headset suddenly they can't hear me, nor I them. If I try to put the phone on speaker, same thing occurs, it's almost as if we are both on mute. Then there is the strange and unusual issue of me not being able to get a single sound out of the phone. No matter what I do I can't get it to make a peep.
For days I have been trying to find a fix for this issue, to no avail. So I turn to the community and hopefully you all can be of some help!
Specs are below. Thanks in advance!
HTC One M7 Verizon
Unlocked bootloader / S-Off / Root privileges
Model: HTC6525LVW
HTC Sense V: 6
HTC SDK API: 6.17
Platform: 4.4.2
Super CID: 11111111
Baseband: 1.13.41.0109_2
Kernal: 3.4.10-Nuk.3rn3l-KK-s6
Build: 1.54.401.5
Release Keys: CL325784
Have you tried doing an ruu to conpleet stock to see if it still happens, or are you just flashing stock roms? If you do an ruu and the sound still dosent work, its more than likley a hardware issue.
cmlusco said:
Have you tried doing an ruu to conpleet stock to see if it still happens, or are you just flashing stock roms? If you do an ruu and the sound still dosent work, its more than likley a hardware issue.
Click to expand...
Click to collapse
Yes I have tried both the ODEXED and DEODEXED versions for my version/system.
It's crazy that this problem hasn't been encountered before, and/or been discussed in the search terms I have been using.
At this point I am running completely stock with the exception of being rooted and S-Off with an unlocked bootloader. If I can't find a way to wipe & restore the entire phone contents from fastboot/bootloader/ADB shell commands, I am just going to give up and reset, lock, and S-On so I can bring the phone to Verizon to get another.
This is just the last of many problems I have had with this phone since I got it. My husband has the exact same phone, and hasn't had any of the problems I've had.
I wouldn't say I am a n00b with adb and fastboot, flashing recoveries & ROM's, but I am not a coder, and really can only operate the basics without a coder's help.
Odexed and deodexed refer to roms, not ruu's. You need to do an ruu thru hboot using fastboot commands.
cmlusco said:
Odexed and deodexed refer to roms, not ruu's. You need to do an ruu thru hboot using fastboot commands.
Click to expand...
Click to collapse
My apologies, I have flashed and done so much in fastboot over the last few days my head is spinning.
I downloaded a 2.10.605.1 RUU Decrypted file, went into fastboot and downgraded my system. Hoping that the entirely different operating system would get the speakers working. NOPE
At this point I'm exhausted, tomorrow I plan on finding the thread that has the steps to get everything locked and back to stock and use the warranty for this POS. I miss my Incredible
Thank you so much for you help though, I appreciate someone responding.
Well if you did the ruu, all you need to do is take the kk ota, then use fastboot commands to lock the bootloader and then go s-on.
cmlusco said:
Well if you did the ruu, all you need to do is take the kk ota, then use fastboot commands to lock the bootloader and then go s-on.
Click to expand...
Click to collapse
That's my plan I'm downloading the needed file to remove the tampered/relocked warning before going s-on. What makes me sad is everything was fine with my phone (unlocked and all) until I broke down and decided to update to KitKat.
Thank you for being responsive to me. The first few days I was feeling very sad that no one had given any kind of response to my issue. You also were the only person who responded to another cry for help by me a few weeks back when this all started. So thank you again for being such a valuable member of this community, even when you have to repeat yourself, I'm sure, many times to those of us who are just starting to get the hand of all this information/terminology/etc. :good::good:
I posted this over in the T-Mobile M8 forums but didn't get any answers. Since the T-Mobile forums don't get much attention, I figured I would try over here in the M8 general forums...
I've got the fuzzy lens problem and I want to get the phone replaced (preferably via T-Mobile but I'll go directly to HTC if I have to). I know you can scratch off the coating on the lens and get some camera improvement but I'm not interested in that solution.
My goal: Return the phone to completely stock condition. No root, locked bootloader and preferably S-ON. I've read a few stories where HTC insisted on replacing the motherboard (with an additional full price fee) because the device was S-OFF and I don't want to go there.
Background: I used firewater to S-off the phone as soon as I got it (it was running 1.12 at the time). I have flashed the Harmon Kardon audio stuff (http://forum.xda-developers.com/showthread.php?t=2737498). I have turned off the tamper flag (http://forum.xda-developers.com/showthread.php?t=2708565). I am running the Stock+ rom which is based on 1.57 (http://forum.xda-developers.com/showthread.php?t=2716843).
My plan:
1) Reset my bootloader to locked (http://forum.xda-developers.com/showthread.php?t=2708571)
2) Wipe the phone and restore my very first nandroid backup I made with TWRP. That will get me back to unrooted 1.12 firmware but without the stock bootloader and still S-OFF. Staying with 1.12 will allow me to S-OFF again with firewater if it comes to that. If some kind of emergency came up, I'd hate to spend $25 on sunshine for a one time use on a phone that is going back to HTC forever.
3) Install the stock bootloader that matches 1.12 firmware. Not sure how to do this yet. I'm afraid I won't be able to achieve this with a locked bootloader and no root.
4) Verify everything is back to stock.
5) Set the phone back to S-ON (http://forum.xda-developers.com/showthread.php?t=2758818)
6) Run the 1.57 RUU (http://forum.xda-developers.com/showthread.php?t=2714456)
7) Proceed with the warranty exchange.
I'm not sure running the RUU is 100% necessary, but I figure it's the best bet I have to make the phone completely stock.
Questions: Is this a sane plan? Am I doing anything in the wrong order? Are there any steps that won't work because I've lost root or unlocked bootloader? Am I setting myself up for a brick anywhere?
There is a thread about doing this on a EU M8 (http://forum.xda-developers.com/showthread.php?t=2735235) but I can't tell what, if any, modifications need to be done for the USA T-Mobile version of the M8. There is talk about having to flash a firmware file twice or risk a hard brick when setting S-ON. Do I need to be worried about any of that?
Generally, when you lock bootloader, it says relocked, so they can tell. Maybe reflashing bootloader will work
Sent from my HTC One V using XDA Free mobile app
tzzeri said:
Generally, when you lock bootloader, it says relocked, so they can tell. Maybe reflashing bootloader will work
Click to expand...
Click to collapse
Thanks for the reply. This thread (http://forum.xda-developers.com/showthread.php?t=2708571) appears to give a way to avoid the relocked indicator and shows the proper "locked" text in the screenshot, so I think I am good there.
Any other advice?
I had a similar problem, only I did remove the coating. I wasn't rooted though, haven't seen the need to do so YET. I went into the store and showed the rep there what the problem was, mine wouldn't focus at all anymore. And they sent me a "new" (read refurbished) device, while I held on to mine. I was at the 4 month mark of having the phone and I didn't have insurance on it. No hoop jumping for me at all. If this happens again anytime soon I might have to fight to switch to a different phone. This is just ridiculous. I love the phone but the camera problems are insane for the price of this device. I also told them the problems popped up after I upgraded to 4.4.3 which they did but that's probably just a coincidence.
Sent from my HTC One_M8 using XDA Free mobile app
Gargamel1 said:
I had a similar problem, only I did remove the coating. I wasn't rooted though, haven't seen the need to do so YET. I went into the store and showed the rep there what the problem was, mine wouldn't focus at all anymore. And they sent me a "new" (read refurbished) device, while I held on to mine. I was at the 4 month mark of having the phone and I didn't have insurance on it. No hoop jumping for me at all. If this happens again anytime soon I might have to fight to switch to a different phone. This is just ridiculous. I love the phone but the camera problems are insane for the price of this device. I also told them the problems popped up after I upgraded to 4.4.3 which they did but that's probably just a coincidence.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Wait, you removed the coating and then went into t-mobile? I would think they would say no to a warranty exchange since you tried to do it yourself first. Get rid of the coating that is.
Sent from my HTC One_M8 using Tapatalk
I thought so also but figured it was worth a try. I did a pretty decent job removing it, and unless the person is fully aware of the issue and some of the diy fixes they won't notice.
Sent from my HTC One_M8 using XDA Free mobile app
Success
UPDATE: T-Mobile gave me a warranty replacement to fix the camera lens problem. I did get the old phone back to completely stock with locked bootloader and S-on before sending it back.
I found it was easiest to use the sunshine installer to gain temp root. You don't need to pay anything since you stop before it goes through the whole S-Off process. Just run the APK and select temp root. When sunshine shows you the next screen, you can exit out and still have root. (http://theroot.ninja/)
In the end I didn't bother with the old nandroid and keeping the exploitable version. I also had the order messed up in my initial post. Here is what worked for me:
1) factory reset the phone (in TWRP I did advanced wipe and also wiped internal storage). This step kills root. Rebooted the phone and verified it was back to factory defaults. Go through the setup wizard and skip all the steps. I couldn't find a way to bail out without going through every step in the wizard.
2) flashed stock recovery (the bootloader was unlocked and the phone was S-Off). Root is not necessary for this since it is done in fastboot. (http://forum.xda-developers.com/tmo...l/ota-recovery-ruus-firmware-dumps-t-t2852107). Rebooted the phone.
3) achieved temp root using sunshine APK
4) locked the bootloader (required before running the RUU). You must have root since you need a SU # prompt in the shell. (http://forum.xda-developers.com/showthread.php?t=2708571). I rebooted again for good measure but it's probably not necessary.
5) reset the phone back to completely stock using the latest 2.22.531.5 RUU. This step does not require root. I found it was easiest to put the phone into fastboot mode before running the RUU. (http://www.htcdev.com/devcenter/downloads)
6) Once the phone booted back up, I looked over everything and made sure it is all completely stock. Checked HBOOT said locked (not relocked) and dis not say tampered.
7) OPTIONAL - set S-On. Again root is not required since this is a fastboot command. (http://forum.xda-developers.com/showpost.php?p=52823014&postcount=2)
My actual process wasn't this streamlined. I ended up doing the RUU a couple of times because I didn't flash the stock recovery first and I didn't think the RUU installed the stock recovery right. Turned out I just didn't know what the stock recovery looked like (it was very confusing since I had never actually used a HTC stock recovery).
Thanks to the authors of the various threads I pulled info from. They are the real MVP's.
I'm done with these issues that my phone is having. It keeps locking up no matter what ROM I use or how little apps I have installed. Something has got to be wrong with my phone and it's time to bring it back to TMO for repair/replacement.
I found this link on HTC to download the RUU: http://www.htc.com/us/support/rom-downloads.html#tmobile
My question is, would this be enough to bring my phone back to stock so that they don't know I've rooted it?
Edit: Also, I just remembered about my bootloader being s-off/unlocked. Would this make a difference or would the RUU set everything back like it should?
Edit again: I found this thread: http://forum.xda-developers.com/showthread.php?t=2735235
So, would I be able to follow his instructions but change the CID to t-mob010 instead of the ones he has listed?
Nobody? I could really use some input on this, I don't want to brick my phone. I have to do this today, I can't take the lockups anymore.
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
jshamlet said:
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
Click to expand...
Click to collapse
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
ned4spd8874 said:
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
Click to expand...
Click to collapse
You are S-off, which means you do NOT have to lock the bootloader first. Most instructions for running an RUU assume you are S-on, however, which does require your bootloader to be locked. It's one of the checks that is disabled by S-off.
Also, S-off is getting harder to obtain, so unless there is a pressing reason to go S-on, it's safer to remain S-off. Warranty support could be that pressing reason.
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
ned4spd8874 said:
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
Click to expand...
Click to collapse
If you think your phone has bad hardware, then yeah, at this point you need to go ahead and S-on with the assumption that you will get a refurb - especially now that the M9 has been out a while. Who knows what you will get, though. You might even luck out and get a "new old stock" device with 4.4.2. Or, the refurb place could RUU it up to the latest. It's purely the luck of the draw.
Well this sucks. Can't get adb to recognize my phone in recovery. I can when it's booted into the system, but not recovery or the bootloader....
What a pain this is becoming!!!!!!!!!!!! I'm even trying to get into shell when the phone is booted up and sure I can do that, but I can't su! The binary isn't installed. So, what now I have to f'ing install a different ROM, s-on it and then ruu again????
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
ned4spd8874 said:
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
Click to expand...
Click to collapse
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
jshamlet said:
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
Click to expand...
Click to collapse
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
ned4spd8874 said:
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
Click to expand...
Click to collapse
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
jshamlet said:
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
Click to expand...
Click to collapse
Things are looking up! Found a ROM called something like Alex V that was stock enough to get SunShine to work. Also, I was using the original version so once I got it to run, it was giving network errors. Once I installed the latest version, that's when I got was able to go S-OFF. So, now I'm S-OFF, the bootloader is saying Official and locked so now I'm going to RUU and throw it in TMO's face!
It been a long time.. Well maybe 3years since i been on xda. I still remember how to root and flash this n that n etc... But yesterday i wanted to get started on flashing my verizon m8 onto a rom. Yeah little complicated. I tried everything to unlock my bootloader i keep getting the 172 error. Still considered S-on, So i just left that alone and tried to go #oldschool. I tried to update using htc sync manager. But I had to leave and go to the store. Left this on the computer to finish updating. came back 20-30mins later its on a black htc screen with the green line across. So i thought it was just finished But my computer had been frozed for 10mins. (ive checked the time) but Now it gotten bricked. i can only boot into hboot... Fastboot... And ruu.. But not recovery... I Already downloaded the rom, and the latest twrp recovery on my pc. But im still s-on.. I really don't got time to start from scratch and just factory reset this.. And im no longer worried about my data and shxt because i know im eventually going to losed them anyway. So right now its on fastboot. My win7 detects it in fastboot usb. So where do i go from here? Anybody? No worries though :fingers-crossed: :angel:
You can't unlock the bootloader on the VZN version by HTCDev.com, you need to s-off by sunshine, then use sunshine to unlock the bootloader.
Unfortunately, sunshine requires a working OS. So first you'll need to RUU back to working stock. http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
After that, you will need to root (think kingroot is the mot common method) then you can load the sunshine app ($25 license) to s-off and unlock the bootloader: http://theroot.ninja/
Once the bootloader is unlocked, you can load custom recovery TWRP and flash a custom ROM.
But keep in mind, there are kernel differences between the VZN version and most other M8 versions. Meaning, you will need to either flash a ROM that explicitly states it supports the VZN M8; or you can flash other ROMs, but you will need the proper kernel.
You'll want to read up in the Verizon M8 forum section, as this version has some peculiarities, as I've mentioned: http://forum.xda-developers.com/verizon-htc-one-m8
Greetings! I've been unlocked / rooted for a while using HTDEV / TWRP / SuperSU with S-ON and would like to revert back to stock just enough to start receiving OTA again... and eventually Marshmallow. Sadly, I'm getting older and would rather limp along the stock road as I don't find myself tweaking as much anymore. Some facts:
HTC One M9 AT&T US
Android 5.1
HTC Sense 7.0
2.11.502.18
*** Software status: Modified ***
***RELOCKED***
***S-ON***
I unlocked bootloader via htcdev and made sure to make a backup of my stock rom before doing anything so I have that.
What I've done so far:
-TWRP restore my stock ROM (message popped up upon completion stating that device is not rooted, do you wish to root and I chose NO)
-Found (what I think to be) correct replacement stock recovery and flashed via fastboot. It was 2.6.502.16 (Android 5.1) AT&T US stock recovery download from andromods
-"Relocked" bootloader.
Is this all I need to do? I see some walkthrough that involve using Sunshine for S-OFF along with MID/CID and RUU back to 100% stock, but do I need to do all that with all I've saved during my original unlock/root process?
I saw right away that there was an 80ish mb update already so I decided to try and install the update but it stalled out about 10% with the red "!" phone graphic.
I follow you guys quite a bit over here at xda and really dig this community. Any help would be much appreciated!
Have the same problem with my HTC one m9 but with unrooting and installing the ruu 3.35.161.12.
New Update received to android 7... It restarts and install it but until 25% comes the red triangle with the exclamation.... Need also help