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] Can we get SuperCID with this?

Hey Guys!
I noticed an article on a android news site
It stated that the HTC Droid Incredible 4G got bootloader unlocked.
They used a method to get SUPERCID
Which means that the devices CID gets overwritten by all 1's.
This basically tricks the HTCDev website into unlocking it..
Which is great but not very usefull for us here..
But!
I want to know, can this method be used to overwrite CIDs in phones which cannot update to the latest JB RUU?
If this is possible everyone could use the JB RUU and ofcourse this will help developers..
As I already stated: I am not sure, and I do not advise anyone to try this unles syou know what you are doing.
Thr original thread is here: http://forum.xda-developers.com/showthread.php?t=1986346

No, no and no

you need S-OFF to get superCID

matt95 said:
you need S-OFF to get superCID
Click to expand...
Click to collapse
I'm sorry, misused a term here..
Its not a superCID but a fakeCID method they use..
But I must say, they do not have S-OFF and still can change the CID of the device..
So excuse me for asking but, if they can change the CID with only temproot,
Than we should also be able to do that..
And trick the JB RUU in thinking every device can use it..
So can someone explain me why this is not possible?
btw, I have a HTC__001 CID, so... Do'nt need it, but others may!

Giblet-dono said:
I'm sorry, misused a term here..
Its not a superCID but a fakeCID method they use..
But I must say, they do not have S-OFF and still can change the CID of the device..
So excuse me for asking but, if they can change the CID with only temproot,
Than we should also be able to do that..
And trick the JB RUU in thinking every device can use it..
So can someone explain me why this is not possible?
btw, I have a HTC__001 CID, so... Do'nt need it, but others may!
Click to expand...
Click to collapse
no man. people would have already used that method if it had been so easy

matt95 said:
no man. people would have already used that method if it had been so easy
Click to expand...
Click to collapse
So... Over at the One S forum they are using this method now and it works!
I want to try it on the One X, But I really need to know which partition I need to edit..
- Nevermidn this ¬¬ I know already
And for the ones that want o know why:
Nvidia is actually messing it all up!
The rest are all qualcom bootloaders.. but this is different because of the tegra 3!
Thats why it does work on the ATT XL, the One S and other qualcomm phones..

Giblet-dono said:
So... Over at the One S forum they are using this method now and it works!
I want to try it on the One X, But I really need to know which partition I need to edit..
Click to expand...
Click to collapse
they are completely different phones...

matt95 said:
they are completely different phones...
Click to expand...
Click to collapse
already editted my post
Also I msut say.>
I ahven't gotten any reason why It would not work..
I finally read on another forum why it would not work..
You all just say: it won;t work, it won't work..
Without giving a reason or anything, and that annoys me pretty much..
I mean, without a reason people will keep on trying and searching..
So please give a proper reason, that helps alot!

Giblet-dono said:
Without giving a reason or anything, and that annoys me pretty much..
I mean, without a reason people will keep on trying and searching...
Click to expand...
Click to collapse
It's been mentioned about 10 times before and that annoys people pretty much.

BenPope said:
It's been mentioned about 10 times before and that annoys people pretty much.
Click to expand...
Click to collapse
completely agree :good:

Method to obtain S-OFF?

According to this thread http://forum.xda-developers.com/showthread.php?t=1632200 by 7pellc he was able to get his device into an unlocked state.
While flashing a RUU the process crashed at "WRITING USER DATA".
He then rebooted the phone and found the rom to be unusable, so he rebooted to HBOOT only to find it being stuck in RUU mode.
HBOOT still reported device to be LOCKED, and for some reason he rebooted to recovery, and then back into HBOOT finding the device in an unlocked state.
Instead of LOCKED/RELOCKED/UNLOCKED HBOOT reported only ******
He then fastboot flashed a boot.img which it accepted even though this device was never unlocked through HTCDev.
It seems to me that the exact procedure temporarily left the device in some form of unlocked state, and maybe the eMMC was actually unlocked.
If this was the case it should have been possible to perform fastboot commands to acheive SuperCID or even S-OFF:
fastboot oem writesecureflag 0
fastboot oem writecid 11111111
I am not sure anyone ever recreated his steps, and the important step is to reach the state where HBOOT reports only ****** instead of LOCKED states.
I would love to try this out myself, but I sold my HOX when SGS3 came out as it was a true unlocked device.
Some of my friends still has this phone, and they come to me when something is wrong with it, and if I can persuade them to try this on their phones I would like to try it ofcourse.
I am really sorry if anyone actually recreated the exact steps, but I have read all the threads about S-OFF, and couldn't find someone who performed the opreation, but if I'm mistaken I'm sorry, and this thread can be closed.

