Develop Bugs

[Q]Unusual brick - Solution?

I have happily had a htc desire z for just over a year. On Tuesday i bought the 'humble bundle' android apps.
I downloaded one of the apps. Cogs. Once i installed it my screen went black and didn't do anything. So after 15 minutes. I reluctantly removed and replaced my battery. From then on my phone wont get passed the htc boot screen. From then on I only assumed i have an expensive paperweight which was bricked one way or another.
It can however access the 'hboot menu' (if thats the correct term?);
When the menu loads it checks for some zip files, its too fast too make out what they are though. The menu info is as follows if it helps;
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011, 23:36:27
Options:
FASTBOOT - Takes me to another menu. Doesn't seem useful as far as i can see.
RECOVERY - It brings up the phone with the green arrow for 2 seconds then buzzes 3 times in succession and then shuts the screen off. Is that what it should do?
FACTORY RESET - This option looks like what id need, however when i select it the phone just freezes.
SIMLOCK/IMAGE CRC - From what ive read theyre not really any use.
Would anyone be able to suggest a port of call in order to recover this lifeless paperweight please?!
Any help is greatly appreciated.
Craig

wuptdo said:
RECOVERY - It brings up the phone with the green arrow for 2 seconds then buzzes 3 times in succession and then shuts the screen off. Is that what it should do?
FACTORY RESET - This option looks like what id need, however when i select it the phone just freezes.
Click to expand...
Click to collapse
Recovery should bring you to your recovery menu. What i mean is that it should start ClockworkMod or 4Ext depending on which one you've installed.
As far as i know those 2 options would allow you to get your phone back to life. I'm afraid that you're screwed without it. But my knowledge about that kind of stuff is pretty basic so maybe someone on this forum has a solution.
Good luck !!!

TenMaKo said:
Recovery should bring you to your recovery menu. What i mean is that it should start ClockworkMod or 4Ext depending on which one you've installed.
Click to expand...
Click to collapse
Sounds like the phone is still stock, so in that case it would be neither of those, and the stock Recovery.
Which brings up the valid question: this phone is stock and unrooted?
Factory reset should do the trick. If not, you might need to find the appropriate RUU file for your phone version (region, carrier) and run that on your computer with the phone connected via USB. What version of the Desire Z do you have (Canada, Euro, Asia, etc.)?
Fastboot is a special tool used with your phone connected by USB to your computer. The Fastboot menu in Hboot simply turns this feature on or off. You don't need to mess with it, unless specifically instructed to.

