Related
I was flashing my Hermes with a custom cooked wm6 ROMs today.
First HTC and then Imate telstra.
In starting itself, the installation got stuck because of some reason.
I reflashed and everything is o.k.
After then, just i wished to checked the BL screen.
When i go to BL mode, the Tri color screen appears for few seconds and then a white screen appears aand shows "Loading.........."
After few more seconds showing "loading......" , it reverts back to BL multi color screen..
Is it normal or any problem with my Hermes?
Although, the OS and everthing else is O.K.
Actually i didn't notice before flshing how it was.
If iam wrong pls forgive me
No reply?
I afraid its not an indication before bricking.
Thatsy i asked
That should be standard behavior. BL searches for the ROM to upgrade on SD card first and then tries other sources -that might have caused the delay. Will try it on my device later. Anyway, I do not think it indicates your device is going to be bricked.
KarhU said:
That should be standard behavior. BL searches for the ROM to upgrade on SD card first and then tries other sources -that might have caused the delay. Will try it on my device later. Anyway, I do not think it indicates your device is going to be bricked.
Click to expand...
Click to collapse
Thanks for the info.
you are right.
I have tried taking out the SD card and then it didn't show that screen anymore.
Thanks a lot friend.
skr_xd said:
Thanks for the info.
you are right.
I have tried taking out the SD card and then it didn't show that screen anymore.
Thanks a lot friend.
Click to expand...
Click to collapse
No problem - my device does it too. No reason to be scared. If you have HardSPL it is really much more difficult to really brick the device. There is only one type of bricking that you can get some indices of it's arrival - radio sudden death -but that seems to be a hardware fault.
regards,
karhu
I am real close to confirming a FIX to at the least get MY hermes and other outta being stuck in limbo. Quick Run Down: I HAD my HERMES stuck it Bootloader Mode, well it would get stuck everytime I tried to flash the OS ROM with WM6 (the offical ROM from HTC site)The upgrade process would start, but then it would get stuck at 11% EVERYTIME!! I could get it back at all!! It was stuck in Tri Color Mode!! But a guy I know(guy I bought the Hermes from) is a MASTER at this stuff. He knew more than ANYONE here and he doesnt even use a HERMES?? Anyways I am gonna try my method 1 more time to confirm that it works!! But here is the kicker I have NO GSM after recovering from this HORRIBLE error!! So if you want ur hermes back to use the wifi at least, STAY TUNED!!
NOTE: My METHOD isnt the casuse of the NO GSM, I think I did that when i messed up flashing my OS ROM
But I do NEED to know on how to get my radio back?? I now have a NO GSM error when I turn my hermes on!! I am using the Official WM6 ROM from HTC
nicknowsky said:
I am real close to confirming a FIX to at the least get MY hermes and other outta being stuck in limbo. Quick Run Down: I HAD my HERMES stuck it Bootloader Mode, well it would get stuck everytime I tried to flash the OS ROM with WM6 (the offical ROM from HTC site)The upgrade process would start, but then it would get stuck at 11% EVERYTIME!! I could get it back at all!! It was stuck in Tri Color Mode!! But a guy I know(guy I bought the Hermes from) is a MASTER at this stuff. He knew more than ANYONE here and he doesnt even use a HERMES?? Anyways I am gonna try my method 1 more time to confirm that it works!! But here is the kicker I have NO GSM after recovering from this HORRIBLE error!! So if you want ur hermes back to use the wifi at least, STAY TUNED!!
NOTE: My METHOD isnt the cause of the NO GSM, I think I did that when i messed up flashing my OS ROM
Click to expand...
Click to collapse
The reason the official ROM died at 11% is because around 11% the radio portion of the ROM (radio.nb inside the nbh file) is being flashed to the device. Simple remedy to this to get your device booting into windows mobile is to flash an OS only ROM (nearly ALL the cooked WM6 versions are OS only...but you can make any ROM OS only using duttys nbh tool). This will get you back into window mobile but your problem is that the device has a corrupted radio flash on it.
The problem, as i have already explained in your other thread about this, is that since your flash procedure was halted by you accidentally resetting the computer halfway through a flash the radio portion of the flashing process was probably interrupted and therefore you have most likely caused an irreversible corruption of the radio area.
Unfortunately for you this is probably the only way now to permanently brick your device, as in the device is no longer a phone it is a pda only......in my opinion still a brick.
As I have already explained the only thing to try is (once your device is bootable) to try and flash a radio only ROM.......if this doesnt work im sorry but you have no options, unless you can actually get physically at the chip with JTAG or some other hardware flasher.
The tone of your post in this thread, this post AND this post suggests that we on this forum have not been forthcoming to help you fix your problem......not true. And regrarding your 'Fanboys' rant earlier had you actually read the wiki and un-bricking threads you would see that ALL the info required to revive a hermes (if it is indeed recoverable) has been well documented for over a year now.
NO this method has BROUGHT me outta Tri-color mode twice already, everyone who seems to have this problem has a COMPLETELY USELESS Hermes it wont even turn on, at the leaset MY way will get u back into Windows Mobile, (it worked for me)
yes...as i said in this sentence above:
This will get you back into window mobile but your problem is that the device has a corrupted radio flash on it.
Click to expand...
Click to collapse
Again your device still has a corrupted radio thus isnt working correctly. Having a Tytn which has a non-existant radio is as bad as a total brick.
OKAY if AND when you are able to START the UPDATE process, meaning you see the PROGRESS BAR appear on your HERMES and ur computer. PULL THE USB CABLE AND as FAST AS HUMANLY possible hit the SOFT RESET button!!!
I mean AS SOON AS YOU SEE THE PROGRESS BAR appear on ur HERMEs, You gotta yank out the USB and HIT RESET SUPER FAST, it will shock ur HERMES and bring you back into Windows Mobile!!!!!
nicknowsky said:
OKAY if AND when you are able to START the UPDATE process, meaning you see the PROGRESS BAR appear on your HERMES and ur computer. PULL THE USB CABLE AND as FAST AS HUMANLY possible hit the SOFT RESET button!!!
I mean AS SOON AS YOU SEE THE PROGRESS BAR appear on ur HERMEs, You gotta yank out the USB and HIT RESET SUPER FAST, it will shock ur HERMES and bring you back into Windows Mobile!!!!!
Click to expand...
Click to collapse
Please explain to us all what good that will do? Your radio area is still corrupt.
Now I dunno I have NO GSM, big deal, that is FIXABLE and I dunno if this IS the CAUSE of having NO RADIO
IF YOU WANT to at the LEAST HAVE A Hermes to BEGIN to FIX give it a try, , I have BROUGHT MY HERMES outta be stuck in TRI COLOR Mode 3 times by following this METHOD, I didnt have a GSM but I dunno what the cause of that is, you might have to flash a RADIO or whatever to get that BACK, but if you want the HERMES back to AT least play with GIVE it A SHOT
ffs, READ.....
NO GSM and an error during flash points to a PERMENANTLY dead radio area on the device...ie NOT ABLE TO FIX THIS.
when your computer was reset it resulted in a failed radio flash...dead radio. There is no way to fix this.
nicknowsky said:
OKAY if AND when you are able to START the UPDATE process, meaning you see the PROGRESS BAR appear on your HERMES and ur computer. PULL THE USB CABLE AND as FAST AS HUMANLY possible hit the SOFT RESET button!!!
I mean AS SOON AS YOU SEE THE PROGRESS BAR appear on ur HERMEs, You gotta yank out the USB and HIT RESET SUPER FAST, it will shock ur HERMES and bring you back into Windows Mobile!!!!!
Click to expand...
Click to collapse
Did not work on my hermes
who said anything about Dead Radio?? I dunno if thats the case I see NO GSM thats it, I know nothing further. If you are so wanting to help now, WHY didnt you DO a better job of helping me earlier?? Now ur saying my phone is busted, I dunno whatever I will deal with it, STEP UP dude and help out BETTER, you wanna be all this fourm than SHOW IT
koorosh_bsboys said:
Did not work on my hermes
Click to expand...
Click to collapse
u gotta do it as soon as the BAR APPEARS, instantly when u see 0% pull it and do a soft reset, 3 times I have gotten outtta TRI COLOR SCREEN
nicknowsky said:
who said anything about Dead Radio?? I dunno if thats the case I see NO GSM thats it, I know nothing further. If you are so wanting to help now, WHY didnt you DO a better job of helping me earlier?? Now ur saying my phone is busted, I dunno whatever I will deal with it, STEP UP dude and help out BETTER, you wanna be all this fourm than SHOW IT
Click to expand...
Click to collapse
NO GSM.....................what do you think that means???? NO GSM shows the radio portion of the device is corrupted, the radio stack is responsible for the phone functions on the device...the GSM functions.
The directions i showed earlier are IDENTICAL to what im saying now......since it hasnt worked your device is not fixable. Booting into windows is easy to achieve but you wont be getting back the phone functions any time soon.
-----------------------------------
Final post since you BLATANTLY don't understand the device or what you are doing...hence how you ended up in this position.
nicknowsky said:
who said anything about Dead Radio?? I dunno if thats the case I see NO GSM thats it, I know nothing further. If you are so wanting to help now, WHY didnt you DO a better job of helping me earlier?? Now ur saying my phone is busted, I dunno whatever I will deal with it, STEP UP dude and help out BETTER, you wanna be all this fourm than SHOW IT
Click to expand...
Click to collapse
Your method did not help me, but thanks anyway dude.
I think you should load hardspl on your device and then try flash any radio.
so read the WIKI and i wish your phone will be just fine. but mine is screwed up
NO no nonono You mnisunderstood me, I know WHAT NO GSM is I was refering to what YOU said in a previous post about my RADIO and how It is DEAD forever and what not< True be told, it might be I dunno, and ya know what I WANT to send it into HTC for repairs, thats what I have wanted to do since the start of my comedy of errors, I know what ur saying but you should help me IN COMPLETE n00b terms and showed me then what you actually thought i could of done, and I know u will say thats what you did, but u could of done it better
koorosh_bsboys said:
Your method did not help me, but thanks anyway dude.
I think you should load hardspl on your device and then try flash any radio.
so read the WIKI and i wish your phone will be just fine. but mine is screwed up
Click to expand...
Click to collapse
I am in the process of reading UP on what I should do bout my RADIO, I might try that, dunno yet I am not done fixing my Hermes, but I WANT to send it in for repairs thats whats best
chillax dude
jaysus boy,will you ever relax, read the posts fully and use ALL the resources available in the forum as well as the excellent wiki site.anyone, including noobs can, if they follow the guides,flash the os/radio of their hermes with more or less complete confidence.Mr vanx himself produces some of the best and most idiot proof guides available but i suppose a few get thru!
do not abuse the good nature and generosity of the rom gods in this forum 'cos you broke your phone,read widely,chose carefully and make your choice.if you cant fix it then send it away and get a proffesional to fix it if possible.
good luck then
nicknowsky said:
..but you should help me IN COMPLETE n00b terms and showed me then what you actually thought i could of done, and I know u will say thats what you did, but u could of done it better
Click to expand...
Click to collapse
hey.. bro, nobody owes you a living... don't sound so ungrateful.. the fact that mrvanx came to share his knowledge is good enuf.. please be polite..
my 2 cents..
kipe said:
hey.. bro, nobody owes you a living... don't sound so ungrateful.. the fact that mrvanx came to share his knowledge is good enuf.. please be polite..
my 2 cents..
Click to expand...
Click to collapse
Here here... Well said.
The type of brick help was requested with is well documented - and while "the fix" the OP described in this post may work for him - it's more likely to cause more problems if someone innocently tries this on an unbrickable phone. Interrupting a flash is always bad advice - and a little reading up on No-GSM bricks would have been a start - or the FAQ on "getting stuck in the tricolour screen!"
There is no such thing as "shocking" a device back into life. You've been watching to much ER where they defibralate humans - doesn't work with electronics generally
There is restoring an OS image, there is (if you're lucky) recovering from intermittent bad blocks by doing a couple of flashes but it's much safer to just flash the bits you need by carefully making the .nb files required using dutties NBH tool then making your own NBH to flash containing just an OS image or just a radio image - or whatever you want to try to flash. If a flash gets stuck - it's getting stuck for a reason and that reason needs investigating before trying things which are known to cause bricks in the first place hence you strip the image down and see what flashes and what doesn't. If noobs don't recognise problem solving techniques - then they haven't read enough before trying to show off an upgraded phone to their mates and should stick to manufacturers updates only. Harsh but in my opinion true.
Sorry, I'm about to have a late night rant...
The reason many experienced users don't always reply to calls for help immediately is because all the information known is well discussed and well documented and people get tired of effectively cutting and pasting solutions to "noobies" just flashing an image not knowing what could happen and what to do if the worst happens and what to do when it all goes wrong. The front page of this forum usually has 3 requests for help on it to solve a brick issue - and generally all 3 are the same type of brick so should an experienced poster have to post the same thing in three threads? No.
Even worse - many newbies don't start with the obvious basics like flashing HardSPL or they end up with a brick and then try to unbrick it by doing so many other things that they end up with a hybrid brick and don't even know what steps they did to make it! Sadly, I feel that if people can't be arsed to read up on stuff and just want to have the very latest thing to show off with - then they deserve the brick they get (and should sell it real cheap on ebay so I can buy them up!) At the end of the day - everything on these forums should be considered experimental and non-supported. If you want full support - go to your network, HTC or Microsoft and PAY for it. If you want to join a community who loves experimenting and discussing the issues then join in, support the forum (make some donations to the good people who keep things ticking) and most importantly learn about your device.
My first upgrade was well over a year ago - and it took me about 2 months of research into de-bricking - and plenty of bookmarking - before I even attempted it so I knew what could go wrong and at least what steps to take to recover my own device if it happened.
Have I bricked my phone? - Of course while experimenting with cooking roms - I've unbricked them using others posts and the wiki here and I've never had to ask how to do it - but I have had to spend several hours reading (with lots of patience and learning a lot in the process) but at least when I flash I know the risks and don't just scream that I used <insert whatever ROM> here created by <insert poster> and it bricked my hermes therefore it must be <insert poster who released the ROM> fault. Nor to I slag off things that don't work - be it ROMs, procedures or advice.
The advice to anyone who is a noob really is to read, read and read - Do your research and know about your device before you tinker with it. Not to the level of being able to explain what each GPIO carries - but at least to understand the different parts of the device - the different images and what to do if any part of those images doesn't quite work properly (ie - bricks)
And if it does brick... DON'T DO ANYTHING until you know why it's bricked and have read the unbricking threads and the wiki. Someone WILL respond if you list what you've tried and what happened when you tried it. They don't respond to "help, I flashed xxx and it doesn't work."
The wiki and unbrick threads might be long but virtually every brick is covered and it's better to know about bricks before you end up holding one in your hand
Rant over.
Ok i have been trying to just get my phone to work not really looking into getting nething new for it right now but the other day i turned off my phone to charge it and then when i went to turn it back on it was stuck in the bootloader screen if im not mistaken (red green blue white bars) and i cant get it to boot up my phone i tryed useing the never brick method and i got a new spl but dont know what to do after this can someone please help thanks
"Never brick method"? Who's your source for ills and leaving you hanging? What new SPL and what are you attempting to achieve?
Use the Wiki link in my sig (also linked with a sticky thread at the top of the forum entitled 'NEED HELP?? LOOKING FOR GUIDES?? NEW?? Read the XDA-Wiki for the Titan before posting'.
Return back with what you've attempted and read if you still cannot resolve your problem.
my objective is just to have a working phone turned this phone off to charge it and then went to turn it back on and the phone boots to the red green an blue stripes cant get rid of it
i dont know what to do thats why im posting does anyone have a clue where i can start i dont care if it has modified firmware or w/e on it i just want my phone to work i think verizon isnt gonna give me another warrenty replacement so im just wondering if neone can help me fix it without dealing with buyin a whole new phone
marcus556 said:
my objective is just to have a working phone turned this phone off to charge it and then went to turn it back on and the phone boots to the red green an blue stripes cant get rid of it
Click to expand...
Click to collapse
So you are saying your phone is just stock rom and it did this?
Are you sure you have not messed with flashing anything?
what version does it say the SPL is?
you said you flashed an SPL? What version?
These things all need to be compatible versions. This can be fixed pretty easy, but the method to fix it depends on what you have done, and what versions of SPL, Radio, and Rom you had when it broke, and what Versions you have now.. and what you did to try and fix it.
Reply with accurate information and I'll tell you what to do to fix it.
Any method I give you may require an SD card thats less than 2GB and non SDHC. You'll need it formatted to fat32... do you have this?
i dont know if it will help since i am still new to this, but does the power+camera+soft reset reboot the phone back into the bootloader ? and if so can you just reflash via sd card?
maniakx said:
i dont know if it will help since i am still new to this, but does the power+camera+soft reset reboot the phone back into the bootloader ? and if so can you just reflash via sd card?
Click to expand...
Click to collapse
Thats pretty much it... but depending on the SPL it's got to be flashed with the right versions.... so once we know at LEAST what SPL, and hopefully the radio.. it'll be simple.
Also... What provider do you have? (sprint, verizon, etc...)
AND do you want DCD 3.2.6 or do you wanna stay with a stock rom.. I can help you either way.. no difference in ease to get it done.
marcus556 said:
i dont know what to do thats why im posting does anyone have a clue where i can start i dont care if it has modified firmware or w/e on it i just want my phone to work i think verizon isnt gonna give me another warrenty replacement so im just wondering if neone can help me fix it without dealing with buyin a whole new phone
Click to expand...
Click to collapse
marcus, you have start by demonstrating a motivation to help yourself.
Starting a thread with the rather ambiguously useless title of "Help" is already a big no-no.
Second, I have given you the links to the Titan Wiki that will explain what you are seeing and routes to go from there.
Third, people here can directly rehash info from other sources (such as the wiki or their own knowledge) but it's rather like shooting in the dark since you don't seem to be too concerned by helping yourself as you still haven't stated that you have bothered to read the forum's fundamental resources and return to specifically state where you are at.
Common upgrading problems explained and solved is found from the main page of the Titan Wiki under the heading of Problems and Questions
(!Pleeeease read here before posting on the Forum):
P: My device is stuck at the Red, Blue and Green Screen?
S: 1. To exit the bootloader, press the reset.
2. Connect your Titan to your PC's USB and then on your PC execute titan_exitbl.exe
3. You may need to reflash the Radio/Operating system ROM
Click to expand...
Click to collapse
From what you have described, those are the routes to attempt.
ok i never messed with the phone tryin to upgrade it or nething it jus happened one day after i turned the phone off and wwas chargeing it when i tried to turn it back on it was at that screen and i cant get it off so thats all the information i can give u other then that spl-1.04.0000 thats all i can give u sorry im not as smart as some of you guys with this stuff oh and yes i have a card
marcus556 said:
ok i never messed with the phone tryin to upgrade it or nething it jus happened one day after i turned the phone off and wwas chargeing it when i tried to turn it back on it was at that screen and i cant get it off so thats all the information i can give u other then that spl-1.04.0000 thats all i can give u sorry im not as smart as some of you guys with this stuff oh and yes i have a card
Click to expand...
Click to collapse
Sounds like it is a stock Verizon phone pre MR1. If you are not interested in free GPS then get the MR1 update from Verizon and run it with that boot screen on the phone connected via USB to your computer.
If you do want free GPS then follow the WiKi basically starting from scratch with a new phone. You could also try to hard reset the phone and see if it will come back alive as well.
Just to clarify, you can actually get third party GPS working on MR1 (see this thread).
i got a warrent replacement and shouldnt have even mesed with it i went to update to windows mobile 6.1 and it will start to update but make a noise on the computer like it was disconnected and say error my spl no is 2.07.000
i am starting to really hate this fing phone!!!!!!!!!
marcus556 said:
i got a warrent replacement and shouldnt have even mesed with it i went to update to windows mobile 6.1 and it will start to update but make a noise on the computer like it was disconnected and say error my spl no is 2.07.000
Click to expand...
Click to collapse
2.07 I believe is the "Locked" spl from Sprint or used with NueSPL relocker. If you want to flash the latest MR1 update from Verizon, I'm assuming, don't quote me on this, you can do it with this spl. You still may have to "Relock" it to 1.07 or below using Titan-Relocker, not NueSPL's version. What does your phone display now? Still 3 color?
the phone is displaying tita100 spl-2.07.0000 below that it says cpld-9 and at the top right it says ruunbh and where can i get the relocker at?
It's stuck in bootloader mode. Use the attached utility to "Unlock" the bootloader "MODE"
OR....
if you are going to flash to a custom rom... copy a TITAIMG.nbh file to your MicroSD card and hit reset.
its saying cannot open usb port. please make sure, that usb connection in activesnc is disabled. Also make sure, that your usb cable is properley connected. i went an made sure it was disabled and it is connected right
marcus556 said:
its saying cannot open usb port. please make sure, that usb connection in activesnc is disabled. Also make sure, that your usb cable is properley connected. i went an made sure it was disabled and it is connected right
Click to expand...
Click to collapse
Best steps to take....
Disconnect cable.
Get into bootloader mode.
Open activesync and uncheck the Allow USB Connections and Allow Connectsion to one of the following. Click OK to make sure it takes.
Then connect the USB cable.
When Bootloader says USB instead of Serial... then execute the titan_exitbl.exe
ok it didnt work i unplugged everything the cable from the computer the cable from the device and went into activesync and unchecked the boxs went back in to make sure they were unchecked they were then i plugged the cable up waited like you said for the usb and ran the file got the same message......thanks for your patients with me.......
by the way i dont know if u know this but it is stuck in bootloader i cant get into the phone at all so the micro sd card wont work
i just bought my hd2 fromt-mobile and naturally couldn't resist but to modify it
So i installed and flashed the HSPL2 with no problem it worked perfect and very fast and easy....and i installed Mesus Rom and love it did my registry tweeks got the phone running awesome!!!
Now i woke up early was browsing on htcpedia and glanced at the new DOPOD version radio.... well..... it installed fine no errors but when it got to 100% to reboot BLACK SCREEN. I've tried getting the phone into bootloader mode nothing, tried a master reset holding down the volume up and down at the sometime and press power nothing, i've tried to plug it in the computer it recognizes it my computer makes the connected to a device noise but when it goes to initialize the hd2 i get this driver error:
Qualcomm CDMA Technologies MSM failed.
i've also read once u have hspl or hspl2 installed it can not be bricked can someone please help me on some step by step and some links
the radio i flashed that caused this was 2.051.03(DOPOD)
poulosjr said:
i've also read once u have hspl or hspl2 installed it can not be bricked can someone please help me on some step by step and some links
Click to expand...
Click to collapse
I hope so for your sake, however... When you say you have a HD2(T-Mobile), do you mean the US one?
Flashing guide for TMOUS HD2 states:
mskip said:
PLEASE READ ALL THE INFORMATION IN THIS GUIDE BEFORE INSTALLING HARDSPL OR FLASHING A ROM/RADIO. IF YOU FLASH AN INCOMPATABLE ROM OR RADIO ON THE 1024LEO THEN THERE IS A POSSIBILITY OF BRICKING YOUR DEVICE SO PLEASE BE VERY CAREFUL!!
Click to expand...
Click to collapse
poulosjr said:
the radio i flashed that caused this was 2.051.03(DOPOD)
Click to expand...
Click to collapse
Is that this one (2.09.51.03)?
Says in the post there it doesn't support 576MB RAM. That would probably mean it's not compatible with the TMOUS HD2. I vaguely remember that being the case for any version with 51 in it.
Sorry to be completely unhelpful here, but I wouldn't have a clue on how to revive your HD2.
Perhaps people in the TMOUS HD2 Flashing guide thread might know something?
----
meptik
chalk another non-starter up to a ..51.. radio on a tmous phone.
still not seen a fix
is the tmobile us hd2 recoverable or is it bricked out?
sorry, not sure. see other threads HERE (post three) and HERE , , it's also mentioned in the mtty and the HSPL (regular HSPL and tmous HSPL) threads.
As far as i can gather so far, roms below 2.10 cause not to boot, but can recover from bootloader, radios with a ..51.. in them cause it not to start at all. (because ..51.. radios don't support the 576mb, presumeably)
Best of luck.
I am having the same problem...I can boot in to bootloader mode and in to restore mode but there is no display on the screen the computer detects it and everything and I can flash the phone, but nothing ever comes up not the tmobile screen or anything...I had this problem when I first got the phone only the backlight would come on, but I took the battery out for a few minutes and then it worked fine until the battery died then the problems started again, then I flashed it with the with the latest tmobile us official rom I could find and it worked until I turned it off and then I could not get it to turn on again. I somehow through some voodoo or something after trying the restore feature like 20 times got it to come on, the I had to take the battery out to put in the sim card and now nothing...The thing I can't understand is why windows recongizes the phone and I can flash it but nothing changes nothing just a blank screen with the backlight on I can attach to it with mtty and everything I ran a task 28 and task 29 and reflashed it nothing I have tried cooked roms and everything still no display...Someone please help...I plan on returning it for a new one except there are none in my entire state, I have called every tmobile store in the phone book and none know when they will get more in...
brandon2004 said:
I am having the same problem...I can boot in to bootloader mode and in to restore mode but there is no display on the screen the computer detects it and everything and I can flash the phone, but nothing ever comes up not the tmobile screen or anything...I had this problem when I first got the phone only the backlight would come on, but I took the battery out for a few minutes and then it worked fine until the battery died then the problems started again, then I flashed it with the with the latest tmobile us official rom I could find and it worked until I turned it off and then I could not get it to turn on again. I somehow through some voodoo or something after trying the restore feature like 20 times got it to come on, the I had to take the battery out to put in the sim card and now nothing...The thing I can't understand is why windows recongizes the phone and I can flash it but nothing changes nothing just a blank screen with the backlight on I can attach to it with mtty and everything I ran a task 28 and task 29 and reflashed it nothing I have tried cooked roms and everything still no display...Someone please help...I plan on returning it for a new one except there are none in my entire state, I have called every tmobile store in the phone book and none know when they will get more in...
Click to expand...
Click to collapse
sounds more like a dodgy phone than a bad flash. wait for stock and get it exchanged.
bricked
I have the same problem. I just wanted to go back to stock rom and i downloaded this bull crap rom
RUU_Leo_HTC_WWE_1.43.405.1_Radio_Signed_15.26.50.07U_2.04.50_22_2_Ship.exe
BRICKED MY TMOBILE USA HD2!!! DO NOT LOAD THIS ROM!!!!
took it to the tmobile and i now have to wait till tomorrow for them to get more in stock... im pissed!!!
sk8er982 said:
im pissed!!!
Click to expand...
Click to collapse
i really hope you mean pissed at yourself, that rom is about as far away from compatible as they get for the tmous.
Cannot believe we don't have a sticky warning about xx.51.xx radios and TMOUS HD2s yet!
i am...
samsamuel said:
i really hope you mean pissed at yourself, that rom is about as far away from compatible as they get for the tmous.
Click to expand...
Click to collapse
i am pissed at myself. anyway i got a new phone now.
how do i go back to original firmware if i flash a cooked rom?
they need to remove the .51 versions, i just bricked mine and all i saw really was to not install it, not that it would completely brick it. I'm really upset.
donalgodon said:
Cannot believe we don't have a sticky warning about xx.51.xx radios and TMOUS HD2s yet!
Click to expand...
Click to collapse
I hope that was sarcasm LOL
sk8er982 said:
i am pissed at myself. anyway i got a new phone now.
how do i go back to original firmware if i flash a cooked rom?
Click to expand...
Click to collapse
That info is still in the same thread that y'all should have read before bricking your HD2's. Many (and I mean many) of us flash our HD2's all the time, run ROM's custom built to even let us run the latest and greatest Android builds available.
When you and the OP (iirc) get some fresh HD2's, read the info and links in the stickies here. There's enough info in those to get you well on your way to mastering your HD2's destiny.
Best of luck.
So true. ALL chefs always warn ab NOT flashing .51 radios on TMOUS HD2 or they posting links to HOW TO FLASH TMOUS HD2.
Dont rush with first flashing! Thats the best way to brick ur phone!
Always read the forum! Thats the bast way to make ur phone happy
htc hd2 after installing andriod
hey everybody.... I have a big problem with my phone which is when the fixer tried to install android on it it become freezing (black screen and just vibert)
so he told me that he has no idea and my phone will not fix ...so please help me out..
sherko_bax said:
hey everybody.... I have a big problem with my phone which is when the fixer tried to install android on it it become freezing (black screen and just vibert)
so he told me that he has no idea and my phone will not fix ...so please help me out..
Click to expand...
Click to collapse
it is tmous yes? it sounds like he flashed a bad radio,
If that is the case, i would be MAD AS HELL and demand they pay for the replacement of teh motherboard.
Dear All,
Before I start, please forgive the repetition, as I know this issue comes up a lot but I've searched all over and can't find a solution for my circumstance. If there's a post I've missed, please direct me there...:fingers-crossed:
I recently received a Lumia 800 with a Qualcomm bootloader, sim-locked to a UK network. The first thing I did was use NSSPro to remove the simlock, which was successful, but I also wanted to debrand and try a custom ROM..
I read round the issue a fair bit and was going to go down the Linux 'dd' route when I spotted the Windows flashing utilties. Ever keen for an easy life, I went ahead and flashed my handset with FunkyRom, apparently making two fatal errors; not backing up my partitions in Linux and not using Linux to do the flash. Laziness stopped me backing up and I'm aware I deserve what I get for that, but the warnings about flashing in Windows were a little harder to spot and I only found those after the event.
ANYWAY....
Unsurpisingly it turns out, the Windows flash bricked the 'phone. I can get it into Qualcomm bootloader mode in Windows and Linux, I can read the partition map (attached), flash it in NSSPro, 'dd' it in Linux and flash it with the Windows tools, but it won't boot past the Nokia logo. After initial flashing the battery went haywire as well and wouldn't hold it's charge much beyond ten minutes. The battery is fine, I have swapped it out for a new one and it works fine in another 'phone, so I'm not sure what that was about. One other thing to note is I've never been able to hard reset it after flashing, the combination of button presses does nothing, no matter how long I hold them down, all that happens is the 'phone reboots if I release the power button.
I've tried many reflashes, replacing the third partition etc but I think I'm just laying s**t on top of s**t now and would appreciate some guidance. I don't think it's terminally bricked because I can still read/write from/to it in Linux, NSSPro etc, but I'm normally a Nokia N9 man, so this partition structure is unknown, I don't know what I'm looking for.
Any help much appreciated, with the note that I realise I ballsed up not making a backup, so you can skip telling me I'm a fool, I'm getting that enough from the missus..!
Sorry for the looong first post,
Squid
Not sure about fixing it as I have the 710, but Im pretty sure you could RMA to the place you bought it, and they would be too lazy to do full checks on what you did to it, send it back to Nokia and send you a replacement
I've bricked tablets and GPUs and phones and RMA'd, and not once have they ever questioned what I did
One phone I RMA'd I'd flashed a German ROM to and everything was stuck in German, UK company just walked me through factory resetting it on the phone, didn't work obviously, so they gave me a new one
Just an idea if you can't fix it yourself
Other options would be taking it to a local phone repair store who have tools to flash bricked phones, there have been a few here who didn't read the "DO NOT FORMAT" posts, and hit the format button bricking their phones, took it to a repair store who flashed it back to a working state for them
Good luck
Hi and thanks for the reply.
I'll be honest, I'm a Nokia N9 man myself, I was hoping to unlock this one as a spare's spare (it looks and feels familiar), so I'm unlikely to be taking it for repair if I can't get it going myself, but it's interesting to hear you've never been questioned about any DIY work you may have done, I've always thought they'd be hot on that...?
I am holding out for a technical hint or two on something I may have borked during the flash itself, and whether that might be recoverable, after all I can get to the bootloader, just whatever I flash on top (FunkyRom, Rainbow Mod etc) just don't load. Also, why doesn't hard reset work on this 'phone? I have questions but I've run out of brains for answers.
Are there generic full partition dumps available to dd in Linux that would be like a vanilla image? Are there specific partitions that may be the problem? If it gets to the Nokia logo but no further, how far in the booting process has it come?
Squid
Hi John,
Maybe you can try this: http://forum.xda-developers.com/showpost.php?p=47076870&postcount=2
Otherwise I can download an original rom for you, maybe you can flash that with nss, just let me/us know.
Greetz,
Rataplan said:
Hi John,
Maybe you can try this: http://forum.xda-developers.com/showpost.php?p=47076870&postcount=2
Otherwise I can download an original rom for you, maybe you can flash that with nss, just let me/us know.
Greetz,
Click to expand...
Click to collapse
Brilliant, I'll take a look at the NSU first, thanks!
Rataplan,
No joy with the NSU Retail I'm afraid. Do you think you could let me have an original ROM please as mentioned? After that, I guess it goes to the bin..
John
Ok, gonna download and upload this evening, keep you informed.
Greetz,
Rataplan said:
Ok, gonna download and upload this evening, keep you informed.
Greetz,
Click to expand...
Click to collapse
Great, thanks!
john smash said:
Great, thanks!
Click to expand...
Click to collapse
Ok John, you can download the rom here: https://dl.dropboxusercontent.com/u/9417919/rm-801.7z , the rom is based on RM801_059L8M3_1750.0805.8773.12220, I also suggest to read this: http://forum.xda-developers.com/showthread.php?t=1457341 and
this: http://forum.dailymobile.net/index.php?topic=77419.0
Greetz,
Many thanks, I'll try it later. I have actually tried those threads you linked previously but I'll take another look.
Cheers,
John
Hey there Rataplan,
No dice I'm afraid. I can't get the phone connected in anything other than Qualcomm mode, so I can't use NCS to flash. I can use NSSPro to flash a file with .nb extension but not the files you uploaded. NSU Retail asks me to connect in Qualcomm mode then doesn't recognise the phone once I do that.
I just don't understand how if I can get to the Qualcomm bootloader, why flashing RainbowMod or FunkyRom/FunkyRom lite doesn't work, do you have any suggestions? Is there a way to check if any of my partitions are corrupted?
JS
EDIT - Just read this post - http://forum.xda-developers.com/showpost.php?p=29583840&postcount=2 and renamed the boot.img of the ROM you uploaded. Now my 'phone shows a 'Three UK' splash screen, then the nokia logo, but still doesn't load. Is there a way to know what stage of the boot the 'phone is getting to before it hangs?
Ha! Got it!
Using the extract and rename method I flashed the 11412 firmware (oldest one in Navifirm) for product code 059M062 and bingo! It boots and there's no simlock...
Thanks for all your help Rataplan, 'phone revived!
:victory:
Great, I know it had to work, that's why I gave you an copy of an older rom, I'm glad you solved it yourself , take care next time.
Greetz,
Rataplan said:
Great, I know it had to work, that's why I gave you an copy of an older rom, I'm glad you solved it yourself , take care next time.
Greetz,
Click to expand...
Click to collapse
Will do..
I've changed my product code with NSSPro but if I try to flash any later ROMS then it goes back to being borked. I can always recover to this ROM now but I'm wondering why I can't upgrade?
john smash said:
Will do..
I've changed my product code with NSSPro but if I try to flash any later ROMS then it goes back to being borked. I can always recover to this ROM now but I'm wondering why I can't upgrade?
Click to expand...
Click to collapse
I have to take a look at your product code, did you try Nokia Update Retrailer.
The original product code was 059L7C6, I've successfully flashed it with a ROM for product code 059M062 and confusingly, I've written the product code 059L7C2 with NSSPro..
Does it bork it if you try to update it through Zune ?
*Detection* said:
Does it bork it if you try to update it through Zune ?
Click to expand...
Click to collapse
Hey,
Just plugged it into Zune now and it's offering me 7.10.7740.16. Question: Does using Zune overwrite the Qualcomm bootloader? Once that's gone I know I can't get any custom ROMS loaded on here..
Thanks,
JS
For those who may be interested:
I've got a working Lumia now, flashed with a 12220 firmware on a UK product code but that's it, I can't get anything more up to date on there. Every time I flash something more recent I get stuck at the Nokia screen. In addition, I get the same result with any of the custom ROMs, they just won't load. Could my hardware version be preventing the upgrade? Any ideas..?
JS
john smash said:
Hey,
Just plugged it into Zune now and it's offering me 7.10.7740.16. Question: Does using Zune overwrite the Qualcomm bootloader? Once that's gone I know I can't get any custom ROMS loaded on here..
Thanks,
JS
Click to expand...
Click to collapse
No the update doesn't overwrite the bootloader, I flashed the unlocked bootloader to mine and have flashed custom & stock & custom & stock in that order and everything stayed unlocked