S-OFF not possible !

Mr Hofs said:
S-OFF not possible !
Click to expand...
Click to collapse
Please refrain from posting here if you can't contribute with anything!

spngbb said:
Please refrain from posting here if you can't contribute with anything!
Click to expand...
Click to collapse
But he's speaking the truth.. S-OFF isn't possible, and if you did some research you would know that Please refrain from asking questions before doing your research.
https://www.youtube.com/watch?v=JmvCpR45LKA

Actually if the emmc was unlocked as the op describes then it would be possible but I'm very sceptical that it actually was.
During the ruu sequence the emmc is indeed unlocked however upon rebooting it gets locked again
This is the same principal that the soff for xl uses however they strictly say you mustn't power off your device because it relocks the security.
I have spent some time looking at this exploit.
It is technically possible to have the emmc unlocked and accept fastboot commands by flashing an updated firmware. (Note it has to be an update and not the same as you already have)
Once first flash of the firmware you get an error and then have to flash again straight away but if you don't flash again you can run other commands with the emmc unlocked.
This is where this method hits a dead end.
In order to progress further we need to be in android which would normally be done with
Fastboot boot boot.IMG or fastboot oem boot however since early hboot versions. I think 1.12. this ability was removed and the command just either errors or crashes the device
Sent from my HTC One X using xda app-developers app

Agil1ty said:
But he's speaking the truth.. S-OFF isn't possible, and if you did some research you would know that Please refrain from asking questions before doing your research.
Click to expand...
Click to collapse
Oh wel, oh well...
I know that the S-OFF progress by xmoo and others has stopped/is on-hold, but saying that S-OFF is impossible is a bad attitude to solving a problem.
I did my research and did not find someone who tested out this method. So, really if you have nothing to contribute with, then please go find someone else to annoy!

bagofcrap24 said:
Actually if the emmc was unlocked as the op describes then it would be possible but I'm very sceptical that it actually was.
During the ruu sequence the emmc is indeed unlocked however upon rebooting it gets locked again
This is the same principal that the soff for xl uses however they strictly say you mustn't power off your device because it relocks the security.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Actually I came up with this idea after reading the threads about the new S-OFF method for XL.
I don't think the eMMC is actually unlocked in the RUU process, the key to achieveing this lies in the sequence of boot back and fourth from RUU mode to the stock recovery and then back to HBOOT.
If the theory is worth anything something happens in the process making HBOOT not recognize the secureflag thus reporting only *****
Ofcourse this is all theory, but who knows
As mentioned in my first post, I cannot test this out myself, and I would never have brought this up if I was able to test it and found it not to be working!

Just telling the truth ..... Sorry for letting you know a fact at the moment.
And you could be a bit nicer you know. I was not rude, bad mouthed or aggressive towards you in any way.....so i expect it the same the other way around !

spngbb said:
Oh wel, oh well...
I know that the S-OFF progress by xmoo and others has stopped/is on-hold, but saying that S-OFF is impossible is a bad attitude to solving a problem.
I did my research and did not find someone who tested out this method. So, really if you have nothing to contribute with, then please go find someone else to annoy!
Click to expand...
Click to collapse
Now now, there is no excuse to behave this way.
Sent from...... The Milky Way

Mr Hofs said:
Just telling the truth ..... Sorry for letting you know a fact at the moment.
And you could be a bit nicer you know. I was not rude, bad mouthed or aggressive towards you in any way.....so i expect it the same the other way around !
Click to expand...
Click to collapse
Sorry, but a statement like your first post in this thread is just pointless. So rude or not... We can call it stupid if you prefer!
maxilick said:
Now now, there is no excuse to behave this way.
Sent from...... The Milky Way
Click to expand...
Click to collapse
I don't follow exactly... I said please

