Develop Bugs

[Q] Does anyone know of a way to force on USB debugging?

I have just been given an old Wildfire that is unrooted, s-on and network locked that has somehow managed to get itself into Qualcomm diagnostic mode. I am unable to get anywhere, adb - device offline. Is there anyway to force on USB debugging so that I am able to use a goldcard?

Dav1_d said:
I have just been given an old Wildfire that is unrooted, s-on and network locked that has somehow managed to get itself into Qualcomm diagnostic mode. I am unable to get anywhere, adb - device offline. Is there anyway to force on USB debugging so that I am able to use a goldcard?
Click to expand...
Click to collapse
bottom line is nope. how is the device reacting? is it just black screening with vibrations?
totally of topic but 1000 posts XD

I'm a bit confused with this diagnostic mode?
If i remember correctly i was able to go into it with vol up + power but then after a battery pull it would reboot just fine........
Maybe as Lesicnik mentioned not so long back the volume button might be stuck or faulty hence pressing the power button will equal vol up+power and start diag mode.
Sent from my GT-I9100 using Tapatalk 2

Scratch0805 said:
I'm a bit confused with this diagnostic mode?
If i remember correctly i was able to go into it with vol up + power but then after a battery pull it would reboot just fine........
Maybe as Lesicnik mentioned not so long back the volume button might be stuck or faulty hence pressing the power button will equal vol up+power and start diag mode.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
qualcomm diagnostic mode happens when you f**k up the phone so bad that it doesnt know what else to do, and reverts to what i think is the backup firmware on the nand chip? not 100% sure. it usually results in the phone powering on but not showing anything on screen. but vibrates a few times depending on what the issue is. sometimes you can "blindboot" which is where you take a stock rom.zip from a ruu and place it on the sdcard and boot to bootloader. then by using time (ie waiting) and logic (when to try push volume up to update the rom+reboot) you can sometimes manage to restore the phone. as far as i am aware the guys over at the evo 3d forum are very advanced in how this mode actually functions. the htc sensation unbricking project, which helps people fix their phones after an attempt to s-on kills it was made with the help of the evo 3d guys knowledge. also i think jupuntobear s-off puts the phone into download mode before you do the "wire trick" to drop write security. so it is possible to fix this issue but it is quite a hard nut to crack.

Scratch0805 said:
I'm a bit confused with this diagnostic mode?
If i remember correctly i was able to go into it with vol up + power but then after a battery pull it would reboot just fine........
Maybe as Lesicnik mentioned not so long back the volume button might be stuck or faulty hence pressing the power button will equal vol up+power and start diag mode.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Have already taken phone apart and checked all connections as my first thought was that something may have worked itself loose after being dropped or something.
Vol up + power and the phone buzzes/vibrates 3 times.
Managed to do a blind factory reset - vol down + power wait for a bit, then vol down etc, etc. After about 3-4 minutes I was able to push the soft buttons which light and vibrate. I am unable to do anymore than this due to usb debugging being off as I need to use adb to make a gold card and run a ruu. Thanks anyway.

heavy_metal_man said:
qualcomm diagnostic mode happens when you f**k up the phone so bad that it doesnt know what else to do, and reverts to what i think is the backup firmware on the nand chip? not 100% sure. it usually results in the phone powering on but not showing anything on screen. but vibrates a few times depending on what the issue is. sometimes you can "blindboot" which is where you take a stock rom.zip from a ruu and place it on the sdcard and boot to bootloader. then by using time (ie waiting) and logic (when to try push volume up to update the rom+reboot) you can sometimes manage to restore the phone. as far as i am aware the guys over at the evo 3d forum are very advanced in how this mode actually functions. the htc sensation unbricking project, which helps people fix their phones after an attempt to s-on kills it was made with the help of the evo 3d guys knowledge. also i think jupuntobear s-off puts the phone into download mode before you do the "wire trick" to drop write security. so it is possible to fix this issue but it is quite a hard nut to crack.
Click to expand...
Click to collapse
Thanks, will check out Evo3D forum tomorrow, hopefully someone over there will be able to help.:fingers-crossed: Btw you need to have USB debugging enabled to run jupuntobear s-off.

