Develop Bugs

[Q] Bell desire Z 2.3.3 Bricked My Phone

I installed this update last night and it straight up bricked my phone. Starting with volume down and doing a hard factory reset leaves the phone hung on the white screen with HTC on it.
The phone is covered under warranty and I'll be getting a box shipped to me to send it in for repair. It is the 6-8 week turn around on the repair that troubles me.
The following briefly flashes on the screen when loading up that volume down / power screen:
SD Checking…
Loading…[PC10DIAG.zip]
No image!
Loading…[PC10DIAG.nbh]
No image or wrong image!
Loading…[PC10IMG.zip]
No image!
Loading…[PC10IMG.nbh]
No image or wrong image!
Knowing this, is there anywhere I can download these files and place them onto the SD card to see if I can't unbrick this thing myself? I am a technical person (java developer) and I have done BB development in the past but haven't done any android type work.
I just don't want to go without my phone for 8 weeks if this is a simple software restoration exercise.

Check out this thread:
http://forum.xda-developers.com/showthread.php?t=842495&highlight=brick
If you cannot execute the suggested method, post exact details of what you did, and have experienced, in that thread. Hopefully someone will be able to assist you. That should be the best place to start.
Good Luck!

From the thread posted above I think I'm screwed. This phone was stock, I've never bothered doing anything with it.
Vision PVT SHIP S-ON
HBOOT-0.05.0009
MICROP-0425
RADIO-26.06.02.25_M2
eMMC-boot
Dec 13, 2010,14:30:18
Since I've never rooted the phone or enabled usb debugging adb is just saying "error: device not found"
I would post this in that thread but it won't let me.
Is there anything I can do? I'll continue reading the rest of that thread.

I would call customer support and demand a supplementary phone or threaten to cut your service. If they won't hook you up with a rental during the time you're apart from your phone that THEIR update broke, then IMO, they're not worth your business.

Try q&a in the android development section. Make sure to provide all info.
bagadonitz said:
From the thread posted above I think I'm screwed. This phone was stock, I've never bothered doing anything with it.
Vision PVT SHIP S-ON
HBOOT-0.05.0009
MICROP-0425
RADIO-26.06.02.25_M2
eMMC-boot
Dec 13, 2010,14:30:18
Since I've never rooted the phone or enabled usb debugging adb is just saying "error: device not found"
I would post this in that thread but it won't let me.
Is there anything I can do? I'll continue reading the rest of that thread.
Click to expand...
Click to collapse
Sent from my Synergy Rom using XDA App

bagadonitz said:
I installed this update last night and it straight up bricked my phone. Starting with volume down and doing a hard factory reset leaves the phone hung on the white screen with HTC on it.
The phone is covered under warranty and I'll be getting a box shipped to me to send it in for repair. It is the 6-8 week turn around on the repair that troubles me.
The following briefly flashes on the screen when loading up that volume down / power screen:
SD Checking…
Loading…[PC10DIAG.zip]
No image!
Loading…[PC10DIAG.nbh]
No image or wrong image!
Loading…[PC10IMG.zip]
No image!
Loading…[PC10IMG.nbh]
No image or wrong image!
Knowing this, is there anywhere I can download these files and place them onto the SD card to see if I can't unbrick this thing myself? I am a technical person (java developer) and I have done BB development in the past but haven't done any android type work.
I just don't want to go without my phone for 8 weeks if this is a simple software restoration exercise.
Click to expand...
Click to collapse
There is a pc10img of the gingerbread update that may unbrick your phone as long as it wasn't on it already, because this one's build number is lower and your bootloader wouldn't accept it being s-on
Sent from my HTC Vision using XDA App

If possible, try contacting HTC's support and see if they can send you a PC10IMG.zip file you can put on your SD card.

HTC support just defacto sent me to Bell Technical support.
Bell Technical support is supplying me with a replacement smart phone while mine is in for this warranty "repair". I was just hoping to avoid the process entirely.
Admittedly I'm very green when it comes to all the lingo (rooted/unrooted, etc) so I'm afraid I'll make things worse by attempting to fix this myself unless I can find a specific solution to my problem.
Any of the threads that have been recommended won't let me post until I have 10 posts but I'll get there eventually.
Thanks.