spngbb said:
Sorry, but a statement like your first post in this thread is just pointless. So rude or not... We can call it stupid if you prefer!
Click to expand...
Click to collapse
Pfffff stupid......yeah well i can say a lot about that but i won't. Its pointless and leading to nowhere ! I will let it rest here....because you are so smart
Good luck with your s-off.....

spngbb said:
Sorry, but a statement like your first post in this thread is just pointless. So rude or not... We can call it stupid if you prefer!
I don't follow exactly... I said please
Click to expand...
Click to collapse
Pointless going on with this if you can't see, have a great day.
Sent from...... The Milky Way

Tester needed

Anyone brave enough to test an hboot that removed the development test on boot?
Requirements:
S-Off
fastboot knowledge
Brave soul
Click to expand...
Click to collapse
Before flash
Durring flash
After flash
Video of boot
Files:
will be sent a link on pm
Commands to run:
Code:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip hboot_nonag.zip
fastboot reboot-bootloader

I'm not s-off, but what does this do?

crazyg0od33 said:
I'm not s-off, but what does this do?
Click to expand...
Click to collapse
When you're S-Off there's a little warning message that pops up on the splash screen on bootup, I'm guessing this gets rid of that. I am definitely not brave enough to try it, but it'd be cool if someone could confirm it worked.

PapaSmurf6768 said:
When you're S-Off there's a little warning message that pops up on the splash screen on bootup, I'm guessing this gets rid of that. I am definitely not brave enough to try it, but it'd be cool if someone could confirm it worked.
Click to expand...
Click to collapse
Exactly that. If we wanted to we could add a custom message to it as well.

why not try and make a plug in for this?
http://forum.xda-developers.com/showthread.php?t=1786498
unless it's been confirmed to not work on newer HTC devices?
It was a lot of fun playing with it on the HTC Inc4G LTE
unfortunately I don't know how to make the plug-in or I'd make one and try it when my phone comes back from Sonic.

andybones said:
why not try and make a plug in for this?
http://forum.xda-developers.com/showthread.php?t=1786498
unless it's been confirmed to not work on newer HTC devices?
It was a lot of fun playing with it on the HTC Inc4G LTE
unfortunately I don't know how to make the plug-in or I'd make one and try it when my phone comes back from Sonic.
Click to expand...
Click to collapse
I used it on my Sprint HTC One, but I think it was only for hboot 1.44

sofla2 said:
I used it on my Sprint HTC One, but I think it was only for hboot 1.44
Click to expand...
Click to collapse
it has to be made for that specific phone and hboot.
otherwise you're asking for a brick
actually anytime you flash hboot you're risking a brick..
but we'd need someone to edit our current hbot and make a patch for this phone and this hboot.

andybones said:
it has to be made for that specific phone and hboot.
otherwise you're asking for a brick
actually anytime you flash hboot you're risking a brick..
but we'd need someone to edit our current hbot and make a patch for this phone and this hboot.
Click to expand...
Click to collapse
Agreed any time you flash hboot you want to pray to your god that there's no power outages, the laptop battery will last, no one will trip on any cord between the computer and phone, cross your fingers and hold your breath. This one was pulled from my phone and modified so it is 1.54 for vzw.
-- Edit --
It is also noted if for any reason you s-on with a custom hboot you brick.

jmstumme said:
Agreed any time you flash hboot you want to pray to your god that there's no power outages, the laptop battery will last, no one will trip on any cord between the computer and phone, cross your fingers and hold your breath. This one was pulled from my phone and modified so it is 1.54 for vzw.
-- Edit --
It is also noted if for any reason you s-on with a custom hboot you brick.
Click to expand...
Click to collapse
always ruu before you s-on for warranty purposes, most people do not need a custom bootloader unless it is part of an exploit

Updated with screenshots and videos