Dav1_d said:
Thanks, will check out Evo3D forum tomorrow, hopefully someone over there will be able to help.:fingers-crossed: Btw you need to have USB debugging enabled to run jupuntobear s-off.
Click to expand...
Click to collapse
do you know what network the phone was locked too? you could hunt for the offical ruu from that network with the 1.01.0002 hboot and try to blind boot that to restore the phone. if you can tell me the network its on i will help you hunt for the ruu 3 vibes is better than 5 as far i know. ive heard of people recovering from 3 vibes.
also, if you have access to another wildfire you can use that to make the goldcard and then use that on the damaged phone then it should run any ruu that has an equal or higher hboot ^^

heavy_metal_man said:
do you know what network the phone was locked too? you could hunt for the offical ruu from that network with the 1.01.0002 hboot and try to blind boot that to restore the phone. if you can tell me the network its on i will help you hunt for the ruu 3 vibes is better than 5 as far i know. ive heard of people recovering from 3 vibes.
also, if you have access to another wildfire you can use that to make the goldcard and then use that on the damaged phone then it should run any ruu that has an equal or higher hboot ^^
Click to expand...
Click to collapse
The phone is locked to Vodafone UK. I've just spoken to my sister whose phone it was (she's not the most technically clued up of people) and she can't remember whether she upgraded to froyo or not. She's now got a GS2 and hasn't even done the official OTA update to ICS (and Touchwizzed Jellybean is on the horizon). So I'm betting its still on Eclair, but I can't be 100% sure. I've looked on the Vodafone UK site and the latest Wildfire software version is '2.24.161.2', which they are only giving out through an OTA. I'm not having much luck googling it either.
I don't have any access to another Wildfire, so the only thing I can think of is if I can find someone else who would be so kind as to make and upload a goldcard for me :fingers-crossed: (highly unlikely), otherwise I think the phone may be taking a trip to environphone (they give £20 for a working wildfire). I'll spend another couple of hours on it, seeing what I can come up with, but it's looking bleak at the moment .

Dav1_d said:
The phone is locked to Vodafone UK. I've just spoken to my sister whose phone it was (she's not the most technically clued up of people) and she can't remember whether she upgraded to froyo or not. She's now got a GS2 and hasn't even done the official OTA update to ICS (and Touchwizzed Jellybean is on the horizon). So I'm betting its still on Eclair, but I can't be 100% sure. I've looked on the Vodafone UK site and the latest Wildfire software version is '2.24.161.2', which they are only giving out through an OTA. I'm not having much luck googling it either.
I don't have any access to another Wildfire, so the only thing I can think of is if I can find someone else who would be so kind as to make and upload a goldcard for me :fingers-crossed: (highly unlikely), otherwise I think the phone may be taking a trip to environphone (they give £20 for a working wildfire). I'll spend another couple of hours on it, seeing what I can come up with, but it's looking bleak at the moment .
Click to expand...
Click to collapse
ok i have found a vodaphone rom that is from denmark, or germany it may be enough to do it. also, the goldcard is specific to the sdcard that is used to make it buddy :/ but! although i may not have a wildfire i do have the xtc clip so i can make a goldcard for the wildfire. so if you were willing to post a small micro-sdcard to me i could make it for you i am currently uploading the rom to mediafire now. will edit this with a link asap
EDIT: ok here is the rom.zip i was talking about, rename it to pc49img.zip and try do a cold boot up to fix it.

heavy_metal_man said:
ok i have found a vodaphone rom that is from denmark, or germany it may be enough to do it. also, the goldcard is specific to the sdcard that is used to make it buddy :/ but! although i may not have a wildfire i do have the xtc clip so i can make a goldcard for the wildfire. so if you were willing to post a small micro-sdcard to me i could make it for you i am currently uploading the rom to mediafire now. will edit this with a link asap
EDIT: ok here is the rom.zip i was talking about, rename it to pc49img.zip and try do a cold boot up to fix it.
Click to expand...
Click to collapse
Nice one :good: Just about to have something to eat then I'll give it a shot. Will post how I get on in a couple of hours. Thanks again.:fingers-crossed:

Dav1_d said:
Nice one :good: Just about to have something to eat then I'll give it a shot. Will post how I get on in a couple of hours. Thanks again.:fingers-crossed:
Click to expand...
Click to collapse
no bother man, i will be in work all night so keep me posted

heavy_metal_man said:
no bother man, i will be in work all night so keep me posted
Click to expand...
Click to collapse
No joy , My girlfriend is going mad at me to get off the computer, will try again tomorrow.

