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.
Related
Sorry, me again!
I needed to re-lock and ‘stockify’ my HTC M8 today for a few reasons. It ended up taking me 4 hours, and I still have no idea if it’s ‘back’ to the way it was before I rooted it. Before you carry on reading, please know I’m fully aware any lack of understanding is my fault, and perhaps I should have realised that compared to the N4s blissfully easy steps, the HTC was a massive can of worms. However, I’m going to ask the below anyway, so hopefully someone is friendly and helpful enough to aid me in my quest for enlightenment of android stuff without me having to spend more hours searching than actually reading useful stuff…
So coming from a Nexus 4, where the guide is super simple:
http://forums.androidcentral.com/ne...3923-guide-nexus-4-factory-image-restore.html
It turned out to be SERIOUSLY complicated. I’ve put down a ‘typical’ guide below, and put my questions about each step in bold. Sorry if it seems like I’m just complaining and being trite, but I’d like to know if A) I’ve missed a far easier way of doing this and if not B) is it just me that seems to have a massive amount of issues?
1. Made sure your device is S-Off. If not, download firewater and S-Off your device.
Assume this is just a thing that some phones have and some don’t?
2. Restore a nandroid of the stock Sense ROM, or find a stock ROM to flash. You'll have to dig around; I used a nandroid.
WHY? Is there no such thing as downloadable factory images for HTC One M8s? Also, where’s the step that says ‘run the commands fast boot erase user data, fast boot erase cache’ etc.?
3. Flash SuperSU.zip in recovery on top of the stock Sense ROM. You can find the SuperSU.zip here: http://download.chainfire.eu/396/SuperSU
Fair enough… still an another extra step compared to N4.
4. Use fast boot to flash the stock firmware zip to your device based on CID (this includes the stock recovery)
-This took SO MUCH EFFORT. Turns out I had to Super CID so that one of the recovery zips worked, because I was getting “FAILED (remote: 42 custom id check fail)” - and I’m now paranoid because I have no idea how important it is to get the correct CID-numbered ‘stock firmware’ etc. The ‘stock firmware’ zips seem to contain boot, radios, recovery .imgs, and with about 4 billion versions of the M8 apparently existing, could I have flashed a wrong boot or radio or something? ARE they even different per CID? Then I changed the CID back to O2___001 in case I need to take it in for warranty repairs, but is that trackable? Would someone know that I’ve messed around with the CID? Could someone going to look at my Nexus and be like “Oh this radio seems to be the one we’d expect on a HTC_001, NOT an O2___001 CID device, they must have tampered with it”.
—OH, and I had to boot into RUU mode as well, which apparently no one felt like explaining what the hell that’s for. So I’ve got and HBoot, a Fastboot, and RUU mode, which no clear way of knowing what to flash where…??
—-ALSO there was a HELL of a lot of faffing by people throwing around CID, MID, Verizon, Sprint, and comments like this doesn’t work on this AT&T model but will only work on non branded eu models with a flag attached to the speaker with an SSID of “600TZL” and a it MUST have a holographic projector otherwise your CID must equal the square root of the MID so that the factory image will know which ID your phone carrier provides through an inter web”.
5. Boot back up into sense, and follow this guide to remove the tampered banner in recovery. http://forum.xda-developers.com/show....php?t=2708565
-Is this just removing a banner? or is it ‘you’ve removed the banner from a visual point of view only, but if they actually look into it it will still appeared ‘tampered’.
6. Follow this guide to lock your boot loader and make it say **LOCKED** instead of **RELOCKED**. http://forum.xda-developers.com/show....php?t=2708571
-So ‘fast boot OEM lock’ doesn’t work on HTCs then- is that an N4 thing? Why all that complicated cmd line stuff? And on a side note, why is it that when referring to re-locking a N4 people call it just that- locking. But with an HTC people on XDA seem to say ‘to make the banner say locked’ as if its not actually locking it, just changing a bit of writing on the boot loader.
7. Boot your device back up, and open SuperSU. Go into settings and find the "full unroot" option and run that. Reboot your device like it suggests.
Does running the unroot zip (can’t find the thread) work? So I can make it appear like the HTC is brand new out of the box? Rather than having to go through the ‘first setup’ screen?
Other question: people seem to keep yammering on about modded RUUs, is there one? is there a couple? (i.e. should I view it a bit like TWRP and CWM- there’s others but there’s one everyone really uses). And if I ‘flash’ a modded RUU, again, is there an easily accessible stock one?
It's really not that complicated! I think the problem is comparing it to a Nexus 4 which is designed to be easily unlocked and locked, due to being a more developer orientated device.
An RUU is a stock image (like the Nexus images) and a modded one would just have the CID/MID requirement removed or something so it can be used on more phones. It would still be the stock, untampered image.
Also, the whole CID/MID thing is only applicable to American devices which vary between GSM and CDMA radios. ANY international modem will work in Europe and you will never find the wrong one.
S-Off is like unlocking the bootloader on a Nexus device except that in this case, its an extra step after unlocking the bootloader in order to be able to modify every partition and flash unsupported firmware in OEM mode. Every consumer phone is initially shipped S-On.
Thanks very much Veryone's v. helpful around here. Just a few more questions based on what you've said:
Matt said:
Also, the whole CID/MID thing is only applicable to American devices which vary between GSM and CDMA radios. ANY international modem will work in Europe and you will never find the wrong one.
Click to expand...
Click to collapse
Why did I have to Super-CID to install the stock recovery? And did I do the right thing by going back to my carrier CID afterwards?
Matt said:
S-Off is like unlocking the bootloader on a Nexus device except that in this case, its an extra step after unlocking the bootloader in order to be able to modify every partition and flash unsupported firmware in OEM mode. Every consumer phone is initially shipped S-On.
Click to expand...
Click to collapse
Although I've read in quite a few places I shouldn't have to S-On to take it in for a warranty repair, because some arrive to people S-off and they can't prove that you did it? Is that right?
Thank you for the step-by-step list. I am in the process of restoring my phone and all the guides say to look for "version-main", but that line is empty for me. What other information can I use to determine what recovery image to flash. Also the reason I want to go back to unrooted is so I can recieve OTA updates.
legolator said:
Thank you for the step-by-step list. I am in the process of restoring my phone and all the guides say to look for "version-main", but that line is empty for me. What other information can I use to determine what recovery image to flash. Also the reason I want to go back to unrooted is so I can recieve OTA updates.
Click to expand...
Click to collapse
this also happened to me- just another thing to confuse....
Can you not receive OTA updates if you're rooted? I thought it was just if you were running a different ROM?
tmorterlaing said:
this also happened to me- just another thing to confuse....
Can you not receive OTA updates if you're rooted? I thought it was just if you were running a different ROM?
Click to expand...
Click to collapse
I was under the impression that flashing a custom recovery removes the ability for the phone to install OTA updates. But I could of course be wrong about that.
The title basically says it all but I'll describe what I did so hopefully you guys can help.
Today I got tired of the ROM I was running and I figured I'd update my firmware before I flashed a new one just cause I hadn't done it in months. So I went and followed this guide: http://forum.xda-developers.com/showthread.php?t=2696282
I used this firmware: https://www.androidfilehost.com/?w=files&flid=32788
My CID is T-MOB010 just like the firmware's and I thought it would be a pretty simple thing, so I got to work.
First I rebooted to fastboot USB and did fastboot getvar all to make sure everything lined up, then I relocked the bootloader and did fastboot oem rebootRUU, all successfully.
Then I flashed the firmware and it all went great but I forgot to flash it a second time. I'm not sure if it's required, but anyway...
After it flashed successfully I did a fastboot reboot and my phone tried to reboot but it stalled on the white HTC splash screen, then went black, then the splash screen returned, then black, then it went into the stock recovery.
The stock recovery functions just fine and I attempted to just clear the cache and reboot but it did the exact same thing.
I don't currently have a stock Nandroid or RUU on my phone and I'm not even sure I have a way to get one on there besides using someone else's phone to put one on my SD.
Can anyone help me out? Is it even possible to get out of this? My bootloader is relocked and my phone can't get S-OFF (tried awhile ago multiple times). As of now I am all out of ideas/experience so I'm hoping you guys can help me. Thank you!!
UPDATE: I got myself into the HBOOT so I think I should be good now but I'll keep this around just in case.
Update: Once I got into hboot all was well, I just flashed TWRP again and got it going. Thanks everyone for the help!
Did you get it going again?
_jakeryan said:
I don't currently have a stock Nandroid or RUU on my phone
Click to expand...
Click to collapse
Just use the official RUU.exe which runs from a PC (with phone connected), not from the phone.
http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
RUU will also update your firmware.
Also, the firmware you linked is not the latest. Its the Android 4.4.4 firmware. The 5.0 (Lollipop) firmware would be 4.20.531.4
hack14u said:
Did you get it going again?
Click to expand...
Click to collapse
I did! Thank you redpoint for the help anyway!
_jakeryan said:
I did! Thank you redpoint for the help anyway!
Click to expand...
Click to collapse
Maybe add 'solved' to the topic? If that's still a thing.
_jakeryan said:
I did! Thank you redpoint for the help anyway!
Click to expand...
Click to collapse
Its not what your top post says, so its not clear whether you were trying to put the RUU.exe on the phone (which is incorrect), unsuccessful in putting on the phone or running an RUU.zip, or did the latter in addition to trying to run the RUU.exe from the PC (which was not originally mentioned). If the last one didn't work, it would help to have more details on failure mode, error messages, etc.
---------- Post added at 09:25 AM ---------- Previous post was at 09:23 AM ----------
_jakeryan said:
UPDATE: I got myself into the HBOOT so I think I should be good now but I'll keep this around just in case.
Click to expand...
Click to collapse
So is your issue resolve or not? Able to get a ROM or nandroid on the phone and flash/restore it?
---------- Post added at 09:26 AM ---------- Previous post was at 09:25 AM ----------
voidzero said:
Maybe add 'solved' to the topic? If that's still a thing.
Click to expand...
Click to collapse
Not everyone does it, but its certainly good to do, and still done from time to time. Its helpful so folks don't click on a link, intending to help someone that doesn't need the help anymore.
Same kinda problem.
I'm stuck in bootloader.
Any key I just brings me back to this again.
Even in HBOOT selecting Recovery or Factory reset does nothing other than bring up this screen.
Powering down and then on again has the same result.
I was trying to get back to stock. Typed in fastboot oem lock and after that... the problem started!!
Any ideas??
morgansgrandad said:
I'm stuck in bootloader.
Any key I just brings me back to this again.
Even in HBOOT selecting Recovery or Factory reset does nothing other than bring up this screen.
Powering down and then on again has the same result.
I was trying to get back to stock. Typed in fastboot oem lock and after that... the problem started!!
Any ideas??
Click to expand...
Click to collapse
This is intentional. When you relock the bootloader, it renders the phone unbootable and expects the RUU to be run.
redpoint73 said:
This is intentional. When you relock the bootloader, it renders the phone unbootable and expects the RUU to be run.
Click to expand...
Click to collapse
Ok. I'd downloaded what I assume is the correct RUU.exe. Ran it from the computer and I get a 131 error. Not the correct RUU !!
Stuck for a solution now!!
morgansgrandad said:
Ok. I'd downloaded what I assume is the correct RUU.exe. Ran it from the computer and I get a 131 error. Not the correct RUU !!
Stuck for a solution now!!
Click to expand...
Click to collapse
You shouldn't be assuming what RUU to run. What is your CID and hboot number? What RUU did you try to run?
HBOOT is 3.19.0.0000 CID, can't find.
RUU is M8_4.16.401.10_Europe.exe
morgansgrandad said:
HBOOT is 3.19.0.0000 CID, can't find.
RUU is M8_4.16.401.10_Europe.exe
Click to expand...
Click to collapse
The OS number (3.32.206.9) shown on your hboot screen (pic in your top post) indicates that is not the right RUU. The number in the x.xx.206.x is carrier specific,and seems to indicate that your phone is the O2 UK version. Running an RUU with version x.xx.401.x won't work. The number in the "401" spot would need to "206" for it to be the right RUU.
Not sure, but I don't think your CID has RUUs. If that is the case, your best bet it to unlock the bootloader again, flash TWRP back to the phone, and restore a nandroid with your software number (3.32.206.9) if you can find it. Then flash stock recovery back to the phone. That is as close to "stock" as you will get, if there is no RUU for your CID version.
redpoint73 said:
The OS number (3.32.206.9) shown on your hboot screen (pic in your top post) indicates that is not the right RUU. The number in the x.xx.206.x is carrier specific,and seems to indicate that your phone is the O2 UK version. Running an RUU with version x.xx.401.x won't work. The number in the "401" spot would need to "206" for it to be the right RUU.
Not sure, but I don't think your CID has RUUs. If that is the case, your best bet it to unlock the bootloader again, flash TWRP back to the phone, and restore a nandroid with your software number (3.32.206.9) if you can find it. Then flash stock recovery back to the phone. That is as close to "stock" as you will get, if there is no RUU for your CID version.
Click to expand...
Click to collapse
Thanks redpoint73. Looks like that's the only way to go!!
By looking at the radio, you need the Euro Version RUU. Looks like we gotta be detectives sometimes, lol.
Ok, I've unlocked the bootloader and am back to where it was.
It's running 5.0.1, Sense 6.0 and Android Revolution HD 34.6 by mike1986
I would like to clear that off and get back to stock with OTT updates.
Revolution HD 34.6 seems to use an awful lot of data. My other M8 has stock on-board, has identical apps etc and doesn't use nearly as much data as this one!!
Any further ideas??
morgansgrandad said:
Ok, I've unlocked the bootloader and am back to where it was.
It's running 5.0.1, Sense 6.0 and Android Revolution HD 34.6 by mike1986
I would like to clear that off and get back to stock with OTT updates.
Revolution HD 34.6 seems to use an awful lot of data. My other M8 has stock on-board, has identical apps etc and doesn't use nearly as much data as this one!!
Any further ideas??
Click to expand...
Click to collapse
Why not just set it up for Dev / Unlocked Edition?
http://www.htc.com/us/support/htc-one-m8/news/
hack14u said:
Why not just set it up for Dev / Unlocked Edition?
http://www.htc.com/us/support/htc-one-m8/news/
Click to expand...
Click to collapse
I'm downloading that now. BUT...........
Because of all my faffing on!! there's NO OS on the phone.
I'm really struggling now:crying:
This is my position now. Totally unusable phone!!
I would appreciate ANY help on getting back to as near as normal as possible.
Thank you.
I should add, the RUU messages are from trying post #16.
And the saga continues!
I found a nandroid backup with the same s/w number as mine, downloaded it from MEGA (it seemed to d/l ok).
When I ran it through TWRP I got signature verification failed.
This phone could end up in the depths of the river Tyne
morgansgrandad said:
This is my position now. Totally unusable phone!!
I would appreciate ANY help on getting back to as near as normal as possible.
Thank you.
I should add, the RUU messages are from trying post #16.
Click to expand...
Click to collapse
What hack14u neglected to mention, is that to run another version's RUU, you need s-off ($25 by sunshine), and then you need to change your MID and CID.
Relocking the bootloader (to run RUU) renders the phone with no OS, this is by design.
---------- Post added at 09:41 AM ---------- Previous post was at 09:34 AM ----------
morgansgrandad said:
And the saga continues!
I found a nandroid backup with the same s/w number as mine, downloaded it from MEGA (it seemed to d/l ok).
When I ran it through TWRP I got signature verification failed.
This phone could end up in the depths of the river Tyne
Click to expand...
Click to collapse
Hang in there, modding phones can often be an exercise in frustration. But the phone is quite recoverable, as long as you perform the correct steps.
A nandroid is not a flashable zip (such as a ROM). It needs to be restored in a very different way, its described in Post 3 of the stock nandroid thread (assuming that is where you go it from) under Question & Answers.
To summarize, you need to:
1) Unpack the zipk, which is a number of folders
2) Move the folders to the proper location on the phone's internal storage (removable SD is also possible, if you setup TWRP to back and restore to that location)
The exact location if very important (its described in Post 3 of the stock nandroid thread), since when restoring a nandroid, TWRP will not see the file to restore if you have it wrong. This is in direct contrast to installing a ROM zip, in which TWRP allows you to browse anywhere on the storage to find the file to flash.
3) Choose the menu option to RESTORE, not INSTALL
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.
Hi every one I have htc one m8 now 2-3 years, I rooted and unlocked bootloader, on stock firmware which is : 4.18.708.12 and now I have system updates that I cant update cuz im rooted , so I relocked bootloader and tried to update , still when i try it goes to fastboot with this : system software modified, security warning and it doesnt update nor perform a factory reset, can some one help me out here? id be glad I need this help asap
You need stock ROM, and stock recovery to update by OTA.
Return to stock ROM and stock recovery using this thread (which will then allow you to update): http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Relocking the bootloader isn't necessary to OTA (only to RUU or flash signed firmware.zip) and didn't help you matters. You'll need to unlock it again in order to perform the process linked above.
Factory reset also won't help your condition, so there isn't a point in doing so. Factory reset is a bit of a misnomer, all it does is wipe user data. It won't restore a previous OS, nor remove root, etc.
redpoint73 said:
You need stock ROM, and stock recovery to update by OTA.
Return to stock ROM and stock recovery using this thread (which will then allow you to update): http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Relocking the bootloader isn't necessary to OTA (only to RUU or flash signed firmware.zip) and didn't help you matters. You'll need to unlock it again in order to perform the process linked above.
Factory reset also won't help your condition, so there isn't a point in doing so. Factory reset is a bit of a misnomer, all it does is wipe user data. It won't restore a previous OS, nor remove root, etc.
Click to expand...
Click to collapse
I want my phone to be back to stock like it came from the company, with the original ruu and firmware signatures, if i install stock rom and stock recovery that way im still rooted in which case I dont want it, I wanna get back to original LB and Unrooted with warrenty back
madshark2009 said:
I want my phone to be back to stock like it came from the company, with the original ruu and firmware signatures, if i install stock rom and stock recovery that way im still rooted in which case I dont want it, I wanna get back to original LB and Unrooted with warrenty back
Click to expand...
Click to collapse
If that is what you wanted, then no mention was made of that in your OP (which you should have done). You should be specific about what you want, and not make it harder for folks trying to help you.
You are incorrect (that after installing the stock ROM, you will still be rooted). Installing the stock ROM will remove root. That's the whole point of the thread I linked.
If there is an RUU for your version number, just use it to return to almost full stock. When I say "almost", its because the bootloader will only say RELOCKED instead of LOCKED. The only way to make it say LOCKED (after its been unlocked) is with s-off. And if you don't already have s-off, it will cost you $25 by sunshine. Probably not worth the cost, as you no longer have warranty, anyway. HTC warranty is only valid for 1 year.
redpoint73 said:
If that is what you wanted, then no mention was made of that in your OP (which you should have done). You should be specific about what you want, and not make it harder for folks trying to help you.
You are incorrect (that after installing the stock ROM, you will still be rooted). Installing the stock ROM will remove root. That's the whole point of the thread I linked.
If there is an RUU for your version number, just use it to return to almost full stock. When I say "almost", its because the bootloader will only say RELOCKED instead of LOCKED. The only way to make it say LOCKED (after its been unlocked) is with s-off. And if you don't already have s-off, it will cost you $25 by sunshine. Probably not worth the cost, as you most likely don't have a warranty, anyway. HTC warranty is only valid for 1 year.
Click to expand...
Click to collapse
and how do i decide which RUU is suitable for my device?
android 5.0.1
software number : 4.18.708.12
I must point out that I never installed a custom rom nor recovery I just unlocked bootloader and rooted and thats it so how do I find my ruu and what to do if i dont?
Its not actually clear what you are trying to do. Return to stock to update? Or something else? Your later post says return to stock for warranty, but no way you have warranty at this point. Is something wrong with the phone? Or just trying to return the phone to stock to sell or trade it?
Can't really provide proper guidance unless we know your intent.
---------- Post added at 12:13 PM ---------- Previous post was at 12:11 PM ----------
madshark2009 said:
and how do i decide which RUU is suitable for my device?
software number : 4.18.708.12
how do I find my ruu and what to do if i dont?
Click to expand...
Click to collapse
You look for an RUU for that version number you just posted.
If no RUU, the process I linked for you in the first place will return you to full stock, with the exception of bootloader will be UNLOCKED. Or you can make it RELOCKED. Not really much different from what an RUU would give you.
redpoint73 said:
Its not actually clear what you are trying to do. Return to stock to update? Or something else? Your later post says return to stock for warranty, but no way you have warranty at this point. Is something wrong with the phone? Or just trying to return the phone to stock to sell or trade it?
Can't really provide proper guidance unless we know your intent.
---------- Post added at 12:13 PM ---------- Previous post was at 12:11 PM ----------
You look for an RUU for that version number you just posted.
If no RUU, the process I linked for you in the first place will return you to full stock, with the exception of bootloader will be UNLOCKED. Or you can make it RELOCKED. Not really much different from what an RUU would give you.
Click to expand...
Click to collapse
I didnt mean to get my warrenty back, I meant to get back to stock just like when getting back to original phone status like it came from the company, so I understood that flashing stock rom and recovery will help me with geting back and stat updating normally, but the precess seems too complicated to understand I might need your further help perferably vie Direct message, but just to save all the efforts, Id perfer the RUU flashing, and since you said none original RUU that has the same number of my version , that means I can install any one I want? whats the difference between RUUs and how do I choose the perfect one
(sorry i am new thats why i ask a lot )
madshark2009 said:
I didnt mean to get my warrenty back
Click to expand...
Click to collapse
But its exactly what you posted:
madshark2009 said:
I wanna get back to original LB and Unrooted with warrenty back
Click to expand...
Click to collapse
I strongly suggest you take a bit more time thinking about what you post, and making sure its properly typed, (lack of proper capitalization, spelling and punctuation makes your posts a pain to read, to say the least) and conveys what you want it to. Otherwise, you're just making it harder for folks to understand and help you.
Any time you think you are saving by typing quickly, is being lost x10 by me having to ask you to clarify what you mean.
madshark2009 said:
so I understood that flashing stock rom and recovery will help me with geting back and stat updating normally, but the precess seems too complicated to understand
Click to expand...
Click to collapse
The process isn't complicated. If you managed to unlock the bootloader and root the phone, you can certainly accomplish restoring the stock ROM and stock recovery. On that same note, it can be fairly said that anyone that is unable restore the phone by that method; probably shouldn't have unlocked the bootloader and rooted to begin with. Or look at it a slightly different way: you should never root a device without knowing how to return it to stock.
The guide looks long, mostly because its written in a very highly detailed, step-by-step manner (some folks seem to like that). But it just boils down to downloading the proper file, unzipping the folders, putting them in the right location on the phone, and restoring in TWRP.
If you have issues on a particular step, feel free to post again here, or the TWRP stock backup thread we are discussing.
madshark2009 said:
Id perfer the RUU flashing, and since you said none original RUU that has the same number of my version , that means I can install any one I want? whats the difference between RUUs and how do I choose the perfect one
Click to expand...
Click to collapse
I never said there was no RUU for your version number; or did you determine that yourself (your wording isn't clear)? I don't definitely know if there is or not; I was leaving it up to you to search. But doing a quick search myseld, it looks like NO.
If you looked, and there is no RUU for your version, you certainly cannot run any RUU you like. In fact, you can't run any RUU at all, unless its intended for your version, CID, MID.
redpoint73 said:
You need stock ROM, and stock recovery to update by OTA.
Return to stock ROM and stock recovery using this thread (which will then allow you to update): http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Relocking the bootloader isn't necessary to OTA (only to RUU or flash signed firmware.zip) and didn't help you matters. You'll need to unlock it again in order to perform the process linked above.
Factory reset also won't help your condition, so there isn't a point in doing so. Factory reset is a bit of a misnomer, all it does is wipe user data. It won't restore a previous OS, nor remove root, etc.
Click to expand...
Click to collapse
I downloaded signed firmware that has the same CID and MID but marshmellow not lolipop (I had lolipop and flashed marshmallow firmware) and now phone is stuck at black screen
madshark2009 said:
I downloaded signed firmware that has the same CID and MID but marshmellow not lolipop (I had lolipop and flashed marshmallow firmware) and now phone is stuck at black screen
Click to expand...
Click to collapse
Why did you flash signed firmware? Its not a ROM, not an RUU. Nobody told you to do this.
Black screen, as in the screen doesn't come on? Not a good sign.
redpoint73 said:
Why did you flash signed firmware? Its not a ROM, not an RUU. Nobody told you to do this.
Black screen, as in the screen doesn't come on? Not a good sign.
Click to expand...
Click to collapse
yes thats what it means! what can i do now?
redpoint73 said:
Why did you flash signed firmware? Its not a ROM, not an RUU. Nobody told you to do this.
Black screen, as in the screen doesn't come on? Not a good sign.
Click to expand...
Click to collapse
i found my version number in TWRP backup 4.18.708.12_ckpv5 can i use this to flash through ADB? because I cant flash TWRP recovery after what i did it says error bootloader signatures veryfication.. what are my options man?
madshark2009 said:
yes thats what it means! what can i do now?
Click to expand...
Click to collapse
How did you flash the firmware? By fastboot, or SD card method?
What's the exact file name for what you flashed?
Any error messages?
Did it tell you to flash again (very common, but actually says "flush image immediately"), and if so, did you flash it again?
Try holding power button and vol up for a minute or more, and see if there is any change.
redpoint73 said:
How did you flash the firmware? By fastboot, or SD card method?
What's the exact file name for what you flashed?
Any error messages?
Did it tell you to flash again (very common, but actually says "flush image immediately"), and if so, did you flash it again?
Try holding power button and vol up for a minute or more, and see if there is any change.
Click to expand...
Click to collapse
flashed by fastboot the way its mentioned in the thread you sent me.. on how to flash marshmallow signed firmwares and now when I rebooted as instructed it gets stuck at black screen after HTC logo on white screen and so I thought I could fix this by flashing twrp but now it says bootloader signatures veryfication error, so I cant proceed to the installation ..
madshark2009 said:
i found my version number in TWRP backup 4.18.708.12_ckpv5 can i use this to flash through ADB? because I cant flash TWRP recovery after what i did it says error bootloader signatures veryfication.. what are my options man?
Click to expand...
Click to collapse
You have to get the phone back on, in one mode or another, before you can do anything.
No, you can't flash the stock TWRP backup with adb. Its a TWRP backup, and you have to restore it with TWRP.
You can't flash custom recovery with the bootloader locked. That is why you have signature verification error. You need to unlock the bootloader again, which I already told you. And you need to be in bootloader-fastboot mode to flash it, anyway. I thought you said the screen wasn't coming on?
redpoint73 said:
You have to get the phone back on, in one mode or another, before you can do anything.
No, you can't flash the stock TWRP backup with adb. Its a TWRP backup, and you have to restore it with TWRP.
You can't flash custom recovery with the bootloader locked. That is why you have signature verification error. You need to unlock the bootloader again, which I already told you. And you need to be in bootloader-fastboot mode to flash it, anyway. I thought you said the screen wasn't coming on?
Click to expand...
Click to collapse
yes it got a black screen.
to Unlock bootloader I need what exactly?
madshark2009 said:
flashed by fastboot the way its mentioned in the thread you sent me.. on how to flash marshmallow signed firmwares
Click to expand...
Click to collapse
I told you to restore a stock ROM and stock recovery from the thread (Post #1). I said nothing about flashing a signed firmware (Post #5) which is not part of returning to stock.
---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------
madshark2009 said:
yes it got a black screen.
to Unlock bootloader I need what exactly?
Click to expand...
Click to collapse
You can't do anything with the phone off.
I asked you to try something in Post #13 above. Please read everything I post, and stop jumping around and trying random things. Read carefully, and proceed with caution and attention. Rushing around isn't going to help anything, and may do permanent damage to the phone (if you haven't already).
redpoint73 said:
I told you to restore a stock ROM and stock recovery from the thread (Post #1). I said nothing about flashing a signed firmware (Post #5) which is not part of returning to stock.
---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------
You can't do anything with the phone off.
I asked you to try something in Post #13 above. Please read everything I post, and stop jumping around and trying random things. Read carefully, and proceed with caution and attention. Rushing around isn't going to help anything, and may do permanent damage to the phone (if you haven't already).
Click to expand...
Click to collapse
so what are my options now?
madshark2009 said:
so what are my options now?
Click to expand...
Click to collapse
Your options are to read more carefully.
I seriously do not like repeating myself; especially having to repeat myself when I say "read more carefully" and try what I already told you several posts ago.
redpoint73 said:
Your options are to read more carefully.
I seriously do not like repeating myself; especially having to repeat myself when I say "read more carefully" and try what I already told you several posts ago.
Click to expand...
Click to collapse
ok it worked now im back to stock..
but now there are no software updates available
PS: I did exactly what the post said! now i am back to stock rom with stock recovery and when i go to check updates it says my device is up to date (on lolipop 5.0.1) but before I had 6.0.1 marshmallow available now its not.
Ok, friend gave me his old HTC One (M8)
Its locked to EE network, Whenever its on HTC Sense Input constantly stops working, I have attempted the fix many forums and youtubes say to just clear the Cache... but this has not helped. I came to conclusion that the OS itself has been corrupted and Factory Reset does not help. I have attempted many Ruu's trying to find the correct one running it from the PC but all say wrong signature. I see things like Fastboot and cmd commands but the bootup screen has no way to type so I must be missing something. I have read guides and such but many seem to have files missing from their uploaded guide lines. So I come to this... please help.
Here's how the Power + Up Arrow screen looks.
*** Software Status: Modified ***
*** Locked ***
*** Security Warning ***
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.61.4
eMMC-boot 2048
After that it's just date/time stamp and the boot options
Edit...
So the closest I've gotten is using the guild here (androidforums.com/threads/htc-one-m8-unusable.995871/#post-7212766)
I have fastboot now installed, stuck on the twrp part as getting anything actually installed on the phone itself is impossible due to the Sense Input not working. At least though what I know what to do. Letting the phone boot normally just ends up with the HTC Sense Input looping and crashing.
From Fastboot getvar all
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
Renaan said:
HTC One (M8) please Help me fix this stupid phone....
Click to expand...
Click to collapse
I strongly suggest you reword the title of the thread. Just because you don't know what to do, doesn't make the phone "stupid". Coming onto this forum, and name calling (the device) is not a good idea. Most folks who you are asking help from, must hold this device in fairly high regard, to be spending their free time to help others with it.
While well-intentioned, it's apparent your knowledge of this device, as well as some common Android tools, is pretty limited. Therefore, you're making some mistakes and incorrect assumptions. That isn't an insult. You only know what you know, and we all hard to start somewhere.
Renaan said:
I have attempted many Ruu's trying to find the correct one running it from the PC but all say wrong signature.
Click to expand...
Click to collapse
You can only run the RUU which is intended for the device's specific CID. There are many (dozens?) of RUUs for the different M8 versions. So you aren't going to find the right one by guessing. In fact, I don't think the your M8 version has an RUU (at least, not for free).
Recovering a device without RUU is possible, but it's somewhat involved. It's going to require an investment of time and effort (and some knowledge gained - not altogether a bad thing).
Renaan said:
I see things like Fastboot and cmd commands but the bootup screen has no way to type so I must be missing something.
Click to expand...
Click to collapse
Fastboot works by connecting the phone to a computer, which needs to have a fastboot environment setup on it. Again, I can go into it. But I want to make sure you are willing to put forth the time and effort, to go through with the whole process. Otherwise, advising you on how to use fastboot in itself is not going to get the phone up and running, and not worthwhile.
Renaan said:
I have read guides and such but many seem to have files missing from their uploaded guide lines.
Click to expand...
Click to collapse
Can't help or advise on this, unless you are specific about what those guides are, or what specific actions/methods you are attempting. I know you don't have enough post to put up links. But you can at least describe what guides, if you want specific advice on them.
---------- Post added at 01:36 PM ---------- Previous post was at 01:03 PM ----------
Renaan said:
I have fastboot now installed, stuck on the twrp part as getting anything actually installed on the phone itself is impossible due to the Sense Input not working. At least though what I know what to do. Letting the phone boot normally just ends up with the HTC Sense Input looping and crashing.
Click to expand...
Click to collapse
Installing TWRP is not related to the OS getting "stuck". TWRP (custom recovery) boots independently of the Android OS, and in fact installing TWRP doesn't even require the OS to be working at all. It just requires being able to access bootloader-fastboot mode (which you can).
But installing TWRP is going to fail, unless you first unlock the bootloader.
You can use the following guide to unlock the bootloader (see Section 1): https://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
But keep in mind that some files (like TWRP version) in the guide are outdated. I recommend current TWRP version 3.1.1-0, which you can get from here: https://dl.twrp.me/m8/
Only perform the part of the guide relevant to unlocking the bootloader and installing TWRP. No need to root (and the SuperSU file linked is outdated), or any of the rest of the guide.
---------- Post added at 01:42 PM ---------- Previous post was at 01:36 PM ----------
Renaan said:
So the closest I've gotten is using the guild here (androidforums.com/threads/htc-one-m8-unusable.995871/#post-7212766)
Click to expand...
Click to collapse
You are on the right track: restore stock TWRP backup, since no RUU available for 6.12.61.4
But I'd suggest just using the original XDA thread, which is referenced in the Android forums thread you linked: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Just follow up through Step 9, and reboot. The rest isn't needed (no more updates for this phone).
I suppose the Android Forums post has a bit more explanation. But ckpv5 deserves full credit for doing all the work posting the files and maintaining the thread.
redpoint73 said:
I strongly suggest you reword the title of the thread. Just because you don't know what to do, doesn't make the phone "stupid". Coming onto this forum, and name calling (the device) is not a good idea. Most folks who you are asking help from, must hold this device in fairly high regard, to be spending their free time to help others with it.
I suppose the Android Forums post has a bit more explanation. But ckpv5 deserves full credit for doing all the work posting the files and maintaining the thread.
Click to expand...
Click to collapse
So I'm already stuck on getting twrp onto the phone, the HTCDev site which I need to unlock the Bootloader just seems to loop on itself when attempting to register.
How can I get twrp installed ?
Renaan said:
So I'm already stuck on getting twrp onto the phone, the HTCDev site which I need to unlock the Bootloader just seems to loop on itself when attempting to register.
How can I get twrp installed ?
Click to expand...
Click to collapse
The HTCDev.com website can be buggy. Maybe wait a while, and try later. I also remember having to use a couple different email addresses to register, before it worked (as it wouldn't take the same email address I already used).
There is no way around it. You need to unlock the bootloader in order to install a custom recovery, by definition.
Also, please refrain from including my whole post (when it's a long one, like the last one) in your response; as it clutters up the forum. I know it's the default (to quote the post you are replying to) when you reply. But just delete it (you can edit your previous post).
Progress....
So,
I have kinda made progress... kinda
It tells me to make a backup so I can find out where the backup goes on internal storage.... but nowhere can I find it... I have simply tried searching for backup and nothing, mounting as usb to search also comes up nothing and I'm not sure what I'm even doing wrong.
I went and made sure to download the correct zipe for my carrier as towards the end it asks me to flash an img... but nowhere does it seem to provide one. I've downloaded the correct ckpv5.zip for my phone but there's no recovery.img file in it, again, not sure what I'm messing up .
Renaan said:
It tells me to make a backup so I can find out where the backup goes on internal storage.... but nowhere can I find it... I have simply tried searching for backup and nothing, mounting as usb to search also comes up nothing and I'm not sure what I'm even doing wrong.
Click to expand...
Click to collapse
In TWRP, in the Backup option, make sure Internal Storage is selected as the storage location (button near the top of the "Backup" screen. It's also possible to select the SD card as the save location, if you have an SD inserted in the phone.
Once internal storage is selected as the save location for the backup, check "boot" and back it up. It's a little irrelavent what you backup. The idea is to just backup "something" so that TWRP creates the proper folder structure, and "boot" is the smallest thing to backup (something like 50 MB, as opposed to backing up System, which is like 1.5 GB).
Make sure TWRP says the backup was successful. After that, you should easily find the folder TWRP in the main directory of internal storage. Inside the TWRP folder, you will find the Backup folder, and inside that, a folder with your phone's serial number (don't post that number - it's personal info). That is where you want to copy the stock TWRP files you extracted from ckpv5's collection.
Renaan said:
I went and made sure to download the correct zipe for my carrier as towards the end it asks me to flash an img... but nowhere does it seem to provide one. I've downloaded the correct ckpv5.zip for my phone but there's no recovery.img file in it, again, not sure what I'm messing up .
Click to expand...
Click to collapse
The stock recovery is not included in the same folder as the stock system and boot. Stock recoveries are in Post #4 of the collection. But you don't need to do it. I already stated above, you only need to perform through Step 9 of the guide. Than just reboot, and setup the phone.
No need to flash stock recovery. It's a waste of time, as your phone will not get anymore updates from HTC, and that is really the only reason to install stock recovery for the device. Plus, if anything goes wrong, and you need to use TWRP again, it won't be there (it will have been over-written by stock recovery) and you will waste more time flashing TWRP back on the phone, if you nee to use it.
Fixed!
ok, Everything seems fixed now, no img was needed just putting things in correct place I guess..
Thankyou for the helps
Renaan said:
ok, Everything seems fixed now, no img was needed just putting things in correct place I guess..
Thankyou for the helps
Click to expand...
Click to collapse
Glad it worked out for you. The process to restore by stock TWRP backup (since no RUU) is not trivial. So nice job, and I'm sure you learned some things in the process!