123421342 said:
always ruu before you s-on for warranty purposes, most people do not need a custom bootloader unless it is part of an exploit
Click to expand...
Click to collapse
So it works then?

PapaSmurf6768 said:
So it works then?
Click to expand...
Click to collapse
Works for me, I would like some testers before general. Release thought.
Sent from my HTC6500LVW using Tapatalk 2

PapaSmurf6768 said:
So it works then?
Click to expand...
Click to collapse
I don't know how that relates to my comment. I was just letting people know there is no reason to flash a bootloader because of the HUGE risk of hard, hard brick and no benefits unless you are a hacker/developer. I am not unlocked but I would not try this anyway, no offense. What benefits does this carry? According to your pictures, this removed s-off and also locked the bootloader. Unless this removes all of those checks, it is stupid because we have no way to unlock.

123421342 said:
I don't know how that relates to my comment. I was just letting people know there is no reason to flash a bootloader because of the HUGE risk of hard, hard brick and no benefits unless you are a hacker/developer. I am not unlocked but I would not try this anyway, no offense. What benefits does this carry? According to your pictures, this removed s-off and also locked the bootloader. Unless this removes all of those checks, it is stupid because we have no way to unlock.
Click to expand...
Click to collapse
Misquote, sorry. Meant to quote OP's post.

123421342 said:
I don't know how that relates to my comment. I was just letting people know there is no reason to flash a bootloader because of the HUGE risk of hard, hard brick and no benefits unless you are a hacker/developer. I am not unlocked but I would not try this anyway, no offense. What benefits does this carry? According to your pictures, this removed s-off and also locked the bootloader. Unless this removes all of those checks, it is stupid because we have no way to unlock.
Click to expand...
Click to collapse
If you look closely there are a few extra spaces in those lines. Basically it makes it look like its s-on and locked. I've found that it's easier to walk into a verizon store and get help when they dont think you've unlocked. It also removed the nag string on the boot splash when you flash a custom rom. I've been using something like this on my rezound for over a year and from the ppl in that forum there was a want for it. Yes hboot is a very dangerous part if you don't know what your flashing. If it makes anyone feel better they can do a binary compare of this hboot with an original hboot and see that only the strings were manipulated.
Basically it was something I wanted so I did it for this phone. If others want to use it that is fine too, I just don't want to release something that could potentially brick based off of my mistakes, but it's been working fine for me for over a day.

jmstumme said:
If you look closely there are a few extra spaces in those lines. Basically it makes it look like its s-on and locked. I've found that it's easier to walk into a verizon store and get help when they dont think you've unlocked. It also removed the nag string on the boot splash when you flash a custom rom. I've been using something like this on my rezound for over a year and from the ppl in that forum there was a want for it. Yes hboot is a very dangerous part if you don't know what your flashing. If it makes anyone feel better they can do a binary compare of this hboot with an original hboot and see that only the strings were manipulated.
Basically it was something I wanted so I did it for this phone. If others want to use it that is fine too, I just don't want to release something that could potentially brick based off of my mistakes, but it's been working fine for me for over a day.
Click to expand...
Click to collapse
Sounds good, thanks for this. I won't flash it now because I don't need to risk it but if I ever need to bring the phone to Verizon then I'll keep this in mind.

jmstumme said:
If you look closely there are a few extra spaces in those lines. Basically it makes it look like its s-on and locked. I've found that it's easier to walk into a verizon store and get help when they dont think you've unlocked. It also removed the nag string on the boot splash when you flash a custom rom. I've been using something like this on my rezound for over a year and from the ppl in that forum there was a want for it. Yes hboot is a very dangerous part if you don't know what your flashing. If it makes anyone feel better they can do a binary compare of this hboot with an original hboot and see that only the strings were manipulated.
Basically it was something I wanted so I did it for this phone. If others want to use it that is fine too, I just don't want to release something that could potentially brick based off of my mistakes, but it's been working fine for me for over a day.
Click to expand...
Click to collapse
Oh okay this is a good idea but risky. May be good for people sending it in but it can't fool command line right?
Sent from my HTC6500LVW using xda app-developers app