Dav1_d said:
No joy , My girlfriend is going mad at me to get off the computer, will try again tomorrow.
Click to expand...
Click to collapse
OK man, looks like your going to need a gold card like.
Sent from my HTC Sensation using xda premium

[Q] Attempting to flash shipped ROM onto a Desire Z (Vodafone NL)

I need an Obi-wan here. I'm a noob -- though I've gotten a solid four day education
hacking at this problem.
My wife's Android Desire Z - Stock ROM, S-ON, got stuck looping with a failed
android.process.acore message and after trying a cache clear that didn't help
I set out to factory reset it. Figured the nuclear option would be dead simple. Nope.
Factory Reset from the Hboot menu simply froze the phone
at the HTC menu for an hour. Not good.
From there dozens of resets and reboots and fastboots would sometimes successfully boot
to my wife's setup (so nothing was reset at all), only to get stuck in the acore loop again.
I was once quick enough to put it into
airplane mode and that stopped the error message loops. YAY! I could try a reset
via software! But when I attempted
Settings > SD & phone storage > Factory data reset it rebooted to HTC screen, Vodafone
screen, HTC screen, vodafone screen. ANOTHER loop.
OK, next try was to flash the ROM with an original shipped version.
Couple forums in Dutch said the shipped ROM for the Vodafone Desire z in NL was Bravo/Froyo World Wide English
so I located this file:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_
signed.exe
and attempted reset by running that on a pc.
But the USB connection failed after the unit reset: Error 171, Error 170.
Tried installing HTC Sync AND the Universal boot drivers
and the Android Booloader Driver, as per the helpful advice from Bob Denny at Phandroid. (As a noob, I can't post links here, sorry)
And yep, I disabled anti-virus, had a fully charged phone (I'm hoping you get
the picture here -- I've done my due dilligence and googling before asking for help.) but
nada. RUU rebooted the phone, waited for the bootoader, and either the phone never pings the USB
port to say it's there or the PC doesn't see it.
FINE. I can put a PC10IMG.ZIP on the SD card and dispense with the frustration of messing with windows, right? Well, no.
I extracted ROM.ZIP from the RUU renamed it PC10IMG.ZIP and slapped it in the root
directory of the SD card. I booted to Hboot with the volume down and power buttons, chose
Fastboot and watched the the Zip load (blue verticle progress bar upper right of screen),
check it (brown progress bar upper right), then NOTHING -- back to the Hboot menu.
No error message, and no invitation to
update. Reboot takes me back to screen loop. Normal power-on does the same.
Further searches make me question if this is the right shipped ROM.
The RUU reports that I'm running version 2.42.161.22
(of what? Vision Gingerbread?) and the Bravo/Froyo WWE Rom reported itself to be version 1.59 something.
As this is an S-ON phone, I know I can't roll back to earlier ROMS, and can only install
the exact version as shipped.
So the questions I THINK I need answered:
1. Does anyone know for certain, or know where I can find out, which ROM
shipped with the Vodafone NL Desire-Z in 2010? I can get Kernel source for it at the HTCDev site,
but I see no compiled ROM there -- anything I can do with kernel source?
2. Anyone know where can I get the right PC10IMG.ZIP file to flash the unit from the SD Card? (I tried Shipped-Roms.com and
dozens of google permutations)
3. Is my methodology for flashing the SD Card right or is there anything in the
description above that lends anyone to believe my problem or solution is anything
other than the one I'm obsessing over?
Any help deeply appreciated.
Info from Hboot screen:
VISION PVT SHIP S-ON
HBOOT-0.05.0013
MICROP-0425
RADIO-26.10.51.26
eMMC-BOOT
Apr 11 2011, 23:36:27
Image CRC:
osbl: 0x1B4C7A4C
amss: 0xEF10821B
hboot: 0xCCCC4C36
recovery: 0x9627D8E8
system: 0xB6CE69CE
Please tell me I'm a stupid Noob and I've missed something so obvious I'll leave a
facepalm scar on my forehead, then tell me what it is so I can fix this dang phone and
get my life back. I'd be one appreciative noob.
-b

Try again with the PC10IMG.zip, this time don't extract the rom image, flash the entire zip. If this doesn't work you may need to make a goldcard. This means you will need to boot the phone and get into setting to turn debugging on and will will also need to get the proper window drivers up and running in order to use adb. (Try holding the s key on the key pad while powering on, this may keep the bootloop away)
Sent from my MyTouch 4G Slide using xda premium

demkantor said:
Try again with the PC10IMG.zip, this time don't extract the rom image, flash the entire zip.
Click to expand...
Click to collapse
Yeah, sorry wasn't clear I extracted the zip from the RUU, not the rom itself, so I've tried this one already.
Safe boot doesn't boot -- gets me the HTC screen and freezes there. I'll keep trying, as I think gettting debugging on and going gold card may be my only hope if the problem isn't incorrect ROM (or if there's no finding the correct one).

Here's a simpler question: If in my hboot screen I see
VISION PVT SHIP S-ON
Does that mean the shipped ROM was vision gingerbread and that's the only one to try,
or could my wife's "system updates" upgraded the phone from a Bravo shipped ROM?
And when I get a CID Incorrect error on a Vision Gingerbread ROM, does that mean the WWE Vision Gingerbread ROM I tried to install isn't good because it's not Vodafone, or because it's not the shipped ROM?
Any help will be thankfully appreciated!

Sorry it took so long to get back,
ship s-on is referring to you have a shipped bootloader and your security flags are on, that line is not specific to any version of the desire z
You won't be able to flash any ROM like that unless it is an upgrade from current version. I believe if you go to HTC website the latest ruu was not released as an ota and may work for you as its probably newer. If it doesn't work then you will need to get super cid in order to flash something older, which means you need to get adb working
Sent from my Nexus 7 using xda premium

[Q] Help needed with Desire Z

Hello,
I tried to help out a friend with rooting a Desire Z. He used the guide on http://forum.xda-developers.com/showthread.php?t=1178912. He was still on stock and everything and the guide pointed to that to do first.
According to him everything went fine untill he got at point "I - 4a) Manual Downgrade". After reviewing the files he had used it seemed to me that he had used the G2 version of PC10IMG.zip instead of the Desire Z version (could see it when inspecting how large the file was)
He told me that all other steps before (the temp rooting etc etc) was no problem. And after he rebooted his phone the install of PC10IMG started. After the first reboot however the phone stuck.
The situation now is a follows:
* phone does not boot. It gets stuck at the white screen with green HTC letters/logo and then does nothing
- S-ON
- Phone does boot into Hboot (version HBOOT-0.82.0000)
- RADIO-26.02.01.15_m2
- eMMC-boot
I can get into Fastboot and can send commands thru adb to the phone. However commands that try to flash result in a FAILED blabla signature. Probably since its S-ON status
SDcard is recognized (finally) and I managed to make it accept a stock rom. Many other .zips fail. System says no image or wrong image when searching for them.
I suspect the phone has a wrong bootloader (?) and will only accept G2 roms (wich would not be right since its a Desire Z (?)).
Things I tried so far:
* flash a stockrom: It did do something (saw the blue "loading" bar in the bootloader). After it's done it verifies and returns to the bootloader. The I reboot but it still hangs at white screen with green letters HTC/logo
* tried to flash other roms by putting then on the SD. Gives message no image or wrong image
* tried with adb with fastboot. Nothing is accepted.
Is this phone beyond DIY repairs? Advice or tips would be greatly appreciated (since this crap costed me already a full saturday and sunday)
Many thanks in advance!
(PS: I should have the basic knowledge about rooting, adb and such. Also I rooted my own desire Z succesfully already)

use THIS RUU directions will be there
now DOWNGRADE AGAIN which you already know
then follow either THE XDA WIKI or THE CYANOGEN WIKI or STRAWMETALS PDF GUIDE

demkantor said:
use THIS RUU directions will be there
now DOWNGRADE AGAIN which you already know
then follow either THE XDA WIKI or THE CYANOGEN WIKI or STRAWMETALS PDF GUIDE
Click to expand...
Click to collapse
Thanks a lot for your reply!
I tried what you suggested 3 times and this is the outcome:
The program starts up fine. Checks the phone with no errors. After a few install screens the phone reboots into a black screen with silver letters HTC (same as seen with adb/fastboot I think?). It starts wiping userdata. Then it says "busy sending"; goes all fine.
The it gets to the point sending "signature" (not sure if I translate correct. I have a dutch version or at least the install was in dutch).
And after a while I get:
ERRORCODE: 130 (model-ID error)
Get right updateapplication and retry
during install it said I had image version 1.00.000.0 and asked if want to update to 2.16.531.6
Anymore advice or sugestions I could try?
Thanks in advance for your answer!
[EDIT]
Seems I can go into some kind of recovery mode (choosing recovery from menu >> gives black screen with greenish icon >> gives red triangle
at that screen I do volume + and power and it gives me a menu in wich I can choose update from SD. Not sure if that can help me in any way? Maybe there is some .zip I can install and reset everything back to factory or something?
Tried already to select something there but gives an error:
(in yellow line) E: Can't mount /cache/recovery/command
Sounds serious tome

Then you'll need the ruu for your model phone, got to HTC.com, find support, look for desire z, then find downloads, follow same steps as before
Sent from my Nexus 7 using xda premium

demkantor said:
Then you'll need the ruu for your model phone, got to HTC.com, find support, look for desire z, then find downloads, follow same steps as before
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Tried quite a lot of RUU versions but everytime the same damn message:
ERRORCODE: 130 (model-ID error)
Get right updateapplication and retry
Tried to get unlocked bootloader with the tool from HTCdev but that gave me a message ERROR[191]: ROM not supported
Anything else I can try out? (going to try and see if I can get something of a rom thru a goldcard but my hopes dwindle by the minute
Thanks in advance for any help/advice
[EDIT]
After hours and hours of reading I can only think of 2 things myself:
1. somehow the emmc is defunct (broken or totally messed up beyond flashable)
2. it has a wrong radio version (= bricked beyond DIY repairs as far as I could read)
Therefor I descided to contact a company that can JTAG the phone and restore it to its glory. What is a reasonable price for such?
If anyone else has still some tips I'll keep watch of this thread

You can't use an older version of the software/firmware so you would need the latest from HTC, if the phone already has the latest installed then you would need a gold card to change the cid. Problem is, as far as I know, you need to at least a functioning adb access to make a gold card.
Being its hard to the version that you were running the state your phone is in, my guess you are at the latest ota, so if there was a ruu that came out for it that wasn't an ota then that will probably be the only one that works. Its a long shot, but you could call HTC (don't mention rooting just say you picked up the phone at it was like this) and ask for a link to the latest ruu so you can try and fix it, even if you're past warranty they should point you in the right direction
Sent from my Nexus 7 using xda premium

demkantor said:
You can't use an older version of the software/firmware so you would need the latest from HTC, if the phone already has the latest installed then you would need a gold card to change the cid. Problem is, as far as I know, you need to at least a functioning adb access to make a gold card.
Being its hard to the version that you were running the state your phone is in, my guess you are at the latest ota, so if there was a ruu that came out for it that wasn't an ota then that will probably be the only one that works. Its a long shot, but you could call HTC (don't mention rooting just say you picked up the phone at it was like this) and ask for a link to the latest ruu so you can try and fix it, even if you're past warranty they should point you in the right direction
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks a lot for your advice Demkantor
According to my friend he checked for OTA updates a few days ago (was his motivation in the first place to unroot and flash a custom since he was pissed that his great device didnt get much love anymore from updates and after seeing my Desire working on a custom hehe)
I checked out the RUU versions and also read that they kinda only work if it essentially updates the device (checked the site http://shipped-roms.com/index.php?category=android&model=Vision.
Tried a lot from there but only the WWE versions (CID of gsm was one of those numbers that indicated the gsm is unbranded)
For the sake of it I did make a goldcard and tried to use the extracted rom from an RUU. No luck. It sees it, sends it but fails at checking after that and returns to Hboot. Had a hope that the downgrade (step before perm root) was kinda succesful...
Gonna give it one last try with one of the none WWE versions with the lastest version number to see what it does.
I'll keep you posted!
PS: Damn I wished Gigabyte would make phones! I bet they'd put in some kind of recover rom in case the **** hits the fan hehe

T-mobile M8 best method to prepare for warranty exchange

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.

HTC One M8 - is there an idiot's guide to restoring the OS? (Marshmallow)

Phone originally on Android 4 - probably KitKat, it was bought in late 2014.
It's had two OTA upgrades, first to Lollipop, which I used without any problems until Marshmallow came along, and then I did the OTA upgrade to that, and used it without any problems for a while.
I've never done any backups, mainly because I could never get HTC Sync Manager to see my phone when I connected it to the laptop, and because I'm lazy, and a friend told me that means there's probably unwanted bits of the old operating systems still on the phone.
I recently tried to "Restart" it when I had an unresponsive app, and it went into a bootloop. At that point I managed to get it started again (in safe mode maybe? not sure, but it started working, so I ignored the problem) and used it for a few days.
Same thing happened again - bootloop. Couldn't get out of it at all. Have tried a factory reset/restore without any success (I've resigned myself to losing any data left on it).
I can still get into recovery mode, but it still won't go any further. I asked about it on this forum a few days ago and was told that the OS is probably corrupted and will need to be restored.
The bootloader screen shows:
*** Software status: Official ***
*** locked ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v51.2.2-00593-M8974_FO.1015
OS-6.12.401.4
eMMC-boot 2048MB
Dec 17 2015,14:15:48.0
My question is this:
In Recovery mode, there's a menu option to "Apply update from SD card".
Can I use this by copying OS 6.12.401.4 to the root directory of an SD card, slotting that into the phone, and selecting that option?
If I can, then what format should this be in, and what format does its name need to be in?
If I can't just do that, what's the idiot's guide to what I need to do to get the phone working again? I don't have any great desire to root it, I was quite happy just using the phone as it was, when it was working.
Any help would be appreciated!

see this post: http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
you'll find this rom file of the official STOCK Sense ROM (ATTACHED HERE IS THE DIRECT LINK, which is also present in the post above): http://forum.xda-developers.com/devdb/project/dl/?id=15489&task=get
You'll need TWRP to just install it like any other ROM, follow the installation through AROMA and that's about it.
good luck.

DL55 said:
I don't have any great desire to root it, I was quite happy just using the phone as it was, when it was working.
Click to expand...
Click to collapse
First : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
Second : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
---------- Post added at 08:22 PM ---------- Previous post was at 08:17 PM ----------
ushabuntu said:
You'll need TWRP to just install it like any other ROM, follow the installation through AROMA and that's about it.
Click to expand...
Click to collapse
He said he doesn't want to root his device. To install TWRP he needs to unlock the bootloader (a process to root a device)

DL55 said:
Phone originally on Android 4 - probably KitKat, it was bought in late 2014.
It's had two OTA upgrades, first to Lollipop, which I used without any problems until Marshmallow came along, and then I did the OTA upgrade to that, and used it without any problems for a while.
I've never done any backups, mainly because I could never get HTC Sync Manager to see my phone when I connected it to the laptop, and because I'm lazy, and a friend told me that means there's probably unwanted bits of the old operating systems still on the phone.
I recently tried to "Restart" it when I had an unresponsive app, and it went into a bootloop. At that point I managed to get it started again (in safe mode maybe? not sure, but it started working, so I ignored the problem) and used it for a few days.
Same thing happened again - bootloop. Couldn't get out of it at all. Have tried a factory reset/restore without any success (I've resigned myself to losing any data left on it).
I can still get into recovery mode, but it still won't go any further. I asked about it on this forum a few days ago and was told that the OS is probably corrupted and will need to be restored.
The bootloader screen shows:
*** Software status: Official ***
*** locked ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v51.2.2-00593-M8974_FO.1015
OS-6.12.401.4
eMMC-boot 2048MB
Dec 17 2015,14:15:48.0
My question is this:
In Recovery mode, there's a menu option to "Apply update from SD card".
Can I use this by copying OS 6.12.401.4 to the root directory of an SD card, slotting that into the phone, and selecting that option?
If I can, then what format should this be in, and what format does its name need to be in?
If I can't just do that, what's the idiot's guide to what I need to do to get the phone working again? I don't have any great desire to root it, I was quite happy just using the phone as it was, when it was working.
Any help would be appreciated!
Click to expand...
Click to collapse
You're funny.
Following is a link to HTC's official stock RUU, and instructions to flash it. This will install your phone's current firmware/software from scratch.
https://www.androidfilehost.com/?fid=24369303960687057
To flash the RUU zip file:
A. You need to put it at the root of your SD CARD and rename it to 0P6BIMG.zip (first character is a zero, and careful not to rename it to 0P6BIMG.zip.zip)
B. Turn your phone off, then start it into bootloader. It will recognize the 0P6BIMG.zip file and give you instructions in RED for proceeding forward.
C. Follow the instructions in RED to flash. You will lose all data as the RUU will format all partitions.
Cheers

