Related
Hi
similar to an other thread here if tried to change my SPL
and never recovered.
I can still get the blue led going using TrackBall + EndCall buttons.
The orange led lights up when I connect the usb cable.
But I cannot see it from the pc in any way (adb/fastboot).
there is some life in it but not a lot, have not seen the screen light
up at all.
Would it be possible to get a new bootloader/spl on it? Perhaps using
some kind of automatic update mechanism that is build in using an
update.zip file on the sd card?
Any help is more than welcome.
abe
*bump*
hmm, post needs al least 10 chars... should be enough now...
Has everyone also drawn a blank on this?
abe
Try downloading the ruu from your phone's official reseller.
T-Mobile USA standard OS.
Assuming that you backed up using Nandroid or something to SAVE and STORE your originally packaged Android 1.5 (Cupcake) version from T-Mobile...you NEED to restore that properly using a recovery image. Amon_RA has a great one, so does Cyanogen, obviously by now I'm sure you're aware. But keep in mind, to get back to that state...you must be careful not to alter any necessary files on that standard OS.
Do some Google searching and try to track down a Cupcake 1.5 download from one of those sites that leaked it or something. That's your best bet. Right now you don't need to be worried about continuing on from where you are. You need to backtrack and begin anew.
Sorry to hear that. I was thinking of installing Haykuro Apps to SD ROM and it needs to change the SPL. But I think not worth taking a risk.
Can you tell a little bit more which ROM were you planning to install?
Which SPL did you update to?
Which ROM did you have at the time of SPL update?
Which thread or instructions did you follow if any?
Hi
@mrjunix
I have a google ion, and therefore cannot return it unfortunately to the
carrier, as there was none. I went to the Google IO conference but
I am back in Europe and there is not support here.
btw what do you mean by RRU??
@Reignzone
I do have a nandroid backup but I cannot get back into recovery mode,
or fastboot mode or anything... the pc does not recognize it either.
@technicolor
I installed the Cyanogen recovery image and was able to install
one of his rom's. It worked fine but then I wanted to install
a Hero rom and I wanted to update the SPL.
Used the cyanogen recovery to update the spl using an update.zip
file. the phone restarted the "android" update screen came on
briefly and it never came back on...
changing the recovery rom should not be an issue,
and normally I think you do not need to flash your spl at all any more.
you can do a lot with the fastboot mode and one of the recovery roms
mentioned by Reignzone
abe
Reignzone said:
Assuming that you backed up using Nandroid or something to SAVE and STORE your originally packaged Android 1.5 (Cupcake) version from T-Mobile...you NEED to restore that properly using a recovery image. Amon_RA has a great one, so does Cyanogen, obviously by now I'm sure you're aware. But keep in mind, to get back to that state...you must be careful not to alter any necessary files on that standard OS.
Do some Google searching and try to track down a Cupcake 1.5 download from one of those sites that leaked it or something. That's your best bet. Right now you don't need to be worried about continuing on from where you are. You need to backtrack and begin anew.
Click to expand...
Click to collapse
This is the same advise you gave me yesterday on my bricked MT3G, but if you can't enter recovery mode, a nandroid backup ain't gonna help much, is it?
Also, any cupcake downloads are not going to help either, if you can't fastboot or enter recovery.
I appreciate you trying to help, but if you pay attention to the OP (and my own post), you'll see that your advise isn't going to solve anything.
For starters:
My advice to have those of you who are in need to take an approach that allows you to backtrack you work. Perhaps you left out various details of your issue or process taken in order to end up where you're at.
Your bitterness isn't appreciated for my having misread the problem.
YOU are the one with the F***** device, not me.
Anyway, all that aside; you might try to read-up on various threads that could be of some help. Google search, HTC support, ADB, etc.
There's always something to be done.
Good luck.
abeman said:
Hi
@mrjunix
I have a google ion, and therefore cannot return it unfortunately to the
carrier, as there was none. I went to the Google IO conference but
I am back in Europe and there is not support here.
btw what do you mean by RRU??
Click to expand...
Click to collapse
forum puffering aside, RUU is ROM Upgrade Utility
Prepackaged programs that bypass the phone's software altogether to reflash the rom
My carrier is Rogers of Canada and I have their "HTC Magic" phone
Be warned that Rogers is intentionally altering their hboot to disable system changes, you may not be able to cook your os after using this rom update.
Their updates page
https://your.rogers.com/web_auth/techsupport.asp
has the update
http://downloads.rogers.com/wireless/products/htc/magic/RUU_Sapphire_Rogers_WWE_2.17.631.2_release_signed_NoDriver.exe
Hello.
This is my first post, so please be kind to me!
I've spent the past few weeks trying to get my head around what to do in order to flash my HD2 which is on the t_mobile network
The original rom 1.43 i think is driving me crazy and I now dont care if I change the rom and it invalidates the warenty!
In order to HSPL I need to SPL first, but will my device allow this?
I've read through so many threads that I am completely confused and dont know which way to turn, never mind which thread to re-read.
Can someone point me to the sspl, HSPL to upgrade to 1.66
Thanks
Glyn
oh its the 512 version
you are over confusing yourself.
download hspl 2
instal it - choose whichever hspl you like (may as well go for 2.08.hspl)
flash whatever rom you like from usb. (don't forget to flash a compatible radio either before or straight after.)
Thanks for your reply......
so downloan the HSPL from here?
'forum.xda-developers.com/showthread.php?t=609477'
and as I run the program I'll get the option of which version to install?
What should I look for to make sure that the radio is compatible with the rom?
Thanks again and sorry for my ignorance
Glyn
best thing you can do is to read a lot. No need to do enerything in one mad dash.
get HSPL2 from HERE - end of the first post (but read the post, dont just skip to download, )
run it as administrator (right click, run as administrator)
for best results use a usb port on the back of your PC (i.e one directly on teh motherboard, not an external usb slot) it will ask what version you want to install. just go for 2.08.hspl (not 2.08.0000) and let it do its thing. the authors say you should match the version to the rom (so 1.43.hspl for roms that are 1.43 or 1.48, 1.66.HSPL for 1.6 based roms, etc, but it isn't critical, most will run on any HSPL, so dont go changing every time you flash a new rom, no need. If it doesnt work then change it.)
As for radio tips, a radio with .51. in the number, (eg 2.09.51.03) will NOT work with any rom that has the 576meg ram, enabled.
If you flash a rom and all you get when you restart is a grey screen, chances are the radio doesnt match. Boot to bootloader and flash the radio.
But most of all, read stuff.
What about shipped rom's that are .exe files? Do they include radios with it? Also, is there a post you can point me to that has a list of compatible radios with different rom's?
that's where reading comes in. the whole process has so many variants that there is no simple "a b c" that covers everything.
yes the exe includes radio (and also spl if you use sd card to flash -stay away from sd card, use usb and if anything goes wrong you just boot to bootloader and re flash)
the chefs give you all the infoyou need in the first couple of posts. the sticky threads in the rom development section will tell you how to do everything, and any problem you encounter has beenwritten about already. so read,search and read.
I suggest you flash Stock WWE 1.66 ROM first so you can have a feel of how much improvement
has been done from 1.43
you can download it in HTC website.
Thanks for your help so far..
I would like to go for the 1.66 official ROM first, so I'll find that on here first and find the exe file so I dont have to mess about with compatible radio's.
Just before I HSPL it, I would like a copy of the original 1.43 T-Mobile ROM, so better get searching.
Thanks again
Glyn
the original 1.43 T-Mobile ROM is on HTCs website so get it from there as a backup
THANKYOU!!
Thankyou so much for your help and guidance.
Last night I decided to just do it - the phone was so poor I couldn't take it anymore.
3 hours from start of backing up, to installing HSPL2, to flashing with 1.66, anf then restoring data
I cant believe the transformation - I am so pleased I didnt throw it at a wall!!!
So a massive thanks to the members of this community
im in the same boat... got a stock uk hd2 on tmobile and wasn't to flash a new rom but the information is overwhelming and im scared I will flash a wrong rom and kill my phone :0)
Chivalryyyy said:
im in the same boat... got a stock uk hd2 on tmobile and wasn't to flash a new rom but the information is overwhelming and im scared I will flash a wrong rom and kill my phone :0)
Click to expand...
Click to collapse
theres nothing to it. the 'normal' hd2 which you do have, is about the safest phone to flash in the world today, with HSPL2. The 'radios killing phones' problem that started last week is specific to the t mobile US model only, , the one with 1 gig rom.
If you install HSPL on your phone, and then only flash over USB, the very worst that will happen (from a software point of view) is that the phone stops at a grey screen, and/or only boots into bootloader, so you boot into bootloader, you flash something else, and it's fixed.
The T Mo UK stock rom is available to download as backup, (as is o2 and voda for anyone looking) in the 'LEO official roms' thread in rom development, first post, first link, first folder (1.43)
At any time, you can flash that rom from sd card (look it up if you need to) and restore everything, spl, radio and rom, , to factory settings.
In all honesty, so long as you are careful, methodical, don't pull out USB cables halfway through, laptop battery dies, etc , then you are more likely to get bricked from some freak incident, like , umm, battery dieing, heh.
Fear not! be smart, be careful, try to understand what you are doing and why at each step, read up on what an spl is, and the job is , as they say, sorted.
RE: Please Help
rockthebus said:
Thankyou so much for your help and guidance.
Last night I decided to just do it - the phone was so poor I couldn't take it anymore.
3 hours from start of backing up, to installing HSPL2, to flashing with 1.66, anf then restoring data
I cant believe the transformation - I am so pleased I didnt throw it at a wall!!!
So a massive thanks to the members of this community
Click to expand...
Click to collapse
Hi Guys
Can you help me...
How do i back up the phone before adding HSPL?
is this neccesary and where do i get the stock rom copy from.
i got the phone this week and hate it in its present form... can't even watch youtube.
looking to update to avoid sending back
Regards
mkhonat
re:
samsamuel said:
theres nothing to it. the 'normal' hd2 which you do have, is about the safest phone to flash in the world today, with HSPL2. The 'radios killing phones' problem that started last week is specific to the t mobile US model only, , the one with 1 gig rom.
If you install HSPL on your phone, and then only flash over USB, the very worst that will happen (from a software point of view) is that the phone stops at a grey screen, and/or only boots into bootloader, so you boot into bootloader, you flash something else, and it's fixed.
The T Mo UK stock rom is available to download as backup, (as is o2 and voda for anyone looking) in the 'LEO official roms' thread in rom development, first post, first link, first folder (1.43)
At any time, you can flash that rom from sd card (look it up if you need to) and restore everything, spl, radio and rom, , to factory settings.
In all honesty, so long as you are careful, methodical, don't pull out USB cables halfway through, laptop battery dies, etc , then you are more likely to get bricked from some freak incident, like , umm, battery dieing, heh.
Fear not! be smart, be careful, try to understand what you are doing and why at each step, read up on what an spl is, and the job is , as they say, sorted.
Click to expand...
Click to collapse
Hi samsamuel,
Sorry to msg you like this.
i have purchased a T mobile HTC HD2 which came with the stock 1.43 ROM.
I want to put 1.66 on but don't know how.
I've read the forum and looked on youtube but confused.
Do you have an idiots guide?... i really am an idiot when it comes to stuff like this!
I have downloaded HSPL2 file.
I have downloaded the back up 1.43 Stock Rom
Do i need to download the 1.66 ROM now and how do i update?
please excuse my ignorance and i am happy to donate if you can help.
Kind regards
Mkhonat
RE:
Hi Samsamuel,
Thanks.. just one more thing.
Saw on youtube that i have to format my SC card
youtube.com/watch?v=nrmlqrfCvas[/url]
is this so and is this referring to the sd card in the HTC or my own sd card used to download the 1.66 onto?
regards
mkhonat
PS. why won't this forum allow me to send you a PM?.. i can't send any msg's at all.
Hello there guys.
I have a few questions which I think have never been asked (at least not as I'm about to ask) before. I reckon they may seem silly and even idiotic at first, but I'm almost sure they're kinda relevant in a way or another.
First: What are the possible methods to really brick your phone?
Explanation: should I take real care with radio/SPL and SPL/bootloader versions? If I flash an incompatible ROM/SPL and/or bootloader, will I be able to boot into fastboot and debrick it, or it's bricked for good?
If I flash an incompatible ROM/Radio will it brick? Also, what kind of impact am I supposed to expect from radio versions? I was using 3.xx and all comms were terrible, now I went back to 6.35 and everything is great, only wifi is kinda weak.
Second: What kind of precautions should I take for testing kernels and mixing them with radio versions?
Explanation: I'm really looking for a Froyo with good battery life (good is like three days with not much data usage - My HTC Touch HD (T8282) was able to do that) and I'm planning to test a few kernels to see which is better in terms of stability, speed and battery life.
Third: How do I extract certain things from a given ROM and port it to another? What kind of importance the kernel has on it?
Explanation: I'm looking for HTC's default softwares (dialer, contacts, album, weather, "Clock" w/ alarms and timer, calendar), and I want to put it in a Froyo. I don't mind if I can't get Sense since I'm using Launcher Pro, the only thing Sense has of interest are a few widgets - which can be mimicked by other ADW.Launcher widgets. But how difficult is it to port that stuff to my Feeyo ROM? How would one do that?
Thank you all for your time, and I think it's all for now.
Not a single answer?
shinobih2o said:
Hello there guys.
I have a few questions which I think have never been asked (at least not as I'm about to ask) before. I reckon they may seem silly and even idiotic at first, but I'm almost sure they're kinda relevant in a way or another.
First: What are the possible methods to really brick your phone?
Explanation: should I take real care with radio/SPL and SPL/bootloader versions? If I flash an incompatible ROM/SPL and/or bootloader, will I be able to boot into fastboot and debrick it, or it's bricked for good?
If I flash an incompatible ROM/Radio will it brick? Also, what kind of impact am I supposed to expect from radio versions? I was using 3.xx and all comms were terrible, now I went back to 6.35 and everything is great, only wifi is kinda weak.
Second: What kind of precautions should I take for testing kernels and mixing them with radio versions?
Explanation: I'm really looking for a Froyo with good battery life (good is like three days with not much data usage - My HTC Touch HD (T8282) was able to do that) and I'm planning to test a few kernels to see which is better in terms of stability, speed and battery life.
Third: How do I extract certain things from a given ROM and port it to another? What kind of importance the kernel has on it?
Explanation: I'm looking for HTC's default softwares (dialer, contacts, album, weather, "Clock" w/ alarms and timer, calendar), and I want to put it in a Froyo. I don't mind if I can't get Sense since I'm using Launcher Pro, the only thing Sense has of interest are a few widgets - which can be mimicked by other ADW.Launcher widgets. But how difficult is it to port that stuff to my Feeyo ROM? How would one do that?
Thank you all for your time, and I think it's all for now.
Click to expand...
Click to collapse
It's easy to brick your phone if you flash the wrong spl with the wrong radio. Basically if you try to flash a HTC spl (one that comes with SenseUI) on a Google phone (non-SenseUI). You're almost always going to brick. Wrong SPL+right radio for your device = brick. Right SPL+wrong radio = possible brick. Wrong SPL+Wrong radio = definite brick.
Test out a bunch of kernels... just make sure you do a nandroid backup first!
It's very rare that you will manage to brick your phone by testing kernels. A nandroid backup backs up the kernel in the boot.img file so if the kernel that you are testing doesn't work then you can always just do a restore. Most of the time anyway...
Most HTC system apps are completely incompatible with Google roms. It's not just kernel but also framework. It's not impossible, just not practical. It's so much easier to design a similiar app to match HTC's than to modify/crack and use the original.
Binary100100 said:
It's easy to brick your phone if you flash the wrong spl with the wrong radio. Basically if you try to flash a HTC spl (one that comes with SenseUI) on a Google phone (non-SenseUI). You're almost always going to brick. Wrong SPL+right radio for your device = brick. Right SPL+wrong radio = possible brick. Wrong SPL+Wrong radio = definite brick.
Test out a bunch of kernels... just make sure you do a nandroid backup first!
It's very rare that you will manage to brick your phone by testing kernels. A nandroid backup backs up the kernel in the boot.img file so if the kernel that you are testing doesn't work then you can always just do a restore. Most of the time anyway...
Most HTC system apps are completely incompatible with Google roms. It's not just kernel but also framework. It's not impossible, just not practical. It's so much easier to design a similiar app to match HTC's than to modify/crack and use the original.
Click to expand...
Click to collapse
Thanks Binary!
If you flash a 32B radio/spl/recovery into a 32A phone it'll obviously brick it, but "how bricked" will it be?
And if I only flash the ROM?
I'm trying to figure out a way to make a FAQ or troubleshooting guide or something you can follow to unbrick your device, and I'm also considering making myself a ROM.
Oh, just out of curiosity: why are the Hero ROMs so popular among Sapphires?
Thanks again Bin!
shinobih2o said:
Thanks Binary!
If you flash a 32B radio/spl/recovery into a 32A phone it'll obviously brick it, but "how bricked" will it be?
And if I only flash the ROM?
I'm trying to figure out a way to make a FAQ or troubleshooting guide or something you can follow to unbrick your device, and I'm also considering making myself a ROM.
Oh, just out of curiosity: why are the Hero ROMs so popular among Sapphires?
Thanks again Bin!
Click to expand...
Click to collapse
How bricked will it be? Allow me to elaborate. The spl calls for a certain radio type to boot the phone. Say you have the 0013 spl that requires the 2.22.23.02 radio. And you flash a radio that is not compatible. The SPL (or bootloader) will continue attempting to activate the radio that is literally not present. It will endlessly loop until it finds that radio which cannot be flashed. Now... sometimes (depending on the situation) you can still get back into the bootloader and simply flash the right radio... but that depends on the situation. Many times you can fix the problem by using the goldcard method but if the spl flash doesn't complete (either because of a hardware malfunction, battery dies (or pulled) while flashing, incompatible spl, etc you will not be able to access the bootloader to flash either a radio or a goldcard. Brick. Also keep in mind that 32A devices (with the exception of the 1.2 devices better known as LE or Fender) require certain SPL and radios and normally come equipped with the HTC Sense UI interface. Because the ROM requires more RAM and ROM to operate the kernels require a different memory map to take the full advantage of it. The kernels usually only operate with certain radios which is one of the reason why there are different ROMs out there (32A/32B). Along with the fact that the 32A ROMs require more space it's pretty much a no brainer.
As for why Sense UI is so appealing... I think it's because of the eye candy and integration. But it's not for everybody. I personally like it but find it too complicated for people that simply want a phone to make calls, sends texts, check e-mail and browse the web. Just my opinion anyway.
single answer^
Binary100100 said:
How bricked will it be? Allow me to elaborate. The spl calls for a certain radio type to boot the phone. Say you have the 0013 spl that requires the 2.22.23.02 radio. And you flash a radio that is not compatible. The SPL (or bootloader) will continue attempting to activate the radio that is literally not present. It will endlessly loop until it finds that radio which cannot be flashed. Now... sometimes (depending on the situation) you can still get back into the bootloader and simply flash the right radio... but that depends on the situation. Many times you can fix the problem by using the goldcard method but if the spl flash doesn't complete (either because of a hardware malfunction, battery dies (or pulled) while flashing, incompatible spl, etc you will not be able to access the bootloader to flash either a radio or a goldcard. Brick. Also keep in mind that 32A devices (with the exception of the 1.2 devices better known as LE or Fender) require certain SPL and radios and normally come equipped with the HTC Sense UI interface. Because the ROM requires more RAM and ROM to operate the kernels require a different memory map to take the full advantage of it. The kernels usually only operate with certain radios which is one of the reason why there are different ROMs out there (32A/32B). Along with the fact that the 32A ROMs require more space it's pretty much a no brainer.
As for why Sense UI is so appealing... I think it's because of the eye candy and integration. But it's not for everybody. I personally like it but find it too complicated for people that simply want a phone to make calls, sends texts, check e-mail and browse the web. Just my opinion anyway.
Click to expand...
Click to collapse
Thanks again Bin, that's pretty clarifying.
Except for hardware problems while flashing stuff (battery removal, cable removal, pc crashing etc) it's probable that ou can still recover and unbrick it, right?
I still wonder why the Hero ports are so common for the Magic... Technical specs are so similar that there's minimum driver adaptation?
I didn't like the Sense launcher, but the HTC softwares are cool - clock, dialer, weather etc.
Do you think it's possible to make a Wiki or FAQ for people who have bricked their phones and troubleshoot it following step by step procedures for specific cases...?
shinobih2o said:
Thanks again Bin, that's pretty clarifying.
Except for hardware problems while flashing stuff (battery removal, cable removal, pc crashing etc) it's probable that ou can still recover and unbrick it, right?
I still wonder why the Hero ports are so common for the Magic... Technical specs are so similar that there's minimum driver adaptation?
I didn't like the Sense launcher, but the HTC softwares are cool - clock, dialer, weather etc.
Do you think it's possible to make a Wiki or FAQ for people who have bricked their phones and troubleshoot it following step by step procedures for specific cases...?
Click to expand...
Click to collapse
I don't think it's necessary b/c there is plenty of information here in the forums.
Plus there are dozens of different MyTouch devices... with different spl versions all requiring their own type of radio. I think that's the reason why it's so confusing. It would be nice if I was smart enough to make a GUI Windows application so simply boot your phone into bootloader mode where you select what you see on the screen and press a selectable option of what you want to do such as flash spl, flash radio, make goldcard, flash goldcard, etc. If you don't see the option then it probably isn't possible yet. That way so many people would mess things up by mistaking their devices for something different. Regarding the wiki... I'm pretty sure there already out there. But I don't know all of the details to make it myself and have it be accurate. I make it a point to be as close as accurate as possible since I'm a mod.
Have been trying my best to figure this out, but so many steps. Lame I know but...
I've got a Rogers 32A SPL 1.33.0010 SAPP50000 3.22.20.17. After buying it used with a Hero ROM almost a year ago, I managed to flash CM6-FroyoRedux-1.6-32a which worked (great!) for almost a year. Lately it has been getting really flakey with lots of FC and problems connecting to wifi.
So I thought a re-flash of ROM should fix things up. No luck, same problems. Super flakey, lots of FC (even with base install). Does that mean I have a hw problem?
So thought I would try another more up to date ROM. Tried CyanogenCARZ-7.1.0... and Ginger Yosi 1.2.1 and a few other but none would flash properly (Recovery on the phone is ClockworkMod Recovery v2.5.0.1 - is that the problem? If so can anyone direct me to easy steps to change this? Found some others but me to dumb, or they to hard to follow b/c no luck. I have done ROM messing about for years, more recently with Dell Streak, but it seemed to be much easier.)
Questions:
- If i can get this far, does it mean my phone is rooted?
- I hear I have a 'Perfect SPL', but if the Hero and the CM6 ROM could be flashed, does that matter?
Where should I go from here?
Thanks for your help, and sorry for being so dumb.
Don't worry, it's natural to have questions whwn confronted with such a confusing phone. I would recommend going to the RUU sticky in the development section, and flashing back to stock. If you still gets fcs and the like on stock, it is likely a hardware issue. Otherwise, we can just reroot and flash another custom rom. Let me know how it goes!
Sent from my Sapphire/dream using XDA App
What you need is a simple (full)wipe.
The problem when applying new roms or re-flashing the same rom is that the userdata and cache partitions are not cleaned.
Userdata = all the app and settings you have accumulated through the years.
Cache = as the name says.
When the partitions are not wiped, then complication can and most likely will occur when (re)flashing roms.
So, inside the recovery, chose to wipe all the partition you can find. Then you flash the rom you want. Wait 5-15 min for it to load and you should be good to go.
paulheth said:
Questions:
- If i can get this far, does it mean my phone is rooted?
- I hear I have a 'Perfect SPL', but if the Hero and the CM6 ROM could be flashed, does that matter?
Click to expand...
Click to collapse
Rooted = have SU binaries... my guess = YES you are rooted.
Perfect SPL does not influence rom flashing since you are working from recovery.
If you are flashing from fastboot, then SPL will have a dominant position.
Looking more like hardware.
Seems it may be a hardware issue? Even with the stock RUU rom from HTC there are still sim recognition and wifi flakiness issues.
Any chance a radio re-flash/update would help?
so today i tried to boot-up my phone but its didnt boot,
Its only show a white screen (of death i guess)
I abled to get into the bootloader (RGB screen)
But when i try to flash the stock wm6.5 htc rom its dont work
I tried to flash from the computer and its just stuck on 0% error 262
I also tried flash from the sd card but its stop after like 20% (and mark in red the radio)
Please please i need help...my phone is dead....Thank you
The hd2 was on android rom
This is exactly the problem i have:
http://www.youtube.com/watch?v=QS02ySr2Kic
I tried:
- task29 - give me 270 error
- Tried to flash the htc stock rom - give me a radio error
- Tried to flash the radio alone - error
- Tried the freezer trick - doesn't work
- Tried soft/hard reset - running for 1 sec and stopped
I will transfer 20$ over PayPal for the one who can solve my problem
what errors are you exactly getting? can you list all of them and what they say in text?
and just in case, what's your hspl version?
hengsheng120 said:
what errors are you exactly getting? can you list all of them and what they say in text?
and just in case, what's your hspl version?
Click to expand...
Click to collapse
when i try to flash a stock wm rom from the sd card its write
Update terminate UPDATE FAIL
and its mark the radio in red
And i dont know how to check the hspl ver. but on the bootloader its said SPL-2.08. HSPL 8G XE
Hello again,
Just wondering if you flashed the correct stock rom check out this post to make sure...
http://forum.xda-developers.com/showthread.php?t=623283
It must be the correct one for your device otherwise there could be a radio problem!!
You do have HSDPL 2.08 on your HD2 so that is a plus. Please post your Carrier's name and the region the HD2 is from. I can use this info to make sure you have the correct stock ROM for your device and see if it might be a older version Win Mo ROM for your device as I think you have what is referred to as a stuck radio. If I remember right some members that have had this was able to get a older version of Win Mo to flash and then they were good to go again. Maybe Samsamuel will come and give some of his enlightened advice as he probably good guide you more than I could.
T-Macgnolia said:
You do have HSDPL 2.08 on your HD2 so that is a plus. Please post your Carrier's name and the region the HD2 is from. I can use this info to make sure you have the correct stock ROM for your device and see if it might be a older version Win Mo ROM for your device as I think you have what is referred to as a stuck radio. If I remember right some members that have had this was able to get a older version of Win Mo to flash and then they were good to go again. Maybe Samsamuel will come and give some of his enlightened advice as he probably good guide you more than I could.
Click to expand...
Click to collapse
I dont know the region, i bought it from newpan in israel, and they dont know ether....can i know from the serial number maybe?
But i have they stock rom and its doesn't work...so it probably not the problem
i9apps said:
I dont know the region, i bought it from newpan in israel, and they dont know ether....can i know from the serial number maybe?
But i have they stock rom and its doesn't work...so it probably not the problem
Click to expand...
Click to collapse
Yes enter the serial number of your device into the HTC website and it should show you the correct ROM for your device. If that does not work try entering the serial number in google and see what you can find that way.
Didn't find a solution yet
Plz guys....its for important cuz..
I am willing to pay even more
i9apps said:
Plz guys....its for important cuz..
I am willing to pay even more
Click to expand...
Click to collapse
As I posted in my first post, it appears you have a stuck radio problem. The only way you will fix it is to find a stock ROM for device that has a earlier version radio. For some reason only earlier radio versions have been able to fix this problem, but it must be in a stock RUU. Just flashing the radio will not work. I am truly sorry I can not offer any more help, but with out the information I asked you for in my second post in this thread I can not help you find a RUU that might would work.
T-Macgnolia said:
As I posted in my first post, it appears you have a stuck radio problem. The only way you will fix it is to find a stock ROM for device that has a earlier version radio. For some reason only earlier radio versions have been able to fix this problem, but it must be in a stock RUU. Just flashing the radio will not work. I am truly sorry I can not offer any more help, but with out the information I asked you for in my second post in this thread I can not help you find a RUU that might would work.
Click to expand...
Click to collapse
can u give me any ROM with earlier radio versions?
I find only with radio_v2 , BTW this is the stock ROM for my hd2:
http://www.htcaddicts.com/uploads/file/122/flash.exe
but i guess its don't work because its without earlier radio versions?
is this software or hardware problem? because my HD2 is like this too, i tried hard resetting but to no avail
Maybe http://forum.xda-developers.com/showthread.php?t=668347
Try your stock ROM.
This is the Stocks on the HTC web page.
If you have tmobile use this with your imei
http://dl.htc.com/ruudownload/t-mobileUS/Filedownload.aspx?pid=leo2
Or if you have EU version;
http://www.htc.com/sea/help/htc-hd2/#download
Choose "news and download". And choose Rom update.
-------------------------------------------------------------------------
Old radio ROMs; EU:
RUU Leo HTC WWE 1.48.479.1 Radio Signed 15.28.50.07U 2.05.51.05
http://hotfile.com/dl/101012104/534f990/RUU_Leo_HTC_WWE_1.48.479.1_Radio_Signed_15.28.50.07U_2.05.51.05.exe
RUU_Leo_HTC_WWE_1.66.405.2_Radio_Signed_15.30.50.07U_2.06.51.07
http://hotfile.com/dl/99848604/1a6fc2a/RUU_Leo_HTC_WWE_1.66.405.2_Radio_Signed_15.30.50.07U_2.06.51.07.exe
----------------------------------------------------------------------------------------
Old Radio ROMs Tmobile:
RUU_Leo_1_5_TMOUS_3.14.531.0_Radio_15.42.50.09U_2.14.50.04_LEO_1.5_Ship
http://rapidshare.com/files/420389702/RUU_Leo_1_5_TMOUS_3.14.531.0_Radio_15.42.50.09U_2.14.50.04_LEO_1.5_Ship.exe
HTC_HD2_RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50.07U_2.08.50.08_2_Ship
http://rapidshare.com/files/421649959/HTC_HD2_RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50.07U_2.08.50.08_2_Ship.zip
Flash magldr and it should work, if it works and it still doesnt let you flash a rom then boot an sd rom from magldr.
Has this not been solved? I see many suggestions but no reply lately from OP.
If it is a radio problem, you can always flash a radio without changing your ROM.
I am curious as to why this started in the first place. Where you using your phone and one day it stopped?
Did you flash the android ROM or did you buy it that way?
Which android ROM was it?
Dblfstr said:
Has this not been solved? I see many suggestions but no reply lately from OP.
If it is a radio problem, you can always flash a radio without changing your ROM.
I am curious as to why this started in the first place. Where you using your phone and one day it stopped?
Did you flash the android ROM or did you buy it that way?
Which android ROM was it?
Click to expand...
Click to collapse
If the OP or anyone else for that matter has what is known as a stuck radio. Then just flashing the radio will not work, it will fail every time. I do not know what causes the issue on HD2's but I do know it does exist. I also do not know why flashing older ROMs via RUU works to fix the issue sometimes either, but again I do know it does on occasion work to fix the device. When you have a stuck radio it does as the OP says it will fail when trying to flash the radio. It also for some reason prevents you from flashing anything to the system partition of the device. Now I know people will say just flash a custom Win Mo ROM as they do not have radios with them or just flash MAGLDR or clk. But again it will not let you flash anything to the system partition so this is null and void as well. Being able to fix this is just finding the right combonation of older SPL version and older radio version in the same RUU. I have never seen a stuck radio be fixed by flashing from SD card.
Dblfstr said:
Has this not been solved? I see many suggestions but no reply lately from OP.
If it is a radio problem, you can always flash a radio without changing your ROM.
I am curious as to why this started in the first place. Where you using your phone and one day it stopped?
Did you flash the android ROM or did you buy it that way?
Which android ROM was it?
Click to expand...
Click to collapse
No , i didn't solved the problem yet
- The problem started from no where
- I flashed the android rom
- The rom was TyphooN
T-Macgnolia said:
If the OP or anyone else for that matter has what is known as a stuck radio. Then just flashing the radio will not work, it will fail every time. I do not know what causes the issue on HD2's but I do know it does exist. I also do not know why flashing older ROMs via RUU works to fix the issue sometimes either, but again I do know it does on occasion work to fix the device. When you have a stuck radio it does as the OP says it will fail when trying to flash the radio. It also for some reason prevents you from flashing anything to the system partition of the device. Now I know people will say just flash a custom Win Mo ROM as they do not have radios with them or just flash MAGLDR or clk. But again it will not let you flash anything to the system partition so this is null and void as well. Being able to fix this is just finding the right combonation of older SPL version and older radio version in the same RUU. I have never seen a stuck radio be fixed by flashing from SD card.
Click to expand...
Click to collapse
Ok, I see. I was not aware of this 'stuck radio' issue. This is the first time I hvae heard of it. I have had the white screen of death before. Mine was caused by a flashable zip that I made which I had misplaced the proper files. I adb'd those files back to the proper location and all was well. That is why I was asking if it happened out of nowhere or after something had changed.
If you cannot do a task 29, but flashing older stock ROMs do work may be because they perform a similar task while flashing. I may be the system partition is too full to allow anything to be loaded to flash.
But, I do not know.
Thread of all HD2 Radios: http://forum.xda-developers.com/showthread.php?t=611787
Custom RUU for flashing: http://forum.xda-developers.com/showthread.php?t=575524
HSPL 3: http://forum.xda-developers.com/showpost.php?p=6891358&postcount=1893
Some official ROMs: http://forum.xda-developers.com/showthread.php?t=577717
More official ROMs: http://forum.xda-developers.com/showthread.php?t=623283
Gold Card mabe?