123421342 said:
Oh okay this is a good idea but risky. May be good for people sending it in but it can't fool command line right?
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
From what I seen in the rest of the hboot no, it looks like it's obvious that its custom, s-off, and unlocked. This should also not be used for insurance fraud in any form or fashion. This is more or less to get people to not freak out and for people that like the stock look. As far as risk goes, having an s-off phone is dangerous since you can access the raw devices.

Looks nice!
jmstumme said:
From what I seen in the rest of the hboot no, it looks like it's obvious that its custom, s-off, and unlocked. This should also not be used for insurance fraud in any form or fashion. This is more or less to get people to not freak out and for people that like the stock look. As far as risk goes, having an s-off phone is dangerous since you can access the raw devices.
Click to expand...
Click to collapse
---------- Post added at 03:06 PM ---------- Previous post was at 02:52 PM ----------
Is there an RUU for our phones that, when flashed, would bring us right back to factory untouched condition?
jmstumme said:
This should also not be used for insurance fraud in any form or fashion.
Click to expand...
Click to collapse

godhamba said:
Looks nice!
---------- Post added at 03:06 PM ---------- Previous post was at 02:52 PM ----------
Is there an RUU for our phones that, when flashed, would bring us right back to factory untouched condition?
Click to expand...
Click to collapse
Looks like this one should work
http://forum.xda-developers.com/showthread.php?t=2437436
Otherwise I still have the original hboot from my phone

Just got an M9 today and need some tips...

Hello everyone, I I just got an M9 at my local Telus store and I would like to be able to do everything with it like I am able to do with my M7, so I know I will need to use sunshine to get S-OFF and I would also like to be able to change everything from the rom to the kernel to the OS, everything, so I was just wondering if someone could let me know the best order to go about doing things, meaning should I do sunshine first then worry about flashing a recovery and all that, or should I do the recovery first so that I can backup the phones current state? The phone currently says this in the hboot screen:
*** LOCKED ***
LK-1.0.0.0000
OS-1.32.661.6
and this is what it says on the phones Setting-About-Software screen:
Android version
5.0.2
HTC Sense version
7.0
Like I mentioned before, it would probably be best if I can make a backup of the phones current state just in case there are any issues, so to do that I know I need a recovery, but do I need to do the HTC Dev unlocker before I can do so? or do I have to flash a recovery first before everything else?
Now, before anyone gets upset with me for asking these questions because they have most likely been asked 1000 times before, I am not asking to be spoon feed all the details step by step, I am just asking to be pointed in the right direction and asking for you guy's opinions on the best way to go about doing things so that I do them right the first time... So if anyone could please take a minute to help me out and get me pointed in the right direction then it would be greatly appreciated... thank you very much...

apaquette420 said:
So if anyone could please take a minute to help me out and get me pointed in the right direction then it would be greatly appreciated... thank you very much...
Click to expand...
Click to collapse
First thing you should do is unlock your bootloader. After that you can install twrp and flash supersu (most can be found here) Once you are rooted run sunshine. After that the sky is the limit. You will be free to flash anything and everything. I know because I've done it. If you want to convert to a developers edition there is a post here. Personally I do not use my stock recovery or system image backups to download ota's. I prefer to run an RUU and do fresh installs. Reason why is because I am constantly changing firmware and roms. A lot of roms are based on the WWE firmware.
let me know if you have any more questions

bigp951 said:
First thing you should do is unlock your bootloader. After that you can install twrp and flash supersu (most can be found here) Once you are rooted run sunshine. After that the sky is the limit. You will be free to flash anything and everything. I know because I've done it. If you want to convert to a developers edition there is a post here. Personally I do not use my stock recovery or system image backups to download ota's. I prefer to run an RUU and do fresh installs. Reason why is because I am constantly changing firmware and roms. A lot of roms are based on the WWE firmware.
let me know if you have any more questions
Click to expand...
Click to collapse
Thank you very much for the tips.. Do I use the HTC Dev website to unlock the bootloader? I seen a link in the dev thread that said Unlock bootloader without HTCDev(root required), but I bet that the HTCDev way is probably the best best. which did you use? I'm not at home right now so I will begin when I get home later on tonight and if I need anything else I will post back, plus I post back to say how everything goes.. Thanks again for help, it is very much appreciated...

