Hello, well I recently got this HTC evo 3D from a friend, he bought it extemely cheap since it was not working, and he tried to fix with no success so he gave it to me to try. The thing is that I have some experience fixing samsung phones but HTC seems like a really new thing to me. Anyway the first thing I would like to ask its about the real state of the phone. The phone only turns on and shows a black screen, the htc logo in white letters at the center, and one triangle in each corner, all of the triangles have an exclamation mark.
Thats all it shows, I tried the volume down + power button to enter the recovery screen but it doesnt work. We dont really know what happened to the phone or how this device was bricked, and since I dont really know htc I cannot really guess. Not sure either if this device is either S/On or OFF, rooted or etc.
I read the HTC Unbricking Project and thought "I might as well try that", but I dont really understand what they are saying, not about using linux, its about the tools they say you need:
the appropriate package for the device
the latest RUU for your device
a device bricked by writing security flag 3 with an unsigned hboot, or caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device
We dont use any of this on samsung phones so I dont really understand what they mean, could anyone offer an overall advice of what should I do or where to read about this stuff.
Thanks in advance
Update: I managed to get this white screen when I unplugged the usb cable, hope it helps
Robert1989 said:
Hello, well I recently got this HTC evo 3D from a friend, he bought it extemely cheap since it was not working, and he tried to fix with no success so he gave it to me to try. The thing is that I have some experience fixing samsung phones but HTC seems like a really new thing to me. Anyway the first thing I would like to ask its about the real state of the phone. The phone only turns on and shows a black screen, the htc logo in white letters at the center, and one triangle in each corner, all of the triangles have an exclamation mark.
Thats all it shows, I tried the volume down + power button to enter the recovery screen but it doesnt work. We dont really know what happened to the phone or how this device was bricked, and since I dont really know htc I cannot really guess. Not sure either if this device is either S/On or OFF, rooted or etc.
I read the HTC Unbricking Project and thought "I might as well try that", but I dont really understand what they are saying, not about using linux, its about the tools they say you need:
the appropriate package for the device
the latest RUU for your device
a device bricked by writing security flag 3 with an unsigned hboot, or caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device
We dont use any of this on samsung phones so I dont really understand what they mean, could anyone offer an overall advice of what should I do or where to read about this stuff.
Thanks in advance
Update: I managed to get this white screen when I unplugged the usb cable, hope it helps
Click to expand...
Click to collapse
I can't make out what all that says on your white screen(that's bootloader by the way.) I need you to tell me a few things first.
1.Is the device s-on or s-off? To find out go to the top line and read across to see if it is s-on or s-off
2. Is the bootloader locked, relocked or unlocked? You can see the status at the very top highlighted in purple.
3. What's the hboot version
4. Also, what's the radio band number?
Now the thing is, with HTC devices there are two different s-off's
S-on bootloader unlocked and true s-off. S-on bootloader only gives you access to some of most of the name memory unlocked. You can't downgrade firmware. You can only flash your current one or upgrades. If you upgrade your firmware, your stuck. S-off gives full access to the whole nand memory. The idea is to gain s-off as it is much easier to flash things, more access to software, can upgrade or downgrade your hboot and firmware.
Edit: I got good news for you. Since your able to access your bootloader screen, your phone is not bricked. As a matter of fact, as long as it can boot up to something, its not bricked. Now keep in mind, you will need to download an ruu file and run it to restore that phone.
Robert1989 said:
Update: I managed to get this white screen when I unplugged the usb cable, hope it helps
Click to expand...
Click to collapse
I've never seen that orange "RUU" flag on the bootloader screen before. I'm not sure what it means but it may need to have the 2.89.651.2 RUU (the build it currently has) re-flashed so I would try running that version of the RUU (similar to Kies) after connecting it via USB to a Windows PC.
You can get the RUU here.
ramjet73
Your bootloader indicates you're S-ON and Re-Locked, which means that it was once HTC unlocked (The manufacturer's poor substitute for unlocking a bootloader)
The device is definitely not Bricked by any definition of the term. A true brick doesn't power on. This is just "soft bricked" meaning it's functional, but has a corrupt partition or partitions that are preventing it from reaching the android subsystem.
You need to use the RUU EXE when you're at that white screen. It should recognize it and re-flash most of the partitions on the device. You might also need to run it twice possibly.
Related
ok, now I am totaly screwed.... imate stuck in loading screen with version numbers etc... Not going further and bootloader not available.... Is there any way to communicate with unit while it's in this mode?
what you are saying is unclear. Does your device say "Serial" (or "USB") on top with "V 1.06" on the bottom?
If so, you ARE in bootloader mode. If not, then please specify what it actually says on the screen
no, it's not in bootlader mode. it's in Tmobile screen at the bottom it says R 1.12.00
G blah
D blah
it stuck there. and I can't enter bootloader mode. looks like it's totaly dead
What happens when you try to enter bootloader (Power - Action - stylus)?
What happens when you try to press (Camera - Record - Stylus)?
GO TO HELL ROM 1.72.104
F%@#&!?G FREAK ROM!! :evil:
Please calm down... in a day or two, this problem will be solved and everyone will probably be back to where they were
((and a lot smarter than they were too))
Victor said:
What happens when you try to enter bootloader (Power - Action - stylus)?
What happens when you try to press (Camera - Record - Stylus)?
Click to expand...
Click to collapse
It both cases it still sits in this screen
Try removing the battery and waiting for a period of time (20 Mins ??)
Then try the two things again (first without the battery -- for the heck of it -- and then replace the battery and try them)
...obviously, you need to remove it from the charger too :wink:
to be clear... nothing is expected to happen when you try to do these without the battery in, except perhaps (??) clear out any remaining charge held in capacitance, if any.
Kinda like removing the batteries in the remote control of a TV and then pushing a button on it (there is always enough charge in the capacitors for a single push/command to the TV
that once happent to me
and softreset dident help
so i did a hardreset and that fixed it
fixed my data too though :/
Rudegar said:
that once happent to me
and softreset dident help
so i did a hardreset and that fixed it
fixed my data too though :/
Click to expand...
Click to collapse
nothing happenes Sent email to imate tech support. I am not sure if they going to warranty unit with Tmobile betta screen stuck on IMATE. looks like i am short 700 USD........
Is there any way to communicate with XDA2 when it stuck in this loading screen? Terminal via serial cable doesn't work. anyother low level programs are out there? please, help.
Have figured out that the problem is in the Bootloader. If there is a way to (and I know there is) revert to an older Bootloader version, then the problems will all be solved.
Problem Solved : Dead devices due to tmob 1.72 + Downgrade
OK Guys. Problem Solved : Dead devices due to tmob 1.72 + Downgrade
http://forum.xda-developers.com/viewtopic.php?t=8606
That's great, but unfortunately my device is one step more screwed that others - no bootloader not even working Windows now.
Is there any way to boot directly from SD card?
victor,
can you upgrade or downgrade the bootloader ? If you can, HOW? please post the way to upgrade or to downgrade the bootloader. :shock:
ID64,
I had an XDA I and wiped the bootloader by accident. As far as I know, you have only two options. The first one is JTAG [http://www.xda-developers.com/jtag/] but I don't think the boards have been documented yet for XDA II. The other option is to bring it back to where you bought it from. Tell them there's something wrong with it and play dumb. If you're lucky they might replace it for you, if they assume that you are still within warranty.
Yes, there is a way to upgrade/downgrade the Bootloader. I just don't know how.
The bootloader is locked, that is the problem you have (except for those who cannot access the bootloader).
If you know the right syntax and use the password to the bootloader (it is BOOTLOADER), you can load the proper ROM back using the "LNB" command. However, they have changed the syntax since ITSME's doc on the subject, or he mis-documented the syntax to the bootloader. Or at least his syntax was wrong with 1.06 version.
I got mine fixed, but I have means available that 99.9% of the people out there do not have. If I knew more, I would tell you about the percise syntax in the bootloader -- but alas, I am not a developer.
Victor said:
Yes, there is a way to upgrade/downgrade the Bootloader. I just don't know how.
The bootloader is locked, that is the problem you have (except for those who cannot access the bootloader).
If you know the right syntax and use the password to the bootloader (it is BOOTLOADER), you can load the proper ROM back using the "LNB" command. However, they have changed the syntax since ITSME's doc on the subject, or he mis-documented the syntax to the bootloader. Or at least his syntax was wrong with 1.06 version.
I got mine fixed, but I have means available that 99.9% of the people out there do not have. If I knew more, I would tell you about the percise syntax in the bootloader -- but alas, I am not a developer.
Click to expand...
Click to collapse
Thanks for the reply, Victor. When you talking about commands for bootloder what connection to PC you are talking about? Serial or jtag?
I am referring to the device in the cradle, in bootloader mode. The screen in this mode should read "USB" on top and "V.1.06" (or whatever version) on the bottom. Very hard to read, as there is no backlight.
Anyhow, just for fun.... why don't you try the following:
Uncheck the USB option in Active Sync Connection Settings
Cold boot your system (hard reset)
place the device in the cradle
run the communications software (found on this forum)
When asked which COM port to use, click on the down arrow and see if there is a USB port listed (should be top entry in list).
If so... click it. (if not, you are basically done)
After clicked, then hit return (enter) on the pc a few times.
Anything happen?
Please dont tell me to read the other threads on this issue. Your better off skipping this topic and moving on to the next. I preffer this to go untouched with no replies than to have smart ass comments. Ive been reading pages and pages on how to do this for weeks with no luck. Theres about a few dozen options and with all the suggestions I have no idea where to start, nor what programs to download first, understand what these terms mean, etc. Maybe this isnt my cup of tea and I shouldnt even be attempting this but thats neither here nor there cause the fact of the matter is I screwed things up. Now Im looking for some help from the community.
Its getting real expensive and I need a serious expert who has patience and is very thurough. This is my second unit and I still have the 1st one that is still bricked as well. This is the situation for both. When I go to setting>system>device info, there was no radio version, no protocol version, no IMEI, and the call duration info was zero. I was able to use both units for thier PDA functions but not the phone prtion. I was attempting to SIM unlock and SuperCid em both. Now they are both stuck in bootloader. Im not sure what went wrong but I have done 3 other 8525's with success also updated roms and reverted back and no problems. I just cant seem to get the bricking undone. Now Ive done tutorials on housing swaps, step by step and provided pics as well. You know what, people still ask how to do it. Its a fact guys. some people just need a little more direction than others. What Im trying to say is Im looking for help not criticism, Im a grown man and the last thing I need is for some young punk to flame me,or telling me to read cause Its already been done. I can easily buy another phone but Im willing to learn how to get out of this bricking crap. So its back to reading. TIA
Heres How You Do It
I know how you feel because last night i bricked my 8525 cingular, Okay, If You Can Start Up Your DEvice All You Have to do is reset it to te factory condition and that would help you, unfortunatley all of your data would be lost, but its better than a bricked expensive phone. Oh, but your stuck in bootlaoder, well i have good news for you your not bricked your just stuck, go to the att website and a download and update and the update should recogize your phone even though the computer dosent, after that you have a brand new updated 8525 and that should get you out of bootloader.
ivan345 said:
I know how you feel because last night i bricked my 8525 cingular, Okay, If You Can Start Up Your DEvice All You Have to do is reset it to te factory condition and that would help you, unfortunatley all of your data would be lost, but its better than a bricked expensive phone. Oh, but your stuck in bootlaoder, well i have good news for you your not bricked your just stuck, go to the att website and a download and update and the update should recogize your phone even though the computer dosent, after that you have a brand new updated 8525 and that should get you out of bootloader.
Click to expand...
Click to collapse
Really??? This seems too easy. I'll try anything at this point. So you say its not bricked,just stuck in bootloader? So there is hope? Thats def bice to hear. I'll give it a shot. Thanks
LOL. Tried and and same problem. It sounded too good to be true. Thanks for the tip though
I'm not trying to be smart (believe me, I'm not equipped to do that!) just trying to help determine the exact state so that someone may be better able to help.
You say the phone's are stuck in bootloader, but that you're able to look at the device info on them, and use them for their PDA side. I always thought stuck in bootloader meant that when you switched it on, it came up with the multi-coloured bars but got no further (as if you'd reset it while holding the power and side OK button). Do you mean that the phone's work as normal but have no PHONE side of things, or can you get no further than the bootloader screen when trying to start them up?
Like I said, not trying to split hais just trying to get the exact symptoms for someone cleverer than me to help.
OK by the sounds of it you are definatly NOT stuck in bootloader.
firstly can you please answer the following questions from the wiki:
1. Which is your SPL version?
Put your hermes in bootloader mode (side ok + power button + softreset), the SPL version appears in yellow letters on the upper side
2. Which is your radio bootloader (HTC_BOOT) version?
If your radio version is <=1.27 your HTC_BOOT is 0106 or 0107, the only exception is Softbank X01HT 1.14 radio which has HTC_BOOT 0108
If your radio version is >= 1.30 your HTC_BOOT is 0108
If you don't know which is HTC_BOOT, but you have bootloader 1.01 MFG, 1.10.Oli or 1.04 you can access to the radio bootloader using the command 'rtask a', then type 'rversion' and hit enter (you won't see anything in the screen when you type rversion, because the radio bootloader has no echo, this is normal).
3. Is your device able to boot Windows Mobile OS?
This one is easy: If can you see your today screen and use your phone as a PDA means you can boot OS. If you only see the splash screen, bootloader screen (tri-color) or windows mobile splash screen you can't boot OS.
4. Do you see "No GSM" message in red letters on the first splash screen?
Reset your hermes, you will see some numbers and letters appear in red and disappear after a few seconds... your radio version is there, but if your radio is corrupted for some reason, you will see 'No GSM'.
5. Does your OS rom have KITL enabled?
Hold COMM MANAGER and POWER buttons together and reset with stylus, if you see the message "Select KITL Transport" your OS rom has KITL enabled, otherwise not.
Click to expand...
Click to collapse
Please post the answers back here when you are done.
Stu has an excellent point. Need to know the exact state of the 8525. Exactly what you have done to it....
Example: I used Pof's free HTC SIM unlock and SuperCid program. It appeared to complete successfully. However, now when I start the 8525 up it automatically goes into the tri-color boot loader screen. I had not applied anything else to the 8525 prior to trying to unlock it.
Also, there is a sticky for dead hermes. I bricked mine as well, and was able to get passed it. I posted in the sticky. If you post in that sticky, then someone else may benefit from what you find out. Keeps everything in one place
jeffreyj900 said:
Stu has an excellent point. Need to know the exact state of the 8525. Exactly what you have done to it....
Example: I used Pof's free HTC SIM unlock and SuperCid program. It appeared to complete successfully. However, now when I start the 8525 up it automatically goes into the tri-color boot loader screen. I had not applied anything else to the 8525 prior to trying to unlock it.
Also, there is a sticky for dead hermes. I bricked mine as well, and was able to get passed it. I posted in the sticky. If you post in that sticky, then someone else may benefit from what you find out. Keeps everything in one place
Click to expand...
Click to collapse
Yeah, but, if you used V3a to unlock it, you actually got Oli's BL as part of the deal--hence why you can unbrick it easily!
WELP no smartass comments HUH? Well if you ****ed up 2 phones like this you really must be doing something wrong there buddy. your phone is not stuck in bootloader if you can see the device info thats for damn sure. first thing load SPLV7 on your phone then flash a a complete ROM including radio and OS and then you should be all fixed and if that dont work there is a WHOLE thread just for BRICKED phones so go read like you said you whrere doing.... To me its sounds like you dont have a clue what your doing since you have done this to 2 phones and if you did have a clue your first thing would have been to load SPLv7
so go enjoy your not really bricked bricks
and if i remember right your one of the fools that was making fun af elf because he charge people like you to fix phones over at hofo... so take your problem over there or call elf for some one on one and eat some ****....
Click to expand...
Click to collapse
I gotta give you a lot of credit for that post. Me and a few other members had a bet that it would take less than an hour before the first idiot would surface, Thanks LOL. Who the hell is elf, and I would like to see the post that I had made making fun of anybody. If your gonna try to put someone on blast, back it up. Its assholes like you that a community can do without. Your a true idiot man. No1 needs you around here with that type of attitude. I dont blame you though, I blame your parents for having you. Your mom should have flushed the toilet when she had you then we wouldnt have a piece of **** like you in this world, shame on her. They should be ashamed of themselves for they way you have turned out.
I was able to do all the PDA functions prior to gettting my phones stuck in bootloader. That is were I am now. I got myself stuck in bootloader while trying to load HardSPLv7. I had not done any type of mods or upgrades prior to doing this.
Elf, I want you and that moron to post topics if me bashing you, I cant imagine me doing that. I am 30+ years of age, 3 children and a beautiful wife. I dont have a lot of time, nor do I have the time or care to flame other on these forums. I know that I look to people here and other forums more than they will need me. So please back up that what you are saying and I make sure that I make it an effort to put in my sig that I am an idiot and that you are god. If this it was gets you thru the day, so be it. Just back them comments up. Its a bad tag to put on someone.
My phone reads on tri color screen
Herm100
IPL-1.01
HERM1
SPL-1.40. Olipro
I can do anything other than see this bootloader screen.
(directed at the OP)
Instead of wasting your time replying to posts which are off topic why dont you answer the question posed in my reply...then we can get your two Hermes devices back to working order. Otherwise a mod will inevitably lock this thread and you will be back to square one.??
mrvanx said:
(directed at the OP)
Instead of wasting your time replying to posts which are off topic why dont you answer the question posed in my reply...then we can get your two Hermes devices back to working order. Otherwise a mod will inevitably lock this thread and you will be back to square one.??
Click to expand...
Click to collapse
When I recieved the phone there was no radio version displayed nor was there a protocol version. I also noticed that there was no IMEI that was displyed under the device info. While I was attempting to load the HardSPLv7, that is when I got stuck.
Bro I need serious step by step instructions on this. I've taken all that had been posted about this stuff and a have a pile of info about it. Theres not a whole lot I can do in the boot mode si Im trying to make sure Im doing the steps properly. The info I have given is based on the 8525, I'll work on the TYTN after. Thanks
My appologies.. I just checked HoFo.. You were not one of the idiots on there, as far as I can tell..
Sorry.
Click to expand...
Click to collapse
Appology accepted. Im not worried about man. I got other things to worry about.
Again can you PLEASE answer the questions in my reply?? I need an answer to all FIVE of them, a simple task which will give us the correct status of your device, even if it seems stupid...do it. (the questions im referencing to)
mrvanx said:
Again can you PLEASE answer the questions in my reply?? I need an answer to all FIVE of them, a simple task which will give us the correct status of your device, even if it seems stupid...do it. (the questions im referencing to)
Click to expand...
Click to collapse
1.SPL-1.40 Olipro
2.Dont know. Is there a way to check this now that I am in boot mode.
3.NO.
4.NO
5.Not sure. How can I find this out in the stage Im in
FLiPinoy9oNe6 said:
1.SPL-1.40 Olipro
2.Dont know. Is there a way to check this now that I am in boot mode.
3.NO.
4.NO
5.Not sure. How can I find this out in the stage Im in
Click to expand...
Click to collapse
OK, right you need to flash ANY ROm that contains an OS only, DO NOT try flashing a ROM which has a radio or SPL etc...
Follow my WM5 Downgrade Guide, this will take you through the steps necessary, select the relevant ROMs by HTC and Cingular (found in the wiki).
If that works as desired then update to HArdSPL v7 for both devices then flash a new radio.
mrvanx said:
(directed at the OP)
Instead of wasting your time replying to posts which are off topic why dont you answer the question posed in my reply...then we can get your two Hermes devices back to working order. Otherwise a mod will inevitably lock this thread and you will be back to square one.??
Click to expand...
Click to collapse
wont lock the thread since the guy needs help... but instead i will play janitor and clean it up... since some people will never learn to play nice...
More to the point, have you managed to fix them using the procedure i described?
mrvanx said:
More to the point, have you managed to fix them using the procedure i described?
Click to expand...
Click to collapse
No sir, Ive got two computers working on this right now. One to look at replies and the other to do the update. I had to get a bite to eat so Im back at it. Im trying to connect to sync but not working. Im reading up again on this Sd card deal and mtty so Im trying.
Yes ofcourse i forgot, once you have rebuilt the nbh to make an OS only update (OS,Ext ROM and the 2 splashes) you cant update as normal because there is no activesync connection...the sd card technique is what you need to do. After the device can get into OS and connect over activesync you can do the rest (HardSPL and Radio).
ok mrvanx, after using device monitor I fianlly got a connection and tried downloading a rom. Process goes thru and at 12% it stops and gives me the 262 error message. I do wat it suggest when getting the message with sof reset and try again, still same error.
flash from a damn SDcard and be done with this **** man... your wasting time half assing around... flash an OS.nb from your card and then do all that was told to you from above... this is the only way you will get your hermes working again
mrvanx said:
OK by the sounds of it you are definatly NOT stuck in bootloader.
firstly can you please answer the following questions from the wiki:
Please post the answers back here when you are done.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=9664136#post9664136
Sir please help me
1 HERM100
IPL-1.01
HERM100
SPL-1.40.Olipro
2 - rite now dont show while OS is on
3 yes OS loads ok
4 (yes) No GSM shows while boot
m 05
s 04 No GSM
B 06 D 3.57
5 I can't find as comm manager button confused
hai guys i hav got a htc hd2 and its in white screen
can any one plz help me to solve this problem
actually i'm new with dis pocket pc
here the info is.
PB81110 Hx-BC
Spl-1.42.0000 Xe
Microp(Led) 0X05
Microp(touch) 0x30
did you do anything to your device ?
i'm asking because i have the same problem and didn't do anything at that time, i had a few freezes which forced me to remove the battery and now its stuck on the white screen, i can't flash anything either. I wasn't trying to either before this happened to me, i had winmo 6.5.x running for months, pretty much untouched since i only use android now.
.) i did a hard reset, which went really fast and did nothing.
.) tried hspl 3 ( it says succesfully flashed, but when i load the bootloader the previous version is being displayed there.
.) tried to flash:
-stock rom from sd, i get stuck in the bootloader "serial"
basicly it just does nothing...
i used a 2gb mirco sd card for that, formatted in fat32. stock rom extracted and renamed the RUU_signed.nbh to leoimg.nbh. volume down + reset
-stock rom from pc/usb connection, error/timeout at 0% saying connection problems.
im running out of idea's, i got 1 month warranty left, but im afraid that it will do me no good since i used hspl
You need to update your spl to 2.08.hardspl AND you mostlikely need to flash your radio as well.
I found out that i made a mistake while trying to flash from sd, i didn't put the leoimg at the root of the sd so it didn't get detected. I managed to get rid of the white screen after flashing but its nowhere near functional. It also gave me an error during the flash, but it carried on and finished the flash eventually...
Now when i boot winmo it says something about microp mismatch, i tried two different roms to make sure it had nothing to do with the rom i was using, it didn't... i had the same problem with both. So my guess is that something is damaged, at least hspl is gone now so i can make use of my warranty again, for the people that don't have warranty left i hope somebody comes up with a solution, if there is one, everything points to hardware damage from my point of view. Would be interesting to know how your problem developed...! anyway good luck
arminneman said:
I found out that i made a mistake while trying to flash from sd, i didn't put the leoimg at the root of the sd so it didn't get detected. I managed to get rid of the white screen after flashing but its nowhere near functional. It also gave me an error during the flash, but it carried on and finished the flash eventually...
Now when i boot winmo it says something about microp mismatch, i tried two different roms to make sure it had nothing to do with the rom i was using, it didn't... i had the same problem with both. So my guess is that something is damaged, at least hspl is gone now so i can make use of my warranty again, for the people that don't have warranty left i hope somebody comes up with a solution, if there is one, everything points to hardware damage from my point of view. Would be interesting to know how your problem developed...! anyway good luck
Click to expand...
Click to collapse
could u explain the procedure how to update spl to 2.08.hardspl
and flash radio...
actually i'm new with pocket pc softwares...
could u explain the procedure how to update spl to 2.08.hardspl
and flash radio...
actually i'm new with pocket pc softwares...
kabir.581 said:
could u explain the procedure how to update spl to 2.08.hardspl
and flash radio...
actually i'm new with pocket pc softwares...
Click to expand...
Click to collapse
Yeah sure i can do that, but before i do you need to tell me how you got that white screen in the first place. If it's not because of a failed flash attempt you probably want to keep your phone as it is now, so you can make use of your warranty... hspl makes that impossible!
It's probably a hardware problem, i looked up on that microp mismatch and it looks like a hardware failure, updating your software isn't going to solve that, it might solve the white screen issue, but the phone itself won't be functional. Try to explain what happened so i can give you proper instructions on what to do.
If you can start your phone and enter the bootloader there is no need to sent to service.
Enter bootloader and flash from there HSPL 2.08, and flash radio too.
After that flash MAGLDR and android rom.
guys as i have posted in my last post
that was a condition i have received from costumer.
i guess he tried to update it...
kabir.581 said:
guys as i have posted in my last post
that was a condition i have received from costumer.
i guess he tried to update it...
Click to expand...
Click to collapse
With the phone off, press and hold the Volume Down button and then tap the Power button.
You will get a multicoloured screen with the word 'Serial' at the bottom. What else does the screen display?
What country and phone operator is the phone locked to?
if you want to install a custom rom or eventually android you are going to need hspl, there are enough guides and tutorials on how to do that on this forum, search for it.
if you just want to bring the phone back to life, running windows mobile, you can go to the htc website. Go to the support section and select your phone and look for available rom updates for your phone/serial number.
connect your phone to the pc and follow the instructions of the setup and upgrade... if the phone doesn't get detected, extract ruu_signed.nbn from the setup file and rename it to leoimg.nbn
put that at the root of your sd card formatted in fat32 and boot your phone holding down the volume down button. Follow the instructions, when its done you can reboot the phone and hopefully you can make use of it
berbecverde said:
If you can start your phone and enter the bootloader there is no need to sent to service.
Enter bootloader and flash from there HSPL 2.08, and flash radio too.
After that flash MAGLDR and android rom.
Click to expand...
Click to collapse
Not really, i was able to do that and even flash an upgrade on the phone, but not without errors, the phone didn't function properly after the flash, so its very likely that something is damaged in my case. I send my phone to htc so they can repair it.
it displays the info
PB81110 Hx-BC
Spl-1.42.0000 Xe
Microp(Led) 0X05
Microp(touch) 0x30
Flash a stock rom... in usb mode..
Sent from my HTC HD2 using XDA App
hey guys i tried to download rom from htc support area
but it asked me to enter serial num when i entered the
device serial it gives error.
The serial number you’ve provided appears to be invalid. Please try again.
could any plz tell me the exact procedure and the links to download
what ever it requires its just because i'm new with this softwares
here the info which i got from bootloader mode is:
PB81110 Hx-BC
Spl-1.42.0000 Xe
Microp(Led) 0X05
Microp(touch) 0x30
If you want to install a stock rom you should know what kind of WM has your HD2.
You may not be able to flash any stock rom.There are a lot of versions, regions and it may take some time to try all of them.(http://shipped-roms.com/index.php?category=windows mobile&model=Leo)
If you do not know the version, as you say you have SPL 1.42.
If this is true you can change to HSPL and after that flash any rom you want, and android.
This should solve your problems.
So download the HSPL from the second post. (http://forum.xda-developers.com/showthread.php?t=611433)
Enter bootloader connect the USB cable and flash HSPL.Select 2.08 HSPL from the list.
If you succeed. If you check the bootloader you should see something like Cotulla HSPL 2-08.
Now you can flash any rom you want, the same way: download a rom of your choice, enter bootloader, connect usb cable and start the RUU utility.
If you want to flash android you have to upgrade the radio version.(the same way)
Flash MAGLDR.(the same way).
Flash android.(this is different).
If i am wrong, anybody feel free to correct me.
I would say also do a task29 that contains blank .nbh. you must have hspl 2.08 first to run this then install any custom ROM through PC or your branded ROM through SD card it should work. i hope this helps.
here you go
http://forum.xda-developers.com/atta...0&d=1268260144
dude it works thanks alot
and thanks to every one who has tried to help me
rgds 4m kabir.
Hi. My problem is simple. I cannot pass boot screen. I have T-Mobile G2 Touch (polish version). I decided to load RUU through HBoot because my PC doesnt see pluged in phone. Only RUU version which is working on my phone is T-Mobile PL 3.35 and some other numbers further. Its, what i think the same soft as i had before (before RUU when it started to not passing boot screen) so it hasnt fixed anything. So i thought that maybe other RUU roms will be more helpful, but when Hboot is checking ROM its says that CID is incorrect and i cant install it. I have heard about Goldcard, but in this case, when i cant plug phoneto my PC, i doubt if this is a good idea. My question is- what can i do in this case? I really dont want to have bricked phone. Thanks!
Hello
I have a serious problem with my phone , started yesterday when i restarted my phone on the button in the system ( like restarting a computer). After that it has started but system booted only to htc welcome screen and no further, so rly help me
Methods i have tried:
- battery pull
- htcdev unlock bootloader ( so my bootloader is now unlocked )
nothing works ;(
SHOOTER_U VT SHIP S-ON RL
HBOOT-1.53.0007
eMMC-boot
What rom did you flashed, being s-on will cause issues flashing the kernel, you must have 4ext recovery with smart flash enabled
(Don't ask me for help as I couldn't care if your phone explodes, eh!
I have the exact same problem. Been using my phone issue free for a year and a half. Today I noticed the gps was on but it was not enabled in the "toggles" menu. I rebooted the phone and now it's in an ENDLESS loop that wont pass the white / green HTC logo boot screen.
I can not access recovery it just reboots.
I have tried:
1) flashing stock RUU through fasboot which did go to 100% ... phone still reboot loops
2) flashing latest stock ICS through fastboot (did not work said CID error)
3) Pulled battery and let phone sit
4) s-off with HTC dev unlocker
At this point I'm not sure what to do... I think this may be a catastrophic hardware failure.
Well I do believe my device is a lost cause.
1) I was able to flash 2.17 via RUU but it didn't change a thing.
2) Did the "Brick" method and downgrade to HBOOT 1.40 Still same behavior.
3) flashed 1.13 fully 100% via RUU.. still same thing.
No matter what I do the phone will not get past the white HTC splash screen. It stays on that screen for about 20 seconds then reboots. Also the phone feels really hot behind the cameras (not the battery) I think it's toast. Luckily I have an old HTC hero for a backup so I'm not completely FUBAR but I'll be on craigslist tomorrow looking for something new. Thinking of jumping ship to PagePlus this might be just the right time.