Unfortunately the phone is still completely stock. Didn't really fancy dabbing in rooting until the warranty ran out, which ironically is now.
The phone is not carrier locked (i.e. it's sim free).
I live in the UK, however i purchased it through a weird net site, it came with alternative languages like THAI pre-installed which suggests its an Asian import. With no option for European languages, except English of course.
Thanks for the swift replies, i'll have a quick read into RUU's, and what they actually are though. But if with the extra info you can further point me in the right direction it'd be great!
thanks
craig
EDIT: Just been rooting around on this site
shipped-roms(dot)com/index.php?category=android&model=Vision
Theres 2 RUUs there with the same radio number.
RUU_Vision_Gingerbread_S_hTC_Asia_TW_2.42.709.10_Radio_12.56.60.25_26.10.04.03_M_release_201045_signed.exe
(does the TW mean anything?)
and
RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed.exe
would these be what i'm after?

The stock/shipped RUUs can be downloaded from here:
http://shipped-roms.com/index.php?category=android&model=Vision
The question is which one. You can try the Asian RUU. I'm not certain what would happen if you try to run the wrong RUU. I think (not sure) that it will just fail and give an error message for wrong version.
---------- Post added at 05:32 PM ---------- Previous post was at 05:28 PM ----------
wuptdo said:
EDIT: Just been rooting around on this site
shipped-roms(dot)com/index.php?category=android&model=Vision
Theres 2 RUUs there with the same radio number.
RUU_Vision_Gingerbread_S_hTC_Asia_TW_2.42.709.10_Radio_12.56.60.25_26.10.04.03_M_release_201045_signed.exe
(does the TW mean anything?)
and
RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed.exe
would these be what i'm after?
Click to expand...
Click to collapse
Woops, cross posted as you were editing your post. WWE is world wide English. I'm guessing TW is Taiwan. Again, not sure which one you want.

Thanks again.
Right once i decipher which RUU is the correct one.
How do i need to connect my phone. Do i need to be just in the hboot menu, or ?
thanks in advance. you're a lifesaver. well.....phone saver. hopefully

wuptdo said:
How do i need to connect my phone. Do i need to be just in the hboot menu, or ?
Click to expand...
Click to collapse
Couldn't remember and had to look that one up. Put your phone into fastboot mode in order to run the RUU.

Right. I gave the WWE version a run. It was able to scan my current firmware and said it was using build 2.42.707.3 there isn't an RUU for this.
Would you think it would load the WWE fine, or result in a worse off brick?
WWE BUILD = 2.42.405.2
ASIA_TW BUILD = 2.42.709.10
would it be worth requesting an ruu for the specific build direct from htc do you think or would i be wasting my time.
Sorry for the tireless questions. I really do thank you for your effort.

Wait, what message are you getting again? It won't allow you to flash because it's the same version?
I would try the version that's on your device. I take that's the ASIA_TW RUU?
However.
What your issue would be with flashing an RUU, is the fact the phone does a version check. Now if the version is higher or equal to the one already installed, it will refuse to flash (not sure on equal, that's why you might have a chance if you flash the RUU that corresponds to your version).
So, the only way you can go around the version check is make the phone think that it's a lower version. You have to do this by editing the "misc" partition. This partition holds information such as version number, and others unique to your phone. The misc partition is edit-able, but editing it is largely accomplished by having access to the Android OS, which apparently isn't the case here. You'll only be able to accomplish this by editing the misc partition using a Jtag, and this is sub-optimal solution, to say the least.

wuptdo said:
Would you think it would load the WWE fine, or result in a worse off brick?
Click to expand...
Click to collapse
As crestofawave mentions, if it fails the version check, it SHOULD just refuse to flash the ROM. But I've heard of cases where a wrong RUU is run (or partially run?), causing the phone to be stuck in recovery. But I don't think that would put you in any worse situation than you are now. As the solution for that particular problem is flashing the correct RUU.
I don't THINK there is anything worse than that, that will happen from flashing the wrong RUU. But I personally don't know enough to answer that for certain. And I would hate to be wrong. But if I were a betting man, I'd just try to flash one of the RUU's and see what happens.
Since the WWE RUU is a lower version number than what is currently installed, I don't think you have a choice, but to run the ASIA_TW one.
The other option is to try to make a goldcard from an SD card. This will allow you to run any RUU.
---------- Post added at 02:42 PM ---------- Previous post was at 02:39 PM ----------
crestofawave said:
Wait, what message are you getting again? It won't allow you to flash because it's the same version?
Click to expand...
Click to collapse
He hasn't tried running an RUU yet.
---------- Post added at 02:43 PM ---------- Previous post was at 02:42 PM ----------
crestofawave said:
I would try the version that's on your device. I take that's the ASIA_TW RUU?
Click to expand...
Click to collapse
He can't figure out version/region his phone is (and I haven't been able to either, just by Googling around). That's the main problem right now.
---------- Post added at 02:47 PM ---------- Previous post was at 02:43 PM ----------
crestofawave said:
What your issue would be with flashing an RUU, is the fact the phone does a version check. Now if the version is higher or equal to the one already installed, it will refuse to flash (not sure on equal, that's why you might have a chance if you flash the RUU that corresponds to your version).
Click to expand...
Click to collapse
Pretty sure you mean if the versions number (you are trying to flash) is lower than the one already installed, it will fail. Equal version should pass the check, as running the RUU is a common means of recovering an existing ROM.
---------- Post added at 02:56 PM ---------- Previous post was at 02:47 PM ----------
wuptdo said:
Right. I gave the WWE version a run. It was able to scan my current firmware and said it was using build 2.42.707.3 there isn't an RUU for this.
Click to expand...
Click to collapse
I ran a search for that version number on this forum, and got this thread:
http://forum.xda-developers.com/showthread.php?t=1434137&highlight=2+42+707+3
The download link seems to work, but at your own risk. Sketchy Chinese download site posted by a member with only 3 posts . . . is a bit sketchy.
In theory this should be the right ROM file (pass version check). Rename to PC10IMG.zip and put on your SD card. Then flash from recovery.

@redpoint73 Thanks for pointing some things out. I was somewhat busy at the time so I didn't have the time to assess the situation as well as I'd like. So, flashing an RUU of the same version does work, huh? Good to know.
So, I also looked up the version number and I found that the same file had been mentioned in some other sites, in one of which I found the same person posting it, and he's a moderator, too. Well, I don't think it helps in terms of trustworthiness, but then again, it sounds like this is your best shot.
Good luck though!

Right. With both the WWE and ASIA_TW editions it runs the RUU, all the way up too the update button. However once i click it. The RUU shows the loading bar with text saying 'rebooting to bootloader' but it just gets stuck here. The phone just hangs on the fastboot menu and doesnt let me do anything until i remove the battery again.
I'm gonna try work out how to download the other one from this rather Chinese site. If that doesn't work....
One last solution. Try extracting the exes to get the firmware. Shove it on the memory stick and load it through recovery?
cheers for the link to that firmware btw.

wuptdo said:
One last solution. Try extracting the exes to get the firmware. Shove it on the memory stick and load it through recovery?
Click to expand...
Click to collapse
I think the same thing will happen in recovery, that the extracted .zip files will fail in region and/or version number check. This is pretty much what "S-On" on your Hboot screen signifies (in addition to write protecting the Hboot, radio, and other things).
One thing you can try, is to turn an SD card into a Gold Card. Gold card will let you then flash any ROM, regardless of region or version number.
This (though a bit dated) is the best guide I know of for making a gold card:
http://forum.xda-developers.com/showthread.php?t=835777
With a gold card, you should be able to flash any RUU. The WWE ROM on the same thread is a good start point, as its the unbranded HTC ROM that was shipped when the phone was initially released (Euro version).
I've personally never had to make a gold card, I just know about the process. For some reason, it doesn't always work from posts I've read in the past. So its not a silver bullet. But for the lack of the right RUU for your phone version, it may be your best bet at this time.

Slowly downloading from that Chinese site at a whopping 10KB/s whilst having a read about gold cards. Can i make a gold card in any android phone and use a gold card in any android phone?

wuptdo said:
Can i make a gold card in any android phone and use a gold card in any android phone?
Click to expand...
Click to collapse
Really don't know. But the "easy guide" to make a gold card is from the HTC Hero forum on Modaco, so it seems there is some standardization, at least among HTC devices. The various manufacturers have very different write protections, so I'm guessing this is just an HTC thing.

apparently you can
apparently you can use any goldcard with any phone, well according to the second post on this thread anywho.
http://androidforums.com/legend-support-troubleshooting/197860-how-do-i-use-goldcard.html
now to find a willing volunteer in uni halls so shouldnt be tooooo hard to find one of these nifty new phones lying round.

Well it passes all the checks and gives me the option to install the firmware with that chinese one so im gonna give it a go once my batteries fully charged!
If it works i'll upload that link to a UK/US host so it doesn't take people in a similar situation 6 hours to download 250 Mb!
EDIT: If it works. Would it be worth rooting/S-off in order to make recovering my phone easier in the future?

Rooting your phone can only lead to benefits. You can flash Custom ROM's (You can go with Stock rooted ones if you just want to use the phone. Having root really makes the difference, there's a lot more freedom.)
To answer your question though, what is meant by "rooting" here is basically unlocking the phone. It allows us for complete control of pretty much every aspect on this phone..
Now, typically, when you "root" the phone you also get what we call a "recovery". Essentially, recovery is a utility that will allow you to control the phone's OS, essentially to install/remove or backup it, as well as other handy features. Think of it as a fail-safe toolbox, isolated from the rest of the android system. So, in many cases, it will "recover" your phone, in case of an issue. This really depends on the incident though, a recovery can't "fix" a broken eMMC chip. Don't worry though, chances of breaking your phone are very little if you do everything right.
Also, in addition to that, whilst rooting (when using the XDA Wiki Guide), you eventually get the option to flash the ENGineering HBOOT. What ENG HBOOT allows you to do is make use of the "fastboot" bridge. With it, you can perform a multitude of tasks, just like in recovery. The only difference is that fastboot is on the lower levels of the phone's building blocks, HBOOT. That means that in the case you can't run the recovery for whatever reason you could flash a new one using fastboot. It's quite useful but it is overlooked as it is considered a dangerous process, while it really isn't, if you're careful. Same goes for the rest of the rooting guide which you can find here, if you feel comfortable enough to root, that is! You don't necessarily have to flash the ENG HBOOT, so if you don't feel comfortable about it you can ignore it.
Best of luck.

Thanks for the info!
BUUT. That method failed miserably. I choose to update. The screen just sits there on updating for the first module (bootloader) and doesnt do anything.
I remove the battery and restarted a bit scared to do so. But it didnt even touch the bootloader in the 15 minutes i waited........so I have a feeling something has physically broken on the thing.

Bummer...Whether it's a soft or hard brick...we're handicapped in terms of options, considering that we have limited access. You can try running it again, and leave it for more time. Probably not going to do any better but until (and if) we can come up with something else, I don't see another option.

[Q]How can I get back to stock from a custom rom?

I recently got my HTC One M8, and I was trying to follow a tutorial on htc-one wonder how to (I cant link it). It links to other tutorials for pre-requisits, and I fell down the rabbit hole trying to get pre-req after pre-req. I spent about 2 days non stop on this and I'm pretty sure I screwed up pretty bad.
I'm think I wrote the recovery image to the boot sector by accident...or something like that
What I have:
1. . My computer recognizes my phone in fastboot. I can transfer files to and from. I am not sure if adb works.
2. I can access TWRP by hitting "Recovery" in fastboot. I think this means I have a custom recovery successfully installed.
3. The InsertCoin rom (insertcoin-m8_5.0.6_ART) is installed and I can boot to it. I was not going to keep it, but I needed it for one of the steps. Wifi does not work so any files have to be added manually via usb.
4. My bootloader is unlocked
5. I have S-ON
6. I have Minimal ADB and Fastboot installed and it works. I also have Hansoon200's All In One HTC One M8 Toolkit
7. This is a brand new phone so I don't care about my data.
I'd like to get back to stock so I can try to run Firewater (will not work without internet. Wifi is broken on the rom) and get S-OFF (needed for Google Play Edition). How can I go about this?
I apologize in advance, I've been at this for days. I wouldn't post unless I was really stuck. I appreciate any help you can provide. I will gladly provide any additional information
Thanks

dyslexicfurby said:
I recently got my HTC One M8, and I was trying to follow a tutorial on htc-one wonder how to (I cant link it). It links to other tutorials for pre-requisits, and I fell down the rabbit hole trying to get pre-req after pre-req. I spent about 2 days non stop on this and I'm pretty sure I screwed up pretty bad.
I'm think I wrote the recovery image to the boot sector by accident...or something like that
What I have:
1. . My computer recognizes my phone in fastboot. I can transfer files to and from. I am not sure if adb works.
2. I can access TWRP by hitting "Recovery" in fastboot. I think this means I have a custom recovery successfully installed.
3. The InsertCoin rom (insertcoin-m8_5.0.6_ART) is installed and I can boot to it. I was not going to keep it, but I needed it for one of the steps. Wifi does not work so any files have to be added manually via usb.
4. My bootloader is unlocked
5. I have S-ON
6. I have Minimal ADB and Fastboot installed and it works. I also have Hansoon200's All In One HTC One M8 Toolkit
7. This is a brand new phone so I don't care about my data.
I'd like to get back to stock so I can try to run Firewater (will not work without internet. Wifi is broken on the rom) and get S-OFF (needed for Google Play Edition). How can I go about this?
I apologize in advance, I've been at this for days. I wouldn't post unless I was really stuck. I appreciate any help you can provide. I will gladly provide any additional information
Thanks
Click to expand...
Click to collapse
couple of things ... firewater is over it no longer works. Sunshine will most likely s-off your phone (for $25)
If TWRP works it's not on the wrong partition. you have no wifi becouse you did not update your firmware .. it says this in every rom thread.
so your steps now are find the nandroid and stock recovery to go back to stock Here > COLLECTION of Stock backup's
http://forum.xda-developers.com/showthread.php?t=2701376

clsA said:
couple of things ... firewater is over it no longer works. Sunshine will most likely s-off your phone (for $25)
If TWRP works it's not on the wrong partition. you have no wifi becouse you did not update your firmware .. it says this in every rom thread.
so your steps now are find the nandroid and stock recovery to go back to stock Here > COLLECTION of Stock backup's
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
Thanks! I'm going to try this. Will post with updates

So I'm going through that thread, and I think I know what to do. The main problem is finding the correct files. Then I use the terminal, fastboot getvar version-main the result is blank and fastboot oem readcid returns SPCS_001. However there does not seem to be a Nandroid matching those values. Any ideas?

dyslexicfurby said:
So I'm going through that thread, and I think I know what to do. The main problem is finding the correct files. Then I use the terminal, fastboot getvar version-main the result is blank and fastboot oem readcid returns SPCS_001. However there does not seem to be a Nandroid matching those values. Any ideas?
Click to expand...
Click to collapse
look in the Sprint forums http://forum.xda-developers.com/sprint-htc-one-m8

Bricked HTC One M8

Hi
Please can anyone help please?
Got a HTC One M8 on o2. I installed a custom rom (Viper One) and used it fine for over a year.
I've since changed to a S6 edge and wanted to revert my old phone back to stock rom unrooted.
In doing so I messed up!!!
I'm now stuck with a handset, everything wiped (including the operating system and backups)
I have TWRP recovery and need to re-install stock rom.
Can anyone help?
Thank you

This section is absolutely filled with the same question.
Have a GOOD read here
http://forum.xda-developers.com/showthread.php?t=3086860

Ah right sorry, thanks... Will check it out

bah77 said:
I'm now stuck with a handset, everything wiped (including the operating system and backups)
Click to expand...
Click to collapse
If I'm understanding you correctly, you wiped the OS, not realizing it would cause your phone to be without . . . an operating system?

NO, the operating was wiped by accident

bah77 said:
NO, the operating was wiped by accident
Click to expand...
Click to collapse
Well the easiest way without going through any hassle to fix your phone and make it Stock/Like Brand New is to run a RUU.
I will explain how to do this process with a PC and you should be good to go :good:
1. Download HTC drivers for your PC if you haven't already Here, install and uninstall HTC Sync Manager while KEEPING "HTC Driver Installer".
2. Download the RUU that best matches your phone Here, you can possibly find a O2 RUU on xda but I did not find one my self for you unfortunately, otherwise if your phone is a GSM variant phone you can flash the international RUU from Here (Instructions would be different in this case)
3. Get your phone into bootloader by TWRP or if your phone is off then hold down VOL DOWN and POWER BUTTON at the same time until HBOOT shows up.
4. Plug your device via USB into the computer and verify that you see "Fastboot USB" on your phone's screen.
5. Run the RUU .exe file, I recommend you "Run as Administrator".
6. Follow the on screen instructions and sit back 10-20 minutes as your phone becomes brand new, do not interupt the process or you could have a permanent phone brick.

bah77 said:
Ah right sorry, thanks... Will check it out
Click to expand...
Click to collapse
Is your problem fixed ? Do you still need a RUU for this ? Or the TWRP backup that you found in that link is good enough ?

Sorry not had time to try yet but hoping to in the next day or two
Thanks for the help guys, will let you know how i get on

bah77 said:
wanted to revert my old phone back to stock rom unrooted.
In doing so I messed up!!!
I'm now stuck with a handset, everything wiped (including the operating system and backups)
I have TWRP recovery and need to re-install stock rom.
Click to expand...
Click to collapse
Seems (from the vague description) that a few things went wrong:
1) You may have been proceeding without the proper knowledge of how to return to stock, and at least somewhat, "making it up" as you went along or "experimenting". This is not the proper way to go about things when modding (or in this case "unmodding") a phone. Stick to specific instructions and guides, as already pointed out the process to return to stock is well documented.
2) No degree of wiping or factory resets is going to restore a stock ROM, if you have a custom ROM installed (if that is what you were trying to do); which is a somewhat common misconception. Also, wiping things without understanding the result is a bad idea. The Wipe options are called "Advanced" for a reason. If you don't understand what it is (or the results of wiping it) than don't do it.
The process to return to working stock has been outlined by others. But if you want more specific help, you will need to do a getvar all and post the output (being sure to delete your IMEI and serial number, as those are personal info) so we can better determine the way forward. But in summary, you have 2 choices:
a) Relock the bootloader and run the proper RUU, of one exists for your CID version.
b) Restore the stock nandroid that corresponds to your CID and main version (firmware), then flash the correct corresponding stock recovery.