shirreer said:
You're funny.
Following is a link to HTC's official stock RUU, and instructions to flash it. This will install your phone's current firmware/software from scratch.
*(link removed because I'm new)*
To flash the RUU zip file:
A. You need to put it at the root of your SD CARD and rename it to 0P6BIMG.zip (first character is a zero, and careful not to rename it to 0P6BIMG.zip.zip)
B. Turn your phone off, then start it into bootloader. It will recognize the 0P6BIMG.zip file and give you instructions in RED for proceeding forward.
C. Follow the instructions in RED to flash. You will lose all data as the RUU will format all partitions.
Cheers
Click to expand...
Click to collapse
Many before you have a similar opinion of me. Sometimes it's in a good way, but I don't like to ask, in case it isn't.
But thanks, that was an impressively quick response, and I think you've recognised how much of an idiot I am. Downloading the zip file now, and I'll report on my success/failure (delete as and when obvious) later.
Cheers!

DL55 said:
Many before you have a similar opinion of me. Sometimes it's in a good way, but I don't like to ask, in case it isn't.
But thanks, that was an impressively quick response, and I think you've recognised how much of an idiot I am. Downloading the zip file now, and I'll report on my success/failure (delete as and when obvious) later.
Cheers!
Click to expand...
Click to collapse
Well, just so we're clear, you're funny in a good good way. Keeping your sense of humor while having phone problems is hard. Also, having phone problems does not an idiot make; that makes you a welcomed member of the XDA community
Do let us know how things go on your end.

shirreer said:
Well, just so we're clear, you're funny in a good good way. Keeping your sense of humor while having phone problems is hard. Also, having phone problems does not an idiot make; that makes you a welcomed member of the XDA community
Do let us know how things go on your end.
Click to expand...
Click to collapse
Thanks, that's kind of you to say as much.
My "idiot" comment was primarily because of my utter failure to be bothered about doing any form of backup.
I blame HTC Sync Manager**, which doesn't do either sync-ing OR managing...
If it wasn't for the fact that all but the most recent of my contacts were synced to Gmail, I'd have been a lot worse off!
I fully intend to report on what happens. I can't be the only one who'd benefit from knowing a straightforward solution to this, and if it helps others too, then that has to be a good thing.
** Yes, it IS the latest version. It can't see either my M8 or my One X, which is only on Jellybean...

shirreer said:
Well, just so we're clear, you're funny in a good good way. Keeping your sense of humor while having phone problems is hard. Also, having phone problems does not an idiot make; that makes you a welcomed member of the XDA community
Do let us know how things go on your end.
Click to expand...
Click to collapse
Oh look, a working M8!
Thanks for your help, it's good to find someone who could understand my level of incompetence.
And it's also good to have a 4G phone back again. I've spent the last couple of weeks swearing at a One X with a comprehensively cracked screen. It's been hell, I tell you...

I wish to do similar, Except my CID is H3G_001, i dont seem to be able to find a version higher than 5.0 anywhere, sd card flashing method that is, does anyone know if theres a copy anywhere, i do know that 3uk is currently on MM, i just cant find it, HEEELLLPPPP, pwetty pleeaasssee

gazza35 said:
I wish to do similar, Except my CID is H3G_001, i dont seem to be able to find a version higher than 5.0 anywhere, sd card flashing method that is, does anyone know if theres a copy anywhere, i do know that 3uk is currently on MM, i just cant find it, HEEELLLPPPP, pwetty pleeaasssee
Click to expand...
Click to collapse
Well, I wouldn't be able to tell you what to do, I don't even know what a CID is when it's not being used to fight crime...
...but you might stand a better chance of attracting attention to your problem by starting a new thread about it. Make the title specific to your problem, then the problem gets seen by more people.

DL55 said:
Well, I wouldn't be able to tell you what to do, I don't even know what a CID is when it's not being used to fight crime...
...but you might stand a better chance of attracting attention to your problem by starting a new thread about it. Make the title specific to your problem, then the problem gets seen by more people.
Click to expand...
Click to collapse
Yep, and that will get me the answers i want.....

DL55 said:
Oh look, a working M8!
Thanks for your help, it's good to find someone who could understand my level of incompetence.
And it's also good to have a 4G phone back again. I've spent the last couple of weeks swearing at a One X with a comprehensively cracked screen. It's been hell, I tell you...
Click to expand...
Click to collapse
I'm glad you're all set. Enjoy your M8, you've earned it.