Related
I figured I would ask the question before anyone else does if it hasn't been asked before.
I am going to get the phone on release day, I am Currently an Android user and I've decided to get a second phone to play around with and was trying to find out if maybe the processes of flashing roms on the T-mo USA HD2 are going to be the same as the Euro HD2 and if maybe if anyone (I know its not officially out yet) has already tried doing anything of the sort to their US HD2.
I am aware that the phone isn't out, but I'm maybe trying to put this post here for maybe future reference or maybe to use as a guide as to how to apply roms or themes on the US T-Mo HD2.
Thank you in advance and I'm sorry if this maybe considered a noob question. But unfortunately I'm a noob to the hacking of WinMo world but like i said previously I'm an Android guy and that is how i originally got introduced to XDA
has been asked and at this point we cannot flash roms to the us hd2 the simplest way because...
it has a new spl so we cannot use the current hard spl.
but! there is sspl which allows you to flash roms but not radios.
reccomend just wait til the new spl comes out since your a noob afterall
Wait, so SSPL works fine?
look through my posts theres a couple about this. in one I was told sspl works
lbhocky19 said:
has been asked and at this point we cannot flash roms to the us hd2 the simplest way because...
it has a new spl so we cannot use the current hard spl.
but! there is sspl which allows you to flash roms but not radios.
reccomend just wait til the new spl comes out since your a noob afterall
Click to expand...
Click to collapse
Thanks for the help, I feel like I'm starting all over again, like its a new learning process all over again lol oh and thanks for rubbing it in that I'm a noob I'm gonna go kill myself now, you see what you did? lol j/k
Yeah i figured I'm jumping the gun a little since the phone isn't really out yet, I guess I'm just excited to hack it, thanks for the info.
yeah im in the same boat, i picked it up already and its been weird using a stock rom but it actually works pretty well i just want 6.5.x back
I flashed laurentius29 rom to my tmous leo.
Result - expensive paperweight.
Already exchanged it in tmob store telling them it just died. I've had it for just two days.
Seriously! Don't attempt to flash non-tmous roms to your tmous phones.
I thought they are fos saying you can brick your phone doing that.
I thought I knew what I was doing with my quite long winmo history. (Samsung i730, Kaiser, Rafael and Leo just recently)
do you have hspl installed?
Doesn't matter as non-TMOUS ROMs won't work on a TMOUS HD2
gees.....better buy openline HTC HD2...
Just to make sure:
Flashing a TMOUS ROM to a NON-TMOUS device won't brick your device?
With Hspl you should be able to recover... ROMS dont touch the bootloader. And without Hspl you wouldnt be able to flash..
It is not the fault of his ROM but your choice of a ROM not compatible. I think his base is 1.72 or 1.66 and with drivers from this same build. I would ask him to be sure.
Make sure you flash a ROM with 2.10 base and you should be ok.
Sorry to hear about your device but at least you were lucky enough to be in the US and they changed it out quickly for you.
Hi Stank0,
I'm very sorry to read this and will make an anouncement immidiatly that the rom isn't compatible with the T-Mob US model.
Sorry to ask you as you got damage enough but can you tell me the procedure you followed flashing the rom?
Thank you.
Stank0 said:
I flashed laurentius29 rom to my tmous leo.
Result - expensive paperweight.
Already exchanged it in tmob store telling them it just died. I've had it for just two days.
Seriously! Don't attempt to flash non-tmous roms to your tmous phones.
I thought they are fos saying you can brick your phone doing that.
I thought I knew what I was doing with my quite long winmo history. (Samsung i730, Kaiser, Rafael and Leo just recently)
Click to expand...
Click to collapse
Indeed that's true far as I know but I realy like to know how Stank0 bricked it to avoid this in future.
snipey said:
With Hspl you should be able to recover... ROMS dont touch the bootloader. And without Hspl you wouldnt be able to flash..
Click to expand...
Click to collapse
After I flashed HSPL2, I tried a few ROMs. 2x NRG's and Kumar's. They all worked OK but I wanted to try yours bcz I used to have it for quite a while on my Rafael. (before I switched 2 NRG for some reason I don't remember).
I always flash over old flash without going through all the "necessary" steps and it almost always worked good. I went through flashing stock first only when something went wrong. (very rarely)
So I did the same thing with your ROM flashing it over NRG's. (Via USB)
Obviously, my poor tmous LEO couldn't handle all that "Ultimate Power" and after the flash was succesfully finished, it never started up.
No light, no sound.
First I thought I'll just get into a bootloader and reflash.
But after I found out that I can't get even bootloader up, I realized I'm pretty much screwed.
The phone didn't react to ANYTHING.
When I plugged it up to my laptop, it tried to install new driver for it but of course unsuccessfully.
I've had quite a hard time to find a store with HD2 in stock. Apparently they sell better than fresh rolls.
Oh by the way Laurentius26, I don't blame you for it at all. It was my fault not listening what wise people say. From now on, if it doesn't say "TMOUS COMPATIBILE", I'm not touching it.
And that what I recommend others to do too.
Unless you want to live dangerously and have a nice but quite expensive paperweight.
Laurentius26 said:
Hi Stank0,
I'm very sorry to read this and will make an anouncement immidiatly that the rom isn't compatible with the T-Mob US model.
Sorry to ask you as you got damage enough but can you tell me the procedure you followed flashing the rom?
Thank you.
Indeed that's true far as I know but I realy like to know how Stank0 bricked it to avoid this in future.
Click to expand...
Click to collapse
Sorry to hear about your device but at least you were lucky enough to be in the US and they changed it out quickly for you
Click to expand...
Click to collapse
Sorry too
but if i`m not wrong the brand new TMOUS Leo costs only 199.99 $ in th US vs 600 in Europ
Yes TMOUS Leo costs 199.99 $ in th US with 2 years contract!!!
HTC HD2 in England is for free with contract!!!
So....
yeah it does. With 2 yrs contract. I paid $450 + tax however. No contract.
gf7800 said:
Sorry too
but if i`m not wrong the brand new TMOUS Leo costs only 199.99 $ in th US vs 600 in Europ
Click to expand...
Click to collapse
So let me get this straight, you flash hspl on your device to flash custom ROMs. If you brick a phone, is it completely useless forever in eternity? (besides being a paperweight) Is there anyway to recover it at all? At all, at all?
Hi Stank0,
Thanks for letting me know.
Flashing a rom shouldn't brick your device like that, even if the flash went all ok or not it should always be possible
to reflash (recover) as mentioned earlier that flashing a rom doesn't touch the bootloader.
Dit you try to take out the battery for half an hour and then try to get in bootloader?
Anyway I'm very sorry your device is bricked .
To make sure I've updated my rom threads with a warning to avoid this in future.
Stank0 said:
After I flashed HSPL2, I tried a few ROMs. 2x NRG's and Kumar's. They all worked OK but I wanted to try yours bcz I used to have it for quite a while on my Rafael. (before I switched 2 NRG for some reason I don't remember).
I always flash over old flash without going through all the "necessary" steps and it almost always worked good. I went through flashing stock first only when something went wrong. (very rarely)
So I did the same thing with your ROM flashing it over NRG's. (Via USB)
Obviously, my poor tmous LEO couldn't handle all that "Ultimate Power" and after the flash was succesfully finished, it never started up.
No light, no sound.
First I thought I'll just get into a bootloader and reflash.
But after I found out that I can't get even bootloader up, I realized I'm pretty much screwed.
The phone didn't react to ANYTHING.
When I plugged it up to my laptop, it tried to install new driver for it but of course unsuccessfully.
I've had quite a hard time to find a store with HD2 in stock. Apparently they sell better than fresh rolls.
Oh by the way Laurentius26, I don't blame you for it at all. It was my fault not listening what wise people say. From now on, if it doesn't say "TMOUS COMPATIBILE", I'm not touching it.
And that what I recommend others to do too.
Unless you want to live dangerously and have a nice but quite expensive paperweight.
Click to expand...
Click to collapse
this is bad, im sorry for your loss
though flashing a rom doesnt screw up the bootloader
Problem is T-Mob US model has different NAND.
XDA opened two section as well as the hardware is different.
* HD2 ROM Development
* T-Mob USA HD2 ROM Development
I have no T-Mob USA model and I'm not 100% sure if the device is bricked because
of flashing the rom so it's better to take precautionary measures to avoid this in future.
bbezja1 said:
this is bad, im sorry for your loss
though flashing a rom doesnt screw up the bootloader
Click to expand...
Click to collapse
It sounds more like coincidence.
I can't imagine Leo includes bootleader in his rom, so it shouldn't have effected the spl at all.
Thanks Fards,
Indeed there's no SPL (bootloader) in the rom so if a user flashed HSPL first and then the rom it doesn't touch the bootloader and it should be always possible to get in bootmodus after a bad flash and reflash the rom.
It worried and made me doubt for 2 days but this makes no sense the device is bricked because of flashing the rom it must be coinsidence.
There are enough stickies how to flash a rom and I've included rom flash instructions in my rom thread so I'm going to remove the warning.
@Stank0, I feel sorry your device is bricked but I hope you understand my decission.
Grtz Leo
fards said:
It sounds more like coincidence.
I can't imagine Leo includes bootleader in his rom, so it shouldn't have effected the spl at all.
Click to expand...
Click to collapse
lemonspeakers said:
So let me get this straight, you flash hspl on your device to flash custom ROMs. If you brick a phone, is it completely useless forever in eternity? (besides being a paperweight) Is there anyway to recover it at all? At all, at all?
Click to expand...
Click to collapse
re-bump. can anyone answer this?
I agree with everyone else. It wasn't the flash-it was the flasher. He didn't follow the basics. Wrong rom, flashed repeatedly while bypassing vital steps. It wasn't bricked-he got jumpy. He shouldn't flash if he can't follow simple tutorials and stickies.
Is there anyone working on rooting this ruu for people who may have installed it before the roms were created or for those like myself that tried the 1.56 ruu and got errors that would not complete? Just asking.
rpierce said:
Is there anyone working on rooting this ruu for people who may have installed it before the roms were created or for those like myself that tried the 1.56 ruu and got errors that would not complete? Just asking.
Click to expand...
Click to collapse
I don't understand why you would install it when it was made clear you would lose root, and that there is no guarantee on getting root back.
wll if I had to guess the devs wont even try rooting this release untill they know for sure that this is a final. This is because they already know that they are removing the root exploit and a new one will need to be found .This will not be a quick process. But rest assured that they will be working on rooting 2.1, I am sure HTC will not beat these guys. LOL
Another point on what you said...if they find an exploit now before the 2.1 is released for the phone, then HTC can delay the release further and quickly plug up the exploit. HTC is not likely to plug up any holes after the release.
Smart move to wait.
nfinitefx45 said:
wll if I had to guess the devs wont even try rooting this release untill they know for sure that this is a final. This is because they already know that they are removing the root exploit and a new one will need to be found .This will not be a quick process. But rest assured that they will be working on rooting 2.1, I am sure HTC will not beat these guys. LOL
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=rY0WxgSXdEE#t=0m49s
The reason i did it was because the 1.56 ruu stuck on me and wouldnt complete. It would get to 85% and say files were missing and i was stuck on the HTC screen. It had already wiped my other rom. I couldnt do anything. this is pretty new to me.
If you've debranded, you can't upgrade...? Is that the issue?
I've read through the big thread and it doesn't really explain much to me
From what can be gathered so far:
The non-branded HTC Legend FroYo up date checks the phones CID to a list that HTC know are debranded. If the CID is not on that list of the update script, it fails the update. Vodafone and other carrier phones that have been de-branded still have the original CID. In my case, mines is something like VODAF001. This is not on the installer scripts list. Hence the update fails even if we have a debranded 2.1 ROM.
We cannot change, yet, the orginal HTC Update Script as the *.zip file has a signature that cannot be re-signed without knowing HTC's private key. Think of it as encryption - the files are visable, however, the phone checks the signature against what it should be for the contained files. If the files are changed (like changing the supported CID's) then the signature does not match and the phone fails to continue with the update.
There's no way way to change your phones CID or re-sign the FroYo installation rom to accept the diffierent CID's.
So far, we're stuck.
YoungPretender said:
There's no way way to change your phones CID or re-sign the FroYo installation rom to accept the diffierent CID's.
So far, we're stuck.
Click to expand...
Click to collapse
Very helpful information there m8 and granted there is no free way to change your phones CID but it is very possible do a quick search for riff box you can change the legend CID with that. Not much use to most people due to it costing £100. Maybe some devs would work on a software CID change, not even sure if it is possible with just software but you never know.
Or what about changin the file in the update to accept your CID then using a goldcard to flash it? Does a goldcard not let you flash unsigned zips?
So corrrect me if I am wrong, I have my Bell Legend Rooted with MCR I also have Rom Manager installed, so, If I edited the froyo update to include my cid, then flashed the rom with Rom Manager, that, as I understand things, should work, since we can flash unsigned roms with Clockwork. Or am I way off base?
bwilliams1 said:
So corrrect me if I am wrong, I have my Bell Legend Rooted with MCR I also have Rom Manager installed, so, If I edited the froyo update to include my cid, then flashed the rom with Rom Manager, that, as I understand things, should work, since we can flash unsigned roms with Clockwork. Or am I way off base?
Click to expand...
Click to collapse
Im not sure I dont even have a phone atm waiting on my legend to turn up but it sounds about right to me. That doesnt mean it will actually work tho best off waiting for someone with more experience with these thhings to post.
I bought a Vodafone Spain one, and have debranded it. I use a Cyanogen mod froyo. So i can't update to the official one ? If i put the 2.1 From Vodafone Spain, can't i update to the Vodafone Spain Official 2.2 ?
xnotte said:
I bought a Vodafone Spain one, and have debranded it. I use a Cyanogen mod froyo. So i can't update to the official one ? If i put the 2.1 From Vodafone Spain, can't i update to the Vodafone Spain Official 2.2 ?
Click to expand...
Click to collapse
From what I understand if you put the vodafone rom on you can update to vodafone 2.2 but people are having problems getting the wwe 2.2 on de branded handsets
I've got a single idea that I'm trying the now to get working.
Not going to post any details until I know wether it'll fail or work. Fingers and toes crossed through :O
YoungPretender said:
I've got a single idea that I'm trying the now to get working.
Not going to post any details until I know wether it'll fail or work. Fingers and toes crossed through :O
Click to expand...
Click to collapse
Good luck let us know how you get on.
FeaRThiS said:
Good luck let us know how you get on.
Click to expand...
Click to collapse
Not very well
I'm pretty new to all this anyway, but I thought my techie background would help playing catchup.
Basically, I found my CID of my phone. VODAF001.
Then I went through the official unbranded FroYo rom and replaced supported CID's in the installation script and the android.info text file in the frimware.zip folder with my CID. Resigned the package.
I then rooted my phone (took a few hours - never did it before, but it was a success) then attempted to install the modified and resigned package.
It verifies ok, but I get a Status 7 error. I think this was the same error I had when trying to install the FroYo update from the very start.
Not too happy, but I had to give it a go. Anyone have any other ideas at modifying the original rom file? At least I got the thing to verify after modding it onto a rooted rom. Maybe, just maybe we're 30% there.
YoungPretender said:
Not very well
I'm pretty new to all this anyway, but I thought my techie background would help playing catchup.
Basically, I found my CID of my phone. VODAF001.
Then I went through the official unbranded FroYo rom and replaced supported CID's in the installation script and the android.info text file in the frimware.zip folder with my CID. Resigned the package.
I then rooted my phone (took a few hours - never did it before, but it was a success) then attempted to install the modified and resigned package.
It verifies ok, but I get a Status 7 error. I think this was the same error I had when trying to install the FroYo update from the very start.
Not too happy, but I had to give it a go. Anyone have any other ideas at modifying the original rom file? At least I got the thing to verify after modding it onto a rooted rom. Maybe, just maybe we're 30% there.
Click to expand...
Click to collapse
At least you ruled out one possibility I think the best way would be to change the phones CID that way you would never have to worry about it again and all updates would work as if it was a sim free phone. I remeber a few years back there was a app for the original iphone that would allow you to change the imei (i know this is illegal in most places) the point is the CID needs the same level access. If we have enough access a dev could probably make an app or script to run to change the phones CID to one of a sim free phone. I have posted the question in the dev section no replys yet.
FeaRThiS said:
At least you ruled out one possibility I think the best way would be to change the phones CID that way you would never have to worry about it again and all updates would work as if it was a sim free phone. I remeber a few years back there was a app for the original iphone that would allow you to change the imei (i know this is illegal in most places) the point is the CID needs the same level access. If we have enough access a dev could probably make an app or script to run to change the phones CID to one of a sim free phone. I have posted the question in the dev section no replys yet.
Click to expand...
Click to collapse
Agreed. It would be the best solution.
I'm still looking at this script file. I reckon that re-writing the entire thing could also be a possibility - and probably quicker to a solution to the CID problem in the short term.
Trying again taking all the checks out at the begining of the script... see what happens, lol.
Well, different error. Status 4 - whatever that means...
It could be anything. My ROM version currently installed could be too old for the update as well (V.1.xxxx).
Anyway, it's twenty to two here, time for my bed I think...
YoungPretender said:
Trying again taking all the checks out at the begining of the script... see what happens, lol.
Click to expand...
Click to collapse
good luck im sure there is a way as with clockwork mod you can flash unsigned roms so just a case of trying as many ways as possible. As for the CID change im guessing that would be a lot of work and would take a long time but would prevent future problems with new updates ect ect.
Not sure why people are freaking out about this. So the Voda Phone one came out early.. I'm sure it's just a matter of days or weeks before the WWE is released. Just chill
skinnypupp said:
Not sure why people are freaking out about this. So the Voda Phone one came out early.. I'm sure it's just a matter of days or weeks before the WWE is released. Just chill
Click to expand...
Click to collapse
I think you are missing the point a legend that was locked to vodafone can not be updated to the wwe. the voda legend has a different cid which is stopping people who debranded there phones from getting the wwe 2.2 update.
skinnypupp said:
Not sure why people are freaking out about this. So the Voda Phone one came out early.. I'm sure it's just a matter of days or weeks before the WWE is released. Just chill
Click to expand...
Click to collapse
So you mean the official FroYo update for non-branded phones? it is! We know the Vodafone one is out.
The problem lie in people who have de-branded. They can't update to the non-branded FroYo that was released today.
(And Yes, I'm still up because I'm a persistant little bugger, lol)
YoungPretender said:
So you mean the official FroYo update for non-branded phones? it is! We know the Vodafone one is out.
The problem lie in people who have de-branded. They can't update to the non-branded FroYo that was released today.
(And Yes, I'm still up because I'm a persistant little bugger, lol)
Click to expand...
Click to collapse
haha still tryin post up everythin you try just so people dont have to try things we know dont work.
FeaRThiS said:
From what I understand if you put the vodafone rom on you can update to vodafone 2.2 but people are having problems getting the wwe 2.2 on de branded handsets
Click to expand...
Click to collapse
but if i put the vodafone rom back again, it's no longer debranded! right ?
So i can update to the Vodafone ROM 2.2 via OTA right ?
Title says it... pretty much just want to go Official without losing my apps and app data if possible. I'm using Ansers custom TANGO ROM atm. Just wondering if something bad could happen if I just plugged into ZUNE and updated.
Thanks in advanced.
Using Verizon TROPHY/Spark_W
Found the answer, you CAN NOT update this way, even if you remove hspl. So had to downgrade after removing hspl.
Sent from my mwp6985 using Board Express
Well, there are ways to update with HSPL installed using Zune.. but you need a rom that is closer to the OEM stock rom. If you had a 7720 rom, like DFT, you could attempt to update. The drivers and sys would update, but Internet Sharing would disappear, because the WIRELESS driver won't have the policies for Internet Sharing anymore... You might also loose parts of fullunlock of those files are overwrote by other files.
Having HSPL installed has nothing to do with the update failing. If an SPL update is pushed in a driver (and with the Verizon HTC drivers, it ALWAYS is), HSPL will prevent the OSPL from being flashed {if it did flash, you wouldn't like it.. trust me.. I made mine do it once using bad methods... not fun). It's as simple as the system build mismatch from my experience.
I really need to get my rom out the door soonish.
TheXev said:
I really need to get my rom out the door soonish.
Click to expand...
Click to collapse
I'm looking forward to the Spark_W version