PaganAng3l said:
There is a pc10img of the gingerbread update that may unbrick your phone as long as it wasn't on it already, because this one's build number is lower and your bootloader wouldn't accept it being s-on
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Where would I go about getting it? How would I get it onto the phone seeing that it is s-on and doesn't seem to get picked up by adb? What about the rest of the files it is complaining are missing or wrong image?

bagadonitz said:
Where would I go about getting it? How would I get it onto the phone seeing that it is s-on and doesn't seem to get picked up by adb? What about the rest of the files it is complaining are missing or wrong image?
Click to expand...
Click to collapse
it should flash a proper pc10img, just pull your sdcard, pop it in a pc and copy the pc10img to the root and pop it back in. someone with a little more knowledge would have to point you towards the right pc10img tho. not my expertise there..
Sent from my HTC Vision using XDA Premium App

You're stock on bell canada right? What version of android did you have before the brick?
Sent from my HTC Vision using XDA App

Honestly, I don't know. It was stock as I have never tried to replace it but I believe there was a previous update of 2.2 sometime between when I bought it and when this latest update came down on Friday.

probably was the 1.34 version then, i don't recall bell ever pushing the 1.82(?) version of 2.2. i don't recall the exact version of 1.34 though =(

I'm having trouble finding a full bell canada ruu, I know I'm just not looking in the right place. Everything you've described can be fixed by reflashing the software.... if only you had s-off and supercid this would be a cakewalk
Sent from my HTC Vision using XDA App

Thanks for the effort. I'm such a newb that I'm really not much help.
Rots me that this happened. I've never messed with the phone so far as I'm concerned the update they pushed out should have worked flawlessly as it appears to have for many many other people.
I had to have my phone in for service to get the screen replaced back in December (that was my own fault). I wonder if they had to do anything with the software at that time that made it incompatible with this latest update.

PaganAng3l said:
I'm having trouble finding a full bell canada ruu, I know I'm just not looking in the right place. Everything you've described can be fixed by reflashing the software.... if only you had s-off and supercid this would be a cakewalk
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Bell pushed out a Froyo update on March 30. Here is the thread: http://forum.xda-developers.com/showthread.php?t=1145163&highlight=bell
Could this be the solution?

David Dee said:
Bell pushed out a Froyo update on March 30. Here is the thread: http://forum.xda-developers.com/showthread.php?t=1145163&highlight=bell
Could this be the solution?
Click to expand...
Click to collapse
I purchased my DZ the day it was launched by bell and it had 666.5 so I am assuming that is the version Bagadonitz has.

I got the phone a couple days after the bell launch and I've installed everything that came down since.
I'm real nervous about trying anything here unless I can get specific instructions. I'm a technical person but haven't done anything with phones before and I'm a little reluctant to jump in on my own

bagadonitz said:
I got the phone a couple days after the bell launch and I've installed everything that came down since.
I'm real nervous about trying anything here unless I can get specific instructions. I'm a technical person but haven't done anything with phones before and I'm a little reluctant to jump in on my own
Click to expand...
Click to collapse
It should be quite simple: Place the OTA on your SD card and launch it through the phone's bootloader. You enter bootloader by shutting down the phone, holding the volume down and power button at the same time. If you have "fast boot" enabled, then you have to do a battery pull and then turn on with the volume down.
I would wait for PaganAng3l to confirm that the OTA (that is associated with the thread I posted above) would work with s on and a non-rooted phone.

About "bootloader", here is an excerpt from gtrab's DZ easy rooting guide, located here http://forum.xda-developers.com/showthread.php?t=835777:
1.- What is "Bootloader" ??
The Bootloader is a firmware management tool included on every stock ROM, it lets you reset to factory default, use "Fastboot" to flash official images, or launch the Recovery utility.
From the Bootloader you can also check your S-ON or S-OFF state, your firmware and Radio version, etc.
You don't need root or S-OFF to enter the Bootloader because every HTC phone has it.
2.- How do I enter the Bootloader ??
Power off your phone, then, hold the volume down key and the power key.
(You need to disable "Fast boot" from Settings -> Applications, or remove the battery to really power off the Desire Z. Otherwise, power off will just hybernate the phone, and when restarting you will not be able to enter the Bootloader).
To exit Bootloader you have to remove the battery.

Help - Desire stuck on boot

Has anyone ever seen this? Got this phone cheap and would like to fix it.
Can't get into bootloader, just goes to this screen and keeps rebooting ever so often.
Cheers for any help

Ok an update, it seems the volume- button is broken but back key + power worked and I got into the boot menu. Here's a pic.
Where should I go from here?
Is there a way of knowing if the phone is branded and what brand or unlocked so I can try flashing a WWE RUU?

Ok so the phone is branded T Mobile since a Tmob RUU worked just fine but with WWE ROMs I get a CID mismatch.
Made a goldcard with 2 sd cards but it doesn't work since I get a CID error mismatch again.
I should mention that after a T Mobile RUU flash that phone was still getting stuck on that same screen in post 1.
I've tried several things but still no luck with getting anywhere.
Thoughts?
EDIT: Made a successful goldcard using a different method and was able to flash the latest WWE RUU but the phone is still stuck on boot, the difference is that now it's the white screen with HTC in the middle.
So the phone doesn't even get into boot.
Can somebody help me with this??

Ruu really should Fix it. If it doesn't, first port of call should be warranty. Does ruu give no error?
Sent from my HTC Desire using Tapatalk

As I've mentioned, I got this phone for cheap so no warranty.
Nope, no errors with goldcard. Also I should mention I can't get into recovery, it just goes back into boot loop.
I suspect some partition somewhere must be corrupted.
If the phone had S-OFF it would make things so much easier.

Ok so an update, for anyone who runs into this problem.
After trying basically everything (even trying to unlock bootloader with a HTC Unlocker device with no success, probably due to action key not working) I was going to go and try to unlock the official way.
To unlock the official way I had to update the ROM so I just used the latest update which is 2.3.3 and after flashing I was finally able to boot!! So it seems like the problem was not hardware related at all.
Next I used Revolutionary to S-OFF, flashed CWM Touch and used root.zip for root access. Now I'm happy I got it all going and it's time for a sandwich, the ice cream variant
Peace!

[Q] Back to stock from NuSense

Need to take my Verizon One M7 in for a replacement. Reception is killing me (keep dropping to 1X or weak 3G in outlying areas), calls drop more than they don't, and even getting mms generic errors. Tried multiple ROM's, multiple radios, stock recovery/ROM/reset, new SIM card...nothing works.
I did notice something though - when I first got this phone, they had trouble initializing the SIM in the store...thought nothing of it until I went to the corporate store for a replacement SIM and they couldn't get the replacement to activate from the phone...I am thinking I have bad hardware.
The guy was cool (he looked my stats up and was shocked at the dropped calls) but made a point to tell me it was likely behaving badly due to being rooted...would rather walk in with a plain vanilla phone and let them replace it or let me out of my extension and I will go back to my trusty ReZound, because this thing is useless as a phone as-is.
How do I get back to pure stock so I can take this in for a replacement?
ROM is NuSenseSIX-KitKat_m7vzw_RC7.4_071714
Radios from 4.10.605.3_NoBootImg_firmware
TWRP 2.7.08
Rooted (and hboot) using Firewater (have the red warning 'this is only for internal HTC use..." on the boot splash screen)

the_Damaged_one said:
Need to take my Verizon One M7 in for a replacement. Reception is killing me (keep dropping to 1X or weak 3G in outlying areas), calls drop more than they don't, and even getting mms generic errors. Tried multiple ROM's, multiple radios, stock recovery/ROM/reset, new SIM card...nothing works.
I did notice something though - when I first got this phone, they had trouble initializing the SIM in the store...thought nothing of it until I went to the corporate store for a replacement SIM and they couldn't get the replacement to activate from the phone...I am thinking I have bad hardware.
The guy was cool (he looked my stats up and was shocked at the dropped calls) but made a point to tell me it was likely behaving badly due to being rooted...would rather walk in with a plain vanilla phone and let them replace it or let me out of my extension and I will go back to my trusty ReZound, because this thing is useless as a phone as-is.
How do I get back to pure stock so I can take this in for a replacement?
ROM is NuSenseSIX-KitKat_m7vzw_RC7.4_071714
Radios from 4.10.605.3_NoBootImg_firmware
TWRP 2.7.08
Rooted (and hboot) using Firewater (have the red warning 'this is only for internal HTC use..." on the boot splash screen)
Click to expand...
Click to collapse
fastboot ruu would be the easiest way.
once ruu is complete you can write secure flag back to s-on and it will be 100% stock.

synisterwolf said:
fastboot ruu would be the easiest way.
once ruu is complete you can write secure flag back to s-on and it will be 100% stock.
Click to expand...
Click to collapse
Thanks synisterwolf...two questions:
1 - I assume one of these would be what I want for a full RUU (not 100% sure which one)?
(from http://forum.xda-developers.com/showthread.php?t=2485319)
2.10.605.1 Decrypted RUU
2.10.605.1 Signed RUU
Odexed Full Rom (4.10.605.3 4.4.2 Sense 6.0)
2 - I found this guide...if I use the updated RUU, is the rest of this process still valid?
http://forum.xda-developers.com/showthread.php?t=2475216

the_Damaged_one said:
Thanks synisterwolf...two questions:
1 - I assume one of these would be what I want for a full RUU (not 100% sure which one)?
(from http://forum.xda-developers.com/showthread.php?t=2485319)
2.10.605.1 Decrypted RUU
2.10.605.1 Signed RUU
Odexed Full Rom (4.10.605.3 4.4.2 Sense 6.0)
2 - I found this guide...if I use the updated RUU, is the rest of this process still valid?
http://forum.xda-developers.com/showthread.php?t=2475216
Click to expand...
Click to collapse
guide is correct but use this link for RUU:
http://forum.xda-developers.com/showthread.php?t=2765784
the one you posted is a rom that you flash in recovery and not a full RUU

Be sure to follow the "lock bootloader" instructions before you ruu. There is a command either done in adb with root or recovery flashable zip to get "locked" instead of "relocked". As you see above, it requires you to either be rooted our have custom recovery, so do it before ruu and s-on after ruu completes.
Side note: ruu will wipe the whole phone, so be sure to copy your pictures, music, etc to a PC before ruu.
Edit: I recommend the signed 2.x.x.x ruu as it is fully stock. The new one linked above is rooted, so you would have to unroot and all that after you ruu.
Sent from my HTC6500LVW using XDA Free mobile app

Thanks guys...any chance one of you has a link to the signed fully stock RUU?
edit: (or is that the one I found above on santod's thread that says it's signed? I am guessing signed means fully stock, not rooted, etc?)

the_Damaged_one said:
Thanks guys...any chance one of you has a link to the signed fully stock RUU?
edit: (or is that the one I found above on santod's thread that says it's signed? I am guessing signed means fully stock, not rooted, etc?)
Click to expand...
Click to collapse
Correct, the one from santods thread. Signed
means it has been signed and encrypted by HTC.
Sent from my HTC6500LVW using XDA Free mobile app

Uzephi said:
Correct, the one from santods thread. Signed
means it has been signed and encrypted by HTC.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
Makes sense...never needed to use an encrypted one before on my DINC or ReZound, so I wasn't up to speed on the differences. Appreciate the guidance on this.
Will also give it a day on stock (keeping s-off) to see if it actually helps...though I suspect it won't.

the_Damaged_one said:
Makes sense...never needed to use an encrypted one before on my DINC or ReZound, so I wasn't up to speed on the differences. Appreciate the guidance on this.
Will also give it a day on stock (keeping s-off) to see if it actually helps...though I suspect it won't.
Click to expand...
Click to collapse
You don't "need" to, but it is always the better option if it is available.
Sent from my HTC6500LVW using XDA Free mobile app

Thanks for the help...
I did get the stock (signed, encrypted) RUU to load...had to back-rev my firmware using santod's post first, but otherwise all went as expected.
After a few updates OTA, I have been on the 4.4.2 for a couple of days - still cruddy signal at my house, so I plan ot s-on and head into the local corporate store to see what's next.
Will post on the other thread for the folks looking for the right RUU link.

Uzephi said:
You don't "need" to, but it is always the better option if it is available.
Click to expand...
Click to collapse
Speaking of better option...want to make sure I avoid a "tampered" issue...
I left my One s-off after the RUU, and updated OTA to latest to see if that helped my issue (it did not).
To go s-on, am I ok to do it now, or do I need to flash back to an older RUU first? Not sure if Verizon built something into a newer update that may catch the flag change.

No. Verizon has no control on that deep of the inner workings of an HTC. Only way to trip a "Tampered" state is messing with the system partition, radio, etc without being s-off. Turning s-off to s-on with everything stock will not trip that flag.
Edit: in my experience with HTC bootloaders, (I have had an Inc, Rezound, DNA, and this m7) they all are different in certain ways. The Inc never had a "Tampered" tag, to my knowledge. The Rezound had "tampered" tripped when a custom recovery was flashed while s-on. We had a special way of utilizing "fastboot boot recovery" command to prevent the tampered from ever being tripped. I didn't have my DNA long enough to worry about "tampered". And to get bootloader unlock for this phone, it did s-off so tampered wasn't tripped for me.
So how are HTC bootloader different by device? When my Inc had to be rooted, it didn't have a "locked" or "unlocked" flag, only s-on/off. The Rezound had to be s-off if you wanted to flash everything of a Rom in recovery (or utilize HTC dumlock or "fastboot boot recovery" command from bootloader) otherwise after a Rom install, tampered would trip and the boot.img wouldn't be flashed and you would have to go to bootloader to flash the boot.img or do the workaround in parentheses... For the DNA and m7, you don't need s-off to flash boot.img in recovery. I do notice on stock bootloader (I have the faux hboot) it will check if radio, hboot, and recovery are stock or not and I think this is what s-on checks for when tripping tampered. (Before I flashed the faux hboot it showed everything green except recovery since I have TWRP and not stock)
For any inaccuracies you can correct me and I will fix. This is from my own experiences with these devices and how they work.
TL/DR: all HTC model bootloader are different, but one thing never changes, if you are completely stock s-off and run the command "fastboot oem writesecureflag 3" it will not trip tampered.
Sent from my HTC6500LVW using XDA Free mobile app

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.

Relocked, OS won't boot

Hey so here's my situation:
Installed the CM Nightly on my AT&T One M9, didn't like it, so I tried to revert to stock. I didn't want to pay $25 to S-OFF so I just tried installing various RUUs, but none would work. I read somewhere that I needed to relock my bootloader in order for the RUUs to work, so I did that, and now my phone just boots to Recovery Mode. I've tried installing AT&T RUU 2.6.502.16 (which didn't work because my phone is on a more recent firmware) and reinstalling 2.11.502.18/flashing its 0PJAIMG.zip (which didn't work because it's apparently broken). I've even tried installing T-Mobile's 2.11.531.19 RUU, which of course didn't work because my CID doesn't match and I can't change it because I'm S-ON.
I realize I went about this very badly almost from the start--no stock backup in TWRP, etc. This is my first Android phone so I've been learning this as I go and I was a bit sloppy.
I'm pretty sure I'm screwed, at least until a new update comes out or the current AT&T RUU is fixed, but I'm wondering if there's something else I can try. Any ideas? Thanks.

StageProps said:
Hey so here's my situation:
Installed the CM Nightly on my AT&T One M9, didn't like it, so I tried to revert to stock. I didn't want to pay $25 to S-OFF so I just tried installing various RUUs, but none would work. I read somewhere that I needed to relock my bootloader in order for the RUUs to work, so I did that, and now my phone just boots to Recovery Mode. I've tried installing AT&T RUU 2.6.502.16 (which didn't work because my phone is on a more recent firmware) and reinstalling 2.11.502.18/flashing its 0PJAIMG.zip (which didn't work because it's apparently broken). I've even tried installing T-Mobile's 2.11.531.19 RUU, which of course didn't work because my CID doesn't match and I can't change it because I'm S-ON.
I realize I went about this very badly almost from the start--no stock backup in TWRP, etc. This is my first Android phone so I've been learning this as I go and I was a bit sloppy.
I'm pretty sure I'm screwed, at least until a new update comes out or the current AT&T RUU is fixed, but I'm wondering if there's something else I can try. Any ideas? Thanks.
Click to expand...
Click to collapse
I downloaded and flashed the 2.11.502.18 ruu from the HTC website with no problem. Ate you getting an error?
Edit: in my experience, if an ruu.exe starts to run and then never does (like you get the spinning wheel for a minute and then nothing) it's either a bad download or antivirus is blocking the file. But just to repeat...the exe on the HTC website works fine. I used it about three weeks ago.

Hm. Out of the myriad RUU.exes I've tried the most recent AT&T one was the only one I couldn't get to start, and when I tried installing it via .zip it would just restart the phone and nothing else. That in combination with other posts I've seen on this forum saying it's borked (although I might have misread the numbers/misinterpreted the jargon) just lead me to think it was broken. I'll redownload and try again. Thanks!
Edit: Well, it worked! I don't know what I was doing wrong. Thanks a lot!