apaquette420 said:
Thank you very much for the tips.. Do I use the HTC Dev website to unlock the bootloader? I seen a link in the dev thread that said Unlock bootloader without HTCDev(root required), but I bet that the HTCDev way is probably the best best. which did you use? I'm not at home right now so I will begin when I get home later on tonight and if I need anything else I will post back, plus I post back to say how everything goes.. Thanks again for help, it is very much appreciated...
Click to expand...
Click to collapse
I've used htcdev for all 2 out o 3 of my m9's. third one is a developer edition so it wasn't needed.
just note download mode is fastboot mode on the m9. htcdev says to boot to fastboot mode and if you do not know than you can waste hours trying to figure it out.

bigp951 said:
I've used htcdev for all 2 out o 3 of my m9's. third one is a developer edition so it wasn't needed.
just note download mode is fastboot mode on the m9. htcdev says to boot to fastboot mode and if you do not know than you can waste hours trying to figure it out.
Click to expand...
Click to collapse
lol I so would have gotten caught up on that lol thanks again man!!! will post back later on...

cool..let me know if you get stuck anywhere

Ok so I got the bootloader unlocked and TWRP installed, right now I am taking a backup of the phones current state just in case. Now I just need to flash the SuperSU beta from the link you provided and then run sunshine, after that I would like to flash the latest OS for my phone, but I am not sure which version to use, I think this one is correct http://forum.xda-developers.com/one-m9/development/firmware-red-t3097678 but I am not 100% sure, do you know if this is the correct latest version for my phone?
Also should I supercid my phone before updating the firmware by entering "fastboot oem writecid 11111111" while in download mode? because my cid is TELUS001 and I do not see that cid listed in the androidinfo.txt file that is in the firmware zip...
Thanks again for all your help...
**UPDATE** I now have S-OFF, I can't believe how smooth the whole process is now with sunshine compared to almost all of my other HTC phones, hats off to those guys for sure... Thank you very much for getting me this far!!! I appreciate it very much...

apaquette420 said:
Ok so I got the bootloader unlocked and TWRP installed, right now I am taking a backup of the phones current state just in case. Now I just need to flash the SuperSU beta from the link you provided and then run sunshine, after that I would like to flash the latest OS for my phone, but I am not sure which version to use, I think this one is correct http://forum.xda-developers.com/one-m9/development/firmware-red-t3097678 but I am not 100% sure, do you know if this is the correct latest version for my phone?
Also should I supercid my phone before updating the firmware by entering "fastboot oem writecid 11111111" while in download mode? because my cid is TELUS001 and I do not see that cid listed in the androidinfo.txt file that is in the firmware zip...
Thanks again for all your help...
**UPDATE** I now have S-OFF, I can't believe how smooth the whole process is now with sunshine compared to almost all of my other HTC phones, hats off to those guys for sure... Thank you very much for getting me this far!!! I appreciate it very much...
Click to expand...
Click to collapse
I was actually just going to tell you to type
Code:
fastboot getvar all
while in download mode and to copy and paste that into a file a text file somewhere so you always have it. then you can supercid. I actually have never seen any firmware for your carrier. what is your mid? this is where I get all of my firmware from. I learned how to remove the red text using hex editor and I also throw in a custom splash screen before I flash.
Here is a link for your stock firmware. not sure what the most up to date is but most custom roms are using the WWE firmware anyways.
p.s. either quote me or tag me if you need a faster response. I'm not getting notifications otherwise.

bigp951 said:
I was actually just going to tell you to type
Code:
fastboot getvar all
while in download mode and to copy and paste that into a file a text file somewhere so you always have it. then you can supercid. I actually have never seen any firmware for your carrier. what is your mid? this is where I get all of my firmware from. I learned how to remove the red text using hex editor and I also throw in a custom splash screen before I flash.
Click to expand...
Click to collapse
My mid is 0PJA11000 but the one that is listed in the androidinfo.txt file of the firmware that I linked earlier is 0PJA10000, does this mean I cant use it? in all I plan to flash ViperOneM9 3.5.0 for the rom and it says it requires 2.10 but my phone is currently at 1.32