Been stuck like this for 40 minutes

bah77 said:
Been stuck like this for 40 minutes
Click to expand...
Click to collapse
What did you do ?
Do you have right RUU ? Can you give the RUU name that you are using ?
I saw you use a ROM.zip .. AFAIK your O2 RUU is an exe file.
You also need USB 2.0 and latest HTC USB Drivers installed.

Do i need to re lock the bootloader first?

Discussion has resumes here:
http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-brick-t3243115
Thread closed.

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.

RESOLVED! [SOS!] Phone can't boot past bootloader

My phone is having a bowl of bootloops right now lol.
I have a unlocked htc 10, i unlocked the bootloader (S-on since leedroid thread didn't say it was necessary), flashed the latest TWRP formatted data part, rebooted recovery again, swiped allow modifications, flashed the marshmallow version of the ROM and nothing but bootloops. what am i missing? thanks
first time HTC owner here coming from a 6p so show mercy

drago10029 said:
My phone is having a bowl of bootloops right now lol.
I have a unlocked htc 10, i unlocked the bootloader (S-on since leedroid thread didn't say it was necessary), flashed the latest TWRP formatted data part, rebooted recovery again, swiped allow modifications, flashed the marshmallow version of the ROM and nothing but bootloops. what am i missing? thanks
first time HTC owner here coming from a 6p so show mercy
Click to expand...
Click to collapse
Are you on MM firmware or N?
Also S-OFF is the way to go.

andybones said:
Are you on MM firmware or N?
Also S-OFF is the way to go.
Click to expand...
Click to collapse
I was on latest stock nougat before I started the process. since the I have tried flashing both leedroid marshmallow zip and the nougat magisk zip also. and what's the deal with s-off?
Everywhere i look they're all how to's about s-off lol. seems hard to find a thread on what s-off is, if it's needed to for a specific ROM or not :/ that being said leedroid it wasn't needed as quoted below. thanks!
If you wish to s-off first, please follow >> THIS GUIDE << by @jcase & return when your device is back up and running.
First boot will take approximately 15 minutes due to Art optimization
Click to expand...
Click to collapse

UPDATE: things have gotten worse.... I was attempting to relock the bootloader since RUU was failing with error 155, someone in a diff HTC thread said locked bootloader was needed for RUU. now phone flashes HTC logo then powers off. buttons pressed not going to recovery right now anyone wanna chime in? please...

@defcomg you know anything about HTC phones? I am currently stuck in the sunken place lol

drago10029 said:
I was on latest stock nougat before I started the process. since the I have tried flashing both leedroid marshmallow zip and the nougat magisk zip also. and what's the deal with s-off?
Everywhere i look they're all how to's about s-off lol. seems hard to find a thread on what s-off is, if it's needed to for a specific ROM or not :/ that being said leedroid it wasn't needed as quoted below. thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=1680928

andybones said:
https://forum.xda-developers.com/showthread.php?t=1680928
Click to expand...
Click to collapse
hmmmm according to that post the TWRP i flashed should have reverted on reboot and that hasn't been the case at all since it has survived multiple reboots... any thoughts on that?
"...Basically, all changes made to these partitions while the phone is running is not permanent, and will be reset upon a reboot..."
EDIT: also does that mean unless I have S-off none of the custom ROMs will flash? so what's the point of unlocking a bootloader is that needs to be disabled also

drago10029 said:
hmmmm according to that post the TWRP i flashed should have reverted on reboot and that hasn't been the case at all since it has survived multiple reboots... any thoughts on that?
"...Basically, all changes made to these partitions while the phone is running is not permanent, and will be reset upon a reboot..."
EDIT: also does that mean unless I have S-off none of the custom ROMs will flash? so what's the point of unlocking a bootloader is that needs to be disabled also
Click to expand...
Click to collapse
Keep in mind the date on that post is from a few years back (2012). You can't put all your eggs into one basket, so to speak. I was just giving you 1 article I found from a simple Google Search. Encryption and TWRP have changed quite a lot, especially since Nougat.
From my small amount of time, I think you may be confused about what the difference is between an unlocked bootloader and S-OFF, which I'd need to even go back and read that article, but thought it touched a little on it
The 10 has changed quite a bit too from past phones. Before you'd need to be S-OFF and unlocked bootloader. Now S-OFF unlocked and S-OFF locked are basically the same, but that can be found in threads if you'd like to find more info on that.
Most the info is there, you just need to search. If you need help finding articles, I can try and help with that. I've been surprised with the great info I've found after awhile of coming up empty.
I'm just now seeing all the new posts that came from before I posted and have been on my phone and don't have the time to catch up on it all right now.
Hope things get squared away for you soon, I'll check in when I can.
It seemed you were in a simple bootloop, but I'm not 100%. I think your issue was flashing MM ROM on N firmware. Can't do that.
Also, Verizon doesn't allow us to unlock bootloader on Htc-dev. So if we want to root, we must S-OFF.

andybones said:
Keep in mind the date on that post is from a few years back. You can't put all your eggs into one basket, so to speak. I was just giving you 1 article I found from a simple Google Search. Encryption and TWRP have changed quite a lot, especially since Nougat.
I'm just now seeing all the new posts that came from before I posted and have been on my phone and don't have the time to catch up on it all right now.
Hope things get squared away for you soon, I'll check in when I can.
Click to expand...
Click to collapse
gotcha and thanks! so for anyone else who wants to help. I have regained access to download mode and bootloader. when attempting to run latest official RUU.exe from HTC's site, i get error 155. via HTC the error means I'm using the wrong update but my phone reports SW 2.48.617.1 and I'm trying to update it to SW 2.48.617.3.
also i have relocked the bootloader and have s-off.

drago10029 said:
gotcha and thanks! so for anyone else who wants to help. I have regained access to download mode and bootloader. when attempting to run latest official RUU.exe from HTC's site, i get error 155. via HTC the error means I'm using the wrong update but my phone reports SW 2.48.617.1 and I'm trying to update it to SW 2.48.617.3.
also i have relocked the bootloader and have s-off.
Click to expand...
Click to collapse
What method have you tried for the SW?
is it an RUU or just firmware?
I suggest the sdcard method.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure.
https://www.androidfilehost.com/?fid=24545065934258327
Either remove your current fastboot.exe and rename this one to it, or keel it as htc_fastboot.exe and use the correct, htc_fastboot flash, over fastboot flash

andybones said:
What method have you tried for the SW?
is it an RUU or just firmware?
I suggest the sdcard method.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure.
https://www.androidfilehost.com/?fid=24545065934258327
Either remove your current fastboot.exe and rename this one to it, or keel it as htc_fastboot.exe and use the correct, htc_fastboot flash, over fastboot flash
Click to expand...
Click to collapse
bear in mind I'm still learning all this HTC stuff lol
is it an RUU or just firmware? It's an RUU.exe for HTC 10 unlocked edition that i got from there website
I suggest the sdcard method. you mean installing custom ROM zip from sd card? otherwise i'm not sure what you mean.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure. hmmm well I used fastboot.exe from minimal adb & fasboot to unlock bootloader and that worked fine, and should i still i just replace fastboot in platform tools folder with fastboot.exe from htc website?
also so s-off shouldn't be needed to install the ROMs? just bootloader unlock?

drago10029 said:
bear in mind I'm still learning all this HTC stuff lol
is it an RUU or just firmware? It's an RUU.exe for HTC 10 unlocked edition that i got from there website
I suggest the sdcard method. you mean installing custom ROM zip from sd card? otherwise i'm not sure what you mean.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure. hmmm well I used fastboot.exe from minimal adb & fasboot to unlock bootloader and that worked fine, and should i still i just replace fastboot in platform tools folder with fastboot.exe from htc website?
also so s-off shouldn't be needed to install the ROMs? just bootloader unlock?
Click to expand...
Click to collapse
Keep in mind this is me helping in my free time.
Use the linked htc_fastboot.. It's made for htc, it's why I mentioned it..
I've seen many ppl have RUU fail by not using this.
Also an RUU/firmware have 3 methods to install.
I suggest the sd-card method. Safest.
Search. Search. Search. ...
Option 1
Copy 2PS6IMG.zip (THIS IS FOR VERIZON, YOUR CARRIER WILL NEED TO BE RENAMED CORRECTLY) to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Option 2
EXE option. Download EXE file below (for windows) and simply double click to start. You can either be booted to OS with USB debugging enabled OR booted into download mode for this to start.
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUU zip file and place in your working fastboot/adb directory. Boot your phone to download mode and connect to PC. Issue the following commands.
htc_fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
htc_fastboot flash zip 2PS6IMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "htc_fastboot reboot-bootloader" command and restart option 1 again.
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "htc_fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
--Taken from
Also read here. This is a great thread.
There's a lot of info out there.
Just search and do your homework.
It's easy to turn that device into a useless brick.
Especially being S-OFF... Secuirty-off..
I know it can be overwhelming, but the info is out there, and if not, just ask, as others most likely have the same question and this will help them.
And correct, with S-OFF isn't needed to flash ROMs. Only bootloader unlock.

andybones said:
Keep in mind this is me helping in my free time.
Use the linked htc_fastboot.. It's made for htc, it's why I mentioned it..
I've seen many ppl have RUU fail by not using this.
Also an RUU/firmware have 3 methods to install.
I suggest the sd-card method. Safest.
Search. Search. Search. ...
Option 1
Copy 2PS6IMG.zip (THIS IS FOR VERIZON, YOUR CARRIER WILL NEED TO BE RENAMED CORRECTLY) to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Option 2
EXE option. Download EXE file below (for windows) and simply double click to start. You can either be booted to OS with USB debugging enabled OR booted into download mode for this to start.
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUU zip file and place in your working fastboot/adb directory. Boot your phone to download mode and connect to PC. Issue the following commands.
htc_fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
htc_fastboot flash zip 2PS6IMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "htc_fastboot reboot-bootloader" command and restart option 1 again.
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "htc_fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
--Taken from
Also read here. This is a great thread.
There's a lot of info out there.
Just search and do your homework.
It's easy to turn that device into a useless brick.
Especially being S-OFF... Secuirty-off..
I know it can be overwhelming, but the info is out there, and if not, just ask, as others most likely have the same question and this will help them.
And correct, with S-OFF isn't needed to flash ROMs. Only bootloader unlock.
Click to expand...
Click to collapse
my bad, i hope i didn't come off rude or anything. i do appreciate all your help and i understand it. I do the same here when i have the free time.
I will ask some question's on both those threads you linked. I came across one of them but no s-off and didn't wanna pay for sunshine app. also topjohnwu thread about stock and guides would be helpful if it listed which phones the code names correlate to.
in the end I see your point, keep researching and asking. and I do that very often and promise. today was different since a bunch of PC failed to install updates at work (post wannacry) lol and dealing with my bootlooping phone, my mind was scattered. iv'e bricked before but never on a phone this expensive *__*
thanks again andy!
JUST AN UPDATE: i restored via twrp after i got the bootlooping to stop. I completely forgot I had made one -__- (more scatter brains) so I'm good to go now.... kinda.

drago10029 said:
my bad, i hope i didn't come off rude or anything. i do appreciate all your help and i understand it. I do the same here when i have the free time.
I will ask some question's on both those threads you linked. I came across one of them but no s-off and didn't wanna pay for sunshine app. also topjohnwu thread about stock and guides would be helpful if it listed which phones the code names correlate to.
in the end I see your point, keep researching and asking. and I do that very often and promise. today was different since a bunch of PC failed to install updates at work (post wannacry) lol and dealing with my bootlooping phone, my mind was scattered. iv'e bricked before but never on a phone this expensive *__*
thanks again andy!
JUST AN UPDATE: i restored via twrp after i got the bootlooping to stop. I completely forgot I had made one -__- (more scatter brains) so I'm good to go now.... kinda.
Click to expand...
Click to collapse
You didn't come off rude at all, I was actually hoping you didn't take my response as being rude. S-OFF and sunshine is completely worth the $25. However, for a normal user like yourself, you don't need it.
Glad to hear that you're somewhat good to go, lol.
You can always pm me or tag me in a post if needed and I'll do my best to help.

andybones said:
You didn't come off rude at all, I was actually hoping you didn't take my response as being rude. S-OFF and sunshine is completely worth the $25. However, for a normal user like yourself, you don't need it.
Glad to hear that you're somewhat good to go, lol.
You can always pm me or tag me in a post if needed and I'll do my best to help.
Click to expand...
Click to collapse
glad no guns are being drawn here
and since no you offered lol.... how do i get my CID and MID? using the fastboot you kindly spotted me...
fastboot getvar all and fastboot oem readcid: both return nothing but fastboot not recognized..... etc. etc. I am in download mode (unlocked and s-on if that matters)

drago10029 said:
glad no guns are being drawn here
and since no you offered lol.... how do i get my CID and MID? using the fastboot you kindly spotted me...
fastboot getvar all and fastboot oem readcid: both return nothing but fastboot not recognized..... etc. etc. I am in download mode (unlocked and s-on if that matters)
Click to expand...
Click to collapse
Fastboot isn't recognized? As in it's not working?

drago10029 said:
gotcha and thanks! so for anyone else who wants to help. I have regained access to download mode and bootloader. when attempting to run latest official RUU.exe from HTC's site, i get error 155. via HTC the error means I'm using the wrong update but my phone reports SW 2.48.617.1 and I'm trying to update it to SW 2.48.617.3.
also i have relocked the bootloader and have s-off.
Click to expand...
Click to collapse
2.48.617.3? I don't think there is such a thing. Do you mean 2.41.617.3?

andybones said:
Fastboot isn't recognized? As in it's not working?
Click to expand...
Click to collapse
xunholyx said:
2.48.617.3? I don't think there is such a thing. Do you mean 2.41.617.3?
Click to expand...
Click to collapse
1st things 1st, SOS is no more. was trying to flash leedroid magisk file, thinking it was a ROM until i noticed the file size so I went back to stock via TWRP backup (i forgot I made) since RUU was giving 155 error.
2nd the HTC fastboot wasn't working for some reason.. adb devices cmd detected nothing, it worked at my job though since i have android studio/platform tools there (shrug) so used that fastboot instead.
3rd I did mean SW 2.48.617.1 that's the exact OS version # that download mode reports currently and was the last official update i took several days before going custom route.

drago10029 said:
1st things 1st, SOS is no more. was trying to flash leedroid magisk file, thinking it was a ROM until i noticed the file size so I went back to stock via TWRP backup (i forgot I made) since RUU was giving 155 error.
2nd the HTC fastboot wasn't working for some reason.. adb devices cmd detected nothing, it worked at my job though since i have android studio/platform tools there (shrug) so used that fastboot instead.
3rd I did mean SW 2.48.617.1 that's the exact OS version # that download mode reports currently and was the last official update i took several days before going custom route.
Click to expand...
Click to collapse
Okay. Cool that you got it fixed. But you did say you were trying to update from 2.48.617.1 to 2.48.617.3, so that's why I said there was no .3

xunholyx said:
Okay. Cool that you got it fixed. But you did say you were trying to update from 2.48.617.1 to 2.48.617.3, so that's why I said there was no .3
Click to expand...
Click to collapse
oooh i see lol.. too many numbers.