apaquette420 said:
My mid is 0PJA11000 but the one that is listed in the androidinfo.txt file of the firmware that I linked earlier is 0PJA10000, does this mean I cant use it?
Click to expand...
Click to collapse
I honestly don't know if the hardware is any different but it looks like your mid is the same as the dev ed. check this one out. @clsA is very knowledgeable on the m9. I learned a lot of what I know from his posts.
Personally I have gotten so relaxed that I just change my mid and cid to whatever it is I want to flash and just go for it. But I also understand that I'm risking a brick by doing so..lol

bigp951 said:
I honestly don't know if the hardware is any different but it looks like your mid is the same as the dev ed. check this one out. @clsA is very knowledgeable on the m9. I learned a lot of what I know from his posts.
Personally I have gotten so relaxed that I just change my mid and cid to whatever it is I want to flash and just go for it. But I also understand that I'm risking a brick by doing so..lol
Click to expand...
Click to collapse
took a look at the thread and it looks like all I need to do to flash 2.10 which is the international version is type fastboot oem writemid 0PJA10000 while in downloader mode because like you said and which I also confirmed in the other thread that my phone is the same as the dev ed and I should be able to switch back and forth with the same command

apaquette420 said:
took a look at the thread and it looks like all I need to do to flash 2.10 which is the international version is type fastboot oem writemid 0PJA10000 while in downloader mode because like you said and which I also confirmed in the other thread that my phone is the same as the dev ed and I should be able to switch back and forth with the same command
Click to expand...
Click to collapse
If going to dev ed I have had better luck running an RUU and accepting ota's as far as the radio goes. my reception went from 2 bars to full bars doing it that way verses just flashing the newest firmware. But it is a very long and tedious process and since you just got your m9 I'm sure you want to use it already..
What rom are you thinking about flashing?

bigp951 said:
If going to dev ed I have had better luck running an RUU and accepting ota's as far as the radio goes. my reception went from 2 bars to full bars doing it that way verses just flashing the newest firmware. But it is a very long and tedious process and since you just got your m9 I'm sure you want to use it already..
What rom are you thinking about flashing?
Click to expand...
Click to collapse
I am hoping to flash ViperOneM9 3.5.0, it was the only rom I ran on my M7 and I loved it, so I'm really hoping to have it on this phone too... I just asked in the roms thread to see if anyone else there is on my same network to see how they got it working... and to be honest I don't mind waiting in order to get things done the right way the first time, know what I mean...

apaquette420 said:
I am hoping to flash ViperOneM9 3.5.0, it was the only rom I ran on my M7 and I loved it, so I'm really hoping to have it on this phone too... I just asked in the roms thread to see if anyone else there is on my same network to see how they got it working... and to be honest I don't mind waiting in order to get things done the right way the first time, know what I mean...
Click to expand...
Click to collapse
Viper is one of my favorites. Was using it for months. They are good about replying too... A little too good because you get spoiled. Then when you post on other roms and nobody ever replies you realize how good those guys are..haha
check out the second line on this thread to reclaim 3 gb of data after using sunshine. I've been s-off for months and just saw this today.

bigp951 said:
Viper is one of my favorites. Was using it for months. They are good about replying too... A little too good because you get spoiled. Then when you post on other roms and nobody ever replies you realize how good those guys are..haha
check out the second line on this thread to reclaim 3 gb of data after using sunshine. I've been s-off for months and just saw this today.
Click to expand...
Click to collapse
do you know where I can find the latest international RUU? what rom are you running now?

@bigp951
Ok so I got the firmware updated to the latest international version 2.10 and was able to flash the ViperOne Rom and I love it just like I did for my M7... Everything is working great, except I have the problem that you mentioned would happen, I only show 1 bar for my signal strength, could you please let me know exactly what you had to do to fix it? Also, I would just like to say thank you once more, you helped me out a great deal and you made my upgrade to the M9 an absolute cake walk, so thank you very much for everything and for explaining the proper steps to take, I appreciate it very much...